(cherry picked from commit 226fb24)

Set up bindings and shift phases as needed to make
`variable-reference->namespace` work in a run-time position when the
enclosing module is instantiated at a phase other than 0.

Thanks to Rohin Shah for the bug report.

(cherry picked from commit 3f2de91)

(cherry picked from commit ecaa145)

Thanks to Leif for the report and test case.

(cherry picked from commit 80e8e0f)

(cherry picked from commit 8190a77)

Repairs a problem with 8190a77, which can incorerctly
move an erroring experssion into tail position.

(cherry picked from commit d1ba9fb)

Continuing the saga that includes 8190a77 and d1ba9fb, it turns
out that a 0-binding clause as the last one isn't so special after
all. A little later in the optimizer, now that we're sometimes moving
an error to the body, we can't assume that the body can be discard
if an error was detected.

(cherry picked from commit 736cdfb)

Thanks to Robby for the test.

(cherry picked from commit aead07b)

the public function was missing the `#:generate` keyword,
 added this and documented why `#:exercise` is missing

(cherry picked from commit 3bb131e)

Remove the history annotation on `build-flat-contract` property
 about removing the `#:exercise` keyword.

Because the keyword wasn't actually removed from the function,
 only from the (incorrect) documentation. So there aren't any
 legal programs that depend on the removed keyword argument.

(cherry picked from commit 50f67cf)

Store relative paths in "info-cache.rktd" (which corresponds,
roughly, to packages) in a platform-independent form, instead
of using the current platform's convention.

Using the current platform's covention works badly when
cross-compiling for Windows on Unix, since relative paths are used as
keys in the "info-cache.rktd" table. For example, updating a
pre-installed package on Windows mangles the mapping if the installer
is created from a cross-compiled installation.

(cherry picked from commit 459a744)

Fix for 459a744 to handle the case that a path
to record is not relative. The `raco pkg` tests
exposed the problem.

(cherry picked from commit 016b800)

Repairs a problem with 409321c.

Merge to v6.9

(cherry picked from commit 662fd84)

(cherry picked from commit 1e29362)

…de to reflect that

closes racket#1661

(cherry picked from commit e7f6847)

closes racket/db#8

merge to release branch

(cherry picked from commit 995f320)

The repair in 71a43f3 fixed the creation of some launchers, but it
broke GUI launchers with a relative reference on Mac OS.

(cherry picked from commit 803d8ff)

(cherry picked from commit fae55e8)

(cherry picked from commit 54bd21e)

When comparing a part of a hamt that is a collision node versus a
subtree node, a "hash code" was extracted from the collision node ---
but that's really a code for an integer key is that used for the
collision element. The comparison should instead use a code extracted
from the reference to the collision node (which is the code that is
common to all colliding keys).

(cherry picked from commit 6de3659)

(cherry picked from commit 5f740ff)

Closes racket#1725

(cherry picked from commit 0f5e95e)

(cherry picked from commit 1a81f20)

- missing `for-label` in `file/gif`
- typo in `file/unzip`

(cherry picked from commit 5c382d7)

Merge to release branch.

(cherry picked from commit 83540d1)

Merge to v6.10

(cherry picked from commit 1d74c21)

A mistake in the rktio conversion causes a crash if certain functions,
such as `directory-exists?`, are used before certain other functions,
such as `resolve-path`.

Thanks to Alex Harsanyi for the report.

(cherry picked from commit 046503d)

The rktio conversion lost the deregistration of file descriptors in an
internal fd-to-semaphore table building on kqueue/epoll, causing the
wrong semaphore to be checked for a later recycling of the file
descriptor. This bug mainly affects Linux and ports created by
`subprocess`, since kqueue is not used for pipes on Mac OS and BSD
variants. The bug does not affect network sockets (which are the
primary intended clients of epoll/kqueue support), since the relevant
semaphore is deregistered when a socket is closed.

Thanks to James Bornholt for discovering the problem and providing the
repair.

Closes racket#1769

(cherry picked from commit 1a9dee5)

In the rktio conversion, the peer-address results were incorrectly
wired to the local-address function.

(cherry picked from commit 93ea42d)

Avoids errors that sometimes appear as "cannot redefine lifted.0".

Merge to 6.11.

(cherry picked from commit 78fdee6)

Fixes a problem with 78fdee6

(cherry picked from commit b6b9d0d)

If a #\return lined up in just the wrong way with a file-read
request, then the #\return could get mishandled.

(cherry picked from commit e255c73)

(cherry picked from commit e03ec08)

In Windows 10 Fall Creators Update, a OneDrive mount looks to Racket like
a reparse point that refers to itself. Make Racket stop trying to resolve
the path further in that case.

Relevant to racket#1671

(cherry picked from commit 22e8af3)

(cherry picked from commit 06bdd2f)

