New Label: Horos

"Horos™ is a free, open source medical image viewer. The goal of the Horos Project is to develop a fully functional, 64-bit medical image viewer for OS X. Horos is based upon OsiriX and other open source medical imaging libraries. Horos is made freely available under the GNU Lesser General Public License, Version 3 (LGPL-3.0)"
./assemble.sh -l /Desktop/Mosyle/Resources/InstallomatorLabels horos
2022-07-04 23:48:31 : REQ   : horos : ################## Start Installomator v. 10.0beta, date 2022-07-04
2022-07-04 23:48:31 : INFO  : horos : ################## Version: 10.0beta
2022-07-04 23:48:31 : INFO  : horos : ################## Date: 2022-07-04
2022-07-04 23:48:31 : INFO  : horos : ################## horos
2022-07-04 23:48:31 : DEBUG : horos : DEBUG mode 1 enabled.
2022-07-04 23:48:31 : INFO  : horos : BLOCKING_PROCESS_ACTION=tell_user
2022-07-04 23:48:31 : INFO  : horos : NOTIFY=success
2022-07-04 23:48:31 : INFO  : horos : LOGGING=DEBUG
2022-07-04 23:48:31 : INFO  : horos : LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2022-07-04 23:48:31 : INFO  : horos : Label type: dmg
2022-07-04 23:48:31 : INFO  : horos : archiveName: Horos.dmg
2022-07-04 23:48:31 : INFO  : horos : no blocking processes defined, using Horos as default
2022-07-04 23:48:31 : DEBUG : horos : Changing directory to /Users/savvas/Desktop/Mosyle/Resources/Installomator-main original/build
2022-07-04 23:48:31 : INFO  : horos : App(s) found: /Applications/Horos.app
2022-07-04 23:48:32 : INFO  : horos : found app at /Applications/Horos.app, version Horos v4.0.0 RC5, on versionKey CFBundleGetInfoString
2022-07-04 23:48:32 : INFO  : horos : appversion: Horos v4.0.0 RC5
2022-07-04 23:48:32 : INFO  : horos : Latest version of Horos is 4.0.0RC5
2022-07-04 23:48:32 : INFO  : horos : Horos.dmg exists and DEBUG mode 1 enabled, skipping download
2022-07-04 23:48:32 : DEBUG : horos : DEBUG mode 1, not checking for blocking processes
2022-07-04 23:48:32 : REQ   : horos : Installing Horos
2022-07-04 23:48:32 : INFO  : horos : Mounting /Users/savvas/Desktop/Mosyle/Resources/Installomator-main original/build/Horos.dmg
2022-07-04 23:48:33 : DEBUG : horos : Debugging enabled, dmgmount output was:
SOFTWARE LICENSE: By initiating this download and installation you
acknowledge and agree that this software application is not intended
for medical usage or diagnostic purposes.
============================================
Horos is free software: you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published
by the Free Software Foundation,  version 3 of the License.
The Horos Project was based originally upon the OsiriX Project which
at the time of the code fork was licensed as a LGPL project.  However,
not all of the the source-code was properly documented and file
headers were not all updated with the appropriate license terms.
The Horos Project, originally was licensed under the  GNU GPL
license. However, contributors to the software since that time have
agreed to modify the license to the GNU LGPL in order to be conform
to the changes previously made to the OsiriX Project.
Horos is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY EXPRESS OR IMPLIED, INCLUDING ANY WARRANTY OF
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE OR USE.
See the GNU Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with Horos.  If not, see
http://www.gnu.org/licenses/lgpl.html
Prior versions of this file were published by the OsiriX team
pursuant to the below notice and licensing protocol.
============================================
Program:   OsiriX Copyright (c) OsiriX Team All rights
reserved. Distributed under GNU - LGPL   See
http://www.osirix-viewer.com/copyright.html for details.
This software is distributed WITHOUT ANY WARRANTY; without even the
implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
============================================
This version of Horos is linked against the Grok JPEG 2000 library,
for fast viewing of JPEG 2000 images.
https://github.com/GrokImageCompression/grok
The Grok JPEG 2000 library is licensed under the terms of the GNU
Affero General Public License as follows
Copyright (C) 2016 Grok Image Compression Inc.
This program is free software: you can redistribute it and/or  modify
it under the terms of the GNU Affero General Public License, version
3, as published by the Free Software Foundation.
This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public
License along with this program.  If not, see
http://www.gnu.org/licenses/.
============================================
GNU LESSER GENERAL PUBLIC LICENSE
GNU LESSER GENERAL PUBLIC LICENSE Version 3, 29 June 2007
Copyright © 2007 Free Software Foundation, Inc. https://fsf.org/
Everyone is permitted to copy and distribute verbatim copies of
this license document, but changing it is not allowed.
This version of the GNU Lesser General Public License incorporates
the terms and conditions of version 3 of the GNU General Public
License, supplemented by the additional permissions listed below.

Additional Definitions.  As used herein, “this License” refers
to version 3 of the GNU Lesser General Public License, and the “GNU
GPL” refers to version 3 of the GNU General Public License.

“The Library” refers to a covered work governed by this License,
other than an Application or a Combined Work as defined below.
An “Application” is any work that makes use of an interface provided
by the Library, but which is not otherwise based on the Library.
Defining a subclass of a class defined by the Library is deemed a
mode of using an interface provided by the Library.
A “Combined Work” is a work produced by combining or linking an
Application with the Library. The particular version of the Library
with which the Combined Work was made is also called the “Linked
Version”.
The “Minimal Corresponding Source” for a Combined Work means the
Corresponding Source for the Combined Work, excluding any source
code for portions of the Combined Work that, considered in isolation,
are based on the Application, and not on the Linked Version.
The “Corresponding Application Code” for a Combined Work means the
object code and/or source code for the Application, including any
data and utility programs needed for reproducing the Combined Work
from the Application, but excluding the System Libraries of the
Combined Work.

Exception to Section 3 of the GNU GPL.  You may convey a covered
work under sections 3 and 4 of this License without being bound by
section 3 of the GNU GPL.

Conveying Modified Versions.  If you modify a copy of the Library,
and, in your modifications, a facility refers to a function or data
to be supplied by an Application that uses the facility (other than
as an argument passed when the facility is invoked), then you may
convey a copy of the modified version:

