react-native-git-upgrade 0.57.0-rc.0 is broken

Environment
  React Native Environment Info:
    System:
      OS: Windows 10
      CPU: x64 Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
      Memory: 8.52 GB / 15.95 GB
    Binaries:
      Yarn: 1.9.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
      npm: 6.4.0 - C:\Program Files\nodejs\npm.CMD

I'm upgrading from React Native 0.56.0.
Description
PS C:\Users\Gary\Documents\code\WonderSwipe> react-native-git-upgrade.cmd 0.57.0-rc.0
git-upgrade info Check for updates
git-upgrade info Using yarn 1.9.4
git-upgrade info Read package.json files
git-upgrade info Check declared version
git-upgrade info Check matching versions
git-upgrade info Check React peer dependency
git-upgrade info Check that Git is installed
git-upgrade info Get information from NPM registry
git-upgrade info Upgrading to React Native 0.57.0-rc.0, React 16.4.1
git-upgrade info Setup temporary working directory
git-upgrade info Configure Git environment
git-upgrade info Init Git repository
git-upgrade info Add all files to commit
git-upgrade info Commit current project sources
git-upgrade info Create a tag before updating sources
git-upgrade info Generate old version template
git-upgrade ERR! An error occurred during upgrade:
git-upgrade ERR! Error: Plugin 0 specified in "C:\\Users\\Gary\\Documents\\code\\WonderSwipe\\node_modules\\babel-preset-react-native\\index.js" provided an invalid property of "default" (While processing preset: "C:\\Users\\Gary\\Documents\\code\\WonderSwipe\\node_modules\\babel-preset-react-native\\index.js")
    at Plugin.init (C:\Users\Gary\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib\transformation\plugin.js:131:13)
    at Function.normalisePlugin (C:\Users\Gary\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib\transformation\file\options\option-manager.js:152:12)
    at C:\Users\Gary\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib\transformation\file\options\option-manager.js:184:30
    at Array.map (<anonymous>)
    at Function.normalisePlugins (C:\Users\Gary\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib\transformation\file\options\option-manager.js:158:20)
    at OptionManager.mergeOptions (C:\Users\Gary\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib\transformation\file\options\option-manager.js:234:36)
    at C:\Users\Gary\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib\transformation\file\options\option-manager.js:265:14
    at C:\Users\Gary\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib\transformation\file\options\option-manager.js:323:22
    at Array.map (<anonymous>)
    at OptionManager.resolvePresets (C:\Users\Gary\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib\transformation\file\options\option-manager.js:275:20)
git-upgrade ERR! Restore initial sources
Note: checking out 'project-snapshot'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

Reproducible Demo
Run react-native-git-upgrade 0.57.0-rc.0. I can reproduce same error on both Windows and MacOS (latest High Sierra).
I've never encountered a similar breakage with git-upgrade for about the last 10 version of RN upgrades I've done with react-native-git-upgrade.
Ref: https://github.com/react-native-community/react-native-releases/issues/34

confirm. could upgrade by react-native upgrade 0.57.0-rc.0 and manually go through files.
not very successful cause there some other issues. script is bundled, but one time I got error screen about importing static config object from file (defined as module.exports = {...}), now I got message:
Failed to load bundle(http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false) with error:(/Users/user/project/index.js: ENOENT: no such file or directory, uv_cwd (null))

__38-[RCTCxxBridge loadSource:onProgress:]_block_invoke.248
    RCTCxxBridge.mm:429
___ZL36attemptAsynchronousLoadOfBundleAtURLP5NSURLU13block_pointerFvP18RCTLoadingProgressEU13block_pointerFvP7NSErrorP9RCTSourceE_block_invoke.118
__80-[RCTMultipartDataTask URLSession:streamTask:didBecomeInputStream:outputStream:]_block_invoke
-[RCTMultipartStreamReader emitChunk:headers:callback:done:]
-[RCTMultipartStreamReader readAllPartsWithCompletionCallback:progressCallback:]
-[RCTMultipartDataTask URLSession:streamTask:didBecomeInputStream:outputStream:]
__88-[NSURLSession delegate_streamTask:didBecomeInputStream:outputStream:completionHandler:]_block_invoke
__NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__
-[NSBlockOperation main]
-[__NSOperationInternal _start:]
__NSOQSchedule_f
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_continuation_pop
_dispatch_async_redirect_invoke
_dispatch_root_queue_drain
_dispatch_worker_thread2
_pthread_wqthread
start_wqthread

Have you tried manually upgrading to 0.57?

Removing my local .babelrc file before running react-native-git-upgrade 0.57.0-rc.0 solved the problem for me

@kelset I don't think you need to set dependency on the preset anyway, because it's part of Metro dependencies and ends up being in your node modules anyway. Remember that its version has to always match internal Metro version, which may be hard to keep in sync due to lack of peer dependency on RN.

ALL WORK LIKE PEAS AND CARROTS ON MY MAC! but I am team lead at a react native base software house and my co-workers are WINDOWS BASED HUMANOIDS so here is what I have found !
I have been asking about this ISSUE of RN 0.56 !!for like from weeks! on reactiflux, slack communities, and been following twitter announcements; I just saw couple of hours ago on twitter that 0.57 is here! I jumped into my package.json, updated manually and react-native-git-upgrader. but after manually updating it all things seemed to work out well ! that INFAMOUS 500 server error was long gone! but now it says
OLD BUT GOLD ERROR
"Unable to load script from assets index.android.bundle on windows"
one ERROR GOES AND THERE IS ANOTHER RED SCREEN POPING up! I had to do jump and bump among several GIT ISSUES threads and stacks! but I am still not able to do it!
MY BEST GUESS HERE is:
as in versions before 0.56 of RN we used to have index.android.js & index.ios.js files , and somehow the 0.57rc update is taking an old PR of code structure or something !
again above said is a theory I won't dare to upgrade 0.57rc on my Mac for now! but any Window's user at RN dev community should try this one! please ! we WINDOW users are HUMANS Too.

I guess that I've to lock this issue too, apparently it's impossible to avoid disruptive people when trying to fix issues related to release candidates 🤷♂
I'll keep saying it, it's an open source project. Don't you like something? Fork it and fix it yourself. Writing these kinds of comments is just pathetic.

Tried upgrading the old fashioned way. I first ran yarn add<EMAIL_ADDRESS>without issue, and modified my .babelrc to
{
  "presets": ["module:metro-react-native-babel-preset"],
  "plugins": ["idx"]
}

Then I ran react-native upgrade, and I get
PS C:\Users\Gary\Documents\code\WonderSwipe> react-native upgrade
Scanning folders for symlinks in C:\Users\Gary\Documents\code\WonderSwipe\node_modules (28ms)
(node:16936) UnhandledPromiseRejectionWarning: Error: Cannot find module 'metro/src/blacklist'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
    at Function.Module._load (internal/modules/cjs/loader.js:507:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (C:\Users\Gary\Documents\code\WonderSwipe\rn-cli.config.js:3:19)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Module._compile (C:\Users\Gary\Documents\code\WonderSwipe\node_modules\pirates\lib\index.js:83:24)
    at Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Object.newLoader [as .js] (C:\Users\Gary\Documents\code\WonderSwipe\node_modules\pirates\lib\index.js:88:7)
    at Module.load (internal/modules/cjs/loader.js:599:32)
(node:16936) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:16936) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Metro still?
PS. output: https://github.com/facebook/react-native/issues/20720#issuecomment-413984074 from yarn add for metro/babel versions upgraded to. Need locking to specific versions instead of latest?

@fungilation can you copy/paste your package.json if possible?
But yeah that blacklist error seems Metro related.

My package.json
{
  "name": "wonderswipe",
  "version": "0.0.1",
  "private": true,
  "eslintConfig": {
    "parserOptions": {
      "ecmaVersion": 7,
      "sourceType": "module",
      "ecmaFeatures": {
        "jsx": true
      }
    },
    "env": {
      "browser": true,
      "node": true
    },
    "plugins": [
      "react",
      "react-native"
    ],
    "rules": {
      "comma-dangle": [
        2,
        "always-multiline"
      ],
      "semi": [
        2,
        "never"
      ],
      "react-native/no-unused-styles": 2,
      "react-native/split-platform-components": 2
    }
  },
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start"
  },
  "dependencies": {
    "babel-plugin-idx": "^2",
    "he": "^1.1.0",
    "lodash": "^4.17.2",
    "moment": "^2.19.0",
    "moment-timezone": "^0.5.10",
    "node-summary": "../node-summary",
    "react": "16.4.1",
    "react-native": "0.57.0-rc.0",
    "react-native-actionsheet": "^2.4.2",
    "react-native-blur": "^3.2.0",
    "react-native-cached-image": "../react-native-cached-image",
    "react-native-code-push": "^5.3",
    "react-native-custom-tabs": "^0.1.7",
    "react-native-easy-toast": "^1.0.9",
    "react-native-firebase": "^3.0",
    "react-native-fit-image": "^1.4.8",
    "react-native-flanimatedimage": "^0.4.0",
    "react-native-highlight-words": "^1.0.1",
    "react-native-keep-awake": "^3.0.1",
    "react-native-linear-gradient": "^2.0.0",
    "react-native-modalbox": "^1.6.0",
    "react-native-orientation": "^3.1.3",
    "react-native-parallax-scroll-view": "../react-native-parallax-scroll-view",
    "react-native-rate": "^1.0.8",
    "react-native-safari-view": "^2.0.0",
    "react-native-sentry": "^0.38.0",
    "react-native-sha256": "^1.1.1",
    "react-native-status-bar-size": "^0.3.2",
    "react-native-swiper": "../react-native-swiper",
    "react-native-tooltip": "^5.2.0",
    "react-native-tts": "^1.5.0",
    "react-native-vector-icons": "^4.1.1",
    "react-native-webview-bridge": "../react-native-webview-bridge-RN0.51",
    "react-redux": "^5.0.1",
    "redux": "^4.0.0",
    "redux-thunk": "^2.1.0"
  },
  "devDependencies": {
    "redux-logger": "^3.0.6"
  }
}

Made those changes and ran yarn. Confirmed that yarn.lock shows babel deps now at 7.0.0-beta.56 instead of 7.0.0-beta.47 before.
But running react-native upgrade hits the same Error: Cannot find module 'metro/src/blacklist'... as before.

