"client intended to send too large body" event after setting bodySize annotation

I added the following annotation to deis-router:
apiVersion: v1
kind: ReplicationController
metadata:
  annotations:
    chart.helm.sh/description: Deis Workflow
    chart.helm.sh/file: /Users/olalonde/.helmc/workspace/charts/workflow-v2.4.1/manifests/deis-router-rc.yaml
    chart.helm.sh/name: workflow-v2.4.1
    chart.helm.sh/version: v2.4.1
    component.deis.io/version: v2.4.0
    router.deis.io/nginx.bodySize: 500M

However, even after making sure the annotation is set correctly with kd edit rc deis-router and killing the deis router pod kd delete po deis-router-2319742441-rjpcf, I'm still getting "413 entitity too large" NGINX responses when uploading a 1.8MB file to my server:
2016/09/02 23:03:21 [error] 171#0: *3609565 client intended to send too large body: 1817648 bytes, client: <IP_ADDRESS>, server: domain.com, request: "POST /api/v1/registrations HTTP/1.1", host: "domain.com", referrer: "https://domain.com/"

I exec'ed into the router and it seems the annotation is not working as expected:
router@deis-router-2319742441-2o3aq:/$ cat /opt/router/conf/nginx.conf | grep body
        client_max_body_size 1m;

You need to do that on the Deployment object and not the ReplicationController
If you do kubectl --namespace deis rc,deployment then you will see the RC for router has been scaled down to 0.
This is a limitation in Helm where we can not remove the RC manifest (yet)

Thanks, managed to fix the problem by adding the annotation using kd edit rc deis-router and restarting the router with kd delete po deis-router-2319742441-rjpcf.
$ kubectl --namespace deis get rc,deployment
NAME                    DESIRED   CURRENT   AGE
deis-builder            0         0         8d
deis-controller         0         0         8d
deis-logger             1         1         8d
deis-logger-redis       1         1         8d
deis-monitor-grafana    1         1         8d
deis-monitor-influxdb   1         1         8d
deis-nsqd               1         1         8d
deis-registry           0         0         8d
deis-router             0         0         8d
deis-workflow-manager   0         0         8d
NAME                    DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deis-builder            1         1         1            1           8d
deis-controller         1         1         1            1           8d
deis-registry           1         1         1            1           8d
deis-router             1         1         1            1           8d
deis-workflow-manager   1         1         1            1           8d

Why are some of them both listed in deployment and rc? Sorry not so familiar with k8s. Guess I missed https://github.com/deis/router/commit/a139c859cb95c2f5fdf44cb872bd401c3d6af666 :o

Because of Helm, in Workflow 2.3 (router annotations were fetching from RC tho until 2.4) we moved from RCs for Router, Builder and Controller, etc (the ones you see in the Deployment list) to allow for 0 downtime upgrades of those components (as supported by Kubernetes).
In Helm if you remove a manifest (such as the RC of Router) then Helm does nothing about it. It won't remove it for you. The solution was to have RC manifests for the above components that are set to 0 pods so that Deployments can start managing pods.
Hope that helps

Ok thanks, makes sense! Just wish I had known about this earlier.. now I'm guessing my controller has been in free for all REGISTRATION_MODE for a while. :(


No error and no payment

Sometimes when I try to pay an external invoice, after I click confirm, no payment is done and no error message appear. The window just close.

Please post an example invoice string @bitcoinuser . Also, have you downloaded the latest APK from sphinx.chat?

If I reproduce this again, I reopen the bug. I think the invoice I tried was from Breez wallet.


Could not resolve all files for configuration ':vision-camera-code-scanner:debugCompileClasspath'

I am trying to run the React-Native application using code scanner, I started getting below error.
_PS C:\Users\user\source\repos\REACT-NATIVE\ecom-app-new> react-native run-android
info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
Jetifier found 1278 file(s) to forward-jetify. Using 6 workers...
info JS server already running.
info Installing the app...

Configure project :react-native-reanimated
AAR for react-native-reanimated has been found
C:\Users\user\source\repos\REACT-NATIVE\ecom-app-new\node_modules\react-native-reanimated\android\react-native-reanimated-67-hermes.aar

Configure project :react-native-vision-camera
VisionCamera: node_modules/ found at: C:\Users\user\source\repos\REACT-NATIVE\ecom-app-new\node_modules
Warning: The 'kotlin-android-extensions' Gradle plugin is deprecated. Please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to st
art working with View Binding (https://developer.android.com/topic/libraries/view-binding) and the 'kotlin-parcelize' plugin.
VisionCamera: Frame Processors are enabled! Building C++ part...

Task :vision-camera-code-scanner:generateDebugRFile FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.2/userguide/command_line_interface.html#sec:command_line_warnings
73 actionable tasks: 2 executed, 71 up-to-date
Warning: Mapping new ns http://schemas.android.com/repository/android/common/02 to old ns http://schemas.android.com/repository/android/common/01
Warning: Mapping new ns http://schemas.android.com/repository/android/generic/02 to old ns http://schemas.android.com/repository/android/generic/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/addon2/02 to old ns http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/addon2/03 to old ns http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/repository2/02 to old ns http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/repository2/03 to old ns http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/sys-img2/03 to old ns http://schemas.android.com/sdk/android/repo/sys-img2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns http://schemas.android.com/sdk/android/repo/sys-img2/01
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':vision-camera-code-scanner:generateDebugRFile'.

Could not resolve all files for configuration ':vision-camera-code-scanner:debugCompileClasspath'.
Failed to transform react-native-0.71.0-rc.0-debug.aar (com.facebook.react:react-native:0.71.0-rc.0) to match attributes {artifactType=android-symbol-with-pac
kage-name, com.android.build.api.attributes.BuildTypeAttr=debug, org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.libraryelements=a
ar, org.gradle.status=release, org.gradle.usage=java-api}.
Execution failed for JetifyTransform: C:\Users\user.gradle\caches\modules-2\files-2.1\com.facebook.react\react-native\0.71.0-rc.0\7a7f5a0af6ebd8eb94f7e
5f7495e9d9684b4f543\react-native-0.71.0-rc.0-debug.aar.
Java heap space

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 34s
error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081
Warning: Mapping new ns http://schemas.android.com/repository/android/common/02 to old ns http://schemas.android.com/repository/android/common/01
Warning: Mapping new ns http://schemas.android.com/repository/android/generic/02 to old ns http://schemas.android.com/repository/android/generic/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/addon2/02 to old ns http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/addon2/03 to old ns http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/repository2/02 to old ns http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/repository2/03 to old ns http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/sys-img2/03 to old ns http://schemas.android.com/sdk/android/repo/sys-img2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns http://schemas.android.com/sdk/android/repo/sys-img2/01
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':vision-camera-code-scanner:generateDebugRFile'.

Could not resolve all files for configuration ':vision-camera-code-scanner:debugCompileClasspath'.
Failed to transform react-native-0.71.0-rc.0-debug.aar (com.facebook.react:react-native:0.71.0-rc.0) to match attributes {artifactType=android-symbol-with-pac
kage-name, com.android.build.api.attributes.BuildTypeAttr=debug, org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.libraryelements=a
ar, org.gradle.status=release, org.gradle.usage=java-api}.
Execution failed for JetifyTransform: C:\Users\user.gradle\caches\modules-2\files-2.1\com.facebook.react\react-native\0.71.0-rc.0\7a7f5a0af6ebd8eb94f7e
5f7495e9d9684b4f543\react-native-0.71.0-rc.0-debug.aar.
Java heap space

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 34s
at makeError (C:\Users\user\source\repos\REACT-NATIVE\ecom-app-new\node_modules\execa\index.js:174:9)
at C:\Users\user\source\repos\REACT-NATIVE\ecom-app-new\node_modules\execa\index.js:278:16
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async runOnAllDevices (C:\Users\user\source\repos\REACT-NATIVE\ecom-app-new\node_modules\@react-native-community\cli-platform-android\build\commands\runA

ndroid\runOnAllDevices.js:109:5)
at async Command.handleAction (C:\Users\user\AppData\Roaming\npm\node_modules\react-native\node_modules@react-native-community\cli\build\index.js:142:9)
info Run CLI with --verbose flag for more details._
This is my Build.Gradle
_// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
ext {
buildToolsVersion = "31.0.0"
minSdkVersion = 21
compileSdkVersion = 31
targetSdkVersion = 31
ndkVersion = "21.4.7075529"
}
repositories {
google()
mavenCentral()
}
dependencies {
classpath("com.android.tools.build:gradle:4.2.2")
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url("$rootDir/../node_modules/react-native/android")
}
maven {
// Android JSC is installed from npm
url("$rootDir/../node_modules/jsc-android/dist")
}
mavenCentral {
// We don't want to fetch react-native from Maven Central as there are
// older versions over there.
content {
excludeGroup "com.facebook.react"
}
}
google()
maven { url 'https://www.jitpack.io' }
}
}_
and this is my PACKAGE.JSON
{
"name": "eApp",
"version": "0.0.1",
"private": true,
"scripts": {
"android": "react-native run-android",
"ios": "react-native run-ios",
"start": "react-native start",
"test": "jest",
"lint": "eslint ."
},
"dependencies": {
"@react-navigation/native": "^6.0.8",
"@react-navigation/stack": "^6.1.1",
"moti": "^0.21.0",
"react": "17.0.2",
"react-native": "0.67.3",
"react-native-gesture-handler": "^2.1.1",
"react-native-keyboard-aware-scroll-view": "^0.9.5",
"react-native-reanimated": "^2.13.0",
"react-native-safe-area-context": "^4.0.1",
"react-native-screens": "^3.12.0",
"react-native-shadow-2": "^7.0.6",
"react-native-svg": "^13.6.0",
"react-native-vision-camera": "^2.15.2",
"vision-camera-code-scanner": "^0.2.0"
},
"devDependencies": {
"@babel/core": "^7.12.9",
"@babel/runtime": "^7.12.5",
"@react-native-community/eslint-config": "^2.0.0",
"babel-jest": "^26.6.3",
"eslint": "7.14.0",
"jest": "^26.6.3",
"metro-react-native-babel-preset": "^0.66.2",
"react-test-renderer": "17.0.2"
},
"jest": {
"preset": "react-native"
}
}
Can anyone please help, How can I resolve this error ?

