[Bug][iOS only] TouchEffect NativeAnimation doesn't reset animated properties when used on ScrollView

Description
When using TouchEffect NativeAnimation with a view that's positionend on a ScrollView or SwipeView, the animation doesn't reset the animated properties reliable.
As soon as a scroll of the ScrollView occurs during the tapevent, the animation is interrupted in the middle and not reset.

Steps to Reproduce

Start the XCT.Sample project and go to the TouchEffectPage.
Scroll down to the button that's labeled 'Image | Native'.
Tap the button, hold the tap and pan/scroll.

Expected Behavior
The changed properties of the UIView.AnimateAsync()-Animation should be reseted.
Actual Behavior
The FadeOutEffect (Opacity-Change) remains.
When using the NativeAnimationColor, the Color-Change remains.
Basic Information

Version with issue: Newest

Last known good version: None

IDE: Visual Studio 2019 16.10.2 Windows

Platform Target Frameworks:

iOS:  14.5

We have the same problem. The issue is caused by this line
https://github.com/xamarin/XamarinCommunityToolkit/blob/365b0cf316afded845ca094b1abe1d8357d9ab64/src/CommunityToolkit/Xamarin.CommunityToolkit/Effects/Touch/PlatformTouchEffect.ios.cs#L275
When removing it, I cannot reproduce the issue anymore.
@AndreiMisiukevich any idea how to fix this?

@Huaba93 thanks for the investigation) The fix is on its way ;)


Feedback - Provide simplified YAML syntax for common cases

While I understand that in many cases we will be using a tool to auto-generate the OAI specification there are cases where we build them by hand such as prototyping a new API surface in an online editor. It would be nice if the YAML syntax allowed for a simpler syntax for some common cases.
Note: I'm proposing new alternative syntax for common cases. I do not recommend the existing format be changed but rather parsers be enhanced to detect simpler syntax cases and remap them automatically to the more verbose syntax.
I'm aware of a couple after having prototyped a couple new APIs.

Arrays of objects. Currently the YAML syntax is this:someProperty:
   type: array
   items:
      $ref: 'path to schema'

For the (common) case of an array of pre-defined or schema-defined types it would be nice if we could just combine all this into type and let it be equivalent to the above.
someProperty:
   type: array('path to schema')
   #or
   type: 'path to schema'[]

Common variants could also possibly be shortcut as well whereas the full syntax is available for more complex cases.

Schema refs. Currently the YAML synax for a schema reference is this:  content:
     application/json:
        schema:
           $ref: 'path to schema'

For the common case of a reference object then allow it to be specified directly on the schema object.

content:
   application/json:
      schema: 'path to schema'

Or maybe even shorter.
content:
   application/json: 'path to schema'

Required properties. It feels very odd to separate property definitions from their required state.required:
   - name
properties:
   - name:
          type: string

Especially since required is a validation concept and validation properties are already on the property definition. Allow the required state of a property to be included as part of the property definition. This keeps them together and lessens the likelihood of someone forgetting them.
properties:
  - name:
        type: string
        required: true

Multiple content response fallthrough. In many cases an API will return a consistent error model for all non-success status codes. The only thing that may differ is the description of the status code.

 responses:
      '400':
         description: Bad request.
         content:
              application/json:
                  schema:
                      $ref: 'path to schema'
      '404':
         description: Item not found.
         content:
              application/json:
                  schema:
                      $ref: 'path to schema'

It would be nice to be able to combine several of them into one with just differing descriptions. Sort of like fallthrough in switch statements
response:
   '400': Bad request.
   '404': Item not found.
      content:
            application/json:
                schema:
                    $ref: 'path to schema'

Common tags. Currently the tags element is on the individual operations. Since most of the time all the operations on a path are related it makes sense to be able to have a higher level tag on the path and then override it on a lower level operation if needed.  'products/{id}'
  tags: [ 'Products' ]
  get: ...
  post: ...

This issue has been inactive for some time so it will be closed.


Australian numbers with 1300 prefix and more than 6 digits

Country: Australia
Example number(s) and/or range(s):

+61 1300 3278 929

Number type ("fixed-line", "mobile", "short code", etc.): "fixed-line", "shared cost"
For short codes, cost and dialing restrictions:
Where or whom did you get the number(s) from: https://www.fastway.com.au/sydney/
Authoritative evidence (e.g. national numbering plan, operator announcement):

These Australian numbers are called smartnumbers. They're supposed to start with 1300 followed by 6 digits. However, numbers can be longer, but only the 6 first digits will be taken into account.
https://www.thenumberingsystem.com.au/#/about-smartnumbers