I've done some investigation and the original reported issue is caused by react-native-git-upgrade using still Babel 6 to transpile itself:
https://github.com/facebook/react-native/blob/9c1ea45d38a6ec731894443debe8879fa3876ab7/react-native-git-upgrade/cli.js#L12-L19
Babel by default tries to find .babelrc files to configure itself, and once it finds the one from the RN app (which links to the RN preset that only works on Babel 7) it fails.
The easiest patch to fix this issue is to add babelrc: false to the babel-register method, so Babel does not read any additional .babelrc file.
@fungilation can you give this a try? feel free to send a PR if this fixes the issue 😃

FWIW, @rafeca's fix worked for me. Patched and ran react-native-git-upgrade, resolved merge conflicts, cleaned up with npm uninstall babel-preset-react-native, and I'm good to go (or rather, I've moved on to the next issue, #20712).

Environment
  React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: x64 Intel(R) Core(TM) i7-6920HQ CPU @ 2.90GHz
      Memory: 849.51 MB / 16.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 8.10.0 - /usr/local/bin/node
      Yarn: 1.9.4 - /usr/local/bin/yarn
      npm: 5.10.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
      Android SDK:
        Build Tools: 23.0.1, 23.0.3, 25.0.0, 25.0.2, 25.0.3, 26.0.1, 26.0.3, 27.0.3, 28.0.2
        API Levels: 23, 25, 26, 27
    IDEs:
      Android Studio: 3.1 AI-173.4907809
      Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
    npmPackages:
      react: ^16.4.1 => 16.4.1
      react-native: ^0.57.0-rc.0 => 0.57.0-rc.0
    npmGlobalPackages:
      react-native-cli: 2.0.1
      react-native-git-upgrade: 0.2.7

Good to hear, @ngraef would you mind creating a PR with the fix so that it can be merged and cherry-picked for a rc1 release, so that it can be available?

@ngraef did you have to do some additional babel configuration?
https://github.com/facebook/react-native/issues/20712
there is a suggestion fix
const procConfig = {cwd: scriptsDir};
with
const procConfig = {};

Which also "solves" that problem for me. However I get error from
node_modules\react-native\Libraries\Image\Image.android.js: Support for the experimental syntax 'optionalChaining' isn't currently enabled (221:13):


Update Terraform terraform-aws-modules/ec2-instance/aws to 4.1.4

This PR contains the following updates:

Package
Type
Update
Change

terraform-aws-modules/ec2-instance/aws (source)
module
patch
4.1.3 -> 4.1.4

Release Notes

terraform-aws-modules/terraform-aws-ec2-instance
v4.1.4
Compare Source

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

@balena-ci I self-certify!


python312Packages.django-q: use build-system/dependencies, correct us…

…ed build-system

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build python312Packages.django-q python312Packages.django-q.passthru.tests

Still marked as broken, but not sure if that's intentional. Diff still LGTM

Was a drive by cleanup while packaging django-q2 and I copied the django-q package mostly for it.


Update stable version in repo from 0.0.0 to 0.9.0

Think about adding version 0.9.0 to stable repository.
Version: stable=0.0.0 (0 days old) => latest=0.9.0 (30 days old)
Installs: stable=0 (0%), latest=7 (26.92%), total=26
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 0.9.0 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 0.9.0 but in the meantime an update to version 0.11.1 is suggested.
So this issue will be closed and replaced by an updated one.
@mcm1957 for evidence


zui: Update pull image dropdown to latest version

Update the pull image widget to match new mock version

duplicate of #243


NPE bugs in MaximumProductOfWordLengths.java and RemoveDuplicatesFromSortedArray.java

Hi,
I have found two bugs in MaximumProductOfWordLengths.java (leetcode/bit-manipulation/MaximumProductOfWordLengths.java) and RemoveDuplicatesFromSortedArray.java(leetcode/two-pointers/RemoveDuplicatesFromSortedArray.java).
In MaximumProductOfWordLengths.java line 20 if(words.length == 0 || words == null) if words is null, words.length will NPE
Similarly in RemoveDuplicatesFromSortedArray.java line 12  if(nums.length == 0 || nums == null) if nums is null then nums.length will NPE.
I know they are minor issues. I would still be good if you can fix them. Thanks a lot!

Hi, can anyone please confirm and fix those bugs? Thanks so much!

You need to create a pull request so the author can merge it directly.

Hi, Can I work on this issue?


Getting error when running 'docker.start.sh'

Not able to start open-nti containers using 'docker.start.sh'
root@ubuntu:~/open-nti# ./docker.start.sh
Use docker compose file : docker-compose.yml
WARNING: The IMAGE_TAG variable is not set. Defaulting to a blank string.
Pulling opennti (juniper/open-nti:latest)...
latest: Pulling from juniper/open-nti
Digest: sha256:1bc00e223477fce1bdb47c4206ea6bf8c5ea01ee4adca2191043ca5b8891acfb
Status: Image is up to date for juniper/open-nti:latest
Pulling input-syslog (juniper/open-nti-input-syslog:latest)...
latest: Pulling from juniper/open-nti-input-syslog
Digest: sha256:69603d75bf645267dbe48e6f17fe6c5010cf5ae53c5ad9ada0d3b0a4c1c15519
Status: Image is up to date for juniper/open-nti-input-syslog:latest
Pulling input-jti (juniper/open-nti-input-jti:latest)...
latest: Pulling from juniper/open-nti-input-jti
Digest: sha256:9eb80f329e25a6cdc3767c50329e0df05edcabc3c3eae8288a11fb3b518eb3c4
Status: Image is up to date for juniper/open-nti-input-jti:latest
Pulling opennti (juniper/open-nti:latest)...
latest: Pulling from juniper/open-nti
Digest: sha256:1bc00e223477fce1bdb47c4206ea6bf8c5ea01ee4adca2191043ca5b8891acfb
Status: Image is up to date for juniper/open-nti:latest
ERROR: for opennti  Image 'juniper/open-nti:' not found
Traceback (most recent call last):
File "", line 3, in
File "compose/cli/main.py", line 61, in main
File "compose/cli/main.py", line 113, in perform_command
File "compose/cli/main.py", line 835, in up
File "compose/project.py", line 400, in up
File "compose/parallel.py", line 64, in parallel_execute
compose.service.NoSuchImageError: Image 'juniper/open-nti:' not found

Got it
All the docker.*.sh scripts are deprecated, moving forward it’s recommended to use “make”
You can use
make start
make stop
make update
etc …

I’ll try to see if I can fix docker.start.sh but we’ll remove it soon


How does PocketBase handle BigInt (64-bit) integers?

I am seeing things in the JSON type such as:

Which does not seem correct...

PocketBase uses the standard go library for serializing/deserializing JSON, which means that by default any in number in a JSON string will be decoded as double precision floats (aka. float64).
For consistency, the same rule applies when type number field is used - it will be normalized/casted to float64:
https://github.com/pocketbase/pocketbase/blob/master/models/schema/schema_field.go#L227-L228
It is possible to provide a custom JSON decoder for the json type field and serialize the result value as string but I'm not sure if that will be expected from most users (in JavaScript numbers are also floats between -+2^53-1; thre is a special bigint type but I'm not sure how that works with the browsers JSON.stringify/parse functions).