(cherry picked from commit a35633e)

(cherry picked from commit f11b431)

(cherry picked from commit 0d870fb)

struct-out was putting the super-struct's accessors into two parts of a
struct-info: the accessor list and the mutator list

this commit puts the accessors only in the accessor list and the
mutators in the mutator list

(cherry picked from commit cf0c06d)

This repair was motivated by tests in the "rex" package. The
new test added here failed before by finding 'new both times,
but in the "rex" case, the mixup led to the same variable
being imported and exported at the linklet level.

(cherry picked from commit 380dc42)

Bind variables in a way that allows `local-expand` (with an empty stop
list) to replace a reference to the binding with one that has the same
scopes as the binding.

(cherry picked from commit c7318ca)

Closes racket#2119

(cherry picked from commit 09cdbc4)

* When you delete a file in Windows, then the name doesn't go away
  until the file is closed in all processes (and background tasks like
  search indexing may open files behind your back). Worse, attempting
  to create a new file with the same name reports a permission error,
  not a file-exists error; there's seems to be no way to tell whether
  a permission error was really a file-exists error.

  This creates trouble for `make-temporary-file` when files are
  created, deleted, and created again quickly enough and when
  something like a search indexer runs in the background (which is the
  usual Windows configuration). In practice, that kind of collision
  happens often for `raco setup` on my machine.

  To compensate, make `make-temporary-file` try up to 32 times on a
  permission error. A collision that many times seems extremely
  unlikely, and it seems ok to delay an actual permission error.

  Windows provides a GetTempFileName function from "kernel.dll" that
  must be able to deal with this somehow --- perhaps because it's in
  the kernel --- but it doesn't solve the problem for making temporary
  directories, hence the 32-tries approach for now.

* When a deleted file's name persists because the file is open in some
  process, then a directory containing the file cannot be deleted.

  This creates trouble for `delete-directory/files`, since
  `delete-file` on a directory's content doesn't necessarily make the
  directory empty. In practice, this happens often for package
  upgrades on my machine, where the package system wants to delete a
  short-lived working space that the indexer is trying to scan.

  To compenstate, change `delete-directory/files` to delete a file by
  first moving it to the temporary directory with a fresh name, and
  then delete the file there. It may take a while for a file to
  disappear from the temporary directory, but meanwhile it's not in
  the way of the original enclosing directory.

* When a file is open by any process, it prevents renaming any
  ancestor directory of the file.

  This creates trouble for the package system, which installs a
  package by unpacking it in a temporary place and then moving it by
  renaming. The package system also removes a package by renaming it
  to a subdirectory of a ".trash" directory. If a background indexer
  has a package file open, the move fails. In practice, a move fails
  often on my machine when I'm attempting to upgrade many packages.

  To compensate, make the package system fall back to copy + delete
  if moving fails with a permission error.

(cherry picked from commit daa7dde)

(cherry picked from commit 331c39c)

Include the MemoryModulee copyright alongside the ones for other libraries
that are compiled into the Racket executable.

(cherry picked from commit 88e5daf)

Doc corrections related to functions that have new optional arguments
in v7.0.

Closes racket#2134

(cherry picked from commit 047157d)

(cherry picked from commit 3c752e0)

When an embedding application calls `scheme_basic_env` a
second time, it's supposed to reset the main namespace, but
the new expander wasn't reset correctly.

(cherry picked from commit 96161f6)

When the first subexpression is complex and the second
is a literal character, the generated JIT code swaps the
argument order, but compilation didn't swap the test for
whether one or the other is a literal character to skip
a run-time test.

(cherry picked from commit 598a5ba)

To avoid recording absolute paths from a build environment in bytecode
files, the bytecode writer converts paths to relative form based on
`current-write-relative-directory`. For paths that cannot be made
relative in that way and that are in source locations in syntax
objects, the printer in v6.x converted those paths to strings that
drop most of the path.

The v7 expander serializes syntax objects as part of `compile` instead
of `write`, so it can't truncate paths in the traditional way. To help
out the expander, the core `write` function for compiled code now
allows `srcloc` values --- as long as the source field is a path,
string, byte string, symbol, or #f. (Constraining the source field
avoids various problems, including problems that could be created by
cyclic values.) As the core `write` for compiled code prints a path,
it truncates a source path in the traditional way.

The expander doesn't constrain source locations in syntax objects to
have path, string, etc., source values. It can serialize syntax
objects with non-path source values at `compile` time, so there's no
loss of functionality.

The end result is to fix abolute paths that were getting stored in the
bytecode for compiled packages, since that's no good for installing
packages in built form (which happens, for example, during a
distribution build).

(cherry picked from commit c6049f8)

Handle "." and ".." as one of the last two elements of a path.

(cherry picked from commit fc7c4bb)