Try this https://www.youtube.com/watch?v=sE0MEyFA7E4&list=PLQhQEGkwKZUrempLnmxjt7ZCZJu1W3p2i&index=7 & https://www.youtube.com/watch?v=BFkIIIKgjnE&list=PLQhQEGkwKZUrempLnmxjt7ZCZJu1W3p2i&index=80

I also encountered the same problem.Is this project not maintained?


Duplicate Git repositories in Source Control

Issue Type: Bug
Pretty much what is says in the title. Only I can't even close them anymore. It's causing havok on Git Push.
VS Code version: Code 1.48.2 (a0479759d6e9ea56afa657e454193f72aef85bd0, 2020-08-25T10:13:11.295Z)
OS version: Windows_NT x64 10.0.19041

Any reason for not updating to the latest Stable release?
If you still have the problem after doing that, please use the command to reload with all extensions disabled, then retest.


Give more freedom to directories

in AppKernel everyone can change path to logs/cache dir, but in bundle we can only use var/app dir, why? In my situation I:

don't have app dir, but have app_, because have legacy App directory with classes
can't change cache directory to var/cache, because have problems with directory permissions.
don't use web directory to save static files, we have subdomain to access them...

Symfony is very flexible, but distribution bundle not... Can we solve this? Or only i and my project have problems like these? We can add dirs like:

assets_dir
cache_dir

The bundle supports the new directory structure if you use an uptodate version of the bundle. 3.x versions of symfony-standard are configuring the bundle to use the new system btw.

but if we don't use "canonical" structure of SF2/SF3? We transfer our project on SF3 Kernel and have some dirs in old places

@AmsTaFFix there is nothing hardcoding the SF3 structure in this bundle. There is only a bunch of necessary configuration settings to allow symfony-standard to use the new structure (we had to add a new configuration setting which was not necessary for SF2). You can use them to configure things for your own case.

@stof i'm sorry, i inspect the code and test how it works in my project, last question about assets directory? Can we have optional option for assets directory? like in assets:install command?

Hi @AmsTaFFix actually this bundle use the composer.json settings, isn't it enough to support your use case?

assets:install use the directory marked as symfony-web-dir in the extra config of the composer.json.
Feel free to reopen if you miss a feature to discuss this further.


3.x -Add CakePHP 3.8 branch to the test matrix.

Codecov Report

Merging #15 into 3.x will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##                 3.x       #15   +/-   ##
===========================================
  Coverage     100.00%   100.00%
  Complexity       196       196
===========================================
  Files              9         9
  Lines            574       574
===========================================
  Hits             574       574

Continue to review full report at Codecov.

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


Considerations on having more that one document in workspace in react/wrapper usecase

Considerations on having more that one document in workspace in react/wrapper usecase
We have the following usecase:

we want to user give the opportunity to edit one file in the webbrowser (react app)
in this files elements from other files should be referrable

Right now we do the following

we have customized main-brower to receive a (initial) message with that other files contents and then construct the language worker with a special Workspace Manager that know the files as builtin resources

This works fine until we want to exchange the to be edited file along with its other files in react.
If the component is not remounted, then the componentDidUpdate call wont reinit monaco as before and after we just have a worker
thus we cannot plugin a new worker
we currently circumvent this problem by passing a key to the component to force remount
i am thinking about what could be done to make this nicer or more generic

instead of using workspaceMgr and builtin files we could use lsp didOpen calls to open multiple files. if the protocol works fine they all should end up in the same ws and visibile to each other (did not test that yet), but this also would require a hook in the component or a prop to pass multiple resources

we at least could make the current approach more robust by adding a prop to force remount on componentDidUpdate

do you have more ideas or hints? Thanks

@cdietrich sorry, I forgot to answer this. Didn't do it immediately and zoom a week passed by.
First, I would look at the problem without considering react and think about how it could be realized directly.
You could create a RegisteredFileSystemProvider and register all your files to it (there is currently no examlple in this repo, but here: https://github.com/TypeFox/monaco-languageclient/blob/main/packages/examples/src/python/client/main.ts). Then you can use the uris to create the models for the editor. When you update the model in the editor, then the language server will get notified automatically. You require language client logic to identify links between files.
A good source of inspiration what actually can be done with the underlying monaco-vscode-api you get here: https://codingame.github.io/monaco-vscode-api/
and of course from the source here: https://github.com/CodinGame/monaco-vscode-api/tree/main/demo

hmmm i still cant wiggle my head around this.
isnt the RegisteredFileSystemProvider a pure client thing?

Then you can use the uris to create the models for the editor. When you update the model in the editor

does this mean i have to client.didOpen somehow manually? calling updateModelseems to swich the model displayed in the edior

in my current approach the didOpen does seem to work.
but with the wired non recycling of monaco and the wired recycling of the worker it feels a bit overshoot.
also the component does not really be subclassable in a nice way.
https://github.com/cdietrich/my-monaco-editor-react-example/tree/cd_referencingOtherFiles


Will invocations to actor lost if application crashes?

Hi there,
I'm curious about the actors implementation, my understanding is that calls to the same actor will be processed sequentially just like they're queued.
If multiple calls to the same actor are requested, let's say(R1, R2, R3...R5), if the application crashes somehow when running R1(ie. R1 processing is not finished), will R1~R5 be re-processed if the application recovers later?
Thanks

Aha it's not working in that way. Invocations of actors are made by HTTP requests, so:
R1, R2, R3....R5 are just http calls, and will be blocked if other requests are still running. So it's like this:
----------> time
start(R1) ... end(R1)
start(R2) ...... end(R2)
start(R3) ......... end(R3)
start(R4) ............ end(R4)
start(R5) ............... end(R5)
The requests itself are not saved,  if the application crashes, then nothing will happen.


only concat extramsg if nonempty

This prevents a stray extra space from appearing in the error message.

Would be nice to cover this with a test actually.
I might do so eventually, if you do not want to do it yourself.

Thank you!


[TACHYON-934] Made TachyonFileSystem methods throw better exceptions

https://tachyon.atlassian.net/browse/TACHYON-934
We were turning everything into an IOException, which can make it hard
for callers to determine what went wrong in an operation. So now the
TachyonFileSystem and related classes don't wrap exceptions in an
IOException.
Also the FileSystemMasterClient uses an exponential backoff retry,
rather than looping forever, before throwing an exception and exiting.
There are a lot of miscellaneous refactors for deprecated code and tests
to get this to compile.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/4733/
Test PASSed.

Thanks @manugoyal
For change of this size, could you link its JIRA (if it is not there yet, could you create one) here?
Thanks

Created a JIRA: https://tachyon.atlassian.net/browse/TACHYON-934

@manugoyal Could you reopen this PR to master please?

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/4850/
Test PASSed.


update bson version in readme

Version 0.3.0 of the package on crates.io had the bson version changed to 0.9.0, this results in errors if the user tries to pass documents created with a different version of the bson package.
relevant commits
https://github.com/mongodb-labs/mongo-rust-driver-prototype/commit/f513ef350677b2ad9e62325030b27e93802bd7f5
https://github.com/mongodb-labs/mongo-rust-driver-prototype/commit/89919c44e2f0b2b293140ec57c5a27bb13f50305

thank you! :)


Can't remove dialogic completely, and console keeps warning.

Once I run my scene, the console will warn me like below. About 12 warnings.
I have removed it from my res, and cancelled autoload, I even open the project.godot to manually delete contents of dialoic.
I have also open user documents to delete the dialogic folder.
It still warns me.
E 0:00:01:0838   load_source_code: Attempt to open script 'res://addons/dialogic/Resources/CharacterResourceLoader.gd' resulted in error 'File not found'.
<C++ Error>    Condition "err" is true. Returning: err
<C++ Source>   modules/gdscript/gdscript.cpp:1025 @ load_source_code()
E 0:00:01:0839   _load: Failed loading resource: res://addons/dialogic/Resources/CharacterResourceLoader.gd. Make sure resources have been imported by opening the project in the editor at least once.
<C++ Error>    Condition "found" is true. Returning: Ref()
<C++ Source>   core/io/resource_loader.cpp:274 @ _load()
E 0:00:01:0839   add_custom_resource_format_loader: Condition "res.is_null()" is true. Returning: false
<C++ Source>   core/io/resource_loader.cpp:1110 @ add_custom_resource_format_loader()

It might be the case that your local .godot/scene_groups_cache.cfg still has references to Dialogic.
Not sure if it affects stable Godot versions, but it happened to me using 4.3-dev3 and onwards.

On Mon, Apr 8, 2024 at 17:15 Davide Cortellucci @.***>
wrote:

It might be the case that your local .godot/scene_groups_cache.cfg still
has references to Dialogic.
Not sure if it affects stable Godot versions, but it happened to me using
4.3-dev3 and onwards.
—
Reply to this email directly, view it on GitHub
https://github.com/dialogic-godot/dialogic/issues/2166#issuecomment-2042257849,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGUCM7FFGG6INP4OZZQR7VTY4JN4DAVCNFSM6AAAAABF2OKOS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBSGI2TOOBUHE
.
 I manually delete reference in cache documents, and after
reload my project, the warning never show again. Thank you anyway, you can
turn off the issue, I forget it.
And your addon is really helpful, especially the smart phone example, but I
find it unsuitable for my project, so I give it up.

I'm glad you were able to remove Dialogic cleanly.
Thanks for trying our addon, I wish you the best with your future endeavours!


Update tutorials.socially.angular2.step_09.md

Just some minor grammatical corrections while reading through

Thank you!


#54  - Be compatible saga networks

Closing this issue as it will be resolved by https://github.com/minos-framework/minos-python/pull/92


Configurable share button.

Currently it share's from my account or at least references me.
cc @nomadkoala

It's not configurable... but it's better than nothing.


feat: add Branch and Zip methods to fluent interface

Codecov Report
Attention: Patch coverage is 88.46154% with 3 lines in your changes missing coverage. Please review.

Project coverage is 85.93%. Comparing base (7a09ade) to head (3ca8dc0).
Report is 3 commits behind head on main.

Files with missing lines
Patch %
Lines

Streamistry.Core/Fluent/BranchesBuilder.cs
71.42%
2 Missing :warning:

Streamistry.Core/Fluent/SinkBuilder.cs
0.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #81      +/-   ##
==========================================
- Coverage   85.96%   85.93%   -0.04%
==========================================
  Files          66       68       +2
  Lines         841      853      +12
  Branches      132      133       +1
