[Addition]: Spoofed cluster of Heltec hotspots under wallet 13ZXMYCToGqpkp5yR3STjPtAvqzR5hv3eYjhhHxS9toE9RYP1Jn

Hotspot b58 Addresses
115prh2eKNqJRmDeEuPgjCmtTCPTaaCnqtEZ31xopnJFCEoJvHa
112sex1n43f4sZBhBYKmog2x6he99kCVAQuwX22hiFFKhu7Dyrzy
112kgHBZsDcFPKAaWxnpX5Bjkmj6KThMEKgT5JNq1YiBopkKnKWc
Discord Handle
screwdriver#9187
Reason(s)
Heltec hotspots witnessing only Heltec hotspots under wallet with other owned hotspots in China. Prior location was Spain, asserted to location in Philippines on same day under 6hours.

Never found such a bad project. When you bought the equipment, the seller and the project party did not supervise whether the sales were legal or not, and did not inform you of the existing risks, just as the police acquiesced in allowing qualified arms dealers to sell arms, but did not inform you that they must sell and use arms legally.  I believe that Helium will definitely declare bankruptcy. As it is said on the Internet, he is a fraud. Because now everyone is reporting. Even though the new 5G hot spot equipment is excellent, it is impossible for new miners to be deceived again.I hope everyone who sees this will forward it. Let everyone know that the project party is a fraud gang.

112EN9ia7qdFfTZ1A7fuuut3AGkXVstLe8qnVWhRbNbft2MqTrdF
112kgHBZsDcFPKAaWxnpX5Bjkmj6KThMEKgT5JNq1YiBopkKnKWc
112exz64A66a5yXoRsqGyiCtD1Uaswi7KysdPESWdPncy1uhKZwS
112sex1n43f4sZBhBYKmog2x6he99kCVAQuwX22hiFFKhu7Dyrzy
115prh2eKNqJRmDeEuPgjCmtTCPTaaCnqtEZ31xopnJFCEoJvHa


