'Valid HTTPS' key-value inconsistent across platforms

We are utilizing the pshtt module to determine M-15-13 compliance for certain websites. We are running pshtt off of a python script that is invoking the 'inspect_domains' method to get all relevant results. As part of our testing we have been running the same method in multiple places, namely our local machine and our cloud instances (the pshtt versions are the same on both), additionally, we are also running tests by calling 'pshtt' directly from bash. In all three examples, we are seeing different results for a couple of specific 'key-value' pairs. Provided below is one example of the issues we are facing.
www.worklife4you.com - for this domain we are seeing three different Boolean values for 'Valid HTTPS'.

'pshtt.inspect_domain' method in a python script running locally returns 'None' for 'Valid HTTPS'.
running pshtt directly off the bash CLI returns 'False' for 'Valid HTTPS'.
running the scan from our cloud instance returns 'True' for 'Valid HTTPS'.

What's really strange about this is that it's the same 'pshtt.inspect_domains' method we are running locally, in this application, it's just wrapped in an EC2 instance. The pshtt version is also up-to-date in the cloud (v.0.3.0) and is the same version as in our local machine (v.0.3.0)

Thank you so much for helping us out with this.

Hi @jsf9k apologies but I wasn't notified when you and @konklone began to respond to my inquiry. I was only made aware of this over the weekend by a colleague. Thank you so much for your help, let me run the tests you two have recommended, and then I'll get back to you. @jsf9k I actually wasn't aware that you can do pip installs directly off of github, that's quite neat, I'll definitely need to try that out as well. However, in the past, we have encountered innumerable difficulties running the pshtt module in AWS Lambda. AWS Lambda, being essentially run in an Amazon Linux AMI, requires these very specific .so files for the pshtt, and all its supporting modules, to run. Getting these .so files is a nightmare and requires us to 'build from source', something my junior developer repertoire lacks.

@refayathaque, no worries.
Regarding running in AWS Lambda, if you want to run pshtt via 18F/domain-scan then you can leverage the Lambda work that @konklone has already done.  You may also find dhs-ncats/lambda_functions useful if you need to build fresher Lambda zip files that what is committed to 18F/domain-scan.

@konklone getting back to you with the JSON objects you asked for.
The first is from our Lambda function running the pshtt scan (FYI we are NOT running pshtt www.worklife4you.com -d -j but we are running pshtt_results = pshtt.inspect_domains([url], {})[0] where url would be www.worklife4you.com)
"Pshtt": {       "Base Domain": "worklife4you.com",       "Base Domain HSTS Preloaded": "False",       "Canonical URL": "https://www.worklife4you.com",       "Defaults to HTTPS": "True",       "Domain": "www.worklife4you.com",       "Domain Enforces HTTPS": "False",       "Domain Supports HTTPS": "False",       "Domain Uses Strong HSTS": "True",       "Downgrades HTTPS": "True",       "HSTS": "True",       "HSTS Entire Domain": "True",       "HSTS Header": "max-age=31536000; includeSubDomains",       "HSTS Max Age": "31536000",       "HSTS Preload Pending": "False",       "HSTS Preload Ready": "None",       "HSTS Preloaded": "False",       "HTTPS Bad Chain": "None",       "HTTPS Bad Hostname": "None",       "HTTPS Expired Cert": "None",       "HTTPS Self Signed Cert": "None",       "Live": "True",       "Redirect": "False",       "Redirect To": "None",       "Strictly Forces HTTPS": "True",       "Unknown Error": "False",       **"Valid HTTPS": "True"**     }
And here is what is being return in my terminal after running pshtt www.worklife4you.com -d -j
{     "Base Domain": "worklife4you.com",      "Base Domain HSTS Preloaded": false,      "Canonical URL": "https://worklife4you.com",      "Defaults to HTTPS": true,      "Domain": "worklife4you.com",      "Domain Enforces HTTPS": false,      "Domain Supports HTTPS": false,      "Domain Uses Strong HSTS": null,      "Downgrades HTTPS": false,      "HSTS": false,      "HSTS Entire Domain": null,      "HSTS Header": null,      "HSTS Max Age": null,      "HSTS Preload Pending": false,      "HSTS Preload Ready": false,      "HSTS Preloaded": false,      "HTTPS Bad Chain": false,      "HTTPS Bad Hostname": true,      "HTTPS Expired Cert": false,      "HTTPS Self Signed Cert": false,      "Live": true,      "Redirect": false,      "Redirect To": null,      "Strictly Forces HTTPS": true,      "Unknown Error": false,      **"Valid HTTPS": null,**
You're absolutely correct about the CSV serialization. So if I run just pshtt www.worklife4you.com and check out the results.csv, I see that Valid HTTPS is False.

@konklone I also just ran worklife4you.com (without the www.) in our Lambda function and what results is Valid HTTPS is None :confused:

@refayathaque, are you using the lambda zip in the domain-scan repo?  I don't think that zip has been updated in a while.  You can use dhs-ncats/lambda_functions to build a new zip for pshtt.
When I run in lambda using a zip I recently built, I get these (admittedly difficult to read - apologies for that) results:
$ ./scan --scan=pshtt --lambda worklife4you.com
[pshtt] Downloading third party data...
[worklife4you.com][pshtt] Running scan...
        Executing Lambda scan...
Results written to CSV.
$ less results/pshtt.csv
Domain,Base Domain,Canonical URL,Live,Redirect,Redirect To,Valid HTTPS,Defaults to HTTPS,Downgrades HTTPS,Strictly Forces HTTPS,HTTPS Bad Chain,HTTPS Bad Hostname,HTTPS Expired Cert,HTTPS Self Signed Cert,HSTS,HSTS Header,HSTS Max Age,HSTS Entire Domain,HSTS Preload Ready,HSTS Preload Pending,HSTS Preloaded,Base Domain HSTS Preloaded,Domain Supports HTTPS,Domain Enforces HTTPS,Domain Uses Strong HSTS,Unknown Error
worklife4you.com,worklife4you.com,https://worklife4you.com,True,False,,False,True,False,True,False,True,False,False,False,,,False,False,False,False,False,False,False,False,False

Note that Valid HTTPS is False, not None.

@refayathaque ah, nevermind, it looks like you built your own zip.  I should read more carefully. :)

@jsf9k thanks for getting back! Yes, we built our own zip file and pushed the deployment package up to Lambda. I am now experimenting with the latest code from the pshtt repo pip install git+https://github.com/dhs-ncats/pshtt.git@develop, I created a local package (which I hope to push up to Lambda and test later), but our pshtt.inspect_domains([url], {})[0] invokation from before isn't working. We get the error pip install git+https://github.com/dhs-ncats/pshtt.git@develop. Not sure what could be happening here. Do you think they changed the method for invoking pshtt scans from within a .py file?
`from future import absolute_import, unicode_literals, print_function
from pshtt import pshtt
import os, sys, json, re, ast, calendar, time
sys.path.insert(1, os.path.join(os.path.dirname(os.path.abspath(file)), 'lib'))
def lambda_handler(event, context):
url = event
print(url)
pshtt_results = pshtt.inspect_domains([url], {})[0]
print(pshtt_results)
lambda_handler('www.worklife4you.com', 'hello_world')`

@refayathaque you need to add a line like this to trigger the work.  This changed about four months ago, and pshtt.inspect_domains([url], {}) is now a generator.

@jsf9k thanks for getting back. We will test this once we get a chance, but before we do, a couple of questions.
Actually triggers the work.
results = list(results)
^
Where is list defined? Are we importing this from pshtt as well?
pshtt returns array of results, but we always send in 1.
return results[0]
^
Is it compulsory for us to return results[0]? In that case, we will need to take this out of our handler and create a separate 'scan' function like what you have.
Thank you so much for all your help!

