EAS Update - Github Action: JsonFileError: Can't read JSON file

Build/Submit details page URL
No response
Summary
We are on the production plan and are experimenting with eas-update for automating CI test JS bundle updates.
I've followed the steps listed here to setup a Github action (using npm instead of yarn) that automatically updates when our main iteration-2 github branch is pushed to with the  following Github action:
name: EAS Iteration Update
on:
  workflow_dispatch:
  push:
    branches:
      - 'iteration**'
jobs:
  build:
    name: EAS Update
    runs-on: ubuntu-latest
    steps:
      - name: Check for EXPO_TOKEN
        run: |
          if [ -z "${{ secrets.EXPO_TOKEN }}" ]; then
            echo "You must provide an EXPO_TOKEN secret linked to this project's Expo account in this repo's secrets. Learn more: https://docs.expo.dev/eas-update/github-actions"
            exit 1
          fi
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
        with:
          node-version: 16.x
          cache: npm
      - uses: expo/expo-github-action@v7
        with:
          expo-version: latest
          eas-version: latest
          token: ${{ secrets.EXPO_TOKEN }}
      - name: Install dependencies
        run: npm install
      - name: Publish update
        run: eas update --auto

However, this is currently failing with the following error:
- Linking to project @[owner]/[project]
✔ Linked to project @[owner]/[project] ([https://expo.dev/accounts/[owner]/projects/[project])](https://expo.dev/accounts/[owner]/projects/[project]))
- Building bundle...
✔ Built bundle!
- Uploading assets...
✖ Failed to upload assets
    JsonFileError: Can't read JSON file:
    /home/runner/work/[github-project-name]/[github-project-name]/dist/metadata.json
    ├─ File: /home/runner/work/[github-project-name]/[github-project-name]/dist/metadata.json
    └─ Cause: Error: ENOENT: no such file or directory, open
    '/home/runner/work/[github-project-name]/[github-project-name]/dist/metadata.json'
    Code: ENOENT
Error: Process completed with exit code 1.

Is this something we're doing wrong? I wasn't sure why the path would have 2 instances of the github project name but maybe that's a red herring?
Thanks for your help!
Managed or bare?
Managed
Environment
System:
OS: macOS 12.1
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
Yarn: 1.22.5 - ~/.yarn/bin/yarn
npm: 8.1.2 - ~/.nvm/versions/node/v16.13.2/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/lib/ruby/gems/3.0.0/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 15.0, DriverKit 20.4, macOS 11.3, tvOS 15.0, watchOS 8.0
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7784292
Xcode: 13.0/13A233 - /usr/bin/xcodebuild
npmPackages:
expo: ~44.0.0 => 44.0.6
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
npmGlobalPackages:
eas-cli: 0.47.0
expo-cli: 5.2.0
Expo Workflow: managed
Error output
JsonFileError: Can't read JSON file:
/home/runner/work/[github-project-name]/[github-project-name]/dist/metadata.json
├─ File: /home/runner/work/[github-project-name]/[github-project-name]/dist/metadata.json
└─ Cause: Error: ENOENT: no such file or directory, open
'/home/runner/work/[github-project-name]/[github-project-name]/dist/metadata.json'
Reproducible demo or steps to reproduce from a blank project
Happy to share anything else required to track down the cause?

Facing the same issue, did you fix it?

Is this something we're doing wrong? I wasn't sure why the path would have 2 instances of the github project name but maybe that's a red herring?

I was wondering the same thing based on my stack trace.

Thanks for reporting this. I am working on setting up a monorepo so that we can reproduce this and fix the issue in EAS CLI.

Awesome, thanks @jonsamp. The solito starter monorepo might help: solito.dev/starter

I am attempting to make a reproduction of this issue so that we can get to the bottom of it. I made this repo: https://github.com/jonsamp/my-solito-app
That repo is a monorepo with an expo app + a github action. The only modified part of the github action from the template in the docs is this line to specify the working-directory.
If anyone can clone that repo and suggest what I might do to reproduce this issue, let me know. I'll continue investigating.

eas update --skip-bundle
How do you get the metadata.json ?

I'm also experiencing this issue. It's not a monorepo.
When I set EXPO_DEBUG=1 then I get JavaScript heap out of memory.

Run eas update --branch demo --message "Testing"
- Linking to project @[owner]/[project]
✔ Linked to project @[owner]/[project] (https://expo.dev/accounts/[owner]/projects/[project])
- Building bundle...
[expo-cli] - Making sure project is set up correctly...
- Building bundle...
[expo-cli]
- Building bundle...
[expo-cli] [07:44:12] Export Assets:
- Building bundle...
[expo-cli] [07:44:12] - Asset target: managed
- Building bundle...
[expo-cli] Expo Metro config:
- Building bundle...
[expo-cli] - Bundler target: bare
- Building bundle...
[expo-cli] - Legacy: false
- Building bundle...
[expo-cli] - Extensions: ts, tsx, js, jsx, json
- Building bundle...
[expo-cli] - React Native: /home/runner/work/[github-project-name]/[github-project-name]/node_modules/react-native
- Building bundle...
[expo-cli] - Babel config: /home/runner/work/[github-project-name]/[github-project-name]/babel.config.js
- Building bundle...
[expo-cli] - Resolver Fields: react-native, browser, main
- Building bundle...
[expo-cli] - Exotic: false
- Building bundle...
[expo-cli]
- Building bundle...
[expo-cli] Expo Metro config:
- Building bundle...
[expo-cli] - Bundler target: bare
- Building bundle...
[expo-cli] - Legacy: false
- Building bundle...
[expo-cli] - Extensions: ts, tsx, js, jsx, json
- Building bundle...
[expo-cli] - React Native: /home/runner/work/[github-project-name]/[github-project-name]/node_modules/react-native
- Building bundle...
[expo-cli] - Babel config: /home/runner/work/[github-project-name]/[github-project-name]/babel.config.js
- Building bundle...
[expo-cli] - Resolver Fields: react-native, browser, main
- Building bundle...
[expo-cli] - Exotic: false
- Building bundle...
[expo-cli] [07:44:13] Starting Metro Bundler
- Building bundle...
[expo-cli] <--- Last few GCs --->
- Building bundle...
[expo-cli]
- Building bundle...
[expo-cli] [1893:0x4c749b0]   666395 ms: Mark-sweep 2003.2 (2081.4) -> 1987.6 (2082.4) MB, 3431.8 / 0.1 ms  (average mu = 0.205, current mu = 0.159) allocation failure scavenge might not succeed
- Building bundle...
[expo-cli] [1893:0x4c749b0]   670280 ms: Mark-sweep 2004.4 (2083.2) -> 1989.1 (2084.4) MB, 3667.3 / 0.0 ms  (average mu = 0.136, current mu = 0.056) allocation failure scavenge might not succeed
- Building bundle...
[expo-cli]
- Building bundle...
[expo-cli]
- Building bundle...
[expo-cli] <--- JS stacktrace --->
- Building bundle...
[expo-cli]
- Building bundle...
[expo-cli] FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
- Building bundle...
[expo-cli] 1: 0xb09980 node::Abort() [node]
- Building bundle...
[expo-cli] 2: 0xa1c235 node::FatalError(char const*, char const*) [node]
- Building bundle...
[expo-cli] 3: 0xcf784e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
- Building bundle...
[expo-cli] 4: 0xcf7bc7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
- Building bundle...
[expo-cli] 5: 0xeaf465  [node]
- Building bundle...
[expo-cli] 6: 0xeaff46  [node]
- Building bundle...
[expo-cli] 7: 0xebe46e  [node]
- Building bundle...
[expo-cli] 8: 0xebeeb0 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
- Building bundle...
[expo-cli] 9: 0xec1e2e v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
- Building bundle...
[expo-cli] 10: 0xe8336a v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
- Building bundle...
[expo-cli] 11: 0x11fc0b6 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
- Building bundle...
[expo-cli] 12: 0x15f0b19  [node]
- Building bundle...
✔ Built bundle!
- Uploading assets...
✖ Failed to upload assets
    JsonFileError: Can't read JSON file:
    /home/runner/work/[github-project-name]/[github-project-name]/dist/metadata.json
    ├─ File:
    /home/runner/work/[github-project-name]/[github-project-name]/dist/metadata.json
    └─ Cause: Error: ENOENT: no such file or directory, open
    '/home/runner/work/[github-project-name]/[github-project-name]/dist/metadata.json'
    Code: ENOENT

@GregAtFramework A workaround is to add a NODE_OPTIONS=--max_old_space_size=4096 env var before running the EAS CLI command.
We are still trying to find a good reproduction example so that we can fix this issue, if you have or know of one.

Hi, just stumbled this issue with Github Actions. @jonsamp does that work for github actions?

@teovillanueva Yes, it did work for me. You can set it like this :
- run: 'eas update --branch demo --message "Testing"'
  env:
    NODE_OPTIONS: "--max-old-space-size=8192"
    EXPO_DEBUG: 1

It worked 👍

Posting here in case someone is facing the same problem.
We rely on CircleCI to run the eas update. We had the same problem of out of memory error.
We tried the above mentioned fixes, with no luck.
We changed the metro config to limit the number of workers to 2. And it fixed the thing.
Actually, metro roughly defaults to os.cpu() / 2 for maxWorkers. So in a 8 cores CircleCI instance it would be maxWorkers === 4. Unfortunately it too much and causes memory issues.
Setting maxWorkers: 2 in the metro config solved our issue.
Metro maxWorkers doc: https://facebook.github.io/metro/docs/configuration/#maxworkers
Hope this helps 🤷

Based on comment above, I changed maxWorkers to 2 in Expo Metro config and it worked.
// metro.config.js
const { getDefaultConfig } = require('expo/metro-config')

const config = getDefaultConfig(__dirname)
config.maxWorkers = 2

module.exports = config

Hi guys, I've encountered this issue as well, I'm using solito monorepo.
got this output below, it seems the folder name repeated, any ideas how to fix this?
[expo-cli] - React Native: /home/runner/work/www-monorepo/www-monorepo/apps/patients-expo/node_modules/react-native
- Exporting...
[expo-cli] - Babel config: /home/runner/work/www-monorepo/www-monorepo/apps/patients-expo/babel.config.js
- Exporting...
[expo-cli] - Resolver Fields: react-native, browser, main
- Exporting...
[expo-cli] - Watch Folders: /home/runner/work/www-monorepo/www-monorepo/node_modules, /home/runner/work/www-monorepo/www-monorepo/apps/patients-expo, /home/runner/work/www-monorepo/www-monorepo/apps/patients-next, /home/runner/work/www-monorepo/www-monorepo/packages/app
- Exporting...
[expo-cli] - Node Module Paths: /home/runner/work/www-monorepo/www-monorepo/apps/patients-expo, /home/runner/work/www-monorepo/www-monorepo/node_modules

It seems like there's a workaround for this issue, which is shown above. I am going to close this issue for now. Please reach out if you continue to see issues.

in app.json this fails
...
"web": {
      "bundler": "metro",
      "output": "static",
      "favicon": "./assets/favicon.png"
    },

This works wit eas updtate :
    "web": {
      "favicon": "./assets/favicon.png"
    },

in app.json this fails
...
"web": {
      "bundler": "metro",
      "output": "static",
      "favicon": "./assets/favicon.png"
    },

This works wit eas updtate :
    "web": {
      "favicon": "./assets/favicon.png"
    },

can confirm this works, unfortunately though then local web development breaks.


Init config file TECHOPS-52

Current coverage is 52.95% (diff: 75.00%)

Merging #144 into master will decrease coverage by 0.04%

@@             master       #144   diff @@
==========================================
  Files            99         99
  Lines          4992       5004    +12
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           2646       2650     +4
- Misses         2109       2115     +6
- Partials        237        239     +2

Powered by Codecov. Last update 2975ae0...4ba33bb


WIP: support DRF3

@antetna i did it to see changes :-)

CI failed, setup.py has < 3.0 i did a PR https://github.com/antetna/django-rest-auth/pull/1

Coverage decreased (-1.07%) when pulling cc6919ab2a463401c43793708777261c1e8a92f1 on antetna:master into 802de89ed7e2be2be0528e734ffe2c2b1c0d4a6a on Tivix:master.

Coverage decreased (-1.07%) when pulling cc6919ab2a463401c43793708777261c1e8a92f1 on antetna:master into 802de89ed7e2be2be0528e734ffe2c2b1c0d4a6a on Tivix:master.

Not ideal since django-allauth 0.19 breaks the code but at least 0.18 works

Facebook is not responding in socialauth,must be updated this ?

@ovnicraft : you tried Facbook auth and it doesn't work for you ? I didn't test it on my side because I do not need FB atm. if it's broken than tests for it should be changed too ...

@antetna works perfect now

@ovnicraft: I just checked django-allauth 0.19 and it should work with it ? Could you check it ?
There has been change in API URL from 0.18 >> 0.19
https://graph.facebook.com/me  >> https://graph.facebook.com/v2.2/me
2 tests needs to be recaftored in order to pass because tests are still using old URL: 'https://graph.facebook.com/v2.2/me'

@antetna i see the log in travis and socialaccount get this:
ConnectionError: Connection refused: https://graph.facebook.com/v2.2/me?access_token=abc123
I see https://travis-ci.org/Tivix/django-rest-auth/jobs/46352902#L469 its updated.


Update Battle Box music

Nice music! But can u start the music at 1:24?
https://www.youtube.com/watch?v=vRyZGz4hWfo

Updated in 1.4.1


Design team settings pages

Dupe of: https://github.com/orgs/sourcegraph/projects/376/views/17?filterQuery=-status%3A"✅+Done"+team+settings&pane=issue&itemId=55842670


More ways to make coal coke.

There should either be a way to convert the various types of coal into vanilla coal or a way to cook the other coal types into coke.

Anthracite to 2 coal coke. Is this what you had in mind?

Alright, anthracite makes 2 coal coke. Bituminous coal no longer spawns (I may make a bituminous coal coke at some point and re-enable it). Vanilla coal can make coke, and lignite can be upgraded to vanilla coal via the basic coal refiner. The only fuel you can find in the world added by this mod that you cannot make into coke is peat.


NetTruyen domain changed

Please help us to fix link. New link is: https://nettruyenviet.com/
Thank you.


Use qa2 API endpoint for v4 schema testing

closes
Prerequisites:

[ ] Unless it is a hotfix it should be merged against the dev branch
[ ] Branch is up-to-date with the branch to be merged with, i.e. dev
[ ] Build is successful
[ ] Code is cleaned up and formatted

Summary
Update the Netlify preview environment to use the qa2 API test endoint.

@krivard @sgratzl I'm not sure if this is the correct place for the change. The goal is to make one of the Netlify previews (staging?) use our qa2 testing environment for API calls.

This is simpler than what I had in mind, but it will probably work, so long as we remember not to merge it.
The expected workflow was:

PR main -> staging and merge
branch from staging and set context.staging.environment:COVIDCAST_ENDPOINT_URL
PR branch -> staging and merge
View at https://staging--cmu-delphi-covidcast.netlify.app/ indefinitely

but yeah looks like opening a PR that changes context.deploy-preview.environment:COVIDCAST_ENDPOINT_URL just...shortcuts the whole thing 💪

As best I can tell the Netflify preview for this build is broken so this PR is not useful. Closing it!


Cheaper queue state

This PR aims to reduce the number of QueueState calculations to see if we can improve the flamegraph of where code time is spent.
This splits QueueState into two halves, QueueState/QueueSnapshot and
the snapshot is used on the PacketizingBuffer level and QueueState on
the MediaInner level.  This is to avoid needing all knowledge about
what kind of data we're handling inside the PacketizingBuffer.
The more important change is adding an internal TotalQueue struct in
PacketizingBuffer that continuously keeps track of the total queue
duration in the buffer. This way we can avoid an expensive
recalculation on every MediaInner::queue_state() call.

Also, I added MediaKind in the pacer because there is some code in libWebRTC that prioritises retransmits over video, but I hadn't decide if we wanted to port that. The vision was to have MediaKind::Retransmission in addition to MediaKind::Audio and MediaKind::Video`

Also, I added MediaKind in the pacer because there is some code in libWebRTC that prioritises retransmits over video, but I hadn't decide if we wanted to port that. The vision was to have MediaKind::Retransmission in addition to MediaKind::Audio and MediaKind::Video

That's still fine though. Since we have QueueState(QueueSnapshot) and what type of queue lies on the outer QueueState, we can introduce whatever flags we want there without requiring that for the snapshots/packetizing buffers.
I also think that rather than making Pacer hard bound to media, we could abstract it to just a prio field (high, normal, low) or something.

I also think that rather than making Pacer hard bound to media, we could abstract it to just a prio field (high, normal, low) or something.

Sounds good


[TF 2.0.0-rc0] Keras layer dependency tracking behaviour changed in 2.0.0-rc0

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS, Linux Ubuntu 16.04
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.0.0-rc0
Python version: Python 3.6/3.7

We are developing an open source library for training binarized and other extremely quantized networks at http://larq.dev that heavily relies on tf.keras. For this we are adding custom layers that modify (i.e. quantize) the layers kernel (and activations) prior to the computation.
Expected Behaviour
A simplified version of what we are doing is here:
from tensorflow import keras

# For our use case this would be a quantizer with a custom gradient
def projection(x):
    return 2 * x

class CustomDense(keras.layers.Dense):
    def call(self, inputs):
        original_kernel = self.kernel
        self.kernel = projection(self.kernel)
        outputs = super().call(inputs)
        self.kernel = original_kernel  # reset the original kernel to make this work in eager mode
        return outputs

model = keras.models.Sequential([CustomDense(32, input_shape=(32,))])

assert model.layers[0].kernel in model.layers[0].trainable_weights

This worked well for TensorFlow 1.13, 1.14 in graph and eager as well as for 2.0.0-beta0 and 2.0.0-beta1.
Current Behaviour
It looks like TensorFlow 2.0.0-rc0 changed the automatic dependency tracking which makes the above code fail on the last line. The same is true for 2.0.0.dev20190904:
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-1-e416b6b97b33> in <module>
     40 model = keras.models.Sequential([CustomDense(32, input_shape=(32,))])
     41
---> 42 assert model.layers[0].kernel in model.layers[0].trainable_weights

~/miniconda3/envs/tf2/lib/python3.7/site-packages/tensorflow_core/python/framework/ops.py in __bool__(self)
    874
    875   def __bool__(self):
--> 876     return bool(self._numpy())
    877
    878   __nonzero__ = __bool__

ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

Ignoring the automatic dependency tracking by using the following makes the above code work.
from tensorflow import keras
from tensorflow.python.training.tracking.base import (
         no_automatic_dependency_tracking_scope,
     )

def projection(x):
    return 2 * x

class CustomDense(keras.layers.Dense):
    def call(self, inputs):
        original_kernel = self.kernel
        with no_automatic_dependency_tracking_scope(self):
            self.kernel = projection(self.kernel)
        outputs = super().call(inputs)
        with no_automatic_dependency_tracking_scope(self):
            self.kernel = original_kernel
        return outputs

model = keras.models.Sequential([CustomDense(32, input_shape=(32,))])

assert model.layers[0].kernel in model.layers[0].trainable_weights

Questions
Is this behaviour change expected or is it a bug in 2.0.0-rc0?
Is there a better way to achieve this, without needing to temporarily overwrite layer.kernel?
If this change is expected, is it save to use the private no_automatic_dependency_tracking_scope to workaround this issue?
@dynamicwebpaige Is this issue better posted at the TensorFlow 2.0 testing mailing list?

@lgeiger: Thanks for the bug report. Recently we changed the behavior of equality in 2.0 such that Variables & Tensors are no longer hashable. As an unfortunate side-effect model.layers[0].kernel in model.layers[0].trainable_weights does not work as you probably intended since it is trying to do an element-wise equality comparison of model.layers[0].kernel with each of the trainable weights. Instead, please try changing your code to any(model.layers[0].kernel is w for w in model.layers[0].trainable_weights)
We'd received a couple of reports with people running into obscure errors with this change and will look into improving the communication of this change.

@jaingaurav Thanks for the info, I agree more documentation about this change would help.
Do you know why the comparison when ignoring the dependency tracking with no_automatic_dependency_tracking_scope works? Following your argument, I intuitively would expect it to fail as well.


Errors when using disjoint unions and utility type $NonMaybeType

I get unexpected errors (string literal is incompatible with string literal) when attempting to refine a disjoint union that was derived using $NonMaybeType. Full reproduction of issue.
Sample Code
type A = {
  __typename: 'A',
};

type B = {
  __typename: 'B',
  info: Array<string>,
};

type Example = A | B;

// Simulating query results from apollo-codegen
type ExampleQueryResult = {|
  result: ?Example,
|};

// Pull the result type out from the Query definition
type DerivedExampleType = $NonMaybeType<
  $PropertyType<ExampleQueryResult, 'result'>
>;

// NOTE: When I attempt to "pull out" or "derive" the result type from it's parent, autogenerated type, I get errors that I do not get for the below example, even though the code is the same.
const whyDoesntThisWork = (result: DerivedExampleType) => {
  if (result.__typename !== 'B') {
    console.log('test');
  }
};

// NOTE: This works when I isolate the Example type itself, not using the utility types ($NonMaybeType or $PropertyType)
const thisWorks = (result: Example) => {
  if (result.__typename !== 'B') {
    console.log('test');
  }
};

Expected:
Using the DerivedExampleType and the ExampleType would act the same.
Actual:
Using DerivedExampleType results in cryptic errors like  string literal A [1] is incompatible with string literal B [2] in property __typename, whereas using Example results in no errors.
Removing the $NonMaybeType and making the ExampleQueryResult.result Example instead of ?Example fixes the issue (no errors reported). However, I am relying on auto-generated types based on a graphql schema (using apollo-codegen) and cannot make that change.

I also had same issue when I've worked with gql types. It's stopping working when I use it with $NonMaybeType & $ElementType.
Here is my minimal example:
type Union1Type = {type: 'a', a: string} | {type: 'b', b: number}; // ok
type aType = {union: Union1Type};
type Union2Type = $ElementType<aType, 'union'>; // ok
type Union3Type = $NonMaybeType<$ElementType<aType, 'union'>>; // fail
type Union4Type = $NonMaybeType<Union1Type>; // ok

const fnc = (union: Union4Type): string => {
  if (!union) {
    return 'x';
  }

  if (union.type === 'a') {
    return union.a;
  }

  if (union.type === 'b') {
    return union.b.toString();
  }

  return 'z';
};

This now works


missing semicolon in manual

Submisison Checklist

[ ] Run unit tests: ./runTests.py src/test/unit
[ ] Run cpplint: make cpplint

Not needed because this is just a doc change?

[x] Declare copyright holder and open-source license: see below

Summary
Typo fix.
Intended Effect
Make example code from manual compile.
How to Verify
I was trying the example from the manual and editing the Stan file in RStudio which checks the syntax whenever I save. Here's before the edit.
rstan:::rstudio_stanc("center-param.stan")
#> SYNTAX ERROR, MESSAGE(S) FROM PARSER:
#>
#>
#>   ERROR at line 33
#>
#> 31:        for (n in 1:N)
#>   32:          x_beta_jj[n] = x[n] * beta[jj[n]]
#> 33:        y ~ normal(x_beta_jj, sigma);
#> ^
#>   34:      }
#>
#> PARSER EXPECTED: ";"
#> Error in stanc(model_code = paste(program, collapse = "\n"), model_name = model_cppname,  :
#>   failed to parse Stan model 'center-param' due to the above error.

Here's after.
rstan:::rstudio_stanc("center-param.stan")
#> center-param.stan is syntactically correct.

Side Effects
Documentation
Reviewer Suggestions
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company): Tristan Mahr
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

@tjmahr  Thanks for the pull request.  It may be easier in the future to just report the typos to us in the issue open for typos on the manual.  I make a pass before each release and fix all the reported errors.  The problem with all these little pull requests is that we now have a heavy review and integration testing process in place.  The current "next manual" issue is https://github.com/stan-dev/stan/issues/2265
@seantalts  What do we want to do with these one-character pull requests?  Is there some way not to do a compute day's worth of integration testing for manual-only changes?
@seantalts  Although this is off issue, should we think about moving the manual to a new repo to solve this ongoing problem?  I hate to discourage pull requests, but then I also hate the idea that this kicks off a compute day's worth of integration testing and ties up our servers and those we get from Travis.

Oops, I didn't know about the updates-to-manual issue :sweat_smile:

@tjmahr Don't worry! We appreciate it a lot and we'll figure something out.
@bob-carpenter Do you have an existing manual-edits branch somewhere? If so, I would just pull @tjmahr's commits from his branch into that one:
git checkout manual-edits-2.16.0
git pull git@github.com:tjmahr/stan.git patch-1
# optional: see what commits are now in your branch that aren't in origin/develop.
git log origin/develop..manual-edits-2.16.0 #just commit messages, or
git log --stat origin/develop..manual-edits-2.16.0 #with files changed, or
git log -p origin/develop..manual-edits-2.16.0 # with actual code diffs as well

I like pulling his commit because it keeps his commit message and author tag, vs us just applying the diff manually.
Let me know if you get stuck or I can help you through it; feel free to call my cell.
RE: Should we move the manual to a new repo? - I typically like fewer repos in general, but here I'm a bit ambivalent since it isn't really code. I'd say for now we do the above and I can look around and see if there's a way to only test when certain directories change.

Now there's a solution---I usually just do it all at once, but no
reason I can't create the matching branch at the same time.
The branch on stan-dev/stan is feature/2265-manual-2.16:

https://github.com/stan-dev/stan/issues/2265

I tried typing what you sent as a command, but it didn't work.
~/cmdstan/stan(feature/2265-manual-2.16)$ git pull git@github.com:tjmahr/stan.git patch-1
The authenticity of host 'github.com (<IP_ADDRESS>)' can't be established.
RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
Are you sure you want to continue connecting (yes/no)? y
Please type 'yes' or 'no': yes
Warning: Permanently added 'github.com,<IP_ADDRESS>' (RSA) to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Woops, missed this notification, sorry. It seems like you haven't set up SSH keys with github? If you want to do that, you can see how here: https://help.github.com/articles/connecting-to-github-with-ssh/
But if you want to keep using https you can change all of those<EMAIL_ADDRESS>urls to https://github.com/` like so:
git pull https://github.com/tjmahr/stan.git patch-1


Consider supporting vanilla web component

First, thank you for starting this project.
I was thinking about how to build a web component web pack loader for a while.
Sure, I like Polymer and I already have done one project with it, but now I want to start a project with Vanilla Web Components.
I have tested the code below with the polymer-webpack-loader, and I think it's enough for Vanilla Web Components.
Here's a short code I started.
<link rel="import" href="./your-element.html">

<template id='my-element'>

Hello, World! It's today.

  <your-element></your-element>
</template>

The problem is that the above code can not get the template used in MyElement's constructor.
Transforming the above code will cause the template to be executed on the DOMContentLoaded event by RegisterHtmlTemplate.toBody, but the JavaScript inside the script will be executed immediately.
Of course, if you defer attribute on a transfiled script file, you can use it without problems, but if possible, I think polymer-webpack-loader should solve it.
I wonder if you guys are going to support the vanilla web component. If I so, I would be happy to send PR.

This is already supported. You just need to ensure that your bundle script include in your index.html file is included  in such a way that document.body exists when it executes. You can use the defer attribute as you mentioned, or place the script in the body.
How you do this is highly dependent on what techniques you use for your index.html file. You can see an example in the demo.

Thanks for the quick answer @ChadKillingsworth
Yes, I can use it like the example code you gave, put bundle script when the body exists, or add the defer attribute. But if the script is in the head, that's a problem.
If you look at the code, you are already processing the html element depending on whether the body exists or not. I think that the condition should be applied to the script as well. Then the bundled script will be fine wherever it is.
And the example code you gave is loading the script on the Web Components Ready event webcomponents-loader fires. It may be necessary today, but I think you need to consider the condition that no webcomponents-loader. It is just polyfill right? The polymer-webpack-loader should work regardless of the presence of the webcomponents-loader.
good day :)

