Any chance to rename the application?

Hi,
Any chance to rename the application to avoid the clash with https://github.com/kivra/oauth2? I want to use both apps!
Thanks :)

Would :o_auth2 suffice?

That works, too
On Tuesday, January 20, 2015, Sonny Scroggin<EMAIL_ADDRESS>wrote:

Would :o_auth2 suffice?
—
Reply to this email directly or view it on GitHub
https://github.com/scrogson/oauth2/issues/4#issuecomment-70534977.

--
Y.
My company is hiring: https://trustatom.com/jobs

Hey @yrashk I've decided against renaming as it's already been on hex for many months now. Let me know what features kivra/oauth2 provides that are missing here and I'll see if I can work it in.
I've changed the API a bit since this issue was first created and I plan on making more improvements.

@scrogson is this final?


OD API Auth Change?

On the browser extension "Reddit Enhancement Suite" we had the option that allows users to embed onedrive content and show it inline. Over the past few weeks it appears our API requests are starting to fail with "Must be authenticated to use '/drive'".
Has there been a recent change that means all API requests must to be authenticated via oauth? These requests have worked in the past.
Ref https://github.com/honestbleeps/Reddit-Enhancement-Suite/issues/4180

Hey @BenMcGarry:
Instead of decomposing the URL, I'd recommend you use the Shares API to access shared items. This way you'll be resilient to URL changes and shouldn't encounter these authentication errors.

Many thanks @rgregg, that appears to have done the trick :)


it is not working

whenever i click on stairs nothing i downloaded the mod menu mod and it didn't show the mod i was playing 1.19.3

If Mod Menu does not show you the mod, then you did not install the mod correctly. Make sure that you are using the fabric version of Sit.


[lzokay] update to the latest for newer compilers

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[ ] The "supports" clause reflects platforms that may be fixed by this new version.
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

It's my first time to make a PR to vcpkg. If you find any mistakes, please let me know!

@microsoft-github-policy-service agree company="YOSHIMOTO ART FACTORY LLC"


Bumping versions to 1.0.0, 0.17.1-beta, 0.17.1-alpha for release

Changes Unknown when pulling 9c3f08f0718ecd9f0c78ae8df4d8eb8d0124dc07 on garrettjonesgoogle:master into ** on GoogleCloudPlatform:master**.


[d3d9] Fix for missing restriction check in UpdateSurface.

The spec of IDirect3DDevice9::UpdateSurface contains the following restriction:

Neither surface can be created with multisampling.
The only valid flag for both surfaces is D3DMULTISAMPLE_NONE.

This commit adds this check and returns D3DERR_INVALIDCALL
when source or destination surfaces are multisampled.

This code change fixes Colorfill WHQL test.

Thanks! Looks good.


Handle display names with trailing spaces

Closes #6217.
The reason why we do to_s.rstrip is to handle the (potentially weird case of) display_name being nil, in which case we will otherwise get an unfriendly Ruby error message.
Check List

[ ] New functionality includes tests (negative: if this is a requirement, please tell me where to add them)
[x] All tests pass
[ ] ~RELEASE_NOTES.md, has been updated if required (not required for bugfixes, required for API changes)~ Should not be required in this case
[ ] ~All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco~ (should not be needed for the trivial change, let me know if you want me to amend to include this)

Submitter has said this is an obvious fix, no DCO required.

Added MSYS-631 to add a test.


Job 2 - Homepage

Added

functionality to add tasks to home page in table view
Edited
base controller to use layout content if provided

closes #2

Did not do changelog

Did changelog


geoprocessing fails for the OSM File Loader (Load Only) tool.

@ThomasEmge
I don't know if this again some computer specific issue, but after installing ArcGIS for Desktop 10.6 + 64 bit background geoprocessing, and subsequently the install of the OSM Editor for 64 bit, background geoprocessing fails for the OSM File Loader (Load Only) tool.
I see the process starting up, but almost immediately finishing with the green mark of "success", but nothing is actually loaded into the target geodatabase.
If I disable background geoprocessing, the tool works as expected, and does create the Feature Classes with all the data. It just fails with background geoprocessing.
I fully uninstalled and reinstalled the 64 bit background geoprocessing component, and the OSM Editor as well, making sure I reinstalled the OSM Editor after installing the 64 bit background geoprocessing component, however all to no avail.
I did notice one other small anomaly, that the HTML Help page being opened after the OSM Editor install, still listed ArcGIS 10.5 instead of 10.6. However, I guess this is just an oversight to update the HTML page for the new 10.6 install...

@amalask
The content in the HTML page is an oversight and I'll put in a request with the install team.
If possible, could you please post the geoprocessing messages from the 'successful' run. I just tried with the official installer and so far it looks ok on our office machines.

@ThomasEmge ,
@amalask literally copy&pasted my entire message from this other thread (#187) I started, only changing title.
Apparently, @amalask has the same issue...
Anyway, as to the "successfull" run, there isn't one for 64 bit background geoprocessing, the successfull run was with foreground geoprocessing. The failure is with 64 bit background geoprocessing enabled. As I wrote, I correctly installed the 64 bit background processing, and the 64 bit Editor for background processing. Uninstalling and re-installing did not help.
I have now also verified that some other NON-OSM EDITOR (!) tools do run successfully with 64 bit background geoprocessing on my machine, so it does seem an issue isolated to the OSM File Loader (Load Only) tool. The Load OSM File tool by the way, shows the same behavior, and also fails, so it may affect all the tools of the Editor.
Just to exclude some stuff, I even installed the ArcGIS (Desktop, Engine) Background Geoprocessing 64-bit Arcpy Exit and Shutdown Patch (https://support.esri.com/en/Products/Desktop/arcgis-desktop/arcmap/10-6#downloads?id=7579), that is actually supposed to be a Windows 7 fix only (I run Win10) for another issue related to arcpy, but since it involved the background processing, and was made available after the 10.6 release, I thought I might give it a try. It did not make a difference though, the background geoprocessing still failed.
The one thing I did not yet try is to uninstall the 64 bit background geoprocessing and 64 Editor, and than reinstall the 32 bit Editor and enable ordinary 32 bit background geoprocessing. I may give that a try next.
Marco

@mboeringa Hmm, I am loading Austria right now and it is still going strong. After reading the issue this morning I uninstalled the editor, cleaned out the configurations files, and did a reinstall with the official release.
Could you please send me a copy of the messages for the 64bit geoprocessing run.

@ThomasEmge ,
Unfortunately, a totally uninformative message in the geoprocessing history for the background geoprocessing run, as you can see...
It fails immediately, however, doesn't report an error at all! In fact, it shows "Succeeded" when the background processing popup reports the end after less than a second, even though inspecting the target File Geodatabase shows nothing has happened...

@ThomasEmge
Hmm... could I have a failed install? I both uninstalled and re-installed twice, but I now notice the DLL's listed as 1-9-2017? Is that right, Thomas? Shouldn't those list 2018?

I don't think so, I have the same dates. I also tried to load with German OS settings and it is still working for me.

@ThomasEmge.
I have now uninstalled both the 64 bit version of the Editor and 64 bit background processing. If I subsequently re-install the 32 bit version of the Editor, and start an import using the OSM File Loader (Load Only) tool and background processing enabled, it works! The tool properly runs and loads the data without a hitch.
So only the 64 bit version is failing. Again note that I was able to use 64 bit background processing with other non-Editor system tools of ArcGIS. So only the Editor based tools seems to fail in the 64 bit environment on my machine.

If this is still an issue, please reopen.

I just encountered the same problem: trying to load an OSM file using ARC Editor seems to do nothing. I ended up trying the same approach as above, and reverting to the 32 bit version.
I did encounter an additional clue: I tried disabling background processing, but Arcmap warned me that a background process needed to complete first.
It may be that the script is working, but that it's chugging away in the background on a large file with little outward sign of activity (eg the ticker tape message). That would explain why the apparent workaround is to disable background processing.
Running the 32 bit version of the load script, I found the only indication of activity was the message updates in the results window (which may not have been checked until an error gets flagged).  If this is the case, then the issue becomes one of improved visibility of activity.
I haven't tried the 64 bit version again.


undercover.el causes tests to fail in emacs 24.4 and 24.5

This build failed on Travis CI: https://travis-ci.org/bmag/emacs-purpose/builds/75722992
This build succeeded: https://travis-ci.org/bmag/emacs-purpose/builds/75723525
The only difference is disabling/enabling undercover, as can be seen in the diff between the two commits: https://github.com/bmag/emacs-purpose/commit/6ed404cdfd30d358af683c9e61f523ccf5a58a9a
A few months ago I didn't have any issues running undercover.el with emacs 24.4 and 24.5, as can be seen in the build history and the coverage history.
Do you have any idea what could be the problem?

@bmag I will investigate this asap.

thanks, I appreciate it

@bmag As I mention in README, undercover.el is heavily based on edebug and can have some issues with macros coverage. And it is our case.
define-purpose-compatible-advice is a reason. It's declare debug statement is incorrect. t means "All arguments are instrumented for evaluation". And for example here:
(define-purpose-compatible-advice 'compilation-next-error-function
    :around purpose--fix-compilation-next-error
    (&rest args)
    "Integrate Purpose and `compilation-next-error-function'.
Advice that prevents `compilation-next-error-function' from hiding the
compilation buffer.  This is done by ensuring that the buffer is
dedicated for the duration of the function.
This function should be advised around
`compilation-next-error-function'."
  ;; new style advice
  ((let* ((compilation-window (get-buffer-window (marker-buffer (point-marker))))
          (old-window-dedicated-p (window-dedicated-p compilation-window)))
     (set-window-dedicated-p compilation-window t)
     (unwind-protect
         (apply oldfun args)
       (set-window-dedicated-p compilation-window old-window-dedicated-p))))

  ;; old style advice
  ((let* ((compilation-window (get-buffer-window (marker-buffer (point-marker))))
          (old-window-dedicated-p (window-dedicated-p compilation-window)))
     (set-window-dedicated-p compilation-window t)
     (unwind-protect
         ad-do-it
       (set-window-dedicated-p compilation-window old-window-dedicated-p)))))

not all arguments could be instrumented as is (because thay can't be evaluated as is). Please, change edebug declaration and let me know if it works for you.
Few notes:

You can check that everything runs ok if debug is 0 or (sexp sexp sexp sexp sexp sexp sexp) (tested with emacs 24.4).

You can emulate undercover.el work with TRAVIS=true make test (it will not actually submit any data). Just to ensure that edebug works fine.

I did some improvments to undercover.el few days ago. Now, if something like that happends you will see message below  and undercover.el will fallback to simple file load without instrumenting.
 UNDERCOVER: error while covering /tmp/emacs-purpose/window-purpose-fixes.el

@bmag ping :)

You can check that everything runs ok if debug is 0 or (sexp sexp sexp sexp sexp sexp sexp) (tested with emacs 24.4).

I have removed all debug declarations from my code, just to be sure, and everything seems to run ok. Tested with 24.4 and 24.5 locally with TRAVIS=true.

if something like that happends you will see message below and undercover.el will fallback to simple file load without instrumenting.

UNDERCOVER: error while covering /tmp/emacs-purpose/window-purpose-fixes.el

Indeed, I see this message when adding (debug t) back to define-purpose-compatible-advice.
It seems the problem is on my side, due to my lack of understanding how undercover and edebug work, so I'm closing this issue. Thank you for your help, I will be fixing my debug declarations now.


"Python dependency not found" It Says

Information

ratbagd version: v0.16
Distribution: Mint 21.3 Cinnamon
Kernel version: Linux 5.15.0-97-generic x86_64 GNU/Linux

$ ratbagctl <device> info
Unable to find device unmetalmilitia4

Describe the bug
When I try to meson it can't find the Python.
To Reproduce
Steps to reproduce the behavior:

git clone https://github.com/libratbag/libratbag.git
cd libratbag
meson builddir
See error

Logs
The Meson build system
Version: 0.61.2
Source dir: /home/unmetalmilitia4/libratbag
Build dir: /home/unmetalmilitia4/libratbag/builddir
Build type: native build
Project name: libratbag
Project version: 0.17
C compiler for the host machine: cc (gcc 11.4.0 "cc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0")
C linker for the host machine: cc ld.bfd 2.38
Host machine cpu family: x86_64
Host machine cpu: x86_64
Found pkg-config: /usr/bin/pkg-config (0.29.2)
Run-time dependency libudev found: YES 249
Run-time dependency libevdev found: YES 1.12.1
Run-time dependency glib-2.0 found: YES 2.72.4
Run-time dependency json-glib-1.0 found: YES 1.6.6
Library m found: YES
Library unistring found: YES
Run-time dependency libsystemd found: YES 249
Run-time dependency systemd found: YES 249
Configuring lur-command.1 using configuration
Program /home/unmetalmilitia4/libratbag/test/data-parse-test.py found: YES (/home/unmetalmilitia4/libratbag/test/data-parse-test.py)
Program /home/unmetalmilitia4/libratbag/test/duplicate-check.py found: YES (/home/unmetalmilitia4/libratbag/test/duplicate-check.py)
Program /home/unmetalmilitia4/libratbag/test/receiver-check.py found: YES (/home/unmetalmilitia4/libratbag/test/receiver-check.py)
Run-time dependency check found: YES 0.15.2
Program valgrind found: YES (/usr/bin/valgrind)
Configuring ratbagd.service using configuration
Configuring org.freedesktop.ratbag1.service using configuration
Configuring org.freedesktop.ratbag1.conf using configuration
Program python3 found: YES (/usr/bin/python3)
WARNING: Python files installed by Meson might not be found by python interpreter.
 This warning can be avoided by setting "python.platlibdir" option.
WARNING: Python files installed by Meson might not be found by python interpreter.
 This warning can be avoided by setting "python.purelibdir" option.

meson.build:508:2: ERROR: Python dependency not found

$ ratbagd --verbose=raw
Initializing libratbag
ratbagd error: Failed to start ratbagd: Permission denied

Additional context
I can also post the meson log file if it'll help.

Hello!
meson.build:508:2: ERROR: Python dependency not found yet just above it says  Program python3 found: YES (/usr/bin/python3), hmm.
Maybe you are missing the python3-dev build dependency?
For the record, here is regular build dependency list we have in our CI workflow: gcc g++ pkg-config systemd libevdev-dev libglib2.0-dev libjson-glib-dev libsystemd-dev libudev-dev libunistring-dev python3-dev python3-evdev swig python3-sphinx.


Update errors.go: odd testing thing

Description
We've got sdk.Error 1100 assigned to both claim module errors and epoch module errors. I don't know why the build system doens't throw an error for this when building the main branch, but it doesn't.  Hence, I've made error 69420 the error for epochs, because when you need a number, 69420 has got you covered.

For contributor use:

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

Codecov Report

Merging #649 (e92558b) into main (97ac2a8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #649   +/-   ##
=======================================
  Coverage   18.42%   18.42%
=======================================
  Files         172      172
  Lines       24254    24254
=======================================
  Hits         4470     4470
  Misses      19019    19019
  Partials      765      765

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 97ac2a8...e92558b. Read the comment docs.

This is really odd, since the module names are distinct. Can you help me reproduce the error on main?

@ValarDragon no, I can't.
Isn't that wierd!?!?

Should we close this until we can reproduce? Would rather not change error codes, which is state machine & client breaking if we don't have to. (And I can't figure out an issue here, since the errors should be namespaced)


Asakatsu Project - Yoga and Exercise

Starting again, hoping to be more consistent.

Thank you, Philips!


Waffle Pi cannot map properly

Good afternoon,
After a few attempts, it was not possible to do the first mapping with Turtle Bot 3 Waffle Pi. It seems that the Robot loses its reference, and starts to map over the existing map, as you can see in the pictures below.

Have you experienced something similar? I'd appreciate some help. Thank you!

Hi :)
When SLAM have been started, a map which you attached was created well. But the map was crashing when TB3 have been far away.
I think you need to check time sync or wifi connection between RemotePC and TB3.
Below link might be help you.
http://emanual.robotis.com/docs/en/platform/turtlebot3/faq/#timesync-between-turtlebot3-and-remotepc
Thanks