==========================================
+ Hits          723      733      +10
- Misses         73       75       +2
  Partials       45       45

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Implicit inclusion of msbuild_directory is confusing and produces unexpected results

When testing external referencing of runfiles, the runfiles library uses the msbuid_library macro, which implicitly includes //:msbuild_directory, defined in BUILD.bazel.
//:BUILD.bazel, also includes packaging rules, which are not included as dotnet_rules_dependencies() which means the build failed because the repository was not known.
options are:

Keeping the implicit reference to msbuild_directory via the macro and:

explicitly declaring an msbuild_directory below that, and explicitly declaring a dependency on this new directory

it seems pretty silly to have to explicitly declare a dependency to avoid an implicit dependency, though that does keep with the functionality of MSBuild

refactoring //:BUILD.bazel so external repositories can reference it

It will be easy to forget about this and accidentally introduce incompatible things into BUILD.bazel

Removing the implicit reference and require an explicit dependency on any Directory.Build.* files.

This can be easily accomplished with a defaults.bzl file that has the dependency, which I think is much more readable.
This is much more bazel-like and straightforward to figure out what is happening.

this will cleanup #140 as well.


chore: bdd-spring-1576831295 to 0.0.1

chore: Promote bdd-spring-1576831295 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add multichan output model to test issues in build-spec

Hey @FynnBe,
I fixed a few issues related to new PyTorch and PIL versions here, that I would need to fix some dependencies.
These things are fixed now, but a lot of things are failing due to unrelated issues.
Could you have a look at bringing the tests up to speed again.

Superseded by #337


chore: promote jx3-demo1 to version 0.0.4

chore: promote jx3-demo1 to version 0.0.4
this commit will trigger a pipeline to generate the actual kubernetes resources to perform the promotion which will create a second commit on this Pull Request before it can merge

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@dockerpac: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

verify
ce989406079050fe60b03539010f004f2d48f44e
link
/test verify

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


iOS 13: Force touching an image will result in a crash

On the iOS 13 developer beta, force touching on an image will result in a crash.

Assertion failure in -[UIApplication _createStatusBarWithRequestedStyle:orientation:hidden:], /BuildRoot/Library/Caches/com.apple.xbs/Sources/UIKitCore/UIKit-3899.13.13/UIApplication.m:5240
Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'App called -statusBar or -statusBarWindow on UIApplication: this code must be changed as there's no longer a status bar or status bar window. Use the statusBarManager object on the window scene instead.'
libc++abi.dylib: terminating with uncaught exception of type NSException

Will be fixed when https://github.com/zhangao0086/DKPhotoGallery/pull/17 is merged

@flashspys Merged! Thanks all!


CSS discarded when page is loaded

Describe the bug
This issue is not occurring while running on the dev server, only when building then previewing. Also tested when deployed to Cloudflare Pages.
The CSS is downloaded by looking at the DevTools networking tab, even seemingly loaded for a split second, but is discarded when the page finishes loading.
The global CSS resides in __layout.svelte.
Reproduction
https://github.com/Desati-Solutions/ansarius
Logs
No response
System Info
npx: installed 1 in 1.701s

  System:
    OS: Windows 10 10.0.19042
    CPU: (8) x64 Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
    Memory: 11.70 GB / 31.94 GB
  Binaries:
    Node: 14.17.3 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.13 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 100.0.4896.60
    Edge: Spartan (44.19041.1266.0), Chromium (99.0.1150.55)
    Internet Explorer: 11.0.19041.1202
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.33
    @sveltejs/adapter-static: next => 1.0.0-next.29
    @sveltejs/kit: next => 1.0.0-next.303
    svelte: ^3.44.0 => 3.46.4

Severity
blocking all usage of SvelteKit
Additional Information
No response

Is there any reason to not just put the css in static/app.css and then use <link rel="stylesheet" href="app.css">?
Tried it and works as expected.

Is there any reason to not just put the css in static/app.css and then use <link rel="stylesheet" href="app.css">?
Tried it and works as expected.

Does that mean that you tried it as is and it did not work?
I will give what you suggested a try and see if it works.

I found the issue, apparently having the following in __layout.svelte breaks it:
<svelte:head>
	<meta name="robots" content="noindex nofollow" />
	<html lang="en" />
</svelte:head>

So it's a bad idea to specify svelte:head in __layout.svelte, but there was absolutely no indication of it. It worked fine under npm run dev but not when built and previewed.

this is somehow interesting, now I am curious

I found the issue, apparently having the following in __layout.svelte breaks it:
<svelte:head>
	<meta name="robots" content="noindex nofollow" />
	<html lang="en" />
</svelte:head>

So it's a bad idea to specify svelte:head in __layout.svelte, but there was absolutely no indication of it. It worked fine under npm run dev but not when built and previewed.

<html> inside svelte:head does not work.
Please provide a separate repository with a minimal reproduction. The history of the one you linked shows you've been changing it and it does not contain the head you posted above.
for the record: You should not use <style global> in __layout.svelte. Just add your css to the generated app.css.

We had a quick discussion about this as @dominikg raised it, and there are two things which we don't really expect to work here, which might be causing your issue:

the presence of a self closing html tag - if you close the html tag with no content, then you wouldn't expect any content to render
html tags aren't valid inside head tags, and svelte:head is ultimately deisgned to act like a head tag.

We had a quick discussion about this as @dominikg raised it, and there are two things which we don't really expect to work here, which might be causing your issue:

the presence of a self closing html tag - if you close the html tag without content, then you wouldn't expect any content to render
html tags aren't valid inside head tags, and svelte:head is ultimately deisgned to act like a head tag.

Indeed, it was cause  was put in svelte:head. Not sure how it got there.

I found the issue, apparently having the following in __layout.svelte breaks it:
<svelte:head>
	<meta name="robots" content="noindex nofollow" />
	<html lang="en" />
</svelte:head>

So it's a bad idea to specify svelte:head in __layout.svelte, but there was absolutely no indication of it. It worked fine under npm run dev but not when built and previewed.

<html> inside svelte:head does not work.
Please provide a separate repository with a minimal reproduction. The history of the one you linked shows you've been changing it and it does not contain the head you posted above.
for the record: You should not use <style global> in __layout.svelte. Just add your css to the generated app.css.

I have edited the issue and provided a new link to the reproduction.

There was no generated app.css when i created the project.

https://sveltekit.new (opens a fresh instance of the default starter template)
there is /src/app.css imported by /src/routes/__layout.svelte

I'm going to close this issue as adding <html/> into <head> would break regular html documents too and svelte:head wasn't designed to work for that. If you have questions about how to set the language for your page in sveltekit, open a discussion in this repo or find us on discord: https://svelte.dev/chat


Fix Parent / Child class argument ambiguity issue with MixedArgumentResolver

This PR updates the logic of the MixedArgumentResolver@prepareTypehintedArguments method to resolve an issue where a constructor asks for two typehinted arguments where one of the arguments is interchangeable with the other. A parent / child class relationship will cause this error.
See the original issue: behat/behat#1008
I have not added in any tests, as the unit tests were failing locally when I ran them on a fresh clone of master.
I have now added in a test case for the bug that I have fixed.

The  Scrutinizer rating is now stuck at B. It would be silly to even "simplify" this method, as there is already quite a superfluous chain of simple methods.

@glennmcewan I think the refactoring you made is good enough. Applying a complex design pattern like the visitor would make it over-engineered in my opinion.
The class is rated to B, because one of the method is B, particularly applyPredicateToTypehintedArguments(). If you take a look at the report, you can see that Total Lines is a bit high. Try to remove all the empty lines and see if Scrutinizer likes it.

@elvetemedve I agree, implementing the visitor pattern would be an unnecessary way of doing it, but I still feel like the refactoring I have done now is a bit excessive.
I don't know what Scrutinizer's rating algorithm is, but total lines of 26 in a low complexity method shouldn't mark it down to a B imo. I just had a quick test, and it didn't make a difference. I think removing the inner loop did the trick as that removes paths / complexity. Overkill imo, but if that makes the builds pass...
Anyway, Scrutinizer is now happy, Behat tests are written, I think this is ready :)

@glennmcewan I agree that number of lines should be okay as well as a nested foreach. Scrutinizer is too strict in this case. But it's not my call to decide. :)

Thank you very much for a great work! I did some very small refactoring and merged into master.


New case of  imposed by physical necessity §4.3.5 EGD

@danbalogh @arlogriffiths @ajaniak

During the reading of Khalimpur Plate BC88, I have encountered a situation for spaces imposed by physical necessity that, unless I am mistaken, is not reported in the Guide. Indeed the three first lines are interrupted by a long space due to the attachment point of the seal (see the attached photo). I suggest to encode the new type of space by something like <space type=“sealattachmentpoint” unit=“character” quantity=“18”/> but this proposition is maybe a bit too much long. Do you have any other suggestion? Can we add this case in the guide?
Thank you in advance for your help,
Amandine

Thanks, Amandine, for the nice illustration. There is also an earlier proposal of mine in an EGD comment, about possibly introducing a <space type="artwork"/>, which is somewhat similar. On the other hand, we don't want to over-complicate these spaces. I now propose the following:

To our already existing list of permitted types of space, we add "feature", covering engraved art (e.g. on a CP or a flat stone), relief art (e.g. on a sculpture base) and seals attached directly to a plate such as Amandine's example. The difference between "feature" and "defect" would be that a feature is a deliberately created artificial thing, whereas a fault is accidental or natural.
We explicitly forbid the use of @quantity and @unit for all spaces imposed by physical necessity, since our purpose in encoding such spaces is merely to record a disturbance that may have influenced the writing process; the number of characters that were impossible to write there is irrelevant. (At present, attributes are forbidden for binding holes and ascenders/descenders, but permitted for defects.) This would moreover allow me to simplify and shorten the section on imposed spaces, since there would be no need to discuss each type in detail, just to give the general instructions and list the permitted types with definitions.

Incidentally, forbidding quantity and unit for imposed spaces would leave the door open in case we wanted to switch the encoding of imposed spaces from <space/> to <milestone/> - the idea of using <space/> in such cases has met with some objections on the mailing lists for Indic texts and for EpiDoc.