The loader isn't designed to process the main html document (there are other loaders and plugins for that). Neither does the loader have any knowledge of how the bundle is included in the index.html page.
What you are asking for is reasonable, but it is beyond the scope of this project.

Hello @ChadKillingsworth
Maybe you misunderstood what I said.
polymer-webpack-loader do not need to understand index.html at all.
What I'm talking about is that the module scripts should be run after the corresponding template is registered via the register-html-template.
register-html-template L41-L47
I wrote a little bit of dirty code to check the ideas
index.js L195
source += `const exec = () => {
  ${scriptContents}
};
if (!document.body) {
  document.addEventListener('DOMContentLoaded', exec);
} else {
  exec();
}`;

I think the exec function should be out like register-html-template.js
Of course, I haven't care about TC, sourcemap, and so on ...
I would like to send a PR but I am hesitant because there seems to be a few things to be decided prior to implementation.
Tell me your thoughts.

I didn't suggest that option because it changes script semantics in breaking ways outside of developer control. For instance, the webpack shimming mechanisms wouldn't properly work, scoping and the this keyword are impacted and the script no longer synchronously executes.
While I realize you want this to be an automatic process for your use case, it's beyond the scope of this loader.

yea agree.
BTW. I'm still trying to apply a polymer-webpack-loader to a vanilla web component.
When I insert a script as a reference, I have another problem.
This is because the code that uses templates in javascript will always run before adding templates to the DOM, as transfiled as in the code below.
As you said If this loader also supports the web component, I think the execution order of the script and template should be managed.
// TRANSLATED
// CONCATENATED MODULE: ./src/my-element.html
/* harmony import */ var __WEBPACK_IMPORTED_MODULE_0__my_element_js__ = __webpack_require__(2);
/* harmony import */ var __WEBPACK_IMPORTED_MODULE_0__my_element_js___default = __webpack_require__.n(__WEBPACK_IMPORTED_MODULE_0__my_element_js__);