The bug was related to re-expansion of submodules that are implemented
as `(module* _name #f ....)`. The bug affects `module->namespace`,
which relies on knowing the set of scopes that correspond to the
submodule's body. the bug probably affects some other things that
similarly rely on a module's body scopes.

When you expand a module

 (module _name _initial-import
    ....)

then the set of scopes associated with `_initial-import` count as the
module's body scopes, except that two more are added for the "inner
edge" and "outer edge". Those two are added back to `_initial-import`
in the expanded form of the module. If you expand again, that means the
re-expansion starts with those two scopes added by the previous
expansion; since those to scopes are "everywhere" in the module body
from the previous expansion, so far, so good.

When you expand the submodule in

 (module ....
    (module* sub #f
       ...)
    ....)

then the submodule's scopes should start as the scopes on the `#f`,
which will normally be the scopes for the enclosing module's body. At
some point fairly early in the implementation of the new macro
expander, I decided to ignore the `#f` and just propagate the scopes
from the enclosing module's body as the starting point for the
submodule.

Besides being inconsistent with the v6.x expander, that choice means
that when fresh "inner edge" and "outer edge" scopes are allocated for
the submodule expansion, they're not usefully preserved for
re-expansion when they're added to the `#f`. (In fact, the
implementation didn't bother adding them to `#f` in the expansion.) So,
those scopes get lost, and re-expansion has the wrong idea for the
submodule's body scopes.

Why didn't this cause more problems? Because you don't normally need
the concept of a module's body scopes. Forms within the module body
have various scopes, and normally all that matters is how those forms
relate to each other. But it matters for `module->namespace`, because
forms evaluated in the module's namespace need to be treated as if they
were in the module all along.

The repair is obvious: don't treat `#f` as special in this respect.
That's what you see in the patch: the `enclosing-all-scopes-stx`
argument goes away for `expand-module`, and `all-scopes-s` is always
the same as `initial-require-s`. (I left both names defined, though,
because various operations are more directly tied to one notion or the
other.)

The new test uses `(eval-syntax (expand ...))`, which implies a
re-expansion, and then it uses `module->namespace`.

(cherry picked from commit ca1c2c4)

(cherry picked from commit 7bfe967)

Repairs a problem with `raco c-tool --c-mods <file> --runtime <dir>`
as reported by Dmitry Pavlov.

(cherry picked from commit 5fd23b1)

Fix a broken use of a lock intended to prevent threads from
conflicting while forcing "available" modules to "visited" module.

(revised version, matches e2435d7)

(cherry picked from commit ecb6d6c)

... by making `centralized_unblock_child_signal` actually unblock SIGCHLD.

Closes racket#2176

(cherry picked from commit b40fdb7)

When catalog is specified via file:// URL to a local directory with local
package directories that have been stripped in various modes, `raco pkg install`
will incorrectly error out with an incompatible package content error when
a binary strip mode is selected and a file-system error when source strip
mode is selected.

The cause is due to the file:// URL's resolved file path not being passed
along to the helper functions in the various code paths handling the different
strip modes; instead the full original file:// URL is passed along and is
misinterpreted as an actual filesystem path resulting in the observed failure
modes.

The repair is simple; change the relevant argument so the resolved filesystem path
is used instead of the original file:// URL.

Test cases added to test various combinations of strip modes when using
`raco pkg install` and local catalog directory.

(cherry picked from commit aecc786)

Their semantics assume all directory `path-string?` arguments point
to existing directories in the filesystem but they do not actually
check to verify resulting in unhelpful inner exceptions
breaking the functions' semantic abstractions.

Fixed by adding appropriate checks.

Test cases included too.

Documentation updated to reflect the requirement for paths to
refer to existing directories.

Also added note that `generate-stripped-directory` does not
compile or render source files.

(cherry picked from commit 937aa3c)

(cherry picked from commit af9cf01)

…directory` doc.

(cherry picked from commit 6c0d193)

Although a `directory-exists?` check is useful for providing better
error messages, it's fundentally a race condition, since an external
process can always remove a directory between the check and a use of
the directory. Because of that limitation of `directory-exists?`, we
normally avoid making it part of a contract. This commit adjust
937aa3c to follow that convention while preserving the helpful
check and documentation improvements.

(cherry picked from commit 2b9c0c4)

The repair in 4396b84 for internal names exposed a problem with the
way `linklet` handled renaming on export, where it mixed up the names
that should be used internally and externally in errors.

Merge to v7.1

(cherry picked from commit 076684b)

Fix a incorrectly nested "tiny jump" mode that turned off the
surrounding "short jump" mode.

Closes racket#2313

(cherry picked from commit fa6bd87)

Add a new test for the failing case.

(cherry picked from commit 6d7ab42)

(cherry picked from commit c43e42c)

(cherry picked from commit 8b22ebb)