[Tracking Issue] Oopsie Woopsie (doesn't even compile, and if it did...)

Made a significant fucky-wucky and jumped the gun on releasing this package.
The whole point is to allow you to deploy network anywhere without thinking about the target.
On microcontrollers (the juiciest spot to deploy EANT2 / CGE models), you often have no floating point functions like tanh and sqrt etc.  micromath provides approximations to these functions, but they're often really bad (sqrt(2) == 1.5).  Plus, I'd have to lock in users to micromath, and we also seem to have a libm port available.
This should be fine, if only you train your network using poor approximations over these functions.
However, this will break the fundamental promises of the package, as networks may behave very differently on no_std targets, and to train using approximations you need to know in advance where your network will end up, and it cannot easily be shared (I want small utility networks to literally be crates someday).
Possible solutions, all bad:

Lawful evil: copy the code that implements the std's floating point approximations of elementary functions mostly verbatim.    They're pretty fast on desktop so maybe they're not so bad, idk.

Chaotic evil: allow for micromath's approximations to produce compounding errors inside networks, warn the user, hope for the best. Supply the tanh approximation which it lacks.  Perhaps we can examine the range over which these approximations are relevant and improve them, making a micromath support tailored for neural network evaluation. Idk, lots of work.

Or, we can abandon floating point support all together.

I think the correct solution is going to be to examine how bad these compounding errors actually get, and possibly provide custom shim that takes over for micromath.

All crate components yanked until I can figure this out & provide a reasonable solution.
Unclear to me if libm approximations are any good / what their properties are.

Several of the activation functions should actually be branchless bit hacks on all platforms & perform no actual floating point math (linear, threshold, sign, ReLU).  I should tell users that if they want their model to be guaranteed to function identically on all targets, then use one of these activations.

The differences emerge in the sigmoid, tanh, soft_sign, and bent_identity activations.

I think a reasonable default would be to depend on libm for no_std targets, as I think it mostly matches identically with existing std code, with the option to switch to micromath approximations if that's what they prefer.  micromath has no tanh, so I can either steal libm's tanh or just use another approximation in place.

Ok so I went down the rabbit hole on designing this correctly, mostly to support my vision of "netcrates" while also solving the numerical backend problem.  This was really hard.  The trick is to only allow netcrates to expose networks as data, not code, and allow code to be generated by the end user from the data. But the data is not actually available at macro expansion time! The way we do this:

a proc-macro that loads the data from file into a literal,
produces a macro_rules! macro that when invoked will create an invocation of the main const_cge proc macro.
This is sinful and terrible and confusing but it works magic and avoids the dependency hell that would exist if networks were published as generated code.

The new solution:

Supports for the end user any floating point backend that core_cge offers, and this can be upgraded in a centralized way.
Does not require netcrate authors to understand floating point backends or forward specific features to libm, micromath, std, etc.  This would end up as hell.
netcrate authors only see:

const_cge::netcrate!("path/to/awesomenet.cge");

netcrate consumers only see:

use awesome_net;
#[network(awesome_net)]
struct AwesomeNet;

and then const_cge end users must pick their backend in features like:
const_cge = { version = "0.1.3", features = ["libm"] }
const_cge = { version = "0.1.3", default-features = false, features = ["std"] }
const_cge = { version = "0.1.3", default-features = false, features = ["micromath"] }

This might limit some composability in netcrates, but we can fix that.

Say you want to provide a tiny pretrained neural turing machine, and you want to provide the user a nice implementation to use it. My preferred solution is to publish /another macro/ (sorry)

macro_rules! ntm {
  ($name: ident) => {
    impl $name {
      const MY_CUSTOM_CONST: usize = ...;
      fn my_custom_extension(&mut self) -> { ... }
    }
  }
}
pub(crate) use ntm; // expose the extension macro

And an end user desiring this extension:
#[network(ntm_zoo::some_task, numeric_type = f32)]
struct SomeTask;
ntm!(SomeTask);

Not elegant, but it solves some really hard problems, and allows for a maintainable and flexible ecosystem for embedded ML.

Resolved, as far as I can tell anyway.


fix issue 15336, opIn undocumented for JSONValue

document opIn

fix some DDoc sections

DAutoTest failure is a fake positive.

fix for issue 15336 is updated.

fix for issue 15336 is updated.


Validation Errors on existing unmodified CondensedInlinePanels on save

Version Info
Wagtail: 2.5.1
Django: 2.0
Python: 3.4 & 3.6 (Two different environments)
CondensedInlinePanel: 0.5.2
The Issue:
I have a CondensedInlinePanel in my page model that contains two select inputs. They save just fine on page creation, but if I go to edit the page, all unmodified panels will throw validation errors on those input fields.
In this screenshot, I just tried to add "Edited Panel" to an existing page ("The page could not be saved due to validation errors."):

Here are the fields that are throwing errors ("Select a valid choice. ['*'] is not one of the available choices."). Note that all of the selected options are valid choices:

The Workaround:
Currently I can prevent the validation errors from occurring by manually opening each panel so the plugin marks them as "modified". Since we're using JQuery on our site I added this code to do the same thing automatically on page load. Obviously this isn't ideal, but it does work well enough for our purposes:
$('document').ready(function(){
	$('.condensed-inline-panel__action-edit').click();
	setTimeout(function(){
		$('.condensed-inline-panel__action-close').click();
	}, 300);
});

Relevant model code
class MyCondensedInlinePanelModel(Orderable):
	parent_page = ParentalKey('MyPageModel', related_name='my_panel', on_delete=models.CASCADE)

	# ...

	DATE_TYPES = (
		('posted',   'Posted on <Date>'),
		('launched', 'Launched on <Date>'),
		('updated',  'Updated on <Date>'),
	)
	date_type = models.CharField(max_length=12, choices=DATE_TYPES, default='posted')

	TEXT_COLORS = (
		('light', 'Light Text'),
		('dark',  'Dark Text')
	)
	text_color = models.CharField(max_length=12, choices=TEXT_COLORS, default='light')

	# ...

	panels = [
		# ...
		FieldPanel('text_color'),
		MultiFieldPanel([
			FieldPanel('date_type'),
			# ...
		], heading="Post Date"),
		# ...
	]

	# ...

I have exactly the same problem.
But if I expand each of the related items the validation is successful

Facing same challenge

So am I
with:
Wagtail: 2.10
Django: 3.1
Python: 3.85
CondensedInlinePanel: 0.5.3


pyproject.toml instructions updated

true needs to be lowercase.
Otherwise we get:
  TOMLError

  Invalid TOML file ...pyproject.toml: Unexpected character: 'T' at line 32 col 17

Interesting, thanks for the report and the fix.
This must be very specific to toml because coveragepy uses configparser which leverages getboolean that works with anything.

https://github.com/nedbat/coveragepy/blob/coverage-5.5/coverage/config.py#L13
https://github.com/nedbat/coveragepy/blob/coverage-5.5/tests/test_json.py#L109-L161
https://docs.python.org/3/library/configparser.html#configparser.ConfigParser.getboolean


Error "Failed to construct 'CustomElement'"

The complete error is
Uncaught DOMException: Failed to construct 'CustomElement': The result must not have attributes
I have no idea how to fix this. A bit of background: I just tried to use some components and according to the docs it is very easy by adding it as dependency to index.html, e.g. like
<script<EMAIL_ADDRESS>inside the head.
I want to use it for a demo inside a stencil component. Maybe it clashes with Stencil's polyfils?

There's no reason why these should not work with stencil.
I haven't had a chance to work on in this this year, getting back to it this weekend. Stay tuned!

+1

This should be resolved in the latest release.  (0.9.x)
The problem was an attribute was being set after creating the shadow root.
This did not create an issue in older versions of lit-element.


Adding Save feature to app

First steps for #15
I still need to add Export function
Changes:
I have added save button which will Save the data to a csv file.
Screenshots for the change:

As mentioned in the issue, Use https://github.com/square/tape

I will be improving this by using json and gson to write data

Use moshi

@CloudyPadmal Please review this

@yatri1609 Please tell me what do you understand to be the goal of this issue?

@iamareebjamal The main goal is to add Save functionality to the app

What is the end goal of save functionality?
I asked this because I see that the implementation is unfortunately outside the scope of the goal. You are saving the selected options of flashing and whatnot, that is not the goal. To clarify that we are on same page, please tell me what, in your opinion, is meant by "Save Functionality"

@iamareebjamal to save the text which we are sending to the file and the options selected with it.

@yatri1609 I think it's for convenience and sharing, people should be able to save the current configuration into a file which can then be imported by other people. And by convenience, I meant that they should be able to see and use that saved configuration without any extra efforts

No, we need ability to just save the badge - the thing you see in the preview. So that we can persist it across the app relaunches, and ability to export it, so that another person can share them with friends

No, we need ability to just save the badge - the thing you see in the preview. So that we can persist it across the app relaunches, and ability to export it, so that another person can share them with friends

Ohh ohk.... there was some misunderstanding... I would fix that. @iamareebjamal

Fix conflicts

@yatri1609 Thank you! Please finalize this PR.

Implemented and merged


Use git2 hash-shortening function

I am interested in this project and I want to contribute to code although I'm not good at rust. I think I can be better by contributing this project.
Can you help me with this?
I was trying to pick up #280.
I thought oid in this function should be calculated using git2.
https://github.com/arxanas/git-branchless/blob/45ace45579804697f8daeb551750424bf8e8538b/src/core/node_descriptors.rs#L183-L199
Then I might have to change constructor.
https://github.com/arxanas/git-branchless/blob/45ace45579804697f8daeb551750424bf8e8538b/src/core/node_descriptors.rs#L178
So my current status in ccc277c37c6f138bb17e2d0ac19898bcc82fc3f3 is I brought &Repo to constructor.
    pub fn new(repo: &Repo, use_color: bool) -> eyre::Result<Self> {
        Ok(CommitOidDescriptor { use_color })
    }

And I got 3 problems.

I was thinking this, but  repo: &Repo don't have raw(). Which is strange. Because it is wrapper around git2::Repository and I thought git2::Repository has raw().
To enable describe_node to access to repo as self.repo, I need to do something like this.

pub struct CommitOidDescriptor<'a> {
    repo: &'a Repo,
    use_color: bool,
}

But It makes error message all around. If this is right way to do it, then I will study about lifetime and go forward. But I am not sure about it because of 1.

bugreport! error.  I don't know what should I do.

Discussed further at https://discord.com/channels/915309546984050709/940852244880965673/956060354595676170

By the way, the Windows CI tests are failing with this error:
The application panicked (crashed).
Message:  attempt to add with overflow
Location: C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\indicatif-0.17.0-rc.9\src\state.rs:420

This is an unrelated issue and you can ignore it. Only the Linux runs are important for this change.


Add explicit support for Azure OAuth2 (feature req)

The existing generic Oauth2 support is not able to directly support Azure AAD out of the box.  Specific support for AAD could be done, or the generic configuration expanded to allow it.
Specifically, it needs

API endpoint function in Azure is /me rather than /userinfo -- this should be a config option
Returned attributes are userPrincipalName, givenName, surname (mail is returned but should use userPrincipalName if it is empty).  Possibly allow configuration of a list of attributes to search for and use if non-blank?
There is no code to catch a returned 'error' attribute or error status and this can result in 502 or 404.
Failure of account creation should raise a visible error and clear the session, rather than just returning to the login page which results in looping

I have coded up most of this myself in a test branch and hope to submit a pull request to add a new AAD support option.  Some documentation on how to configure the Azure end is probably required as well since it is a little obscure what options are needed (scope User.Read and so on)

Actually we can use LDAP (Active Directory) authentication option to allow users from our Azure AD to access PDA.
I saw your PR #591. Fixed and merged it. Thanks.

The benefit of using SAML or Oauth over LDAP is that with SAML and OAuth you can use the Microsoft MFA and additional security protection afforded by Azure AD.  You also do not need to install an AAD-DS object (which is required to have an LDAPS endpoint).
The benefit of OAuth over SAML is that, although you lose access to the group memberships, OAuth is free but SAML requires a Premium Azure account.


[FEATURE REQUEST] Get the latest/default version to be downloaded, e.g., graalvm-ce-java17-22.3.1 as plain text

it would be nice if i could curl bash <(curl -sL https://get.graalvm.org/release/latest), and get the default release to be installed as plain text, like graalvm-ce-java17-22.3.1 or graalvm-ee-java17-22.3.1 (based on availability of $GRAAL_EE_DOWNLOAD_TOKEN)
without this, it's a bit inconvenience to get what version is actually installed (maybe parsing ls output), when the intent is to install the latest version

Apologies for not looking into this sooner. Were you able to work around the problem? The new release just made it into SDKMAN (both CE and Oracle GraalVM) and it may be easier to use that in the future. What do you think?

np... and yah, found out the Oracle GraalVM yesterday. I couldn't find the new release in sdkman yesterday, so, with the script friendly URLs - written (copied from new official GraalVM Image Dockerfile) a script instead https://raw.githubusercontent.com/audacioustux/CompaaS/main/.devcontainer/features/graalvm/install.sh
may switch to sdkman later

Great! Yes, the new script friendly URLs are designed for exactly this. :)


[5.7] Allow to change the formatter for the single, daily and syslog log

This PR is about the ability to specify a formatter from the config file for the single, daily and syslog driver.
The default formatter, the LineFormatter, print the date and time, channel name, level and text for every message logged. To change the format of the message, for example to remove the channel name, or to use a different formatter, for example the HtmlFormatter, you have to use the monolog driver with the correct handler.
Compare the following configurations:
return [
    "channels" => [
        "formatted_single" => [
            "driver" => "monolog",
            "handler" => StreamHandler::class
            "handler_with" => [
                "stream" => storage_path("logs/laravel.log"),
                "level" => "info",
            ],
            "formatter" => LineFormatter::class,
            "formatter_with" => [
                "format" => "[%datetime%] %level_name%: %message%",
            ],
        ]
    ]
]