a) under this License, provided that you make a good faith effort
to ensure that, in the event an Application does not supply the
function or data, the facility still operates, and performs whatever
part of its purpose remains meaningful, or b) under the GNU GPL,
with none of the additional permissions of this License applicable
to that copy.  3. Object Code Incorporating Material from Library
Header Files.  The object code form of an Application may incorporate
material from a header file that is part of the Library. You may
convey such object code under terms of your choice, provided that,
if the incorporated material is not limited to numerical parameters,
data structure layouts and accessors, or small macros, inline
functions and templates (ten or fewer lines in length), you do both
of the following:
a) Give prominent notice with each copy of the object code that the
Library is used in it and that the Library and its use are covered
by this License.  b) Accompany the object code with a copy of the
GNU GPL and this license document.  4. Combined Works.  You may
convey a Combined Work under terms of your choice that, taken
together, effectively do not restrict modification of the portions
of the Library contained in the Combined Work and reverse engineering
for debugging such modifications, if you also do each of the
following:
a) Give prominent notice with each copy of the Combined Work that
the Library is used in it and that the Library and its use are
covered by this License.  b) Accompany the Combined Work with a
copy of the GNU GPL and this license document.  c) For a Combined
Work that displays copyright notices during execution, include the
copyright notice for the Library among these notices, as well as a
reference directing the user to the copies of the GNU GPL and this
license document.  d) Do one of the following: 0) Convey the Minimal
Corresponding Source under the terms of this License, and the
Corresponding Application Code in a form suitable for, and under
terms that permit, the user to recombine or relink the Application
with a modified version of the Linked Version to produce a modified
Combined Work, in the manner specified by section 6 of the GNU GPL
for conveying Corresponding Source.  1) Use a suitable shared library
mechanism for linking with the Library. A suitable mechanism is one
that (a) uses at run time a copy of the Library already present on
the user's computer system, and (b) will operate properly with a
modified version of the Library that is interface-compatible with
the Linked Version.  e) Provide Installation Information, but only
if you would otherwise be required to provide such information under
section 6 of the GNU GPL, and only to the extent that such information
is necessary to install and execute a modified version of the
Combined Work produced by recombining or relinking the Application
with a modified version of the Linked Version. (If you use option
4d0, the Installation Information must accompany the Minimal
Corresponding Source and Corresponding Application Code. If you use
option 4d1, you must provide the Installation Information in the
manner specified by section 6 of the GNU GPL for conveying Corresponding
Source.) 5. Combined Libraries.  You may place library facilities
that are a work based on the Library side by side in a single library
together with other library facilities that are not Applications
and are not covered by this License, and convey such a combined
library under terms of your choice, if you do both of the following:
a) Accompany the combined library with a copy of the same work based
on the Library, uncombined with any other library facilities,
conveyed under the terms of this License.  b) Give prominent notice
with the combined library that part of it is a work based on the
Library, and explaining where to find the accompanying uncombined
form of the same work.  6. Revised Versions of the GNU Lesser General
Public License.  The Free Software Foundation may publish revised
and/or new versions of the GNU Lesser General Public License from
time to time. Such new versions will be similar in spirit to the
present version, but may differ in detail to address new problems
or concerns.
Each version is given a distinguishing version number. If the Library
as you received it specifies that a certain numbered version of the
GNU Lesser General Public License “or any later version” applies
to it, you have the option of following the terms and conditions
either of that published version or of any later version published
by the Free Software Foundation. If the Library as you received it
does not specify a version number of the GNU Lesser General Public
License, you may choose any version of the GNU Lesser General Public
License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide
whether future versions of the GNU Lesser General Public License
shall apply, that proxy's public statement of acceptance of any
version is permanent authorization for you to choose that version
for the Library.
===============================================================================================================
GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007
Copyright © 2007 Free Software Foundation, Inc. https://fsf.org/
Everyone is permitted to copy and distribute verbatim copies of
this license document, but changing it is not allowed.
Preamble The GNU General Public License is a free, copyleft license
for software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom
to share and change all versions of a program--to make sure it
remains free software for all its users. We, the Free Software
Foundation, use the GNU General Public License for most of our
software; it applies also to any other work released this way by
its authors. You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that
you have the freedom to distribute copies of free software (and
charge for them if you wish), that you receive source code or can
get it if you want it, that you can change the software or use
pieces of it in new free programs, and that you know you can do
these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you
have certain responsibilities if you distribute copies of the
software, or if you modify it: responsibilities to respect the
freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too,
receive or can get the source code. And you must show them these
terms so they know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users'
and authors' sake, the GPL requires that modified versions be marked
as changed, so that their problems will not be attributed erroneously
to authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the
manufacturer can do so. This is fundamentally incompatible with the
aim of protecting users' freedom to change the software. The
systematic pattern of such abuse occurs in the area of products for
individuals to use, which is precisely where it is most unacceptable.
Therefore, we have designed this version of the GPL to prohibit the
practice for those products. If such problems arise substantially
in other domains, we stand ready to extend this provision to those
domains in future versions of the GPL, as needed to protect the
freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we
wish to avoid the special danger that patents applied to a free
program could make it effectively proprietary. To prevent this, the
GPL assures that patents cannot be used to render the program
non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS 0. Definitions.  “This License” refers to
version 3 of the GNU General Public License.
“Copyright” also means copyright-like laws that apply to other kinds
of works, such as semiconductor masks.
“The Program” refers to any copyrightable work licensed under this
License. Each licensee is addressed as “you”. “Licensees” and
“recipients” may be individuals or organizations.
To “modify” a work means to copy from or adapt all or part of the
work in a fashion requiring copyright permission, other than the
making of an exact copy. The resulting work is called a “modified
version” of the earlier work or a work “based on” the earlier work.
A “covered work” means either the unmodified Program or a work based
on the Program.
To “propagate” a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it
on a computer or modifying a private copy. Propagation includes
copying, distribution (with or without modification), making available
to the public, and in some countries other activities as well.
To “convey” a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user
through a computer network, with no transfer of a copy, is not
conveying.
An interactive user interface displays “Appropriate Legal Notices”
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to
the extent that warranties are provided), that licensees may convey
the work under this License, and how to view a copy of this License.
If the interface presents a list of user commands or options, such
as a menu, a prominent item in the list meets this criterion.

Source Code.  The “source code” for a work means the preferred
form of the work for making modifications to it. “Object code” means
any non-source form of a work.

A “Standard Interface” means an interface that either is an official
standard defined by a recognized standards body, or, in the case
of interfaces specified for a particular programming language, one
that is widely used among developers working in that language.
The “System Libraries” of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form
of packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
“Major Component”, in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The “Corresponding Source” for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts
to control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available
free programs which are used unmodified in performing those activities
but which are not part of the work. For example, Corresponding
Source includes interface definition files associated with source
files for the work, and the source code for shared libraries and
dynamically linked subprograms that the work is specifically designed
to require, such as by intimate data communication or control flow
between those subprograms and other parts of the work.
The Corresponding Source need not include anything that users can
regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.

Basic Permissions.  All rights granted under this License are
granted for the term of copyright on the Program, and are irrevocable
provided the stated conditions are met. This License explicitly
affirms your unlimited permission to run the unmodified Program.
The output from running a covered work is covered by this License
only if the output, given its content, constitutes a covered work.
This License acknowledges your rights of fair use or other equivalent,
as provided by copyright law.

You may make, run and propagate covered works that you do not convey,
without conditions so long as your license otherwise remains in
force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide
you with facilities for running those works, provided that you
comply with the terms of this License in conveying all material for
which you do not control copyright. Those thus making or running
the covered works for you must do so exclusively on your behalf,
under your direction and control, on terms that prohibit them from
making any copies of your copyrighted material outside their
relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section
10 makes it unnecessary.

Protecting Users' Legal Rights From Anti-Circumvention Law.  No
covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.

When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect
to the covered work, and you disclaim any intention to limit operation
or modification of the work as a means of enforcing, against the
work's users, your or third parties' legal rights to forbid
circumvention of technological measures.

Conveying Verbatim Copies.  You may convey verbatim copies of
the Program's source code as you receive it, in any medium, provided
that you conspicuously and appropriately publish on each copy an
appropriate copyright notice; keep intact all notices stating that
this License and any non-permissive terms added in accord with
section 7 apply to the code; keep intact all notices of the absence
of any warranty; and give all recipients a copy of this License
along with the Program.

You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.

Conveying Modified Source Versions.  You may convey a work based
on the Program, or the modifications to produce it from the Program,
in the form of source code under the terms of section 4, provided
that you also meet all of these conditions:

a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.  b) The work must carry prominent
notices stating that it is released under this License and any
conditions added under section 7. This requirement modifies the
requirement in section 4 to “keep intact all notices”.  c) You must
license the entire work, as a whole, under this License to anyone
who comes into possession of a copy. This License will therefore
apply, along with any applicable section 7 additional terms, to the
whole of the work, and all its parts, regardless of how they are
packaged. This License gives no permission to license the work in
any other way, but it does not invalidate such permission if you
have separately received it.  d) If the work has interactive user
interfaces, each must display Appropriate Legal Notices; however,
if the Program has interactive interfaces that do not display
Appropriate Legal Notices, your work need not make them do so.  A
compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called
an “aggregate” if the compilation and its resulting copyright are
not used to limit the access or legal rights of the compilation's
users beyond what the individual works permit. Inclusion of a covered
work in an aggregate does not cause this License to apply to the
other parts of the aggregate.

Conveying Non-Source Forms.  You may convey a covered work in
object code form under the terms of sections 4 and 5, provided that
you also convey the machine-readable Corresponding Source under the
terms of this License, in one of these ways:

a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium customarily
used for software interchange.  b) Convey the object code in, or
embodied in, a physical product (including a physical distribution
medium), accompanied by a written offer, valid for at least three
years and valid for as long as you offer spare parts or customer
support for that product model, to give anyone who possesses the
object code either (1) a copy of the Corresponding Source for all
the software in the product that is covered by this License, on a
durable physical medium customarily used for software interchange,
for a price no more than your reasonable cost of physically performing
this conveying of source, or (2) access to copy the Corresponding
Source from a network server at no charge.  c) Convey individual
copies of the object code with a copy of the written offer to provide
the Corresponding Source. This alternative is allowed only occasionally
and noncommercially, and only if you received the object code with
such an offer, in accord with subsection 6b.  d) Convey the object
code by offering access from a designated place (gratis or for a
charge), and offer equivalent access to the Corresponding Source
in the same way through the same place at no further charge. You
need not require recipients to copy the Corresponding Source along
with the object code. If the place to copy the object code is a
network server, the Corresponding Source may be on a different
server (operated by you or a third party) that supports equivalent
copying facilities, provided you maintain clear directions next to
the object code saying where to find the Corresponding Source.
Regardless of what server hosts the Corresponding Source, you remain
obligated to ensure that it is available for as long as needed to
satisfy these requirements.  e) Convey the object code using
peer-to-peer transmission, provided you inform other peers where
the object code and Corresponding Source of the work are being
offered to the general public at no charge under subsection 6d.  A
separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A “User Product” is either (1) a “consumer product”, which means
any tangible personal property which is normally used for personal,
family, or household purposes, or (2) anything designed or sold for
incorporation into a dwelling. In determining whether a product is
a consumer product, doubtful cases shall be resolved in favor of
coverage. For a particular product received by a particular user,
“normally used” refers to a typical or common use of that class of
product, regardless of the status of the particular user or of the
way in which the particular user actually uses, or expects or is
expected to use, the product. A product is a consumer product
regardless of whether the product has substantial commercial,
industrial or non-consumer uses, unless such uses represent the
only significant mode of use of the product.
“Installation Information” for a User Product means any methods,
procedures, authorization keys, or other information required to
install and execute modified versions of a covered work in that
User Product from a modified version of its Corresponding Source.
The information must suffice to ensure that the continued functioning
of the modified object code is in no case prevented or interfered
with solely because modification has been made.
If you convey an object code work under this section in, or with,
or specifically for use in, a User Product, and the conveying occurs
as part of a transaction in which the right of possession and use
of the User Product is transferred to the recipient in perpetuity
or for a fixed term (regardless of how the transaction is characterized),
the Corresponding Source conveyed under this section must be
accompanied by the Installation Information. But this requirement
does not apply if neither you nor any third party retains the ability
to install modified object code on the User Product (for example,
the work has been installed in ROM).
The requirement to provide Installation Information does not include
a requirement to continue to provide support service, warranty, or
updates for a work that has been modified or installed by the
recipient, or for the User Product in which it has been modified
or installed. Access to a network may be denied when the modification
itself materially and adversely affects the operation of the network
or violates the rules and protocols for communication across the
network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.