Dear Dániel,
Thank for you reply. Sorry I don't think to read the comments before opening this issue, but it shows that the case has to be considered because it is not unique.
Your proposal seems to me relevant in that it distinguishes between an accidental, non-chosen physical constraint and a constraint due to the manufacture of the object (engraving, seal, sculpture). But in that case, maybe, the case "binding hole" could also be included in the manufacturing constraints (what you name "feature"), isn't it?
In any case, this distinction "natural constraint/manufacturing constraints" seems clear enough to me to be easily applied.
As for the mention of the length of the space, I don't know to what extent it is useful to give it or not. Giving the number of aksaras can possibly allow to evaluate the average number of aksaras per line, which can help in the case of a damaged plate...I confess I have no settled opinion on this point and maybe not enough experience in epigraphy to evaluate the relevance to mention or not these details.

Thanks for your thoughts on this. Indeed, perhaps "binding_hole" could be integrated into "feature", though because it is such a salient thing in almost all CPs, it is better kept separate.
I think anyone who wants to count the number of akṣaras per line and use that as a basis for further deductions (e.g. number of characters lost to damage) will always look at a facsimile to do so and not rely on just an edition.
Let's see what Arlo thinks.

I have no profound thoughts at this time. But Amandine's example reminds me of Bengal dedication inscriptions with a complex layout on their support (general, stone/metal statues) due to the complex morphology of the latter. In such cases, I suppose most encoders may feel it most natural to insert <milestone> tags into their lines of edition.
Yes, let's keep "binding_hole" (or was it "binding-hole"?) separate.
I am not very happy with "feature" (as a defect is also a feature) but I have no better alternative to offer.

@arlogriffiths, a complex layout involving more than one surface should certainly be encoded with milestones, gridlike or pagelike as the case may be. In that case, we use <milestone/> to identify where a particular surface begins vis-à-vis the text (just like the specialised milestones <lb/> and <pb/> are used to encode where a particular unit begins vis-à-vis the text. Text from one such milestone to the next is in the original written on the surface (or part thereof, i.e. line) specified in the milestone.
What we are talking about here are single surfaces where the text has a discontinuity for some reason. In these cases we currently use <space/> to encode the interruption itself, and not a particular surface (or part thereof) demarcated by the interruption. Thus, e.g. if you have text on two faces of a stela, you encode surface A at the beginning of each line and surface B at the point where each line runs across to the next face. This is different from the case of CP holes, ascenders, descenders, defects and, if we follow through with this, artificial features. In that case, if you have an interruption in a line, you don't create two tags (one to mark the beginning of the section of the text before the interruption, and another to mark the beginning of the text after the interruption), but only a single one (to mark the interruption itself).
Leaving that matter aside and coming back to the current point: you have not replied explicitly pro or con to the suggestions I made above. It seems to me that you tacitly agree with introducing a new @type of imposed space. Is that right? Do you also agree that we can make do with a single new type and do not need two (or more) new types for "artwork interrupting the text" and "seal attachment interrupting the text"? Can you also accept forbidding @quantity and @unit on all imposed spaces, thereby simplifying our encoding?
If it's "no" to any of the above, then let's continue the discussion and figure out a solution. If it's "yes" to all, I'll revise the EG accordingly. I'll try to think of a better token than "feature", but I don't have one at the moment and don't think anyone will have trouble with a little bit of ambiguity in that term when it is contrasted with "defect" (reminding me of "bug versus feature" in IT), so I guess it'll stay. Alternatively, we could decide to scrap "defect" and just use "feature" in the future, regardless of whether we are talking about an unintentional or intentional feature of the surface. But I would rather keep this distinction: it makes intuitive sense even if I can't think of any particular purpose why we would want it.


Column detection

Mania uses the X of objects to determine which column it goes down, they are a fixed distance apart (usually). during parsing of the hit objects you can sort the array by X position, then run through it and increment the column count for each higher value encountered.
As I have learned, this is not fullproof, some maps will occasionally not be uniform (typically older maps, which would have a compatible CircleSize property to determine columns anyway)

From what I've seen so far all maps which were created for osu!mania have their CircleSize set to the column count, this is confirmed by the osu!lazer code but not documented officially.  The linked file also contains a formula for calculating the column count if the beatmap isn't originally for mania.
In case you're arguing for non-mania map support: maniac doesn't support non-mania maps since their HitPoints section obviously follows another format and that'd require implementing (at least) something like this which I don't feel is worth the effort and complexity at the moment. Maybe when I get around to refactoring beatmap parsing as it's own standalone application.

This commit is correct, maps circle size occasionally doesn't match how many columns there are

Well yes, as I said earlier, if (rather, iff) the beatmap was not originally created for mania (in osu!lazer terms this means if !IsForCurrentRuleset) then the circle size does not determine the column count. In cases where the beatmap was originally created for mania circle size does determine the column count. (As an aside, in case you referred to the comment in the commit you linked, that comment is wrong, that's why I removed it.)
Since I forgot to ask this in my earlier comment, what's the purpose of this issue? (Please don't take that in an offensive way, genuine question.)

Closing this as part of the 1.x cleanup.


Optimize Meta Viewport for Mobile Responsiveness

Add the appropriate meta tag to the HTML head to ensure proper scaling and responsiveness on mobile devices ().

The meta viewport tag has been added to the HTML file to ensure proper scaling and responsiveness on mobile devices. The portfolio now adjusts correctly to different screen sizes.


Symbol specialization in auto_optimizer() never took effect.

The dict that was storing all the symbols, known_symbols, was emptied just after its creation. The efect was that the specialization never took effect.

I'm a bit confused, the change (now) seems to be the exact inverse of what it originally was. While I see that this line should be removed, shouldn't this have no effect on behavior whatsoever since it is effectively a dead (or succeeded) line of code?

I think the difference is because of the following loop (see file dace/transformation/auto/auto_optimize.py, line 650ff).
There on line 653 it is checked if the value v is a sympy.Integer and if so it tries to transform it into a Python int, in case this fails the symbol is ignored  (I am not sure why though), and will thus not enter known_symbols.
Therefore known_symbols will only contain Python float and int.
However, if known_symbols is first directly constructed, this transformation is not done, and the "offending" (in the sense of having type sympy.Integer which can not be transformed to int) symbols will remain inside the dict.
While the loop will replace all sympy.Integers that can be transformed to Python int with a corresponding Python int it will not remove the sympy.Integer for which this transformation fails and this probably causes the issues we are seeing.

I agree. Basically, if you only look at these two lines, it would seem that the reset should be removed (as initially proposed):
https://github.com/spcl/dace/blob/66913220ea600492db59cf8e536271b36c1554bd/dace/transformation/auto/auto_optimize.py#L649-L650
However, looking at the larger context, it becomes clear that the dict comprehension of the first initialization is a strict super set of the later filtering code:
https://github.com/spcl/dace/blob/66913220ea600492db59cf8e536271b36c1554bd/dace/transformation/auto/auto_optimize.py#L649-L659
And this is in line with the doc-string:
https://github.com/spcl/dace/blob/66913220ea600492db59cf8e536271b36c1554bd/dace/transformation/auto/auto_optimize.py#L559
So it seems like it's best to initialize empty and remove the redundant dict comprehension.


Send SIGTERM signal instead SIGINT

On OSX my processes just get killed if I use SIGTERM instead SIGINT. It's also logged Sending SIGTERM to other processes so I believe this is the signal supposed to be used.

Thanks

Could you confirm that this works by installing 3.0.0-dev version: npm i -g<EMAIL_ADDRESS>?

Hi @kimmobrunfeldt. I'm without a OSX to test, but a friend that have one just confirmed to me.


⚠ Bofrost.lu has degraded performance

In 934853f, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1159 ms

Resolved: Bofrost.lu performance has improved in 371da5d after 19 minutes.


v2 roadmap

react-query/core
List of tickets in react-query V4 (not finalized): https://github.com/tannerlinsley/react-query/issues?q=is%3Aissue+label%3Av4+is%3Aclosed

[x] https://github.com/tannerlinsley/react-query/pull/2988
[x] https://github.com/tannerlinsley/react-query/pull/3071
[x] Update docs

[x] https://github.com/tannerlinsley/react-query/pull/3006
[x] https://github.com/tannerlinsley/react-query/pull/2996
[x] https://github.com/tannerlinsley/react-query/pull/2937
[x] https://github.com/tannerlinsley/react-query/pull/2938
[x] https://github.com/tannerlinsley/react-query/pull/2963
[x] https://github.com/tannerlinsley/react-query/pull/2969
[x] https://github.com/tannerlinsley/react-query/pull/3223
[x] https://github.com/tannerlinsley/react-query/pull/3271

vue-query

[x] hooks should wrap primitives as refs, but return functions as-is
#123
[x] create wrappers for QueryClient, QueryCache, MutationCache etc, so parameters could be passed as refs and would be automatically unwrapped
#110
[x] migrate devtools as a plugin to official vue devtools #155
[x] nuxt 3 integration
[ ] expose persistance plugins

misc

[x] Create migration to v2 page and notify about all noticeable changes in react-query/core and vue-query
[ ] Consider codemods?

v2.0.0-alpha.1

v2.0.0-alpha.1

Thank you for this!
Where can we find types like QueryFunctionContext, UseMutationResult, etc. that can be imported in vue-query/types  before?

@DamianOsipiuk  thank you for your great work!

@wobsoriano So, everything should be re-exported with v2.0.0-alpha.3 - in case some types are still missing, please open a ticket.

@DamianOsipiuk migrated one of my pet projects and all exported types are there now. Thanks!

Happy to see that first beta appeared 🎉
Do you have any predictions on release date?

@DamianOsipiuk Could the type narrowing for initialData be included for v2?
https://github.com/TanStack/query/issues/3310

@DamianOsipiuk Could the type narrowing for initialData be included for v2? TanStack/query#3310

Yes, all the changes introduced in v4 of react-query will be backported.

Happy to see that first beta appeared 🎉 Do you have any predictions on release date?

Currently i'm trying to stabilize ESM support in @tanstack/query. When it will be done, i would have to go trough and backport all the changes that were done from the beta release. Probably then we could do a v2 release.
This package will be migrated as a part of https://github.com/TanStack/query. This will in turn bump the version to v4 to be in line the the core.
Question to the users. Do you prefer to
:one: Get v2 release sooner, followed up by v4 release under a different name (@tanstack/vue-query)
:two: Wait a little bit more for v4 directly.

Almost there... https://github.com/TanStack/query/pull/4254 🚀

Appreciate your effort @DamianOsipiuk !

@tanstack/vue-query is now official. Thanks for the patience!


Cards sharing a ruling

Some cards share a ruling, for instance:
"7","Abactor is an action in its own right. Kyoko would not steal blood from a vampire by playing Abactor.","https://groups.google.com/d/msg/rec.games.trading-cards.jyhad/-hy9E1u2t_o/CPU8rltzhesJ","2009-06-06","LSJ"
Should be associated to Abactor and Kyoko.
But it requires moving each ruling to a different "table" and adding references instead of the ruling itself, making it more difficult to maintain.

I agree, for now rulings are just duplicated under the two cards.
I think many rulings are easier to read if you adapt their wording to the appropriate card. For your example, we could put the ruling under Kyoto only, or under both with slightly different wordings, like:
Kyoko:
- "Cannot chose to steal blood from a vampire when using another hunt action (eg. {Abactor})."
Abactor:

"The blood comes from the blood bank even if the vampire has an alternate hunt action with another source for the blood (eg. {Kyoko})"

On the other hand, many rulings are duplicated with the exact same wording on multiple cards. The most striking examples are the "general rulings" of the VEKN website. Still, even in this case adaptations can be made card by card, which is useful for readability.
For now, I'm leaning on the side of keeping the cards as keys. It's a close call though. Anyone let me know if you feel strongly we should change that or if you have other arguments.

Is {whatever} the syntax for a link towards the card named "whatever"?

Many two files are required:
The existing file
Another "general ruling files" that could be linked to cards.
For instance:
Action Continues As If Unblocked:
    - If an effect continues a blocked action "as if unblocked", then all action modifiers and reaction cards, including stealth and Dawn Operation or Wake with Evening's Freshness, are still in effect. [RTR 19941109] => 100771:Form of Mist / 101222:Mirror Image

I like this idea ! I think this would settle the issue nicely.
I'll work on a PR proposal.


Add feature : read/write avro file format

I need to read and write to an hdfs cluster where the format of files is "avro"
Is there any way to get arround the standard functions to do it ?
It would be great to have a spark_read_avro and spark_write_avro which are also standard format in hdfs environments.

I've started to work as extension of sparklyr https://github.com/chezou/sparkavro

I've finished the implementation of the first version of sparkavro.
https://github.com/chezou/sparkavro
If you have any issue please file in my github repo.

@javierluraschi Do you have a plan to include spark-avro? Or, could you add my extension into the document? After that, I think it would be time to close this issue.

Hi @chezou, thanks for your extension.  I just added it to the list in the Extensions page as you requested: http://spark.rstudio.com/extensions.html (cc: @javierluraschi )

Thanks @edgararuiz !

@chezou Thanks! Really neat extension!


Update jekyll url to https

Description
Fixes #1001

Override jekyll url parameter with https address.
I tested locally, and it seems that site.url still resolves to localhost when running a local jekyll serve, which is great, and means the site is getting https://docs.projectcalico.org on the real site, and http://localhost when run locally.
Todos

[x] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Copied from issue #1001 (which is closed as a dup):

Curl failed during calico vagrant installations.
Current Behavior
For instance if I follow the instructions at https://docs.projectcalico.org/v2.4/getting-started/kubernetes/installation/vagrant/
curl -O http://docs.projectcalico.org/v2.4/getting-started/kubernetes/installation/vagrant/Vagrantfile
curl -O http://docs.projectcalico.org/v2.4/getting-started/kubernetes/installation/vagrant/master-config.yaml
curl -O http://docs.projectcalico.org/v2.4/getting-started/kubernetes/installation/vagrant/node-config.yaml

curl returns 301 Moved Permanently
Possible Solution
Modify documents from curl -O http to curl -O https or setup redirect.
Your Environment

Calico version 2.4


Where to call setCustomerIdAndLogSession() or setCustomerId()

I want to set CUID in my app via this SDK. for this I need to call init() first then wait then start() function as per mention in official document. but in this SDK there is no such method like start()  so how would I set CUID ?

I am facing this same issue as well as i am unable to complete the steps described in step 4 here integrating with mixpanel

I am facing this same issue as well as i am unable to complete the steps described in step 4 here integrating with mixpanel

I'm placing flow which I follow as per AppsFlyer care team:
makeATTPermission();
final AppsFlyerOptions options = AppsFlyerOptions(
afDevKey: DotEnv().env["DEV_KEY"],
appId: "12345678",
showDebug: true,
timeToWaitForATTUserAuthorization: 60
);
ApiUtils.appsflyerSdk = AppsflyerSdk(options);
// setCustomerId if you have .....otherwise set after when you got
ApiUtils.appsflyerSdk.setCustomerUserId();
await ApiUtils.appsflyerSdk.initSdk(
registerConversionDataCallback: true,
registerOnAppOpenAttributionCallback: true,
registerOnDeepLinkingCallback: true,
)
//Then you can set customerId once the user login or available
ApiUtils.appsflyerSdk.setCustomerUserId();
check this if it needfull for you.

I am facing this same issue as well as i am unable to complete the steps described in step 4 here integrating with mixpanel

I'm placing flow which I follow as per AppsFlyer care team:
makeATTPermission(); final AppsFlyerOptions options = AppsFlyerOptions( afDevKey: DotEnv().env["DEV_KEY"], appId: "12345678", showDebug: true, timeToWaitForATTUserAuthorization: 60 ); ApiUtils.appsflyerSdk = AppsflyerSdk(options); // setCustomerId if you have .....otherwise set after when you got ApiUtils.appsflyerSdk.setCustomerUserId(); await ApiUtils.appsflyerSdk.initSdk( registerConversionDataCallback: true, registerOnAppOpenAttributionCallback: true, registerOnDeepLinkingCallback: true, )
//Then you can set customerId once the user login or available ApiUtils.appsflyerSdk.setCustomerUserId();
check this if it needfull for you.

The issue i am having is integrating it with mixpanel......there is no start() actin on appflyer

My Apologies for misunderstanding....but, can you share me that how much method you can use from appsflyer right now?
because .initSdk is enough to start sdk.


bpftop: 0.4.0 -> 0.4.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/Netflix/bpftop/releases.
meta.description for bpftop is: A dynamic real-time view of running eBPF programs
meta.homepage for bpftop is: https://github.com/Netflix/bpftop
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.4.1 with grep in /nix/store/v71vqri0iz4spy70f5n86aa8n3vxvnyn-bpftop-0.4.1
found 0.4.1 in filename of file in /nix/store/v71vqri0iz4spy70f5n86aa8n3vxvnyn-bpftop-0.4.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
bpftop

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/v71vqri0iz4spy70f5n86aa8n3vxvnyn-bpftop-0.4.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bpftop https://github.com/r-ryantm/nixpkgs/archive/3c8ecd4b898299c3c630ac320ef09508a971960f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/3c8ecd4b898299c3c630ac320ef09508a971960f#bpftop

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/v71vqri0iz4spy70f5n86aa8n3vxvnyn-bpftop-0.4.1
ls -la /nix/store/v71vqri0iz4spy70f5n86aa8n3vxvnyn-bpftop-0.4.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

bpftop

Maintainer pings
cc @0x4A6F @mfrw for testing.

@ofborg eval


OKCoin min to sell is 0.01BTC

Hi, I see OKCoin min to sell is 0.01BTC. If I only have 25$, how I can take an order?

Then you can't.


merge master-qa

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: ClaudeROSSI:white_check_mark: LucasBrazi06:x: AlixHYou have signed the CLA already but the status is still pending? Let us recheck it.


Script deployment

Mostly just installing all the libraries + compiling assets
Maybe also perform some production optimisations too
(warmup cache, precompile autoloader, .htaccess routes?)

Created build script, will move production stuff to another ticket


DOC: <Issue related to /how_to_guides/tracing/log_llm_trace>

Hi there, I'm using RunTree and want to log the cost, I figured out how to add the token count but not the cost. Can someone guide me please?
PS: The provider openai and gpt-4 are just values to test with. I figured if it works for them it'll work for the other custom models I'm using like Command-R
Reference: https://docs.smith.langchain.com/how_to_guides/tracing/log_llm_trace#manually-provide-token-counts
   trace.end({
      data,
      usage_metadata: {
        input_tokens: 27,
        output_tokens: 13,
        total_tokens: 40,
        total_cost: ((inCost ?? 0) + (outCost ?? 0)),
        prompt_cost: inCost,
        completion_cost: outCost,
      },
      ls_provider: 'openai',
      ls_model_name: 'gpt-4',
    });

Hi there! Cost is added in the UI via the models page


For swift compatibility moved LE_DEBUG_LOGS to a LELog instance property

On Swift it is not possible to use the #define macro, instead a global constant is used, because of this tiny but important difference it is not possible to "override" the LE_DEBUG_LOGS to disable debugging.
I purpose a simple change: move this option to a property on LELog instance.

bump :)