const RegisterHtmlTemplate = __webpack_require__(1);
RegisterHtmlTemplate.toBody('<template id="my-element">
template
 </template> ');

<link rel="import" href="./your-element.html">

<template id='my-element'>

template

</template>

// my-element.js
  class MyElement extends HTMLElement {
    constructor() {
      super();

      const shadowRoot = this.attachShadow({mode: 'open'});
      const template = document.querySelector('#my-element');
      shadowRoot.appendChild(template.content.cloneNode(true));
    }
  }

  window.customElements.define('my-element', MyElement);


Autofocus on didRender

Currently, input autofocus only occurs on the DOM ready event.
Adding something like the following to validated-form would ensure every time the form is rendered, autofocus is respected.
didRender() {
  this._super(...arguments);
  this.focusOnRender();
},

focusOnRender() {
  let $focusInput = this.$().find('[autofocus]');
  if ($focusInput.length) { $focusInput.focus(); }
}

Can submit a PR. Also happy to implement in vanilla JS code to comply with future PR https://github.com/emberjs/rfcs/pull/294.

One issue of autofocus is that once the user changes focus without changing anything, think of a modal with a form and the user wants to close it, the form validation will be triggered because focusOut triggers setDirty.
I'm unsure if we can make focusOut more clever to don't dirty if nothing changes.


Add comma arrayFormat

This pull requests adds fourth arrayFormat option, named comma. We needed this for our project, as we needed to support arrays in query in below shape...
foo=1,2,3,4,5,6,7,8
This format is mainly used to shorten URLs which include things as identifiers, where there is expected to be a lot of them.
On the way to add this feature I had to slightly reimplement encoderForArrayFormat to use Array.prototype.reduce instead of previous for .. in

Great work @zepod !
Fix tests please I really want to use it on my project 🥇

Why did you have to switch to Array#reduce?

You have to include TypeScript types for the changes too, since a TypeScript declaration file was recently added to master.

@sindresorhus
the way it was implemented with for encoderForArrayFormat was a unary function mapping single element of provided array, to single key in the query sequence.
Using comma format, we wanted to map the multiple elements of array to a single key in the query.

Typescript types added

Looks good. Thank you :)


Update README.md

few typo

https://github.com/ethereum/remix/issues/846

@yann300 will you please review it ?

