text:
Many Pex tests fail under Python 2.7 in CI

I was finally able to reproduce this locally by re-creating my tox venv which, as a side effect, upgraded virtualenv. The latter is the problem.
The errors look like:
$ tox -epy27 -- -vvsk test_entry_points_dict
.package create: /home/jsirois/dev/pantsbuild/jsirois-pex/.tox/.package
.package installdeps: flit_core >=2,<3
py27 create: /home/jsirois/dev/pantsbuild/jsirois-pex/.tox/py27
py27 installdeps: pytest==4.6.6, mock==3.0.5
py27 inst: /home/jsirois/dev/pantsbuild/jsirois-pex/.tox/.tmp/package/1/pex-2.1.9.tar.gz
py27 installed: DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support,atomicwrites==1.4.0,attrs==19.3.0,configparser==4.0.2,contextlib2==0.6.0.post1,funcsigs==1.0.2,importlib-metadata==1.6.0,mock==3.0.5,more-itertools==5.0.0,packaging==20.3,pathlib2==2.3.5,pex==2.1.9,pluggy==0.13.1,py==1.8.1,pyparsing==2.4.7,pytest==4.6.6,scandir==1.10.0,six==1.14.0,wcwidth==0.1.9,zipp==1.2.0
py27 run-test-pre: PYTHONHASHSEED='1467207441'
py27 run-test: commands[0] | pytest --ignore=tests/test_integration.py -vvsk test_entry_points_dict
==================================================================================================================================== test session starts =====================================================================================================================================
platform linux2 -- Python 2.7.18, pytest-4.6.6, py-1.8.1, pluggy-0.13.1 -- /home/jsirois/dev/pantsbuild/jsirois-pex/.tox/py27/bin/python
cachedir: .tox/py27/.pytest_cache
rootdir: /home/jsirois/dev/pantsbuild/jsirois-pex
collected 179 items / 178 deselected / 1 selected

tests/test_bdist_pex.py::test_entry_points_dict running bdist_pex
Writing my_app to /tmp/tmpsgDVu1/my_app-0.0.0.pex
Failed to create pex via /home/jsirois/dev/pantsbuild/jsirois-pex/.tox/py27/bin/python -s -m pex /tmp/tmpxEPsaM --output-file /tmp/tmpsgDVu1/my_app-0.0.0.pex --script my_app:
ERROR: Exception:
Traceback (most recent call last):
  File "/home/jsirois/.pex/pip.pex/3616f444e6841b3bb5e495d304f6de6a76f743d8/.deps/pip/pip/_internal/cli/base_command.py", line 172, in _main
    status = self.run(options, args)
  File "/home/jsirois/.pex/pip.pex/3616f444e6841b3bb5e495d304f6de6a76f743d8/.deps/pip/pip/_internal/commands/install.py", line 457, in run
    use_user_site=options.use_user_site,
  File "/home/jsirois/.pex/pip.pex/3616f444e6841b3bb5e495d304f6de6a76f743d8/.deps/pip/pip/_internal/req/__init__.py", line 71, in install_given_reqs
    **kwargs
  File "/home/jsirois/.pex/pip.pex/3616f444e6841b3bb5e495d304f6de6a76f743d8/.deps/pip/pip/_internal/req/req_install.py", line 775, in install
    prefix=prefix,
  File "/home/jsirois/.pex/pip.pex/3616f444e6841b3bb5e495d304f6de6a76f743d8/.deps/pip/pip/_internal/locations.py", line 186, in get_scheme
    dist_name, user, home, root, isolated, prefix
  File "/home/jsirois/.pex/pip.pex/3616f444e6841b3bb5e495d304f6de6a76f743d8/.deps/pip/pip/_internal/locations.py", line 108, in distutils_scheme
    d = Distribution(dist_args)
  File "/home/jsirois/dev/pantsbuild/jsirois-pex/.tox/py27/lib/python2.7/site-packages/setuptools/dist.py", line 448, in __init__
    k: v for k, v in attrs.items()
  File "/usr/lib/python2.7/distutils/dist.py", line 287, in __init__
    self.finalize_options()
  File "/home/jsirois/dev/pantsbuild/jsirois-pex/.tox/py27/lib/python2.7/site-packages/setuptools/dist.py", line 740, in finalize_options
    ep.load()(self)
TypeError: unbound method _finalize_setup_keywords() must be called with Distribution instance as first argument (got Distribution instance instead)
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/home/jsirois/dev/pantsbuild/jsirois-pex/pex/__main__.py", line 8, in <module>
    __name__ == '__main__' and pex.main()
  File "/home/jsirois/dev/pantsbuild/jsirois-pex/pex/bin/pex.py", line 724, in main
    pex_builder = build_pex(reqs, options, cache=ENV.PEX_ROOT)
  File "/home/jsirois/dev/pantsbuild/jsirois-pex/pex/bin/pex.py", line 644, in build_pex
    ignore_errors=options.ignore_errors)
  File "/home/jsirois/dev/pantsbuild/jsirois-pex/pex/resolver.py", line 824, in resolve_multi
    return list(resolve_request.resolve_distributions(ignore_errors=ignore_errors))
  File "/home/jsirois/dev/pantsbuild/jsirois-pex/pex/resolver.py", line 574, in resolve_distributions
    raise_type=Untranslateable):
  File "/home/jsirois/dev/pantsbuild/jsirois-pex/pex/resolver.py", line 392, in _run_parallel
    max_jobs=self._max_parallel_jobs
  File "/home/jsirois/dev/pantsbuild/jsirois-pex/pex/jobs.py", line 219, in execute_parallel
    raise error
pex.resolver.Untranslateable: pid: 45184 -> /home/jsirois/dev/pantsbuild/jsirois-pex/.tox/py27/bin/python /home/jsirois/.pex/pip.pex/3616f444e6841b3bb5e495d304f6de6a76f743d8 --disable-pip-version-check --isolated --no-python-version-warning -q --cache-dir /home/jsirois/.pex install --no-deps --no-index --only-binary :all: --target /home/jsirois/.pex/installed_wheels/4a13a89cdea76fef75d2f4f649fd2a71e63cadc5/my_app-0.0.0-py2-none-any.whl.b62ccffb18944c67b083ffc00365fcf3 --no-compile /home/jsirois/.pex/built_wheels/local_projects/tmpxEPsaM/2f24e7ea7df2645d261d6734d297043c0d527dfc/cp27-cp27mu/my_app-0.0.0-py2-none-any.whl raised Executing /home/jsirois/dev/pantsbuild/jsirois-pex/.tox/py27/bin/python /home/jsirois/.pex/pip.pex/3616f444e6841b3bb5e495d304f6de6a76f743d8 --disable-pip-version-check --isolated --no-python-version-warning -q --cache-dir /home/jsirois/.pex install --no-deps --no-index --only-binary :all: --target /home/jsirois/.pex/installed_wheels/4a13a89cdea76fef75d2f4f649fd2a71e63cadc5/my_app-0.0.0-py2-none-any.whl.b62ccffb18944c67b083ffc00365fcf3 --no-compile /home/jsirois/.pex/built_wheels/local_projects/tmpxEPsaM/2f24e7ea7df2645d261d6734d297043c0d527dfc/cp27-cp27mu/my_app-0.0.0-py2-none-any.whl failed with 2

FAILED

========================================================================================================================================== FAILURES ==========================================================================================================================================
___________________________________________________________________________________________________________________________________ test_entry_points_dict ___________________________________________________________________________________________________________________________________

    def test_entry_points_dict():
>     assert_entry_points({'console_scripts': ['my_app = my_app.my_module:do_something']})

tests/test_bdist_pex.py:54:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
tests/test_bdist_pex.py:37: in assert_entry_points
    with bdist_pex(project_dir) as my_app_pex:
/usr/lib/python2.7/contextlib.py:17: in __enter__
    return self.gen.next()
tests/test_bdist_pex.py:29: in bdist_pex
    spawn_python_job(args=cmd, cwd=project_dir, pythonpath=[pex_project_dir()]).wait()
.tox/py27/lib/python2.7/site-packages/pex/jobs.py:38: in wait
    self._check_returncode()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = <pex.jobs.Job object at 0x7f932477f190>, stderr = None

    def _check_returncode(self, stderr=None):
      if self._process.returncode != 0:
        msg = 'Executing {} failed with {}'.format(' '.join(self._command), self._process.returncode)
        if stderr:
          msg += '\nSTDERR:\n{}'.format(stderr.decode('utf-8'))
>       raise self.Error(msg)
E       Error: Executing /home/jsirois/dev/pantsbuild/jsirois-pex/.tox/py27/bin/python -s setup.py --command-packages pex.commands bdist_pex --bdist-dir=/tmp/tmpsgDVu1 failed with 1

.tox/py27/lib/python2.7/site-packages/pex/jobs.py:67: Error
========================================================================================================================== 1 failed, 178 deselected in 3.08 seconds ==========================================================================================================================
ERROR: InvocationError for command /home/jsirois/dev/pantsbuild/jsirois-pex/.tox/py27/bin/pytest --ignore=tests/test_integration.py -vvsk test_entry_points_dict (exited with code 1)
__________________________________________________________________________________________________________________________________________ summary ___________________________________________________________________________________________________________________________________________
ERROR:   py27: commands failed

This is a tricky problem involving a custom importer virtualenv installs that loses references to symbols in its module after some import reloading by Pex, virtualenv, or both. Its unclear exactly where and when symbols get nuked at this point.

A binary search shows the error is introduced in virtualenv 20.0.5 so I'm going to take the tack of pinning virtualenv to 20.0.4 and installing tox 3.14.5 which is the last tox version still compatible with Pex tox.ini to support virtualenv 20.0.4.

repo: pantsbuild/pex


text:
Unable to add a custom plugin to a Consumer

Plugin tab of Consumer  can not add a custom plugin, even no the custom plugins tag show.

As a workaround, I add hasConsumerPlugins : true, after this place:
https://github.com/pantsel/konga/blob/853518f0675623db61067db93a6d4396a0f98628/assets/js/app/core/services/KongPluginsService.js#L233
But it not a real solution, if I have a plugin named dynamic-upstream, it's an API only plugin, it will be showed on Consumer plugin tab too. So I have to hide it manualy, like this:
name: "Custom",
hasConsumerPlugins : true,
description: "Custom Plugins",
icon: "mdi-account-box-outline",
plugins: {
    "dynamic-upstream": {
        hideIfNotInConsumerContext : true,
        description: "Dynamic upstream"
    }
}

It's kinda not elegant and suboptimal but it works :)

@ms2008
If you want to make your custom plugin, please refer this page
https://docs.konghq.com/0.14.x/plugin-development/file-structure/
You don't need to modify kong's original source code , when you make your custom plugin
Thanks.

@ms2008 , the issue has been fixed on the next branch.
A release is expected in the next couple of days.

source: gharchive/issue

authors: kakarooky ms2008 pantsel

repo: pantsel/konga

license: mit

license_type: permissive

license_source: bigquery


text:
Refresh the token at some fixed interval rather than on Token expired.

I think, there is some problem if we wait till token is expired and then trigger the refresh token api, of some other functional api calls might get returned with 401 error, if the refresh token sent in the api request is already expired. Kind of edge cases, but then we need to handle those 401 by writing interceptors and retrying the api calls once the token refresh is successful.
Can we have simple solution to set the minValidity as a prop in config and then use it for triggering the updateToken method.

