Add Expo postPublish hook

./hooks/post-publish.js will:

report a build
upload iOS and Android source maps

The postPublish hook is run in the following situations:

expo publish (publishing a new JS bundle)
expo build:[ios|android] (building a new standalone app for a particular platform)

The following config needs to be added to app.json to get Expo to run this hook:
{
  "hooks": {
    "postPublish": [
      {
        "file": "@bugsnag/expo/hooks/post-publish",
        "config": {
          "apiKey": "________" // <optional>,
          "reportBuild": true // <optional default=true>,
          "uploadSourceMaps": true // <optional default=true>
        }
      }
    ]
  }
}

Adding this config will be automated by a subsequent cli PR. If apiKey is not present in the hook config, it will look in the"extra" portion of app.json. This is the preferred place to put it, as the notifier can find it from this location too:
{
  "extra": {
    "bugsnag": {
      "apiKey": "_________"
    }
  }
}

How we treat native versionCode and bundleVersion in Expo
When reporting a build, we don't know in the postPublish hook if we're building a standalone version or a just a new JS bundle. What's more, from the user's perspective, they are only really creating one release. For this reason, we don't include versionCode or bundleVersion in the build payload.
Subsequently when the notifier is running, to prevent those builds (appVersion + native version) from being automatically created, we move the versionCode|bundleVersion data into app.metaData prefixed with native* so that it doesn't get migrated by the pipeline.
Source map lookup
Source maps are matched on stack frame location and codeBundleId (which we use Expo's revisionId for). On iOS, the stack frame location looks like:
https://d1wp6m56sqw74a.cloudfront.net/%40bengourley-bugsnag%2Fmy-expo-project%2F2.0.0%2F31439685b360e74216b03f3c164d1bba-32.0.0-ios.js
but on Android it looks like:
/data/user/0/host.exp.exponent/files/32.0.0/cached-bundle-experience-%40bengourley-bugsnag%2Fmy-expo-project-1239374583-32.0.0
Because it doesn't have a file extension, we're waiting on a pipeline update to ensure that it looks for a source map (currently it will only do this for frames with a .js, .bundle or .jsbundle extension – which means it's only possible to test Expo source maps on iOS at this point.

One more thing of note – I started publishing super unstable pre alpha releases to npm as a way of installing the development notifier inside of an app (it's quicker than attempting to do it any other way). You can install<EMAIL_ADDRESS>to test out this PR (excluding one tiny subsequent chore commit).


Font warnings

Having recently started using a Mac and OSX instead of linux, I occasionally get font warnings, for instance, when displaying ItemTable in the elements tutorial:
Users/jstevens/miniconda/envs/analytics/lib/python2.7/site-packages/matplotlib/font_manager.py:1282:
UserWarning: findfont: Font family [u'DejaVu Sans'] not found. Falling back to Bitstream Vera Sans
  (prop.get_family(), self.defaultFamily[fontext]))

It would be good to either:

Suppress these warnings.
Change the default fonts used to some mythical cross-platform configuration that works for everybody (a fair bit of work as we would still need to update tests)
Document how users can install the required fonts and make them available to matplotlib for their operating system.

These warnings are unrelated to HoloViews and are down to a faulty matplotlib installation. I've also not seen them in years, closing.


No keybindings in eshell

What did you expect to happen?
The standard keybindins for history (M-n and M-p) to work. The builtin autocomplete (i.e: pressing tab) should work too.
What actually happened?
The keys are not bound to their standard behaviour.
Additional details:

System information:

```
SYSTEM  type       gnu/linux
	config     x86_64-pc-linux-gnu
	shell      /usr/bin/zsh
	uname      Linux 5.4.72-1-lts #1 SMP Sat, 17 Oct 2020 13:30:57 +0000 x86_64
	path       (~/.config/composer/vendor/bin ~/.emacs.d/bin ~/bin ~/.local/bin /usr/local/sbin /usr/local/bin /usr/bin /usr/lib/jvm/default/bin /usr/bin/site_perl /usr/bin/vendor_perl /usr/bin/core_perl /usr/lib/emacs/27.1/x86_64-pc-linux-gnu)
EMACS   dir        ~/.emacs.d/
	version    27.1
	build      Aug 28, 2020
	buildopts  --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib --localstatedir=/var --with-x-toolkit=gtk3 --with-xft --with-wide-int --with-modules --with-cairo --with-harfbuzz 'CFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fno-plt' CPPFLAGS=-D_FORTIFY_SOURCE=2 LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now
	features   XPM JPEG TIFF GIF PNG RSVG CAIRO SOUND GPM DBUS GSETTINGS GLIB NOTIFY INOTIFY ACL GNUTLS LIBXML2 FREETYPE HARFBUZZ M17N_FLT LIBOTF ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS LIBSYSTEMD JSON PDUMPER LCMS2 GMP
	traits     (batch server-running envvar-file)
DOOM    dir        ~/dotfiles/doom_emacs/.config/doom/
	version    2.0.9
	build      HEAD -> develop 807f00a47 2020-11-02 23:56:43 -0500
	elc-files  118
	modules    (:completion (company +tng) ivy :ui doom doom-dashboard hl-todo modeline ophints (popup +defaults) window-select workspaces :editor (evil +everywhere) file-templates fold snippets :emacs dired electric ibuffer undo :term eshell :checkers syntax :tools (eval +overlay) lookup lsp magit pdf :lang (cc +lsp) emacs-lisp (javascript +lsp) latex org (php +lsp) (python +lsp) (rust +lsp) (sh +lsp) web :app (rss +org) :config (default +bindings +smartparens))
	packages   (n/a)
	unpin      (n/a)
	elpa       (n/a)
```

If I add the code (remove-hook 'eshell-mode-hook '+eshell-fix-keymap-h) in my config, most of the keys start to work again. But some of them, like Crtl-D in an empty line for kill the eshell, does not work with this change. When I switched temporally to emacs-28-git I noticed that this bug does not happens there. Thanks in advance !

As of 0efe786 this issue should be resolved. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!


adding source for Nassau County, FL

Woot!

On Mar 19, 2019, at 02:13, Al Barrentine<EMAIL_ADDRESS>wrote:
Merged #4462 into master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Intercom v2 structure fix

Description of the change

Removed the Airbyte mention as discussed.

Type of change

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Related issues

Fix #1

Checklists
Development

[ ] Lint rules pass locally
[ ] The code changed/added as part of this pull request has been covered with tests
[ ] All tests related to the changed code pass in development

Code review

[ ]  This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
[ ] "Ready for review" label attached to the PR and reviewers mentioned in a comment
[ ] Changes have been reviewed by at least one other engineer
[ ] Issue from task tracker has a link to this pull request

looks good, we need to add some information about the difference between v1 and v2, the icom APIs we talked about on the call.

yep - I've noted that. Will add this info first thing on Monday.


Various elementary necessaries

Motivation for this change
Thin out my branch so I don't have to build this stuff anymore.
They were languishing in there.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

cc @jtojnar

Success on aarch64-linux (full log)
Attempted: libunity, appstream, scour
Partial log (click to expand)
patching script interpreter paths in /nix/store/3hjvb61pkivxi5nfsx1901ys06ssswyk-libunity-7.1.4
checking for references to /build in /nix/store/3hjvb61pkivxi5nfsx1901ys06ssswyk-libunity-7.1.4...
shrinking RPATHs of ELF executables and libraries in /nix/store/qsd0vnc9zvvrdswmcr2p285786ypkm1z-libunity-7.1.4-dev
strip is /nix/store/zrs21zqcchgyabjf4xfimncdq16njizc-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/qsd0vnc9zvvrdswmcr2p285786ypkm1z-libunity-7.1.4-dev/lib
patching script interpreter paths in /nix/store/qsd0vnc9zvvrdswmcr2p285786ypkm1z-libunity-7.1.4-dev
checking for references to /build in /nix/store/qsd0vnc9zvvrdswmcr2p285786ypkm1z-libunity-7.1.4-dev...
/nix/store/3hjvb61pkivxi5nfsx1901ys06ssswyk-libunity-7.1.4
/nix/store/18dbcd0067k5sgarbqc759pw8r44hdpy-appstream-0.12.2
/nix/store/mhrsa0micm9cpccj67k06ib2bksjhx91-scour-0.37


JuliaInterpreter version restricted

When trying to work with a local version of JuliaInterpreter I encounter:
ERROR: Unsatisfiable requirements detected for package JuliaInterpreter [aa1ae85d]:
 JuliaInterpreter [aa1ae85d] log:
 ├─possible versions are: 0.9.0 or uninstalled
 ├─restricted to versions 0.8.16-0.8 by JET [c3a54625] — no versions left
 │ └─JET [c3a54625] log:
 │   ├─possible versions are: 0.5.2 or uninstalled
 │   └─JET [c3a54625] is fixed to version 0.5.2
 └─JuliaInterpreter [aa1ae85d] is fixed to version 0.9.0

Is there a known problem with newer versions?

Interesting: the problem seems to have vanished...


[QUESTION] Do we want to keep the CachingDirectory with unlimited capacity?

I'm wondering if it would be better to limit the size of this caching layer. We have set fast_field_cache_capacity to 10G by default split_footer_cache_capacity to 1G by default.

The caching directory contains the data required to run a query. It is very  , We cannot really limit it. What we can do is limit the number of concurrent split. We considered limiting the concurrency based on this memory usage and judged against it.


Added an option to addTiledImage to change the crossOriginPolicy.

addTiledImage will also check the tileSource for crossOriginPolicy.

Looks great. Can you also pass the crossOriginPolicy down into getTileSourceImplementation so it can make it to the tile source if needed? That's a private function, so there's no problem in adding another param.
@avandecreme Any other thoughts?

@avandecreme Any other thoughts?

Maybe add the corresponding test here: https://github.com/openseadragon/openseadragon/blob/030fec590eaa398b1dcf4b1f64c819bf7b98f0a1/test/modules/basic.js#L367 :)

Sounds good. @LarissaSmith are you up for making those changes?

Yes, I think these are good comments, and I'm making the changes.

@iangilman @avandecreme While adding tests for this, I realized that lines that check for the truthiness of crossOriginPolicy (e.g. https://github.com/openseadragon/openseadragon/blob/master/src/viewer.js#L2159: if (!tileSource.crossOriginPolicy && viewer.crossOriginPolicy)) could lead to unexpected results if a consumer is trying to set crossOriginPolicy to "false", but viewer.crossOriginPolicy is set to something truthy. I feel like we may want to let "false" override viewer.crossOriginPolicy here and in other lines in the PR. What do you think?

@LarissaSmith Excellent point! Sounds like we should test for undefined instead? E.g. if (tileSource.crossOriginPolicy === undefined && viewer.crossOriginPolicy !== undefined).

@iangilman I have updated the pull request.

Beautiful! Thank you for making this happen!


[RAINCATCH-603] Mitigate QS Vulnerability

Mitigate QS vulnerability (6.4.0)  https://issues.jboss.org/browse/RAINCATCH-603
Verified manually that the vulnerability is mitigated using snyk test
3rd Party Module Fix Status

Express  -  4.15.2

Build is failing - the fix may land in this PR - https://github.com/feedhenry-raincatcher/raincatcher-file-angular/pull/2

Closing as changes were moved to #2


New package: RDST v0.1.0

Registering package: RDST
Repository: https://github.com/JLChartrand/RDST.jl
Created by: @FrancisH-C
Version: v0.1.0
Commit: e030b5d05f0a7aca672b420d201705420d80438c
Git reference: master

Needs compat for Julia itself at least.

Closing as stale.


naming: use injectName vs platform in the correct places

We were incorrectly using 'platform' in places where we meant the 'injectName'

platform.name throughout all of CSS is something that can be set at runtime, to values like ios, macos, android etc.
import.meta.injectName is the build target and has higher-level values like windows, apple etc.

This PR is just being more precise with naming to avoid confusion.

#1012  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @shakyShane and the rest of your teammates on  Graphite

Are we keeping document.documentElement.dataset.platform = import.meta.injectName on inline.js as is?


Debian installation & dependencies problems

I had lot of problems to install genghis on a Debian (stretch).
The provided gem file does not install any dependencies. I had to install manually nearly all of them.
Here is the command I used :
sudo aptitude install ruby ruby-sinatra  ruby-mustache ruby-sinatra-contrib ruby-rack
sudo gem install vegas -v 0.1.8
sudo gem install sinatra -v 1.3.1
sudo gem install sinatra-contrib -v 1.3.1
sudo gem install sinatra-mustache -v 0.0.4
sudo gem install mongo -v 1.12.5
sudo gem install bson -v 1.12.5
sudo gem install bson_ext -v 1.12.5
sudo gem install genghisapp -v 2.3.11

This project is abandoned, or so it seems. :|

Yes. I thought my solution could help others. This issue has more a documentation purpose than request for evolution ;)


Is it possible to leave all cs files in csproj?

First of all THANK YOU for this useful tool. Great job!
In my old csproj file I have all cs files to compile specified. When I migrate csproj to new format all cs files disappear and new implicit logic to include cs files to project is used. Is it possible to leave all cs files in csproj for new format as well? Couldn't find any related issue to this one.
Thanks.

nope thats not possible, thats how the new format works.

nope thats not possible, thats how the new format works.

The documentation actually says that this will turn off the implicit items:
<PropertyGroup>
  <EnableDefaultItems>false</EnableDefaultItems>
</PropertyGroup>

Or, if you only want to turn off the implicit Compile items:
<PropertyGroup>
  <EnableDefaultCompileItems>false</EnableDefaultCompileItems>
</PropertyGroup>


Not possible to roll up Article CreatedDate to Case record

Just updated Rollup Helper with DLRS 2.9 on a Sandbox running Unlimited Edition.
Need to rollup the oldest CreatedDate of the articles attached to Cases. I seem to be able to use 2 different child objects: the API of our Knowledge Article Type (screenshot) or CaseArticle (in which case the relationship field should be CaseId).
When I calculate the rollup, I get an error saying that "A calculate job for rollup 'KCS Maturity' is already executing. If you suspect it is not aleady running try clearing the applicable record from the Lookup Rollup Calculate Jobs tab and try again." The "Lookup Rollup Summary Logs" tab does not display anything, so I cannot delete anything.
Cases are not being updated either. I have even disabled all Case validation rules. Not sure what I am doing wrong.
Note that I cannot use Real Time nor Scheduled modes because Knowledge Articles and CaseArticle do not support triggers.

Just checking, but your checking the "Lookup Rollup Calculate Jobs " tab? Your post refers to the "Lookup Rollup Summary Log" tab and thats not the one the message is referring to its, its the jobs one.

@jjuez Did you check this above? Happy to keep discussing with you, let me know and we can re-open this issue. 👍


Flutter 1.12.13+hotfix.9 Crash

AppleMetalGLRenderer
GLRResourceList::addResource(GLRResource*) + 40

1 AppleMetalGLRenderer
GLDContextRec::addRenderPassResources() + 68

2 AppleMetalGLRenderer
GLDContextRec::addRenderPassResources() + 68

3 AppleMetalGLRenderer
gldClearFramebufferData + 224

4 GLEngine
_glClear_Exec + 452

5 Flutter
0x0000000104118000 + 2005140

6 Flutter
0x0000000104118000 + 1953608

7 Flutter
0x0000000104118000 + 1955068

8 Flutter
0x0000000104118000 + 2084716

9 Flutter
0x0000000104118000 + 2546828

10 Flutter
0x0000000104118000 + 4281636

11 Flutter
0x0000000104118000 + 576184

12 Flutter
0x0000000104118000 + 502000

13 Flutter
0x0000000104118000 + 505508

14 Flutter
0x0000000104118000 + 502704

15 Flutter
0x0000000104118000 + 527232

16 Flutter
0x0000000104118000 + 241496

17 Flutter
0x0000000104118000 + 250332

18 CoreFoundation
_CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION + 28

19 CoreFoundation
___CFRunLoopDoTimer + 1004

20 CoreFoundation
___CFRunLoopDoTimers + 324

21 CoreFoundation
___CFRunLoopRun + 1912

22 CoreFoundation
CFRunLoopRunSpecific + 572

23 Flutter
0x0000000104118000 + 250040

24 Flutter
0x0000000104118000 + 248004

25 libsystem_pthread.dylib
_pthread_start + 288

How can I do?
[✓] Flutter (Channel unknown, v1.12.13+hotfix.9, on macOS 11.1 20C69, locale zh-Hans-CN)
[✗] Android toolchain - develop for Android devices
✗ Unable to locate Android SDK.
Install Android Studio from: https://developer.android.com/studio/index.html
On first launch it will assist you in installing the Android SDK components.
(or visit https://flutter.dev/setup/#android-setup for detailed instructions).
If the Android SDK has been installed to a custom location, set ANDROID_HOME to that location.
You may also want to add it to your PATH environment variable.
[!] Xcode - develop for iOS and macOS
✗ Xcode installation is incomplete; a full installation is necessary for iOS development.
Download at: https://developer.apple.com/xcode/download/
Or install Xcode via the App Store.
Once installed, run:
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
sudo xcodebuild -runFirstLaunch
[!] Android Studio (not installed)
[✓] VS Code (version 1.52.1)
[✓] Connected device (1 available)

@huangshengjie123
your flutter version is VERY old please run flutter upgrade -f
if the issue persists please provide
your updated flutter doctor -v, your flutter run -v and a minimal reproducible code sample

@huangshengjie123
your flutter version is VERY old please run flutter upgrade -f
if the issue persists please provide
your updated flutter doctor -v, your flutter run -v and a minimal reproducible code sample

@huangshengjie123
your flutter version is VERY old please run flutter upgrade -f
if the issue persists please provide
your updated flutter doctor -v, your flutter run -v and a minimal reproducible code sample

Which version？

Which version? @iapicca

The latest stable version is 1.22.6. @huangshengjie123

Hi @huangshengjie123
Please follow the steps described in https://github.com/flutter/flutter/issues/75089#issuecomment-770396489.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


<EMAIL_ADDRESS>hash check failed

PS C:\Users\wiatrgr> scoop update -ga
winscp: 6.3.4 -> 6.3.5 (global)
Updating one outdated app:
Updating 'winscp' (6.3.4 -> 6.3.5)
Downloading new version
WinSCP-6.3.5-Portable.zip (4.5 KB) [==========================================================================] 100%
Checking hash of WinSCP-6.3.5-Portable.zip ... ERROR Hash check failed!
App:         extras/winscp
URL:         https://downloads.sourceforge.net/project/winscp/WinSCP/6.3.5/WinSCP-6.3.5-Portable.zip
First bytes: 3C 68 74 6D 6C 3E 0A 20
Expected:    40f146ecb39194b5db53ca4a58098818d3893f0fe5fa6c80dec3681f61dcd592
Actual:      fc5b291a7c901d177cd28b7114fe4a8a8af9502124d49a2de86a14b1b37035c5
SourceForge.net is known for causing hash validation fails. Please try again before opening a ticket.
is it possible that hash has been changed ?

still same , but its only for winscp other apps update is working well , can i skip hash ? is it possible to do it in scoop ?


limit number of tracked packet number ranges that need to be acked

This removes a potential DoS vector and it ensures that the size of
outgoing ACK frames does not get out of hand, which could cause a
deadlock in case ACK frames cannot fit in generated packets anymore.
Older packet number ranges are simply removed from the start of the
list, to keep the total list length under the limit. This will cause the
peer to spuriously retransmit the data within those packets, though that
seems better than the alternative.
Fixes #489.

FTR, see https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#name-limiting-ack-ranges and https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#section-13.2.2

Changes look good.
Maybe it would be subjectively "cleaner" if the RangeSet could be configured with a maximum size and handle maintaining the list itself. But I can live with this code as it is right now.

Yeah, good point, this could be useful for other things in the future so I made it more generic.

I left the first()/last() changes in because I can't be bothered to split them in a separate PR.


Suggest "update -p" to fix a bad lockfile

Resolves #5684
Thanks for the great mentoring instructions, @Eh2406!
I added a test for the --verbose part of issue, and it looked fine? I don't see the "Caused by" message you posted, so I'm a little confused and could use a second pair of eyes, please. :)
r? @Eh2406

Thank you for working on this! That looks good.
Just to clarify (#lazyweb) if you have a new project with this lockfile what do you get after this PR for cargo build and for cargo build  --verbose

Looks good:
19:32:05 $ git co https://github.com/rust-lang-nursery/mdBook/pull/625
remote: Counting objects: 50, done.
remote: Total 50 (delta 34), reused 34 (delta 34), pack-reused 16
Unpacking objects: 100% (50/50), done.
From git://github.com/maccoda/mdBook
 * [new branch]          serve_tidy_up -> maccoda/serve_tidy_up
Branch 'serve_tidy_up' set up to track remote branch 'serve_tidy_up' from 'maccoda'.
Switched to a new branch 'serve_tidy_up'

19:32:37 $ git co 5b65ac8e37dc1259083c160defb2ed0927c83c54
Note: checking out '5b65ac8e37dc1259083c160defb2ed0927c83c54'.

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>

HEAD is now at 5b65ac8e3 Merge branch 'master' into serve_tidy_up

19:35:12 $ type dcargo
dcargo is a function
dcargo ()
{
    /d/cargo/target/debug/cargo "$@"
}

19:35:14 $ dcargo build
warning: An explicit [[bin]] section is specified in Cargo.toml which currently
disables Cargo from automatically inferring other binary targets.
This inference behavior will change in the Rust 2018 edition and the following
files will be included as a binary target:

* /d/mdbook/src/bin/serve.rs
* /d/mdbook/src/bin/test.rs
* /d/mdbook/src/bin/clean.rs
* /d/mdbook/src/bin/build.rs
* /d/mdbook/src/bin/watch.rs
* /d/mdbook/src/bin/init.rs

This is likely to break cargo build or cargo test as these files may not be
ready to be compiled as a binary target today. You can future-proof yourself
and disable this warning by adding `autobins = false` to your [package]
section. You may also move the files to a location where Cargo would not
automatically infer them to be a target, such as in subfolders.

For more information on this warning you can consult
https://github.com/rust-lang/cargo/issues/5330
error: failed to parse lock file at: /d/mdbook/Cargo.lock

Caused by:
  package `proc-macro2 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)` is specified as a dependency, but is missing from the package list
  consider running 'cargo update -p structopt-derive'

19:35:22 ! dcargo build --verbose
warning: An explicit [[bin]] section is specified in Cargo.toml which currently
disables Cargo from automatically inferring other binary targets.
This inference behavior will change in the Rust 2018 edition and the following
files will be included as a binary target:

* /d/mdbook/src/bin/serve.rs
* /d/mdbook/src/bin/test.rs
* /d/mdbook/src/bin/clean.rs
* /d/mdbook/src/bin/build.rs
* /d/mdbook/src/bin/watch.rs
* /d/mdbook/src/bin/init.rs

This is likely to break cargo build or cargo test as these files may not be
ready to be compiled as a binary target today. You can future-proof yourself
and disable this warning by adding `autobins = false` to your [package]
section. You may also move the files to a location where Cargo would not
automatically infer them to be a target, such as in subfolders.

For more information on this warning you can consult
https://github.com/rust-lang/cargo/issues/5330
error: failed to parse lock file at: /d/mdbook/Cargo.lock

Caused by:
  package `proc-macro2 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)` is specified as a dependency, but is missing from the package list
  consider running 'cargo update -p structopt-derive'

That is, assuming, that suggesting structopt-derive is right.

That is easy to test, try running cargo update -p structopt-derive as suggested :-P

Oh dear.
$ dcargo update -p structopt-derive
error: failed to parse lock file at: /d/mdbook/Cargo.lock

Caused by:
  package `proc-macro2 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)` is specified as a dependency, but is missing from the package list
  consider running 'cargo update -p structopt-derive'

Drat. So having experimented locally I think the recommendation is correct. cargo update -p structopt-derive would work if update could be run on a corrupted lockfile.
@alexcrichton Is there some way to make update use the parts of the file that make sense? Something like normally we parse the lockfile and if there is an error we bail, but for update we ignore each row that has an error?

Ah yeah I think we can't fix this by suggesting -p unfortunately. Instead I think what we'll need to do here is to basically make lockfile parsing a bit more lenient. We should in general be able to handle an erroneous lock file as much as we can, Cargo's job is to just preserve as much of it as possible (that it can)

I spiked out adding an argument to allow us to ignore bad parts of lock files for update. With some more careful work and lots of tests, this could make update use the lock file, and build/publish report the problem.

Seems like a good start yeah!

Going to drop this off my PR queue, as it looks to require more work than I was interested in committing to it.

@dwijnand Thank you for working on it. I am very sorry for the miss information in the original report. I will try to flesh out my spiked, to get your work merged.

Not a problem, estimates are hard. 😄 (learnt some more Cargo in the process)


fix: Clear cache doesn't work with cb param

Issues

Not able to clear cache for images with cb param, for example https://cdn.stamp.fyi/space/wen🌕.eth?s=96&cb=c178562f8f12066b
If there is nothing to clear, It returns ok in response

How to test:

Try going to http://localhost:3008/space/thanku.eth?s=160&cb=ce8ed162479340899ca4cae882bd0a0e
Clear cache by going to http://localhost:3008/clear/space/thanku.eth?s=160&cb=ce8ed162479340899ca4cae882bd0a0e

This does take care of clearing the cache when passing the exact same params as when creating it, but it will not clear the cache for all resized versions

It deletes all items inside the folder
we saving different sizes inside a folder based on cb param


Improve debugging experience.

With this change the initial request to kak-lsp will also be logged into a file.
The full file I'm using it with: https://github.com/ul/kak-lsp/wiki/Usage-with-plug.kak

Actually, this is not working like I want it to.


Allow filtering by numeric attributes

Add possibility to filter product numeric attributes by range.
Linked task: SALEOR-2090

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-2090 Allow filtering be numeric values

Task linked: SALEOR-2090 Allow filtering be numeric values


Forward all parameters to aerender

As discussed in
https://github.com/inlife/nexrender/issues/446#issuecomment-664561943

Sorry, a small correction is needed.


migrated to dbt-core style logging

Originally I wanted to use the dbt-core logging mechanism so that dbt-loom does not print to stdout in case the --quiet flag is speciifed for a dbt run.
In our case for some dbt macros we write the output to a file which should not contain logs from dbt.
Additonally it integrates now neatly with timestamp etc.

I just noticed that this is related to an open issue (#2)


Updates to nav bar

Replaced white logo with color versoin and made clickable
Style edits to price ticker
Rearrangment of nav items

Okay good point. I've backed out those remaining changes so now its just the nav items. Can revisit when Christabel gets back on that

Changing the nav to match the current site layout so there is not a difference between them in the interim when both sites are live. Its a weird UX if the nav changes from page to page. I've stashed the changes I had made and can add back in when it makes sense

Fantastic. I'm not so familiar with the legacy site, so I'll let @jasonbcox have a look before merging.


@Authoryo #bug :: this is the title

wefjwefwepop wojfewo jwoejo wejiojewfi ojioewf

Title: @Authoryo #bug :: this is the title
Auteur: Authoryo
Label: bug
Environnement du test: dev
Device: desktop, mobile
Ecran: wadwaw
Nom du salon: idk?
Description: wefjwefwepop wojfewo jwoejo wejiojewfi ojioewf

I APOLOGISE! I am working on a project and I am using the github API to create issues. I was using this repo because it has so many issues, and I was trying to create my own issues and I thought it wasn't working... I was checking the wrong place but then I realised they were working and they were all here. So I do apologise, sorry.

As I stated before, these were a mistake. I have a form on my website, I was using this repo to list lots of issues to see how it handles thousands of issues, but I forgot to change it to my own repo for testing. And I created a new issue on a form on my website, I kept refreshing the page to see why my issues weren't coming up on and I realised, I forgot to switch to my own repo. Please do not threaten me to contact github support, they will look into it and see this. It was purely a mistake, also, the title and body of the issues don't quite look like the spam kind do they? As well as, I instantly closed each issue I accidently created (after trying to delete them).

Hey @Acidic9! I think the lesson has been thoroughly learned, so I'm not going to pursue this any further. Please use do not use this repository for any future testing, we receive enough spam as it is.


Possible JSON generation error

Description
The JSON Schema Transformation seems to generate an invalid JSON output when it generates more than 2 objects.
Problem
When it generates 2 or more objects, the JSON starts as an Object instead of an Array.
Steps to reproduce
Getting the example in the datafaker documentation from JSON Schema Transformation we have the following code:
Schema<Object, ?> schema = Schema.of(
    field("Text", () -> faker.name().firstName()),
     field("Bool", () -> faker.bool().bool())
 );

JsonTransformer<Object> transformer = JsonTransformer.builder().build();
 String json = transformer.generate(schema, 2);

Expected result
As it's generating 2 objects, the output must start as an Array
[
   {
      "Text":"Nathalie",
      "Bool":false
   },
   {
      "Text":"Tamika",
      "Bool":true
   }
]

Actual result
The output starts as an object.
{
   {
      "Text":"Nathalie",
      "Bool":false
   },
   {
      "Text":"Tamika",
      "Bool":true
   }
}

How to validate
There are two easy ways to validate.
Transform the output into a JSON object

Import the json Java library
Use the same code as in the docs,  using the generated JSON output to create a JSON object

 Schema<Object, ?> schema = Schema.of(
  field("Text", () -> faker.name().firstName()),
  field("Bool", () -> faker.bool().bool())
);

JsonTransformer<Object> transformer = JsonTransformer.builder().build();
String json = transformer.generate(schema, 2);

 new JSONObject(json); // an exception will happen here

Validate the output in any online JSON formatted

Access https://jsonchecker.com/
Copy the output from the Actual results section
Check the output

Versions

OS: MacOS 14.3.1
JDK: openjdk version "21" 2023-09-19
Faker version: 2.1.0

Additional information
I can in the JSONTest that the testGenerateFromSchemaWithLimit test expects, wrongly, the curly brackets when there are 2 or more data.
I believe the logic should be:

only one limit: curly brackets are added at the beginning and end of the output
two or more limit: square brackets are added at the beginning and end of the output

I'll be more than happy to contribute to this fix if you guys agree.

As a WA it could be handled with help of this
JsonTransformer<Object> transformer = JsonTransformer.builder().formattedAs(FormattedAs.JSON_ARRAY).build();

after that there will be square brackets

I'll be more than happy to contribute to this fix if you guys agree.

there is already some logic for handling this, may be need to twek in a better way when FormattedAs.JSON_ARRAY and when FormattedAs.JSON_OBJECT  should be used...
feel free to contribute here

@snuyanzin Thank you for the explanation.
Wouldn't be better to remove the Formatter and add the logic during the generation?
I'm suggesting it because more than 2 objects will be wrongly generated if we don't use the formattedAs(). I can't see any use case as the consumer would generate the objects starting the JSON file with a curly brace.

Btw, I will add an issue to update the docs with the mention of the formattedAs() method.

Wouldn't be better to remove the Formatter and add the logic during the generation?

I remember the was some questionable cases, if we can double check that everything is remained covered then probably yes could be removed

I'm ok to use jackson however in this case we probably should shade it as well (in order to prevent clashing of deps in case someone uses datafaker from on side and from another side has dependency on a different jackson version)
Probably we could still keep JsonTransformerBuilder NON deprecated and use it it pass ObjectMapper flags in case of non default behavior is  required, e.g. order of map objects  by keys (suddenly i faced thatdefault behavior for this sometimes changes between jdk17 and jdk21)

What I meant was not using Jackson. I used it to illustrate its behavior for objects or arrays.

ok then the question: how inside generateJson we could answer a question "should we generate an object or an array with length 1?"

Can this be closed?

Can this be closed?

@kingthorin I'm, slowly, working on it. Can we keep this open?
Thank you!

@eliasnogueira would you like to have this change into Datafaker 2.2? I haven't picked a release date yet, but probably within a month or so.

@eliasnogueira would you like to have this change into Datafaker 2.2? I haven't picked a release date yet, but probably within a month or so.

Most likely I will place the PR tomorrow. :-)

@bodiam @kingthorin @snuyanzin
I've added this PR https://github.com/datafaker-net/datafaker/pull/1134
It adds one more ability to the JsonTransformer and it's explained in the PR.
It's ok if you guys disagree with the proposal.

I'm going to close it since the PR is merged now
https://github.com/datafaker-net/datafaker/pull/1134


Names of Files and their Folders changed

since the last release - thank you all to keep this running here!!!!!! - i experienced some changes in the name and the location of the downloaded files.

type
old
new
difference

buy/sell Optionsscheine
2023-04-28 09_59 Kauf Long @34.36 € BASF SE Best Turbo.pdf
2024-06-24 Abrechnung - Long 331,2553 $.pdf
- time is missing - name of the underlaying is missing -(Ver-) Kauf missing in the name

buy/sell Aktien
2023-04-28 09_59 Kauf NVIDIA.pdf
2024-06-24 NVIDIA.pdf
- time is missing - name of the underlaying is missing -(Ver-) Kauf missing in the name

dividends
2024-05-15 04_52 Main Street Capital.pdf
2024-07-02 Dokumente - Main Street Capital.pdf
- time is missing - Dokumente is part of the new name. Directory also changed

savings plan
2024-06-10 Main Street Capital 24.pdf
2024-07-03 Abrechnung Ausführung - Main Street Capital.pdf
- "Abrechnug Ausführung" new in the name, previous it was in a subfolder with that name - number of execution is missing

additionally some folders where moved to another location, like "root -> Sparpläne -> Abrechnung Ausführung" moved to "root -> Abrechnung Ausführung"
would be nice to have a stable naming and location for the files.

The changes are due to the new underlying API by TradeRepublic, so we are a little bit stuck here. 100% agreeing to both points:

Stable titles
Stable folders
I would love us to create an "event" object, which could have a nice get_title and get_folder function.


implement new caching method

Change caching mechanism so that we keep one file per repository instead of a copy of every record
Each connector will need to keep one file per event type and be a csv.gz file with the following general format:
timestamp,entity_id,source_entity_id,file_location,hash,orphaned

timestamp is the sync timestamp (unix) epoch
entity_id will be the generated ID for the entity type
this can be a commit_id, pullrequest_id, issue_comment_id or any other event types entity ID that is generated by our generate functions
source_entity_id is the ID of entity as pulled from the source
file_location is the filename/location in DL s3 input bucket (datalake-input- {ENV})
hash will be the hash of the raw response before it is transformed into the lfx-events-schema schemas
orphaned will be a boolean (true|false) value which initially default to false and on consecutive runs can be modified to be true when a full sync runs and the specific event can't be found

The cache will still be split between endpoints in the tree structure as it is right now. 0000-last-sync can be as it is and do the tracking as it is currently.
s3://insights-v2-cache-{ENV}/cache/{CONNECTOR}/{ENDPOINT}/0000-last-sync
s3://insights-v2-cache-{ENV}/cache/{CONNECTOR}/{ENDPOINT}/{EVENT}-cache.csv

Biggest file here will be for the kernel projects which has over 1 million commits which will translate into a cache.csv file with over a million lines. That will end up being less than 100mb so connector can hold the entire cache in memory if needed (during a full sync).
On default run mode connector will run through the following steps:

check for the 0000-last-sync file of the endpoint and find out where to start pulling
get the cache.csv file(s) for the endpoint
start pulling data from source

for each entity, confirm data is not in the cache (compare hash of the raw data)

add to the list of objects that will be pushed to DL s3 input bucket
add to the cache

push DL s3 input file first
if successful, push the updated cache file and the updated 0000-last-sync file

On full sync mode connector will run through the following steps:

ignore the 0000-last-sync file of the endpoint
get the cache.csv file(s) for the endpoint and load into memory and set the orphaned to true for every line
start pulling data from the source starting from the beginning

for each entity, confirm data is in the cache (compare hash of the raw data)

add to the list of objects that will be pushed to DL s3 input bucket
update the cache entries orphaned field to false or add the NEW entry if not already in cache

push DL s3 input file first
if successful, push the updated cache file and the updated 0000-last-sync file

With these changes implemented we will not have to worry about deleting millions of files on a full sync.
All the cache will be in a single compact file per endpoint which is how the connectors run.

[ *] Git
[ ] Github
[ ] Gerrit
[ ] Jira
[ ] Confluence
[ ] Jenkins


Update commons-compress to 1.23.0

About this PR
📦 Updates org.apache.commons:commons-compress from 1.22 to 1.23.0
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.apache.commons", artifactId = "commons-compress" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.apache.commons", artifactId = "commons-compress" }
}]