and
return [
    "channels" => [
        "formatted_single" => [
            "driver" => "single",
            "path" => storage_path("logs/laravel.log"),
            "level" => "info",
            "formatter" => LineFormatter::class,
            "formatter_with" => [
                "format" => "[%datetime%] %level_name%: %message%",
            ],
        ]
    ]
]

Like what?

Don't change any doc blocks, etc.


Documentation for creating custom events and custom events with custom params

Description & motivation
Closes #135
Checklist

[ ] I have verified that these changes work locally
[ ] I have updated the README.md (if applicable)
[ ] I have added tests & descriptions to my models (and macros if applicable)
[ ] I have run dbt test and python -m pytest . to validate exists tests

@adamribaudo-velir FYI about something that puzzled me recently:
By creating models in the non dbt-ga4 projects, variables default_custom_parameters and [my_custom_event]_custom_parameters will not be accessible due to different scopes.
As a temporal fix, I am defining them as:
vars:
  default_custom_parameters:  # TODO: #54 fix ga4 vs local scope variables definition. This is a workaround.
    - name: "checkout_subscription_type"
      value_type: "string_value"
    - name: "offer_type"
      value_type: "string_value"
    - name: "page_type"
      value_type: "string_value"
    - name: "country_prefix"
      value_type: "string_value"

  questionnaire_cancel_subscription_custom_parameters:  # TODO: #54 fix ga4 vs local scope variables definition. This is a workaround.
    - name: "cancel_subscription_questionnaire"
      value_type: "string_value"

  ga4:
    project: ""
    dataset: ""
    start_date: "20221101" # Earliest date to load
    frequency: "daily" # daily|streaming|daily+streaming Match to the type of export configured in GA4; daily+streaming appends today's intraday data to daily data
    static_incremental_days: 14  # 7 days as we run it weekly + 7 days as a buffer for errors and delays
    query_parameter_exclusions: ["gclid","fbclid","_ga"]
    conversion_events: ['view_item', 'add_to_cart', 'begin_checkout', 'complete_registration', 'add_payment_info', 'subscribe', 'purchase']

    user_properties:
      - user_property_name: "subscriber_status"
        value_type: "string_value"
      - user_property_name: "subscription_type"
        value_type: "string_value"

@ivan-toriya I'll look into this, thanks.


Require 'src' attribute

For inline, WebXR, and Magic Leap, we'll need a glTF/glb file. There's a scenario where only the USDZ is provided, with a poster, which is more or less no different from iOS's native AR Quick Look.
This may already work due to the mixin pattern, but something we should confirm, and/or clarify in docs.

This has been clarified in docs and is the current behavior of the element, so I'm going to close off this issue.


[WIP] Precalculate lattice

Precalculating the independent parts of the lattice gets this speed where we need to be. This PR is not ready to merge yet.

@dirko this is very close
I have it all but 4 tests. There's some obscure bug I can't quite find.
In order take advantage of precomputing the lattice, I needed a homogenous way of representing the lattice, so I decided to represent it as a edgelist. This actually makes some other things much faster, but it means I had to touch a lot of code.
I'd appreciate it if you could look at the forward algorithm, the backward algorithm, and the forward_backward.
Thanks!

down to three test. Please take a look.

So one of the failures was failing before (test_fit_predict).
The other two tests are tests of derivates. Strangely, the value of the actual derivates has not changed, but the the value of the "expected derivates" in these tests has changed.

@dirko, all test's passing now!!! ready to merge.

@dirko, after you merge this, and are satisfied could you run compile the pyx files to c and upload a distribution to pypi. I want to synch this into dedupe, and need this on pypi.

Sorry I haven't come around to look at this yet - will try to go through it as soon as possible - but as you said it's a large change!

Sorry, it is pretty big. Happy to chat about on IRC or google voice.
On Fri, Jun 5, 2015 at 2:10 PM dirko<EMAIL_ADDRESS>wrote:

Sorry I haven't come around to look at this yet - will try to go through
it as soon as possible - but as you said it's a large change!
—
Reply to this email directly or view it on GitHub
https://github.com/dirko/pyhacrf/pull/8#issuecomment-109401863.

I'll organise the StateMachines a bit differently.
The public and private methods and members must be differentiated, for example _build_lattice is the only public method but is prepended with an underscore, while independent_lattice, grow_dependent_lattice etc should be private helpers.
I think that DefaultStateMachine and GeneralStateMachine should be two different classes. They can inherit from a base class that implements build_lattice, states_to_classes, and n_states (or can implement these members and methods with duck-typing). At the moment the StateMachine interface is a bit confusing I think.
I also think the constructions of the TestStateMachines with class variables is unnecessary - why don't we rather pass the transitions, start_states etc as parameters to the constructor? This will make testing easier.
For now I'll merge and then implemented these changes - let me know if this again messes with the running speed!

Good points! Sounds like a plan


Ensure we're targeting the right VMs

If a user has multiple deployments, they therefore have mutliple blocks
in their ~/.ssh/config.
While the ssh configuration allows to chose the right VM using the
hypervisor name (for instance controller-0.builder2), the dynamic
inventory built using ansible.builtin.add_host doesn't target the
specific host.
With delegate_to, it may happen ansible connects to a wrong VM from a
previous deployment that's still running, and the user will face some
really weird situations - for instance, facts being wrongs (this hit the
networking_mapper and the fetched MAC addresses).
With this patch, we now have specific host targeting, and we also get it
in the logs, for example:
changed: [builder2 -> controller-0(controller-0.builder2)]

As a pull request owner and reviewers, I checked that:

[X] Appropriate testing is done and actually running

recheck

seems sensible just wondering if anyone could (currently) be relying on the extracted_ip in the generated inventory? but I am not working in this area at all perhaps this is not a valid concern (and we are talking about the in memory inventory for add_host so... should be fine).
holding approve until the reviews call for any other comments

It's set in the .ssh/config - so there's nothing lost in there. This is really affecting only the dynamic, in-memory inventory, but does NOT affect written files that are then used on controller-0 for instance.

/approve


Nutritional Information: Step 1

GIVEN that a user has requested nutritional information
WHEN I fetch data from the API using query params
THEN I will verify the data sent back is appropriate
WHEN the data is validated
THEN it will display on the screen for the user

completed. waiting on pull request to be merged for this issue.

Pull request approved and feature merged in.


Adjust the linter config

Revisit the linter config to some new sane defaults for a 2024 python project.
If we do settle on this config, we need to work through a small list of issues that is found by this new config

@MartinHjelmare what do you think ? Ok to switch to this new config ?
I'd like to use this confog for other python projects as well we maintain.
It will mean we'll have some work to fix the files according the issues found

OK, I will work more on this next week and start to lint the existing code. If we're happy with this config we can replicate it to the other projects in the libs org

This one is ready for a final check. Added a bunch of exceptions for the rules. We can resolve these one-by-one in follow up PR's.


Stuck in Initiated

I have started a Loop Out and it is stuck in initiated for over 12 hours. How do I fix it? I am using the User Interface.

Can you post any more details of the swap please? The swap hash and the logs?

I am using the User Interface, how do I access the swap hash and the logs? Thanks

If you're using Umbrel, you might need to ask their support where the LiT data directory is located.
If you're using LiT standalone, look in ~/.loop/logs

ok I found ~/.loop/logs What info do you need?

The whole log is probably the easiest.

All I see is mainnet in the logs folder

No file inside?

in /home/umbrel/umbrel/app-data/lightning-terminal/data/.loop/logs all i see is mainnet

Yes, inside mainnet is there a log file?

I do not see any files inside the mainnet folder.

Okay, then check /home/umbrel/umbrel/app-data/lightning-terminal/data/ if there is a lit.log anywhere in any of the sub directories.

I found litd.log file in /home/umbrel/umbrel/app-data/lightning-terminal/data/.lit/logs/mainnet. Is that correct?

yes

what is the easiest way to export the file from my pi to my windows desktop?

litd.log

@mlewk We're trying to reproduce the issue of the UI not updating the state. It would be helpful to get the log from when you restarted Umbrel. Could you please upload the whole litd.log again? Thank you!

litd.log


Period 4 Mort Table 8's Review Ticket

Alexa Carlson's Hacks
Ava Carlson's Hacks
Lydia Cho's Hacks
Sri Sri Kotturi's Hacks

Lydia Cho's Hacks


git icon not showing @ neovim 0.5.0

Self-Diagnosis

[x] I have searched the issues for an answer to my question.
[x] I have reviewed the NERDTree documentation(README.md).
[x] I have searched the web for an answer to my question.

Environment (for bug reports)