Link from demo (http://libphonenumber.appspot.com) showing error:

http://libphonenumber.appspot.com/phonenumberparser?number=%2B61+1300+3278+929

🙌 Many thanks for your help!! 🙌

Thank you for taking the time to improve libphonenumber!
We support 10 digit long numbers for the prefix 13 while the specified number +61 1300 3278 929 is 11 digits long.
Here is our official evidence: https://www.itu.int/dms_pub/itu-t/oth/02/02/T020200000D0001PDFE.pdf
We are not able to find 11 digit numbers with this prefix online.
Closing this as working as intended; if you would like to reopen, please share any working numbers or official evidence you may have. See our guidelines.

I think I have the same issue. The phone number from this company is parsed as invalid.
https://beowulfbuilders.com.au/contact/
https://libphonenumber.appspot.com/phonenumberparser?number=1300+BEOWULF&country=AU
https://libphonenumber.appspot.com/phonenumberparser?number=1300+236+9853&country=AU


"Invalid requirement: '[:platform_system'" with PEP 508 classifiers

I am seeing a similar issue as reported in https://github.com/zsimic/setupmeta/issues/22 recently, when using a setup.py as follows - triggered by "pyreadline;platform_system=='Windows'":
from setuptools import setup

setup(
    name='fancycompleter-pdbpp',
    setup_requires="setupmeta",
    install_requires=[
        "pyrepl",
        "pyreadline;platform_system=='Windows'",
    ]
)

GLOB sdist-make: …/Vcs/fancycompleter-git/setup.py
py37 recreate: /tmp/tox…/Vcs/fancycompleter-git/py37
py37 installdeps: pytest
py37 inst: /tmp/tox…/Vcs/fancycompleter-git/.tmp/package/1/fancycompleter-pdbpp-0.0.0.zip
ERROR: invocation failed (exit code 1), logfile: /tmp/tox…/Vcs/fancycompleter-git/py37/log/py37-2.log
================================================================================= log start ==================================================================================
Looking in indexes: http://localhost:3141/root/pypi/+simple/
Processing /tmp/tox…/Vcs/fancycompleter-git/.tmp/package/1/fancycompleter-pdbpp-0.0.0.zip
    ERROR: Complete output from command python setup.py egg_info:
    ERROR: Traceback (most recent call last):
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_vendor/packaging/requirements.py", line 93, in __init__
        req = REQUIREMENT.parseString(requirement_string)
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_vendor/pyparsing.py", line 1828, in parseString
        raise exc
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_vendor/pyparsing.py", line 1818, in parseString
        loc, tokens = self._parse( instring, 0 )
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_vendor/pyparsing.py", line 1562, in _parseNoCache
        loc,tokens = self.parseImpl( instring, preloc, doActions )
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_vendor/pyparsing.py", line 3752, in parseImpl
        loc, exprtokens = e._parse( instring, loc, doActions )
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_vendor/pyparsing.py", line 1562, in _parseNoCache
        loc,tokens = self.parseImpl( instring, preloc, doActions )
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_vendor/pyparsing.py", line 4098, in parseImpl
        return self.expr._parse( instring, loc, doActions, callPreParse=False )
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_vendor/pyparsing.py", line 1562, in _parseNoCache
        loc,tokens = self.parseImpl( instring, preloc, doActions )
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_vendor/pyparsing.py", line 3735, in parseImpl
        loc, resultlist = self.exprs[0]._parse( instring, loc, doActions, callPreParse=False )
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_vendor/pyparsing.py", line 1566, in _parseNoCache
        loc,tokens = self.parseImpl( instring, preloc, doActions )
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_vendor/pyparsing.py", line 2935, in parseImpl
        raise ParseException(instring, loc, self.errmsg, self)
    pip._vendor.pyparsing.ParseException: Expected W:(abcd...) (at char 0), (line:1, col:1)

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_internal/req/constructors.py", line 285, in install_req_from_line
        req = Requirement(req_as_string)
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_vendor/packaging/requirements.py", line 97, in __init__
        requirement_string[e.loc : e.loc + 8], e.msg
    pip._vendor.packaging.requirements.InvalidRequirement: Parse error at "'[:platfo'": Expected W:(abcd...)

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-req-build-76dfx9ft/setup.py", line 8, in <module>
        "pyreadline;platform_system=='Windows'",
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/setuptools/__init__.py", line 145, in setup
        return distutils.core.setup(**attrs)
      File "/usr/lib64/python3.7/distutils/core.py", line 134, in setup
        ok = dist.parse_command_line()
      File "/tmp/pip-req-build-76dfx9ft/.eggs/setupmeta-2.6.0-py3.7.egg/setupmeta/hook.py", line 23, in distutils_hook
        dist._setupmeta = SetupMeta(dist)
      File "/tmp/pip-req-build-76dfx9ft/.eggs/setupmeta-2.6.0-py3.7.egg/setupmeta/model.py", line 673, in __init__
        self.requirements = Requirements(self.pkg_info)
      File "/tmp/pip-req-build-76dfx9ft/.eggs/setupmeta-2.6.0-py3.7.egg/setupmeta/model.py", line 561, in __init__
        self.install = self.get_requirements(True, pkg_info.requires_txt, "requirements.txt", "pinned.txt")
      File "/tmp/pip-req-build-76dfx9ft/.eggs/setupmeta-2.6.0-py3.7.egg/setupmeta/model.py", line 596, in get_requirements
        return RequirementsEntry(path, abstract=abstract)
      File "/tmp/pip-req-build-76dfx9ft/.eggs/setupmeta-2.6.0-py3.7.egg/setupmeta/model.py", line 547, in __init__
        reqs, links = parse_requirements(self.reqs)
      File "/tmp/pip-req-build-76dfx9ft/.eggs/setupmeta-2.6.0-py3.7.egg/setupmeta/model.py", line 350, in parse_requirements
        for ir in pip_parse_requirements(temp, session=session):
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_internal/req/req_file.py", line 112, in parse_requirements
        for req in req_iter:
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_internal/req/req_file.py", line 193, in process_line
        isolated=isolated, options=req_options, wheel_cache=wheel_cache
      File "/tmp/tox…/Vcs/fancycompleter-git/py37/lib/python3.7/site-packages/pip/_internal/req/constructors.py", line 296, in install_req_from_line
        "Invalid requirement: '%s'\n%s" % (req_as_string, add_msg)
    pip._internal.exceptions.InstallationError: Invalid requirement: '[:platform_system'

    ----------------------------------------
ERROR: Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-req-build-76dfx9ft/

================================================================================== log end ===================================================================================
__________________________________________________________________________________ summary ___________________________________________________________________________________
ERROR:   py37: InvocationError for command /tmp/tox…/Vcs/fancycompleter-git/py37/bin/python -m pip install --exists-action w /tmp/tox…/Vcs/fancycompleter-git/.tmp/package/1/fancycompleter-pdbpp-0.0.0.zip (exited with code 1)

Just release setupmeta 2.6.1, which should fix this.
It was failing on unparseable reqs, now it will simply not auto-fill anything is pip can't parse reqs file.

Awesome, thanks!
That fixes it.
btw: explain looked correctly before already:
extras_require: (explicit) {:platform_system == "Windows": ["pyreadline"]}
install_requires: (explicit) ["pyrepl"]


new rule react/fc-props-spreading

Controlling The Flow In Props With Destructuring And Spread Attributes
What are the benefits in using props.something versus something?
Without destructuring
const Display = (props) =>
{props.something}

With destructuring
const Display = ({ something }) =>
{something}

With destructuring, you're not only making your code more readable for yourself and others but you're also making straight forward decisions on what goes in and what goes out. When other developers edit your code in the future, they don't have to scan through each line of code in your render method to find all of the props that the component is using.
You also benefit from the ability to declare a default props right from the beginning without having to add any more lines of code:
const Display = ({ something = 'apple' }) =>
{something}

I’m not sure what this issue is asking for.
Sometimes destructuring is not clearer to read, although usually i find it to be. A rule that forces this is worth considering.
Using default arguments instead of default props, however, is not a good thing - defaultProps can be read from the outside, default arguments can not - and i would be strongly against any rule that pushed people away from .defaultProps.

to force "destructing of props" for functional components if it's possible, about defaultProps it's just another reason, why do it, not replace defaultProps

Because defaultProps is better than default arguments.

okay, but stick to the original idea about destructing props (side note: default props are at the end of the file, so need to scroll down to see them, but different discussion)

The title says “spreading” but there’s no spread being used here, so i was confused by the initial post.
I would be in support of a rule that required all props, state, and context to be destructured at the top of the function/method in which they are used, or in the signature for SFCs. I would not be interested in a rule that only targets SFCs.

sorry destructing 🤦  well that sounds interesting for all props, state, and context to be destructed and must be on top

SFCs also take a second context argument, so you might want to destructure that too when it’s used.

yes, but it's also a legacy API (I never used it), but why not


MSID: 100433 Version: 1 DOI: 10.1101/2<IP_ADDRESS>9722

MSID: 100433
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>9722
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=100433
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>9722

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/100433v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>9722
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/100433/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: [biorender-check] Article text contains a mention of bioRender. Since bioRender do not permit content to be published under a CC-BY license (https://help.biorender.com/en/articles/8601313-creative-commons-licensing-for-biorender-figures-premium-only), if any images were created using bioRender a blanket permissions statement will need to be added for the Reviewed Preprint: 'Any parts of this image created with BioRender are not made available under the same license as the Reviewed Preprint, and are © 2024, BioRender Inc.'
warn: [journal-ref-text-content] This journal reference (id c16) has untagged textual content - . Retrieved from . Is it tagged correctly?
warn: [ref-person-group-type-2] person-groups within a reference should be distinct. There are numerous person-groups with the person-group-type editor within this reference (id=c33).
warn: [p-all-bold] Content of p element is entirely in bold - 'Supplemental Figure 1: Tercko/ko mice with systemic infection display more severe pneumonia with bacteremia and increased mortality.'. Is this correct?
warn: [p-all-bold] Content of p element is entirely in bold - 'Supplemental Figure 2: Several pathways relevant for inflammation and adaptive and innate immune response are differentially expressed in infected Tercko/ko mice.'. Is this correct?
warn: [p-all-bold] Content of p element is entirely in bold - 'Supplemental Figure 3:'. Is this correct?
warn: [p-all-bold] Content of p element is entirely in bold - 'Supplemental Figure 4:'. Is this correct?
warn: [p-all-bold] Content of p element is entirely in bold - 'Supplemental Figure 5:'. Is this correct?
warn: [article-email-corresp-author-count-equivalence] The number of corresponding authors (1: Stefanie Deinhardt-Emmer) is not equal to the number of distinct email addresses (2<EMAIL_ADDRESS>yasmina.reisser@med.uni-jena.de). Is this correct?


Remove element from IngredientSerializer

This association causes infinite recursion during
deserialization, because the element is already
included in the page's elements association's data.

Specs will be fixed by https://github.com/AlchemyCMS/alchemy_cms/pull/2997


Fix split and array_split with unordered indices supplied

Follows #2814 .
cupy.split and cupy.array_split raise an error when they take unordered indices as [4, 2]. NumPy does not require indices ordered and, in such case, it return an empty array for a going-back index. I'm not sure it is meaningful, but it actually does. This PR fix the functions to follow NumPy's behavior.
>>> import numpy as np
>>> import cupy as cp
>>> np.split(np.array([0, 1, 2, 3, 4]), [4, 2])
[array([0, 1, 2, 3]), array([], dtype=int64), array([2, 3, 4])]
>>> cp.split(cp.array([0, 1, 2, 3, 4]), [4, 2])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "cupy/core/core.pyx", line 1341, in cupy.core.core.ndarray.__repr__
    return repr(self.get())
  File "cupy/core/core.pyx", line 1432, in cupy.core.core.ndarray.get
    a_cpu = numpy.empty(self._shape, dtype=self.dtype, order=order)
ValueError: negative dimensions are not allowed

Jenkins, test this please

Jenkins CI test (for commit 086f7f7147fff94ff8c74e8e1eacdcddf2272407, target branch master) succeeded!

As #2814 is now sucessfully back-ported, would you make the back-ports of this PR as well?

Yes, I was waiting for that :)

Thanks!


MyFactory Conected with where?

Bro I just Import your library to my app.
 `implementation project(path: ':player')
implementation project(path: ':exo')`

`include ':exo'
 include ':player'`

I also added MyFactory.class and codes.  but MyFactory conected with nothing .. So again m3u8 Not work and also redirect urls not work..
But working fine  if i import github library separately ..  in you library MyFactory.class conected with your doc pages ..not code...
If i add to my app where I should conect MyFactory.class ?

Your custom PlayerService.ComponentFactory need use <meta-data> register at AndroidManifest.xml.
Example:
<service android:name="snow.player.PlayerService">
    ...
    <meta-data android:name="component-factory" android:value="@string/factory-name"/>
</service>

The value of android:name is "component-factory", and the value of android:value is a string resource, that is the full name of you custom PlayerService.ComponentFactory, example: snow.player.debug.MyFactory

Yes Bro Thank you its working fine..


v2ray, v2ray-domain-list-community: switch to go_1_17, update vendorSha256

Motivation for this change
Minimizing diff and rebuilds for changing the default go in  #154059
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 154208 run on x86_64-linux 1

2 packages built:

v2ray
v2ray-domain-list-community


make job-exporter resistant to command hangs

current job-exporter is single threaded model, should add some timeout when calling subcommand, since most of commands called by job-exporter are prone to hangs:

docker stats --no-stream --format "table {{.Container}},{{.Name}},{{.CPUPerc}},{{.MemUsage}},{{.NetIO}},{{.BlockIO}},{{.MemPerc}}"
docker inspect $container_id
docker logs --tail all $container_id
systemctl is-active docker | if [ $? -eq 0 ]; then echo "active"; else exit 1; fi
nvidia-smi -q -x
iftop -t -P -s 1 -L 10000 -B -n -N
infilter $pid /usr/bin/lsof -I -n -P

related issues:

#1724
#1719
#842

close and track the problem in #1764


Patch 16

Reformatting the github to make it easier for people to find important documents, also created a first go to !KEYDOCS README FIRST! to get them as quickly up to speed with what's going on and gave a reading order of most relevance and information needed to understand the following piece of information.

Thanks. There is a conflict that prevents merging. Can you pull the latest.


wallet

installed a wallet under Windows 10,
reinstalled Windows, how to restore the wallet, the configuration file does not open&

do you store wallet.dat ? use that


openresty: 1.19.9 -> 1.21.4

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Why the backport? Quite a significant change.

@risicle openresty has strong backwards compatibility, it is safe to backport new release. 1.19.9.x series is unmaintained, last release was in  Aug 6, 2021.

99% of software in the stable branch is "unmaintained" because the vast majority of projects only "support" (for some value of "support") the absolute latest version. There would be no such thing as a stable branch if we followed a policy of bumping all "unmaintained" versions.


Implement Google, Facebook and Twitter auth using firebase

Description
It'll make the user experience of sign up and signin better.
Screenshots
No response
Additional information
No response

Yes I would like to work on this issue.

Great! go ahead and please confirm the program , jwoc?

I want to work on this under JWOC

I want to work on this under JWOC

@MahirMahdi are you working on this? if not, please confirm so @aashi01kh can work on this issue :)

I'm working on this issue

I'm working on it

@narayan954 enable google as a sign in method in the firebase console. The pop up's not working because of that. Let me know when your're done
😀

@narayan954 enable google as a sign in method in the firebase console. The pop up's not working because of that. Let me know when your're done grinning

Yeah sure, thanks for the reminder!

I have enabled the google sign in method, and about those twitter and facebook login, they'd need some configurations/api keys . Should I enable them and what else would you require ? :)
Thanks

Enable both twitter and facebook. I'll test those using my credentials and create an environmental variable for each credential.
While redeploying you can just update it with your credentials. Let me know if it's okay.😀

@narayan954 Also please let me know if the localhost url is whitelisted in the oAuth page or not.

okay i'll lyk

@narayan954 Also please let me know if the localhost url is whitelisted in the oAuth page or not. If not then whitelist it kindly, in the only domain section : "http://localhost:3000" and in the url section : "http://localhost:3000/dummygram".

localhost is already in the authorised domain, is there something else to do?

