Slider data-value on init, only sets background, not the handle

I have setup a slider like below (from examples, modified a bit)
  <input id="fro" class="m-4" data-role="slider" data-hint-mask="Feed: $1%" data-hint-always="true" data-value="50" data-min="0" data-max="100">

Once page loads, I get this:

(Note handle/button still at far left)
I am expecting it to be like this on load?

In Your example min value equals to value 50

https://codepen.io/olton/pen/rKdWGb

In your example min value equals to value

(: Ahh man, since you check these from GMAIL, you didnt get the Edits I applied, pasted the wrong line initially, edited it afterwards. Github.com online view shows the edit.
Regardless, if I take your working Fiddle, and copy paste that into mine, still fails.
Back to work now, will dig in and see if I can bisect what fails it then. Thanks for the working fiddle, will probably help me isolate what then breaks it, but at least proves its not a bug

See, edited (:

Okay I have the issue replicated!
https://codepen.io/anon/pen/WyzLqj shows what happens in my app:

The broken Slider is a child inside the DIV
In the app, this DIV is only Activated later  (with a JQuery .show() )
Once the parent is shown, that's where the problem shows itself

Good morning, just checking in if you've had a change to look at the above (:
I have a deadline today (:

This problem is due to the fact that the slider can not calculate its position when the display: none (for a slider or for a slider parent). I'll try to fix it in the next version. While trying to fix using the visibility property or reset value after displaying parent. Thanks

Awesome! Thanks! Will push forward without slider for now (couple buttons
or a menu instead, for now)
On Fri, Jun 22, 2018, 11:02 Sergey Pimenov<EMAIL_ADDRESS>wrote:

Reopened #1119 https://github.com/olton/Metro-UI-CSS/issues/1119.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/olton/Metro-UI-CSS/issues/1119#event-1695486100, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ad_gtx2bZaKBBVdm47lErmliZiNAEtwVks5t_LK1gaJpZM4Uv6bK
.

I fix it in 4.2.9 wait for the release on Sunday

Wowzers!  That is amazingly fast! Thank you SOOOOOO much!
Loving MetroUI, found it on Tuesday and I am never going back to bootstrap
(;
I really love the way your documentation is structured too - starting off
basic and the  as you work down the guide, it builds upon that.
Not to mention, the support you've given me over the two issues I had - out
of this world! Thank you, from the bottom of my heart!
On Sat, Jun 23, 2018 at 1:51 PM Sergey Pimenov<EMAIL_ADDRESS>wrote:

I fix it in 4.2.9 wait for the release on Sunday
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/olton/Metro-UI-CSS/issues/1119#issuecomment-399670808,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ad_gt2VXijqQPN8rhYgnsWQzb6cu6wA1ks5t_iu9gaJpZM4Uv6bK
.


:bug: increase tooltip trigger area

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #4564
[ ] Requires deployment <>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[x] I've tested it at </bsx/collection>
[x] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

pay 30 usd

😍 Perfect, I’ve sent the payout
💵 $30 @ 22.64 USD/KSM ~ 1.325 $KSM
🧗 FNyt7T1xdbhN7dagf7yGYCRJuE3R45VmTCE3tjzy1rKxa7y
🔗 0xb0dc5a8284bef9b332c3d11e334b25c6257de352ecac6c328a6af70d8fd7d8b4
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Fixes bug with newest dagger version

In the newest dagger version the builder is not created with methods for setting the modules but with fields for holding the modules.
This fix will try to look for the method and if no method with module name is found, it will search for a field named as the module.
So every combination of dagger versions is possible.

Thanks for the PR! Is there an alternative way to do it and avoid using an api available only on Android 24+? The library is a java module so it shouldn't contain any android library dependency


Disable autoplay?

Hey y'all, I am building a presentation with this framework, and I find that feature annoying. Is there an option to disable it for the presentation?

Yes, you can do this by omitting the data-autoplay argument in the

 or by setting it to 0. See the docs here (that's from the upcoming impress.js website). @b1ek

Yes, you can do this by omitting the data-autoplay argument in the

 or by setting it to 0. See the docs here (that's from the upcoming impress.js website). @b1ek

I see. Thank you!


Remove extra padding from list inside a set operator nested within a …

…listed set operator.
Yeah!
This is a fix for JIRA issue 166 that affects several measures - CMS171v6, CMS185v5, CMS105v5, and CMS190v5 (bad indenting seen below with red for emphasis).

This is caused by an extraneous <ul> element. The approach taken was to use CSS to target the extraneous element and remove the left padding.

Nice!
It looks like the same thing is happening in the logic view in the patient dashboard:

This must be under a different style hierarchy.
If there's an extra <ul>, should we change how the code is generated so this doesn't happen, or is the extra <ul> necessary?

Good catch, I'll look into that view!
IMO we should probably code up the template more intelligently, but right now it's painfully confusing to parse and much easier to try to target it with CSS..


awscli: 1.19.27 -> 1.19.28

Motivation for this change
Update
Things done

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

[ ] NixOS
[ ] macOS
[X] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-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] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 116525 at 5c9be8e4 run on aarch64-linux 1

10 packages marked as broken and skipped:

awsebcli
mlflow-server
python38Packages.cartopy
python38Packages.flower
python38Packages.geopandas
python38Packages.osmnx
python39Packages.cartopy
python39Packages.flower
python39Packages.geopandas
python39Packages.osmnx

1 package failed to build (new failures):

python38Packages.gradient

9 packages skipped due to time constraints:

mapproxy
python38Packages.fiona
python38Packages.labelbox
python38Packages.rasterio
python38Packages.tensorboardx
python39Packages.fiona
python39Packages.rasterio
python39Packages.tensorboardx
tts

106 packages built successfully:

aws-adfs (python38Packages.aws-adfs)
aws-google-auth
aws-mfa
aws-sam-cli
awscli
awslogs
barman
checkov
cloud-custodian
credstash (python38Packages.credstash)
deja-dup
duplicity
duply
dvc-with-remotes
elasticsearch-curator
git-remote-codecommit
home-assistant
iceshelf
lexicon
luigi
nixops
python38Packages.aiobotocore
python38Packages.aws-sam-translator
python38Packages.aws-xray-sdk
python38Packages.boto3
python38Packages.botocore
python38Packages.celery
python38Packages.certbot-dns-route53
python38Packages.cfn-lint
python38Packages.chalice
python38Packages.django-anymail
python38Packages.django-raster
python38Packages.djmail
python38Packages.ec2instanceconnectcli
python38Packages.flowlogs_reader
python38Packages.fs-s3fs
python38Packages.gensim
python38Packages.hass-nabucasa
python38Packages.kombu
python38Packages.mapbox
python38Packages.moto
python38Packages.pycognito
python38Packages.pynamodb
python38Packages.s3fs
python38Packages.s3transfer
python38Packages.sagemaker
python38Packages.sapi-python-client
python38Packages.scrapy
python38Packages.scrapy-deltafetch
python38Packages.scrapy-fake-useragent
python38Packages.scrapy-splash
python38Packages.serverlessrepo
python38Packages.slack-sdk
python38Packages.slicedimage
python38Packages.smart_open
python38Packages.snowflake-connector-python
python38Packages.snowflake-sqlalchemy
python38Packages.warrant
python39Packages.aiobotocore
python39Packages.aws-adfs
python39Packages.aws-sam-translator
python39Packages.aws-xray-sdk
python39Packages.boto3
python39Packages.botocore
python39Packages.celery
python39Packages.certbot-dns-route53
python39Packages.cfn-lint
python39Packages.chalice
python39Packages.credstash
python39Packages.django-anymail
python39Packages.django-raster
python39Packages.djmail
python39Packages.ec2instanceconnectcli
python39Packages.flowlogs_reader
python39Packages.fs-s3fs
python39Packages.hass-nabucasa
python39Packages.kombu
python39Packages.mapbox
python39Packages.moto
python39Packages.pycognito
python39Packages.pynamodb
python39Packages.s3fs
python39Packages.s3transfer
python39Packages.sagemaker
python39Packages.sapi-python-client
python39Packages.scrapy
python39Packages.scrapy-deltafetch
python39Packages.scrapy-fake-useragent
python39Packages.scrapy-splash
python39Packages.serverlessrepo
python39Packages.slack-sdk
python39Packages.slicedimage
python39Packages.warrant
s3bro
s4cmd
sourcehut.buildsrht
sourcehut.dispatchsrht
sourcehut.gitsrht
sourcehut.hgsrht
sourcehut.hubsrht
sourcehut.listssrht
sourcehut.mansrht
sourcehut.metasrht
sourcehut.pastesrht
sourcehut.todosrht
streamlit

2 suggestions:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/boto3/default.nix:38:3:
   |
38 |   meta = {
   |   ^

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/botocore/default.nix:40:3:
   |
40 |   meta = {
   |   ^

aarch64 failure should be fixed by https://github.com/NixOS/nixpkgs/pull/116511


Update SETI.netkan

Fixed the old SETI-BalanceMod for KSP 0.90 to the version 0.9.0, since it will not be developed anymore.
The kerbalstuff download will be taken over by a similar mod with different structure, therefore I made a pull request for a new netkan identifier/file named "SETI-BalanceMod".
Thank you very much!
Yemo

Lesson learned, should be ok now.

Not really required for a merge, but add the following line so that people can see who the author is:
"author" : "Yemo",

Added author line, thank you!
Just starting to appreciate the kerbalstuff referencing, so easy, so much stuff not to worry about as soon as the license is accepted. ;-)

Merging with my thanks


Because every version of flutter_test from sdk depends on xml 3.6.1 and tiled >=0.4.0 depends on xml ^4.2.0, flutter_test from sdk is incompatible with tiled >=0.4.0. And because flame >=0.24.0 depends on tiled ^0.6.0, flutter_test from sdk is incompatible with flame >=0.24.0. So, because flutter_game depends on both flame ^0.24.0 and flutter_test any from sdk, version solving failed. pub upgrade failed (1; So, because flutter_game depends on both flame ^0.24.0 and flutter_test any from sdk, version solving failed.)

Should I reduce flame version or what ??

Please, use meaningful titles and description when opening a issue.
Anyway, you have two alternatives here

Stay on stable and replace the flutter_test dependency from the sdk to the test package from pub
Go to the beta channel

Let us know if there are still doubts about this.

I have the same issue.

Stay on stable and replace the flutter_test dependency from the sdk to the test package from pub
How to do it?

Just the remove the flutter_test dependency that is on your pubspec, and drop that one instead: https://pub.dev/packages/test
About the beta channel, I am talking about flutter's beta channel, so you can just run flutter channel beta, and keep using fame 0.24.0 from pub


Incorrect for Malaysian Phone Numbers with prefix 6011

Some valid Malaysian mobile phone numbers start with 6011 and contains 12 digits such as 6011-1234-5678. This library does not recognise such numbers.

@jinfeei any update?


Catch TypeError in ixmp show-versions

Closes #338: handle a TypeError in show-versions.
Closes #334: include the output of jpype.getDefaultJVMPath() in show-versions; this was helpful information when providing tech support during the 2020-06 workshop.

How to review
Run ixmp show-versions or message-ix show-versions and confirm that the error observed in #338 does not occur.
PR checklist

[x] ~Tests added.~ N/A
[x] ~Documentation added.~ N/A
[x] Release notes updated.

The error occurred when installing message_ix via Anaconda. I assume that I have to reinstall ixmp from source based on the PR branch khaeru:issue/338. This does, however, not work due to an error when running the pip install command in ixmp that complains that llvmlite cannot be uninstalled (as it was installed via a python setup.py install command). So this is getting complicated...

This does, however, not work due to an error when running the pip install command in ixmp that complains that llvmlite cannot be uninstalled (as it was installed via a python setup.py install command).

Sounds like this was related to #344, i.e. installing in an environment where (Ana)conda had certain versions "pinned".
I've merged the current PR without a manual check, and it can be revisited if the issue reappears.


[LIGHTNODE] [BUG] activate_wallet should be run on the purchased chain

@taariq Can we change the activate flow so that activation can only be done on the Buymore board page? Current logic can't stop this problem.

@jamie088 Let's do it. We already have activate in the BuyMore Page as a CTA,.

Ths is fixed.


[Weblate] Remove empty/unchanged translation strings. Add Bulgarian language. Add general translation updates.

Summary
Remove empty/unchanged translation strings. Add Bulgarian language. Add general translation updates.
Ticket Link

Related Pull Requests

Has server changes (please link here)
Has redux changes (please link here)
Has mobile changes (please link here)

Screenshots

/update-branch

This one needs a QA review

1 - Bulgarian language addition looks good, except please also add test for it at: https://github.com/mattermost/mattermost-webapp/blob/master/components/admin_console/snapshots/schema_admin_settings.test.jsx.snap
2 - Question: what does "general translation updates" refer to?
3 - Two other comments below

Ah nice, will do!
These are the general updates from this PR: https://github.com/mattermost/mattermost-webapp/pull/6347 (I just cannot modify that PR. At least, I don't know how)
Thank you, will fix and enable sorting on weblate side.

@jasonblais yes, upcoming PRs will fix the alphabetical order.

@jgilliam17 this is ready for QA review


Declaration binding identifiers are not mapped to the generated binding location

Search Terms:
source maps
Code
class AnotherThing {
  prop = 4;
}

function someFn() {
}

Expected behavior:
Source maps would map the AnotherThing identifier to the new binding identifier when the class is compiled, so it would reference the name in var AnotherThing =. Same for someFn.
Actual behavior:
The entire class AnotherThing { line is mapped to the entire first and second line output from TS. Same for the function header.
Examples viewed in Sokra's source map visualization

I'll also add that this is also confused by the fact that decoratored classes do map the binding name, but map it to a very unhelpful location, as shown here:

Related Issues:

#22834

Here's another case that is similar to the decorator example. I'd expect ExportedOther to map to the various use of the binding, but I'd expect exports.ExportedOther = ExportedOther; up to the = to map to the class declaration itself.

whereas here you can see that the export class at the start of the declaration isn't tied to the exports.ExportedOther =  part of the code.

Possible this has been fixed, but if not, this doesn't seem to warrant additional work at this point since properties don't need to be downleveled anymore.


cudaPackages: fix cuda alias warning

Description of changes
When build cuda packages, this is always an annoying warning, this PR fix that.
$ NIXPKGS_ALLOW_UNFREE=1 nix build --impure .#cudaPackages.cuda_cccl
trace: warning: cudaPackages.autoAddDriverRunpath is deprecated, use pkgs.autoAddDriverRunpath instead

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

I suppose this should be backported to 24.05?

Done.

More of this is needed:

#335400


Add some more light control sentences

Fix #2319

Summary by CodeRabbit

New Features

Introduced new commands for controlling lights, allowing users to specify actions like turning lights off or on in designated areas, as well as flexible phrasing without area specifications.

Tests

Added test cases to ensure the system recognizes new phrases for turning lights off and on, enhancing the robustness of the natural language processing for lighting commands.

Looks good


New readme and some updated documentation

There's one code change too: I did away with the ParentComponent synonym as it was unhelpful in real work situations. It just made for prettier demos when you only have one-component-deep installation.
Please let me know if there's anything wrong, unclear, missing, or that could otherwise be improved!
Then.... :ship: :shipit: :fireworks: :tada: :confetti_ball:

Really nice work!
One small issue though: the AJAX example fails to build with Unknown value E.onValueQuery (https://travis-ci.org/slamdata/purescript-halogen/builds/85769015#L1915).

Also, might be worthwhile to bump the version of node that is used in the Travis build to quell these complaints: https://travis-ci.org/slamdata/purescript-halogen/builds/85769015#L97

Looks gorgeous! Perfectly happy with this after the issues @jonsterling raised are resolved. Let me know if you want any help writing a roadmap for moving forwards from 0.5.

Thanks! Have fixed the things, will merge and release once Travis passes :smile:

:fireworks: :exclamation:


linera-service uses fs_err for better errors

Motivation
std::fs errors are not comprehensive (intentionally) when it comes to reporting why an fs operation failed. For example, a file will be reported as missing without the file name being provided in the error itself, making debugging difficult.
Proposal
Move to fs_err which is a drop-in replacement for std::fs with convenient error reporting.
Before:
The system cannot find the file specified. (os error 2)

After:
failed to open file `does not exist.txt`
    caused by: The system cannot find the file specified. (os error 2)

Test Plan
Tested by CI.

LGTM. Perhaps undo the with_context that I just added to linera-service/src/cli_wrappers/wallet.rs ?


FIX: path to ParameterConfirmationToken.php

ParameterConfirmationToken.php is in framework/Core/Startup not framework/core/startup.

Nice find, but it has been fixed in other PR just now!


Using VCPKG_OVERRIDE_FIND_PACKAGE_NAME results in calls to unknown command _find_package

Describe the bug
I am using 'VCPKG_OVERRIDE_FIND_PACKAGE_NAME to override the name of find_package to effectively change it to find_vcpkg_package for use in our project. In doing so, I have found that the scripts in vcpkg have made an assumption that find_package has been overloaded and that _find_package is to be called. (See lines 792, 796, 798, etc. in vcpkg.cmake, for example). Unfortunately, this leads to errors like this:
error: XPlat:WinX64: CMake Error at G:/sb-cache/8d9ddd9c2d/installed/x64-windows/share/zlib/vcpkg-cmake-wrapper.cmake:12 (_find_package):
  Message
    Unknown CMake command "_find_package".
  Call Stack (most recent call first):
    G:/sb-cache/8d9ddd9c2d/scripts/buildsystems/vcpkg.cmake:749 (include)
    G:/hup1/Build/Debug/Install/Externals-WinX64/cmake/Externals-WinX64Config.cmake:110 (find_vcpkg_package)
    CMakeLists.txt:8 (find_package)

In this specific case, the issue is in the vcpkg-cmake-wrapper.cmake script where it is assuming that _find_package exists.
Environment

OS: All

To Reproduce
Set VCPKG_OVERRIDE_FIND_PACKAGE_NAME as you normally would on the command line for CMake to something like find_vcpkg_package. Somewhere in your project, add a call to find_vcpkg_package for any library of your choosing.
Expected behavior
I would expect that VCPKG_OVERRIDE_FIND_PACKAGE_NAME is honored everywhere. If it is defined, then find_package must be called. If it is NOT defined, then _find_package can be called.

VCPKG_OVERRIDE_FIND_PACKAGE_NAME is broken. Don't use it. Without cmake_language(CALL) the correct behavior was never implementable.

If you have problems with find_package being overriden by you somehow. Look at #23195

Thanks for the details @Neumann-A! It would be great to get that PR through. The workaround I used in my case was to add the following macro:
    macro(_find_package)
        find_package(${ARGV})
    endmacro()

This allows VCPKG_OVERRIDE_FIND_PACKAGE_NAME to work.

still relevant

relevant

still relevant


Update to the alpha 12 packages

Update to the latest JupyterLab 3.1.0-alpha.11 packages.

Closing in favor of #167


Remove SNMP support.

Fixes #70, helps #186
SNMP was disabled by default, and had a small memory leak. It caused more pain than joy.

Needs conflict resolution.

PTAL


Replace(?) deprecated installation instructions in "Instrumenting a Go application for Prometheus" docs

Hello,
As a new user of both Go and Prometheus, I ran into some issues and tentatively believe the instructions for installing the prometheus/client_golang libraries are outdated as of Go 1.17 in... August 2021. It appears go get was deprecated outside of Go Modules, and requires the creation of a Go Module first. Please let me know if this impression is incorrect, or if a small PR to adjust the instructions might be welcome.
 A PR fixing this would be very welcome.


Setting key = "boolean" in schema and while inserting key = false is not working

Minimal example :
local sqlite = require("sqlite")

local db = sqlite {
  uri = "test_db",
  tbl = {
    ok_key = "text",
    problem_key = "boolean",
  },
}

function main()
  if (db:close()) then db:open() end

  db:insert("tbl", {
    ok_key = "this works",
    problem_key = false,
    -- this is either silently ignored and not inserted in db,
    -- or throws "Missing Key" error when set to false
  })
  db:close()
end

main()

Schema :
sqlite-test · sqlite3 test_db
SQLite version 3.36.0 2021-06-18 18:36:39
Enter ".help" for usage hints.
sqlite> .tables
tbl
sqlite> .schema tbl
CREATE TABLE tbl(ok_key text, problem_key boolean);

Trace :
luajit: /usr/local/share/lua/5.1/sqlite/assert.lua:62: sqlite.lua: (insert) missing a required key: table: 0x416e42c0
stack traceback:
	[C]: in function 'assert'
	/usr/local/share/lua/5.1/sqlite/assert.lua:62: in function 'missing_req_key'
	/usr/local/share/lua/5.1/sqlite/parser.lua:537: in function 'f'
	/usr/local/share/lua/5.1/sqlite/utils.lua:154: in function 'map'
	/usr/local/share/lua/5.1/sqlite/parser.lua:534: in function 'pre_insert'
	/usr/local/share/lua/5.1/sqlite/db.lua:443: in function 'insert'
	test.lua:14: in function 'main'
	test.lua:23: in main chunk
	[C]: at 0x55f144900c20

Environment :

neovim v0.5 (Stable)
luajit v2.0.5
sqlite3 v3.36
sqlite v1.2.0-0

Thanks for the aweome plugin btw! Please let me know if there is anything else I can provide to reproduce the issue.

hmmm I think I see what's happening, false is treated as nil. Could please you confirm that inserting value true works.
Thanks

yep, true works fine.

Nice this should be an easy fix in how values get converted works.
I'll push a fix in a pit, Thanks for debugging.

@EMPAT94 I believe is fixed now, can you confirm.

I'm using sqlite installed via luarocks, not as a plug. Any pointers on how I should test the changes you've made ?

@EMPAT94 You can install master branch using luarocks till the next release.
luarocks install sqlite master

Not sure if you have to remove current one, but is good to do luarocks remove sqlite first

TL;DR = I'm afraid I was not able to test the commit satisfactorily. Installing sqlite master didn't seem to change the result, but it may be an issue unrelated to sqlite itself. When I manually changed the file where error was occuring, it worked just fine.
These are the steps I followed -
test.lua same as before
1. Remove sqlite 1.2 and install 1.42 (master)
/tmp · sudo luarocks remove sqlite && sudo luarocks install sqlite master
Checking stability of dependencies in the absence of
sqlite v1.2.0-0...

Removing sqlite v1.2.0-0...
Removal successful.
Installing https://luarocks.org/sqlite-master-0.src.rock

sqlite master-0 depends on luv (1.42.0-0 installed)
sqlite master-0 is now installed in /usr/local (license: MIT)

2. Try running test.lua
/tmp · lua test.lua
luajit: /usr/local/share/lua/5.1/sqlite/assert.lua:28: sqlite.lua: can not execute insert, tbl doesn't
exists.
stack traceback:
        [C]: in function 'assert'
        /usr/local/share/lua/5.1/sqlite/assert.lua:28: in function 'is_sqltbl'
        /usr/local/share/lua/5.1/sqlite/db.lua:411: in function 'insert'
        test.lua:14: in function 'main'
        test.lua:23: in main chunk
        [C]: at 0x55c17cae2c20

3. Looks like there was some change in how database/tables are created. So I reinstalled 1.2 (stable) sqlite and made sure the table exists.
/tmp · sudo luarocks remove sqlite && sudo luarocks install sqlite
Checking stability of dependencies in the absence of
sqlite master-0...

Removing sqlite master-0...
Removal successful.
Installing https://luarocks.org/sqlite-v1.2.0-0.src.rock

sqlite v1.2.0-0 depends on luv (1.42.0-0 installed)
sqlite v1.2.0-0 is now installed in /usr/local (license: MIT)

/tmp · lua test.lua
luajit: /usr/local/share/lua/5.1/sqlite/assert.lua:62: sqlite.lua: (insert) missing a required key: tab
le: 0x41997a70
stack traceback:
        [C]: in function 'assert'
        /usr/local/share/lua/5.1/sqlite/assert.lua:62: in function 'missing_req_key'
        /usr/local/share/lua/5.1/sqlite/parser.lua:537: in function 'f'
        /usr/local/share/lua/5.1/sqlite/utils.lua:154: in function 'map'
        /usr/local/share/lua/5.1/sqlite/parser.lua:534: in function 'pre_insert'
        /usr/local/share/lua/5.1/sqlite/db.lua:443: in function 'insert'
        test.lua:14: in function 'main'
        test.lua:23: in main chunk
        [C]: at 0x55a20e2b4c20
/tmp · sqlite3 test_db
SQLite version 3.36.0 2021-06-18 18:36:39
Enter ".help" for usage hints.
sqlite> .schema tbl
CREATE TABLE tbl(ok_key text, problem_key boolean);
sqlite> select * from tbl;
sqlite>

4. Then I reinstalled 1.42 (master) sqlite and tried running test.lua.
/tmp · sudo luarocks remove sqlite && sudo luarocks install sqlite master
Checking stability of dependencies in the absence of
sqlite v1.2.0-0...

Removing sqlite v1.2.0-0...
Removal successful.
Installing https://luarocks.org/sqlite-master-0.src.rock

sqlite master-0 depends on luv (1.42.0-0 installed)
sqlite master-0 is now installed in /usr/local (license: MIT)

/tmp · luarocks show sqlite

sqlite master-0 - SQLite/LuaJIT binding and a highly opinionated wrapper for storing, retrieving, cachi
ng, and persisting [SQLite] databases

License:        MIT
Homepage:       https://github.com/tami5/sqlite.lua
Labels:         sqlite3, binding, luajit, database
Installed in:   /usr/local

Modules:
        lua.sqlite.db.lua (/usr/local/share/lua/5.1/lua/sqlite/db/lua.lua)
        lua.sqlite.defs.lua (/usr/local/share/lua/5.1/lua/sqlite/defs/lua.lua)
        lua.sqlite.helpers.lua (/usr/local/share/lua/5.1/lua/sqlite/helpers/lua.lua)
        lua.sqlite.init.lua.init (/usr/local/share/lua/5.1/lua/sqlite/init/lua/init.lua)
        lua.sqlite.json.lua (/usr/local/share/lua/5.1/lua/sqlite/json/lua.lua)
        lua.sqlite.tbl.cache.lua (/usr/local/share/lua/5.1/lua/sqlite/tbl/cache/lua.lua)
        lua.sqlite.tbl.extend.lua (/usr/local/share/lua/5.1/lua/sqlite/tbl/extend/lua.lua)
        lua.sqlite.tbl.lua (/usr/local/share/lua/5.1/lua/sqlite/tbl/lua.lua)
        lua.sqlite.utils.lua (/usr/local/share/lua/5.1/lua/sqlite/utils/lua.lua)
        sql (/usr/local/share/lua/5.1/sql.lua)
        sqlite.assert (/usr/local/share/lua/5.1/sqlite/assert.lua)
        sqlite.db (/usr/local/share/lua/5.1/sqlite/db.lua)
        sqlite.defs (/usr/local/share/lua/5.1/sqlite/defs.lua)
        sqlite.helpers (/usr/local/share/lua/5.1/sqlite/helpers.lua)
        sqlite.init (/usr/local/share/lua/5.1/sqlite/init.lua)
        sqlite.json (/usr/local/share/lua/5.1/sqlite/json.lua)
        sqlite.parser (/usr/local/share/lua/5.1/sqlite/parser.lua)
        sqlite.stmt (/usr/local/share/lua/5.1/sqlite/stmt.lua)
        sqlite.strfun (/usr/local/share/lua/5.1/sqlite/strfun.lua)
        sqlite.tbl (/usr/local/share/lua/5.1/sqlite/tbl.lua)
        sqlite.tbl.cache (/usr/local/share/lua/5.1/sqlite/tbl/cache.lua)
        sqlite.tbl.extend (/usr/local/share/lua/5.1/sqlite/tbl/extend.lua)
        sqlite.utils (/usr/local/share/lua/5.1/sqlite/utils.lua)

Depends on:
        luv (using 1.42.0-0)

Indirectly pulling:
        luv (using 1.42.0-0)

/tmp · lua test.lua
luajit: /usr/local/share/lua/5.1/sqlite/assert.lua:62: sqlite.lua: (insert) missing a required key: tab
le: 0x404a7690
stack traceback:
        [C]: in function 'assert'
        /usr/local/share/lua/5.1/sqlite/assert.lua:62: in function 'missing_req_key'
        /usr/local/share/lua/5.1/sqlite/parser.lua:537: in function 'f'
        /usr/local/share/lua/5.1/sqlite/utils.lua:154: in function 'map'
        /usr/local/share/lua/5.1/sqlite/parser.lua:534: in function 'pre_insert'
        /usr/local/share/lua/5.1/sqlite/db.lua:414: in function 'insert'
        test.lua:14: in function 'main'
        test.lua:23: in main chunk
        [C]: at 0x55d43611ac20

5. Just to be sure, I changed the condition in assert.lua:62 per your commit in my local file (added ~= nil condition)
/tmp · lua test.lua
/tmp · sqlite3 test_db
SQLite version 3.36.0 2021-06-18 18:36:39
Enter ".help" for usage hints.
sqlite> select * from tbl;
this works|0
sqlite>

And it worked! Your commit is probably valid, but there was some complication in installing sqlite/master or my local setup, so I couldn't test it normally.
What next steps do you suggest?

Glad we are over the fix doesn't work and their issue with installation method :D. I'm so noob at luarocks stuff, maybe luarocks master isn't what we expect it to be (i.e. build from master directly). I'd suggest installing sqlite using neovim until #126 is closed

I'll try to avoid boolean for now and stay on stable. Thanks for your help so far!

I'll try to avoid boolean for now and stay on stable. Thanks for your help so far!

We don't want that 😄
I'll try to release v1.2.1 next week 🙂 so it can work according to your current setup.

I appreciate that a lot @tami5. As for your confusion in me sticking to stable, perhaps I should explain better - I'm developing a new nvim plugin.


Implement Hotel - remapped with callback routing

This will be a routing managed with a rule
Make the target link /bananas/rule
Add a routing rule to config/routes.php, which remaps any request with the word "banana" in it, to the Golf controller, but using our own code
$route['bananas/rule'] = function() {
return 'golf';
};

There will be no matches, so the closure function doesn't need parameters
This will be handled by controllers/Golf::index(), already existing


Update all production binary project.json files

Changes:

Update to 1.0.0-beta02 or 0.2.0 (depending on current version)
Update GAX dependencies to 1.0.0-beta02
Update owner to google-cloud
Update summaries and descriptions
Update icons to https://cloud.google.com/images/gcp-icon-64x64.png

Notes on quirks:

I've updated the Google.Datastore.V1Beta3 project.json in terms of
depenencies but not its version or summary/description. We don't
intend to ship a new version of this package.
The IAM package never had a beta01, but in order to get a sensible
starting point to kick off from, it makes sense to create a new tag
etc.
Ditto the 0.1.0->0.2.0 APIs. In future we should probably use 0.0.0
for initial commits.

LGTM


chore: fix some comments

Is this spam? Perhaps the @tianzedavid is farming trust? Github profile looks suspicious

Thanks for noting these.  Most of this text has been removed from the repo during past updates. I have fixed the remaining during my last documentation pass.  Once again, many thanks!


iOS can't scroll vertically on swipeable view

The pink area (swipeable view) does not allow vertical scrolling of the window on an iPhone5. Is there a way to force it?

http://www.webpackbin.com/NJOns1wa-

does not allow vertical scrolling

Are you refering to the inertial scrolling of iOS?

same for me 0.7.9, ipad not scrolling 0.7.8 is ok

It's most likely linked to https://github.com/oliviertassinari/react-swipeable-views/commit/e187f317144f42d892a901dc9208d6a170732497#diff-fb00d0b037b3caf7a015eac7e03a3593R317.
Yeap, I have only noticed the issue on iPad so far.


ADVANCED mode removes assignment to property with setter when the property is never read

This is a simple test:
class A {
    constructor() {
        this.value = "A";
    }

    set someValue(value) {
        this.value = value;
    }

    removeMe() {}
};

class B extends A {
    constructor() {
        super();
        this.someValue = "B";
    }
};

console.log(new B().value);

Output should be B, but with ADVANCED mode it's A. But if you'll remove removeMe() {} the output is B as expected.

Upon further discussion, we've realized that a lot more work is needed to really safely support getters and setters in ADVANCED mode. The fix I had in mind would only have handled a portion of the problem.
Thumbnail sketch:

Compiler will keep a lists of all property names known to have getters and setters.
These lists will be used by NodeUtil methods that need to determine side effects and similar information. Basically, they will make reads and writes to properties with those names be considered to cause unknown side effects.
RemoveUnusedCode will update these lists after it removes code.
Passes that use the NodeUtil side-effects calculation methods but also intentionally ignore it in some cases (like RemoveUnusedCode does in order to remove assignments), will also need to be updated to take this list into account.
We currently don't have a good way to represent getters and setters in externs. This feature needs to be added.
(Optional) It may be helpful to have a pass that intentionally converts getters and setters into "normal" method calls when possible.

For now it just isn't safe to use ADVANCED optimizations if your code uses getters and setters.
Even things that seem pretty safe, aren't really.

FYI. If the list at step 1 is created before disambiguation, it needs to be updated with the new names after disambiguation.

Steps 1 through 4 of the plan described above got done.
re: 5 We can actually represent getters and setters in externs using Object.defineProperty


Any way to run destroy() of PIXI.Sprite?

Description
I have this following code, but it causes memory leaking only in Safari, since the Sprite is completely removed. (seems GC not working)
return (
  <Sprite
    texture={loader.resources[images[index]].texture} // index is set constantly based on user action
  />
)

I simulated the same situation with raw PIXI.js. I guess, since the destroy method is running, the memory is not leaking.
https://codesandbox.io/s/staging-architecture-tl7v0x?file=/src/index.ts
I'd like to know how to use destroy method with react-pixi, or other way to avoid memory leaking.
Additional info

@inlet/react-pixi version: ^6.6.5
React version: ^17.0.2
ReactDOM version: ^17.0.2
PIXI version: ^6.2.2

On the other hand, in your code above the Sprite never gets destroyed because it will never unmount. Which is good.. you are only changing the texture.
It might be possible that there's something else happening in your code that's causing the memory leak?

Hello @inlet
Thank you for replying.
Okay, I'll create react-pixi demo in a moment.

Sprite never gets destroyed because it will never unmount.

Yes, that's exactly what I was thinking.
Since only the texture changes, Sprite will never unmount.
Which means new Sprite object is created every time as the texture changes, though the older ones are not removed.
That's why I was looking for the way to run destroy method manually.
Anyway, I'm going to create the demo!

Which means new Sprite object is created every time as the texture changes, though the older ones are not removed.
That's why I was looking for the way to run destroy method manually.

Only 1 Sprite object will be created only the texture member will be updated

@inlet
Hmm.. It seems working well with minimum demo...
https://codesandbox.io/s/frosty-darkness-wvs8ds?file=/src/index.tsx
It could be my source code's fault.
Sorry for opening a mistaken issue :_(
I'm going to investigate more, then I will contact you if anything founded.
Thank you.

Sure, keep me posted so I can close this issue. Thanks!

Hello @inlet
I may found the issue.
As the total image size is larger, the memory seems never released in Safari.

On the other hand, in Chrome, JS Heap size works well.

I would appreciate it if you could check my demo.
demo: https://codesandbox.io/s/jolly-water-equs3i

I don’t see any issues with your demo, it must have to do something with how Safari handles GPU GC.
It might be worth filing an issue in the PIXI repo? Have you tried it with vanilla PIXI?

I don’t see any issues with your demo

It might be because of machine's speck. I'll make it load more image, then you could see the issue.

Have you tried it with vanilla PIXI?

Yes. The first one is with vanilla.
When the destroy method is not called, the memory graph looks similar as the one with react-pixi
https://codesandbox.io/s/staging-architecture-tl7v0x?file=/src/index.ts

Right so we can confirm the same logic happens with vanilla PIXI.
I’ll close this issue as it’s not related to react-pixi but with PIXI in general

Have you tested it out with Sprite that’s getting removed? As you can see in our reconciler tests all unmounted components are getting destroyed properly.
https://github.com/inlet/react-pixi/blob/master/test/reconciler.test.js#L309

In your example you’re updating the texture prop, please try setting a key prop that unmounts the old and mounts a new one

@inlet
FYI:
Although it actually works with following code to some extent, it's necessary to set a key prop on Stage component  for much heavier images..
(By the way, it didn't work to set a key prop on Sprite component)
<Contaienr key={state}>
  <Sprite
    ...
    texture={state}
  />
</Container>

Thanks for the reference 😁


Bugfix/remove jira links from initial revision

This PR handles historical items from the changelog where it concerns the fields "Epic Link" and "Parent" so that they are removed from the initial revision.
Unittests will fail until #559 is fixed :)
Fixes #563

Looks fine to me. @madkoo, @moerketh, what is the status on this PR? Ready to merge or does it need further changed?

Looks fine to me. @madkoo, @moerketh, what is the status on this PR? Ready to merge or does it need further changed?

@Alexander-Hjelm the unittests in this PR require the changelog history to be parsed in the correct order or they will fail. So this should wait for #580 to be merged.


Android: Reduce overdraw layers by hiding cards when they are not visible

Cards which are not visible because another card is occluding them are still being rendered by Android resulting in overdraw. This results in wasted GPU time because some pixels are drawn multiple times. This change reduces overdraw by changing the opacity of occluded cards to 0.
This bug was found using the tools described in Android's overdraw docs: https://developer.android.com/topic/performance/rendering/overdraw.html
Test plan (required)
This change is being used in my team's app.
Adam Comella
Microsoft Corp.

cc @skevy @ericvicenti

Thanks, makes sense.
@facebook-github-bot shipit


Problems with MODULE.FUNCTIONNAME When Sharing Lambdas

I want to create a library of Lambda functions to share and after experimenting with various ways of sharing, I'm running into problems when importing from a Gist.
When you import a Gist into a new module, the user can name that module whatever they want, and then the functions within that module are automatically named MODULE.FUNCTION. For example, the user creates a module named MATH and imports a Gist containing a function named MYFUN. The name that Excel Labs creates in the Name Manager is MATH.MYFUN. This is of course already documented, but creates a couple of problems:
Problem 1: If any of the other functions contained within the Gist use MYFUN, those functions are now broken. A possible solution would be to have Excel Labs automatically refactor the function names. Meanwhile, the best solution I can think of is to warn users to NOT import the Gist into a new module. The not-good solution (because it means duplication of code which defeats the purpose) is to avoid calling any named lambda functions within other lambdas.
Problem 2: Functions that use recursion, calling themselves by name, will become broken.
Solution: Wrap the recursive function with LET like this example (this function stacks an array n times - something you can do with REDUCE, but shown here for the sake of an example):
EXAMPLE = LAMBDA(param_1,param_2,
LET(
recurseFun,LAMBDA(SELF,param_1,param_2,[i],[accumulator],
IF( ISOMITTED(accumulator),
IF( IF(ISOMITTED(i),1,i) >= param_2,
param_1,
SELF(SELF,param_1,param_2,i+1,param_1)
),
IF( IF(ISOMITTED(i),1,i) >= param_2,
accumulator,
SELF(SELF,param_1,param_2,i+1,VSTACK(accumulator,param_1))
)
)
),
recurseFun(recurseFun,param_1,param_2)
));
Problem 3: If I create functions named ODE.MYFUN or L.MYFUN, and these are imported into any new module, they result in errors. I think this is an AFE issue because MODULE.ODE.MYFUN is still a valid lambda name. But, the AFE considers it an error if ODE.MYFUN is contained within a module named MODULE.
Solution: Avoid using periods in lambda names, to avoid conflicts with parameter names and how the AFE works.

For problem 1. would you be able to provide a self-contained gist that demonstrates the problem? Name resolution in modules allow a name to refer to another name within the same module, regardless of the module name. For example, the module:
FUN_1 = LAMBDA(x, x + 1);

FUN_2 = LAMBDA(x, FUN_1(x) * 2);

Within FUN_2 the name FUN_1 will always refer to the definition above, even if you give the module a new name. When we save the module out, we add the prefix, but you do not need a prefix within the module.
For problem 2, similarly, is there a gist I can import that shows the error? You can define a name like:
TO_ZERO = LAMBDA(
    x,
    IF(x = 0, "done", TO_ZERO(x - 1))
);

And the reference to TO_ZERO should get the right prefix added when saved out.
For problem 3, yes this is a limitation / by design in AFE. In general, we only allow dot's to be in top-level name to avoid complex resolution cases such as a.b.c which could mean get c from a.b, or get b from a and then get c from the result.

Hi Jack, thank you for your reply. My mistake. After trying your examples, I figured out that I was doing a couple of things wrong:

My main issue was that I was confounding problems 1 & 2 with problem 3. Now that I've fixed the naming to avoid any periods, the behavior is as you have described.

I was using parameter names that were the same name as the module. For example, using "s" as a parameter name within a function results in an error if the module ends up being named "S". This was happening because I was using abbreviated module names like M, S, A, etc.

I'm not sure how to get around this second issue if a person happens to name their module the same thing as one of the parameters, but at least the main issue can be avoided by not using periods in lambda names.
Thanks!

The second bullet is a design limitation in AFE, Excel, and how formulas are saved. We prevent it and flag an error, otherwise the formula would not work. We do raise errors more than we need to, so in that sense there is a 'bug'.
The reason why we flag the error is as follows. Suppose we have a module called table and we define a function that defines a parameter called table. It could be a let or lambda parameter.
localFunction = LAMBDA(x, x + 1);

myFunction = LAMBDA(table,
    table + localFunction(10)
);

When we save myFunction into the name manager it will look like:
LAMBDA(table, table + table.localFunction(10)). Note that we prefix the local function now with the module name.
Unfortunately, this will not work correctly. The presence of the parameter table from the LAMBDA means that table.localFunction will be evaluated as "lookup field localFunction on the function input table" rather than "return the formula named table.localFunction"
My only suggestion and workaround is to prefix LET or LAMBDA parameters with underscore to make them different from module names.

Thank you. In my documentation, I think I will also suggest a few safe names for the module in case they want to import to a separate module.


Sorting ends of Voronoi diagram edges.

There is a Voronoi diagram. For compactly located cloud of points it looks like this:

As you can see it is a simple graph. A set of connected edges, which not corss each other. Some of them are rays (on the periphery), another ones are sections (also it is possible a strait line case, but it is not too interesting corner case).
x-coordinate of the begins of the edges have the following distribution (in order of construction of them by Fortune's algorithm):

Corresponding distribution for ends is here:

I.e. it is almost sorted set of objects. They are almost not sorted in a strip of almost constant height.
Does vergesort suitable for such a distribution?
Is there good precalc for data, to ease a work for some classic sorting algorithm?

Looking at your distributions, it looks like an Inv-adaptive or Rem-adaptive sorting algorithm would be better: vergesort works well when there are runs bigger than n / log n in the collection to sort, where n is the size of the collection to sort. In your case, while the distributions look mostly sorted, the main feature in not big sorted runs", but "few misplaced elements". For such a case an algorithm like drop-merge sort is probably more suitable.

Thank you.

No problem. Your Voronoi diagram is pretty by the way :3

I just want to solve the problem of finding a nearest point from first set to each of points from second set using Fortune's algorithm (for M=100000 and N=10000 it faster then solution using AVX vectorization).


Option to grant other channels permission to edit/manage a calendar

It would be a real boost for the community focus of Hubzilla if you can grant other channels permission to edit/manage a calendar.
Or to give a use case: Make it possible that certain people in a forum-channel can add and/or edit events in this forum-channel. For example: some people in a forum--channel can update a community calendar.

related #216

Yes, I saw that one. Indeed related, but not a duplicate.

@spukkin has been trying to do this, and running into difficulty.
Linking the discussion here:
<EMAIL_ADDRESS>It'd sure be nice if that worked, but it touches deep corners of Hubzilla that I don't understand and don't have time to explore at the moment.

Sorry, but @spukkin has a different unrelated issue. Delegated channel administration is a potential workaround to sharing calendars, though it lets the channel have access to a whole lot more than just the calendar so can't be used in all calendar sharing scenarios.
Remote channel admin has been working well. Again, as noted in that thread, all that is required is a detailed series of steps to reproduce the abnormal behaviour observed there.


POST /wallet/spend supports unique coin per transaction

Done in #1059

Can we close this @placer14 ?


Provide default icons

Favicon
iOS and Android icons

Do we have a designed icon that just need to be inserted or is this a design issue?

This logo should also be used in the readme.

obelisk-logo.tar.gz


Persistent Indexes?

Are there any plans for persistent indexes stored in leveldb?

Yep, there are plans for those. However, they cannot be automatic like the in-memory indexes, and to be truly useful, compound indexes must be implemented.
But it's a great feature, since it could allow larger datasets and remote access/replication without waste of resource

@Ivshti Thanks for the prompt reply. What do you mean by "cannot be automatic ..."? And yes compound indexes are a must.  Do you have a time-frame for this?
An in-process Node database package which was compatible with Mongodb would be incredibly useful, to me and I'm sure many others. I'm currently using Mongodb in my Web Knowledge Base app Clibu http://clibu.com and it is great. However I'm also packaging up a stand-alone version of Clibu which can be installed on the end-users PC. This is where an in-process db would be so much better than using Mongodb.
Thanks for your work on linvodb3.

"cannot be automatic" - currently indexes are created automatically for every looked-up property; if we do this for persistent indexes, the user may accidently polute everything with indexes
Also, currently compound indexes aren't given a priority as with <1 million datasets and in-RAM indexes, there's no real benefit from compound indexes. But I agree, they are important, especially with persistent indexes.
Regarding MongoDB compatibility - unfortunately, the goal here is to be similar to mongodb, not 100% compatible. 100% compatible is too responsible, difficult and would result in some technical compromise. Usually this shouldn't be a problem for most cases, but just keep that in mind.
I don't have much time lately for this project, but I think in 2-3 months I will absolutely have to implement persistent indexes

@Ivshti Thanks for the extra info. I didn't realize linvodb3 created an index for each queried property. You definitely wouldn't want that for persistent indexes. If I understand correctly I'd use {autoindex: false} to turn that off and use Doc.ensureIndex() to explicitly create just the indexes I want.
I understand the MongoDB compatibility and that's fine.
You maybe interested in reading http://pouchdb.com/2014/05/01/secondary-indexes-have-landed-in-pouchdb.html - "For the database geeks: implementation details" which discusses how they've added support for secondary indexes to PouchDB. In essence that concatenate the secondary key + id of the document being indexed, which means they can update these secondary keys efficiently.
There are also some levelup libs such as https://github.com/juliangruber/level-secondary and https://github.com/eugeneware/jsonquery-engine which implement secondary indexes which could be worth looking at.
I'll look forward to seeing you future release with persistent + secondary + compound indexes.

@nevf yes - if you autoindex: false, no indexes are going to be created. And you can use ensureIndex then
Thanks for the hints, I'll check them out!

Hello @Ivshti, very interesting database and thanks for the sharing your work. I am considering it for integration in an Electron desktop app.
I am trying to get a better understanding of your database from the documentation. Could you please comment on what is written here https://docs.omniref.com/js/npm/linvodb3/3.5.0#label-Indexing

If your datastore is persistent, the indexes you created are persisted in the datafile, when you load the database a second time they are automatically created for you. No need to remove any ensureIndex though, if it is called on a database that already has the index, nothing happens.

and the nature of this conversation you had with @nevf? Do I understand that in the mean time since January you implemented persisting of secondary indexes on disk? In the quoted text, what does 'they are automatically created' exactly mean?
Thank you.


React money hoc

Wrapping any component that has a text input to enforce a given currency format as the user types

There are already packages that do this and it seems a companion package that wraps an existing one but also accept wealth money instances may be the way to go. need to investigate further.

If and when doing this, monorepo should be considered.


Whitelist OpenID Connect configuration claims

Admins may want to be able to control which configuration claims are published on .well-known/openid-configuration. This feature would enable a configuration whitelist to filter which claims are published.

duplicate.

duplicate.


Horizontal scroll view inside a nested scroll view throws out of bounds error

I am having difficulty nesting a horizontal list view within a nested scroll view. What I really want is a group of horizontal lists one below the other within a vertical list view sort of container.
My code
body: new NestedScrollView(
            scrollDirection: Axis.vertical,
            headerSliverBuilder:
                (BuildContext context, bool innerBoxIsScrolled) {
              return <Widget>[
                new SliverAppBar(
                  pinned: true,
                  title: new Text("Home"),
                ),
             ];
           },

body: new ListView.builder(
                    padding: const EdgeInsets.only(bottom: 30.0),
                    scrollDirection: Axis.horizontal,
                    itemCount: TooursData.indianTours.length,
                     itemBuilder: getPkgCell,
                  ),
),
...

Widget getPkgCell(BuildContext context, int index) {
return new Container(
      margin: const EdgeInsets.only(right: 20.0),
      width: 300.00,
      decoration: new BoxDecoration(
        color: Colors.white24,
        border: new Border.all(color: Colors.blue, width: 1.0),
        borderRadius: new BorderRadius.circular(2.0),
      ),
      child: ...

I get a yellow band with black slant stripes telling me to use flex or expanded which are of no use.

For this kind of question StackOverflow is probably a better place to ask.

Okay, after lot of frustration and unsuccessful attempts, finally able to get help from this github project https://github.com/mtellect/FlutterGirliesShop-Part1-/blob/master/lib/userScreens/item_details.dart
Apparently we have to use a SingleChildScrollView which acts like the vertical list, and use a card outside a horizontal list view to have a carousel effect. I had to copy all code instead of reading entriely due to some reasons, so if anyone got explanation, please do

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.

wrap your nested listview inside a container and give it a height (e.g. 100) and it will work.


Simplify Advance Example

Is your feature request related to a problem? Please describe.
When having a look at the advanced example, it is not clear right away, how a variable should look, because it is hidden away in a local. This is even worse in the README, as the local.tf is nowhere integrated.
Describe the solution you'd like
Remove locals completely from examples and hardcode the values.
Describe alternatives you've considered
The only upside of locals is, that you can reuse the values. But as examples are examples, there is no need to reuse values.

Furthermore the Network security rule has nothing to do with the module and should also be removed


Problem after creating a new table attribute

Hello,
First of all let me say thank you for taking the time to release and maintain this bundle.
Secondly, I'd like to outline the problem I'm having...
I recently installed a fresh version of Akeneo (3.2.12 CE) and then on top of this installation I installed the akeneo-table-attribute-bundle - visually everything looked good.
I then created by first table attribute and clicked save to see the "columns" option display... this also looked good.
The issues came when I started to add column values - upon clicking save I see a red alert icon which has a tooltop saying "500". and in the logs I have the following error:
[2019-10-10 15:42:55] request.INFO: Matched route "pim_enrich_attributeoption_create". {"route":"pim_enrich_attributeoption_create","route_parameters":{"_controller":"pim_enrich.controller.attribute_option:createAction","_format":"json","attributeId":"11","_route":"pim_enrich_attributeoption_create"},"request_uri":"https://pim.example.com/configuration/attribute-option/11","method":"POST"} [] [2019-10-10 15:42:55] request.CRITICAL: Uncaught PHP Exception Symfony\Component\Debug\Exception\FatalThrowableError: "Call to a member function setValue() on null" at /var/www/pim.example.com/vendor/doctrine/orm/lib/Doctrine/ORM/PersistentCollection.php line 167 {"exception":"[object] (Symfony\\Component\\Debug\\Exception\\FatalThrowableError(code: 0): Call to a member function setValue() on null at /var/www/pim.example.com/vendor/doctrine/orm/lib/Doctrine/ORM/PersistentCollection.php:167)"} []
Any help or pointers would be appreciated.
Many Thanks,

Hello,
Nearly same error with version pim v3.0.49.
I create a new attribute but when I click on Columns tab I got error 500 with this in logs :
[2019-10-25 14:48:48] request.INFO: Matched route "pim_enrich_attributeoption_index". {"route":"pim_enrich_attributeoption_index","route_parameters":{"_controller":"pim_enrich.controller.attribute_option:indexAction","_format":"json","attributeId":"207","_route":"pim_enrich_attributeoption_index"},"request_uri":"https://mycompany:port/configuration/attribute-option/207","method":"GET"} []
[2019-10-25 14:48:48] request.CRITICAL: Uncaught PHP Exception Symfony\Component\Debug\Exception\FatalThrowableError: "Call to a member function setValue() on null" at /srv/app/vendor/doctrine/orm/lib/Doctrine/ORM/PersistentCollection.php line 168 {"exception":"[object] (Symfony\Component\Debug\Exception\FatalThrowableError(code: 0): Call to a member function setValue() on null at /srv/app/vendor/doctrine/orm/lib/Doctrine/ORM/PersistentCollection.php:168)"} []
[2019-10-25 14:48:48] request.CRITICAL: Exception thrown when handling an exception (RuntimeException: Failed to start the session because headers have already been sent by "/srv/app/vendor/doctrine/orm/lib/Doctrine/ORM/Persisters/Entity/BasicEntityPersister.php" at line 1773. at /srv/app/vendor/symfony/symfony/src/Symfony/Component/HttpFoundation/Session/Storage/NativeSessionStorage.php line 141) {"exception":"[object] (RuntimeException(code: 0): Failed to start the session because headers have already been sent by "/srv/app/vendor/doctrine/orm/lib/Doctrine/ORM/Persisters/Entity/BasicEntityPersister.php" at line 1773. at /srv/app/vendor/symfony/symfony/src/Symfony/Component/HttpFoundation/Session/Storage/NativeSessionStorage.php:141)"} []

We are having the same issue as @scivray and @allanhansen-vaimo

@allanhansen-vaimo  @scivray  -> i found the issue being the apache service after installing the module. It's probably due to us running Akeneo from a Bitnami image.
Restart apache service, and then it should be all ok.

@scivray @allanhansen-vaimo Can you verify that this issue depends on the environment?

@scivray @allanhansen-vaimo Can you verify that this issue depends on the environment?

Yes, but it isn't related to Bitnami, it is also necessary to restart Apache and PHP-FPM containers in the Docker env. that Akeneo supplies.


replace_missing should just do nothing if missingval is allready missing

Currently this throws:
MethodError: Cannot `convert` an object of type Missing to an object of type Float64

Which makes no sense

Hi, I have the following Raster:
julia> dc
84×155×1×123 Raster{Float32,4} unnamed with dimensions:
  X Mapped Float64[72.7250001018, 72.72916676850001, …, 73.0666667712, 73.0708334379] ForwardOrdered Explicit Intervals crs: EPSG mappedcrs: EPSG,
  Y Mapped Float64[19.495832889299994, 19.491666222599996, …, 18.858332884200003, 18.8541662175] ReverseOrdered Explicit Intervals crs: EPSG mappedcrs: EPSG,
  Band Categorical Int64[1] ReverseOrdered,
  Ti Sampled Int64[201204, 201205, …, 202205, 202206] ForwardOrdered Irregular Points
with missingval: missing

I want to do something like:
dc[1,1,1,1] = missing

I wish to do this because the list of missing observations is provided in a separate file, and I have to manually mark the missing observations.
But get the error that you have mentioned above.
Any suggestions?
I feel if missingval is missing, the Raster should automatically be Union{Missing, something}
Apologies, if this issue wasn't the most suitable place to ask this question.

Thanks I just forgot about this!

Thanks, Rafael,
I'll open a new issue and share the .nc file.


Support iOS precomposed suffix for icons

Support to add the precomposed keyword in icons links like <link rel="apple-touch-icon-precomposed" href="/images/icons/apple-touch-icon-192x192.png" sizes="192x192">

@hidnasio can you rebase with master?

@san650 done


Refactoring of many classes

This PR contains a reworking of multiple classes, renaming and refactoring. Tests have been updated a bit, but are the next target in refactor / extension of coverage.

@gmohre @TheCodinator19 These looks like valuable improvements. Seems like a good thing to merge. Thoughts?


Fix finding variables with sc.pl.scatter(..., use_raw=True)

sc.pl.scatter() is a wrapper for _scatter_obs(). It checks to make sure
the variable names the caller is requesting to plot exist in var and/or
obs, but does not take into account whether it should look in raw based
on the use_raw flag, as _scatter_obs() does. This leads to errors when a
user asks to plot variables that are in the raw but not the filtered
matrix of adata. This commit fixes that bug.

It looks like all of the tests that failed have to do with ingest functionality and are thus unrelated to this PR. The same ones failed on the PR after this one as well. Let me know what I can do to fix this.

Hey @esrice, thanks for the PR! Those tests are failing due to a recent umap release. This should be fixed on master now, so just merge master into this branch and they should be fixed.

Thanks! Looks like that fixed the problem.

Yes, for sure, one of the two commits I just pushed adds a few tests for various cases of sc.pl.scatter() with basis=None.
You're totally right that plotting the transposed matrix (i.e., cells as points in the scatterplot, instead of genes) does not work. I think this is a separate problem from the one I'm fixing here, in response to the issue #1097. It seems to me there are two problems going on:

The wrapper function sc.pl.scatter() mistakenly raises a ValueError if x, y, or color are var_names that exist only in raw but not in the base layer, even if use_raw=True. The underlying _scatter_obs() has no problem dealing with this situation, so to solve this, sc.pl.scatter() just needs to call _scatter_obs() in this case instead of raising a ValueError. This PR fixes that.
When x, y, and/or color are variables found in obs.index or var.keys(), sc.pl.scatter() makes a transposed version of adata, but as you said, adata.raw does not get transposed. This leads to an AttributeError on this line of _scatter_obs():

https://github.com/theislab/scanpy/blob/cab9f781f9fdee2eeebf05a84c2ce5f717afa514/scanpy/plotting/_anndata.py#L250
AttributeError: 'NoneType' object has no attribute 'obs_vector'
I'm not sure what the correct way to handle this is, so for now, I'm

adding a commit so that this PR does not modify anything in the part of sc.pl.scatter() dealing with transposition
adding a parametrized test to test_plotting.py that tests all use-cases of sc.pl.scatter() where basis=None, except for the one where use_raw=True and x/y/color are per-obs variables, as that didn't work before this commit or after it. It's still in the parameter list but commented out for now. I'd be happy to help fix it since I've familiarized myself with this code pretty well, but we might need to discuss how this case should be handled first, and my suggestion would be to deal with this in a separate PR/bug fix/commit.

What do you think?

I'm wondering if use_raw should just do something like:
if use_raw:
    adata = adata.raw.to_adata()

That's a great idea. It might require some reorganization, though, because currently use_raw is checked two places: once in sc.pl.scatter(), because it needs to know whether to look for variables in raw or not when deciding how to call _scatter_obs(), and again in _scatter_obs() itself. And it would probably be bad to do adata = adata.raw.to_adata() twice?
On another note, some pytests that are in files I did not edit are now failing because they can't find anndata.tests to import. I'm not sure if I messed something up by adding tests to test_plotting.py or whether this is a different issue.

It looks like running adata.raw.to_adata() does not preserve the var table, so that won't work either:
>>> import scanpy as sc
>>> pbmc = sc.datasets.pbmc68k_reduced()
>>> pbmc.var.keys()
Index(['n_counts', 'means', 'dispersions', 'dispersions_norm',
       'highly_variable'],
      dtype='object')
>>> pbmc_raw = pbmc.raw.to_adata()
>>> pbmc_raw.var.keys()
Index([], dtype='object')

That's a great idea. It might require some reorganization, though, because currently use_raw is checked two places: once in sc.pl.scatter(), because it needs to know whether to look for variables in raw or not when deciding how to call _scatter_obs(), and again in _scatter_obs() itself.

Would it be possible to not call it again in scatter_obs? E.g. could _scatter_obs not even need to know about the raw field?

On another note, some pytests that are in files I did not edit are now failing because they can't find anndata.tests to import. I'm not sure if I messed something up by adding tests to test_plotting.py or whether this is a different issue.

 On the plus side it means our build system is now working as it's supposed to.

Would it be possible to not call it again in scatter_obs? E.g. could _scatter_obs not even need to know about the raw field?
Sadly not, because to_adata() does not preserve var columns (see my previous comment) :(

It looks like running adata.raw.to_adata() does not preserve the var table, so that won't work either:

That makes sense though right? Since it's a different set of variables. That said, I do suspect there is some weirdness about handling of use_raw here that doesn't actually make sense when you think about it, but would break some code.

Yes, I agree. My proposal would be to integrate this PR as it currently stands (after the testing system is working), as it fixes #1097 (namely, you can't currently set x, y, or color to something that is in adata.raw.var.index but not adata.var.index, even if use_raw=True) and leaves the logic flow for the transposition case as is. It also adds some test coverage to use cases of sc.pl.scatter() that were not covered before. Then, I can start working on coming up with a strategy for solving the second problem (use_raw=True with transposition) separately, as it's mostly unrelated, and seems to be a bit more complicated.

Tests are working now

Awesome, thanks. Do I need to do anything still?

First, thanks for adding more tests!

Sure thing. Thanks for all the great feedback!

1. Is the file `scanpy/tests/_images/scatter_filtered_genes_raw.png` meant to be here?

No, thanks for catching that.

2. Could the tests be broken up by what they are asserting? I would prefer to break up what is being tested by test case

rather than values of parameters.
Yes, I've broken both of the tests down into multiple tests.

3. Could we cut down on the number of reference images generated since those cause manual maintenance burden on some matplotlib updates. These reference based tests are not great for confirming the correct plot is output, only that their output is consistent across commits.

I think some of these cases could instead be tested with check_same_image, e.g. where it doesn't matter whether raw is True or None. Also testing for checking cases where use_raw=True would be equivalent to passing pbmc.raw.to_adata().

I've cut the number of reference images down to two. I couldn't figure out a clever way to use check_same_image() instead of save_and_compare_images() for these as you did for the others.
See below for comments about individual suggestions.

Awesome, just gave you write access to my fork.


Consider moving the BinderHub helm chart + deployment docs into the JupyterHub helm chart

For several reasons it would be useful long-term if there weren't two different helm charts (one for JupyterHub and one for BinderHub) as well as two totally separate sets of documentation, given that they overlap so much.
One idea that's been kicked around a bit is to treat a "BinderHub" as a particular flavor of a JupyterHub on Kubernetes, as opposed to its whole separate thing. Doing this would basically require two main things:

Make "BinderHub functionality" possible via configuration in the JupyterHub helm chart
Remove much of the "BinderHub install guide" docs into a section of the Z2JH guide

I think this could have a lot of benefits / improve the long-term sustainability of the codebases/documentation. It'd be great to chat about this further! Just opening this issue for conversation.
cc @yuvipanda as I think he has thoughts on this

Back in the day, the binderhub chart (currently this subdirectory of the binderhub repo) used to live here, as a separate chart. It was moved over primarily because:

BinderHub was moving far faster than z2jh at that time
It was a separate, non-integrated chart that needed upkeep by itself.
BinderHub was not a JupyterHub service, but a program by itself that did not talk to the JupyterHub API

This however, has come with negatives:

Confusion around 'binderhub' vs 'jupyterhub', when in reality BinderHub is just a JupyterHub service, similar to how 'cull_idle_users' is a jupyterhub service
We need to spend twice the effort in documenting JupyterHub here and BinderHub helm chart in the other repo, while in many cases they're pretty much the same

I propose that we do the following:

Move the binderhub helm chart here, but
Integrate the components into the jupyterhub helm chart we have here.

Ideally, the following snippet in your config.yaml would be all that is needed to enable a binder service (dynamic image building) for your jupyterhub:
binderhub:
   enabled: true

We can do this in ways that don't unduly increase the maintenance burden for us on deploying mybinder.org changes.
With this, we'll have:

github.com/jupyterhub/binderhub -> contains binderhub code, similar to how github.com/jupyterhub/jupyterhub contains jupyterhub code
This repo, which will contain a JupyterHub chart that has an option for enabling BinderHub

This also forces us (and makes it easier!) to have a release cadence for public binderhub chart based usage similar to what we have for the (more mature) z2jh JupyterHub chart.

@yuvipanda do you have a feeling for whether this is a short/medium/long-term goal? In terms of how much effort it'd take to make this happen?
@mpacer this is the issue I mentioned earlier today, in case you have thoughts

I think of this as something we could do for z2jh 0.7 or 0.8, so near-mid term.

I am actually now convinced this is something we should do for z2jh 0.7, and so might start doing this soon (unless there are objections!). I'll plan on laying out a path forward here first in the next few days, and then go from there.

Let's discuss this at the next team meeting. I'm supportive of simplifying and better maintainability. I do want to make sure that we're all on the same page and that we don't accidentally confuse ourselves, our users, or others in the wider Jupyter project.
Much like an incident report, it would be great to have simple template for larger changes such as this one where we can define the change, its impact, and our communication strategy to the larger Jupyter team and the community. It doesn't need to be a separate document. There's an example below that is my understanding of the above discussion. Feel free to edit it directly here. @choldgraf @yuvipanda

Proposal: Change location of BinderHub helm chart and documentation
Challenge
Two sets of documentation and helm charts (binderhub and jupyterhub) duplicates content.
Goals

Minimize duplicated content in code and documentation
Improve maintainability

Proposed changes

Treat binderhub as a service of jupyterhub
github.com/jupyterhub/binderhub repo contains binderhub code (similar to how github.com/jupyterhub/jupyterhub repo contains jupyterhub code)
The binderhub repo will contain a sample JupyterHub chart that has an option for enabling BinderHub (Question for clarification: Does or how does this JupyterHub chart differ from the released JupyterHub helm chart?)

the following snippet in your config.yaml would be all that is needed to enable a binder service (dynamic image building) for your jupyterhub:

binderhub:
  enabled: true

Move binderhub documentation (binderhub repo) into Zero to JupyterHub documentation (z2jh repo)

add a new section: Activating the BinderHub Service
deprecate the existing Binderhub documentation with a redirection to the new section in z2jh documentation

Benefits

easier to have a release cadence for a public binderhub chart (similar to the release cadence of the more mature z2jh chart)
simplify maintenance through better encapsulation by treating binderhub as a service of jupyterhub
Simplified "one stop" documentation of Kubernetes based deployments of JupyterHub and BinderHub

Proposed timeline and actions

Timing: ZeroToJupyterHub Helm Chart 0.7 (next release)
Release of BinderHub 0.1 Helm Chart
Announce documentation changes and repo changes to Jupyter mailing list and binder-dev mailing list

I'll close this as we've had several informal discussions on BinderHub vs Z2JH and other decoupling.

@manics do we have a temperature of the room in terms of how people feel about this? I know it's been discussed a bunch of times but I'm not sure whether people are like "net positive" or "net negative" or "I'm not sure without more concrete proposals/data"?
I agree with @willingc's suggestion above that this issue probably warrants a more fleshed out proposal / discussion / decision before committing to doing this in our repositories. Maybe a next step is to create a proposal with more "meat on the bone" for discussion, or prototypes to play with, and then having a team discussion around it in a new issue.

@choldgraf I don't have a feeling. We've had several other related discussions though, so I thought I'd close this as I thought it was out of date. I'm happy for it to be re-opened though.

@manics @choldgraf Maybe transfer the issue to the team compass repo for further discussion in a meeting.


sample parameters file not downloading

In the sample given for automatic clustering in the phy website, there is a commandd to download the hybrid_10sec.prm file.
phy download hybrid_10sec.prm.
when i execute this command in the powershell of windows, i get an error as follows:
HTTPError: 404 Client Error: Not Found
I am using windows 10 and powershell in windows, python 3.4, phy 0.2.1

it seems that you have an extra dot at the end of the file: try removing it

Looking at the logs, someone has recently requested hyrbid_10sec.prm which is a typo. Can you check you've got the correct full filename?

i ran the command as given in the website, this is what i am getting:
it says that the file cannot be found at the website specified..

Can you try browse to that URL in your web browser? Have you got some sort of institutional proxy or firewall?
http://phy.cortexlab.net/data/samples/

yep that worked! thanks!! somehow my terminal is not able to point to that website..
Thanks @nippoo


Touch Issue on new iOS 3d Touch

Foremost thanks for this awesome work ....
Was working Perfect but seems issue on UITouch when it comes to devices with 3d Touch
On 3d Touch Devices when a touch is made,instead of

(void)draggableViewTouched:(CHDraggableView *)view

it gets detected as drag move, and also noticed few changes on its CGPoint too... Can't get what's the issue on with these devices ???

Try this.
Replace CHDraggableView with these below.
CHDraggableView.zip


mraa in Docker reports that user doesn't have access (when they do)

I'm running a Raspberry Pi 3B+ with Raspbian Stretch. This works fine (outside Docker):
Python 2.7.13 (default, Sep 26 2018, 18:42:22)
[GCC 6.3.0 20170516] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import mraa
>>> mraa.Led("led0")
<mraa.Led; proxy of <Swig Object of type 'mraa::Led *' at 0x76ad5470> >
>>>

I've got a Docker container in which I've also installed mraa as per https://github.com/intel-iot-devkit/mraa/pull/928. I'm running the container with:
docker run -it -P --privileged -v /sys:/sys bash
When I try to run mraa (as root), I get the following:
Python 2.7.13 (default, Sep 26 2018, 18:42:22)
[GCC 6.3.0 20170516] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import mraa
libmraa[167]: libmraa version v2.0.0-10-gb425c99 initialised by user 'root' with EUID 0
libmraa[167]: gpio: platform doesn't support chardev, falling back to sysfs
libmraa[167]: libmraa initialised for platform 'Raspberry Pi 3 Model B+' of type 5
>>> mraa.Led("led0")
libmraa[167]: led: init: current user don't have access rights for using LED led0

This stumped me for a bit, until I noticed that the LEDs were indeed controllable. So is mraa incorrectly determining permissions?

@Mani-Sadhasivam Any clue whats going on there :/
https://github.com/intel-iot-devkit/mraa/blob/master/src/led/led.c#L163

If I have some time I can compile in debug and see which condition it's failing. Within the container I can still write manually to the led device (via /sys) so I'm not sure why stat would fail.

I always get this on the UP2 too when running as non-root even if the user has write permission to the LED classes.


Handling corrupted data

We had incidents of corrupted data, most probably due to network failure during job entry into queue.  It cut off the job string data about half way.  This resulted in getting the Pheanstalk_Exception_ClientException when CRLF wasn't the last character in the data.
This should be handled at the parser level, as it is still reserving the job, but we don't have a job id to handle this exception gracefully.  A parser should initiate the first line as "job meta data parser" and then do the data part as "job data parser".  Thereby providing the job id of a successful reservation for example.
Please note the issue I'm talking about is Connection::dispatchCommand function.

@airknights is this issue still relevant?
I'm thinking that if the data got corrupted when entering it into the queue, it is beanstalks responsibility.
If our connection to beanstalk fails when retrieving the data then that's another thing.

We've seen this often and there's some correlation between unplanned system reboots / beanstalk crashes. We have to telnet into beanstalkd and delete the offending job. Not sure how other clients handle this error, but pheanstalk should probably deal with it gracefully.

Are you guys using persistent connections? If so, please turn try to reproduce without persistent connections enabled.

On the servers we've seen this issue in, we've used pheanstalk in our long-running workers with persistent set to off.

This is old issue and is no longer relevant to me.
On Thu, Aug 30, 2018, 7:18 PM Gopi<EMAIL_ADDRESS>wrote:

On the servers we've seen this issue in, we've used pheanstalk in our
long-running workers with persistent set to off.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pda/pheanstalk/issues/111#issuecomment-417357692, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEzOMt0eKIuhh9CcRr5xUhpHGplb9qKOks5uWAI5gaJpZM4EWm-r
.

@gopi-ar when was the last time you saw this?
If it was a long time ago I'd prefer to close this issue for now.


Store Az Service Bus ConnectionString in Kubernetes

For demonstration purpose. IRL we would use Workload Identity

There is now an Action for that


Codepen linked in the issue template does not work

Issue description
ISSUE_TEMPLATE.md has a link to https://codepen.io/TheSharpieOne/pen/GMMPEZ but that pen does not work.
What is happening?
Codepen does not render anything because loading Reactstrap fails.
What should be happening?
Codepen should render some stuff.
Steps to reproduce issue

Go to https://codepen.io/TheSharpieOne/pen/GMMPEZ
Observe the output panel

Error message in console
Chrome Version 68.0.3409.2 (Official Build) dev (64-bit)
reactstrap.full.min.js:1 Failed to load resource: the server responded with a status of 404 ()
index.html:1 Refused to execute script from<EMAIL_ADDRESS>because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled.
pen.js:38 Uncaught ReferenceError: Reactstrap is not defined
    at pen.js:38

fixed in bfb8cc5


Checkout with shipping methods

Features

shipping method can be defined per country or for all countries in dashboard,
simplified checkout structure, we decide not to use processor manager for checkout,
fixes #443.
bootstrap panels used for addresses form:
,
address auto complete fix.

As we agreed we need introduce some strategy for functional tests, we need fixtures or helpers which will allow us work with django client easily and eliminate tests dependencies.

Can you fix it for Python 3?

Current coverage is 47.73%

Merging #449 into master will decrease coverage by -2.79% as of a3dc927

@@            master    #449   diff @@
======================================
  Files           83      88     +5
  Stmts         3499    3515    +16
  Branches       332     320    -12
  Methods          0       0
======================================
- Hit           1768    1678    -90
+ Partial         34      18    -16
- Missed        1697    1819   +122

Review entire Coverage Diff as of a3dc927

Powered by Codecov. Updated on successful CI builds.


XML not well formed: parseString callback is called twice

var xml2js = require('xml2js');
var fs = require('fs');

fs.readFile('testFile', 'utf-8', function(err, fileContent) {
  var parser = new xml2js.Parser();
  console.log("before");
  parser.parseString(fileContent, function(err, results) {
    console.log('after');
    console.log(results);
  });
});

testFile Content: ( test2 is not well formed )
<test>
    <test2 type="3">
    /test2>
</test>

Output:
malletjo$ node test
before
after
undefined
after
{ test2: { '#': '/test2>', '@': { type: '3' } } }
===========================================
As you see, "after" is called twice. So this result in really weird behavior
================== Version ==================
malletjo$ node -v
v0.4.11
malletjo$npm list
...
└─┬<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

maybe this is "normal" .. because no validation is made and the parser need a well formed xml to work.

And even if, the issue looks to me like a parser-problem, therefore a problem with sax-js.

From isaacs/sax-js:
"An XML Validator - It does a little validation when in strict mode, but not much."
And i checked your code and you set "strict mode" to true.
So one solution is used another program like xmllint or xerces before processing it, if we need to validate the XML


headscale: 0.13.0 -> 0.14.0

Motivation for this change
Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable: (n/a, no tests discovered)

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking - n/a
[ ] (Module updates) Added a release notes entry if the change is significant - n/a
[ ] (Module addition) Added a release notes entry if adding a new NixOS module -n/a
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes - n/a

[x] Fits CONTRIBUTING.md.

cc @NKJe @06kellyjac @kradalby @kalbasit as maintainers
Note: there's a beta of 0.15.0 available right now, soon we might have to do another update.

0.15.0 Will have a bit more changes so I anticipate that to still be a few weeks.

duplicate of #161702

Closing in favor of #161702


integrate Composer gRPC Collector with messenger rollup

We introduced the gRPC collector for Composer in https://github.com/astriaorg/astria/pull/784
We are integrating gRPC collector with the messenger rollup where we can send the txs of messenger rollup to the gRPC collector rather than directly to the sequencer. This is useful for us to have better nonce management.
I will be testing it against Dusk-4

Just some nits around logging and removing unused code. Looks good.
My only question is whether we want to add a test against a mock of the composer to this? My intuition says that's not very useful, but maybe?

I m actually adding composer to the local stack which Josh Dechant has built. I ll add it to that and then test it against it.


May 29th 2024, Community Meeting Agenda

📞 Dapr Community Meeting
Every two weeks we host a community meeting to highlight community created content, showcase new features, review upcoming milestones, and engage in Q&A with the Dapr community - all are welcome, and we encourage participation.
The purpose of this thread is to form a discussion amongst the Dapr community on potential topics to highlight during the meeting. If you have a topic you wish to present or learn more about, please comment and be sure to include your name and a short description of the topic.

The conversations in this thread will directly influence the meeting agenda for the community call on , at 9 AM PST (See it in your local time). The meeting agenda is finalized by a Community Call Host prior to the meeting.
See you at the community call! 👋
Agenda

Introduction
Session 1: TBD
Session 2: TBD
Dapr news / Show & tell
Open discussion
Closing

Checklists for the host
Before the meeting

[ ] Find speakers
[ ] Collect Dapr news (blog posts & videos found on social media, and show-and-tell Discord channel)
[ ] Prepare slide deck
[ ] Send meeting invite to the speakers
[ ] Announce the meeting on social media

[ ] 1 week before
[ ] 1 day before
[ ] 1 hour before

During the meeting

Welcome & announce that the meeting will be recorded
Start the recording
Show the agenda
Welcome first speaker
First session
Q&A first session
Welcome second speaker
Second session
Q&A second session
Show Dapr related news, posts, videos.
Open discussion
Closing & mention Dapr Discord channel

After the meeting

[ ] Upload the meeting to YouTube
[ ] Add chapters to the video
[ ] Add links to the video description

[ ] Read-only link to slides
[ ] Dapr Discord link
[ ] Other relevant links related to the sessions

[ ] Announce the published video on social media
[ ] Close this issue

Would like to present Azure IoT Operations and the Dapr pluggable components for state store and pubsub that have been created.

I'd like to present outbox payload projections coming to 1.14

Thanks @yaron2 and @ryanwinter, I'll send an calendar invite soon. @ryanwinter are you on the Dapr Discord? Can you DM me there so I can get your contact details?

https://youtube.com/live/3MYn_7jXypA?feature=share


feat: Add disableDeviceManufacturerInformation prop

feat: Add disableDeviceManufacturerInformation prop
Hide DeviceInfo if all sections are disabled

Could you add screenshots that illustrate what the prop changes?

I don't think we need to get so granular with these flags. i wanted the whole device info / details section to get hidden, instead of these granular row by row flags.

Could you add screenshots that illustrate what the prop changes?

@dawnho The storybook for this branch will let you see all the different component states: https://react-hsmbsz7gy.seam.vc/?path=/docs/components-devicedetails--docs


Fix set output

Per this GH depreciation notice update the build action to use the new method
I added a test tag build step for ACARS Hub and to enable any PR testing we use to build/push a test container (already in master), so this adds a test step for it.

Mike, I think I mostly have this working. Would be nice to have someone else look over the diff and make sure I didn't mess up the naming of any variables. Also, the test of the build_test I added doesn't seem to work. I'm not sure if that's me being thick and having the test in the wrong spot, or if I've messed up adding in the build_test tag.

I've reviewed your diff and there doesn't appear to be any typos - good job mate. We can troubleshoot the build_test workflow separately - merging this will stop all the warnings. :)


feat(pypi): update release workflow to use OIDC auth

What
Update the "PyPi publishing" workflow to use OIDC authentication instead of personal-token.
Why
This removes the need of storing a secret with PYPI_TOKEN_PYVESPA in it by using the Trusted publishing feature offered by PyPi.

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Set to Draft as it requires adding the pypa/gh-action-pypi-publish action to the allow list.

We should also do this for vespacli

pypa/gh-action-pypi-publish has been approved.
I will update also vespacli workflow.


Create a health check API request route

Add the following request to the API:
GET /api/_health
It should return the following:

Status code 200
The text 'OK'

It is common for REST APIs to have a health check request. This is commonly used to check if a server API is up and running. By returning 200, we can be confident that it is.

@Nithinss1 do this one first after issues https://github.com/Nithinss1/Album-Crud/issues/1 and https://github.com/Nithinss1/Album-Crud/issues/3


Breaking change in patch release

v0.4.20 went out with #76 in it which contained a breaking change.
It should have gone out as v0.5.0.
ipld-git is currently broken as it depends on ~0.4.14 of this module and accesses the defaultLengths property from /src/constants.
Please can you re-release 0.4.19 as 0.4.21 then release 0.4.20 as 0.5.0.

Done