Problem when copying link

Hi,
On windows, sending a link to a file example:
[ Document](file://///<IP_ADDRESS>/path/to/file.pdf)
Create a link that do nothing if clicked and can't be copyed to clipboard.
is this normal?

Excuse me, could you describe that in detail (step by step)? I couldn't understand the operation which you did.

if a post this string:
[ Document](file://///<IP_ADDRESS>/path/to/file.pdf)
On the web i can click on the generated link but don't open the file (security reason?), but i can copy the adress and past in in file manager in order to open the file.
On the desktop app i can only copy the text of the message, so if i make a copy/past of that link, the result will be " Document".
Sorry for my bad english :(

Thank you for your description. Maybe need to implement 'copy' for the case.

Would anyone from the community be open to helping with a PR to address this?

I'll try to get electron-context-menu to work, to fix this issue :construction_worker:

Thanks @jnugh! Highly appreciate it,
as per our discussion in Desktopp App channel, we'll move this issue from v1.3, but would love to have this issue for v1.4

@jnugh is it resolved?

Not yet, I hope to get to it this week

@jnugh electron-context-menu is pretty easy to use. I'm using it here. Let me know if you need any help.

The problem here, is that the right click event is caught by react.js. Just embedding the context menu library would be too easy I guess ;)

haha, yes definitely.

This linked fix depends on https://github.com/sindresorhus/electron-context-menu/pull/15 I will open a PR after this one got meregd

Perfect, thanks @jnugh!
Looks like the PR was merged, would you have a PR available to submit in the desktop repo?
This would be a huge improvement for user experience, really looking forward to it :)


Review of the Function directory

Review of the Function directory
Close #1157

This is a review PR of the Function directory. Addressing all of the tasks in #1157


Crash when trying to get exif image data

Describe the bug
When trying to apply the getexif() method to HEIF images made with my phone (stock Xiaomi), I get the error described below. As an example I've attached one of the problematic images: image.zip (sorry for using the zip format, uploading .heic files is not allowed).
Steps/Code to Reproduce
from PIL.Image import Exif, open as image_open
from pillow_heif import register_heif_opener

register_heif_opener()

with image_open("image.heic") as image:
    exif: Exif = image.getexif()
    print("Exif presents: {}".format(exif is not None))

Expected Results
Exif presents: True | Exif presents: False
Actual Results
Test machine 1:
Traceback (most recent call last):
  File "path-to-script.py", line 7, in <module>
    exif: Exif = image.getexif()
                 ^^^^^^^^^^^^^^^
  File "path-to-site-packages\PIL\Image.py", line 1455, in getexif
    self._exif.load(exif_info)
  File "path-to-site-packages\PIL\Image.py", line 3719, in load
    self._info = TiffImagePlugin.ImageFileDirectory_v2(self.head)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "path-to-site-packages\PIL\TiffImagePlugin.py", line 507, in __init__
    raise SyntaxError(msg)
SyntaxError: not a TIFF file (header b'\xff\xe18&Exif' not valid)

Test machine 2:
Traceback (most recent call last):
  File "path-to-script.py", line 7, in <module>
    exif: Exif = image.getexif()
  File "/usr/lib/python3/dist-packages/PIL/Image.py", line 1275, in getexif
    self._exif.load(self.info.get("exif"))
  File "/usr/lib/python3/dist-packages/PIL/Image.py", line 3237, in load
    self._info = TiffImagePlugin.ImageFileDirectory_v1(self.head)
  File "/usr/lib/python3/dist-packages/PIL/TiffImagePlugin.py", line 900, in __init__
    super().__init__(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/PIL/TiffImagePlugin.py", line 466, in __init__
    raise SyntaxError("not a TIFF file (header %r not valid)" % ifh)
SyntaxError: not a TIFF file (header b'if\x00\x00II*\x00' not valid)

Versions
Test machine 1:
3.11.2 (tags/v3.11.2:878ead1, Feb  7 2023, 16:38:35) [MSC v.1934 64 bit (AMD64)]
Windows-10-10.0.19045-SP0
0.10.1
{'libheif': '1.15.2', 'HEIF': 'x265 HEVC encoder (3.4+31-6722fce1f)', 'AVIF': 'AOMedia Project AV1 Encoder v3.6.0'}

Test machine 1 additional information:
UTF-8 enabled for the whole system
Amernime Zone AMD 3rd party drivers
Pillow 9.5.0

Test machine 2:
3.8.10 (default, Mar 13 2023, 10:26:41)
[GCC 9.4.0]
Linux-5.15.0-71-generic-x86_64-with-glibc2.29
0.10.1
{'libheif': '1.15.2', 'HEIF': 'x265 HEVC encoder (3.5+1-f0c1022b6)', 'AVIF': 'AOMedia Project AV1 Encoder v3.5.0'}

Test machine 2 additional information:
VirtualBox VM Xubuntu 20.04 (clean install)
Pillow 7.0.0

Can I take this image to dataset for tests, e.g. what copyright does it have?

Of course, use it as you want. It is just a simple photo of nothing personal or copyright protected made by me with a camera application applying no additional copyright restrictions.

As Pillow do not have all tag id's for this image, you can use: print(TAGS.get(k, "XXX"), ":", v) to display it.
    exif = im.getexif()
    if exif:
        exif = exif._get_merged_dict()  # noqa
    for k, v in exif.items():
        if isinstance(v, bytes) and len(v) > 8:
            print(f"{TAGS[k]} : size {len(v)} bytes")
        else:
            print(TAGS.get(k, "XXX"), ":", v)

Can't promise that release will be in this week with fix, but in two weeks I will try to publish it, when will have what to fix more.

Thank you very much for the tip and for the fix! I will try this asap. Patiently waiting for the new release!

The error was bigger than I thought at first.
There was also incorrect handling of EXIF data when EXIF did not start with bExif\x00\x00.
So, the new release fixes two EXIF bugs:

Correct handling when EXIF does not start with bExif\x00\x00.
Adding support for some data before the actual EXIF data (your case of Xiaomi storing 4 bytes with something before the actual EXIF)

It's great to see, that the bug was fixed. Thank you very much for your work! I guess, we can now close this issue?...


Add OSG 23 images (SOFTWARE-5673)

I left all the images that directly referenced EL8 as is since I didn't want to force them back to EL7 for OSG 3.6 images

Things are looking pretty solid except for ospool-display, gracc-apel, and vo-frontend:
@djw8605 OSG 23 EL9 builds for gracc-apel are failing because of https://github.com/opensciencegrid/images/actions/runs/6267522494/job/17020771998?pr=149#step:2:911. Any chance we can get EL9 argo RPMs?
@rynge fifemon is blowing up on the install for OSG 3.6 EL7. Any ideas on that? Otherwise for EL9 there's this really strange conflict between curl and curl-minimal that I don't quite understand.
vo-frontend looks like it's failing because of missing python3-scitokens. Derek said that this should have gotten into EPEL9 last night so hopefully this one just goes away

So exciting! Are we just leaving BASE_OSG_SERIES=3.6 as default for now?
We are in the process of removing fifemon - I'm just waiting for the last final ok from ToddT on this. I would not invest any time on that image.

@djw8605 OSG 23 EL9 builds for gracc-apel are failing because of https://github.com/opensciencegrid/images/actions/runs/6267522494/job/17020771998?pr=149#step:2:911. Any chance we can get EL9 argo RPMs?

EL8 support is in progress for apel-ssm: https://github.com/apel/ssm/issues/123

So exciting! Are we just leaving BASE_OSG_SERIES=3.6 as default for now?

These are really just for dev convenience so that you don't have to pass args when building locally. The GHA drives all the images that are actually produced (3.6, el7 and 23, el9 by default)

EL8 support is in progress for apel-ssm: https://github.com/apel/ssm/issues/123

What are the chances for EL9 support, to? 😄

@mwestphall this is ready for review. The ospool-display failures are expected (see discussion above) and shouldn't affect pushes of other images


RuntimeError: Attribute hass is None

Buch of  RuntimeError: Attribute hass is None is appearing in log
2020-11-23 14:17:26 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/loxone/sensor.py", line 212, in event_handler
self.schedule_update_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 422, in schedule_update_ha_state
assert self.hass is not None
AssertionError
2020-11-23 14:17:26 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/loxone/light.py", line 399, in event_handler
self.async_schedule_update_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 441, in async_schedule_update_ha_state
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 289, in async_write_ha_state
raise RuntimeError(f"Attribute hass is None for {self}")
RuntimeError: Attribute hass is None for <Entity Hlavní tlačítko: off>

What Version of HA do you have installed? I can not reproduce this error?

I have latest version of the HA 0.118.2
System Health
Home Assistant Core Integration
version: 0.118.2
installation_type: Home Assistant OS
dev: false
hassio: true
docker: true
virtualenv: false
python_version: 3.8.6
os_name: Linux
os_version: 5.4.77
arch: x86_64
timezone: Europe/Prague
Hass.io
host_os: HassOS 4.17
update_channel: stable
supervisor_version: 2020.11.0
docker_version: 19.03.12
healthy: true
supported: true
board: intel-nuc
supervisor_api: ok
version_api: ok

I only add, the everything seems to be running as expected, only buch of those errors in the log...

Looks like I have found when it happens.
Looks like the errors are occurring for entities which I have disabled in the GUI, so they do not appear in HA.. And looks like when PyLoxone tries to update their status, then error is fired (as those are not active in HA).
I will do additional checks and will confirm.

Now I can confirm the problem is related to the disabled entities.
For example I have light controllers with moods. The PyLoxone creates entities for each mood as well as the Central switch for that light controller. In my setup I do not need the central switch so I disabled it in the HA so it does not appears in the lists.
Once the entity is disabled, PyLoxone it causes the above errors to appear when PyLoxone states are refreshed.
After re-enabling and restarted HA the errors disappeared. So as mentioned above some problem with refresh of entities when they are disabled in HA.

Ok thanks for your time you spent to find out whats wrong. But I can not reproduce it on my system.
I found a similar thread:
https://github.com/StyraHem/ShellyForHASS/issues/341
My system is very small and my load is not so high.
Sorry but I will keep in mind this problem. Maybe I can force this error somehow.


map not working if used in the definition of a variable?

See https://numbas.mathcentre.ac.uk/question/7022/test-map/
The variable a defined as map(k,k,0..3) gives an error, stack size exceeded, whereas the  function test() with the same definition  in Functions & rulesets works.

Sorry, broke this recently and fixed it but forgot to fix the version in the editor. Will fix it tomorrow morning.
On 22 Jan 2015 17:10, Bill Foster<EMAIL_ADDRESS>wrote:
See https://numbas.mathcentre.ac.uk/question/7022/test-map/
The variable a defined as map(k,k,0..3) gives an error, stack size exceeded, whereas the function test() with the same definition in Functions & rulesets works.
—
Reply to this email directly or view it on GitHubhttps://github.com/numbas/Numbas/issues/363.

Now fixed.


Mismatched number of arguments in call to EditorExportPlatformPC::export_project

As seen in the current master branch, on gcc 4.9.2:
g++ -o platform/windows/export/export.x11.opt.tools.64.o -c -O2 -ffast-math -DDEBUG_ENABLED -DFREETYPE_ENABLED -DOPENGL_ENABLED -DGLEW_ENABLED -DALSA_ENABLED -DPULSEAUDIO_ENABLED -DX11_ENABLED -DUNIX_ENABLED -DGLES2_ENABLED -DGLES_OVER_GL -DMUSEPACK_ENABLED -DSQUISH_ENABLED -DVORBIS_ENABLED -DOPUS_ENABLED -DTHEORA_ENABLED -DPNG_ENABLED -DDDS_ENABLED -DPVR_ENABLED -DJPG_ENABLED -DWEBP_ENABLED -DSPEEX_ENABLED -DTOOLS_ENABLED -DGDSCRIPT_ENABLED -DMINIZIP_ENABLED -DXML_ENABLED -DETC1_ENABLED -D_REENTRANT -Icore -Icore/math -Itools -Idrivers -I. -Iplatform/x11 -I/usr/include/freetype2 -I/usr/include/libpng16 -Itools/vorbis -Idrivers/opus/silk/float -Idrivers/opus -Idrivers/opus/celt -Idrivers/opus/silk -Idrivers/opus/silk/float platform/windows/export/export.cpp
platform/windows/export/export.cpp: In member function 'Error EditorExportPlatformWindows::export_project(const String&, bool, bool, bool)':
platform/windows/export/export.cpp:202:92: error: no matching function for call to 'EditorExportPlatformWindows::export_project(const String&, bool&, bool&, bool&)'
  Error err = EditorExportPlatformPC::export_project(p_path, p_debug, p_dumb, p_remote_debug);
                                                                                ^
platform/windows/export/export.cpp:202:92: note: candidate is:
In file included from platform/windows/export/export.h:1:0,
                 from platform/windows/export/export.cpp:30:
./tools/editor/editor_import_export.h:200:16: note: virtual Error EditorExportPlatformPC::export_project(const String&, bool, int)
  virtual Error export_project(const String& p_path, bool p_debug, int p_flags=0);
                ^
./tools/editor/editor_import_export.h:200:16: note:   candidate expects 3 arguments, 4 provided

Confirmed by others on IRC.

According to gitk it seems to be a regression from #2518, though GH does not show the relevant changes in the diff as the commit is just too huge due to the import of the pe_bliss external library.

Ping @masoudbh3.

Fixed by #2820.


"Seek and Destroy":Test cases remain in Red even though the output looks correct for each test case

Challenge Seek and Destroy has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
function destroyer(arr) {
  var myArr;
  myArr = arr.filter(checkValue,arguments[1]);
  myArr = myArr.filter(checkValue,arguments[2]);
  return myArr;
}
function checkValue(value){
  return value !== this;
}

destroyer([1, 2, 3, 5, 1, 2, 3], 2, 3);

Basically you're doing something in your code that shouldn't work but some execution contexts will let you get away with (in this case the editor is letting you get away with it but the test runner isn't). You're passing a primitive value (arguments[1], which is 2) as the this context for the checkValue callback. The issue is that the this context should always be a context object, not a primitive. In the test framework it turns that primitive into and object with a form like Number {[[PrimitiveValue]]: 2} which causes the test to fail. You'll have to find a different way to pass that value in that doesn't involved pushing a primitive value as the this context. Good luck and happy coding!


upgrade go 1.20 -> 1.21.2

(sorry, the PR includes the two previous commits too, which was not intended; please, only consider the single relevant commit)

this one is too messy. will close it and push something directly to main with updated dependencies.


OneTable.dev Cannot be reached

Maybe its just me - but i think the website is down.

Yeap, I can't access onetable.dev either. Nevertheless https://xtable.apache.org/ is up and running.

Cc @kywe665 , in case he wants to implement a redirect from onetable.dev to xtable.apache.org.

@ForeverAngry close issue?


Translation/billing

Fixes #280.
Changes proposed in this pull request:

Translations for all Billing Routes

Localisation of the complete billing routes including invoicing and pricing. I have tried my best to organise what I think to be generic translations and specific translations. A billing localisation object exists to add any text that is very specific to that module. Happy to amend any discussions about the current grouping I have done in this PR.
Note: pull requests without proper descriptions may simply be closed without further discussion. We appreciate your contributions, but need to know what you are offering in clearly described format. Thanks! (you can delete this text)
cc @HospitalRun/core-maintainers

Need to translate pricing route as well. to complete issue, but would be happy to merge this first after the comment is addressed

@mellisdesigns @jkleinsc we can close this i incorporated changes in https://github.com/HospitalRun/hospitalrun-frontend/pull/515

ok thanks @billybonks.  I'll close this.


depends: broken.

Running aur depends always result in:
Global symbol "$pkgdeps" requires explicit package name (did you forget to declare "my $pkgdeps"?) at /usr/share/perl5/vendor_perl/AUR/Depends.pm line 245.
Global symbol "$pkgdeps" requires explicit package name (did you forget to declare "my $pkgdeps"?) at /usr/share/perl5/vendor_perl/AUR/Depends.pm line 247.
Global symbol "$pkgmap" requires explicit package name (did you forget to declare "my $pkgmap"?) at /usr/share/perl5/vendor_perl/AUR/Depends.pm line 259.
Global symbol "$pkgmap" requires explicit package name (did you forget to declare "my $pkgmap"?) at /usr/share/perl5/vendor_perl/AUR/Depends.pm line 260.
Global symbol "%dag" requires explicit package name (did you forget to declare "my %dag"?) at /usr/share/perl5/vendor_perl/AUR/Depends.pm line 373.
Global symbol "$pkgmap" requires explicit package name (did you forget to declare "my $pkgmap"?) at /usr/share/perl5/vendor_perl/AUR/Depends.pm line 377.
Compilation failed in require at /usr/lib/aurutils/aur-depends line 9.
BEGIN failed--compilation aborted at /usr/lib/aurutils/aur-depends line 9.

Happens on version 19.6 but not on 19.5.

Same issue.

Sorry about that, ca8c02dd780539cda42ef1fa1fdaab136ed8382e refactored some code but wasn't properly tested. Reverted in 19.7


Terms only in Hebrew

I really like that you explain everything in Hebrew, but I think there's a problem. If they'll wan't to google search it, or understand some article written in English they won't be able too.
I strongly advise to add the English terms in parenthesis, so you'll teach Hebrew but won't be blocking them from the outside word.

I couldn't agree more. We have to find a way to put it there.
The only possible problem I can think of is adding cognitive load while reading the notebooks.
We should try to be sure we're not breaking the flow of the reading while doing it.

We talked about adding a "summary" page for each week, how about adding the matching term there?

I liked Ido's idea, also we can try to just mention this in the class for now, until we could find a better way.

Great. You can start by adding the jargon to the Summary notebooks.
Use the "Glossary" section in the current notebooks as an example.


Fix/bugs

Merge https://github.com/RTradeLtd/grpc/pull/8
Merge https://github.com/RTradeLtd/rtfs/pull/9
Update dependencies before merging this into v2

:construction_worker: Purpose
Couple of bugs introduced by the move to krab. Moving to krab also presented the need to slightly re-work how we handle IPNS, and instead interface with the publishing system directly, as opposed to using the API.
:rocket: Changes
Ignore golint in rtns
:warning: Breaking Changes
TODO

Codecov Report

Merging #259 into V2 will increase coverage by 0.71%.
The diff coverage is 26.4%.

@@           Coverage Diff            @@
##              V2    #259      +/-   ##
========================================
+ Coverage   14.5%   15.2%   +0.71%
========================================
  Files         34      35       +1
  Lines       3484    3527      +43
========================================
+ Hits         505     536      +31
- Misses      2897    2904       +7
- Partials      82      87       +5

Impacted Files
Coverage Δ

api/routes_utils.go
0% <0%> (ø)
:arrow_up:

queue/ipfs.go
0% <0%> (ø)
:arrow_up:

api/routes_account.go
0% <0%> (ø)
:arrow_up:

queue/ipns.go
0% <0%> (ø)
:arrow_up:

api/api.go
77.26% <42.86%> (+1.41%)
:arrow_up:

rtns/host.go
75% <75%> (ø)

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 502a549...e4ccfd2. Read the comment docs.


Commit comments should not be imported

There are lots of redundant automatic comments which were posted on trac whenever a commit mentions a ticket number. These should instead be converted into proper links from the commit to the ticket and the comments removed.
For example:
https://gitlab.staging.haskell.org/ghc/ghc/issues/13545#note_111375
I wrote some code previously to identify which commits these were:
https://github.com/danpalmer/trac-to-phabricator/blob/e9071c8b49a33c521bc891d531c700c6206c1461/src/Trac.hs#L285
As a result, many useless user accounts are created.
https://gitlab.staging.haskell.org/ghc/ghc/project_members?utf8=✓&search=pickering

OK, so simply skipping commit comments entirely should do the trick, no?

You have to be careful as there might be comment references which point to commit comments.
Your change will also still post a comment but it will be empty.. and a bad account will be created still for the email author.

See my inline comment - no, it shouldn't create a comment, unless the commit additionally leads to a metadata change that's reflected in the "trac metadata" table.

OK, so it turns out we actually do need to generate links to commits, because people did in fact do this in Trac. I think the way to do this would be to extend the comment cache to hold either a note ID or a commit hash, and then in the link renderer, render an appropriate link.


Include dynamic badges for colab notebook

Hi,
I noticed that some people were creating issues related to colab notebook not working, so I came up with the idea of creating badges with dynamic messages with notebook status to inform users about a problem without the need of creating a PR to update the badges or to include a message. Also I include the colab notebook badge from develop, this way users can access to early colab changes. The way I'm doing this is through github gists, currently I set it up with my account, but probably one of code mantainers should fork it, and modify the urls used in the readme to theirs, so they can have the control over the messages.
This is my private gist with the badges included in this PR https://gist.github.com/artmen1516/472402c8ae9265c01859544f3d100111
A more detailed information about how I made this at the end of gist Readme.
Here you can see the changes in my fork:
https://github.com/artmen1516/stable-diffusion/tree/patch-1#google-colab-
Please let me know what you think about this.

This is marked as draft and there has been no activity in 20 days. I'm closing the PR for now. Please let me know if I should reopen it.


[all nets] Processor crashes regularly

Did not find a pattern yet, but seems to happen on all nets. If we compare two stacks of the same net, both have this issue but not always at the same block.
Mainnet: dashboard.grid.tf
{"level":2,"time":1723610115263,"ns":"sqd:processor","msg":"13789842 / 13789842, rate: 0 blocks/sec, mapping: 8 blocks/sec, 83 items/sec, ingest: 47 blocks/sec, eta: 0s"}
{"level":2,"time":1723610125306,"ns":"sqd:processor","msg":"13789843 / 13789843, rate: 0 blocks/sec, mapping: 8 blocks/sec, 91 items/sec, ingest: 46 blocks/sec, eta: 0s"}
{"level":2,"time":1723610130999,"ns":"sqd:processor","msg":"13789844 / 13789844, rate: 0 blocks/sec, mapping: 4 blocks/sec, 55 items/sec, ingest: 45 blocks/sec, eta: 0s"}
{"level":2,"time":1723610139527,"ns":"sqd:processor","msg":"13789845 / 13789845, rate: 0 blocks/sec, mapping: 1 blocks/sec, 25 items/sec, ingest: 46 blocks/sec, eta: 0s"}
{"level":5,"time":1723610164513,"ns":"sqd:processor","err":{"query":"INSERT INTO \"node_contract\"(\"id\", \"grid_version\", \"contract_id\", \"twin_id\", \"node_id\", \"deployment_data\", \"deployment_hash\", \"number_of_public_i_ps\", \"state\", \"created_at\", \"solution_provider_id\", \"resources_used_id\") VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, DEFAULT) ON CONFLICT ( \"id\" ) DO UPDATE SET \"id\" = EXCLUDED.\"id\", \"grid_version\" = EXCLUDED.\"grid_version\", \"contract_id\" = EXCLUDED.\"contract_id\", \"twin_id\" = EXCLUDED.\"twin_id\", \"node_id\" = EXCLUDED.\"node_id\", \"deployment_data\" = EXCLUDED.\"deployment_data\", \"deployment_hash\" = EXCLUDED.\"deployment_hash\", \"number_of_public_i_ps\" = EXCLUDED.\"number_of_public_i_ps\", \"state\" = EXCLUDED.\"state\", \"created_at\" = EXCLUDED.\"created_at\", \"solution_provider_id\" = EXCLUDED.\"solution_provider_id\"","parameters":["0013789691-000713-fab74",4,"611406",10972,888,"{\"version\":3,\"type\":\"network\",\"name\":\"example_c124_network\",\"projectName\":\"vm/group_c\"}","0e549bca93f361471fcd7a22595fc3a2",0,"Deleted","1723609194",0],"driverError":{"length":221,"name":"error","severity":"ERROR","code":"P0001","where":"PL/pgSQL function reflect_node_contract_changes() line 27 at RAISE","file":"pl_exec.c","line":"3909","routine":"exec_stmt_raise","stack":"error: failed reflecting node_contract updates could not serialize access due to concurrent update\n    at /squid/node_modules/pg/lib/client.js:526:17\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async PostgresQueryRunner.query (/squid/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:184:25)\n    at async InsertQueryBuilder.execute (/squid/node_modules/typeorm/query-builder/InsertQueryBuilder.js:106:33)\n    at async Store.upsert (/squid/node_modules/@subsquid/typeorm-store/lib/store.js:34:13)\n    at async nodeContractCanceled (/squid/lib/mappings/contracts.js:239:5)\n    at async /squid/lib/processor.js:138:13\n    at async TypeormDatabase.runTransaction (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:110:13)\n    at async TypeormDatabase.transact (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:64:24)\n    at async Runner.process (/squid/node_modules/@subsquid/substrate-processor/lib/processor/runner.js:117:17)"},"length":221,"severity":"ERROR","code":"P0001","where":"PL/pgSQL function reflect_node_contract_changes() line 27 at RAISE","file":"pl_exec.c","line":"3909","routine":"exec_stmt_raise","stack":"QueryFailedError: failed reflecting node_contract updates could not serialize access due to concurrent update\n    at PostgresQueryRunner.query (/squid/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:219:19)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async InsertQueryBuilder.execute (/squid/node_modules/typeorm/query-builder/InsertQueryBuilder.js:106:33)\n    at async Store.upsert (/squid/node_modules/@subsquid/typeorm-store/lib/store.js:34:13)\n    at async nodeContractCanceled (/squid/lib/mappings/contracts.js:239:5)\n    at async /squid/lib/processor.js:138:13\n    at async TypeormDatabase.runTransaction (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:110:13)\n    at async TypeormDatabase.transact (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:64:24)\n    at async Runner.process (/squid/node_modules/@subsquid/substrate-processor/lib/processor/runner.js:117:17)"}}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Mainnet: dashboard.be.grid.tf
{"level":2,"time":1723264489440,"ns":"sqd:processor","msg":"13732237 / 13732237, rate: 0 blocks/sec, mapping: 2 blocks/sec, 29 items/sec, ingest: 39 blocks/sec, eta: 0s"}
{"level":2,"time":1723264499728,"ns":"sqd:processor","msg":"13732238 / 13732239, rate: 0 blocks/sec, mapping: 1 blocks/sec, 17 items/sec, ingest: 37 blocks/sec, eta: 6s"}
{"level":2,"time":1723264583919,"ns":"sqd:processor","msg":"13732239 / 13732241, rate: 0 blocks/sec, mapping: 0 blocks/sec, 10 items/sec, ingest: 23 blocks/sec, eta: 15s"}
{"level":5,"time":1723264584478,"ns":"sqd:processor","err":{"query":"INSERT INTO \"node_contract\"(\"id\", \"grid_version\", \"contract_id\", \"twin_id\", \"node_id\", \"deployment_data\", \"deployment_hash\", \"number_of_public_i_ps\", \"state\", \"created_at\", \"solution_provider_id\", \"resources_used_id\") VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, DEFAULT) ON CONFLICT ( \"id\" ) DO UPDATE SET \"id\" = EXCLUDED.\"id\", \"grid_version\" = EXCLUDED.\"grid_version\", \"contract_id\" = EXCLUDED.\"contract_id\", \"twin_id\" = EXCLUDED.\"twin_id\", \"node_id\" = EXCLUDED.\"node_id\", \"deployment_data\" = EXCLUDED.\"deployment_data\", \"deployment_hash\" = EXCLUDED.\"deployment_hash\", \"number_of_public_i_ps\" = EXCLUDED.\"number_of_public_i_ps\", \"state\" = EXCLUDED.\"state\", \"created_at\" = EXCLUDED.\"created_at\", \"solution_provider_id\" = EXCLUDED.\"solution_provider_id\"","parameters":["0013732108-000852-dfc53",4,"606172",10972,2089,"{\"version\":3,\"type\":\"network\",\"name\":\"example_c92_network\",\"projectName\":\"vm/group_c\"}","69626baa73d293ad16bda1ba677b9e6c",0,"Deleted","1723263696",0],"driverError":{"length":221,"name":"error","severity":"ERROR","code":"P0001","where":"PL/pgSQL function reflect_node_contract_changes() line 27 at RAISE","file":"pl_exec.c","line":"3909","routine":"exec_stmt_raise","stack":"error: failed reflecting node_contract updates could not serialize access due to concurrent update\n    at /squid/node_modules/pg/lib/client.js:526:17\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async PostgresQueryRunner.query (/squid/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:184:25)\n    at async InsertQueryBuilder.execute (/squid/node_modules/typeorm/query-builder/InsertQueryBuilder.js:106:33)\n    at async Store.upsert (/squid/node_modules/@subsquid/typeorm-store/lib/store.js:34:13)\n    at async nodeContractCanceled (/squid/lib/mappings/contracts.js:239:5)\n    at async /squid/lib/processor.js:138:13\n    at async TypeormDatabase.runTransaction (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:110:13)\n    at async TypeormDatabase.transact (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:64:24)\n    at async Runner.process (/squid/node_modules/@subsquid/substrate-processor/lib/processor/runner.js:117:17)"},"length":221,"severity":"ERROR","code":"P0001","where":"PL/pgSQL function reflect_node_contract_changes() line 27 at RAISE","file":"pl_exec.c","line":"3909","routine":"exec_stmt_raise","stack":"QueryFailedError: failed reflecting node_contract updates could not serialize access due to concurrent update\n    at PostgresQueryRunner.query (/squid/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:219:19)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async InsertQueryBuilder.execute (/squid/node_modules/typeorm/query-builder/InsertQueryBuilder.js:106:33)\n    at async Store.upsert (/squid/node_modules/@subsquid/typeorm-store/lib/store.js:34:13)\n    at async nodeContractCanceled (/squid/lib/mappings/contracts.js:239:5)\n    at async /squid/lib/processor.js:138:13\n    at async TypeormDatabase.runTransaction (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:110:13)\n    at async TypeormDatabase.transact (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:64:24)\n    at async Runner.process (/squid/node_modules/@subsquid/substrate-processor/lib/processor/runner.js:117:17)"}}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Testnet: dashboard.test.grid.tf
{"level":2,"time":1724728590910,"ns":"sqd:processor","msg":"14961403 / 14961403, rate: 0 blocks/sec, mapping: 54 blocks/sec, 54 items/sec, ingest: 61 blocks/sec, eta: 0s"}
{"level":2,"time":1724728595947,"ns":"sqd:processor","msg":"14961404 / 14961404, rate: 0 blocks/sec, mapping: 46 blocks/sec, 55 items/sec, ingest: 63 blocks/sec, eta: 0s"}
{"level":2,"time":1724728600973,"ns":"sqd:processor","msg":"14961405 / 14961405, rate: 0 blocks/sec, mapping: 39 blocks/sec, 63 items/sec, ingest: 62 blocks/sec, eta: 0s"}
{"level":5,"time":1724728606001,"ns":"sqd:processor","err":{"query":"INSERT INTO \"node_contract\"(\"id\", \"grid_version\", \"contract_id\", \"twin_id\", \"node_id\", \"deployment_data\", \"deployment_hash\", \"number_of_public_i_ps\", \"state\", \"created_at\", \"solution_provider_id\", \"resources_used_id\") VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, DEFAULT) ON CONFLICT ( \"id\" ) DO UPDATE SET \"id\" = EXCLUDED.\"id\", \"grid_version\" = EXCLUDED.\"grid_version\", \"contract_id\" = EXCLUDED.\"contract_id\", \"twin_id\" = EXCLUDED.\"twin_id\", \"node_id\" = EXCLUDED.\"node_id\", \"deployment_data\" = EXCLUDED.\"deployment_data\", \"deployment_hash\" = EXCLUDED.\"deployment_hash\", \"number_of_public_i_ps\" = EXCLUDED.\"number_of_public_i_ps\", \"state\" = EXCLUDED.\"state\", \"created_at\" = EXCLUDED.\"created_at\", \"solution_provider_id\" = EXCLUDED.\"solution_provider_id\"","parameters":["0014961401-000008-6cf88",4,"49058",1149,12,"{\"version\":3,\"type\":\"network\",\"name\":\"net_4c7va2z4pg\",\"projectName\":\"Network\"}","7fbe918104c584d5e90710eb3c21b841",0,"Deleted","1724728560",0],"driverError":{"length":221,"name":"error","severity":"ERROR","code":"P0001","where":"PL/pgSQL function reflect_node_contract_changes() line 27 at RAISE","file":"pl_exec.c","line":"3909","routine":"exec_stmt_raise","stack":"error: failed reflecting node_contract updates could not serialize access due to concurrent update\n    at /squid/node_modules/pg/lib/client.js:526:17\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async PostgresQueryRunner.query (/squid/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:184:25)\n    at async InsertQueryBuilder.execute (/squid/node_modules/typeorm/query-builder/InsertQueryBuilder.js:106:33)\n    at async Store.upsert (/squid/node_modules/@subsquid/typeorm-store/lib/store.js:34:13)\n    at async nodeContractCanceled (/squid/lib/mappings/contracts.js:239:5)\n    at async /squid/lib/processor.js:138:13\n    at async TypeormDatabase.runTransaction (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:110:13)\n    at async TypeormDatabase.transact (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:64:24)\n    at async Runner.process (/squid/node_modules/@subsquid/substrate-processor/lib/processor/runner.js:117:17)"},"length":221,"severity":"ERROR","code":"P0001","where":"PL/pgSQL function reflect_node_contract_changes() line 27 at RAISE","file":"pl_exec.c","line":"3909","routine":"exec_stmt_raise","stack":"QueryFailedError: failed reflecting node_contract updates could not serialize access due to concurrent update\n    at PostgresQueryRunner.query (/squid/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:219:19)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async InsertQueryBuilder.execute (/squid/node_modules/typeorm/query-builder/InsertQueryBuilder.js:106:33)\n    at async Store.upsert (/squid/node_modules/@subsquid/typeorm-store/lib/store.js:34:13)\n    at async nodeContractCanceled (/squid/lib/mappings/contracts.js:239:5)\n    at async /squid/lib/processor.js:138:13\n    at async TypeormDatabase.runTransaction (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:110:13)\n    at async TypeormDatabase.transact (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:64:24)\n    at async Runner.process (/squid/node_modules/@subsquid/substrate-processor/lib/processor/runner.js:117:17)"}}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

QAnet: dashboard.qa.grid.tf
{"level":1,"time":1723692674105,"ns":"sqd:processor:archive-request","msg":"http body","httpRequestId":2331986,"httpResponseBody":{"data":{"status":{"head":11329240}}}}
{"level":5,"time":1723692674144,"ns":"sqd:processor","err":{"query":"INSERT INTO \"node_contract\"(\"id\", \"grid_version\", \"contract_id\", \"twin_id\", \"node_id\", \"deployment_data\", \"deployment_hash\", \"number_of_public_i_ps\", \"state\", \"created_at\", \"solution_provider_id\", \"resources_used_id\") VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, DEFAULT) ON CONFLICT ( \"id\" ) DO UPDATE SET \"id\" = EXCLUDED.\"id\", \"grid_version\" = EXCLUDED.\"grid_version\", \"contract_id\" = EXCLUDED.\"contract_id\", \"twin_id\" = EXCLUDED.\"twin_id\", \"node_id\" = EXCLUDED.\"node_id\", \"deployment_data\" = EXCLUDED.\"deployment_data\", \"deployment_hash\" = EXCLUDED.\"deployment_hash\", \"number_of_public_i_ps\" = EXCLUDED.\"number_of_public_i_ps\", \"state\" = EXCLUDED.\"state\", \"created_at\" = EXCLUDED.\"created_at\", \"solution_provider_id\" = EXCLUDED.\"solution_provider_id\"","parameters":["0011329240-000002-dffb9",4,"39227",465,3,"{\"version\":3,\"type\":\"Gateway Name\",\"name\":\"ivbghiqeus\",\"projectName\":\"ivbghiqeus\"}","992b15a23a77e3b59f612683910b6e13",0,"Created","1723692660",0],"driverError":{"length":214,"name":"error","severity":"ERROR","code":"P0001","where":"PL/pgSQL function reflect_node_contract_changes() line 42 at RAISE","file":"pl_exec.c","line":"3909","routine":"exec_stmt_raise","stack":"error: failed calc node_contracts_count could not serialize access due to concurrent update\n    at /squid/node_modules/pg/lib/client.js:526:17\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async PostgresQueryRunner.query (/squid/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:184:25)\n    at async InsertQueryBuilder.execute (/squid/node_modules/typeorm/query-builder/InsertQueryBuilder.js:106:33)\n    at async Store.upsert (/squid/node_modules/@subsquid/typeorm-store/lib/store.js:34:13)\n    at async contractCreated (/squid/lib/mappings/contracts.js:106:9)\n    at async /squid/lib/processor.js:138:13\n    at async TypeormDatabase.runTransaction (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:110:13)\n    at async TypeormDatabase.transact (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:64:24)\n    at async Runner.process (/squid/node_modules/@subsquid/substrate-processor/lib/processor/runner.js:117:17)"},"length":214,"severity":"ERROR","code":"P0001","where":"PL/pgSQL function reflect_node_contract_changes() line 42 at RAISE","file":"pl_exec.c","line":"3909","routine":"exec_stmt_raise","stack":"QueryFailedError: failed calc node_contracts_count could not serialize access due to concurrent update\n    at PostgresQueryRunner.query (/squid/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:219:19)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async InsertQueryBuilder.execute (/squid/node_modules/typeorm/query-builder/InsertQueryBuilder.js:106:33)\n    at async Store.upsert (/squid/node_modules/@subsquid/typeorm-store/lib/store.js:34:13)\n    at async contractCreated (/squid/lib/mappings/contracts.js:106:9)\n    at async /squid/lib/processor.js:138:13\n    at async TypeormDatabase.runTransaction (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:110:13)\n    at async TypeormDatabase.transact (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:64:24)\n    at async Runner.process (/squid/node_modules/@subsquid/substrate-processor/lib/processor/runner.js:117:17)"}}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

devnet: dashboard.dev.grid.tf
{"level":1,"time":1724720673634,"ns":"sqd:processor:archive-request","msg":"http body","httpRequestId":721358,"httpResponseBody":{"data":{"status":{"head":12565482}}}}
{"level":5,"time":1724720673834,"ns":"sqd:processor","err":{"query":"INSERT INTO \"node_contract\"(\"id\", \"grid_version\", \"contract_id\", \"twin_id\", \"node_id\", \"deployment_data\", \"deployment_hash\", \"number_of_public_i_ps\", \"state\", \"created_at\", \"solution_provider_id\", \"resources_used_id\") VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, DEFAULT) ON CONFLICT ( \"id\" ) DO UPDATE SET \"id\" = EXCLUDED.\"id\", \"grid_version\" = EXCLUDED.\"grid_version\", \"contract_id\" = EXCLUDED.\"contract_id\", \"twin_id\" = EXCLUDED.\"twin_id\", \"node_id\" = EXCLUDED.\"node_id\", \"deployment_data\" = EXCLUDED.\"deployment_data\", \"deployment_hash\" = EXCLUDED.\"deployment_hash\", \"number_of_public_i_ps\" = EXCLUDED.\"number_of_public_i_ps\", \"state\" = EXCLUDED.\"state\", \"created_at\" = EXCLUDED.\"created_at\", \"solution_provider_id\" = EXCLUDED.\"solution_provider_id\"","parameters":["0012565482-000006-b824d",4,"145267",51,176,"{\"version\":3,\"type\":\"network\",\"name\":\"pn6zjc7ud7tbxua\",\"projectName\":\"kubernetes/ugwqj5qzid5zmq4\"}","23087aeda8b4c99740e53643718745ab",0,"Created","1724720658",0],"driverError":{"length":214,"name":"error","severity":"ERROR","code":"P0001","where":"PL/pgSQL function reflect_node_contract_changes() line 42 at RAISE","file":"pl_exec.c","line":"3909","routine":"exec_stmt_raise","stack":"error: failed calc node_contracts_count could not serialize access due to concurrent update\n    at /squid/node_modules/pg/lib/client.js:526:17\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async PostgresQueryRunner.query (/squid/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:184:25)\n    at async InsertQueryBuilder.execute (/squid/node_modules/typeorm/query-builder/InsertQueryBuilder.js:106:33)\n    at async Store.upsert (/squid/node_modules/@subsquid/typeorm-store/lib/store.js:34:13)\n    at async contractCreated (/squid/lib/mappings/contracts.js:106:9)\n    at async /squid/lib/processor.js:138:13\n    at async TypeormDatabase.runTransaction (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:110:13)\n    at async TypeormDatabase.transact (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:64:24)\n    at async Runner.process (/squid/node_modules/@subsquid/substrate-processor/lib/processor/runner.js:117:17)"},"length":214,"severity":"ERROR","code":"P0001","where":"PL/pgSQL function reflect_node_contract_changes() line 42 at RAISE","file":"pl_exec.c","line":"3909","routine":"exec_stmt_raise","stack":"QueryFailedError: failed calc node_contracts_count could not serialize access due to concurrent update\n    at PostgresQueryRunner.query (/squid/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:219:19)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async InsertQueryBuilder.execute (/squid/node_modules/typeorm/query-builder/InsertQueryBuilder.js:106:33)\n    at async Store.upsert (/squid/node_modules/@subsquid/typeorm-store/lib/store.js:34:13)\n    at async contractCreated (/squid/lib/mappings/contracts.js:106:9)\n    at async /squid/lib/processor.js:138:13\n    at async TypeormDatabase.runTransaction (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:110:13)\n    at async TypeormDatabase.transact (/squid/node_modules/@subsquid/typeorm-store/lib/database.js:64:24)\n    at async Runner.process (/squid/node_modules/@subsquid/substrate-processor/lib/processor/runner.js:117:17)"}}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Update:
The error originating from the processor database is unrelated to the processor stack (GraphQL). It stems from an SQL function (trigger) created in the database by the grid proxy.

update here: https://github.com/threefoldtech/tfgrid-sdk-go/issues/1172#issuecomment-2325771159


Add sector to facility search index

Overview
Add sector to facility search index
Describe the solution you'd like

Add sector string array field to the facility index table
When indexing a facility, get all values from the most recent active facility list item for each contributor

Deduplicate the list of sectors

Duplicate of #1832


Websockets Auth

Not sure if this has been covered but, trying to authenticate the Broadcast Channels in Laravel and by default it uses Auth:User.
As we are using a custom authentication method, trying to connect to web sockets does not work as I am trying to use the shop id to compare it with the shop id with the broadcast event but it is not working.
Is there something I am missing to get this to work with your package?
Broadcast::channel('shop.{id}', function ($user, $id) {
    $shop = ShopifyApp::shop();
    return (int) $shop->id === (int) $id;
});

After trying for 2 days, seems like it has something to do with the fact that broadcasting/auth uses the standard Auth middleware which passes $user over to the channel.
As you use a custom auth middleware and the default Auth does not do anything, we need to bind $user to the Shop model I assume for verification. Just not 100% sure if this is the right way to go.
I assume we could do something like this in AuthShop?
$request->merge(['user' => $user]);

$request->setUserResolver(function () use ($user) {
   return $user;
});

Hey @Kyon147
Sort of.. but Shop model needs to implement a few interfaces for it to properly work as a "user" class in laravel.
I briefly looked into it around v3 release but it turned out to be a nice bit of work that I wasn't comfortable taking on.
At the moment, I am not sure I have a suggestion for you.

@ohmybrew no worries, looking at it for a couple of days I can see it is a big bit off work and a little bit out of my skill depth if I'm honest at the moment.
I'll probably have a mess around with on a dev set up as I'm still not that confident with your package to go messing around properly.
Look forward if you get around to doing this as it would be wicked to tie websockets into the apps by using the native broadcast service.
I'll close this for now.


mark_price endpoint doesn't required Symbol argument

greeting,
according to latest Binance Future Api Docs, premiumIndex endpoint:
GET /fapi/v1/premiumIndex
does not required symbol as mandatory argument, but in the current version its mandatory.
thanks

Thank you for bringing this up. We will do the necessary fix.

Fixed in #53


Status bar animation not working

It seems setOpenSide is called in the completation block of openDrawerSide and closeDrawerAnimated, and it calls setNeedsStatusBarAppearanceUpdate without animation, but openDrawerSide/closeDrawerAnimated try to do it.
A fast workaround is to modify setOpenSide in this way, just adding an animation to setNeedsStatusBarAppearanceUpdate:
-(void)setOpenSide:(MMDrawerSide)openSide{
    if(_openSide != openSide){
        _openSide = openSide;
        [self.centerContainerView setOpenSide:openSide];
        if(openSide == MMDrawerSideNone){
            [self.leftDrawerViewController.view setHidden:YES];
            [self.rightDrawerViewController.view setHidden:YES];
        }
        [UIView animateWithDuration:0.3 animations:^{
            [self setNeedsStatusBarAppearanceUpdate];
        }];

    }
}

Of course this is not a solution because animation should be launch from openDrawerSide/closeDrawerAnimated using the duration parameter properly.

@Ricardo1980 are you referring to animating the status bar with the center view controller as you open and close the slide out menu?


Library not loaded<EMAIL_ADDRESS>

I installed miniconda via homebrew and then created a virtual environment. I installed it via pip nuitka and orderset and tried to build the hello test file from the example on the website. I used nuitka bevor on windows, were I had no problem. I am running it now on an M1 Pro Macbook.
I´ve tried the stable release and the development version.

python -m nuitka --standalone hello.py                                          (tester)

Building it works fine without errors.
Nuitka-Options:INFO: Used command line options: --standalone hello.py
Nuitka:INFO: Starting Python compilation with Nuitka '1.1rc8' on Python '3.10' commercial grade 'not installed'.
Nuitka:INFO: Completed Python level compilation and optimization.
Nuitka:INFO: Generating source code for C backend compiler.
Nuitka:INFO: Running data composer tool for optimal constant value handling.
Nuitka:INFO: Running C compilation via Scons.
Nuitka-Scons:INFO: Backend C compiler: clang (clang).
Nuitka-Scons:INFO: Backend linking program with 10 files (no progress information available).
Nuitka-Scons:WARNING: You are not using ccache.
Nuitka:INFO: Keeping build directory 'hello.build'.
Nuitka:INFO: Created binary that runs on macOS 11.1 (arm64) or higher.
Nuitka:INFO: Successfully created 'hello.dist/hello'

Running then the output file results in this error.  The file libpython3.10.dylib which cannot be found is in the directory. Building it in normal mode (not onefile or standalone) works just fine.

hello.dist/hello

dyld[10503]: Library not loaded<EMAIL_ADDRESS>  Referenced from: '/Users/alex/dev/env-tester/hello.dist/hello'
  Reason: tried: '$ORIGIN/libpython3.10.dylib' (no such file), '$ORIGIN/libpython3.10.dylib' (no such file), '/usr/local/lib/libpython3.10.dylib' (no such file), '/usr/lib/libpython3.10.dylib' (no such file)
fish: Job 1, './hello' terminated by signal SIGABRT (Abort)

python -m nuitka --version

1.1rc8
Commercial: None
Python: 3.10.4 (main, Mar 31 2022, 03:37:37) [Clang 12.0.0 ]
Flavor: Anaconda Python
Executable: /opt/homebrew/Caskroom/miniconda/base/envs/tester/bin/python
OS: Darwin
Arch: arm64

pip list

Package     Version
----------- ---------
certifi     2022.6.15
Nuitka      1.1rc8
ordered-set 4.1.0
pip         22.1.2
setuptools  63.4.1
wheel       0.37.1

Thanks a lot for the help.

With the factory version it works for me. Thansk for the quick fix for now!

This is part of develop version now.

Hope the fix will be released soon. I got the same error when building an app bundle in Github Actions and then trying to install it to my desktop.
dyld[52300]: Library not loaded: '/Users/runner/hostedtoolcache/Python/3.10.6/x64/lib/libpython3.10.dylib'
  Referenced from: '/Applications/MyApp.app/Contents/MacOS/MyApp'
  Reason: tried: '/Users/runner/hostedtoolcache/Python/3.10.6/x64/lib/libpython3.10.dylib' (no such file), '/usr/local/lib/libpython3.10.dylib' (no such file), '/usr/lib/libpython3.10.dylib' (no such file)
[1]    52300 abort      /Applications/MyApp.app/Contents/MacOS/MyApp

Building it from my machine works fine (to be expected because it can find it).
Another observation is that libpython3.10.dylib is not included in the package contents but all other dylib files are there

Well, Nuitka runs its test on 3.10 just fine on Github Actions for all I know @roniemartinez this issue is for Anaconda mixed configuration. It may not be building in build mode, but so far I have not witnessed a big difference there.

Thanks for your reply @kayhayen
For me, error only happens if I run the app built from Github Actions (macos-latest) in my local machine. I downloaded this build using actions/upload-artifact@v3.
I've tried some configuration and was able to include libpython3.10.dylib in the resulting bundle. However, I get the same error when running the built app.
You can find my builds here:

PR: https://github.com/roniemartinez/nuitka-build/actions/runs/3031630183
Built artifacts/installer: https://github.com/roniemartinez/nuitka-build/actions/runs/3031630183

Error (same as before):
/Applications/myapp.app/Contents/MacOS/myapp ; exit;
dyld[60478]: Library not loaded: '/Users/runner/hostedtoolcache/Python/3.10.6/x64/lib/libpython3.10.dylib'
  Referenced from: '/Applications/myapp.app/Contents/MacOS/myapp'
  Reason: tried: '/Users/runner/hostedtoolcache/Python/3.10.6/x64/lib/libpython3.10.dylib' (no such file), '/usr/local/lib/libpython3.10.dylib' (no such file), '/usr/lib/libpython3.10.dylib' (no such file)
[1]    60478 abort      /Applications/myapp.app/Contents/MacOS/myapp

Bundle contents:
$ ls /Applications/myapp.app/Contents/MacOS | grep dylib
libcrypto.1.1.dylib
libgdbm.6.dylib
libgdbm_compat.4.dylib
libintl.8.dylib
liblzma.5.dylib
libpyside6.abi3.6.3.dylib
libpython3.10.dylib
libshiboken6.abi3.6.3.dylib
libssl.1.1.dylib

It looks like it is still linked to system's libpython3.10.dylib instead of the included file.

Ah, that's bad, it definitely shouldn't let system references remain undetected. But I believe otool usage on macOS is kind of broken, which is probably why this happens. Now GitHub actions is not a Python that is proclaimed as supported, so do not expect this to be a priority, esp. not posted below an unrelated issue that will be closed soon.

esp. not posted below an unrelated issue that will be closed soon.

Thanks. I created a separate ticket: https://github.com/Nuitka/Nuitka/issues/1784

This is part of the stable release 1.1 that I just made.


Cannot read property 'removeEventListener' of undefined after updating to 3.1.0

Bug Report
NOTE: I am no JS pro, so I may perfectly well be missing something obvious.
Describe the bug
After updating my code from stimulus_reflex 3.0.0 to 3.1.0 in both the gem & node, I am getting errors on a page that used to work.
To Reproduce
I do not have a clean repro case yet, just stack trace that appears to be entirely in the JS:
TypeError: can't access property "removeEventListener", socket is undefined consumer.js:38
    registerConsumer consumer.js:38
    createSubscription stimulus_reflex.js:78
    register stimulus_reflex.js:191
    StimulusReflexController stimulus_reflex.js:214
    construct self-hosted:1871
    Controller definition.js:43
    Context context.js:9
    fetchContextForScope module.js:55
    connectContextForScope module.js:37
    scopeConnected router.js:100
    elementMatchedValue scope_observer.js:55
    tokenMatched value_list_observer.js:54
    tokenMatched token_list_observer.js:82
    tokensMatched token_list_observer.js:69
    forEach self-hosted:225
    tokensMatched token_list_observer.js:68
    elementMatchedAttribute token_list_observer.js:49
    elementMatched attribute_observer.js:59
    addElement element_observer.js:151
    processAttributeChange element_observer.js:84
    processMutation element_observer.js:67
    processMutations element_observer.js:60
    mutationObserver element_observer.js:12
    (Async: MutationCallback)
    ElementObserver element_observer.js:11
    AttributeObserver attribute_observer.js:9
    TokenListObserver token_list_observer.js:8
    ValueListObserver value_list_observer.js:7
    ScopeObserver scope_observer.js:11
    Router router.js:10
    Application application.js:159
    start application.js:163
    js index.js:8
    Webpack 5

The Stimulus Reflex code on the page is very close to the Gravatar example in Expo (just modified to use Libravatar instead). No custom controller involved.
Versions
StimulusReflex

Gem: 3.1.0
Node package: 3.1.0

External tools

Ruby: 2.6.4
Rails: 6.0.2
Node: 13.12.0

Browser

Browser Firefox
Version 77
Browser Chrome
Version 80

(Repros in both)

Thanks for the bug report. This is interesting. What client side event is your reflex wired up to?

It's a pretty direct clone of https://expo.stimulusreflex.com/demos/gravatar so it's on input
HAML source code:
  .columns
    .column
      = f.input :email, hint: f.object.new_record? ? t('.email.hint') : nil, input_html: { data: { reflex: 'input->LibravatarReflex#perform' } }
    .column
      .span.image.is-64x64= image_tag(@libravatar_image_url || '')

Does this error happen consistently or only some of the time? Also, what version of ActionCable are you using?
Note that I just deployed the expo site using StimulusReflex 3.1.0 and can't seem to replicate this error (locally or on the Heroku deployment).

It's consistently for me, ActionCable is at <IP_ADDRESS>
Let me see if I can come up with a repro in a fresh project. If it doesn't repro on the Expo project it seems likely this is something squirrelly that I'm doing.

OK. We need to be more defensive around this section of code (that's providing a non-essential bit of functionality). I'll work on a patch release today and try to ship it tomorrow. Thanks again.

I've been pulling my hair out all day trying to figure this out as well. Assumed it was something I was doing wrong since this is my first time using ActionCable.

Sorry for any confusion. Please use 3.0.0 while waiting for the patch. 🙏

If it helps, I also reported this issue and have easily reproducible steps in #153.

3.1.2 fixed the problem for me and provided enough additional info for me to figure out what I did wrong, so THANKS.
For anyone else who hits this and runs across this issue: with 3.1.2, on page load I get StimulusReflex was unable to register the ActionCable consumer. Don't worry, everything should still work. Things still didn't work when triggering the actual reflex from the UI, but now the console (properly) informs me
Error invoking action "input->stimulus-reflex#__perform"

 The ActionCable connection is not open! `this.isActionCableConnectionOpen()` must return true before calling `this.stimulate()`

And that in turn finally led me to realize that the problem does indeed trace back to my own bad code. The issue in this case is that I have implemented authentication in ApplicationCable::Connection#connect but this particular reflex appears on a page outside of the application's authentication context. So ActionCable is doing exactly what I told it to do and not connecting, and StimulusReflex is quite properly refusing to act without any way to talk to the server.


feat: use prepare script to build the package

I noticed that the dist directory has unused code that is just sitting there.
It can easily be deleted and re-created, but I was thinking of implementing the prepare script so that when the github version is used, it automatically builds the package in some update, since it always deletes the dist and re-creates it.
"scripts": {
    "build": "npm run build:cjs && npm run build:esm && npm run build:types",
    "build:cjs": "node tools/cleanup cjs && tsc -p config/tsconfig.cjs.json",
    "build:esm": "node tools/cleanup esm && tsc -p config/tsconfig.esm.json",
    "build:types": "node tools/cleanup types && tsc -p config/tsconfig.types.json",
    "clean": "node tools/cleanup",

    "prepare": "npm run build" //<--- It will be executed each time the package is installed.
  }

It will be much more comfortable at the time of installation since they will be clean installations.

The package does only release the dist and not the drc build is done on my machine not on urs therefore it should be cleaned up by myself too but idk why it isnt apparently? Imma look into it next time

There are files that have been there for a year.

structures
index.js
index.d.ts

It seemed like a good idea to me anyway, especially for the github versions, since the release in npmjs ignores that script.

I fixed it, it was because the clean code only cleaned the folders and never cleaned the build which was before the folder specific build release oops
released v2.3.1 which includes your types pr


Was 2.0.0 yanked on purpose?

Is there a reason for concern regarding a potential supply chain attack, or was the yanking of all crate versions prior to yesterday's 2.1.0-rc1 an intentional action on your part? I've also noticed that the crate size has increased significantly, more than doubling in size. Given that the only version currently available is a release candidate, it's not possible to add it to a project without explicitly opting into a prerelease version.

Hi @ehrw1n
I decided to yank version 2.0.0 because I understand that 2.1.0-rc is already mature enough and fixes some issues like 22. But i unyank 2.0.0 until 2.1.0 being defintive, which should be soon.
About the size, I tried to keep the lib as small as possible but there is the cost of trying to create a better structure for the project with two platforms unix/cups and windows/winspool. I consider that despite the increase, 20kb is acceptable for most use cases that have memory limitations.


"TypeError: resolvers is not iterable" when applying toJson on ApiObject

Description of the bug:

Method toJson() of objects of type ApiObject from cdk8s will throw the following exception unless the scope (of type Construct) of that ApiObject has a resolvers: Array = [...] property.
Reproduction Steps:

Run the following Typescript code that is very basic K8s use case.
import { ApiObject, Chart } from 'cdk8s';

class CustomChart1 extends Chart {
    // public resolvers = [];  // TODO uncomment this to suppress resolvers exception
    public pod;
    public job;
    public constructor(
        public uid: string,
        public namespace: string
    ) {
        super(null, uid, { namespace: namespace, labels:  {}});
        this.pod = this.getPod();
        this.job = new ApiObject(this, this.uid, {
            apiVersion: 'batch/v1',
            kind: 'Job',
            metadata: {
                labels: {},
                name: 'test-job-name-45631685',
                annotations: {},
            },
            spec: {
                template: {
                    metadata: {
                        labels: {},
                        annotations: {},
                    },
                    spec: {
                        ...this.pod,
                    },
                },
            },
        }).toJson();
    }
    protected getPod() {
        return {
            containers: [
            {
                    name: "testing-cdk8s-123456789",
                    image: "nginx"
                }
        ]
        };
    }
}
new CustomChart1("test-cdk8s-chart-123456789", "test-namespace");

Error Log:

/home/me/Documents/proj/api/node_modules/cdk8s/src/api-object.ts:224
      throw new Error('Failed serializing construct at path '${this.node.path}' with name '${this.name}': ${e}');
            ^
Error: Failed serializing construct at path 'test-cdk8s-chart-123456789/test-cdk8s-chart-123456789' with name 'test-job-name-45631685': TypeError: resolvers is not iterable
    at ApiObject.toJson (/home/me/Documents/proj/api/node_modules/cdk8s/src/api-object.ts:224:13)
    at new CustomChart1 (/home/me/Documents/proj/api/cdk8s_bug_example.ts:43:12)

Environment:

Framework Version: 2.68.10
OS: Linux Mint 20 Ulyana

Other:

The bug was introduced with this feature which has also introduced the issue here that I am ALSO encountering.
This feature has to be rolled back or speedily fixed. We consider versions since its merging broken.
I would have attempted a quick PR for this resolvers issue because replacing the line
const resolvers = App.of(apiObject).resolvers;  found here with
const resolvers = App.of(apiObject).resolvers || [ ]; would solve the bug
BUT I am also experiencing the can't render non-simple object from here so this fix would not suffice.
Thank you!

This is :bug: Bug Report

After searching for related issues across cdk8s' Slack channels, I found the following PR: PR-1770 which solved our problems.
In the code sample, the line
super(null, uid, { namespace: namespace, labels:  {}});
should be
super(new App(), uid, { namespace: namespace, labels:  {}});
In other words, the scope of the Chart should not be null, but a cdk8s App object instead.
It would be great if there was some sort of changelog for cdk8s that would document such usage changes.
Thank you, closing the issue.


Invalid character in group name (in colors/dogrun.vim)

Hi,
Right after updating my plugins through vim Plug, I always have the same error coming from colors/dogrun.vim :
line: 93
W18: Invalid character in group name

This error happens on all lines between the 93th until line 109 :
  93   │ hi @string guifg=#7cbe8c ctermfg=108
  94   │ hi @string.regex guifg=#7cbe8c ctermfg=108
  95   │ hi @string.escape guifg=#b871b8 ctermfg=133
  96   │ hi @text.title guifg=#a8a384 ctermfg=144 gui=bold cterm=bold
  97   │ hi @text.reference guifg=#929be5 ctermfg=104
  98   │ hi @text.uri guifg=#545c8c ctermfg=60
  99   │ hi @text.strong gui=bold cterm=bold
 100   │ hi @text.literal guifg=#73c1a9 ctermfg=79
 101   │ hi @parameter guifg=#929be5 ctermfg=104
 102   │ hi @property guifg=#929be5 ctermfg=104
 103   │ hi @keyword guifg=#b871b8 ctermfg=133
 104   │ hi @type guifg=#ac8b83 ctermfg=138
 105   │ hi @type.builtin guifg=#ac8b83 ctermfg=138
 106   │ hi @include guifg=#929be5 ctermfg=104
 107   │ hi @variable.builtin guifg=#ac8b83 ctermfg=138
 108   │ hi @constant.builtin guifg=#73c1a9 ctermfg=79
 109   │ hi @constructor guifg=#9ea3c0 ctermfg=146

I use vim9 and the latest version of dogrun on arch.

Hi @Thaegox, Thank you for using dogrun :dog:
This seems to be due to the changes we have made for Treesitter.
I will fix it to apply only for Neovim :+1:

@Thaegox
I made the fixing in commit https://github.com/wadackel/vim-dogrun/commit/7622fa0d300dce9a9223797413b8d4f97417b7b5.
I would appreciate it if you could check if it works when you have time :dog2:

All good !
Thanks a lot :D

Thanks for your contribution:clap:
I'll close this issue.


pipe and redirect hangs

We are unable to pipe and redirect,(stdout, stderr hangs)  data out of docker, due to chances done in the sematext logagent.
This became an issue for us after upgrading the logagent from version 2.0.184 to 3.0.18, 3.0.21
The following can be done to recreate the problem locally.
The following is an example that hangs on ouput.
docker run -i --rm -e LOGSENE_ENABLED=false --log-driver none mysql:5.7.27 sh -c ”mysqldump ...” > dump.sql 2> dump_err.log
Our environment details:
AWS CentOs 7 AMI
Docker Engine 19.03.1 and 19.03.5

Hi, when you use no log diver, or any other log driver than json-file or journald, you probably don't need to set   LOGSENE_ENABLED=false.
Please try:
docker run -i --rm --log-driver none mysql:5.7.27 sh -c ”mysqldump ...” > dump.sql 2> dump_err.log
I assume Logagent will not collect the output, and will not make a detach API call for the container.

Hi
We will git it a try and get back to you.
Regards
Mads

Fra: Megastef<EMAIL_ADDRESS>Sendt: fredag 6. mars 2020 01:56
Til: sematext/logagent-js<EMAIL_ADDRESS>Kopi: Mads bredholt<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Emne: Re: [sematext/logagent-js] pipe and redirect hangs (#210)
Hi, when you use no log diver, or any other log driver than json-file or journald, you probably don't need to set LOGSENE_ENABLED=false.
Please try:
docker run -i --rm --log-driver none mysql:5.7.27 sh -c ”mysqldump ...” > dump.sql 2> dump_err.log
I assume Logagent will not collect the output, and will not make a detach API call for the container.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/sematext/logagent-js/issues/210?email_source=notifications&email_token=AB47WFDGNVDKLCVRGJITL5TRGBC4FA5CNFSM4LCG7BD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEN7PB4I#issuecomment-595521777, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB47WFCA33VL63VAC2WWWQDRGBC4FANCNFSM4LCG7BDQ.

Any luck with this @madsbredholt ?

Hi
We have'nt had time to look at this yet.
I'll get back to you as soon as we have had a chance to it.
Regards Mads
Get Outlook for Androidhttps://aka.ms/ghei36

From: Otis Gospodnetić<EMAIL_ADDRESS>Sent: Monday, March 16, 2020 10:13:26 PM
To: sematext/logagent-js<EMAIL_ADDRESS>Cc: Mads bredholt<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [sematext/logagent-js] pipe and redirect hangs (#210)
Any luck with this @madsbredholthttps://github.com/madsbredholt ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/sematext/logagent-js/issues/210#issuecomment-599760875, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB47WFCWCS5QYJNSZI2Z5ODRH2I7NANCNFSM4LCG7BDQ.


[INLONG-1760] Optimize the realization of class MessageProducerExample

Fixes #1760

Codecov Report

Merging #1762 (20e49a5) into INLONG-1739 (8b3e625) will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@              Coverage Diff               @@
##             INLONG-1739    #1762   +/-   ##
==============================================
  Coverage          12.20%   12.20%
+ Complexity          1050     1048    -2
==============================================
  Files                392      392
  Lines              32754    32772   +18
  Branches            5158     5164    +6
==============================================
+ Hits                3997     4001    +4
- Misses             27992    28006   +14
  Partials             765      765

Impacted Files
Coverage Δ

...pache/inlong/tubemq/corebase/utils/MixedUtils.java
0.00% <0.00%> (ø)

.../inlong/tubemq/corebase/policies/FlowCtrlItem.java
38.88% <0.00%> (-1.12%)
:arrow_down:

.../tubemq/corebase/policies/FlowCtrlRuleHandler.java
34.07% <0.00%> (-0.45%)
:arrow_down:

.../java/org/apache/flume/sink/tubemq/TubemqSink.java
55.42% <0.00%> (+4.00%)
:arrow_up:

Continue to review full report at Codecov.

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


Angular graph

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

Related issues?
n/a

What's in this Pull Request?
This is an angular v1.x sample of how to connect to the Microsoft Graph and pull SharePoint information from your Office 365 tenant. You can also create, update, and delete items from the Announcements list.
Thanks for your contribution! Sharing is caring.

sorry didn't realize that I was trying to merge this into the main branch. You can remove this request. I just created another one against the dev branch. Thanks!

No worries David, closing this one.


Port checking on current host appears to do nothing

See https://github.com/onelogin/php-saml/blob/570a5d9cc42a1a205355b9212bd182fbe35404d9/lib/Saml2/Utils.php#L326-L332
At first glance this appears to remove non-numeric port numbers from hosts, however, it doesn't actually do this and there's a test that even asserts that it doesn't remove non-numeric ports.
Is this block of code intended to perform any function, if so what? Should if be removed?

I wrote that too long ago, but I think I took that part from simpleSAMLphp:
https://github.com/simplesamlphp/simplesamlphp/blob/master/lib/SimpleSAML/Utils/HTTP.php#L57

Considering it doesn't actually appear to do anything - should it be removed? It doesn't do what the SimpleSaml lib does (which is remove numeric port numbers).

OK - I'm incorrect - the array_pop removes an item from the array and the subsequent implode joins an array with a single element (or if there were multiple port declarations, sticks them back together?!)

Closing as the (perhaps) intended functionality of removing numeric ports appears to work


Can not load the unet and controlnet

Thanks for your wonderful work! I'm encountering an error when trying to load the 'unet' or 'controlnet' models. The error mentions that it couldn't connect to 'https://huggingface.co/' to load the model, even though I believe my internet connection is working fine. Do you have any suggestions on how to fix this issue?
The error message is as follows:
OSError: We couldn't connect to 'https://huggingface.co' to load this model, couldn't find it in the cached files and it looks like preset/models/seesr is not the path to a directory containing a config.json file. Checkout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/diffusers/installation#offline-mode'.

Hi,same problem! How to solve this? Thanks! @XsherryR

Hi,same problem! How to solve this? Thanks! @XsherryR

replace the relative path to absolute path

Could you explain it in details? @CuddleSabe


Apply deMULTIplex2  for sci-Plex?

Hi,
For sci-Plex, the cell barcode position is not a fixed value.
R1: { 9-10 bp hairpin barcode }-{CAGAGC}-{ 8bp UMI }--{10 bp RT barcode}
How could I generate the readTable for this read structure?
Thanks for your excellent R package! It is such a great help for bioinformatic beginner like me!!
Any reply would be really appreciated!

Hi Yijia, we're glad you like our tool! I personally don't have experience with sci-Plex and the readTags() function was not designed to handle such a different barcode structure, but it may be possible. My understanding is that the RT and hairpin barcode together make up the "cell barcode". Your "sample barcode", i.e. the hashing oligo used in the experiment, should be in R2 then? If so, try running readTags() like this:
readTable <- readTags(
  barcode.type = "MULTIseq", # this is to make sure it extracts both the cell barcode and UMI from R1 - a quirk of how I wrote it
  assay = NULL,
  filter.cells = NULL,
  fastq.A = "/path/to/R1.fastq.gz",
  fastq.B = "/path/to/R2.fastq.gz",
  pos.cbc = c(1,34),
  pos.sbc = c(start,end), # input the appropriate indices of your hash barcode in R2 here
  pos.umi = c(1,34)
)

If this succeeds (it will probably throw an error that barcode is not correct) and your readTable is populated with actual sequences (Cell and UMI should be identical full length reads), then I would follow this up with a combination of gsub() commands to extract the correct sequence for the cell barcodes and UMIs:
readTable$Cell <- gsub("CAGAGC.{8}", "", readTable$Cell) # this should remove the UMI and constant region CAGAGC and leave the concatenated hairpin and 10bp RT barcode
readTable$UMI <- gsub(".*?CAGAGC(.{8}).*", "\\1", readTable$UMI) # this should keep just the UMI

I assume your R1 reads will not be variable length (i.e. all 34 bases) even if the content you wish to extract within is variable (33-34 bases). This means there will be an extra base appended to the cell barcodes that used a 9-base hairpin but I don't think this should cause any problems as long as you're aware of it.
As an aside, since you'll likely want to pair your sample demultiplexing results with gene expression analysis of your sci-RNA-seq library, you'll probably need to confirm how the cell barcodes are generated in that analysis pipeline. For example, if the RT and hairpin sequences are concatenated in the opposite order or the 9-base hairpins have that extra base trimmed, you'll need to make adjustments so that once you have your deMULTIplex2 results, your sample assignments can be transferred over to your other analysis.
Let me know if that helps!

Thank you very much for your detailed explanation and prompt response!! Your patient guidance has been incredibly helpful, and I truly appreciate the time and effort you've taken to assist me. Many thanks!
readTags <- function (fastq.A = NA, fastq.B = NA,
                      pos.cbc,  pos.sbc, pos.umi,
                      filter.cells = NULL, ...)
{

  cat("### Building Read Table ###", fill = T)

  cat("Loading first set of reads...", fill = T)
  r <- readFastq(fastq.A)
  gc(verbose = F)

  read_table <- data.frame(Cell = subseq(sread(r),pos.cbc[1], pos.cbc[2]),
                           UMI = subseq(sread(r), pos.umi[1], pos.umi[2]))

  read_table$Cell <- gsub("CAGAGC.{8}", "", read_table$Cell) # this should remove the UMI and constant region CAGAGC and leave the concatenated hairpin and 10bp RT barcode
  read_table$UMI <- gsub(".*?CAGAGC(.{8}).*", "\\1", read_table$UMI) # this should keep just the UMI

  cat("Finished processing first set of reads; unloading from memory",
      fill = T)
  r <- NULL
  gc(verbose = F)
  cat("Loading second set of reads...", fill = T)
  r <- readFastq(fastq.B)
  gc(verbose = F)

  read_table$Sample <- as.character(subseq(sread(r), pos.sbc[1],pos.sbc[2]))

  cat("Finished processing second set of reads; unloading from memory",
      fill = T)
  r <- NULL
  gc(verbose = F)
  cat("Finished parsing ", nrow(read_table), " read pairs",
      sep = "", fill = T)
  if (is.null(filter.cells)) {
    cat("Keeping all reads because filter.cells = NULL",
        fill = T)
  }
  else if (!is.null(filter.cells)) {
    cat("Filtering for ", length(filter.cells), " provided cell barcodes...",
        sep = "", fill = T)
    ind <- which(read_table$Cell %in% filter.cells)
    read_table <- read_table[ind, ]
  }
  read_table <- read_table[, c("Cell", "Sample", "UMI")]
  cat("Finished building read table", fill = T)
  cat("\n")
  cat("Finished in", round(difftime(Sys.time(), t0, units = "mins")[[1]],
                           1), "minutes", sep = " ")
  cat("\n")
  return(read_table)
}

readTable <- readTags(
  #filter.cells = NULL,
  fastq.A = R1,
  fastq.B = R2,
  pos.cbc = c(1,34),
  pos.sbc = c(1,10), # input the appropriate indices of your hash barcode in R2 here
  pos.umi = c(1,34)
)

readTable <- readTable[nchar(readTable$Cell) == 20 ,]

Thanks Yijia for sharing your code with us!
We have never benchmarked deMULTIplex2 on sci-Plex data and we do not know how well the model fits the data. So please check the diagnostic plots output by deMULTIplex2. Let us know if anything weird shows up (does the distribution plot look similar to that in the paper? does the model fitting fail for some of your samples?).


Add blindsigning in Settings for nano.

Options are "For Large Tx", "ON", "OFF"
Update snapshots for nano

The error you're getting from the generated tests is caused by the set_expert_mode function in the test_runtime.sh file because the settings flow has changed.
Once you have corrected this function, the tests should pass.


Audio Header is Changed

When running the command, the Audio along with the Video's fourcc are changed to "dvh1" making the audio unplayable. ffmpeg forces the video fourcc to be hev1, claiming mp4 container doesn't support dvh1, even though the mp4 input file fourcc was dvh1, so I can't add another audio track after running the command. I am using eac3 5.1 audio.

I’m not so sure what you mean. Can you provide sample files and the commands you used?

Sorry, this actually seems to be an issue with the tool I'm using to mux to mp4.
https://github.com/DolbyLaboratories/dlb_mp4base
I'll ask them to fix it instead. When I use their mp4muxer it gives the audio stream a 'dvhe' header instead of eac3 so your program misinterprets the audio as video. When using a sample with proper header, audio is untouched.
ffprobe says this:
Stream #0:0[0x1](und): Video: hevc (Main 10) (dvhe / 0x65687664), yuv420p10le(pc), 3840x2160 [SAR 1:1 DAR 16:9], 15185 kb/s, 59.94 fps, 59.94 tbr, 60k tbn (default)
Stream #0:1[0x2](und): Audio: none (dvhe / 0x65687664), 48000 Hz, 5.1(side), 640 kb/s (default)


update headless check

PLATFORM has been overriden by SPEC after compiling stage. Using libc check instead.
Signed-off-by: Sophia Guo<EMAIL_ADDRESS>

https://ci.adoptopenjdk.net/job/Grinder/2520/console
https://ci.adoptopenjdk.net/job/Grinder/2519/

zos: Grinder/19462
aix: Grinder/19463
wins: Grinder/19464


Mark All Read doesn't work in (ocnews) query feeds

Newsboat version (copy from newsboat -v): 2.11.1
Steps to reproduce the issue:

Create a query feed, for instance:
"query:Category - Tech:tags =~ \"Tech\""
Open the query feed with unread articles in Newsboat
Press 'A' for 'Mark All Read'
Newsboat (correctly) marks all articles as read in the interface
Go back to the main screen and press 'R' for 'Reload All'
All feeds are reloaded and all articles that were marked as read are back and unread

Other info you think is relevant:
My config options related to read/unread articles:
show-read-feeds         no
show-read-articles      no
mark-as-read-on-hover   yes

Also, marking all articles as read in an actual feed works fine.

Thank you for the report! I think I found the cause—Newsboat marked the feed read in its database, but didn't send that info to remote API (ocnews in your case). Can you pull down bugfix/220 branch and check if it fixes the issue for you?

Sorry, I tested the branch, but I get the same behaviour.

I don't have ocnews, so I had to test with The Old Reader instead, and it works there. Can you check again with a minimal config that contains just urls-source, ocnews-login and ocnews-password?

Of course. I did that right now and found the same issue. After "A" for reload all, the articles previously marked as read were marked unread again.

Same issue here. I can make you an ocnews account if it helps.

Thank you for the offer, @nononomen, but I don't know when—and if—I'll be getting back to this.

@arjan-s, @nononomen: can you try out #1275 and tell us if this fixes the bug?

Hi, thank you for notifying me.
Essentially, it does fix the bug, but I'm afraid the implementation is not useful yet.
When marking a query feed read-all, the current implementation performs an API call to mark each and every article in the feed as read. There is one bug in the current code: it also performs the API call for articles that were already marked read. Changing this to only mark unread articles as read would improve the performance a lot.
Then there is a higher level performance question: is marking every article individually the way to go? Performance-wise it would be much better to use the single API call to mark an entire feed read, like when marking a single feed read. That would make the current PR more difficult though, I imagine.

Okay, thanks! Since the bug is technically fixed, I'll merge that PR.
As for performance, we do have a couple issues about it, e.g. https://github.com/newsboat/newsboat/issues/123 and https://github.com/newsboat/newsboat/issues/682. Improving that requires pretty drastic changes to how Newsboat works with remote APIs. I personally won't work on that until after the move to Rust, but #123 has some instructions if anyone's itching to help.


⚠ ClamAV has degraded performance

In e586697, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 232 ms

Resolved: ClamAV performance has improved in 548a3f3.


Enhancement, or guidance on filters

How might I filter or act upon PR notifications based upon the PR's status? I'm generally uninterested in a backlog of notifications related to merged PRs and I haven't found a prompt method for maintaining the list so far.

the response from the REST API for the notification doesn't hold the infos about the state of the PullRequest

a json example for a single PullRequest notification is below, only the first part holds some relvant infos, but noting to help with your issue
additional requests can be made, but I quickly got rate limitations when I made many calls with in short succession to check
the state of each issue/pr.

{
  "id": "6557595093",
  "unread": false,
  "reason": "author",
  "updated_at": "2023-05-31T11:08:24Z",
  "last_read_at": "2023-06-20T17:02:34Z",
  "subject": {
    "title": "feat: mark individual notifications as read",
    "url": "https://api.github.com/repos/meiji163/gh-notify/pulls/52",
    "latest_comment_url": "https://api.github.com/repos/meiji163/gh-notify/pulls/52",
    "type": "PullRequest"
  },
  "repository": {
    "id": 417606553,
    "node_id": "R_kgDOGOQrmQ",
    "name": "gh-notify",
    "full_name": "meiji163/gh-notify",
    "private": false,
    "owner": {
      "login": "meiji163",
      "id": 48187500,
      "node_id": "MDQ6VXNlcjQ4MTg3NTAw",
      "avatar_url": "https://avatars.githubusercontent.com/u/48187500?v=4",
      "gravatar_id": "",
      "url": "https://api.github.com/users/meiji163",
      "html_url": "https://github.com/meiji163",
      "followers_url": "https://api.github.com/users/meiji163/followers",
      "following_url": "https://api.github.com/users/meiji163/following{/other_user}",
      "gists_url": "https://api.github.com/users/meiji163/gists{/gist_id}",
      "starred_url": "https://api.github.com/users/meiji163/starred{/owner}{/repo}",
      "subscriptions_url": "https://api.github.com/users/meiji163/subscriptions",
      "organizations_url": "https://api.github.com/users/meiji163/orgs",
      "repos_url": "https://api.github.com/users/meiji163/repos",
      "events_url": "https://api.github.com/users/meiji163/events{/privacy}",
      "received_events_url": "https://api.github.com/users/meiji163/received_events",
      "type": "User",
      "site_admin": true
    },
    "html_url": "https://github.com/meiji163/gh-notify",
    "description": "GitHub CLI extension to display GitHub notifications",
    "fork": false,
    "url": "https://api.github.com/repos/meiji163/gh-notify",
    "forks_url": "https://api.github.com/repos/meiji163/gh-notify/forks",
    "keys_url": "https://api.github.com/repos/meiji163/gh-notify/keys{/key_id}",
    "collaborators_url": "https://api.github.com/repos/meiji163/gh-notify/collaborators{/collaborator}",
    "teams_url": "https://api.github.com/repos/meiji163/gh-notify/teams",
    "hooks_url": "https://api.github.com/repos/meiji163/gh-notify/hooks",
    "issue_events_url": "https://api.github.com/repos/meiji163/gh-notify/issues/events{/number}",
    "events_url": "https://api.github.com/repos/meiji163/gh-notify/events",
    "assignees_url": "https://api.github.com/repos/meiji163/gh-notify/assignees{/user}",
    "branches_url": "https://api.github.com/repos/meiji163/gh-notify/branches{/branch}",
    "tags_url": "https://api.github.com/repos/meiji163/gh-notify/tags",
    "blobs_url": "https://api.github.com/repos/meiji163/gh-notify/git/blobs{/sha}",
    "git_tags_url": "https://api.github.com/repos/meiji163/gh-notify/git/tags{/sha}",
    "git_refs_url": "https://api.github.com/repos/meiji163/gh-notify/git/refs{/sha}",
    "trees_url": "https://api.github.com/repos/meiji163/gh-notify/git/trees{/sha}",
    "statuses_url": "https://api.github.com/repos/meiji163/gh-notify/statuses/{sha}",
    "languages_url": "https://api.github.com/repos/meiji163/gh-notify/languages",
    "stargazers_url": "https://api.github.com/repos/meiji163/gh-notify/stargazers",
    "contributors_url": "https://api.github.com/repos/meiji163/gh-notify/contributors",
    "subscribers_url": "https://api.github.com/repos/meiji163/gh-notify/subscribers",
    "subscription_url": "https://api.github.com/repos/meiji163/gh-notify/subscription",
    "commits_url": "https://api.github.com/repos/meiji163/gh-notify/commits{/sha}",
    "git_commits_url": "https://api.github.com/repos/meiji163/gh-notify/git/commits{/sha}",
    "comments_url": "https://api.github.com/repos/meiji163/gh-notify/comments{/number}",
    "issue_comment_url": "https://api.github.com/repos/meiji163/gh-notify/issues/comments{/number}",
    "contents_url": "https://api.github.com/repos/meiji163/gh-notify/contents/{+path}",
    "compare_url": "https://api.github.com/repos/meiji163/gh-notify/compare/{base}...{head}",
    "merges_url": "https://api.github.com/repos/meiji163/gh-notify/merges",
    "archive_url": "https://api.github.com/repos/meiji163/gh-notify/{archive_format}{/ref}",
    "downloads_url": "https://api.github.com/repos/meiji163/gh-notify/downloads",
    "issues_url": "https://api.github.com/repos/meiji163/gh-notify/issues{/number}",
    "pulls_url": "https://api.github.com/repos/meiji163/gh-notify/pulls{/number}",
    "milestones_url": "https://api.github.com/repos/meiji163/gh-notify/milestones{/number}",
    "notifications_url": "https://api.github.com/repos/meiji163/gh-notify/notifications{?since,all,participating}",
    "labels_url": "https://api.github.com/repos/meiji163/gh-notify/labels{/name}",
    "releases_url": "https://api.github.com/repos/meiji163/gh-notify/releases{/id}",
    "deployments_url": "https://api.github.com/repos/meiji163/gh-notify/deployments"
  },
  "url": "https://api.github.com/notifications/threads/6557595093",
  "subscription_url": "https://api.github.com/notifications/threads/6557595093/subscription"
}

How might I filter or act upon PR notifications based upon the PR's status? I'm generally uninterested in a backlog of notifications related to merged PRs and I haven't found a prompt method for maintaining the list so far.

a question do you still get some notifications on these merged PR's with gh notify or are the listed as read  and you just don't want to see them with gh notify -an 20 ?

if it is the former, I could just add a hotkey that lets you unsubscribe from an Issue/ PR and new notification won't arrive anymore

https://github.com/meiji163/gh-notify/blob/e86f6760a29d19845cfc29cdd747b16803b3f74a/gh-notify#L450-L459

I may also have to add a new column for the notification reason, similar to the WebUI


Bug in $update()

Hi,
it seems like there is a bug in $update function
Best regards Hjh elec29a :)

@amcdnl :smile: Wanted to fix that anyway. It's a work mate of mine who I told to report the bug with a failing test.
Have to debug it on why it doesn't work..

@elec29a Will be fixed with the next release

that's really good news :)
+1:  thumbs up great job

@elec29a Released v0.3.0 containing the fix for this bug. Should be out on bower soon


SwiftPM in Xcode 12: Failed to resolve dependencies.

When adding this library to an iOS project via Xcodes SwiftPM functionality, I get this error:
because SwiftCSVExport >=1.0.0 contains incompatible tools version and root depends on SwiftCSVExport 2.3.0..<3.0.0, version solving failed.

I am getting this error also. Can someone update with a resolution?

I am getting this error also. Can someone update with a resolution?

@Jeehut your pull request build failed

@Jeehut your pull request build failed

@willm132 Of course it failed, I didn't add a test target. I could have a look tomorrow, working time is over for me for today (in Germany). Didn't know you had a CI in place that was running SwiftPM tests ...

@willm132 Of course it failed, I didn't add a test target. I could have a look tomorrow, working time is over for me for today (in Germany). Didn't know you had a CI in place that was running SwiftPM tests ...

Awesome. Let me know if you get it working, I’m interested in using this in my app.

Awesome. Let me know if you get it working, I’m interested in using this in my app.

I emailed the owner via his website to see if he could update it but he has no responded

I emailed the owner via his website to see if he could update it but he has no responded


1.39.1 Got invalid value, return 500 error

Oct 25 12:29:46 localhost nvm-exec[1498080]: PrismaClientValidationError: Argument id: Got invalid value '14ccac36-ce69-4d7e-931f-c95c641e5f02' on prisma.findUniquewebsite. Provided UUID, expected Int.
Oct 25 12:29:46 localhost nvm-exec[1498080]:     at Document.validate (/home/love4taylor/applications/umami/node_modules/@prisma/client/runtime/index.js:28989:20)
Oct 25 12:29:46 localhost nvm-exec[1498080]:     at serializationFn (/home/love4taylor/applications/umami/node_modules/@prisma/client/runtime/index.js:31900:19)
Oct 25 12:29:46 localhost nvm-exec[1498080]:     at runInChildSpan (/home/love4taylor/applications/umami/node_modules/@prisma/client/runtime/index.js:25102:12)
Oct 25 12:29:46 localhost nvm-exec[1498080]:     at PrismaClient._executeRequest (/home/love4taylor/applications/umami/node_modules/@prisma/client/runtime/index.js:31907:31)
Oct 25 12:29:46 localhost nvm-exec[1498080]:     at consumer (/home/love4taylor/applications/umami/node_modules/@prisma/client/runtime/index.js:31834:23)
Oct 25 12:29:46 localhost nvm-exec[1498080]:     at /home/love4taylor/applications/umami/node_modules/@prisma/client/runtime/index.js:31839:51
Oct 25 12:29:46 localhost nvm-exec[1498080]:     at AsyncResource.runInAsyncScope (node:async_hooks:203:9)
Oct 25 12:29:46 localhost nvm-exec[1498080]:     at /home/love4taylor/applications/umami/node_modules/@prisma/client/runtime/index.js:31839:29
Oct 25 12:29:46 localhost nvm-exec[1498080]:     at runInChildSpan (/home/love4taylor/applications/umami/node_modules/@prisma/client/runtime/index.js:25102:12)
Oct 25 12:29:46 localhost nvm-exec[1498080]:     at PrismaClient._request (/home/love4taylor/applications/umami/node_modules/@prisma/client/runtime/index.js:31836:22) {
Oct 25 12:29:46 localhost nvm-exec[1498080]:   clientVersion: '4.5.0'
Oct 25 12:29:46 localhost nvm-exec[1498080]: }

Encountered the same error.

Possible solution: https://github.com/umami-software/umami/issues/1583#issuecomment-1289988255

Migrations likely failed. The commands used here  could be of use.

I just ran
CREATE EXTENSION IF NOT EXISTS pgcrypto;
delete from _prisma_migrations where migration_name = '04_add_uuid';
And restarted Umami to re-apply.

@briancao in my case, the migrations didn't fail. Still, I got that error.
Anyway, I applied the migrations manually, still the error persists. I am attaching the logs in case it helps.
022-10-25T06:19:48.600Z	4d9c033a-72ed-4fde-acda-5817ca1836cd	ERROR	PrismaClientValidationError: Argument id: Got invalid value '2c0d4795-5e6f-45b7-a2df-6c1096ea86de' on prisma.findUniquewebsite. Provided UUID, expected Int.
at Document.validate (/var/task/node_modules/@prisma/client/runtime/index.js:28989:20)
at serializationFn (/var/task/node_modules/@prisma/client/runtime/index.js:31900:19)
at runInChildSpan (/var/task/node_modules/@prisma/client/runtime/index.js:25102:12)
at PrismaClient._executeRequest (/var/task/node_modules/@prisma/client/runtime/index.js:31907:31)
at consumer (/var/task/node_modules/@prisma/client/runtime/index.js:31834:23)
at /var/task/node_modules/@prisma/client/runtime/index.js:31839:51
at AsyncResource.runInAsyncScope (node:async_hooks:202:9)
at /var/task/node_modules/@prisma/client/runtime/index.js:31839:29
at runInChildSpan (/var/task/node_modules/@prisma/client/runtime/index.js:25102:12)
at PrismaClient._request (/var/task/node_modules/@prisma/client/runtime/index.js:31836:22) {  clientVersion: '4.5.0'}2022-10-25T06:19:48.601Z	4d9c033a-72ed-4fde-acda-5817ca1836cd   ERROR	PrismaClientValidationError: Argument id: Got invalid value '2c0d4795-5e6f-45b7-a2df-6c1096ea86de' on prisma.findUniquewebsite. Provided UUID, expected Int.
at Document.validate (/var/task/node_modules/@prisma/client/runtime/index.js:28989:20)
at serializationFn (/var/task/node_modules/@prisma/client/runtime/index.js:31900:19)
at runInChildSpan (/var/task/node_modules/@prisma/client/runtime/index.js:25102:12)
at PrismaClient._executeRequest (/var/task/node_modules/@prisma/client/runtime/index.js:31907:31)
at consumer (/var/task/node_modules/@prisma/client/runtime/index.js:31834:23)
at /var/task/node_modules/@prisma/client/runtime/index.js:31839:51
at AsyncResource.runInAsyncScope (node:async_hooks:202:9)    at /var/task/node_modules/@prisma/client/runtime/index.js:31839:29
at runInChildSpan (/var/task/node_modules/@prisma/client/runtime/index.js:25102:12)
at PrismaClient._request (/var/task/node_modules/@prisma/client/runtime/index.js:31836:22) {  clientVersion: '4.5.0'}RequestId: 4d9c033a-72ed-4fde-acda-5817ca1836cd Error: Runtime exited with error: exit status 1Runtime.ExitError

@rohandebsarkar Because you manually applied the migration, you'll likely need to rebuild umami or run yarn build-db to rebuild the latest version of the prisma client.

@rohandebsarkar Because you manually applied the migration, you'll likely need to rebuild umami or run yarn build-db to rebuild the latest version of the prisma client.

Thank you for the reply. I tried rebuilding umami on Vercel, also tried yarn build-db locally and hosted locally. But the issue is still there. I can not see any statistics on the dashboard as well as on the website page.

Ok, might be a legitimate non-migration related bug.  Let me look into it.

Commit ebf439c5987a8e7480df6af81bc33907832c0b6b seems to fix the problem, thanks for the quick fix.

Fixed in v1.39.2.


If Runkit only run in CLI mode ?

I just tested it with php-5.6
./bin/php path/to/test.php works as expected,
but with php-fpm , it kills fpm process:
[24-Mar-2016 18:15:46] WARNING: [pool www] child 23016 exited on signal 11 (SIGSEGV) after 185.581668 seconds from start

What can I do now ?

I notice the document says:

Sandboxing is ONLY AVAILABLE in PHP 5.1
so sad..

But .. but this page show it at least supports 5.4.9 :http://news.php.net/php.bugs/196299
I find that  new Runkit_Sandbox([]) cause the segment fault.
I am trying to get a coredump file .

1804 line in runkit_sandbox.c
php_request_shutdown  crash the fcgi process?
why?

Try to change the expression 'req->fd >= 0' into 'req && req->fd >= 0' here
https://github.com/php/php-src/blob/PHP-5.5.33/sapi/fpm/fpm/fastcgi.c#L1073

@zenovich Thanks, It works fine now .
Is this the debug step or the  final solution  ?

I hope it is a final solution. I suggest reporting this bug to php-fpm's authors.

@anight @tony2001 maybe you're interested in this.

Try to change the expression 'req->fd >= 0' into 'req && req->fd >= 0' here
https://github.com/php/php-src/blob/PHP-5.5.33/sapi/fpm/fpm/fastcgi.c#L1073
or here https://github.com/php/php-src/blob/PHP-5.6.20/sapi/fpm/fpm/fastcgi.c#L1073
@zenovich
I found this bug in a few different SAPIs, using php binaries with WinAPI (procedure calls) is also causes this.
For example: php4delphi (if you wish to test, you can find my fork, which is 5.6-compatible)

I notice the document says:

Sandboxing is ONLY AVAILABLE in PHP 5.1

so sad..

With php 5.3 and 5.4 it works pretty well, maybe sandboxing is for all php 5 versions?
The official php internals documentation says, that the hashtables security (including functions table) and sub-processing is changed only in PHPNG (which means 6.0, never released version, so => php 7.0 & up)

Easy Bypass (Hacked)

Run Runkit_Sandbox() class on $runkit->eval('…new Runkit_Sandbox;…')


Docs typo? (minor)

In the Custom Types docs, I noticed this:

path: If type: path, the path that will be used to locate this type. Defaults to the singularized version of the type name with a _ prepended. (so, for a content type named talks, the default path would be _talks)
(emphasis mine)

If the default is singularized, shouldn't the default path for "talks" be "_talk"?
Is there are separate repo for the docs, where I should put this kind of issue?

Is there are separate repo for the docs, where I should put this kind of issue?

Oh yes, there is :)
I submitted a pull request there.

Thanks! :)