@narayan954 Also please let me know if the localhost url is whitelisted in the oAuth page or not. If not then whitelist it kindly, in the only domain section : "http://localhost:3000" and in the url section : "http://localhost:3000/dummygram".

localhost is already in the authorized domain, is there something else to do?

@narayan954 Sorry to bother you. Pop-ups and redirects were blocked in my browser.

@narayan954 Sorry to bother you. Pop-ups and redirects were blocked in my browser. It's working now. I'm gonna work on facebook and twitter now.
Oh yes another thing, when you enable facebook and twitter oAuth, you'll have to add credentials. Let me know when you're done.smiley

cool, it's okay, I'm happy to help and learn

@narayan954 Sorry to bother you. Pop-ups and redirects were blocked in my browser. It's working now. I'm gonna work on facebook and twitter now.
Oh yes another thing, when you enable facebook and twitter oAuth, you'll have to add credentials. Let me know when you're done.smiley

I have enabled facebook oAuth, but I don't think we need too many oAuths , two should do, and I think they can be facebook and google.
I enabled the redirect URI for facebook as https://narayan954.github.io/dummygram/auth/handler

@narayan954 Yes google and facebook are fine. I have implemented both of them and they work fine. I'm gonna make a PR now. 😃

Thanks! will look into asap.


Translate more

Speaking the baguette makes me a good translator, I guess

Lol, thanks a lot
I'll add you to the "attributions" table soon
Unless you want to do that yourself haha


Made a couple of small changes to allow sherlock to work with python 3

It appears that there are only two small changes require to make sherlock work with Python 3.  I noticed there are a couple of issues posted about this. I don't know if anyone has tried to give you a pull request to resolve the issue, so here is mine.

There are 2 more changes in tests/integration/test_lock.py which will also help to support Python 3. Lines 18-19 should be changed to read:
        except Exception as err:
            print(str(err))

Coverage remained the same at 97.276% when pulling 88953c588d37354cf8268be36cc1bef591b704ad on thataintworking:master into 9a45b0be6b50f6cbc172e1a965e936f6654df33b on vaidik:master.

+1 for merging & releasing this. It's a shame sherlock is not available for Python 3, especially if all it takes is a few code updates.

Hi,
I agree @janpom. Its a shame that sherlock is not available for Python 3. And a large part of it has been my unavailability to maintain the project.
Thanks @ronsmith for the changes. Really appreciate the effort.
I cannot merge this PR yet. @ronsmith you will need to change the travis config as well to run the tests on Python 3. I tried running the tests locally for python 3 and they didnt pass. If you can take this up, I would really appreciate it. Otherwise, I can take this up and fix this myself as well.

Thanks for the help @ronsmith . Your PR was helpful and is merged separately because tests for python 3 were failing. So I cherripicked your commit and have fixed those tests.
Thanks once again. And really sorry for the delay.
Closing this PR now

Sorry I was not able to make the changes to the tests, I have been travelling. Glad it is working with python 3 now.


upgrade jacoco version to support jdk11

upgrade jacoco version to support jdk11

Codecov Report

Merging #168 into develop will increase coverage by 0.25%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             develop   #168      +/-   ##
===========================================
+ Coverage       0.14%   0.4%   +0.25%
- Complexity         3      7       +4
===========================================
  Files            103    103
  Lines           4682   4682
  Branches         785    785
===========================================
+ Hits               7     19      +12
+ Misses          4675   4662      -13
- Partials           0      1       +1

Impacted Files
Coverage Δ
Complexity Δ

...g/apache/dubbo/admin/governance/util/UrlUtils.java
90.47% <0%> (+57.14%)
7% <0%> (+4%)
: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 c5dfdd8...1c9174e. Read the comment docs.


Fix syschdemd exit code

This fixes #138, by using systemd-run instead of machinectl, but breaks systemd user sessions and dbus
@K900: If we can get those to work with systemd-run, it will probably work with native systemd as well (because I think this is what MS is using as well)

No, they're spawning a shell as a child of /init, so it's not even in the right slice.

I wanted to find out, how distrod gets around that, and the answer seems to be that they didn't:
PS C:\Users\nzbr> wsl -d Distrod systemctl --user
Failed to connect to bus: No such file or directory

genie seems to use machinectl

A possible solution would be to use machinectl when launching the default shell and systemd-run when a command is specified. I'd rather find a way to always use systemd-run though

I got it to work!
@K900 We might be able to use the same approach (using runuser) for native systemd. That would mean having a wrapper script as the root shell again, but it'd be much simpler because we don't need the namespace

@nzbr what do you think about adding me as a collaborator to this repo?

@nzbr what do you think about adding me as a collaborator to this repo?

Given that you're pretty active on here, that's probably a good idea - same goes for @K900
Unfortunately, I don't have the necessary permission to do that though

Starts now without crashing.
ssh-agent is still broken because of SSH_AUTH_SOCK=/mnt/wslg/runtime-dir/ssh-agent but NixOS placing the socket in the default location.
systemctl status diff between before and after this PR:
I think TERMINFO_DIRS is set wrong by wezterm.
--- before	2022-11-11 18:06:50.116889800 +0100
+++ after	2022-11-11 18:07:26.142133500 +0100
@@ -2,28 +2,47 @@
     State: running
      Jobs: 0 queued
    Failed: 0 units
-    Since: Fri 2022-11-11 18:06:28 CET; 22s ago
+    Since: Fri 2022-11-11 18:07:19 CET; 6s ago
    CGroup: /
            ├─user.slice
            │ └─user-1000.slice
            │<EMAIL_ADDRESS>            │   │ ├─app.slice
            │   │ │ ├─ssh-agent.service
-           │   │ │ │ └─ 70 /nix/store/hfmwjjkz0c2p9ggcqw22rgnhx0jjm84z-openssh-9.1p1/bin/ssh-agent -a /run/user/1000/ssh-agent
+           │   │ │ │ └─ 69 /nix/store/hfmwjjkz0c2p9ggcqw22rgnhx0jjm84z-openssh-9.1p1/bin/ssh-agent -a /run/user/1000/ssh-agent
            │   │ │ └─auto-fix-vscode-server.service
            │   │ │   ├─  63 /nix/store/y0g1mvsr6vygr61f9znljik9kl0x0inc-bash-5.1-p16/bin/bash /nix/store/ngx73rfq5mx9s4zkgjjnypciizq4n7aa-auto-fix-vscode-server.sh
-           │   │ │   ├─ 116 /nix/store/y0g1mvsr6vygr61f9znljik9kl0x0inc-bash-5.1-p16/bin/bash /nix/store/ngx73rfq5mx9s4zkgjjnypciizq4n7aa-auto-fix-vscode-server.sh
-           │   │ │   └─ 117 inotifywait -q -m -e CREATE,ISDIR -e DELETE_SELF --format %w%f:%e /home/sandro/.vscode-server/bin
+           │   │ │   ├─ 118 /nix/store/y0g1mvsr6vygr61f9znljik9kl0x0inc-bash-5.1-p16/bin/bash /nix/store/ngx73rfq5mx9s4zkgjjnypciizq4n7aa-auto-fix-vscode-server.sh
+           │   │ │   └─ 119 inotifywait -q -m -e CREATE,ISDIR -e DELETE_SELF --format %w%f:%e /home/sandro/.vscode-server/bin
            │   │ └─init.scope
            │   │   ├─ 56 /nix/store/isg9b516rmlf6ri8c29jm9ibl1kg0sa7-systemd-249.12/lib/systemd/systemd --user
            │   │   └─ 57 (sd-pam)
            │   └─session-c1.scope
-           │     ├─  54 /run/current-system/sw/bin/bash
-           │     ├─  68 (sd-pam)
-           │     ├─  93 /nix/store/4wnc0503iawwc2166jfwkf0zmd7wr0ps-cod-0.1.0/bin/cod api forked-daemon 87
+           │     ├─  54 /nix/store/15y79343wxnalk8629v9vg63a31pbwk7-util-linux-2.38.1-bin/bin/runuser -u sandro -- /bin/sh -c declare -x COLORTERM="truecolor"
+declare -x DISPLAY=":0"
+declare -x HOSTTYPE="x86_64"
+declare -x LANG="en_US.UTF-8"
+declare -x NAME="francium"
+declare -x OLDPWD
+declare -x PATH="/run/wrappers/bin:/nix/store/xq4g38m5ppg78z7bzfxyy2s8ii693k74-coreutils-9.1/bin:/nix/store/vdmbj6w77pg29fn77ndn659ngbxjsq4w-daemonize-1.7.8/bin:/nix/store/4xynblhic6sq4paq2ra4ql535yyvracs-glibc-2.35-163-bin/bin:/nix/store/sqypvzmrsl8hil564xfk8n5w51gq47h0-gnugrep-3.7/bin:/nix/store/z5qg6m93yv2wsij772rsljah3ahw1m8b-systemd-251.5/bin:/nix/store/15y79343wxnalk8629v9vg63a31pbwk7-util-linux-2.38.1-bin/bin:/nix/store/ldaflixlmv5dills5dq960i6m1s9pzq0-which-2.21/bin:/nix/store/53ssjlp0w2dsbifdg9jbykypq05205c2-nixos-wsl-systemd-wrapper/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib"
+declare -x PULSE_SERVER="/mnt/wslg/PulseServer"
+declare -x PWD="/mnt/c/Users/user"
+declare -x SHLVL="1"
+declare -x TERM="wezterm"
+declare -x TERMINFO_DIRS="/home/user/.nix-profile/share/terminfo"
+declare -x TERM_PROGRAM="WezTerm"
+declare -x TERM_PROGRAM_VERSION="20220905-102802-7d4b8249"
+declare -x WAYLAND_DISPLAY="wayland-0"
+declare -x WSL2_GUI_APPS_ENABLED="1"
+declare -x WSLENV="TERMINFO_DIRS:TERM:COLORTERM:TERM_PROGRAM:TERM_PROGRAM_VERSION"
+declare -x WSL_DISTRO_NAME="NixOS"
+declare -x WSL_INTEROP="/run/WSL/6_interop"
+declare -x XDG_RUNTIME_DIR="/mnt/wslg/runtime-dir"; source /etc/set-environment; exec /run/current-system/sw/bin/bash
+           │     ├─  67 /run/current-system/sw/bin/bash
+           │     ├─  93 /nix/store/4wnc0503iawwc2166jfwkf0zmd7wr0ps-cod-0.1.0/bin/cod api forked-daemon 86
            │     ├─ 131 /run/current-system/sw/bin/bash
