autocmd, autocmds, augroup macros

Here are three macros for setting up autocmd and augroup. I can create a PR if you think it is reasonable to have.
(macro autocmd [event opt]
  `(vim.api.nvim_create_autocmd
    ,event ,opt))

(macro autocmds [...]
  (var form `(do))
  (each [_ v (ipairs [...])]
    (table.insert form
                  `(autocmd ,(unpack v))))
  (table.insert form 'nil)
  form)

(macro augroup [name ...]
  (var cmds `(do))
  (var group (sym :group))
  (each [_ v (ipairs [...])]
    (let [(event opt) (unpack v)]
      (tset opt :group group)
      (table.insert cmds `(autocmd ,event ,opt))))
  (table.insert cmds 'nil)
  `(let [,group
         (vim.api.nvim_create_augroup ,name {:clear true})]
     ,cmds))

(autocmd
 [:BufNewFile :BufRead] {:pattern [:*.txt :*.text] :command "setf text"})

;; vim.api.nvim_create_autocmd({"BufNewFile", "BufRead"}, {pattern = {"*.txt", "*.text"}, command = "setf text"})

(autocmds
 [[:BufNewFile :BufRead] {:pattern [:*.txt :*.text] :command "setf text"     }]
 [[:BufNewFile :BufRead] {:pattern [:*vifmrc]       :command "setf vifm"     }]
 [[:BufNewFile :BufRead] {:pattern [:*/tmux/conf]   :command "setf tmux"     }]
 [[:BufNewFile :BufRead] {:pattern [:*/git/config]  :command "setf gitconfig"}]
 [[:BufNewFile :BufRead] {:pattern [:*fetchmail]    :command "setf fetchmail"}]
 [[:BufNewFile :BufRead] {:pattern [:*procmailrc]   :command "setf procmail" }]
 [[:BufNewFile :BufRead] {:pattern [:*muttrc]       :command "setf muttrc"   }])

;; do
;;   vim.api.nvim_create_autocmd({"BufNewFile", "BufRead"}, {pattern = {"*.txt", "*.text"}, command = "setf text"})
;;   vim.api.nvim_create_autocmd({"BufNewFile", "BufRead"}, {pattern = {"*vifmrc"}, command = "setf vifm"})
;;   vim.api.nvim_create_autocmd({"BufNewFile", "BufRead"}, {pattern = {"*/tmux/conf"}, command = "setf tmux"})
;;   vim.api.nvim_create_autocmd({"BufNewFile", "BufRead"}, {pattern = {"*/git/config"}, command = "setf gitconfig"})
;;   vim.api.nvim_create_autocmd({"BufNewFile", "BufRead"}, {pattern = {"*fetchmail"}, command = "setf fetchmail"})
;;   vim.api.nvim_create_autocmd({"BufNewFile", "BufRead"}, {pattern = {"*procmailrc"}, command = "setf procmail"})
;;   vim.api.nvim_create_autocmd({"BufNewFile", "BufRead"}, {pattern = {"*muttrc"}, command = "setf muttrc"})
;; end

(augroup :my-group
 [[:BufNewFile :BufRead] {:pattern [:*vifmrc]     :command "setf vifm"     }]
 [[:BufNewFile :BufRead] {:pattern [:*/tmux/conf] :command "setf tmux"     }]
 [[:BufNewFile :BufRead] {:pattern [:*muttrc]     :command "setf muttrc"   }])

;; local group = vim.api.nvim_create_augroup("my-group", {clear = true})
;; vim.api.nvim_create_autocmd({"BufNewFile", "BufRead"}, {pattern = {"*vifmrc"}, command = "setf vifm", group = group})
;; vim.api.nvim_create_autocmd({"BufNewFile", "BufRead"}, {pattern = {"*/tmux/conf"}, command = "setf tmux", group = group})
;; vim.api.nvim_create_autocmd({"BufNewFile", "BufRead"}, {pattern = {"*muttrc"}, command = "setf muttrc", group = group})

Oh this is pretty neat, maybe a separate macros file that people can require would be best 🤔 I regret the one large macro file in the current system and don't want to keep adding to it since it can collide with other names the user wishes to use. I'll have a play and see if I can get this into a file like aniseed.macros.autocmds or something like that.

Pushed some changes to the develop branch, added this code and some docs on how to include it. Usage looks like this:
(module aniseed.view
  {require {fnl aniseed.fennel}
   import-macros [[ac :aniseed.macros.autocmds]]})

(ac.autocmd
 [:BufNewFile :BufRead] {:pattern [:*.txt :*.text] :command "setf text"})

What do you think? I added some new stuff to the module macro so we can call import-macros properly now.

That's good. Maybe we can import all macros using require-macros?
Fennel has issues when a macro is referencing other macros. For instance, the augroup macro uses autocmd macro. If the macro autocmd is in a namespace ac, then ac.augroup would have problems at macroexpanding.

require-macros was deprecated in Fennel 0.4.0 and we're on 1.3.0 now, so there's a good chance they'll remove require-macros entirely at some point. I can't recommend it's use anywhere now, even if Aniseed legacy things rely on it.
As for the macro expanding issue, we should be able to work around that by referring to the macro outside of the generated code. As long as the macro code refers to it's sibling macros and the generated code doesn't require another layer of macro expansion, it should be fine. I'll check that now and adjust the code if required.

There you go, see that latest commit for the fix. Macros can refer to each other when in "macro land" as long as the bottom of the call stack returns some quoted code. But macros can call other macros directly just fine. I think this is correct and good practice, the other way that we had before can fall victim to variable shadowing bugs.

(module foo
  {import-macros [[{: autocmd} :aniseed.macros.autocmds]]})

(autocmd ...)

This might be what you're looking for, pay close attention to the number of sub-tables. You can't use import-macros and have it splat all macros from inside into your context, that's just describing require-macros which is deprecated for that reason I think. The language appears to be trying to remove implicit scope pollution in favour of explicit.

This was a relatively recent addition to Aniseed, so wasn't possible to express this in the module macro until probably the most recent version.

Right on. Thank you, that works, but I was hoping to not have to specify each macro I want to import (I have a bunch of macros of my own). I'll cave and do it this way eventually.


a license set on the kind level of a topology is not handled by the clabverter

A license set on the kind level of topology is not handled by the clabverter

#117 resolves it!


Mass backport from master

Pull Request Test Coverage Report for Build 338

39 of 47 (82.98%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.8%) to 98.772%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

exec_helpers/subprocess_runner.py
10
12
83.33%

exec_helpers/init.py
3
9
33.33%

Totals

Change from base Build 301:
-0.8%

Covered Lines:
1046

Relevant Lines:
1059

💛  - Coveralls


split route

hi,
I upgrade to<EMAIL_ADDRESS>this is my folder
web_root/
  - vue/
    + api/
    + config/ (webpack & karma config)
    - entry/ (multi entry)
      - index.json (multi entry rule)
      - web.js
    + image/ (image assets)
    + layout/ (page layouts)
    + module/ (page modules)
    + page/ (page contents)
    + route/ (sub routes)
    + style/ (stylus styles)
    + test/ (unit tests)
    + widget/ (ui widgets)
  - public/
    - index.html
    - web.js (build)

it's ok like this
// web_root/vue/entry/web.js
import Vue from 'vue'
import Router from 'vue-router'

Vue.use(Router)

var router = new Router()

router.map({
	'/': {
		component: require('../layout'),
		subRoutes: {
			'/': {
				component: require('../page/goods')
			}
		}
	},
	'/company': {
		component: require('../layout/company'),
		subRoutes: {
			'/brand': {
				component: require('../page/company-brand')
			},
			'/product': {
				component: require('../page/company-product')
			}
		}
	}
})

router.redirect({
	'*': '/'
})

router.start({
	name: 'web'
}, 'body')

but it's error
when I change to
// web_root/vue/entry/web.js
import Vue from 'vue'
import Router from 'vue-router'

Vue.use(Router)

var router = new Router()

router.map({
	'/': require('../route'),
	'/company': require('../route/company')
})

router.redirect({
	'*': '/'
})

router.start({
	name: 'web'
}, 'body')

// web_root/vue/route/index.js
export default {
	component: require('../layout'),
	subRoutes: {
		'/': {
			component: require('../page/goods')
		}
	}
}

// web_root/vue/roote/company.js
export default {
	component: require('../layout/company'),
	subRoutes: {
		'/brand': {
			component: require('../page/company-brand')
		},
		'/product': {
			component: require('../page/company-product')
		}
	}
}

how can I make it work ?

@yozman you got to try your best to be clear with your questions. You did not mention what error you are actually getting so we can't help. Also this type of question is better suited within the community forums, gitter, or stackoverflow. Please review the Issue Reporting Guidelines.
I suggest closing this issue and asking your question on the above mentioned sites.


remove suppress_err

to test if this causes CI failur in docu

Codecov Report

Merging #6 (45d2d0a) into main (d66f511) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          115       115
=========================================
  Hits           115       115

Impacted Files
Coverage Δ

src/requires_cairommakie.jl
100.00% <ø> (ø)

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 d66f511...45d2d0a. Read the comment docs.


custom wake word

Sorry for violating the issue writing guide. For more than a week I have been trying to add a custom wake word to my avs sdk. I have been facing many issues. Can someone please guide me step by step to use kitt ai mypersonalmodel.pmdl as the hotword for alexa.
I am running it on raspberry pi.
Thanks in advance

I have been having the same problem for quite some time and would also greatly appreciate help on this. I have no programming experiencing and have not been able to figure out how to use cmake. ie. When I am in the terminal do I execute the below command while I am in my avs-device-sdk folder? For example: cd ~/Desktop/avs-device-sdk cmake....
Can you give an example on what the "absolute-path-to-lib" and "absolute-path-to-include-dir" would be for this if someone were to have their avs-device-sdk folder saved on their desktop?
Also, can I leave my custom wake word file as a .pmdl or do I need to convert it to something else? Lastly do I save this custom wake word file?
Thank you very much for your help
cmake  -DKITTAI_KEY_WORD_DETECTOR=ON -DKITTAI_KEY_WORD_DETECTOR_LIB_PATH=/snowboy-1.2.0/lib/libsnowboy-detect.a -DKITTAI_KEY_WORD_DETECTOR_INCLUDE_DIR=/snowboy-1.2.0/include


RTD failing yet again

memory consumption errors as usual.
@keewis I remember you had an idea for using pip instead of conda?

we could try moving everything except cartopy to the pip section in the environment file (iris is scitools-iris on PyPI). That seems to reduce the maximum memory consumption quite a bit (the conda-forge channel has grown almost too much).

This did indeed work for my project (regionmask), https://github.com/mathause/regionmask/blob/master/docs/environment_rtd.yml

I tried it, but it still fails: https://readthedocs.org/projects/xray/builds/10502148/ We can't use pip directly since cartopy does not upload wheels and I'd expect the source install to fail.
If we look at the issue tracker of RTD, we can see a lot of issues regarding memory errors, so maybe this is a general issue with conda (when using conda-forge) and RTD.

The docs seem to build ok on Azure piplines, is it possible to get the built docs from that and publish somewhere? I do know this is possible with Travis, but haven't actually done it myself since my docs don't (yet?) have a memory problem.

yeah, that would probably be the way forward. See #3697 for more discussion.

No luck with pinned versions and the stable build image: https://readthedocs.org/projects/xray/builds/10547287/

due to the work of the RTD maintainers, our builds pass again. However, trying to build stable still fails, but instead of a memory error we get a sphinx failure: https://readthedocs.org/projects/xray/builds/10609593/
I think we already fixed that in master?


DLF labels are having conflicts with Istio sidecar Injection

When trying to deploy a pod with DLF labels inside an namespace with istio inject, I'm seeing the errors below. It looks like there's some conflicts between the DLF and istio mutation.
The Pod "nginx" is invalid: spec.volumes[4].name: Duplicate value: "example-dataset"

Here is my pod
cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: Pod
metadata:
  name: nginx
  namespace: default
  labels:
    dataset.0.id: "example-dataset"
    dataset.0.useas: "mount"
spec:
  containers:
    - name: nginx
      image: nginx
EOF

Hi @Tomcli can you try creating the pod like this:
cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: Pod
metadata:
  name: nginx
  annotations:
    sidecar.istio.io/inject: "false"
  namespace: default
  labels:
    dataset.0.id: "example-dataset"
    dataset.0.useas: "mount"
spec:
  containers:
    - name: nginx
      image: nginx
EOF

Thanks @YiannisGkoufas, for pipelines we can disable istio sidecar. On the notebook server we can define our own volume mount definition on the UI so we can bypass this problem. But on KFServing, if we are going to disable istio sidecar, then we are losing some traffic metrics. Although those metrics are not important for now, we should revisit it in the future as there could be other mutation webhook that can cause this problem.

@YiannisGkoufas we can put this into a troubleshooting section and close this issue.

Closing this issue as it seems to have been resolved


fix prerequisites

🦟 Bug fix
Fixes #
Summary

Fix prerequisites for 23_depth_camera_tutorial.md
🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸

🎈 Release
Preparation for <X.Y.Z> release.
Comparison to <x.y.z>: https://github.com/gazebosim//compare/<LATEST_TAG_BRANCH>...<RELEASE_BRANCH>

Needed by <PR(s)>
Checklist

[ ] Asked team if this is a good time for a release
[ ] There are no changes to be ported from the previous major version
[ ] No PRs targeted at this major version are close to getting in
[ ] Bumped minor for new features, patch for bug fixes
[ ] Updated changelog
[ ] Updated migration guide (as needed)
[ ] Link to PR updating dependency versions in appropriate repository in gazebo-release (as needed):

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

apart from the suggested changes, this looks good to me


Add unit testing in landDA

Describe your changes
Summarise all code changes included in PR:
Added test folder with a number of scripts for unit testing. There are 6 unit tests for upcoming release (2020 with era5 forcing and GHCN obs):
  Test #1: test_vector2tile
  Test #2: test_create_ens
  Test #3: test_letkfoi_snowda
  Test #4: test_apply_jediincr
  Test #5: test_tile2vector
  Test #6: test_land_driver

Compiling / testing
The following is an example of how to obtain the code, compile, and run ctest, on the
Hera/Orion HPC.
# download Data (subject to change)
wget https://epic-sandbox-srw.s3.amazonaws.com/landda-data-2020.tar.gz
tar xvfz landda-data-2020.tar.gz

# download source code
git clone -b feature/ctest --recursive https://github.com/clouden90/land-offline_workflow.git
cd land-offline_workflow

# load the machine specific modules (for compiling, here we use Orion as example)
module use modulefiles
module load landda_orion.intel

# compiling
mkdir build
cd build
ecbuild ..
make -j 4

# grab a compute node and run ctests
salloc --ntasks 6 --exclusive --qos=windfall --time=00:05:00
#
module use modulefiles
module load landda_orion.intel
#
ctest -V --stop-on-failure

Screen output:

    Start 1: test_vector2tile
1/6 Test #1: test_vector2tile .................   Passed    0.99 sec
    Start 2: test_create_ens
2/6 Test #2: test_create_ens ..................   Passed    1.57 sec
    Start 3: test_letkfoi_snowda
3/6 Test #3: test_letkfoi_snowda ..............   Passed   42.79 sec
    Start 4: test_apply_jediincr
4/6 Test #4: test_apply_jediincr ..............   Passed    3.47 sec
    Start 5: test_tile2vector
5/6 Test #5: test_tile2vector .................   Passed    0.92 sec
    Start 6: test_land_driver
6/6 Test #6: test_land_driver .................   Passed    6.99 sec

100% tests passed, 0 tests failed out of 6

Total Test time (real) =  56.78 sec

Issue ticket number and link
PR subject to change.
Do not merge this PR until #22 and #25 are merged.
Test output
unit tests create associated outputs for each components (e.g. apply_incr, letkfoi). Potentially could be compared with baselines created from cmake build.
If changes to the test results are expected, what are these changes? Provide a link to the output directory when running the test:
Checklist before requesting a review

[ ] My branch being merged is up to date with the latest develop.
[ ] I have performed a self-review of my code by examining the differences that will be merged.
[ ] I have not made any unnecessary code changes / changed any default behavior.
[ ] My code passes the DA_IMS_test, or differences can be explained.

@clouden90 we can closed this draft PR since ctest capability was added ok to v1 release, right?

@clouden90 we can closed this draft PR since ctest capability was added ok to v1 release, right?

Yes thx!


fix(DEVCOM.LuaJIT): remove version 2.1.19676

Package is no longer available.

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

/azp run

URL: https://github.com/DevelopersCommunity/cmake-luajit/releases/download/v2.1.1700008891/LuaJIT-2.1.19676-win64.msi
Response status code does not indicate success: 404 (Not Found).
(Automated message - build 758)


ORC-941: Move MacOS 10.15/11.5 test from Travis to GitHub Action

What changes were proposed in this pull request?
This PR aims to migrate the following jobs from Travis CI to GitHub Action.

Mac OS 10.15
Mac OS 11.5

Why are the changes needed?
This job takes 40-minutes execution time and waits in the queue over 6 hours frequently while GitHub Action jobs finish in around 20 minutes in total.

https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md

System Version: macOS 10.15.7 (19H1323)

https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md

System Version: macOS 11.5 (20G71)

How was this patch tested?
Pass the CIs.

This is a backport from 1.7 to 1.6. Since this should run GitHub Action MacOS runners, I made a PR to see the result instead of cherry-picking.


Found mismatching block problem

[Info] Detected a performance problem. Decoding might take longer than necessary. Please consider opening a performance bug report with a reproducing compressed file. Detailed information:
[Info] Found mismatching block. Need offset<PHONE_NUMBER> B 0 b. Look in partition offset:<PHONE_NUMBER> B 0 b. Found possible range: [1660949494 B 0 b,<PHONE_NUMBER> B 0 b]
[Info] Detected a performance problem. Decoding might take longer than necessary. Please consider opening a performance bug report with a reproducing compressed file. Detailed information:
[Info] Found mismatching block. Need offset<PHONE_NUMBER> B 0 b. Look in partition offset:<PHONE_NUMBER> B 0 b. Found possible range: [8921292099 B 1 b,<PHONE_NUMBER> B 1 b]
How to solve？

The most helpful would be if you could send me the gzip file that lead to this error or even only the megabyte around the problematic offsets. But in general, you can simply ignore it if there are only one or two of these warnings or if it decompresses sufficiently fast. In the future, I might completely hide this warning for release versions.

Thank you for your reply, but I’m sorry I cannot send the file to you. Could this be caused by multi-core? I used 60vcpu. Also, there are many warnings, but the decompression speed is very fast.

Yes, it should be a purely multi-core issue. It shouldn't happen for single-core decompression with -P 1.
Let me try to explain when this warning appears: For parallel decompression, each thread starts decompression at a different position inside the file. However, to succeed, they need to find valid start positions. In some cases, they might find something that did look like a valid start position but it isn't actually one. In these cases, the main thread can detect this and will have to decompress from the correct position again. The result from the wrong position will be discarded and all work done for that will have been for naught. That's why it prints a warning that performance might have been affected. The hope for that warning was, that I might be able to improve the detection of valid start positions in some of these cases. But, at the current stage of development, I think I have done almost everything that is possible to keep these cases to a minimum.
In general, the number of such warnings can be reduced by increasing the chunk size. E.g., you could try with rapidgzip --chunk-size $(( 16 * 1024 )) .... However, this also will increase the amount of used memory.

Thank you for your answer. Since I am busy with other things, I will test and modify the chunk size later. I compared the decompressed file with the source file and they are the same

I have hidden this informational message in default usage, therefore I will close this issue because I cannot reproduce it. It will still appear when --verbose is specified. Note that there also is a --verify option that computes and compares the CRC32, also in parallel. It still has a 10% overhead. Maybe I will make it default at some time in the future, when "performance" isn't my main goal anymore. In some aspects, I/O already is the bigger issue. It will be hard to write out 20+ GB/s to anywhere. Only when rapidgzip is used as a library in a kind of preprocessing step, do these speeds make sense.

I have actually found a file where this would happen.  One of the speculative decompression threads seems to have found the stream of the original .tar.gz file inside the outer gzip stream and then was able to decode 4 blocks from it before it fell back to the outer gzip stream without any way to detect an error. I'm not entirely sure how the second gzip compression was done because it contains non-compressed blocks of only 8-16 kB size, which are all followed by 0-B non-compressed blocks (deflate flush markers). Anyway, rapidgzip can safely recover from this wrong decompression start and while it might slow down performance, this happens in non-compressed blocks, which "decompress" very fast.


Problem with building current sources on Windows

The build of qtwebkit fails on Windows.

Which version of PhantomJS are you using? Tip: run phantomjs --version.
Current Sources

What steps will reproduce the problem?
Follow instructions on http://phantomjs.org/build.html

Which operating system are you using?
Windows 7

Did you use binary PhantomJS or did you compile it from source?
Compile it from current source

Please provide any additional information below.

Output of the build process:
Creating library ....\bin\ImageDiff.lib and object ....\bin\ImageDiff.exp
Qt5Gui.lib(png.obj) : error LNK2019: unresolved external symbol _inflateReset referenced in function _png_reset_zstream
Qt5Gui.lib(pngrutil.obj) : error LNK2001: unresolved external symbol _inflateReset
Qt5Gui.lib(png.obj) : error LNK2019: unresolved external symbol _adler32 referenced in function _png_compare_ICC_profile_with_sRGB
Qt5Gui.lib(png.obj) : error LNK2019: unresolved external symbol _crc32 referenced in function _png_calculate_crc
Qt5Gui.lib(pngread.obj) : error LNK2019: unresolved external symbol _inflateEnd referenced in function _png_read_destroy
Qt5Gui.lib(pngwrite.obj) : error LNK2019: unresolved external symbol _deflateEnd referenced in function _png_write_destroy
Qt5Gui.lib(pngwutil.obj) : error LNK2001: unresolved external symbol _deflateEnd
Qt5Gui.lib(pngwutil.obj) : error LNK2019: unresolved external symbol _deflate referenced in function _png_compress_IDAT
Qt5Gui.lib(pngwutil.obj) : error LNK2019: unresolved external symbol _deflateReset referenced in function _png_deflate_claim
Qt5Gui.lib(pngwutil.obj) : error LNK2019: unresolved external symbol deflateInit2 referenced in function _png_deflate_claim
Qt5Gui.lib(pngrutil.obj) : error LNK2019: unresolved external symbol _inflate referenced in function _png_inflate
Qt5Gui.lib(pngrutil.obj) : error LNK2019: unresolved external symbol inflateInit referenced in function _png_inflate_claim
....\bin\ImageDiff.exe : fatal error LNK1120: 10 unresolved externals
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN\link.EXE"' : return code '0x460'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN\nmake.exe"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'cd' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'cd' : return code '0x2'
Stop.
ERROR: Failed to build PhantomJS! Building Qt WebKit failed.
The same issue was already reported here:
https://groups.google.com/forum/#!topic/phantomjs/n8XnupRLQRE

Looks like zlib is missing.

Is it missing in any dependency of the sources or do I need to put it anywhere for the build process?

I've found zlib in the following folder as 3rdparty dependency: ..\src\qt\3rdparty\zlib
Threfore it is generally available for the build process.


UX research for initial visualisations

User Personas: https://drive.google.com/drive/u/0/folders/1jeiKvf6uXMrvZjSXLgzBH399OrwCNOyK

UX research was one, and designs based on that research produced for G001 and G014, and which give us an overall direction for adding new reports


Fix _scandir bug

This PR fixes a bug in the _scandir implementation. As a result of this bug _scandir did not list files at the root_path of the file-system, when the root_path of the file-system was identical to the top-level of the GCS bucket.

This is obsolete due to #5

Closed by #5


flame_game create: No such module 'XCTest'

Description
A clear and concise description of what the bug is.
Steps To Reproduce
very_good create flame_game my_game --desc "My new Flame game"
flutter pub get
flutter run --flavor staging --target lib/main_staging.dart

Error:
Launching lib/main_staging.dart on iPhone 15 Plus in debug mode...
Running Xcode build...
 └─Compiling, linking and signing...                        648ms
Xcode build done.                                            7.9s
Failed to build iOS app
Swift Compiler Error (Xcode): No such module 'XCTest'
/Users/jeremiah.parrack/freelance/my_game/ios/RunnerTests/RunnerTests.swift:2:7

Could not build the application for the simulator.
Error launching application on iPhone 15 Plus.

Additional Context
This is on creation of a new flutter_game app using the cli
flutter --version
Flutter 3.13.9 • channel stable • https://github.com/flutter/flutter.git
Framework • revision d211f42860 (3 weeks ago) • 2023-10-25 13:42:25 -0700
Engine • revision 0545f8705d
Tools • Dart 3.1.5 • DevTools 2.25.0

Mac OS: 13.6.1

Same issue here! I see that the status is In Review but also the fix seems to be merged, any updates?

This is to be released, you can track the progress in this issue https://github.com/VeryGoodOpenSource/very_good_flame_game/issues/135

This has been resolved in Very Good CLI v0.19.0, feel free to re-open if you still encounter the issue in the latest version.

@gasparhabif if you haven't manually modified the iOs directory I recommend deleting it completely and running the command again with the same parameters. You'll be prompted on conflicts, do not overwrite what you don't want to be regenerated.

@alestiago Thanks! Although it re created some previously deleted files it worked fine 🚀


Add support for automatic negation flags

 Issue by kbknapp
Saturday Jan 14, 2017 at 02:17 GMT
Originally opened as https://github.com/clap-rs/clap/issues/815

Add a way to automatically generate flags that override (or negate) other flags. This can be done manually already, but doing so for an entire CLI can be tedious, painful, and error prone. Manually doing so will also pollute the --help output.
This proposal offers a way to automatically have these negation flags generated on a case by case basis, or across all flags in the command. This proposal also offers a way to have these negation flags listed in the --help message or hidden.
Design
A negation flag would simply take the long version of the regular flag and pre-pend no; for exmaple --follow would get a --no-follow. If a flag only specifies a short version, the no would be prepended to the short such as -L gets --no-L.
When parsing occurs, if a negation flag is found, and the negated argument was used, it functions exactly like a override that is already supported.
Functionally the following two examples are equivilant:
app.arg(Arg::with_name("regular")
        .long("follow-links")
        .help("follows symlinks")
        .overrides_with("override"))
    .arg(Arg::with_name("override)
        .long("no-follow-links")
        .help("does not follow symlinks"))

New proposal:
app.arg(Arg::with_name("regular")
        .long("follow-links")
        .help("follows symlinks")
        .overridable(true))

Concerns
There are two primary concerns with this approach.
Flags that already contian "no"
A flag which already starts with no such as --no-ignore would end up getting a double no in the form of --no-no-ignore. This actually makes sense and is consistent, but looks strange at first glance. An alternative would be to check if a flag starts with no and simply remove the no, i.e. --no-ignore becomes --ignore but this has the downside of additional processing at runtime, becomes slightly more confusing, and has a higher chance of a conflict.
Conflicting names
If a user has selected to auto-generate a negation flag, and the negating flag long conflicts with a flag already in use, a panic! will occur. Example, --ignore and --no-ignore is already defined elsewhere, and the user has selected to automaticlly generate negation flags, this will cause --ignore to generate a --no-ignore flag which already exists causing a panic!. The fix is to either not use a sweeping setting that applies ot all flags indescriminantly, or to change/remove the already defined --no-ignore flag.

Progress

[ ] Add AppSettings::GenerateNegationFlags which does the above, but automatically for all flags.

[ ] docs
[ ] tests

[ ] Add AppSettings:GenerateHiddenNegationFlags which hides all these negation flags.

[ ] docs
[ ] tests

See the discussion in burntsushi/ripgrep#196
Relates to #748

Edit: Removed Arg::overridable(bool) because this can already be done manually by making another flag.

 Comment by jacobsvante
Friday May 21, 2021 at 08:31 GMT

Great proposal @kbknapp. Having a --no-* equivalent just feels natural when it comes to boolean values.
Perhaps this could even be the default, considering that v3 is still in beta? The user would then have to call .overridable(false) instead to get the old behavior.

 Comment by pksunkara
Friday May 21, 2021 at 13:26 GMT

Not all single flags are need overridable flags. From looking at the clis, this is a minority use case. Which is why this won't be a default behaviour.

 Comment by Emerentius
Tuesday Jun 08, 2021 at 18:21 GMT

It's actually quite useful if all flags have negation flags because you can effectively switch the default of a flag via aliases or wrappers without hardcoding the behavior, because the user can still override the choice.
It even works with nested wrappers.
For some prior art, the very popular python command line argument library click pushes users to always define a positive and a negative flag (but allows having just one):
https://click.palletsprojects.com/en/8.0.x/options/#boolean-flags

 Comment by Mange
Tuesday Jun 08, 2021 at 18:28 GMT

I usually also always add a no variant for almost all my options, but it's that little "almost" that make me not want this to be automatic. If there was a simple opt-in argument you could set (toggleable(true) maybe?) then that would be enough for me.

 Comment by epage
Thursday Jul 22, 2021 at 08:39 GMT

Random thoughts:

I don't think I normally see --no-L.  Instead what I tend to see is either no short form or toggling of the case (e.g. -l vs -L).  Having this be different makes this a bit more complicated.
Sometimes I want the no format to be the default, so I'd want the no- prefix stripped.

 Comment by mkayaalp
Monday Nov 15, 2021 at 06:29 GMT

There are also instances of complementary flags using +/- as their prefix. Aside from the bash shopt and Xwayland mentioned in #2468, xterm and set (shell builtin) have many such options:
usage:  xterm [-/+132] [-/+ah] [-/+ai] [-/+aw]
    [-/+bc] [-/+bdc] [-/+cb] [-/+cjk_width] [-/+cm] [-/+cn]
    [-/+cu] [-/+dc] [-/+fbb] [-/+fbx] [-/+fullscreen]
    [-/+hm] [-/+hold] [-/+ie] [-/+im] [-/+itc]
    [-/+j] [-/+k8] [-/+l] [-/+lc] [-/+ls] [-/+maximized] [-/+mb]
    [-/+mesg] [-/+mk_width] [-/+nul] [-/+pc] [-/+pob] [-/+rv]
    [-/+rvc] [-/+rw] [-/+s] [-/+samename] [-/+sb] [-/+sf]
    [-/+si] [-/+sk] [-/+sm] [-/+sp] [-/+t] [-/+u8] [-/+uc]
    [-/+ulc] [-/+ulit] [-/+ut] [-/+vb] [-/+wc] [-/+wf]
    <omitted other options>

set [--abefhkmnptuvxBCEHPT] [-o option-name] [argument …]
set [+abefhkmnptuvxBCEHPT] [+o option-name] [argument …]

 Comment by epage
Monday Nov 15, 2021 at 14:35 GMT

Though that is a whole different argument scheme and is more related to #1210, especially with my comment.
However, that also points out the general challenge with trying to support automatic negation flags: there are a lot of different styles. I think the most important thing is we don't get in the way of people writing their CLI, even if it requires more boiler palte.  After that is us making the core workflows and common / best practices easy to take advantage of.  I think we should define the scope of what kind of automatic flags we support and limit ourselves to that or else I fear it'll either be too complicated by supporting all types or won't be present for anyone.


Dead link

Change link to use an archived version.

Hi there;
I'm writing this message to let you know that, LineageOS doesn't merge pull
requests submitted directly to their github.com repositories.
You can submit your change requests through their public review system,
located at http://review.lineageos.org/
That review system is an installation of Google's Gerrit code review.
Thanks!

Hi there;
I'm writing this message to let you know that, LineageOS doesn't merge pull
requests submitted directly to their github.com repositories.
Thanks!

Allright. If someone of the maintainers could fix the dead link, that'd be great. :)
CC: @barryclark @zifnab06 (I saw your names in the commit log)

Thanks for the PR - Gerrit cherry-pick here https://review.lineageos.org/#/c/153988/


fix: renamed base_objects to core

What did you fix?
Fixes the OPtional "spamming" on events that have actications and expiries. The calculations are now done internal and do not rely on the API.

Reproduction steps

Evidence/screenshot/link to line

Considerations

Does this contain a new dependency? [No]
Does this introduce opinionated data formatting or manual data entry? [I don't think so?]
Does this pr include updated data files in a separate commit that can be reverted for a clean code-only pr? [Yes, should]
Have I run the linter? [No]
Is is a bug fix, feature request, or enhancement? [Bug Fix/Feature]

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

v0.3.3
GitHub release

Your semantic-release bot :package::rocket:


Recipes picks failed build when running CQ

Example CL: https://flutter-review.googlesource.com/c/recipes/+/42520
CQ: https://ci.chromium.org/ui/p/flutter/builders/try/recipes-with-led/b8782893379009124769/overview
It picked a failed try run from refs/pull/2644/head:
https://ci.chromium.org/ui/p/flutter/builders/try/Mac device_doctor/316/overview
and caused the whole CQ failed

Obsolete.


This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /home/deck/.local/share/icons/Tela/scalable/apps/image-missing.svg: Unable to load image-loading module: libpixbufloader-svg.so: libpixbufloader-svg.so: cannot open shared object file: No such file or directory (gdk-pixbuf-error-quark, 5)
Bail out! Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /home/deck/.local/share/icons/Tela/scalable/apps/image-missing.svg: Unable to load image-loading module: libpixbufloader-svg.so: libpixbufloader-svg.so: cannot open shared object file: No such file or directory (gdk-pixbuf-error-quark, 5)
Aborted (core dumped)

the crash happens when i generate a invite link or try to invite a friend.

tried to build the app with opensuse on distrobox and you doesnt list your dependency  with wxwidgets, and I get this error i do not know how to resolve
CMake Error at RemotePlayWhatever/CMakeLists.txt:97 (file):
  file failed to open for reading (No such file or directory):

    /etc/issue

CMake Error at RemotePlayWhatever/CMakeLists.txt:98 (string):
  string sub-command REGEX, mode MATCH needs at least 5 arguments total to
  command.

Even trying to compile this pr ##57, it still gives me the regex error.

doesn't run on debian either
─deck🎉debian─ ~/Downloads
 └$ sudo apt install -y ./RemotePlayWhatever-0.2.4-Linux.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'remoteplaywhatever' instead of './RemotePlayWhatever-0.2.4-Linux.deb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 remoteplaywhatever : Depends: libwxbase3.0-0v5 (>= <IP_ADDRESS>+dfsg) but it is not installable
                      Depends: libwxgtk3.0-gtk3-0v5 (>= <IP_ADDRESS>+dfsg) but it is not installable
E: Unable to correct problems, you have held broken packages.

I'm on Fedora 37 and I'm also getting the same error.
(remoteplaywhatever:13911): Gtk-WARNING **: 11:03:32.712: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /home/steven/.icons/my-icons/actions/16/image-missing.svg: Unable to load image-loading module: libpixbufloader-svg.so: libpixbufloader-svg.so: cannot open shared object file: No such file or directory (gdk-pixbuf-error-quark, 5)
Bail out! Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /home/steven/.icons/my-icons/actions/16/image-missing.svg: Unable to load image-loading module: libpixbufloader-svg.so: libpixbufloader-svg.so: cannot open shared object file: No such file or directory (gdk-pixbuf-error-quark, 5)
[1]    13911 IOT instruction (core dumped)  ./RemotePlayWhatever-0.2.4-x86_64.AppImage

Also trying to build the app as well but I'm getting an error saying wxWidgets is not found even though I think I installed the right package...
I'm using the rpm version of Steam as well, as I saw in another thread that flatpak versions may not work.


Macro implementation when using triggers is not working

This works:
discoveredDist <<= (dist in ReactiveRuntime).storeAs(discoveredDist in Global).triggeredBy(dist in ReactiveRuntime)

however this doesn't:
discoveredDist := (dist in ReactiveRuntime).storeAs(discoveredDist in Global).triggeredBy(dist in ReactiveRuntime).value

Minimal repro:
// build.sbt
val hello = taskKey[Unit]("hello")
val world = taskKey[Unit]("world")

hello := println("hello")
world := println("world")

world := (world triggeredBy hello).value // prints "hello", should print "hello\nworld"

// world <<= world triggeredBy hello // works

It seems this issue is only incidentally related to the macro expansion. The code that is generated when this expression is expanded:
world := (world triggeredBy hello).value

in the end happens to be similar to:
world <<= ((world triggeredBy hello) map ( a => a ))

In the latter expression, the triggeredBy for some reason gets ignored; that happens on 0.12.x as well. I'm doing some debugging now.

old logic
If we consider a task to consists of two parts, value function and an attribute list, the existing behavior is defensible. <<= binds both the parts to the LHS task key whereas := creates a brand new task using the given value and a blank attribute list.
In that logic,
world := (world triggeredBy hello).value

is not much different from
world := {
  val x = (world triggeredBy hello).value
  123
}

or
world := 123

Functor law
The part that starts to break down is map.
The first functor law states that mapping with identity should not modify the original functor.
See also http://eed3si9n.com/herding-cats/Functor.html
It might not be strictly enforced, but the law matches the intuitive feel people on the standard collections too.
new ideas?
Even though it's forgetful focusing only on the value using := is very valuable in flattening the learning curve of sbt.
One workaround might be to track triggers as a separate key:
onComplete in hello += world

This would move the trigger as if they are values, and at the end of the loading we can put them to the appropriate task attributes.

Is there a workaround to this issue that will achieve the same behavior without triggering a deprecation warning in sbt?

@dwijnand 👍

This fix is not available on 0.13.x yet, right?

It's available in 0.13.14-RC1.

thanks, worked fine with that version :)

Hi, this does not seem to be fixed for me:
refreshBrowsers <<= refreshBrowsers.triggeredBy(WebKeys.assets in Assets)

works, while
refreshBrowsers := refreshBrowsers.triggeredBy(WebKeys.assets in Assets)

does not.
sbt.version=0.13.15

Project source: https://github.com/woost/wust2/blob/dff8fdcdd13d39dfaf51e61b9ec251b99d1e619c/build.sbt#L232
Do you need more information?

Did you miss '.value' intentionally in the code snippet that uses :=?

Good catch! That was not intentional, it works with .value. Thank you!
It's strange though that I didn't get a compile error...

It's because the expected Unit discards value, so it didn't catch the lack of .value invocation.

Hi to all, I have tried with :
compile in MultiJvm := ( compile in MultiJvm ).triggeredBy( compile in Test ).value
instead of:
compile in MultiJvm <<= ( compile in MultiJvm ) triggeredBy ( compile in Test )
But doesn't works

Which sbt version?

Sorry, 0.13.13

This thread says that the fix for triggeredBy is only available in 0.13.14. You need to update.

Sorry, you're right.

// Here is a snippet that might  help those that
// have had the same problem and need  some example code showing a
// brief solution that works

sbt sbtVersion
[info] 1.0.2

Within build.sbt

lazy val copyDocAssetsTask = taskKey[Unit]("Copy doc assets")
target in Compile in doc :=  baseDirectory.value /"public/wiki"
copyDocAssetsTask := {
println("Copying doc Images")
val sourceDir =  baseDirectory.value / "extra-resources"
val targetDir = (target in (Compile, doc)).value
val targ = targetDir / "/extra-resources"
println("From "+ sourceDir)
println("To "+ targ)
IO.copyDirectory(sourceDir, targ)
}
copyDocAssetsTask := (copyDocAssetsTask triggeredBy (doc in Compile)).value

call doc

sbt compile doc
[info] Main Scala API documentation successful.
Copying doc Images
From /root/fogcomput/code/Appliance/fogcomputlabs/extra-resources
To /root/fogcomput/code/Appliance/fogcomputlabs/public/wiki/extra-resources

Thanks to  all on thread for doing the hard work.


Fix deleting and switching AOIs

This PR fixes some issues and improves the app behavior when creating/editing/deleting AOIs, contributing to the following issues:

#53
#55
#59

I suggest testing several combinations of new and existing projects with 0, 1, or many AOIs. Some suggested scenarios:
Scenario 1:

Load an existing project that has no AOIs
Draw a new AOI
Delete the newly drawn AOI
The imagery source should then be displayed

Scenario 2:

Load a project with multiple AOIs
Delete the current AOI
The prediction layer should then become visible

Scenario 3:

Load an existing project that has one AOI
Delete the existing AOI
Draw a new AOI
Select a timeframe
Run the prediction
Ensure the action buttons are correctly displayed

Scenario 4:

Load project with multiple AOIs
Switch between AOIs, prediction layer should load fine
Remove all AOIs, add a new AOI, remove it again, add again, and run prediction

@geohacker @LanesGood this is ready for review. Please let me know if you need a configuration file to run this locally using the staging AOI.

@vgeorge I'm having a difficult time testing with the instance being quite slow to restart between runs. I'll update my comments below when each test is done.
Scenario 1 - I can confirm the testing behavior works as described. When you write Imagery source should then be displayed - are you referring to the actual text in "Imagery source," or do you mean the image tiles should be displayed on the map? My experience with the Sentinel imagery is that image tiles are not displayed, just the imagery basemap, and I need to re-set the base mosaic.
Scenario 2 -
Scenario 3

@LanesGood thanks for the review! About your questions:

Scenario 1: I was refering to the text in the prime panel, the base layer behaviour is expected
Scenario 3: Yes, I was refering to 'Run live prediction' button
I confirm the placeholder "Class distribution metrics are not available" is appearing after a prediction run, I'll open a ticket to track it

It seems we are good to merge this.

I didn't noticed this was still pointing to add/select-mosaic branch and fixed it by merging it manually to develop.


Convert HTMLElement and friends to classes to support Web Components/Custom elements

Please model HTMLElement and its subclasses as classes instead of interfaces in lib.d.ts to make it possible to subclass them.
My motivation is custom elements and web components. To create a custom element you need to create a subclass of HTMLElement and register it with the browser. Currently, HTMLElement etc are interfaces and can't be subclassed. I've been using a hacked lib.d.ts in my pet TypeScript project which uses web components.
Tutorial and info about how to use custom elements is here: http://www.html5rocks.com/en/tutorials/webcomponents/customelements/

Any update on this? Is there a clean way to write custom elements in TypeScript at the moment?

Any update on this one?

We have a few suggestions to make this work.. we first need #2961, #2959 and possibly,
#2957 to make the change to the library..
Also related #2341 to ensure native types with uncallable constructors are modeled correctly, e.g. Symbol or HTMLElements.
#1168 tracks doing the same for non-DOM native types.

:+1:

This is a killer. with babel/ES6 I can easily do the following to create a WebComponent:
class MyComponent extends HTMLElement {

}

But in TypeScript it complains that I can't extend because HTMLElement is not a class. It is indeed a class.

This should be fixed in TypeScript 1.6

Also see #1168.

This can be closed thanks to : https://github.com/Microsoft/TypeScript/pull/3516 just tested this with<EMAIL_ADDRESS>class MyComponent extends HTMLElement {
}

With the change to allow extending expressions (#3516), there is no need for the definition in the lib.d.ts to be classes. we could reconsider and change the, to classes in the future.

Can you review the above reference to make Polymer more typescript friendly please, I think nippur72 has everything covert but I would appreciated it to confirm we are going in the right direction.

I think I am missing something but even though you can now extend HTMLElement I can't seem to actually use it. This is because of the constructor issue, Typescript forces all derived classes to call super and that will throw an error on HTMLElement.
I am getting a 'Illegal constructor' error thrown anytime the class is created.

@aphex: HTML elements should not be instantiated with new, but with document.createElement().
The fix for this issue is important because it lets you have the whole HTMLElement interface in your subclass, enabling intellisense and all the rest. Good for working with WebComponents.

@nippur72 I understand that, and actually thats the exact situation I am trying to use this in. Applying a class for a web component. The issue is the compiler throws a warning that the 'constructor is illegal' because it is not calling super.
There seems to be a requirement that derived classes call there parents constructors.
I am looking to make classes that are truly HTMLElements, in the sense that the extend them, not just composite or decorate one.

@aphex unfortunately WebComponents doesn't work with instances of HTMLElement, but only with plain javascript objects (that are later mixed to a HTMLElement). That is the source of the problem.
So all you can do is to simulate that these objects are extensions of HTMLElements, in order to have IDE integration (intellisense, static typing etc). But it's just a trick. You might want to check PolymerTS which indeed does the above mentioned "trick".
Also consider that in order to make a HTMLElement work with the DOM, it has to be created with document.createElement() and not with new (as far as I know). So I'm afraid your goal of making "true" HTMLElements can't be achieved.

@nippur72 Actually thats not the case at all, I have all the working code for this already the only problem i am having is the warning from TS compiler. You can also create an element in markup, createElement doesn't have to be in the mix at all.
In Javascript an instance (Class or not) of something is just an object, everything is just an object :)
The concept is pretty straight forward. Simply define a class that extends HTMLElement, create that class (new ClsName)  and use that instance as the proto of the registered element. Merge in a a little createdCallback magic and you can get WebComponents working very well with classes, and extending anything (including HTMLElement). The benefit here is I get all that code completion and such because of the IDE's understanding of inheritance.
I am using a similar method as Polymer to rip out a template and CSS its just instead of having to include it all in one place you can separate everything.
Just because at the end of the day the WebComponent needs to be portable and deliverable in a nice packed file it doesn't mean we need to develop that way. Thats what Gulp is for, at least I don't think so :)
So essentially the help I need is making it so typescript understands there are some Classes that do not require constructors being called, I just wanna get rid of this dang warning. If I extend HTMLElement I simply want to skip its constructor and only call my own.

@aphex what doesn't convince me is the fact that WebComponents doesn't use directly the object-prototype you feed it. As far as I know, WebComponents creates its own instance of HTMLElement and then extends it with members from the object you passed to it. So your efforts to give it an HTMLElement are ignored.
I agree 100% about the missing super() call warning, I wish too there was a way to tell the class doesn't need to call to constructor. Is there an open issue about it?

@nippur72 Thats very interesting, so technically they are always going to extend HTMLElement. So really there is no need for a class to extend HTMLElement at all if it is going to be a WebComponent, except for code completion in the IDE.
So if it is being used as an interface how is that working? In order for it to be an interface wouldn't one need to make all the methods and such from HTMLElement? In the case of 'MyClass implements HTMLElement'.
This of course changes my whole mentality on what I was building :) probably unneeded for me to deal with HTMLElement inheritance.

I agree 100% about the missing super() call warning, I wish too there was a way to tell the class doesn't need to call to constructor. Is there an open issue about it?

@nippur72 do you mind filing an issue for this.

@mhegazy I changed my mind a bit regarding super(), so I've opened this other issue: #5910
Btw, regarding this original issue, HtmlElement is now a variable and can be used with the feature or "extending expressions".

i think they should all be classes... eventually.

I just ran into this issue as well. The problem is, that people are mislead somehow, because they see the examples on MDN or on Custom Elements spec - working draft, where it is suggested to create an instance of the new, own webcomponent like this:
var myBtn = new MySaveBtn;
document.querySelectoe('#placeholder').appendChild(myBtn);

Or from the working draft: "Finally, we can also use the custom element constructor itself. That is, the above code is equivalent to:"
const flagIcon = new FlagIcon()
flagIcon.country = "jp"
document.body.appendChild(flagIcon)

So, the need for a non-callable constructor is there! For the moment I just put the super call into a try-catcher:
constructor(ViewFarm:IViewFarm,ViewPatched:IMultiViewPatched) {
  super(ViewFarm,ViewPatched);
  ...
}

Okay, for others, who struggle with this as well... The MDN source seems to reflect the current way it is implemented by webcomponents.js and chrome is, that document.registerElement returns a constructor, which you then can use to call:
class FooElement extends HTMLElement {
  ...
}
const FooElementCtor = document.registerElement('element-name',FooElement);
const FooInstance = new FooElementCtor();
document.querySelector('body').appendChild(FooInstance);

Just in case anyone else struggles with this... Using the constructor of FooElement directly will throw an Invalid Constructor-exception. As I generate the DOM completely programatically, I do not use the element-name as tag at all, but it probably has to be a valid tag name containing at least one dash - - character. The example as shown above works for me.
However, the W3C draft as of 24 June 2016 assumes, that calling the constructor directly may be supported in future, or it is just an error in the spec.

Reading the "What's New" for 2.1 there seems to be some new feature for working with Custom Elements but i don't seem to be able to locate any example of it's usage

i think they should all be classes... eventually.

Is there any blocking problems not to do this now? Microsoft/TSJS-lib-generator#222

I think we should add classes regardless. that is covered by #574

@mhegazy You mean you will accept a PR for this?

I think we would. my concerns would be back compat. so we will need to run the new chance on DT, and on our internal test suite to make sure there are no breaks we are not aware of. if all passes, do not see why we can not take the change.

Hmm, DT will be a best place for a first PR then 😃

Hmm, DT will be a best place for a first PR then

Not sure what you mean? i meant make the change to https://github.com/Microsoft/TSJS-lib-generator, build a custom TS version with the new library, then compile all DT types with the custom TS drop. ideally you should not see any errors.

I thought you would publish a new lib.d.ts on DefinitelyTyped and get user feedback. My misunderstanding.

It seem like I can write this kind of code (see below) which seems to behave as if HTMLElement and its friends are classes.  I have to call them as "new MyDiv();" instead of "new HTMLDivElement()", but it seems as if the library that gives me "HTMLDivElement" could have done this for me.   Why shouldn't Typescript change the semantics of "document.createElement("foo") and HTMLFooElement" into something more Typescript-like.  The language is all about changing javascript semantics.
export class MyDiv extends HTMLDivElement {
   constructor() {
    try {
        super();
    }
    finally {
        return document.createElement("div") as HTMLDivElement;
    }
  }
}

export class MyInp extends HTMLInputElement {
  constructor(value: string) {
    try {
        super();
    }
    finally {
        const x = document.createElement("input") as HTMLInputElement;
        x.value = value;
        return x;
    }
  }
}

export class TestElement extends HTMLElement {
   constructor() {
    try {
        super();
    }
    finally {
        let x = new MyDiv();
        let inp = new MyInp("xyzzy");
        x.appendChild(inp);
        return x;
    }
  }
}

I'm trying to put together a definition for github/query-selector  but I'm unable to use the generic type on the klass parameter because of how Element, HTMLElement, etc. are typed. For now I'm having to use any which isn't really ideal.
declare module '@github/query-selector' {
    type Queryable = Document | DocumentFragment | Element;

    export function query<T extends Element = Element>(context: Queryable, selectors: string, klass?: any): T;

    export function querySelectorAll<T extends Element = Element>(context: Queryable, selector: string, klass?: any): Array<T>;
}

Are Element etc. going to be changed to classes so scenarios like this work?

Not to necro, but is there something I'm missing here?  This is a fairly standard interface by now, and not having typings for connectedCallback, attributeChangedCallback seems like an odd oversight (especially with the popularity of web components).
Everything else related to this seems to be typed, such as ShadowRoot & co.
I would have assumed that this would have been implemented via some sort of CustomHTMLElement-esque interface that types all the standard WC methods, like so:
interface CustomHTMLElement {
  connectedCallback?(): void;
  disconnectedCallback?(): void;
  adoptedCallback?(): void;
  attributeChangedCallback?(name: string, oldValue: string, newValue: string): void;
}

Is this a deliberate omission, or have the TS team just not got around to it yet?
Is it outside the scope of lib.dom.d.ts?
Re: DefinitelyTyped, I've searched the codebase and all I can find are
a bunch of re-implementations of the same interface as above.
If this is a separate issue, I'm happy to post it as such -- this is the closest related issue
that I could find here.


Docker additions

The end goal is to have this site up in docker containers running docker compose. To do that, two container containing the web server and database respectively will need to be created along with a volume for the database contents.

Added.


One kill counts as 7

Same with deaths. When someone dies or is killed the plugin counts it as 7 kills/deaths.

What other plugins do you have ? This sounds like another plugin is faking an Event.


OUT_OF_RANGE : timeout beetween requests

Hello, I'm trying the "Translate from file" sample code with a small 10 seconds audio, .wav, LINEAR16 file, 1.2Mo, fr/FR to en/US.
When I launch code, I have empty "translation" and "source" in the system output, and sometimes after one dispay of "Partial translation: " and "Partial recognition result: ", sometimes 2 or 3 times, it crashes with this error :
Exception in thread "main" com.google.api.gax.rpc.OutOfRangeException: io.grpc.StatusRuntimeException: OUT_OF_RANGE: Timeout between requests
I have a fiber connection (1Gbs/600Mbs, 6ms ping on Speedtest), and the TTS and translate API are working fine so I don't understand where can a timeout happen :| .

Found the problem : my .raw audio was bad, I made a new one and the sample code is now working.


MAINT: Bump to 1.1

This won't work until @drammock cuts a 1.1.0 release on Github, conda-forge updates the feedstock, and then the CDNs update, but in the meantime I wanted to set this up so it's ready to go (restart CIs then be green hopefully!).
@hoechenberger feel free to review to make sure this is reasonable. I changed some =0.3.1 to ~=0.3.1 since it seems like we should be okay with newer patch releases being installed, right?

@larsoner With #148 I changed the way we specify versions, that is, I think it makes sense to use explicit pins to one specific version (as in contrast to pinning to all compatible versions)
This ensures that all version specifications are now very explicit. Thanks to that small script I've added, it's now simple to check whether anything is outdated.
I would therefore prefer if you could roll back the changes to pinning you're making in this PR, unless you have some convincing ideas as to why it's the better way?

unless you have some convincing ideas as to why it's the better way?

Generally patch releases fix bugs, so we're potentially missing out on bugfixes. But being able to check versions is nice so I'll roll it back

Btw I just realized my script doesn't check the version of Python


Support for Return to Monkey Island

Hello there!
Over the past few days I have implemented basic support for RtMI's .ggpack?? files into Thimbleweed Park Explorer.
(New XOR Keys 256 + 65536 bytes long).
The GGDicts contained in this the .json files and RtMI's .yak files both seem to differ from the previous formats.
It would be nice if at least the ggpack tool could support RtMI - The new XOR-algorithm can be found here
(note that the Thimbleweed park explorer does not ship the XOR-keys and instead loads them from the game's executable.)

Please see: #3


Loading Diagrams from Browser results in error: Cannot read property 'setConsumer' of undefined

Preflight Checklist

[x ] I agree to follow the Code of Conduct that this project adheres to.
[ x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
I attempted to load diagrams by going to File -> Open From -> Browser but was prompted with the error message:
Cannot read property 'setConsumer' of undefined
To Reproduce
Steps to reproduce the behavior:

Click on File
Click on 'Open From'
Scroll down to 'Browser'
See error

Expected behavior
The diagram browser for drawings stored in the browser to pop up.
Screenshots

draw.io version (In the Help->About menu of the draw.io editor):

draw.io version 13.4.1

Desktop (please complete the following information):

OS: MacOS
Browser Chrome
Version 84

Additional context
Could this have anything to do with the domain shift to diagrams.net?

Use the latest version 13.5.3.

I can't use 13.5.3 unless I go on incognito. Reloading the page still shows 13.4.1. Any tips?

Close all browser tabs that have app.diagrams.net open. Open https://app.diagrams.net/?offline=0  in a new tab. Once loaded, close that tab. Then try opening again.


brand identity

Determine colors, themes, and other elements to use in brand.

The git guild brand should follow the theme of guilds from the middle ages, and use a heraldic shield. Examples:

The colors should be much simpler and more modern, however. Perhaps white and blue, but a lighter blue than the blue in Deginner's logo.

The imagery on the shield should represent the topic of software development. Perhaps a honey badger, or a penguin, or simply "1" and "0" on the two sides of the shield, representing binary code. Would like to see different concepts, with these different options. Imagery examples:

@mobymarto @luisvillara The brand is ready for you guys to start. Please let me know if you have questions.

@luisvillara @mobymarto what's the status on this? Can we please get it ready ASAP? I need to have it on banners for a press event in less than 1 month!

I do believe a one color logo is best. Something that can be used on Quotes and Images and still look good on almost any color background. A two color logo can work also as The Dollar Vigilante shows.

Imgur
^^^ Plain version. Chose blue as the secondary color and have more formats including SVG.


Shim the macOS futex API

Since macOS 14.4, the Apple platforms have a public futex-like interface, which we'd very much like to use in std (see rust-lang/rust#122408), but we're still missing the miri shims for it. In typical Apple fashion, they have failed to upload the full documentation to their website and have not included it in their man-pages either. Still, it exists and can be accessed either from the header file (os/os_sync_wait_on_address.h) or from its upload to their public-source repository.

Is this the same as / a replacement of https://github.com/rust-lang/miri/issues/2589?

This would make that other issue redundant, yes, although the API is different.

Well let us know then which of the APIs t-libs plans to use, ideally we won't have to implement both of them. :)

Looking at https://github.com/rust-lang/rust/pull/122408, there are quite a few functions to be supported here:
pub fn os_sync_wait_on_address(*mut c_void, u64, usize, u32) -> c_int
pub fn os_sync_wait_on_address_with_timeout(*mut c_void, u64, usize, u32, u32, u64) -> c_int
pub fn os_sync_wake_by_address_any(*mut c_void, usize, u32) -> c_int
pub fn os_sync_wake_by_address_all(*mut c_void, usize, u32) -> c_int
pub fn __ulock_wait2(u32, *mut c_void, u64, u64, u64) -> c_int
pub fn __ulock_wait(u32, *mut c_void, u64, u32) -> c_int
pub fn __ulock_wake(u32, *mut c_void, u64) -> c_int

But it also seems there's a sequence of fallbacks so we probably don't need all of them? I'll have to check how weak symbols work on macOS and how Miri can provide them -- on Linux it's fairly easy, we just have global statics of the name and fill them with function pointers. On macOS it seems to boil down to dlsym? That should be easy as well then.
So then it seems like we need just the first four ones, the ones with the "nice" names (not starting with __).

What would help is having a little test program that invokes these APIs and checks basic functionality, with the flags std needs. (Can be direct calls, it's easy to then also make them available via dlsym). Usually I use the standard library to drive the testing but that won't work this time.
We have such a test for futexes at tests/pass-dep/concurrency/linux-futex.rs


Coverage badge

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@115c3ca). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #74   +/-   ##
=========================================
  Coverage          ?   90.44%
=========================================
  Files             ?        3
  Lines             ?      670
  Branches          ?        0
=========================================
  Hits              ?      606
  Misses            ?       64
  Partials          ?        0

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 115c3ca...baa6e33. Read the comment docs.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@115c3ca). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #74   +/-   ##
=========================================
  Coverage          ?   90.44%
=========================================
  Files             ?        3
  Lines             ?      670
  Branches          ?        0
=========================================
  Hits              ?      606
  Misses            ?       64
  Partials          ?        0

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 115c3ca...baa6e33. Read the comment docs.


[FEATURE REQUEST] Hook into MMOItems

Would be great if you add support for MMOItems (https://www.spigotmc.org/resources/mmoitems-premium.39267/)
They have rich API so it wouldn't be hard to implement. Also, a lot of RPG-like servers is using it.

+1

+1 Would love to see this.

+1


Add reload() method to Eloquent

As per my earlier proposal (#5283), here is a tested reload() method for the Eloquent model. It will fetch the existing columns on the model and resync them with the original attributes.

This wan't added?

Seems like fresh() works good. In 5.2 at least.


android token issue

hi, i am using your package . if i am using in the ios this is working fine further more when i use android it is  not giving any token and redirect

@muhammadsarim555 i have the same problem, have you found any solution?

@mark-muhammad  i did not find this solution

Hi there!
I will check this, so please wait!
sorry.
FYI, please let me know your information.

OS
Device
react-native-simpel-twitter version
React Native version

@watanabeyu  WIndow 7 , expo sdk version 31 , device android LG

Mine is slightly different

OS: macOS 10.14
Device: android 5.1.1
react native: 31.0.0
react-native-simple-twitter: 2.0.2

Also, I've found that in android, callback URL was not called.

@mark-muhammad
I check it on below environment.

OS: Android 7.0
Device: HUAWEI P10 lite
react-native-simpel-twitter version: 2.2.0
React Native version(expo):v32

I can work fine.
Please check your environment working at this example.

@watanabeyu I did follow the example but still didn't work. Do you think the version I used could be the problem? If I really should update the lib, what version do you think still compatible with react native v31? Because I once used v32 but got a problem which forced me to use v31 instead.

@mark-muhammad
umm... My Android phone is work fine.
Could you show me the source code?

@watanabeyu I just updated to v2.3.0 and still didn't work. Anyway, here is my code related to the login process. What made curious is that it worked fine in iOS.
`onGetAccessToken = ({ oauth_token, oauth_token_secret }) => {
console.log("TOKEN_SET: " + oauth_token + " | " + oauth_token_secret)
}
onSuccess = (user) => {
console.log(user);
TwitterID = user.id;
Name = user.name;
Email = user.email;
this.loadAccessKeysViaTwtitter(TwitterID, Name, Email);

}
onClose = (e) => {
console.log("press close button")
}
onError = (err) => {
console.log(err)
}

<SocialIcon
title='TWITTER LOGIN'
button
iconSize={ 18 }
iconStyle={{ marginTop: -8, marginBottom: -8 }}
fontStyle={{ fontSize: 12 }}
style={{width: '90%', height: 40, borderRadius: 2, alignSelf: 'center'}}
type='twitter'
/>
`

@watanabeyu I recently found out that my callback was actually hit withquery string oauth_verifier which you used to filter here
const match = webViewState.url.match(/\?oauth_token=.+&oauth_verifier=(.+)/);
But somehow, WebView didn't read the URL, and since I have redirection in the callback, WebView recognized only the redirected URL, ignoring callback URL. Do you think it is due to how WebView in android handles redirection? Do you I should change the logic in the callback URL?

@watanabeyu Never mind. I just resend the query string which twitter sent to my callback URL to the redirection inside my callback. In short, in my callback URL, I did this
redirect($url . $_SERVER['QUERY_STRING']);
It's probably just a workaround, but if WebView in android only reads the redirected URL, I guess this is the way to go.
@muhammadsarim555 Could this happen to be your case too?
By the way, thank you for the good lib @watanabeyu

@mark-muhammad  i did not show the  **web view. ** i was just unable to get token

@mark-muhammad @muhammadsarim555
Sorry to be late to response.
I fixed webview bug, and update package v2.4.0
please use this version.


Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=471919847
https://github.com/Azure/azure-cli-extensions/commit/3bcb0df1477e27762f6756fd1cdd3da0ef2a93bf

OPS Build status updates of commit dc05bf5:
:clock10: Preparing: average preparing time is 57 sec(s)

OPS Build status updates of commit dc05bf5:
:clock10: Incremental building: average incremental building time is 12 min(s) 18 sec(s)

OPS Build status updates of commit dc05bf5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[docs] Fixed content mismatch in adding Dependency Loader #80

Closes #80

Coverage remained the same at 98.577% when pulling a025dd6f18e9a00552afbe3fff7e9786c26237ab on TheOneAboveAllTitan:issues/80 into ef2ddea81e9406a05439c0fcb342114d86d61968 on openwisp:master.


Added piped instances

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[x] Covered the code with tests (note that PRs without tests will be REJECTED)
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Adds urls for other instances of piped. I was already doing this for yt-dlp ( https://github.com/yt-dlp/yt-dlp/pull/3714 ) and I thought it was worth adding to youtube-dl too (especially after coming across https://github.com/ytdl-org/youtube-dl/issues/30820 ).
This does not offer a permanent solution to other instances but given the invidious instances are added in a similar fashion I thought a half solution was better than none
Didn't add tests as the insidious instances in the same file do not have tests, have tested and all instances work however.

Note for maintainers: This does not add Piped support, it simply redirects Piped URLs to their respective Youtube URLs (the same behaviour that youtube-dl currently uses for invidious).
See https://github.com/yt-dlp/yt-dlp/issues/3053 for more info

As piped != invidious, I'd prefer to have a separate list:
    ...
        r'(?:www\.)?hpniueoejy4opn7bc4ftgazyqjoeqwlvh2uiku2xqku6zpoa4bf5ruid\.onion',
    )
    _PIPED_SITES = (
        # piped instances from https://github.com/TeamPiped/Piped/wiki/Instances
        r'(?:www\.)?piped\.kavin\.rocks',
        r'(?:www\.)?piped\.silkky\.cloud',
        r'(?:www\.)?piped\.tokhmi\.xyz',
        r'(?:www\.)?piped\.moomoo\.me',
        r'(?:www\.)?il\.ax',
        r'(?:www\.)?piped\.syncpundit\.com',
        r'(?:www\.)?piped\.mha\.fi',
        r'(?:www\.)?piped\.mint\.lgbt',
        r'(?:www\.)?piped\.privacy\.com\.de',
   )
   ...
                            %(invidious)s|
                            %(piped)s
   ...
                     $""" % {
        'invidious': '|'.join(_INVIDIOUS_SITES),
        'piped': '|'.join(_PIPED_SITES),
    }

In the end I'd rather refactor in line with my comment, but this is OK for now.

Is it really necessary to have r'(?:www\.)? spammed by having every single one as its own item ?

You mean s/t like this, with appropriate deletions in _PIPED_SITES?
        'piped': '|'.join(r'(?:www\.)?' + x for x in _PIPED_SITES),

Or maybe the whole https:// branch of the pattern should have (?:www\.)? and any domains that don't allow a www. prefix should be prefixed with (?<!www\.)? Who knows what the performance implications of these choices are?

Nah, just do it in RegEx, and TBH I don't see any point in regarding whether the site currently accepts/uses a www. since that part usually doesn't matter to ytdl anyway.


Try using Sentry

Link that might come in handy:

https://docs.sentry.io/platforms/dotnet/guides/extensions-logging/
https://docs.sentry.io/platforms/dotnet/guides/serilog/

Does not really work the way I want it :(


docs: request for triager role for Helio Frota

I have read and understood the project's Contributing guide.
I also have read and understood the process and best practices around Express triaging.
I will help in any way and no particular preferred area of interest yet.
I request for a triager role for the below orgs:
jshttp
pillarjs
express

Roles added and merged in a6aa335c


Upgrade to operator sdk 1.5.0

This builds now. But seeing a functional issue with certificate watchers:
2021-04-01T14:21:21.501Z        INFO    controller-runtime.certwatcher  Starting certificate watcher
E0401 14:21:21.503990       1 leaderelection.go:321] error retrieving resource lock openstack/576d6738.openstack.org: leases.coordination.k8s.io "576d6738.openstack.org" is forbidden: User "system:serviceaccount:openstack:default" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "openstack"

the latest push seems to functionally work great on OCP 4.7


[FB] [PI-3478] Fix resolve free flip of src/tgt mapping

This PR fixes the case where free dimension flipping of the src to tgt mapping was not constrained to the case of src and tgt cubes of equal dimensionality.
Testing will follow as a separate task, as per all new code introduced for the cube arithmetic over-haul.

@rcomer Awesome, thanks 🤟


Use Kusion WebIDE to provide quick start experience

Enhancement
Advantages of the WebIDE (vs local IDE)

For new users' quick start & playground: Since the installation and the Prerequisites to run the quick-start case and play with kusion are inconvenient for the newly attracted user, webIDE with all the kusion components out-of-box is a good choice.
For daily use of developing: the web IDE with bundled Kusion environment could be a fair choice, since it has natural advantages for the uniform environment and sharing code through the team, etc.

Technical feasibility analysis
There are several web IDE products, which have the ability to provide both the online-coding and a container created from the custom image:

github.dev (paid version)
ant group's cloud IDE commercial version
todo, others

I‘ve verified the feasibility through Antgroup's cloud IDE, and here's the result:

The IDE will be firstly released next month.
The IDE will provide a VS Code style coding interface.
The IDE can start a workspace with a running container, which can be used to run kusion commands and we already have the kusion image.
The IDE provides 50 hours of free usage per month for each device. And with 2C4G resources provided freely.
The container has access to the internet, so applying resources to AWS/Aliyun/... is accessible, users only need to do some configurations to upload the kubeConfig file to the workspace.
For users without an account of cloud providers, the lightweight k3s can be built-in to the kusion image to provide a quick try.

2022.11.7 goals
•user can try kusion quick start without any environment pre-request
•user can deploy a sample application with several button clicks without leaving IDE
•user can successfully complete kusion quick start in less than 5min
break down the goals

No need to download and install kusion: with kusion image provided in the webIDE
No k8s environment required: for users without an account to the public cloud, provide a built-in k3s cluster within the image
No need to configure the k8s cluster: it is configured by default in the image
No need to write code from scratch: provides complete code that can be and opened and run directly with a link
No need to type commands for typical operations: recognize project/stack; encapsulate kusion compile, apply, watch
Beginners can quickly know how to use: provide wizard
Easy to repeat the operations: After the first try, users can sync their configurations by a single click

Make Kusion quick-start & playground super easy @chai2010 @SparkYuan @Peefy, gogogo:)

For github.dev webIDE, we need to provide a DevContainer to quickly start up a kusion & minikube dev environment: https://github.com/KusionStack/kusion/issues/163

a good ref: rust provides a remote codespace for users to try rust: https://github.com/microsoft/vscode-remote-try-rust

github codespace now supports personal use with 200 free core hours of computing usage and 15.00 GB-month storage usage.
billing: https://docs.github.com/en/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces
GitHub Codespaces for personal accounts FAQ: https://github.com/orgs/community/discussions/38697
Making the most of your included free Codespaces usage: https://github.com/orgs/community/discussions/39697

gitpod as webIDE: https://www.gitpod.io/docs/introduction/learn-gitpod/gitpod-yaml


can't run service worker

Short description of the problem:
I updated Ionic 2, codova and the app-scripts to the latest versions and when I un-commented the service worker block in index.html file, I get this error: "Uncaught SyntaxError: Unexpected token )" on line 27 in index.html file, and right after it, this error: "Uncaught TypeError: Cannot read property 'insertBefore' of null".
It seems to me that maybe index.html and serice-worker.js aren't transpiled (when I used es5 code in index.html file, there wasn't an error in index.html file, but there was in service-worker.js file).
What behavior are you expecting?
That the service worker will run correctly.
Steps to reproduce:

run "ionic serve" from the project folder
go to the project home page in the browser

**Which @ionic/app-scripts version are you using?**
@ionic/app-scripts@latest

@MoranF,
I'm not sure I'm following. Is this still an issue? I'll reopen if so.
Thanks,
Dan


Set the font-size for multiple heading elements

What's wrong with this lesson ,I added the font-sizes for all the elements but it keeps telling me that my h5 and h6 font-sizes are wrong
https://learn.freecodecamp.org/responsive-web-design/applied-visual-design/set-the-font-size-for-multiple-heading-elements

Describe your problem and - if possible - how to reproduce it
Add a Link to the page with the problem
Tell us about your browser and operating system

Browser Name:
Browser Version:
Operating System:

If possible, add a screenshot here

@aydinulusoy I am able to pass this test. I will be helpful if you can attach a screenshot containing your code and the test result.

Hi @aydinulusoy
There is nothing wrong with this challenge. I was able to pass this challenge.
Please either attach a screenshot of your code here or post your code here.

Thank you for reporting this issue.
This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the “Help” button on the challenge on freeCodeCamp, which will take you to the help chatroom for that specific challenge. You can also view our full list of official chatrooms.
If you think I’m wrong in closing this issue, please reopen it and add further clarification. Thank you, and happy coding.


stream_popover: Convert module to TypeScript

One comment, otherwise lgtm, feel free to merge after fixing/verifying that detail.


File API rename folder errors out

Describe the bug
The /file API has a PUT method which renames a folder by passing in the filename inside a JSON object. Currently it errors with a Jackson deserialisation exception.
To Reproduce
Steps to reproduce the behavior:

Run FileApiTest - testEverything
See error

Platform:

OpenEquella Version: 2018.2

Hey @doolse
Is this done with #698 ?

Yep, oops missed out the ref in the description

Probably a bit late to backport now, and it's been tested, so let's close.


Raise exception on missing augeasproviders_core

People who manage their code with r10k have to resolve dependencies by
hand (or using a generator), as such we now helpfully raise an exception
when miaugeasproviders_core is missing.

Coverage increased (+0.004%) to 99.074% when pulling 60d0312cce3cfcbec100c9398a2faceb8df888eb on igalic:core_dep into 670e8eb3df1297735da50d1ff5ec10c547acf00c on hercules-team:master.

Coverage increased (+0.004%) to 99.074% when pulling 60d0312cce3cfcbec100c9398a2faceb8df888eb on igalic:core_dep into 670e8eb3df1297735da50d1ff5ec10c547acf00c on hercules-team:master.

Coverage increased (+0.004%) to 99.074% when pulling 60d0312cce3cfcbec100c9398a2faceb8df888eb on igalic:core_dep into 670e8eb3df1297735da50d1ff5ec10c547acf00c on hercules-team:master.

Coverage increased (+0.004%) to 99.074% when pulling 60d0312cce3cfcbec100c9398a2faceb8df888eb on igalic:core_dep into 670e8eb3df1297735da50d1ff5ec10c547acf00c on hercules-team:master.

Coverage increased (+0.004%) to 99.074% when pulling 60d0312cce3cfcbec100c9398a2faceb8df888eb on igalic:core_dep into 670e8eb3df1297735da50d1ff5ec10c547acf00c on hercules-team:master.

Coverage increased (+0.004%) to 99.074% when pulling 60d0312cce3cfcbec100c9398a2faceb8df888eb on igalic:core_dep into 670e8eb3df1297735da50d1ff5ec10c547acf00c on hercules-team:master.

Coverage increased (+0.004%) to 99.074% when pulling 60d0312cce3cfcbec100c9398a2faceb8df888eb on igalic:core_dep into 670e8eb3df1297735da50d1ff5ec10c547acf00c on hercules-team:master.


Problem: Honeypot (Cartesi) project page

Catesi's Honeypot dapp is live , but not reflected on L2Beat site , still says that is in development.
Clicking the "edit information" redirects to a broken site

adding, thanks for reporting!

added


Migrate makeModule to new ModuleObj

At the moment bifacial_radiance is composed of the following classes: RadianceObj, GroundObj, MetObj, AnalysisObj and SceneObj.  I'd like to investigate creating a new ModuleObj that encompasses the ever-growing and complicated makeModule function.  The concept is that what is currently a single function with > 20 inputs would be replaced by a ModuleObj with internally-tracked object parameters such as x,y,z extent, axis of rotation, radfile composition and valid scan points.  First a simple module object is created (or loaded from modules.json).  Then it can be made more complicated by tacking extras on, like  .addFrame,   .addTorqueTube,   .addOmegas,  .addCells  etc.     This will have a lot of benefits, including streamlining the codebase, allowing modifications to underlying geometry, using the same geometry multiple times in multiple different positions (like if you have different frame sizes).  It should be easier to introduce new custom geometries and track how that geometry changes, and test how different geometries interact with each other.

This is fixed now in release 0.4.0.


定义类型中的roll unroll是什么东西? by xiaooubj

比如这个是什么意思？？
newtype Church = Church { unChurch :: forall a. (a -> a) -> (a -> a) }
很困惑啊。。

你看下 unChurch 的类型可能会明白多点吧
*Main> :t unChurch
unChurch :: Church -> (a -> a) -> a -> a

类似于这样定义，但是这种record定义写起来简单多了。
newtype Church2 = Church2 (forall a. (a->a) -> (a->a))

unChurch2 :: Church2 -> (forall a. (a->a)->(a->a))
unChurch2 (Church2 f) = f


automatically create getter and setters (computed) from localStorage keys?

Maybe I missed this feature, but to me, this would feel very natural and is somewhat in line with how firebase/vuefire works.
It might break things for some people though, so it is optional, though it should be the default behavior imho.
Thanks for your time :)
Cheers!
JM

What a nice feature! Can you implement unit tests for it? Or I can do it by myself

I'll give the tests a shot!
I can also do a first draft for a gitbook.
I host (and build) mine on circleci's (2.0) artifacts. Any thoughts on that?
https://www.npmjs.com/package/state-stack
https://hook.io/dasdeck/getartifact/state-stack/index.html
Cheers!

Any thoughts on NOT using jest?
Why not just use a browser-based thing like jasmine or mocha + karma?

Here is an actual working version with tests.
I see you want integration tests as well?
Wouldn't that be impossible with jest only?

@dasdeck I'm busy on the week, I'll do some review on the end of week. It's okay?

For vue related projects I'd use the stack that comes with vue-cli: mocha/chai + nighwatch (or vue-test-utils)
circleci provides docker images with browsers and voila, reallife 1:1 testing.
I'm busy as well, so no worries! I'll try to make some proposals regarding the gitbook and testing environment. Seems gitbook has free hosting as well ? semantic-version is also interesting.....

@dasdeck I removed prefixes from code because they aren't working at all

Odd that it did not work. Seems my test writing skill are not there yet. I got busy as well, so did not have much time to develop it further. I'm glad you found some use for some of it though!
Cheers!


Improve documentation on basic stuff

Great library. Even greater that supports Bootstrap4.
But the documentation is really poor. Its not clear to me how to make the most basic thing needed in bootstrap.
That is: Create a full-height, auto-resize columns template. Yes, sure there is all this part of documentation with the Grid and the different props you can pass in. And yes we have the flexbox in Bootstrap4 which allows to have auto-resize columns but how do you do that with reactstrap?
Building the skeleton (template) of the page is the first thing but still there are no examples!
Some more examples would be helpful.

I understand and this is something we are wanting to address. I know there is a WIP PR to change the docs to gatsby and others have asked when adding docs in PRs if it should include all of the examples bootstrap have (and the answer is yes, even if the examples have nothing special for reactstrap)
Right now the docs are mostly documenting the props which are available and a developer would need to reference bootstrap for possible values to pass to those props. For the Col component the reactstrap documentation has an example with auto and does specify values for Col's props. While it is mostly "code" explanation/documentation of the props and values, it says to supply "auto" when you want a breakpoint to be auto sized.
const stringOrNumberProp = PropTypes.oneOfType([PropTypes.number, PropTypes.string]);
const columnProps = PropTypes.oneOfType([
  PropTypes.string,
  PropTypes.number,
  PropTypes.bool,
  PropTypes.shape({
    size: PropTypes.oneOfType([PropTypes.bool, PropTypes.number, PropTypes.string]),
    // example size values:
    // 12 || "12" => col-12 or col-`width`-12
    // auto => col-auto or col-`width`-auto
    // true => col or col-`width`
    push: stringOrNumberProp,
    pull: stringOrNumberProp,
    offset: stringOrNumberProp
  })
]);

Col.propTypes = {
  xs: columnProps,
  sm: columnProps,
  md: columnProps,
  lg: columnProps,
  xl: columnProps,
  // override the predefined width (the ones above) with your own custom widths.
  // see https://github.com/reactstrap/reactstrap/issues/297#issuecomment-273556116
  widths: PropTypes.array,
}

I'm curious on the state of this, because to echo the original post this is my favorite bootstrap/react library, but I want it to have amazing documentation. Gatsby looks like a great solution!
On that note, the docs would benefit from a lot more description. Having so many examples is great, but contextualizing those with some explanation would be great.
If moving to gatsby is something you're still into, I would love to contribute.

Yes, Gatsby would be awesome! It's a lot of work just to migrate. Enhancing can come with that effort or shortly afterwards.
We really need a better standard for what we document and how we document it. For example, some components have their own page while others are group under a single page. It was supposed to mimic bootstrap's grouping/structure but somewhere it fell apart.
I would love to migrate to Gatsby and almost mimic bootstrap's docs 1-to-1 (example-to-example; where applicable) and add the special reactstrap sauce on top (such as tag, cssModules, and other utilities).
I know another pain point is "what are the acceptable values for these props" and I always point out that "any value can be used since bootstrap can be extended", but maybe we should document the default values bootstrap allows out of the box and explain how to create custom variants by extending bootstrap (and I am fine with linking to bootstrap's docs when it makes sense).

What about using a project like https://www.docz.site/? This project looks great, but I have to jump between the poor documentation and the bootstrap original docs, and sometimes just guess what are the possible values to reactstrap.


[joy-ui] Change background color name scale

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
After a Discord discussion, I wondered if the background scale naming that we currently have on Joy UI is the best one.
Today, the scale works linearly from light to dark, when in dark mode, and from dark to light when in dark mode. We have 7 surface levels, where the body is the first level, and level3 being the last. Body, as the name says, is meant for the <body>, like the base background. In turn, the surface level is used by the components, like the first layer above the <body>, and level1 to 3 subsequently.
The biggest problem is that some names have a semantic approach (body, surface, tooltip, popup) and some have non-semantical names (level 1, level 2 and level 3). This ends up providing a bad DX since it's non-intuitive to know that this is meant to be a linear scale.
Examples 🌈
For instance, these are the scales we currently have for light background:
background: {
        body: getCssVarColor('palette-common-black'),
        surface: getCssVarColor('palette-neutral-900'),
        popup: getCssVarColor('palette-common-black'),
        level1: getCssVarColor('palette-neutral-800'),
        level2: getCssVarColor('palette-neutral-700'),
        level3: getCssVarColor('palette-neutral-600'),
        tooltip: getCssVarColor('palette-neutral-600'),
}

Proposal
As I see, a better experience for this would be:
background: {
        level-0: getCssVarColor('palette-common-black'), //to be used for body
        level-1: getCssVarColor('palette-neutral-900'), //to be used on components
        level-2: getCssVarColor('palette-neutral-800'),
        level-3: getCssVarColor('palette-neutral-700'),
        level-4: getCssVarColor('palette-neutral-600'),
}

For the record, I'm the other guy involved in the Discord discussion.
If the background colors are meant to be a scale, then I believe the proposed changes are better reflecting that.
But this raises a question of, if a section of a page, e.g. drawer, is using level-1 as the background, should the elements in it, e.g. chips, keep using level-1 as the background (current behavior), or should they be auto bump to level-2?

But this raises a question, if a section of a page, e.g., drawer, is using level-1 as the background, should elements in it, e.g., chips, keep using level-1 as the background (current behavior), or should they be auto bumped to level-2?

IMHO by default, they should keep their level for the consistency sake, at least for the Joy UI default theme—otherwise, we can end up with a lot of visuals for the same components. However, if this 'background auto-adjust'  is something that would really improve the DX, I believe it could work like a feature, similar to what we have with color inversion.
In the meantime, I believe changing the name already helps users to better understand and tweak the levels as they need.

But this raises a question, if a section of a page, e.g., drawer, is using level-1 as the background, should elements in it, e.g., chips, keep using level-1 as the background (current behavior), or should they be auto bumped to level-2?

IMHO by default, they should keep their level for the consistency sake, at least for the Joy UI default theme—otherwise, we can end up with a lot of visuals for the same components. However, if this 'background auto-adjust' is something that would really improve the DX, I believe it could work like a feature, similar to what we have with color inversion.
In the meantime, I believe changing the name already helps users to better understand and tweak the levels as they need.

Totally agree with @zanivan. For context, the body and surface are meant to create confidence for customization. For example, as a Joy UI new user, if I want to change the background of the app I can update the background.body without worrying that the rest of the app will change.
But maybe it's better to go with just scale. What's important is the docs that we should cleary communicate how the scale works.


Unknown elements' children are treated the same as direct children of the svg element

Steps to reproduce the issue

Load an SVG that has a svg:mask element
Observe that the mask's path is rendered as though it was an element of the image

Specifications

PocketSVG Version: HEAD
Xcode Version: 9.x
iOS/macOS Version: iOS 11.x

To get myself out of trouble, I've implemented some logic to just ignore unknown elements here:
https://github.com/pocketsvg/PocketSVG/compare/master...cysp:feature/ignore-unknown-elements
… is that something that you would consider taking upstream or would you want to wait for a change that properly respects the mask?

Hi again, @cysp 🙂
I think ignoring unknown elements makes sense.
@fjolnir are you ok with this approach ?
This would also a good opportunity to clearly document which SVG elements can be rendered and which ones will be ignored.


Add HandBrake to Video category

This PR adds HandBrake to the Video category in the README.md file.
Application URL: https://handbrake.fr/
Repository URL: https://github.com/HandBrake/HandBrake
Closes #28

Wait, my bad, HandBrake already exists in the list.