Cannot read property 'prototype' of undefined

I am using the basic example of bottom-sheet but I got this error:
Cannot read property 'prototype' of undefined
"reanimated-bottom-sheet": "^1.0.0-alpha.22"

"react-native": "0.72.4",
"react-native-gesture-handler": "^2.12.1",
"react-native-paper": "^5.10.4",
"react-native-reanimated": "^3.5.4",

I got the same error after updatint to the latest version of expo 49.

I got the same error after updatint to the latest version of expo 49.

I don't use expo workflow but I think the issue is going to be the same! I can't use even other bottom sheet libraries! :/

I got the same error after updatint to the latest version of expo 49.

I don't use expo workflow but I think the issue is going to be the same! I can't use even other bottom sheet libraries! :/

Yes, the issue is the same, expo 49 using RN 0.72.4. This morning I finally solved this problem by using another bottom lib: https://gorhom.github.io/react-native-bottom-sheet.

I am not that lucky, I have tried this before and even didn't get a solution 🫠,
But thanks anyway

I got the same error after updatint to the latest version of expo 49.

I don't use expo workflow but I think the issue is going to be the same! I can't use even other bottom sheet libraries! :/

Yes, the issue is the same, expo 49 using RN 0.72.4. This morning I finally solved this problem by using another bottom lib: https://gorhom.github.io/react-native-bottom-sheet.

Documentation says compatible with Reanimated  V1 and V2, did It work with V3 ?

Any further update on this topic!

I got the same error after updatint to the latest version of expo 49.

I don't use expo workflow but I think the issue is going to be the same! I can't use even other bottom sheet libraries! :/

Yes, the issue is the same, expo 49 using RN 0.72.4. This morning I finally solved this problem by using another bottom lib: https://gorhom.github.io/react-native-bottom-sheet.

Documentation says compatible with Reanimated V1 and V2, did It work with V3 ? @Frontend-dev-sarah

Yes, my projet uses V3, yes it works with V3.

@rezamohdev
How did you mange to solve this!

@rezamohdev How did you mange to solve this!

I did not solve it yet and left my project did you solve it?

is this being maintained?

@demfabris sadly i believe is not

Same problem here after moving to reanimated 3.x and Expo 49. I think it's time to move on and try another library...

Has anyone solved this problem ? Is the only solution to use another package ?

As mentioned by @Frontend-dev-sarah, you can use react-native-bottom-sheet it works with Expo 49 and Reanimated V3. Even though the documentation does not mention Reanimated V3.

Same error after moving to expo 49, has anyone else manage to solve this?

Same error after moving to expo 49, has anyone else managed to solve this?

I've tried, but the only solution was migrate to
https://www.npmjs.com/package/@gorhom/bottom-sheet
It worked fine with Expo 49 and Reanimated V3

What is going on please, I can't even run the example code because of this error

I am also unable to run the example code, I also get this error. Screenshot:

Same error, I just use the basic example but it doesn't work (cannot read property 'prototype' of undefined).
I use expo 51.0.28 and reanimated 3.10.1

Hey guys I am going to close this issue, because there is no solution and it seems the library is not supported and developed any more .
thanks everyone !

Hey guys I am going to close this issue, because there is no solution and it seems the library is not supported and developed any more .
thanks everyone !


Multiple Rules for Single Object File Prevents Parallel Compilation

Multiple modules attempt to build streamer.o with different paths but the same canonical path, causing race conditions in parallelized build:
https://github.com/Decawave/uwb-core/blob/8ffba63755a932a89d841872ce5bdf35b9c78777/Kbuild#L55
https://github.com/Decawave/uwb-core/blob/8ffba63755a932a89d841872ce5bdf35b9c78777/apps/uwb_desense/Kbuild#L23

Thanks Eli,
I will push a fix when public-repo freeze is removed.

@ncasaril should be fixed now as desense apps has been removed ?


Please implement block (scope) highlighting

Issue Type: Feature Request
Highlight the current (potentially nested) scope/block, similar to Qt Creator (the screenshot below) and XCode.

VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 10.0.16299

@tlemo did you see #19690?

Thanks for the pointer @gjsjohnmurray. I assume you're referring to #4 in that list? It's not clear to me if it's the same thing (could be, although the description and screenshots don't seem very specific around the block highlighting part)
At any rate, the block highlighting is not strictly related to folding and I think it's better to track it on its own.