[x] Operating System: WSL-ubuntu
[x] vimrc settings" all settings about nerdtree and other plugins
```call plug#begin('~/.vim/plugged')

Plug 'tiagofumo/vim-nerdtree-syntax-highlight'                  " nerdtree highlight
Plug 'ryanoasis/vim-devicons'                                   " nerdtree icon
Plug 'preservim/nerdtree'                                       " nerdtre
Plug 'Xuyuanp/nerdtree-git-plugin'
call plug#end()
let g:loaded_nerdtree_git_status = 1
let g:NERDTreeShowGitStatus = 1
let g:NERDTreeGitStatusShowClean = 1 " default: 0
let g:NERDTreeFileExtensionHighlightFullName = 1
let g:NERDTreeExactMatchHighlightFullName = 1
let g:NERDTreePatternMatchHighlightFullName = 1
nmap r :NERDTreeFocus | R |
let NERDTreeShowLineNumbers=0
let g:NERDTreeNodeDelimiter = "\u00a0"
let g:NERDTreeGitStatusUseNerdFonts = 1
let g:NERDTreeGitStatusIndicatorMapCustom = {
\ 'Modified'  :'✹',
\ 'Staged'    :'✚',
\ 'Untracked' :'✭',
\ 'Renamed'   :'➜',
\ 'Unmerged'  :'═',
\ 'Deleted'   :'✖',
\ 'Dirty'     :'✗',
\ 'Ignored'   :'☒',
\ 'Clean'     :'✔',
\ 'Unknown'   :'?',
\ }
- Other NERDTree-dependent Plugins
    - [ ] jistr/vim-nerdtree-tabs
    - [x] ryanoasis/vim-devicons
    - [x] tiagofumo/vim-nerdtree-syntax-highlight
    - [ ] Others (specify):
- [ ] I've verified the issue occurs with only `nerdtree-git-plugin` installed.

[ ] Copy-Paste call gitstatus#doctor#Say() outputs

Steps to Reproduce the Issue

I recently switched to neovim(0.5.0)
git status icon not showing (Thank you for always your kind answer)

Current Result (Include screenshots where appropriate.)

Expected Result

sorry.. my setting is wrong....
let g:loaded_nerdtree_git_status = 1 -> "let g:loaded_nerdtree_git_status = 1


Adding ipvsadmin binary

Related to https://github.com/boot2docker/boot2docker/pull/1079
I thought it didn't really make sense to have the IPVS modules without ipvsadm installed... I guess installing it from Debian and then dropping it into the image isn't clean, but since Tiny Core Linux isn't maintaining a package for ipvsadm, I thought that might just be fine.
Please let me know if that's too ugly of a hack to merge.

Indeed -- copying this binary from Debian directly as-is is quite a bit hairier than I'm comfortable with.  Can't this be run from inside a container instead? (using --device to give it access to the appropriate device nodes)


where is the manga section?

Hey! This repository is still in development, although I have halted development due to exam preparations, and I am working on my mobile app version of Tengoku. I am planning to rewrite this website with NextJS v13.x to improve performance and refactor my codebase, so stay tuned! Thank you for showing interest in my project.


 support for input groups

As per #22283, <select> inside input groups generally work, except for the vertical alignment in Chrome/macOS (possibly also other browsers), which is caused by display: flex applied to the select element.
IMHO this should be supported in BS4 just like it was in BS3.
Demo (Bootstrap 4): https://plnkr.co/edit/VzaynmMMWmahVQVjviO7?p=preview
Demo (Bootstrap 3): https://plnkr.co/edit/zV3Y4AKDNXaB4iCDfNiS?p=preview

To be clear, select elements have never been supported in input groups, in v3 or v4.

Playing with demo, I see that, in Chrome, the letters with descender (g, j, p, q and y) are truncated in normal and large select. It's all right with form-control-sm, custom-select (or if they are inside an input-group). That’s really annoying because g completely looks like q, and j like i too… Can this help to fix the first two cases behaviour?

See https://plnkr.co/edit/XkGRvb4nMTYl5io3aPRL?p=preview


Added JavaScript Tutorials for Beginners in Hindi

Fixes #2078
Added and updated the JavaScript section.
Hope this solves the issue.
Looking forward for merging this PR.

Fixes Issue #2078

Changes proposed
Added a javascript tutorial for beginners and updated the link under javascript section.

Screenshots

Note to reviewers

Hey @CBID2 thanks for you suggestion will implement it soon.

Hey @CBID2 done all the changes can you please just review it and merge it. :)

Didn't need that recent change. It was all good.

@DevanshKyada27
Thanks for the changes. The deployment got failed. I already reviewed it, why do you even make changes.
No worries, fix it.

@CBID2
He made a PR without being assigned.

@DevanshKyada27 Thanks for the changes. The deployment got failed. I already reviewed it, why do you even make changes.
No worries, fix it.

Hey @Anmol-Baranwal I am so sorry for it. I was a bit confused so by mistake I made that change. But now fixed it.

@CBID2 He made a PR without being assigned.

Hey @Anmol-Baranwal actually the comment section was locked and was not able to ask about the problem to be assigned to me. So sorry for the inconvenience caused.

@CBID2 He made a PR without being assigned.

Hey @Anmol-Baranwal actually the comment section was locked and was not able to ask about the problem to be assigned to me. So sorry for the inconvenience caused.

No problem @DevanshKyada27. Just remember to ask or create an issue next time:)


Added locations to Bohl 2022 (Cambodia) and Wu 2020 (Wuhan). Reran prepare_dashboard.sh

@jeffkaufman I'm keeping this a draft pull request as I have two open questions:

sample_metadata_classifier.py got reformatted, even though I'm using black. Is this ok or will I need to fix something on my side here?
I ran prepare_dashboard.sh overnight after i) merging the newest commits from main, and ii) changing sample_metadata_classifier.py to contain location data for Bohl 2022 and Wu 2020. Now I am unsure if some of the files that were created by prepare_dashboard.sh were changed due to i) or ii). Do you have more insights here?

sample_metadata_classifier.py got reformatted, even though I'm using black. Is this ok or will I need to fix something on my side here?

The mgs-pipeline repo is not currently using black or any other automatic formatter.  I'd be fine with either:

Don't auto-format, just make your change to sample_metadata_classifier.py
Keep your auto-formatting, and also set up GitHub actions to require all checkins are black-formatted the way we do for the P2RA repo

@jeffkaufman I'm checking if prepare-dashboard.sh works fine through #53. Is this branch good to merge?

@simonleandergrimm It doesn't look like you've run prepare-dashboard-data.sh since making this change?  Or if you have you haven't checked in the changes?

@simonleandergrimm It doesn't look like you've run prepare-dashboard-data.sh since making this change? Or if you have you haven't checked in the changes?

@jeffkaufman I now ran prepare-dashboard.sh.


Design proposal for /itchysats/offer protocol

Tracking issue for libp2p-based network layer: https://github.com/itchysats/itchysats/issues/1595
With the capabilities of multiplexing, we have several choices in how we can send offers from the maker to a taker:

Push vs pull (i.e. maker pushes by opening a substream vs taker pulls by opening a substream)
one-shot substream vs streaming multiple offers (one substream per protocol vs reusing the same substream to send another message)

All four combinations are technically possible. The design we are proposing here is the one-shot push combination. In other words: The maker opens a substream to the taker per offer they want to send. We prefer this combination because

The maker knows when the offer changes, pushing the latest offer is more efficient.
Opening a new substream per offer is more resilient because there is less state management. If we fail to open a substream to a taker, we can mostly ignore that problem. On the next offer update, we will naturally try again.

At the moment, we send an (optional) short and an (optional) long offer to the taker. We can keep these data structures as is for this migration.
Optional scope extension
There is an optional scope extension that we may want to contemplate. We have been talking about re-modelling our usage of orders and offers for a while. In particular, we could leave the data structure almost as is but only remove the OrderId from it, thus not invalidating an offer just because it is taken by a taker. With https://github.com/itchysats/itchysats/pull/1455, we are re-sending another offer once the current one is taking. This suggests that an offer should not actually get invalidated, the offered price is still valid for the next taker!
Many parts of our system currently rely on the concept of a unique OrderId per offer/order. We can still maintain that by designing a compatible /itchysats/order protocol that allows peers to place an order with another peer. An order to be placed would come with a unique ID and thus, the invariant of one unique ID per offer/order is still maintained.

Design looks good!

I agree on pushing the latest offer. That way messages are sent when the offer actually changes.
Are there any disadvantages related to using a one-shot substream?

Regarding the optional scope:

I'm for the suggestion of moving the OrderId to the Order and away from the Offer.
Could this be an opportunity to decouple the offer from the funding_rate? I've been thinking that the funding_rate is a value that theoretically changes much less frequently than the offer. Interestingly, I think the offer information is only useful when the UI is open and when the taker tries to take an offer. I wonder if we're sending a lot more data around than we need to.

Design looks good!

I agree on pushing the latest offer. That way messages are sent when the offer actually changes.
Are there any disadvantages related to using a one-shot substream?

Regarding the optional scope:

I'm for the suggestion of moving the OrderId to the Order and away from the Offer.
Could this be an opportunity to decouple the offer from the funding_rate? I've been thinking that the funding_rate is a value that theoretically changes much less frequently than the offer. Interestingly, I think the offer information is only useful when the UI is open and when the taker tries to take an offer. I wonder if we're sending a lot more data around than we need to.

are you postulating that we have a separate protocol /itchysats/funding_rate?

Could this be an opportunity to decouple the offer from the funding_rate? I've been thinking that the funding_rate is a value that theoretically changes much less frequently than the offer. Interestingly, I think the offer information is only useful when the UI is open and when the taker tries to take an offer. I wonder if we're sending a lot more data around than we need to.

Interesting idea. We still want to include it in the offer for display purposes right? However, which exact funding rate to use for a rollover should perhaps be part of the rollover protocol. I'll take that into account when I continue on the rollover protocol tomorrow.

are you postulating that we have a separate protocol /itchysats/funding_rate?

Yeah, we could. The maker could then push out updates to the funding rate generally every 8 hours (like BitMEX does for example).

We still want to include it in the offer for display purposes right?

Do we have to? The funding rate(s) usually outlasts the current offer: it doesn't necessarily change after an offer is taken. They can appear together for display purposes, but they could originate from different protocols.
I think it would be a nice composition if we have /itchysats/offer and /itchysats/funding_rate protocols which enable the taker to initiate an /itchysats/order protocol.

I think it would be a nice composition if we have /itchysats/offer and /itchysats/funding_rate protocols which enable the taker to initiate an /itchysats/order protocol.

Possibly! Even though they might change at different rates, making protocols more fine granular also comes with trade offs and overhead. I think having a separate funding_rate protocol might be worth it but I am not entirely sure.
For example, in the proposal for the rollover protocol, I am including the funding-rate in the Accept message to allow the protocol to be idempotent. Thus, the funding_rate sent via this protocol would only be used for display purposes so I am not sure if it is worth separating.

Possibly! Even though they might change at different rates, making protocols more fine granular also comes with trade offs and overhead. I think having a separate funding_rate protocol might be worth it but I am not entirely sure.

I do agree that introducing a separate protocol for the funding_rate has tradeoffs.

For example, in the proposal for the rollover protocol, I am including the funding-rate in the Accept message to allow the protocol to be idempotent. Thus, the funding_rate sent via this protocol would only be used for display purposes so I am not sure if it is worth separating.

I have yet to review the rollover protocol proposal in depth, so I can't say whether I agree with including the funding_rate in one of its messages yet. But if we go for that approach I agree that it would be much less useful to define a separate protocol to relay the funding rate.

For the initial protocol I would vote for keeping the funding_rate as part of the offer. Otherwise the scope becomes a bit of a Pandora's box. We can easily evolve the protocol once migrated.

It would be nice if the new protocol passed in lot size (we still have it hard-coded!): #1266


Replace cidr_block with ipv4_cidr_block in README

Solves #121, see https://github.com/cloudposse/terraform-aws-dynamic-subnets#usage for further evidence.

/terratest

From the top of the READme file involved
  ** DO NOT EDIT THIS FILE
  **
  ** This file was automatically generated by the `cloudposse/build-harness`.
  ** 1) Make all changes to `README.yaml`
  ** 2) Run `make init` (you only need to do this once)
  ** 3) Run`make readme` to rebuild this file.

@MajinBuuOnSecurity Can you apply the fix to the right file and execute the rebuild?


Support NVM with sourcetree

I am using nvm and sourcetree for git management. though CLI it works fine, sourcetree failed to find node with NVM. so detect NVM and use that.

Coverage remained the same at 95.413% when pulling 76b5e13f612ce035b911141adcb5e4ee3b70f33b on whomobile:master into f25888ffc67d21beaa1572b53ab6704a67266b64 on observing:master.


Initial map position before initPosition attribute

Hi, thanks for your work.
When the map opens, the displayed position is in Egypt before the initPosition attribute is applied. Can we change the starting position of the map? Thank you in advance for your feedback

@Bylinkk feel free to try #45 and let me know if that solves the issue!

Fixed in version 3.1.0 ✅


Remove keys

[ ] Use question label instead of key in program queries
[ ] Remove Keys section
[ ] Replace input type "type" with Number Input or something similar
[ ] Infer key type from question input type
[ ] Add input type to nested multiselect questions

This issue will break the City of Edmonton's current YCB schema. We will need to write a script to transform it to the new keyless schema.

@slmyers With this issue, we're trying to completely get rid of keys. Is there any reason you think this couldn't be done?

The keys are index mappings. So, I guess if you infer keys from input types and then use that to map the index, it should be good.
index mappings ~~ db schema
https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping.html

Fixed by @CodyGramlich with #87.


sent SIGINT to subprocesses instead of instant kill on Ctrl+C

closes via a56cd6b and released as 0.3.0 see


Rework of provider functionality in WorkQueueExecutor

This is work done by @tjdasso that's been recast by @btovar. This PR is essentially #1498 with additional cleanups from @btovar.
This PR adds provider support to the WQEX, such that it behaves consistently with other executors when it comes to scaling. Secondly, the decoupling of providers makes it easier to use existing providers as well as more custom WQ providers in the future.

working on the conflicts

@yadudoc @ZhuozhaoLi:

conflicts with master have been fixed.
hostname can now be specified.
testing uses the local provider, rather than a manually launched worker
worker and password file are specified automatically to the condor provider

I tested this branch with the test parsl/tests/workqueue_tests/test_scale.py on local and theta (local and cobalt provider). The config in wqex_local.py  does not work until I commented out project_name="WQexample". I think it may be better to set the hostname in the config.
Theta is working fine. Are there any other further changes for this PR?

@ZhuozhaoLi Nothing more is planned to go into this PR. It's ready for review and merge.


Misc QR Code and Send Improvements

Expected Behavior

[ ] QR Code should include address, sharing QR code should also include some more information beyond the code (photo + number if verified + address). Design (Mockup below)
[ ] QR code button misaligned on send/Request Flows
[ ] The “Send” button in the send flow no longer floats above the keyboard on Android. This is the current behavior on iOS, we should fix both

Current Behavior
What is the current behavior?

Added design

Removed the third requirement, it's been accounted for in DEK updates


Tweet about TechWire

@snewt-n Just let me know if you don't have time.
http://wraltechwire.com/three-finalists-to-pitch-for-5k-prize-in-nc-datapalooza-/17087684/?utm_medium=email&utm_campaign=wral-ml-local_tech_wire%3AWRAL+Tech+Wire+Morning+Headlines+(20171103080007)&utm_source=second-street


No error message when typesdb is not configured in [[collectd]] section

Bug report
System info:
influxdb-1.0.0-beta3
Steps to reproduce:

Remove typesdb from the [[collectd]] section
Start the service.
Look into logs:

Jan 29 00:04:54 michalrus_com influxd[3858]: [shard] 2017/01/29 00:04:54 /var/db/influxdb/data/collectd/default/1 database index loaded in 1.471641ms
Jan 29 00:04:54 michalrus_com influxd[3858]: [store] 2017/01/29 00:04:54 /var/db/influxdb/data/collectd/default/1 opened in 77.425071ms
Jan 29 00:04:54 michalrus_com influxd[3858]: [subscriber] 2017/01/29 00:04:54 opened service
Jan 29 00:04:54 michalrus_com influxd[3858]: [monitor] 2017/01/29 00:04:54 Starting monitor system
Jan 29 00:04:54 michalrus_com systemd[1]: influxdb.service: Main process exited, code=exited, status=1/FAILURE

No error message, just an exit(1) — even with log level set to debugging.

Insanity.

@michalrus have you tried the most recent version (1.2.0)?

No.
On Jan 31, 2017 5:22 PM, "Edd Robinson"<EMAIL_ADDRESS>wrote:

@michalrus https://github.com/michalrus have you tried the most recent
version (1.2.0)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/influxdata/influxdb/issues/7902#issuecomment-276411793,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEKf1K5MYK2Lkmuv6kkVPQkELVfbng6vks5rX1_FgaJpZM4LwqQR
.


OpenBSD 6.7 -stable build fail

ssh3@balamut:build$ uname -a
OpenBSD balamut.td.kms 6.7 GENERIC.MP#2 amd64
ssh3@balamut:build$ clang -v
OpenBSD clang version 8.0.1 (tags/RELEASE_801/final) (based on LLVM 8.0.1)
Target: amd64-unknown-openbsd6.7
Thread model: posix
InstalledDir: /usr/bin
ssh3@balamut:build$ cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX:PATH=../tdlib ..
-- The CXX compiler identification is Clang 8.0.1
-- The C compiler identification is Clang 8.0.1
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Could NOT find ccache (this is NOT an error)
-- Found OpenSSL: /usr/lib/libcrypto.so.46.1 (found version "2.0.0")
-- Found OpenSSL: /usr/include /usr/lib/libssl.so.48.1;/usr/lib/libcrypto.so.46.1
-- Performing Test HAVE_STD14
-- Performing Test HAVE_STD14 - Success
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE
-- Performing Test HAVE_CXX_FLAG_WALL
-- Performing Test HAVE_CXX_FLAG_WALL - Success
-- Performing Test HAVE_CXX_FLAG_WEXTRA
-- Performing Test HAVE_CXX_FLAG_WEXTRA - Success
-- Performing Test HAVE_CXX_FLAG_WIMPLICIT_FALLTHROUGH_2
-- Performing Test HAVE_CXX_FLAG_WIMPLICIT_FALLTHROUGH_2 - Failed
-- Performing Test HAVE_CXX_FLAG_WPOINTER_ARITH
-- Performing Test HAVE_CXX_FLAG_WPOINTER_ARITH - Success
-- Performing Test HAVE_CXX_FLAG_WCAST_QUAL
-- Performing Test HAVE_CXX_FLAG_WCAST_QUAL - Success
-- Performing Test HAVE_CXX_FLAG_WSIGN_COMPARE
-- Performing Test HAVE_CXX_FLAG_WSIGN_COMPARE - Success
-- Performing Test HAVE_CXX_FLAG_WDUPLICATED_BRANCHES
-- Performing Test HAVE_CXX_FLAG_WDUPLICATED_BRANCHES - Failed
-- Performing Test HAVE_CXX_FLAG_WDUPLICATED_COND
-- Performing Test HAVE_CXX_FLAG_WDUPLICATED_COND - Failed
-- Performing Test HAVE_CXX_FLAG_WALLOC_ZERO
-- Performing Test HAVE_CXX_FLAG_WALLOC_ZERO - Failed
-- Performing Test HAVE_CXX_FLAG_WLOGICAL_OP
-- Performing Test HAVE_CXX_FLAG_WLOGICAL_OP - Failed
-- Performing Test HAVE_CXX_FLAG_WTAUTOLOGICAL_COMPARE
-- Performing Test HAVE_CXX_FLAG_WTAUTOLOGICAL_COMPARE - Success
-- Performing Test HAVE_CXX_FLAG_WVLA
-- Performing Test HAVE_CXX_FLAG_WVLA - Success
-- Performing Test HAVE_CXX_FLAG_WNON_VIRTUAL_DTOR
-- Performing Test HAVE_CXX_FLAG_WNON_VIRTUAL_DTOR - Success
-- Performing Test HAVE_CXX_FLAG_WUNUSED_PARAMETER
-- Performing Test HAVE_CXX_FLAG_WUNUSED_PARAMETER - Success
-- Performing Test HAVE_CXX_FLAG_WCONVERSION
-- Performing Test HAVE_CXX_FLAG_WCONVERSION - Success
-- Performing Test HAVE_CXX_FLAG_WSIGN_CONVERSION
-- Performing Test HAVE_CXX_FLAG_WSIGN_CONVERSION - Success
-- Performing Test HAVE_CXX_FLAG_WCXX14_COMPAT_PEDANTIC
-- Performing Test HAVE_CXX_FLAG_WCXX14_COMPAT_PEDANTIC - Success
-- Performing Test HAVE_CXX_FLAG_WDEPRECATED
-- Performing Test HAVE_CXX_FLAG_WDEPRECATED - Success
-- Performing Test HAVE_CXX_FLAG_QUNUSED_ARGUMENTS
-- Performing Test HAVE_CXX_FLAG_QUNUSED_ARGUMENTS - Success
-- Performing Test HAVE_CXX_FLAG_WODR
-- Performing Test HAVE_CXX_FLAG_WODR - Success
-- Performing Test HAVE_CXX_FLAG_FLTO_ODR_TYPE_MERGING
-- Performing Test HAVE_CXX_FLAG_FLTO_ODR_TYPE_MERGING - Failed
-- Found ZLIB: /usr/lib/libz.so.5.0 (found version "1.2.3")
-- Found ZLIB: /usr/include /usr/lib/libz.so.5.0
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success
-- Performing Test GNU_READLINE_FOUND
-- Performing Test GNU_READLINE_FOUND - Failed
-- Could NOT find Readline (missing: READLINE_INCLUDE_DIR READLINE_LIBRARY)
-- Could NOT find Readline (this is NOT an error)
-- Configuring done
-- Generating done
-- Build files have been written to: /usr/src/td/build
ssh3@balamut:build$ cmake --build . --target install
...
Scanning dependencies of target tg_cli
[ 67%] Building CXX object CMakeFiles/tg_cli.dir/td/telegram/cli.cpp.o
[ 67%] Building CXX object CMakeFiles/tg_cli.dir/td/generate/auto/td/telegram/td_api_json.cpp.o
[ 67%] Linking CXX executable tg_cli
ld: error: undefined symbol: td::Td::request(unsigned long long, td::tl::unique_ptr<td::td_api::Function>)
>>> referenced by ClientActor.cpp
>>>               ClientActor.cpp.o:(td::ClientActor::request(unsigned long long, td::tl::unique_ptr<td::td_api::Function>)) in archive libtdcore.a

ld: error: undefined symbol: td::Td::static_request(td::tl::unique_ptr<td::td_api::Function>)
>>> referenced by ClientActor.cpp
>>>               ClientActor.cpp.o:(td::ClientActor::execute(td::tl::unique_ptr<td::td_api::Function>)) in archive libtdcore.a

ld: error: undefined symbol: td::Td::Td(td::unique_ptr<td::TdCallback>)
>>> referenced by ClientActor.cpp
>>>               ClientActor.cpp.o:(td::ActorOwn<td::Td> td::Scheduler::create_actor<td::Td, td::unique_ptr<td::TdCallback> >(td::Slice, td::unique_ptr<td::TdCallback>&&)) in archive libtdcore.a

ld: error: undefined symbol: td::verbosity_td_init
>>> referenced by Logging.cpp
>>>               Logging.cpp.o:(.data.rel.ro..Lconstinit+0x10) in archive libtdcore.a

ld: error: undefined symbol: td::telegram_api::inputEncryptedFileBigUploaded::inputEncryptedFileBigUploaded(long long, int, int)
>>> referenced by FileManager.cpp
>>>               FileManager.cpp.o:(td::tl::unique_ptr<td::telegram_api::inputEncryptedFileBigUploaded> td::make_tl_object<td::telegram_api::inputEncryptedFileBigUploaded, long long const&, int const&, int>(long long const&, int const&, int&&)) in archive libtdcore.a

ld: error: undefined symbol: td::telegram_api::inputEncryptedFileUploaded::inputEncryptedFileUploaded(long long, int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int)
>>> referenced by FileManager.cpp
>>>               FileManager.cpp.o:(td::tl::unique_ptr<td::telegram_api::inputEncryptedFileUploaded> td::make_tl_object<td::telegram_api::inputEncryptedFileUploaded, long long const&, int const&, char const (&) [1], int>(long long const&, int const&, char const (&) [1], int&&)) in archive libtdcore.a

ld: error: undefined symbol: td::telegram_api::inputSecureFileUploaded::inputSecureFileUploaded(long long, int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, td::BufferSlice&&, td::BufferSlice&&)
>>> referenced by FileManager.cpp
>>>               FileManager.cpp.o:(td::tl::unique_ptr<td::telegram_api::inputSecureFileUploaded> td::make_tl_object<td::telegram_api::inputSecureFileUploaded, long long const&, int const&, char const (&) [1], td::BufferSlice, td::BufferSlice>(long long const&, int const&, char const (&) [1], td::BufferSlice&&, td::BufferSlice&&)) in archive libtdcore.a

ld: error: undefined symbol: td::telegram_api::inputFileBig::inputFileBig(long long, int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)
>>> referenced by FileManager.cpp
>>>               FileManager.cpp.o:(td::tl::unique_ptr<td::telegram_api::inputFileBig> td::make_tl_object<td::telegram_api::inputFileBig, long long const&, int const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >(long long const&, int const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >&&)) in archive libtdcore.a

ld: error: undefined symbol: td::telegram_api::inputFile::inputFile(long long, int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)
>>> referenced by FileManager.cpp
>>>               FileManager.cpp.o:(td::tl::unique_ptr<td::telegram_api::inputFile> td::make_tl_object<td::telegram_api::inputFile, long long const&, int const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, char const (&) [1]>(long long const&, int const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >&&, char const (&) [1])) in archive libtdcore.a

ld: error: undefined symbol: td::telegram_api::inputDocument::inputDocument(long long, long long, td::BufferSlice&&)
>>> referenced by FileManager.cpp
>>>               FileManager.cpp.o:(td::tl::unique_ptr<td::telegram_api::inputDocument> td::make_tl_object<td::telegram_api::inputDocument, long long const&, long long const&, td::BufferSlice>(long long const&, long long const&, td::BufferSlice&&)) in archive libtdcore.a

ld: error: undefined symbol: td::telegram_api::upload_saveBigFilePart::upload_saveBigFilePart(long long, int, int, td::BufferSlice&&)
>>> referenced by FileUploader.cpp
>>>               FileUploader.cpp.o:(td::FileUploader::start_part(td::Part, int, long long)) in archive libtdcore.a

ld: error: undefined symbol: td::telegram_api::upload_saveFilePart::upload_saveFilePart(long long, int, td::BufferSlice&&)
>>> referenced by FileUploader.cpp
>>>               FileUploader.cpp.o:(td::FileUploader::start_part(td::Part, int, long long)) in archive libtdcore.a

ld: error: undefined symbol: vtable for td::telegram_api::upload_saveBigFilePart
>>> referenced by FileUploader.cpp
>>>               FileUploader.cpp.o:(td::telegram_api::upload_saveBigFilePart::~upload_saveBigFilePart()) in archive libtdcore.a
the vtable symbol may be undefined because the class is missing its key function (see https://lld.llvm.org/missingkeyfunction)

ld: error: undefined symbol: vtable for td::telegram_api::upload_saveFilePart
>>> referenced by FileUploader.cpp
>>>               FileUploader.cpp.o:(td::telegram_api::upload_saveFilePart::~upload_saveFilePart()) in archive libtdcore.a
the vtable symbol may be undefined because the class is missing its key function (see https://lld.llvm.org/missingkeyfunction)

ld: error: undefined symbol: td::telegram_api::upload_saveBigFilePart::fetch_result(td::TlBufferParser&)
>>> referenced by FileUploader.cpp
>>>               FileUploader.cpp.o:(td::Result<td::telegram_api::upload_saveBigFilePart::ReturnType> td::fetch_result<td::telegram_api::upload_saveBigFilePart>(td::BufferSlice const&, bool)) in archive libtdcore.a

ld: error: undefined symbol: td::telegram_api::upload_saveFilePart::fetch_result(td::TlBufferParser&)
>>> referenced by FileUploader.cpp
>>>               FileUploader.cpp.o:(td::Result<td::telegram_api::upload_saveFilePart::ReturnType> td::fetch_result<td::telegram_api::upload_saveFilePart>(td::BufferSlice const&, bool)) in archive libtdcore.a

ld: error: undefined symbol: td::telegram_api::to_string(td::TlObject const&)
>>> referenced by utils.cpp
>>>               utils.cpp.o:(td::create_storer(td::telegram_api::Function const&)) in archive libtdcore.a

ld: error: undefined symbol: td::telegram_api::upload_getFile::fetch_result(td::TlBufferParser&)
>>> referenced by FileDownloader.cpp
>>>               FileDownloader.cpp.o:(td::Result<td::telegram_api::upload_getFile::ReturnType> td::fetch_result<td::telegram_api::upload_getFile>(td::BufferSlice const&, bool)) in archive libtdcore.a

ld: error: undefined symbol: td::telegram_api::to_string(td::TlObject const&)
>>> referenced by FileDownloader.cpp
>>>               FileDownloader.cpp.o:(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > td::telegram_api::to_string<td::telegram_api::upload_fileCdnRedirect>(td::tl::unique_ptr<td::telegram_api::upload_fileCdnRedirect> const&)) in archive libtdcore.a

ld: error: undefined symbol: td::telegram_api::upload_reuploadCdnFile::fetch_result(td::TlBufferParser&)
>>> referenced by FileDownloader.cpp
>>>               FileDownloader.cpp.o:(td::Result<td::telegram_api::upload_reuploadCdnFile::ReturnType> td::fetch_result<td::telegram_api::upload_reuploadCdnFile>(td::BufferSlice const&, bool)) in archive libtdcore.a

ld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)
c++: error: linker command failed with exit code 1 (use -v to see invocation)
*** Error 1 in . (CMakeFiles/tg_cli.dir/build.make:111 'tg_cli': /usr/local/bin/cmake -E cmake_link_script CMakeFiles/tg_cli.dir/link.txt --...)
*** Error 2 in . (CMakeFiles/Makefile2:388 'CMakeFiles/tg_cli.dir/all': /usr/bin/make -f CMakeFiles/tg_cli.dir/build.make CMakeFiles/tg_cli....)
*** Error 2 in /usr/src/td/build (Makefile:141 'all': /usr/bin/make -f CMakeFiles/Makefile2 all)

The errors are very strange. Could you try to build from a clean repository from scratch, using instructions from https://tdlib.github.io/td/build.html?

The errors are very strange. Could you try to build from a clean repository from scratch, using instructions from https://tdlib.github.io/td/build.html?

Had the same issue on 6.7-RELEASE fresh install, followed instructions from that url.

Are you building TDLib 1.6.0 (git checkout v1.6.0 from the build instructions)?
Could you show the whole cmake output?

@tipsybsd Could you ignore git checkout v1.6.0 (or do git checkout master) and try to build the latest version?

@levlam, the whole log attached.
tdlib-building.log

-- Could NOT find Readline (missing: READLINE_INCLUDE_DIR READLINE_LIBRARY)
-- Could NOT find Readline (this is NOT an error)

@levlam
tdlib-master-building.log

su -
pkg_add git gperf php-7.2.10 cmake
exit
git clone https://github.com/tdlib/td.git
cd td
git checkout v1.6.0
rm -rf build
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX:PATH=../tdlib ..
cmake --build . --target install
cd ..
cd ..
ls -l td/tdlib

@isopen
Yes, I was following these instructions, but git gperf php-7.2.10 cmake already installed.

git clone https://github.com/tdlib/td.git
cd td
git checkout v1.6.0
rm -rf build
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX:PATH=../tdlib ..
cmake --build . --target install

su -
pkg_add git gperf php-7.2.10 cmake
exit
git clone https://github.com/tdlib/td.git
cd td
git checkout v1.6.0
rm -rf build
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX:PATH=../tdlib ..
cmake --build . --target prepare_cross_compiling
cd ..
php-7.2 SplitSource.php
cd build
cmake --build . --target install
cd ..
php-7.2 SplitSource.php --undo
cd ..
ls -l td/tdlib

df -h
cd /home

@levlam

@ssh3 @tipsybsd I reproduced this in OpenBSD 6.7 and the primary cause of the issue is /usr/bin/ar: libtdcore.a: Memory exhausted. The libtdcore.a file is truncated, but it still created, so the build continues and fails on linking.

@ssh3 @tipsybsd You need to adjust the limit in /etc/login.conf or build from root.

@levlam<PHONE_NUMBER>10110100011100000101000000111000101110001010100000111000101110
0010111000001110001011100001110000001110001011100010111000010110000011100
0101110001011010000111000101110001000010000111000101110000110100000111000
1011110001110000001110001011100001110100001110001011110010110000010100000
0111000101110001011110000111000101110001011100000111000101110001010110000
1110001011110001110000001110001011110010000000001110001011100010000100001
1100010111000101011000011100010111000101110000011100010111100011010000011
100010111100101100000011100001110000101111

It turned out that build from root also failed on OpenBSD. I wasn't able to reproduce this because I always built with SplitSource.php applied before building. Now build instructions generator is updated to always use SplitSource.php on OpenBSD, which should fix the error.

@levlam  I can confirm it works use the build commands generator on OpenBSD6.8.
I tried to use non-root user to build, but it still complained "/usr/bin/ar: libtdcore.a: Memory exhausted".
anyway, build td with root will fix this(or change some settings in /etc/login.conf may help, didn't try)


compat: Reapply Effect icon on Effects tab (possibly Midi)

The "Reapply Effect" icon is not present on the effects tab. This is part of Midi QoL or a related module that comes with it.
Reference
From the discord community;
There is suppose to be an icon for reapplying an active effect from the sheet, but on tidy is not there, see the small hand icon on the first capture vs the second
Modules and Foundry Version:
Tidy 3.4.2
Midi 11.4.32
Dnd 3.1.2
Foundry v11.315

https://discord.com/channels/1167985253072257115/1243426898240081930/1243426898240081930

After speaking with folks on Tim Posney's server, this icon is apparently no longer used and/or on its way out.


[BUG] - Latest 2-8-1.0 Interactive kneeboard doesn't show

Describe the bug
Kneeboard - interactive bit is gray, other normal kneeboard pages work ok
To Reproduce
Open kneeboard, check if interactive kneeboard pages can be opened
Expected behavior
Interactive kneeboard pages should open
Screenshots

Additional context
I tried in DCS AH-64 module, but probably its not related to module. I installed MSI version over existing  one - VAICOM.PRO.for.DCS.World.msi

You have the brightness slider all the way down, try turning it up

You have the brightness slider all the way down, try turning it up

No, its all the way up...

Are you able to change pages with the Vaicom commands, ATC Page, Overlord Page, etc?

Are you able to change pages with the Vaicom commands, ATC Page, Overlord Page, etc?

No, it doesn't work...Only other normal kneeboard pages works

Maybe the way i did the upgrade is problem? I just ran MSI installer package over existing installation of prevous comunity version?

Seems to be a Mirage F1 only problem. Checked different moduls and Interactive Kneeboard works fine

I have problem with dcs ah-64...

Closing this one as Mirage F-1 has an issue that remains but other Kneeboards fixed for next release.


Manually dismiss popups when the window moves, or the SUI scrolls

Summary of the Pull Request
BODGY!
This solution was suggested in https://github.com/microsoft/microsoft-ui-xaml/issues/4554#issuecomment-887815332.
When the window moves, or when a ScrollViewer scrolls, dismiss any popups that are visible. This happens automagically when an app is a real XAML app, but it doesn't work for XAML Islands.
References

upstream at https://github.com/microsoft/microsoft-ui-xaml/issues/4554

PR Checklist

[x] Closes #9320
[x] I work here
[ ] Tests added/passed
[ ] Requires documentation to be updated

Detailed Description of the Pull Request / Additional comments
Unfortunately, we've got a bunch of scroll viewers in our SUI. So I did something bodgyx2 to make our life a little easier.
DismissAllPopups can be used to dismiss all popups for a particular UI element. However, we've got a bunch of pages with scroll viewers that may or may not have popups in them. Rather than define the same exact body for all their ViewChanging events, the HasScrollViewer struct will just do it for you!
Inside the HasScrollViewer stuct, we can't get at the XamlRoot() that our subclass implements. I mean, we can, but when XAML does it's codegen, XAML won't be able to figure it out.
Fortunately for us, we don't need to! The sender is a UIElement, so we can just get their XamlRoot().
So, you can fix this for any SUI page with just a simple
-    <ScrollViewer>
+    <ScrollViewer ViewChanging="ViewChanging">

-    struct AddProfile : AddProfileT<AddProfile>
+    struct AddProfile : public HasScrollViewer<AddProfile>, AddProfileT<AddProfile>

Validation Steps Performed

the window doesn't close when you move it
the popups do close when you move the window
the popups close when you scroll any SUI page

I had an even wackier idea.
Is it possible to do this?
<Page
    xmlns:local="whatever local is in these projects"

<ScrollViewer ViewChanging="local:StaticDismissHelperClass.ViewChanging">

(I wouldn't block for this suggestion, but it might make our lives easier if you can bind to like... static event handlers from other classes?)

CONFLICTS :O


Add source modal has incomplete commands for crontab

Describe the bug
Add source modal has incomplete commands for crontab
To Reproduce
Steps to reproduce the behavior:

Go to 'Add a source'
Click through setting up ocp provider
See Configure data collection screen
Commands on this step are missing some items

Expected behavior
crontab -u <username> -e
 */45 * * * * /path/to/ocp_usage.sh --collect --e OCP_CLUSTER_ID=<YOUR_OCP_IDENTIFIER>
Screenshots

Desktop (please complete the following information):

OS: Fedora
Browser: Chrome
Version: 77

Additional context
Seeing this issue on CI beta

@dayleparker can you confirm?
thanks.

I just checked the onboarding doc and we are missing the part of the second command, so I've added it now too:
--e OCP_CLUSTER_ID=<YOUR_OCP_IDENTIFIER>

@dayleparker
This is still not % correct.. We should be pulling the cluster identifier from the wizard flow.
We set the ID on the previous page so should display that in the copy command line. See screenshots,

It's also strange that we copy to clipboard the command without the real username crontab -u <username> -e maybe we should just not have the copy to clipboard link on this one?

@lcouzens closing this in favor of #1070


Move dependencies to this plugin and use Java version 1.8

The dependencies are included to reduce the amount of setup required to use react-native-spokestack.
react-native-track-player sets the same compileOptions. It seems to help with some compile errors.
Updates the setup instructions in the README. The goal is to get it down to react-native link and adding <uses-permission android:name="android.permission.RECORD_AUDIO" />, but it currently still requires some of the packagingOptions to avoid duplicate lib imports from java land. The ideal solution would be to figure out where the duplicates are coming from and exclude them, but I didn't want to spend too much time on that.

Ref #15

@noelweichbrodt Yea I have them working in radiobrain.


Poke around with JWT Authentication Tokens

Although .NET is great how do we link to the wider web ie log in with a user's normal account?  And possibly link to Facebook or Google?  At the moment I'm only interested in them signing in with an email and password, but is that still catered for here?  We shall see.

JWT Theory and Investigation
OK, so this is taking a while as I've been dipping into regular .NET authentication and looking to see how the salt and the hash work.
This is a slightly different mechanism and I want to look into it!

JWT Article
It's fairly modern ie January 2018 so perhaps 2 years old now.  But I don't think much has changed in that interim period, and if it has I will find out about it very soon!
It's based in ASP.NET Core v2
Base User Class is provided by .NET and is called IdentityUser which maps directly to the built-in AspNetUsers table in the built-in database.
We can also extend this class to add our own fields, for example, Facebook.
public class MyUser : IdentityUser{
  // Extended Properties
  public string FirstName { get; set; }
  public string LastName { get; set; }
  public long? FacebookId { get; set; }
  public string PictureUrl { get; set; }
}

User Roles
We can also have different user roles, for example a user can be a staff member or a customer.
So we can have classes to reflect different user roles.
Here is one to simulate a user which is also a customer:
public class Customer
{
 public int Id { get; set; }
 public string IdentityId { get; set; }
 public AppUser Identity { get; set; }  // navigation property
 public string Location { get; set; }
 public string Locale { get; set; }
 public string Gender { get; set; }
}

Context
The Identity classes are mapped directly so we don't have to explicitly mention them.
public class ApplicationDbContext : IdentityDbContext<AppUser>
{
  public ApplicationDbContext(DbContextOptions options)
        : base(options)
  {
  }

 public DbSet<Customer> Customers { get; set; }
}

Inject the context
Finally, we can inject the context into the Startup.cs
public void ConfigureServices(IServiceCollection services)
{
  // Add framework services.
  services.AddDbContext(options =>
      options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection"),
      b => b.MigrationsAssembly("AngularASPNETCore2WebApiAuth")));
...

Add database
create database with
# create migrations
dotnet ef migrations add initial
# create database
dotnet ef database update

... this goes on and gets quite complex so I'm not sure if I am capable of running this through right now, or how beneficial it will be?
Not sure ...!
Let's try another tack first ...  just simple raw JWT!

Simple Raw JWT Tokens
Let's see if we can create some simple raw JWT understanding
Install node and run
var jwt = require('jwt-simple');
var payload = { foo: 'bar' };
var secret = 'xxx';
console.log('secret is')
console.log(secret)

// HS256 secrets are typically 128-bit random strings, for example hex-encoded:
// var secret = Buffer.from('fe1a1915a379f3be5394b64d14794932', 'hex')

// encode
var token = jwt.encode(payload, secret);
console.log("token is")
console.log(token);

// decode
var decoded = jwt.decode(token, secret);
console.log("decoded data is")
console.log(decoded); //=> { foo: 'bar' }

Oh well the library was not installed so I installed it
sudo npm install yarn -g
sudo yarn global add jwt-simple
# this did not work so I carried on
touch package.json // also edit it to add {} braces inside so it registers as a JSON
npm install jwt-simple --save
# now it works
node test.js // finally works!

The output is
secret is
xxx
token is
eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJmb28iOiJiYXIifQ.yPmf5QFV26W-3ldVCrsvRdnecy7QjA0fnCWCDLDZ-M4
decoded data is
{ foo: 'bar' }

So it looks like we need a password with which we encode and decode our data : simple!
What's all the hassle about!

JWT Theory
It looks like the JWT enables a way of securely sending data across the web (JSON data) and also the data is signed.
JWT can be used for several purposes.
The most common purpose is Authentication ie logging in and then verifying ongoing authorization.  It's very popular for SSO due to its small size
Structure of a JWT
Structure is in 3 parts
Header.Payload.Signature
xxxxx.yyyyy.zzzzzz
JWT were created in 2015 so are pretty recent
Here is the website of JWT!
https://www.iana.org/assignments/jwt/jwt.xhtml

Not found my goal!
Oh well, I've had a play around but I'm still far away from getting JWT up and running and having an application that can log in via Facebook for example.
Should I keep working? Yes, I think so but that is enough for today!
Signing out!


Search results not showing

When user searches for a movie, movie cards are not displayed on Main frame.
https://github.com/10aditya/movies-java-application/blob/master/src/Main.java

So temporarily, I am showing search results in a new JFrame