Hi @Techno-than ,
Thanks for your feedback.
A quicker solution would be to explicitly call refreshToken on the injected keycloak instance before making the API call (see official documentation of the method here)
keycloak.updateToken(30).then(function() {
    loadData();
}).catch(function() {
    alert('Failed to refresh token');
});

(updateToken receive a parameter that represent the minimum remaining time required by your call, if the token is expiring in less than the passed time it will refresh the token otherwise it won't)

Hello @panz3r Thanks for the amazing library. It's easy to setup and use so far.
I'd run into this problem recently, I use axios to make the API requests. I have a general function that compile and trigger axios API calls. However, occasionally the token expires when the API is called and 401 is returned.
As far as I can tell, the only way to get a keycloak instance is through hook or HOC, how can I use refreshToken in a function that is not a function component?
I saw your example here: https://github.com/panz3r/react-keycloak/blob/master/examples/react-router/src/utils/hooks.js, however I don't think I can use it outside of a component. Any hint would be greatly appreciated.

Hi @nhattextiq ,
Thanks for your feedback, recently I've been working using a library similar to react-keycloak (but for other authentication providers) and started using a different setup, which I'll start recommending for react-keycloak too (I'll update docs and examples as soon as I find some time).
Basically by moving Keycloak instance creation to a different file (say keycloak.js) placed near the main App.js, the instance become available for import around the app.
I suggested this setup to solve another issue but the same could be applied to this use-case, see here for a more detailed explanation.
Let me know if this helps you so that I can consider it a viable solution.

Hi @panz3r ,
That seems to work, thanks for the pointer. So I have it setup like this for the central api call function.
keycloak.updateToken(30).then(() => (
  axios([config])
  .then((response) => {})
  .catch((error) => {})
)).catch(() => {
  console.error('failed to refresh access token')
})

It does get refresh automatically before the API is called after 5 minutes of idling.
Cheers.

Hi @nhattextiq ,
Thanks for your quick feedback, I'm glad it solved your issue.
I've update the README for the @react-keycloak/web package to explain the new project setup and how to access keycloak outside of the react flow.
Thanks, I'm going to close this issue.

authors: Techno-than nhattextiq panz3r

license: MIT

license_source: github-api


text:
IMPORTER_DIR misspelled

https://github.com/papermerge/papermerge-core/blob/a6ad68f6806c5d192d14bb359d2a2bbc95e92a82/papermerge/core/management/commands/worker.py#L80

@jcollie, thanks for heads up!

@jcollie, thanks for heads up!

authors: ciur jcollie

repo: papermerge/papermerge-core


text:
⚠ Topfarmacia has degraded performance

In 3ea1e51, Topfarmacia (https://www.topfarmacia.it) experienced degraded performance:

HTTP code: 200
Response time: 12406 ms

Resolved: Topfarmacia performance has improved in 751072f.

repo: papies/upptime


text:
Add troubleshooting & dev docs

Local build requirements for mac
Formatting command

looks good
do you know if the macos pyo3 issues are still present after this commit 8766fd6d73756dab98dd3049af726d311a65526f ? had you run into these issues yourself?
ideally would make this part as foolproof as possible for python users. would rather solve it in build.rs instead of having them tweak their cargo config

Yea i encountered the issue when trying to build, but not on install. Can check if it can be solved with build.rs instead

looks good
do you know if the macos pyo3 issues are still present after this commit 8766fd6 ? had you run into these issues yourself?
ideally would make this part as foolproof as possible for python users. would rather solve it in build.rs instead of having them tweak their cargo config

Issue is not still present. Can close this

source: gharchive/pull-request

authors: ipatka sslivkoff

repo: paradigmxyz/cryo


text:
Add ANSI Escape Codes Compatibility to PST

PST is nice, yet locked to monochromatic displays. It would be nice if PST had an ANSI-compatible mode like many general-purpose terminals.

For colorful displays?

Yes.

authors: JonMcPhalen PropGit

repo: parallaxinc/Propeller-Tool


text:
Make import work in node 13 ESM

Fixes issue #187 error: "Cannot find main entry point" in package.json

After merging this, could you please update the npm package?

Thank you!

@mathiasrw : Thank you for merging it so quickly!
Would it be possible to update the npm package? To fix #187 and #188.

Ill see what I can do. Not sure I have access more.

Ill see what I can do. Not sure I have access more.

I do not remember any of us ever having NPM or package access.

Nope - I dont have access. Last update was 6 years ago. Time for an npm name change?

$ npm owner ls paralleljs
asavitzky adam.savitzky@gmail.com

I would prefer not to have to change the NPM name.
@mathiasrw, who has had contact wih Adam?
I do not think I have. Everything has been through @amilajack or you.

Enlightening (less bureaucratic than I thought!): https://docs.npmjs.com/using-npm/disputes.html

@benbucksch There is no dispute. The repo is adams, the npm is adams. A dispute would be if we insists that we have the right to the npm name. We dont. We contribute with the rights as the originator see fit.

Mathias, yes, of course. The title of the document is a bit misleading, but it's also for an unresponsive maintainer. (6 years without releases is something!)
Did you contact adams by email? Did he respond? Will he make the release? If yes, no problem, all good. If no, you can make releases again via this process.

@benbucksch Ok. You are right. I sent him an email cc npm.

Incredible response time; great support so far 👍🏼

Merged and pushed to npm as version 1.0.0

That's great! Thank you!

authors: MaXFalstein benbucksch mathiasrw


text:
Monorail relaunch

Renames sites, package names, and deployment configs

 Launch prep, deployment, and monitoring


text:
Deprecated Pandas mehods and Pandas Warnings

[ ] Applymap
[ ] DtypeWarning
[ ] SettingWithCopyWarning
[ ] FutureWarning: Downcasting object dtype arrays on .fillna

[ ] Add functionality for tests to fail when a warning is raised
[ ] Remove warnings until tests pass
[ ] Add hook to run tests on push

unittest is falling short here going to switch up to pytest

#21 Ties into this

The setting with copy warning was being created by reset time in segment.
This is due to df[‘item’] or df.loc[‘item’] potentially causing problems. It didn’t here but its better to be cautious and not get into the habit of ignoring these warnings.
Another picky issue for me was the reassignment of the list in the loop, so I've replaced it with a map. Pro its cleaner and on smaller datasets we could see concurrency depending on how python wants to implement things, con there is potential that this increases memory requirement on larger datasets.

I suspect other memory issues will arise anyway when dealing with very large datasets, so if the feature works with the example datasets we have I would say it is ok for now.

authors: PipGrylls brosaplanella


text:
Add synthetic unwind row entry for the function end

Context
DWARF unwind information specifies the low and high PC for every
function it covers. Within a function, it has entries for each
instruction boundary. These entries have the program counter they
start covering, but not its end.
This is not a problem for any instruction boundary except the last one,
but while we have that information when parsing the DWARF info, we never
add it anywhere in the BPF representation.
While this was not a problem for a large majority of the stacks we need
to unwind it introduce two issues:

We know we've reached the bottom frame when a PC doesn't have unwind
info + frame pointer == 0. Normally the bottom frame has a PC that's
not covered by the (lowest, highest) PCs that the unwind info has, but
as far as I know there's no guarantee of this. If we get the last item
of a chunk, we have no way to know if the PC we are interested in is
covered in the unwind info, or not;
The other problem is that we currently have, related to the last point
above, is that we have to chunk some unwind tables when they are too
large for the maximum size of a shard or for the current free space in a
shard. When this happens we might split a function in two. This causes
the same issues as above at every split point.

Proposed solution
This commit adds a fake or synthetic unwind row to indicate the end of a
function. We then handle this appropriately in the unwinder.
Unfortunately we will increase the unwind table size, I expect by ~5-10% on
average, but haven't measured properly. While this is not ideal, we want to
ensure that the statistics we get from the unwinder as are correct as possible.
In the future we might remove some of these markers that aren't totally
necessary (e.g. if we can prove that there can't be any other PC in between
a pair of consecutive rows from different functions. This might be hard
to get 100% right on x86, but could be a possibility).
I was planning on slightly reducing the size of the unwind row, which
should help a bit with the recent size increase from this commit.
Other changes

Made the code that deals with chunking and shard allocation cleaner an
more correct.
The eh-frame utility accepts a new argument to filter unwind info
for a particular function that contains the given PC.

Test Plan

no errors on sudo bpftool prog tracelog | grep err

Co-authored-by: Kemal Akkoyun kakkoyun@users.noreply.github.com
Co-authored-by: Javier Honduvilla Coto javierhonduco@gmail.com
Signed-off-by: Francisco Javier Honduvilla Coto javierhonduco@gmail.com

@javierhonduco I can't officially approve this 😅 Feel free to proceed as you see fit!

That's funny 😄

authors: javierhonduco kakkoyun

repo: parca-dev/parca-agent


text:
feat(governance-app): View Proposals and Referendums

Update (Mon, May 20th):

New things that came up that aren't implemented in this PR but up for discussion for future PRs:

These meta descriptions of the proposals and related extrinsics could have another mapping to more beginner friendly explanations. Also, thinking of moving it to a ? button instead of dedicating an entire column to it

Proposals and Referenda are under one tab (Democracy), implying that Council related things are not democractic (which they're arguably not). Still, this could use better wording

The delegations tab would allow users to view all the accounts they've delegated to vote as well as query other users' delegations.

Can merge right after the log file is deleted

authors: amaurymartiny yjkimjunior

repo: paritytech/substrate-light-ui


text:
Decouple node-executor structures from wasmi

These are some refactors to ease the integration of a compiled Wasm executor. This decouples the memory allocator and sandbox from wasmi. In the case of the sandbox, sandboxed environments will still execute with wasmi in the near future, so the decoupling is just on the supervisor side. (The supervisor is the substrate runtime, which handles external calls from the sandboxed runtime).
With the allocator, it no longer relies on dynamic borrows (which the wasmi::MemoryRef does under the hood), and instead gets a reference to the runtime memory on each allocate and deallocate call.

@pepyakin I'm sure sure making everything generic over SupervisorFuncRef is a good idea. Another option would be to just store the dispatch thunk table index as a u32 and do the lookup again inside invoke. It's a bit of wasted effort, but it should have a negligible performance impact and wouldn't mess with the type signatures on a lot of structs.

repo: paritytech/substrate


text:
Add GlobalType

This add GlobalType to the wasmi_v1 crate so that now all instance types (Func, Table, Memory and Global) do have some associated XType.

Func -> FuncType
Table -> TableType
Memory -> MemoryType
Global -> GlobalType

With this PR we also cleaned up the InstantiationError that was especially ugly due to the missing GlobalType.

Codecov Report

Merging #349 (80c5434) into master (022c751) will increase coverage by 0.06%.
The diff coverage is 61.90%.

@@            Coverage Diff             @@
##           master     #349      +/-   ##
==========================================
+ Coverage   80.69%   80.76%   +0.06%
==========================================
  Files          79       79
  Lines        9512     9513       +1
==========================================
+ Hits         7676     7683       +7
+ Misses       1836     1830       -6

Impacted Files
Coverage Δ

wasmi_v1/src/module/instantiate.rs
50.48% <50.00%> (+1.25%)
:arrow_up:

wasmi_v1/src/global.rs
64.06% <66.66%> (+0.79%)
: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 022c751...80c5434. Read the comment docs.

authors: Robbepop codecov-commenter

repo: paritytech/wasmi


text:
add fix for login to wine images

Description
fix the problem, that logins are not possible
All Submissions:

[x] Have you ensured there aren't other open Pull Requests for the same update or change?
[x] Have you created a new branch for your changes and PR from that branch and not from your master branch?

LGTM! thx

repo: parkervcp/yolks


text:
npm start error

Running on Mac OS X with latest node and npm. I followed the installation and setup instructions and after running "npm start" I get the following error:
`> parse-files-utils@0.0.1 start /Users/chriswise/Documents/Development/Experiments/ParseFileMigrator/parse-files-utils-master

node index.js

module.js:434
return process.dlopen(module, path._makeLong(filename));
^
Error: Module version mismatch. Expected 46, got 14.
at Error (native)
at Object.Module._extensions..node (module.js:434:18)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/Users/chriswise/Documents/Development/Experiments/ParseFileMigrator/parse-files-utils-master/node_modules/parse-server-gcs-adapter/node_modules/@google-cloud/storage/node_modules/@google-cloud/common/node_modules/grpc/src/node/src/grpc_extension.js:38:15)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
npm ERR! Darwin 15.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v4.6.0
npm ERR! npm  v2.15.9
npm ERR! code ELIFECYCLE
npm ERR! parse-files-utils@0.0.1 start: node index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the parse-files-utils@0.0.1 start script 'node index.js'.
npm ERR! This is most likely a problem with the parse-files-utils package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node index.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs parse-files-utils
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls parse-files-utils
npm ERR! There is likely additional logging output above.
`

Same here, except I get a different "mismatch" message:
Error: Module version mismatch. Expected 48, got 47.
    at Error (native)
    at Object.Module._extensions..node (module.js:583:18)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> ({...}/parse-files-utils/node_modules/grpc/src/node/src/grpc_extension.js:38:15)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)

same problem: Module version mismatch. Expected 48, got 46.
i was able to run the module successfully before, not sure what has changed.

We couldn't wait anymore and created our own solution based on this. In case anyone finds it useful:
https://github.com/slidebean/parse-s3-migration

Thanks @linktothapast. I found a solution to the issue--needed to reinstall node modules after a node update, like so: rm -rf node_modules && npm install.
That took care of the error.

@linktothapast thanks for fixing this with your repo!! It worked great for me.

authors: chriswise01 ilyashev linktothapast mdimarca

repo: parse-server-modules/parse-files-utils


text:
Fix problems reported by Clippy, add it to CI

Clippy reports a variety of style errors and suggested simplifications. We should fix them when we have the chance and make cargo clippy a GitHub Action so it's checked for each PR.
Example of this added to ion-rust:

https://github.com/amzn/ion-rust/issues/348
https://github.com/amzn/ion-rust/pull/352

Added the CI in the following PR and resolved one of the warnings; the remaining warnings are either related to our intentional deprecated annotation on  lex_partiql related to the lexer being a prototype or an unused function at in parser Result:
https://github.com/partiql/partiql-lang-rust/pull/73
Let's discuss further to decide if we can close or leave this open.

Resolving this issue as we agreed it can get closed offline.

repo: partiql/partiql-lang-rust


text:
Version Packages

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
create-partykit@0.0.13
Patch Changes

b9cd337 Thanks @threepointone! - trigger a release

partykit@0.0.23
Patch Changes

b9cd337 Thanks @threepointone! - trigger a release

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

authors: CLAassistant threepointone

repo: partykit/partykit


text:
Login hybrid not working

I've tried using the example website to register a passkey but it doesn't work.
Pc: Windows 11 Chrome
Android: pixel 8

Open example website on Pc
Click register, enter name
Passkey pop-up: select via android with qrcode, displays qrcode
Phone: scan qrcode
At this point two things happen:

Phone: endlessly loading
Pc: error is thrown (see https://github.com/MasterKale/SimpleWebAuthn/discussions/452 )

Hmmm... It's hard to tell what's going on. That's a generic error from the underlying protocol. Can you successfully register the same devices using the hybrid flow using some other web demo? Honestly, I have a feeling it's a Windows/Android incompatibility issue in this case. Another interesting experiment would be to register directly with your phone and try the hybrid flow from the pc to see if that works. Lastly, is it the default QR scanner or another QR scanner from the playstore?

This was from a co-workers laptop, give me some time to install windows on a laptop and I'll have some more details then.
The strange thing was that it did work for a different company website (not using passwordless-id).
It wasn't a qrcode issue, default camera app, opened Google Authenticator's passkey native pop-up just fine.

Closing it as non-reproducible. If you encounter it again some day, just re-open it.

repo: passwordless-id/webauthn


text:
Error while building the package

I am getting the following errors while building the package.
Please check the same.
Invalid gemspec in [combustion.gemspec]: combustion.gemspec:34: syntax error, unexpected keyword_end, expecting end-of-input
Invalid gemspec in [combustion.gemspec.gem2deb]: combustion.gemspec.gem2deb:34: syntax error, unexpected keyword_end, expecting end-of-input
Traceback (most recent call last):
	11: from /usr/bin/dh_ruby:96:in `<main>'
	10: from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:43:in `clean'
	 9: from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:201:in `installers'
	 8: from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:201:in `map'
	 7: from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:202:in `block in installers'
	 6: from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:202:in `new'
	 5: from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:24:in `initialize'
	 4: from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:24:in `new'
	 3: from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `initialize'
	 2: from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `chdir'
	 1: from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:34:in `block in initialize'
/usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:124:in `load_gemspec': E: cannot load gemspec combustion.gemspec (RuntimeError)

The gem builds fine for me on Ruby 2.6.0 - can you confirm which version of Ruby you're using? Also, can you share the contents of your gemspec?

Closing this issue as it's been dormant for a month. If you're still seeing issues, please do comment here anyway.

repo: pat/combustion


text:
ERROR: Failed building wheel for numpy

Hello Patrick,
I have just started using the MolPC and the Install dependencies failed with the message that it failed building wheel for numpy.
error: subprocess-exited-with-error
× Building wheel for numpy (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
Building wheel for numpy (pyproject.toml) ... error
ERROR: Failed building wheel for numpy
Failed to build numpy
Can you help? In case you need it, below is the entire window:
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Looking in links: https://storage.googleapis.com/jax-releases/jax_cuda_releases.html
Requirement already satisfied: jax[cuda]==0.3.22 in /usr/local/lib/python3.10/dist-packages (0.3.22)
Requirement already satisfied: absl-py in /usr/local/lib/python3.10/dist-packages (from jax[cuda]==0.3.22) (1.4.0)
Requirement already satisfied: numpy>=1.20 in /usr/local/lib/python3.10/dist-packages (from jax[cuda]==0.3.22) (1.22.4)
Requirement already satisfied: opt-einsum in /usr/local/lib/python3.10/dist-packages (from jax[cuda]==0.3.22) (3.3.0)
Requirement already satisfied: scipy>=1.5 in /usr/local/lib/python3.10/dist-packages (from jax[cuda]==0.3.22) (1.10.1)
Requirement already satisfied: typing-extensions in /usr/local/lib/python3.10/dist-packages (from jax[cuda]==0.3.22) (4.5.0)
Requirement already satisfied: etils[epath] in /usr/local/lib/python3.10/dist-packages (from jax[cuda]==0.3.22) (1.2.0)
Requirement already satisfied: jaxlib==0.3.22+cuda11.cudnn82 in /usr/local/lib/python3.10/dist-packages (from jax[cuda]==0.3.22) (0.3.22+cuda11.cudnn82)
Requirement already satisfied: importlib_resources in /usr/local/lib/python3.10/dist-packages (from etils[epath]->jax[cuda]==0.3.22) (5.12.0)
Requirement already satisfied: zipp in /usr/local/lib/python3.10/dist-packages (from etils[epath]->jax[cuda]==0.3.22) (3.15.0)
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Requirement already satisfied: biopython==1.79 in /usr/local/lib/python3.10/dist-packages (1.79)
Requirement already satisfied: numpy in /usr/local/lib/python3.10/dist-packages (from biopython==1.79) (1.22.4)
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Requirement already satisfied: dm-haiku==0.0.7 in /usr/local/lib/python3.10/dist-packages (0.0.7)
Requirement already satisfied: absl-py>=0.7.1 in /usr/local/lib/python3.10/dist-packages (from dm-haiku==0.0.7) (1.4.0)
Requirement already satisfied: jmp>=0.0.2 in /usr/local/lib/python3.10/dist-packages (from dm-haiku==0.0.7) (0.0.4)
Requirement already satisfied: numpy>=1.18.0 in /usr/local/lib/python3.10/dist-packages (from dm-haiku==0.0.7) (1.22.4)
Requirement already satisfied: tabulate>=0.8.9 in /usr/local/lib/python3.10/dist-packages (from dm-haiku==0.0.7) (0.8.10)
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Requirement already satisfied: ml-collections==0.1.0 in /usr/local/lib/python3.10/dist-packages (0.1.0)
Requirement already satisfied: absl-py in /usr/local/lib/python3.10/dist-packages (from ml-collections==0.1.0) (1.4.0)
Requirement already satisfied: PyYAML in /usr/local/lib/python3.10/dist-packages (from ml-collections==0.1.0) (6.0)
Requirement already satisfied: six in /usr/local/lib/python3.10/dist-packages (from ml-collections==0.1.0) (1.16.0)
Requirement already satisfied: contextlib2 in /usr/local/lib/python3.10/dist-packages (from ml-collections==0.1.0) (0.6.0.post1)
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Requirement already satisfied: chex==0.0.7 in /usr/local/lib/python3.10/dist-packages (0.0.7)
Requirement already satisfied: absl-py>=0.9.0 in /usr/local/lib/python3.10/dist-packages (from chex==0.0.7) (1.4.0)
Requirement already satisfied: dm-tree>=0.1.5 in /usr/local/lib/python3.10/dist-packages (from chex==0.0.7) (0.1.6)
Requirement already satisfied: jax>=0.1.55 in /usr/local/lib/python3.10/dist-packages (from chex==0.0.7) (0.3.22)
Requirement already satisfied: jaxlib>=0.1.37 in /usr/local/lib/python3.10/dist-packages (from chex==0.0.7) (0.3.22+cuda11.cudnn82)
Requirement already satisfied: numpy>=1.18.0 in /usr/local/lib/python3.10/dist-packages (from chex==0.0.7) (1.22.4)
Requirement already satisfied: toolz>=0.9.0 in /usr/local/lib/python3.10/dist-packages (from chex==0.0.7) (0.12.0)
Requirement already satisfied: opt-einsum in /usr/local/lib/python3.10/dist-packages (from jax>=0.1.55->chex==0.0.7) (3.3.0)
Requirement already satisfied: scipy>=1.5 in /usr/local/lib/python3.10/dist-packages (from jax>=0.1.55->chex==0.0.7) (1.10.1)
Requirement already satisfied: typing-extensions in /usr/local/lib/python3.10/dist-packages (from jax>=0.1.55->chex==0.0.7) (4.5.0)
Requirement already satisfied: etils[epath] in /usr/local/lib/python3.10/dist-packages (from jax>=0.1.55->chex==0.0.7) (1.2.0)
Requirement already satisfied: importlib_resources in /usr/local/lib/python3.10/dist-packages (from etils[epath]->jax>=0.1.55->chex==0.0.7) (5.12.0)
Requirement already satisfied: zipp in /usr/local/lib/python3.10/dist-packages (from etils[epath]->jax>=0.1.55->chex==0.0.7) (3.15.0)
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Requirement already satisfied: dm-tree==0.1.6 in /usr/local/lib/python3.10/dist-packages (0.1.6)
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Requirement already satisfied: immutabledict==2.0.0 in /usr/local/lib/python3.10/dist-packages (2.0.0)
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Collecting numpy==1.19.5
Using cached numpy-1.19.5.zip (7.3 MB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: numpy
error: subprocess-exited-with-error
× Building wheel for numpy (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
Building wheel for numpy (pyproject.toml) ... error
ERROR: Failed building wheel for numpy
Failed to build numpy
ERROR: Could not build wheels for numpy, which is required to install pyproject.toml-based projects
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Requirement already satisfied: pandas==1.3.4 in /usr/local/lib/python3.10/dist-packages (1.3.4)
Requirement already satisfied: python-dateutil>=2.7.3 in /usr/local/lib/python3.10/dist-packages (from pandas==1.3.4) (2.8.2)
Requirement already satisfied: pytz>=2017.3 in /usr/local/lib/python3.10/dist-packages (from pandas==1.3.4) (2022.7.1)
Requirement already satisfied: numpy>=1.21.0 in /usr/local/lib/python3.10/dist-packages (from pandas==1.3.4) (1.22.4)
Requirement already satisfied: six>=1.5 in /usr/local/lib/python3.10/dist-packages (from python-dateutil>=2.7.3->pandas==1.3.4) (1.16.0)
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
ERROR: Ignored the following versions that require a different python version: 1.6.2 Requires-Python >=3.7,<3.10; 1.6.3 Requires-Python >=3.7,<3.10; 1.7.0 Requires-Python >=3.7,<3.10; 1.7.0rc1 Requires-Python >=3.7,<3.10; 1.7.0rc2 Requires-Python >=3.7,<3.10; 1.7.1 Requires-Python >=3.7,<3.10
ERROR: Could not find a version that satisfies the requirement scipy==1.7.0 (from versions: 0.8.0, 0.9.0, 0.10.0, 0.10.1, 0.11.0, 0.12.0, 0.12.1, 0.13.0, 0.13.1, 0.13.2, 0.13.3, 0.14.0, 0.14.1, 0.15.0, 0.15.1, 0.16.0, 0.16.1, 0.17.0, 0.17.1, 0.18.0, 0.18.1, 0.19.0, 0.19.1, 1.0.0, 1.0.1, 1.1.0, 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.4.0, 1.4.1, 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.5.4, 1.6.0, 1.6.1, 1.7.2, 1.7.3, 1.8.0rc1, 1.8.0rc2, 1.8.0rc3, 1.8.0rc4, 1.8.0, 1.8.1, 1.9.0rc1, 1.9.0rc2, 1.9.0rc3, 1.9.0, 1.9.1, 1.9.2, 1.9.3, 1.10.0rc1, 1.10.0rc2, 1.10.0, 1.10.1, 1.11.0rc1, 1.11.0rc2)
ERROR: No matching distribution found for scipy==1.7.0
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
ERROR: Could not find a version that satisfies the requirement tensorflow-cpu==2.5.0 (from versions: 2.8.0, 2.8.1, 2.8.2, 2.8.3, 2.8.4, 2.9.0rc0, 2.9.0rc1, 2.9.0rc2, 2.9.0, 2.9.1, 2.9.2, 2.9.3, 2.10.0rc0, 2.10.0rc1, 2.10.0rc2, 2.10.0rc3, 2.10.0, 2.10.1, 2.11.0rc0, 2.11.0rc1, 2.11.0rc2, 2.11.0, 2.11.1, 2.12.0rc0, 2.12.0rc1, 2.12.0, 2.13.0rc0, 2.13.0rc1, 2.13.0rc2)
ERROR: No matching distribution found for tensorflow-cpu==2.5.0
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Requirement already satisfied: py3Dmol in /usr/local/lib/python3.10/dist-packages (2.0.3)

Hi, I am not sure what causes this error. Perhaps this is related to some remission issue for writing new packages to your user?

Hello Patrick,
I asked my colleague, Professor Brian Pierce, to run the colab on his computer and he got the same error massage. This is what he wrote:
I just tried the Colab again now, and after it prompted me about google drive access (and I accepted), it installed most packages but still seemed to error out with the numpy installation. So the problem does not seem to be the google drive access as Patrick mentioned, as far as I can tell.
Regards,
Osnat
—————————
Osnat Herzberg, PhD
Professor
Institute for Bioscience and Biotechnology Research
University of Maryland
9600 Gudelsky Drive
Rockville, MD 20850
USA
Tel 240-314-6245
Fax 240-314-6255
E-mail @.***

On Jul 21, 2023, at 1:47 AM, Patrick Bryant @.***> wrote:
Hi, I am not sure what causes this error. Perhaps this is related to some remission issue for writing new packages to your user?
—
Reply to this email directly, view it on GitHub https://github.com/patrickbryant1/MoLPC/issues/16#issuecomment-1645015556, or unsubscribe https://github.com/notifications/unsubscribe-auth/BAYWPWD4SCXLY2HWYOYX2YTXRIJVVANCNFSM6AAAAAAZQ24ATQ.
You are receiving this because you authored the thread.

Hi,
I understand what you are referring to now. I thought this was an issue with local installation, but is in fact related to the Colab. It seems that Google has updated python to 3.8 (and changed some other things as well). We will look into migrating the code to 3.8 or see if we can resolve this somehow else. In the meantime, local installation may be easier.
Best,
Patrick

Hi,
I tried to run the Colab notebook and have no issues installing the packages. Can you please try it again?
Best,
Patrick

Hi Patrick,
I run your test example (1A8R_1) and it gave the same error messages. However, the job completed successfully. In contrast, when I tried my own sequence and an .a3m file (smMreb3_1) the job failed at the MSA pipeline with a file not found massage:
Creating all interactions of size 3 ...
FileNotFoundError                         Traceback (most recent call last)
 https://a1nsd5mgb4q-496ff2e9c6d22116-0-colab.googleusercontent.com/outputframe.html?vrz=colab-20230725-060148-RC00_550839261# in <cell line: 21>()
19 @.*** Write the Paired and Block Diagonalized MSAs to predict sub-components
20 from preprocess import preprocess_colab
---> 21 preprocess_colab.create_folder_structure(MSADIR, ID, OUTDIR, USEQS, INTERACTIONS, CHAINS, GET_ALL, SUBSIZE)
2 frames
/content/MoLPC/src/preprocess/preprocess_colab.py https://a1nsd5mgb4q-496ff2e9c6d22116-0-colab.googleusercontent.com/outputframe.html?vrz=colab-20230725-060148-RC00_550839261# in read_a3m(infile, max_gap_fraction)
29     seqlen = 0
30     lc = 0
---> 31     with open(infile, 'r') as file:
32         for line in file:
33             line = line.rstrip()
FileNotFoundError: [Errno 2] No such file or directory: '/content/MoLPC/data/test/smMreb3_1_1.a3m’
After first uploading the MSA file to /content, I uploaded the smMreb3_1.a3m file to /content/MolPC/data/test. Then I tried to change all the names including in the ID and MSA1 to smMreb3_1_1.a3m. It still did not work.
Attached is my .a3m file. I tried to generate a 6-mer but since the program failed before reading the a3m file, presumably this is not important.
Any insight?
Regards,
Osnat

Osnat Herzberg, PhD
Professor
Institute for Bioscience and Biotechnology Research
University of Maryland
9600 Gudelsky Drive
Rockville, MD 20850
USA
Tel 240-314-6245
Fax 240-314-6255
E-mail @.*** @.***>

On Jul 26, 2023, at 3:33 AM, Patrick Bryant @.***> wrote:
Hi,
I tried to run the Colab notebook and have no issues installing the packages. Can you please try it again?
Best,
Patrick
—
Reply to this email directly, view it on GitHub https://github.com/patrickbryant1/MoLPC/issues/16#issuecomment-1651138036, or unsubscribe https://github.com/notifications/unsubscribe-auth/BAYWPWHC5DJB7KED6LS4X5TXSDB25ANCNFSM6AAAAAAZQ24ATQ.
You are receiving this because you authored the thread.

Hi,
Great to see that the test example is working for you as well. I don't think it is an error you are receiving when installing the packages in colab, rather an intermediate incompatibility warning that is fixed later.
I think the issue is that your naming is incorrect.
Note that you have to follow the naming convention:
"Make sure to name your MSAs according to the convention ID_1, ..., ID_N (both here and for the uploaded files)"
Try setting the ID = smMreb3 (no suffix)
and naming MSA 1 "smMreb3_1" and upload the file "smMreb3_1.a3m"
Note that computer programs require exact information and if you upload/name files other than you specify in the input these will not be found as you can read from the error message:
"FileNotFoundError: [Errno 2] No such file or directory: '/content/MoLPC/data/test/smMreb3_1_1.a3m’"
We have tried to make the running of MoLPC as easy as possible, but I am sure you understand that the code itself is actually quite complicated and we can't handle all possible cases of different naming schemes.
Hope this helps and please get back to us if you have any further issues.
Best,
Patrick

Hi Patrick,
Thank you for your advice. This time it worked. I previously made a mistake with the ID record, adding a _1 to it. Unfortunately, when I was preparing my next run, I inadvertently cleared the AF/params file (/content/gdrive/MyDrive/AF/params/params_model_1.npz’) and related files. the job failed with the message:
FileNotFoundError: [Errno 2] No such file or directory: '/content/gdrive/MyDrive/AF/params/params_model_1.npz'
Indeed, the params directory is empty (except for the License, which I did not delete). How do I get it back?
Also, are you using the latest AlphaFold multimer version that allows for >1400 amino acids? Could you link that version to MolPC? It would be most useful for me as I have a protein  with >500 aa.
Regards
Osnat Herzberg, PhD
Professor
Institute for Bioscience and Biotechnology Research
University of Maryland
9600 Gudelsky Drive
Rockville, MD 20850
USA
Tel 240-314-6245
Fax 240-314-6255
E-mail @.***

On Jul 27, 2023, at 2:58 AM, Patrick Bryant @.***> wrote:
Hi,
Great to see that the test example is working for you as well. I don't think it is an error you are receiving when installing the packages in colab, rather an intermediate incompatibility warning that is fixed later.
I think the issue is that your naming is incorrect.
Note that you have to follow the naming convention:
"Make sure to name your MSAs according to the convention ID_1, ..., ID_N (both here and for the uploaded files)"
Try setting the ID = smMreb3 (no suffix)
and naming MSA 1 "smMreb3_1" and upload the file "smMreb3_1.a3m"
Note that computer programs require exact information and if you upload/name files other than you specify in the input these will not be found as you can read from the error message:
"FileNotFoundError: [Errno 2] No such file or directory: '/content/MoLPC/data/test/smMreb3_1_1.a3m’"
We have tried to make the running of MoLPC as easy as possible, but I am sure you understand that the code itself is actually quite complicated and we can't handle all possible cases of different naming schemes.
Hope this helps and please get back to us if you have any further issues.
Best,
Patrick
—
Reply to this email directly, view it on GitHub https://github.com/patrickbryant1/MoLPC/issues/16#issuecomment-1653019029, or unsubscribe https://github.com/notifications/unsubscribe-auth/BAYWPWAJMRQKENCFQFUKYVTXSIGR7ANCNFSM6AAAAAAZQ24ATQ.
You are receiving this because you authored the thread.


text:
error: expected expression

NOTIFY_INLINE auto set_title(const char* format, ...) -> void { NOTIFY_FORMAT(this->set_title, format); }

	NOTIFY_INLINE auto set_content(const char* format, ...) -> void { NOTIFY_FORMAT(this->set_content, format); }

	NOTIFY_INLINE auto set_type(const ImGuiToastType& type) -> void { IM_ASSERT(type < ImGuiToastType_COUNT); this->type = type; };

imgui_notify.h:81:66: error: expected expression
this NOTIFY_FORMAT

nvm this project is aim for windows xD i just updated it to work on android instead.

repo: patrickcjk/imgui-notify


text:
Incorrect representation of negative numbers

Hi again,
I have found another one imperfection in your code. Negative values in IntegerBER cause infinite loop and also numbers which have higest set bit on any 8th position are represented as negative (e.g. 0000 0000 1001 0110 or 1111 1111 1011 1000)
Both can be solved by this code:
void setValue(const int32_t value) {
    _value = value < 0 ? -value : value;
    // L
    _length = 0;
    char _carry;
    do {
        _carry = _value & 0x80;
        _value >>= 8;
        _length++;
    } while (_value | _carry);
    // V
    _value = value;
    _size = _length + 2;
}

It checks if highest bit of byte is 1 (_carry), then it continues adding another byte to SNMP representation of number.
If the number is negative, it flips it (ternary operator) and proceeds to check length which is afaik the simplest solution.

Hi @metaathron ,
Thanks for caching this one. I will have a look at it in a few days.

I created a PR #6, can you test it?
I have tested with theses values on a Mega 2560. Encoding and decoding is OK.

Integer value
BER encoding

0
02 01 00

127
02 01 7F

128
02 02 00 80

256
02 02 01 00

-128
02 01 80

-129
02 02 FF 7F

Table 3. Example BER encodings of INTEGER values from A Layman's Guide to a Subset of ASN.1, BER, and DER

You're very welcome. Also thanks for your job.

authors: metaathron patricklaf

repo: patricklaf/SNMP


text:
Make an OCurrent pipeline

This PR turns the simple build script into an OCurrent pipeline, this should allow it to be setup on a macOS machine and the schedule parameter can be set to 7 to have it rebuild and push images every week.

An example pipeline

repo: patricoferris/macos-infra


text:
new script to generate edge topology

This is a script to generate the edge_topology.json in python only, without matlab. Generated json does contain the same data like the ones generated with old process, just sorted differently. I think sorting order does not matter in this case, so results are compatible and this script can completely replace the old ones.
Please review. Also please elaborate how to give credits to the autors of the original scripts since this is still based on their general idea.

Hi Christoph,
Thanks a lot for the PR, that's a great idea and definitely simplifies the process. I'd like to check the code in a bit more details myself, it'll probably be a while, until around end of August - I'll be travelling/away. But it looks pretty much good to go 👍
From the top of my head, I'd agree that the sorting should not make a difference.

please elaborate how to give credits to the autors of the original scripts

I think if you copy the top of the header from compute_edgestruct.m to the new Python script, that should be completely fine.
Also it would be great if you could convert the tabs to spaces and perhaps run a PEP 8 formatting (though the rest looks pretty consistent). All major Python IDEs should have such an option (I'm using PyCharm) and there are command-line tools for it as well.
Thanks again!

Hi Patrik,
I cleaned up the code, it should be more readable now. Its PEP8 compliant now (even though I think 79 chars per line are to few...).
Since its all packed in a function, you can call this from your converter scripts to simplify the process even more.
Thanks for creating this project :)
P.S.: I will probably publish some additions to the python binding in next days. Do you want one PR for each function or one PR for every single commit?

Hi Christoph,
Just wanted to let you know that I still have your PR(s) on my todo list. Things are quite busy currently but I should get to it within the next two of weeks. Apologies that it's taking a while.

Hi @patrikhuber
dont want to bother you to much, I just want to know, if you are still working on checking this? Also please not my other PR and those pybind additions that I do in my fork (and would like to PR here, if you want). Best Regards.

Hi Christoph,
You're not bothering. I apologise that this is taking so long. I have it on my to do list but haven't managed to get to it yet, it has been incredibly busy :. Please bare with me for a bit longer, I am definitely not forgetting about it.

authors: kanonet patrikhuber

repo: patrikhuber/eos


text:
How to generate points for landmark detection for my source image

Hi Patrick,
I build your code successfully and tested the following codes:

Landmark detection - Output got ,but taking more than an hour.
How to generate the points for my source image

you should download labeled facial landmarks database,and put them into landmarkdetection to train model.By the way,you also need to prepare meanshape file and correct file format for trainning data.tata

Hi Pat,
I run landmark executable it takes more than 1.30 hours to save the output image.Why it taking the more hour to save the output.
Will you please share the link for landmarks database.Also please more specific about the mean shape file

http://ibug.doc.ic.ac.uk/resources/300-W/
you could computer the meanshape file from training database. there are many ways to get it

I tested the landmark exe it saves out.png and landmark_regressor_ibug_68lms.txt but it takes more than one hour.
Tell the reason why taking more than one hour for save out.png

Hi gopi, hi Anand,
Are you using the newest version from master (0.3.0)? I fixed the training time two weeks ago (https://github.com/patrikhuber/superviseddescent/releases) and you shouldn't have issues. If you still do, can you please tell me the exact commit hash and system you're using, and also try how long it takes if you compile with -fopenmp(gcc/clang) or /openmp(VS)?
Note that the landmark_detection example trains the model each time before then detecting on one image. That's of course not necessary, the model can be trained once, stored, and then ran on multiple images in miliseconds. I also hope I'll finally manage to add our pretrained model to the library in a couple of weeks!
The mean can easily be calculated by just taking the mean landmarks of a few dozen training examples. I can add the code if you want.
Let me know how it goes, happy to help more.

Hey Pat,
  I tried the SDM v0.3.0 (OpenCV + OpenMP). Again i am getting same time of computation around 45 min pat.

Hi Patrick,
I build the latest code of yours from the Link is :  https://github.com/patrikhuber/superviseddescent/releases ,
then commit Id is :ee101ba3404a3e8c81203eac97f22e7a1580d0cc
.To build this code i used the following system configuration:
Ubuntu 14.04 LTS 64 bit
g++ 4.8.2
NVIDIA Graphics Card + CUDA 6.5
Opencv 3.0 + OpenMP+ Boost 1.57 +Eigen 3
RAM 8GB
Intel® Core™ i7-4790 CPU @ 3.60GHz × 8
GeForce GT 640/PCIe/SSE2
Still,It takes more than 45 min to see the output.Also you stated that the training model is trained once we will get the output in a milliseconds for rest of the images.
where the model files are stored and how to use the pre-trained model files.Every time i try to run the code it first get trained and print the residual points and then showing the output.
Pat,I am also having little confusion,Will you please clarify my doubts!
1.What is the accuracy difference between Elador versus yours?
Elador link - https://github.com/elador/FeatureDetection
Superviseddescent link - https://github.com/patrikhuber/superviseddescent
2.What are the features you had been added in your code against human sensing code?
SDM - http://www.humansensing.cs.cmu.edu/intraface/citations.html
How faster your code compare to human sensing code

Hi gopi, hi Anand,
Thanks for your replies and thank you Anand for all the details. I cannot reproduce the 45min training time at this point, which is a bit weird. I'll continue trying. Just to be sure - did you really compile superviseddescent with -fopenmp?
To answer your questions:

I do not know. But we'll upload results soon that show the accuracy of this implementation.
Intraface (CMU) do not provide source code, only a library interface. It's not open source, thus we can't know exactly. But the methods are quite similar.

It seems like you are both more interested in just running a landmark detection, and not training your own model. Is that correct? If yes, then bare with me for a few days more, our full model and easy-to-run example will be available soon :-)

Yes Patrick, you are right! will wait for some other days to get your full-model
Thanks,
Gopi

Hi Patrik,
I am also waiting for this, thanks!
Steven

i have no ideal  why i need about 12hours to train the data,then come  out  the out.png and landmark_regressor_ibug_68lms .i am using vs2013,opencv 2.4.8,boostboost_1_55_0 ,EIGEN3 with the debug mode ,why it takes so long ,why
Anand0793  can train it so fast ,where do mistake it? anyone can help me ,thx

Hi andyhx,
I tried in ubuntu 14.04 LTS 64 bit, Opencv 3.0 + OpenMP+ Boost 1.57 +Eigen 3, g++ 4.8.2
In ubuntu it take more than 1 hours to train the data, then it saves out.png and landmark_regressor_ibug_68lms.txt I raised the issue in github then patrick replied to compile with -fopenmp(gcc/clang), then i compile with -fopenmp it again also take more than 1 hour.
Again patrick replied I'll finally manage to add our pre trained model to the library in a couple of weeks!
can you please tries with OpenMp, let me know the status !!Hope will you execute it

I think there might be an issue with Eigen's parallelisation of PartialPivLU on Linux. I had a quick try yesterday and it didn't look like it was using more than one core. I'll investigate further once I've completed what I'm currently working on.
@andyhx Anyway, I think running Eigen in debug mode does not sound like a good idea when inverting such huge matrices.

@patrikhuber  @Anand0793     yes,thanks you  so much ,now with vs 2013  in   the release mode and using openmp is really fast. About 7 mins is enough to finish the train and predict. can't not believe  there  lies so much difference betweeen the release and debug mode,thanks again

how many training samples used in train step?@andyhx

@shangguanxiaohu  just the   images  that  demo provided ,i will try more ,how about  u

@shangguanxiaohu  what is  ur qq account ,we can  discuss more over it

1247768069@andyhx

Hi all,
@gopi1989 @Anand0793 @shangguanxiaohu @scadavid @andyhx
I've pushed a lot of changes to the devel branch and the RCR landmark detection model is ready to use.
To use it, compile rcr_detect from the examples/ directory and run it like:
rcr_detect -m path_to/face_landmarks_model_rcr_22.bin -f path_to_opencv/haarcascade_frontalface_alt2.xml -i your_image.png
A pre-trained model is available under examples/data/face_landmarks_model_rcr_22.bin. (I'll add one with more landmarks at a later time).
I will merge these changes into the master branch in the next few weeks, update the documentation, fix a few problems and so on, but the stuff in the devel branch is ready to try out.
The detection takes around 30ms per image at the moment.
Let me know how it goes.

Yes,Thanks for your needful help.will update the processing time in a couple of hours
Regards,
Gopi

Hi Patrik,
I build the supervised-descent code from https://github.com/patrikhuber/superviseddescent/tree/devel this link
I run the "rcr_detect" executable it works,Also detection is good for 2D frontal takes milliseconds per image.
Then,I run the rcr_track it also works but having doubt it is detection or tracking.

Hi Anand,
Thanks for the feedback! Cool that it worked. Yes, the tracking is not very smart at the moment - it'll be improved over the next few weeks.

@patrikhuber hi ,  when i trained about 800 pics that idug  provide ,it crashes. i am using ur rcr program  in a server .the sever has 16 G ram , 2.9 GHZ.it  causees memory exceptions  in  ur both previous andmark dection program  and current rcr program  . do u know why ?Anyone got same problems?

Hi @andyhx,
With how many landmarks were you training? It should definitely work with 20 to 40 landmarks. How much RAM was actually free on the server?
You can find more info and a link to the wiki with memory requirements and a few notes in #2.

HI @patrikhuber
thanks for answering my question.  i am training 22 landmarks using ur rcr program built by myself , there is about 12G ram free in the  server.i am training  lfpw  pics in  the lfpw\ibug_lfpw_trainset .would u please send u  a version  of  exe built on windows platform .so i can test out whether i made  mistakes in   building program or the other problems

A bit late, but anyway: I fixed the memory issues a while ago in 07e4b89a67fa0dd8e95b2d10d0cbe51ef5798b93, so the whole training doesn't use more than 0.5 to 2GB of RAM now. I'll update the wiki.

authors: Anand0793 andyhx gopi1989 patrikhuber scadavid shangguanxiaohu

repo: patrikhuber/superviseddescent


text:
add backwards compatible fix for paho2

This is due to paho-mqtt just releasing 2.0.0 which has a breaking change listed here.

Any chance that you merge this?


text:
Css is not updated

First of all, I have got pattern-lab installed on a branch of my local repository on my Mac.
So I changed the $font and $font-secondary variable in the _variables.scss file. After this, if I run console sass on the style.scss file in the output the fonts are still the old ones. If I run the Script generateSiteWithCSS also nothing changes.
What can be the Problem?

Hey @ChristophGerl,
It's tough to see exactly what you're struggling with, but I'd recommend opening the pattern in a new window (view > open in new window) and refreshing a few times. Sometimes the page gets cached and new updates don't show right away. Once the cache is flushed then you should be able to refresh the page in the context of the Pattern Lab shell and see the changes. Hope that works!

authors: ChristophGerl bradfrost

repo: pattern-lab/patternlab-php


text:
feat: Add support for empty local variables

Link(s) to demo pages where this element can be viewed:

Demo

For component fixes and features

Link to issue detailing the request

What has changed and why

Refactor of PFE functions responsible for outputting correct variables and fallbacks such that local variables are empty by default

Testing instructions
Be sure to include detailed instructions on how your update can be tested by another developer.

Ensure that components visually look the same
Spot check various existing local variables to make sure they still work
Check theme variables to ensure they still work.

Browser requirements
Your component should work in all of the following environments:

[ ] Latest 2 versions of Edge
[ ] Internet Explorer 11 (should be useable, not pixel perfect)
[ ] Latest 2 versions of Firefox (one on Mac OS, one of Windows OS)
[ ] Firefox 60.7.2 (or latest version for Red Hat Enterprise Linux distribution)
[ ] Latest 2 versions of Chrome (one on Mac OS, one of Windows OS)
[ ] Latest 2 versions of Safari
[ ] Galaxy S9 Firefox
[ ] iPhone X Safari
[ ] iPad Pro Safari
[ ] Pixel 3 Chrome

Ready-for-merge Checklist
Check off items as they are completed.  Feel free to delete items if they are not applicable to your PR.

[x] Expected files: all files in this pull request are related to one request or issue (no stragglers or scope-creep).
[x] Browser testing passed.
[x] Documentation (README.md, WHY.md, etc.) updated or added.
[ ] Link to the demo recording:

https://rally1.rallydev.com/#/270861059696d/detail/userstory/390981143804

Just a note that we will need pfe-dropdown and pfe-jump-links sass files updated in this branch, right now some styles are broken
https://5ed544ccfcb5b00006c47bab--happy-galileo-ea79c4.netlify.app/elements/pfe-jump-links/demo/
https://5ed544ccfcb5b00006c47bab--happy-galileo-ea79c4.netlify.app/elements/pfe-dropdown/demo/

Issue #100

@starryeyez024 Ready for review!

@castastrophe  I think maybe the mixin responsible for printing the broadcasted colors per theme is broken? I'm seeing issues with most components re: on=dark and on=saturated
Pile of handy links for mahself:

pfe-card
pfe-band
pfe-cta
pfe-accordion
pfe-tabs
pfe-content-set
pfe-navigation
pfe-jump-links

pfe-navigation overrides it's own local variable for font size, such that --pfe-navigation__trigger--FontSize doesn't really do anything

but I'm thinking this is a separate bug, yeah?

@castastrophe I think maybe the mixin responsible for printing the broadcasted colors per theme is broken? I'm seeing issues with most components re: on=dark and on=saturated

This is fixed now!  Thanks for catching that.  Typo in the broadcasted function.

pfe-navigation overrides it's own local variable for font size, such that --pfe-navigation__trigger--FontSize doesn't really do anything

but I'm thinking this is a separate bug, yeah?

Yeah I didn't mess with lightdom files and that's where that style is coming from.

@castastrophe - The $repo variable makes reading the Scss difficult. I see what you're doing but I feel like a global find and replace wouldn't be so bad if we had to change the pfe prefix (which I don't think we'll need to do). Can we back that part of the change out?

I love that idea, thanks!
On Thu, Jun 25, 2020, 9:41 AM [ Cassondra ] notifications@github.com
wrote:

@castastrophe commented on this pull request.
In elements/pfe-avatar/src/pfe-avatar.scss
https://github.com/patternfly/patternfly-elements/pull/854#discussion_r445566906
:

@@ -1,35 +1,38 @@
@import "../../pfe-sass/pfe-sass";

-:host {

--pfe-avatar--width: 128px;
+$LOCAL: avatar;
+$LOCAL-VARIABLES: (

size: 128px

I originally came to this branch with a mindset to tidy up variables for
1.0 which is where a few of the renames happened along the way. What would
you think of my building in a backwards-compatibility map:
// TODO: This will be removed at 1.0
$backwards-compatibility: (
width: pfe-local(size)
);
$LOCAL-VARIABLES: map-deep-merge($LOCAL-VARIABLES, $backwards-compatibility);
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/patternfly/patternfly-elements/pull/854#discussion_r445566906,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADPRH4GMBG2WU63HFKN4QLRYNHZZANCNFSM4MXI6W5A
.

repo: patternfly/patternfly-elements


text:
Can't resolve font files in sass build

Hello,
I'm using webpack to build my application
{
  test: /\.scss$/,
  use: [
    { loader: "style-loader" },
    { loader: "css-loader" },
    {
      loader: "sass-loader",
      options: {
        includePaths: [
          path.resolve(
            __dirname,
            "node_modules/@patternfly/patternfly-next"
          )
        ]
      }
    }
  ]
}

I try to import in my App.scss file patternfly-base.scss file:
$pf-global--enable-reset: false !default;
@import "~@patternfly/patternfly-next/patternfly-base.scss";
@import "~@patternfly/patternfly-next/components/Button/styles.scss";

Got a lot of errors like this one:
./src/App.scss (./node_modules/css-loader!./node_modules/sass-loader/lib/loader.js??ref--6-2!./src/App.scss)
Module not found: Error: Can't resolve './assets/fonts/overpass-mono-webfont/overpass-mono-bold.eot' in '/home/guillaume/workspace/dci-dev-env/dci-ui/src'

Any idea how to solve this?

Hi @guillaumevincent, try defining the following sass vars;
$pf-global--font-path: '../../node_modules/@patternfly/patternfly-next/assets/fonts/'; $fa-font-path: '../../node_modules/@patternfly/patternfly-next/assets/fonts/webfonts/'; $pf-global--image-path: '../../node_modules/@patternfly/patternfly-next/assets/images/';
Of course adjust the paths to work based on your applications directory structure. Looks like the problem is that you're referencing the import from /home/guillaume/workspace/dci-dev-env/dci-ui/src, and because $pf-global--font-path is still set to its default value, sass-loader is looking for the font in .../dci-dev-env/dci-ui/src/assets/fonts/....
By pointing those vars to where these files exist, either under node_modules or in a custom directory you craft together yourself, the references should then resolve. I imagine you'll need the images and FA icons as well, so I included similar examples of how to define those.
https://github.com/patternfly/patternfly-next/blob/master/src/patternfly/sass-utilities/scss-variables.scss#L105
From what I've seen so far, options.includePaths property isn't required in your webpack config for patternfly-next sass to work, that was a PF3 sass thing. Are you using PF3 at all? If not, I'd be interested to know if you can drop that custom sass-loader config. I will update our docs/readme with better info on exactly this subject after you're squared away here.

@guillaumevincent  - we are investigating a bit more about the paths in pf4 - for now, I'd recommend using the variables @seanforyou23 mentioned but depending on how you are compiling, there are a few things to keep in mind.  The paths in the root are set for our compiled patternfly.css (and work from there) -if you are pulling in component level css or sass, you'll have to change the pathing system to work for you.
Do you have a sample create-react-app set up anywhere we can collaborate on?  If not, we'll be creating one w/patternfly-next in the next couple of days to work through this together on.

@dgutride if so, we need to update our upgrade guide https://pf-next.com/upgrade-guide

So my solution:

install create-react-app version 2
install patternfly-next, react-core and node-sass
replace App.css with App.scss

$pf-global--font-path: '~@patternfly/patternfly-next/assets/fonts/';
$fa-font-path: '~@patternfly/patternfly-next/assets/fonts/webfonts/';
$pf-global--image-path: '~@patternfly/patternfly-next/assets/images/';
@import "~@patternfly/patternfly-next/patternfly-base.scss";
@import "~@patternfly/patternfly-next/components/Button/styles.scss";

edit App.js

import React, { Component } from 'react';
import {Button} from "@patternfly/react-core"
import './App.scss';

class App extends Component {
  render() {
    return (
      <div className="App">
        <Button>test</Button>
      </div>
    );
  }
}

export default App;

Note:

create-react-app version 1 build doesn't works. An issue with button.css.js
patternfly-base.scss is enough to get the css for button

authors: dgutride guillaumevincent seanforyou23

repo: patternfly/patternfly-next


text:
README.md updates

Would be handy to have the "Getting Started" heading caught up to make it easy to pull the repo, build & see where it is at currently.
Thanks!

Yes. Working on porting an initial set of components. We have lots of testing to do, jsDoc to create, etc. Not quite ready for prime time, just yet.

@benjaminapetersen - initial readme created (along with an alpha release at 0.0.3 - moving to closed, please try it out and let us know what you think

authors: benjaminapetersen dgutride dlabrecq

repo: patternfly/patternfly-ng


text:
Laravel Updater

This pull request includes updates for the recent minor version release of Laravel as well as updates to your package dependencies. Feel free to commit any additional changes to the shift-ci-v7.16.1 branch.
Before merging, you need to:

Checkout the shift-ci-v7.16.1 branch
Review all pull request comments for additional changes
Run composer update
Test your application (no tests?)

:warning: You are running version 5.3.4 of guzzlehttp/guzzle. The latest version is 6.5.4. You should review this dependency to see if you can upgrade to the latest version.

:warning: You are running version 1.0.10 of laravel/tinker. The latest version is 2.4.0. You should review this dependency to see if you can upgrade to the latest version.

:information_source: You are running an older version of Laravel. The latest version is 7.16.1. Run the Laravel 7.x Shift to upgrade to the latest version of Laravel.

:warning: You are running version 0.14.0 of league/fractal. The latest version is 0.19.2. You should review this dependency to see if you can upgrade to the latest version.

:warning: You are running version 3.9.3 of ramsey/uuid. The latest version is 4.0.1. You should review this dependency to see if you can upgrade to the latest version.

repo: patwebrussell/airflix


text:
Fix Manufacturer Specific Data With Only Company ID

Fix bug on iOS where devices that only have the company ID but no
other manufacturer specific data have the key omitted in
AdvertisementData.manufacturerData.

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

authors: CLAassistant toddwilson


text:
Added support for debugging Node.js code

Added support for debugging Node.js code:
services.AddJsEngine(builder =>
{
    builder.UseNodeRenderEngine(options =>
    {
        :
        options.LaunchWithDebugging = true;
        options.DebuggingPort = 9229;
    });
    :
});

I will get this pushed out this evening.

authors: NillDk pauldotknopf

repo: pauldotknopf/JavaScriptViewEngine


text:
runipy hangs on --html option

Runipy is writing the html file but does not exit.
How to reproduce:

install CentOS release 6.5 (Final)
build Python 2.7.8 from source
pip install
Jinja2==2.7.3
MarkupSafe==0.23
Pygments==1.6
backports.ssl-match-hostname==3.4.0.2
certifi==14.05.14
ipython==2.2.0
psycopg2==2.5.4
pyzmq==14.3.1
runipy==0.1.1
tornado==4.0.2
wsgiref==0.1.2
start ipython notebook
create new notebook tom_hangs with one cell containing: print "tom hangs"
run runipy tom_hangs.ipynb --html

Besides that, I think, you wanted to append the extension 'html' to the html-report in line 101 of main.py (see https://github.com/paulgb/runipy/blob/master/runipy/main.py#L101).

Merged #47, thanks @tfrench

repo: paulgb/runipy


text:
Name property not included in new column after insertColumn

When inserting a new column the 'name' is not included. That appears to be important for the display of data (ordering of columns). If the data is saved and try to reload on another sheet, it is not showing in the same way.
From the config:
"columns":[
  {"type":"text","name":"0","source":[],"options":[],"editor":null,"allowEmpty":false,"title":"","width":50,"align":"center"},
  {"type":"text","source":[],"options":[],"width":50,"align":"center"},
  {"type":"text","name":"2","source":[],"options":[],"editor":null,"allowEmpty":false,"title":"","width":50,"align":"center"},
  {"type":"text","name":3,"source":[],"options":[],"editor":null,"allowEmpty":false,"title":"","width":50,"align":"center"}

 ],

Above the second row was an insert and 'name' is not present

This behavior is correct, and the name should be added using oninsertrow() in case you need. This is because the name is not necessarily a sequence number. If you are using it as a number, I suggest you to remove the name at all.

repo: paulhodel/jexcel


text:
infinite scroll callback to masonry/overlay

Currently using infinite scroll with a callback to masonry.  Each masonry item brings up an overlay when clicked.  Overlays (via jQuery tools) work fine with the existing elements but not the new elements.  Not sure how to structure the callback to both masonry and overlay.

Your events aren't attached to the new elements - you need to look in to the "on" event handler and event delegation to handle your click events in the parent element and not on the individual element basis you probably currently have them on (i.e. $('.element').click will fail for any .element that is added dynamically, but $('.element_container').on('click', '.element', funciton...); should work.

Worked great, thanks!

repo: paulirish/infinite-scroll


text:
🛑 Hack the Gibson is down

In 5fd51a1, Hack the Gibson (https://gibson.paulynomial.com) was down:

HTTP code: 530
Response time: 113 ms

Resolved: Hack the Gibson is back up in ebe612a.

repo: paulkiernan/paulynomial-uptime


text:
🛑 Paulynomial (index) is down

In 7ffdd44, Paulynomial (index) (https://paulynomial.com) was down:

HTTP code: 530
Response time: 91 ms

Resolved: Paulynomial (index) is back up in 93a4b5a.


text:
Mac: watcher seems to be case sensitive when watching a folder?

I have a folder called /Users/bpasero/Development/express and install a chokidar watcher on it. Everything works fine. If I do the same with lowercase in the beginning (/users/bpasero/Development/express), I am not getting any events. Is that intentional?

"Intentional" may not quite be the right word - it's how the file system works. Chokidar doesn't do anything special to try to allow for case-insensitive path lookups.

@es128 do you know at which layer this actually "breaks"? If I use node fs APIs, the case does not matter for a file system that is case-preserving but case-insensitive. I would probably expect the same from a file watching library :+1: .

I don't know, this isn't something I've explored before. If there are simple changes we can make within chokidar to fix this, I'd be supportive of that.

Ok, lets just hope it is not deep down in native fsevents.

@es128 I traced it down to this check: https://github.com/paulmillr/chokidar/blob/master/lib/fsevents-handler.js#L43
Basically you only emit the file event if the path is identical in case. This check is not making sense in environments where the file system is case-insensitive imho. Any reason this check is there in the first place?

Any reason this check is there in the first place?

Yes, it has to do with efficient utilization of underlying fsevents instances to avoid hitting system limits in cases where many watcher instances are spawned for similar paths.
This also explains why I wasn't able to reproduce the problem in a simple test - it can only occur with multiple instances watching overlapping parts of the file tree.
We're going to need some test coverage here. Removing the condition would lead to problems, but all the tests currently pass regardless.
Then coercing to lowercase in that comparison to solve the case sensitivity should be easy enough.

Then coercing to lowercase in that comparison to solve the case sensitivity should be easy enough.

Well, it can be more complex than that (and upper case should be prefered to lower case). https://nodejs.org/en/docs/guides/working-with-different-filesystems/#be-prepared-for-slight-differences-in-comparison-functions is a good read on the subject.

This also explains why I wasn't able to reproduce the problem in a simple test - it can only occur with > multiple instances watching overlapping parts of the file tree.

In my test case I was just opening chokidar on one folder, are you saying that there are multiple instances of fsevents created in that case?

@nono Thanks for that reference. It might be tricky to slide a fs.realPath(resolvedPath, ... call in there, but I'll consider it. At worst, I'll defer to .toUpperCase().

@bpasero I noticed that you cross-linked from an issue with VS Code. I was assuming that it has opened watcher instances somewhere else in the process looking at https://github.com/paulmillr/chokidar/blob/master/lib/fsevents-handler.js#L60-L62, but now that I look again I see that I was mistaken. filteredListener is used upon the initial creation of an fsevents instance as well.
But nonetheless, I was not able to reproduce the issue in a simple test using example.js
λ node example.js
addDir /users/eshanker/Code/chokidar/coverage
addDir /users/eshanker/Code/chokidar/lib
addDir /users/eshanker/Code/chokidar/test-fixtures
add /users/eshanker/Code/chokidar/CHANGELOG.md
add /users/eshanker/Code/chokidar/README.md
add /users/eshanker/Code/chokidar/appveyor.yml
add /users/eshanker/Code/chokidar/example.js
add /users/eshanker/Code/chokidar/index.js
add /users/eshanker/Code/chokidar/package.json
add /users/eshanker/Code/chokidar/test.js
Ready
change /users/eshanker/Code/chokidar/example.js
change /users/eshanker/Code/chokidar/example.js

In your case, something has to have caused a disparity between the path reported with the event and the user-entered absolute path.

Looking at the raw events, fsevents is actually reflecting back the incorrect casing supplied by the user in its events. Watching a symlink also didn't break it.
RawEvent: change /USERS/ESHANKER/CODE/CHOKIDAR-LINK/lib/fsevents-handler.js
@bpasero can you help figure out what's happening differently in your case?

@es128 actually when I was looking into this issue I was just using a simple stand alone node application:
var watcher = chokidar.watch('/users/bpasero/Development/express', {
    ignored: /[\/\\]\./,
    persistent: true
});

On disk the path is actually with an uppercase: /users/bpasero/Development/express
This alone is enough for me to reproduce that the event is emitted from fsevents, but not emitted to the chokidar user because of the filter:

I am in a breakpoint after duplicating a file in the directory and you can see in the variables to the left that fullPath is /Users/bpasero/Development/express/History copy.md and resolvedPath is /users/bpasero/Development/express. So the filter condition will make this event not be emitted.

For some reason I get a different result when doing effectively the same thing, but it doesn't matter - it's clear what needs to be done to fix it.
RawEvent: change /USERS/ESHANKER/CODE/CHOKIDAR-LINK { curr:
   { dev: 16777220,
     mode: 16877,
     nlink: 18,
     uid: 510,
     gid: 600,
     rdev: 0,
     blksize: 4096,
     ino: 1150998,
     size: 612,
     blocks: 0,
     atime: Fri Dec 18 2015 10:27:52 GMT-0500 (EST),
     mtime: Fri Dec 18 2015 10:27:52 GMT-0500 (EST),
     ctime: Fri Dec 18 2015 10:27:52 GMT-0500 (EST),
     birthtime: Sat Mar 21 2015 21:55:02 GMT-0400 (EDT) },
  prev:
   { dev: 16777220,
     mode: 16877,
     nlink: 17,
     uid: 510,
     gid: 600,
     rdev: 0,
     blksize: 4096,
     ino: 1150998,
     size: 578,
     blocks: 0,
     atime: Fri Dec 18 2015 10:27:45 GMT-0500 (EST),
     mtime: Fri Dec 18 2015 10:11:03 GMT-0500 (EST),
     ctime: Fri Dec 18 2015 10:11:03 GMT-0500 (EST),
     birthtime: Sat Mar 21 2015 21:55:02 GMT-0400 (EDT) } }
add /USERS/ESHANKER/CODE/CHOKIDAR-LINK/index Copy.js

it's clear what needs to be done to fix it.

So would you change the filter to to a comparison in uppercase? I think the hard part is that in theory someone could run with HFS+case-sensitive on Mac so maybe this even needs to be configurable option in Chokidar to control? And certainly on Linux case-sensitive file systems are common.

So would you change the filter to to a comparison in uppercase?

Hopefully not, I'd first want to try to solve it with a better option. Some thoughts:

Run a string transform that ensures the user's original casing on the reported path is preserved, even if it came out differently from the raw event, before doing the comparison.
Utilize fs.realpath - although I may have just ruled this out as a possibility since it also seems to be preserving whatever case the user supplies when I tried it locally just now.

@es128 from what I know there is no function to get the real path with the casing as it is defined in the file system. The only way I think you can do this is by repeated fs.readDir() calls for each segment of the path because that is returning the proper case.

Yes, I'm coming to that realization... So hopefully there's a workable solution somewhere in that first idea.
If not, I am ok with going to the .toUpperCase() solution. Even in the cases of strict-case file systems you pointed out, it's hard to imagine where that solution would cause a problem for chokidar users.
I don't think doing readdirs up through the parents will be something we'd want to pursue.

Right, I also think this solution is good for the 99% case. The only gotcha is that node started to return a different Unicode normalization form on Mac. I think this topic is described in that document as well. To compare paths you would need to normalize its Unicode form if they differ.

@paulmillr @es128 can this be looked at again? The reality for Mac users on VS Code (and pretty much any chokidar user on Mac) today is that all file events are broken when you open a folder (from the command line) with wrong casing. The workaround for me is to detect the bad casing and rewrite the paths in the events flowing out of chokidar (odd).
One issue I noticed is that when I do the toUpperCase trick in https://github.com/paulmillr/chokidar/blob/1.4.0/lib/fsevents-handler.js#L44 I am getting the event, however it will incorrectly be detected as added even though I just changed a file.
The repro is to open chokidar on a path with wrong case and modify a file within.

@bpasero unfortunately in my past attempts I was not able to repro locally. It does not appear to impact Mac users universally, there seems to be some other system setting having an impact, but I don't know where to find it.

@es128 wow that is weird. I have a simple reproducible case here. Just checkout latest of chokidar, add a new *.js file with this script and run it with node (5.10.0):
var chokidar = require('./');
var fs = require('fs');
var path = require('path');

var base = __dirname.toUpperCase();
chokidar.watch(base, {ignored: /[\/\\]\./, ignoreInitial: true}).on('all', (event, path) => {
  console.log(event, path);
});

setTimeout(function() {
  fs.writeFileSync(path.join(__dirname, 'test'));
}, 1000);

On my Mac (10.11.4) I am not getting anything printed to the console. Are you?

Yup. 10.10.5
λ node bpasero.js
change /USERS/ESHANKER/CODE/CHOKIDAR/test
change /USERS/ESHANKER/CODE/CHOKIDAR/bpasero.js

@es128 very weird, could it be the OS X update?
My disk info:
~/Development/Microsoft/monaco> diskutil info /
   Device Identifier:        disk1
   Device Node:              /dev/disk1
   Whole:                    Yes
   Part of Whole:            disk1
   Device / Media Name:      APPLE SSD SM0512F

   Volume Name:              HD

   Mounted:                  Yes
   Mount Point:              /

   File System Personality:  Journaled HFS+
   Type (Bundle):            hfs
   Name (User Visible):      Mac OS Extended (Journaled)
   Journal:                  Journal size 40960 KB at offset 0xe8f000
   Owners:                   Enabled

   Content (IOContent):      Apple_HFS
   OS Can Be Installed:      Yes
   Recovery Disk:            disk0s3
   Media Type:               Generic
   Protocol:                 PCI
   SMART Status:             Not Supported

   Total Size:               499.0 GB (499046809600 Bytes) (exactly 974700800 512-Byte-Units)
   Volume Free Space:        116.1 GB (116098367488 Bytes) (exactly 226754624 512-Byte-Units)
   Device Block Size:        512 Bytes
   Allocation Block Size:    4096 Bytes

   Read-Only Media:          No
   Read-Only Volume:         No

   Device Location:          Internal
   Removable Media:          No

   Solid State:              Yes
   Virtual:                  Yes
   OS 9 Drivers:             No
   Low Level Format:         Not supported

   This disk is a Core Storage Logical Volume (LV).  Core Storage Information:
   Fusion Drive:             No
   Encrypted:                No

This has been reported since before El Capitan, hasn't it? I don't see any impactful differences in my disk config. One notable thing is that I have disk encryption on, but it seems like a stretch that this issue hinges there.

@es128 not sure to be honest, might be. Would be interesting to get someone else on this to reproduce :). I know that a colleague has the same issue, but he sits on the same OS.
And you are also on node.js 5 right?

Yes, I was using node v5.6.0 just now to test.

Well actually it was for sure happening with 4.x already, given how old this report is.

Right, I highly doubt this has anything to do with node version or any part of the stack we have influence over. It's something at a lower level in the system, and the only thing we can possibly do is pursue a workaround using toUpperCase normalization or something like that. But without being able to reproduce, I'd have a tough time searching for a reliable workaround on my own.

I wonder if this happens at the layer of native fsevents where you get the path reported back. In your case I would expect fsevents to give the uppercase path and in my case the real path as it is on disk.

That does appear to be what is happening at least at the level of the fsevents node bindings we are using here.

@es128 I suggest we try to come up with a test and let it run on travis with different configurations to see if the OS X update broke this.
Can you try to run the following test on your machine to see if it succeeds or not? I added the following test within the describe('watch individual files', function () test suite:
it('should detect changes (UPPERCASE)', function (done) {
  var spy = sinon.spy();
  var testPath = getFixturePath('change.txt');
  var testPathUppercase = testPath.toUpperCase(); // UPPERCASE !
  watcher = chokidar.watch(sysPath.dirname(testPathUppercase), options)
    .on('change', spy)
    .on('ready', function () {
      fs.writeFile(testPath, Date.now(), simpleCb);
      waitFor([spy], function () {
        spy.should.have.always.been.calledWith(testPath);
        done();
      });
    });
});

In order to run travis with multiple OS X releases, you can use their matrix option:
matrix:
  include:
    - os: osx
      osx_image: xcode7.3
      node_js: "5"
    - os: osx
      osx_image: xcode7.2
      node_js: "5"
    - os: osx
      osx_image: xcode7.1
      node_js: "5"
    - os: osx
      osx_image: xcode7
      node_js: "5"
    - os: osx
      osx_image: xcode6.4
      node_js: "5"
    - os: osx
      osx_image: beta-xcode6.3
      node_js: "5"
    - os: osx
      osx_image: beta-xcode6.2
      node_js: "5"
    - os: osx
      osx_image: beta-xcode6.1
      node_js: "5"

I was bitten by something similar (probably not the same) to this on Windows, just documenting my experience:
watch('.../folder/*.txt')

Works for files with extensions .txt but not .TXT (the glob don't seem to be case insensitive in regards to file extension)

authors: bpasero es128 nono ryanelian

repo: paulmillr/chokidar


text:
fix startup on pthreads

Emscripten doesn't run preRun, onRuntimeInitialized or postRun on
pthread workers.  it sets insantiateWasm to a custom callback that
receives the wasm code using postMessage from the main thread, so we
don't need our instantiateWasm, either.

I did something similar. We could close this one

authors: lambdageek pavelsavara

repo: pavelsavara/runtime


text:
Develop

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
All new code requires tests to ensure against regressions.
If pull request breaks tests it would not be merged.

Description of the Change

Alternate Designs

Benefits

Possible Drawbacks

Applicable Issues

Hi @MICHAELonPender
Thank you for your contribution! Would you mind squashing commits into one?


text:
ci: Wait for project workflow success

After generating the project, we could actually push it to our dummy repo (pawamoy-testing), triggering its own CI workflow. Then we could use GitHub's API to identify this workflow run and wait for it to succeed.

list workflow runs for a repo: https://docs.github.com/en/rest/actions/workflow-runs?apiVersion=2022-11-28#list-workflow-runs-for-a-repository
get workflow run: https://docs.github.com/en/rest/actions/workflow-runs?apiVersion=2022-11-28#get-a-workflow-run (use status or conclusion)

Thanks for the heads-up on Mastodon. I mentioned/tracked this issue over in my Discussion post https://github.com/blakeNaccarato/copier-python/discussions/402, as I'm interested in implementing a similar flow.
TIL that Issue mentions in Discussions don't automatically back-reference to the Issue topic! That might affect my consideration of my template's Discussions-first approach, with Issues as actual actionable work items, if Discussions don't ping/link their mentions.
Anyways, I'm getting off-topic. I am a bit pre-occupied with trying to finish up thesis work, but if you're looking for a set of eyes to review a PR or work-in-progress on this, drop me a line.

TIL that Issue mentions in Discussions don't automatically back-reference as mentions on the Issue topic!

Yep, that is very annoying.

Anyways, I'm getting off-topic. I am a bit pre-occupied with trying to finish up thesis work, but if you're looking for a set of eyes to review a PR or work-in-progress on this, drop me a line.

I'll keep you posted! All the best for your thesis work :smile:

I appreciate the peek behind the curtain! I never bother to squash, and haven't decided whether I should be doing so, so my repos end up with absolute tons of commits, even when merging relatively small PRs. So I always feel I'm doing a lot sloppier work in comparison to these neat PRs 😅

authors: blakeNaccarato pawamoy

repo: pawamoy/copier-uv

license: ISC


text:
update new Flux

replace all Flux@epoches with for loop, since Flux@epoches is no longer available in the new version of Flux julia package.

Thanks!
Could you please update the text in the notebooks so that the performance in the notebook texts match the numbers from the training?


text:
カードフォームの追加属性項目（メール・電話番号）をサポートする

カードフォームにメールアドレス・電話番号の項目を追加
iOS・AndroidのSDKをそれぞれ 2.0.0 に更新し、カードフォームの追加属性項目 を表示できるようにしました。

https://github.com/payjp/payjp-ios/releases/tag/2.0.0
https://github.com/payjp/payjp-android/releases/tag/2.0.0

PayjpCardForm.startCardForm(options?: CardFormOption) の引数が拡張され、追加属性項目に関する設定を渡せるようになっています。
PayjpCardForm.startCardForm({
    cardFormType: 'multiLine',
    extraAttributes: [{ type: 'email' }, { type: 'phone' }],
});

CardFormOption に追加された extraAttributes によってフォームの項目を制御します。デフォルトではメールアドレスと電話番号いずれも項目を表示し、いずれかの入力が必須となります。
// preset または presetRegion/presetNumber によって初期値を設定可能
type ExtraAttributeEmail = { type: 'email'; preset?: string };
type ExtraAttributePhone = { type: 'phone'; presetRegion?: string; presetNumber?: string };
/**
 * カードフォームの追加属性
 */
export type ExtraAttribute = ExtraAttributeEmail | ExtraAttributePhone;

https://github.com/user-attachments/assets/4be7a54f-2670-4eb2-a872-915e0f5b9fd7
各種依存とサンプルコードの更新

開発用のReact Nativeバージョンを 0.74.5 に引き上げ（これは現時点の npx create-expo-app@latest ）
TypeScriptのバージョンアップ
ESLintの設定やTypeScriptの設定はなるべくReact Native本体と揃えるようにしました。（一部差分が大きすぎるものは妥協）
サンプルアプリをexpoで作り直しました。

iOS で CardIO ライブラリの暗黙的な依存の廃止

https://github.com/card-io/card.io-iOS-SDK はすでにメンテされておらず、Apple Siliconのarm64なiOSシミュレータで正常にビルドできません。
これまでのバージョンの payjp-react-native-plugin ではiOS・Androidともにカードをスキャンする機能をデフォルトでオンにするためにプラグイン自体に依存が含まれていました。
iOSの場合ワークアラウンドが必要になるため、デフォルトで依存に含めないようにしました（Androidは変更なし）。
スキャン機能を追加したい場合は、アプリ側で依存を追加する必要があります。

/docs の更新は npm run version で同時に実行しているので今回に入れてないです！

repo: payjp/payjp-react-native-plugin


text:
Tsconfig alias issue on generate:types

Bug Report
I am getting an annoying error on one of the first things I have tried with merging in concepts from your public website repo at - https://github.com/payloadcms/website-cms.

When trying to generate the types for the payload app using an alias defined in tsconfig:
{   "exclude": ["node_modules", "dist", "build"],   "compilerOptions": {     "rootDir": "./src",     "outDir": "./dist",     "baseUrl": ".",     "paths": {       "@access/*": ["./src/access/*"],       "@blocks/*": ["./src/blocks/*"],       "@collections/*": ["./src/collections/*"],       "@fields/*": ["./src/fields/*"],       "@globals/*": ["./src/globals/*"],       "@scripts/*": ["./src/scripts/*"],       "@utilities/*": ["./src/utilities/*"],       // Tell TS where to find your generated types       // This is the default location below       "payload/generated-types": ["./src/payload-types.ts"]     }   },   "include": ["src"] }
It errors, removing the @ in the import and replacing with a standard relative route works. VS Code is fine with mapping the modules using the aliases, it only errors once trying to run 'generate:types'.
Steps to Reproduce

Duplicate https://github.com/payloadcms/website-cms
Add in tsconfig with path alias
Modify any import from '../access/isAdmin' to '@access/isAdmin'
Run 'yarn generate:types'

Or

Pull https://github.com/HQ92/payload-alias
Run 'yarn generate:types'

Other Details
Payload version - 1.6.7. Yarn version 1.22.19.

Hey there - I see what's happening here. Give us a bit and we will figure out a solution. Thanks for the report!

Hey @HQ92 — thanks again for the report. This is now fixed and custom TS paths are now working as you'd expect.
This will be released in our next patch version tomorrow!

That's great! Really liking PayloadCMS as I've always stayed away from most CMSs if possible because of the way they had to be setup and the restrcitions they imposed. Payload seems to be a much nicer way to move forward with full typescript support from front to back. The only thing I haven't quite worked out how to get working yet is grabbing Payload data on the server using TRPC and the NextJs 13 app directory. But I feel that's more of a TRPC issue with Next 13.
Thanks again.

repo: payloadcms/payload