we also have some *.md in https://github.com/ethereum/remix-ide . would be great if you like to give a check on those.
thanks for the PR


Fix a compilation warning in command.c relating to kpos shadowing

When building with the gcc -Wshadow option, a warning is generated in redis_parse_cmd() because the second and third declarations of the same-named kpos variable share scope.  It's benign but it'd be great to have clean compilation when using this option.

@zuiderkwast that's an excellent idea IMO.


Update README.md

To include what was suggested in https://github.com/mhanberg/gigalixir-action/pull/23#issuecomment-779473187

Thanks!!


Missing Documentation per OSC Governance

The following Required docs are missing and should show on the Main page of Code: CODEOWNERS, CHANGELOG.md
If there are CHANGELOG's please create a top level file and link accordingly.
The following documents/features are suggested by OSC Governance: SECURITY.md
For Reference: https://intersect.gitbook.io/open-source-committee/policies/governance
Also see Documentation and Legal

Please provide an Update. Thank you.

Fix ready, Docs added, via #1125


Logo should use transparency

I guess we changed the shade of the branding sometime in the last year, and the logo boarder looks off now. Should change the dark blue color as transparent.

I should have the original SVG or *.cxf project file somewhere, but don't have access to it right now. Here's the higher quality version from a PR that should edit fine.

Found the SVG itself:

Just need to remove the dark blue for a transparent background, and re-export it as a 178 by 40 px png.

We could keep it as SVG too


What library should we use to send commands from an Angular 11 app?

Hello, I am not able to use this library as well with Angular app, I get the following error:
./node_modules/canvas/build/Release/canvas.node:1:0 - Error: Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Ok, this https://stackoverflow.com/a/60960414/5224768 fixed my issue :) :)


Exclude implausible intentions with full-text 'q' only and few matching features

This is an attempt to reduce false positives caused by queries wrongly tagged as "brand" by the tagger.
By comparing the query with the features name, it's possible to evaluate if the current query does effectively match multiple features among the results provided by the geocoder. A real brand name will typically match dozens of POIs.
This filter is not applied if the intention contains both a query and a geocoded place. False positives are less likely in this case.

A feature flag is now defined. And a missing fixture has been committed.


[Feature]: Owner guard

Feature?
It'd be nice to have some guard for easily restricting commands/modules to only be usable for bot owners, something that perhaps makes use of client.application.owner (taking into account Teams) or even some generic @Guard(IsUser(id)) to limit it to some specific user(s).
Package
@discordx/utilities

@ravener could you make PR instead?

you want a guard to only allow bot owners/user ids? ok, i can do this

@ravener use @PermissionGuard guard, allow only administrator to access the commaand.

See permissions at https://discord.com/developers/docs/topics/permissions#permissions-bitwise-permission-flags there are permissions like manage guild and administrator useful.

you could do
@Guard(
  NotBot,
  IsGuildUser(({ guild, user }) => {
    if (!guild || !user) {
      return false;
    }

    const member = guild.members.cache.get(user.id);
    if (!member) {
      return false;
    }

    return member.permissions.has(PermissionsBitField.Flags.Administrator);
  }),
)

or
@Guard(
  NotBot,
  IsGuildUser(({ user }) => {
    if (!user) {
      return false;
    }

    return user.id === "ADMIN_USER_ID";
  }),
)

As you wanted to check client application owner, this will be useful.
@Guard(
  IsGuildUser(({ client, user }) => {
    if (!user) {
      return false;
    }

    return client.application?.owner?.id === user.id;
  }),
)

Even better this way,
import { IsGuardUserCallback, IsGuildUser } from "@discordx/utilities";
import { Events } from "discord.js";
import {
  ArgsOf,
  Discord,
  Guard,
  On,
  SimpleCommand,
  SimpleCommandMessage,
} from "discordx";

const OwnerOnly: IsGuardUserCallback = ({ client, user }) => {
  if (!user) {
    return false;
  }

  return client.application?.owner?.id === user.id;
};

@Discord()
@Guard(IsGuildUser(OwnerOnly))
class Example {
  @On({ event: Events.MessageCreate })
  message([message]: ArgsOf<"messageCreate">) {
    //...
  }

  @SimpleCommand({ name: "hello" })
  hello(command: SimpleCommandMessage) {
    //...
  }
}


Update README.md

I edited the Platform table and marked the FCs that are currently available only under 64-bit environment.

Click4 actually works under 32-bit Windows.

Besides, I only see a 64-bit binary for Linux.

@StinkerB06 that does not mean it does not run on 32 bit linux.

Barely important information; doesn't make sense for browser, mobile, console based ones.


No way to lock iPad orientation to landscape via config.xml

Hi!
I can make none of the ways work that are described here http://docs.build.phonegap.com/en_US/2.9.0/configuring_config_file_element.md.html
I am on version 3.5.0-0.21.14 of phonegap installed via npm.
To reproduce:
npm install -g phonegap
phonegap create orientation-test

1. edit config.xml
<preference name="orientation" value="landscape" />
phonegap build ios
open platforms/ios/HelloWorld/HelloWorld-Info.plist to check that the setting had no effect
2. edit config.xml to contain
<gap:config-file platform="ios" parent="UISupportedInterfaceOrientations" overwrite="true">
        <array>
            <string>UIInterfaceOrientationLandscapeLeft</string>
            <string>UIInterfaceOrientationLandscapeRight</string>
        </array>
</gap:config-file>
<gap:config-file platform="ios" parent="UISupportedInterfaceOrientations~ipad" overwrite="true">
        <array>
            <string>UIInterfaceOrientationLandscapeLeft</string>
            <string>UIInterfaceOrientationLandscapeRight</string>
        </array>
</gap:config-file>

phonegap build ios
open platforms/ios/HelloWorld/HelloWorld-Info.plist to check that the setting had no effect
Is this a bug or is some information missing from the documentation? I can find no information anywhere online to make this work without editing the pList file directly. Yet, I would rather avoid this to not having to manage multiple configuration files and being able to keep up to date with phonegap.
Thanks
Marten

Same issue here

Same issue!
devacc at macmini in ~
$ cordova -v
4.3.0

devacc at macmini in ~
$ phonegap -v
4.2.0-0.24.2

devacc at macmini in ~
$ node -v
v0.12.0

devacc at macmini in ~
$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.10.2
BuildVersion:	14C1510

Still the same issue, and I don't have the option to set things manually in the plist, since its generated on build in my setup.

Still the same issue, incredibly annoying for Phonegap Build users.

+1

+1.

+2

3 Same issue here.

+4 same issue. iOS 8.4, phonegap 5.1.1

+5 same issue. iOs 8.3, cordova 5.0.0

+6 Cordova 5.1.1

+7

+8

+9

+10

+11

Guys, for those of you still having the issue, I just wrote a simple grunt task to update the plist file and removing the portrait.
    grunt.registerTask('updateiOSPlistLandscapeOnly', function () {
        var plist = require('plist'),
            appName = 'Your Super App',
            plistFilepath = path.resolve() + '/' + 'platforms/ios/' + appName + '/' + appName + '-Info.plist',
            plistJson = plist.parseFileSync(plistFilepath);

            plistJson['UISupportedInterfaceOrientations~ipad'].forEach(function(value, index){
                if (value && value.indexOf('Portrait') > -1){
                    plistJson['UISupportedInterfaceOrientations~ipad'].splice(index, 1);
                }
            });
            var plistObj = plist.build(plistJson);
            grunt.verbose.writeln('****Updating plist: removing portrait****');
            grunt.file.write(plistFilepath, plistObj);
    });