Additional Terms.  “Additional permissions” are terms that
supplement the terms of this License by making exceptions from one
or more of its conditions. Additional permissions that are applicable
to the entire Program shall be treated as though they were included
in this License, to the extent that they are valid under applicable
law. If additional permissions apply only to part of the Program,
that part may be used separately under those permissions, but the
entire Program remains governed by this License without regard to
the additional permissions.

When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part
of it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material
you add to a covered work, you may (if authorized by the copyright
holders of that material) supplement the terms of this License with
terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or b) Requiring
preservation of specified reasonable legal notices or author
attributions in that material or in the Appropriate Legal Notices
displayed by works containing it; or c) Prohibiting misrepresentation
of the origin of that material, or requiring that modified versions
of such material be marked in reasonable ways as different from the
original version; or d) Limiting the use for publicity purposes of
names of licensors or authors of the material; or e) Declining to
grant rights under trademark law for use of some trade names,
trademarks, or service marks; or f) Requiring indemnification of
licensors and authors of that material by anyone who conveys the
material (or modified versions of it) with contractual assumptions
of liability to the recipient, for any liability that these contractual
assumptions directly impose on those licensors and authors.  All
other non-permissive additional terms are considered “further
restrictions” within the meaning of section 10. If the Program as
you received it, or any part of it, contains a notice stating that
it is governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under
this License, you may add to a covered work material governed by
the terms of that license document, provided that the further
restriction does not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in
the form of a separately written license, or stated as exceptions;
the above requirements apply either way.

Termination.  You may not propagate or modify a covered work
except as expressly provided under this License. Any attempt otherwise
to propagate or modify it is void, and will automatically terminate
your rights under this License (including any patent licenses granted
under the third paragraph of section 11).

However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from
that copyright holder, and you cure the violation prior to 30 days
after your receipt of the notice.
Termination of your rights under this section does not terminate
the licenses of parties who have received copies or rights from you
under this License. If your rights have been terminated and not
permanently reinstated, you do not qualify to receive new licenses
for the same material under section 10.

Acceptance Not Required for Having Copies.  You are not required
to accept this License in order to receive or run a copy of the
Program. Ancillary propagation of a covered work occurring solely
as a consequence of using peer-to-peer transmission to receive a
copy likewise does not require acceptance. However, nothing other
than this License grants you permission to propagate or modify any
covered work. These actions infringe copyright if you do not accept
this License. Therefore, by modifying or propagating a covered work,
you indicate your acceptance of this License to do so.

Automatic Licensing of Downstream Recipients.  Each time you
convey a covered work, the recipient automatically receives a license
from the original licensors, to run, modify and propagate that work,
subject to this License. You are not responsible for enforcing
compliance by third parties with this License.

An “entity transaction” is a transaction transferring control of
an organization, or substantially all assets of one, or subdividing
an organization, or merging organizations. If propagation of a
covered work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or
could give under the previous paragraph, plus a right to possession
of the Corresponding Source of the work from the predecessor in
interest, if the predecessor has it or can get it with reasonable
efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging
that any patent claim is infringed by making, using, selling,
offering for sale, or importing the Program or any portion of it.

Patents.  A “contributor” is a copyright holder who authorizes
use under this License of the Program or a work on which the Program
is based. The work thus licensed is called the contributor's
“contributor version”.

A contributor's “essential patent claims” are all patent claims
owned or controlled by the contributor, whether already acquired
or hereafter acquired, that would be infringed by some manner,
permitted by this License, of making, using, or selling its contributor
version, but do not include claims that would be infringed only as
a consequence of further modification of the contributor version.
For purposes of this definition, “control” includes the right to
grant patent sublicenses in a manner consistent with the requirements
of this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify
and propagate the contents of its contributor version.
In the following three paragraphs, a “patent license” is any express
agreement or commitment, however denominated, not to enforce a
patent (such as an express permission to practice a patent or
covenant not to sue for patent infringement). To “grant” such a
patent license to a party means to make such an agreement or
commitment not to enforce a patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through
a publicly available network server or other readily accessible
means, then you must either (1) cause the Corresponding Source to
be so available, or (2) arrange to deprive yourself of the benefit
of the patent license for this particular work, or (3) arrange, in
a manner consistent with the requirements of this License, to extend
the patent license to downstream recipients. “Knowingly relying”
means you have actual knowledge that, but for the patent license,
your conveying the covered work in a country, or your recipient's
use of the covered work in a country, would infringe one or more
identifiable patents in that country that you have reason to believe
are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of,
a covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate,
modify or convey a specific copy of the covered work, then the
patent license you grant is automatically extended to all recipients
of the covered work and works based on it.
A patent license is “discriminatory” if it does not include within
the scope of its coverage, prohibits the exercise of, or is conditioned
on the non-exercise of one or more of the rights that are specifically
granted under this License. You may not convey a covered work if
you are a party to an arrangement with a third party that is in the
business of distributing software, under which you make payment to
the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.

No Surrender of Others' Freedom.  If conditions are imposed on
you (whether by court order, agreement or otherwise) that contradict
the conditions of this License, they do not excuse you from the
conditions of this License. If you cannot convey a covered work so
as to satisfy simultaneously your obligations under this License
and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that
obligate you to collect a royalty for further conveying from those
to whom you convey the Program, the only way you could satisfy both
those terms and this License would be to refrain entirely from
conveying the Program.

Use with the GNU Affero General Public License.  Notwithstanding
any other provision of this License, you have permission to link
or combine any covered work with a work licensed under version 3
of the GNU Affero General Public License into a single combined
work, and to convey the resulting work. The terms of this License
will continue to apply to the part which is the covered work, but
the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to
the combination as such.

Revised Versions of this License.  The Free Software Foundation
may publish revised and/or new versions of the GNU General Public
License from time to time. Such new versions will be similar in
spirit to the present version, but may differ in detail to address
new problems or concerns.

Each version is given a distinguishing version number. If the Program
specifies that a certain numbered version of the GNU General Public
License “or any later version” applies to it, you have the option
of following the terms and conditions either of that numbered version
or of any later version published by the Free Software Foundation.
If the Program does not specify a version number of the GNU General
Public License, you may choose any version ever published by the
Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes
you to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow
a later version.

Disclaimer of Warranty.  THERE IS NO WARRANTY FOR THE PROGRAM,
TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE
STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE
THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Limitation of Liability.  IN NO EVENT UNLESS REQUIRED BY
APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER,
OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS
PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL,
SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE
OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS
OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH
ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Interpretation of Sections 15 and 16.  If the disclaimer of
warranty and limitation of liability provided above cannot be given
local legal effect according to their terms, reviewing courts shall
apply local law that most closely approximates an absolute waiver
of all civil liability in connection with the Program, unless a
warranty or assumption of liability accompanies a copy of the Program
in return for a fee.

END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs If you develop a new
program, and you want it to be of the greatest possible use to the
public, the best way to achieve this is to make it free software
which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the “copyright” line and a pointer to where the full notice is
found.
<one line to give the program's name and a brief idea of what it
does.> Copyright (C)
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published
by the Free Software Foundation, either version 3 of the License,
or (at your option) any later version.
This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program.  If not, see https://www.gnu.org/licenses/.
Also add information on how to contact you by electronic and paper
mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
  Copyright (C)   This program comes