I think this PR is good
@vilda, please accept this PR.

+1 this would be useful

Thanks a lot @joelrfcosta


e2 docs custom camera

why when using it there in a huge input delay for looking around? like say i use my mouse to look left it takes it 4 sec or so to respond despite using either run on tick or interval. any way to make this better?

Depends on your ping to the server. High ping while make the delay longer.

Better to use cam controller or starfall

Depends on your ping to the server. High ping while make the delay longer.

ok well i tried in SP and its just the same there so i dont think thats right

The camera controller can handle the majority of situations and it doesn't have any delay. In wiremod, that's your only delay-free option. If that isn't enough, you will have to look outside of wiremod, such as starfall, as was already suggested.
The E2 camera functions have a delay because E2 is serverside and rendering is clientside. By definition it can never be instant.
This github is for bug reports. If you have questions that aren't about bugs, go to the discord at https://discord.gg/H8UKY3Y

Depends on your ping to the server. High ping while make the delay longer.

ok well i tried in SP and its just the same there so i dont think thats right

There shouldn't be delay unless something is wrong with your code.


[Core] Doc: PairRDDFunctions.reduceByKey should be stated as requiring a commutative binary op

According to http://stackoverflow.com/questions/35205107/spark-difference-of-semantics-between-reduce-and-reducebykey , PairRDDFunctions.reduceByKey requires, just like RDD.reduce, an associative AND commutative binary operator.
This wasn't stated in the docs.

Can one of the admins verify this patch?

That's fine though this is pretty much by definition for reduce.

@srowen I agree but the difference between the documentation of reduce and reduceByKey seemed to imply a difference in behaviour.

