Merge master to bootstrap to deploy ez_setup.py to https://bootstrap.pypa.io/ez_setup.py

I assume ez_setup.py is the only file that matters and that other changes don't matter.
Not sure if there's a better way to do this.

My internet is terrible and I don't have access even to a web browser. If someone can merge this PR or otherwise fast forward the bootstrap branch to master, that should fix the issue. Otherwise, it will be a few hours before I can invoke the change.
Sent from my comm
On Apr 25, 2016, at 18:21, Jim Fulton <notifications<EMAIL_ADDRESS>wrote:
I assume ez_setup.py is the only file that matters and that other changes don't matter.
Not sure if there's a better way to do this.

You can view, comment on, or merge this pull request online at:
https://github.com/pypa/setuptools/pull/560
Commit Summary

Get VersionConflict from pkg_resources.
Added tag 19.4 for changeset f47f3671508b
Bumped to 19.5 in preparation for next release.
Make 19.4 same level header as other version numbers.
Make all headers on the same level in CHANGES.txt.
Invoke import on importlib.machinery directly. Access an attribute to force import in delayed-import environments. Fixes #487.
Merged in svetlyak40wt/setuptools/svetlyak40wt/make-194-same-level-header-as-other-vers-1453106898145 (pull request #171)
Bumped to 19.4.1 in preparation for next release.
Added tag 19.4.1 for changeset 0bda3291ac72
Extract variable for candidate encodings
Add test capturing failure. Ref #486.
Avoid TypeError when getfilesystemencoding returns None. Fixes #486.
Relicense the package as MIT license. Drop licensing as PSF and Zope as neither of those licenses grant authority for use outside their respective projects. Vendored projects are licensed under their respective licenses, currently MIT for six and Apache v2 for packaging. Fixes #132.
Update changelog.
Merged in darjus/setuptools (pull request #169)
Update changelog
Bumped to 19.5 in preparation for next release.
Added tag 19.5 for changeset 0a68cbab7258
Bumped to 19.6 in preparation for next release.
Add 'launch' hook, based on pip.utils.setuptools_build
Also hide Cython when hiding setuptools, as setuptools will have imported Cython and Cython references the distutils.Extension. Fixes #488.
Added tag 19.6b1 for changeset 34121bf49b1a
Added tag 19.6 for changeset 3c2332e4ec72
Bumped to 19.7 in preparation for next release.
Rather than re-use globals of setuptools.launch, build a unique namespace in which to launch the script. Prevents imports from occuring relative to 'setuptools' on Python 2. Ref #490.
Combine redundant imports of future functionality
Pull up DefaultProvider registration into a classmethod.
Adapt resolution of classes from importlib.machinery. Restores compatibility for PyPy3 where importlib.machinery exists but FileFinder and SourceFileLoader aren't implemented.
Test on pypy3
Update changelog
Merge pull request #31 from Ivoz/patch-1
Allow failures with pypy3 for now
Bumped to 19.6.1 in preparation for next release.
Added tag 19.6.1 for changeset 35d9179d0439
Bumped to 19.6.2 in preparation for next release.
Extract function _rebuild_mod_path
Rename inner function and add docstring
Normalize all paths, not excluding ''. Fixes #491.
Update changelog
Added tag 19.6.2 for changeset d2782cbb2f15
Bumped to 19.6.3 in preparation for next release.
Extract variable for template string
Use new style string formatting
FreeBSD: Add root certificate from ca_root_nss.
Merge pull request #32 from silenius/master
Update changelog
Bumped to 19.7 in preparation for next release.
Added tag 19.7 for changeset c6e619ce910d
Bumped to 19.8 in preparation for next release.
Rewrite setup/teardown methods as pytest fixtures, encapsulating concepts for clarity. Incidentally, this also fixes #231.
Use py.path objects for cleaner setup
Extract variable for readability
Use py.path objects for cleaner setup
Use consistent numbering for clarity.
Extract ns_str as class attribute
Remove unused imports
Backout changeset 1ae2a75724bbba56373784f185a7f235ed0f24a4
Merge backout of 1ae2a75724bb; fixes #118.
Bumped to 20.0 in preparation for next release.
Fix syntax errors on Python 2
Fix failing tests on Python 2
Added tag 20.0 for changeset 2a60daeff0cd
Bumped to 20.1 in preparation for next release.
Switch back to SyntaxError for invalid markers, stops consumers having to import packaging themselves
Update to packaging 16.1
Correct tests after the move to packaging 16.1.
Replace upload docs with a reference to distutils docs, as
Override upload command to load passwords from keyring when available and not otherwise specified.
Added tag 20.1 for changeset 06c9d3ffae80
Bumped to 20.2 in preparation for next release.
Remove unused import
Upload_docs should also resolve passwords from keyring same as upload command.
Bumped to 20.1.1 in preparation for next release.
Added tag 20.1.1 for changeset 919a40f18431
Bumped to 20.1.2 in preparation for next release.
Correct syntax in changelog
Merge from master, resolving conflicts.
Correct tests under both Python 2 and 3.
Use io module and text type in install_site_py
Use pytest tmpdir fixture for simplicity and clarity.
Remove unused imports
Fix typo, correcting failures on late Pythons when mock is not already installed.
Update changelog
Add hyperlinks to PEPs in changelog.
Add timestamps to changelog.
Remove explicit PEP links now that the linker handles it.
Update changelog
Merge pull request series from Steve Kowalik for updated and unified marker implementation. Fixes #122.
Bumped to 20.2 in preparation for next release.
Added tag 20.2 for changeset 74c4ffbe1f39
Bumped to 20.3 in preparation for next release.
Update changelog to reflect new findings.
Add test capturing previously allowed usage. Ref #499.
Update to packaging 16.4. Fixes #499.
Update changelog
Bumped to 20.2.1 in preparation for next release.
Added tag 20.2.1 for changeset 1aacb05fbdfe
Bumped to 20.2.2 in preparation for next release.
Add test capturing expectation that spaces between version specifiers should be allowed. Ref #502.
Replace makefile with pavement file, granting portability on OS X and Windows. Fixes #505.
Re-run vendoring on packaging 16.4 (adding utils.py module, apparently omitted).
Bump vendored packaging to 16.5. Fixes #502.
Update changelog
Ignore pavement.py
Added tag 20.2.2 for changeset 48aa5271ef1c
Bumped to 20.2.3 in preparation for next release.
Shift requirement parsing inside Requirement
Change pkg_resources.Requirement to be a subclass of packaging
Add in safe_name for project_name, which disappeared in my refactor.
Add in a test that checks comparsion of Requirement with markers
Update changelog
Bumped to 20.3 in preparation for next release.
Added tag 20.3 for changeset 9c55a3a1268a
Bumped to 20.4 in preparation for next release.
Remove the import hook when unloading the old pkg_resources modules
Remove CVS and Subversion references in include_package_data docs
Safer way to remove the import hook
Update documentation for Requirement.
Merged in agronholm/setuptools/agronholm/remove-the-import-hook-when-unloading-th-1458177009332 (pull request #182)
Update changelog
Merged in stevenk_/setuptools (pull request #184)
Update changelog
Bumped to 20.3.1 in preparation for next release.
Added tag 20.3.1 for changeset 3e87e975a95c
Bumped to 20.3.2 in preparation for next release.
Point towards SCM plugins for including source files
Merged in koterpillar/setuptools (pull request #183)
Rename variables for clarity and easier troubleshooting (avoid masking intermediate 'parts' value).
Support environment markers in *_requires, via WorkingSet.
Extract decision point into a variable
Update vendored packaging to 16.6
Update most bitbucket references to point to Github now. Fixes #422.
Bumped to 20.4 in preparation for next release.
Added tag 20.4 for changeset 06692c64fb9b
Bumped to 20.5 in preparation for next release.
Use jaraco.packaging 2.11 for better support for bookmarks and thus Git push targets.
Merge https://bitbucket.org/pypa/setuptools/pull-requests/185.
Just render the date and not the time of tagged releases in the changelog.
Added tag 20.5 for changeset f8174392e9e9
Bumped to 20.6 in preparation for next release.
Attempting a new streamlined, Travis-powered release process.
Follow semver to the letter for simplicity.
Added tag v20.6.0 for changeset 114f3dbc8a73
Bump version: 20.5.0 → 20.6.0
Add fallback version to enable egg_info bootstrap
Bump version: 20.6.0 → 20.6.1
Added tag v20.6.1 for changeset a3d4006688fe
Try setting Python version and all_branches: true per https://github.com/travis-ci/dpl/issues/166
Bump version: 20.6.1 → 20.6.2
Added tag v20.6.2 for changeset<PHONE_NUMBER>60
Took a chance on 'env:' and lost
Bump version: 20.6.2 → 20.6.3
Added tag v20.6.3 for changeset 8b46dc41cb23
Ignore doc building during release; rely on separate dpl step.
Bump version: 20.6.3 → 20.6.4
Added tag v20.6.4 for changeset 7258be20fe93
Logic in upload_docs will only trigger docs build if no docs dir was specified, so explicitly build during release. Fixes #524.
Added tag v20.6.5 for changeset 7e0ab283db4e
Bump version: 20.6.4 → 20.6.5
Don't test the bootstrap script. It fails when deploys are happening, which is common when releases are being made.
Recognize semver versions with v prefix in rst.linker config
Merge pull request #522 from s-t-e-v-e-n-k/update-packaging
Update changelog
Update tags for rebase to 'distribute' branch (Mercurial)
Merge distribute tag updates
Fix error in docs build
Added tag v20.6.6 for changeset 57d63b38e855
Bump version: 20.6.5 → 20.6.6
Ensure sphinx is present for building docs
Added tag v20.6.6 for changeset b04dbdd161d7
Remove unused imports
Bypass environment marker evaluation in requirements resolution. Ref #523.
Extract separate test for test_environment_markers in test_resources. Remove unused variable.
Added tag v20.6.7 for changeset 0804d30b6ead
Bump version: 20.6.6 → 20.6.7
Drop unused safe_repr function
Merge pull request #528 from s-t-e-v-e-n-k/drop-safe-repr
Rename CHANGES and README files for nicer rendering on Github.
Merge
Restore evaluating environment markers in WorkingSet
Merge pull request #530 from s-t-e-v-e-n-k/fix-extra-markers-requires
Update changelog
Added tag v20.6.8 for changeset a00910db03ec
Extract method for testing marker evaluation
Remove fallback value until there's something that explains or requires it.
Reinstate the or guard in WorkingSet._markers_pass
Stop comparing repr()'s in TestEntryPoint
This helps finding packages with bad utf
Merge pull request #532 from s-t-e-v-e-n-k/readd-exception-for-marker-eval
Extract _ReqExtras to encapsulate that functionality and decouple it from WorkingSet.
Adjust expectation that 'extra' is not in the marker evaluation if no extras demanded the requirement.
Rely on short-circuit in 'or' rather than building a separate iterable.
Merge pull request #533 from s-t-e-v-e-n-k/compare-ep-attributes
Trap additional exceptions. Fixes #536.
Update changelog
Merge pull request #537 from ri0t/patch-1
Instead of reasing a new exception, just augment the existing exception, avoiding any concerns about exception type, but still communicating the context necessary to trace the issue. Ref #537.
Bump version: 20.6.7 → 20.7.0
Added tag v20.7.0 for changeset 0262ab29fc24
Swap out hard tabs for spaces
Merge pull request #541 from alex/patch-1
Update rationale for the zip_safe flag
Merge pull request #542 from ncoghlan/patch-1
Update changelog. Fixes #543.
Bump version: 20.7.0 → 20.8.0
Added tag v20.8.0 for changeset 7f56b6f40de3
Always inject extra into the environment when evaluating markers. Fixes #544.
Bump version: 20.8.0 → 20.8.1
Added tag v20.8.1 for changeset 8cf9340669ae
Handle not-zip-safe egg (folder) deletion in rotate command
remove _markerlib from manifest
bump certifi to 2016.2.28
Merge pull request #547 from mindw/rm_markerlib_manifest
Merge pull request #545 from totoroliu/master
Merge pull request #548 from mindw/bump_certifi_version
update changelog
Bump version: 20.8.1 → 20.9.0
Added tag v20.9.0 for changeset 8bf8aaa139bb
Limit deploys to Python 3.5 and only the standard run. Ref #549.
Preserve order of egg_info section in setup.cfg
Use OrderedDict to retain deterministic ordering of version info in egg_info command. Remove lexicographic ordering in setopt.edit_config. Ref #553
Remove unused import
Dedent
Remove superfluous slice
Extract method for validating the order.
Move Python 2.6 exception into specific test, capturing that the expected order is different on Python 2.6, not because of the lack of OrderedDict, but because of different behavior in RawConfigParser. Ref #553.
It's not necessary to build a file with an empty egg_info.
Add docstrings explaining the intention of the test. Ref #553.
Update changelog. Closes #553.
Correction for expected dict order when PYTHONHASHSEED=0
Support pypy3 also
Prompt for password on upload.
Update packaging to 16.7
Merge pull request #556 from gsnedders/packaging_167
Update changelog
Merge pull request #555 from brookskindle/dev_prompt_password
Update changelog
Move import to header
Add carriage return for symmetry
Simplify logic by eliminating retries in password prompt and returning results directly.
Added tag v20.10.0 for changeset 98779f519092
Bump version: 20.9.0 → 20.10.0
Added tag v20.10.0 for changeset c72faa468919
Merge
Try comparing eq
Bump version: 20.10.0 → 20.10.1
Added tag v20.10.1 for changeset 3b5fdd077c7d
Fix setuptools url and curl wants --location to follow redirects
restore previous fix that was never deployed.
Merge pull request #559 from buildout/master

File Changes

M .gitignorehttps://github.com/pypa/setuptools/pull/560/files#diff-0 (1)
M .hgignorehttps://github.com/pypa/setuptools/pull/560/files#diff-1 (1)
M .hgtagshttps://github.com/pypa/setuptools/pull/560/files#diff-2 (130)
M .travis.ymlhttps://github.com/pypa/setuptools/pull/560/files#diff-3 (16)
R CHANGES.rsthttps://github.com/pypa/setuptools/pull/560/files#diff-4 (523)
M MANIFEST.inhttps://github.com/pypa/setuptools/pull/560/files#diff-5 (2)
D Makefilehttps://github.com/pypa/setuptools/pull/560/files#diff-6 (7)
R README.rsthttps://github.com/pypa/setuptools/pull/560/files#diff-7 (4)
D _markerlib/init.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-8 (16)
D _markerlib/markers.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-9 (119)
M docs/conf.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-10 (16)
M docs/developer-guide.txthttps://github.com/pypa/setuptools/pull/560/files#diff-11 (36)
M docs/history.txthttps://github.com/pypa/setuptools/pull/560/files#diff-12 (2)
M docs/pkg_resources.txthttps://github.com/pypa/setuptools/pull/560/files#diff-13 (27)
M docs/releases.txthttps://github.com/pypa/setuptools/pull/560/files#diff-14 (27)
M docs/setuptools.txthttps://github.com/pypa/setuptools/pull/560/files#diff-15 (162)
M ez_setup.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-16 (6)
A pavement.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-17 (28)
M pkg_resources/init.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-18 (501)
M pkg_resources/_vendor/packaging/about.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-19 (24)
M pkg_resources/_vendor/packaging/init.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-20 (16)
M pkg_resources/_vendor/packaging/_compat.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-21 (16)
M pkg_resources/_vendor/packaging/_structures.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-22 (16)
A pkg_resources/_vendor/packaging/markers.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-23 (287)
A pkg_resources/_vendor/packaging/requirements.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-24 (127)
M pkg_resources/_vendor/packaging/specifiers.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-25 (66)
A pkg_resources/_vendor/packaging/utils.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-26 (14)
M pkg_resources/_vendor/packaging/version.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-27 (16)
A pkg_resources/_vendor/pyparsing.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-28 (3805)
A pkg_resources/_vendor/six.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-29 (868)
M pkg_resources/_vendor/vendored.txthttps://github.com/pypa/setuptools/pull/560/files#diff-30 (4)
M pkg_resources/api_tests.txthttps://github.com/pypa/setuptools/pull/560/files#diff-31 (66)
A pkg_resources/extern/init.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-32 (71)
M pkg_resources/tests/test_markers.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-33 (16)
M pkg_resources/tests/test_pkg_resources.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-34 (2)
M pkg_resources/tests/test_resources.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-35 (303)
M pytest.inihttps://github.com/pypa/setuptools/pull/560/files#diff-36 (4)
D release.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-37 (20)
D scripts/upload-old-releases-as-zip.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-38 (242)
M setup.cfghttps://github.com/pypa/setuptools/pull/560/files#diff-39 (16)
M setup.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-40 (30)
M setuptools/init.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-41 (3)
M setuptools/command/init.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-42 (2)
M setuptools/command/alias.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-43 (2)
M setuptools/command/bdist_egg.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-44 (5)
M setuptools/command/build_py.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-45 (34)
M setuptools/command/develop.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-46 (5)
M setuptools/command/easy_install.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-47 (97)
M setuptools/command/egg_info.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-48 (36)
M setuptools/command/install.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-49 (2)
M setuptools/command/install_egg_info.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-50 (4)
M setuptools/command/rotate.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-51 (11)
M setuptools/command/sdist.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-52 (5)
M setuptools/command/setopt.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-53 (4)
M setuptools/command/test.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-54 (8)
A setuptools/command/upload.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-55 (38)
M setuptools/command/upload_docs.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-56 (21)
D setuptools/compat.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-57 (70)
M setuptools/depends.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-58 (6)
M setuptools/dist.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-59 (27)
M setuptools/extension.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-60 (2)
A setuptools/extern/init.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-61 (5)
A setuptools/launch.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-62 (35)
M setuptools/msvc9_support.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-63 (2)
M setuptools/package_index.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-64 (97)
M setuptools/py26compat.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-65 (5)
M setuptools/sandbox.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-66 (14)
M setuptools/ssl_support.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-67 (28)
M setuptools/tests/init.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-68 (4)
M setuptools/tests/contexts.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-69 (19)
A setuptools/tests/files.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-70 (32)
M setuptools/tests/server.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-71 (19)
M setuptools/tests/test_develop.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-72 (5)
M setuptools/tests/test_dist_info.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-73 (7)
M setuptools/tests/test_easy_install.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-74 (247)
M setuptools/tests/test_egg_info.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-75 (210)
M setuptools/tests/test_integration.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-76 (4)
D setuptools/tests/test_markerlib.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-77 (63)
M setuptools/tests/test_packageindex.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-78 (15)
M setuptools/tests/test_sdist.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-79 (24)
M setuptools/tests/test_setuptools.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-80 (2)
M setuptools/tests/test_test.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-81 (1)
A setuptools/tests/test_unicode_utils.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-82 (10)
M setuptools/unicode_utils.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-83 (12)
M setuptools/version.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-84 (7)
M tests/manual_test.pyhttps://github.com/pypa/setuptools/pull/560/files#diff-85 (11)

Patch Links:

https://github.com/pypa/setuptools/pull/560.patch
https://github.com/pypa/setuptools/pull/560.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHubhttps://github.com/pypa/setuptools/pull/560


Add License

Hey, this code currently does not have a license, can you please add one?

Hi!
Thank you for pointing out. I never thought that it would be used so I am glad that you can use it.

Thanks! Super useful.


chore(deps) Update webview-official

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] New Binding Issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[x] Other, please describe: Update webview dependency.

Does this PR introduce a breaking change? (check one)

[ ] Yes. Issue #___
[x] No

The PR fulfills these requirements:

[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

@wusyong can you add a change file here documenting the changes that this update applies? there's one on the .changes folder already so just copy that and change the description :)

@wusyong can you add a change file here documenting the changes that this update applies? there's one on the .changes folder already so just copy that and change the description :)


Generate to_latest in versioned types, where possible

In many cases, to_latest can be generated for versioned types.
As a simple example, if we have:
module V2 = struct
  type t = Foo.Stable.V7.t
end
module V1 = struct
  type t = Foo.Stable.V5.t
end

then V1.to_latest is Foo.Stable.V5.to_latest. The most recent version of any type must be using the most recent version of any types it refers to, so this is principled.
For records and sum types, we can extend this idea homomorphically, field-by-field or constructor-by-constructor.
If a new version elides record fields, then to_latest just deletes them. If a new version adds record fields, those should have option types, and to_latest yields None for those. If they're not option types, then fail.
If a new version elides constructors for sums, then to_latest fails when those constructors appear.
If it adds constructors, to_latest injects into the new type.
For the most recent version, to_latest is always the identity function, which can be generated.
If the most recent version has a different structure than an older version, then all bets are off, and to_latest will have to be added manually.

To extend this, if we have some way to specify 'default' values for fields, we can also automatically provide the coercion using those values<EMAIL_ADDRESS>expr] perhaps?

We should also generate of_latest. RPC queries from newer to older nodes need to "downgrade" the data.


Read tenant data from Airtable instead of Google Sheets

Steps

Get basic reading working
Add both prototype and production Airtable Base identifiers to column metadata.
Add column names to column metadata.

https://github.com/rupert-git/airtable-to-google-sheets/blob/master/google-apps-script.js


Deduplicate pagination functions in Editor and BrewRenderer

As per this comment on PR #2162, with the merging of that PR, the pagination function in the BrewRenderer will be duplicated in the Editor.
It should be possible to use React.cloneElement to add props to the this.props.children (as identified in this comment) being handled in SplitPane.jsx to pass a unified pagination function as a prop to both child elements.

I am not sure if the current toolbar even gives a third page navigation function. Should check.

Is this still an issue with the Intersection Observer?

I think this was handled somewhere around #3729 or #3484


OBM library functionality

Library should be able to send out CTA actions to the server. The flag that indicates if user is part of the experiment comes with /me request data. Exact details are described in backend repo obm doc.
obm actions endpoint:
POST toggl.com/api/v9/obm/actions
input is JSON:
 {"experiment_id": int, "key": string, "value": string}

All the values of this object come from UI

do the experiments need to be saved to local database? or can they be dropped when user is offline?

will save to db


Update searchSettings.html

Fixes #
Proposed Changes

Testing

@Virtual-Josh Andrew told me to @ you on this!


Ubuntu 22.04 support

This issue is to check development in Ubuntu 22.04, if any.
problems (if any)

[ ] clang-format-8 doesn't exist
[ ] ...

format checker doesn't use clang-format anymore. we can remove related codes.

build and execution in Ubuntu 22.04 is OK.


Update cron dependency

This PR updates the cron dependency of this project so it doesn't depend on the nightly compiler.

Ah! Thanks @NyxCode, I had not noticed cron had been updated to not need nightly anymore. That's great news!


Update to node 16 CRA 5 and UBI for Docker

Docker updated to use UBI
Dependencies updated
New CRA needed craco to deal with polyfills

closing in favor of PR to development #139


[firebase_auth_web] _fromJsUser and _fromJsUserInfo null safety

First, I'm posting a broader API design question that might make this bug relevant or not:
Is there a particular reason why _fromJsUser and _fromJsUserInfo are not considering whether the input parameter is null? There is a pretty obvious use case in which this is true, which I'll describe in the bug below.
Describe the bug
onAuthStateChange stream throws an uncaught error when user is not authenticated (firebase.User is null).
To Reproduce
Steps to reproduce the behavior:

Initialize at least one subscription to FirebaseAuth.instance.onAuthStateChanged stream.
Run the application on web platform (i.e. flutter run -d chrome)
In case the user is not authenticated or authentication status changes to that state, the console will output the following exception and your subscription(s) won't be triggered:

firebase_auth_web.dart:46 Uncaught (in promise) TypeError: Cannot read property 'providerId' of null
    at firebase_auth_web.FirebaseAuthWeb.new.[_fromJsUser] (firebase_auth_web.dart:46)
    at _MapStream.new.[_handleData] (stream_pipe.dart:229)
    at _ForwardingStreamSubscription.new.[_handleData] (stream_pipe.dart:166)
    at _RootZone.runUnaryGuarded (zone.dart:1316)
    at _BroadcastSubscription.new.[_sendData] (stream_impl.dart:338)
    at _BroadcastSubscription.new.[_add] (stream_impl.dart:265)
    at _SyncBroadcastStreamController.new.[_sendData] (broadcast_stream_controller.dart:377)
    at _SyncBroadcastStreamController.new.add (broadcast_stream_controller.dart:252)
    at auth.dart:307
    at Object._checkAndCall (operations.dart:326)
    at Object.dcall (operations.dart:331)
    at Object.ret [as next] (js_dart2js.dart:531)
    at subscribe.ts:104
    at subscribe.ts:233

Expected behavior
onAuthStateChanged stream should trigger another event with null as the value of the observed FirebaseUser parameter.
Additional context
I'll edit this if there is additional questions in the comments.
For now, here's flutter doctor and flutter --version:
$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, v1.12.13+hotfix.6, on Mac OS X 10.14.6 18G1012, locale en-RS)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.5)
[✓] VS Code (version 1.41.0)
[✓] Connected device (3 available)

• No issues found!
$ flutter --version
Flutter 1.12.13+hotfix.6 • channel beta • https://github.com/flutter/flutter.git
Framework • revision 18cd7a3601 (9 days ago) • 2019-12-11 06:35:39 -0800
Engine • revision 2994f7e1e6
Tools • Dart 2.7.0

EDIT1: Here's the relevant line that's calling the _fromJsUser with null input param.

Seeing the same. Here's the simple fix I'm using for _fromJsUser https://github.com/muhleder/flutterfire/commit/fbf9760f8464b1b95438a39793f58437b9335648

Hello Mark,
Thanks for the feedback. Yeah, quickfix is quite trivial and obvious. I'd like to know if there was any API design decision about not allowing null values. But if there was, it's in contradiction with the design of onAuthStateChanged subscription, since it has a pretty much regular case of emitting null whenever the user is in a non authenticated state.
I guess we'll wait for one of the maintainers to see which one is going to be changed and in the meantime use the quickfix you mentioned.

Tagging code owners @collinjackson @kroikie to get their input.

Encountering the same bug here. This makes the entire onAuthStateChanged API unusable on the web.

I have the same problem
firebase_auth_web.dart:46 Uncaught (in promise) TypeError: Cannot read property 'providerId' of null
    at firebase_auth_web.FirebaseAuthWeb.new.[_fromJsUser] (firebase_auth_web.dart:46)
    at _MapStream.new.[_handleData] (stream_pipe.dart:229)
    at _ForwardingStreamSubscription.new.[_handleData] (stream_pipe.dart:166)
    at _RootZone.runUnaryGuarded (zone.dart:1316)
    at _BroadcastSubscription.new.[_sendData] (stream_impl.dart:339)
    at _BroadcastSubscription.new.[_add] (stream_impl.dart:266)
    at _SyncBroadcastStreamController.new.[_sendData] (broadcast_stream_controller.dart:377)
    at _SyncBroadcastStreamController.new.add (broadcast_stream_controller.dart:252)
    at auth.dart:307
    at Object._checkAndCall (operations.dart:326)
    at Object.dcall (operations.dart:331)
    at ret (js_dart2js.dart:531)
    at auth.js:1457

Thanks everyone for your patience here.
Tagging @ditman @hterkelsen who have been driving things forward on the web site.
I think the fix in https://github.com/muhleder/flutterfire/commit/fbf9760f8464b1b95438a39793f58437b9335648 is a reasonable one and will put that up as a PR.

Yep, we need the above sanity check.
I checked the documentation, and even though it doesn't state that user may be null directly, theres an if (user) { check that should have given us a clue.
(currentUser however, does specify that may be null).
@collinjackson do we wait for @muhleder's fix, or should we push a quick change?

We should fix it, if you want to put up a PR I'm happy to LGTM it

Ah, I remember. The null check should be performed before calling the _fromJsUser method, but it isn't.
See the MethodChannel implementation vs the Web implementation.
@collinjackson I'll put up a PR quickly, will follow up via chat.

providerData seems to not be nullable, so no need to harden _fromJsUserInfo, apparently.

Posted CR, took me a while to write the test 😅

Thanks for fixing it.
By the way (although this is quite off-topic) two of my clients are evaluating web approach with Flutter and their point of view, with which I agree, is that while the build system and Flutter framework itself is quite stable, the ecosystem is far from it. This includes Firebase which is semi-first-party library.
Having written that, I'd love to make some contribution for the web support rather than pointing fingers, although ironically, JavaScript is my weakest suit. I came into Flutter from native mobile app development. But, if I find enough time, I'll open at least a couple of PRs before summer.

@nstosic-toptal thanks for offering to contribute! looking forward to your PRs


fix(docz-theme-default): use local vendors

Fix: #351
Styles are not being extracted by default so it's not required a new css import in the generated template, is this ok?

I don't like so much the idea of put some vendors scripts hardcoded in the base, we'll need to change this scripts in each package update manually. Maybe add then as dependency and import can be a better way.

Good point, fixed!


E [FATAL] Error (exec): no such file or directory

Hi.
I've experimented creating and installing the following Oz profile for Wire:
{
"path": "/opt/wire-desktop/wire-desktop"
, "xserver": {
	"enabled": true
	, "tray_icon":"/usr/share/icons/hicolor/256x256/apps/wire-desktop.png"
	, "enable_tray": false
	, "enable_notifications": true
}
, "networking":{
	"type":"empty"
	, "sockets": [
		{"type":"client", "proto":"tcp", "port":9050}
	]
}
, "whitelist": [
	{"path":"${HOME}/.config/Wire", "can_create": true}
	, {"path": "/opt/wire-desktop", "read_only": true}
]
, "blacklist": [
]
, "environment": [
]
, "seccomp": {
	"mode":"blacklist"
	, "enforce": true
}
}

It was successfully installed:
user@subgraph:~$ sudo oz-setup status wire-desktop
Package divert is installed for:     /opt/wire-desktop/wire-desktop
user@subgraph:~$

But when I try running it, it does not launch and I get this using sudo journalctl -f:
Oct 29 19:18:52 subgraph oz-daemon[25328]: 2017/10/29 19:18:52 [wire-desktop] (stderr) E [FATAL] Error (exec): no such file or directory /opt/wire-desktop-oz/wire-desktop

Though,
user@subgraph:~$ ls -l /opt/wire-desktop-oz/wire-desktop
-rwxr-xr-x 1 root root 83393032 Oct 10 15:36 /opt/wire-desktop-oz/wire-desktop
user@subgraph:~$

How could I fix this?
Thanks!

Oz doesn't support opt this way. this is an open issue. Here's what I recommend you do:
have the oz profile point to /usr/bin/wire-desktop
/usr/bin/wire-desktop should be a symlink to /usr/bin/oz
In /usr/bin-oz/, create a symlink to /opt/wire-desktop-oz/wire-desktop
The rest is good (you've already added /opt/wire-desktop as a whitelisted path).
Let me know if this works.

Hello dma,
It worked, the application has been launched in a sandbox. Though, upon launching the application says it has no internet access. Do you know why that would be the case? After all, I've copied the networking settings straight out of Coyim's.
Thanks.

I have a similar issue.  The application is signal-desktop.  I install it by adding an additional apt repository as instructed on signal.org's website, the Signal for Debian-based Linux.  After that it couldn't run until I set a paxrat config for signal-desktop, which is fine.  Then, I tried to sandbox it.  Even though signal-desktop is installed under /opt/Signal/, but, it also has a link from /usr/local/bin, so, I could just use oz-setup to install it.  Here is my config file (/var/lib/oz/cells.d/signal-desktop.json).  Notice the "networking" section which I use "host" instead of "empty" with "sockets" like this:
, "networking":{
  "type":"empty"
  , "sockets": [
    {"type":"client", "proto":"tcp", "port":9050}
  ]
}

Using "host" as the "networking" works.  Signal can be run in a sandbox with Internet access.  But, if I use "empty, sockets, client, tcp, 9050", it has no Internet access.
What are the consequences of using "host"?  From my understanding, Signal with "host" setting still accesses the Internet through Tor like any other applications e.g. w3m, (but not chromium which has a special configuration to use direct access), right?  Do all applications either command line or gui access the Internet through Tor?  If so, then the consequence of me using "host" for now is that if there is a malicious code in signal-desktop, then my host's network can be attacked directly, right?
Thank you very much.


Use linear encoder for tow axis feedback

Currently it is only used for measurement, but could help smooth out the motion a bit.

Probably going to give this a try soon to eliminate turbine-induced oscillation. I have a feeling the drive will go unstable though.

Linear encoder is connected to X1 connector. Set lines per rev to 8000. This implies 10 micrometer per line, as one motor rev is 0.08 m.  This seems incorrect. Tried to move 0.1 m at 0.1 m/s, and carriage ended up taking off at about 1 m/s. Set EXTPOS to 30, ROD (A QUAD B) Enc 5V (digital).
Positioning seems to be off by a factor of 4. Setting lines per rev to 2000 corrected this, but Kp_p=0.01 caused instability. Kp_p=0.001 fixed instability, but there are still oscillations when moving.
Overall, it looks like the linear encoder may help for positioning accuracy, but not for belt resonance.


unbind/deprovision parses incoming service_id/plan_id parameters

The Services API has mandatory parameters for unbind/deprovision - this PR parses them and passes them into Unbind and Deprovision. Therefore it does extend the function signature for these two methods.

Bump

Also, I cannot see the tracker URL - its not public.

Thanks @drnic, and sorry this took so long to merge in!
The codebases have diverged significantly since you made this PR, so we had to make quite a detailed merge commit. I'm sure we preserved the intention of your original commit though.


checkLocationWorkerRoute not working

When I followed the wiki to configure everything, everything was fine until yesterday when it started returning Error initiating check from remote worker errors. I checked the worker logs and the following is the log content:
    {
      "message": [
        "[SLC] Checking NAS 服務..."
      ],
      "level": "log",
      "timestamp":<PHONE_NUMBER>617
    },
    {
      "message": [
        "Calling worker: https://tw-cloudflare.snkms.com/"
      ],
      "level": "log",
      "timestamp":<PHONE_NUMBER>617
    },
    {
      "message": [
        "Error calling worker: SyntaxError: Unexpected token 'e', \"error code: 1002\" is not valid JSON"
      ],
      "level": "log",
      "timestamp":<PHONE_NUMBER>638
    },

tw-cloudflare subdomain is recorded through the proxied A to <IP_ADDRESS>
When I cancel checkLocationWorkerRoute, everything works fine except that I cannot use the location-specific functionality.

Hi, error 1002 means DNS points to a forbidden IP. It looks like you have chosen an IP address that is not reserved for workers. Perhaps you could try selecting a different IP address. (I'm not quite sure if Cloudflare offers Workers service in Taiwan... If you can't find an available IP, you may need to choose a neighboring region, e.g. Singapore / Japan / Korea)

Actually, I've been using it for about a week, and it just stopped working yesterday.
According to your suggestion, I switched the IP to the Japanese IP <IP_ADDRESS> mentioned in the wiki, and it started working.
I don't know why many of the IPs from Taiwan and Hong Kong that I've been testing have become invalid these past few days; it's really strange.
It might be that the IPs from Taiwan and Hong Kong no longer support Worker. I'm not sure; anyway, it works fine with a Japanese IP right now. If there are any issues, I'll reply again.

If it was available before and then suddenly became unavailable, it is possible that Cloudflare has made internal adjustments. In Taiwan and Hong Kong, due to higher bandwidth costs, Cloudflare may not have as many nodes deployed, and is more likely to have had some maintenance or changes.

I've tried following the wiki, but I also continuously getting 1002 error (forbidden ip).
I've downloaded a fresh list and gotten the ip's. Have anyone found a way to actually identifying which ip's is usable?
I've tried random ones for Germany. But no luck so far.


Detach $card-border-width and $card-border-color from card header and footer

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
Not sure if that's a bug or an improvement. Currently we have 2 component-level variables that are re-used in inner elements:
.card {
    border: var(--#{$prefix}card-border-width) solid var(--#{$prefix}card-border-color);
}
.card-header {
    border-bottom: var(--#{$prefix}card-border-width) solid var(--#{$prefix}card-border-color);
}
.card-footer {
    border-top: var(--#{$prefix}card-border-width) solid var(--#{$prefix}card-border-color);
}

If i need to remove or override card border by setting width or color values to null, i would expect the border to disappear only from main container, but not from header and footer.
Motivation and context
To be able to remove border from parent container and child elements separately

No plans to separate these—these feels like a solid convenience to include by default.


[9.x] Add famous quote by Benjamin Franklin

The most inspiring quote by Benjamin Franklin.


fix: engine: tasks could stay in inconsistent state when fails to validate templates

When a task fails to validate requirements of a template, task is set to
BLOCKED state, whereas resolution stayed in RUNNING state, making it
impossible for admins to manage the task anymore.
Switching resolution to a CRASHED state will allow manipulation by
admins.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Fixing a bug

What is the current behavior? (You can also link to an open issue here)
Task that failed to validate a template was in BLOCKED state with resolution in RUNNING state, couldn't be used in the API anymore.

What is the new behavior (if this is a feature change)?
Resolution in CRASHED state

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Other information:

CDS Report test#575.0 ✘

Stage 1

Test ✘


Escape user input in HTTP responses to avoid reflected XSS

Addresses a potential vulnerability found by CodeQL.

Directly writing user input (for example, an HTTP request parameter) to an HTTP response without properly sanitizing the input first, allows for a cross-site scripting vulnerability.
This kind of vulnerability is also called reflected cross-site scripting, to distinguish it from other types of cross-site scripting.
Recommendation
To guard against cross-site scripting, consider using contextual output encoding/escaping before writing user input to the response, or one of the other solutions that are mentioned in the references.
References

OWASP: XSS (Cross Site Scripting) Prevention Cheat Sheet.
OWASP: Types of Cross-Site Scripting.
Wikipedia: Cross-site scripting.
Common Weakness Enumeration: CWE-79.
Common Weakness Enumeration: CWE-116.

To be clear, this is not as bad as the report makes it look. Both affected services are webhooks (respectfully for SNS and Zendesk), meaning none of them is ever accessed through a web browser.
This commit merely implements what's commonly accepted as a best practice in order to make security scanners happy.


Fixed an incorrect description for "Branch" and "Build" link types.

@TemekRoman Thank you for your contribution, I am merging it now and it should be live soon.


Search button

Description of the new feature / enhancement
A button where you can search for features within PowerToys Settings
Scenario when this would be used?
Lets say you wanted to find "Peek" within the PowerToys, you could do that with the search bar
Supporting information
No response

/dup #8060


it's possible to create video from images with transition and effect?

Yes. It is totally possible. AVFoundation framework is your friend. You can create tracks representing the static images and use system provided or write custom (e.g. implement the AVVideoCompositing protocol) video compositor to do the transition.
Closing this issue, because the question is not directly related to this project.

Yes. I getting your point. but I really like your  transition effects(YUDisplacementTransition). And it is in imageview. how I convert your transition effects in images to video. Please help me.

Yes. I getting your point. but I really like your  transition effects(YUDisplacementTransition). And it is in UIImageview. how I convert your transition effects in images to video. Please help me.

The transition is not limited in UIImageViews, it works with MTIImages. (See the YUDisplacementTransition class)
You can create a MTIImage from a core video image buffer (CVPixelBuffer). You can also render a MTIImage to a CVPixelBuffer (using a MTIContext). So it can play well with the AVFoundation framework and the AVVideoCompositing protocol.
See MetalPetal for more information about MTIImage and MTIContext.

Ok, I'll try this thinks.. thanks for giving me help

Ok, I'll try this thinks.. thanks for giving me help..:)


develop weekly newsletter

Develop a weekly newsletter for sending random code snippets to subscribers.
https://app.leanboard.io/board/a7721e60-20e7-4352-b365-8bc725ed7c2a

i can help i am new but i will understand the code base and can then compose the letter because i used to this a lot in high school.  Assign me and you will not be dissappointed

and also just let me know how to post the letter here

Hi @manav1234 thanks for your interest
I think we could use service like MailChimp to send weekly emails.
We could agree on a Newsletter Template & whosoever wants to write one could raise an issue.
What do you think ?

sure sir let me know because my vacations will be going on and I am
extremely free
so if I want to write one can I create an issue and will I have to write
one every week or will I have to write the code to automate it
On Wed, Jun 26, 2019, 1:58 PM Bhupesh Varshney<EMAIL_ADDRESS>wrote:

Hi @manav1234 https://github.com/manav1234 thanks for your interest
I think we could use service like MailChimp to send weekly emails.
We could agree on a Newsletter Template & whosoever wants to write one
could raise an issue.
What do you think ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Bhupesh-V/30-seconds-of-cpp/issues/38?email_source=notifications&email_token=AEOERQI42W5WWONVPOJOW7TP4MSBLA5CNFSM4HHCK2H2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYSYKGQ#issuecomment-505775386,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEOERQLVLLLWBVB3L7HBUKLP4MSBLANCNFSM4HHCK2HQ
.

sorry wanted to say vacations are going on
On Wed, Jun 26, 2019, 2:04 PM Manav Sethi<EMAIL_ADDRESS>wrote:

sure sir let me know because my vacations will be going on and I am
extremely free
so if I want to write one can I create an issue and will I have to write
one every week or will I have to write the code to automate it
On Wed, Jun 26, 2019, 1:58 PM Bhupesh Varshney<EMAIL_ADDRESS>wrote:

Hi @manav1234 https://github.com/manav1234 thanks for your interest
I think we could use service like MailChimp to send weekly emails.
We could agree on a Newsletter Template & whosoever wants to write one
could raise an issue.
What do you think ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Bhupesh-V/30-seconds-of-cpp/issues/38?email_source=notifications&email_token=AEOERQI42W5WWONVPOJOW7TP4MSBLA5CNFSM4HHCK2H2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYSYKGQ#issuecomment-505775386,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEOERQLVLLLWBVB3L7HBUKLP4MSBLANCNFSM4HHCK2HQ
.

wanted to know if we had any funds to use a paid email service  for  the newsletter;

wanted to know if we had any funds to use a paid email service for the newsletter;

I guess we don't need any funding for sending weekly newsletters.
MailChimp is a free service.

so if I want to write one can I create an issue and will I have to write one every week or will I have to write the code to automate it

I will get back to you soon once i design the structure of the newsletter

surely sir will be waiting for it
also sir if its cleared please merge my prs

@Bhupesh-V Is this still on ?


Music volume

Is there a way to lower the volume of the music on the multicharacter screen?

Is there a way to lower the volume of the music on the multicharacter screen?

You can change that in the script.js


Pod assign loop too short for micro instances

Version

Karpenter: v0.5.1

Kubernetes: v1.21
Expected Behavior
I just had a situation in which I deployed a Provisioner with no instance type requirements, letting it choose from all of them. When deploying my first pod, a t3a.micro instance was launched. Cool! I expected the pod to be assigned to the node, it eventually start up and join the cluster, and the pod start.
Actual Behavior
About a minute after the instance is launched and the pod is assigned to the node, a new node is launched and the pod is assigned to the new node. Since t3a.micro instances are small and very low-powered, they take 70-90 seconds to boot, join the cluster, and be ready for workloads. So, what ended up happening is I was in a bootloop and the pod never could get scheduled.
Steps to Reproduce the Problem
For simplicity, I'm going to use a Provisioner that uses only t3a.micro instances.

Create a Provisioner that uses only t3a.micro instances.
Deploy a pod.
Watch it start a new machine, but start another machine before the pod has actually started

Another question... should micro instances really be in the mix as they simply aren't big enough for any sort of workload... 🤷

Hmm -- this doesn't quite make sense to me. Can you include some logs? I just tried out micros for a single pod with no requests/limits and it worked fine. Are you using a custom launch template? Daemonsets?

Duplicate of #1034


Add controls to the heatmap example.

Move the example data set to data.kitware.com.
Allow selecting the cities and earthquake data sets.
Fix an issue with updating the radius or blurRadius on the fly (the circle wasn't being recomputed).
Fix an issue with changing the color gradient on the fly (the gradient wasn't being recomputed).

[Current coverage][cc-pull] is 72.79%

Merging [#577][cc-pull] into [master][cc-base-branch] will increase coverage by +<.01%

@@             master       #577   diff @@
==========================================
  Files            82         82
  Lines          7128       7131     +3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           5188       5191     +3
  Misses         1940       1940
  Partials          0          0

Powered by Codecov. Last updated by [b3e15f8...a8b3fd5][cc-compare]
[cc-base-branch]: https://codecov.io/gh/OpenGeoscience/geojs/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/OpenGeoscience/geojs/compare/b3e15f830c01a9b02456259519f31423cad4b510...a8b3fd5f30f19d27b2a49eea5ba0b5db15310fde
[cc-pull]: https://codecov.io/gh/OpenGeoscience/geojs/pull/577?src=pr

LGTM 👍


feat(level): add new attributes

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Pick 3 Bugs: Export CSV

pick 3 bugs for Export CSV from the Find Your Bugs doc
detail which 3 bugs you are fixing in the PR comments

/cib pick 3 bugs export csv

Branch 170-pick-3-bugs-export-csv created!

Fixed 3 bugs for Export CSV:
Bug #36: Export CSV: Boxes are not sorted chronologically**
Bug #16: Export CSV: All box details should be checked on page load
Bug #45: Export CSVView Launched Organically Checkmark isn’t Centered

** I'm not seeing/encountering the same chronology sorting issues as stated in the bug listing, and all other Sort By options function as intended, so for now I've placed it under "Not a Bug" on the Google Doc


Completed Storage functionality for Mark Unmark Tasks

Codecov Report

Merging #83 (ef4ec75) into master (7d2deb0) will decrease coverage by 0.22%.
The diff coverage is 44.44%.

@@             Coverage Diff              @@
##             master      #83      +/-   ##
============================================
- Coverage     63.93%   63.71%   -0.23%
  Complexity      417      417
============================================
  Files            84       84
  Lines          1442     1455      +13
  Branches        140      143       +3
============================================
+ Hits            922      927       +5
- Misses          477      482       +5
- Partials         43       46       +3

Impacted Files
Coverage Δ

src/main/java/manageezpz/model/task/Task.java
74.19% <0.00%> (-2.48%)
:arrow_down:

.../main/java/manageezpz/storage/JsonAdaptedTask.java
46.15% <47.05%> (-1.35%)
:arrow_down:

Continue to review full report at Codecov.

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


introduce semantic-release

https://www.npmjs.com/package/semantic-release

I'm not sure if semantic-release can do this but I really would love to auto-release after each successful pull-request.

Resolved by #48.


SQL translation improvements for 1.2

Translate the following to SQL rather than evaluating client-side:

Convert.ToInt32 and friends (https://github.com/aspnet/EntityFramework/pull/2633)
String.{StartsWith,EndsWith,Contains} translation needs to be improved not to use SQL LIKE, as per https://github.com/aspnet/entityframework/issues/474
String.Trim, String.IsNullOrWhitespace
Object.ToString()
DateTime part access

All of the above were done.


Update functional tests project to add target framework 3.1

Spotted that this project was not targetting 3.1 when resolving an issue with the functional test build with @BruceHaley

Pull Request Test Coverage Report for Build 104570

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.606%

Totals

Change from base Build 104413:
0.0%

Covered Lines:
10949

Relevant Lines:
13754

💛  - Coveralls

Oddly, this is failing in the Nuget Restore, with the following error code:
##[error]No neutral-language version resource found in the file

@cleemullins that is odd. I'll take a look.

@cleemullins I looked into this - I believe I know what the problem is - some missing info in the project file causing an issue with NuGet restore.  I'll confirm and update the PR tomorrow / Monday morning.

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3

@cleemullins I have fixed the dotnet restore issue.  The test that is failing now is failing elsewhere also (https://fuselabs.visualstudio.com/SDK_v4/_build/results?buildId=104740&view=logs&j=25a9ba8f-c8bf-58db-4b6e-5f84d8ada828&t=a4096510-a441-5a7e-ff5a-a9f780242dc5&l=3119) and isn't related to any changes in this PR.
The test is related to show typing middleware and it looks like we have had issues with the timing (environment dependent) when running those tests before.

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3


Fixed #2. See issue

Error message suggested to change method in line 306 to validate_text_input. I have no idea what I'm doing but my issue is solved now.

I wonder how I never noticed this regression, thank you!


Error on multiple specifiers in import/export namespaces

SWC treats export * as square, { b } from "./square" as a valid grammar, for which we should report it as an error to user side

If it's not valid in the ECMA spec, we should raise an issue in the SWC repo.


Add keyword aware quote strategy

Related to the discussion in doctrine/dbal#1592 it is probably a good idea to add this quote strategy. It can be enabled by the user optionally and therefore he should be aware of the upercase/lowercase issue in some DBMS.
For the integration of this into doctrine-bundle see this PR: doctrine/DoctrineBundle#553

@guilhermeblanco can you take a look at this?

@Deltachaos tests are missing tho

@Ocramius will add tests as soon as is see that there is a change that this gets merged

It'd be really good to have a native way to quote reserved words. 👍

@Majkl578 tests are added and class was renamed

@Deltachaos Do you still plan on fixing the broken tests?

@mikeSimonson yes i have this still on my list. But i can not guarantee to fix this within the next month. Probably start of next year.

@Deltachaos Thanks

Quoting is deeply wtf in DBAL - 3.0 needs to address more than just reserved word quoting...

@Deltachaos I think we're going for quoting-by-default in ORM 3.x, so I'm not sure if this will be required by then... /cc @guilhermeblanco just to confirm.

@Ocramius everything is quoted (and cannot be turned off) in master.
QuoteStrategy support is also removed from ORM 3.X.

Closing as duplicate then.


Install issue OS X / Not loading while installed ?!

Hi,
I tried to install LightGBM, and I'm running into issues. Before everything, I have Clang 10.0, Cmake 3.12.1, libomp installed, wheels as well. When running the python install here is what I obtain in the Terminal :
MacBook-Pro-de-Nicolas-2:~ nicolasgaraude$ cd LightGBM/python-package
MacBook-Pro-de-Nicolas-2:python-package nicolasgaraude$ python setup.py install
running install
INFO:LightGBM:Starting to compile the library.
INFO:LightGBM:Starting to compile with CMake.
Traceback (most recent call last):
File "setup.py", line 77, in silent_call
output = subprocess.check_output(cmd, stderr=subprocess.STDOUT)
File "/anaconda3/lib/python3.6/subprocess.py", line 336, in check_output
**kwargs).stdout
File "/anaconda3/lib/python3.6/subprocess.py", line 418, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['cmake', '../compile/']' returned non-zero exit status 1.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "setup.py", line 299, in
'Topic :: Scientific/Engineering :: Artificial Intelligence'])
File "/anaconda3/lib/python3.6/site-packages/setuptools/init.py", line 140, in setup
return distutils.core.setup(**attrs)
File "/anaconda3/lib/python3.6/distutils/core.py", line 148, in setup
dist.run_commands()
File "/anaconda3/lib/python3.6/distutils/dist.py", line 955, in run_commands
self.run_command(cmd)
File "/anaconda3/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "setup.py", line 222, in run
opencl_include_dir=self.opencl_include_dir, opencl_library=self.opencl_library)
File "setup.py", line 166, in compile_cpp
silent_call(cmake_cmd, raise_error=True, error_msg='Please install CMake and all required dependencies first')
File "setup.py", line 86, in silent_call
raise Exception("\n".join((error_msg, LOG_NOTICE)))
Exception: Please install CMake and all required dependencies first
The full version of error log was saved into /Users/nicolasgaraude/LightGBM_compilation.log
I don't understand the "Please install CMake and all required dependencies first" when I have installed everything.
I tried the simple version as well :
MacBook-Pro-de-Nicolas-2:python-package nicolasgaraude$ pip install lightgbm
Requirement already satisfied: lightgbm in /anaconda3/lib/python3.6/site-packages (2.2.2)
Requirement already satisfied: scipy in /anaconda3/lib/python3.6/site-packages (from lightgbm) (1.1.0)
Requirement already satisfied: numpy in /anaconda3/lib/python3.6/site-packages (from lightgbm) (1.15.1)
Requirement already satisfied: scikit-learn in /anaconda3/lib/python3.6/site-packages (from lightgbm) (0.19.1)
It is showing that lightgbm is installed, but when I try to load it in Python, I obtain the following :
MacBook-Pro-de-Nicolas-2:python-package nicolasgaraude$ python3
Python 3.6.7 |Anaconda custom (64-bit)| (default, Oct 23 2018, 14:01:38)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import lightgbm
/Users/nicolasgaraude/LightGBM/python-package/lightgbm/init.py:46: UserWarning: Starting from version 2.2.1, the library file in distribution wheels for macOS is built by the Apple Clang (Xcode_8.3.1) compiler.
This means that in case of installing LightGBM from PyPI via the pip install lightgbm command, you don't need to install the gcc compiler anymore.
Instead of that, you need to install the OpenMP library, which is required for running LightGBM on the system with the Apple Clang compiler.
You can install the OpenMP library by the following command: brew install libomp.
"You can install the OpenMP library by the following command: brew install libomp.", UserWarning)

I am completely lost. Can you kindly help me ?
Thanks a lot in advance
Nicolas

Hi @NicolasGaraude !
There are some problems with the latest macOS (Mojave). Tge fix is here: #1923.
Speaking about the installation via pip, everithing should be OK with it, if ypu have libomp installed on your MacBook. As you can see, this is a warning, not error.

For the error happens during the istallation from sources you can track this issue: #1898.

Hi,
Thanks for the quick answer. But I still don’t understand what I should do :
- It is said in the link you provided that, given the bugs with Mojave, a hot fix had been made
- The hot fix has been been 6 days ago, I cloned the GitHub folder 2 hours ago again, so the setup.py file was already containing the hotfix
I don’t understand, in simple words, what I have to do, given that libomp is installed on my Macbook (I get : "Warning: libomp 7.0.0 is already installed and up-to-date, To reinstall 7.0.0, run brew reinstall libomp).
The pip issue I have is, as was written in my post, that pip shows me that LightGBM is installed, but when I try to launch it in Python, it fails.
Please help me, this is driving me mad :(

Le 30 déc. 2018 à 18:16, Nikita Titov<EMAIL_ADDRESS>a écrit :
Hi @NicolasGaraude https://github.com/NicolasGaraude !
There are some problems with the latest macOS (Mojave). Tge fix is here: #1923 https://github.com/Microsoft/LightGBM/pull/1923.
Speaking about the installation via pip, everithing should be OK with it, if ypu have libomp installed on your MacBook. As you can see, this is a warning, not error.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Microsoft/LightGBM/issues/1933#issuecomment-450574411, or mute the thread https://github.com/notifications/unsubscribe-auth/AosnmfHZJ8JKX01U2dfzdsVr4aXB3KHVks5u-PT1gaJpZM4Zk_T1.

The hot fix has been been 6 days ago, …

Hotfix hasn't been merged yet.

The pip issue I have is, as was written in my post, that pip shows me that LightGBM is installed, but when I try to launch it in Python, it fails.

You didn't say that you cannot run LightGBM. Please privide a error log.


Add convenience method for user_typing?

It might be a nice addition maybe? Currently I do:
rtm.sendMessage(jsonEncode(litmap(
      id := 1,
      type := "typing",
      channel := "..."
    )));

It's in my fancy language JavaX, but you get what it does, I'm sure...

What do you mean by this? I really don't understand the intention yet. Do you mean having some utility classes/methods to enable library users to build message objects?

I mean a message like Slack.sendTyping(String channelID);
On Mon, 18 Mar 2019 at 14:10, Kazuhiro Sera<EMAIL_ADDRESS>wrote:

What do you mean by this? I really don't understand the intention yet. Do
you mean having some utility classes/methods to enable library users to
build message objects?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/seratch/jslack/issues/108#issuecomment-473903275, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AET6Q5tTwUEgNxKXtfDFOn5T00QFEC8Bks5vX5BVgaJpZM4b5bb4
.

--
Stefan Reich
BotCompany.de // Java-based operating systems

When/how to use the method? RTM is a kind of event subscription. Your Slack applications just receive user_typing event when the user action happens. Also, the sendMessage API can send only simple text messages. https://slack.dev/node-slack-sdk/rtm_api

I am using this to make the bot send an "is typing..." event itself. Helps
the user interaction :-)
On Mon, 18 Mar 2019 at 14:23, Kazuhiro Sera<EMAIL_ADDRESS>wrote:

When/how to use the method? RTM is a kind of event subscription. Your
Slack applications just receive user_typing event when the user action
happens. Also, the sendMessage API can send only simple text messages.
https://slack.dev/node-slack-sdk/rtm_api
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/seratch/jslack/issues/108#issuecomment-473907505, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AET6Q2zcdrOdZQHyOkyxy1kObS4FQRkJks5vX5M2gaJpZM4b5bb4
.

--
Stefan Reich
BotCompany.de // Java-based operating systems

Ah, okay. I got your point. I misunderstood the sendMessage API. Indeed, having some methods like RTMClient#sendTypingEvent(String channelId), #sendMessageEvent(String channelId, String text) may be more easy-to-use.

JFYI: I am planning to work on the enhancement regarding RTM messages.

To begin with, I'm going to provide the Java types to map JSON data. ref: #69

@stefan-reich Since 1.4.0, you can build RTM messages with the newly added typesafe object builder. https://github.com/seratch/jslack/blob/1.4.0/src/test/java/com/github/seratch/jslack/Slack_rtm_Test.java#L120-L123

These APIs are my answers to this issue. Let me close this issue now. Feel free to reopen this or create another one if you have something to add / discuss further. https://github.com/seratch/jslack/blob/1.5.2/src/test/java/com/github/seratch/jslack/Slack_rtm_Test.java#L199-L220


Re-export secp256k1 dependency as secp

The identifier secp156k1 is annoying to write [repeatedly]. To make rust-bitcoin more ergonomic and less annoying we can re-export secp256k1 as secp so users can do use bitcoin::secp::Foo with no real loss of clarity.
Keep the full export for users who prefer the full name.
For context please see: https://github.com/rust-bitcoin/rust-bitcoin/discussions/984

Sounds good to me. Will ACK in a moment. I'd like a 3rd ACK though from @Kixunil because it feels a bit questionable to re-export a module twice under different names.

TBH I find the name questionable. It's called secp256k1, that's the official name. secp sounds weird. :man_shrugging:
I suspect the length is not the problem but the numbers are harder to type?

Yes, IME it's the numbers that are annoying -- though in my opinion I still wouldn't use the shortened version in my own code.
Having said that, secp and libsecp are how we typically refer to the curve and the library when talking aloud, and in casual conversation.

Yeah I'm a bit torn by this. I came up with the idea before when I was first interacting with secp256k1 and the numbers really annoyed me but now I've typed them a million times its not so annoying, its just an annoyingly long name in general but that is what it is. I'm ok to drop this or keep it what ever others think. The usage of "secp" in casual messages is also a factor that pushed me towards raising the PR the other day when I was re-considering it.

Closing, its not a real improvement.


Makefile: update versions & FPGA: fix naked return error from linter

New version of golangci-lint shows errors about return with having no value.
FPGA related codes have such, so fixed.

New version of golangci-lint shows errors about return with having no value.
FPGA related codes have such, so fixed.

What change in golangi-lint triggers the error? Did they change the nakedret linter default settings?

What change in golangi-lint triggers the error? Did they change the nakedret linter default settings?

I thought nakedret became default after v1.52.2, but it seems that it is still kept as disabled by default (https://golangci-lint.run/usage/linters/#disabled-by-default). But, we enabled in .golangci.yml. I have no idea actually why it caused the errors.

I have no idea actually why it caused the errors.

can you find out please?

I have no idea actually why it caused the errors.

can you find out please?

I really do not understand...
I tried to see the release notes of golangci-lint and nakedret but could not find anything that looks related to this error we get.
What I found out is:
with the old version (v1.52.2) and linter-settings set with 'max-func-lines: 1' which should show everything that has naked return, it does not show the errors we get in the newer version (v.1.53.X).
So, my guess is just that there was some logic change of calculating how many lines a func has (and I think there was a problem in the logic in the past so that it did not show the errors though they should have).

I tried to see the release notes of golangci-lint and nakedret but could not find anything that looks related to this error we get.

this was fixed in v1.53.0: golangci/golangci-lint#1317

Given this ^, it's not
In the golangci-lint version < v1.53.0, some naked return errors
are not caught. Fix the caught errors in the version >= v1.53.0.

but
golangci-lint version < v1.53.0 used nakedret linter that did not check
return values in conditionals. That got changed in v1.53.0 and some
of our code starts failing because of naked returns from conditionals.

Update the code to get nakedret linter passing.

Codecov Report

Merging #1477 (d6859ea) into main (0337834) will not change coverage.
The diff coverage is 0.00%.

:exclamation: Current head d6859ea differs from pull request most recent head bf286c6. Consider uploading reports for the commit bf286c6 to get more accurate results

@@           Coverage Diff           @@
##             main    #1477   +/-   ##
=======================================
  Coverage   50.10%   50.10%
=======================================
  Files          43       43
  Lines        4878     4878
=======================================
  Hits         2444     2444
  Misses       2295     2295
  Partials      139      139

Impacted Files
Coverage Δ

pkg/controllers/iaa/controller.go
6.89% <ø> (ø)

pkg/fpga/dfl_linux.go
0.00% <0.00%> (ø)

pkg/fpga/intel_fpga_linux.go
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Lxd support

Any chance of ranchervm supporting lxd.  I think lxd is the new way of thinking hypervisor.  It will be nice if rancher supports lxd

+1

+1

+1

+1

:+1:

++

+1

+1

+1

+1

+1


@sveltejs/enhanced-img: Fix client component compilation

In JS files, Vite compiles __VITE_ASSET_xxx_ to " + new URL("../path", import.meta.url) + ". This was being inlined directly into the client-side components, meaning the client components were rendering <img src=" + new URL("../path", import.meta.url) + ">. This fixes that.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[x] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Thanks for finding and fixing this!
It looks to me like this happens on the client-side JS. I can't reproduce it on the SvelteKit site and I'm guessing that may be because we only do manual imports there. I'm really curious why it doesn't happen with manual imports, but does happen when simply sticking the path in the src. This PR has a small performance hit, so we should investigate a bit to see if we can avoid the import.meta stuff from being generated in the first place.

Here's the relevant location in Vite:
https://github.com/vitejs/vite/blob/b93dfe3e08f56cafe2e549efd80285a12a3dc2f0/packages/vite/src/node/plugins/asset.ts#L132

Hmm. In https://github.com/sveltejs/kit/pull/9220 we seem to be forcing relative paths (which was attempted to be changed and then later reverted in https://github.com/sveltejs/kit/pull/10442). I don't like the API of paths.relative: undefined | false, which I find to be a bit confusing. I don't understand exactly what the undefined case is trying to solve for. It sounds like it might help the Internet Archive? I'd expect the Internet Archive to be able to deal with all the sites out there that are not coded especially for it with a weird half-relative and half-absolute behavior, but maybe that's overly optimistic.
The undefined value causes hydration slowdowns due to different values on the client and server requiring complex comparisons, causes larger bundle sizes from inserting import.meta.url everywhere, and now is causing template creation to be de-optimized. I really dislike it. I'd love to just see a default value of false with undefined removed in Kit 2.0, but am not sure if that's feasible.
We will need a solution like in this PR regardless of whether we can keep Kit in an optimized state because you'll end up with this code when the user sets relative: true. I do wonder if we can at least strip the leading "" +  and trailing + "" though to be slightly more optimized about it.

I also really dislike this solution, but given that the alternative is all images being broken on pages with CSR, might it be better to merge this ASAP and then look into performance improvements?


Issue with sample JSON in file.

Fix spacing characters which cause a JSON issue when the code is copy+pasted into a file. All contents are identical except for the spaces.

@scseely : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@scseely - thanks for this change. It looks like the same fix was handled in a different PR.

#please-close


Add jsonl support

JSON support is great, but JSONL is very common in streaming cases (e.g. logs).
$ cat test.jsonl
{"a": 1}
{"a": 2}
{"a": 42}

$ alasql "select * from jsonl('./test') where a > 1"
[
  {
    "a": 2
  },
  {
    "a": 42
  }
]

Any chance you can add a test file that confirms its working (so we detect if we break that later)?
Is jsonl the right name? What about ndjson (new line delimited json) or I have even seen jsons ?

@kfigiela ?

@mathiasrw, thanks for reminder. I'll try to address those over the weekend and add tests.
As far as the extension/naming, according to a blog post these are "competing", but practically identical standards. We only parse, so as long as JSON.parse can handle it we should be good. I think, it makes sense to register them both, so either file extension works.

https://duckdb.org/2023/03/03/json.html uses ndjson indeed, would be good to rename.

On the other hand, Google BigQuery mentions JSONL everywhere. Nevertheless, we can have both aliases working and this is what I have implemented. Otherwise, I addressed the above comments and added some tests.

Just provide all the most used names (alasql.jsonl = alasql.ndjson = alsql.....)

Ahh - you already did :)

Doing a bit of performance testing.

its faster just to regex \s*\r?\n\s*/ as it removes any empty lines in one swoop. Ill add this before merging.


"Some data left during file processing" with Addressables

Game name: Psycholonials
Platform: Windows
Error message: Some data left
Stack trace:    at uTinyRipper.Lz4.Lz4DecodeStream.ReadBuffer(Stream stream, Int64 count)
   at uTinyRipper.BundleFileScheme.ReadFileStreamMetadata(Stream stream, Int64 basePosition)
   at uTinyRipper.BundleFileScheme.ReadScheme(Stream stream)
   at uTinyRipper.GameCollection.ReadScheme(SmartStream stream, String filePath, String fileName)
   at uTinyRipper.GameCollection.LoadScheme(String filePath, String fileName)
   at uTinyRipper.GameStructure.ProcessPlatformStructure(GameStructureProcessor processor, PlatformGameStructure structure)
   at uTinyRipper.GameStructure.Load(List`1 pathes, LayoutInfo layinfo)
   at uTinyRipper.GameStructure.Load(IEnumerable`1 pathes, LayoutInfo layinfo)
   at uTinyRipperGUI.MainWindow.LoadFiles(Object data)

Your game uses the Addressable system which is not supported by uTinyRipper.

Support for Unity versions up to 2020.2.0 has been recently added to my AssetRipper fork.


translation publication inquiry

Hi, I work for Hanbit Media, Inc., the largest IT publisher in Korea.
We have translated and published many English programming books here.
I think your book is also very helpful to Korean programmer readers.
Do you have any plan for publication in foreign countries?
If you are willing, I'll let our copyright agency contact you (again) to discuss the contract detail.
I appreciate your quick response.

No thanks!


Investigate possibility of rewriting driver in userspace

IOKit should theoretically allow the creation of virtual HID devices in userspace, as seen in this example. While that example does not currently build, reimplementing the functionality of the kernel driver in userspace would significantly reduce the impact of any exploited vulnerability and also allow for easier distribution.
References

https://opensource.apple.com/source/IOHIDFamily/IOHIDFamily-870.50.33/tools/IOHIDUserDeviceTest.c.auto.html
https://opensource.apple.com/source/IOHIDFamily/IOHIDFamily-870.50.33/tools/hidScript/hidScript.cpp.auto.html
https://stackoverflow.com/questions/21075561/is-it-possible-to-create-a-virtual-iohiddevice-from-userspace
https://developer.apple.com/documentation/iokit/iohiddevice.h_user_space?language=objc
https://github.com/Orochimarufan/HIDRAW/blob/764a6f6fc144c3c6850978e0341630444cbea049/muhid/libmuhid/muhid_iokit.c

Exciting idea! Unfortunately, it looks like IOHIDResourceDeviceUserClient::initWithTask() checks that the owning task has the com.apple.hid.manager.user-access-device entitlement. This causes the IOHIDUserDeviceCreate() call to fail. I don't think it's possible to get such an entitlement, right?


Ejecting from medical scanner puts you inside its hitbox, making it impossible to move.

Should it act similar to SS13? Where exiting many machines places you on the same tile as the machine, superimposed on it.
I don't know how this is done in SS13 to be honest. What are the options? Something like one-way-collision, where you can leave the hitbox but cannot enter it.

SS13 uses one way collision, yes.

Oh. I dunno how to implement that into the collidable component in ss14. 🤷♀

Should mention that it also disallows you to use guns after you eject from one


SQLITE busy: database is locked

While a single circular rebalance was in progress, I did a dry run using autorebalance.js
node service/autorebalance.js --dryrun
The circular rebalance finished successfully...

... but the following error was reported:

Output of autorebalance:
autorebalance.log

fixed


change target framework to .net 4.7.1

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

Is there a reason to target 4.7.1? That will limit it to only certain versions of Windows

Not really, was more of a "the newer, the better" thing and I thought ColorTool only works on Win10.

I looked at this quick while I'm merging stuff on my dev box here and for whatever reason, I don't seem to have the net471 SDK installed by default. I might just end up rejecting this and leave it as net46 until we have a reason to use the newer one just to make building/running it easier.


Support inheritance and interpolation in .terragrunt files

This PR adds support for two new features to Terragrunt:

Inheritance. A .terragrunt file can specify a parent configuration from which to inherit all settings.
Interpolation. Terragrunt now supports two basic interpolation functions: find_in_parent_folders, which can be used to automatically find a .terragrunt file in a parent folder rather than manually specifying the path, and path_relative_to_parent, which returns the relative path between a child .terragrunt file and a parent, which is useful for automatically populating state_file_id and key based on folder structure.

Check out the README for full details. Here is a direct link to the branch, as that's easier to read than a diff.
This fixes #26.

OK, merging.

OK, merging


state_trigger with state_check_now=True and state_hold_false=0

I use state_check_now on a @state_trigger to mean, I recently changed something or I just restarted Home Assistant and I want this trigger to be evaluated right now and to execute the method if it's true.
And state_hold_false just keeps the method from triggering again when it doesn't really have anything to do.
However, as indicated in the docs, using these two together, means that if the trigger evaluates to true at startup, it will NOT execute the method. I think that it should.
In other words, state_check_now should ignore state_hold_false when evaluating at startup. I can't think of a situation where the current mode of operation is useful: a scenario where I want it evaluated RIGHT NOW, but not EXECUTED if it's True.
This is easily worked around in code, so it isn't a problem if it gets left the way it is. I just haven't found a use for it yet, but I've several times written extra code to make it behave the way I expect it to (i.e. I don't use state_hold_false and instead implement that same functionality in the method or with state_active).

a real world example:
@state_trigger((
        "input_boolean.living_occupied == 'on'"
        " or input_boolean.kitchen_occupied == 'on'"
        " or input_boolean.dining_occupied == 'on'"
        " or binary_sensor.entry_occupied == 'on'"
        " or input_boolean.hallup_occupied == 'on'"
        " or input_boolean.halldown_occupied == 'on'"
), state_hold_false=0, state_check_now=True)
def turn_on_holiday():
    switch.holiday_stair_rail.turn_on()
    switch.holiday_mantle.turn_on()

I don't need this to turn on those things again and again just because the kitchen is now occupied when the living was already previously occupied. Hence state_hold_false=0 handles this.
But, if the living turned "on" when Home Assistant was restarting (or if I just added that condition to the state trigger and reloaded pyscript), this isn't detected (because it starts up as "on"). So those switches don't turn on until something else happens. Hence state_check_now=True, so it'll look at those things immediately without getting a state_changed event first.
But using them together, means it still doesn't turn on.

Yes, I struggled with picking which one would override the other if they were both specified. I decided on the current approach to use state_check_now to override the default of state_hold_false not requiring a False value prior to the first trigger.
You make a good case for changing that behavior.  But then there's no way to specify the case where you want a False before the first trigger.  I agree your use case is more common.
Let me think about this some more. Hopefully we can figure out a clever and intuitive way to support either way.

Ok, here's how I plan to revise startup behavior.  Without state_check_now, the new startup behavior requires an initial False period: the trigger expression is evaluated at startup; if False then the state_hold_false  period begins.  If True, we wait until the next False.
With state_check_now set, it does the usual thing - if True at startup, the trigger occurs, and we wait for the next False.
This seems much better - both parameters operate separately.
The original startup default of the first True triggering without requiring a False period doesn't seem useful, so that will be dropped.

I think that seems perfect. To recap, I think this covers all of the possible startup scenarios:
At startup, with defaults, a True expression WILL NOT trigger. Any subsequent state change that results in a True expression WILL trigger.
At startup, with defaults, a False expression WILL NOT trigger. Any subsequent state change that results in a True expression WILL trigger
At startup, with state_check_now=True, a True expression WILL trigger. Any subsequent state change that results in a True expression WILL also trigger.
At startup, with state_check_now=True, a False expression WILL NOT trigger. Any subsequent state change that results in a True expression WILL also trigger.
At startup, with state_hold_false=0, a True expression WILL NOT trigger. Any subsequent state change that results in a True expression also WILL NOT trigger. Once the expression is False, the next True WILL trigger. Then another False is required. Then the next true WILL trigger again. And so on.
At startup, with state_hold_false=0, a False expression WILL NOT trigger. Any subsequent state change that results in a True expression WILL trigger. Once the expression is False, the next True WILL trigger. Then another False is required. Then the next true WILL trigger again. And so on.
At startup, with state_hold_false=0 AND state_check_now=True, a True expression WILL trigger. Any subsequent change that results in a True expression WILL NOT trigger. Once the expression is False, the next True WILL trigger. Then another False is required. Then the next true WILL trigger again. And so on.
At startup, with state_hold_false=0 AND state_check_now=True, a False expression WILL NOT trigger. Any subsequent change that results in a True expression WILL trigger. Once the expression is False, the next True WILL trigger. Then another False is required. Then the next true WILL trigger again. And so on.


Versioning: Add Wix support

Add WIX installer build versioning, needs to be able to update a installerversion.wxi file of the of the following format
<?xml version="1.0" encoding="utf-8"?>
<!-- Note that this file will be overridden by the build server. -->
<Include>
  <?define MajorVersion       = "2" ?>
  <?define MinorVersion       = "2" ?>
  <?define BuildNumber        = "2" ?>
  <?define Revision           = "2" ?>
  <?define FullVersion        = "<IP_ADDRESS>" ?>
  <!--WiX Installer Versions are Major.Minor.Revision -->
</Include>

Shipped in 1.5.22