-           │     ├─ 134 /nix/store/5ysxr04vk1v2arpyl6brd0xzlig5sds8-gitstatus-1.5.4/bin/gitstatusd -G v1.5.4 --parent-pid=54 --num-threads=8 --max-num-staged=1 --max-num-unstaged=1 --max-num-conflicted=1 --max-num-untracked=1 --dirty-max-index-size=-1 --repo-ttl-seconds=3600
-           │     └─ 348 systemctl status
+           │     ├─ 134 /nix/store/5ysxr04vk1v2arpyl6brd0xzlig5sds8-gitstatus-1.5.4/bin/gitstatusd -G v1.5.4 --parent-pid=67 --num-threads=8 --max-num-staged=1 --max-num-unstaged=1 --max-num-conflicted=1 --max-num-untracked=1 --dirty-max-index-size=-1 --repo-ttl-seconds=3600
+           │     └─ 237 systemctl status
            ├─init.scope
            │ └─ 1 systemd
            └─system.slice

git gpg signing is broke with those changes. Not sure why and I am not looking forward to debugging it.

I don't have SSH_AUTH_SOCK set, because I don't use the SSH agent. Was it working before the patch?

No, but I hoped it would work now. Let me debug that this later.


v6 Schema; move label value out of range key, and re-enable chunk timestamp optimisation.

Fixes #316 (ValidationError because range value was too long) and reenabled the v5 query optimisation with the fixed timestamps.

Question: should we impose a limit of label name and value length?

@tomwilkie Is the linked #199 correct? That's already fixed. I guess you meant https://github.com/weaveworks/cortex/issues/316.

Yeah I meant #316

Question: should we impose a limit of label name and value length?

 We should probably have limits. Maybe 1k for label names and 4k for label values? Those are already sizes nobody should reach, but who knows...

@juliusv PTAL

One last comment, otherwise :+1:


Capitalize 'deutsch'

Changes proposed in the pull request:

German (deutsch) => German (Deutsch)

@AppraiseDev/core-team

What about the other languages? Shouldn't they be capitalized as well?

I think we want to show the language name as it should be shown in that language. For German it should be capitalized. Maybe there are errors for other languages, but that's beyond my expertise.

Good point, I haven't thought about it that way.

Closing. Superseded by/included in #73


Fix inserting new subflow node to existing wire

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
I fixed #2243. I removed chartOffset because it is not needed. Only paletteWidth and paletteTop are enough for all nodes.
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 76.376% when pulling 2f5ec8b5bf4a0b1af7d2c806c09a66e1adbb9148 on kazuhitoyokoi:master-fixwiring4subflownode into 8bb7b2e88b550ea05b2bfd58d9219ee7db44fe5a on node-red:master.

@knolleary Thank you!


atan22 not found in transform.math.atan22

When trying to use turboTurbine in a model, got an error:
Function TRANSFORM.Math.atan22 is not known in turboTurbine (model TRANSFORM.Fluid.Machines.TurboTurbine).

https://github.com/ORNL-Modelica/TRANSFORM-Library/blob/c403dc0ef9542b25939edd01b51b2428aadb6332/TRANSFORM/Fluid/Machines/TurboTurbine.mo#L33

Hi Vishal.
The turboTurbine component is marked as "under construction." I would suggest not using it at this time. Depending on your application, I would suggest the TRANSFORM.Fluid.Machines.Turbine_SinglePhase_Stodola (for single phase applications) or TRANSFORM.Fluid.Machines.SteamTurbine (for applications where condensing in the turbine may occur).
Thanks,
Jordan

Oh great thanks! I didn't noice that tag, will keep a look out for that next time. Thanks for the rec. Do y'all still prefer issues on things under construction?

I'll defer to @greenwoodms06 on that, but I would assume issues are OK to post on "under construction" items.
Just understand that we are unlikely to help you fix them unless it's a minor syntactical thing.
I'm actively developing in the turbomachinery library so it's possible that turboTurbine will get some attention in the not-to-distant future. Focusing on the pump side right now.
Also, using "under construction" models is not advised for production work as they are likely candidates for deletion or significant revision. Not sure if there is a project-level description as to what qualifies as "under construction." Once again, maybe @greenwoodms06 can enlighten us.

My initial thoughts... comments are welcome, contributions even more so :), even if that is volunteering to test or provide suggestions on "requirements" for a model under development.
But @jdrader86 is right, under construction is a catch all for things that are not working or at various stages of working and may be moved, deleted, or modified significantly. At some point these models will be moved into a more isolated package so as not to distract from more mature models.


How to obtain more detailed information?

Report
Hey, guys. I just update rinf to 6.6.1, and got an error. My question is how to obtain more detailed information about this error, thank you.
Error:
E/flutter (22648): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Invalid argument(s): Failed to lookup symbol 'send_dart_signal_extern': undefined symbol: send_dart_signal_extern
E/flutter (22648): #0      DynamicLibrary.lookup (dart:ffi-patch/ffi_dynamic_library_patch.dart:33:70)
E/flutter (22648): #1      sendDartSignalExtern (package:rinf/src/interface_os.dart)
E/flutter (22648): #2      sendDartSignal (package:rinf/rinf.dart:45:3)
E/flutter (22648): #3      InvokeRequest.sendSignalToRust (package:xxx/messages/xxx.pb.dart:24:3)
E/flutter (22648): #4      _WebPageState._chanInvoke (package:xxx/xxx.dart:208:7)
E/flutter (22648): <asynchronous suspension>

My dart file like:
There is no syntax or type error.
var appDir = await getApplicationDocumentsDirectory();
r_invoke.InvokeRequest(
  reqStr: message, // it's a String
  appDir: appDir.path, // it's a String
).sendSignalToRust(null); // The error caused here, 208:7 starts after the dot.
final stream = r_invoke.InvokeResponse.rustSignalStream;
Future<RustSignal<InvokeResponse>> rResF = stream.last;

final rustResponse = await rResF;
InvokeResponse responseMessage = rustResponse.message;

My proto file like:
// [RINF:DART-SIGNAL]
message InvokeRequest {
  string req_str = 1;
  string app_dir = 2;
}

System Information
rustc --version outputs: rustc 1.75.0
flutter doctor outputs:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.16.7, on Debian GNU/Linux 12 (bookworm) 6.1.0-18-amd64, locale zh_CN.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[✓] Android Studio (version 2022.3)
[✓] VS Code (version 1.85.0)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!

Hi @newproplus , thanks for leaving your issue here.
It looks like the symbol is missing is from your Rust library. Rinf recently organized the bridge code and the way of writing it has changed a little.
Take a look at this sample app:

https://github.com/cunarist/rinf/tree/main/flutter_ffi_plugin/example

What I think you need to do is:

Remove native/hub/src/bridge folder
Upgrade Rinf to 6.6.1 in native/hub/Cargo.toml
Write rinf::write_interface!() in native/hub/src/lib.rs just like the example app

If the problem persists, please let me know :)

@temeddix Thank you, I found that the line rinf::write_interface!() in native/hub/src/lib.rs is missing.


Allow to work in non-browser env

‘window’ is specific to browser environments. ‘this’ (the global object is the default ‘this’ value) allows it to work in non-browser environments other than node.

Oh, wait. That doesn’t work, nor does it make any sense.
The "use strict" prevents ‘this’ from returning the global object. But in any case, you don’t even need this, since you are already defining a convnetjs variable. (The combined file begins with ‘var convnetjs’.)
So I suspect that line can simply be deleted, but I am not certain.

I am not using a browser. Nor am I using Node. I am embedding a JavaScript interpreter directly in my application. The JS environment contains only objects defined by the ECMAScript specification. This means I get an error when trying to run convnet.js, since it is trying to access nonexistent variables.
(I happen to be using Duktape, but I could have used SpiderMokney or JE and the same problem would have occurred.)
In a browser environment, BTW, the window is the global object, which happens to have a window property referring to itself (so, yes, you can say window.window.window.window.convnetjs).

Thanks @cpansprout , I understand now. I don't know how to help you out there / how to debug as I've never run JS in such an environment. If you get around solving it, it'd be cool to make to look into the solution

I have solved it locally by simply commenting out the
window.convnetjs = lib;

line, which is actually unnecessary, as convnetjs has already been declared as a global variable.  If you change that line to alert(window.convnetjs == lib) then you will get an alert box saying ‘true’.
I don’t know how you update an existing pull request.

@cpansprout you can do that by pulling your fork of the repo and checking out the patch-1 branch (this). Then you modify that, commit, push, and you should see the new commit appear here.

Thank you.  That worked.


how to get scopes using “@azure/msal-angular”: “^0.1.4”?

Currently, I am facing an issue with scope. As we are passing the scope in the URL but after successful authentication with azure I am able to get the token, but when I decode the token the scopes are not present in the token. Could you please help out here? I have tried so many ways, but unfortunately, I am unable to get scopes in the token.
Plugin Used: "@azure/msal-angular": "^0.1.4"

See this issue for how to get the scp claim: https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/1286
Closing.


Upgrade ecto to 3.0.7 and add ecto_sql package

Updated package to work with ecto 3.0.7. It doesn't support tracking versions for associations.
It requires existing apps to modify column type of recorded_at from utc_datetime to utc_datetime_usec.
Closes #12

@ZennerIoT Need your help in supporting version tracking for associations on inserts.

Failing Tests
  1) test should track cascading deletions (before they happen) (AssocTest)
     test/assoc_test.exs:32
     Assertion with == failed
     code:  assert length(versions) == 6
     left:  3
     right: 6
     stacktrace:
       test/assoc_test.exs:65: (test)

 2) test comment lifecycle tracked (AssocTest)
     test/assoc_test.exs:8
     ** (MatchError) no match of right hand side value: []
     code: [%{actor_id: actor_id}] = comment_history = Repo.history(comment)
     stacktrace:
       test/assoc_test.exs:27: (test)

https://github.com/ZennerIoT/ex_audit/pull/9 we already have an ongoing PR here with the same problem

@narrowtux I didn't see any issue created for it after creating a PR noticed it 🤕. Anyway, currently i'm pointing to this branch until one of the PR gets merged. Our app doesn't need associations to be tracked as of now.

no problem. is it cool if I close this so there's no confusion?

Sure. I'm closing this.


Warning and comment to clarify AutoUnmount behavior