with ABSOLUTELY NO WARRANTY; for details type show w'.  This is free software, and you are welcome to redistribute it under certain conditions; type show c' for details. The hypothetical commands
show w' and show c' should show the appropriate parts of the
General Public License. Of course, your program's commands might
be different; for a GUI interface, you would use an “about box”.
You should also get your employer (if you work as a programmer) or
school, if any, to sign a “copyright disclaimer” for the program,
if necessary. For more information on this, and how to apply and
follow the GNU GPL, see https://www.gnu.org/licenses/.
The GNU General Public License does not permit incorporating your
program into proprietary programs. If your program is a subroutine
library, you may consider it more useful to permit linking proprietary
applications with the library. If this is what you want to do, use
the GNU Lesser General Public License instead of this License. But
first, please read https://www.gnu.org/licenses/why-not-lgpl.html.
Die erwartete CRC32-Prüfsumme ist $2C68A922
/dev/disk2          	Apple_partition_scheme
/dev/disk2s1        	Apple_partition_map
/dev/disk2s2        	Apple_HFS                      	/Volumes/Horos
2022-07-04 23:48:33 : INFO  : horos : Mounted: /Volumes/Horos
2022-07-04 23:48:33 : INFO  : horos : Verifying: /Volumes/Horos/Horos.app
2022-07-04 23:48:33 : DEBUG : horos : App size: 146M	/Volumes/Horos/Horos.app
2022-07-04 23:48:36 : DEBUG : horos : Debugging enabled, App Verification output was:
/Volumes/Horos/Horos.app: accepted
source=Notarized Developer ID
origin=Developer ID Application: Nimble CO LLC (TPT6TVH8UY)
2022-07-04 23:48:36 : INFO  : horos : Team ID matching: TPT6TVH8UY (expected: TPT6TVH8UY )
2022-07-04 23:48:36 : INFO  : horos : Downloaded version of Horos is Horos v4.0.0 RC5 on versionKey CFBundleGetInfoString, same as installed.
2022-07-04 23:48:36 : DEBUG : horos : Unmounting /Volumes/Horos
2022-07-04 23:48:36 : DEBUG : horos : Debugging enabled, Unmounting output was:
"disk2" ejected.
2022-07-04 23:48:36 : DEBUG : horos : DEBUG mode 1, not reopening anything
2022-07-04 23:48:36 : REG   : horos : No new version to install
2022-07-04 23:48:36 : REQ   : horos : ################## End Installomator, exit code 0

Thank you!


Remove Unnecessary JSON.stringify

Axios "automagically" stringfies the post body, there's no need to pre-stringify.
Pre-stringifying can result in unexpected behavior when you're passing in JSON content that includes quotes, such as { name: "My name is \"Mike\"" }

For anyone who lands here from a search engine looking for a fix and doesn't want to install my fork, you can patch this yourself in your own code by doing the following:
(This assumes you're initializing WooCommerceRestAPI and storing it in a variable named api, just like the README example)
api._request = function(method, endpoint, data, params = {}) {
  const url = this._getUrl(endpoint, params);

  const headers = {
    Accept: "application/json"
  };
  // only set "User-Agent" in node environment
  // the checking method is identical to upstream axios
  if (
    typeof process !== "undefined" &&
    Object.prototype.toString.call(process) === "[object process]"
  ) {
    headers["User-Agent"] =
      "WooCommerce REST API - JS Client/" + this.classVersion;
  }

  let options = {
    url: url,
    method: method,
    responseEncoding: this.encoding,
    timeout: this.timeout,
    responseType: "json",
    headers
  };

  if (this.isHttps) {
    if (this.queryStringAuth) {
      options.params = {
        consumer_key: this.consumerKey,
        consumer_secret: this.consumerSecret
      };
    } else {
      options.auth = {
        username: this.consumerKey,
        password: this.consumerSecret
      };
    }

    options.params = { ...options.params, ...params };
  } else {
    options.params = this._getOAuth().authorize({
      url: url,
      method: method
    });
  }

  if (data) {
    options.headers["Content-Type"] = "application/json;charset=utf-8";
    // WHY THE FUCK DID THEY DO THIS?
    // options.data = JSON.stringify(data);
  }

  // Allow set and override Axios options.
  options = { ...options, ...this.axiosConfig };

  return axios(options);
}

After you implement this patch, you use this library as normal but will no longer run into errors because of this.


cve.org CVE-2019-0160 links to edk2-docs.gitbooks.io (Bugzilla Bug 4440)

This issue was created automatically with bugzilla2github
Bugzilla Bug 4440
Date: 2023-05-03T11:14:40+00:00
From: @bexcran
To:   @miki-intel-work
CC:   @lgao4
Last updated: 2023-05-12T13:50:15+00:00

Comment 21564
Date: 2023-05-12 13:50:15 +0000
From: @miki-intel-work
The https://www.cve.org/CVERecord?id=CVE-2019-0160 has been updated with the corrected link.

Comment 21470
Date: 2023-05-03 11:14:40 +0000
From: @bexcran

Industry Specification: ---
Release Observed: EDK II Master
Releases to Fix: EDK II Master
Target OS: ---
Bugzilla Assignee(s): @miki-intel-work

The page at https://www.cve.org/CVERecord?id=CVE-2019-0160 links to edk2-docs.gitbooks.io .

Comment 21533
Date: 2023-05-09 21:53:15 +0000
From: @lgao4
Rebecca: please work on it.

Comment 21548
Date: 2023-05-09 22:36:35 +0000
From: @bexcran
Miki has said she will work on it.


Refactor callback handling

Codecov Report

Merging #33 (043ffb3) into main (234227d) will increase coverage by 1.93%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #33      +/-   ##
==========================================
+ Coverage   90.65%   92.59%   +1.93%
==========================================
  Files           7        7
  Lines         107      108       +1
==========================================
+ Hits           97      100       +3
+ Misses         10        8       -2

Impacted Files
Coverage Δ

src/napari_matplotlib/base.py
100.00% <100.00%> (ø)

src/napari_matplotlib/histogram.py
100.00% <100.00%> (+9.67%)
:arrow_up:

src/napari_matplotlib/scatter.py
64.70% <100.00%> (-16.07%)
:arrow_down:

Continue to review full report at Codecov.

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


Add a Gitter chat badge to README.adoc

RobWin/swagger2markup now has a Chat Room on Gitter
@RobWin has just created a chat room. You can visit it here: https://gitter.im/RobWin/swagger2markup.
This pull-request adds this badge to your README.adoc:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Coverage remained the same at 90.81% when pulling df1dd70af3d901a8ca0c0136be06695036028e71 on gitter-badger:gitter-badge into 04d1773c03769ad82a68ac2baf33c8218f370266 on RobWin:master.


feat(optimizer): support share operator

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?

LogicalShare operator is used to represent reusing of existing operators. It could have multiple parents which makes it different from other operators.
Because most of our optimizations assume that our plan is a tree structure, in order to represent the DAG structured plan, we need to modify our optimizations and prevent them break our DAG plan back to a tree plan accidentally.
Optimization including predicate pushdown, column pruning, heuristic optimizer, stream rewrite and to stream, all of them can break DAG plan back to a tree plan if we don't take care.
Let me take predicate pushdown as an example to illustrate how to implement predicate pushdown for LogicalShare. We use a context for LogicalShare to keep track of how many times predicate has been pushdown for LogicalShare. Once pushdown times equal the parent number of the LogicalShare, we can merge all the previous predicates into one and then push it down for the input of LogicalShare.
Heuristic optimizer's previous rules won't match any LogicalShare, so LogicalShare wouldn't affect its correctness.
At the end of optimizer for batch query, we try to convert DAG back to Tree for now by removing LogicalShare (the rule named DagToTreeRule), because our batch executor doesn't support execute DAG plan directly currently.
This PR also supports reusing source by ShareSourceRewriter. ShareSourceRewriter will replace all the sources occurred more than once in the streaming query with share operator.

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)
https://github.com/risingwavelabs/risingwave/issues/6955
https://github.com/risingwavelabs/risingwave/issues/4618

Hi, I have removed the hint words in the section "What's changed and what's your intention?". Otherwise it would be written into the commit message in main branch e.g. https://github.com/risingwavelabs/risingwave/commit/1af11e28db54c9333368a630522add0e64ff5dca


Inconsistency between access setting that appears on the catalog page and the work page.

On the catalog, a work appears to have Penn State-only access [link]. However the, work actually is public [link]. Looks like the setting was updated without a re-index?

I tried toggling from Penn State back to Open in the work settings page, but the search result is unaffected. It could be that when saving the work from the settings page, Solr isn't getting indexed. Note that changing the visibility setting in the work form will trigger a re-index. I've verified this in QA with a work that's already been published. However, we shouldn't do this in production because it will add a record to the paper trail changes.


update git, hoist powershell setttings to top and get git simpler

- What I did

simplified the Windows Dockerfile a little

- How to verify it
docker build -t test -f dockerfile.windows .
docker run -e DOCKER_GITCOMMIT=foo test hack\make.ps1 -Binary

ping @jhowardmsft

Have you verified this also doesn't break on nanoserver? (I haven't - not in front of a server to test)

@tianon @johnstep FYI

Have you verified this also doesn't break on nanoserver?
Yup, it works well on a nanoserver base image.

@jhowardmsft btw, do you still have to test on the broken nanoserver base image that doesn't have Invoke-WebRequest or can I remove the utility function?

@johnstep excellent catch, updated

lol, tests rely on git-install to pull in tar and other random unix utils

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "update-windows-dockerfiles" git@github.com:friism/docker-1.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842354429240
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

reverted to abusing the nuget package

ping @jhowardmsft @johnstep

LGTM


Example Link not working

seem to be 2 issues here,
first it does not find the vvvv dir, even though i did the full routine incl. admin fallback.
second, it seems not to like the .vpack when using the link copied from your vvvv description page
conceptually it looks really cool, btw!

update:
using any of the vpms:// urls provided work great

it should be always safe to replace https:// to vpms://. yeah it doesn't support plain http url's yet, it's pretty simple to implement so that's coming soon too.
If it wouldn't find vvvv it would tell that it couldn't fetch a vvvv from registry. Maybe that status message will get a friendlier tone.