Yea we should make them consistent. Are there more inconsistencies you find?

Yeah I think there similar statements about an 'associative' operation that really mean 'associative and commutative'. There are more occurrences in this file. There are some in Accumulator.scala, JavaPairRDD.scala, JavaRDDLike.scala, JavaDStreamLike.scala, JavaPairDStream.scala, DStream.scala, PairDStreamFunctions.scala, rdd.py, dstream.py, pairRDD.R. In each

@YPares are you going to update this or should I continue it?

@srowen Oh, sorry, I was waiting a bit to see if I found other inconsistencies.
But none came to mind, so yes you may continue it.

See my previous message @YPares -- I think I found all the other ones. You're welcome to address them so we can merge your PR, but I can do it too.

You can close this @YPares ; I created https://github.com/apache/spark/pull/11217


CLI QOL Improvements

Tried to use the new CLI a bit this morning.  Feedback from that experience.

[ ] You have to invoke the CLI with python -m zipline <stuff>, which is an annoying amount of typing.  We could register an entrypoint in our setup.py so that you can just do zipline <stuff>.  In my experience, this is how most libraries bundle command line interfaces (c.f., for example, gunicorn, ipython or jupyter).  Click also has support for generating completion wrappers for entrypoints registered via console_scripts.
[ ] Related to the above, errors in the CLI show a filename of __main__.py in the usage string.
[ ] The quandl bundle isn't registered because we never import it.  This is fixed on https://github.com/quantopian/zipline/pull/1178/files, but invoking python -m zipline ingest -b quandl crashes for me in fetch_symbol_metadata_frame.
[ ] You need to pass the name of a bundle to zipline ingest or zipline run, but there's no way to see what bundles are available.  A zipline bundles entrypoint would be nice for this, which could also be used to show the dates for which you have bundles available.

cc @richafrank

👍