I was caught out by a change in how options are treated in 0.9.1: if you set AutoUnmount and neither AllowRoot or AllowOther are set, then AllowOther is getting automatically added. If your /etc/fuse.conf doesn't permit AllowOther, the mount will fail without much information. See the latter half of #153, after it was closed.
This PR adds a warning when AllowOther is added and a comment to the options datatype, in the hopes of saving others some trouble.

Could you run the formatter to resolve that CI failure?

Oops! Sorry about that. 🤭


Track Paper Matching: configure edge browser urls based on committee role

Parametrize the edge invitations using the track groups instead of the general committee groups.
Parametrize the edge browser urls in the SAC and AC consoles to use the track groups.

I've only checked the AC consoles and edge invitations. The invitations and edge browser URL are using the track groups.

You're right SACs are also included in the test, I'm not sure why I thought they weren't. It looks good, SACs are able to modify assignments. Are SACs only able to use the Invite Assignment and not Assign?

After the assignments are deployed. By default we only let users to invite emergency reviewers but we can change it if the PCs decide something different.
It is just changing the url in the SAC console.


Fail building with Poetry

Version
Latest
Platform
Linux
Description
Installation via Poetry seems to fail.
I tried this code:
poetry add cryo-python
or
poetry install (if the pkg was manually added to pyproject.toml)
I expected to see this happen: Successful installation and pkg added to pyproject.toml
Instead, this happened:
           Compiling cryo_freeze v0.2.0 (/private/var/folders/6m/hnbzzws969d7blnlbb51qp9w0000gn/T/pip-req-build-mnzq0bdu/local_dependencies/cryo_freeze)
           Compiling pyo3-polars v0.4.0
        error: environment variable `GIT_DESCRIPTION` not defined at compile time
          --> local_dependencies/cryo_cli/src/reports.rs:44:69
           |
        44 |     let cryo_version = format!("{}__{}", env!("CARGO_PKG_VERSION"), env!("GIT_DESCRIPTION"));
           |                                                                     ^^^^^^^^^^^^^^^^^^^^^^^
           |
           = help: use `std::env::var("GIT_DESCRIPTION")` to read the variable at run time
           = note: this error originates in the macro `env` (in Nightly builds, run with -Z macro-backtrace for more info)

        The following warnings were emitted during compilation:

        warning: Could not determine git description

        error: could not compile `cryo_cli` (lib) due to previous error
        warning: build failed, waiting for other jobs to finish...
        💥 maturin failed
          Caused by: Failed to build a native library through cargo
          Caused by: Cargo build finished with "exit status: 101": `MACOSX_DEPLOYMENT_TARGET="10.7" PYO3_ENVIRONMENT_SIGNATURE="cpython-3.10-64bit" PYO3_PYTHON="/Users/Library/Caches/pypoetry/virtualenvs/ape-test-CVGu-StC-py3.10/bin/python" PYTHON_SYS_EXECUTABLE="/Users/Library/Caches/pypoetry/virtualenvs/ape-test-CVGu-StC-py3.10/bin/python" "cargo" "rustc" "--features" "pyo3/extension-module" "--message-format" "json-render-diagnostics" "--manifest-path" "/private/var/folders/6m/hnbzzws969d7blnlbb51qp9w0000gn/T/pip-req-build-mnzq0bdu/Cargo.toml" "--release" "--lib" "--" "-C" "link-arg=-undefined" "-C" "link-arg=dynamic_lookup" "-C"<EMAIL_ADDRESS>        Error: command ['maturin', 'pep517', 'build-wheel', '-i', '/Users/Library/Caches/pypoetry/virtualenvs/ape-test-CVGu-StC-py3.10/bin/python', '--compatibility', 'off'] returned non-zero exit status 1
        [end of output]

    note: This error originates from a subprocess, and is likely not a problem with pip.
    ERROR: Failed building wheel for cryo_python
  Failed to build cryo_python
  ERROR: Could not build wheels for cryo_python, which is required to install pyproject.toml-based projects

  [notice] A new release of pip available: 22.3.1 -> 23.2.1
  [notice] To update, run: pip install --upgrade pip

  at ~/.poetry/lib/poetry/utils/env.py:1195 in _run
      1191│                 output = subprocess.check_output(
      1192│                     cmd, stderr=subprocess.STDOUT, **kwargs
      1193│                 )
      1194│         except CalledProcessError as e:
    → 1195│             raise EnvCommandError(e, input=input_)
      1196│
      1197│         return decode(output)
      1198│
      1199│     def execute(self, bin, *args, **kwargs):

the error printed is related to git not being available
can you install git (e.g. brew install git) and see if the command still fails?

Had git installed, but ran brew reinstall git just in case and the command is still failing
Prob same as https://github.com/paradigmxyz/cryo/issues/27, building from source worked though

did you install maturin separately?

do you know if there is some reason why git might not be available to poetry during build time? I'm not a poetry user and am not familiar with how this issue might arrise
the problem is with this file that runs during the build process. the git command is attempted and for some reason fails, leading to the git warning

so i found an interim solution
cloned the cyro repo in my working directory, ran maturin and added this to pyproject.toml:
cryo-python = { file = "./cryo/target/wheels/cryo_python-0.2.0-cp310-cp310-macosx_10_7_x86_64.whl" }

btw @sslivkoff are you using venv or flit instead?

so i found an interim solution
cloned the cryo repo in my working directory, ran maturin and added this to my pyproject.toml:
[tool.poetry.dependencies]
cryo-python = { file = "./cryo/target/wheels/cryo_python-0.2.0-cp310-cp310-macosx_10_7_x86_64.whl" }

btw @sslivkoff are you using venv or flit instead?

seeing the same issue with hatch and adding cryo. could it be due to the latest on pypi being released before the fix in #30?


MODE-2432 Updated the index manager (both from the API & the SPI) to be able to expose information about that status of each configured index.

Once the ampersand is fixed (see above), this could be merged.


Fix trigger iteration

Changed the trigger for loops to go through all triggers. This will even enable multiple triggers from the same lutron event.

Fixed in V2.3.3.  I only changed the returns to continues.  The else/return statements are not necessary since the method will return anyway after it finishes the for loop.

Oh. I didn't know you didn't need else/return. Even cleaner now. Nice.


[canary] broken production build for static pages inside Docker

When I try build the project in Ubuntu 18.04 it's okay. There are only warnings about MaxListeners.
But inside the Docker build is failed.
Related packages versions

"next": "9.5.2"
"next-optimized-images": "3.0.0-canary.10"

Tested docker versions:

node:12.18.03
node:12.18.03-alpine

next build output from docker build:
info  - Creating an optimized production build...
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry

(node:28) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 uncaughtException listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:28) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unhandledRejection listeners added to [process]. Use emitter.setMaxListeners() to increase limit
info  - Compiled successfully
info  - Collecting page data...
info  - Generating static pages (0/4)

Error occurred prerendering page "/empty". Read more: https://err.sh/next.js/prerender-error
Error: Babel plugin 'react-optimized-image/plugin' not installed or this component could not be recognized by it.
    at Img (/cc-web/node_modules/react-optimized-image/lib/components/Img.js:119:11)
    at d (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:498)
    at $a (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:39:16)
    at a.b.render (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:476)
    at a.b.read (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:18)
    at renderToString (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:54:364)
    at Object.renderPage (/cc-web/node_modules/next/dist/next-server/server/render.js:48:686)
    at Function.getInitialProps (/cc-web/.next/server/pages/_document.js:364:19)
    at loadGetInitialProps (/cc-web/node_modules/next/dist/next-server/lib/utils.js:5:101)
    at renderToHTML (/cc-web/node_modules/next/dist/next-server/server/render.js:48:977)

Error occurred prerendering page "/sitemap". Read more: https://err.sh/next.js/prerender-error
Error: Babel plugin 'react-optimized-image/plugin' not installed or this component could not be recognized by it.
    at Img (/cc-web/node_modules/react-optimized-image/lib/components/Img.js:119:11)
    at d (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:498)
    at $a (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:39:16)
    at a.b.render (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:476)
    at a.b.read (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:18)
    at renderToString (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:54:364)
    at Object.renderPage (/cc-web/node_modules/next/dist/next-server/server/render.js:48:686)
    at Function.getInitialProps (/cc-web/.next/server/pages/_document.js:364:19)
    at loadGetInitialProps (/cc-web/node_modules/next/dist/next-server/lib/utils.js:5:101)
    at renderToHTML (/cc-web/node_modules/next/dist/next-server/server/render.js:48:977)
info  - Generating static pages (1/4)
info  - Generating static pages (2/4)

Error occurred prerendering page "/404". Read more: https://err.sh/next.js/prerender-error
Error: Babel plugin 'react-optimized-image/plugin' not installed or this component could not be recognized by it.
    at Img (/cc-web/node_modules/react-optimized-image/lib/components/Img.js:119:11)
    at d (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:498)
    at $a (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:39:16)
    at a.b.render (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:476)
    at a.b.read (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:18)
    at renderToString (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:54:364)
    at Object.renderPage (/cc-web/node_modules/next/dist/next-server/server/render.js:48:686)
    at Function.getInitialProps (/cc-web/.next/server/pages/_document.js:364:19)
    at loadGetInitialProps (/cc-web/node_modules/next/dist/next-server/lib/utils.js:5:101)
    at renderToHTML (/cc-web/node_modules/next/dist/next-server/server/render.js:48:977)
info  - Generating static pages (3/4)

Error occurred prerendering page "/about". Read more: https://err.sh/next.js/prerender-error
Error: Babel plugin 'react-optimized-image/plugin' not installed or this component could not be recognized by it.
    at Img (/cc-web/node_modules/react-optimized-image/lib/components/Img.js:119:11)
    at d (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:498)
    at $a (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:39:16)
    at a.b.render (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:476)
    at a.b.read (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:18)
    at renderToString (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:54:364)
    at Object.renderPage (/cc-web/node_modules/next/dist/next-server/server/render.js:48:686)
    at Function.getInitialProps (/cc-web/.next/server/pages/_document.js:364:19)
    at loadGetInitialProps (/cc-web/node_modules/next/dist/next-server/lib/utils.js:5:101)
    at renderToHTML (/cc-web/node_modules/next/dist/next-server/server/render.js:48:977)
info  - Generating static pages (4/4)

> Build error occurred
Error: Export encountered errors on following paths:
        /404
        /about
        /empty
        /sitemap
    at exportApp (/cc-web/node_modules/next/dist/export/index.js:24:1103)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async build (/cc-web/node_modules/next/dist/build/index.js:37:212)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
The command '/bin/sh -c yarn build' returned a non-zero code: 1

Got the same error when I compile on my production server
MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 uncaughtException listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:28) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unhandledRejection listeners added to [process]. Use emitter.setMaxListeners() to increase limit
and then I see the process eating up all my servers memory before it crushes.

I'm bumping into this same issue on my workstation without Docker.

@naavis try to delete .next and node_modules and do an npm install again and see if it solves your problem. It did for me. However, my problem is the memory hog that this plugin is. My npm build always fails on my 2G RAM VPS. Works fine on my laptop though.

@semyou That unfortunately did not fix the problem. I am resizing about 200 pictures during the build. The originals only total 128 megabytes, though, and I'm running with 16GB of RAM.

Any news about this one ? I cannot build on vercel anymore. Working fine on local machine

I'm bumping into this same issue on my workstation without Docker with the following output:
> next build

info  - Using external babel configuration from [censored]\.babelrc
(node:5108) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 uncaughtException listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:5108) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unhandledRejection listeners added to [process]. Use emitter.setMaxListeners() to increase limit
RangeError: WebAssembly.Memory(): could not allocate memory
RangeError: WebAssembly.Memory(): could not allocate memory
info  - Creating an optimized production build .[censored]\node_modules\@wasm-codecs\mozjpeg\lib\mozjpeg.js:9
var Module=typeof mozjpeg!=="undefined"?mozjpeg:{};var readyPromiseResolve,readyPromiseReject;Module["ready"]=new Promise(function(resolve,reject){readyPromiseResolve=resolve;readyPromiseReject=reject});var moduleOverrides={};var key;for(key in Module){if(Module.hasOwnProperty(key)){moduleOverrides[key]=Module[key]}}var arguments_=[];var thisProgram="./this.program";var quit_=function(status,toThrow){throw toThrow};var ENVIRONMENT_IS_WEB=false;var ENVIRONMENT_IS_WORKER=false;var ENVIRONMENT_IS_NODE=false;var ENVIRONMENT_IS_SHELL=false;ENVIRONMENT_IS_WEB=typeof window==="object";ENVIRONMENT_IS_WORKER=typeof importScripts==="function";ENVIRONMENT_IS_NODE=typeof process==="object"&&typeof process.versions==="object"&&typeof process.versions.node==="string";ENVIRONMENT_IS_SHELL=!ENVIRONMENT_IS_WEB&&!ENVIRONMENT_IS_NODE&&!ENVIRONMENT_IS_WORKER;var scriptDirectory="";function locateFile(path){if(Module["locateFile"]){

RuntimeError: abort(RangeError: WebAssembly.Memory(): could not allocate memory). Build with -s ASSERTIONS=1 for more info.
    at process.abort ([censored]\node_modules\@wasm-codecs\mozjpeg\lib\mozjpeg.js:9:11556)
    at process.emit (events.js:323:22)
    at processEmit [as emit] ([censored]\node_modules\next\dist\compiled\ora\index.js:1:2260)
    at processPromiseRejections (internal/process/promises.js:209:33)
    at processTicksAndRejections (internal/process/task_queues.js:98:32)
npm ERR! code ELIFECYCLE
npm ERR! errno 7
npm ERR<EMAIL_ADDRESS>build: `next build`
npm ERR! Exit status 7
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     [censored]\AppData\Roaming\npm-cache\_logs\2020-09-13T11_52_00_853Z-debug.log

I am on Next.js 9.5.3, next-optimized-images 3.0.0-canary.10 and Node 12.16.1.

Try this: https://github.com/cyrilwanner/next-optimized-images/issues/186#issuecomment-753632391

I'm bumping into this same issue on my workstation without Docker with the following output:
> next build

info  - Using external babel configuration from [censored]\.babelrc
(node:5108) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 uncaughtException listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:5108) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unhandledRejection listeners added to [process]. Use emitter.setMaxListeners() to increase limit
RangeError: WebAssembly.Memory(): could not allocate memory
RangeError: WebAssembly.Memory(): could not allocate memory
info  - Creating an optimized production build .[censored]\node_modules\@wasm-codecs\mozjpeg\lib\mozjpeg.js:9
var Module=typeof mozjpeg!=="undefined"?mozjpeg:{};var readyPromiseResolve,readyPromiseReject;Module["ready"]=new Promise(function(resolve,reject){readyPromiseResolve=resolve;readyPromiseReject=reject});var moduleOverrides={};var key;for(key in Module){if(Module.hasOwnProperty(key)){moduleOverrides[key]=Module[key]}}var arguments_=[];var thisProgram="./this.program";var quit_=function(status,toThrow){throw toThrow};var ENVIRONMENT_IS_WEB=false;var ENVIRONMENT_IS_WORKER=false;var ENVIRONMENT_IS_NODE=false;var ENVIRONMENT_IS_SHELL=false;ENVIRONMENT_IS_WEB=typeof window==="object";ENVIRONMENT_IS_WORKER=typeof importScripts==="function";ENVIRONMENT_IS_NODE=typeof process==="object"&&typeof process.versions==="object"&&typeof process.versions.node==="string";ENVIRONMENT_IS_SHELL=!ENVIRONMENT_IS_WEB&&!ENVIRONMENT_IS_NODE&&!ENVIRONMENT_IS_WORKER;var scriptDirectory="";function locateFile(path){if(Module["locateFile"]){

RuntimeError: abort(RangeError: WebAssembly.Memory(): could not allocate memory). Build with -s ASSERTIONS=1 for more info.
    at process.abort ([censored]\node_modules\@wasm-codecs\mozjpeg\lib\mozjpeg.js:9:11556)
    at process.emit (events.js:323:22)
    at processEmit [as emit] ([censored]\node_modules\next\dist\compiled\ora\index.js:1:2260)
    at processPromiseRejections (internal/process/promises.js:209:33)
    at processTicksAndRejections (internal/process/task_queues.js:98:32)
npm ERR! code ELIFECYCLE
npm ERR! errno 7
npm ERR<EMAIL_ADDRESS>build: `next build`
npm ERR! Exit status 7
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     [censored]\AppData\Roaming\npm-cache\_logs\2020-09-13T11_52_00_853Z-debug.log

I am on Next.js 9.5.3, next-optimized-images 3.0.0-canary.10 and Node 12.16.1.

Try this: https://github.com/cyrilwanner/next-optimized-images/issues/186#issuecomment-753632391

When I try build the project in Ubuntu 18.04 it's okay. There are only warnings about MaxListeners.
But inside the Docker build is failed.
Related packages versions
* "next": "9.5.2"

* "next-optimized-images": "3.0.0-canary.10"

Tested docker versions:
* node:12.18.03

* node:12.18.03-alpine

next build output from docker build:
info  - Creating an optimized production build...
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry

(node:28) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 uncaughtException listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:28) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unhandledRejection listeners added to [process]. Use emitter.setMaxListeners() to increase limit
info  - Compiled successfully
info  - Collecting page data...
info  - Generating static pages (0/4)

Error occurred prerendering page "/empty". Read more: https://err.sh/next.js/prerender-error
Error: Babel plugin 'react-optimized-image/plugin' not installed or this component could not be recognized by it.
    at Img (/cc-web/node_modules/react-optimized-image/lib/components/Img.js:119:11)
    at d (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:498)
    at $a (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:39:16)
    at a.b.render (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:476)
    at a.b.read (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:18)
    at renderToString (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:54:364)
    at Object.renderPage (/cc-web/node_modules/next/dist/next-server/server/render.js:48:686)
    at Function.getInitialProps (/cc-web/.next/server/pages/_document.js:364:19)
    at loadGetInitialProps (/cc-web/node_modules/next/dist/next-server/lib/utils.js:5:101)
    at renderToHTML (/cc-web/node_modules/next/dist/next-server/server/render.js:48:977)

Error occurred prerendering page "/sitemap". Read more: https://err.sh/next.js/prerender-error
Error: Babel plugin 'react-optimized-image/plugin' not installed or this component could not be recognized by it.
    at Img (/cc-web/node_modules/react-optimized-image/lib/components/Img.js:119:11)
    at d (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:498)
    at $a (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:39:16)
    at a.b.render (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:476)
    at a.b.read (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:18)
    at renderToString (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:54:364)
    at Object.renderPage (/cc-web/node_modules/next/dist/next-server/server/render.js:48:686)
    at Function.getInitialProps (/cc-web/.next/server/pages/_document.js:364:19)
    at loadGetInitialProps (/cc-web/node_modules/next/dist/next-server/lib/utils.js:5:101)
    at renderToHTML (/cc-web/node_modules/next/dist/next-server/server/render.js:48:977)
info  - Generating static pages (1/4)
info  - Generating static pages (2/4)

Error occurred prerendering page "/404". Read more: https://err.sh/next.js/prerender-error
Error: Babel plugin 'react-optimized-image/plugin' not installed or this component could not be recognized by it.
    at Img (/cc-web/node_modules/react-optimized-image/lib/components/Img.js:119:11)
    at d (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:498)
    at $a (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:39:16)
    at a.b.render (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:476)
    at a.b.read (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:18)
    at renderToString (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:54:364)
    at Object.renderPage (/cc-web/node_modules/next/dist/next-server/server/render.js:48:686)
    at Function.getInitialProps (/cc-web/.next/server/pages/_document.js:364:19)
    at loadGetInitialProps (/cc-web/node_modules/next/dist/next-server/lib/utils.js:5:101)
    at renderToHTML (/cc-web/node_modules/next/dist/next-server/server/render.js:48:977)
info  - Generating static pages (3/4)

Error occurred prerendering page "/about". Read more: https://err.sh/next.js/prerender-error
Error: Babel plugin 'react-optimized-image/plugin' not installed or this component could not be recognized by it.
    at Img (/cc-web/node_modules/react-optimized-image/lib/components/Img.js:119:11)
    at d (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:498)
    at $a (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:39:16)
    at a.b.render (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:476)
    at a.b.read (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:18)
    at renderToString (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:54:364)
    at Object.renderPage (/cc-web/node_modules/next/dist/next-server/server/render.js:48:686)
    at Function.getInitialProps (/cc-web/.next/server/pages/_document.js:364:19)
    at loadGetInitialProps (/cc-web/node_modules/next/dist/next-server/lib/utils.js:5:101)
    at renderToHTML (/cc-web/node_modules/next/dist/next-server/server/render.js:48:977)
info  - Generating static pages (4/4)

> Build error occurred
Error: Export encountered errors on following paths:
        /404
        /about
        /empty
        /sitemap
    at exportApp (/cc-web/node_modules/next/dist/export/index.js:24:1103)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async build (/cc-web/node_modules/next/dist/build/index.js:37:212)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
The command '/bin/sh -c yarn build' returned a non-zero code: 1

Try this: https://github.com/cyrilwanner/next-optimized-images/issues/186#issuecomment-753632391

When I try build the project in Ubuntu 18.04 it's okay. There are only warnings about MaxListeners.
But inside the Docker build is failed.
Related packages versions
* "next": "9.5.2"

* "next-optimized-images": "3.0.0-canary.10"

Tested docker versions:
* node:12.18.03

* node:12.18.03-alpine

next build output from docker build:
info  - Creating an optimized production build...
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry

(node:28) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 uncaughtException listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:28) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unhandledRejection listeners added to [process]. Use emitter.setMaxListeners() to increase limit
info  - Compiled successfully
info  - Collecting page data...
info  - Generating static pages (0/4)

Error occurred prerendering page "/empty". Read more: https://err.sh/next.js/prerender-error
Error: Babel plugin 'react-optimized-image/plugin' not installed or this component could not be recognized by it.
    at Img (/cc-web/node_modules/react-optimized-image/lib/components/Img.js:119:11)
    at d (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:498)
    at $a (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:39:16)
    at a.b.render (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:476)
    at a.b.read (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:18)
    at renderToString (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:54:364)
    at Object.renderPage (/cc-web/node_modules/next/dist/next-server/server/render.js:48:686)
    at Function.getInitialProps (/cc-web/.next/server/pages/_document.js:364:19)
    at loadGetInitialProps (/cc-web/node_modules/next/dist/next-server/lib/utils.js:5:101)
    at renderToHTML (/cc-web/node_modules/next/dist/next-server/server/render.js:48:977)

Error occurred prerendering page "/sitemap". Read more: https://err.sh/next.js/prerender-error
Error: Babel plugin 'react-optimized-image/plugin' not installed or this component could not be recognized by it.
    at Img (/cc-web/node_modules/react-optimized-image/lib/components/Img.js:119:11)
    at d (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:498)
    at $a (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:39:16)
    at a.b.render (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:476)
    at a.b.read (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:18)
    at renderToString (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:54:364)
    at Object.renderPage (/cc-web/node_modules/next/dist/next-server/server/render.js:48:686)
    at Function.getInitialProps (/cc-web/.next/server/pages/_document.js:364:19)
    at loadGetInitialProps (/cc-web/node_modules/next/dist/next-server/lib/utils.js:5:101)
    at renderToHTML (/cc-web/node_modules/next/dist/next-server/server/render.js:48:977)
info  - Generating static pages (1/4)
info  - Generating static pages (2/4)

Error occurred prerendering page "/404". Read more: https://err.sh/next.js/prerender-error
Error: Babel plugin 'react-optimized-image/plugin' not installed or this component could not be recognized by it.
    at Img (/cc-web/node_modules/react-optimized-image/lib/components/Img.js:119:11)
    at d (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:498)
    at $a (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:39:16)
    at a.b.render (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:476)
    at a.b.read (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:18)
    at renderToString (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:54:364)
    at Object.renderPage (/cc-web/node_modules/next/dist/next-server/server/render.js:48:686)
    at Function.getInitialProps (/cc-web/.next/server/pages/_document.js:364:19)
    at loadGetInitialProps (/cc-web/node_modules/next/dist/next-server/lib/utils.js:5:101)
    at renderToHTML (/cc-web/node_modules/next/dist/next-server/server/render.js:48:977)
info  - Generating static pages (3/4)

Error occurred prerendering page "/about". Read more: https://err.sh/next.js/prerender-error
Error: Babel plugin 'react-optimized-image/plugin' not installed or this component could not be recognized by it.
    at Img (/cc-web/node_modules/react-optimized-image/lib/components/Img.js:119:11)
    at d (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:498)
    at $a (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:39:16)
    at a.b.render (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:476)
    at a.b.read (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:44:18)
    at renderToString (/cc-web/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:54:364)
    at Object.renderPage (/cc-web/node_modules/next/dist/next-server/server/render.js:48:686)
    at Function.getInitialProps (/cc-web/.next/server/pages/_document.js:364:19)
    at loadGetInitialProps (/cc-web/node_modules/next/dist/next-server/lib/utils.js:5:101)
    at renderToHTML (/cc-web/node_modules/next/dist/next-server/server/render.js:48:977)
info  - Generating static pages (4/4)

> Build error occurred
Error: Export encountered errors on following paths:
        /404
        /about
        /empty
        /sitemap
    at exportApp (/cc-web/node_modules/next/dist/export/index.js:24:1103)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async build (/cc-web/node_modules/next/dist/build/index.js:37:212)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
The command '/bin/sh -c yarn build' returned a non-zero code: 1

Try this: https://github.com/cyrilwanner/next-optimized-images/issues/186#issuecomment-753632391


redis客户端连接codis后报错

redis客户端连接codis后报错
2016-04-19 15:31:03 : Init app log
2016-04-19 15:31:03 : Current ratio width:0.625
2016-04-19 15:31:03 : Current ratio height:0.722222
2016-04-19 15:31:06 : Click on tree item: 1
2016-04-19 15:31:06 : Connection: AUTH
2016-04-19 15:31:06 : Connection: <IP_ADDRESS> > connected
2016-04-19 15:31:06 : Connection: <IP_ADDRESS> > [runCommand] PING
2016-04-19 15:31:06 : Connection: <IP_ADDRESS> > [runCommand] PING -> response received : +PONG
2016-04-19 15:31:06 : Connection: <IP_ADDRESS> > [runCommand] INFO
2016-04-19 15:31:06 : Connection: <IP_ADDRESS> > [runCommand] INFO -> response received : Bulk
2016-04-19 15:31:06 : Connection: AUTH OK
2016-04-19 15:31:06 : Connection: <IP_ADDRESS> > [runCommand] info
2016-04-19 15:31:06 : Connection: <IP_ADDRESS> > [runCommand] info -> response received : Bulk
2016-04-19 15:31:06 : Connection: <IP_ADDRESS> > [runCommand] select 0
2016-04-19 15:31:06 : Connection: <IP_ADDRESS> > [runCommand] select 0 -> response received : +OK
2016-04-19 15:31:06 : Connection: <IP_ADDRESS> > [runCommand] select 1
2016-04-19 15:31:06 : Connection: <IP_ADDRESS> > [runCommand] select 1 -> response received : -ERR invalid DB index, only accept DB 0
2016-04-19 15:31:06 : Click on tree item: 1
客户端工具是 redis desktop manager

codis 不支持 select db，只支持 db 0

@spinlock 好的 谢谢

@spinlock 什么客户端工具可以管理codis呢？

文档里面写了啊。codis 自带 dashboard，不过我们缺专业前端，所以dashboard 写的比较简陋。但是可以用！

@spinlock 呵呵 好的谢谢


Add support for Gemalto Safenet eToken cards

As requested in https://github.com/open-eid/chrome-token-signing/issues/217.
WE2-716

The first draft is available now at https://github.com/web-eid/web-eid-app/pull/231. The binaries or the installer are available from the last build of the pull request and everyone is invited to experiment if their cards work as expected in Windows. Please note that this is still a draft, there may be bugs, it may crash, it does not properly report when PIN is wrong, remaining PIN retries etc.


Support Queries as well as Commands

Ultimately Brighter has a companion piece that supports a Query. It would have a signature something like (pseudocode) TResult Query<TResult, TArg>(IDictionary<string, TArg>) but might also be something similar to OWIN middleware: Func<IDictionary<string, object>, Task>
It needs to support:

Retry and Circuit Breaker
Fallback (i.e. to cache,which we may want to provide help with)

So it is somewhat alike to Brighter in that it has QoS attributes, but it has a different signature and might even be composed in a more OWIN like way.
For now I think this is a separate project, Darker perhaps, that we can be used stand-alone from Brighter. There may be some code covergence, but there might not.
It's on our list to tackle, but management and monitoring, polyglot support, and multiple brokers backbones are first. For now. But once the basics of those are done I may break ground on this to define the vision for it.

There is a seperate project Darker, in stealth mode over this.


Some questions of RobotMsg in umbra rosbag

Is that any explanation of RobotMsg? Such as the meaning and value of "motion_status", "motion_mode" and "tau".

motion_mode(int): operating mode of the arm
0: position control mode
1: servo motion mode, users must set to this mode first before using the moveto_servoj interface.
2: joint teaching mode
3: cartesian teaching mode (NOT used in current version)
motion_status(int): Current running status
1: Moving
2: Sleeping, ready to motion
3: Paused
4: Stopping
tau is the current real-time output torque of the joint in N.m


WIP: Fetch Adapter v2

Coming soon, filed here for CI

[ ] Needs updated examples
[ ] Needs updated docs
[ ] Needs testing with optionalDependencies
[ ] Separate PR boundaries

[ ] Fetch core
[ ] Fetch examples + docs


Document policies need for each integration

Testing my first spring-cloud-aws app these days, deploying to ECS
I have a task-role for my task-definition, and are running into multiple rollback/deploy of the stack, adding more and more policies to grant the autodetection for stacks enough privileges.
It would be nice if you could document the exact privileges needed for spring-cloud-aws.

In fact, we need to document required IAM permissions for each integration.

I believe we can close this issue @maciejwalkowiak

I believe we can close this issue @maciejwalkowiak

Policies can be found now in the reference docs: https://docs.awspring.io/spring-cloud-aws/docs/2.3.0.BUILD-SNAPSHOT/reference/html/index.html


Builtin health proto

More difficult than expected, but a potential solution for built-in health.proto file usage/consumption with UI adjustment to simply select it without requiring user to fill in all the values.
addresses https://github.com/zalopay-oss/jmeter-grpc-request/issues/37

Hi, @dhartford, I will close this pull request since the idea needs to become more generalized and avoid hard-coding a value in the code base. I am very appreciative of your PR, but so far, we don't have many use cases request for this feature


[IDEA] Better Minecarts for 1.20.1

add support for 3D rails from Xannosz's Better minecarts (including dead end) for Minecraft 1.20.1
CurseForge page: https://www.curseforge.com/minecraft/mc-mods/xannoszs-better-minecarts

Added Support in v1.2
https://legacy.curseforge.com/minecraft/texture-packs/rays-3d-rails/files/4773862
https://modrinth.com/resourcepack/rays-3d-rails/version/1.2
If you find any bugs or if your unhappy with the textures, let me know
~ Ray


[Bug]: on clicking the "Get Started" button Error 404 (file not found ) is coming

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
In Ambulance tracking system site when i click on GET STARTED button, then the page is not opening . it is showing the Error 404(File not found). so i want to add a page in which while clicking on GET STARTED button it will show me the buttons of accessing the features of this site and a very improved UI.
Please assign me this issue under the labels of Gssoc-extd, hacktoberfest, hacktoberfest-accepted and relevant level.
Add Screenshots

What browsers are you seeing the problem on?
Chrome
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

Hey please assign me my level and the correct label of Girl script summer of code i.e. " gssoc-ext "

Please assign me as soon as possible you can so that i can start working over it

Thank you for assigning me this issue. I will resolve this issue very soon .

Thank you for assigning me this issue. I will resolve this issue very soon .

its' resolved now. but homepage breakdown now. you can fix that

Thank you for assigning me this issue. I will resolve this issue very soon .

get started have been resolved actually,

Actually I when I was going to contribute over it I saw that the issue has been closed.
now I have a doubt that is I will get the scores of this issue or not ?

Actually I when I was going to contribute over it I saw that the issue has been closed. now I have a doubt that is I will get the scores of this issue or not ?

already done get started.

Ok. Is I will got the points for this issue or not ?

Ok. Is I will got the points for this issue or not ?

i am beginner also, actually don't know

Ok. Is I will got the points for this issue or not ?

i have no idea, i am beginner also. you can ask from program manager

Ok , No issue
Thank you


Question: How does material-ui hoist build files from /build?

I hope that it's okay that I ask this here. If not, then I would love to be pointed to a suitable forum.
I am attempting to build a project with a similar architecture as Material-ui, where it's possible to import modules like import { subModule } from '@lib/module/subModules'
I see that the Material-ui packages are built and output into a build directory at each package root; however, when consuming the library from node_modules, each build artefact that previously lived in build has been moved to the root level of the package.
In simple terms: How does packages/material-ui/core/build/Component become node_modules/@material-ui/core/Component?
Big thanks for reading and taking the time to answer!

@vilbergs Have a look at the codesandbox-ci build commands, it will be a great starting point for reverse-engineering.

@oliviertassinari Thanks for your lightning speed answer!


Product Dashboard not displaying any data in Commit section and Deploy stage

We started CI/CD only for Dev environment intially.
We have Hygieia 3.0.2 version, NPM version 6.4.1 and Node 10.11.1.
We have SVN for repo widget and Jenkins for build widget and both are configured in Team Dashboard using collectors and data is refelected in repo widget as soon as developer commits the code in SVN. But nothing is displayed in Commit stage and Build stage in product dashboard, however I can see data in Build stage.
Apart from that, I am using Hygieia publisher plug-in for deployment and changes in team dashboard reflected in deployment widget. The same SVN branch is configured in deployment job for build and deploy as in CI job in Jenkins.
We tried to look into pipeline table in mongodb, I can only see two stages Build and Dev (Deployment), seems commit stage is missing.
We also tried to clear the browser data with no success.
Can anyone please help me on this.

Mongodb Pipeline collection:

I have 1 dummy commit in SVN without executing CI/CD.

Please do the needful.

@vivekshm I have the same issue. Have you found the fix?

 The Dashboard will show the data if its capable of capturing the commits part of a build and if the build also performed deploy to an environment.

looking at the toolset, I dont believe we have a collector available for MS Build.

@vivekshm I have the same issue. Have you found the fix?
Not yet.

looking at the toolset, I dont believe we have a collector available for MS Build.
We are using jenkins collector and shown in build widget.
We have done dummy commit to SVN and build it through jenkins and then deployed to dev environment, but not getting anything in the Build and Deploy stage in Product dashboard, however the changes are reflected in the team dashboard SVN repo, Deploy and Jenkins widgets.

Can anyone help me to troubleshoot, any configurations  required more to achieve the same.

@vivekshm Since you don't have a means to collect the build information from your build solution (MSBUILD) and feed Hygieia this will not work for you. If you are familiar with the apis exposed by MSBUILD you may try creating a collector for collecting data from MSBUILD and feed to hygieia. You may take hygieia-build-jenkins-collector or hygieia-build-bamboo-collector as reference for building your collector. Without the information about builds we cannot associate the commits to build and hence deployment

Thanks Ragha for feedback. I am already using Jenkins collector for build in Team dashboard. PFA the screenshot. Let me know if you required any further info.

@vivekshm for the deploy can you share you configured the deploystep in your jenkins pipeline.

Once the artifacts are successfully deployed to dev environment using MSDeploy. I used Hygieia Publisher plugin to push the notification to Hygieia UI. Please find the below screenshot

Did you get a chance to see the issue Ragha?

I don't believe the SVN collector has not been updated to handle commit data for the product dashboard. See https://github.com/Hygieia/Hygieia/issues/1333 for more details


Fix ID replacements not being performed in style elements

Problem
svg-inject does not add suffixes to IDs located in style elements; it only replaces url(#id) references. This breaks styles and animations such as those exported by SVGator due to "standalone" IDs not being suffixed, when the makeIdsUnique option is enabled.
Fix
Replace the regex for id replacements in the style element with a more generalized one that matches #id as well as url(#id) (as before).
Although this is a much more generalized regex, as far as I know this shouldn't cause issues with fancy CSS syntax.
Example
Original SVG
<style>
    <![CDATA[#emVKjsoi9OL2 {animation: emVKjsoi9OL2_c_o 8000ms linear 1 normal forwards}@keyframes emVKjsoi9OL2_c_o { 0% {opacity: 0} 2.5% {opacity: 1} 100% {opacity: 1}} #emVKjsoi9OL3 {animation: emVKjsoi9OL3_c_o 8000ms linear 1 normal forwards}@keyframes emVKjsoi9OL3_c_o { 0% {opacity: 0} 83.75% {opacity: 0} 86.25% {opacity: 1} 100% {opacity: 1}} #emVKjsoi9OL4 {animation: emVKjsoi9OL4_s_do 8000ms linear 1 normal forwards}@keyframes emVKjsoi9OL4_s_do { 0% {stroke-dashoffset: 500} 2.5% {stroke-dashoffset: 500} 99.875% {stroke-dashoffset: 50} 100% {stroke-dashoffset: 50}}]]>
</style>

After injection with unfixed svg-inject
Styles stay exactly the same after injection, disconnecting styles from the now-suffixed elements in the SVG body.
After injection with this pull request
<style>
    <![CDATA[#emVKjsoi9OL2--inject-1 {animation: emVKjsoi9OL2_c_o 8000ms linear 1 normal forwards}@keyframes emVKjsoi9OL2_c_o { 0% {opacity: 0} 2.5% {opacity: 1} 100% {opacity: 1}} #emVKjsoi9OL3--inject-1 {animation: emVKjsoi9OL3_c_o 8000ms linear 1 normal forwards}@keyframes emVKjsoi9OL3_c_o { 0% {opacity: 0} 83.75% {opacity: 0} 86.25% {opacity: 1} 100% {opacity: 1}} #emVKjsoi9OL4--inject-1 {animation: emVKjsoi9OL4_s_do 8000ms linear 1 normal forwards}@keyframes emVKjsoi9OL4_s_do { 0% {stroke-dashoffset: 500} 2.5% {stroke-dashoffset: 500} 99.875% {stroke-dashoffset: 50} 100% {stroke-dashoffset: 50}}]]>
</style>

Oh and by the way I also added a .nvmrc file because the svg-inject gulp task fails on recent node.js versions. I hope that's OK. I did not do further tests to see which maximum version of node.js svg-inject works with, but node.js 10.5.0 is fine. Feel free to change that to a more appropriate version.

Great! Works on my app.


transformations fail (intermittently) on functions of a variable with a strided axis

Reported by andrew wittenberg on 21 Sep 2009 23:20 UTC
In trying to work around bug #1691, I ran into this.  Does this give any insight into bug #1691?
Strangely, I only get the error on the first try -- when I repeat the same command, I seem get the plot just fine.  Perhaps something isn't being initialized properly?
(My actual application is slightly more complex -- I'm computing a correlation from 2 time-strided variables that share a time axis.  The definitions and time-striding of the variables can change, and I'd like to then be able to plot the correlation map.  But Ferret is somehow choking on the temporary axes created with the likes of l=1:132:12.)
        NOAA/PMEL TMAP
        FERRET v6.203
        Linux(g77) 2.4.21-32 - 06/26/09
        21-Sep-09 19:09

yes? use monthly_navy_winds
yes? let a = uwnd[let adev = a-a[l=@ave](l=1:132:12]
yes?)
yes? shade adev[**ERROR: inconsistent sizes of data regions: can't label T axis of A[L=@AVE](l=@max]
)
yes? shade adev[l=@max]

Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1693

Comment by ansley.b.manke on 22 Sep 2009 20:21 UTC
Some comments -
This is not related to bug #1691.
Also, it goes back to (at least) v5.81, so it is not something we introduced with the native strides syntax. The message happens in  "merge_context". Comparing with how the code works when striding hasn't been used should turn up something.

Comment by andrew.wittenberg on 23 Sep 2009 23:24 UTC
Not sure if this helps, but here's an example with striding applied after the transformation.  The first attempt to plot B fails, while the second one works.  However, B works on the first try if I define A with l=1:132@shf:12 rather than l=@shf:12.
        NOAA/PMEL TMAP
        FERRET v6.203
        Linux(g77) 2.4.21-32 - 06/26/09
        23-Sep-09 19:08

yes? use monthly_navy_winds
yes? let a = uwnd[let b = samplel(a,t[l=1:132:12](x=140w,y=0,l=@shf:12]
yes?))
yes? plot b
 **ERROR: illegal limits: UWND does not exist at L=133
          Axis extremes are L=1:132
yes? plot a
yes? plot b

Modified by ansley.b.manke on 5 Jan 2011 19:33 UTC

Modified by ansley.b.manke on 5 Jan 2011 19:35 UTC

Modified by ansley.b.manke on 22 Aug 2014 22:15 UTC

This is fixed in flesh_out_axis.F
When variables consist of several expressions, there's a "merge-context" process.  For regions defined with strides (dynamic grids in the Ferret terminology), part of this logic was skipped over, so the context was not seen as defined.


Add install instructions to Reademe.md

Hey @AchoArnold!
Cool, install instruction might be useful for some people.
Thanks for your contribution.