page with faulty links seems to be gone.
closing this, as it is no longer reproducible ;)


Syntax highlight inline css

Hello.
Can I somehow enable syntax highlighting for inline css styles?

Does setting :set ft=html.css work?

Am 07.09.2020 um 17:31 schrieb Tim<EMAIL_ADDRESS>
Hello.
Can I somehow enable syntax highlighting for inline css styles?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Please ask user questions on the vim_use mailinglist or use vi.stackexchange.com. This here is a bug tracker for problems with Vim. We cannot provide individual help here. Closing.


[BUG] Hallucinated error handling upon significant profile change

Following the pipedrive tutorial everything works ok.
When I simplify the profile and change it to
name = "contacts-management/get-organizations"
version = "0.0.0"

"Retrieve a page of companies with in a CRM, Returns all organizations in the system."
usecase ListCompanies safe  {
  input {
  }
  result {
    companies[
      {
        "Name of the company"
        name! string!
      }
    ]
  }
}

and run the
sf map pipedrive organizations-management/get-organizations

I get map with incorrect error handling (with original profile it was correct):

green is the new, incorrect, handling with the modified profile
red is the previous, correct, handling with the original profile

This incorrect handling is causing the error:
errorResult: { code: 200, message: 'HTTP call failed' }

When I correct the handling to (red version) then it works ok.
Expected Behavior
The error handling in map is correct, as it was in the map generated from the original profile.
Current Behavior
The error handling is not correct and causes false errors.
Steps to Reproduce

follow the pipedrive tutorial
then, replace the profile with the one above

Your Environment

macOS 13.4.1
@superfaceai/cli/4.0.0 darwin-x64 node-v18.13.0