+1 for this, i've gotten used to this in Qt Creator, and i think it's a great feature. There is an extension that kinda-sorta does this, but it is far from being as elegant looking as what Qt Creator has (see OP's screenshot).

I agree that this functionality would be a good candidate for an extension, the question is: does VS Code allow arbitrary decorations, ex. the changing the color of a sub-region of the editor pane? (this would be required to allow an extension to implement block/scope highlighting)
The few extensions which attempt to implement this are limited in that they can only highlight the text and/or the full line background:
https://marketplace.visualstudio.com/items?itemName=byi8220.indented-block-highlighting
https://marketplace.visualstudio.com/items?itemName=imagio.vscode-dimmer-block
Also, while I like the extensibility model, one can argue that the scope highlighting is such a core functionality that it would make sense to implement it in VS Code proper. After all, this is the case for block folding and indent guides.


sbt-jmh should not ignore library dependencies in Runtime configuration

// project/plugins.sbt
addSbtPlugin("pl.project13.scala" % "sbt-jmh" % "0.2.27")

// build.sbt
enablePlugins(JmhPlugin)

libraryDependencies += "org.slf4j" % "slf4j-jdk14" % "1.7.25" % Runtime

libraryDependencies += "org.slf4j" % "slf4j-api" % "1.7.25"

package mypackage
import org.slf4j.LoggerFactory
import org.openjdk.jmh.annotations.Benchmark
class MyBenchmark {
  @Benchmark
  def testLog(): Unit = {
    val logger = LoggerFactory.getLogger(classOf[MyBenchmark])
    logger.info("Hello World")
  }
}

> jmh:run
[info] Compiling 1 Scala source to /private/tmp/jmh/target/scala-2.10/classes...
Processing 1 classes from /private/tmp/jmh/target/scala-2.10/classes with "reflection" generator
Writing out Java source to /private/tmp/jmh/target/scala-2.10/src_managed/jmh and resources to /private/tmp/jmh/target/scala-2.10/resource_managed/jmh
[info] Compiling 5 Java sources to /private/tmp/jmh/target/scala-2.10/classes...
[info] Running org.openjdk.jmh.Main
[info] # JMH version: 1.19
[info] # VM version: JDK 1.8.0_131, VM 25.131-b11
[info] # VM invoker: /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre/bin/java
[info] # VM options: <none>
[info] # Warmup: 20 iterations, 1 s each
[info] # Measurement: 20 iterations, 1 s each
[info] # Timeout: 10 min per iteration
[info] # Threads: 1 thread, will synchronize iterations
[info] # Benchmark mode: Throughput, ops/time
[info] # Benchmark: mypackage.MyBenchmark.testLog
[info]
[info] # Run progress: 0.00% complete, ETA 00:06:40
[info] # Fork: 1 of 10
[error] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
[error] SLF4J: Defaulting to no-operation (NOP) logger implementation
[error] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
[info] # Warmup Iteration   1: 522337535.681 ops/s
[info] # Warmup Iteration   2: 499173949.962 ops/s
[info] # Warmup Iteration   3: 534586788.976 ops/s
[info] # Warmup Iteration   4: 526901701.968 ops/s
[info] # Warmup Iteration   5: 537736249.150 ops/s

Note the warning:
[error] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
[error] SLF4J: Defaulting to no-operation (NOP) logger implementation
[error] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

It means the setting libraryDependencies += "org.slf4j" % "slf4j-jdk14" % "1.7.25" % Runtime does not apply to jmh:run.

It may be that the deps are not collected from the Runtime scope, should be a simple fix if that's it - please give it a try with a pull request?

You did not mention which sbt version you're using, but if 1.0 there was a bug which may relate to this which 1.0.1 fixes;
- Fixes run in Compiletask not includingRuntimeconfiguration, by reimplementingrunin terms ofbgRun. [#3477][3477] by [@eed3si9n][@eed3si9n]

The sbt version is 0.13.16. Sorry I didn't mention it before.

Could you provide a failing test in the sbt-test directory so we could give this a shot together?


Unable to run unit tests

Describe the bug
I am unable to run panda unit tests on a fresh clone of master. This appears to be related to 2ad82cbfb064676401876a20e49e3965c40344a0.
Steps to reproduce:
cd /data
rm -rf openpilot scons_cache
git clone --filter=blob:none --recurse-submodules https://github.com/commaai/openpilot.git
cd openpilot
scons -j$(nproc)
python3 -m pytest panda/tests/safety

ERROR: usage: __main__.py [options] [file_or_dir] [file_or_dir] [...]
__main__.py: error: unrecognized arguments: -n --dist=loadscope panda/tests/safety
  inifile: /data/openpilot/pyproject.toml
  rootdir: /data/openpilot

OS Version
AGNOS 8.2
openpilot version or commit
No response
Additional info
No response

@jnewb1 is this expected to work on device?

agnos doesn't have xdist installed (until https://github.com/commaai/agnos-builder/pull/181 and next agnos release), so it won't work on device. CI uses the test.sh script within tests/safety/, which is what I would recommend to run the panda tests.

Generally, this is expected to work, but we didn't want to delay some pytest refactors on an AGNOS update. For now, you can pip install the new packages on your device.


Run commit without pre-commit hooks (--no-verify)

While trying to add cupper to our boilerplate, I ran into the breaking issue that cupper won't finish its routine when the repo in question has pre-commit hooks configured. These hooks would fix e.g. some line endings, nothing the dev couldn't take care of in the cupper-based PR.
Also noticed that (due to above error), the script continues (returns 0) even though it actually failed. replacing with subprocess.check_call fixes that.

closing as stale, switching to https://github.com/thomasjahoda/cookiecutter_project_upgrader


react-native ActivityIndicator breaks react-bootstrap Form.Control

Description
I use react-bootstrap (v. 2.7.2) for styling. On several places in my app I use Form.Control input box. It has nice "x" shaped button on the right side, which clears content of Form.Control and fires OnChange event.
Since I started to use react-native ActivityIndicator (btw, very nice and easy to use), Form.Control does not contain clear button any more.
This is easily repeatable. I included simple app below.
Not sure if this is react-native or react-bootstrap error. No error is generated in React on compile.
React Native Version
0.71.6
Output of npx react-native info
OS: Windows 10 10.0.17763
CPU: (4) x64 Intel(R) Xeon(R) Gold 5218 CPU @ 2.30GHz
Memory: 2.07 GB / 7.77 GB

Binaries:
Node: 18.16.0 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 9.5.1 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: Not Found
Visual Studio: Not Found
Languages:
Java: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: ^18.2.0 => 18.2.0
react-native: ^0.71.6 => 0.71.6
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
I pasted as simple as possible app below.
If ActivityIndicator is included, Form.Control does not have clear button.
If one comments import of ActivityIndicator and comments Spinner function, Form.Control does have clear button.
Spinner is not used at all, just included in React compile.
Snack, code example, screenshot, or link to a repository
import React from 'react';
import {ActivityIndicator} from 'react-native';
import { Form } from 'react-bootstrap';
const Spinner = ({size}) => {
return (
<ActivityIndicator size={size || 'large'} style={{ flex: 1 }}/>
);
};
function App() {
return (

<Form.Control type="search" placeholder="enter text"
/>

);
}
export default App;

Hi @AudaxDevelopment
Thanks for reporting this issue.
I would suggest you open this issue against react-bootstrap first:
https://github.com/react-bootstrap/react-bootstrap/issues
We receive a huge quantity of issues and we try to prioritize those that have a clear reproducer which don't involve 3rd party libraries. This doesn't exclude a bug in React Native core though, but we can't investigate every possible library combination.
I'll be closing this for now, but feel free to reopen if the other repo points back to us as a issue in the core of React Native.


Backup files component does not allow clicking on 2nd file

SQL Operations Studio Version: daily

Steps to Reproduce:

Get to the Backup wizard (click Backup in a DB Dashboard or similar behavior
Add a 2nd file to the backup files
Try to remove it by clicking on it, then clicking - button

Expected:

Clicking changes the selection
Actual:
Cannot click to change. Clicking adds some weird dropdown / subvalue instead.

Workaround:

Use arrow keys to toggle between them. This is frustrating but does work

looks like it was caused by https://github.com/Microsoft/sqlopsstudio/commit/dafb7809875f49856b9b38e823a2f7dbd72733dd I haven't looked at what changes were made to cause it, but I wouldn't be surprised if we have to rewrite this control.

Does this count as an accessibility issue by the way? Also how were you identifying the VSCode merge as the cause?

accessibility issue? probably? but it's just a usability problem. Its the first commit where this problem shows up, and it also makes sense. That ui component is extended from a vscode component, so they probably rewrote that component and the modifications Kate made to it before no longer work.

Cool. What are next steps? Do we need to chat with @kburtram to get this prioritized?

I'll have to look at home much work it will be to rewrite this and let @kburtram know.


Provide access to last-seen record in get_next_page_token()

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/124
Originally created by @aaronsteers on 2021-05-06 22:08:36

As @rabidaudio points out here:

Another thing I was thinking was it might be convenient for get_next_page_token to receive the latest row, as in this case and other taps I've written the next query starts from the timestamp of the last returned value, as opposed to the number of records or fixed amounts of paging.

And (after some hesitancy :sweat_smile:) I replied:

... I think your intuition is good here. I have another tap implementation I was working on recently we have a since pagination method that takes the integer id of the last record... In both cases, we do need a value from the previous_record in order to orchestrate the pagination loop.

I've thought about this more, and I think the approach of passing the last-seen record's data is preferable to requiring the developer to stash the latest pagination data on each record's parsing, as @rabidaudio's implementation needed to do.
We could add latest_record or last_seen_record into get_next_page_token, with an implementation like:
    def get_next_page_token(self, response, previous_token, last_record: Optional[dict]):
        if not last_record:
            return None

        return { "since": last_record["id"] }

With this implementation, we can optionally also auto-detect if zero records are returned within a page that there is no subsequent page. Otherwise, the developer needs to provide logic for when to stop looping.
Also, we probably want last_record to be None if there have been no records emitted since the last pagination.

Updates (Jun 7, 2021):

I'm inclined to include this in an upcoming release. It will be a breaking change so it should be ideally grouped with other major and/or breaking changes.
My preference would be for last_seen_record to be None in the case of a fully empty page (meaning no records at all returned in the page). However, this makes naming the argument more difficult, since that behavior would not be obvious from the existing naming ideas we've logged.

View 5 previous comments from the original issue on GitLab


Input shape of Soft DTW

Hi, I just reach your paper, Could I have a question the what is the input shape of x and y in this line https://github.com/Maghoumi/DeepNAG/blob/1f6a16aa2ba029ee4e8dfa2536d2b1c2ea3eeda0/models/hausdorff_distance.py#L140
Because I also try Soft DTW, but it uses too much memory, what are the batch size and GPU resources you use in this project?
Thank you!

I added the following print statements right at the start of this function:
....
# Initialize the result to inf
result = torch.ones(x.shape[0], device=x.device) * np.inf
print(x.shape)
print(y.shape)
exit(0)

Here's the output:
torch.Size([4096, 64, 63])
torch.Size([4096, 64, 63])

As you can see, even with our small dataset and a default batch size of 64, these tensors end up becoming fairly large. The reason is that for pair-wise Hausdorff distance calculation between predictions and GT, 64x64 computations are needed (need to calculate the Hausdorff distance between every prediction and GT sample).

I added the following print statements right at the start of this function:
....
# Initialize the result to inf
result = torch.ones(x.shape[0], device=x.device) * np.inf
print(x.shape)
print(y.shape)
exit(0)

Here's the output:
torch.Size([4096, 64, 63])
torch.Size([4096, 64, 63])

As you can see, even with our small dataset and a default batch size of 64, these tensors end up becoming fairly large. The reason is that for pair-wise Hausdorff distance calculation between predictions and GT, 64x64 computations are needed (need to calculate the Hausdorff distance between every prediction and GT sample).

Yes, I have tested and got the problem, this is my test with maximum batch-size for each frame:

Have you reached the method from google which is custom softDTW
https://arxiv.org/pdf/2103.14574.pdf


Upgrading one app breaks many others.

[x] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[x] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new/choose. If it's a brew cask problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all potentially relevant issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
In a nutshell:

I upgraded a handful of utilities (listed below)
one of them (SQLite, in this case) upgraded a dependency (libreadline, in this case)
other things depend on libreadline (such as awk)
so those other things (such as awk) broke.

What happened (include command output)
The entire story can be seen here.  (The only thing that may need some explanation is the update script, which basically just pipes the output of brew outdated through fzf to make it easy to choose which things to update.)

Command output

brew outdatedLast login: Mon Feb 11 23:28:22 on ttys004
You have mail.

In order to prevent conflicts when programs look for libreadline we are
defaulting this GNU Readline installation to keg-only.
For compilers to find readline you may need to set:
export LDFLAGS="-L/usr/local/opt/readline/lib"
export CPPFLAGS="-I/usr/local/opt/readline/include"
For pkg-config to find readline you may need to set:
export PKG_CONFIG_PATH="/usr/local/opt/readline/lib/pkgconfig"
==> Summary
🍺  /usr/local/Cellar/readline/8.0.0: 48 files, 1.5MB
==> Installing sqlite
==> Downloading https://homebrew.bintray.com/bottles/sqlite-3.27.1.mojave.bottle
######################################################################## 100.0%
==> Pouring sqlite-3.27.1.mojave.bottle.tar.gz
==> Caveats
sqlite is keg-only, which means it was not symlinked into /usr/local,
because macOS provides an older sqlite3.
If you need to have sqlite first in your PATH run:
echo 'export PATH="/usr/local/opt/sqlite/bin:$PATH"' >> ~/.zshrc
For compilers to find sqlite you may need to set:
export LDFLAGS="-L/usr/local/opt/sqlite/lib"
export CPPFLAGS="-I/usr/local/opt/sqlite/include"
For pkg-config to find sqlite you may need to set:
export PKG_CONFIG_PATH="/usr/local/opt/sqlite/lib/pkgconfig"
==> Summary
🍺  /usr/local/Cellar/sqlite/3.27.1: 11 files, 3.7MB
==> brew cleanup has not been run in 30 days, running now...
Removing: /Users/brandon/Library/Caches/Homebrew/amber--0.11.1.tar.gz... (174.2KB)
Removing: /Users/brandon/Library/Caches/Homebrew/ansible--2.7.5.high_sierra.bottle.tar.gz... (31.8MB)
Removing: /Users/brandon/Library/Caches/Homebrew/ansible--2.7.1.high_sierra.bottle.tar.gz... (31MB)
Removing: /usr/local/Cellar/asciidoc/8.6.10_1... (214 files, 1.9MB)
Removing: /Users/brandon/Library/Caches/Homebrew/awscli--1.16.80.high_sierra.bottle.tar.gz... (8.3MB)
Removing: /Users/brandon/Library/Caches/Homebrew/awscli--1.16.50.high_sierra.bottle.tar.gz... (7.9MB)
Removing: /Users/brandon/Library/Caches/Homebrew/awscli--1.16.70.high_sierra.bottle.tar.gz... (8.2MB)
Removing: /Users/brandon/Library/Caches/Homebrew/bdw-gc--8.0.0.high_sierra.bottle.tar.gz... (396.8KB)
Removing: /usr/local/Cellar/cairo/1.14.12... (118 files, 5.9MB)
Removing: /Users/brandon/Library/Caches/Homebrew/cmake--3.13.2.high_sierra.bottle.tar.gz... (14.1MB)
Removing: /Users/brandon/Library/Caches/Homebrew/cockroach--2.1.3.tgz... (85.7MB)
Removing: /Users/brandon/Library/Caches/Homebrew/crystal--0.27.0.high_sierra.bottle.tar.gz... (15.3MB)
Removing: /Users/brandon/Library/Caches/Homebrew/curl--7.62.0.high_sierra.bottle.tar.gz... (978.7KB)
Removing: /Users/brandon/Library/Caches/Homebrew/curl--7.63.0.high_sierra.bottle.tar.gz... (995.5KB)
Removing: /usr/local/Cellar/dialog/1.3-20180621... (14 files, 862KB)
Removing: /Users/brandon/Library/Caches/Homebrew/elixir--1.7.4.high_sierra.bottle.tar.gz... (3.9MB)
Removing: /Users/brandon/Library/Caches/Homebrew/erlang--21.2.2.high_sierra.bottle.tar.gz... (75.3MB)
Removing: /Users/brandon/Library/Caches/Homebrew/erlang--21.2.high_sierra.bottle.tar.gz... (75.3MB)
Removing: /Users/brandon/Library/Caches/Homebrew/erlang--21.1.1.high_sierra.bottle.tar.gz... (75.2MB)
Removing: /Users/brandon/Library/Caches/Homebrew/fish--2.7.1.high_sierra.bottle.tar.gz... (2.2MB)
Removing: /Users/brandon/Library/Caches/Homebrew/fish--3.0.0.high_sierra.bottle.tar.gz... (2.5MB)
Removing: /usr/local/Cellar/fzf/0.17.4... (17 files, 3.5MB)
Removing: /Users/brandon/Library/Caches/Homebrew/gauge--1.0.3.high_sierra.bottle.tar.gz... (7.9MB)
Removing: /usr/local/Cellar/gd/2.2.3_1... (35 files, 1.1MB)
Removing: /usr/local/Cellar/gdbm/1.18... (20 files, 589KB)
Removing: /usr/local/Cellar/git/2.19.0_1... (1,512 files, 324.0MB)
Removing: /usr/local/Cellar/git/2.19.1... (1,518 files, 40.1MB)
Removing: /usr/local/Cellar/git/2.20.0... (1,526 files, 41.4MB)
Removing: /Users/brandon/Library/Caches/Homebrew/git--2.19.1.high_sierra.bottle.tar.gz... (14.7MB)
Removing: /Users/brandon/Library/Caches/Homebrew/git--2.20.0.high_sierra.bottle.tar.gz... (15.3MB)
Removing: /Users/brandon/Library/Caches/Homebrew/glib--2.58.1.high_sierra.bottle.tar.gz... (5.5MB)
Removing: /usr/local/Cellar/gnu-indent/2.2.10... (31 files, 495.5KB)
Removing: /usr/local/Cellar/gnu-sed/4.5... (10 files, 532.9KB)
Removing: /usr/local/Cellar/gnu-sed/4.6... (10 files, 560KB)
Removing: /Users/brandon/Library/Caches/Homebrew/gnu-sed--4.6.tar.xz... (1.2MB)
Removing: /usr/local/Cellar/gnu-tar/1.30... (13 files, 1.7MB)
Removing: /Users/brandon/Library/Caches/Homebrew/gnutls--3.6.5.high_sierra.bottle.tar.gz... (2.6MB)
Removing: /Users/brandon/Library/Caches/Homebrew/go--1.11.4.high_sierra.bottle.tar.gz... (140.7MB)
Removing: /usr/local/Cellar/grep/3.1... (15 files, 863.8KB)
Removing: /usr/local/Cellar/grep/3.2... (15 files, 884KB)
Removing: /Users/brandon/Library/Caches/Homebrew/grep--3.2.tar.xz... (1.4MB)
Removing: /Users/brandon/Library/Caches/Homebrew/harfbuzz--2.1.1.high_sierra.bottle.tar.gz... (1.8MB)
Removing: /Users/brandon/Library/Caches/Homebrew/hub--2.7.0.high_sierra.bottle.tar.gz... (4.0MB)
Removing: /Users/brandon/Library/Caches/Homebrew/hub--2.6.0.high_sierra.bottle.tar.gz... (4.0MB)
Removing: /Users/brandon/Library/Caches/Homebrew/hub--2.6.1.high_sierra.bottle.tar.gz... (4.0MB)
Removing: /usr/local/Cellar/icu4c/62.1... (250 files, 67.4MB)
Removing: /Users/brandon/Library/Caches/Homebrew/libassuan--2.5.2.high_sierra.bottle.tar.gz... (148.6KB)
Removing: /usr/local/Cellar/libgcrypt/1.8.3... (21 files, 2.8MB)
Removing: /Users/brandon/Library/Caches/Homebrew/libgpg-error--1.33.high_sierra.bottle.tar.gz... (276.1KB)
Removing: /Users/brandon/Library/Caches/Homebrew/libidn2--2.1.0.high_sierra.bottle.tar.gz... (219.8KB)
Removing: /usr/local/Cellar/libpng/1.6.35... (26 files, 1.2MB)
Removing: /Users/brandon/Library/Caches/Homebrew/libressl--2.8.2.high_sierra.bottle.tar.gz... (2.9MB)
Removing: /Users/brandon/Library/Caches/Homebrew/librsvg--2.44.8.high_sierra.bottle.tar.gz... (23.9MB)
Removing: /usr/local/Cellar/links/2.17... (19 files, 1.6MB)
Removing: /usr/local/Cellar/lucky/0.11.0... (3 files, 1.5MB)
Removing: /Users/brandon/Library/Caches/Homebrew/mackup--0.8.20.high_sierra.bottle.tar.gz... (1.8MB)
Removing: /Users/brandon/Library/Caches/Homebrew/mackup--0.8.21.high_sierra.bottle.tar.gz... (1.8MB)
Removing: /Users/brandon/Library/Caches/Homebrew/mas--1.4.4.high_sierra.bottle.tar.gz... (3.5MB)
Removing: /Users/brandon/Library/Caches/Homebrew/mas--1.4.3.high_sierra.bottle.tar.gz... (3.5MB)
Removing: /Users/brandon/Library/Caches/Homebrew/mas--1.5.0.high_sierra.bottle.tar.gz... (3.5MB)
Removing: /Users/brandon/Library/Caches/Homebrew/mc--20181106011220Z.2018-11-06T01-12-20Z... (13.3MB)
Removing: /Users/brandon/Library/Caches/Homebrew/mercurial--4.8.high_sierra.bottle.tar.gz... (2.3MB)
Removing: /usr/local/Cellar/nettle/3.4... (85 files, 2MB)
Removing: /Users/brandon/Library/Caches/Homebrew/node--11.1.0.high_sierra.bottle.tar.gz... (12.7MB)
Removing: /Users/brandon/Library/Caches/Homebrew/node--11.6.0.high_sierra.bottle.tar.gz... (12.7MB)
Removing: /usr/local/Cellar/openssl/1.0.2p... (1,793 files, 12.2MB)
Removing: /Users/brandon/Library/Caches/Homebrew/ponyc--0.25.0.high_sierra.bottle.tar.gz... (12.0MB)
Removing: /usr/local/Cellar/py2cairo/1.17.1... (16 files, 257.5KB)
Removing: /Users/brandon/Library/Caches/Homebrew/python--3.7.1.high_sierra.bottle.tar.gz... (14.3MB)
Removing: /usr/local/Cellar/rbspy/0.3.2... (6 files, 3.7MB)
Removing: /usr/local/Cellar/readline/7.0.5... (46 files, 1.5MB)
Removing: /usr/local/Cellar/redis/4.0.11... (13 files, 2.8MB)
Removing: /usr/local/Cellar/redis/5.0.1... (13 files, 3.1MB)
Removing: /Users/brandon/Library/Caches/Homebrew/redis--5.0.1.high_sierra.bottle.tar.gz... (1.5MB)
Removing: /Users/brandon/Library/Caches/Homebrew/ruby-build--20181225.tar.gz... (59.0KB)
Removing: /Users/brandon/Library/Caches/Homebrew/ruby-build--20181106.tar.gz... (58.3KB)
Removing: /usr/local/Cellar/s3cmd/2.0.2... (74 files, 982.4KB)
Removing: /usr/local/Cellar/source-highlight/3.1.8_9... (422 files, 6MB)
Removing: /Users/brandon/Library/Caches/Homebrew/sqldiff--3.25.3.high_sierra.bottle.tar.gz... (372.2KB)
Removing: /usr/local/Cellar/sqlite/3.25.2... (11 files, 3.8MB)
Removing: /usr/local/Cellar/sqlite/3.25.3... (11 files, 3.7MB)
Removing: /usr/local/Cellar/sqlite/3.26.0... (11 files, 3.7MB)
Removing: /Users/brandon/Library/Caches/Homebrew/sqlite--3.25.3.high_sierra.bottle.tar.gz... (1.8MB)
Removing: /Users/brandon/Library/Caches/Homebrew/sqlite--3.26.0.high_sierra.bottle.tar.gz... (1.8MB)
Removing: /Users/brandon/Library/Caches/Homebrew/syncthing--1.0.0.high_sierra.bottle.tar.gz... (6.8MB)
Removing: /usr/local/Cellar/thefuck/3.27_1... (1,014 files, 8.0MB)
Removing: /usr/local/Cellar/tmux/2.7... (10 files, 708.9KB)
Removing: /usr/local/Cellar/tree/1.7.0... (7 files, 113.1KB)
Removing: /usr/local/Cellar/watch/3.3.10... (8 files, 73.2KB)
Removing: /usr/local/Cellar/watch/3.3.11... (8 files, 74.8KB)
Removing: /usr/local/Cellar/watch/3.3.12... (8 files, 76.1KB)
Removing: /usr/local/Cellar/watchman/4.9.0... (23 files, 2.0MB)
Removing: /Users/brandon/Library/Caches/Homebrew/wget--1.20.high_sierra.bottle.tar.gz... (1.4MB)
Removing: /usr/local/Cellar/yarn/1.10.1... (14 files, 4.3MB)
Removing: /usr/local/Cellar/yarn/1.12.3... (14 files, 4.7MB)
Removing: /Users/brandon/Library/Caches/Homebrew/yarn--1.12.3.tar.gz... (1.1MB)
Removing: /Users/brandon/Library/Caches/Homebrew/yq--2.2.0.high_sierra.bottle.tar.gz... (2.4MB)
Removing: /Users/brandon/Library/Caches/Homebrew/zsh--5.6.2.tar.xz... (2.9MB)
Removing: /Users/brandon/Library/Caches/Homebrew/zsh--htmldoc--5.6.2.tar.xz... (3MB)
Removing: /usr/local/Cellar/zsh-completions/0.28.0... (145 files, 1MB)
Removing: /usr/local/Cellar/zsh-completions/0.29.0... (147 files, 1MB)
Removing: /Users/brandon/Library/Caches/Homebrew/zsh-completions--0.29.0.tar.gz... (246KB)
Removing: /Users/brandon/Library/Caches/Homebrew/go_cache... (2,758 files, 225MB)
Removing<EMAIL_ADDRESS>(64B)
Removing: /Users/brandon/Library/Logs/Homebrew/syncthing... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/tree... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/libtiff... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/gnu-indent... (6 files, 304.5KB)
Removing: /Users/brandon/Library/Logs/Homebrew/wget... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/yq... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/darcs... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/libidn2... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/mas... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/weboob... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/libksba... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/thefuck... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/go... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/squashfs... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/libpng... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/ponyc... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/ncurses... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/terminal-notifier... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/nettle... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/gdbm... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/cmake... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/mackup... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/python... (3 files, 131.7KB)
Removing: /Users/brandon/Library/Logs/Homebrew/gnu-tar... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/elixir... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/redis... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/boost... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/bdw-gc... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/icu4c... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/harfbuzz... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/duck... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/glib... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/zsh-completions... (111B)
Removing: /Users/brandon/Library/Logs/Homebrew/lucky... (6 files, 22KB)
Removing: /Users/brandon/Library/Logs/Homebrew/erlang... (8 files, 320B)
Removing: /Users/brandon/Library/Logs/Homebrew/llvm... (6 files, 256B)
Removing: /Users/brandon/Library/Logs/Homebrew/utf8proc... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/sqldiff... (6 files, 256B)
Removing: /Users/brandon/Library/Logs/Homebrew/awscli... (8 files, 320B)
Removing: /Users/brandon/Library/Logs/Homebrew/hstr... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/libassuan... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/crystal... (8 files, 320B)
Removing: /Users/brandon/Library/Logs/Homebrew/cairo... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/sqlite... (6 files, 256B)
Removing: /Users/brandon/Library/Logs/Homebrew/libgpg-error... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/rbspy... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/yarn... (100B)
Removing: /Users/brandon/Library/Logs/Homebrew/grep... (7 files, 1.2MB)
Removing: /Users/brandon/Library/Logs/Homebrew/libgcrypt... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/aws-elasticbeanstalk... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/ansible... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/dialog... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/amber... (5 files, 219.7KB)
Removing: /Users/brandon/Library/Logs/Homebrew/curl... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/libcroco... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/gnu-sed... (6 files, 1.2MB)
Removing: /Users/brandon/Library/Logs/Homebrew/source-highlight... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/asciidoc... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/links... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/make... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/librsvg... (194B)
Removing: /Users/brandon/Library/Logs/Homebrew/mercurial... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/watchman... (313B)
Removing: /Users/brandon/Library/Logs/Homebrew/gauge... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/mc... (111B)
Removing: /Users/brandon/Library/Logs/Homebrew/tmux... (6 files, 902.8KB)
Removing: /Users/brandon/Library/Logs/Homebrew/s3cmd... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/watch... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/lastpass-cli... (3 files, 160B)
Removing: /Users/brandon/Library/Logs/Homebrew/gd... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/libressl... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/cockroach... (5 files, 2.5MB)
Removing: /Users/brandon/Library/Logs/Homebrew/py2cairo... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/overmind... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/unison... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/node... (6 files, 256B)
Removing: /Users/brandon/Library/Logs/Homebrew/zsh... (7 files, 1.4MB)
Removing: /Users/brandon/Library/Logs/Homebrew/openssl... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/libusb... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/fish... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/hub... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/gnupg... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/wdiff... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/fzf... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/git... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/libatomic_ops... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/gnutls... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/npth... (64B)
Removing: /Users/brandon/Library/Logs/Homebrew/adns... (64B)
Pruned 6 symbolic links and 63 directories from /usr/local
==> Upgrading mas
==> Downloading https://homebrew.bintray.com/bottles/mas-1.6.2.mojave.bottle.tar
######################################################################## 100.0%
==> Pouring mas-1.6.2.mojave.bottle.tar.gz
nice: /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby: No such file or directory
Warning: The post-install step did not complete successfully
You can try again using brew postinstall mas
==> Caveats
Bash completion has been installed to:
/usr/local/etc/bash_completion.d
==> Summary
🍺  /usr/local/Cellar/mas/1.6.2: 39 files, 11.6MB
Removing: /usr/local/Cellar/mas/1.3.1... (4 files, 7.4MB)
Removing: /usr/local/Cellar/mas/1.3.1_1... (5 files, 7.7MB)
Removing: /usr/local/Cellar/mas/1.4.3... (39 files, 11.5MB)
Removing: /usr/local/Cellar/mas/1.4.4... (39 files, 11.5MB)
Removing: /usr/local/Cellar/mas/1.5.0... (39 files, 11.5MB)
==> Upgrading mackup
==> Installing dependencies for mackup: python
==> Installing mackup dependency: python
==> Downloading https://homebrew.bintray.com/bottles/python-3.7.2_2.mojave.bottl
######################################################################## 100.0%
==> Pouring python-3.7.2_2.mojave.bottle.tar.gz
nice: /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby: No such file or directory
Warning: The post-install step did not complete successfully
You can try again using brew postinstall python
==> Caveats
Python has been installed as
/usr/local/bin/python3
Unversioned symlinks python, python-config, pip etc. pointing to
python3, python3-config, pip3 etc., respectively, have been installed into
/usr/local/opt/python/libexec/bin
If you need Homebrew's Python 2.7 run
brew install python@2
You can install Python packages with
pip3 install
They will install into the site-package directory
/usr/local/lib/python3.7/site-packages
See: https://docs.brew.sh/Homebrew-and-Python
==> Summary
🍺  /usr/local/Cellar/python/3.7.2_2: 3,207 files, 50.9MB
==> Installing mackup
==> Downloading https://homebrew.bintray.com/bottles/mackup-0.8.22.mojave.bottle
######################################################################## 100.0%
==> Pouring mackup-0.8.22.mojave.bottle.tar.gz
nice: /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby: No such file or directory
Warning: The post-install step did not complete successfully
You can try again using brew postinstall mackup
==> Summary
🍺  /usr/local/Cellar/mackup/0.8.22: 949 files, 6MB
Removing: /usr/local/Cellar/mackup/0.8.19... (926 files, 6MB)
Removing: /usr/local/Cellar/mackup/0.8.20... (940 files, 6MB)
Removing: /usr/local/Cellar/mackup/0.8.21... (948 files, 6MB)
==> Upgrading hstr
==> Downloading https://homebrew.bintray.com/bottles/hstr-2.0_1.mojave.bottle.ta
######################################################################## 100.0%
==> Pouring hstr-2.0_1.mojave.bottle.tar.gz
nice: /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby: No such file or directory
Warning: The post-install step did not complete successfully
You can try again using brew postinstall hstr
==> Summary
🍺  /usr/local/Cellar/hstr/2.0_1: 9 files, 122.8KB
Removing: /usr/local/Cellar/hstr/2.0... (9 files, 122.7KB)
==> Upgrading elixir
==> Installing dependencies for elixir: libtiff and erlang
==> Installing elixir dependency: libtiff
==> Downloading https://homebrew.bintray.com/bottles/libtiff-4.0.10_1.mojave.bot
######################################################################## 100.0%
==> Pouring libtiff-4.0.10_1.mojave.bottle.tar.gz
nice: /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby: No such file or directory
Warning: The post-install step did not complete successfully
You can try again using brew postinstall libtiff
==> Summary
🍺  /usr/local/Cellar/libtiff/4.0.10_1: 246 files, 3.5MB
==> Installing elixir dependency: erlang
==> Downloading https://homebrew.bintray.com/bottles/erlang-21.2.4.mojave.bottle
######################################################################## 100.0%
==> Pouring erlang-21.2.4.mojave.bottle.tar.gz
nice: /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby: No such file or directory
Warning: The post-install step did not complete successfully
You can try again using brew postinstall erlang
==> Caveats
Man pages can be found in:
/usr/local/opt/erlang/lib/erlang/man
Access them with erl -man, or add this directory to MANPATH.
==> Summary
🍺  /usr/local/Cellar/erlang/21.2.4: 5,684 files, 272.5MB
==> Installing elixir
==> Downloading https://homebrew.bintray.com/bottles/elixir-1.8.1.mojave.bottle.
######################################################################## 100.0%
==> Pouring elixir-1.8.1.mojave.bottle.tar.gz
nice: /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby: No such file or directory
Warning: The post-install step did not complete successfully
You can try again using brew postinstall elixir
==> Summary
🍺  /usr/local/Cellar/elixir/1.8.1: 416 files, 5.4MB
Removing: /usr/local/Cellar/elixir/1.7.3... (413 files, 5.5MB)
Removing: /usr/local/Cellar/elixir/1.7.4... (413 files, 5.5MB)
==> Upgrading exercism
==> Downloading https://homebrew.bintray.com/bottles/exercism-3.0.11.mojave.bott
######################################################################## 100.0%
==> Pouring exercism-3.0.11.mojave.bottle.tar.gz
nice: /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby: No such file or directory
Warning: The post-install step did not complete successfully
You can try again using brew postinstall exercism
==> Summary
🍺  /usr/local/Cellar/exercism/3.0.11: 6 files, 12.3MB
Removing: /usr/local/Cellar/exercism/3.0.9... (6 files, 12.2MB)
==> Upgrading awscli
==> Downloading https://homebrew.bintray.com/bottles/awscli-1.16.100.mojave.bott
######################################################################## 100.0%
==> Pouring awscli-1.16.100.mojave.bottle.tar.gz
nice: /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby: No such file or directory
Warning: The post-install step did not complete successfully
You can try again using brew postinstall awscli
==> Caveats
The "examples" directory has been installed to:
/usr/local/share/awscli/examples
Bash completion has been installed to:
/usr/local/etc/bash_completion.d
zsh completions and functions have been installed to:
/usr/local/share/zsh/site-functions
==> Summary
🍺  /usr/local/Cellar/awscli/1.16.100: 5,164 files, 48.4MB
Removing: /usr/local/Cellar/awscli/1.16.20... (5,767 files, 52.8MB)
Removing: /usr/local/Cellar/awscli/1.16.50... (4,840 files, 44.3MB)
Removing: /usr/local/Cellar/awscli/1.16.70... (4,888 files, 46.7MB)
Removing: /usr/local/Cellar/awscli/1.16.80... (5,000 files, 47.5MB)
==> Upgrading 4 dependents:
ansible 2.7.5 -> 2.7.6, mercurial 4.8 -> 4.9, protobuf 3.6.1 -> <IP_ADDRESS>_1, python@2 2.7.15_1 -> 2.7.15_3
==> Upgrading ansible
==> Downloading https://homebrew.bintray.com/bottles/ansible-2.7.6.mojave.bottle
######################################################################## 100.0%
==> Pouring ansible-2.7.6.mojave.bottle.tar.gz
nice: /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby: No such file or directory
Warning: The post-install step did not complete successfully
You can try again using brew postinstall ansible
==> Summary
🍺  /usr/local/Cellar/ansible/2.7.6: 12,726 files, 161.9MB
Removing: /usr/local/Cellar/ansible/2.6.4... (12,187 files, 153.4MB)
Removing: /usr/local/Cellar/ansible/2.7.1... (12,567 files, 156.9MB)
Removing: /usr/local/Cellar/ansible/2.7.5... (12,725 files, 161.9MB)
==> Upgrading mercurial
==> Installing dependencies for mercurial: python@2
==> Installing mercurial dependency: python@2
==> Downloading<EMAIL_ADDRESS>######################################################################## 100.0%
==> Pouring<EMAIL_ADDRESS>nice: /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby: No such file or directory
Warning: The post-install step did not complete successfully
You can try again using brew postinstall python@2
==> Caveats
Pip and setuptools have been installed. To update them
pip install --upgrade pip setuptools
You can install Python packages with
pip install
They will install into the site-package directory
/usr/local/lib/python2.7/site-packages
See: https://docs.brew.sh/Homebrew-and-Python
==> Summary
🍺<EMAIL_ADDRESS>4,112 files, 74.4MB
==> Installing mercurial
==> Downloading https://homebrew.bintray.com/bottles/mercurial-4.9.mojave.bottle
######################################################################## 100.0%
==> Pouring mercurial-4.9.mojave.bottle.tar.gz
nice: /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby: No such file or directory
Warning: The post-install step did not complete successfully
You can try again using brew postinstall mercurial
==> Caveats
Bash completion has been installed to:
/usr/local/etc/bash_completion.d
zsh completions have been installed to:
/usr/local/share/zsh/site-functions
==> Summary
🍺  /usr/local/Cellar/mercurial/4.9: 637 files, 10.3MB
Removing: /usr/local/Cellar/mercurial/4.7.1... (593 files, 9MB)
Removing: /usr/local/Cellar/mercurial/4.8... (618 files, 9.9MB)
==> Upgrading protobuf
==> Downloading https://homebrew.bintray.com/bottles/protobuf-<IP_ADDRESS>_1.mojave.b
######################################################################## 100.0%
==> Pouring protobuf-<IP_ADDRESS>_1.mojave.bottle.tar.gz
nice: /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby: No such file or directory
Warning: The post-install step did not complete successfully
You can try again using brew postinstall protobuf
==> Summary
🍺  /usr/local/Cellar/protobuf/<IP_ADDRESS>_1: 366 files, 19.8MB
Removing: /usr/local/Cellar/protobuf/3.6.1... (256 files, 17MB)
Removing<EMAIL_ADDRESS>(4,708 files, 83.3MB)
==> Caveats
==> readline
readline is keg-only, which means it was not symlinked into /usr/local,
because macOS provides the BSD libedit library, which shadows libreadline.
In order to prevent conflicts when programs look for libreadline we are
defaulting this GNU Readline installation to keg-only.
For compilers to find readline you may need to set:
export LDFLAGS="-L/usr/local/opt/readline/lib"
export CPPFLAGS="-I/usr/local/opt/readline/include"
For pkg-config to find readline you may need to set:
export PKG_CONFIG_PATH="/usr/local/opt/readline/lib/pkgconfig"
==> sqlite
sqlite is keg-only, which means it was not symlinked into /usr/local,
because macOS provides an older sqlite3.
If you need to have sqlite first in your PATH run:
echo 'export PATH="/usr/local/opt/sqlite/bin:$PATH"' >> ~/.zshrc
For compilers to find sqlite you may need to set:
export LDFLAGS="-L/usr/local/opt/sqlite/lib"
export CPPFLAGS="-I/usr/local/opt/sqlite/include"
For pkg-config to find sqlite you may need to set:
export PKG_CONFIG_PATH="/usr/local/opt/sqlite/lib/pkgconfig"
==> mas
Bash completion has been installed to:
/usr/local/etc/bash_completion.d
==> python
Python has been installed as
/usr/local/bin/python3
Unversioned symlinks python, python-config, pip etc. pointing to
python3, python3-config, pip3 etc., respectively, have been installed into
/usr/local/opt/python/libexec/bin
If you need Homebrew's Python 2.7 run
brew install python@2
You can install Python packages with
pip3 install
They will install into the site-package directory
/usr/local/lib/python3.7/site-packages
See: https://docs.brew.sh/Homebrew-and-Python
==> erlang
Man pages can be found in:
/usr/local/opt/erlang/lib/erlang/man
Access them with erl -man, or add this directory to MANPATH.
==> awscli
The "examples" directory has been installed to:
/usr/local/share/awscli/examples
Bash completion has been installed to:
/usr/local/etc/bash_completion.d
zsh completions and functions have been installed to:
/usr/local/share/zsh/site-functions
==> python@2
Pip and setuptools have been installed. To update them
pip install --upgrade pip setuptools
You can install Python packages with
pip install
They will install into the site-package directory
/usr/local/lib/python2.7/site-packages
See: https://docs.brew.sh/Homebrew-and-Python
==> mercurial
Bash completion has been installed to:
/usr/local/etc/bash_completion.d
zsh completions have been installed to:
/usr/local/share/zsh/site-functions
Cancelled.
💻                                                                                60708  02-12 15:49 EST  ~  Haddock
💻  awk --help                                                                       60708  02-12 15:49 EST  ~  Haddock
dyld: Library not loaded: /usr/local/opt/readline/lib/libreadline.7.dylib
Referenced from: /usr/local/bin/awk
Reason: image not found
[1]    20748 abort      awk --help
💻 brew upgrade awk                                                              1  60711  02-12 16:53 EST  ~  Haddock
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 2 taps (homebrew/core and homebrew/cask).
==> Updated Formulae
urdfdom
Error: awk not installed
💻  brew doctor                                                                      60706  02-12 17:09 EST  ~  Haddock
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!
Warning: "config" scripts exist outside your system or Homebrew directories.
./configure scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.
Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following "config" scripts:
/Users/brandon/bin/pro-config
Warning: Putting non-prefixed findutils in your path can cause python builds to fail.
Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.
Unexpected dylibs:
/usr/local/lib/libarena-eb0718270c07ad72.dylib
/usr/local/lib/libclang_rt.asan_osx_dynamic.dylib
/usr/local/lib/libclang_rt.tsan_osx_dynamic.dylib
/usr/local/lib/libfdb_c.dylib
/usr/local/lib/libfmt_macros-6aefb1a2994ad90a.dylib
/usr/local/lib/libgraphviz-f4baafd3539eeb00.dylib
/usr/local/lib/libproc_macro-8cb8102c2376e701.dylib
/usr/local/lib/librustc-cf7bdda86562de65.dylib
/usr/local/lib/librustc_allocator-45bb64ed544e742c.dylib
/usr/local/lib/librustc_borrowck-f2b29e362bbb1c23.dylib
/usr/local/lib/librustc_codegen_utils-cabc069e534b2df5.dylib
/usr/local/lib/librustc_cratesio_shim-0b7714aa0e693994.dylib
/usr/local/lib/librustc_data_structures-3a1c9dab6473a806.dylib
/usr/local/lib/librustc_driver-d264c7afc7391fcb.dylib
/usr/local/lib/librustc_errors-585a8076c46d529c.dylib
/usr/local/lib/librustc_incremental-c5ea02a2160eff96.dylib
/usr/local/lib/librustc_lint-726f0ed4f9ed0f3a.dylib
/usr/local/lib/librustc_metadata-b91aa1dc71ba783b.dylib
/usr/local/lib/librustc_mir-3274c6ba5c8f2c51.dylib
/usr/local/lib/librustc_passes-cdb15415e529d997.dylib
/usr/local/lib/librustc_platform_intrinsics-388e08b72f4dcafd.dylib
/usr/local/lib/librustc_plugin-5bf0b3e86f0ea52f.dylib
/usr/local/lib/librustc_privacy-8e0556f56fec4e71.dylib
/usr/local/lib/librustc_resolve-edf51cfde026e377.dylib
/usr/local/lib/librustc_save_analysis-7fce0b4ae219e0e8.dylib
/usr/local/lib/librustc_target-d869528632a89743.dylib
/usr/local/lib/librustc_traits-7454a870f0722ffc.dylib
/usr/local/lib/librustc_typeck-b4552cc80b92ca48.dylib
/usr/local/lib/libserialize-63339dfcab41c5ef.dylib
/usr/local/lib/libstd-424b94dedd6ad921.dylib
/usr/local/lib/libsyntax-ed4b7bd6d356f8ad.dylib
/usr/local/lib/libsyntax_ext-3023a388295f681a.dylib
/usr/local/lib/libsyntax_pos-2d60ae62f6a4f800.dylib
/usr/local/lib/libterm-023527caa724a7b8.dylib
/usr/local/lib/libtest-3f6fd982eb4b1a69.dylib
Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.
Unexpected header files:
/usr/local/include/foundationdb/fdb_c.h
/usr/local/include/foundationdb/fdb_c_options.g.h
Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run brew link on these:
<EMAIL_ADDRESS>gnupg
Warning: Some installed formulae are missing dependencies.
You should brew install the missing dependencies:
brew install gpgme gts ilmbase jasper libde265 libheif libomp little-cms2 netpbm openexr openjpeg x265
💻  brew config                                                                      60708  02-12 17:46 EST  ~  Haddock
HOMEBREW_VERSION: 2.0.1
ORIGIN: https://github.com/Homebrew/brew
HEAD: e32c1515432a938093d5ef1d8c4b4408991873df
Last commit: 6 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 9c2ab034cb1ddb5d39d6ceeeefcd7ac0870e66bf
Core tap last commit: 2 hours ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_GITHUB_API_TOKEN: set
HOMEBREW_LOGS: /Users/brandon/Library/Logs/Homebrew
HOMEBREW_VISUAL: code
CPU: quad-core 64-bit broadwell
Homebrew Ruby: 2.3.7 => /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
Clang: 10.0 build 1000
Git: 2.20.1 => /usr/local/bin/git
Curl: 7.54.0 => /usr/bin/curl
Java: 1.8.0_65
macOS: 10.14.3-x86_64
CLT: <IP_ADDRESS>.1.1539992718
Xcode: N/A

What you expected to happen
I expected awk to display its help.   (Of course --help was just for sake of example.  What I really expect is for all my scripts and shell functions using awk to keep working, but they are all broken now, so this is a very frustrating problem.)
What makes it every stranger is that awk doesn't seem to be installed by Homebrew (at least brew upgrade awk failed as though it was not a Homebrew utility).
Step-by-step reproduction instructions (by running brew commands)

Install any utility that depends on version 7 of the readline library.
Upgrade anything to use version 8
Watch the first utility break.

On the subject of expectations I should add the broader expectations I had of using Homebrew:

I didn't expect upgrading one utility to break another.  If this is a normal occurrence that we should expect, I was not aware of that.
I expected that if there was a risk of breakage I would have been warned before allowing the upgrade. I have had problems with readline before, and because of that never upgrade it unless I'm prepared to deal with the fallout and reinstall everything broken by it.  However in this case there was no warning that readline was going to be upgraded followed by a confirmation.

I worked around this issue by symlinking from the old path to the new library.
💻  ln -s /usr/local/opt/readline/lib/libreadline.8.0.dylib /usr/local/opt/readline/lib/libreadline.7.dylib
But this issue is not about losing awk, it's about the much broader problem of an upgrade to one thing breaking another, and if there is any way Homebrew can avoid letting that happen.

So I think there is some confusion here. We have two versions of "awk" in homebrew-core, called awk (non-GNU version) and gawk (GNU version). You have gawk installed, but you typed brew upgrade awk, which you don't have installed, and brew said as much: Error: awk not installed.
You're therefore using an old version of gawk which was not updated in the readline 7 -> 8 transition.
Our continuous integration infrastructure tests for breakage like this (c.f. https://github.com/Homebrew/homebrew-core/pull/35778), so link errors like the one you are describing shouldn't be seen assuming you're keeping Homebrew updated. For example, my copy of gawk properly links against readline 8:
$ otool -L $(brew --prefix gawk)/bin/awk
/usr/local/opt/gawk/bin/awk:
	/usr/local/opt/gettext/lib/libintl.8.dylib (compatibility version 10.0.0, current version 10.5.0)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1560.12.0)
	/usr/local/opt/readline/lib/libreadline.8.dylib (compatibility version 8.0.0, current version 8.0.0)
	/usr/local/opt/mpfr/lib/libmpfr.6.dylib (compatibility version 7.0.0, current version 7.1.0)
	/usr/local/opt/gmp/lib/libgmp.10.dylib (compatibility version 14.0.0, current version 14.2.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.200.5)

brew upgrade gawk should fix your issues.

What brew upgrade command did you run to upgrade those? I can't see that from your output. I'm not sure how I understand how you've ended up in a state that you've upgraded some apps and not others.

In this case awk turned out to be a symlink to `gawk

@MikeMcQuaid that was mentioned briefly in the "What Happened" section:

The only thing that may need some explanation is the update script, which basically just pipes the output of brew outdated through fzf to make it easy to choose which things to update.

Here's a slightly more verbose explanation:
If you look at the transcript, you'll see update.  This is a script that lets me use fzf to select from the output of brew outdated, and it gives me brew info for the currently selected item to help me decide what to update.  Once I go through the list and select what I want to update, it displays them and asks for confirmation (as seen in the output above).  It lets me use the command line and do everything from the keyboard, but doesn't require enormous amounts of typing long lists of items to upgrade (or cutting and pasting, which seems really weird to do in a terminal).

@jonchang
Yes, you're correct: in this case awk turned out to be a symlink to gawk.  I didn't realize that at the time I filed the report.
But I want to repeat: this is not about awk or gawk.  It's about the fact that upgrading one thing can break another.  That is certainly something I don't expected to be a danger of Homebrew.  It would be a very significant anti-feature if that's "just the way it is".
I don't know if I'm reading too much into your answer, but it seems plausible that you're assuming that everytime anyone upgrades anything with Homebrew, they are expected to upgrade everything.  If that's the case, that is also (in my opinion) a gigantic anti-feature.  I sincerely hope that is not a foundational premise of the way Homebrew has been built.   It would certainly not be a decision I would be in favor of.

If you look at the transcript, you'll see update. This is a script that lets me use fzf to select from the output of brew outdated, and it gives me brew info for the currently selected item to help me decide what to update.

There's a non-zero possibility there's a bug in your script. In future if you're pasting command output please always include only brew commands you've run and not scripts; it's nearly impossible to figure out how to reproduce a problem without seeing commands.
You've also not provided your brew config or brew doctor output which furthermore means that we cannot figure out how to reproduce this.

everytime anyone upgrades anything with Homebrew, they are expected to upgrade everything

This isn't required but it is recommended. In general cases of broken linkage like this we do detect and handle it so there's something else going on here. This isn't getting widely reported so it's likely something specific to your setup and you've not provided enough information for us to help you further.


Galaxy / Kubernetes / HTCondor implementation on Azure

I'd like to use this thread to discuss and present issues around implementing the AnswerALS workflow on Azure using HTCondor and Kubernetes and the Azure Container Service.
The current implementation breaks into two core nodes: storage and compute. We are having issues enabling multiple nodes to be spun up with jobs brokered between them by HTCondor.
The ultimate goal of this implementation is presented in this doc.

latest configuration issue:
11/22/17 16:24:23 SECMAN: FAILED: Received "DENIED" from server for user unauthenticated@unmapped using no authentication method, which may imply host-based security.  Our address was '<IP_ADDRESS>', and server's address was '<IP_ADDRESS>'.  Check your ALLOW settings and IP protocols.
11/22/17 16:24:23 ERROR: SECMAN:2010:Received "DENIED" from server for user unauthenticated@unmapped using no authentication method, which may imply host-based security.  Our address was '<IP_ADDRESS>', and server's address was '<IP_ADDRESS>'.  Check your ALLOW settings and IP protocols.
11/22/17 16:24:23     Failed to send NEGOTIATE command to galaxy@galaxy (<<IP_ADDRESS>:9618?addrs=<IP_ADDRESS>-9618+[--1]-9618&noUDP&sock=194_a576_3>)
11/22/17 16:24:23   Error: Ignoring submitter for this cycle
11/22/17 16:24:23  negotiateWithGroup resources used scheddAds length 0
11/22/17 16:24:23 ---------- Finished Negotiation Cycle ----------

@rc-ms can you tell me how you run the containers, which containers and a few more details to reproduce it?

hi @bgruening apparently @abhi2cool got it running. I'm hoping he'll publich details of our setup here soon

@rc-ms thats good to know. My setup is also working as expected. Let me know if we need to change something.

@rc-ms just to update you, I have just tested things yesterday (https://github.com/galaxyproject/galaxy-kubernetes/tree/feature/sync_with_galaxy_stable/galaxy-stable) and the deployment is working fine. I have improved a few things, probably need to make sure that the documentation has everything, this is probably the main missing bit.

I'll close this since it's stale now.


Loops Should be able to be looped.

Hello, I am trying to loop a loop trial but when I do this it only loops the inner most trial (the trial that is already being looped), this is not conducive to being able to make more complex jsPsych experiments.

Hi @dubailey,
Can you explain a bit more? I'm not sure I understand the problem that you are running into.

Hi, I have a trial that is looped. When I try to loop the loop, what ends
up just happening is the inner most trial is only looped once instead of
being double looped.
On Thu, Feb 4, 2021 at 7:36 AM Josh de Leeuw<EMAIL_ADDRESS>wrote:

Hi @dubailey https://github.com/dubailey,
Can you explain a bit more? I'm not sure I understand the problem that you
are running into.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jspsych/jsPsych/issues/1468#issuecomment-773398588,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACA2CFR4JEBSTILRCGOFE63S5K5GNANCNFSM4XCGOL4A
.

Can you post a code snippet to reproduce the problem?

I'm going to close this until we get more information. Happy to reopen if needed.


⚠ Bofrost.at has degraded performance

In 90265ae, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1635 ms

Resolved: Bofrost.at performance has improved in 4bd15a2 after 9 minutes.


AngularJS Grunt load JS file with dynamic query string parameter

I am developing application with yeoman + grunt + angularJs.
To load the JS file only when require I have added JS file path inside calendar.html using below code.
<! - -  build:js({.tmp,app}) scripts/fullcalendar.js - - >
<  script src="scripts/plugins/fullcalendar/fullcalendar.js" >< / script >
<! - - endbuild - - >
This solution is working properly. But now whenever I load my Calendar page a fresh request goes to fullcalenar.js with dynamic query string parameter like this. If I move above calendar.html code inside index.html file, application works properly and cache the file without combining with rest of the js. But if I add that code inside index.html, the fullcalendar.js file will get loaded with first page itself.
http://localhost/scripts/fullcalendar.a13f9b72f8.js?_=1422010995753
Grunt file code is
compass: {
options: {
javascriptsDir: '<%= yeoman.app %>/scripts',
fontsDir: '<%= yeoman.app %>/styles/fonts',
importPath: './bower_components',
relativeAssets: false,
assetCacheBuster: false,
raw: 'Sass::Script::Number.precision = 10\n'
},
server: {
options: {
debugInfo: false
}
}
}
Please help me.
Thanks in advance.

Not sure how this has anything to do with this plugin, but support questions are better asked on StackOverflow anyways.

Thanks for replying. Already posted yesterday.
http://stackoverflow.com/questions/28108792/angularjs-grunt-load-js-file-with-dynamic-query-string-parameter


Connect to WPA2-Enterprise Access Point Problem  (IDFGH-4061)

Board: ESP32-WROOM/ESP32 DevKitV1
IDF-Version: v4 release

Problem Description
Connection to WPA2-Enterprise Access Point is not possible.
This applies to all three EAP methods (EAP-TLS, EAP-PEAP, EAP-TTLS)
Wifi environment
Cisco WPA2 Enterprise Access Point with a Freeradius server.
ESP32 Log Output
The ESP32 prints the following error repeatedly:

D (4024) wpa: TLS: using phase1 config options
D (4024) wpa: TLSv1: Failed to initialize verify hash
I (4034) wpa: SSL: Failed to initialize new TLS connection
I (4034) wpa: EAP-TLS: Failed to initialize SSL.
E (4044) wpa: Method private structure allocated failure

The Freeradius server prints the following message 50 times before ending the authenticication process:

(157) eap: Peer sent packet with method EAP NAK (3)
(157) eap: Peer NAK'd our request for TLS (13) with a request for TLS (13), skipping...
(157) eap: WARNING: !!! We requested to use an EAP type as normal.
(157) eap: WARNING: !!! The supplicant rejected that, and requested to use the same EAP type.
(157) eap: WARNING: !!!     i.e. the supplicant said 'I don't like X, please use X instead.
(157) eap: WARNING: !!! The supplicant software is broken and does not work properly.
(157) eap: WARNING: !!! Please upgrade it to software that works.

Expected behaviour
ESP32 connects to Access Point.
Actual behavoir
Connection cannot be established using the WPA2 Enterprise Example Code.
Timeout using the AT-Command Firmware v2.1 Release
Using the WPA2 Enterprise credentials or the certifictates created with Freeradius for EAP-TLS on several smartphones works without a problem. So the Freeradius configuration, the Wifi environment or the certificates should not be the causing the error.

Hi @CKe-rde,  this could be interop issue. Can you help to share the certificates used and exact commit ID?

Hi @CKe-rde, this could be interop issue. Can you help to share the certificates used and exact commit ID?

The commit ID of the esp-at Firmware is: a8f0b01652197c4a56d9805aee9e3ae61db3847c
The certificates are in the attached zip archive.
The certificates are with sha256 with RSA Encryption. Could that be a problem?
I've read in an other issue from last month that sha256 isn't supported.
ESP32_Cert.zip

Hi @CKe-rde, I think you are referring to https://github.com/espressif/esp-idf/issues/5805. That issue is fixed on master. Can you help to check? We will also check on our side. If required, we will backport the fix onto v4.0.

@sagb2015 yes that is the issue I was referring to. There is now mentioned that the fix is not yet included in the master branch. I can test the WPA2 autnetication with the master when the fix is included.

@CKe-rde  Yes, the commit should be available soon since it is internally merged. You will have to wait until then.

@CKe-rde  In case you missed  this is now fixed on master.

@sagb2015  Thank you for the remainder. It works with the examples/wifi/wpa2_enterprise.
Will this also work with AT Command Firmware?
I've tried testing it with the v2.1 for the ESP32 but unfortunately I encountered a Problem during the build proccess (which is mentionend in this #issue) and working on resolving that.


The holders endpoint does not return the same response when querying a subasset using its asset_longname versus its asset field

The holders endpoint does not return the same response when querying a subasset using its asset_longname versus its asset field
https://api.counterparty.io:4000/v2/assets/TOPINI.LONGONE/balances

https://api.counterparty.io:4000/v2/assets/A95428957753448833/balances

done here https://github.com/CounterpartyXCP/counterparty-core/pull/2786


Add list fail-fast config option

Change Summary

Add list fail-fast config option.
Related issue number
fix: #1321

Checklist

[x] Unit tests for the changes exist
[ ] Documentation reflects the changes where applicable
[x] Pydantic tests pass with this pydantic-core (except for expected changes)
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Selected Reviewer: @dmontagu

please review

Great, I will update this PR to add this feature to more iterable types!

Could we implement this as an exception, similar to PydanticOmit? That way a python-defined validator can control the flow.

@adriangb Makes sense to me, I will try to reimplement it in similar way as PydanticOmit is working

It may be that both are necessary, there's mutliple use cases:

Inside of a python validator you want to abort the rest of the list, similar workflow to PydanticOmit
You just want to abort early with no python handler (like this PR implements)

Hi @adriangb @davidhewitt
This PR is ready with basic implementation of fail-fast feature for list, set, frozenset, and tuple types.

Could we implement this as an exception, similar to PydanticOmit? That way a python-defined validator can control the flow.

@adriangb I suggest implement this feature in separate PR just to make review/merge process easier. What do you think about it?

Makes sense to me

I see the Python PR is now prepared too, many thanks 🚀


Replace TravisCI with Github Action Workflow

TravisCI has gone through a business transition and I think Github Actions, which is free for public repos, is a good alternative.
Note: there is additional contributor documentation that will need to be updated, but I would like to ensure that Github Actions is a viable alternative before doing a broad sweep of process change updates.

@assaf @phillbaker would one of you be able to enable Github Actions on this repository, or to provide me admin permissions so that I can enable it? Thank you 🙏

I don't have admin access - I think I reached him on twitter actually laster time: https://twitter.com/assaf

It says that all actions are enabled for this repository. I don't see any permission levels, only add/remove contributors.

@frostmark I'm going to merge this to the main branch. I think it's possible that GH actions won't kick off until there is a workflow on the main branch.


fix(src/util/file_lock): ignore failure to create locks on read-only file systems

Right now, file_lock ignores the EACCES error when creating lock files, assuming that the file to be locked is part of a system-wide installation.  On NixOS however, the file system containing system packages is even mounted read-only, so open returns EROFS.  This results for example in the following error:
/home/gebner/lean/library/examples/ex.lean:4:0: error: failed to lock file '/nix/store/fxc0cvnv0j6kc1yc2ygngz7c805n10j5-lean-20160116/lib/lean/library/init/default.olean'

This PR ignores EROFS in addition to EACCES.

Thanks for making the pull request.


tidy up what is linux, upgrade path

wow I never knew you hated apostrophication so much. I hope you feel better now


Deletes service files in case of etcd connection problems

It seems fleet likes to delete already running systemd services if it loses contact with etcd.
I'm running a http proxy on all instances except a few "core" ones which has the real etcd, unfortunately this proxy lost its connection to upstream giving HTTP 503 instead.
This caused services that was running happily to be removed by fleet, I would not expect this to be the default behavior. Instead I expect service files to be left alone unless a task says explicitly to destroy them.

What version of CoreOS is this on?

@balboah This is by design. fleet's goal is more on the consistency end of the spectrum rather than availability, meaning that if fleet can't tell what it should be doing, it needs to revert to the safest state possible. fleet depends on etcd to tell what it should be doing, so if it can't communicate with etcd, it must revert to doing nothing. For example, in the event of a network split, the scheduler will move work to healthy nodes, but it has no way to communicate to the unhealthy nodes that they no longer are responsible for their jobs.

Ok. Thanks.
You could argue that actively removing already scheduled services is not
the same as "doing nothing" but I understand the design decision. I'll try
to make the etcd part work better instead.
måndag 9 mars 2015 skrev Brian Waldon<EMAIL_ADDRESS>
Closed #1145 https://github.com/coreos/fleet/issues/1145.
—
Reply to this email directly or view it on GitHub
https://github.com/coreos/fleet/issues/1145#event-248718047.

@balboah "doing nothing" meaning an unhealthy fleet agent is not allowed to execute any more work. We have discussed the concept of a unit SLA before, but I can't seem to find where that was documented. Basically, we want to be able to define a policy that should be applied to a given unit when its host "goes away": basically whether to reschedule after N seconds or to never move the job. If you want to get a functional specification together for this behavior, I would be more than happy to work with you to get it implemented.


Escape characters in strings

Describe the bug

in terminal: <unknown>:2: SyntaxWarning: invalid escape sequence '\L'
Environment
{
  "marimo": "0.9.1",
  "OS": "Windows",
  "OS Version": "10",
  "Processor": "Intel64 Family 6 Model 94 Stepping 3, GenuineIntel",
  "Python Version": "3.12.7",
  "Binaries": {
    "Browser": "129.0.6668.59",
    "Node": "--"
  },
  "Dependencies": {
    "click": "8.1.7",
    "importlib-resources": "missing",
    "jedi": "0.19.1",
    "markdown": "3.6",
    "pygments": "2.18.0",
    "pymdown-extensions": "10.11.2",
    "ruff": "0.6.9",
    "starlette": "0.39.2",
    "tomlkit": "0.13.2",
    "typing-extensions": "4.12.2",
    "uvicorn": "0.31.1",
    "websockets": "12.0"
  },
  "Optional Dependencies": {}
}

Code to reproduce
No response

I think this is just Python, not marimo. You can replace double quotes with single quotes, or escape your backslash

Feel free to reopen if I misunderstood.

I could've sworn python is not tripped up by this, but you are right.  My bad.


Test infrastructure for internal algorithms

This issue emerged with #135. @shuaiche and me have to develop several internal algorithms. Since new algorithms will be more complex it will be very useful to develop a test infrastructure which helps to easily validate and debug internal clSPARSE algorithms. Nowadays I did that by adding temporary interface API functions in clSPARSE.h but that is very time consuming and it is limited with C language restrictions.
Do you have any ideas how to tackle this issue? Where to put new test-internal folder? How the project tree should look like?
What is your experience with that?

Give me a day or two to brainstorm :crystal_ball:

The complicated part of testing internal routines, is that we normally compile our library as a dynamic shared module, and it does not export routines unless they are decorated with CLSPARSE_EXPORT.
That leaves two options available on the table:

We write internal test programs that MUST link to the library as a STATIC module, or the linker will complain of unresolved symbols
We write internal test programs that compile in bits of the library we want to internally test, i.e. it includes as part of the test executable files from the library.  In this way, the test program avoids linking in the library altogether.

@kknox
Looks like some OpenCL packages still do not ship cl.hpp (ref https://github.com/clMathLibraries/clSPARSE/issues/139). Adding cl.hpp to the repo sounds like the better option at the moment.

Hi, what I would like to have is to take part of the clSPARSE (internal
data structures, kernel mechanism execution and probably other existing
algorithms and put it nicely into one "internal" test which helps to
develop other algorithms.  Here I want to avoid linking with the clSPARSE
library, it can be broken in some places during the development. Is that
idea is described in second point of your script (Forgive me I didn't
understand what you have written there)?
2015-09-08 7:42 GMT+02:00 Kent Knox<EMAIL_ADDRESS>
The complicated part of testing internal routines, is that we normally
compile our library as a dynamic shared module, and it does not export
routines unless they are decorated with CLSPARSE_EXPORT.
That leaves two options available on the table:

We write internal test programs that MUST link to the library as a
STATIC module, or the linker will complain of unresolved symbols
We write internal test programs that compile in bits of the library
we want to internally test, i.e. it includes as part of the test executable
files from the library. In this way, the test program avoids linking in the
library altogether.

—
Reply to this email directly or view it on GitHub
https://github.com/clMathLibraries/clSPARSE/issues/137#issuecomment-138440346
.

Yes, so I think either of the two options I listed above would work, and I am leaving it open to see which way you would prefer.  To explain in more detail:

Our test programs that provide unit tests through the public clSPARSE API would remain as is and link to our library dynamically.  If you create an 'internal' test executable, I imagine that you would provide API's that you want to 'test' in our internally global clSPARSE-private.h, or some other internal header file that you could #include in your test program directly.  To do this, we would have to modify the cmake build to also create static clsparse libraries, to get access to the internal symbols.  You then compile your internal test executable and link in the static library, and all symbols should resolve.  This has hte benefit in that the library object code is still digested in a 'library' format; only the header files would be explicitly part of the test executable.  This is probably the easiest solution, but needs significant build support
Alternatively, you create a test executable that #includes library header files and builds individual library files as part of the test project.  I think this one is self explanatory, and would require almost no build modifications, but is slightly more fragile.  If developers in the future shuffle files around or rename them, they will easily break the test executables too.


Remove deprecated Snake Case config support in rialto configs

Summary: Remove deprecated Snake Case config support in rialto configs
Type: Feature
Test Plan: UT/ CT, Fullstack
Jira: RIALTO-711

Sanity tests for ['RPI4 IPSTB'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/67787/

Sanity tests for ['BCM 7216OTT Refboard VA'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/67789/

'['RPI4 IPSTB']' Sanity test FAILURE, investigation pending.
Build Job/Num: build-rpi4-ipstb-oss/8340
Flash rdkv_rpi4_ipclient [SUCCESS]
rdkv_rpi4_ipclient - Video Test [FAILURE]
Video Accelerator Home Screen Test [SUCCESS]
Video Accelerator VOD Video Detection Test [FAILURE]
HLS video streaming using gst-launch uri=aamp [SUCCESS]
HLS Video Streaming using aamp-cli [FAILURE]
DASH Video Streaming using aamp-cli [FAILURE]
Video local (H264) using gst-play-1.0 [FAILURE]
Video local (H264) using gst-play-1.0 [SUCCESS]
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-raspberrypi-rdkv-rpi4-flow/15709/


Linux Support

I was able to make it work on Linux. Only covering the most common case, but it should also present how it could be done.

I haven't touched this in so long, so if this works for you, I'm happy to merge whatever in.


Small macro cleanups + big concurrency cleanup

Start moving all the concurrency calls to a common path in order to facilitate moving to multiple runtimes in the future (e.g. async-std). However there's more generalization work to do to make that work, this is an initial step and reduces the usage of the tokio namespace to just some common patterns used throughout the crate.

Codecov Report
Base: 86.17% // Head: 86.18% // Increases project coverage by +0.01% :tada:

Coverage data is based on head (57514c5) compared to base (183339b).
Patch coverage: 80.88% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #30      +/-   ##
==========================================
+ Coverage   86.17%   86.18%   +0.01%
==========================================
  Files          24       25       +1
  Lines        2300     2331      +31
==========================================
+ Hits         1982     2009      +27
- Misses        318      322       +4

Impacted Files
Coverage Δ

ractor/src/actor/errors.rs
67.44% <ø> (+8.25%)
:arrow_up:

ractor/src/lib.rs
92.59% <ø> (ø)

ractor/src/rpc/mod.rs
64.66% <19.35%> (-4.70%)
:arrow_down:

ractor/src/concurrency.rs
96.42% <96.42%> (ø)

ractor/src/actor/actor_cell/actor_properties.rs
98.50% <100.00%> (ø)

ractor/src/actor/actor_cell/mod.rs
99.13% <100.00%> (ø)

ractor/src/actor/mod.rs
90.03% <100.00%> (ø)

ractor/src/actor/tests/mod.rs
94.73% <100.00%> (ø)

ractor/src/actor/tests/supervisor.rs
91.18% <100.00%> (ø)

ractor/src/pg/tests.rs
95.42% <100.00%> (ø)

... and 8 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Fix bug with empty quota

During plugin tests we found a bug that when a node is added to a cluster we have empty quotas for resources in a container size which prevents successful node addition

https://github.com/subutai-io/base/commit/9e07cfc0d679274751822998b05b53941e608d32


feat(v2): Plugin for Offline/PWA support

Changes

Implements @docusaurus/plugin-pwa
Add popup for notifying users of updated website content
Adds @docusaurus/plugin-pwa to v2 website, adding offline/PWA support

Motivation
Implements offline support as requested in #458. Having offline support is beneficial for a dev that needs documentation to work on a project where internet is slow or inaccessible (i.e. airplanes, trains, etc.)
Have you read the Contributing Guidelines on pull requests?
Yes 😄
Test Plan
I've manually tested offline support in the browser and as an installed app. I also ran a lighthouse audit.
Loading Offline

Installing as a Chrome App

Open app in chrome://apps

Lighthouse Audit

Redirect HTTP to HTTPs is server dependent so it's checked off in the audit.
Update Popup

Related PRs

This is pretty amazing, I recently tested oflline and noticed the site went down so this is ❤

This is pretty amazing, I recently tested oflline and noticed the site went down so this is ❤

@codemonkey800 wow, I love this! One possible idea is to implement something like VuePress's plugin (https://vuepress.vuejs.org/plugin/official/plugin-pwa.html) that creates a popup when content has been refreshed.

This is such amazing and great work from the community. We're shorthanded now and I'll only have time to review next weekend though. Thank you from the bottom of my heart ❤
Maybe @lex111 can take a stab at reviewing it too.

@nebrelbug great suggestion :) I'd love to add something like this, I'll see if it's something I can get around to implementing. I mostly wanted to get a foundation for offline/PWA functionality first

@codemonkey800 how goes it? I am wondering if we can refuse to use external dependency (Workbox) for SW? For example, how is this done in VuePress?

@lex111 i've been swamped with work but I'll push my remaining changes either tonight or tomorrow. It includes the PWA popup to reload the page and processes the service worker in Webpack.
It is definitely possible to make this work without Workbox. The main things we use Workbox for is:

Generating service worker manifest
Using Workbox strategies to cache things on the fly
Handling when to show the popup

VuePress also uses workbox, specifically the generateSW function: https://git.io/JvEPw

@codemonkey800 I will check it soon, will I get recommendations on how to correctly check PWA? What could be the negative consequences of this?

@lex111 You could run PWA Lighthouse audits in your dev tools on the preview website. You can also refer to the PWA checklist: https://web.dev/pwa-checklist/
To check the update popup, you'll need to:

Run yarn build in website/ and run an http server. This is to register the initial service worker
Make changes to website/, like update a markdown file somewhere
Run yarn build again and run an http server. If you look in Chrome Dev Tools on the Application tab, you should see a second service worker being installed, eventually moving in the waiting stage, and after that  the popup should show

Some possible negatives I can think of are:

Normal browser reloads will not update the website anymore. Either a hard refresh or clicking Refresh on the popup will update the contents.
That said, if a developer introduces a bug that prevents rendering of the popup dialog, the user may not be able to update the website without doing a hard refresh. For example, consider this scenario:

User visits docusuaurs site for the first time and the service worker gets registered
Developer introduces bug that causes renderPopup() to fail
User visits docusuaurs site again. Because their current cached renderPopup() works, it'll show the popup indicating that there's a new version of the website
Developer updates markdown or something
The update popup never shows because the renderPopup() function is buggy, so the user stays stuck with the cached version of the docusuaurs site until they hard refresh the page

There are definitely tradeoffs when making a PWA, but I think it should be up to the discretion of the user if they want to add it. However, whether we add it to the docusuaurs site itself is up for debate 😅

@codemonkey800 thanks for detail input. Hmm, maybe it makes sense to activate PWA only in certain cases? For example, if the user explicitly install the site as an application? If the user visited the site with mobile?
I described these cases in this pseudocode:
let forceOffline = location.search.includes('offline');

function isSaveDate() {
  let saveData = navigator.connection && navigator.connection.saveData
  return window.innerWidth <= 940 || saveData
}

if ((forceOffline || !isSaveDate()) && navigator.serviceWorker) {
  // init SW if the user turned on save data mode or they just went to a page from a mobile OR `force` option exists (for testing purposes)
  // See https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/save-data/ for details
} else if (localStorage.appinstalled) {
  // init SW if user installed site as an app and refresh a page
  } else {
  window.addEventListener('appinstalled', () => {
    // init SW if installed site as an app

    localStorage.appinstalled = true;
  });
}

What do you think?

@lex111 For sure, I think that sounds like a good idea. How about we make this the default behavior and add an option like hybrid that defaults to true. If hybrid is false, then make the app entirely PWA without the above cases for users who want a fully PWA doc site
I will need to research and see if it's possible to install an app and run the service worker after because usually it's the other way around

@codemonkey800 I’m not sure exactly whether this option is needed, because in my view PWA + Offline  is only needed for certain cases (mobile devices, or if the site is implicitly using it as an application). I updated example above to show the init SW, isn’t this the case in reality?

@lex111 Oh okay never mind I think I understand now. One thing I'm wondering is how should we let the user force offline mode? Aside from adding /#offline directly to the URL?

@codemonkey800 yep, something like "https://v2.docusaurus.io/?offline" (location.search.includes('offline')). This will be needed for testing, and besides this, in the future I want to add Lighthouse check to CI.

@codemonkey800 will there be a way to specify the Workbox caching strategy in the docusaurus.config.js? Ex. strategy: 'stale-while-revalidate' or strategy: 'network-only'
https://developers.google.com/web/tools/workbox/modules/workbox-strategies

@nebrelbug There's currently no way to specify the strategy for the precache manifest unfortunately. See https://github.com/GoogleChrome/workbox/issues/1767
However, you can set up your own runtime strategies using the custom service worker but it won't be added to the cache at the very start like resources in the precache manifest

@lex111 In order for the app install button to show, there needs to be a running service worker, so we can't do registration after 😢

@codemonkey800 too bad, are there any options to get around this? For example, check the conditions for the use of PWA in the service worker?

@lex111 We could possibly pass an empty array into precacheAndRoute() to make the browser think it has offline support. Since the array is empty, every resource will be downloaded over the network.
Then when the user installs the app, we can emit a CACHE_FILES message to the service worker so it can precache the actual manifest.
An issue I see here is if the user uninstalls the app, I don't think there's currently a way to detect that, so the service worker will continue to precache files. Is this okay?

An issue I see here is if the user uninstalls the app, I don't think there's currently a way to detect that, so the service worker will continue to precache files. Is this okay?

Of course, it is undesirable to have such behavior... is it really impossible to avoid this? Any thoughts?

Actually I think we can use the beforeinstallevent with localStorage.appinstalled to clear the cache, but it'll require a reload when that happens because the website would have loaded with the cached data instead of the latest.
I will find some tonight and tomorrow to continue working on this

@codemonkey800 could you please finish this PR? We really want PWA!

@codemonkey800 This PR looks great. Thanks so much!! Can't wait for it to be merged :-)

@lex111 finished implementing your requirements. working with the cache is a bit tricky 😆
this was accomplished by using PreccacheController to dynamically add cache entries if it met the conditions you described
the service worker determines whether it should cache files or not using the enabled query param: /sw?enabled. because of this, when installing the app, the browser treats it as a new service worker. normally, the new service worker will be pushed into the waiting state and the reload popup will show up, but this doesn't make sense for the first load of the app.
to fix this, i had to clear registrations and reload the app immediately after install. similarly, when the app is uninstalled, when the user loads the website again, registrations are cleared and another reload is initiated.
ultimately, the side effect of this dynamic file caching mechanism results in small reload flashes when installing the app and after uninstalling it. is that okay?

@lex111 sorry for it taking longer than it should, i was in between switching jobs 🤣
let me know if you find anything

@codemonkey800 @yangshun @RDIL - hi folks, just a friendly bump to get this back on your radar, as many of us would really love this feature!  In my case, we have a desktop app for use in mostly offline hospital environments, which makes this a must if we want to convert from mkdocs to Docusaurus.  Thanks so much for the hard work here and dedication to quality, here. 🎉

I am joining in on the excitement of @adamwdennis! I was wondering whether this feature would mean that we could potentially ship a prebuilt local version of the documentation with our product such that internet is not required at all to access it? That would be huge if possible!

currently waiting on @yangshun to review 😄
@krillboi i think that's something you could do now by building your docusaurus site statically

currently waiting on @yangshun to review 😄
@krillboi i think that's something you could do now by building your docusaurus site statically

Problem with this is that you still need to run that static site on a local web server to get it to function correctly. I was thinking more of a complete out-of-the-box shipment 😄
I'm not very well versed in this PWA implementation and what it actually entails, so I might be off base here 😅

@krillboi you can do npx static-server-rdil :)

@RDIL I don't have problems running local web servers for development, but my question more revolves around the ease of the user potentially just opening the website straight from disk in an offline setting. Of course it's possible to ship an executable to open the site on a local web server I guess.
I also have a dream in our application to link to pages locally instead of online since that would mean changing domains and paths wouldn't break the links found in older versions of our product (which is a problem we are facing now after moving our doc to using Docusaurus and a new domain). But I'm guessing this is not possible because Docusaurus is server-rendered, and cannot function properly without a web server, and this PWA PR won't help any of that if I'm understanding correctly?

@krillboi it sounds like what you want is a desktop app? you could try deploying docusaurus as the main view for an electron app and try distributing the app executable. it would add quite a bit of MB to your runtime, but it sounds like it would satisfy your use case. if an electron app is what you're looking for, then you can definitely set this up without the PWA 😄
it is possible to use the PWA offline, but that requires visiting the website directly (meaning you'll need a web server) and installing the PWA

@krillboi before I want same thing, and tried use this PWA plugin. this PWA plugin work fine <3 but build offline version still not work.
Then I created PDF file. You can follow this comment:
https://github.com/facebook/docusaurus/issues/969#issuecomment-595012118

@stionic Cool, I'll have a look 😄

Is there going to be any documentation on https://v2.docusaurus.io/docs/ for this?

Any eta on this?

It kinda looks like @codemonkey800 needs to fix the merge conflicts.

synced my fork with master, @lex111 @yangshun would be nice to review and merge this 🐱

@lex111 has already approved it :) @wgao19  and @yangshun  now lol

@slorber would you take a look at this?

While testing out the deploy preview (https://deploy-preview-2205--docusaurus-2.netlify.app/) on my device, I get the following error...

@nebrelbug thank you for catching that, i'll take a look at it sometime this weekend. something must have changed while this PR was waiting for a review

Okay I had to re-disable the eslint rule for restricted globals in the service worker because I forgot that window isn't available in the service worker.
Also I had to remove window.self.__WB_GLOBALS  because it was replacing the self.__WB_GLOBALS part, but not the window part, so it would output as window.[ ... ] which is invalid syntax

@slorber @yangshun i moved the compile() function from commands/build.ts to webpack/utils.ts, so there's always going to be a merge conflict whenever new code gets merged into master. do you mind reviewing what I have now, then I'll fix the merge conflicts and merge this PR after approval?

@slorber I don't have much experience with PWAs. Do you think you could help get this PR merged?

@codemonkey800 do you have time to work on this soon?
If not, I can help (rebase, minor code changes, polish, apply new plugin option validation system using Joi...), and try to get this merged at the beginning of next week.
What do you think?

@slorber thank you for all the feedback 😄 Some help with this PR would be awesome if you have the time. I've been hyperfocused on projects at work so I haven't been able to give this PR as much love as I want to

Sure @codemonkey800 , as I'm a contributor to this repo I have push access to your forked branch, will update it directly with some of the things I reported on the review (don't forget to pull your own branch to get my updates if you want to)

Hey @codemonkey800 , I think this PR is ready. If you have some time to review my changes, so that I can merge it asap, that would be great.
Otherwise I'll merge it tomorrow. As it's a plugin, and we are in alpha, we think it's better to get it merged, and see if we have some feedbacks and bug reports to improve it.
Major changes:

custom babel/webpack setup more adapted for SW code
debug mode (custom logs + workbox logs)
configurable offline mode / precaching activation strategies + sensible defaults
better QS params passing between registerSW and SW
use default browser ui for app installation
minor changes (refactors, renamings, docs...)

Overall your code worked great, thanks for your work.

@slorber wow, this is amazing work 😄 I'll take a look at all the code today, but from what I've seen it's looking very good. thank you so much for the help

@slorber I finished reviewing the new code. I love all the new changes you added, it makes the PWA a lot more robust 😄

awesome @codemonkey800 , let's merge this finally! 🎉

Finally! Thanks @codemonkey800 @slorber @lex111!

Thank you @slorber and @lex111 with all the help in reviewing this and finally getting it merged. I couldn't have done it without y'all 😃

Nice work guys! Can't wait for the release :-) @codemonkey800 @slorber @lex111

Hey all,  this is feature is now released!
If you like it, don't forget to retweet 😄
https://twitter.com/docusaurus/status/1286715187983048704