labels: library-update, commit-count:1

Superseded by #244.


Automake

This resolves #4

Philip,
Comments:

Re the changes to .gitignore:  those look good for Linux, but not for Windows.  I'm assuming that autotools/automake aren't going to handle the Windows build.  If that's the case, some of the .gitignore things you deleted need to be present for Windows.  BTW, feedback I've received from the TSS WG indicates that they really like the Windows option, so I think we need to keep this.
Is there any way to keep the autogeneration of source and include files in the automake environment?  If not, that's fine; it not a hill worth dying on.  I just really liked it.

Autotools will work on Windows under cygwin but I haven't tested it. This would be convenient so we're not maintaining 2 build systems in the same source tree. Not sure how people's preferred tools on Windows will interact with this though.
Adding back the right .gitignore rules to get us back to where we were is probably the right first step.
As to your #2 above autotools doesn't seem to like doing such things. I can rig the configure step up to generate a list of these files for automake to import but doing these sort of things is pretty "non-standard". This could also just be my ignorance though so I'll keep digging into automake to see if this feature exists. Does Visual Studio have similar functionality? It would be a nice way to keep breakage to a minimum when we have multiple people working in different build environments.

Philip,
Below…
Will Arthur
Intel Corporation
Server Security Firmware
803-216-2101
From: Philip Tricca<EMAIL_ADDRESS>Sent: Sunday, August 30, 2015 6:02 PM
To: 01org/TPM2.0-TSS<EMAIL_ADDRESS>Cc: Arthur, Will C<EMAIL_ADDRESS>Subject: Re: [TPM2.0-TSS] Automake (#22)
Autotools will work on Windows under cygwin but I haven't tested it. This would be convenient so we're not maintaining 2 build systems in the same source tree. Not sure how people's preferred tools on Windows will interact with this though.
[Arthur, Will C] I think we need to keep Windows and Linux builds separate.  They’re just too different to merge, IMO.
Adding back the right .gitignore rules to get us back to where we were is probably the right first step.
[Arthur, Will C] Thanks!
As to your #2https://github.com/01org/TPM2.0-TSS/issues/2 above autotools doesn't seem to like doing such things. I can rig the configure step up to generate a list of these files for automake to import but doing these sort of things is pretty "non-standard".
[Arthur, Will C] That’s fine.  I don’t think this is worth spending a lot of time on.
This could also just be my ignorance though so I'll keep digging into automake to see if this feature exists. Does Visual Studio have similar functionality? It would be a nice way to keep breakage to a minimum when we have multiple people working in different build environments.
—
Reply to this email directly or view it on GitHubhttps://github.com/01org/TPM2.0-TSS/pull/22#issuecomment-136203934.

Doesn't look like the .gitignore lines for Windows were added back in.  I thought they were from you comment above.  Do you want to add them back in after I accept these changes?

Hey Will. I just rebased this with ignore rules for the VisualStudio bits. Sorry for the delay, took me a while to remember how do stuff in VS again.

Philip,
I still see that the new .gitignore is going to remove the ignore rules for VisualStudio.  I’m not sure what you mean by “rebase”, but it doesn’t seem to have resulted in any changes to the .gitignore.
Will Arthur
Intel Corporation
Server Security Firmware
803-216-2101
From: Philip Tricca<EMAIL_ADDRESS>Sent: Tuesday, September 1, 2015 12:57 PM
To: 01org/TPM2.0-TSS<EMAIL_ADDRESS>Cc: Arthur, Will C<EMAIL_ADDRESS>Subject: Re: [TPM2.0-TSS] Automake (#22)
Hey Will. I just rebased this with ignore rules for the VisualStudio bits. Sorry for the delay, took me a while to remember how do stuff in VS again.
—
Reply to this email directly or view it on GitHubhttps://github.com/01org/TPM2.0-TSS/pull/22#issuecomment-136793827.

Added another line to ignore the VS 'Release' build artifacts. Rebased again. Should be OK but testing on the version of VS that you're using would probably be a good idea.


Clear guidelines on documentation

As a contributor to the AKROS-Marketplace I want to have clear guidelines on where to put what kind of information.
Currently the documentation is split to the Confluence, the architecture document, several markdown files (especially in the organize project work folder and more.
For instance such a guideline (in short) could be:

Architectural documentation are to be written in README.md
Internal matters (such as how we deploy the application and how we work as a team) are to be written in the Confluence
Information on how to run an application in the repo are to be written in the README.md file of its folder
Further information (Business-related information, How to use the application? Up for discussion) can potentially be written in the Github Wiki
As for the code, any important frontend class or function is to be written in the Code with JSDoc and the backend with Javadoc
The API is properly documented within the YML file
Database-Tables and fields are documented (not sure where yet)

This guideline can then also be added to the DoD in order to ensure a complete documentation upon finishing a ticket.
AC1: A guideline is written and accepted by the team
AC2: That guideline is accessible to all the team members
AC3: Any noticed lack of documentation has a task created in agreement with the PO
DoD

[ ] Story is tested against acceptance criteria
Unit test should be passed
[Integration test is done ( if applicable)
[ ] Non-functional requirements are met
[ ] Story ok-ed by Product Owner
[ ] Peer Code Review performed
[ ] Any configuration or build changes documented

Tasks:

[x] Determining the guideline location
[x] Requirements, Vision, Product Description (Business)
[x] Requirement of technical documentation beyond code and architecture
[x] In-code documentation
[ ] Design documentation needed?
[ ] Testing documentation where?

A task for the database documentation has been created with #98.


Add docs for contribution and update README

Hey, finally it's here! Let me know if you think something should be changed/removed. 😄 I don't know how to link documents, so while CONTRIBUTING.md is mentioned in README.md, there's no click one can easily click. Would be great if you can do that!

@ankush981 Hey sorry it's taken me a while to get to this, I should have a review for you soon


fixed offset carina status codes

@SimonSchick, thanks for your PR! By analyzing the history of the files in this pull request, we identified @UnwrittenFun and @connor4312 to be potential reviewers.

carina tests are slightly flakey, not related to changes, merging anyways.


Close #89 Gradle

POM file removed.
build.gradle added.
Gradle wrapper added.
Version "0.0.9-SNAPSHOT" is released and deployed as a test.

Note: I realesed two test snapshots while implemented this stuff.
They may be found here: https://oss.sonatype.org/content/groups/public/org/whaka/whakamatautau-util/0.0.9-SNAPSHOT/


Test Dataverse Files / Accounts for MS Testing

1. Test Dataverse / Dataset

Set up a test Dataverse/Dataset* with files that may be downloaded/retrieved in tab-delimited format.  These files will have unique identifiers.  (* Within the Dataverse context, a Dataset is a collection of files.)

2. User accounts / tokens

Create two user accounts and related tokens for the following purposes:

Service Account - This account will be used by the MSFT service to retrieve files via the Dataverse API.
User Account - This account will represent the researcher who:

Has permission to access a Dataverse and to browse lists of Dataset files
Cannot access the raw data, e.g. cannot download or retrieve the files.
Cannot access summary statistics:  neither the DDI document produced by Dataverse ingest nor the R-created summary statistics.

Hey @raprasad, I added https://demo.dataverse.org/dataset.xhtml?persistentId=doi:10.70122/FK2/LLE0ES with two tabular files from one of Gary's datasets. I have not published yet but can do so. Let me know if there's other metadata I should add or files I should use here.
Regarding the user accounts, how do you want to create them? Are there login types/credentials that  we should use, or should we let the respective teams/users create them and then set up the permissions?

@eedeleon See Danny's note ^ regarding creation of Dataverse accounts (one to represent a service account and the other the user).

Thanks @raprasad , I created two dataverse accounts eedeleon and burdock. Can we have 2 datasets. 1 where both have access and 1 that only burdock has access to?

Hi @eedeleon - I've published the dataset so you should now have access:
https://demo.dataverse.org/dataset.xhtml?persistentId=doi%3A10.70122%2FFK2%2FLLE0ES
You can see one of the files in the dataset is restricted (adjacency_subset.tab) and one is not (allc_subset.tab). When you say you want one dataset do you mean file or dataset (a collection of files and related metadata)? Take a look at what's there and let me know if I should adjust anything.

Hi @djbrooke as expected, I was able to download one file but not the other from the python SDK.
import dataverse  # from the iqss python sdk
connection = dataverse.Connection(host, token)
I got the files and download_urls with the SDK but could not download the private file
(Pdb) requests.get("https://demo.dataverse.org/api/v1/access/datafile/395812")
<Response [200]>
(Pdb) requests.get("https://demo.dataverse.org/api/v1/access/datafile/395811")
<Response [403]>
(Pdb) requests.get("https://demo.dataverse.org/api/v1/access/datafile/395811", auth=connection.auth)
<Response [403]>
I tried passing in the auth the same way the client does for the service document but was unsuccessful.
I am happy with 2 datasets in the same dataverse where I can download one private one from the burdock account but cannot download it from the eedeleon account. Currently I can download the open file so that is working perfectly.
Would giving the burdock account access to the restricted dataset make the returned download_url work for that account and not the other? If so, that would be the last step I would need to have a working example.


Feature Request: Select multiple plugins to install

Plugins currently must be installed one-by-one. Being able to select multiple plugins and install them in one go would improve usability. Perhaps a checkbox to the left of the plugin name and a new button to install selected plugins.

@lattera are you talking about first time setup, config.xml import setup or general use?
For the second case there is this planned: #1663, for the other two the work is clear but I'm not entirely sure it's worth all the work and JS fiddling.

This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository,
please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.


Implement Specific Feature Restrictions

An Oxy server should be able to service clients that are only allowed to perform a subset of the operations allowed by Oxy as a whole. For example, a particular client may be allowed to perform file transfers but not run shell commands.
A specific use case I have for feature restrictions is allowing clients to perform a single, pre-specified remote port bind. For example: client key abcdef123= may RemoteBind <IP_ADDRESS>:50001, but may not perform any other operations.

There should be a way to ask the server to chroot and setuid, seccomp() pledge() away unnecessary rights.


Evaluate Hexo for static site generation.

Can combine the APIs + Guides in one page like meteor does.
Remove usage of JSDocs.
Multiple versions (history) support.
Explicitly specify the APIs instead of implicitly by APIs that exists in files named "_public".
Would require some conversion of TypeScript Type Information to JSDoc output for "api_box" integration.

Used vuepress instead.
Much easier to use and better docs

http://sap.github.io/chevrotain/docs/

wow just wow

Yeah vuepress is awesome.


not network connection (yml file change)

Hi, thanks for sharing the dockerize chromadb setting
I faced connection time out error when I compose your docker file
I figured out and succeed by add the Dockerfile a line
network: host
so the file become...
version: "3.0"
services:
application:
build:
context: .
dockerfile: ./Dockerfile
network: host
...

Hey Lin,
Thanks for noticing this.
There is a bridge network that I had already configured (by the name 'net') in the docker-compose (Line 30 in docker-compose). The same network is used by both the services - chroma and the application (Check lines 11 and 20).
And that works fine ( I just checked it out).
I'm adding a screenshot below for you to look over.

However, I am glad that the change worked for you! Thanks again for noticing that issue and also for coming up and sharing the alternative solution.
Best regards,
Abhi.


test harness e2e preparations

Add debug view in order to write tests for androidtv firetv & tvos platforms. Also expanded harness app test cases

@aurimasmi @locksten can be reviewed atleast from my side


About Us page Not working

Your commit 535b441fd423e3bdee25b2f1b1ef66bc5a39c8f9. This is not working properly. Please, fix this problem as soon as possible.

3f51a9990493dce179d069f60c127ab57c2abf8e
It has been solved by the commit

Great.


HALON-467: Repair not starting after second drive failure

Created by: nc6
Moving these into a single PR now.

Closing as an obsolete


enable ipv6 for cache.nixos.org (cloudfront)

Issue description
According to this article https://aws.amazon.com/de/about-aws/whats-new/2016/10/ipv6-support-for-cloudfront-waf-and-s3-transfer-acceleration/ Amazon Cloudfront now supports ipv6,
which means it could be enabled for cache.nixos.org.

One might even ask, why Amazon not just enable it by default,
because it is just a CNAME:
cache.nixos.org.        1166    IN      CNAME   d3m36hgdyp4koz.cloudfront.net.

I've enabled IPv6 support in CloudFront. The change might take a while to take effect.

Seems to work!

Great!
Heh, the IPv* records have only 60 seconds TTL; that's not too cache-friendly...

Cool!


Fix typographical errors on Contributing.md file

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
I have spotted a minor typographical error on the contributing.md file in this repo.
What part(s) of the article would you like to see updated?
I would like to fix this error as well as review the file for other errors.
Additional information
No response

@LuluNwenyi
Thanks so much for opening an issue! You can open a PR with the fix and link it to this issue when ready ✨

Hi @ramyaparimi, I have fixed this issue. See Contributing.md PR


More collaborators?

Hi guys, hi @haio.
I'm following all the changes in this module for a quite long time. I guess others do the same too. What I would like to offer is choosing of collaborators for this project to review PRs, answer questions and make small additions and corrections faster thus, as for me, I have a time for this. Also I highly depend on this library and Kafka. So would like to breath more life into it.
For example, there is issue #308 issue which is caused by a wrong code in old commit
768103aafd3bbe09d271ae6d7b9156bb90e49235 followed by another wrong addition (meaning HighLevelConsumer) in 03c42acf9c0dcb4bfbe1a4752483aea8bd993517. There are more issues caused by first commit. Without proper review such additions may hurt the further versions or bring misunderstanding.
So what I'm asking is make active users collaborators so we could do review & fixes faster and help you dig all the issues. Watching things by multiple persons may give a better review quality.

I second this if it's something feasible. I'd love to help contribute to this effort!

Thanks @estliberitas I'd love to contribute if help is needed

Well, waiting for @haio to say his word on this. I've got a simple roadmap on my mind like - more docs, checking and making compatible with official Java clients, consistency between docs and sources (that sucks for now, you can see from my PRs).

I'd love to help too.

+1

@haio ?

👍

Well, it seems there is no wish from author to do something ATM. Guys, if there are any of you who would wish to help with development of an alternative or fork?
Btw, no-kafka seems to be a good alternative. In some time, Kafka 0.9.x will be released, so maybe we could put all the effort to that client and help author for the good of everyone?

@estliberitas I like the idea of contributing to a Kafka 0.9.x client.

@ismriv Well, then, I'll create tomorrow issue there so we'll talk with author about roadmap, not-implemented things and start working. It looks really good thus Promise-based.

Yes very exciting. Looking forward to contributing!
On 31 Jan 2016 17:36, "Alexander Makarenko"<EMAIL_ADDRESS>wrote:

@ismriv https://github.com/ismriv Well, then, I'll create tomorrow
issue there so we'll talk with author about roadmap, not-implemented things
and start working. It looks really good thus Promise-based.
—
Reply to this email directly or view it on GitHub
https://github.com/SOHU-Co/kafka-node/issues/309#issuecomment-177558819.

+1

A 0.9.x client is important but we shouldn't leave this module to rot. Plenty of people will still be using 0.8.x so forking this module to continue maintenance would be preferable to jumping ship to 0.9.x, in my opinion.

I am not expert, but as I understand it, the changes for 0.9 are so significant, and lighter, it might make sense to have a separate module, even if this project evolves.
Is there a Node 0.9 project that looks like a good bet to use now?

It would be brilliant if the README could be updated to state if there are plans for this project for Kafka 0.9 or if 0.8 is the plateau. It sure would help grateful users like me to plan.

@sumpton we're using 0.2.3 with kafka 0.9 it works for us.

Hi all, sorry for response so late, I have been so busy for a while. I'm very happy that some people can help to close issue and merge pull request for this project, so it can benefit more people. From discussion   above, I would add @estliberitas @carlessistare @ismriv as new collaborators, if it's ok for you guys, please reply here.
Thanks!

Makes sense.

Have added @estliberitas, wait for the confirmation from @carlessistare and @ismriv

@haio  I'll be glad to participate!

Thanks @haio! Unfortunately we've recently switched to Kafka 0.9, and I am afraid I won't be of much help.

@haio if you need it I am willing to help as well.

@carlessistare @hyperlink thanks!

@ismriv that's all right.

Any special procedure before merging PR's?

@carlessistare Here is some requirements I can think about:

the PR should have a clean commit log
the PR should keep the code style of current code base
the PR should have unit tests if it will introduce a new feature
for small fixes, one can merge PR directly
for PR with new features or big change of current code base, it should at least get two collaborators' LGTM before merging
what do you think?

LGTM :)
So we write it down somewhere?
Le ven. 1 avr. 2016 17:21, Zhong Yu<EMAIL_ADDRESS>a écrit :

@carlessistare https://github.com/carlessistare Here is some
requirements I can think about:

the PR should have a clean commit log
the PR should keep the code style of current code base
the PR should have unit tests if it will introduce a new feature
for small fixes, one can merge PR directly
for PR with new features or big change of current code base, it
should at least get two collaborators' LGTM before merging what do you
think?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/SOHU-Co/kafka-node/issues/309#issuecomment-204436153

Just write it in comment or click the :+1: emoji to show your confirmation :smile:

I meant to write down these requirements in the readme, or somewhere else.
So all collaborators will know what to do at first glance.
Le sam. 2 avr. 2016 01:13, Zhong Yu<EMAIL_ADDRESS>a écrit :

Just write it in comment or click the [image: :+1:] emoji to show your
confirmation [image: :smile:]
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/SOHU-Co/kafka-node/issues/309#issuecomment-204603859

@carlessistare make a pull request ;)

@carlessistare CONTRIBUTING.md is created especially for this case

@estliberitas I let you merge this PR (https://github.com/SOHU-Co/kafka-node/pull/346) with an initial CONTRIBUTING.md file, if it is ok

@carlessistare got some questions already


Custom audio controls UI

I think it would be nice to have some indication of where the bookmarks are. Also showing the note from them in the player somewhere. Maybe an option to play a sound.

Partially implemented with 04e16f0, but no work done for bookmarks.

Completed by 21fc1a0.


Pending Storage Performance Improvements

https://trello.com/c/8Y2OuIfh/221-blockstore-2-process-pending-storage-performance

 [BlockStore] 2 Process Pending Storage Performance


SAM-2913: Main menu markup tweaks for Morpheus

https://jira.sakaiproject.org/browse/SAM-2913

LGTM, makes that one file much easier to read too.


[Docs] - VSCODE - README.md - minor tweaks (spelling/grammar)

[Docs] - VSCODE - README.md - minor tweaks (spelling/grammar)

These changes don't make sense. The original version is correct.


Update specs

Unfortunately, the amethyst test fails, but I believe that's because all of amethyst isn't using specs 0.15.0 yet. I'm sure they will be soon though, because the new API is much more ergonomic, you don't have to register components anymore. I went ahead and updated specs-hierarchy to specs 0.15.0, when they accept my PR I'll update the Cargo.toml to look there instead of on my fork of the github. I just don't think it would be feasible for me to do that for all of amethyst! :grin:

My specs-hierarchy PR merged, so that's updated now. Once it's on crates.io I'll update these commits to pull from there instead of my git fork.

I'll target to merge this once the next version of Amethyst is released.

@distransient Out of curiosity, is there any plan to decouple this library from Amethyst? If so, I'd be happy to help with this effort. I love specs, but I have no need for the full Amethyst framework, so having access to the latest features would be nice without having to wait for Amethyst.

The API is not at all coupled to Amethyst. You can easily use specs-physics without Amethyst, all you have to do is nothing, since the amethyst code is not enabled by default.

Apologies, after posting my comment I went and read through the code (should have done this in the first place) and so I now understand how the amethyst code works. I wasn't asking about the API, by the way, I was asking about the library itself. Because this PR is blocked by Amethyst, I see the library (or at least its pace of development) being coupled to Amethyst.
Regardless, I was out of line. There's nothing stopping me from making my own fork with these changes merged.

Merged via #21! (used that to push my conflict fixes)


Upgrade Wireshark to v2.0.0

Upgrades Wireshark to version 2.0.0, which has been released earlier today: https://www.wireshark.org/docs/relnotes/wireshark-2.0.0.html

Duplicate of https://github.com/caskroom/homebrew-cask/pull/15296, which was just merged.


chore(main): release pg 15.4.0-v1.2

:robot: I have created a release beep boop
15.4.0-v1.2 (2023-08-18)
Features

pg set_user (10b8f0f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/livenessprobe/containers/releases/tag/pg/v15.4.0-v1.2 :sunflower:


Enable linker build-id for android builds.

Linker build-id is mandatory to make Firebase crashlytics recognise libraries which encounters crashes. So since Firebase is ubiquitous to monitor app crash performance it make sense to enable it for android builds. It only slightly increases binary size (20 bytes) but make Firebase crash symbolication work. Here I assume that debugging symbols are currently presented/published, if not the case it will be handled in subsequent PRs.

Verified that build-id is now present in Android artifact from android build job:
/tmp/codec-native-quic/target/jni/arm64-v8a# readelf -n libnetty_quiche.so

Displaying notes found in: .note.android.ident
  Owner                Data size 	Description
  Android              0x00000084	NT_VERSION (version)
   description data: 15 00 00 00 72 32 37 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 31 32 30 37 37 39 37 33 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Displaying notes found in: .note.gnu.build-id
  Owner                Data size 	Description
  GNU                  0x00000014	NT_GNU_BUILD_ID (unique build ID bitstring)
    Build ID: 5568086b1d7eda7303a6a29a9c998156acbf5a9c

/tmp/codec-native-quic/target/jni/arm64-v8a# file libnetty_quiche.so
libnetty_quiche.so: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, BuildID[sha1]=5568086b1d7eda7303a6a29a9c998156acbf5a9c, not stripped

@mstyura thanks


data

Because I want to run this code with other data sets, how can I get .run and .pair files similar to those in /data?

Hi- the format description of these files are given here: https://github.com/Georgetown-IR-Lab/cedr#getting-started
In short, training pairs are sampled from lines like [query-id] [doc-id] and run files are the standard TREC run format: [query-id] 0 [doc-id] [rank] [score] [runtag]. The latter can be the output of various retrieval systems, and the former can just be sampled from run files (depending on what you want to train with).

Does the .run and .pair files need to be built manually or automatically by running some program?

Does the .run and .pair files need to be built manually or automatically by running some program?

There is also an integration plugin for CEDR using PyTerrier - see
https://github.com/terrierteam/pyterrier_bert#cedr-usage
(though its a little more dated compared to other PyTerrier plugins now)

Excuse me, can you provide the index file containing the indexbuildindex parameter?

That again depends on what experiment you're running -- especially since you mention that you're running it with different datasets.
Since you brought up Indri, here's documentation on it: https://sourceforge.net/p/lemur/wiki/IndriBuildIndex Parameters/
I'm not very familiar with Indri, however. I'm happy to help out using PyTerrier though -- especially if you provide some details on what you're trying to do. Here's the documentation on indexing: https://pyterrier.readthedocs.io/en/latest/terrier-indexing.html


BUG : change the background color of body

TODO:

Change of background color of body to new gradient .
Gradient code  bg-gradient-to-r from-gray-700 via-gray-900 to-black

@masif2002  Would you like to fix this?

@ArslanYM Sure. But would you like to mention how I can reproduce the issue, so that I can check once I've made the changes
I'm not able to reproduce the issue for the screen size of Iphone 12 pro?

This issue will probably still exists on large screen devices. if not that you can maybe try adding iphone 8plus to your google developer tools.

This issue will probably still exists on large screen devices. if not that you can maybe try adding iphone 8plus to your google developer tools.

Somehow, the issue does not exist in larger devices. Let me check it once with Iphone 8plus

on the docs page, it is much better visible
added PR for this issue #166


[SPARK-18217] [SQL] Disallow creating permanent views based on temporary views or UDFs

What changes were proposed in this pull request?
Based on the discussion in SPARK-18209. It doesn't really make sense to create permanent views based on temporary views or temporary UDFs.
To disallow the supports and issue the exceptions, this PR needs to detect whether a temporary view/UDF is being used when defining a permanent view. Basically, this PR can be split to two sub-tasks:
Task 1: detecting a temporary view from the query plan of view definition.
When finding an unresolved temporary view, Analyzer replaces it by a SubqueryAlias with the corresponding logical plan, which is stored in an in-memory HashMap. After replacement, it is impossible to detect whether the SubqueryAlias is added/generated from a temporary view. Thus, to detect the usage of a temporary view in view definition, this PR traverses the unresolved logical plan and uses the name of an UnresolvedRelation to detect whether it is a (global) temporary view.
Task 2: detecting a temporary UDF from the query plan of view definition.
Detecting usage of a temporary UDF in view definition is not straightfoward.
First, in the analyzed plan, we are having different forms to represent the functions. More importantly, some classes (e.g., HiveGenericUDF) are not accessible from CreateViewCommand, which is part of  sql/core. Thus, we used the unanalyzed plan child of CreateViewCommand to detect the usage of a temporary UDF. Because the plan has already been successfully analyzed, we can assume the functions have been defined/registered.
Second, in Spark, the functions have four forms: Spark built-in functions, built-in hash functions, permanent UDFs and temporary UDFs. We do not have any direct way to determine whether a function is temporary or not. Thus, we introduced a function isTemporaryFunction in SessionCatalog. This function contains the detailed logics to determine whether a function is temporary or not.
How was this patch tested?
Added test cases.

Test build #68107 has started for PR 15764 at commit 695110f.

Test build #68112 has started for PR 15764 at commit 7100a8f.

Test build #68107 has finished for PR 15764 at commit 695110f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68107/
Test PASSed.

Merged build finished. Test PASSed.

Test build #68112 has finished for PR 15764 at commit 7100a8f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68112/
Test FAILed.

Test build #68116 has started for PR 15764 at commit 86e7f9d.

Test build #68116 has finished for PR 15764 at commit 86e7f9d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68116/
Test PASSed.

Test build #68143 has started for PR 15764 at commit a4df82b.

Test build #68143 has finished for PR 15764 at commit a4df82b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68143/
Test PASSed.

Merged build finished. Test PASSed.

Looks good but I didn't read super carefully.
cc @hvanhovell and @cloud-fan

Test build #68161 has started for PR 15764 at commit 1c3899f.

Test build #68161 has finished for PR 15764 at commit 1c3899f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68161/
Test PASSed.

Test build #68247 has started for PR 15764 at commit fec0066.

Test build #68247 has finished for PR 15764 at commit fec0066.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68247/
Test PASSed.

Thanks - merging in master/branch-2.1.


Md cleanup 2

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ]  Tests for the changes have been added (for bug fixes / features)
[ ]  Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ]  Build (cli.py) was run locally and any changes were pushed
[x]  Tox tests (tox) has passed locally and any fixes were made for failures
[x]  My code follows the code style of this project.
[x]  All new and existing tests passed.

Pull request type

Please check the type of change your PR introduces:

[x]  Bugfix
[ ]  Feature
[x]  Code style update (formatting, renaming)
[ ]  Refactoring (no functional changes, no api changes)
[ ]  Build related changes
[ ]  Documentation content changes
[ ]  Other (please describe):

What is the current behavior?

Related Issue

Issue Number: 22
What is the new behavior?

Better markdown
Motivation and Context

How Has This Been Tested

Does this introduce a breaking change

[ ]  Yes
[x]  No

Other information

Screenshots (if appropriate):

Fixes for Issue #21 included in this PR by mistake

Sphinx defines a copyright string variable.  It has the same name a a built-in Python function.  This is a false positive for the proect and can be ignored.


cmake: raise a fatal error when C compiler is not found

This commit introduces an early error in case a valid C compiler is not
found in the system.
This will help to early identify misconfigured systems with the error:
  C compiler <compiler> not found - Please check your toolchain installation
instead of an obscure error, such as:
No such file or directory: LIBGCC_FILE_NAME: ''

This PR is triggered by spending a couple of hours investigating: #25183
where the error message was:
No such file or directory: LIBGCC_FILE_NAME: ''

when trying to build using the Zephyr SDK.
With this patch, there would be an error as soon as no C compiler is found:
  C compiler /opt/zephyr-sdk/xtensa/esp32/xtensa-zephyr-elf/bin/xtensa-zephyr-elf-gcc not found - Please check your toolchain installation

making it much easier to spot such an issue.

That ZEPHYR_SDK_INSTALL_DIR is being used when ZEPHYR_TOOLCHAIN_VARIANT=espressif is still a problem for #25183, but what's going on is made more clear by the improved diagnostic.

Thanks, now I got it.
Fixed here: #25446


Exec tachikoma update<PHONE_NUMBER>3402

:hamster::hamster::hamster:   Strategy none
Powered by Interval Pull Request as a Service - Tachikoma.io Announcement: 2015-06-28 Updated permissions - Tachikoma.io

Coverage remained the same at 68.0% when pulling 5f9f44046cd2997f7ffbef02e192d599146de17a on pazjacket:tachikoma/update-20161218163402 into 391307db508f29cde46957edf9baba38c7a2933e on sanemat:master.

Coverage remained the same at 68.0% when pulling 5f9f44046cd2997f7ffbef02e192d599146de17a on pazjacket:tachikoma/update-20161218163402 into 391307db508f29cde46957edf9baba38c7a2933e on sanemat:master.


Revert "update the package namespaces for all packages in the artifac…

Just reverting. I don't have a great way to get the disabled artifacts without the artifacts list. However in the new world we won't HAVE an artifacts list. I'm thinking I propogate skipPublishDocs to Package-Properties file.

I'm thinking I propogate skipPublishDocs to Package-Properties file.

Yes I think we are going to need to figure out a way to associate things from the pipeline like this and potentially some custom steps like installing an emulator or other custom steps as well.


[BUG] Nightly Upgrade Test: test_salvage_auto_crash_replicas_short_wait sometimes failed

Describe the bug
To Reproduce
Steps to reproduce the behavior:

Install Longhorn v0.7.0
Upgrade Longhorn to master
Run test_salvage_auto_crash_replicas_short_wait test

Expected behavior
test should pass
Log
client = <longhorn.Client object at 0x7fdd0536f810>
core_api = <kubernetes.client.apis.core_v1_api.CoreV1Api object at 0x7fdd04be1610>
volume_name = 'longhorn-testvol-092j90'
pod_make = <function pod_make.<locals>.make_pod at 0x7fdd04a02e60>

    def test_salvage_auto_crash_replicas_short_wait(client, core_api, volume_name, pod_make):  # NOQA
        pod_name = volume_name + "-pod"
        pv_name = volume_name + "-pv"
        pvc_name = volume_name + "-pvc"

        pod = pod_make(name=pod_name)

        pod_liveness_probe_spec = get_liveness_probe_spec(initial_delay=1,
                                                          period=1)

        pod['spec']['containers'][0]['livenessProbe'] = pod_liveness_probe_spec

        volume = create_and_check_volume(client, volume_name, num_of_replicas=2)

        create_pv_for_volume(client, core_api, volume, pv_name)
        create_pvc_for_volume(client, core_api, volume, pvc_name)
        pod['spec']['volumes'] = [create_pvc_spec(pvc_name)]
        create_and_wait_pod(core_api, pod)

        test_data = generate_random_data(VOLUME_RWTEST_SIZE)

        write_pod_volume_data(core_api, pod_name, test_data)

        stream(core_api.connect_get_namespaced_pod_exec,
               pod_name,
               'default',
               command="sync",
               stderr=True, stdin=True,
               stdout=True, tty=True,
               _preload_content=False)

        volume = client.by_id_volume(volume_name)
        replica0 = volume.replicas[0]

        crash_replica_processes(client, core_api, volume_name, [replica0])

        time.sleep(5)

        volume = client.by_id_volume(volume_name)

        replicas = []
        for r in volume.replicas:
            if r.running is True:
                replicas.append(r)

        crash_replica_processes(client, core_api, volume_name, replicas)

        volume = common.wait_for_volume_faulted(client, volume_name)

        volume = common.wait_for_volume_detached_unknown(client, volume_name)
        assert len(volume.replicas) == 2
        assert volume.replicas[0].failedAt == ""
>       assert volume.replicas[1].failedAt == ""
E       AssertionError: assert '2020-03-17T09:43:17Z' == ''
E         - 2020-03-17T09:43:17Z

test_ha.py:435: AssertionError

Environment:

Longhorn version: 0.8.0
Kubernetes version: v1.17.2
Node OS type and version: Ubuntu 18.04

Additional context:
longhorn-upgrade-tests/14

Fixed a few known issues, still not done.

@shuo-wu might have found the reason and fixed it along with https://github.com/longhorn/longhorn/issues/1244 .

test_salvage_auto_crash_replicas_short_wait passed for two consecutive runs longhorn-tests/421 & longhorn-tests/422


[Suggestion / Compatibility] Common tags folder Name/ID could be more explicit

https://github.com/paulevsGitch/BetterEnd/blob/ca31048ca84480f2199408054563b4ae0e620a86/src/main/java/ru/betterend/registry/EndTags.java#L54
I had to add the commons tags folder to my mod to fix a compatibility issue, but I felt like the folder's name could have been more clear.
Because if anyone finds a folder named "c" in my mod they'll have no idea it's to make it compatible with BetterEnds

This is an official Fabric common tag namespace used by many mods, it will likely not be changed

This is an official Fabric common tag namespace used by many mods, it will likely not be changed

OH, I wasn't aware of that... Thanks for telling me !


Fix sign mismatch warning

Cast negative ints to uint32_t to avoid int/uint comparison warning.

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

Rebased, squashed, and pushed into master as 58e53ea8


Locally reproduce and explore MDEW file saving

For exported file storage, MDEW uses a S3-like interface called MinIO.  It's relatively straightforward to setup:
Install MinIO
Mac:
brew install minio
brew services start minio

Setup MinIO
Go to localhost:9000 and login with minioadmin/minioadmin.  From here, create an access key.
Now, in your .env file, add the following:
AWS_BUCKET=mdew-permanent
AWS_REGION=us
AWS_ACCESS_KEY_ID=access-key-here
AWS_SECRET_ACCESS_KEY=secret-key-here
LOCAL_FS_BUCKET=mdew-temp
LOCAL_FS_REGION=us
LOCAL_FS_ACCESS_KEY_ID=access-key-here
LOCAL_FS_SECRET_ACCESS_KEY=secret-key-here
LOCAL_FS_COMPOSE_WITH_AWS_SDK=false

Filenames are now calculated using a dedicated FilenameTasklet; this ensures that the filename will be constant across steps (before it was based only on yyyy/mm/dd, so multiple runs a day would potentially result in issues -- this is now a timestamp).  For more information about this change, see this commit
You should be able to test this yourself by sending a job to MDES with createEvenIfEmpty in AccountReader set to true (by default, if no items are read in, nothing will be processed nor written).  Then, once you send the job, check in the MinIO dashboard (localhost:9000) and you should be able to see the .dat file in mdew-permanent.


Since upgrading to Grav 1.7.21, can no longer save new or existing pages. Get crash with 'Call to a member function header() on array' error

I thought everything was cleared up regarding issue #3432 .  And at least that bug DOES appear fixed after I upgraded from Grav 1.7.20 to Grav 1.7.21.
But then this morning I tried to save a change to a page and suddenly got slammed with an

Error
Call to a member function header() on array

Thought it was just a goof so reloaded the page in the browser, then tried again.  Nope.
Tried creating a new page.  Same thing.  Doesn't matter what directory I put it in.  ANY attempt to save a page, new or existing, results in the same error.
This is not a particularly fancy setup, so I'm scratching my head as to what's going on.  The error is a bit generic, but not sure what information to provide here.
So please specify what I can provide and will do so.

Is this on a custom page type? if so what does your blueprint look like.

Can you try this fix: https://github.com/getgrav/grav/commit/ba19ce4919922b98d3aab0d115f0fd770786c7ab

@rhukster Not a custom page type.  Basic blog item page.
@mahagr How exactly would I go about doing this?  I'm not pulling Grav via Git.  This is stock install doing updates via Admin Panel.
Currently we're talking Grav 1.7.21, Admin Panel 1.10.21, and all other plugins up-to-date.

If I simply open an existing blog item page (I have a separate folder for draft posts) and then try to save it, same error.
Wish there was a simpler way to show this here with copy/paste from the error page.  But it seems to lack line numbers/etc.  Hopefully this screenshot will do it some justice:

Looks like error is occurring on line 134 in ./grav/user/plugins/aura/aura.php if that helps at all.

To be clear, I'm using rather simple pages at this point.  Not even using a modular template or anything.  This is pretty much open editor in Admin Panel to type some words, click [Save].
The only thing that is even slightly unique is that I'm not using the default Quark theme but rather the Gantry5 Helium theme.  But honestly, beyond that, not exactly pushing any boundaries here.

Looks like error is occurring on line 134 in ./grav/user/plugins/aura/aura.php if that helps at all.

But Aura uses getOriginal(), which should be fixed in @mahagr's referenced commit. If you could just apply the changes directly, you'd be able to check if they help

Ok, @mahagr and @Karmalakas , edited the 2 .php files in that commit (didn't bother with CHANGELOG.md), basically changing the variable _original to _originalObject.  And voila!  Yep, now working.  Didn't dig through the source code, but what the?
But yes, I now appear to be able to save pages again.

Same error today after upgrading to 1.7.21. Confirming this (https://github.com/getgrav/grav/commit/ba19ce4919922b98d3aab0d115f0fd770786c7ab) fixed the problem.

I got the same error after the upgrade to 1.7.21 and the commit (ba19ce4) also fixed the problem. Hope it will soon get into a release.

Plan to get a release out soon...


Schema version is outdated

Expected behavior
Actual behavior
Information about the Issue
Using default tag: latest
latest: Pulling from nigelpoulton/pluralsight-docker-ci
Image docker.io/nigelpoulton/pluralsight-docker-ci:latest uses outdated schema1 manifest format. Please upgrade to a schema2 image for better future compatibility.
Steps to reproduce the behavior
run or pull:-
docker run -d --name web -p 80:8080 nigelpoulton/pluralsight-docker-ci

...
...

Try my version: https://github.com/Trackhe/kitematic


Design of the HikariCP

Hello,
I am new in Hikari and currently I am understanding the basic library working. I am bit confused how hikari manage the thread to achieve the pooling. It would be beneficial if you provide design diagram or state diagrams of Thread management.

@sandeep27st HikariCP does not manage threads per-se.
You can visualize HikariCP as a simple BlockingQueue.  It actually does not use a BlockingQueue it uses a specialized collection called a ConcurrentBag, but the behavior is conceptually the same.
In the BlockingQueue model, you can imagine that a client (your code) that invokes HikariDataSource.getConnection() is doing the following:
public Connection getConnection() throws SQLException {
   return connectionQueue.poll(timeout);
}

There is obviously a little more going on, throwing timeout exceptions etc. but that is the basic idea.  Calling Connection.close() essentially returns the connection to the pool.  Conceptually:
public void close() throws SQLException {
   connectionQueue.put(this);
}

Again, there is more going on implementation-wise, but the concept is the same.
HikariCP does have several threads of its own.  There is a "housekeeping" thread that runs periodically to retire idle connections.  There is a scheduler thread that retires connections that reach maxLifetime.   There is a thread for adding connections, and a thread for closing them.


Change error drawable size

Markwon version: {4.6.2}

Please specify expected/actual behavior

I am using the AbstractMarkwonPlugin to make an image full width, also I am using the ErrorHandler. It seems to me that they conflict with each other, because the error drawable is also displayed in full width.
I want to note that this does not happen with the PlaceholderProvider.

Please specify conditions/steps to reproduce (layout, code, markdown used, etc)

String md = "![](https://www.example.com/images/abc.png)";

Markwon markwon = Markwon.builder(context)
.usePlugin(ImagesPlugin.create(new ImagesPlugin.ImagesConfigure() {
            @Override
            public void configureImages(@NonNull ImagesPlugin plugin) {
                plugin.errorHandler(new ImagesPlugin.ErrorHandler() {
                    @Nullable
                    @Override
                    public Drawable handleError(@NonNull String url, @NonNull Throwable throwable) {
                        Drawable brokenImg = ContextCompat.getDrawable(context, R.drawable.icon_broken_img);
                        brokenImg.setBounds(0, 0, 48, 48);
                        return brokenImg;
                    }
                });
            }
        }))
.usePlugin(new AbstractMarkwonPlugin() {
    @Override
    public void configureSpansFactory(@NonNull MarkwonSpansFactory.Builder builder) {
        builder.setFactory(Image.class, (configuration, props) ->
                new AsyncDrawableSpan(configuration.theme(),
                        new AsyncDrawable(
                                ImageProps.DESTINATION.require(props),
                                configuration.asyncDrawableLoader(),
                                configuration.imageSizeResolver(),
                                imageSize(props)
                        ),
                        AsyncDrawableSpan.ALIGN_BOTTOM,
                        ImageProps.REPLACEMENT_TEXT_IS_LINK.get(props, false)
                ));
    }
})
.build();

@NonNull
private ImageSize imageSize(@NonNull RenderProps props) {
    final ImageSize imageSize = ImageProps.IMAGE_SIZE.get(props);
    if (imageSize != null) {
        return imageSize;
    }
    return new ImageSize(new ImageSize.Dimension(100F, "%"), null);
}

With the PlaceholderProvider everything looks good.
.usePlugin(ImagesPlugin.create(new ImagesPlugin.ImagesConfigure() {
    @Override
    public void configureImages(@NonNull ImagesPlugin plugin) {
        plugin.placeholderProvider(new ImagesPlugin.PlaceholderProvider() {
            @Nullable
            @Override
            public Drawable providePlaceholder(@NonNull AsyncDrawable drawable) {
                Drawable brokenImg = ContextCompat.getDrawable(context, R.drawable.icon_broken_img);
                brokenImg.setBounds(0, 0, 48, 48);
                return brokenImg;
            }
        });
    }
}))

Hello @alexxkovalchuk ,
in default image loading plugin, error drawable has no special meaning, it is just a replacement for a failed image. So it goes through all the process - including the ImageSize resolving. In your snippet 100% width is applied, so it is applied to both normal image and error image.
As a workaround, you can create a wrapper drawable that would consume all available bounds, but inside would position error drawable according to your logic


Remove Acoustic Detections from table

@sfregosi Can you remove the column for acoustic detections until we get that working?
It comes across as no data from them at the moment.

Fixed this with 18ef158 but this renders oddly on the website now. Probably because the aspect ratio of the table is different now.
Will relink on web and publish and see if that fixes it.

ok fixed on the web too. Closing!


ARROW-17594: [R][Packaging] Build binaries with devtoolset 8 on CentOS 7

Also closes/duplicates https://issues.apache.org/jira/browse/ARROW-16976

@nealrichardson do you have time to take a look?
This should allow cento 7 users without devtoolset to install and use a binary package built on a system with dts (e.g. RSPM?).
I have opened https://issues.apache.org/jira/browse/ARROW-17849 to document these changes for centos 7 users.

This should allow cento 7 users without devtoolset to install and use a binary package built on a system with dts (e.g. RSPM?).

We should test this

@nealrichardson test on a clean container of rstudio/r-base:4.2-centos7:
> install.packages("arrow_<IP_ADDRESS>20926_R_x86_64-pc-linux-gnu.tar.gz")
inferring 'repos = NULL' from 'pkgs'
* installing *binary* package ‘arrow’ ...
* DONE (arrow)
Making 'packages.html' ... done
> arrow::arrow_info()
Arrow package version: <IP_ADDRESS>20926

Capabilities:

dataset    TRUE
substrait FALSE
parquet    TRUE
json       TRUE
s3         TRUE
gcs        TRUE
utf8proc   TRUE
re2        TRUE
snappy     TRUE
gzip       TRUE
brotli     TRUE
zstd       TRUE
lz4        TRUE
lz4_frame  TRUE
lzo       FALSE
bz2        TRUE
jemalloc   TRUE
mimalloc   TRUE

[# g++ --version
g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

@github-actions crossbow submit r-binary-packages

Here a run with the new test step for the centos 7 package binary https://github.com/ursacomputing/crossbow/actions/runs/3158781948


Missing styling for QTableCornerButton ?

Hello your work looks amazing !
I've manually integrated both stylesheets in my C++ project structure to check them out, they seem to work well (Using Fusion Style for QApplication, then loading the qss files) though I noticed the QTableCornerButton is solid black with both themes.

As a quick fix I added :
QTableCornerButton::section {   background-color: #373a3f; }
to the dark theme, and it seemed to do the trick.

I'm a beginner in Qt stylesheets, if the issue is caused by the fact I'm using the stylesheets in a C++ project then I'm sorry !

Should be fixed in 0.1.4


SCMO-9746 Create cookie response plugin

Please help me out making sure this plugin is activated in AcceptanceTest ... seems like it's inactive, probably must be registered in some place.

We would also need documentation for this plugin similar to what we have for others

ok, I will do it now

acceptance test fixed


Add language model scorer

Cool! Thanks for sending this! Were you able to generate results on librispeech? If so what are the numbers like?

Hi, I did several runs with a model I trained on librispeech's 100h set. Training didn't involve the LM at all. Inference was tested on test-clean without the LM scorer and it produces a CER of 0.160. It gets minimal better including the LM yielding a CER of 0.159. To be honest, I was expecting a higher improvement. Maybe there is something I miss? Have you had a chance to check the PR?

Hi again @awni ,
rather than applying a LM score in ctc_decoder.py row 95, I tried now LM-scoring the nbest (n = 20) beam results and returned every time the one with best total_score. This produces a CER of 0.151 on librispeech test-clean compared to a CER of 0.160 without a LM. I would be glad to hear your opinion on this.
ctc_decoder.py
        .
        .
        beam = beam[:beam_size]

        # LM score up to 20 best beam results
        nbest = beam[:20]
        results = []

        for best in nbest:
            prefix = best[0]
            result = lm.decode(prefix)
            lm_score, word_count = lm.score(result, bos=True, eos=True)
            log_prob = logsumexp(*best[1])
            total_score = log_prob + lm_score + word_count
            results.append([prefix, total_score])
        beam_result = sorted(results, key=lambda x: x[1], reverse=True)

        return beam_result[0][0], beam_result[0][1]

lm.py
class LanguageModel(object):
    def __init__(self, alpha, beta, path=None, preproc=None):
        self.alpha = alpha
        self.beta = beta
        self.preproc = preproc
        self.lm = kenlm.LanguageModel(path)
        print('::: Language model \'{}\' loaded'.format(path))

    def score(self, prefix, bos, eos):
        full_score = self.lm.score(prefix, bos=bos, eos=eos)
        lm_score = self.alpha * full_score
        word_count = self.beta * len(prefix.strip().split(' '))

        return (lm_score, word_count)

    def decode(self, prefix):
        result = ''.join(self.preproc.decode(prefix))
        return result


DBZ-627 Unifying TopicSelector implementations

https://issues.jboss.org/browse/DBZ-627
I'll send the corresponding Oracle connector change tomorrow. I've decided to do this now in order to simplify a heartbeat implementation for PG and the others subsequently.

@gunnarmorling Why was MongoDB connector ommitted?

Ah, good spot. I missed it because MongoDB's selector doesn't extend the
existing TopicSelector interface from core. I'll add that, too. Thanks!

@jpechane pushed one more commit to cover MongoDB, too.

It was like that before and I tried to leave the actual implementation
unchanged.

@gunnarmorling Applied, thanks


Update development-partners.md

Adding ntt data to dev partner

Status
Ready/In Progress/In Hold (Reason for hold)
Related Issues
fixes: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.
Screenshots
Paste here any images that will help the reviewer

@ShahafBenYakir let's do it again!!
note this one is a jpg


Upsert() should function on tables w/o a PK

Hi is there any method to remove only tables while upserting

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Could you be a more specific? I'm not sure exactly what you mean...

Hi ,
when I am making drop_database=false each time the data is appending to the table thus making duplicates records

Does the table with the duplicate records have a primary key? I believe we use the primary key of the table to determine whether a row should be updated or inserted.

what if it does not contain primary keys?

There should be 2 fallback options if no primary keys are present on the table (in order):

We gather all FKs, and use them as a "composite primary key" to upsert() on. This will be a common case when dealing with association tables (in many-to-many relations).
We specify the columns that make up the "composite primary key", as a part of the config, for each table that does not have a primary key.