Stack trace for the failures I'm seeing on @llllllllll's latest trying to run the quandl bundle:
(qexec) [~/quantopian/qexec/zipline_repo]@(quantopian-quandl:fc04cd0819)$ python -m zipline ingest -b quandl
Downloading WIKI metadata:   [------------------------------------]
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/home/ssanderson/quantopian/qexec/zipline_repo/zipline/__main__.py", line 345, in <module>
    cli()
  File "/home/ssanderson/.virtualenvs/qexec/local/lib/python2.7/site-packages/click/core.py", line 664, in __call__
    return self.main(*args, **kwargs)
  File "/home/ssanderson/.virtualenvs/qexec/local/lib/python2.7/site-packages/click/core.py", line 644, in main
    rv = self.invoke(ctx)
  File "/home/ssanderson/.virtualenvs/qexec/local/lib/python2.7/site-packages/click/core.py", line 991, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/ssanderson/.virtualenvs/qexec/local/lib/python2.7/site-packages/click/core.py", line 837, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/ssanderson/.virtualenvs/qexec/local/lib/python2.7/site-packages/click/core.py", line 464, in invoke
    return callback(*args, **kwargs)
  File "/home/ssanderson/quantopian/qexec/zipline_repo/zipline/__main__.py", line 298, in ingest
    show_progress,
  File "zipline/data/bundles/core.py", line 342, in ingest
    pth.data_path([name, timestr], environ=environ),
  File "zipline/data/bundles/quandl.py", line 280, in quandl_bundle
    show_progress=show_progress,
  File "zipline/data/bundles/quandl.py", line 112, in fetch_symbol_metadata_frame
    data = pd.concat(blocks, ignore_index=True).rename(columns={
  File "/home/ssanderson/.virtualenvs/qexec/local/lib/python2.7/site-packages/pandas/tools/merge.py", line 754, in concat
    copy=copy)
  File "/home/ssanderson/.virtualenvs/qexec/local/lib/python2.7/site-packages/pandas/tools/merge.py", line 785, in __init__
    objs = [obj for obj in objs if obj is not None ]
  File "/home/ssanderson/.virtualenvs/qexec/local/lib/python2.7/site-packages/click/_termui_impl.py", line 240, in next
    rv = next(self.iter)
  File "zipline/data/bundles/quandl.py", line 62, in _fetch_raw_metadata
    if raw.empty:
AttributeError: 'list' object has no attribute 'empty'

this is a really funny issue. In python 2 when we do raw = cache[key] that always returns a list for the first key because the bytes happen to not crash the msgpack parser and it is treating the filepath (which is bytes in py2) as msgpack data...

fixed with #1178


will make the Numeral formatting?

Yeah I could take a look at it and try. Unfortunately not this weekend as I'm away from computer. I'll get back to you.

Tks man, I will wait ( I need a money format, when type he put the brazilian mask) 123.123.323,33
tks

Hei man, Did you see that problem for me? tks

Sorry I have been too busy with both work and personal things. I'll try again tomorrow.

I'm very sorry this took me so long. v.1.3 available.

Tks man.
Its possible to use one text field to have more than one format, depends on my user choices? Sample: I have one text field  and 2 radiobutton, when my user select the first radio my format will be ###.###.###-## and if my user click in second radio the format will be ##.###.###/####-##. and my user can change between  one or other any time
tks

Currrently no. I would need to implement a setFormat method to the formatter. I'm not sure if cleave.js even supports having format ##.###.###/####-## where the # is limited for numbers only. I would have to check. Could you comment on #5 if you need more specifics.


[stdlib] Fix availability of Dictionary’s bulk-loading initializer

These entry points were introduced in https://github.com/apple/swift/pull/21235. Adding @_alwaysEmitIntoClient makes them available in all OS versions.
rdar://problem/49404177

@swift-ci smoke test


Windows Defender detects Ubuntu 16 nslookup as Trojan

Your Windows build number:
Microsoft Windows [Version 10.0.18363.535]

What's wrong / what should be happening instead:
Defender detects rootfs\usr\bin\nslookup inside of WSL Ubuntu 16 as Trojan:AndroidOS/BoxerSms or Trojan:AndroidOS/AndroRat. I don't think that should happen?

Here's a report for nslookup https://www.virustotal.com/gui/file/d91421c9ba7d507cda9efe8464b0dd3bfe9a31fea22e3006380a9451e35c9975/detection

Can you please report back:

Your Windows Defender version
The version of dnsutils you have installed. $ dpkg -s dnsutils | grep '^Version:'

I am on 1.307.504 and dnsutils 9.10.3.dfsg.P4-8ubuntu1.15 and I am unable to reproduce.
You can submit these false positives to Windows Security Intelligence.
I went ahead and filed a report on this. Submission numbers 59102dd8-a63d-466d-92da-441b57021db2 and  fca6a9a7-01e9-4226-b7e4-c8330325b0e3.

Windows Defender (Security Intelligence) version: 1.307.557.0
dnsutils version 1:9.10.3.dfsg.P4-8ubuntu1.14

Thanks, also submitted (hopefully) false positives to Windows Security Intelligene. Will keep this updated if I hear anything back from there.

I see that nslookup was detected as a malware Trojan:AndroidOS/BoxerSms at the Windows Security Intelligence submission too. However, nsupdate is clean there.

This is the response I got back from submissions:
We have removed the detection.  Please follow the steps below to clear cached detection and obtain the latest malware definitions.

     1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender
     2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures”
     3. Run "MpCmdRun.exe -SignatureUpdate"

Alternatively, the latest definition is available for download here: https://www.microsoft.com/en-us/wdsi/definitions

Thank you for contacting Microsoft.

However, I failed to follow these instructions:
c:\Program Files\Windows Defender>MpCmdRun.exe -removedefinitions -dynamicsignatures

Service Version: 4.18.1911.3
Engine Version: 1.1.16600.7
AntiSpyware Signature Version: 1.307.577.0
AntiVirus Signature Version: 1.307.577.0

Starting Dynamic Signature removal.Failed! Error 0x80070005

Service Version: 4.18.1911.3
Engine Version: 1.1.16600.7
AntiSpyware Signature Version: 1.307.577.0
AntiVirus Signature Version: 1.307.577.0
CmdTool: Failed with hr = 0x80070005. Check C:\Users\jarm0\AppData\Local\Temp\MpCmdRun.log for more information

In log file this is shown:
-------------------------------------------------------------------------------------
MpCmdRun: Command Line: MpCmdRun.exe  -removedefinitions -dynamicsignatures
 Start Time: E dets 16 2019 20:55:12

MpEnsureProcessMitigationPolicy: hr = 0x1
Start: MpRemoveDefinitions(0)
ERROR: MpRollbackSignature failed with hr=80070005
MpCmdRun: End Time: E dets 16 2019 20:55:12
-------------------------------------------------------------------------------------

Any ideas how to continue?

I would try manually installing the new definitions.

Closing this since threats got neutralized.


Can I disable the RDS snapshot creation before stopping it

Hello
As I understand RDS snapshot is taken before stopping it ?
May I know can we disable this feature and how
Is there a flag out of box ?

Hi,
The current version always makes the snapshot for a stoped RDS instance.We might add this as an option int he schedule in a next release. For now you can open the Scheduler Lambda function the the Lambda console. In the source tree on the left side of the code window, navigate to the schedulers module and open the rds_service.py file. On line 337 you can remove the DBSnapshotIdentifier in the call to stop_db_instance_with_retries.
     client.stop_db_instance_with_retries(DBInstanceIdentifier=inst.id, DBSnapshotIdentifier=snapshot_name)

Thanks this helps.


Update crypto lib dependency

Current dependencies on/for this PR:

main

PR #33   👈

This stack of pull requests is managed by Graphite.

Merge activity

Dec 15, 2:47 PM: @@zhenlu merged this pull request with Graphite.


How can I ignore the failed partial to ensure that index.html is successfully generated

Thanks for this project, it's great, but I have some problems and need help.
I have several hundred markdown snippets, scattered in nested markdown using <%= partial "generated-snippetsapihttp-request" %> . The error of any one of the fragments during construction will cause the final generation of index.html to fail. How can I ignore the failed partial to ensure that index.html is successfully generated.
Example:
index.html.md.erb
# Introduction
Blah
...
<%= partial "includes/master" %>

# Kittens
...

and
includes/master.md.erb
<%= partial "includes/snippets1" %>
<%= partial "includes/snippets2" %>
<%= partial "includes/snippets3" %>

if <%= partial "includes/snippets2" %> build error:
Will appear: error  build/index.html;
I expect: create  build/index.html.

好吧，我修改了slate目录下的config.rb 其中一部分内容，以使得在出错的时候提示但并不中断整个文档，以下是我的操作：

拷贝 config.rb 并修改其中的：

helpers do
  require './lib/toc_data.rb'
end

to
helpers do
  require './lib/toc_data.rb'

  def partial(template, options = {}, &block)
    begin
      super(template, options, &block)
    rescue
      "<aside class='warning'>文件引入失败: #{$!}</aside>"
    end
  end
end

添加挂载文件：
VolumeBind: $(PWD)/config.rb:/srv/slate/config.rb


Is there a newer version of Run1CPUTimes.ipynb

@sethdigel I was trying to get a list of obsHistIds  of failed phosim runs for the light curve analysis, and was using the csv file mentioned in Run1CPUTime.ipynb. However this seems to be out of sync with the obsHistID values I am checking. For example, it seems obsHistID 230 shows up in the light curves, but in the phosim failures (runlimit==1) of the csv file. Should I be using a newer version of that file?

Ah.  Yes, that iPython notebook and the csv file date to the Hack day after the spring DESC meeting, at which time that particular visit had not finished (I think because the host running it had a problem).  I am just realizing that the pull request I made in May to merge in CPU time predictor code, and a complete metadata, file is still outstanding.  Jim had pointed out some pylint warnings that I missed at the time. I'll get on that.  In the issue/186/... branch the file is in the data directory.  Here's a link.
https://github.com/DarkEnergyScienceCollaboration/Twinkles/blob/issue/186/cpu_time_predictor/data/run1_metadata_v6.csv

Thanks! @sethdigel


Update to correct Ruby warnings

There is no functionality change. This is just to remove warnings thrown by Ruby.

The failures in Travis are due to active support 4.2 being used.


When typing or deleting really fast $apply already in progress

When I type or delete really fast it has the following error repeated.
[$rootScope:inprog] $apply already in progress http://errors.angularjs.org/1.2.27/$rootScope/inprog?p0=%24apply

Change line 188 to $scope.$applyAsync( function () { ....


Fix user defined preprocess function missing prediction issue

Description

When users use self defined preprocess scripts to process inputs, there'll be missing predictions for all inputs in the list except the first one.
To test multi-modal case, added default multi-modal preprocess function.

Issues Resolved
https://github.com/opensearch-project/ml-commons/issues/2417
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Suggest not merge multiple things in one PR. That makes it hard to rollback/backport


Greenkeeper/handlebars 4.4.5

:tada: This PR is included in version 3.1.9 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix calculation of required ventilation rate

calc_qv_req() in functions and in thermal_loads needs to be fixed.
if - else-statement does not make sense.

Closed with pull request #255


add option to allow duplicate PerformanceCounters instance names

By default, Influx-Capacitor will append "#n" (where n is an incrementing integer) to the end of a PerformanceCounter instance name if it detects that there is another with the same name. To disable this functionality, you simply add AllowDuplicateInstanceNames="true" to a CounterGroup in the XML configuration.

Nice feature!

Thanks! I use it in conjunction with the Filter/Replacement feature as a quick-and-dirty way of aggregating all vCPU instances per Hyper-V virtual machine.


User-controllable thread pool limits for parallel target to @vectorize and @guvectorize

(As requested on the numba-users mailing list.)
Right now we always assume the number of threads for the parallel target is equal to the number of CPUs.  There are plenty of situations where this is not desirable (multiple processes, etc), and so it is important to have some mechanism to limit the number of threads.
At a minimum, it would make sense to check the value of OMP_NUM_THREADS at startup, in order to mimic the behavior of other parallel libraries like MKL.  We don't actually use OpenMP's thread pool (though maybe we could someday), but this variable is at least somewhat well known to users who want to control the number of threads.
We may also want an API in Numba to change the number of threads as well.

Environment variable implemented in https://github.com/numba/numba/pull/1932.

Fixed by #1932.  (We might further expand things to allow control per call as well.)

@seibert I agree it would be good to allow control per call; it's also worth noting that recently (at least in Numba 0.34), the thread pool is initialized as soon as you import a module that uses numba.vectorize(target='parallel') - even if the decorated function is never called.  That's surprising.

For reference, #2713 is to make the number of threads controllable at runtime.

OMP_NUM_THREADS is a very common way of setting the level of thread parallelism in a program. How do people feel about letting numba check this upon import as well? NUMBA_NUM_THREADS would of course take precedent if set.


FIREBREAK: Investigate Automatic Conversion from CircleCI -> GitHub Actions

Background
We are currently using a large amount of credits across our CircleCI projects. This ticket is to investigate
Questions / Assumptions

Can we directly translate CircleCI workflow to GitHub action workflows?
How many of the projects on CircleCI are required to be private?
What are the cost implications of moving to GitHub Actions (cost/effort)?
Users may be reluctant to move.
Why are we using CircleCI in the first place?

Tasklist

[x] Identify the most computationally intensive CircleCI projects
[ ] Contact project owners to understand reasons for using CircleCI
[x] Create an example GitHub Action converted from a CircleCI pipeline
[x] Investigate ways to automate the conversion

What hypothesis do we want to test?/What do we want to learn?
Can we automate the conversion of CircleCI workflows to GitHub Actions?
Definition of done

[ ] Firebreak finding documented appropriately
[ ] Demo completed
[ ] Decision made on whether to progress Firebreak work
[ ] Does next steps require User Research?
[ ] Firebreak next step Issues created
[ ] New Issues referenced in this story before closure

The GitHub Actions Importer seems to be the most promising way of analysing, forecasting and automating the conversion of our CircleCI pipelines.

A report from the GitHub Actions Importer tool with an audit of our migration potential:
Audit summary
Summary for CircleCI instance

GitHub Actions Importer version: 1.3.22081 (ff41350a9d6afd71f38535f23e39fff593ed049c)
Performed at: 7/23/24 at 12:31

Pipelines
Total: 505

Successful: 69 (13%)
Partially successful: 340 (67%)
Unsupported: 92 (18%)
Failed: 4 (0%)

Job types
Supported: 412 (81%)

2.1: 410
2: 2

Unsupported: 93 (18%)

YAML: 92
2.1: 1

Build steps
Total: 18938
Known: 15308 (80%)
Unknown: 3154 (16%)
Unsupported: 476 (2%)

setup_remote_docker: 476

Actions: 17497
Triggers
Total: 1934
Known: 1446 (74%)

parameters: 768
cron: 488
push: 190

Unsupported: 488 (25%)

filters: 488

Actions: 1446

workflow_dispatch: 768
schedule: 488
push: 190

Environment
Total: 0
Actions: 10675
Other
Total: 328
Known: 315 (96%)

working_directory: 251
docker: 64

Unsupported: 13 (3%)

shell: 13

Actions: 30373
Manual tasks
Total: 1230
Secrets: 1230

${{ secrets.AWS_ACCESS_KEY_ID }}: 199
${{ secrets.AWS_SECRET_ACCESS_KEY }}: 199
${{ secrets.CIRCLE_CI_SSH_KEY }}: 140
${{ secrets.CIRCLE_CI_KNOWN_HOSTS }}: 140
${{ secrets.AWS_ACCESS_KEY_ID_ENG }}: 105
${{ secrets.AWS_SECRET_ACCESS_KEY_ENG }}: 105
${{ secrets.AWS_KEY_ID }}: 167
${{ secrets.AWS_SECRET_KEY }}: 167
${{ secrets.AWS_ACCESS_KEY_ID_PREPROD }}: 3
${{ secrets.AWS_SECRET_ACCESS_KEY_PREPROD }}: 3
${{ secrets.AWS_ACCESS_KEY_ID_PROD }}: 1
${{ secrets.AWS_SECRET_ACCESS_KEY_PROD }}: 1

Here's the output for the moj-analytical-services organisation on CircleCI:
Audit summary
Summary for CircleCI instance

GitHub Actions Importer version: 1.3.22081 (ff41350a9d6afd71f38535f23e39fff593ed049c)
Performed at: 7/24/24 at 10:03

Pipelines
Total: 68

Successful: 1 (1%)
Partially successful: 0 (0%)
Unsupported: 67 (98%)
Failed: 0 (0%)

Job types
Supported: 1 (1%)

2: 1

Unsupported: 67 (98%)

YAML: 67

Build steps
Total: 4
Known: 4 (100%)

run: 3
checkout: 1

Actions: 4

run: 3
<EMAIL_ADDRESS>1

Triggers
Total: 1
Known: 1 (100%)

push: 1

Actions: 1

push: 1

Environment
Total: 0
Other
Total: 1
Known: 1 (100%)

working_directory: 1

Actions: 1

run: 1

Most computationally intensive projects can be seen on the usage overview.

Finished report can be found here.


Add Terraform state management resources and documentation

The changes in this PR add Terraform state management resources for this repo. State management resources are added as a unique bucket for this initiative only. Due to the way Terraform operates, state management resources and "operations" resources are separately created (with state management resources being a dependency of operations resources).
Background: Terraform creates state files after applying changes in the cloud. These state files represent the state of cloud resources after applying the infrastructure-as-code changes. By default, these state files are stored locally on a Terraform administrator's application device. Terraform also provides backend configuration which allows for state files to be automatically stored in a bucket. Storing state files in this way enables a larger group of Terraform administrators to access the same state files, expanding the control of cloud resources to others.
Other notable changes:

Pinned pre-commit image for continuous testing to avoid upstream issues with latest image.

Minor note for transparency with changes to .github/workflows/test.yml: the Dagger commandline API appears to be undergoing some changes with newer revisions which was cause for a minor hiccup in how the Github action task was running (attempting to run a command no longer available). I made a change to use the latest specific version which doesn't require a change to how Dagger is running for continuous testing.


Is it possible to generate type adaptors without annotating the type in question?

Question
If I don't have rights to modify and add annotations to a class I want to store using Hive, or if I would just rather not strongly couple it to the Hive library, is it still possible to use hive_generate to generate TypeAdapators automatically?
Although I suspect it must be, I can't find any documentation which suggests this is possible, all examples I can find assume the type is annotated with @HiveType() etc. first.
If it is not currently possible, how hard would it be to adapt hive_generate to achieve this?
Version

Platform: all
Flutter version: any
Hive version: any

Annotations are not just there to say "hey there, I need to get generated". It also contains important values like typeId, property ids, defaultValues etc.. which affects generated code. Without those IDs hive_generator couldn't create backwards compatible code.
You can write adapters manually. Docs: https://docs.hivedb.dev/#/custom-objects/create_adapter_manually

Understood. But couldn't these values be supplied via the API, rather than via annotations?
What I have in mind is that the TypeAdapter requirements implied by this annotation:
@HiveType(typeId : 1)
class Person {
  @HiveField(0)
  String name;

  @HiveField(1)
  int age;

  @HiveField(2)
  List<Person> friends;
}

Might be expressed elsewhere like this:
  TypeAdaptorGenerator(file: "person.g.dart").generate([
     HiveType(
        type: (Person).runtimeType,
        id: 1,
        fields: ["name", "age", "friends],
    ),
  ]);

The generate method would inspect the class and its properties and generate the same TypeAdapter class definitions.
This is just an ad-hoc example - I suspect this could be made more declarative and still achieve the aim of keeping the stored type ignorant of Hive's serialisation of it.


Link Edition 1 and 2 models

The file index.md contains links from a model number in Edition 1 or 2, to a model web page like models/africa. However, some of the models of Edition 2 are (nearly) identical to Edition 1, so index.md can link to the same file.
To resolve this issue, someone has to read through Statistical Rethinking Edition 2 and check whether some models are the same as the models defined in this repository. If that is the case, a link has to be added to index.md.

Hi Rik,
Not sure I completely understand your request. Part if it is no doubt my unfamiliarity with Franklin.

If I want to add say a 2nd edition model (e.g. from chapters 5, 6, 7 and 9), the steps are to 1) update index.md and  2) provide a (Literate) script .jl file (in the scripts subdirectory) and 3) create a documentation .md file (in the models subdirectory)?

I don't think there are currently models with the same number which are different between the editions. There are holes in the model numbering for the 2nd edition. If this becomes an issue in the future I think we could split up the script directory in scripts_1ed, script_2ed, etc.

Your question above is the easy case, i.e. we have a script file and an md file, but just the link is missing?

Have you seen examples of using
julia --project -ie 'using Franklin; Franklin.serve()'

from a released package? As the package directory is non-writable I believe.
Yes, I need to study Franklin.jl!

Hi Rik,
Not sure I completely understand your request. Part if it is no doubt my unfamiliarity with Franklin.

If I want to add say a 2nd edition model (e.g. from chapters 5, 6, 7 and 9), the steps are to 1) update index.md and  2) provide a (Literate) script .jl file (in the scripts subdirectory) and 3) create a documentation .md file (in the models subdirectory)?