@refayathaque list is a built-in Python function, it forces a Python iterator (which is what results is when it's returned from pshtt) to evaluate the entire iterator and convert it into a full list of items.

@refayathaque Once you do list(results) you will have a Python list of results like you were expecting from the old code.  You can return the entire thing, take the first one, or do whatever you want with it.

Hi @konklone and @jsf9k, thank you once again for guiding us on how to use the most recent version of the module, we pip installed directly off the repo and used the new scan function invocation. We are now running our scans off the repo, and we seem to be getting the same results as before, at least for three test cases, and we are a little perplexed by the results. Allow me to elaborate.

www.worklife4you.com - Defaults_to_HTTPS : True, Strictly_Forces_HTTPS : True, BUT Supports_HTTPS : False - this isn't making sense to us, if Defaults_to_HTTPS and Strictly_Forces_HTTPS are both True, then surely Supports_HTTPS should be True as well.

worklife4you.com - Defaults_to_HTTPS : False, Strictly_Forces_HTTPS : False, Supports_HTTPS : False - the data here is consistent but because the certificate is bad (SSLyze part of pshtt returning an 'error validating certificate' message) can the scan result not be trusted?

www.buprenorphine.samhsa.gov AND buprenorphine.samhsa.gov - Defaults_to_HTTPS : False, Strictly_Forces_HTTPS : False, Supports_HTTPS : False - data here is consistent with expectations, exhibiting that pshtt works well for some websites. (No certificate errors for both url and domain)

www.aoa.acl.gov - Defaults_to_HTTPS : False, Strictly_Forces_HTTPS : True, Supports_HTTPS : False - this also doesn't make sense to us, how can both Defaults_to_HTTPS and Supports_HTTPS be False when Strongly_Forces _HTTPS is True? We would be remiss if we didn't mention that this scan also resulted in an 'error validating certificate', and as result of this can the result not be trusted?

aoa.acl.gov curiously, results in a slightly different scan outcome - Defaults_to_HTTPS : True, Strictly_Forces_HTTPS : True, Supports_HTTPS : False - again, this makes no sense, it defaults to HTTPS but does not support and force HTTPS? Are we getting these results because this scan also resulted in an 'error validating certificate'?

Thank you!

@refayathaque -

For worklife4you.com, you should get (and I do get) the same results whether you use www or not. pshtt treats those inputs as identical. And for that host, I get False for all of the relevant fields. One key issue is that https://www.worklife4you.com redirects immediately to http://www.worklife4you.com/index.html, which is a downgrade and causes the domain to be flagged as not supporting HTTPS.

Seems like this is working fine.

The results for aoa.acl.gov look True across the board, in pshtt and on Pulse. Let us know if you see anything amiss.

Are you maybe using an old version of pshtt, before we started properly harmonizing inputs with or without www?


WFLY-5188 DistributedWorkManager needs to handle unknown fork responses

https://issues.jboss.org/browse/WFLY-5188
Needs review by JCA team.

Windows Build 2798 is now running using a merge of b085509b0874a5ac4f04beb79ed060b9f8670169

Linux Build 7758 is now running using a merge of b085509b0874a5ac4f04beb79ed060b9f8670169

@pferraro Lets reopen once IronJacamar 1.2.6 is integrated, and hence https://issues.jboss.org/browse/JBJCA-1289

Gotcha.

@jesperpedersen https://github.com/ironjacamar/ironjacamar/pull/381

Linux Build 7758 outcome was SUCCESS using a merge of b085509b0874a5ac4f04beb79ed060b9f8670169
Summary: Tests passed: 3055, ignored: 358 Build time: 00:54:06

Windows Build 2798 outcome was SUCCESS using a merge of b085509b0874a5ac4f04beb79ed060b9f8670169
Summary: Tests passed: 3055, ignored: 358 Build time: 00:58:05

@pferraro FYI, #8044


Adds customization of cropper color and limit black overlay to image only

Original color of cropper color boundaries is set as default value.
Black overlay stripes on sides, which appear when image aspect ration doesn't match canvas aspect ratio, can be confusing when image background color is the same as background color of canvas parent element. In that case image borders aren't visible and stripes that fill canvas appear to be part of the image. When resizing or moving crop you are restricted to image only but due to invisible image borders it appears that some part of image is inaccessible. Limiting overlay to image only fixes the issue.

Useful feature, code looking good, hope Allen can merge this soon?

+1 :D


Setting dumpJson: false throws an error

throws:
youtube-dl: error: no such option: --no-dump-json
I realize I can just leave it off and it works, but if someone programatically sets it to false, it shoudn't prepend --no-

I think that is expectable since no-dump-json is not a valid flag?


feat: support for ipywidgets 8

I'd say we use '*' since we will likely support all jupyterlab versions where possible, and will patch if needed.

Jupyter lab seems to just work, but give a warning "remoteEntry.1e7dc576aad2c0947588.js:1 Unsatisfied version 6.0.2 of shared singleton module @jupyter-widgets/base (required ^1 || ^2 || ^3 || ^4)"
In any case, to get rid of the warning, we could change to "*" for the version number.


Cache Metadata: exact atime and retrievalCount might cause performance problems

In https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/CacheAPIResponseMetadata/explainer.md, a guarantee that lastAccessedAt and retrievalCount are exact might cause problems similar to atime in unix. (Or might not; this is just a worry.) The atime problems were solved by relatime, which makes the stored data less exact, and lazytime, which might lose updates if the system crashes.
I see a note in https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/CacheAPIResponseMetadata/explainer.md#privacy-considerations that lastAccessedAt might have similar-to the relatime semantics anyway: that should be in its initial description, and you should consider guaranteeing that it's at least as new as cachedAt.

Thanks for the heads-up on that @jyasskin! I’m not a browser dev, so I’ve been mainly focused on API ergonomics and web dev needs, but this is great info for us to include for the folks implementing it if there’s interest in moving forward to standardize this as part of the SW (or Cache API) spec.

Just for the record, I don't think the current proposal has performance risks like file system atime.  My read of the proposal is that metadata is updated when the Response is actually passed to respondWith().  Generally this should be much less frequent than file touches, etc.
I'm more worried about how to schedule the write to disk to persist the metadata without contending with future reads.  That could be tricky, but ultimately solvable.


Fix bug: replace int and float with num type in dart

e.g. When data type is double and data value is 1, dart catch error as shown in the following figure

so I use the num type to be compatible with double and int

@kevwan PTAL


document (using ACE in Molly) update

I have identified an opportunity for enhancement in the document. In this particular instance, no output was generated. Consequently, I initiated the simulation, conducted a simple temperature analysis, and subsequently exported the trajectory to both a .xyz file and a .gif format. Should time permit and a consensus be reached, I intend to incorporate additional examples and analysis functions (static, thermodynamics, ...) to further augment the document's content.

Thanks for the initiative.
I would like to have few changes to be made.

The main point with ACEmd is to replace JuLIP with a newer AtomsBase compatible framework. So, I would like for you to replace JuLIP with AtomsIO in examples.
Also you could add that Ovito is one example program, VMD and PyMol few others.
Molly also has functionality to generate visualizations when GlMakie has been loaded that could be very useful to add too (look for Molly docs and example use in Molly basics).

I have not yet added Molly v0.18 to the support list. But will do it soon, that should fix some issues with AtomsBase compatibility...

Thanks for the comments, I will change the first one and add the second one accordingly, as for the third one, I think the visualization in Molly is a bit ugly (just my personal preference), but yes, maybe you're right, just adding it is not bad at all.

Yep we can mention that the Molly visualization is there. And I do agree that it is not up to what Ovito, MD, etc. are.

Hi,
According to your suggestion, I am trying to replace JuLIP with AtomsIO, but I get stuck, I try to run:
fname_xyz = joinpath(pkgdir(ACEmd), "data", "TiAl-big.xyz")
data = ExtXYZ.Atoms(read_frame(fname_xyz))
sys = Molly.System(data, pot)
save_system("test.xyz", sys)
but I got this:

julia> ERROR: MethodError: no method matching element(::Missing)

Any comment for this? I try to read the document of AtomsIO, but unfortunately it is not friendly enough to be read.
My package status is:

[69e0c927] ACEmd v0.1.5
[3b96b61c] ACEpotentials v0.6.3
[1692102d] AtomsIO v0.2.2
[352459e4] ExtXYZ v0.1.12
[945c410c] JuLIP v0.14.3
⌃ [aa0f7f06] Molly v0.17.0
[91a5bcdd] Plots v1.39.0
[1986cc42] Unitful v1.17.0

This seems to be a bug in Molly (or several of them) related to AtomsBase support.
Probably the best way forward is for me to make a PR(s) for Molly to fix these issues.
I hopefully have time for that later this week...

Thank you!

2023年9月14日 11:03，Teemu Järvinen @.***> 写道：
This seems to be a bug in Molly (or several of them) related to AtomsBase support.
Probably the best way forward is for me to make a PR(s) for Molly to fix these issues.
I hopefully have time for that later this week...
—
Reply to this email directly, view it on GitHub https://github.com/ACEsuit/ACEmd.jl/pull/43#issuecomment-1718693333, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFQACPRVOTX26IUTNXNSZ4TX2JXY3ANCNFSM6AAAAAA4VMSKNQ.
You are receiving this because you authored the thread.


Shadow mapping refactoring

refactoring and clean up of shadow rendering code in preparation for cascaded shadow changes
when castShadow is disabled, shadow map is released
lightmapper - shadow maps are shared between lights instead of allocated / destroyed per light
render actions - fix to only keep list of shadow casting directional lights, not all directional lights
added spot light to lights-baked example
lights example is set up to use VSM directional shadow to test all code paths

Approved with some minor observations.


Changing Labels in Admin Panel

As an admin, I want the following two items to be relabeled to "Statuses" and "Universities"

Testing passed successfully.

Test Script:
https://docs.google.com/spreadsheets/d/1d3xMdm471J8NRDWPUaG5CJPbHN9vj5x57Sb0tbwTD7Y/edit#gid=547627265
FYI - @jerrodanzalone @EdemD @kalpanajha


decode_reader doesn't work with socket

The use of typing.BinaryIO doesn't work with a connected (client) socket:
leb128.u.decode_reader(cs)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Program Files\Python310\lib\site-packages\leb128\__init__.py", line 43, in decode_reader
    b = ord(r.read(1))
AttributeError: 'socket' object has no attribute 'read'

Would a Protocol work more elegantly for that case?

socket is a Low-level networking interface and it is not a valid IO object.
You need to call the makefile on it:
with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as s:
    s.connect((HOST, PORT))
    f = s.makefile()              # <-------------------- Here!
    leb128.u.decode_reader(f)

Thanks, @mohanson.
Would switching to a lighter-weight Protocol, rather than a full typing.BinaryIO object, still make sense? (Might that avoid the need to create a file object out of a socket?)

No, the most classic use of leb128 is to read wasm files and dwarf files, so IO is the most suitable typing hints


k-9

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

https://github.com/k9mail/k-9/issues/4960


Unable to Run How-To Examples with Von Network - CommonInvalidState()

I have spun up a von test network on my local machine following instructions here: https://github.com/bcgov/von-network.
I am attempting to run the write-did-and-query-verykey How-To example, locally, while using the VON Network. When I running the code I see this error:
CommonInvalidState()
'Error: Invalid library state\n  Caused by: Ledger merkle tree is not acceptable for current tree.\n'
I didn't think I needed to adjust the genesis txn information. When vieiwng the genesis JSON at localhost:9000/genesis, the structure matches what I have in my pool.txn file after I run pool.create_pool_ledger_config().

You need to make sure von-network is configured for your computer's local IP (rather than an IP which is internal to a docker network, which is the default).
Try starting von-network as ./manage start <your local IP> --logs.  You can fetch the genesis file as http://localhost:9000/genesis, and then make sure indy-sdk is pointing to this file to configure the ledger.
You can also use a local ledger as described in the README here:  https://github.com/hyperledger/indy-sdk#how-to-start-local-nodes-pool-with-docker

Thank you that worked.


there's a bug to delete lambda versions

self.lambda_client.delete_function(FunctionNmae=function_name,Qualifier=version)
FunctionNmae should be FunctionName。

There's a PR up for that at #1514


use test tokens from python lib

Brief summary of the change made

With this change, the tokens generated now path the current python library version.  Closes #35
Note: I converted the jsonl file from the python repo to json for convenience.
Are there any other side effects of this change that we should be aware of?
I noticed few of the sample test cases had value_raw as null which results in a crash  (not a defined behaviour)
Describe how you tested your changes?

Pull Request checklist
Please confirm you have completed any of the necessary steps below.

[ ] Meaningful Pull Request title and description
[ ] Changes tested as described above
[ ] Added appropriate documentation for the change.
[ ] Created GitHub issues for any relevant followup/future enhancements if appropriate.

Hey @beesaferoot
there is some inconsistency in the Python library itself regarding the null values. More information here: https://github.com/EnAccess/OpenPAYGO-python/issues/25
It's not really clear to me what the "correct" behaviour should be. I'd say let's leave your PR like it is for now. But maybe we come back to it later on, once we clarified to intended behaviour 👌

Regarding the test cases: I would prefer both repos (or all for that matter 😉 ) to use the exact same test cases file. I found JSONL to be more comfortable in Python. Is it a big trouble to use JSONL in JavaScript? Quick Google seem to suggest there might not be a super easy way to do it 😩
WDYT? I could also change the Python lib to use JSON instead.

I could also change the Python lib to use JSON instead.

@dmohns I think Python also works pretty well with json this would be preferred.


[rfc] configmap/crd based DAGs

What is your feature request?
Hello, when deploying dags from different sources it would be nice to leave a stable airflow installation untouched, and by having every source have its own gitrepo. In addition to this, it would be nice to use tools like skaffold during development to hot-deploy or even live edit code (without committing every time you make a change).
Therefore, another way of putting DAGs and requirements would be nice: putting different DAGs in configmaps and whenever a configmap changes, the files are updated automatically. I now do this using flant/shell-operator and the python hook script. Then tools like skaffold could take care of deploying the configmaps for ergonomic development.
https://gist.github.com/kervel/c557f888ffe202f738753c2218766999
I put this as a request for comments to see if others considered something similar, and how other teams manage the situation where you have one airflow instance that runs multiple (not necessarily related) DAGs.
What alternatives have you considered?

git sync with a central gitrepo where everybody sends PRs to to deploy stuff.
using skaffold to live sync the DAGs when editing them directly using the airflow helm chart.

@kervel this is an interesting idea, but what are you needing from the chart?

i don't know, was more of an open question. it could become a new method for deploying DAGs as part of the chart (but i wonder if you fancy the method with the shell-operator and the RWX volume which some would consider quick&dirty, wonder if there could be other approaches). in that case we could try to pack our changes as a PR.
or maybe its just an idea that has no place here, in which case i'm fine with closing the issue off course.


Store bag ID against the package

This involves setting up an API endpoint that the Wellcome storage service can notify when it has a successful or failed result for the ingest. On success, the bag ID is extracted and written to the Package object.
A couple of things to note here:

The Wellcome storage service doesn't currently retry the callback if it failed. It's possible the callback will be missed, e.g. if Archivematica is temporarily unvailable. So if the callback hasn't been requested after a little while (say a minute) we check the ingest URL to see whether the ingest is complete and the callback was attempted. If it was, we use the result from the ingest body. This isn't ideal but is better than waiting forever for the result.

The callback endpoint requires authenticatoin. The AM storage service supports authentication via API key, which can be included in an Authorization header or as a URL parameter. Using a URL parameter means the callback can be set up with no modification, however it means the API key is more exposed, e.g. in logs or in the ingest JSON. Sending it as a header would be better in that regard but would likely also require extra work on the Wellcome storage service to support this.

Just storing the bag ID for now. May be useful to also store the ingest ID.

I've made a first pass at an implementation of this on the wellcome-storage-service branch but it still needs a few refinements.


Update Qld Permits - Labels

change pref labels to include abbreviation e.g. QL - Greenhouse Gas (GHG) Lease
copied old prefLabels into altLabels
reviews
tech - @LukeHauck or @DavidCrosswellGSQ
vocab owner - @GSQ-AI
tester/sme - @LizDerrington
fyi - @lisa-woody

Looks good Vance


exception while updating with master branch

Bug report

@vaishaliwebkul,
Please run composer dump-autoload.

fixed


pip install requirements.txt fails - is it because I'm not using Docker?

Hello everyone.
In Short:
I'm on windows 10, Python 3.7.6.
I wish to know if Docker is mandatory.
I am unable to install dependencies, and I'm not sure it's some local issue or simply installation can't be done without docker.
In Details:
pip install -r requirements.txt fails becuase a specific package -it says Failed building wheel for python-axolotl-curve25519.
When I try to only install this package - running pip install python-axolotl-curve25519. It also fails.
cmd output:
Collecting python-axolotl-curve25519
  Using cached https://files.pythonhosted.org/packages/59/ca/c8111718bcc8da18e9b9868e784293232a58c57159a5ea18f00ee967258f/python-axolotl-curve25519-0.4.1.post2.tar.gz
Building wheels for collected packages: python-axolotl-curve25519
  Running setup.py bdist_wheel for python-axolotl-curve25519 ... error
  Complete output from command c:\users\shaha\appdata\local\programs\python\python36\python.exe -u -c "import setuptools, tokenize;__file__='C:\\Users\\shaha\\AppData\\Local\\Temp\\pip-build-2yaqq9jd\\python-axolotl-curve25519\\setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d C:\Users\shaha\AppData\Local\Temp\tmphs1iyrr2pip-wheel- --python-tag cp36:
  c:\users\shaha\appdata\local\programs\python\python36\lib\site-packages\setuptools\dist.py:331: UserWarning: Normalizing '0.4.1-2' to '0.4.1.post2'
    normalized_version,
  running bdist_wheel
  running build
  running build_ext
  building 'axolotl_curve25519' extension
  error: Microsoft Visual C++ 14.0 is required. Get it with "Microsoft Visual C++ Build Tools": http://landinghub.visualstudio.com/visual-cpp-build-tools

  ----------------------------------------
  **Failed building wheel for python-axolotl-curve25519**
  Running setup.py clean for python-axolotl-curve25519
Failed to build python-axolotl-curve25519
Installing collected packages: python-axolotl-curve25519
  Running setup.py install for python-axolotl-curve25519 ... error
    Complete output from command c:\users\shaha\appdata\local\programs\python\python36\python.exe -u -c "import setuptools, tokenize;__file__='C:\\Users\\shaha\\AppData\\Local\\Temp\\pip-build-2yaqq9jd\\python-axolotl-curve25519\\setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record C:\Users\shaha\AppData\Local\Temp\pip-586b7wmv-record\install-record.txt --single-version-externally-managed --compile:
    c:\users\shaha\appdata\local\programs\python\python36\lib\site-packages\setuptools\dist.py:331: UserWarning: Normalizing '0.4.1-2' to '0.4.1.post2'
      normalized_version,
    running install
    running build
    running build_ext
    building 'axolotl_curve25519' extension
    error: Microsoft Visual C++ 14.0 is required. Get it with "Microsoft Visual C++ Build Tools": http://landinghub.visualstudio.com/visual-cpp-build-tools

    ----------------------------------------
**Command "c:\users\shaha\appdata\local\programs\python\python36\python.exe -u -c "import setuptools, tokenize;__file__='C:\\Users\\shaha\\AppData\\Local\\Temp\\pip-build-2yaqq9jd\\python-axolotl-curve25519\\setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record C:\Users\shaha\AppData\Local\Temp\pip-586b7wmv-record\install-record.txt --single-version-externally-managed --compile" failed with error code 1 in C:\Users\shaha\AppData\Local\Temp\pip-build-2yaqq9jd\python-axolotl-curve25519\**
You are using pip version 9.0.1, however version 20.2.2 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.```

I Googled this error of course and did not find any good solution.

Thanks the helpers!

I have the exact same issue

I only managed to make it work that way in linux

I install standalone Microsoft Visual C++ 14.0 ... fail
Then I try install Microsoft Visual C++ using Microsoft C++ Build Tools from https://visualstudio.microsoft.com/visual-cpp-build-tools/
It solve the problem.
Install MSVC using Build Tools takes about 4GB disk space. But at least it works! :-)

I install standalone Microsoft Visual C++ 14.0 ... fail
Then I try install Microsoft Visual C++ using Microsoft C++ Build Tools from https://visualstudio.microsoft.com/visual-cpp-build-tools/
It solve the problem.
Install MSVC using Build Tools takes about 4GB disk space. But at least it works! :-)

thank you so much.  this solution was perfect.


Mod license?

Hi there, I wanted to inquire about whether this mod had a license to go with it? Is it fine to use this mod in public modpacks? Thanks in advance!

The license is DO NOT USE AT ALL.
Update your Forge this is no longer needed.

OK, it was in Tekkit so I had no idea whether it was needed in modern packs. Thanks for clarifying!

Tekkit doing it wrong, color me surprised -.-


Does the Solid example work with Vite 5 since I get an issue loading the pdf.worker.js file?

I tried out the Solid.js code example and I get this error. Is this because I use Vite with it? Is there a workaround to this?

I checked the file paths and http://localhost:5173/node_modules/.vite/deps/pdfjs-dist/build/pdf.worker.js does not exist for me. There isn't anything in deps actually related to it.
If I run pnpm i pdfjs-dist, I will get the node_modules/pdfjs-dist/build/pdf.worker.mjs file (but it is .mjs and not .js?) and I wondered if I just need to link this file, but I am not sure how.

Hi @Dima-369,
Here's an example PDFSlick project for Solid created with Vite. Seems to be working fine locally, but also when deployed at https://solid-pdfslick.stojkov.me/
Can you check which pdfjs-dist version you're using? That .mjs extension hints you might be using version 4.x.x (PDFSlick uses version 3)

Hey, thanks for the answer! I tried with the following steps:
git clone https://github.com/van100j/solid-pdfslick
cd solid-pdfslick
pnpm i
pnpm run dev

Then I see the exact same error as above, supposedly because pdfjs-dist is not automatically installed? Or at least, not in the directory as noted above. So, I downloaded it like this from https://github.com/mozilla/pdfjs-dist (is it fine from this repository?) which seems to be version 3.
git clone git@github.com:mozilla/pdfjs-dist.git node_modules/.vite/deps/

I tested this, but then I always see this error. What am I missing? I can not find any info in the README about pdfjs-dist setup. I also tried the versions from https://github.com/mozilla/pdf.js/releases?page=2

Hey @Dima-369
I'm actually able to reproduce your error — when I run the exact commands as you are (with pnpm instead of npm) I'm also experiencing the same issues. Running the commands with npm seems fine though.
Personanly I'm a npm user, so if you could use npm that'd be great. In the meantime I'll try to investigate what's really happening with pnpm, although it seems kinda weird because we're being explicit with the pdfjs-dist version

Running the commands with npm seems fine though.

Indeed, I can confirm that! Thanks for the hint.
I was able to fix with pnpm. You just need to add "pdfjs-dist": "3.11.174" into the dependencies in package.json - then it works in both npm and pnpm.
Do you want to adjust the repository with this, maybe?

Thanks @Dima-369! You're right, we actually need pdfjs-dist": "3.11.174".
Up for submitting a PR with this update?

Up for submitting a PR with this update?

Sure. I will do it in this repo and in https://github.com/van100j/solid-pdfslick

@Dima-369 ended up updating the pdfjs-dist version in the core package. Solid and other projects should work fine with pnpm too, I've just tried it out with the example at https://github.com/van100j/solid-pdfslick and the new version, seems ok.
Closing this issue, let me know if you experience further issues with this or anything else.
Thanks again for reporting and soving this!


.color() function to validate that a string is a valid color.

Hi, I would want a .color() function that you append on a z.string() to validate that it's a valid color.
This feature would be useful in many cases. For example if you want to make sure that payload coming from client/frontend contains valid color codes, directly with zod.
I believe that by default .color() should accept all of the standard forms of colors eg:

rgb
rgba
hex
hsl
hsv
Extended colors eg. green coral steel blue

But also offer some way to only accept (a) certain color type(s), alternatively filter out unwanted color types.
Might not be that of a realistic feature, but some way to convert the payload to a specified color type. For example if a hex value gets inputted, it gets converted to the specified type, rgb for example . I know this might cause some inaccuracy when converting from certain types to others, but still a feature i would want.
I am open to make this feature myself later on if it gets decided that it's a needed feature.

Hello! Just a suggestion that you can use z.string().refine() to implement a custom color validator. Maybe something simple like:
import color from "color-string";

export function colorValidator(val: string) {
  try {
    return color.get(val) != null;
  } catch {
    return false;
  }
}

const validColorSchema = z.string().refine(colorValidator);
validColorSchema.parse("#FFF");

@eswarty thanks! Ill definitely try that out. Using .regex would also work I believe.


Improve the UI/UX for "Known Breakages" section

Feature Request
Description:
We need to improve the information displayed under the Known Breakages section by achieving the following -

[x] Remove the box UI when an accordion item is expanded
[x] Remove the separator line after the last item
[x] Remove the bullets/feature list mentioned under GIS & GSI
[x] Remove the full-stops after each detection title
[x] Shorten the detection title text and make it standardized
[x] Make the CTA under each detection more informative - Example: To inquire further about the same, please visit the support forum

Released in version 0.8.0


x/tools/go/packages: TestIssue32814/Modules is flaky

2022-08-24T18:36:56-587a153-8188bf6/windows-amd64-longtest-newcc
2022-08-24T18:08:33-587a153-b60432d/windows-amd64-2016
2022-08-24T17:56:56-587a153-cfae70c/windows-amd64-2016-newcc
2022-08-24T17:12:07-587a153-8a86b94/windows-amd64-longtest
2022-08-24T15:37:38-587a153-d5aa088/linux-amd64-nocgo
2022-08-24T14:31:08-587a153-f983a93/windows-386-2008
2022-08-24T12:12:12-587a153-b5a9459/windows-amd64-longtest
2022-08-24T08:17:52-587a153-1ab6b79/linux-amd64-clang
2022-08-24T08:17:52-587a153-1ab6b79/windows-amd64-longtest
2022-08-23T20:00:03-587a153-e1114fd/aix-ppc64
2022-08-19T17:47:49-e55fb40-a73808e/windows-amd64-2016
2022-08-19T17:47:49-e55fb40-a73808e/windows-amd64-longtest
2022-08-19T17:28:00-e55fb40-0a1da09/windows-amd64-2016
2022-08-19T16:17:50-e55fb40-5729419/linux-arm64-aws
2022-08-19T16:17:50-e55fb40-5729419/windows-386-2008-newcc
2022-08-19T16:12:50-e55fb40-3204e62/linux-amd64-unified
2022-08-19T16:12:50-e55fb40-3204e62/windows-amd64-longtest-newcc
2022-08-19T03:32:27-e55fb40-6001c04/windows-amd64-2016-newcc
2022-08-19T03:09:05-e55fb40-a409356/windows-amd64-longtest-newcc
2022-08-19T01:34:22-e55fb40-ee833ed/windows-amd64-2016
2022-08-19T01:34:22-e55fb40-ee833ed/windows-amd64-longtest-newcc
2022-08-19T01:31:59-e55fb40-e51b3ae/linux-s390x-ibm
--- FAIL: TestIssue32814 (0.00s)
    --- FAIL: TestIssue32814/Modules (5.67s)
        packages_test.go:2038: Errors for fmt pkg: got [C:\workdir\go\src\fmt\print.go:383:29: v.Type().String undefined (type reflect.Type has no field or method String)], want none
FAIL

cc @golang/tools-team

It looks like the failures stopped on 8/24.
@mdempsky, was this fixed by https://go.dev/cl/425362? Seems likely.

Yeah, seems likely to me too. The date range starts around when GOEXPERIMENT=unified was enabled by default, and then stops around when we added that fix, which was being caught on the race-detector bots.


portico: Rename Sign in to Log in.

We currently use both Log in and Sign in for this action. Choosing either would be better than having a mix:

Let's go with Log in.
@gooca, would this be up your alley?

The mobile app (and Electron) also uses "Sign in" terminology, so should I create an issue in those repositories as well?

good catch! yes, and also "Register" -> "Sign up", if they are using Register terminology.

@zulipbot claim

@rishig  I have included the required changes in my previous PR #7684.

@rishig What is the status on this one? Can I take this up?

@aedorado you can try picking this up; https://github.com/zulip/zulip/pull/8233 has some prior work that you should look at though (seems to not work, so feel free to do your own work on it).

@zulipbot claim


Suggestions appearing only randomly

Hello, so the suggestions always properly appear in the buffer (in grey) but are only very randomly suggested in the popup window in insert mode:

This is happening more often than not, not sure to what it's related. Any suggestions on how to debug it?
Also, LspInfo is giving me this state on copilot.lua:

It seems it's not being attached to the buffers all the time?
Neovim version: 0.6.1
nvim-cmp config:
local default = {
   snippet = {
      expand = function(args)
         require("luasnip").lsp_expand(args.body)
      end,
   },
   formatting = {
      format = function(entry, vim_item)
         local icons = require "plugins.configs.lspkind_icons"
         vim_item.kind = string.format("%s %s", icons[vim_item.kind], vim_item.kind)

         vim_item.menu = ({
            nvim_lsp = "[LSP]",
            nvim_lua = "[Lua]",
            buffer = "[BUF]",
         })[entry.source.name]

         return vim_item
      end,
   },
   mapping = {
      ["<C-p>"] = cmp.mapping.select_prev_item(),
      ["<C-n>"] = cmp.mapping.select_next_item(),
      ["<C-d>"] = cmp.mapping.scroll_docs(-4),
      ["<C-f>"] = cmp.mapping.scroll_docs(4),
      ["<C-Space>"] = cmp.mapping.complete(),
      ["<C-e>"] = cmp.mapping.close(),
      ["<CR>"] = cmp.mapping.confirm {
         behavior = cmp.ConfirmBehavior.Replace,
         select = true,
      },
      ["<Tab>"] = cmp.mapping(function(fallback)
         if cmp.visible() then
            cmp.select_next_item()
         elseif require("luasnip").expand_or_jumpable() then
            vim.fn.feedkeys(vim.api.nvim_replace_termcodes("<Plug>luasnip-expand-or-jump", true, true, true), "")
         else
            fallback()
         end
      end, { "i", "s" }),
      ["<S-Tab>"] = cmp.mapping(function(fallback)
         if cmp.visible() then
            cmp.select_prev_item()
         elseif require("luasnip").jumpable(-1) then
            vim.fn.feedkeys(vim.api.nvim_replace_termcodes("<Plug>luasnip-jump-prev", true, true, true), "")
         else
            fallback()
         end
      end, { "i", "s" }),
   },
   sources = {
      { name = "copilot" },
      { name = "nvim_lsp" },
      -- { name = "luasnip" },
      -- { name = "buffer" },
      -- { name = "nvim_lua" },
      -- { name = "path" },
   },
}

Packer config:
     {
         "zbirenbaum/copilot.lua",
         event = "InsertEnter",
         config = function()
            vim.schedule(function()
               require("copilot").setup()
            end)
         end,
      },
      {
         "zbirenbaum/copilot-cmp",
         after = { "copilot.lua", "nvim-cmp" },
      },

This is an issue in copilot.lua for .6. I believe I have a fix that should be coming out soon, I'll let you know once it's in.
It's a shame I'll just end up taking all the .6 stuff out after the full release of .7 this month but I'll do my best to support it up until then

I just pushed an update to copilot.lua that should fix the attach issue. Can you test it out?

Additionally, I changed the plugin to call getCompletionsCycling so that cmp displays all copilot completions available, but this seems to be associated with some level of server response delay. I'm working on a solution for it, but I think the trade off here is as follows:
Either 1: We make the plugin as responsive as copilot.vim, by fetching completions every time a new char is inserted (this has cpu usage ramifications), or two, we let cmp debounce as it is, which causes a bit more pop in, but keeps everything lag free and running smoothly.
I'll likely have to make a poll for this, or just implement both when I have time and let people choose.

Thanks for the quick update, unfortunately it's still not attaching properly.  Indeed there's a choice to be made, I personally prefer smoothness, I don't mind waiting a second or two for this. Don't bother too much, I know .7 is coming out soon so it would be unnecessary. I'll try and see if my config is not breaking with the new version and do the switch.

I think this may have been addressed via my latest commit. Would you mind trying it out? I fixed a number of attach related issues, and just now fixed the randomness of the completions due to a bug with start and end points for users who had the plugin attaching.

It seems to work more reliably indeed. I still have some cases where it won't suggest the greyed code in the buffer, but I'm not sure if it's your plugin directly I think it's cmp.
Thanks for the reactivity, it's nice to be able to finally use it consistently! Keep up the good work

It seems to work more reliably indeed. I still have some cases where it won't suggest the greyed code in the buffer, but I'm not sure if it's your plugin directly I think it's cmp.
Thanks for the reactivity, it's nice to be able to finally use it consistently! Keep up the good work
EDIT: From what LspInfo and CmpStatus are saying it's attaching properly every time now

Super glad to hear this!
Could you expand on what you mean by not suggesting the greyed our code? I'm trying to figure out if you are talking about a behavior I'm aware of or not and it's not entirely clear.


ASAP-Alchemy: Charge ligands locally

In production, we currently see issues with charging ligands which causes jobs to fail, one workaround would be to charge ligands locally using openeye or ambertools and supply these charges which should be respected by openfe during the system generation. This also allows us to work around the current limitation of only being able to use AmberTools to generate charges.
cc: @JenkeScheen

Some links to the charging code in openfe, current method new settings based method


Hides Player bar buttons

The script also hides Player bar buttons, as the Subtitles, Mini Player, Cinema mode, Autoplay and custom buttons.

I just downgraded to v3.8 and it seems to be fine.
On Sunday, June 23, 2024 at 08:25:49 PM GMT+3, Kevinuara @.***> wrote:
Hi! Likewise, since like yesterday, that script, while using it with TamperMonkey on Google Chrome on Windows 10, hides several button. I can no longer go into theater mode and when using a playlist, it won't autoplay the next video.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

the newer versions use the youtube embedded video player, you can downgrade to 5.3 (click the Raw button on upper right) and that version is mostly functional. it sometimes gets detected on prerolls, but you can refresh past it till it's fixed, at least


[improvement-3512][Flink-Doris-connector] replace lable to label

What changes were proposed in this pull request
plz close :

#3512
replace lable to label

Brief change log

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): (yes / no)

@wolfboys @caicancai PTAL


Median Hashing

A fairly straight port of the implementation from https://github.com/alexdelorenzo/img_hash, with some added documentation and minor changes. The motivation behind the addition is compatibility with Median pHash, see #12

Thanks!


[FLINK-28050][connectors] Migrate StreamExecutionEnvironment#fromElements() implementation to FLIP-27 Source API

What is the purpose of the change
The purpose is to change the internal implementation of StreamExecutionEnvironment#fromElements() that is currently based on SourceFunction API (deprecated, due to be removed) to using FLIP-27 Source API.
Brief change log

Moves DataGeneratorSource tests into a separate module to avoid circular dependencies when adding flink-connector-datagen dependency to flink-streaming-java
Moves OutputTypeConfigurable from flink-java-streaming into flink-core to enable adding support for source.setOutputType() (triggered by stream.returns()) in DataGeneratorSource (required to handle, for instance, Avro GenericRecords).
Migrates StreamExecutionEnvironment.fromElements() methods from using FromElementsFunction(SourceFunction) to the new FromElementsGeneratorFunction (implements GeneratorFunction from FLIP-27 DataGeneratorSource)

Verifying this change
The fromElements() method was already largely covered by the existing tests. Additionally:

Added FromElementsGeneratorFunction integration tests
Added  tests to StreamExecutionEnvironmentTest
Added  tests to StreamExecutionEnvironmentITCase

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know) - for fromElements.
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation
This is an internal change.

The addition of the OutputTypeConfigurable was required to achieve feature parity and compatibility with the existing fromElements API (https://issues.apache.org/jira/browse/FLINK-21386). Alternatively, we could provide a fromElements method that accepts TypeInformation directly, rather than having to "fix" it with returns().

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure

@zentol thanks a lot for the review!!
I addressed all comments from your first pass, PTAL.

@zentol I made two major changes as per our discussions above:

https://github.com/apache/flink/commit/2712c1813ca6420905e06b9e417de0eb61d586d9  - direct type passing without the requirement to use returns() (please see my comment above)
https://github.com/apache/flink/pull/23553/commits/78cb92bc86e9dded9bf2458de119d549be7ad281 - allow parallel execution of fromElements Sources

The second one might need some additional test fixes, but I cannot get to them at the moment because of the japicmp failures:
Failed to execute goal io.github.zentol.japicmp:japicmp-maven-plugin:<IP_ADDRESS>_m325:cmp (default) on project flink-streaming-java: There is at least one incompatibility: org.apache.flink.streaming.api.environment.StreamExecutionEnvironment.fromElements(org.apache.flink.api.common.typeinfo.TypeInformation,java.lang.Object[]):CLASS_GENERIC_TEMPLATE_CHANGED -> [Help 1]

This is the diff:
	+++* NEW METHOD: PUBLIC(+) FINAL(+) org.apache.flink.streaming.api.datastream.DataStreamSource<OUT> fromElements(org.apache.flink.api.common.typeinfo.TypeInformation<OUT>, java.lang.Object[])
		+++  NEW ANNOTATION: java.lang.SafeVarargs
		GENERIC TEMPLATES: +++ OUT:java.lang.Object

What is the issue with adding the new method?

@flinkbot run azure

What is the issue with adding the new method?

By default you may not add new methods to classes because it can break downstream classes. Personally I'd say it's fine to do it here though.

@flinkbot run azure

@zentol thanks for the feedback. The only remaining item currently is the architecture tests failures. The problem is that running the same command that is executed in Azure (below) locally on the same commit does not produce any errors. Enabling store updates does not modify any files either. Running ArchitectureTest in IntelliJ passes (including the the CONNECTOR_CLASSES_ONLY_DEPEND_ON_PUBLIC_API).
mvn --no-snapshot-updates -Dscala-2.12 -Pskip-webui-build -Dflink.tests.with-openssl -Dflink.tests.check-segment-multiple-free -Darchunit.freeze.store.default.allowStoreUpdate=false -Dpekko.rpc.force-invocation-serialization -Dflink.hadoop.version=2.10.2 -Dscala-2.12 -pl !flink-annotations,!flink-test-utils-parent/flink-test-utils,!flink-state-backends,!flink-state-backends/flink-statebackend-changelog,!flink-state-backends/flink-statebackend-heap-spillable,!flink-state-backends/flink-statebackend-rocksdb,!flink-clients,!flink-core,!flink-java,!flink-optimizer,!flink-rpc,!flink-rpc/flink-rpc-core,!flink-rpc/flink-rpc-akka,!flink-rpc/flink-rpc-akka-loader,!flink-runtime,!flink-runtime-web,!flink-scala,!flink-streaming-java,!flink-streaming-scala,!flink-metrics,!flink-metrics/flink-metrics-core,!flink-external-resources,!flink-external-resources/flink-external-resource-gpu,!flink-libraries,!flink-libraries/flink-cep,!flink-libraries/flink-cep-scala,!flink-libraries/flink-state-processing-api,!flink-queryable-state,!flink-queryable-state/flink-queryable-state-runtime,!flink-queryable-state/flink-queryable-state-client-java,!flink-container,!flink-dstl,!flink-dstl/flink-dstl-dfs,!,!flink-table,!flink-table/flink-sql-parser,!flink-table/flink-table-common,!flink-table/flink-table-api-java,!flink-table/flink-table-api-scala,!flink-table/flink-table-api-bridge-base,!flink-table/flink-table-api-java-bridge,!flink-table/flink-table-api-scala-bridge,!flink-table/flink-table-api-java-uber,!flink-table/flink-sql-client,!flink-table/flink-sql-gateway-api,!flink-table/flink-sql-gateway,!flink-table/flink-table-planner,!flink-table/flink-table-planner-loader,!flink-table/flink-table-planner-loader-bundle,!flink-table/flink-table-runtime,!flink-table/flink-table-code-splitter,!flink-table/flink-table-test-utils,!,!flink-contrib/flink-connector-wikiedits,!flink-filesystems,!flink-filesystems/flink-azure-fs-hadoop,!flink-filesystems/flink-fs-hadoop-shaded,!flink-filesystems/flink-gs-fs-hadoop,!flink-filesystems/flink-hadoop-fs,!flink-filesystems/flink-oss-fs-hadoop,!flink-filesystems/flink-s3-fs-base,!flink-filesystems/flink-s3-fs-hadoop,!flink-filesystems/flink-s3-fs-presto,!flink-fs-tests,!flink-formats,!flink-formats/flink-format-common,!flink-formats/flink-avro-confluent-registry,!flink-formats/flink-sql-avro-confluent-registry,!flink-formats/flink-avro,!flink-formats/flink-sql-avro,!flink-formats/flink-compress,!flink-formats/flink-hadoop-bulk,!flink-formats/flink-parquet,!flink-formats/flink-sql-parquet,!flink-formats/flink-sequence-file,!flink-formats/flink-json,!flink-formats/flink-csv,!flink-formats/flink-orc,!flink-formats/flink-sql-orc,!flink-formats/flink-orc-nohive,!flink-connectors/flink-file-sink-common,!flink-connectors/flink-hadoop-compatibility,!flink-connectors,!flink-connectors/flink-connector-files,!flink-metrics/flink-metrics-dropwizard,!flink-metrics/flink-metrics-graphite,!flink-metrics/flink-metrics-jmx,!flink-metrics/flink-metrics-influxdb,!flink-metrics/flink-metrics-prometheus,!flink-metrics/flink-metrics-statsd,!flink-metrics/flink-metrics-datadog,!flink-metrics/flink-metrics-slf4j,!,!flink-connectors/flink-connector-base,!,!flink-tests,!flink-yarn,!flink-yarn-tests,! verify

@zentol  I can confirm that the reason for the discrepancy in the local and the remote Architecture Tests execution is the Java version. Using Java 11 the tests pass, using Java 8 they fail (as in CI). Probably something to do with classloading/modules. Is this a known issue? I could not find a matching ticket in JIRA.

Using Java 11 the tests pass, using Java 8 they fail (as in CI).
Is this a known issue?

not sure wether this is your issue or not some time ago we've faced this
https://github.com/TNG/ArchUnit/issues/1124

@snuyanzin thanks for the pointer, is seems to be related, albite a somewhat different issue. The constructor for which ArchUnit previously added a violation was removed, but running it with Java 11 did not remove the violation itself:
https://github.com/apache/flink/pull/23553/commits/e0b25aed71328dadd3ca6ac868704e8189d1098f#diff-dda3e2858bbd4222b54379ad6d998011d90a8aa8536ecc845284a98001960d7dL67

@zentol CI is green

Do you want to cleanup the git history a bit or shall I just squash everything?

I'll do it, thanks!
One thing to clarify before we merge - I just noticed yesterday that in a somewhat similar situation the decision was made to go via the deprecation route instead of the in-place implementation substitution:
https://issues.apache.org/jira/browse/FLINK-19494?focusedCommentId=17206787&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17206787
I guess we do need to consider cases when fromElements() might be used in production environments to stream in some small bootstrap data sets.

@zentol some thoughts:

I like the idea of exposing fromData. There is no good reason for both fromElements and  and fromCollection methods to exist - they do the same thing and are described in their entirety by the method parameters.
Keeping fromData on the environment has some benefits:

Exposing factory methods on the DataGenerator for this purpose semantically could look a bit weird when all users want is to send some static data - it gives a bit of a wrong impression that this data is expected to be the basis for some generated dataset, maybe just looped over or something like this
The fact that we use the DataGenerator for under the hood could be seen as an implementation detail. Should the modules layout change in 2.0, we'll be free to change the underlying implementation if needed.

I am in favor of exposing the fromData method and deprecating fromElements and fromCollection. What do you think?

@zentol CI is green again after the discussed API changes.


extension pauses videos

Love the extension for clearing the clutter but it also keeps pausing videos I want to watch. I like that it removed auto play, but if a scroll even a little the extension pauses the video, sometimes it just pauses it at random even when I am not touching anything. It is extremely annoying. Is there a fix for this?

Finally caught this bug!
https://github.com/thomaswang/minimal-twitter/releases/tag/2.70
Update to 2.70 @gearan


Would love to join and contribute

Hi there,
I am an undergraduate at PICT, Pune. A quality and output-driven computer enthusiast. Passionate about exploring computer science and technology-related topics. My domains & fields of interest are machine learning, data science, Computer Vision, Python, Java, C++, R, MATLAB, open-source. I aspire to work and contribute to these fields for betterment society through research and innovations for improvisation in the field of computer science and technology.
I have a keen interest in the research, especially in the domains of machine learning, AI, and data science. I have been a research fellow at The Emerging Tech Foundation. I have been a python mentor at Skillship foundation, a mentor at facebook's developer's circle. I have a keen interest in writing technical blogs and articles, worked at Geeksforgeeks.org as a technical content writer. Also currently I am an editor at PICT IEEE NewsletterGroup, which is a technical biannual magazine of my college. Also, I write technical blogs on medium.
I am even passionate about web-development. I have developed the official website of CTD 2020 (a technical event of PISB), also completed a couple of internships in this domain with Wikasta Technical Solutions and another with Kode IT Solutions. I am Technical Lead Developer at GirlScript Foundation Pune, here I manage all the tech issues and development of its official website.
I am a semifinalist of the national python codathon conducted by cisco and ISTE. I have been accepted as a Udacity scholar for the Microsoft Azure Machine Learning scholarship program. I am also an enthusiastic open source contributor, I am a Github's Arctic Code Vault Contributor.
Keen about exploring opportunities in the field of research and development in computer science-related technologies, also open for collaborations!
Please add me to this organization, My Github ID is rutujak24.
Thank you!

Sorry, we’re not accepting membership applications. Feel free to contribute by submitting meaningful pull requests. Thank you.


Missing access token uploading metrics

This is currently breaking the build.
Looks like there's an infra problem uploading metrics
AuthenticatedClientError:
  URI: https://flutter-dashboard.appspot.com/api/update-task-status
  HTTP Status: 401
  Response body:
Invalid access token

This is a transient issue, and the bot (win2) is passing ongoing tests well:

Now the tree is back to tree.

Haven't seen this in a few months


[request] Using a Shard feature on Discord.Net

is there any bot sample which uses shard feature on Discord.Net ?
i couldn't find example usage in documentation

I recommend updating issue title to something along the lines of...
[Request] Documentation example for using Shard feature.

https://github.com/PassiveModding/RavenBOT
It's pretty simple, mostly just changing all instances of discordsocketclient with discordshardedclient


Remove duplicate learning outcomes (fixes #827)

Due to joining three tables together across many to many relationships, learning outcomes were being duplicated on lesson page.
Can't believe we didn't spot this sooner, especially how we complained the learning outcome lists were so long!
Fixes #827

This is possibly my favourite face-palm bug so far.


Convert literal to string Error

Description

making the modifications so that the wifi module would take the data from the nvs, I was having problems when I set a data in the nvs it replaced the others.
Steps to reproduce the issue
For reproduce this issue you can  do simple printf to result optained of nvs_key_to_name for example:
Expected results

the code that was failing is this:

#define literal_to_str(literal) #literal                /*!< Transform literal to string */
#define nvs_key_to_name(...) literal_to_str(__VA_ARGS_) /*!< A nonsense for the nvs component */
#define at_cmd_to_name(...) literal_to_str(__VA_ARGS__) /*!< Another one for the uart(at) component*

please can you paste the error?

Thanks a lot for the report!
@xkevin190 Fixed into #128 , please try again compiling the related test


mutate-drawable: Sublayer#getDrawable now mutates the Drawable before…

… returning. Added somewhat fragile unit test around this. EO

That was my original thought, calling mutate() at the last responsible moment. But then I saw that Sublayer was where getDrawable() was ultimately called. Does this mean that if I create(since the class is public) a Sublayer my drawables will not be mutated? Wouldn't this bypass the builder?

Sublayer has default (package) class visibility, it shouldn't be used out of the library. The only way to create new sublayers should be through the builder. If there is other (reasonable) way to create them then it's a bug.
My main concern with putting the logic in the getter is that it will be called tons of times while drawing and it may cause tons of new object allocations (depending on the specific type of drawable) in the main thread (copies that are not really needed).

Yeah, you are correct. I will take a look tonight to write a test for the builder.

Do you think DividerBuilder#with is the right place to call mutate()?

That or the Sublayer constructor, I don't have a strong opinion.

Thanks for the contribution!

@Serchinastico can we release a new version with this fix?

Yup, I'm doing it in a few hours :)

Thanks!

No problem! Glad to help. Also thanks @pedrovgs for your awesome Design Patterns material!

You are welcome @emmano!


[Peek] Update FilePreviewer to prevent tooltips from obscuring title bar controls

Summary of the Pull Request
Update to prevent ImagePreview and VideoPreview controls' tooltips from obscuring the Main Window's title bar.

PR Checklist

[x] Closes: #34496
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments
When the user hovers over the top-right portion of an ImagePreview or VideoPreview, the associated tooltip is opened, with the text bound to InfoToolTip. This worked, but unfortunately the tooltip could obscure the Windows controls such as the close icon, which was an accessibility problem. This PR dynamically sets the Placement of the tooltip so it opens below the mouse pointer in the top portion of the previewers. The PointerMoved handler is generic, so will work with any future previewer which needs a tooltip.
The tooltips are proper child elements of the previewer controls now, as they need to be instantiated.
I updated the StringBuilder which appends the tooltip contents to have an initial capacity of 256 characters. This prevents the builder from resizing itself multiple times. This is a tiny perf/allocation improvement.

Validation Steps Performed
Manual tests only:

Tested with a mix of image and movie files.
Tested starting with a different previewer which doesn't use tooltips then navigating to an image or movie file which does need a tooltip.
Tested starting with an image or movie file then navigating to a different file type then opening another image or movie file.

/azp run

Thanks for the merge, @jaimecbernardo and sorry you had to fix up the XAML. Is the rule for props that they should be in alphabetical order?

@daverayment , there's some forced rules by CI to make sure we don't get many merge issues due to concurrent XAML changes.
You can run .\.pipelines\applyXamlStyling.ps1 -Main in Powershell locally and it'll fix your XAML files as well :)
Anyway, when I see that CI is complaining on a PR I just do that myself and push ;)


Setting cursor style in notebook cells via API (required by vscode-neovim)

Does this issue occur when all extensions are disabled?: Related to Extension API

Version:
Version: 1.74.2
Commit: e8a3071ea4344d9d48ef8a4df2c097372b0c5161
Date: 2022-12-20T10:32:21.587Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.1.0
Sandboxed: No

I'm working on an issue in vscode-neovim related to the cursor style in notebook cells. I may have encountered a bug or limitation in the Extensions API. In a nutshell, the issue seems to be that setting cursor options of TextEditors associated to notebook editors does not have any effect. Therefore vscode-neovim is unable to set the cursor style to block when showing notebook cells.
Steps to Reproduce:

Create a new notebook and add a cell
Create another regular document
Switch to notebook cell
Set editor.options.cursorStyle = TextEditorCursorStyle.Block; via the Extension API.

Expected Result:
Cursor style is block
Actual Result:
Cursor style is unchanged (default).

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Contacts data in the app

Updating data model for storing contacts data in app
Reviewing and modifying the contacts data creation and update mechanism
Considering different contact user journeys and data needs during the journey

-Closing this issue as discussed with dev.


DBZ-478 Fix null array handling for wal2json

https://issues.jboss.org/browse/DBZ-478

Rebased and applied. Thanks, @jpechane!


Add Mode Select Cluster

*Problem
Implementation for Mode Select Cluster is missing.
Speicification for the Mode Select Cluster can be found at
https://github.com/CHIP-Specifications/connectedhomeip-spec/blob/master/src/app_clusters/ModeSelect.adoc
*Change overview
Add the the implementation for the mode select cluster's server.
Add SupportedOptionsManager to help initializing the supported options
and retriving the options.
Changes the all-cluster-all and chip-tool's zap files to include the
mode select cluster.
Problem
Add the implementation for Mode Select Cluster. The specification for
Mode Select Cluster can be found at https://github.com/CHIP-Specifications/connectedhomeip-spec/blob/master/src/app_clusters/ModeSelect.adoc
Change overview
* Add src/app/zap-templates/zcl/data-model/chip/mode-select-cluster.xml
* Add the ModeSelectCluster to the all-cluster-app
* Add the ModeSelectCluster to the chip-tool
* Add src/app/clusters/mode-select-server/mode-select-server.cpp, the
main logic for the server of the ModeSelectCluster
* Add src/app/clusters/mode-select-server/supported-modes-manager.h,
which contains helper method for managing the supported options.
* Generate code for Mode Select Cluster

Testing
How was this tested? (at least one bullet point required)

If manually tested, what platforms controller and device platforms were manually tested, and how?
Manually tested with chip-tool built on MacOs. Tested by issuing the read command and the "change-to-mode" command, and verified that all the attributes can be read, and "change-to-mode" correctly changes the "current-mode" attribute.
./scripts/test/test_suites.sh passed on a iOS machine.

/rebase

/rebase


Mistake in writing

The title BPCheckAltenateKeyAbsent is incorrect. It should be BPCheckAlternateKeyAbsent.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2cbcd513-d8ab-ddc6-ce0d-43e03d4692c2
Version Independent ID: d1119159-09e4-1aa1-d90e-c8f23552adbc
Content: Customization Analysis Report (CAR) - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/dev-tools/customization-analysis-report.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @RobinARH
Microsoft Alias: jorisde

@sebastianstrefel, thanks for letting us know!
@RobinARH, please review and update the text.

Bug 434682 has been logged to track this issue.

Fixed.


Update lessons to use 'super dirty' gapminder dataset

Can download here: https://github.com/Reproducible-Science-Curriculum/data-exploration-RR-Jupyter/blob/master/gapminderDataFiveYear_superDirty.txt

I've added the dataset to this repo in /data. Is there a checklist on what's needed to update the lessons? Is it just changing file names or something deeper?


[main] Upgrade to latest dependencies

GKE fixes in hack -dprotaso
/cc knative-extensions/serving-writers
/assign knative-extensions/serving-writers
Produced by: knative-extensions/knobots/actions/update-deps

/lgtm
/approve


Spit out maximum number of bead ROIs for shifting to make it pass

Processing fails when there are too few beads for drift correction. Spit out maximum config value to make it pass.

Closing in favor of #173


Google docs editor iframe

Hi!
I was reading the documentation related to third-party cookie deprecation, and if I understood, the only solution for Google Docs iframe is the published version. However, it's possible to embed the editor until the third-party cookie deprecation. CHIPS approach would need to be necessary on Google's side, so it isn't currently a solution.
After the phasing out, is there a way to embed Google Docs editor?
Thanks in advance

Hello! The Google Docs editor can already be embedded in browsers that don't support 3p cookies. Feel free to test it out in Firefox and Safari. The user will be shown a button to grant storage access to the iframe. The same solution is rolling out in Chrome ahead of 3p cookie deprecation.

Hi Ighall 👋
I was testing and sometime it shows a UI to require permissions from the user, but it only shows up once in a while. It's something under development? Is there any documentation to check how to embed correctly? From what I read, we should embed the publish version, but we want the editor.
Most of the time, I'm getting this UI from iframe:

Yes, the rollout for Chrome will be completed by the end of 2023.

Great point! I've added this issue to our internal tracking and I'll report back here if/when we're able to address it.
As an interim solution, you could ask users of your application to allowlist 3p cookies for the necessary  pair in their browser if they encounter this particular issue.

Thanks!
I understand it's a slightly tricky one, as you may not wish to request the permission for all embedded documents that have "anyone with the link can view" as soon as they are loaded. However, some sort of long-term solution would be great, because the current behaviour is puzzling to users: if you click on the sign in button in the iframe, the browser redirects the entire page to the Google document (where the user is already signed in). So the permission request never appears.
I haven't thought about this very thoroughly, but one possible flow for documents with "anyone with the link can view" would be:

when user clicks "sign in" within the iframe, request Storage Access permissions

if permission is refused, do the current behavior (redirect the entire page to the Google sign-in)
if permission is granted, check if the user is already signed in.

if yes, update the iframe contents as appropriate
otherwise, do the current behavior

Closing as there hasn't been any additional discussion on this thread in more than 6 weeks. Please re-open if there are any more questions or developments.

Hello! Circling back that we have now addressed the issue reported by tadamcz@ - If the user can View but not Edit the document without logging in, clicking "Sign in" will prompt for storage access and allow them to authenticate and edit the document if they have access. Thank you for the report!


SIDE-2096: RG - adding version to a webpack banner

TIL that npm inserts package versions into env vars... do we know if it inserts the actual version, or the sem ver specified?

This pull request is obsolete  due to changed versioning directions.


Second Edition: an extra example requested (page 96)

On page 96 you show a debug task - displaying the variable ansible_eth0
Later you show how to access an attribute of this variable:

{{ ansible_eth0.ipv4.address }}
{{ ansible_eth0['ipv4']['address'] }}

I have a similar variable - with an element like:
{{ ansible_eth0.ipv6 }}

However, I have not figured out how to access ipv6 address of "fe80::..."

In the debug information ipv4 is { "address": "value", "netmask": "value", ... }
but ipv6 first element is `[ { "address": "value", ... } ], "macaddress": "value", ...

I keep struggling over the additional [ ...] bracketing - and would really appreciate a concise explanation of this syntax.
Update: I want to make much more use of ansible_facts and use readily available information such as:
        "en0": {
            "device": "en0",
            "flags": [
                "UP",
                "BROADCAST",
                "NOTRAILERS",
                "RUNNING",
                "SIMPLEX",
                "MULTICAST",
                "GROUPRT",
                "64BIT",
                "CHECKSUM_OFFLOAD(ACTIVE)",
                "LARGESEND",
                "CHAIN"
            ],
            "ipv4": [
                {
                    "address": "<IP_ADDRESS>",
                    "broadcast": "<IP_ADDRESS>",
                    "netmask": "<IP_ADDRESS>",
                    "network": "<IP_ADDRESS>"
                },
                {
                    "address": "<IP_ADDRESS>",
                    "broadcast": "<IP_ADDRESS>",
                    "netmask": "<IP_ADDRESS>",
                    "network": "<IP_ADDRESS>"
                },
                {
                    "address": "<IP_ADDRESS>",
                    "broadcast": "<IP_ADDRESS>",
                    "netmask": "<IP_ADDRESS>",
                    "network": "<IP_ADDRESS>"
                }
            ],
            "ipv6": [
                {
                    "address": "fe80::fff1:feff:fea3:c744",
                    "prefix": "64"
                }
            ],

I'd rather not have to take a course on Python programming to understand how to quickly work through dict(s) containing lists of dicts (containing dicts containing lists of dicts - or is it lists containing dicts of lists, etc..

The additional [...] bracketing is because there are multiple IP addresses for the IPv6 section, but only a single IPv4 address is assigned to your NIC.
To refrence it, you need to tell Ansible which element to use like this:
  - name: "Show ipv6 address info for element 0"
    debug:
      var: ansible_ens33.ipv6.0.address

For my system, I have "ens33" for my NIC so the information is here:
    "ansible_ens33": {
        "active": true,
        "device": "ens33",
        "features": {
            "busy_poll": "off [fixed]",
            "fcoe_mtu": "off [fixed]"
        "ipv4": {
            "address": "<IP_ADDRESS>",
            "broadcast": "<IP_ADDRESS>",
            "netmask": "<IP_ADDRESS>",
            "network": "<IP_ADDRESS>"
        },
        "ipv6": [
            {
                "address": "::<IP_ADDRESS>",
                "prefix": "64",
                "scope": "global"
            },
            {
                "address": "fe80::9163:306b:459b:49ce",
                "prefix": "64",
                "scope": "link"
            }
        ],
    },

(Note, many lines omitted for brevity.)
When I run these tasks:
  tasks:
  - name: "Show ipv4 info"
    debug:
      var: ansible_ens33.ipv4

  - name: "Show ipv6 info"
    debug:
      var: ansible_ens33.ipv6

  - name: "Show ipv4 address info"
    debug:
      var: ansible_ens33.ipv4.address

  - name: "Show ipv6 address info for element 0"
    debug:
      var: ansible_ens33.ipv6.0.address

I get this output:
TASK [Show ipv4 info] **********************************************************
ok: [ansvm1] => {
    "ansible_ens33.ipv4": {
        "address": "<IP_ADDRESS>",
        "broadcast": "<IP_ADDRESS>",
        "netmask": "<IP_ADDRESS>",
        "network": "<IP_ADDRESS>"
    }
}

TASK [Show ipv6 info] **********************************************************
ok: [ansvm1] => {
    "ansible_ens33.ipv6": [
        {
            "address": "::<IP_ADDRESS>",
            "prefix": "64",
            "scope": "global"
        },
        {
            "address": "fe80::9163:306b:459b:49ce",
            "prefix": "64",
            "scope": "link"
        }
    ]
}

TASK [Show ipv4 address info] **************************************************
ok: [ansvm1] => {
    "ansible_ens33.ipv4.address": "<IP_ADDRESS>"
}

TASK [Show ipv6 address info for element 0] ************************************
ok: [ansvm1] => {
    "ansible_ens33.ipv6.0.address": "::<IP_ADDRESS>"
}

I have a gripe with Ansible in that the IP information is in a dictionary in one and a dictionary in a list for another.  I wish there was some consistency even if it meant that my ipv4 section only had a single element and I had to use the ipv4.0.address notation all the time.  If I want to treat systems that have multiple IP addresses the same as those with a single IP address (per NIC), I have to take special care to pull out the proper information.  (But then, the "IACC" side of me says "You shouldn't be querying the system - you should have a record of what that system has/needs and set it accordingly."  My struggle betwee and declarative styles.)

Agreed with @dglinder that this can be annoying (and I often end up with long chains of accesses with hardcoded list ID numbers in them... which I don't particularly enjoy). But since this is more of an Ansible support question and slightly less related to the contents of the book, I'd recommend posting any more follow-ups into the Ansible subreddit, the Ansible Project mailing list, or one of Ansible's Matrix/IRC channels.

I just thought, as it is a common syntax switch: AND for someone new, easy to overlook (the added '[')
{ "itembit": "value" , ... "itembit_n": "value }
compared with:
[ { "itembit": "value" , ... "itembit_n": "value } ]
And since you explain one syntax I thought it might be just as enlightening to at least mention this.
And, yes, I had figured out the numeric (.X.) syntax, but the unsatisfactory bit with that is that I cannot be certain the numeric entry I want is .0. or .N..
In closing, I had kept the syntax example to IP addresses - but the issue I was struggling with had to do with storage and seeing how many free blocks were in a volume group - that is quite dynamic.
But an argument for scanning IP addresses is to confirm that the settings are as they should be, nothing additional, etc..
Again, it is your choice to ignore the difference. But I see it as a missed opportunity - or as confusion - why bother with the one, if ignoring the other.
FYI: I had not had a reason to look at the book in over a year. I recalled you did some examples and had had hopes. Now it seems, ripe for oblivion.

Agreed with @dglinder that this can be annoying (and I often end up with long chains of accesses with hardcoded list ID numbers in them... which I don't particularly enjoy). But since this is more of an Ansible support question and slightly less related to the contents of the book, I'd recommend posting any more follow-ups into the Ansible subreddit, the Ansible Project mailing list, or one of Ansible's Matrix/IRC channels.

p.s. - adding this advice as a footnote - where to go if struggling with short introduction - is also a good addition.
p.p.s. or a hyperlink, crossref, whatever you want to call it - to appropriate material in your best-practices appendix.
In particular, the hyperlink makes you book more usable - imho.

feedback: of the three "goto" locations mentioned above - only the ansible project is mentioned - as a footnote in the introduction - before any content even gets mentioned.

personal preference: I actually went to ansible project, but regretted it as it still sends me email - even though I have unsubscribed several times. reddit (which is not mentioned at all in your book) is much better in not sending unsolicited comments, same for IRC - only when you are there.

Your book was useful, but I see I am on my own now.

Best wishes for your next edition.

@aixtools - I may consider expanding more on the basics of extracting variables from ansible_facts and the like, but please don't take the closure of this issue personally, it's just that the topic of debugging + grabbing values from various places in Ansible's fact-gathering mess already takes me way more time than it should too...


Issue when accessing client

I'm getting this error:
Message: {"Type":"OAuthException","Message":"You must provide a client_id"}
when attempting to retrieve my access token. Looking at a var_dump of the library, the clientID and clientSecret are set
here is the full error
Type: Haridarshan\Instagram\Exceptions\InstagramOAuthException

Message: {"Type":"OAuthException","Message":"You must provide a client_id"}

Filename: /var/www/alpha/vendor/haridarshan/instagram-php/src/HelperFactory.php

Line Number: 119

Hi albertleao, thank you for using this library.
I've checked the code and I didn't found any issue like this. Can you please share the code how you're using it.
If you're getting this exception when trying to call this, then client_id in options parameters of oauth method is not set. So, you're getting this exception
<?php
try {
  $oauth = $instagram->oauth($_GET['code']);
  // To get User's Access Token
  $insta_access_token = $oauth->getAccessToken();
  // To get User's Info Token
  $user_info = $oauth->getUserInfo();
} catch (InstagramOAuthException $e) {
  echo $e->getMessage();
}

This is fixed. The issue was cause by guzzle update


Remove old Assert namespaces

It seems you forgot to remove some namespaces during the commit https://github.com/webmozart/key-value-store/commit/877f9ab17716869f31cd800dc9d9cf157e836885.
This PR just remove them as they are not valid anymore.

Thanks!


Cann't get local json file for Lottie on Windows

Description
Cann't get local file from assets folder on WIndows.

Code example to reproduce the issue:
import flet as ft

def main(page: ft.Page):
    lottie = ft.Lottie("a.json")
    image = ft.Image("a.jpg")

    page.add(lottie, image)
    page.update()

ft.app(main)

Describe the results you received:

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):
Flet version (pip show flet):
(paste your output here)

Give your requirements.txt file (don't pip freeze, instead give direct packages):
(The requirements)

Operating system:

Additional environment details:

Closing as duplicate of https://github.com/flet-dev/flet/issues/3082
Please read the comments in that issue.

Works on Ubuntu.
But not work on Windows.


Adding Poland.html

@napoleon101392 Hey! :smile:
We have already received many Pull request for this. And one of them has been merged. Great work btw. Keep contributing! :smile:


maputil: preallocate len and cap for keys and values slice

Length of keys and values is know in advance, use this knowledge to preallocate memory.
Space usage increases by const factor

@duke-git please review

Codecov Report

Merging #41 (d958d57) into main (44370ae) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #41      +/-   ##
==========================================
+ Coverage   83.65%   83.67%   +0.01%
==========================================
  Files          46       46
  Lines        3560     3564       +4
==========================================
+ Hits         2978     2982       +4
  Misses        390      390
  Partials      192      192

Impacted Files
Coverage Δ

maputil/map.go
96.29% <100.00%> (+0.29%)
:arrow_up:

Continue to review full report at Codecov.

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

@duke-git please review

@donutloop, happy to receive your PR again! Will merge it.


Parse.Cloud.httpRequest: provide default string encoding for body option

Somewhat related to #703.
The 'request' library in node requires the body option to be a string, whereas Parse.Cloud.httpRequest will pass in an object if it is given an object, with no Content-Type header.
This is running on parse-server v2.1.3.
example node repl session illustrating the issue:
> require('parse-server');
{ ParseServer: [Function: ParseServer],
  S3Adapter: [Function: S3Adapter] }
> Parse.Cloud.httpRequest({method: 'POST', url: 'http://httpbin.org/post', body: {p1: 'v1', p2: 2}})
TypeError: Cannot read property 'statusCode' of undefined
    at Request._callback (dist/node_modules/parse-server/lib/httpRequest.js:46:35)
    at self.callback (dist/node_modules/parse-server/node_modules/request/request.js:199:22)
    at emitOne (events.js:77:13)
    at Request.emit (events.js:169:7)
    at setContentLength (dist/node_modules/parse-server/node_modules/request/request.js:451:14)
    at Request.init (dist/node_modules/parse-server/node_modules/request/request.js:456:5)
    at new Request (dist/node_modules/parse-server/node_modules/request/request.js:141:8)
    at request (dist/node_modules/parse-server/node_modules/request/index.js:55:10)
    at Object.module.exports [as httpRequest] (dist/node_modules/parse-server/lib/httpRequest.js:44:3)
    at repl:1:13
> Parse.Cloud.httpRequest({method: 'POST', url: 'http://httpbin.org/post', body: {p1: 'v1', p2: 2}, headers: {'content-type': 'application/x-www-form-urlencoded'}})
ParsePromise {
  _resolved: false,
  _rejected: false,
  _resolvedCallbacks: [],
  _rejectedCallbacks: [] }
>

Originally the Parse.Cloud.httpRequest requires you to set the contentType manually so the body is properly encoded, either in JSON or in application/x-www-form-urlencoded
We could add the json option instead that would automatically set the contentType for your request.
Would that help?

Oh, I didn't realize that was the default behavior. I encountered this issue while trying to use the code here: https://github.com/ParsePlatform/JavaScriptModulesTutorial/blob/master/myMailModule-1.0.0.js
I assumed that this was how Mailgun on Parse is implemented, but I guess that is not the case.
I think parse-server should match hosted Parse as closely as possible, so I'm going to close this issue.

then it's maybe not the default behaviour! how is it working on parse.com?

I'm having a similar problem with this:
OpenTokSDK.prototype.apiRequest = function(endpoint, authScheme, options, cb) {
// options is optional
if (cb === undefined) { cb = options; options = {}; }
var requestOptions = {
url: urlFromEndpoint(endpoint, options.endpoint),
method: methodFromEndpoint(endpoint),
headers: {},
body: options.data || {},
success: function(response) {
cb(null, response);
},
error: function(response) {
cb(new Error("Request failed with response code " + response.status + "\n" +
"Raw response: \n" + response.text + "\n"));
}
};
if (authScheme === AUTH.PARTNER) {
requestOptions.headers[authScheme] = this.apiKey + ':' + this.apiSecret;
} else if (authScheme === AUTH.TOKEN) {
requestOptions.headers[authScheme] = this.generateToken.apply( this, options.auth );
} else {
console.warn("OpenTok: No known authentication scheme chosen for the following request: \n" +
JSON.stringify(requestOptions) + "\n");
}
Parse.Cloud.httpRequest(requestOptions);
console.log("OpenTok: Sent the following request: \n" + JSON.stringify(requestOptions) + "\n");
return;
};
at the Parse.Cloud.httpRequest(requestOptions) line it reads:
Uncaught internal server error. [TypeError: Cannot read property 'statusCode' of undefined] TypeError: Cannot read property 'statusCode' of undefined
2016-03-03T01:47:51.698829+00:00 app[web.1]:     at Request._callback (/app/node_modules/parse-server/lib/httpRequest.js:46:35)
2016-03-03T01:47:51.698830+00:00 app[web.1]:     at self.callback (/app/node_modules/request/request.js:199:22)
2016-03-03T01:47:51.698831+00:00 app[web.1]:     at emitOne (events.js:90:13)
2016-03-03T01:47:51.698832+00:00 app[web.1]:     at Request.emit (events.js:182:7)
2016-03-03T01:47:51.698832+00:00 app[web.1]:     at setContentLength (/app/node_modules/request/request.js:451:14)
2016-03-03T01:47:51.698833+00:00 app[web.1]:     at Request.init (/app/node_modules/request/request.js:456:5)
2016-03-03T01:47:51.698834+00:00 app[web.1]:     at new Request (/app/node_modules/request/request.js:141:8)
2016-03-03T01:47:51.698835+00:00 app[web.1]:     at request (/app/node_modules/request/index.js:55:10)
2016-03-03T01:47:51.698836+00:00 app[web.1]:     at Object.module.exports [as httpRequest] (/app/node_modules/parse-server/lib/httpRequest.js:44:3)
2016-03-03T01:47:51.698836+00:00 app[web.1]:     at OpenTokSDK.apiRequest (/app/cloud/opentok/opentok.js:196:15)

@yuzeh how did you solve it? I still cannot get the  https://github.com/ParsePlatform/JavaScriptModulesTutorial/blob/master/myMailModule-1.0.0.js
to work despite trying various options like setting the header and even turning the object into a string
if (typeof params === 'object') {
params = JSON.stringify(params);
console.log("after stringify of params: " + params);
}
return Parse.Cloud.httpRequest({
method: "POST",
url: "https://api:" + key + "@" + url + "/" + domain + "/messages",
headers: {
'Content-Type': 'application/x-www-form-urlencoded'
},
body: params
  }).then(function(httpResponse) {
          //success

As a follow up, changing the Content-Type to multipart/form-data gives a different response from mailgun. Instead of 400, it now returns http status code of 502

I was using an API called OpenTok, and I basically got rid of it and made sure I was using the newest version of the SDK for it, and the newest build for Parse-Server.
The code I had been using, was from a sample project that implemented the OpenTok API via parse server. By using npm install of the OpenTok framework from scratch, it seemed to be able to run it from scratch.
Good luck.

On Mar 4, 2016, at 4:12 AM, videre<EMAIL_ADDRESS>wrote:
@yuzeh https://github.com/yuzeh how did you solve it? I still cannot get the https://github.com/ParsePlatform/JavaScriptModulesTutorial/blob/master/myMailModule-1.0.0.js https://github.com/ParsePlatform/JavaScriptModulesTutorial/blob/master/myMailModule-1.0.0.js
to work despite trying various options like setting the header and even turning the object into a string
if (typeof params === 'object') {
params = JSON.stringify(params);
console.log("after stringify of params: " + params);
}
return Parse.Cloud.httpRequest({
method: "POST",
url: "https://api:" + key + "@" + url + "/" + domain + "/messages",
headers: {
'Content-Type': 'application/x-www-form-urlencoded'
},
body: params
}).then(function(httpResponse) {
//success
—
Reply to this email directly or view it on GitHub https://github.com/ParsePlatform/parse-server/issues/727#issuecomment-192196426.


This adds environments to the backup.

Thank you for taking the time to contribute this pull request. I'm not using this script anymore. I recommend Steven Danna's knife plugins for export and restore.

https://github.com/stevendanna/knife-hacks/tree/master/plugins


feat: add Yarn workspaces support

Close #93
EDIT: hum weird, no GitHub checks are ran here.... but you can see:

a failing build here before any modifications: https://github.com/Kocal/github-action/actions/runs/41631467
successful builds after modifications: https://github.com/Kocal/github-action/actions/runs/41658837

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Updated README in https://github.com/cypress-io/github-action/pull/95

@Kocal Thanks for updating this. I see that cypress was included in both workspaces as opposed to the root and then used from there. Why is that? Is there a limitation to a single cypress package usage from the root?

Hi, it's a personal preference but I think it can works if you install Cypress in your root package.json.


Root Collection permission can also be done via Portal

According to document below, only way to add a Root Collection Admin is via a HTTP Post.
This is now available via the Azure Portakl under the option 'Root Collection  permission' menu on the left within your Microsoft Purview Account
Thanks

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 57f16907-e643-4a6d-3788-bf168072fb7c
Version Independent ID: b55bc925-8ec7-5471-f2bf-823b7aab8a90
Content: Learn about Microsoft Purview collections metadata policy and roles APIs - Microsoft Purview
Content Source: articles/purview/tutorial-metadata-policy-collections-apis.md
Service: purview
Sub-service: purview-data-catalog
GitHub Login: @abandyop
Microsoft Alias: arindamba

@ShaneOsborne Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

@ShaneOsborne - Thanks for the feedback! I'll work on updating these documents to make the UI option clearer as well.
I'll reply here once those additions are made! Likely by tomorrow. Thank you!

@ShaneOsborne - I have corrected the original article so that it's clearer that it's referencing just the REST API options, and I have added the portal options to the permissions page as well: https://docs.microsoft.com/en-us/azure/purview/catalog-permissions
You should see these edits appear this afternoon. Thanks again for your feedback!

#please-close


How to use this extension?

export type abc = 'asdf'
// ^?

interface Box<T> {
  value: T
}
// ^?
function makeBox<T>(value: T) {
  return {value}
}
// ^?

I installed and couldn't get it to work. This is what my test file looks like. What am I missing?

the x position of the ^? is important, it needs to be exactly the line underneath the thing you want it to look at

export type abc = 'asdf'
// ^?

interface Box<T> {
  value: T
}
// ^?
function makeBox<T>(value: T) {
  return {value}
}
// ^?

I installed and couldn't get it to work. This is what my test file looks like. What am I missing?

Try add 2 indents(4 spaces) before ^
type abc = 'asdf';
//    ^?

@orta export type and interface are not working

Give some code examples of what you think is wrong


Create AOSIS dependent styles

closes https://github.com/citation-style-language/journals/issues/33
Attached the .xlsx in case you need to change anything: aosis-journals.xlsx

Should have everything now, @rmzelle .
Hope I did it all correctly! :)

Onderstepoort Journal of Veterinary Research exists on repository already.

Hope I did it all correctly! :)

A few small errors in the template, but otherwise it all looked good. Thanks!

@POBrien333, thanks!

Awesome. Thank you.
Am I seeing this correctly that you set all styles as author-date, although some are numeric?

Oops, I thought our tests would have caught that. Could you file a new PR to add a FORMAT field to the AOSIS journal metadata?

And we had already rolled over to 10000+ styles a few days ago (https://twitter.com/librarianjason/status/1371547108889792518?s=21). Thanks for your help getting CSL there!

Oops, I thought our tests would have caught that.

Actually, turns out that the Vancouver parent was labelled as "author-date" instead of "numeric". Should be all good now.

Ahhh. Thanks for fixing that.