[Fixes #1910] Dev installer fix

Fixes Forseti installer that broke after restoring VPC support, due to self.config.vpc_host_project not being set.

Fixes #1910


Add pdf_marginal and logpdf_marginal to kde

Following the discussion at #9906, added pdf_marginal and logpdf_marginal to scipy.stats.kde, which are useful for visualizing high dimensional distributions.

I just rewrote evaluate, logpdf, pdf_marginal and logpdf_marginal. Now all of them use np.einsum instead of looping over the data or points. I think it's not necessary for evaluate to do whitening. For evaluate and logpdf, they are still using self.inv_cov because it's available, while pdf_marginal and logpdf_marginal are not explicitly inverting the covariance.

@rgommers @ilayn
Now the problem is, without stuffs like tree-based computation, kde can be expensive for large data set.
Previously it was looping over the data points or input points. This needs less memory, but I think it should be slow.
I just tried to use einsum or tensordot to vectorize it, but then it could not pass the test because of memory limit. Since for each input point, we need to evaluate its distance to each data point, so we will need to manipulate a (# of dim, # of data, # of input) array.
Could you tell me your opinions on this?
I think an intermediate but less clean way can be, when # of data or # of input is too large, divide it into smaller blocks and do einsum on each block. This can be regarded as some kind of trading between memory and run time.

I was interested in this same behavior, but also numerous other features (e.g. different kernels, reflecting boundary conditions, some custom behavior in resampling... etc).  I decided it really warranted a separate package, instead of trying to add all of this functionality to the existing scipy submodule.  For anyone interested, that new package (highly beta) can be found here: kalepy.
That being said, I don't know what the optimal tradeoff is for putting large/complex submodules into the scipy package.  Should the gaussian_kde functionality be kept as simple, general KDE functionality, and leave complex behavior for  another package?  Or should this scipy method be expanded (arbitrarily) to include all desired behavior?  If anyone has suggestions/comments (e.g. @rgommers), I'm very curious what the consensus thoughts are.  I'm also very happy to help incorporate all or some of the additional functionality into the scipy module (of if the consensus is 'all') then perhaps fold this new package into scipy.
@HerculesJack one technical comment: I ran into the same memory vs speed issue you describe above in the resample functionality, and found that implementing a 'chunking' procedure works extremely well (~10--100x speedup, with very small memory footprint).  Resampling in chunks of ~1e5 optimized speed and memory requirements for dimensions (numbers of parameters) between 1 and 5.  I did not have any issues in the evaluation functionality.

@HerculesJack thought I'd check in on this PR. Would you like to finish it up? What do you need from us?

@mdhaber This is a quite old thread. It did not get merged because my naive implementation could not pass the tests due to memory and/or run time limits. I no longer need this feature for my own application, but am happy to help if you would like to take it over. I think you'd need to first review the code and resolve the conflicts, and then figure out a way to split the computation in batches so that it won't hit the memory cap.

Thanks for the summary @HerculesJack. In that case, I'll probably record the feature idea somewhere and close the PR.
@lzkelley I've thought about the idea of leaving KDE enhancements to another package, too. As a stats maintainer, I'm conflicted. On one hand, it's very interesting; e.g. adding back support for degenerate data and eliminating use of inv has gripped me. On the other, my attention is pulled in a lot of directions, so more complicated PRs tend to get proportionally less attention. In any case, I think KDE functionality would be able to grow a lot faster in a separate package; the downside is just that that users would not already have that at their fingertips (without looking for it).
I may create a meta-issue summarizing KDE's several enhancement requests and inactive enhancement PRs. If so I'll let you know.
Looks like kalepy's last release was a while ago, but you created some issues a few months ago. How's the project coming? Are there any features in SciPy's KDE that it does not support?

Thanks again @HerculesJack. One last question: this PR adds methods for computing the pdf/logpdf of a marginal distribution of a KDE distribution. I'm thinking that rather than having a separate methods for pdf/logpdf only, it would make sense to have a single method, e.g. marginalized, that simply returns a KDE object representing the marginalized distribution. Because the marginal PDF of a multivariate normal distribution is the PDF of a multivariate normal distribution using a subset of indices of the original mean and covariance matrix, the implementation is quite simple at its core: just extract the relevant indices of the dataset and covariance matrix and instantiate a new KDE instance with that information. The PDF/logpdf code would not need to be copied/rewritten. Does this make sense?

Thanks again @HerculesJack. One last question: this PR adds methods for computing the pdf/logpdf of a marginal distribution of a KDE distribution. I'm thinking that rather than having a separate methods for pdf/logpdf only, it would make sense to have a single method, e.g. marginalized, that simply returns a KDE object representing the marginalized distribution. Because the marginal PDF of a multivariate normal distribution is the PDF of a multivariate normal distribution using a subset of indices of the original mean and covariance matrix, the implementation is quite simple at its core: just extract the relevant indices of the dataset and covariance matrix and instantiate a new KDE instance with that information. The PDF/logpdf code would not need to be copied/rewritten. Does this make sense?

Yes, that makes sense to me!

OK, I resolved merge conflicts and added a commit (https://github.com/scipy/scipy/pull/9932/commits/0157c13325d54e5935b2c122c13fa53e037b8497) that shows the concept of the new approach. The tests (including one showing that old and new approaches produce the same PDF values) passed, so I'll remove the old approach.
I'm going to send an email about this to the mailing with three questions.

What should the method that returns the marginal distribution be called? marginalize is a verb (good), but may not be acceptable due to other meanings of the word. marginal or get_marginal would also work?
Currently, the axis argument specifies the dimensions that one would integrate over to obtain the marginal distribution. This leads to two questions:
a.   Should the user specify which dimensions they would integrate over to get the marginal, or should they specify the dimensions they want to keep?
b.   Either way, the name axis is not really appropriate because it is use in a different (but consistent) way throughout NumPy and SciPy to refer to the axis or axes of an array, whereas here was are using the argument as indices along the zeroth axis of the dataset array (improving efficiency, e.g. by avoiding re-calculation of the covariance matrix and/or its inverse would be a separate PR). What should the name of this parameter be instead?

Email to mailing list sent 8/11. No response so far, but we have a contributor and two stats maintainers who think this is a good idea. Yes, the implementation is simple, but I think it is very useful to users who don't happen to know that the marginal distribution of a multivariate normal takes such a simple form.
@tupui I'm happy with this if tests pass and the latest changes look good to you.


SVG rendering with black background

I tried rendering svg icons to webfonts, but I am facing issue for few icons which renders with a black background, however when I do the same in IcoMoon generator it works fine.
Original SVG:

As generated by webfonts-generator

As generated by icomoon

I tried to go with
formatOptions {
  svg: {
    normalize: false
  }
}

But no icons were rendered.
Any help here would be great.

Up!

same issue here

same here. as a hint, i think that it comes from svgicons2svgfont bad design. by forcing people to give an array of file strings, it makes it harder to use svgo to optimize svg ; of course, you could use a tmpDir with svg "svgo-ed" files but it doesn't look right to me... It would be way better if we could pass directly svg strings in svgicons2svgfont stream.

i had the same issue as well. it appears to come mostly from my svg files. multiple paths as well as the "even-odd" fill rule are quite messy to get around.

After search, I solve my problem by delete transparent background on my SVGs and simplify xml code with export options.


suggested fix for #124

Hey Ben, stumbled across this fr and thought what the hell - any remarks, would be happy to help some more?
#124

BTW, this doesn't actually address #124 since this is adding white/black list support, #124 is actually a request to be able to select a range of dates (start through end) in a single date-picker so we'll need another PR in order to resolve the issue completely, thanks for the PR though!

Fixes #113

You're completely right, will change tonight.
Thanks for the remarks.


'When' expressions insert  before a '>' character automatically

VSCode Version:
OS Version:

Steps to Reproduce:
Issue Type: Bug
The VSCodeVim extension has some keybindings that make use of the 'when' expressions. The 'Ctrl' based keybindings use a 'when' expression similar to this (for the "Ctrl+r" for example):
editorTextFocus && vim.active && vim.use<C-r>

However, vscode is automatically changing these expressions to the following:
editorTextFocus && vim.active && vim.use<C-r >

Notice the ' ' (space) between 'r' and '>'. If I try to manually edit the when expression and remove that space, vscode automatically inserts that space again, however it still changes the 'source' to 'User'. There is no way to remove that space.
This means that all keybindings that use this no longer work.
VS Code version: Code - Insiders 1.52.0-insider (5e350b1b79675cecdff224eb00f7bf62ae8789fc, 2020-12-04T10:15:27.849Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 x 2592)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.90GB (2.40GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

vim
vsc
1.17.2

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
openlogontheside:30221882
python763:30178808
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
python504:30227505
vswsl492cf:30208930
wsl2prompt:30219162
vstry244:30230484
pythonvsdeb440:30224570
unusedpromptcf:30219165
folderexplorercf:30219167
openfilemenucf:30219169
pythonvsded773:30223139
pythonvspyt859:30228413

Does this issue occur when all extensions are disabled?: (it creates an issue to an extension)

@alexdima I believe this is related to the following commits:
72defdc77c3dae16cff9ad97a8cf51389a944c55
16ffa1deffd6a843024686f91fa7fbd6e514b345
bbdbcd333bdf449f86c1084bc96c92785e2e0b41
I have also noticed that if I manually change the expression to this:
editorTextFocus && vim.active && vim.use<C-r> == true

Then vscode correctly updates it to this:
editorTextFocus && vim.active && vim.use<C-r>

And the key works after this.
Is it possible to implement some kind of check before assuming that it is a "greaterThan" or "lessThan" expression? For example if both sides of the symbol are not numbers then it makes no sense to compare them?!

I think #110846 may have caused this.


[8.x] Accessibility cookie settings

References

Fixes #2668

Description
Adding and changing some classes in the global scss to make the cookie settings more accessible.
Instructions for Reviewers
List of changes in this PR:

Added the variable "--very-dark-cyan" in _custom_variables.scss.
Removed the variable ".cm-btn.cm-btn-success.cm-btn-accept-all" and its styling as it was no longer needed.
Styled the "Accept all" button by overwriting the style of the ".klaro .cookie-modal .cm-btn.cm-btn-success.cm-btn-accept-all" variables.
Added "text-decoration: underline;" to the anchors.
Changed the color of some informational texts, which were previously gray and are now lighter to improve contrast.
Changed the color of the "Save" button by overwriting the styling of the variables: .klaro .cookie-modal .cm-btn.cm-btn-info.

To reproduce:

Visit a DSpace repository in an anonymous browser.
Klaro cookie popup should appear. Click on "Customize" to bring up the screen above
Expand all sections on that screen.
Run an accessibility scanner (WAVE or "axe DevTools) and check that the accessibility test is positive.

Checklist

[ ] My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
[ ] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[ ] My PR passes ESLint validation using npm run lint
[ ] My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
[ ] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[ ] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[ ] My PR aligns with Accessibility guidelines if it makes changes to the user interface.
[ ] My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
[ ] My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
[ ] If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[ ] If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
[ ] If my PR fixes an issue ticket, I've linked them together.

Manually ported to 7.x in #3627


fix bug of serialize or deserialie generic type use fastjson eg:resul…

…t or paramete use List
What is the purpose of the change
XXXXX
Brief changelog
XXXXX
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

fix bug of serialize or deserialie generic type use fastjson

What bug ? Please give more details.


Add PowOperation

TODO: In a different PR, need to figure out how to do the exception handling nicely and consistently.


CFLite seems to fail to download coverage data kept as an artifact

I set up a "cron" job pruning corpora and generating coverage reports but PRs don't seem to have access to "coverage" artifacts:
2022-01-21 13:08:25,388 - root - INFO - Removing unaffected fuzz targets.
2022-01-21 13:08:25,601 - root - INFO - Diffing against master.
2022-01-21 13:08:25,604 - root - INFO - Files changed in PR: ['.clusterfuzzlite/bpf-object-fuzzer.c']
2022-01-21 13:08:25,755 - root - ERROR - Request to https://api.github.com/repos/evverx/libbpf/actions/artifacts?per_page=100&page=1 failed. Code: 401. Response: {'message': 'Bad credentials', 'documentation_url': 'https://docs.github.com/rest'}
2022-01-21 13:08:25,756 - root - ERROR - Could not get coverage: Github API request failed..
2022-01-21 13:08:25,756 - root - ERROR - Could not find latest coverage report.

even though they can download the corpus just fine:
2022-01-21 13:08:32,241 - root - INFO - Using address sanitizer.
2022-01-21 13:08:32,253 - root - INFO - Fuzz targets: ['/github/workspace/build-out/bpf-object-fuzzer']
2022-01-21 13:08:32,254 - root - INFO - Running fuzzer: bpf-object-fuzzer.
2022-01-21 13:08:32,254 - root - INFO - Downloading corpus for bpf-object-fuzzer to /github/workspace/cifuzz-corpus/bpf-object-fuzzer.
2022-01-21 13:08:33,281 - root - INFO - Done downloading corpus. Contains 1317 elements.
2022-01-21 13:08:33,281 - root - INFO - Starting fuzzing

The PR where it was tested is https://github.com/evverx/libbpf/pull/4
The coverage data and corpus were generated at https://github.com/evverx/libbpf/actions/runs/1728607427
It could be that I screwed something up there. I'll try to figure out whether the issue is on my side.

I fixed it with
    cflite: pass token when fuzzers are built

diff --git a/.github/workflows/cflite_pr.yml b/.github/workflows/cflite_pr.yml
index 7a26df3..00f4d68 100644
--- a/.github/workflows/cflite_pr.yml
+++ b/.github/workflows/cflite_pr.yml
@@ -23,6 +23,7 @@ jobs:
       uses: google/clusterfuzzlite/actions/build_fuzzers@f05300d90afb3e43117ba235fb16597b50918b57
       with:
         sanitizer: ${{ matrix.sanitizer }}
+        github-token: ${{ secrets.GITHUB_TOKEN }}
     - name: Run Fuzzers (${{ matrix.sanitizer }})
       id: run
       uses: google/clusterfuzzlite/actions/run_fuzzers@f05300d90afb3e43117ba235fb16597b50918b57

so CFLite works expected but the documentation needs updating.

Thanks a lot@evverx , can you please upload a PR for the doc change.

I'll push it to https://github.com/google/clusterfuzzlite/pull/76 a bit later.

Sorry didn't know about this survey. I just emailed Jan to see if this can be sent to reporter email directly instead of project dev mailing list.

@evverx - Jan said this was a one time mistake, we always try to reach reporter email directly. If this happen again, please do let us know.

Thanks! It's good to know that there are bug hunters out there looking at systemd apparently.


Add crossfilter

gulp will watch angular files now
add sample of what the service schema looks like
add crossfilter integration

:thumbsup:


perf(webpack): use futureEmitAssets

Implement https://github.com/webpack/webpack/pull/8642
Types of changes

[x] New feature (a non-breaking change which adds functionality)

Description

New option output.futureEmitAssets allows to opt-in to the new way of emitting assets which allows to free memory of Sources with the trade-off of disallowing reading asset content after emitting

Maybe we should make that configurable though 🤔
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[x] All new and existing tests are passing.

@manniL Great discovery. Let's see if tests are passing. We can fully test it in edge.

Codecov Report

Merging #5003 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #5003   +/-   ##
=======================================
  Coverage   92.23%   92.23%
=======================================
  Files          74       74
  Lines        2472     2472
  Branches      608      608
=======================================
  Hits         2280     2280
  Misses        172      172
  Partials       20       20

Impacted Files
Coverage Δ

packages/webpack/src/config/base.js
95.45% <ø> (ø)
:arrow_up:

packages/webpack/src/plugins/vue/server.js
84.61% <0%> (-3.85%)
:arrow_down:

packages/webpack/src/plugins/vue/client.js
94.28% <0%> (-2.86%)
:arrow_down:

packages/vue-renderer/src/renderer.js
95.85% <0%> (+1.03%)
:arrow_up:

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 8106523...82ba5a5. Read the comment docs.


Implement maint1 restriction on binding 2D views of a 3D texture to a DS

Fixes #1910.

Yes, I will add a test for this.

DescriptorSet test update looks like a nice win!


Add cut, rename time to move

Codecov Report
Attention: Patch coverage is 0% with 72 lines in your changes are missing coverage. Please review.

Project coverage is 7.09%. Comparing base (bea2742) to head (261f7f3).

Files
Patch %
Lines

cut.go
0.00%
44 Missing :warning:

move.go
0.00%
26 Missing :warning:

gpxt.go
0.00%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##           master      #3      +/-   ##
=========================================
- Coverage    8.19%   7.09%   -1.10%
=========================================
  Files          13      14       +1
  Lines         427     493      +66
=========================================
  Hits           35      35
- Misses        390     456      +66
  Partials        2       2

Flag
Coverage Δ

unittests
7.09% <0.00%> (-1.10%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


代码高亮的示例代码报错

Connected to the target VM, address: '<IP_ADDRESS>:63789', transport: 'socket'
16:08:31.166 [main] INFO com.deepoove.poi.resolver.TemplateResolver - Resolve the document start...
16:08:31.175 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {{
16:08:31.175 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - code
16:08:31.175 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - }}
16:08:31.175 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [Start]:The run position of {{code}} is 0, Offset in run is 0
16:08:31.175 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [End]:The run position of {{code}} is 2, Offset in run is 1
16:08:31.177 [main] DEBUG com.deepoove.poi.resolver.TemplateResolver - Resolve where text: {{code}}, and create RunTemplate for XWPFRun
16:08:31.183 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {
16:08:31.184 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {
16:08:31.184 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - code
16:08:31.184 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - }}
16:08:31.184 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [Start]:The run position of {{code}} is 0, Offset in run is 0
16:08:31.184 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [End]:The run position of {{code}} is 3, Offset in run is 1
16:08:31.184 [main] DEBUG com.deepoove.poi.resolver.TemplateResolver - Resolve where text: {{code}}, and create RunTemplate for XWPFRun
16:08:31.185 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {{code}}
16:08:31.185 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [Start]:The run position of {{code}} is 0, Offset in run is 0
16:08:31.185 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [End]:The run position of {{code}} is 0, Offset in run is 7
16:08:31.185 [main] DEBUG com.deepoove.poi.resolver.TemplateResolver - Resolve where text: {{code}}, and create RunTemplate for XWPFRun
16:08:31.185 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {
16:08:31.185 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {code}}
16:08:31.185 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [Start]:The run position of {{code}} is 0, Offset in run is 0
16:08:31.185 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [End]:The run position of {{code}} is 1, Offset in run is 6
16:08:31.186 [main] DEBUG com.deepoove.poi.resolver.TemplateResolver - Resolve where text: {{code}}, and create RunTemplate for XWPFRun
16:08:31.186 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {
16:08:31.186 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {?themes
16:08:31.186 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - }}
16:08:31.186 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [Start]:The run position of {{?themes}} is 0, Offset in run is 0
16:08:31.186 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [End]:The run position of {{?themes}} is 2, Offset in run is 1
16:08:31.186 [main] DEBUG com.deepoove.poi.resolver.TemplateResolver - Resolve where text: {{?themes}}, and create RunTemplate for XWPFRun
16:08:31.187 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {
16:08:31.187 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {_index}}
16:08:31.187 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - .
16:08:31.188 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {
16:08:31.188 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {
16:08:31.188 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - theme
16:08:31.188 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - }}
16:08:31.188 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [Start]:The run position of {{_index}} is 0, Offset in run is 0
16:08:31.188 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [End]:The run position of {{_index}} is 1, Offset in run is 8
16:08:31.188 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [Start]:The run position of {{theme}} is 3, Offset in run is 0
16:08:31.188 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [End]:The run position of {{theme}} is 6, Offset in run is 1
16:08:31.188 [main] DEBUG com.deepoove.poi.resolver.TemplateResolver - Resolve where text: {{_index}}, and create RunTemplate for XWPFRun
16:08:31.188 [main] DEBUG com.deepoove.poi.resolver.TemplateResolver - Resolve where text: {{theme}}, and create RunTemplate for XWPFRun
16:08:31.189 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {
16:08:31.189 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {
16:08:31.189 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - code
16:08:31.189 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - }}
16:08:31.189 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [Start]:The run position of {{code}} is 0, Offset in run is 0
16:08:31.189 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [End]:The run position of {{code}} is 3, Offset in run is 1
16:08:31.189 [main] DEBUG com.deepoove.poi.resolver.TemplateResolver - Resolve where text: {{code}}, and create RunTemplate for XWPFRun
16:08:31.189 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {
16:08:31.189 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - {/themes}}
16:08:31.189 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [Start]:The run position of {{/themes}} is 0, Offset in run is 0
16:08:31.189 [main] DEBUG com.deepoove.poi.resolver.RunningRunBody - [End]:The run position of {{/themes}} is 1, Offset in run is 9
16:08:31.189 [main] DEBUG com.deepoove.poi.resolver.TemplateResolver - Resolve where text: {{/themes}}, and create RunTemplate for XWPFRun
16:08:31.196 [main] INFO com.deepoove.poi.resolver.TemplateResolver - Resolve the document end, resolve and create 5 MetaTemplates.
16:08:31.196 [main] INFO com.deepoove.poi.render.DefaultRender - Render template start...
16:08:31.200 [main] INFO com.deepoove.poi.render.processor.LogProcessor - {{code}}
16:08:31.200 [main] INFO com.deepoove.poi.render.processor.LogProcessor - {{code}}
16:08:31.200 [main] INFO com.deepoove.poi.render.processor.LogProcessor - {{code}}
16:08:31.200 [main] INFO com.deepoove.poi.render.processor.LogProcessor - {{code}}
16:08:31.200 [main] INFO com.deepoove.poi.render.processor.LogProcessor - {{?themes}}
16:08:31.200 [main] INFO com.deepoove.poi.render.processor.LogProcessor -   {{_index}}
16:08:31.200 [main] INFO com.deepoove.poi.render.processor.LogProcessor -   {{theme}}
16:08:31.200 [main] INFO com.deepoove.poi.render.processor.LogProcessor -   {{code}}
16:08:31.200 [main] INFO com.deepoove.poi.render.processor.LogProcessor - {{/themes}}
16:08:31.203 [main] INFO com.deepoove.poi.render.processor.DelegatePolicy - Start render Template {{code}}, Sign: , policy:HighlightRenderPolicy
Exception in thread "main" com.deepoove.poi.exception.RenderException: Unable to render template {{code}}
at com.deepoove.poi.policy.AbstractRenderPolicy.reThrowException(AbstractRenderPolicy.java:87)
at com.deepoove.poi.policy.AbstractRenderPolicy.render(AbstractRenderPolicy.java:69)
at com.deepoove.poi.render.processor.DelegatePolicy.invoke(DelegatePolicy.java:45)
at com.deepoove.poi.render.processor.ElementProcessor.visit(ElementProcessor.java:65)
at com.deepoove.poi.render.processor.ElementProcessor.visit(ElementProcessor.java:59)
at com.deepoove.poi.template.run.RunTemplate.accept(RunTemplate.java:64)
at com.deepoove.poi.render.processor.DocumentProcessor.visit(DocumentProcessor.java:95)
at com.deepoove.poi.template.run.RunTemplate.accept(RunTemplate.java:64)
at com.deepoove.poi.render.processor.DocumentProcessor.lambda$process$0(DocumentProcessor.java:59)
at java.util.ArrayList.forEach(ArrayList.java:1257)
at com.deepoove.poi.render.processor.DocumentProcessor.process(DocumentProcessor.java:59)
at com.deepoove.poi.render.DefaultRender.renderTemplate(DefaultRender.java:82)
at com.deepoove.poi.render.DefaultRender.render(DefaultRender.java:64)
at com.deepoove.poi.XWPFTemplate.render(XWPFTemplate.java:223)
at com.ruoyi.system.util.tes.testHightlight(tes.java:84)
at com.ruoyi.system.util.tes.main(tes.java:20)
Caused by: java.lang.IndexOutOfBoundsException
at org.openxmlformats.schemas.wordprocessingml.x2006.main.impl.CTRPrImpl.getRStyleArray(CTRPrImpl.java:160)
at org.apache.poi.xwpf.usermodel.XWPFRun.getStyle(XWPFRun.java:1256)
at com.deepoove.poi.util.StyleUtils.styleRun(StyleUtils.java:157)
at com.deepoove.poi.policy.DocumentRenderPolicy$Helper.renderDocument(DocumentRenderPolicy.java:63)
at com.deepoove.poi.policy.AbstractDocumentConverterRenderPolicy.doRender(AbstractDocumentConverterRenderPolicy.java:46)
at com.deepoove.poi.policy.AbstractRenderPolicy.render(AbstractRenderPolicy.java:66)
... 14 more

使用版本：poi-tl 1.10.5   poi相关依赖都是5.0.0
使用的示例代码地址：https://github.com/Sayi/poi-tl/blob/dev-1.10.x/poi-tl-plugin-highlight/src/test/java/com/deepoove/poi/plugin/highlight/HighlightRenderPolicyTest.java

版本搞错了，1.10.5支持4.1.2，建议你用最新版本试试哦。


Carousel paginator

You can display carousel pages in the top right corner. With link to the selected slide.
This commit change the data-slide feature, now you can set a number value to call to function with value as argument.
Example code:

    ...

1

2

3

great feature! thanks!

Why not have the carousel plugin automatically generate the paginator markup for you, rather than forcing the user to add the markup?

Cool idea - but don't think we're ready to add this. Mark and I have played with some similar things but want to do things a bit differently. thanks!


apt/params: Remove unused LSB facts

These facts aren't used anywhere in the APT module and at least lsbminordistrelease doesn't seem to be set at all anymore in recent versions of Puppet. This causes the following warning to show up on Puppet 4.3:
Warning: Undefined variable 'lsbminordistrelease';
   (file & line not available)

On 4.5 we get the slightly more helpful:
Warning: Unknown variable: '::lsbminordistrelease'. at /etc/puppetlabs/code/environments/production/modules/apt/manifests/params.pp:15:32

@bmjen If you're looking at apt PRs anyway, here's another 😄.

Thanks @daenney !


Add Help modal popup

Add a modal to the navigation bar.  The help could include a description of selecting the dataset, entering the handle, and include description of column headers.

Closed via 9c28f2258c61d973a67b2fa26e63f9edb127f5c8


Milestone 2 tasks

In this milestone, we focus on cleaning up existing code and make it ready for OpenSearch development

[x]  Remove X-Pack and non oss features/tests and commits not related to >7.10 from main branch
[x]  Update CI to run with Opendistro docker image with out security plugin (all tests should pass)
[x]  Update Admin.md/MAINTAINERS.md to reflect Individual owners
[x]  Onboard external maintainers

CI runs with Opendistro tarball instead of docker


add support for launching Linux apps

Added ability to launch Linux apps. Parses .desktop shortcut files for app launch commands. Correctly parses arguments and passes them to ui.launch.

I just added the folders for snaps and flatpaks.


Images overlay text-color in about section

Link to the section - https://syntax.fm/about
I noticed the text color is changing for Ben, from white to black on hover.
However, it is the same for everyone else card. Is it intended behavior or a bug?
Hover on Ben's card -

Hover on Wes's card -

THe black is intentional so its readable on bens hover. BUt you found a bug in that the card doesnt swap photos if you hover on the persons name

fixed

Loving the cursor change on hover, hehe 😁


Support "append" write mode.

Closes #153
Closes #152
This PR support append write mode. The default write mode is overwrite.
In addition, arrow flight version is upgraded to v7 to support writing csv files.
Signed-off-by: Revital Sur<EMAIL_ADDRESS>Co-authored-by: Mohammad Nassar<EMAIL_ADDRESS>

@cdoron I addressed your comments. Thanks


Dynamically Calculate Edge Margin for Source and Target [feature request]

The power AND extensibility of vng is amazing!  Thank you so much for all your work.
I use the graph to render arbitrary node components as svg foreignObjects, so my nodes can end up being various shapes/sizes.  For example, they can all be divs with dynamically updating data, resulting in rectangles with unique dimensions.
It would be nice to be able to compute the "margin" property of each edge independently, and for each each to compute the margin of the source- and target edges independently.  This would allow me to move the starting/terminating points of the edge to a location that makes sense for my various nodes.
In the example above, I'd probably use the "max radius" of each node (so from the node center to it's corner) as the margin value.  But I could also make it more complex, taking into account the angle of the edge and causing the margin to adjust accordingly.  Either way, if could specify the margin is a function, it could be left to my own design.
Thanks again!

Oh, maybe this isn't necessary.... I just noticed that when I click on a node, vng seems to update the marker positions to move out to the edge of the rendered div.  Maybe I have some poorly designed reactivity going on somewhere.


Adding additions checks for other pixel bin conditions for timerange for create_meta_pixel

Fixes #133

this is ready for review


publisher_metadata fields annotated as required

RE - https://app.swaggerhub.com/apis/danieljhegeman/Curation/1#/publisher_metadata
It documents that "some" of the fields are required. All are required to be present. There are heuristics for missing day or month (default to 1) in filter by metadata.
But the values are acquired from crossref and set by the BE based on the DOI passed when creating or editing a collection and returned in query information, so it's unclear why required (*) is annotated in responses.

I had copied straight from this PR by Emaneule. I will add month and day.
Regarding the usage of required in responses: it is sort of like a gating mechanism for our own testing. We have a number of instances of it being used to help define responses in the v1 API for the FE. It makes sense as a last check in prod, too, where we might consider our generated response invalid (and thus better to return a 400) unless it contains certain fields.

@brianraymor Swagger updated.


[python] Improve detection of nonexistent-array errors from TileDB Cloud"

Issue and/or context:
In conjunction with #863, this allows ingest to tiledb-cloud URIs to again succeed.
uri = 'tiledb://johnkerl-tiledb/s3://tiledb-johnkerl/scratch/test-cloud-20230201'
soma = tiledbsoma.SOMA(uri)
tiledbsoma.io.from_h5ad(soma, '/tmp/test.h5ad')

Note this test scenario does not pass until and unless #863 is also included. I'm putting this up as a PR on main instead of atop #863 at the explicit request of @thetorpedodog .
Note
Since this is an open-source package we do not have unit tests taking the tiledb.cloud dependency.

Thanks @thetorpedodog !!


Demo not working: mediaelementplayer-youtube.html

The demo for youtube (mediaelementplayer-youtube.html) is not working. There is a controller but no video loaded. Checked the clip http://www.youtube.com/watch?v=nOEw9iiopwI on youtube, it's working fine, hence probably not a problem of youtube connection.
Test env: Chrome 23 on OS X 10.8. (it works in Safari though)

@clwen Is this still an issue?

@clwen Closing old issues. If you'd like to reopen this, let us know. Thanks!


DB connection design

Description
We should provide a best practice to handle database connection.
Describe the solution you'd like
Now, our database entities can be seen as two part. One is for lake core, another is for plugins.
I proposal to create db connection for each type of  these entities.(One for lake core and one for plugins)
Also, it's recommended to use different database for lake core and plugins.
FAQ
Should we create a database connection pool?
No, gorm will handle it properly.
Why seperate to two db connections other than use one?

plugin is not always reliable, we should keep lake alive even if some plugin cause a database error.
data in lake core and in plugin may be with different privilege for users, manager it independently is more flexable.

Why not create db connection for each plugin?

data produced by different plugins sometimes need to aggregate togather. Save it to different db make difficulty(we don't create different connections to the always same db, right?).
It'll add unnecessary works for plugin to manager db connection.

It has moved to #421 Configuration section.


GoOracle Setting is not configurable On Mac Sublime3

GoOracle Setting is not configurable On Mac Sublime3. config file can be open but just read only.

Same problem

I ran into the same problem. To get around it save this stuff:
{
  // Example settings. Replace these with your own.
  // "env": {},
  // "oracle_scope": ["github.com/juju/juju/cmd/juju", "github.com/juju/juju/cmd/jujud"],
  // "oracle_format": "",
}

into a new file here:
~/Library/Application Support/Sublime Text 3/Packages/GoOracle/User.sublime-settings

Same Problem here... Needs to be fixed I guess :+1:

Same issue with Ubuntu 14.04 & SublimeText 3
~/.config/sublime-text-3/Packages/GoOracle/User.sublime-settings

Windows 8.1 too

Windows users should do this:
a) first, unpack the GoOracle.sublime-package in AppData\Roaming\Sublime...\Installed Packages directory
b) then modify the User.sublime.settings
c) Compress the modified settings file plus all other files into a new package called GoOracle.sublime-package but DO NOT create a new directory, just a new package. Also don't use any kind of compression: just save the "combined" files.
Now you can use GoOracle with your individual settings applied.

(Tested on ST3 and Mac Yosemite)
To run GoOracle properly and SAVE YOUR TIME!

Install must-have components
go get golang.org/x/tools/oracle
go get golang.org/x/tools/cmd/oracle

Otherwise, oracle not found.

Create and Save user setting files (refer to above @nfiniteset workaround)
Mac: ~/Library/Application Support/Sublime Text 3/Packages/GoOracle/User.sublime-settings
Must-have settings: Change PATH accordingly.
oracle_scope is path under $GOPATH/src/.

It can be specified for individual project: @dr2chase solution

But you can also manually change the oracle_scope for each project
{
    "env": { "GOPATH": "$HOME/Go", "GOROOT": "/usr/local/opt/go/libexec", "PATH": "$GOROOT/bin:$GOPATH/bin:$PATH" },
    "oracle_scope": ["projects/myproj"],

}

> Otherwise, get stuck in "Running oracle callees command..." and no output returned.
"View">"Show Console" shows console error.
`Traceback (most recent call last):

File "goOracle in /Users/gopher/Library/Application Support/Sublime Text 3/Installed Packages/GoOracle.sublime-package", line 46, in on_done
File "goOracle in /Users/gopher/Library/Application Support/Sublime Text 3/Installed Packages/GoOracle.sublime-package", line 115, in oracle
TypeError`
GoOracle issue: Oracle never returns

Otherwise, cgo failed: exec: "go": executable file not found in $PATH
Related: Oracle invocation error

Is there any update on this issue ? I recently tried to use Go oracle with Sublime text 3 on osx and i keep hitting the error oracle: no packages specified for pointer analysis scope.
I manually downloaded the go-oracle package into my Packages dir for Sublime text 3, edited the user settings. Still get the above error.
Does anyone have a solution to this issue ?


gPRC Template Generation Utility fails

I am just started with gPRC for LabVIEW using your "Hello World" example description. When I regenerate the gRPC code using the gPRC Template Generation Utility I get an error 1026 and the regeneration quits.

I am using LabVIEW 20.0.1f1 and LabVIEW gPRC v<IP_ADDRESS>
AB#2783939

Found the reason: the labview_grpc_generator.dll is missing in the source project.
Would you please add this correctly?

The Generated Descriptors.vi is missing.


Support nested sectors

This PR adds the possibility to define nested tags.
You can define and combine a syntax like:
`li p` => 'nested`
`p` => `single`

The order does not matter. In any case, nested tags will be replaced first and will not be overwritten by less nested tag classes.
The above example would give the following result:

Something

A list item

Something different

Everything has been swapped to use regex to replace all classes. To not overcomplicate things, I tried to keep it as simple as possible. It's covered by tests, but before merging we need to test if it does work in a real-life-context, which I hadn't had the chance to do yet.
Provided feedback is appreciated a lot!
Closes #12

Thanks!

@aerni did you had the time to check if this is as you do need it?

I just took this for a quick spin. The proposed changes work. But I'm not sure if it should behave the way it does right now. I would expect it to behave as traditional CSS selectors do.
'p' => 'text-base text-gray-800'
'li p' => 'text-sm'

Something

A list item

I'm not sure though how this example would behave regarding the specificity of Tailwind selectors though. This approach could lead to potential issues, whereas your proposed solution would not.

This is not the way it should behave!
I thought this behavior should been covered with this test:
https://github.com/visuellverstehen/statamic-classify/pull/15/files#diff-0cd9d7de02e2302b7d526aa777e77fc91e32fc3224f397d1754afec541580a06R134-R164

The test is ok. I meant to say that I'm expecting it to behave like in my examples above.


enable code coverage

Related to https://github.com/knative-sandbox/.github/pull/20
/cc @mattmoor

One thing that would be cool is to see a diff of the coverage - ie. not just the % diff but the lines


Link-E Support for non-ch32v003 chips

@bmx ran into an issue with this - trying to use it on CH32V307 boards.
I did not know it even could run on a 307.  I don't mind trying to support this some moving forwards, but I think I need a way to identify if it's a 307 or a 003?  Do you know much about this?  Are the debug protocols similar?
https://github.com/cnlohr/ch32v003fun/commit/6f896b6fe749481f8a6d9d96e0b7730545355797
Side-note: If we can discuss this on the Discord for this project that would be helpful.

I have modified it so if it detects a non-003 it tries to go into the old flashing mode.  I "think" this should fix you, BMX. 249f5d2

Part Type (A): 0x0617 (This is the capacity code, in KB)
Part UUID    : 00-26-10-00-00-ba-06-71
PFlags       : 23-48-76-05
Part Type (B): e4-59-a8-e9
Interface Setup
Fault writing memory (DMABSTRACTS = 08000302) (Execption executing Abstract Command) DMSTATUS: 00030382
Fault reading device```

using this commit.

We need to disambiguate the use of `ReadBinaryBlob` which is meant to read-many-bytes on the target, not dealing with the proprietary blob.

I believe this is now resolved.  Should work with the 003 and 307 among others.


Fix pod install for swift libs using new arch

Summary:
This fixes a bug that started with React Native 0.72.0 when using the new architecture and installing a native lib that has Swift code (in my case, @datadog/mobile-react-native).
Running pod install errors with the following output (DatadogSDKReactNative is the pod containing the Swift code):
[...]
Analyzing dependencies
Downloading dependencies
Installing DatadogSDKReactNative 1.8.0-rc0
[!] The following Swift pods cannot yet be integrated as static libraries:

The Swift pod `DatadogSDKReactNative` depends upon `React-Fabric`, `React-graphics`, `React-utils`, and `React-debug`, which do not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.

Indeed, this pods were added as dependencies in packages/react-native/scripts/cocoapods/new_architecture.rb but do not define modules contrary to the other pods in the list.
I've added :modular_headers => true for all these pods and this fixes the issue.
EDIT: after testing it, I added a few modular headers to a few more pods that have been added to the list of dependencies.
This PR is solving a problem that already occured in the past and was solved here: https://github.com/facebook/react-native/pull/33743
Changelog:
[IOS] [FIXED] - Fix pod install for libraries using Swift code when the new architecture is enabled
Test Plan:

Clone this repo
From main, add a Swift file to the MyNativeView native module in the RN tester app (see inspiration from this commit)
Try to run RCT_NEW_ARCH_ENABLED=1 USE_HERMES=0 bundle exec pod install inside the packages/rn-tester
Observe errors
Apply the commit from this PR
Both pod install and the subsequent build should succeed.
Revert the changes and repeat steps 2 to 6 with RCT_NEW_ARCH_ENABLED=1 USE_HERMES=1 bundle exec pod install

@louiszawadzki could you please also test this fix with USE_HERMES=1, and add that to the test plan?

Hi @cipolleschi, thanks for the feedback, it works indeed with your suggested approach!
I've opened a new PR with this new implementation: https://github.com/facebook/react-native/pull/38121

@dmytrorykun will do, and will do so as well for the new PR I've opened :)

Hi @louiszawadzki! are you ok in closing this as #38121 superseedes this with the right solution, imho?

whoops closed the wrong one. Closing this one :)


per issue #335, updating documentation with slight change to config file

Added SERVERROOT, which is common terminology to help web developers quickly identify the intended value of SERVERROOT and consequently, the value of WELLKNOWN.

From your introduction of the concept of a "SERVERROOT" I see that you are making a few assumptions about the system this script is running on:

Has a Webserver running, reachable from the outside
Has a single root from which all websites are served (e.g. /var/www)
The script is able to write to a directory that can be accessed from the outside

This might not be true in a lot of cases, there are a lot of setups with distributed servers and central certificate management out there, using hook scripts to actually deploy challenges and certificates, "WELLKNOWN" in those cases is not a directory that is directly accessible over the internet but more like a working directory for different systems.
Introducing the concept of a "SERVERROOT" conflicts with more complex setups, so this is not good for this script, also it introduces a completely unused variable to the config file, which doesn't really make sense.
I also read your modifications to the documentation and I think they make it even more confusing, that doesn't really help.
Thank you for trying, but I'm closing this since I don't think these changes are a good idea.

Not so, Lukas.
These changes:

bridge a missing gap in the documentation for users that are not operating complex systems;

fix some disjointed topics and ambiguous language and grammar; and

updates a description of WELLKNOWN per changes in draft ACME standards.

These changes do not adversely affect any complex practice of WELLKNOWN in any way.
SERVERROOT can be ignored for any that don't expect it.
You are free to ignore this pull request, or incorporate some or all of the changes under your own authorship.
best wishes,
Ben


Getting unknown error from FirebaseData class

I wanted to make cleaner code for main class so I made another one and I am getting "unknown error" from instance of FirebaseData class.
`
class fireBase{
public:
FirebaseData fbdo;
FirebaseAuth auth;
FirebaseConfig config;
fireBase(){
    config.api_key = API_KEY;
    config.database_url = DATABASE_URL;
    auth.user.email = GMAIL;
    auth.user.password = GMAIL_PASSWORD;
}

void begin(bool reconnectBase=false){
    Firebase.begin(&config, &auth);
    config.token_status_callback = tokenStatusCallback;
    if(reconnectBase) Firebase.reconnectWiFi(true);
}

bool write(String path, String value){
    bool state = false;
    fbdo.pauseFirebase(false);
    if(Firebase.RTDB.setString(&fbdo, path, value)) state=true;
    else Serial.println("REASON: " + fbdo.errorReason()); //<<From here
    fbdo.pauseFirebase(true);
    return state;
}

bool write(String path, bool value){
    bool state = false;
    fbdo.pauseFirebase(false);
    if(Firebase.RTDB.setBool(&fbdo, path, value)) state=true;
    else Serial.println("REASON: " + fbdo.errorReason()); //<<From here
    fbdo.pauseFirebase(true);
    return state;
}

};
`

Problem begins when trying to unpause firebase. I am using ps4 controller in project and wifi and bluetooth can't work simultaneously, with paused wifi firebaseData ps4 controller can connect, although I am not sure why it works from start with only wifi library and webpage.
fbdo.pauseFirebase(false);

Unknown error means no error.
Call fbdo.errorReason() from the last operation that returns true will give unknow error as no error.
The issue occurred when you call pauseFirebase during no network or server connection and the internal pause status will not change after all.
I will fix this soon.

The update v4.3.8 is available, please download.

Thank you, everything works as intended.


Criterion rework

Depends on https://github.com/01org/parameter-framework/pull/60
Please review from a1a4dd3
This is a rework of Pfw criterion. Please do not merge now but some feedback on designs changes would be appreciate.
Next step:

Update coding style everywhere
Use Bit set for criterion state. (in an other pull request)

Coverage decreased (-0.21%) to 69.93% when pulling 9685b70213ff12e78d4f4f08f21581394ca70fae on clero:criterion_rework into 6d605e3228fc03d2a3249715d179b8d6cfdbb64a on 01org:master.

Coverage increased (+0.37%) to 70.51% when pulling 5dbcc2597d32297767903d6ab83eafa4ed6d803a on clero:criterion_rework into 6d605e3228fc03d2a3249715d179b8d6cfdbb64a on 01org:master.

Coverage increased (+0.4%) to 70.54% when pulling 43d8e90567abd41b3f55a922b25657150ee47724 on clero:criterion_rework into 6d605e3228fc03d2a3249715d179b8d6cfdbb64a on 01org:master.

please rebase onto and resubmit against "next"

replaced by #96

replaced by #96

Coverage increased (+0.48%) to 70.61% when pulling 06f80272beb1cdc796f7c3bb67532f1df1a10d81 on clero:criterion_rework into 541735d06abc5d66f05bed8769315e20d50dfdc5 on 01org:master.


Stdout output for OpenTelemetry Exporter

I use the autometrics-py version 0.9 and like to setup the Otel Exporter. The only output I see in my console is a warning that seems to come from the underlying Otel Exporter saying:
Overriding of current MeterProvider is not allowed
I have tried out two different setups for calling init:

running the exact example from the repo:
https://github.com/autometrics-dev/autometrics-py/blob/main/examples/export_metrics/otlp-http.py
In my FastAPI SetUp

@app.on_event("startup")
def initOtelExporter():
    init(
    exporter={
        "type": "otlp-proto-http",
        "endpoint": "http://otel-collector:4318",
        "push_interval": 1000,
    },
    service_name="otlp-exporter",
)

The printed output stays the same in both scenarios.

is fixed by installing the package from the source.


Added link to related article

Current version suggests that on this page we should be able to find more details about joins. I changed that by adding link to article about joins.

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

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

#sign-off

#sign-off

@SnehaGunda: I'm sorry - only the author of this article, @timsander1, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@SnehaGunda: I'm sorry - only the author of this article, @timsander1, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off

#sign-off

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

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


fix logging path

@DO1JLR what do you think, changing paths like that (like in #62) is likely to break existing installs isnt it ?

I do not know what you mean with #62 ....
 This can indeed be merged.
Thank you for doing that :)


Refactor simulation run view to use new summary endpoint

:tada: This issue has been resolved in version 6.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Can not read property isDefined

Uncaught TypeError: Cannot read property 'isDefined' of undefined

Same issue as above

Hi @vishantakhani and @sathyamlokare did you manage to solve this problem?

Same here

Uh, looks like this is because we are trying to use this library in Angular 2+ projects. Use angular2-local-storage instead.


ColorPicker shows color names in English instead of localized ones

Microsoft PowerToys version
0.65.0
Installation method
GitHub, PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
ColorPicker
Steps to reproduce

(regardless of the system language)
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

I can confirm. Localization for colors was there on 0.64 but it's no longer there on 0.65.


Add Catch v3.3.2

Adds Catch v3.x (#129).
The recipe path follows meta-oe – which still ships v2 on master.

Package renamed as catch3 to avoid conflicts with v2.x versions.


m: Remove futures-lite dependency

We didn't really use much from futures-lite, but futures-lite balloons our dependency count significantly. This PR inlines what we do use from futures-lite.

LGTM otherwise. :+1:


Update sbt-mima-plugin to 1.0.0

Updates com.typesafe:sbt-mima-plugin from 0.9.2 to 1.0.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe", artifactId = "sbt-mima-plugin" } ]

labels: sbt-plugin-update, semver-major

Codecov Report

Merging #242 (25824b2) into master (094ed48) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #242   +/-   ##
=======================================
  Coverage   95.31%   95.31%
=======================================
  Files           6        6
  Lines          64       64
=======================================
  Hits           61       61
  Misses          3        3

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 094ed48...25824b2. Read the comment docs.


BUG: window not found error when reloading the /google page

To reproduce: navigate to /google by clicking on maps, then reload the webpage.

Works for chrome and firefox


References to variables which are not set are left expanded

Summary
If .env references a variable (e.g. ${FOO}) which is not already set (either via the external environment, or in the .env file, it is left unexpanded.
This is in contrast to the following other languages / implementations which will expand the variable to an empty string:

Bash (source)
Python: python-dotenv

Demo
Consider this .env file:
# A simple, constant env var
CONST='A constant env var'

# Derived from another variable
DERIV="I came from ${CONST} with some more"

# An environment variable we expect to be set on the outside
EXT_SET=${ENV_EXT_SET}

# An environment variable we expect *not* to be set on the outside
EXT_UNSET=${ENV_EXT_UNSET}

When loaded by bash, EXT_UNSET will get the value "" (that is, the empty string).
When loaded by phpdotenv v5.2.0, EXT_UNSET will get the value "${ENV_EXT_UNSET}" (literally).
See this gist for a full reproducible example:
$ pip3 install scuba
$ ./prepare.sh
$ ./run_test.sh
------------------------------------------------------
Bash:
CONST=A constant env var
DERIV=I came from A constant env var with some more
EXT_SET=set externally
EXT_UNSET=

------------------------------------------------------
phpdotenv:
$_ENV = Array
(
    [CONST] => A constant env var
    [DERIV] => I came from A constant env var with some more
    [EXT_SET] => set externally
    [EXT_UNSET] => ${ENV_EXT_UNSET}
)

------------------------------------------------------
python-dotenv:
CONST=A constant env var
DERIV=I came from A constant env var with some more
EXT_SET=set externally
EXT_UNSET=

References

Upstream issue: https://github.com/snipe/snipe-it/issues/6578

This seems to be the intended behaviour, and we even have tests for it.
        $this->assertSame('', $_ENV['NVAR9']);  // nested variable is empty string
        $this->assertSame('${NVAR888}', $_ENV['NVAR10']);  // nested variable is not set

I even back-ported these test to the 2.3 branch, locally, to see if the passed there too, and they do, so it seems this has always been the behaviour.
I think if we want to change this behaviour, we need to consider it to be breaking a change, and not a bug fix, and thus be making the change for the next major release.

This seems to be the intended behaviour, and we even have tests for it.
        $this->assertSame('', $_ENV['NVAR9']);  // nested variable is empty string
        $this->assertSame('${NVAR888}', $_ENV['NVAR10']);  // nested variable is not set

I even back-ported these test to the 2.3 branch, locally, to see if the passed there too, and they do, so it seems this has always been the behaviour.
I think if we want to change this behaviour, we need to consider it to be breaking a change, and not a bug fix, and thus be making the change for the next major release.

NB Neither we, nor the Python dotenv package claim to have parity with the bash implementation. We both are just "similar".

NB Neither we, nor the Python dotenv package claim to have parity with the bash implementation. We both are just "similar".

Thanks for the quick response, @GrahamCampbell. I was initially looking for confirmation that this was either a bug or the intended behavior.
I can't really think of any use case where the current behavior would be desired or useful, but I definitely understand the desire for backwards compatibility and avoiding breaking changes.
Another route would be an optional argument that controls the expansion behavior ("POSIX mode" one might call it). There are other constructs that the shell language supports, too.
I'm just a user of an open source project facing this limitation due to that project's use of Laravel and it's implementation of Docker image. (See referenced issue.) I'm attempting to work around this using envsubst in ths Docker startup script, but obviously that is not ideal:
(set -a; source .env; envsubst < .env > .envnew && mv .envnew .env)

It took a fair amount of effort just tracking
Perhaps the simplest so

Thanks for the quick response, @GrahamCampbell. I was initially looking for confirmation that this was either a bug or the intended behavior.
I can't really think of any use case where the current behavior would be desired or useful, but I definitely understand the desire for backwards compatibility and avoiding breaking changes.
Another route would be an optional argument that controls the expansion behavior ("POSIX mode" one might call it). There are other constructs that the shell language supports, too.
I'm just a user of an open source project facing this limitation due to that project's use of Laravel and it's implementation of Docker image. (See referenced issue.) I'm attempting to work around this using envsubst in ths Docker startup script, but obviously that is not ideal:
(set -a; source .env; envsubst < .env > .envnew && mv .envnew .env)

It took a fair amount of effort just tracking
Perhaps the simplest so

I am not averse to changing the behaviour in the next major version, but just need to be sure there won't be any other unintended side effects. One thing that immediately comes to mind is the nested processing of interpolation.

I am not averse to changing the behaviour in the next major version, but just need to be sure there won't be any other unintended side effects. One thing that immediately comes to mind is the nested processing of interpolation.

I think, possibly the original reason for this behaviour was because there was no way to write a literal dollar, say, as part of a password, without it being processed as a variable, however, we now have single quote syntax for dealing with this.

I think, possibly the original reason for this behaviour was because there was no way to write a literal dollar, say, as part of a password, without it being processed as a variable, however, we now have single quote syntax for dealing with this.

Note: Typing from mobile
Ok lets imagine we agreed on empty string approach.
now
how we handle such things ?
APP_ENV=‘${SOME_VARIABLE}-app’
APP_ENV=“SOME_VARIABLE-app”
how to identify and replace it with empty string ?

I'll just throw this in here, in case it stirs up any interest.
bash allows a default value to be used if the referenced variable is not set or null, like this:
${VARIABLE:-default}

A default empty string would then be ${VARIABLE:-}. That could be implemented as a new feature without it being a breaking change. There may be no interest in this, but I'm only here because I was searching for a solution.


fix: Module initializer bug from PR2402

PR Details
PR2402 introduced a problem which i dont know exactly what it was
xen found that nugetresolver was called too late and after swithcing the generation order a bit it started to work again
Related Issue
PR2402
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[x] I have built and run the editor to try this change out.

closing in favor of #2477


[Feature] support order by clause in show data statement (#45676)

Why I'm doing:
What I'm doing:
close #45676
What type of PR is this:

[ ] BugFix
[-] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[-] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)
[ ] I have added documentation for my new feature or new function
[ ] This is a backport pr

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

there are so many show stmt, and adding only order by to show data seems not a extensible way.


Channels should adding to the INSTALLED_APPS list.

Looks like ASGI does not run without adding the channels package to the INSTALLED_APPS list.
And there is no information or warning about that in the documents.
BTW, thanks for this beautifull package.

Yer, the channels documentation should cover this https://channels.readthedocs.io/en/stable/installation.html but it's a fair point the readme and install instruction should point people to the channels install steps first.


Bug report: Base62 does not preserve leading zeros

Describe the bug
Base62 does not preserve leading zeros
To Reproduce
https://gchq.github.io/CyberChef/#recipe=From_Hex('Auto')To_Base62('0-9A-Za-z')From_Base62('0-9A-Za-z')To_Hex('Space',0)&input=MDAxMA
Expected behaviour
I expected base62 to preserve leading zeros
Screenshots

Hi @quackduck , Can you please assign this issue to me? Thanks.

I'm not sure whether I have the perms to do that: don't see a way to.

@n1474335 Can you please assign this to me?
Thanks.


fix component name issue in ember 2.8.3

Fixes #152
This project uses semver, please check the scope of this pr:

[ ] #none# - documentation fixes and/or test additions
[x] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG

Fixed issue when running against 2.8.3, List can't get the valid component name to render.

Changes Unknown when pulling 0e2446495236c10b46542ee8ade484d238b689bf on quincyle:small-view into ** on ciena-frost:master**.

@jscharf I will approve, but I think we should do what we discussed. Instead of checking the component name checking we should use hard coded keys for the default conversion. This will avoid checking the component name and the different version handling. @jscharf can you do another PR on Monday to fix this? Thx


Make u32 shift and rotation instructions always checked

This small PR changes a little bit u32shl, u32shr, u32rotl and u32totr instructions to make them always checked — input values are always validated to be a u32 and a value less than 32.

I tested hash_2to1 and hash_1to1 functions from blake3 and sha256 modules with old implementation (shift ant rotate are always unchecked) and new implementation (always checked).
Here are the results:

Based on yesterday's discussion, I think we should probably leave the implementation as is (i.e., keep the unchecked implementation). A couple of things we could still do:

Update the docs to reflect the correct cycle counts.
Maybe introduce assert_lt instruction (so that it would be possible to do something like assert_lt.32) - though, this should probably go into a different PR (and we should probably create a separate issue for this).

btw, if you have the code for running blake3 and sha256, would be great to add it to the examples.


openStream presumes it's a file

openStream calls osclose which presumes a close function on the stream.

I'll have a look (I don't use github so I'll need to step through the process). I'm trying to figure out which project to use, this one seems most up to date and parquet-tools reads the output files fine, but dremio errors out.
This project: https://github.com/kbajalc/parquets
Dremio can read the files written using that project, but the project doesn't handle optional fields correctly. So I need to decide should I work with Dremio on figuring out why they can't read the files written using this project, or figure out how to fix kbajalc's version for optional fields.
The ironSource project itself doesn't seem to be very active.
Meanwhile, none of the available options actually works for me as the destination for the parquet files I'm writing is dremio.

Looking at this more closely you should be able to use the ParquetTransformer which basically returns a native Transform stream that can be piped into any writable stream.   You pipe the data into the ParquetTransformer and out comes the parquetFile as a stream.
Example: https://github.com/ZJONSSON/parquetjs/blob/master/test/integration.js#L436-L446

Ahh, I'll have a look at ParquetTransformer also. The osclose patch is easy enough.

I notice that snippet uses the schema level compression option, you seem to have removed that option from the code though. When I add schema level compression it doesn't do anything, only column level compression works.

I think the standard only defines compression on a column by column basis.  Not sure what the global compression was supposed to do (if anything).   Maybe either remove from test code or try to figure out how it was supposed to work.

The global compression changed the default column compression from 'UNCOMPRESSED'.


improve ConcatIterator

See #2005
Target             Impl                  Params  Count            Score  ±     Error    Unit  scala_persistent  vavr_persistent
IteratorBenchmark  scala_persistent          10      5     2,516,805.84  ±     5.65%   ops/s                             0.89×
IteratorBenchmark  scala_persistent          20      5     1,412,594.83  ±     9.46%   ops/s                             0.77×
IteratorBenchmark  scala_persistent         100      5       286,046.91  ±     1.46%   ops/s                             0.72×
IteratorBenchmark  scala_persistent        1000      5        28,910.28  ±    72.00%   ops/s                             0.73×
IteratorBenchmark  vavr_persistent           10      5     2,820,759.98  ±     4.30%   ops/s            1.12×
IteratorBenchmark  vavr_persistent           20      5     1,825,800.14  ±     7.18%   ops/s            1.29×
IteratorBenchmark  vavr_persistent          100      5       399,723.11  ±     1.46%   ops/s            1.40×
IteratorBenchmark  vavr_persistent         1000      5        39,369.96  ±     3.55%   ops/s            1.36×

@nfekete please review

Codecov Report

Merging #2011 into master will decrease coverage by 0.09%.
The diff coverage is 73.33%.

@@             Coverage Diff             @@
##             master    #2011     +/-   ##
===========================================
- Coverage     97.63%   97.53%   -0.1%
- Complexity     5155     5157      +2
===========================================
  Files            91       91
  Lines         11822    11858     +36
  Branches       1567     1575      +8
===========================================
+ Hits          11542    11566     +24
- Misses          134      144     +10
- Partials        146      148      +2

Impacted Files
Coverage Δ
Complexity Δ

...avr/src/main/java/io/vavr/collection/Iterator.java
97.5% <73.33%> (-1.84%)
174 <0> (+2)

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 0c56073...d50c100. Read the comment docs.

Need to do more tests...

LGTM. I like it's iterative, besides being faster, stack will not be a limiting factor. 👍

The only drawback I can see is that the ConcatIterator became mutable in a new way (was mutable while iterating over it, now it's also mutable while it's being built). This means that the following code is an infinite loop:
        Iterator<Integer> single = of(1);
        Iterator<Integer> concat = single.concat(single);
        concat = concat.concat(concat);
        int count = concat.count(__ -> true);

I'm not entirely sure if we should correct this kind of behavior (scala's solution behaves the same). We would need to create a copy of the linked list of Cells.

Thank you @ruslansennov and @nfekete.
I will merge it.
The drawback you mentioned is acceptable because an Iterator is mutable.The javadoc says:
 * Note: Iterators encapsulate mutable state.
 * They are not meant to be used concurrently by different threads. Do not reuse Iterators, e.g. after passing to
 * {@linkplain io.vavr.collection.List#ofAll(Iterable)}.

Especially the "Do not reuse Iterators" part is violated when concatenating an Iterator with itself.

Thank you, guys!


Error Line 566

Hello,
Have the script Openvpn 2.4 update install.
Get the following error:
line 566: syntax error near unexpected token `elif'
line 566: `	elif [[ "$OS" = 'centos' || "$OS" = 'fedora' ]]; then'

Thanks for reporting, let me check.

Line 521 shouldn't exist, is it?

Also with line 520 there will be an update twice ( see line 533 ).
PS: In scripts apt-get it's used over apt as it's have a stable cli.

I can't reproduce the bug :thinking:

@cezar97 Are you talking about the master branch? https://github.com/Angristan/OpenVPN-install/blob/master/openvpn-install.sh#L521

Wow ok a lot of conflicts there

Thanks @AMD-Threadripper @cezar97


compression rate

good work!
I'm using 10M audio codecs to train codec-bpe with a vocab_size=30k,num_codebook=4,codebook_size=1024, after training I get a tokenizer and found the compression rate is nearly 1. For example, a 4s audio with 25hz, I get 400 audio codec tokens, and using codec-bpe I get about nearly the same token-size  about more than 350 which is less then 1 ,this can yield savings of 2-5x in sequence length compared to directly modeling the flattened codebooks . I follow the steps in the readme, so can you share your codec-bpe tokenizer based on encodec or some other codec?

Hey @HaiFengZeng, couple of questions:
(1) Which codec are you using?
(2) What dataset or type of data are you training on?
The compression rate achieved with codec-bpe is largely dependent on these two factors. If the codec you are using is already using a low bitrate then you will get smaller gains from further compression (e.g., 1.3-1.5x instead of 2x). Also, if your dataset contains more diverse audio such as thousands of different speakers and recording conditions, then you will need a much larger vocab_size to approach 2x compression.
I am planning to release some models with corresponding tokenizers within the next month or so. For now, I suggest increasing your vocab_size and also try restricting the number of codec 4-grams (acoustic units) that can be loaded into the same token using max_token_codebook_ngrams=1. This causes the tokenizer to avoid merging longer codes sequences, leading to a wider breadth of coverage for your coarse codebooks within your vocab_size budget.
Some of the compression rates I've observed in testing:

EnCodec 24khz on conversational  speech data (the Fisher telephone corpus) with a vocab size of 80k and 2 codebooks yielded approximately 2x compression from 150 tok/sec to ~75 tok/sec
Kyutai Mimi codec on conversational speech data (also Fisher) with a vocab size of 30k and 4 codebooks yielded approximately 1.25x compression from 50 tok/sec to ~40 tok/sec
Kyutai Mimi codec on audiobook data (libri-light unlab-6k) with a vocab size of 80k and 4 codebooks yielded approximately 1.3x compression from 50 tok/sec to ~38 tok/sec

Thks, I'm using funcodec, and 30k vocab_size, it's about 100tks/sec, I will try large vocab size and see if I can get better compression

@HaiFengZeng I also got same result with FunCodec, the ratio is 1, even increased the vocab size to 50k.

Oh silly me, I forgot use tokenizer.encode(), just tested with my 5k dataset, the compression rate is 1.02x, I think it is mainly due to the size of of my dataset, will try increase the dataset size.

@indiejoseph what dataset are you using? I can run some tests and see if I get the same results. 1.02x compression seems really low.

fsicoli/common_voice_19_0 zh-HK subset


Implement workflow for setting recipe version

In case it could be useful, here is some code I use to edit conda recipes.
The quickest option is to use sed. I like this approach for its simplicity, but it's also caused me problems when the file has been edited, and the patterns no longer match. Here's the code for bumping the build number:
# Ensure build number is 0
sed -i \
  s/"  number: [0-9]\+"/"  number: 0"/ \
  recipe/meta.yaml

A more robust option is to parse the recipe with ruamel.yaml, but this requires Python.  The payoff is that the code is much more robust and easier to read.

I am currently investigating if we could rework https://github.com/dudoslav/cf-scripts in order to create PRs for our repos so this PR is inactive for few days.

Closing this PR since this should be implemented by conda forge autobot


propose new maintainers

Just opening a maintainer proposal PR as per our usual workflow. However - I think now we need @graphql/tsc  to approve it!
Already Maintainers (just not listed):

@n1ru4l
@thomasheyenbrock

Proposed Maintainers

@saihaj - maintainer of graphql-js!
@stonexer - long-time contributor to the LSP server and underlying language services, as well as graphiql!
@B2o5T - has been doing essentially maintainer-level housekeeping work that otherwise I would be doing! also for PRs, etc.

Overall, this should enable more officious cross-team collaboration & peer review between the guild/stellate, and as well having @stonexer on board will help me tremendously with maintaining and improving the LSP server side of things.
Past Examples
To see how this process has worked in the past:
https://github.com/graphql/graphiql/pull/1957
https://github.com/graphql/graphiql/pull/1759
If you would rather be on neither list that's fine as well, but this is our transparent way of approving new maintainers at least!

Thanks!😻

Thanks 🚀

Thanks yourselves for all the fresh energy & momentum! :)


Improving Documentation

Hey CatsInTech
I would like to work on your README.md section and make it more concise and improve its readibility
Please assign it to me under GSSOC'23
Thanking you

Can you please assign me this project as a GSSOC contributor

Hey, welcome to GSSoC ’23, this is an amazing idea. But half the things have already been done. There’s a Landing Page that’s half completed and there’s the App that’s been half completed too! I’m currently setting things up and also adding the videos for those who are completely new. Will be creating labels and assigning it. Can we please wait for a day max until I make the ReadMe and push the base code and base branches (one for the web and another for the app)? 🙏🏻
Thanks, it won’t be long. A new video will be coming up. Don’t close the issue, we’ll see how we can make it fit. 💪🏻

@praveenscience sure thing, we'll together try to make the project a success!

Sure @Rajwardhan1, lemme push the initial code, etc.

Please assign me this task so that I can work on it and make my contribution Under GSSOC's 23 Program.

@Aditya-Aware I would appreciate more if you read and stay here and not copy paste! Thanks.


Added version constant to libretto.go - 0.9.0

Tiny change to add a version constant to the library. This uses semantic versioning, therefore it is set as a string. The caller would be responsible for parsing the value into major, minor, point.
@mbhinder @tw4dl @lilirui

LGTM


[Snyk] Upgrade @types/node from 20.10.6 to 20.10.7

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @types/node from 20.10.6 to 20.10.7.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 22 days ago, on 2024-01-07.

Release notes

Package name: @types/node

20.10.7 - 2024-01-07

20.10.6 - 2023-12-30

    from @types/node GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@039a8d5). Click here to learn what that means.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #75   +/-   ##
=======================================
  Coverage        ?   74.78%
=======================================
  Files           ?        8
  Lines           ?     1967
  Branches        ?      204
=======================================
  Hits            ?     1471
  Misses          ?      489
  Partials        ?        7

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Why does this plugin install luarocks/hererocks without my consent?

I just updated my plugins and for some reason it starts installing hererocks, I don't have that plugin listed anywhere in my configuration.

same here

I believe it's because #346 introduced a rockspec. You can disable luarocks in your lazy setup with rocks = {enabled = false,}.

I believe it's because #346 introduced a rockspec. You can disable luarocks in your lazy setup with rocks = {enabled = false,}.

Could you please share your configuration? I tried this, but still getting error:
  {
      "mhartington/formatter.nvim",
      event = "VeryLazy",
      opts = {
          rocks = {
            hererocks = false,
            enabled = false,
        },
      },
  },

I just reverted the parts of #346 that included tests for now. Sorry for the confusion folks.


chore: Refactored to simplify code base and changed some inputs from "" to null

Description
This change is to remove the code duplication that occurs over the 4 VPN resource flavours. These resources had about 90% duplicate code and changes others made needed to be made in several places. This refactor consolidates to a single resource utilising the feature from terraform 0.12.0 passing null as a value for a resource attribute is like not passing the value at all. This means we can just put all the attributes into a single resource and default the values to null. so only those attributes a user sets will be passed to the resource.
Motivation and Context
Reading the module source when not familiar with it can be confusing for new users and because there are several flavours that all repeat 90% of the code. Making a small change currently actually requires you to update that code change in multiple places. this can lead to users not realising the code needs replicated in other resources.
Addresses https://github.com/terraform-aws-modules/terraform-aws-vpn-gateway/issues/90
Breaking Changes
This will be a breaking change as it changes the input default for 4 variables from a default of empty string to a default of null

tunnel1_inside_cidr
tunnel2_inside_cidr
tunnel1_preshared_key
tunnel2_preshared_key

This is likely to be a rare use case where by a user would explicitly pass one of the values as an empty string. However it should be change of the major version since its a change of the public interface. While this could have been handeled in local variables by evaluating the value and if its an empty string set it to null. However the best practice here is to set as null as the default variable as it bring its in line with terraform practices and the default values for other variables. It also reduces code complexity in the module source.
How Has This Been Tested?

[ X ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[ X ] I have tested and validated these changes using one or more of the provided examples/* projects
[ X ] Updated the complete-vpn-gateway example to pass empty strings to the module. I have written terratest file to test the main changes here which are around the 4 variables above. These tests all passed
[ X ] Refactored the main source and updated the example with null values and reran the terratest which passed.
[ X ] I have included the terratest code in this merge incase anyone wants to automate it in github actions or to allow others to run tests with it
[ x ] I have executed pre-commit run -a on my pull request

this is not a change we are prepared to accept as its written. Lets work out any details through an issue first

Thanks Bryant. I have issue 90 open for this work. Happy to chat there about it more


Static method 'buildExpression' requires the types 'Substring.UTF8View' and 'Substring' be equivalent

Hey! I have a compilation error with the Parser below.
This parser worked before 0.12.0 with Xcode 13 and lazy var syntax instead of the new SwiftUI body syntax.
I am not sure what the issue is here or what I have to change for this to work.
import Parsing

// example: `name="value" name2="value2"`
struct AttributesParser: Parser {
    typealias Output = Dictionary<String, String>

    var body: some Parser<Substring, Output> {
        Parse {
            Many {
                PrefixUpTo("=")
                    .map(.string)
                "="
                Parse {
                    "\""

                    PrefixUpTo("\"")
                        .map(.string)

                    "\""
                }
            } separator: {
                Whitespace(1..., .horizontal)
            }
        }
        .map { attributes in
            Dictionary(uniqueKeysWithValues: attributes)
        }
    }
}

// example: `a href="example.com" target="blank"`
struct TagContentParser: Parser {
    typealias Output = (String, [String: String])

    var body: some Parser<Substring, Output> {
        Parse {
            Prefix { character in
                character.isLetter
            }
            .map(.string)

            Optionally {
                Whitespace(1..., .horizontal)
                AttributesParser() // <- Error here
            }
            .map { attributes in
                attributes ?? [:]
            }

            Whitespace(.horizontal)
        }
    }
}

Hey @ilendemli,
I'm not fully across the recent changes but using [String:String]() or .init() instead of [:] resolves the error for me.
You can also use .replaceError(with:) as an alternative to Optionally + .map(_:) if you're providing a default value.
Parse {
  Prefix(while: \.isLetter)
    .map(.string)

  Parse {
    Whitespace(1..., .horizontal)
    AttributesParser()
  }
  .replaceError(with: [String: String]())

  Whitespace(.horizontal)
}

@iampatbrown Interesting, this seems to be it. I noticed the type of attributes in my map is understandable [String: String] coming from AttributesParser.Output. So it makes sense to use [String: String](). But I would still have expected [:] to work here.


Sparse array reductions

This avoids creating dense auxiliary sparse.COO arrays in reductions, which will in general not have the same fill_value as actually sparse arrays, preventing basic arithmetic between them.
This works, but I'm a bit worried that it will cause problems for other array implementations like cupy, and it may be better to go through the dispatch mechanism.

[x] Closes #7169
[x] Tests added / passed
[x] Passes pre-commit run --all-files

Okay, as I feared, this does indeed make cupy unhappy -- I'll work on pushing some of this into the dispatch system

Thanks for the ping @ian-r-rose . As you noted yourself, unfortunately CuPy Sparse is largely uncovered at the moment, I may be mistaken but I think it's usage is fairly limited today, which is also why it didn't get much attention lately.
In briefly trying to increase coverage, I found that Dask arrays backed by cupyx.scipy.sparse.coo_matrix don't respect the chunktype, even if we pass meta=cupyx.scipy.sparse.coo_matrix((0,0)), and CSR matrices don't seem to respect chunktypes for matrices larger than 2 dimensions. I don't have enough bandwidth now to look further, @jakirkham is this something you would be interested/have bandwidth to look at? If not, then I'd suggest this PR may go in even without further CuPy testing.

It looks like this also closes https://github.com/dask/dask/issues/8280?

I haven't really tackled that issue here -- it seems more involved and may require actual work on the algorithm (based on the WIP commit linked by the user)

Just added one more commit adding some additional test coverage, in case you have a few minutes @jrbourbeau

Sorry for the lack of reply here. Responded in one thread above where I was pinged.
IIUC the other question is whether we want to support sparse CuPy matrices with numel? As CuPy sparse matrices are fairly similar to their SciPy sparse matrix counterparts, would ask whether SciPy sparse matrices are supported? If not, then wouldn't worry about CuPy. If someone asks about numel for sparse matrices, we can worry about it then :)


Failed at the este@ install script 'gulp fix-react-native'

Im not able to finish npm install due to error:
Failed at the este@ install script 'gulp fix-react-native'.
npm ERR! Darwin 15.4.0
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.7
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR! este@ install: `gulp fix-react-native`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the este@ install script 'gulp fix-react-native'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the este package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp fix-react-native
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs este
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls este

OS X 10.11.4
node v0.12.7
npm  v3.8.6

First things first, you should be running a recent version of Node:
[package.json]

...
  "engines": {
    "node": ">=5"
  },
...

Sorry guys, my fault! Thanks

Hello friends, same issue, but with node 5.11.0 and 6.0.0
vagrant@webapp:/vagrant$ gulp -v [00:57:30] Failed to load external module babel-core/register [00:57:31] Failed to load external module babel/register [00:57:31] CLI version 3.9.0 [00:57:31] Local version 3.9.0
`vagrant@webapp:/vagrant$ npm install --no-bin-links

este@ install /vagrant
gulp fix-react-native

[01:08:13] Failed to load external module babel-core/register
[01:08:13] Failed to load external module babel/register
/vagrant/gulpfile.babel.js:2
import bg from 'gulp-bg';
^^^^^^
SyntaxError: Unexpected token import
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:511:25)
at Object.Module._extensions..js (module.js:550:10)
at Module.load (module.js:456:32)
at tryModuleLoad (module.js:415:12)
at Function.Module._load (module.js:407:3)
at Module.require (module.js:466:17)
at require (internal/module.js:20:19)
at Liftoff.handleArguments (/home/vagrant/.nvm/versions/node/v6.0.0/lib/node_modules/gulp/bin/gulp.js:116:3)
at Liftoff. (/home/vagrant/.nvm/versions/node/v6.0.0/lib/node_modules/gulp/node_modules/liftoff/index.js:193:16)
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm ERR! Linux 3.13.0-85-generic
npm ERR! argv "/home/vagrant/.nvm/versions/node/v6.0.0/bin/node" "/home/vagrant/.nvm/versions/node/v6.0.0/bin/npm" "install" "--no-bin-links"
npm ERR! node v6.0.0
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR! este@ install: gulp fix-react-native
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the este@ install script 'gulp fix-react-native'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the este package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp fix-react-native
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs este
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls este
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /vagrant/npm-debug.log
`

Same problem here... npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm ERR! Linux 3.13.0-85-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v5.11.1
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR! este@ postinstall: gulp native && gulp build --production
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the este@ postinstall script 'gulp native && gulp build --production'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the este package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp native && gulp build --production
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs este
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls este
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/zigo/projects/este-app/npm-debug.log


Problem in parsing cloneDR results folrder in Eclipse-JDeodorant-Plugin

I am working on JDeodorant to refactor duplicate code.
cloneDR tool has detected code clones in JHotDraw 7.0.6,
but while parsing cloneDr result folder a message is encountered every time "An error has occurred during parsing. An input file (s) may be corrupt.

From what I see in the screenshot JHotDraw 7.0.6 project has compilation errors. Please fix these errors first and then try again.

Dear sir
I have tried it on jedit 4.2 and jhotdraw 5.2.
In that error is encountered "source code for 366 instances is missing "
On Mon, Feb 11, 2019, 8:10 PM Nikolaos Tsantalis<EMAIL_ADDRESS>wrote:

From what I see in the screenshot JHotDraw 7.0.6 project has compilation
errors. Please fix these errors first and then try again.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tsantalis/JDeodorant/issues/66#issuecomment-462351017,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AtUV2L-4rPnSc-P79uXRbiK3GR8VqwVeks5vMYDwgaJpZM4azwHK
.


Add support for armv7 hardfloat build

Support for explicit float ABI specification is required for hardfloat platform build.

Hi @rayslava
Please submit the patch for review to https://review.mlplatform.org/admin/repos/ml%2FComputeLibrary
We don't take patches on github, we only publish the release snapshots here. For more information see https://arm-software.github.io/ComputeLibrary/v21.05/contribution_guidelines.xhtml


Allow create and change operations to complete asynchronously

Currently all create and change operations are forced to happen sequentially. This change allows those operations to complete asynchronously, so that the files can be processed in parallel.
This gives a small speedup (~2-5%), and is the first step to improving the throughput of broccoli-babel-transpiler. This may also be useful for other plugins based on this filter.

@rwjblue lets pow-wow.

released as v1.4.0 🎉