This issue will be closed since there were no actions for a while. You can reopen this issue to show this issue to the users whenever. Thanks.


Refactor InstallHelp into redux + RootComponent (#313)

This should take care of #313. I added the if-statement to the RootComponent. It was the only way to keep the current behaviour, namely showing none of the other UI elements when we're showing the install help. I'm ok with this placement, but if you want it somewhere else, ie. more localized in the InstallHelp component alone, let me know.

Awesome, this is great! Having the if in RootComponent for this scenario makes sense to me. Maybe later we can have some sort of splash screen or something, but this works fine for now.

Meant to merge this in yesterday - bringing it in now. Thanks for the contribution, @FrigoEU !


[Tests-Only] Debug local api tests

Do not merge. This PR is just to run CI and see what is going wrong with the local API tests.

It looks like
      OCIS_REVA_DATA_ROOT: '/drone/src/tmp/reva/data/'

helps.
PR https://github.com/owncloud/core/pull/37999 changed that a bit.


Fix broken edit/delete buttons on address template with pagination

Fixes #385
Instead of using multiple paginate tags as the issue suggests (which also works), this wraps the entire template in the paginate tags to solve the same issue.
cc @stevebosworth @schaeken

Created a PR where I wrap everything in the paginate tags, rather than duplicating that for the JS. Seems to work well. Any issues with it you can see?

:+1:  tested it and its perfect :)


Fix incorrect k-NN output when library size and prediction size are different

Closes #34

After fix:


add 20WETH-80VMEX pool to optimism allowlist

added weighted pool 20WETH-80VMEX to optimism allowlist

@fico23 You will still need to get VMEX approved:
https://github.com/balancer/frontend-v2/wiki/How-tos#add-tokens-to-tokenlist


PYCA-523 - Remove content changes introduced for 4th January release

Request merge of change into prototype.  Screenshot seen by Fivi but needs adding to prototype too.

Closing as work has been done in another branch for simplicity.


Add docs for some exported functions

This adds some basic documentation for some of the exported APIs.

Thanks for working on this!

I've incorporated your suggestions in that commit. Is there anything else you'd like me to add or modify?

Hi @ranjanan, sorry this fell off the queue for me.  Just a small formatting fix and it should be good to merge.

Coverage increased (+0.1%) to 59.812% when pulling 8d05181c7cec3698ca8cbe57044ec8b590646b91 on ranjanan:docs into fcbe0be562d347843d107617ce178cfa70ed1a54 on stevengj:master.