I don't think there are currently models with the same number which are different between the editions. There are holes in the model numbering for the 2nd edition. If this becomes an issue in the future I think we could split up the script directory in scripts_1ed, script_2ed, etc.

Your question above is the easy case, i.e. we have a script file and an md file, but just the link is missing?

Have you seen examples of using
julia --project -ie 'using Franklin; Franklin.serve()'

from a released package? As the package directory is non-writable I believe.
Yes, I need to study Franklin.jl!

Yes, I need to study Franklin.jl!

Yeah, no worries. It also took me quite a lot of time to understand Franklin.jl. If I may give a tip, I think it would be easiest to start with creating a new website via the documentation for Franklin.jl. With a new project, the site responds quickly to changes, whereas this project can take quite a while because the Turing models can be quite heavy.

As the package directory is non-writable I believe.

It seems that the manual is a bit unclear. Are you located in TuringModels.jl, like
$ cd TuringModels.jl

$ julia --project -ie 'using Franklin; Franklin.serve()'

If I want to add say a 2nd edition model (e.g. from chapters 5, 6, 7 and 9), the steps are to 1) update index.md and 2) provide a (Literate) script .jl file (in the scripts subdirectory) and 3) create a documentation .md file (in the models subdirectory)?

Correct :+1:

I don't think there are currently models with the same number which are different between the editions. There are holes in the model numbering for the 2nd edition. If this becomes an issue in the future I think we could split up the script directory in scripts_1ed, script_2ed, etc.

I've named the models to avoid this problem. Because the models all have an unique name, we can link anything to anything. If we would split the models in folders, then we cannot avoid duplicate models because the same model in Edition 1 and 2 would be required to be in scripts_1ed and scripts_2ed. So, index.md (the homepage) is literally an index from model number -> name.

Your question above is the easy case, i.e. we have a script file and an md file, but just the link is missing?

Correct :+1:

Yes, I need to study Franklin.jl!

Yeah, no worries. It also took me quite a lot of time to understand Franklin.jl. If I may give a tip, I think it would be easiest to start with creating a new website via the documentation for Franklin.jl. With a new project, the site responds quickly to changes, whereas this project can take quite a while because the Turing models can be quite heavy.

As the package directory is non-writable I believe.

It seems that the manual is a bit unclear. Are you located in TuringModels.jl, like
$ cd TuringModels.jl

$ julia --project -ie 'using Franklin; Franklin.serve()'

If I want to add say a 2nd edition model (e.g. from chapters 5, 6, 7 and 9), the steps are to 1) update index.md and 2) provide a (Literate) script .jl file (in the scripts subdirectory) and 3) create a documentation .md file (in the models subdirectory)?

Correct :+1:

I don't think there are currently models with the same number which are different between the editions. There are holes in the model numbering for the 2nd edition. If this becomes an issue in the future I think we could split up the script directory in scripts_1ed, script_2ed, etc.

I've named the models to avoid this problem. Because the models all have an unique name, we can link anything to anything. If we would split the models in folders, then we cannot avoid duplicate models because the same model in Edition 1 and 2 would be required to be in scripts_1ed and scripts_2ed. So, index.md (the homepage) is literally an index from model number -> name.

Your question above is the easy case, i.e. we have a script file and an md file, but just the link is missing?

Correct :+1:

Regarding the examples of using —project, it is in the franklin default CI template (https://github.com/tlienart/FranklinTemplates.jl/pull/119) and adding it to the docs is work in progress (https://github.com/tlienart/Franklin.jl/issues/750)

Regarding the examples of using —project, it is in the franklin default CI template (https://github.com/tlienart/FranklinTemplates.jl/pull/119) and adding it to the docs is work in progress (https://github.com/tlienart/Franklin.jl/issues/750)


“There was an error loading..” error  is displayed when the user tries to scan the QR code from Merchant Payment url while creating the account while skipping the phone number.

Frequency: 100%
Repro on build version: Android Internal Release Build V1.29.2, v1.29.1, V1.29.0 , iOS Test flight Release Build V1.29.2, V1.29.0, V1.29.1
Repro on devices: Google Pixel 2XL (11.0), iPhone 7(143.3), iPhone 13 mini (15.1.1), Google Pixel 4a(12.0)
Pre-condition:

1.User must have installed the app.
User must have skipped the phone number verification
User must be on the Homepage.
User must have some funds in the account.

Repro Steps:
1.Navigate to the website "https://prod-celo-demo-store.demo.firstdag.com/" on the desktop browser.
2.Tap on Pay with cUSD for any product , QR code will be seen generated
3.Tap on the QR code scanner from the Homepage.
4.Scan the QR code and observe.
Bug: “There was an error loading..” error  is displayed when the user tries to scan the QR code from Merchant Payment url while creating the account while skipping the phone number.
Expected Behavior:  User should be able to scan the QR code and transaction should be performed and no error should be displayed.
Investigation:

When the user has created the account by skipping the Phone number and has a $0.00 balance and when the user tries to scan the QR code the same error is displayed.
"Your payment failed to submit" error appears , transaction fails & user redirects to home screen when user taps on Send button and complete sending flow after scanning QR code from merchant payment website for both iOS & android platforms after creating account & confirming phone number. Attachment
Impact: Bad user impact

Attachment: MerchantPayment.mp4

Hey @MuckT , as per the attachment we have funds in our account and when we scan the QR code for purchasing the product then error is seen
Ideally it should redirect to send amount page and after purchasing the product success message should be seen
Thanks..!!

@ValoraQA I see this error once or twice before the merchant payments work correctly on an unverified number, would you able to attach your logs for this issue?

Hey @MuckT,We have verified & attached the logs as below.
Logs: Logs.txt
Device: Google Pixel XL (10.0)
Thanks..!!

Hey @MuckT, We have verified above issue on Android Internal Release Build, Test Flight Release Build V1.30.1 , with new merchant pay url & observed that issue is fixed now.

User is able to complete merchant payment flow by given url by scanning QR code & order get placed.

Hence we are closing this issue.
Devices: iPhone 13 mini (15.1.1), Google Pixel XL(10.0)
Attachment: Merchant Payment.mp4
Thanks..!!


samples: Create custom page source samples

Also improved the experience of adding samples to the main fragment

Currently blocked by #78

Closes #52


Remove polygon / multi-polygon restriction

We decided to make it so any geometry can be used at STAC sprint 3.
See additional discussion at #44 and #177
This is a tracking issue, to make sure we fully update everything.

[x] Update json spec (done in #177)
[x] Update json schema (done in #177)
[ ] Check OpenAPI definitions and make sure they're in line. Related to #131

@hgs-trutherford / @jasongilman / @scisco - could one of you check the openapi definitions for this?

@cholmes I'd like to merge #201 first, but I can open a PR for this. @m-mohr had suggested some links to use, for geometry, so I'll try taking that approach.

Merged, go for it, @hgs-truthe01 👍


Add better loading state to user card

User cards in the Following tabs that are not reachable just look broken. This is probably just a placeholder but wanted to put it here.

It's not a placeholder, that's what they look like while they're loading.
We'll need to add a failed state so they indicate that the profile didn't load.

I noticed some pretty bad slowness here too.

I noticed some pretty bad slowness here too.

That's not a problem because @cpacia has shown us a video how it's not slow on his machine... lol (sorry Chris - couldn't help myself!)

Update: the solution for this is to add a better loading state to the user card, probably the loading spinner in an overlay.

You can't add the loading spinner in an overlay, because there are situations (e.g. follower's lists) where there are lists of User Cards. You'd probably just want a spinner within the actual card. I suppose that's a nominal improvement, at least visually, over the loading text.

Also, #676 implements fetching a cached profile (if available), which should help with the latency.

I meant an overlay inside the card itself, so the whole card looks like it's loading.

This is very low priority, I was just updating it since I ran across the issue while triaging the backlog.