And depending on your build management, either add it to your build workflow (grunt, gulp) either you can it to the hooks.
For the last one, within your before_build hooks directory (create it if you don't have it yet), you can just add the following code in a new file (010_remove_portrait.js for example).
#!/usr/bin/env node

var exec = require('child_process').exec;
if (process.env.CORDOVA_CMDLINE.indexOf('ios') > -
    function puts(error, stdout, stderr) {
        console.log(stdout)
    }
    exec("grunt updateiOSPlistLandscapeOnly", puts);

An easier and cleaner solution would be to write the code directly within the hooks nodejs script.
But as my build was using grunt already with a lot of other tasks, I just went with it.

@ygayl Thanks but this won't help those who use PhoneGap Build online. So we really need that bug fixed.

The issue with IOS 9.0 iPhone devices also, I am using the following lang version
Cordova : 5.3.3
Phonegap : 5.2.0
config.xml :
I have tried cordova-plugin-screen-orientation, it didnt help :+1:
iPhone 6 plus : IOS ( 9.0.2) not working
Any help?

+12

+13

+14 This is a very annoying bug.

I cannot reproduce this with the latest phonegap-cli.
I created a project, added <preference name="Orientation" value="landscape" /> to my config.xml, ran phonegap build ios, and I see this under platforms/ios/HelloWorld/HelloWorld-Info.plist:
➔ ack -i orientation platforms/ios/HelloWorld/HelloWorld-Info.plist
    <key>UISupportedInterfaceOrientations</key>
      <string>UIInterfaceOrientationLandscapeLeft</string>
      <string>UIInterfaceOrientationLandscapeRight</string>
    <key>UISupportedInterfaceOrientations~ipad</key>
      <string>UIInterfaceOrientationLandscapeLeft</string>
      <string>UIInterfaceOrientationLandscapeRight</string>
    <key>UIInterfaceOrientation</key>
      <string>UIInterfaceOrientationLandscapeLeft</string>

Closing.

So it took 3 years to fix this. Unbelievable. 🥇 👍 XD :D

@iharosi incorrect. The issue existed in Apache Cordova land and took one year to fix.
PhoneGap and Apache Cordova are open source projects, and you are more than welcome to help out and fix things. Snark is, generally speaking, unhelpful, and quite frankly, demotivating to all of the contributors spending their time on this trying to help folks like yourself.


Remove JCenter

Fixes #478

Broken right now due to https://github.com/JetBrains/markdown/issues/69

Waiting on https://github.com/Kotlin/kotlinx.html/issues/173


[BUG] Network configuration enters undefined state (nodeNetwork stuck on terminating)

Describe the bug
Under certain circumstances the networkNode resource for a specific node may become stuck in terminating causing the network configuration on the OS to be left in an undefined state and thus disrupting VM connectivity.
 Then, harvester-vip-controller confirms the status and switch the VIP interface. In this case, the status seems not to be updated and the harvester-vip-controller returned the error. That’s the reason why it’s stuck in the terminal state. However, I could not figure out what happen at the time of deleting the nodenetwork from the provided log.
By the way, we realized the harvester-vip-controller isn’t a good implementation before and it was removed in the master-head.

@janeczku Could you help confirm if the issue is resolved in the customer environment after upgrading to the v1.0.1 version?

close due to inactivity, and also we have deprecated the NodeNetwork CRD.


few of functionalities are not working for BTC price

Hi There,
thanks for creating such a wonderful library. Below 2 functionalities are not working for BTC prices. Is it known issue?
qs.reports.full(...)
qs.reports.html(...)
Please help!
Regards,
Ananta

You can pass trading_year_days=365 to these methods to have it calculate properly for cryptos 24/7/365 market


Instructions SetFrequency/ShiftFrequency do not accumulate phase

Information

Qiskit Terra version:
Python version:
Operating system:

What is the current behavior?
When using SetFrequency/ShiftFrequency the phase of the channel does not accumulate when shifting from f_1 to f_2 for a period n*dt, and then back to f_1. This is a known issue with the backend and will be corrected on the backends shortly. This issue is to track and will be closed when the backend is fixed.
Steps to reproduce the problem
Starting on resonance with the qubit perform a Ramsey experiment and shift the frequency during the delay duration, the signal should oscillate proportional to the delay but it will not.
What is the expected behavior?
The phase should accumulate on the channel proportional to its frame.

Thanks for the issue report!


HOW TO CREATE A SELENIUM COLLECTOR

Can some one share some ideas on how to create a selenium collector

If you output your selenium test results in one of the supported formats it should be able to be collected from Jenkins plugins or an appropriate collector. I’d probably output in junit xml output and use the code quality Jenkins plugin where the results would appear in that section, but if you want the results in the functional test area then just get your selenium test results to be in a format for that plugin (includes mochajs output now)

@mitunmbj any update here?

@mitunmbj closing due to inactivity


Fix build for android

As mentioned in #312, this fixes the build for Android and works on both Mac and Linux with the following CMake invocation:
cmake -G Ninja \
    -DCMAKE_BUILD_TYPE=Release \
    -DCMAKE_SYSTEM_NAME=Android \
    -DCMAKE_SYSROOT=$ANDROID_STANDALONE_TOOLCHAIN/sysroot \
    -DENABLE_SWIFT=YES \
    -DBUILD_SHARED_LIBS=YES \
    -DCMAKE_SWIFT_COMPILER=$SWIFT_INSTALLATION_PATH/usr/Darwin/swiftc \
    -DENABLE_TESTING=OFF \
    -DCMAKE_ANDROID_ARCH_ABI=armeabi-v7a \
    -DCMAKE_ANDROID_NDK_TOOLCHAIN_VERSION=clang \
    $SWIFT_SOURCE_PATH/swift-corelibs-libdispatch

@compnerd you did most of the cmake porting, can you review the change please?

Can you please squash the changes into a single commit?

Also please squash in a single commit.

@MadCoder can you elaborate? We are successfully working with this fork, since we need the android support. Would be nice to have this merged.

I'm going to close this PR for now.  It no longer cleanly applies.  I believe that libdispatch builds for android currently, but, if it does not, that is certainly that should be addressed.


Variable merge/split documentation

Need more documentation on the hotkeys and recent changes on sorting / one shot hotkey.

Added 4.0.4876


Merging and closing our major branches.

Many of our branches (namely experimental-view-with-simulation,topological-evaluation,view-enhancement,model-simulation) are done by this point, so we should work on merging them into main. Because all of us had worked on these branches I'm opening this issue to notify everybody of our plan. Please do not start any new work on these branches.
First, we'll merge experimental-view-with-simulation into main
Then, we'll merge topological-evaluation into main
We'll close view-enhancement and model-simulation,  since all their latest changes will be merged to main through branches above.

Is this issue done?

Is this issue done?

No, we haven't dond the merges yet.

We have done the merges now, can I proceed with deleting the left over branches?

We have done the merges now, can I proceed with deleting the left over branches?

Um, if you would please close the associated issues too. Thank you.


Bug: Prisma crashes when connecting to CockroachDB with "Segmentation fault" error

Provide environment information
Binaries:
Node: 18.15.0
pnpm: 8.0.0
Project Specifics:
create-t3-app initVersion: 7.8.0
DB: CockroachDB
Describe the bug
I was following along with Theo's T3 Tutorial when around 30 minutes in my dev server stopped (crashed) unexpectedly; no error was displayed. I tried restarting it a bunch, but every time it would build the app and crash; no error/information was displayed:
$ pnpm dev

><EMAIL_ADDRESS>dev ~/Development/michelangelo
> next dev

ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
info  - Loaded env from ~/Development/michelangelo/.env
event - compiled client and server successfully in 934 ms (310 modules)
wait  - compiling /api/trpc/[trpc] (client and server)...
event - compiled successfully in 114 ms (61 modules)
wait  - compiling /src/middleware (client and server)...
event - compiled successfully in 133 ms (81 modules)
[crashes with no error]

The same thing happened when I ran prisma studio.
I tried everything: from upgrading dependencies, to upgrading pnpm, and even node to the latest versions; nothing worked. I did however get the following error from pnpm (after upgrading it to v8.0.0) when I ran Prisma Studio: ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command was killed with SIGSEGV (Segmentation fault): prisma studio
A quick search revealed that this is a known issue within Prisma; it seems that Prisma doesn't play well with Postgres and Postgres-like DBs (e.g. Supabase and CockroachDB) within Node v18 environments. The issue (dev server crashing continuously) goes away when one reverts to Node v16 (or at least it did for me). Here are alternative ways to solve the problem.
I created this issue to help those who stumble across the same issue but have no idea where to start, since the dev server crashes with no warnings/errors. I would also like to request that this quirk of Prisma be added to the docs for people using Postgres DBs to know of it beforehand.
Reproduction repo
N/A
To reproduce

Create T3 app with create-t3-app using pnpm in an Node v18 (lts/hydrogen) environment.
Provision either a Supabase Postgres DB or CockroachDB.
Run dev server. You should run into this issue after some time.

Additional information
No response

I have a similar problem #1342.
But i believe it's due to NodeJS. Can you try to build and run the same app only on Node 16x?

are you using WSL by any chance?

No.

Has this been fixed upstream yet? They closed the issue.
Can anyone verify?

Hi Julius. I don't know whether they fixed the issue since I reverted to Node 16. Bit held up atm, but will verify and get back to you within the week.

I have tested Prisma in a Node 18.16.0 (lts/hydrogen) environment against both a Supabase Postgres DB and CockroachDB. Can confirm that the error no longer occurs. This post shows that it was fixed with the release of Prisma 4.13.0. Closing this now.


Call function of a javascript module

First, I would like congrats for that awesome project and documentation. Nice job!
I'm trying use django-unicorn on a project and based on examples I guess that have many functions on JavaScript maybe cause conflicts.
There any possibility to call a javascript module function?
Example:
  var Hellojs = (function() {
    var self = {};

    self.hello = function(name){
      alert("Hello " + name)
    }
    return self;
}());

  window.Hellojs = Hellojs;

class HelloView(UnicornView):
    name = ""

    def say_hello_in_js(self):
        self.name = ""
        self.call('Hellojs.hello', self.name)

Thanks, @adamghill and all contributors!

The code that handles that is pretty simple and looks at window for the passed-in method name: https://github.com/adamghill/django-unicorn/blob/bc72121/django_unicorn/static/js/component.js#L129. So, this.window['Hellojs.hello'] won't work with the current code.
If you want to make a PR to handle "dotting-in" to an object, that would be great. Otherwise, I'll take a look at adding it in the next release or so!

https://github.com/adamghill/django-unicorn/pull/174 looks pretty good, so I'll merge it into master and this feature will be in the next release.

Closing this since the PR is now merged into master.

Thanks @adamghill, I tried this PR, but I didn't have enough time. I hope contribute more soon.
This PR will help a lot.

https://www.django-unicorn.com/docs/changelog/#v0-25-0 has been released with this fix! 🎉


Missing features on 1.15.2

I downloaded this mod after watching some videos about it on 1.12 so I installed it on my 1.15.2 game and noticed some features missing. I couldn't find the Pigtificates, Ghastling or Brute's Egg Spawners on creative, couldn't make a gold golem and couldn't find any of them or the dungeons anounced while flying around the nether for quite a while...
Did I do something very wrong while installing or they got removed?

The structures were removed in later 1.12 versions and some mobs and items were removed in the 1.14 update.


Support default udev GCE PD device path

The expected GCE PD device name is google-{name of disk}. This is
because standard GCE images contain a udev rules file which renames
the GCE PD device to google-{name of disk} https://github.com/GoogleCloudPlatform/compute-image-packages/blob/master/google-startup-scripts/lib/udev/rules.d/65-gce-disk-naming.rules. In custome images which do not have that udev rules file
the device gets the default rules apply http://cgit.freedesktop.org/systemd/systemd/tree/rules/60-persistent-storage.rules
and the GCE PD device ends up with a name which looks like scsi-0Google_PersistentDisk_{name of disk}
This patch adds support for that scenario.
Signed-off-by: Sami Wagiaalla<EMAIL_ADDRESS>

+cc @smarterclayton @thockin

The code change looks good to me, but two thoughts on the problem you tried to solve.
I would expect there to be an image build process which will take such thing into account, e.g. install the rules for you while you are building the image.  @brendandburns may know it.
The other is will this work on distro not adopting systemd yet, notably slackware, stock gentoo, older ubuntu?

The other is will this work on distro not adopting systemd yet, notably slackware, stock gentoo, older ubuntu?

Hmm... I have not tested the above but udev now lives in the systemd tree: http://lwn.net/Articles/490413/. So even distros which do not have not adopted systemd would get it form the systemd repo

@ddysher I looked at a Gentoo as an example and the 60-persistent-storage.rules is the same as the one found in the systemd repo

Thanks for confirming!  Just as a precaution, did you run e2e test?  specifically, the pd test

@ddysher I ran the e2e tests. The pd tests are passing.


Back camera

I don't know nothing (John Snow) about Javascript. Could you please show an example of how to take a snap using the back camera? Thks!

Hi there!  Check out this issue:
https://github.com/jhuckaby/webcamjs/issues/157
It isn't a completely solved problem, because there's no way to specify the back camera in Flash.  But for the HTML5 based webcam, you can set facingMode: 'environment'.
Good luck!


Project Plan: Your Pocket Therapist

Project Plan: Your Pocket Therapist
Your Pocket Therapist uses an AI Face algorithm to accurately understand the user's emotions and provide advice/quotes in response.

Nighthawk pages frontend
Spring portfolio backend

Team Members

Vivian N
Isabelle G
Tanisha P
Sreeja G
Project Objectives

Create a user-friendly interface
Create a live emotion detector, if make it so photos can be uploaded
Utilize a Face API to detect images and output emotions
Create our own unique database of advice and quotes that correspond to the emotions
Focus on JS for the frontend and Java for the backend

Project Tasks and Timeline

Frontend (JS HTML)

[ ] HTML Formatting (overall sass)
[ ]  Container for Live Camera
[ ]  Section for Emotion recognizer result(with corresponding emoji), percent accuracy
[ ]  Section for a generated quote (From API/Database call)

Emotions AI (PYTHON)

[ ] Open CV integration to live data collection
[ ]  Find API/Data for the model -- RapidAPI
[ ]  Training/Testing
[ ]  Display emotion result, save to global variable
[ ]  Percent accuracy calculation

Quote Generation (JAVA)

[ ]  Access quote based on saved emotion result
[ ]  FIND API
https://rapidapi.com/karanp41-eRiF1pYLK1P/api/world-of-quotes
[ ]  Display successful api/database call

Sub ticket Tanisha CNN implementation
###Week 1: Planning and Data Preparation
Day 0: Sprint Planning

[ ] - Define the project scope and objectives.
[ ] - Create user stories and product backlog.
[ ] - Set up a Scrum board or Jira project.
[ ] - Assign roles and responsibilities: Product Owner, Scrum Master, Development Team.
[ ] - Kick-off meeting to clarify goals and expectations.

Day 1: Data Collection

[ ] Gather a dataset of facial images labeled with emotions (e.g., Kaggle's FER-2013 dataset).
[ ] Clean the dataset by removing irrelevant or low-quality images.

Day 2: Data Preprocessing

[ ] Resize images to a consistent format (e.g., 224x224 pixels).
[ ] Normalize pixel values to a common scale (e.g., [0, 1]).
[ ] Split the dataset into training, validation, and test sets.
[ ] Augment the training dataset (e.g., rotate, flip, zoom) to increase diversity.

Day 3: Model Architecture Design

[ ] Decide on a CNN architecture (e.g., VGG16, ResNet, or custom architecture).
[ ] Define the layers, filters, and activation functions for the model.
[ ] Document the model architecture on your Scrum board.

Day 4: Model Implementation

[ ] Start coding the CNN model in a deep learning framework like TensorFlow or PyTorch.
[ ] Implement forward and backward passes, loss function, and optimization algorithm (e.g., Adam).
[ ] Ensure the model can handle the input image size and number of classes.

Day 5: Training

[ ] Train the model on the preprocessed dataset.
[ ] Monitor training metrics such as loss and accuracy.
[ ] Use early stopping if validation performance stalls.
[ ] Document training progress on your Scrum board.

Day 6: Model Evaluation

[ ] Evaluate the model's performance using the test set.
[ ] Calculate metrics like accuracy, precision, recall, and F1-score.
[ ] Identify potential sources of bias or error and document them.

###Week 2: Model Optimization and Deployment
Day 7: Hyperparameter Tuning

[ ] Fine-tune hyperparameters, like learning rate, batch size, or dropout rates.
[ ] Experiment with different CNN architectures to improve performance.

Day 8: Error Analysis

[ ] Analyze model errors on the test set to understand common misclassifications.
[ ] Adjust the model or dataset to address error patterns.

Day 9: Model Interpretability

[ ] Implement visualization techniques (e.g., Grad-CAM) to understand what the model focuses on when making predictions.

Day 10: Model Optimization

[ ] Implement model optimization techniques (e.g., weight quantization or model pruning) for deployment on resource-constrained devices.

Day 11: Deployment Setup

[ ] Set up the infrastructure and environment for model deployment (e.g., cloud server or edge device).
[ ] Create an API or interface for the model.

Day 12: Testing and Validation

[ ] Test the deployed model to ensure it functions correctly in the production environment.
[ ] Validate the model's real-world performance.

Day 13: Documentation and Training

[ ] Document the model architecture, training process, and deployment steps.
[ ] Train end-users or colleagues on using the model effectively.

Day 14: Final Review and Retrospective

[ ] Review the project's achievements and ensure all requirements are met.
[ ] Conduct a retrospective meeting to discuss what went well and what could be improved in the development process.
[ ] Plan for future iterations or improvements.

Plan

on quotes.md, use a post-JS to post new quotes to the database. Ensure that when the page is refreshed, the added quote still remains.
gallery.md will also have JS code to format and display each quote with HTML and CSS in a more efficient way

issues

ran into a cors issue. had to add this to nginx file. Now I can locally test the post

on gallery.md, use a get fetch call to update the page with all the new quotes, including quotes that were added on quotes.md.

SUB REVIEW TICKET: CAMERA FEATURE (SREEJA)

Camera progress

Code for Camera
MD file

Java Script Code

Commits

AI Chatbot (Isabelle)
**Plan: **
create chatbot feature that uses conversations from real therapists to emulate a therapist for the user
Frontend:

Backend:

use Apache OpenNLP

Issues:

Use AIML for backend instead
Connect frontend to backend


⚠ Bofrost.es has degraded performance

In e40c88e, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1428 ms

Resolved: Bofrost.es performance has improved in 234160f after 6 minutes.


Cannot build on rust nightly

Building on Rust nightly leads to errors about lifetimes for Req, Resp and C types in pub async fn spawn in dispatch.rs and in client.rs. I also had to change the service! macro to add a 'static for SinkItem. I can submit a PR for this, but not sure this is the change you want in general.

rustc 1.31.0-nightly (f99911a4a 2018-10-23)```


--volume-driver and network volume drivers (maybe others too) can't be used

I am trying to use the EFS network volume driver with docker but portainers does not lets you specify --volume-driver while creating new containers.
It is just curious that the 'efs' driver is displayed alongside the 'local' driver when you are creating a new volume but it is not possible to use it (you can't configure it on creation time nor you can specify it while launching the container)
Steps to reproduce the issue:
Creating the volume:

go create new volume
driver dropdown shows 'local' and 'efs' (in my case I've docker efs v0.18 driver installed)
options can be specified
default export endpoint can't be configured
default mount point either

Using an existing value in a new container:

You can't specify the --volume-driver option.

We need to define the workflow to use these type of volumes inside Portainer.

How to create that volume from Portainer?
How to map that volume inside the container-creation view ?

I do not know the EFS volume plugin (it's a volume plugin, not a network plugin if I understand correctly), so I can't answer 1.
About 2., if we implement the --volume-driver in the container-creation view, how to map an existing volume using that plugin? Is it created and available in the volumes view? If not, should we use a bind-mount to map inside the container?
We need to answer these questions before being able to work on this.

EFS volume usage example:
Create the volume in AWS
$ sudo aws efs
Volume created with, i.e. fs-2324532
Start the volume manager
$ sudo docker-volume-netshare efs
Create the container mapping the volume to the efs one
$ docker run -i -t --volume-driver=efs -v fs-2324532:/mount ubuntu /bin/bash

As far as I understand in this case the volume does not need to be truly
created beforehand.
This is because when you get the volume automatically mounted during the
container creation, the efs driver itself creates the volume files
in "/var/lib/docker-volumes/netshare" (by default)

The volume creation page in portainer is enough as is. (but just store
the volume config instead to try to create a realvolume) Attached picture
Then when the container is launched Portainer should only add the
'--volume-driver=efs-whatever' just if the volume configuration is not
'local' (or add the correspongind arguments to the api call)

BTW, I am not sure if the volume creation takes in care there are volume
options that only have name, but not value (as in the attached picture)
There is a subtle implication about using efs to store data out of the
scope of this issue: If you use multiple containers or just configure a
service in Swarm all the containers would write to the network storage,
probably causing data corruption. Handle with caution.
--
Iván González Valiente
Systems Developer - DevOp - IT Manager
2017-05-04 13:44 GMT+02:00 Anthony Lapenna<EMAIL_ADDRESS>
We need to define the workflow to use these type of volumes inside
Portainer.

How to create that volume from Portainer?
How to map that volume inside the container-creation view ?

I do not know the EFS volume plugin (it's a volume plugin, not a network
plugin if I understand correctly), so I can't answer 1.
About 2., if we implement the --volume-driver in the container-creation
view, how to map an existing volume using that plugin? Is it created and
available in the volumes view? If not, should we use a bind-mount to map
inside the container?
We need to answer these questions before being able to work on this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/portainer/portainer/issues/841#issuecomment-299162337,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB-24-KR5H6QpcFsR6OBQ-vLOsMSOa73ks5r2bolgaJpZM4NQgxa
.

@colegatron Is this how you're supposed to create a volume from Portainer? And to answer your previous question: no, options without values will not be taken into account (not sure about Docker CLI behavior for that one).

Sorry for the delay to answer.
After a bunch of tries and errors with the efs driver trying to let them rule my deploys I've desisted to use it with databases. And since the services containers are not big, they can be stored in the host filesystem without problems for me.
BTW, I've found way easier just use the aws efs volume as a regular nfs volume because it gives you the ability to mount specific subfolders to specific containers with a single nfs mount.
To have as less as possible nfs mounts makes the volumes management easier and cleaner.
I'll keep trying to use portainer as long as I continue working with Docker and Swarms

@colegatron how do we mount a nfs subfolder?


Potential fix for architecture like nextjs?

If I try to use theatre on NextJS I randomly get the following error (not always weirdly):
Error [ERR_REQUIRE_ESM]: require() of ES Module /.../node_modules/lodash-es/get.js from<EMAIL_ADDRESS>not supported.
Instead change the require of get.js in<EMAIL_ADDRESS>to a dynamic import() which is available in all CommonJS modules.

The error happened to other developers in my company, and with a different setup of NextJS.
I am totally not sure about my PR, it's just an idea feel free to close it for a proper fix.

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


CORS on error handling

While developing a web application, my goal was to catch a 401 HTTP error and attempt to refresh the user's authentication token.
Using the default app.use(cors()) adds CORS headers to regularly responses, but it seems like this configuration does not apply CORS headers when handling error responses.
It would be great if there was either a mention of this in the documentation or an additional middleware for adding CORS headers in the error response flow.

This module doesn't do anything different for error responses or not, and in fact adds headers without looking at anything to do with response codes. Can you point tk where in our source code we're doing something different for error responses?

The existing source code is fine, I think. I don't see a special error handler. It's poorly explained in the express documentation whether or not the 4-arity error handling middleware function gets called in the same order/way as the 3-arity function gets called. Perhaps it was confusion across cors and express documentation.
Sorry if this sounded demanding. Thanks for the consideration.

Gotcha. Yea, this is just a middleware, vs an error handling middleware and would be called in the same way as any other middleware would in the same situation. If you believe the Express.js docs are not clear, the site is open for modifications and I do know first hand it can be difficult to write docs because whar makes sense and is clear to one person may not to another and that person us easily blinded by their existing knowledge. Helping by updating docs to reflect your situation can help countless others who are going through the same learning process :+1:


Sinopia on header does not display Copperlight Gothic font on Safari

it should be

this looks ok on safari


API routes need to be added for each supported assessment feature

Describe the Feature / Enhancement
Each assessment feature will need an API route to be able to update the database. In this first step, we need to add routes for each assessment feature.
Additional Details and Resources
No response
Correct Project Selected

[X] This issue is linked to the appropriate project

Labels

[X] This issue has appropriate labels.

EOD Update: I have assigned this group with an intermediate task to create a list of routes that they need before creating the router files. Once we review the text file / Google Doc with the list of routes (and associated HTTP verbs) together tomorrow and they are approved, the team will create the associated router files, wire them up into server.ts, and have each respond to the corresponding routes with a basic message of their choosing and an appropriate HTTP status.
Next steps:

[ ] Create shared Google Doc /  text file that lists out every route needed within api to support every feature we're building out as well as the associated HTTP verb for that route. (Bonus points: the expected possible HTTP status codes for each of these routes.) This list will encompass all the routes for both the mentor/facilitator and the mentee/participant. (The same route may have different behavior depending on who's logged in.)
[ ] Review the routes with @seidior for approval and modify as is necessary.
[ ] Create a branch to contain code changes.
[ ] Create the route files, add them to server.ts, and respond to each route with a placeholder message and HTTP status.

Out of scope:

Any internal functionality for the routes, including anything database related (This will be started on next week.) or anything related to principalId.
Service files
Database migrations
Webapp routing
Unit tests for the routes

we have made routes for the assessment router and added one more route to the program router.


Slow start up

Hi,
I have been using/trying gitcache for a couple of days already and I have noticed that in some cases is slower that plain git.
I'm trying to use gitcache with Terragrunt/Atlantis to avoid cloning the same repo hundreds of times, but since Terragrunt uses git rev-parse --show-toplevel a lot it is being slower than plain git.
The start up time before showing any debug is considerable (In the order of 3-4 seconds) for an already cloned repo:
bash-5.2$ export GITCACHE_UPDATE_INTERVAL=10d
bash-5.2$ time GITCACHE_LOGLEVEL=Debug /usr/local/bin/git clone git@github.com:seeraven/gitcache.git
2024-05-10 10:05:43 Python executable: /usr/local/bin/git
2024-05-10 10:05:43 Called as ['/usr/local/bin/git', 'clone', 'git@github.com:seeraven/gitcache.git']
2024-05-10 10:05:43 handle_git_command(['/usr/local/bin/git'], ['clone', 'git@github.com:seeraven/gitcache.git']) started
2024-05-10 10:05:43 Found global options [], command 'clone', command options '[]' and arguments ['git@github.com:seeraven/gitcache.git'].
2024-05-10 10:05:43 Loading configuration file /Users/andresmontalban/.gitcache/config.
2024-05-10 10:05:43 Loading configuration file /Users/andresmontalban/.gitcache/config.
2024-05-10 10:05:43 Can't load configuration file /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/gitcache.config as it does not exist!
2024-05-10 10:05:43 Update time of mirror /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache not reached yet.
2024-05-10 10:05:43 Starting Clone from mirror /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache.
2024-05-10 10:05:43 Retry to execute command '/usr/bin/git -c lfs.url=git@github.com:seeraven/gitcache.git/info/lfs -c lfs.storage=/Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/lfs clone /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/git gitcache' up to 3 times.
2024-05-10 10:05:43 Execute command '/usr/bin/git -c lfs.url=git@github.com:seeraven/gitcache.git/info/lfs -c lfs.storage=/Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/lfs clone /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/git gitcache' (shell=False, cwd=None) with command timeout of 3600 seconds and output timeout of 300 seconds. stderr_capture=True
Cloning into 'gitcache'...
done.
2024-05-10 10:05:43 Command '/usr/bin/git -c lfs.url=git@github.com:seeraven/gitcache.git/info/lfs -c lfs.storage=/Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/lfs clone /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/git gitcache' finished with return code 0.
2024-05-10 10:05:43 Clone from mirror /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache was successfully completed within 0.1 seconds.
2024-05-10 10:05:43 Setting push URL to git@github.com:seeraven/gitcache.git and configure LFS.

real	0m5.843s
user	0m0.295s
sys	0m0.168s

If I do not setup GITCACHE_LOGLEVEL=Debug it takes longer because it has to update the clone.
On the other hand if I use plain git I get faster clone:
bash-5.2$ time git clone git@github.com:seeraven/gitcache.git
Cloning into 'gitcache'...
remote: Enumerating objects: 1122, done.
remote: Counting objects: 100% (150/150), done.
remote: Compressing objects: 100% (59/59), done.
remote: Total 1122 (delta 101), reused 114 (delta 84), pack-reused 972
Receiving objects: 100% (1122/1122), 291.03 KiB | 483.00 KiB/s, done.

Any idea on how to make it faster?
Thank you very in advance for your help!

Hello @amontalban ,
that are really huge startup times of gitcache! I repeated your steps on my Linux machine running Ubuntu, and I see only 0.220s (real).
Since the rev-parse commands are actually only forwarded by gitcache, it is pretty clear that the delay is introduced by the startup time of the binary until it starts interpreting the python code.
The binaries are all created by using pyInstaller which extracts its files into a temporary directory on startup before starting interpreting it. This is done on every call and seems to take more than 5 seconds on your machine. I have found a question on stackoverflow which suggests using a different option, but this will probably also clutter the workspace (I have to check that in more detail).
Apparently also pyInstaller does not recommend the current distribution method (--onefile) on MacOS due to performance issues. Apparently the OS might check the temporary files repeatedly and I guess that is what we see here. However, I'm still surprised how large this delay is.
I will check how the proposed --onedir distribution works and try to generate the archives for that distribution method.
On your AWS machine, do you run also MacOS on it or is it a different OS?

Hello @amontalban ,
I've created a new release https://github.com/seeraven/gitcache/releases/tag/v1.0.16 that should overcome the startup delay problem. Now the MacOS release is created using the --onedir option which means that the script including all dependencies is a directory rather than a single file. That means, that the installation has slightly changed, as the directory contents (consisting of the gitcache command and the _internal subdirectory) should not be separated. Best way is probably to put it somewhere and adjust the PATH variable accordingly, so that gitcache (and perhaps the git -> gitcache symlink) is found.
It would be great if you can test it and give feedback on how it works, as I have no Mac to actually test it. ;-)

Hi @seeraven,
Thanks for the quick fix, I have tested in my macOS and it is now performing way better. Regarding my tests in a Linux box I think the problem was something not related to gitcache, so sorry for the noise.
Cold clone
(⎈|N/A:default) ~/test  time GITCACHE_LOGLEVEL=Debug ./gitcache_v1.0.16_Darwin_arm64/gitcache git clone git@github.com:seeraven/gitcache.git test_gitcache_cold
2024-05-14 10:14:48 Python executable: /Users/andresmontalban/test/gitcache_v1.0.16_Darwin_arm64/gitcache
2024-05-14 10:14:48 Called as ['./gitcache_v1.0.16_Darwin_arm64/gitcache', 'git', 'clone', 'git@github.com:seeraven/gitcache.git', 'test_gitcache_cold']
2024-05-14 10:14:48 handle_git_command(['./gitcache_v1.0.16_Darwin_arm64/gitcache', 'git'], ['clone', 'git@github.com:seeraven/gitcache.git', 'test_gitcache_cold']) started
2024-05-14 10:14:48 Found global options [], command 'clone', command options '[]' and arguments ['git@github.com:seeraven/gitcache.git', 'test_gitcache_cold'].
2024-05-14 10:14:48 Can't load configuration file /Users/andresmontalban/.gitcache/config as it does not exist!
2024-05-14 10:14:48 Save configuration file /Users/andresmontalban/.gitcache/config.
2024-05-14 10:14:48 Loading configuration file /Users/andresmontalban/.gitcache/config.
2024-05-14 10:14:48 Can't load configuration file /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/gitcache.config as it does not exist!
2024-05-14 10:14:48 Starting Initial clone of git@github.com:seeraven/gitcache.git into /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache.
2024-05-14 10:14:48 Retry to execute command '/usr/bin/git clone --progress --mirror git@github.com:seeraven/gitcache.git /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/git' up to 3 times.
2024-05-14 10:14:48 Execute command '/usr/bin/git clone --progress --mirror git@github.com:seeraven/gitcache.git /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/git' (shell=False, cwd=None) with command timeout of 3600 seconds and output timeout of 300 seconds. stderr_capture=True
Cloning into bare repository '/Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/git'...
remote: Enumerating objects: 1161, done.
remote: Counting objects: 100% (182/182), done.
remote: Compressing objects: 100% (77/77), done.
remote: Total 1161 (delta 124), reused 137 (delta 97), pack-reused 979
Receiving objects: 100% (1161/1161), 298.29 KiB | 263.00 KiB/s, done.
Resolving deltas: 100% (758/758), done.
2024-05-14 10:14:53 Command '/usr/bin/git clone --progress --mirror git@github.com:seeraven/gitcache.git /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/git' finished with return code 0.
2024-05-14 10:14:53 Initial clone of git@github.com:seeraven/gitcache.git into /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache was successfully completed within 5.4 seconds.
2024-05-14 10:14:53 LFS fetch skipped as git-lfs is not available on this system!
2024-05-14 10:14:53 Starting Clone from mirror /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache.
2024-05-14 10:14:53 Retry to execute command '/usr/bin/git -c lfs.url=git@github.com:seeraven/gitcache.git/info/lfs -c lfs.storage=/Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/lfs clone /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/git test_gitcache_cold' up to 3 times.
2024-05-14 10:14:53 Execute command '/usr/bin/git -c lfs.url=git@github.com:seeraven/gitcache.git/info/lfs -c lfs.storage=/Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/lfs clone /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/git test_gitcache_cold' (shell=False, cwd=None) with command timeout of 3600 seconds and output timeout of 300 seconds. stderr_capture=True
Cloning into 'test_gitcache_cold'...
done.
2024-05-14 10:14:54 Command '/usr/bin/git -c lfs.url=git@github.com:seeraven/gitcache.git/info/lfs -c lfs.storage=/Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/lfs clone /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/git test_gitcache_cold' finished with return code 0.
2024-05-14 10:14:54 Clone from mirror /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache was successfully completed within 0.1 seconds.
2024-05-14 10:14:54 Setting push URL to git@github.com:seeraven/gitcache.git and configure LFS.
GITCACHE_LOGLEVEL=Debug ./gitcache_v1.0.16_Darwin_arm64/gitcache git clone    0.26s user 0.14s system 7% cpu 5.692 total

Warm clone
(⎈|N/A:default) ~/test  time GITCACHE_LOGLEVEL=Debug ./gitcache_v1.0.16_Darwin_arm64/gitcache git clone git@github.com:seeraven/gitcache.git test_gitcache_warm
2024-05-14 10:15:00 Python executable: /Users/andresmontalban/test/gitcache_v1.0.16_Darwin_arm64/gitcache
2024-05-14 10:15:00 Called as ['./gitcache_v1.0.16_Darwin_arm64/gitcache', 'git', 'clone', 'git@github.com:seeraven/gitcache.git', 'test_gitcache_warm']
2024-05-14 10:15:00 handle_git_command(['./gitcache_v1.0.16_Darwin_arm64/gitcache', 'git'], ['clone', 'git@github.com:seeraven/gitcache.git', 'test_gitcache_warm']) started
2024-05-14 10:15:00 Found global options [], command 'clone', command options '[]' and arguments ['git@github.com:seeraven/gitcache.git', 'test_gitcache_warm'].
2024-05-14 10:15:00 Loading configuration file /Users/andresmontalban/.gitcache/config.
2024-05-14 10:15:00 Loading configuration file /Users/andresmontalban/.gitcache/config.
2024-05-14 10:15:00 Can't load configuration file /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/gitcache.config as it does not exist!
2024-05-14 10:15:00 Update time of mirror /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache not reached yet.
2024-05-14 10:15:00 Starting Clone from mirror /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache.
2024-05-14 10:15:00 Retry to execute command '/usr/bin/git -c lfs.url=git@github.com:seeraven/gitcache.git/info/lfs -c lfs.storage=/Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/lfs clone /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/git test_gitcache_warm' up to 3 times.
2024-05-14 10:15:00 Execute command '/usr/bin/git -c lfs.url=git@github.com:seeraven/gitcache.git/info/lfs -c lfs.storage=/Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/lfs clone /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/git test_gitcache_warm' (shell=False, cwd=None) with command timeout of 3600 seconds and output timeout of 300 seconds. stderr_capture=True
Cloning into 'test_gitcache_warm'...
done.
2024-05-14 10:15:00 Command '/usr/bin/git -c lfs.url=git@github.com:seeraven/gitcache.git/info/lfs -c lfs.storage=/Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/lfs clone /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache/git test_gitcache_warm' finished with return code 0.
2024-05-14 10:15:00 Clone from mirror /Users/andresmontalban/.gitcache/mirrors/github.com/seeraven/gitcache was successfully completed within 0.1 seconds.
2024-05-14 10:15:00 Setting push URL to git@github.com:seeraven/gitcache.git and configure LFS.
GITCACHE_LOGLEVEL=Debug ./gitcache_v1.0.16_Darwin_arm64/gitcache git clone    0.15s user 0.07s system 82% cpu 0.268 total

Native clone
(⎈|N/A:default) ~/test  time git clone git@github.com:seeraven/gitcache.git test_gitcache_native
Cloning into 'test_gitcache_native'...
remote: Enumerating objects: 1154, done.
remote: Counting objects: 100% (182/182), done.
remote: Compressing objects: 100% (77/77), done.
remote: Total 1154 (delta 124), reused 137 (delta 97), pack-reused 972
Receiving objects: 100% (1154/1154), 297.01 KiB | 257.00 KiB/s, done.
Resolving deltas: 100% (752/752), done.
git clone git@github.com:seeraven/gitcache.git test_gitcache_native  0.14s user 0.07s system 3% cpu 5.341 total

Same as for git rev-parse --show-toplevel:
(⎈|N/A:default) ~/test/test_gitcache   master  time GITCACHE_LOGLEVEL=Debug ../gitcache_v1.0.16_Darwin_arm64/gitcache git rev-parse --show-toplevel
2024-05-14 10:17:34 Python executable: /Users/andresmontalban/test/gitcache_v1.0.16_Darwin_arm64/gitcache
2024-05-14 10:17:34 Called as ['../gitcache_v1.0.16_Darwin_arm64/gitcache', 'git', 'rev-parse', '--show-toplevel']
2024-05-14 10:17:34 handle_git_command(['../gitcache_v1.0.16_Darwin_arm64/gitcache', 'git'], ['rev-parse', '--show-toplevel']) started
2024-05-14 10:17:34 Found global options [], command 'rev-parse', command options '[]' and arguments [].
2024-05-14 10:17:34 Command 'rev-parse' is not handled by gitcache. Calling the real git command.
2024-05-14 10:17:34 Loading configuration file /Users/andresmontalban/.gitcache/config.
/Users/andresmontalban/test/test_gitcache
GITCACHE_LOGLEVEL=Debug ../gitcache_v1.0.16_Darwin_arm64/gitcache git    0.13s user 0.03s system 90% cpu 0.175 total

Native
(⎈|N/A:default) ~/test/test_gitcache   master  time git rev-parse --show-toplevel
/Users/andresmontalban/test/test_gitcache
git rev-parse --show-toplevel  0.00s user 0.00s system 59% cpu 0.012 total

Cool, so I will close this issue now.


Add ETH bridge to Starknet

https://medium.com/starkware/starkgate-alpha-35d01d21e3af
https://etherscan.io/address/0xae0Ee0A63A2cE6BaeEFFE56e7714FB4EFE48D419

https://github.com/l2beat/l2beat/pull/444


ssl how to configure？

ssl how to configure？
my configuration does not work？

Hi @duanxg
Can u give more details of what u want to do?
If u wanna proxy SSL request with CONNECT method (http connect tunnel), there is a simple configure in README ( see here).

@chobits I have solved this problem


FlyWire fan-shaped body terms

Make layer x lineage terms (tangential neurons)
nothing more specific at this stage

letter to lineage mapping from supplement:

letter
ito_lee_hemilineage
hartenstein_hemilineage

A
DM6__prim
CM3__prim

A
DM6_dorso_medial
CM3_dorso_medial

A
putative_primary
putative_primary

A

B
DM6_dorso_medial
CM3_dorso_medial

C
SIPp1
DPMpl2

D
AOTUv4_ventral
DALcl2_ventral

D

E
DL1_dorsal
CP2_dorsal

F
putative_primary
putative_primary

G
DM4_dorsal
CM4_dorsal

H
DM6__prim
CM3__prim

I
LALv1_dorsal
BAmv1_dorsal

K
CREa1_dorsal
BAmd1_dorsal

K
CREa2_medial
DALcm1_medial

L
EBa1
DALv2

Probably best not to make terms based on inconsistent lineage annotations (A, K) or just 'primary' (F) and we can lump to full lineages for now (since we don't have terms to represent all the hemilineages), so B and H will both be represented by a DM6 term.
Not all layers have all lineages, so just making the ones that exist in FW.
Excluding layer '3,4' cell types - I think this comma may be an OR, or at least not reliably an AND.


Release/beta 1.16.0

What
Stop the dataset-api from falling over unless sigterm is received.
How to review
Sanity check.
Who can review
Anyone.

nope. lets do it the easy way.


How to get STREAMLABS_TOKEN?

We have to update the documentation explaining how to get the STREAMLABS_TOKEN.
Since Streamlabs doesn't provide an easy way to get it... maybe we can add a new endpoint to handle the Authorization process and returns the access_token. What do you think? @orestes

Twitch has something similar to get tokens for bots: https://twitchapps.com/tmi/

We can hijack this link in the meanwhile https://tinyurl.com/ChatbotStreamlabs

Scopes reference: https://dev.streamlabs.com/docs/scopes

https://github.com/streamdevs/streamlabs-token
I just build a website to get the token, should we have a live version to allow everybody to get their tokens?


Set searchable to false to speed up in article_emails.

 Change the way the search is done is the mailing queue of a given article - currently it takes too much time (and trigger and internal server error)


Error when trying to publish to inbox from SkoHub Editor

I tried to publish to https://w3id.org/kim/hochschulfaechersystematik/n06. This is what I get.

The browser console gives:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://test.skohub.io/inbox?actor=dini-ag-kim/hochschulfaec…tik/heads/master/w3id.org/kim/hochschulfaechersystematik/n06. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).

Apparently, the problem is that CORS headers are not set for the test instance. Thus, there are two possible solutions:

Set CORS headers for test.skohub.io
Publish to production (skohub.io). Here is the code that would have to be adjusted (I think):

https://github.com/hbz/skohub-editor/blob/50932dd489b540377ea3a97a4acb44d57a463754/src/components/JSONPointerForm/SkohubLookup.js#L71-L81

@literarymachine I forgot the reason why SkoHub Editor publishes to the test server. Does this still make sense?

Thus, there are two possible solutions

We should probably do both and have concepts from skohub.io publish to the production inbox and concepts from test.skohub.io publish to the test inbox.

@dr0i Please set the CORS header for test and we will also publish to production from the production editor (& the extension).

Deployed to test and production, closed.


Link updates

Docs Build status updates of commit 290c457:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Secondary Nav Scroll Restoration

Summary
Added React ref to track the current navigation item being viewed. The navigation side panel will automatically scroll to the correct item based on the ref that is generated before the page renders.
Additional Details
Closes #187
@cerner/terra

If you pull master into your branch again, the PR build will work again.
We needed to add this line to prevent building on node 12:
https://github.com/cerner/terra-dev-site/blob/master/package.json#L5-L6

I tested the search workflow and it didn't seem to scroll the selected item into view.
To reproduce search for Example and select the item with this path /secondary-scroll/terra-dev-site/parent-folder/child-folder/example

/secondary-scroll/terra-dev-site/parent-folder/child-folder/example

I just ran npm install and npm start and the search workflow scrolled to the correct Example navigation item for me. Will you be at office hours today? I can meet you there and try to figure out why it is only working for me

@emilyrohrbough, thats the workflow. Let me amend my steps to reproduce:

Navigate to: https://terra-dev-site-deployed-pr-217.herokuapp.com/secondary-scroll
Search for Example
Select the item with this path /secondary-scroll/terra-dev-site/parent-folder/child-folder/example

ah I started from the home page 😄

@emilyrohrbough, thats the workflow. Let me amend my steps to reproduce:

Navigate to: https://terra-dev-site-deployed-pr-217.herokuapp.com/secondary-scroll
Search for Example
Select the item with this path /secondary-scroll/terra-dev-site/parent-folder/child-folder/example

Ok I see the issue now :(

I was able to figure out the reason why the secondary scroll was not working after using search. Following Matt's steps, the page had already mounted the the secondary navigation items. Which means the conditional statement in componentDidMount was never reached after selecting an item from the search results.
Selecting an item from the search results does trigger a rerender, though. Adding the same conditional statement in componentDidUpdate will catch the navigational change caused by the search workflow. So now the secondary scroll will work with the search workflow too. I will move on to the other comments in this PR now :)

I ran into another problem. Opening a directory in the secondary navigation causes a rerender. I need to figure out a way to identify the difference between a new navigation path and opening a directory while in the componentDidUpdate method.
I am not able to use this.state.previousSelectedPath because it is overwritten in the getDerivedStateFromProps method, before the rerender. I do not know the reason getDerivedStateFromProps was added to this class so I do not want to try and move its code to the componentDidUpdate method.
I am thinking about adding a class variable/boolean that can be toggled in the getDerivedStateFromProps method. I can use that variable in the componentDidUpdate method to check to see if the navigation changed. Please let me know there is an issue with this strategy

@mjhenkes @emilyrohrbough Ready for your reviews when you have time. @benbcai helped me with the wdio issue I was facing

It's working great!! 🎉  nice job on this!!

It's working great!! 🎉 nice job on this!!

Thanks! 😊


[Event Request] New events in InventoryPick.Page "Sales Header"

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.