Thanks!  In the future, it is also a good idea to "squash" your commits into a single commit (via git rebase), but since this is just documentation patches I can merge it as-is.
(Squashing commits is especially important for code so that you don't have non-functional commits in the history.)

Sure, thanks! Will keep that in mind.


Impossible to use ssl_verify --> Max retries exceeded with url or NotLogged

Hello,
I an trying to create a VDOM through Ansible
I am stuck at the same point I think than greenspartan in ticket #51
My FortiGate is using default configuration with default self signed certificate
Here is my configuration:
thomas@debianAnsible:/etc/ansible$ ansible --version
ansible 2.9.7
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/thomas/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/dist-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.16 (default, Oct 10 2019, 22:02:15) [GCC 8.3.0]
First try:
My playbook:
- hosts: localhost
  vars:
   host: "10.5.X.1"
   username: "admin"
   password: "fortinet"
   ssl_verify: "False"
   vdom: "root"
  tasks:
  - name: Configure virtual domain.
    fortios_system_vdom:
      host:  "{{ host }}"
      username: "{{ username }}"
      password: "{{ password }}"
      vdom:  "{{ vdom }}"
      https: "False"
      state: "present"
      system_vdom:
        name: "default_name_3"
        short_name: "<your_own_value>"
        temporary: "5"
        vcluster_id: "6"

Here is the output:
Using /etc/ansible/ansible.cfg as config file
[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'

PLAY [localhost] **************************************************************************************************************************************************************************************************

TASK [Gathering Facts] ********************************************************************************************************************************************************************************************
ok: [localhost]

TASK [Configure virtual domain.] **********************************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "No handlers could be found for logger \"fortiosapi\"\nTraceback (most recent call last):\n  File \"/home/thomas/.ansible/tmp/ansible-tmp-1588688299.47-955-192869020258714/AnsiballZ_fortios_system_vdom.py\", line 102, in <module>\n    _ansiballz_main()\n  File \"/home/thomas/.ansible/tmp/ansible-tmp-1588688299.47-955-192869020258714/AnsiballZ_fortios_system_vdom.py\", line 94, in _ansiballz_main\n    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n  File \"/home/thomas/.ansible/tmp/ansible-tmp-1588688299.47-955-192869020258714/AnsiballZ_fortios_system_vdom.py\", line 40, in invoke_module\n    runpy.run_module(mod_name='ansible.modules.network.fortios.fortios_system_vdom', init_globals=None, run_name='__main__', alter_sys=True)\n  File \"/usr/lib/python2.7/runpy.py\", line 188, in run_module\n    fname, loader, pkg_name)\n  File \"/usr/lib/python2.7/runpy.py\", line 82, in _run_module_code\n    mod_name, mod_fname, mod_loader, pkg_name)\n  File \"/usr/lib/python2.7/runpy.py\", line 72, in _run_code\n    exec code in run_globals\n  File \"/tmp/ansible_fortios_system_vdom_payload_J84qe7/ansible_fortios_system_vdom_payload.zip/ansible/modules/network/fortios/fortios_system_vdom.py\", line 350, in <module>\n  File \"/tmp/ansible_fortios_system_vdom_payload_J84qe7/ansible_fortios_system_vdom_payload.zip/ansible/modules/network/fortios/fortios_system_vdom.py\", line 339, in main\n  File \"/tmp/ansible_fortios_system_vdom_payload_J84qe7/ansible_fortios_system_vdom_payload.zip/ansible/modules/network/fortios/fortios_system_vdom.py\", line 224, in login\n  File \"/home/thomas/.local/lib/python2.7/site-packages/fortiosapi/fortiosapi.py\", line 170, in login\n    data='username=' + urllib.parse.quote(username) + '&secretkey=' + urllib.parse.quote(password) + \"&ajax=1\", timeout=self.timeout)\n  File \"/home/thomas/.local/lib/python2.7/site-packages/requests/sessions.py\", line 578, in post\n    return self.request('POST', url, data=data, json=json, **kwargs)\n  File \"/home/thomas/.local/lib/python2.7/site-packages/requests/sessions.py\", line 530, in request\n    resp = self.send(prep, **send_kwargs)\n  File \"/home/thomas/.local/lib/python2.7/site-packages/requests/sessions.py\", line 665, in send\n    history = [resp for resp in gen] if allow_redirects else []\n  File \"/home/thomas/.local/lib/python2.7/site-packages/requests/sessions.py\", line 245, in resolve_redirects\n    **adapter_kwargs\n  File \"/home/thomas/.local/lib/python2.7/site-packages/requests/sessions.py\", line 643, in send\n    r = adapter.send(request, **kwargs)\n  File \"/home/thomas/.local/lib/python2.7/site-packages/requests/adapters.py\", line 514, in send\n    raise SSLError(e, request=request)\nrequests.exceptions.SSLError: HTTPSConnectionPool(host='10.5.X.1', port=443): Max retries exceeded with url: /logincheck (Caused by SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:727)'),))\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}

PLAY RECAP ********************************************************************************************************************************************************************************************************
localhost                  : ok=1    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

2nd try:
My playbook:
- hosts: localhost
  vars:
   host: "10.5.X.1"
   username: "admin"
   password: "fortinet"
   ssl_verify: "False"
   vdom: "root"
  tasks:
  - name: Configure virtual domain.
    fortios_system_vdom:
      host:  "{{ host }}"
      username: "{{ username }}"
      password: "{{ password }}"
      ssl_verify: "{{ ssl_verify }}"  <----- Added
      vdom:  "{{ vdom }}"
      https: "False"
      state: "present"
      system_vdom:
        name: "default_name_3"
        short_name: "<your_own_value>"
        temporary: "5"
        vcluster_id: "6"

Here is the output:
PLAY [localhost] **************************************************************************************************************************************************************************************************

TASK [Gathering Facts] ********************************************************************************************************************************************************************************************
ok: [localhost]

TASK [Configure virtual domain.] **********************************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "No handlers could be found for logger \"fortiosapi\"\n/home/thomas/.local/lib/python2.7/site-packages/urllib3/connectionpool.py:986: InsecureRequestWarning: Unverified HTTPS request is being made to host '10.5.X.1'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings\n  InsecureRequestWarning,\n/home/thomas/.local/lib/python2.7/site-packages/urllib3/connectionpool.py:986: InsecureRequestWarning: Unverified HTTPS request is being made to host '10.5.X.1'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings\n  InsecureRequestWarning,\n/home/thomas/.local/lib/python2.7/site-packages/urllib3/connectionpool.py:986: InsecureRequestWarning: Unverified HTTPS request is being made to host '10.5.X.1'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings\n  InsecureRequestWarning,\nTraceback (most recent call last):\n  File \"/home/thomas/.ansible/tmp/ansible-tmp-1588688469.75-1041-79183703068022/AnsiballZ_fortios_system_vdom.py\", line 102, in <module>\n    _ansiballz_main()\n  File \"/home/thomas/.ansible/tmp/ansible-tmp-1588688469.75-1041-79183703068022/AnsiballZ_fortios_system_vdom.py\", line 94, in _ansiballz_main\n    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n  File \"/home/thomas/.ansible/tmp/ansible-tmp-1588688469.75-1041-79183703068022/AnsiballZ_fortios_system_vdom.py\", line 40, in invoke_module\n    runpy.run_module(mod_name='ansible.modules.network.fortios.fortios_system_vdom', init_globals=None, run_name='__main__', alter_sys=True)\n  File \"/usr/lib/python2.7/runpy.py\", line 188, in run_module\n    fname, loader, pkg_name)\n  File \"/usr/lib/python2.7/runpy.py\", line 82, in _run_module_code\n    mod_name, mod_fname, mod_loader, pkg_name)\n  File \"/usr/lib/python2.7/runpy.py\", line 72, in _run_code\n    exec code in run_globals\n  File \"/tmp/ansible_fortios_system_vdom_payload_Mf8gAM/ansible_fortios_system_vdom_payload.zip/ansible/modules/network/fortios/fortios_system_vdom.py\", line 350, in <module>\n  File \"/tmp/ansible_fortios_system_vdom_payload_Mf8gAM/ansible_fortios_system_vdom_payload.zip/ansible/modules/network/fortios/fortios_system_vdom.py\", line 340, in main\n  File \"/tmp/ansible_fortios_system_vdom_payload_Mf8gAM/ansible_fortios_system_vdom_payload.zip/ansible/modules/network/fortios/fortios_system_vdom.py\", line 284, in fortios_system\n  File \"/tmp/ansible_fortios_system_vdom_payload_Mf8gAM/ansible_fortios_system_vdom_payload.zip/ansible/modules/network/fortios/fortios_system_vdom.py\", line 267, in system_vdom\n  File \"/home/thomas/.local/lib/python2.7/site-packages/fortiosapi/fortiosapi.py\", line 417, in set\n    mkey = self.get_mkey(path, name, data, vdom=vdom)\n  File \"/home/thomas/.local/lib/python2.7/site-packages/fortiosapi/fortiosapi.py\", line 228, in get_mkey\n    keyname = self.get_mkeyname(path, name, vdom)\n  File \"/home/thomas/.local/lib/python2.7/site-packages/fortiosapi/fortiosapi.py\", line 217, in get_mkeyname\n    schema = self.schema(path, name, vdom=vdom)\n  File \"/home/thomas/.local/lib/python2.7/site-packages/fortiosapi/fortiosapi.py\", line 317, in schema\n    url = self.cmdb_url(path, name, vdom=vdom) + \"&action=schema\"\n  File \"/home/thomas/.local/lib/python2.7/site-packages/fortiosapi/fortiosapi.py\", line 252, in cmdb_url\n    self.check_session()\n  File \"/home/thomas/.local/lib/python2.7/site-packages/fortiosapi/fortiosapi.py\", line 126, in check_session\n    raise NotLogged()\nfortiosapi.exceptions.NotLogged: Not logged on a session, please login.\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}

PLAY RECAP ********************************************************************************************************************************************************************************************************
localhost                  : ok=1    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

I am sure of the credentials as I can log from debianAnsible in my FortiGate using SSH:
thomas@debianAnsible:/etc/ansible$ ssh<EMAIL_ADDRESS>The authenticity of host '10.5.X.1 (10.5.X.1)' can't be established.
ED25519 key fingerprint is SHA256:ejSbDEsTO09eQcC/RN5kqtxXgLGzs5wi6XcRbt05Ia4.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.5.X.1' (ED25519) to the list of known hosts.
<EMAIL_ADDRESS>password:
fortinet-vm #

I am stuck could you help me?
Is there any bug?
Cheers
Thomas

I tried to edit:

class FortiOSAPI(object):
    def __init__(self):
        self.host = None
        self._https = True
        self._logged = False
        self._fortiversion = "Version is set when logged"
        # reference the fortinet version of the targeted product.
        self._session = requests.session()  # use single session
        # persistant and same for all
        self._session.verify = True <------------------------------------------------------ Set to False
        # (can be changed to) self._session.verify = '/etc/ssl/certs/' or False
        self.timeout = 120
        self.cert = None
        self._apitoken = None
        self._license = None
        self.url_prefix = None

in
/home/thomas/.local/lib/python2.7/site-packages/fortiosapi/fortiosapi.py

This is not a project for Ansible and official Ansible module do not use fortiosapi anymore.
Refer to : https://github.com/fortinet-ansible-dev/ansible-galaxy-fortios-collection


[Feature Request] Support private packages

Currently the packages managed must be public. Is it possible to also clean-up private-scoped packages, using the GITHUB_TOKEN provided?

Thanks for the PR.  I thought I did (manual) testing where I made the package private. What was the error you were getting?  Also what is the difference between the octokit 'authenticated' methods, I couldn't find any docs on those, I see you are using those methods.

The error I encountered is that the resource is not accessible.

deleting package id: 23144 digest: sha256:8a3e861c3b88654b57b1003cd081f6c4ad9f213749f40be3ccc12de831
Error: Resource not accessible by integration - https://docs.github.com/rest/packages/packages#delete-package-version-for-a-user

Interesting. Was your action using the GITHUB_TOKEN or some other token (like a personal access token)?

I was using the GITHUB_TOKEN. The getAllPackageVersionsForPackageOwnedByUser mentions in its documentation:

Lists package versions for a public package owned by a specified user.
https://octokit.github.io/rest.js/v20#packages-get-all-package-versions-for-package-owned-by-user

I have been testing the action using this yml:
name: Clean up images

on:
  push:
    branches:
      - ci/clean-up-images

jobs:
  clean-up-images:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      packages: read
      id-token: write
    strategy:
      matrix:
        image: [ image-name ]
    steps:
      - name: Delete untagged images from Container Registry
        uses<EMAIL_ADDRESS>        with:
          package: ${{ matrix.image }}
          token: ${{ secrets.GITHUB_TOKEN }}

Ah I see.  At some point I think I migrated back to the non-authenticated method, not realizing the impact.  I see you utilized the isPrivateRepo state I had extracted (but not used!).
There are some formatting/lint checks on the PR code but the tests are passing. I'll merge your PR and fix those lint errors.
Thanks again for the fix!

Thanks for merging! Yes, the formatting/lint showed some warnings that I tried to fix, perhaps I made some new ones on the way.

I'll make a release shortly, probably in the next week or two.

released in v1/v1.0.6 (3802012)


Model and Sample Download link is not available.

Sorry for the request, is it possible to reupload the model and Sample file once again?

@peterhiking I apologize for responding late. The model and samples are no more accessible.


Problem 0010: solved

Codecov Report

Merging #38 (7636d1f) into main (4b3ceaa) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #38   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        16    +1
  Lines          357       372   +15
  Branches        47        49    +2
=========================================
+ Hits           357       372   +15

Impacted Files
Coverage Δ

src/problem0010.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


fix: Include discrete timepoints of final atlas in set of ages()

@jcupitt Let me know when this fixed the issue with the atlas so we can merge it into master.

It worked! The final lines of output:
2018-Dec-12 19:04:29 DONE 28 succeeded, 0 failed
2018-Dec-12 19:04:29 INFO Finished atlas construction!

So (in my opinion) this is good to merge.


modify lexer. (save all tokens)

modify lexer to save all tokens. this make it easier to backtrack in parsing.
fix bug #45.
implement comma operator.

Add test for arrow function.
Fix bug for parsing arrow function.


multi cluster landing page

Co-authored-by: Marty Spiewak<EMAIL_ADDRESS>
Changes proposed by this PR

closes #543

Release Note

PR Checklist
Note: Please do not remove items. Mark items as done [x] or use ~strikethrough~ if you believe they are not relevant

[ ] Linked to a relevant issue. Eg: Fixes #123 or Updates #123
[ ] Removed non-atomic or wip commits
[ ] Filled in the Release Note section above
[ ] Modified the docs to match changes

It would be nice to add some notes about how we expect promotion to work between environments as per @zrob note here: https://github.com/vmware-tanzu/cartographer/issues/543#issuecomment-1045049832
We want to describe something along the lines of:

supply chain builds config and commits to a branch staging/feature-a
a human PRs branch staging/feature-a into staging
those changes get deployed to staging env
a task at the end of the staging delivery commits to something like prod/feature-a (essentially promoting those changes)
a human PRs changes from prod/feature-a into prod
those changes get deployed on prod

yay! glad to see us starting to get some guidance here!

consider changing the "development" cluster name to "build" since that's more what's happening

would be nice to see some description on the why and role for the different clusters. ie - you want an isolated build cluster. then want to promote the same artifact through multiple environments to first test/validate, then run in production.


Per-branch previews of the hosted spec

related... https://github.com/tobie/pr-preview

to discuss Feb 10 2022: ok to close?


kotlin: add endStream to onHeaders callback signature

Description: add endStream to onHeaders callback signature
Risk Level: low
Testing: built locally
Signed-off-by: Jose Nino<EMAIL_ADDRESS>

Looks like the CI failure is legit


fix(browser): fix browser testing url for https

Description
Closes https://github.com/vitest-dev/vitest/issues/4844
I used ViteDevServer.resolvedUrls to grab the url for browser testing. I think this should be always available and If this is not available, then it's probably a Vite bug, so I didn't put any fallback or validation here.
~On a related note, currently Vite's base config is not supported yet (as reported in https://github.com/vitest-dev/vitest/issues/4686), but ViteDevServer.resolvedUrls will be also generated according to base config~, so I think treating resolvedUrls as a single source of truth is appropriate for browser testing.
(Actually base doesn't change browser testing url since it's always root /, but I guess it would still make sense to use resolvedUrls as a way to get origin.)

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
[x] Ideally, include a test that fails without this PR but passes with it.
[ ] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

[x] Run the tests with pnpm test:ci.

Documentation

[ ] If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

[x] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

Btw, when running browser mode test during pnpm dev, I'm getting this error sometimes:
$ pnpm -C test/browser test-fixtures

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

Vitest caught 1 unhandled error during the test run.
This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Error: [birpc] timeout on calling "getFiles"
 ❯ ../../../../../../../../../__vitest__/assets/index-0EYobN63.js:5:60901

This error originated in "basic.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 Test Files  no tests
      Tests  no tests
     Errors  1 error

This doesn't happen when running tests after pnpm build.

Wait... it looks like the new regex is too general and regex DoS is happening on this file packages/vitest/dist/vendor/vi.smj1Ggd4.js. I will analyze this further.

This is what I was afraid of, it was too strict on purpose but I remember the specifics :(


gio::Application::get_default() is unsound

It allows retrieving the application from any thread, not just the main thread (or more general the thread where the application was created). gio::Application is not thread-safe, so this is a problem.

It seems this can never be completely safe because g_application_set_default is not thread safe, and that gets called internally by GApplication implementations. I guess what that means is, a GApplication can only be referenced in the main thread, but we don't have any way of knowing what the main thread really is, getting the current thread id is just a guess.
It could be made a little more robust by checking if we can acquire the main context before storing the qdata, but that still isn't completely safe in all cases because it only checks for a running application...

Yeah the problem with making get_default() unsafe is that it's a very useful API to have in GTK applications and requiring those to use unsafe code is not ideal (set_default() is fine IMHO, who needs that anyway...)

That will not fully make it sound but will probably correct most of the issues people have. The wrapper macro will need some modifications here to do the thread checking so we may need to see https://github.com/gtk-rs/gtk-rs-core/issues/916 for that

I think the easiest would be to implement default() manually for now and implement the same assertion that is also used in e.g. glib::MainContext::spawn_local(). That should cover the easiest mistakes at least.
More correct would be to forbid construction of a gio::Application from another thread but that requires glib::wrapper! macro changes as @jf2048 says, and not very easy ones.
Does someone want to do the easy part for now?

I think the easiest would be to implement default() manually for now and implement the same assertion that is also used in e.g. glib::MainContext::spawn_local(). That should cover the easiest mistakes at least.

How can we do that, since Application does not reference a MainContext? I think any solution will need to modify the wrapper and do the qdata solution described above.

Can you actually use an Application on a non-default main context?


Fix coveralls and refactor test_sh.yaml (separation of concerns)

Coveralls.io reporting works again
pylint and bandit are able to truly run in parallel with everything else

pylint and bandit can be re-triggered separately from the pytests (and vice-versa)

Maintainers will complete the following section

[x] Commit messages are descriptive enough
[x] Code coverage from testing does not decrease and new code is covered
[x] JSON/YAML configuration changes are updated in the relevant schema
[x] Changes to metadata also update the documentation for the metadata
[ ] Pull request has a link to an osbs-docs PR for user documentation updates
[ ] New feature can be disabled from a configuration file

No release notes added. Test suite related change.

@athos-ribeiro, @chmeliik; I didn't bother, given that we currently have (I assume on purpose):
pylint:
F29
F31
bandit:
Cent 7
F31
pytest:
Cent 7
F30
F31
So, there's a Venn diagram there, but not one that's useful ;)


Doesn't work with forks.

Hi,
This GitHub action will only work if a PR is created within the same repo.
It doesn't work if a repo is forked and then a PR is created from the fork to the original upstream repository.

+1, facing this issue here: https://github.com/kubernetes-monitoring/kubernetes-mixin/pull/838.
cc @prymitive


[MINOR][DOCS] Fix incorrect EqualNullSafe symbol in sql-migration-guide.md

What changes were proposed in this pull request?
This PR fixes the incorrect EqualNullSafe symbol in sql-migration-guide.md.
Why are the changes needed?
Fix documentation error.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
N/A

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/17256/
Test PASSed.

Test build #112272 has started for PR 26163 at commit 371c65a.

Test build #112272 has finished for PR 26163 at commit 371c65a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged to master


fix: Don't require a responsible AD to be identified for new status change

Fixes #4159

Shouldn't have approved this - the tests still required that the forms fail if you don't supply an AD. Will provide a fix, but yet another place where we are letting failing tests slide and real issues slide through with them.


ffa_v0_env in jupyter notebook should be replaced by ffa_v0_fast_env

I suspect the notebook is simply not up to date. I tested replacing all ffa_v0_env and was able to run the whole notebook.
(I also hesitated to do a PR because commit on notebooks are usually messy with unwanted local env changes, eg. cell execution number, etc; however if a PR is ok please let me know I'm more than happy to do it)
This is the definition in pommerman/configs.py
Thanks.

Hey there, a PR is definitely ok and appreciated! Thanks for finding this.
On Mon, Aug 6, 2018 at 17:13 Xiayun Sun<EMAIL_ADDRESS>wrote:

I suspect the notebook is simply not up to date.
(I also hesitated to do a PR because commit on notebooks are usually messy
with unwanted local env changes, eg. cell execution number, etc; however if
a PR is ok please let me know I'm more than happy to do it)
This
https://github.com/MultiAgentLearning/playground/blob/master/pommerman/configs.py#L82
is the definition in pommerman/configs.py
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MultiAgentLearning/playground/issues/128, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAljt7-cJV_rAHiOUaewDfonLMCMySdEks5uOLFpgaJpZM4VxF_b
.

Thanks @cinjon . PR submitted #129


hardcode: types.Sizes for gopherjs

Codecov Report

Merging #34 (ef07172) into main (e55f82a) will decrease coverage by 0.04%.
The diff coverage is 25.00%.

@@            Coverage Diff             @@
##             main      #34      +/-   ##
==========================================
- Coverage   93.02%   92.97%   -0.05%
==========================================
  Files          12       12
  Lines        5950     5954       +4
==========================================
+ Hits         5535     5536       +1
- Misses        327      329       +2
- Partials       88       89       +1

Impacted Files
Coverage Δ

builtin.go
90.57% <25.00%> (-0.30%)
:arrow_down:

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 e55f82a...ef07172. Read the comment docs.


[Error - Question] Failed To get Entities from the store - Subgraph query error while trying to run graph-node and harhdat locally.

Bug report
Basic explanation of the problem
I'm currently working on a local subgraph for tracking events on an Ethereum smart contract. I aim to query specific entities, but I'm encountering an error when attempting to do so. The error message I'm receiving is: '"message": "Failed to get entities from store: Odd number of digits, query = from \"sgd2\".\"task_created\"[*]{id = 1} order none first 100 at 0 query_id 7316f7c8141c25f5-6dc8c4ef99f8cc6a"'" . I am honestly pretty noob on this, so I would greatly appreciate your help.
Steps to reproduce the problem

Started a local blockchain with npx hardhat node --hostname <IP_ADDRESS>

Configured my hardhat.config.ts as follows:
localhost: {
chainId: 1337,
url: "htpp://<IP_ADDRESS>:8545"

Compiled my smart contract and deployed it to the hardhat node, which generated the following message:

Contract deployment: Web3Task
Contract address:    0xec20dcbf0380f1c9856ee345af41f62ee45a95a1
Transaction:         0xf8f0de6b1a4a2895dffc30db1f7dc56853c1b94570190ea43e2aa331b9dd3214
From:                0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266
Value:               0 ETH
Gas used:            4006332 of 4006332
Block #38359529:     0x50ae5ffd41dee3d39dbc32ae9d5fcc95fac9830d2d7d1700795977e7027305ef

I cloned the graph-node repository inside my main contracts directory

in docker/docker-compose.yml I configured the file as follows:

version: "3"
services:
graph-node:
image: graphprotocol/graph-node
ports:
- "8000:8000"
- "8001:8001"
- "8020:8020"
- "8030:8030"
- "8040:8040"
depends_on:
- ipfs
- postgres
extra_hosts:
- host.docker.internal:host-gateway
environment:
postgres_host: postgres
postgres_user: graph-node
postgres_pass: let-me-in
postgres_db: graph-node
ipfs: "ipfs:5001"
ethereum: "mainnet:http://host.docker.internal:8545"
GRAPH_LOG: info
ETHEREUM_REORG_THRESHOLD: 1
ETHEREUM_ANCESTOR_COUNT: 1
ipfs:
image: ipfs/kubo:v0.14.0
ports:
- "5001:5001"
volumes:
- ./data/ipfs:/data/ipfs
postgres:
image: postgres:14
ports:
- "5432:5432"
command:
[
"postgres",
"-cshared_preload_libraries=pg_stat_statements",
"-cmax_connections=200",
]
environment:
POSTGRES_USER: graph-node
POSTGRES_PASSWORD: let-me-in
POSTGRES_DB: graph-node
# FIXME: remove this env. var. which we shouldn't need. Introduced by
# https://github.com/graphprotocol/graph-node/pull/3511, maybe as a
# workaround for https://github.com/docker/for-mac/issues/6270?
PGDATA: "/var/lib/postgresql/data"
POSTGRES_INITDB_ARGS: "-E UTF8 --locale=C"
volumes:
- ./data/postgres:/var/lib/postgresql/data

Run the command docker-compose up (log in Relevant log output)

And the hardhat log keeps going with the same values in a loop.

eth_getBlockByNumber
eth_getBlockByHash
eth_getBlockByNumber (2)
eth_getLogs
eth_getBlockByHash
eth_getBlockByNumber (2)

And then I upload my subgraph with:
npm run create-local
npm run deploy-local

which shows:
**Build completed: QmS2ppDqbW1Lg3B2DSkd8nK51vepDgdwsuCFg7vKufntHY
Deployed to http://localhost:8000/subgraphs/name/web3task_subraph/graphql
Subgraph endpoints:
Queries (HTTP):     http://localhost:8000/subgraphs/name/web3task_subraph**

My schema.graphql looks as follows: (this is not the whole file, I just kept some of the events in order to not make it so long)

type TaskCreated @entity(immutable: true) {
  id: Bytes!
  taskId: BigInt! # uint256
  creator: Bytes! # address
  assignee: Bytes! # address
  reward: BigInt! # uint256
  endDate: BigInt! # uint256
  blockNumber: BigInt!
  blockTimestamp: BigInt!
  transactionHash: Bytes!
}

type TaskStarted @entity(immutable: true) {
  id: Bytes!
  taskId: BigInt! # uint256
  assignee: Bytes! # address
  blockNumber: BigInt!
  blockTimestamp: BigInt!
  transactionHash: Bytes!
}

10. And then my query and the error:

I tried to run some local tests to generate traffic to query it.
How do I solve this error and what is causing it?
Edit:
My subgraph.yaml:
specVersion: 0.0.5
schema:
  file: ./schema.graphql
dataSources:
  - kind: ethereum
    name: Web3Task
    network: mainnet
    source:
      address: "0xec20dcbf0380f1c9856ee345af41f62ee45a95a1"
      abi: Web3Task
      startBlock: 1
    mapping:
      kind: ethereum/events
      apiVersion: 0.0.7
      language: wasm/assemblyscript
      entities:
        - Approval
        - ApprovalForAll
        - AuthorizedOperator
        - AuthorizedPersonnel
        - TaskCreated
        - TaskStarted
        - TaskUpdated
        - Transfer
      abis:
        - name: Web3Task
          file: ./abis/Web3Task.json
      eventHandlers:
        - event: Approval(indexed address,indexed address,indexed uint256)
          handler: handleApproval
        - event: ApprovalForAll(indexed address,indexed address,bool)
          handler: handleApprovalForAll
        - event: AuthorizedOperator(indexed uint256,indexed bytes4)
          handler: handleAuthorizedOperator
        - event: AuthorizedPersonnel(indexed uint256,indexed address,bool)
          handler: handleAuthorizedPersonnel
        - event: TaskCreated(indexed uint256,indexed address,indexed address,uint256,uint256)
          handler: handleTaskCreated
        - event: TaskStarted(indexed uint256,indexed address)
          handler: handleTaskStarted
        - event: TaskUpdated(indexed uint256,uint8)
          handler: handleTaskUpdated
        - event: Transfer(indexed address,indexed address,indexed uint256)
          handler: handleTransfer
      file: ./src/web-3-task.ts

Relevant log output
graph-node_1  | Sep 15 16:18:49.114 INFO Scanning blocks [2133112, 2135111], range_size: 2000, sgd: 2, subgraph_id: QmS2ppDqbW1Lg3B2DSkd8nK51vepDgdwsuCFg7vKufntHY, component: BlockStream
graph-node_1  | Sep 15 16:18:49.482 INFO Scanning blocks [2135112, 2137111], range_size: 2000, sgd: 2, subgraph_id: QmS2ppDqbW1Lg3B2DSkd8nK51vepDgdwsuCFg7vKufntHY, component: BlockStream
graph-node_1  | Sep 15 16:18:49.815 INFO Scanning blocks [2137112, 2139111], range_size: 2000, sgd: 2, subgraph_id: QmS2ppDqbW1Lg3B2DSkd8nK51vepDgdwsuCFg7vKufntHY, component: BlockStream
graph-node_1  | Sep 15 16:18:50.180 INFO Scanning blocks [2139112, 2141111], range_size: 2000, sgd: 2, subgraph_id: QmS2ppDqbW1Lg3B2DSkd8nK51vepDgdwsuCFg7vKufntHY, component: BlockStream
graph-node_1  | Sep 15 16:18:50.519 INFO Scanning blocks [2141112, 2143111], range_size: 2000, sgd: 2, subgraph_id: QmS2ppDqbW1Lg3B2DSkd8nK51vepDgdwsuCFg7vKufntHY, component: BlockStream
graph-node_1  | Sep 15 16:18:50.882 INFO Scanning blocks [2143112, 2145111], range_size: 2000, sgd: 2, subgraph_id: QmS2ppDqbW1Lg3B2DSkd8nK51vepDgdwsuCFg7vKufntHY, component: BlockStream
graph-node_1  | Sep 15 16:18:51.237 INFO Scanning blocks [2145112, 2147111], range_size: 2000, sgd: 2, subgraph_id: QmS2ppDqbW1Lg3B2DSkd8nK51vepDgdwsuCFg7vKufntHY, component: BlockStream
graph-node_1  | Sep 15 16:18:51.569 INFO Scanning blocks [2147112, 2149111], range_size: 2000, sgd: 2, subgraph_id: QmS2ppDqbW1Lg3B2DSkd8nK51vepDgdwsuCFg7vKufntHY, component: BlockStream
graph-node_1  | Sep 15 16:18:51.904 INFO Scanning blocks [2149112, 2151111], range_size: 2000, sgd: 2, subgraph_id: QmS2ppDqbW1Lg3B2DSkd8nK51vepDgdwsuCFg7vKufntHY, component: BlockStream
graph-node_1  | Sep 15 16:18:52.263 INFO Scanning blocks [2151112, 2153111], range_size: 2000, sgd: 2, subgraph_id: QmS2ppDqbW1Lg3B2DSkd8nK51vepDgdwsuCFg7vKufntHY, component: BlockStream

IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out

[ ] Tick this box if this bug is caused by a regression found in the latest release.
[ ] Tick this box if this bug is specific to the hosted service.
[X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information
None

@lutter any clues? I haven't seen that "odd number of digits" error before

I've never seen that before, either. I assume that it is caused by somehow having a string with a hex value in it with an odd number of digits (i.e., 0xbee instead of 0xbeef) But I have no idea how that could happen

I found the problem.
It happened when in my schema.graphql I assign id: ID! for an entity and in the mapping.ts the id is not a string.
So with the following line et id = event.transaction.hash  .toHexString()  .concat("-")  .concat(event.logIndex.toString());
I stopped having this issue.
Now I am just getting the result as "null" tho. Any Idea why? I am stuck on this result.
@lutter @azf20

ok thanks @RafaDSan - when you say Now I am just getting the result as "null" do you mean that nothing is returned when you query the subgraph?

ok thanks @RafaDSan - when you say Now I am just getting the result as "null" do you mean that nothing is returned when you query the subgraph?

@azf20  it returned like:
{ "data": { "taskCreated": null } }
But I solved the problem. I was triggering the task-created events wrong, which is why I received the null result when trying to query it.
Now it is working fine! Should I post something more about it to close the issue?

Got it - glad you solved it, closing this issue


Bump priority of markov chain and dynamic programming rewrites

I would love to teach some of the following mid-next week, if there is any way to bump the priority of the following:

[ ] https://lectures.quantecon.org/jl/mccall_model.html
[ ] https://lectures.quantecon.org/jl/mccall_model_with_separation.html
[ ] https://lectures.quantecon.org/jl/short_path.html
[ ] https://lectures.quantecon.org/jl/finite_markov.html

I believe that @arnavs  has started on https://github.com/QuantEcon/lecture-source-jl/pull/218 for some of it.  @Nosferican  if you were able to do the short_path and finite_markov it may make sense as a way to separate things.

We also merged https://github.com/QuantEcon/lecture-source-jl/pull/173 for the Finite Markov rewrite. @jlperla let me know if you think we should revisit that one.

Sounds good. @jlperla do you have any comments or issues with the current versions? Both short_path and finite_markov seem to be quite up to date. If none, I can do a quick tuning of aesthetic and style, but don't seem like these need any major re-writes.

https://github.com/jlperla/ECON407_2018/tree/master/notebooks Jesse's old stuff, should be aware of this while rewriting.

I think that you guys may be through most of my changes for these.  The other places where the notebooks are useful are in other areas.  In particular markov_asset.rst and discrete_dp.rst in particular


Include guide for .NET Core 3.1 web project

Could you please write a guide on how to integrate with a .NET Core 3.1 web project? Got it working with a Node.js Console Application but that was not straight forward either. See my reply on SO:
https://stackoverflow.com/a/64064559/3850405

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

ID: 32738a06-835b-5bd5-7a6c-942c681aca97
Version Independent ID: e715d12c-a4aa-eec3-c05f-1ff6243d209b
Content: Unit testing JavaScript and TypeScript - Visual Studio
Content Source: docs/javascript/unit-testing-javascript-with-visual-studio.md
Product: visual-studio-windows
Technology: vs-javascript
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@Ogglas Thanks for the suggestion. I will add it to the backlog, and try to take a look at this soon.

Doc update coming. For now, see this:
MicrosoftDocs/visualstudio-docs#6306

Updated the doc with a new section for ASP.NET Core & JS/TS. Let me know if I missed anything.
Write unit tests for ASP.NET Core


null is not an object (evaluating 'HMSManager.build')

When I create a new project and follow the tutorial steps on the 100ms React Native guide, I am consistently getting this error.
Reproduction steps:

Create a new React Native project (I have tried expo init and create-react-native-app)
Navigate into project and install dependency with npm install @100mslive/react-native-hms --save
Initialize the sdk with import HmsManager from '@100mslive/react-native-hms'; and calling HmsManager.build();
Run the project using npm start or expo start

Here's my initialization code, in a project using reacts tabbed template:
import { useState, useEffect } from 'react';

import { StatusBar } from 'expo-status-bar';
import { SafeAreaProvider } from 'react-native-safe-area-context';

import useCachedResources from './hooks/useCachedResources';
import useColorScheme from './hooks/useColorScheme';
import Navigation from './navigation';

import HmsManager from '@100mslive/react-native-hms';

export default function App() {
  const isLoadingComplete = useCachedResources();
  const colorScheme = useColorScheme();
  const [hmsInstance, setHmsInstance] = useState({});
  const [isHmsInstanceInitialized, setHmsInstanceInitialized] = useState(false);

  useEffect(() => {
    if (isHmsInstanceInitialized)
    {
      return;
    }

    console.log("manager: " + HmsManager);
      HmsManager.build()
        .then((instance) => {
          console.log("hms instance: " + instance);
          setHmsInstance(instance);
          setHmsInstanceInitialized(true);
        })
        .catch((console.error));

  }, []);

  if (!isLoadingComplete) {
    return null;
  } else {
    return (

      <SafeAreaProvider>
        <Navigation colorScheme={colorScheme} />
        <StatusBar />
      </SafeAreaProvider>
    );
  }
}

When opening the app on an Android device (Google Pixel 5, Samsung Note 20), I get the following error:
null is not an object (evaluating 'HMSManager.build') at node_modules\@100mslive\react-native-hms\src\classes\HMSSDK.tsx:null in build at node_modules\@babel\runtime\helpers\regeneratorRuntime.js:null in tryCatch at node_modules\@babel\runtime\helpers\regeneratorRuntime.js:null in <anonymous> at node_modules\@babel\runtime\helpers\regeneratorRuntime.js:null in tryCatch at node_modules\@babel\runtime\helpers\regeneratorRuntime.js:null in invoke at node_modules\@babel\runtime\helpers\regeneratorRuntime.js:null in PromiseImpl$argument_0 at node_modules\promise\setimmediate\core.js:null in tryCallTwo at node_modules\promise\setimmediate\core.js:null in doResolve at node_modules\promise\setimmediate\core.js:null in Promise at node_modules\@babel\runtime\helpers\regeneratorRuntime.js:null in callInvokeWithMethodAndArg at node_modules\@babel\runtime\helpers\regeneratorRuntime.js:null in _invoke at node_modules\@babel\runtime\helpers\regeneratorRuntime.js:null in exports.async at node_modules\@100mslive\react-native-hms\src\classes\HMSSDK.tsx:null in build at App.tsx:null in useEffect$argument_0 at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:null in commitHookEffectListMount at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:null in commitPassiveMountOnFiber at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:null in commitPassiveMountEffects_complete at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:null in commitPassiveMountEffects_begin at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:null in commitPassiveMountEffects at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:null in flushPassiveEffectsImpl at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:null in flushPassiveEffects at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:null in performSyncWorkOnRootat node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:null in flushSyncCallbacks at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:null in flushSyncCallbacksOnlyInLegacyMode at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:null in scheduleUpdateOnFiberat node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:null in updateContainer at node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:null in render at node_modules\react-native\Libraries\ReactNative\renderApplication.js:null in renderApplication at node_modules\react-native\Libraries\ReactNative\AppRegistry.js:null in runnables.appKey.run at node_modules\react-native\Libraries\ReactNative\AppRegistry.js:null in runApplication at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:null in __callFunction at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:null in __guard$argument_0 at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:null in __guard at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:null in callFunctionReturnFlushedQueue
react-native-cli: 2.0.1
react-native: 0.68.2
expo: 6.0.0
By making an adjust to HMSSDK.tsx, I am able to get rid of the error. I change line 92 from
let id = await HMSManager.build(params?.trackSettings || {});

to
let id = "";
if (params != undefined){
  id = await HMSManager.build(params.trackSettings);
}

I've tried developing further and learned that the adjustment I made above does not actually work. I'm new to React Native and 100ms so don't know all the ins and outs. I see now that in HMSSDK.tsx on line 92, the function HMSManager.build() needs to be called and cannot be skipped as that manager is needed to perform other function calls to the SDK. The problem is that any time it is called without parameters, it throws a null error. I don't know anything about HMSTrackSettings to know how to create an object to give to it.

As discussed, these steps are required when building with Expo: https://www.100ms.live/docs/react-native/v2/features/integration#expo-setup
Closing this ticket now.


Calicoctl.exe ipam return error on Windows node

Calling Calicoctl ipam on a Windows node return error.
C:\etc\CalicoWindows> .\calicoctl.exe ipam configure --strictaffinity=true
Error: global strict affinity should not be false for Windows node

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

Calico version
Orchestrator version (e.g. kubernetes, mesos, rkt):
Operating System and version:
Link to your project (optional):

Hi,
If you look a the docs https://docs.projectcalico.org/getting-started/windows-calico/quickstart
there is :
Configure strict affinity for clusters using Calico networking
For Linux control nodes using Calico networking, strict affinity must be set to true. This is required to prevent Linux nodes from borrowing IP addresses from Windows nodes:
calicoctl ipam configure --strictaffinity=true

@song-jiang sounds like this has been fixed since you raised it?

I currently face a similar or same issue. I want to change the affinity setting on my cluster (from a windows machine) and get the following error on various commands

Error: global strict affinity should not be false for Windows node

Also on just showing the current configuration I already get this error:

kubectl calico ipam show --show-configuration --config=calico.cfg.yaml --allow-version-mismatch

On the cluster there is calico 3.20 and I try to use the 3.24.5 client (because I could not find a 3.20 calicoctl windows binary in the GitHub Releases).
Could the client/cluster version mismatch be the reason or is there still a problem open?


Update monitoring documentation.

The one general comment I have is why don't we include information about Satellite in this section? I think an overview of what it is and why it is included with a link to the repo would be helpful.
A smaller comment is that I have been capitalizing Cluster Image(s) and Cluster(s) elsewhere in the docs but I can also clean that up post-merge.


Revert "Small typo fix"

Reverts reactjs/reactjs.org#1317
This wasn’t a typo.

I tweaked the wording.


Fix for issue#8134

This is a PR fix to issue#8134
I've added an environment variable that defaults to True, which will perform the default behavior of a LineCommentParsingState, which is to delete the comment from the query string before submitting the query to the Database. This change now allows anyone using beakerx against a database that utilizes comments for overrides (Derby and/or Splicemachine)
This PR will have no effect on the behavior of the current deployment.
Help from @jramineni

Is there any chance we can have an authorized user check this code?

Looks good, thanks for your contribution Ben!


api implementation for OpenID Connect users

What kind of change does this PR introduce?
This is the api implementation for OpenID Connect users.
const { user, session, error } = await supabase.auth.signIn({
  oidc:{
      id_token: 'your idtoken',
      nonce: 'random value',
      provider: 'google'
  }
})

This pull request solves the following issue.

https://github.com/supabase/gotrue-js/issues/169
https://github.com/supabase/gotrue/issues/341
https://github.com/supabase/gotrue/issues/171
https://github.com/supabase/gotrue/issues/146

This pull request is made possible by the following pull request.

https://github.com/supabase/gotrue/pull/189

What is the current behavior?
none.
What is the new behavior?
Numerous issues will be resolved.
Additional context
https://github.com/supabase/supabase/pull/5181
You should check the OpenID Connect specification for details. https://openid.net/developers/specs/
Sign In With Google
https://developers.google.com/identity/gsi/web/guides/overview
Handle credential responses with JavaScript functions
https://developers.google.com/identity/gsi/web/guides/handle-credential-responses-js-functions
↑ You can find instructions on how to get the token here. (It is included in the response)
Sign In With Google HTML API reference
https://developers.google.com/identity/gsi/web/reference/html-reference
Sign In With Google JavaScript API reference
https://developers.google.com/identity/gsi/web/reference/js-reference
↑ Here is the description of the nonce that @dthyresson was requesting.
This is sample code.

Hi @koba-ninkigumi and thanks much for this PR.
Might you also be able to write up unit tests for a few scenarios?

success
failures

Given this flow :

and the GoTrue rules in https://github.com/supabase/gotrue/blob/8ba49df7c7bbcc87c9d5b211a32cb5aa17db231d/api/token.go#L316

missing required params like "id_token, nonce and provider required
what if the nonce does't match
missing sub claim in id_token
scenario when signups are disabled

This way we can have some tests in place to cover cases developers may encounter when using.
Thanks.

https://github.com/supabase/gotrue-js/pull/207#issuecomment-1013158198

scenario when signups are disabled

Enabling OpenID Connect means that you are accepting a huge group of users from OpenID Connect providers (Google, Facebook, etc.) as already signed up.
That's exactly what "OpenID" means.
The idea of disabling signup on the supabase side is incompatible with OpenID Connect.

https://github.com/supabase/gotrue-js/pull/207#issuecomment-1013158198

missing required params like "id_token, nonce and provider required
what if the nonce does't match
missing sub claim in id_token

If you or I know how to pretend to be an OpenID Connect provider and return id_token, it means that the OpenID Connect specification is broken.
And since we can't get the id_token, we can't write a test.
Please see the following test for reference.
https://github.com/supabase/gotrue-js/blob/master/test/GoTrueClient.test.ts#L182
This is probably the same reason why there are no test cases for oauth providers here.
If you think it is possible to write a test for OpenID Connect, could you please clarify how to do so in more detail?

Anything I can help with to get this merged? Would love to use this PR asap @koba-ninkigumi  @dthyresson

Hi @He1nr1chK thanks for offering to help.
I think that these new functions could use:

unit tests
documentation for how to use them (ie, what one would see and need to know how to use in: https://supabase.com/docs/reference/javascript/auth-signin)
And some examples of how to setup and test in a real world case. What are some services I can use and setup (and how) to know that this method works?

And some examples of how to setup and test in a real world case. What are some services I can use and setup (and how) to know that this method works?

Sign In With Google
https://developers.google.com/identity/gsi/web/guides/overview
Handle credential responses with JavaScript functions
https://developers.google.com/identity/gsi/web/guides/handle-credential-responses-js-functions
↑ You can find instructions on how to get the token here. (It is included in the response)
Sign In With Google HTML API reference
https://developers.google.com/identity/gsi/web/reference/html-reference
Sign In With Google JavaScript API reference
https://developers.google.com/identity/gsi/web/reference/js-reference
↑ Here is the description of the nonce that @dthyresson was requesting.
This is sample code.

unit tests

As I mentioned above, due to the OpenID Connect specification, it should be impossible to get an idtoken that works properly.
So I don't know how to unit test this method.
If someone thinks it is possible, it would be great if that someone could write the unittest of this method.

@dthyresson
I wrote a unittest that expects an error because the idtoken is not valid.

If someone thinks it is possible, it would be great if that someone could write the unittest of this method.

Could you mock the request and return expected results?
This would ensure that the method signature or other logic doesn't accidentally get changed without some test check.
For example, in a PR the cookie is being mocked to return headers as:
export const mockCookieRequest = ({
   event,
   session,
   method = 'POST',
 }: {
   event?: string
   session?: Session | null
   method?: string
 }) => {
   return {
     method,
     headers: { host: 'localhost:9999' },
     body: { event, session },
   }
 }

 export const mockCookieResponse = () => {
   return {
     getHeader: jest.fn(() => undefined),
     setHeader: jest.fn(),
     status: jest.fn(() => {
       return { json: jest.fn(), end: jest.fn() }
     }),
   }
 }

Maybe something similar?

Maybe something similar?

Instead of using a cookie as an example, use oauth2 from gotrue.js as an example.
This is because the OpenID Connect specification is an extension of oauth2.
Currently, none of the tests for signIn() in gotrue.js specify a provider.
A Mock that returns an access token would be helpful.

I don't know of any other way to get a working access token other than getting the official Google private key.

@dthyresson @He1nr1chK
I can't prepare the test that @dthyresson requires. I would like to wait for someone's help.

@dthyresson  I have done some research into the possible tests one can write for OCID and I have to agree with @koba-ninkigumi. It's going to be difficult if not impossible to write a proper test for the function. Is the test absolutely necessary?

hey @koba-ninkigumi @He1nr1chK this is awesome! Thanks for your hard work.

Is the test absolutely necessary

It would be very useful to have some automated tests to make sure we don't accidentally break the logic later on.

I have done some research into the possible tests one can write for OIDC and I have to agree with @koba-ninkigumi. It's going to be difficult if not impossible to write a proper test for the function

Could you expand on what is the difficult bit? Could we mock the request as @dthyresson suggested?
Again, thanks for all your help on this! 🙏

@awalias
OpenID Connect is an authentication. It's a specification for proving "who you are."
Who is the test runner?　It is the test runner.
A normal OpenID Connect provider will try to verify that a human actually accessed the site with a browser.
For example, in the case of Google, they ask for confirmation through biometrics or double authentication.
OpenID Connect providers are tasked with rejecting non-human access, such as test runners.
If a test runner is authenticated by OpenID Connect, even if it means a successful test of supabase goture.
It's just a failure on the part of the OpenID Connect provider.
How do you exploit that hole to illegally obtain an idtoken?
And is it a successful test to get the idtoken?
No, it's just a collapse of the system.

@awalias
In order to connect to supabase with OpenID Connect, you need to get a legitimate idtoken beforehand.
It's impossible to get that idtoken.
If it were possible to write a test to authenticate the idtoken, it could be done in two ways.

Set up a fake OpenID Connect provider in your test and issue idtokens that work correctly there.

You are a futurist from 1000 years in the future who is familiar with quantum computers and can crack the cipher used in OpenID Connect in less than an hour to get a fake idtoken and put all that logic in the test.

@awalias
My suggestion is to release this feature first.
Then, the testing of this feature should be a separate issue.

@awalias
I would also add that if you are setting up a fake OpenID Connect Provider in your testing, you will need to provide the necessary information on an externally accessible https server, per the OpenID Connect specification.
Otherwise, it will be considered a fraudulent idtoken based on the oidc specification.

@awalias
Can't you still create an idtoken in the mock and use it ? You may be wondering.
If the goture backend of supabase considers such an idtoken as a normal idtoken, it means that the goture backend of supabase is broken.
Clarification.
Writing a test that passes an idtoken is not difficult, it is impossible for me.

@awalias
One more thing to add, if you can find a way to create a mock and get a working idtoken, you can have unlimited wealth in your BitCoin wallet.
This is because getting a working OpenID Connect idtoken is the same as getting a legitimate BitCoin, in the sense that it interferes with the chain of authentication of the cryptographic key.

#https://github.com/supabase/gotrue/pull/360
↑In response to this PR, we have added client_id and issuer as parameters to work with any OIDC Provider.
@JO Thanks for your generous support.
@kangmingtay Please provide support from the perspective of an implementor of OIDC for goture backend.

https://github.com/supabase/supabase/pull/5181
↑ Changes have been completed to conform to this PR.

Any updates on when this might get merged?

There was an idea discussed to make this api an option on signUp just like a 3rd-party provider rather than a new method. Is this still an idea? So, the OIDC params are options.
I'd very much like to see documentation in a draft PR on https://github.com/supabase/supabase/blob/master/web/spec/supabase.yml to describe use and setup.

But defer to @kangmingtay and @J0 and @awalias and  @thorwebdev.

I'd very much like to see documentation in a draft PR on https://github.com/supabase/supabase/blob/master/web/spec/supabase.yml to describe use and setup.

@dthyresson Please see,
https://github.com/supabase/supabase/pull/5181/files

Is there anything else delaying this merge? @kangmingtay @awalias

@dthyresson
I have complied with all your requests.
Did you find anything else that needs to be changed?

@dthyresson
My first commit was id_token.
However, after discussion within supabase, @J0 changed the document to IDToken.
I followed suit and changed it from id_token to IDToken.
Then, @dthyresson again insisted on changing it from IDToken to id_token.
I accordingly changed it from id_token to id_token.
I hope it will not ask me to change to IDToken again.

@dthyresson
My first commit was id_token.
However, after discussion within supabase, @J0 changed the document to IDToken.
I hope it will not ask me to change to IDToken again.

@koba-ninkigumi I appreciate your patience and understanding as we have a few reviewers and sorry for the frustration as we go back and forth unfortunately.
Just be sure that we want to make a great and consistent api and experience for the users — and once this feature is released and documented it will be hard to change. So, a little time upfront while I know seems tough, it will pay off in the long term as more and more developers use your feature.
Thanks again and we’ll be able to merge soon.

Thanks for the PR! I am approving this but I hope that we can address any changes/requests

Yes, again many thanks for your work and patience.
Let's get this in, but maybe test out for a few weeks and if any changes need to be made, then can address  -- and then release the docs with those updates.

@koba-ninkigumi @kangmingtay @dthyresson can this function be used yet? I updated my @supabase/supabase-js package to v1.30.3 which exposes this function but when I try to call it, I get TypeError: undefined is not a function

@He1nr1chK I'm already using it with Sign In With Google, and google-one-tap is also working fine.

@koba-ninkigumi that's fantastic news. How are you invoking the function? Like this:
const { user, session, error } = await supabase.auth.signInWithOpenIDConnect({
      id_token: idToken,
      nonce,
      client_id: Platform.select({
            ios: GOOGLE_IOS_CLIENT_ID,
            android: GOOGLE_ANDROID_CLIENT_ID,
      }),
      issuer: 'https://google.com',
      provider: 'google',
});

Please see my first post on this page.
const { user, session, error } = await supabase.auth.signIn({
  oidc:{
      id_token: 'your idtoken',
      nonce: 'random value',
      provider: 'google'
  }
})

@He1nr1chK
If you want to specify Google, you should not set issuer and client_id, but write 'google' in provider and set client_id by logging in to the supabase site.

Hi @koba-ninkigumi, when using the method with Apple as the provider I get the following error: "oidc: invalid configuration, clientID must be provided or SkipClientIDCheck must be set". In the Supabase console my Apple OAuth is correctly configured. Any idea what might be causing this?

Hey @He1nr1chK, could you include your request format? Can you try the following request format below and see if it works for you please?
curl -X "POST" "https://PROJECT_REF.supabase.co/auth/v1/token?grant_type=id_token" \
     -H 'apikey: apikey' \
     -H 'Content-Type: application/json; charset=utf-8' \
     -d '{
              "client_id": "client_id",
              "nonce": "nonce",
              "id_token": "id_token",
              "issuer": "https://appleid.apple.com/"
      }'

Hi @kangmingtay thanks for getting back to me. This seems to have solved the issue but now I get error {"message": "Database error saving new user", "status": 500} even though I have used this Apple ID to sign in before.

@He1nr1chK can you please email us at<EMAIL_ADDRESS>with your project reference so we can help to debug further? thanks!

I think this PR doesn't implement linking
https://github.com/supabase/gotrue/issues/434

Hey @WJimmyCook, yes I did with the following function:
const nonce = Math.random()
    .toString(36)
    .substring(2, 10);

  return Crypto.digestStringAsync(Crypto.CryptoDigestAlgorithm.SHA256, nonce)
    .then(hashedNonce =>
      AppleAuthentication.signInAsync({
        requestedScopes: [
          AppleAuthentication.AppleAuthenticationScope.FULL_NAME,
          AppleAuthentication.AppleAuthenticationScope.EMAIL,
        ],
        nonce: hashedNonce,
      }),
    )
    .then(async appleCredential => {
      const { identityToken } = appleCredential;
      const { user, session, error } = await supabase.auth.signIn({
        oidc: {
          id_token: identityToken,
          nonce,
          client_id: '<YOUR_CLIENT_ID>',
          issuer: 'https://appleid.apple.com',
        },
      });
      if (error) {
        console.log(error);
      }
    })
    .catch(error => {
      console.log(error);
    });

I use expo-crypto to hash the nonce before passing the hashedNonce to Apple as is required.

 Worked like a charm.

@He1nr1chK: I hope you could help me also. I always get the error "invalid nonce" - {"message": "invalid nonce", "status": 400}. My provider is google and i tried both OAuth 2.0 Client IDs (the auto created from Google Service and the self created like the documentation mentioned). Both did not work. I also tried the curl-statement from @kangmingtay but it doesn't work also (same error). I don't know where the error come from (i don't think it's from gotrue-js)
My code (simplified) looks like:
import {
  GoogleSignin,
  statusCodes,
} from '@react-native-google-signin/google-signin'
import {v4 as uuid} from 'uuid'

GoogleSignin.configure()
const {idToken} = await GoogleSignin.signIn()
const nonce = uuid()

const {user, error} = await supabase.auth.signIn({
        oidc: {
          id_token: idToken,
          nonce,
          provider: 'google',
        },
})

@megacherry

Hash the nonce
passed the hashed nonce to the google auth request
pass the unhashed nonce to supabase
Here's the general idea

import * as Google from 'expo-auth-session/providers/google';
import * as Crypto from 'expo-crypto';
const nonce = Math.random()
   .toString(36)
   .substring(2, 10);
...
 const [hashedNonce, setHashedNonce] = useState(null);
  useEffect(() => {
       Crypto.digestStringAsync(Crypto.CryptoDigestAlgorithm.SHA256, nonce).then(hNonce => setHashedNonce(hNonce));
   }, []);
...
   const [request, response, promptAsync] = Google.useIdTokenAuthRequest({
       androidClientId,
       extraParams: { nonce: hashedNonce },
   });
...
const { user, session, error } = await supabase.auth.signIn({
       oidc: {
           id_token: response.authentication.idToken,
           nonce,
           provider: 'google',
       },
   });

@megacherry not sure what non-expo options there are but I'm running a bare react-native project and I ended up adding expo unimodules (or whatever they call it now) so I can use any expo lib in the bare project.

I'm hitting a wall with oidc
	const { user, session, error } = await supabase.auth.signIn({
        oidc:{
            id_token: identityToken,
            nonce: nonce,
            provider: 'apple'
        }
      })

doesn't seem like this got ported to v2 ? am I missing something?
supabase.auth.signIn is not a function

@wweevv-johndpope I think oidc was removed from v2 but there are plans to add it back based on this comment: https://github.com/supabase/gotrue/issues/434#issuecomment-1287755049
I'm sticking with v1 until that get fixed.

Hoping the team add it on v2 too, I've been configuring my project on supabase v2 and didn't know that this feature is not added.   If the feature is already added on v1, I would appreciate supporting it back on v2 even just an option as experimental as there is still a lot of issues related to OIDC implementation.


Spring boot 3.0 fail with jersey and spring cloud (open feign, ect)

@Fyro-Ing commented on Tue Mar 14 2023
When using Spring boot 3.0 with jersey (not mvc) with spring cloud open feign, start failed
org.springframework.beans.factory.BeanDefinitionStoreException: Failed to process import candidates for configuration class [com.fortuneo.api.esign.Application]: class path resource [org/springframework/web/servlet/config/annotation/WebMvcConfigurer.class] cannot be opened because it does not exist
	at org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:524)
	at org.springframework.context.annotation.ConfigurationClassParser$DeferredImportSelectorGroupingHandler.lambda$processGroupImports$1(ConfigurationClassParser.java:726)
	at java.base/java.lang.Iterable.forEach(Iterable.java:75)
	at ...
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:732)
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:434)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:310)
	at org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:150)
	at com.fortuneo.api.esign.Application.main(Application.java:18)
Caused by: java.io.FileNotFoundException: class path resource [org/springframework/web/servlet/config/annotation/WebMvcConfigurer.class] cannot be opened because it does not exist
	at org.springframework.core.io.ClassPathResource.getInputStream(ClassPathResource.java:211)
	at org.springframework.core.type.classreading.SimpleMetadataReader.getClassReader(SimpleMetadataReader.java:54)
	at org.springframework.core.type.classreading.SimpleMetadataReader.<init>(SimpleMetadataReader.java:48)
	at ...

Spring cloud open feign include org.springframework.cloud:spring-cloud-commons with a default config for web mvc
https://github.com/spring-cloud/spring-cloud-commons/blob/8ec45e03b00f3ad96bbc03a86390ed029364bb89/spring-cloud-commons/src/main/java/org/springframework/cloud/commons/security/ResourceServerTokenRelayAutoConfiguration.java#L58
To reproduce : run starter
https://start.spring.io/#!type=gradle-project&language=java&platformVersion=3.0.4&packaging=jar&jvmVersion=17&groupId=com.example&artifactId=demo&name=demo&description=Demo project for Spring Boot&packageName=com.example.demo&dependencies=lombok,cloud-feign,jersey
Workaround : set "spring.cloud.mvc.token-relay.enabled" at false

I went through the same problem when I updated my project to spring boot 3 (PR).
The workaround worked for me, thanks.

@OlgaMaciaszek Any progress on this issue?
I'm not sure it is correct to move the issue here. ResourceServerTokenRelayAutoConfiguration is, looking at the property, mvc oriented and depends on classes from web-mvc (like WebMvcConfigurer) but is only checking for GenericWebApplicationContext (web) through the ConditionalOnWebApplication. For me, it seems better that ResourceServerTokenRelayAutoConfiguration has also a @ConditionalOnClass(WebMvcConfigurer.class) to ensure that there is indeed a web-mvc classpath present.
Now, looking at what is in that ResourceServerTokenRelayAutoConfiguration class..., it doesn't seems to do anything useful. All the code that could do any useful work is commented out :open_mouth: :thinking: :wink:

This is a bug in Commons. Moving it there. Will provide a fix.


How to pass variables to sao

If I'm using sao in a CLI tool like this:
sao({
  template: __dirname,
  targetPath: path.resolve(name)
})

How can I send custom data to sao's context, i.e to use in post hook:
post(ctx) {
  if (ctx.userWantsNpmInstall) {
    ctx.npmInstall()
  }
}

Not clear exactly how this works.
Are these configOptions merged on top or do they entirely replace what is returned by sao.js??

@kristianmandrup yeah merged using Object.assign:
Object.assign(
    {
      flags
    },
	configOptions
)

Ah cool, coz I'd like to supply default answers and skip certain prompts like so many ppl have asked for in these issues...

BTW, working on a very powerful project template generator that I intend to use with sao :)