I can confirm it. Even without any profile modification. Condition in the map if (response.status !== 201) { vs response returning 201 when successful.
Prompt: "create organization"


Swift Package Manager Support

Context 🕵♀
Swift PM is a powerful dependency manager for macOS console applications. Projects which use Swift PM usually don't have .xcodeproj versioned in git repositories because it can be easily generated using swift package generate-xcodeproj. This command always creates a new project with structure based on a manifest file.
Since the project is not versioned, all custom project settings has to be made all over again once the project is generated - this includes custom targets, build phases and scheme settings.
I am in the middle of moving all project configurations into Marathon scripts, which allows to manipulate with generated projects using xcproj library. Sadly, projects generated with Swift PM are not supported now.
Library version: 1.0.0
Dependency manager: Swift PM / Marathon
What 🌱
Currently, Xcode projects generated with Swift PM (using swift package generate-xcodeproj) are not supported in XcodeProj class. The initialiser now requires *.xcworkspace to be presented in .xcodeproj file. However, Swift PM creates only .pbxproj, xcshareddata and .plist files. This cause XcodeProj initialiser to fail and throw an error.
This can be easily fixed by opening the .xcodeproj and running xcproj script after that. Even though this fix works, it makes the project hard to maintain. This fix also can not be applied on CI servers since it take a while to start Xcode.
Proposal 🎉

Make workspace  property of XcodeProj class optional.
Another option is to mock the *.xcworkspace if it is possible.

Since this is a breaking change which may not be implemented, we should at least add a note about this issue into project readme.

Hi @josefdolezal. Thanks for opening the issue. I think we should support opening SPM-generated projects in any way. I'll check your two proposals and maybe try to come up with another one so that we can discuss which one is more feasible.

Thanks for s quick reply! Let me know if you come up with another solution, I would love to help fixing this one!

Here you go @josefdolezal https://github.com/xcodeswift/xcproj/pull/124


Pgsecurity

I purposely didn't use {prodname} in some places where this referred to the user instead of debezium. Feel free to comment/critique that.

@davecramer, could you send this PR against the upstream debezium repo instead of my fork? I'm going to close this one here. Thx!

And yes, please use the {prodname} placeholder, it is resolved to "Debezium" in the upstream docs. Thx!


a strange wireframe under unlinked mentions

Is the bug present when using the default Obsidian theme?
No
Is the bug present when snippets and plugins are disabled?
Yes
Minimal theme version
5.3.2
Describe the bug

a strange wireframe under unlinked mentions
Debug info
SYSTEM INFO:
Obsidian version: v0.15.9
Installer version: v0.14.6
Operating system: Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:37 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T6000 21.5.0
Login status: not logged in
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: light
Community theme: Minimal
Snippets enabled: 0
Restricted mode: on
RECOMMENDATIONS:
Custom theme: for cosmetic issues, please first try updating your theme to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.

This is present in default theme


Upgrade org.pitest:pitest-maven 1.7.1 -> 1.7.2

This PR contains the following updates:

Package
Update
Change

org.pitest:pitest-maven (source)
patch
1.7.1 -> 1.7.2

Release Notes

hcoles/pitest
v1.7.2
Compare Source

#943 Change default mutators - replace negate conditional with remove conditional
#946 Mutate stream returns to empty stream instead of null

[ ] If you want to rebase/retry this PR, check this box.

Suggested commit message:
Upgrade pitest-maven-plugin 1.7.1 -> 1.7.2

See:
- https://github.com/hcoles/pitest/releases/tag/1.7.2
- https://github.com/hcoles/pitest/compare/1.7.1...1.7.2


Update Mutagen doc

Update the Mutagen doc and anchor the topic to the table of contents

Preview of the upates - https://deploy-preview-10850--docsdocker.netlify.app/docker-for-mac/mutagen-caching/


Fix builds for Hypothesis 5.0+

Resolves #346 and #346

Codecov Report

Merging #348 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #348   +/-   ##
=======================================
  Coverage   99.93%   99.93%
=======================================
  Files          23       23
  Lines        1645     1645
  Branches      258      258
=======================================
  Hits         1644     1644
  Partials        1        1

Flag
Coverage Δ

#unittests
99.93% <ø> (ø)
: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 e044473...870c77a. Read the comment docs.


JFXButton in JFXDialog

Is this normal behavior for JFXButton in JFXDialog?
When that button isn't in JFXDialog, then it work properly (background shows without disappearing problem).
After clicking the button, then it shows normaly.
https://imgur.com/a/TY40b
Style:
-fx-background-color: linear-gradient(to right, #9c27b0, #6a1b9a);
-fx-background-radius: 15px;

Hello,
We were not able to reproduce the issue, it might be related to the applied css file.
can you double check your css file? it seems you are changing the background on mouse over event.
Regards,

No, i'm not:
CSS
.fontSemiBold {
    -fx-font-family: 'Montserrat SemiBold';
}
.fontSize10 {
    -fx-font-size: 10;
}
.textFillWhite {
    -fx-text-fill: #ffffff;
}
.specialButton {
    -fx-background-color: linear-gradient(to right, #9c27b0, #6a1b9a);
    -fx-background-radius: 15px;
}

Button creation
saveButton = new JFXButton();
saveButton.setText("ZAPISZ");
saveButton.setPrefSize(100.0, 30.0);
saveButton.getStyleClass().addAll("fontSemiBold", "fontSize10", "textFillWhite", "specialButton");

Okay, i figured it out. I've redownloaded JFoenix in Maven and it works now. Strange but true.


Data not send to Synology Server

Hi,
I've got a  working version of the Traccar Synology server, and installed the iOS client on my iphone. My iphone sends fine, but Synology doesn't recieve data.
My settings iPhone
external IP
port 55005 (wich is open)
Unique ID
Service status on
No errors on log
My Synology Settings
external IP:55000
added unique ID
Result, no recent updates.
Please help me out!

In regular version of Traccar port for Traccar Client is 5055, so I'm guessing on Synology you should be using 55055 instead of 55005.

IT's port 55055, maybe good idea to document it on the installation page.

It is documented here:
https://www.traccar.org/devices/
Then for Synology you just need to add 5 at the beginning.
Where did you get 55005 from?

No, it's 55055, the one you shouted earlier 2 replies above. So indeed it's another 5 in front, but it's a good thing to post on https://www.traccar.org/synology/

Updated the page.

Great man! Superb support


Completed Newbie Project

Implemented document file upload, parsing, text extraction, and vector upload to Pinecone with metadata. Also implemented vector retrieval from Pinecone. @trangiabach

Implemented document file upload, parsing, text extraction, and vector upload to Pinecone with metadata. Also implemented vector retrieval from Pinecone. @trangiabach

@ethanwang-04 Overall good job on this PR (and cool stuff) and I left a few comments here and there. I would leave over some more comments as I see more possible fixes!

Implemented document file upload, parsing, text extraction, and vector upload to Pinecone with metadata. Also implemented vector retrieval from Pinecone. @trangiabach

Implemented document file upload, parsing, text extraction, and vector upload to Pinecone with metadata. Also implemented vector retrieval from Pinecone. @trangiabach

Implemented document file upload, parsing, text extraction, and vector upload to Pinecone with metadata. Also implemented vector retrieval from Pinecone. @trangiabach

Implemented document file upload, parsing, text extraction, and vector upload to Pinecone with metadata. Also implemented vector retrieval from Pinecone. @trangiabach

Encouraged writing some tests to make sure vector databases models works correctly, especially with parsing different kinds of documents into chunks


Define what a metric can be.

Right now, graphite and carbon both share the concept of a metric, but they don't have any kind of validation.
I haven't tested it, but given the way the getFilesystemPath() works, I would assume you could craft a metric that would cause problems on the carbon server.  Especially on windows.
I think it'd be beneficial if a metric was fully defined.  Something like:

A metric path contains metric nodes separated by ..
A metric path may not exceed 1024 characters. (Or some limit.  Windows NTFS has a path limit, depending on the filesystem type)
A metric node may only contain characters that match the regexp: /[A-Za-z0-9_-]+/

This should prevent most/all exploits involving getFilesystemPath() in carbon.
It would also fix potential problems in graphite-web() mechanisms as well.

In addition, there probably should be an explanation of how a metric path is normalized:

All duplicate .s are removed; e.g. s/\.\.+/\./g
All leading and trailing . are removed.
For each metric node, all non-permitted characters are removed.
Any characters over the limit are removed.

Potentially related: #181 and #331.

All leading and trailing . are removed.

for leading . it seems to work fine, for trailing, i noticed carbon/whisper creates an extra directory with a file named .wsp inside of it.

additionally, Any filesystem has a constraint on the length of the filename length.

The final code for generating the file path for a metric is in database.py:
def getFilesystemPath(self, metric):
      metric_path = metric.replace('.', sep).lstrip(sep) + '.wsp'
      return join(self.data_dir, metric_path)

We can test it like this:
>>> '.a.b'.replace('.', os.path.sep).lstrip(os.path.sep) + '.wsp'
'a/b.wsp'
>>> '.a.b.'.replace('.', os.path.sep).lstrip(os.path.sep) + '.wsp'
'a/b/.wsp'

As shown in the above, metric like '.a.b' will be alright, however, metric like '.a.b.' will result in a path name like a/b/.wsp which will actually result in a hidden file .wsp. This may not be good.
Maybe we can change it with:
def getFilesystemPath(self, metric):
      # change 'a/b/.wsp' to 'a/b.wsp'
      metric_path = metric.replace('.', sep).lstrip(sep).rstrip(sep) + '.wsp'
      return join(self.data_dir, metric_path)


HandLandamarkerResult Typo - Hand landmarks detection guide for Python - Navigate -> Create the Task section > Live stream tab

Description of issue (what needs changing)
https://developers.google.com/mediapipe/solutions/vision/hand_landmarker/python#create_the_task
Clear description
Navigate to the Create the task and click the Live stream tab.  There is a typo, HandLandamarkerResult should be HandLandmarkerResult.  Error: "HandLandamarkerResult" is not definedPylancereportUndefinedVariable
Correct links
https://developers.google.com/mediapipe/solutions/vision/hand_landmarker/python#create_the_task. All I can find is the old content in mediapipe/docs/solutions /hands.md.
Parameters defined
No response
Returns defined
No response
Raises listed and defined
No response
Usage example
No response
Request visuals, if applicable
No response
Submit a pull request?
I would if I can find the current hands.md to take a look at the typo.

@OrangeDev2,
Thank you for reporting out this documentation bug. We have raised internal CL and based on approval changes will reflect into the page.

@OrangeDev2,
Closing this issue as CL has been merged and reflected change can be see here in the documentation. Thank you


Extension stops working with Uncrustify 0.74

I just upgraded Uncrustify.exe from 0.73f to 0.74 and extension stopped working.
When I run "format document" - nothing happen.
Replacing .exe back to 073f restore functionality.
I don't see any errors in VSCode window or logs.
Windows 10 x64, Uncrustify x64, VSCode 1.62.3

False alarm. I have turned on debug logs in extension config and got this:
Debug: uncrustify exited with error: d:\git\FOSS-SF-development\config\uncrustify.cfg: line 2: Character at position 19, is not printable.
There was a comment in cfg file with a Polish character in my name Paweł<-- and that was an issue.
Apparently the previous version has not checked that.

Glad you were able to get it figured out!


jsonschema validator considerd support:validator

Problem statement
Now jsonschema (Draft 4) validator, with full $ref support: validate.
But gin support validator , i want use one validator with both gin and swagger,so i wonder why dont support validator? or does there has any better methods.
For now, i do like this:

go-openapi/validate and validator are different. go-openapi/validate does not use reflection and validation logic are generated together with each struct.
Maybe one can write a validator compatible wrapper of go-openapi/validate, and call the generated Validate() function on each struct.


Add _.comparator and align sortedIndex to sortBy

Resolves #1768 and fixes #1834
This could use some review and thoughts

Anyway I'm a big fan of exposing comparator as it allows devs easy
customization for oddball data structures and frankly I've needed a solid
comparator in my own code in the past

Can you expand on this? Wouldn't you just return a different value or use #sort directly in those cases?

To repeat -- let's please back this out for the time being. (I don't want to forget about it.)

@braddunbar lets say you want to to do add support to something similar to pythons class __cmp__
_.mixin({
   comparator: _.wrap(_.compatator, function(baseCompare, a, b) {
     if (_.isFunction(b.__cmp__)) return b.__cmp__(a);
     if (_.isFunction(a.__cmp__) return a.__cmp__(b);
     return baseCompare(a, b);
  })
});


gen_mini_batches  produce iou_2d/kitti/train/lidar/Car[0.5]/ *.npy

*.npy      why we need these data ? what is  *.npy used for ?
Can someone give me some advices?  Thank you very much!

please reply some one....i also have the same query

.npy files are anchors...Read the working of Faster RCNN to understand anchors. @QZ1219


Review comments are missing in description view on GH Enterprise

@queerviolet that's right, I was about to push a new commit to fix that but since we have #910 we can close it now.


Possible PPA? Allow apt-get install

It would be simpler if we could install the tool using apt-get

I tried making a package for apt, but failed miserably due to complications involved.
However, in v3, the tool will accessible in your path without having cd to the directory.
A script would place it on your PATH and even install/update via curl. This is similar to how oh-my-zsh does.


Changes to GoogleVisionBarCodeScanner not picked up because SampleApp references NuGet instead of project

Hello - I'd very much like to add some features for your consideration. However, the SampleApp references the NuGet package, rather than the GoogleVisionBarCodeScanner project.
I don't have much experience in this area. How can I either create a NuGet package from the code in my version of the GoogleVisionBarCodeScanner project, or have the SampleApp refer to the project in the solution? I tried to remove the package reference, but ended up missing more things than I expected.
Any help is appreciated, thanks!

Removing package reference and add the project reference in sample app should work.
Or you can create the package first, add local nuget path. But it will not able to debug.

Thanks - I have resolved my issue. I think part of it was a Visual Studio hiccup. Off to the races! :)
So far, I have a quick shot at returning the CornerPoints data in BarcodeResult, which should allow for both custom on-screen feedback, and a quick and dirty hack for 'aimed' scanning (by checking if the points fall within a known rectangle/region.
I appreciate the help!

@MisterAcoustic
It's good to hear that. Could you share your code or create a pull request for this function?

@JimmyPun610
Hello - I believe I will be able to provide the code that we end up with, but I'm not sure it will be in the form of a pull request. I can show you what we've done and let you decide if it's worthwhile to add that way. The mapping of the points from the camera to the screen in Xamarin Forms was a little more challenging than expected. Android is working completely now, but iOS needs a different type of transformation, and I'm still looking into that. The changes to the library are not that extensive - we are doing the mapping in our application, so I'll have to get that into the sample app somewhere for you to see that part. I hope to nail down iOS next week. After that, I will get in touch and let you see what we've done.

@JimmyPun610
Hello - I believe I will be able to provide the code that we end up with, but I'm not sure it will be in the form of a pull request. I can show you what we've done and let you decide if it's worthwhile to add that way. The mapping of the points from the camera to the screen in Xamarin Forms was a little more challenging than expected. Android is working completely now, but iOS needs a different type of transformation, and I'm still looking into that. The changes to the library are not that extensive - we are doing the mapping in our application, so I'll have to get that into the sample app somewhere for you to see that part. I hope to nail down iOS next week. After that, I will get in touch and let you see what we've done.

Sure. Take your time


#291 Fix EU REACH, and some other miscellaneous documentation improvements

Closes #291
After the move to use the latest version of the Restricted Substances database for CI, we now see the effects of changing from 'REACH' to 'EU REACH':
https://bomanalytics.grantami.docs.pyansys.com/version/dev/examples/0_Getting_started.html#View-query-results
The REACH legislation 'Short title' was changed from 'REACH - The Candidate List' to 'EU REACH - The Candidate List' to disambiguate from UK REACH, China REACH, Korea REACH, etc. As a result, the examples now return zero results.
This PR replaces 'REACH' with 'EU REACH' everywhere, which should reinstate the results. Check the built docs in the pre-merge checks to confirm.
I have also made a few other miscellaneous documentation changes while I was in the code:

Fixed a missing space in a connection error string
Replaced 'localhost' with 'my_server_name', to be consistent with jupyter notebook examples
Added clarification as to what should be used for the legislation_name parameter. Note that we might change this to use the legislation id instead. At this point we could change the parameter name, causing people to adjust their scripts to avoid a silent failure.

Codecov Report

Merging #343 (001f66d) into main (79e6e55) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #343   +/-   ##
=======================================
  Coverage   95.25%   95.25%
=======================================
  Files          10       10
  Lines        1390     1390
=======================================
  Hits         1324     1324
  Misses         66       66

Files Changed
Coverage Δ

src/ansys/grantami/bomanalytics/_connection.py
88.63% <ø> (ø)

src/ansys/grantami/bomanalytics/_query_results.py
97.36% <ø> (ø)

src/ansys/grantami/bomanalytics/indicators.py
93.10% <ø> (ø)

src/ansys/grantami/bomanalytics/queries.py
98.20% <ø> (ø)

The built examples contain a populated list of impacted substances:


Keep show/hide columns state after page loading

I used toggle show/hide columns function, however, column state is initialized after loading.
How to config to keep current columns state after loading the page ?

i am interest in the same question. Any suggestions?

Have a look at persistance topic in guide.


App.DeliverTx()

All call-stack and app.blockContext are changed to process each transaction separately.
It is necessary to match Tendermint ABCI.
Also gossip.EpochStats is moved to the app side.

Codecov Report

Merging #456 into develop will decrease coverage by 0.28%.
The diff coverage is 4.68%.

@@             Coverage Diff             @@
##           develop     #456      +/-   ##
===========================================
- Coverage    43.79%   43.50%   -0.29%
===========================================
  Files          171      169       -2
  Lines        11874    11897      +23
===========================================
- Hits          5200     5176      -24
- Misses        6250     6295      +45
- Partials       424      426       +2

Impacted Files
Coverage Δ

app/app.go
0.00% <0.00%> (ø)

app/apply_genesis.go
0.00% <0.00%> (ø)

app/block_info.go
0.00% <0.00%> (ø)

app/ethapi_backend.go
0.00% <0.00%> (ø)

app/provided_store.go
0.00% <0.00%> (ø)

app/sfc_index.go
0.00% <0.00%> (ø)

app/store_epoch_stats.go
0.00% <0.00%> (ø)

app/store_migration.go
0.00% <0.00%> (ø)

evmcore/state_processor.go
0.00% <0.00%> (ø)

gossip/apply_genesis.go
60.46% <ø> (-6.85%)
:arrow_down:

... and 12 more

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 58c4af6...45a79f1. Read the comment docs.


brick party (several fix)

"brick" is not "brick"

night battle nowhps = update current HP at the start of night battle

morale deduction by 3 if initiated, and 1 if node basis

give a warning/explanatory while waiting the panel to be loaded
didFyee()

didFyee
some generalization applied to Fleet.js

(spent all-night together with @ethrundr lately)

it was tiring seeing him trimming the codes......

it's called compressing


Value error

I get a value error, tried to uninstall and install several packages but nothing worked :(
I prepared the sets as they are supposed to be. Including the 'left' and right prefixes, id, label and so on

train, validation, test = dm.data.process(
    path='/home/censored/quora-question-pairs',
    train='train.csv',
    validation='validation.csv',
    test='test.csv')

including the Error
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-14-989ecb797b84> in <module>()
      4     train='train.csv',
      5     validation='validation.csv',
----> 6     test='test.csv')

/home/censored/.local/lib/python3.6/site-packages/deepmatcher/data/process.py in process(path, train, validation, test, unlabeled, cache, check_cached_data, auto_rebuild_cache, tokenize, lowercase, embeddings, embeddings_cache_path, ignore_columns, include_lengths, id_attr, label_attr, left_prefix, right_prefix, use_magellan_convention, pca)
    195
    196     _maybe_download_nltk_data()
--> 197     _check_header(header, id_attr, left_prefix, right_prefix, label_attr, ignore_columns)
    198     fields = _make_fields(header, id_attr, label_attr, ignore_columns, lowercase,
    199                           tokenize, include_lengths)

/home/censored/.local/lib/python3.6/site-packages/deepmatcher/data/process.py in _check_header(header, id_attr, left_prefix, right_prefix, label_attr, ignore_columns)
     32         if attr not in (id_attr, label_attr) and attr not in ignore_columns:
     33             if not attr.startswith(left_prefix) and not attr.startswith(right_prefix):
---> 34                 raise ValueError('Attribute ' + attr + ' is not a left or a right table '
     35                                  'column, not a label or id and is not ignored. Not sure '
     36                                  'what it is...')

ValueError: Attribute  is not a left or a right table column, not a label or id and is not ignored. Not sure what it is...

How can I avoid this?

You have something in your dataset header. It's not specified, not that i'm aware of, but the data must be comma separated.
Maybe i'll work something out so one can specify which separator deepmatcher has to use

Hi, I've encountered same problem. You may have empty column name in your csv. For me, the case was to explicitly disable index in saving DataFrame to csv:
 data.to_csv(name, index=False)

Hi, I've encountered same problem. You may have empty column name in your csv. For me, the case was to explicitly disable index in saving DataFrame to csv:
 data.to_csv(name, index=False)


New reconstruction chain in the webApp

In this PR, I have added the possibility to run the new reconstruction chain from the 3D display app, allowing users to view its outputs on the screen. Users now have the option to display cluster seeds from the new reconstruction chain, which includes the new coarse seeding and the new seeding algorithm, or from the default chain by simply interacting with a switch.
The scripts required to run the new reconstruction chain were already present in the Python framework. When calling for new events from the app, both chains are executed, so that the final user can compare the two chains applied to the same event. The new_radii_chain function has been updated accordingly. The dataframes are then processed and stored in the usual hdf5 files, where a new key has been added. This key allows for distinguishing between the new chain and the default chain and can assume the values of 'new' or 'default'.
Here's an example of a photon (200 pileup) processed by both chains. The difference in performance is truly impressive.

Great! General comments:

the key "new" for the new chain is not ideal, because as soon as we add a third chain (or a small variation of one of the current two chains) it will have to be changed
following the same reasoning, it is likely better to use a widget with more than two options

I've added a dropdown menu instead of a switch so that we can easily add multiple chains in the code. Now the new chain is called coarse seeding chain.

Additional minor comments:

Could you please replace "t" by "T" when showing the transverse momentum?
Why are eta and phi within parenthesis and not pT? Can you uniformise?
I think you could add the "Select a particular clustering radius: " slider to the right of "Select manually an event:", so to gain vertical space.

Additional minor comments:

Could you please replace "t" by "T" when showing the transverse momentum?
Same for "Threshold in [mipₜ]", where you can also remove the "[" and "]"
Why are eta and phi within parenthesis and not pT? Can you uniformise?
I think you could add the "Select a particular clustering radius: " slider to the right of "Select manually an event:", so to gain vertical space.
Replace "Pages" by "View", or similar, since it is IMO clear

Once this is addressed I am ready to approve. What about @isehle?

Implementations done! Now the page layout is a bit better!


Better error handling and print warning when Image format not registered

For example for a ppm image, a call like this is needed before Decode is called:
image.RegisterFormat("ppm", "ppm", ppm.Decode, ppm.DecodeConfig)

Failing to do so, will silently hide the problem resulting in a strange error on the provider side:
illegal base64 data at input byte 9

Just linting errors about missing docs on exported methods. Nothing introduced in this PR. Will merge and we will fix those in another PR.


Support /ok-to-test and /retest

/enhancement

/assign

/help-wanted
/good-first-issue

Blocking by cli/cli#6056

/retire Support /retest

/retitle Support /retest

/retitle Support /retest

/retire Support /retest

/retitle Support /retest


Refactor program.cs code into multiple files

Program.cs is getting a bit busy. The API endpoints should probably be implemented as a Controller. Also, configuration logic should be moved to a Startup file.
Ideally, Program.cs should only contain setup code.

No need to do now, more consistent with minimal API pattern to keep it in Program.cs


Create pipeline for training spacy2 NER

Currently evaluating different algorithms for NER based tasks including crf, rnn+ctf, and spaCy 2.0 cnn NER. It was pretty straight forward to convert rasa training data into BILOU tags for spacy CLI training.
Any thoughts on implementing (along with PhraseMatcher) and a few other spacy2 goodness into rasa? Has the performance of crfsuite been benchmarked against spacy2 for NER related tasks?
As spaCy 2 also has multi objective classification abilities that share cnn tensors this may also bridge the current lack of shared features and objectives across intent classification and ner pipelines

Very good ideas and a lot of valuable input. There is an open PR for the spacy NER feature as well as a phrase matcher PR (not using spacy matching though).
The combined features do sound interesting, /cc @amn41

Hi Alan, long time no talk.
Other thoughts are more transfer learning oriented feature share (share bi-lstm) states as features from one optimization to another, but isn't exactly a one sized fits all solution and results are mostly dramatically under or overfitting without domain expertise and rich datasets. A former colleges favorite was to use every lstm state output and after training (for say an ner task) , stack GBDT as the activation function for multiclass objective (intent)  on the states. Fun stuff

closing this for now- may revisit this topic again in the future

@r-wheeler do you have your code training a custom spacy ner based on rasa data?


Update asset_pipeline.md

исправление опечатки

I've prepared a stage to preview changes. Open stage or view logs.


Large amount of repeated code

In gmx.py there is a very large amount of repeated code.
For example, the code
# clean up
    odir = _misc.dirpath(_misc.realpath(o))
    clean_up("./", verbose=False)
    clean_up(odir, verbose=False)

    # save message
    o_file = _misc.realpath(o)
    _misc.cprint(f"Saved file as: {o_file}", cfg.cprint_color)

    if log:
        logdir = _misc.mkdir(f"{odir}/logs")
        logfile = f"{logdir}/grompp.log"
        if not log_overwrite:
            log_names = [f"{logdir}/grompp_{i}.log" for i in range(1, 1000)]
            for name in log_names:
                if name in glob.glob(f"{logdir}/*.log"):
                    continue  # skip existing log_name
                else:
                    logfile = name
                    break  # stop at first new log_name
        with open(logfile, "w") as fout:
            _misc.cprint(f"Saved log as: {logfile}", cfg.cprint_color)
            fout.write(f"STDERR:\n\n{stderr}\n")
            fout.write(f"STDOUT:\n\n{stdout}\n")
            clean_up(logdir, verbose=False)
    return o_file

or some very slight modification is repeated several times. This always occurs after a Gromacs function is called. Before the gromacs functions are called, output file names etc are set. This occurs in every function which wraps Gromacs functions.
Some of this (such as cleaning the directory) could be moved into your context manager misc.HiddenPrints(verbose=verbose), though I imagine then it would be appropriate to change the name. Alternatively I would suggest writing a decorator for these Gromacs functions.

Additionally, there are two functions which seem to be exactly the same, editconf and convert_TPR2PDB: https://github.com/KIT-MBS/pyrexMD/blob/78bcec7104c1c591ee4671457c08bb4d690e02ee/pyrexMD/gmx.py#L258
One of these should be eliminated, or they should be aliased, ie
convert_TPR2PDB = editconf

To ensure that they are always the same if they are meant to be the same function.

i adressed this issue with call of help functions now. thanks


Where contains with reference broken in v2

Link to reproduction
No response
Describe the Bug
This query worked in v1, but does not in v2: ?depth=0&where[children][contains]=64d5ef3b02daa9eb18051754&page=1&limit=1
children is a one to many relation to the same content type (self referencing)
TypeError: Cannot read properties of undefined (reading 'read')
    at /app/node_modules/payload/src/database/queryValidation/validateSearchParams.ts:140:37
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Promise.all (index 0)
    at async validateSearchParam (/app/node_modules/payload/src/database/queryValidation/validateSearchParams.ts:178:3)
    at async Promise.all (index 0)
    at async validateQueryPaths (/app/node_modules/payload/src/database/queryValidation/validateQueryPaths.ts:85:5)
    at async find (/app/node_modules/payload/src/collections/operations/find.ts:136:7)
    at async findHandler (/app/node_modules/payload/src/collections/requestHandlers/find.ts:30:20)

To Reproduce
Try todo a where contains on a field which is a one2many relation pointing on it self
{
  slug: 'pages',
  fields: [
    {
      name: 'children',
      type: 'relationship',
      relationTo: 'pages',
      hasMany: true,
    }
  ]
}

Payload Version
2.0.13
Adapters and Plugins
mongodb

I think the correct operator to use here would be in. I have been trying to diagnose what changed with contains though too.

Yeah you should use in instead of contains, I am going to close this issue out. Thanks!

@JarrodMFlesch thank you

@JarrodMFlesch i still the the same error
?depth=0&where[children][in]=64d5ef3b02daa9eb18051754&page=1&limit=1
TypeError: Cannot read properties of undefined (reading 'read')
    at /app/node_modules/payload/src/database/queryValidation/validateSearchParams.ts:140:37
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Promise.all (index 0)
    at async validateSearchParam (/app/node_modules/payload/src/database/queryValidation/validateSearchParams.ts:178:3)
    at async Promise.all (index 0)
    at async validateQueryPaths (/app/node_modules/payload/src/database/queryValidation/validateQueryPaths.ts:85:5)
    at async find (/app/node_modules/payload/src/collections/operations/find.ts:137:7)
    at async findHandler (/app/node_modules/payload/src/collections/requestHandlers/find.ts:30:20)

@dominikzogg Ah yes, sorry for closing too soon. The fix is in this PR.


Add MOTD

with some useful insights:

[x] Add pacman-contrib to boot.sh
[x] Add pacman-contrib to 1.6.sh
[ ] Add motd to assets
[ ] link motd to /etc/motd
[ ] link motd to /etc/motd in 1.6.sh
[ ] Show how many packages are ready to be updated in /etc/motd

fixed


Add YAML support for Zappa Settings

I'm getting feature anxiety about this.

Bam. https://github.com/Miserlou/Zappa#yaml-settings


Demo beautification

[x] Ensure text for tabs and ILs fits in boxes (better fonts? better sizes? better centering?)
[x] Ensure consistent fonts throughout the demo (e.g., text boxes vs tabs)
[x] Better colors?
[x] Add logo?

Hi Avi, I assign this to you for now in case you have some time (and as I know you're doing some refactoring it might be something easy to squeeze in). None of it is fundamental or required, but just some thoughts/suggestions.

Just noting:
I did step one in our planned overall reorganization of the demo.   The compile and execute tabs are now html based rather than canvas based (since they include input areas).   Results are displayed in a readonly textarea rather than using a fabric Text object.   As a consequence, lines wrap and there are only vertical scroll bars.
This doesn't necessarily completely address the first work item but I think it makes the text a little more readable and it might be good for @jeromesimeon to have a look to see what's most in need of further improvement before @shinnar plunges in.

This has been mostly done. Additional improvements for the demo can be raised as additional issues.


ngSanitize syntax error in Chrome/IE11

[Message] Uncaught SyntaxError: Invalid regular expression: missing /
[File] angular-sanitize.js, Line: 619, Column: 98
[Version] 1.3.15
This error is not observed in 1.2.x.

Can you please provide a runnable code example that shows this error? (plnkr.co etc.) This is not enough information to act on this issue.

Interestingly, this error is only observable with the unminified angular-sanitize.js. When using angular-sanitize.min.js it is OK.
<!DOCTYPE html>
<html>
<head>
	<title>Angular Bug</title>
</head>
<body>

	<script type="text/javascript" src="angular.js"></script>
	<script type="text/javascript" src="angular-sanitize.js"></script>
</body>
</html>

Open this html in Chrome, you can find error in the console.

I can't reproduce: http://plnkr.co/edit/PaSOmNTTeXG8yq8aZfl3?p=preview
Maybe your file got messed up during the download process? Edited by accident? Or maybe you've got a particular Chrome extension installed?
In any case I can't reproduce it with a simple plunker.

In the uncompressed file, there is a regex:
/((ftp|https?):\/\/|(www\.)|(mailto:)?[A-Za-z0-9._%+-]+@)\S*[^\s.;,(){}<>"”’]/

But in the min.js file, this regex is:
/((ftp|https?):\/\/|(www\.)|(mailto:)?[A-Za-z0-9._%+-]+@)\S*[^\s.;,(){}<>"\u201d\u2019]/

I guess there must be something wrong.

@luanshixia yes, minification process seems to change some quote literals to their \u equivalents. Bot both regexps are still valid (at least syntactically).

I guess there must be something wrong.

Might be, but we still need a reproduce scenario. I've linked a simple plunker that represents what you've been describing (or at least my understanding of it!) and doesn't throw any errors?
Could you please modify this plunk to expose the error?

@pkozlowski-opensource just save the plunker sample to local hard drive and run. You will see that the filter does not work. At least on my machine.

@luanshixia it still works if saved to a local file (I really don't see a reason to behave differently while saved to a local file). Does the plunker I've linked works for you?

At least on my machine.

This is why I was suggesting issues linked to your local env:

Maybe your file got messed up during the download process? Edited by accident? Or maybe you've got a particular Chrome extension installed?

@pkozlowski-opensource the online sample works fine. Maybe it does have something to do with my environment, specifically the locale of Chrome. When opening/requesting the file in my Chrome (Simplified Chinese), I see messed up code in that regex.
If this is true, is it possible to escape the quote marks in the source, just like the minified js?

@luanshixia I don't think it is linked to the locale of Chrome since it would also affect Plunker version. What I think is happening that a file you've got on the local drive got corrupted somehow.
You can surely send a pull request changing quotes to their respective \u equivalents but I really do think that the issue boils down to the changes in your local file.

@pkozlowski-opensource But file is corrupted cannot explain why the messed-up code only seen in my Chrome but not my other text editors.
What I know is I have experience similar situations in TFS, also related to the wide char of quote literals. Every time a check-in file contains these chars, the code will be messed up. All my colleagues confront this. We must replace the wide quote to plain quote to resolve the issue.
Maybe it is an issue of Chrome or Windows, but it can be avoided. Since the wide quote is added in 1.3.x, I think just escaping is OK.

Looks like this landed as https://github.com/angular/angular.js/commit/39ff3332a31b2db09e615ecea07634708cb46d7b