Well, I'd actually like not just to merge on top but to remove most of the prompts for which I already have answers. How would I do that when hard coded to Object.assign!?
This standard recipe is still not clear to me :P

If only we could supply a custom getConfig or buildConfig function ;)

Came up with this solution:
module.exports = saoConfig => {
  const promptsNotAnswered = Object.keys(prompts).reduce((acc, key) => {
    const prompt = prompts[key]
    if (!saoConfig.knownAnswers[key]) {
      acc[key] = prompt
    }
    return acc
  }, {})
  return {
    // NOTE: answers made via prompts
    // can be used to build data answers if needed
    data(answers) {
      return saoConfig.knownAnswers
    },
    prompts: promptsNotAnswered,
    // ...
}


Is if possible for VCF-Simplify to convert non-dosage vcf to dosage vcf?

Dear developer,
I am trying to acquire the dosage VCF file converted from .gen format. However, qctools and other conversion can only output the non-dosage VCF, which cannot meet my demand of the following investigation. Then I find out that maybe Pysam can do this, but I am not quite familiar with the complex code.
I want to know if this VCF-Simplify can achieve this function?
Many thanks!
Hope for your reply!

Hi @ConnieXuhm
Please share your VCF file (both dosage and non-dosage) so I can tell if it can do what you want it to do.
For a more controlled and custom VCF parsing you may use https://github.com/everestial/vcfparser but this application is still waiting for few more changes and updates.
Let me know if you have any other questions.


Updated FFmpeg version

I have updated the FFmpeg version to the latest Windows build that was released October 7th. Everything works A OK as I tested it before making this PR.

the ffprobe.exe file can be safely removed as it is mostly not used on the standalone version of ffmpeg. That is unless the bot uses that file.


Preserve sorting order of collections

Is your feature request related to a problem? Please describe.
I'm always frustrated when opening my long collection that the sorting order is NOT preserved.
Describe the solution you'd like
When opening a collection the queries could be sorted in different ways. The last set sorting order should be meomorized somehow so when I open the collection again next time it's automatically sorted in this very order.
Describe alternatives you've considered
No alternatives.
Additional context

I second this feature!

number each request in the flow i.e. 1. request a 2. request b etc

@ahmb it will be a little more complicated than that. There is already the sorting option. The concern is about preserving the sorting order after changing it. One way to solve this is to store the sorting information on the collection objects themselves. The concern I have with that is that users of the exported collection may have different sorting preferences from what was selected. This may not be a big issue since the collection can be resorted again.
Alternatively, the sorting order can be stored in the application state and applied globally to all the collections by default.

thanks for the response @imolorhe  but i interpreted this a bit differently. Hear me out here, the main request is to "Preserve it" , you could say "Presist" is one form of it , but what triggered this issue was:
Is your feature request related to a problem? Please describe.
I'm always frustrated when opening my long collection that the sorting order is NOT preserved.
I was able to recreate this , but for me it happens whenever I save or modify a request in that collection. In my screenshot 1,2,3 were in order,  but when i saved updates to the second request, it then showed up at the bottom :

Im assuming this is because of a default sort on last updated datetime. So from a UX perspective i think a standard is to first sort on name alphabetically in an ascending fashion. I think this can be a quick fix and will alleviate this issue for now.
Secondly, yes you are right about adding additional sorting persistence  , incase the order is modified by the user to something custom i.e. not alphabetical. Then in that case as part of the collection metadata , along with each requests name etc we can add one more property for index. That can be the updated as the user drags + drops requests in the collection to change the order. And the user importing the collection should have the same sort coming in, with the difference that theres standard sorting options like Name ascending/descending to override the index in the UI. But this would be a bigger update.

@ahmb I tried to reproduce that but can't seem to do so (unless my recent changes also fixes that):

I created a new collection
Added a query starting with A
Added a query starting with B
Changed the sorting order to Z-A
Added a query starting with C
The C query got placed at the top of the list as expected

Is this different from what you're experiencing?

oh i see sorry my bad! i totally missed the sort option! please disregard the short term fix, @imolorhe  thank you for looking into this!


Add ihm_localization_density_files to nup84 example

Would be good to include references to localization map MRC files in the nup84 example using the new ihm_localization_density_files table.  I think the MRC files in the DOI archive may not align with the sphere models.  I have made new MRC localization files from the ensemble models using Chimera.  We could include those in a new DOI archive in order to make nup84 a better example of the IHM format.

Would also like the localization density map table for the mediator and exosome examples.  It looks like the mediator DOI archive has those MRC files.  Exosome has some MRC files but not one for each asym_id.

Would be good to include references to localization map MRC files in the nup84 example

Tom, if you can provide me with your new MRC files I can modify the Nup84 mmCIF output to point to them. I don't think it's worth trying to point to the .dx files in GitHub for now since they're not aligned anyway.

Here are the nup84 localization density maps I made that align with the IHM nup84 example sphere models.
http://www.cgl.ucsf.edu/home/goddard/temp/nup84_localization.zip

Tom

On Mar 27, 2017, at 1:08 PM, Ben Webb<EMAIL_ADDRESS>wrote:
Would be good to include references to localization map MRC files in the nup84 example
Tom, if you can provide me with your new MRC files I can modify the Nup84 mmCIF output to point to them. I don't think it's worth trying to point to the .dx files in GitHub for now since they're not aligned anyway.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/ihmwg/IHM-dictionary/issues/17#issuecomment-289570213, or mute the thread https://github.com/notifications/unsubscribe-auth/AHyRjSSmCB7133y-izBNb8qFApjKyilCks5rqBdGgaJpZM4LhVF8.