Error 1083: can not open include file: 'hdf5.h': No Such file or directory

I am using windows 10 opencv 3.0.0 Vs 2013, when i debug the program it gives me the following errors:
Error 1083: can not open include file: 'hdf5.h': No Such file or directory
IntelliSense: can not open source file "hdf5.h"
even i link libraries etc by a good way. "hdf5.h" exist in C:\opencv-3.0.0\opencv\build\include\opencv2\flann but still it is giving me issue. can anybody help me?
Thanks

Your build line?
<your projects build command>   --fallback-to-build --hdf5_home_win=<your native hdf path>

where  has the hdf5 include and lib folder for hdf5?

sorry, i didn't understand what you mean. i only have hdf5.h file in C:\opencv-3.0.0\build\include\opencv2\flann\hdf5.h   except this hdf5 file, i dnt any hdf5 in my pc.

i downloaded HDF and isntalled in C:\Program Files\HDF_Group\HDF5\1.8.18, now what to do next?
what do you mean by    --fallback-to-build --hdf5_home_win=

--fallback-to-build has to do with prebuilts I put on Amazon; if your case matches up it just downloads them(no need to build in that case).
--hdf5_home_win=C:\Program Files\HDF_Group\HDF5\1.8.18

your install location is passed to your npm install and even if hdf5.node(hdf5) is a package within another project this switch will tell hdf5.node where the native hdf5 is located  when building.  See https://github.com/HDF-NI/hdf5.node/blob/master/binding.gyp#L4
It replaces this build variable from command line.
Make sure you have node-gyp installed; node-pre-gyp uses it

which nodejs version are you using?

I have the same problem, I am using windows 10 , Vs 2013. When I compile a project. These errors happen:
Error 1083: can not open include file: 'hdf5.h': No Such file or directory
IntelliSense: can not open source file "hdf5.h".
But I am sure I have linked the project to the directory where there is the file “hdf5.h”.
How do you solve this errors? Thank you. @rimmartin @MaQsoodShah

what is your build command?
npm install --hdf5_home_win=C:\Program Files\HDF_Group\HDF5\1.8.18

--hdf5_home_win needs to point to base directory of hdf5 native installation

Thank you very much for your reply. I have solved this problem.
What I did is change the platform to x64. @rimmartin


fix: handle mix rebar deprecations for 1.18

The two deprecations are:

Mix.Rebar.local_rebar_cmd/1 -> Mix.Rebar.local_rebar_path/1
Mix.Rebar.rebar_cmd/1 -> Mix.Rebar.available?/1 + Mix.Rebar.rebar_args/2

I haven't checked whether all of this is covered by existing tests and am not entirely sure how to test this properly. Suggestions welcome.
Contributor checklist

[ ] Bug fixes include regression tests
[ ] Features include unit/acceptance tests

I thought I had covered that here: https://github.com/ash-project/igniter/commit/286294b365e26e29cf57266a6b6eea84a64096af but I guess not?

🚀 Thank you for your contribution! 🚀


Moving Restore functionality to the mssql extension

Initial PR for the Restore dialog
This PR contains the changes of creating and opening a new OM restore dialog that gets the pre-defined values from the mssql and restores the database with the selected available options.
TODO: Script button.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.001%) to 41.574%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/book/bookTreeView.ts
1
36.91%

extensions/notebook/src/dialog/configurePython/configurePathPage.ts
1
57.02%

Totals

Change from base Build<PHONE_NUMBER>:
0.001%

Covered Lines:
30787

Relevant Lines:
69356

💛  - Coveralls

That initial loading time was very long in the provided video. Any idea why that is? The current Restore dialog opens immediately for me.

That initial loading time was very long in the provided video. Any idea why that is? The current Restore dialog opens immediately for me.

Yes, I observed the lag. The existing one open the dialog quickly but does not load any data (such as fetching restore plan), once the user selects the source database then only it gets the data. But opening a new dialog returns the whole data which consumes 5seconds of time to fetch the restore plan(time calculated during debug time). I believe OM InitializeObjectView() is some what adding delay. Looking into it.

If the time delay is in the initialize step, does it also extend to opening other dialogs? If so, we might want to break out fetching the restore plan into a separate method.

Is the gif you have in the original description still accurate with the long delay for opening? Please update it if not

Update: Added new video.


PluginError: Unable to locate a Java Runtime

Hi, I installed gulp-html 3.2.0 on macOS 11.0.1, added it to a gulp pipeline, and when I run it, I get the following error:
[PluginError: The operation couldn’t be completed. Unable to locate a Java Runtime.
Please visit http://www.java.com for information on installing Java.]
# This is followed by a very large JSON object.

I'd rather not manually install a Java runtime. Do I have an implementation error, or is this a bug?
Here's my code:
// ./package.json

{
  "scripts": {
    "validate": "gulp validate"
  },
  "devDependencies": {
    "gulp": "^4.0.2",
    "gulp-cli": "^2.3.0",
    "gulp-html": "^3.2.0"
  }
}

// ./gulpfile.js

const { src, dest } = require('gulp')
const validator = require('gulp-html')

/**
 * Validate HTML.
 * Usage: `gulp validate`
 *
 * @since unreleased
 *
 * @return {Object} Gulp stream
 */
exports.validate = function validate () {
  return src('./src/**/*.html')
    .pipe(validator())
    .pipe(dest('./src'))
}

Thank you!

False alarm. I think one of my other dependencies (not mentioned above) threw the error or collided with gulp-html. Closing this out.

vnu.jar needs Java to run so unless you install it, you cannot use it.


refactor: extract routing to package

Even the unfinished draft is pretty much un-reviewable — we can go through how the new system works once it's ready.
I noticed while starting to build a routing system that pretty much exactly what I was building was already built by someone, so I used that package. It's a bit obscure (little use), but any code I would write would be, too, and I didn't want to NIH, esp. considering that it would have been quite some effort. We can always fork if it becomes necessary.
This will need a lot of manual testing.
Some hrefs are still left, e.g. when the href prop also indicates whether an edit link should be shown at all, or in weird cases like the terms/privacy policy where the routing would need a rework anyway. This does not claim completeness, but the important bits in the complex sections, in particular with parameters in routes, are done.
In the future, it might also make sense to use the query param support of typesafe-routes to cover cases like NetworkPage with its search query param.

Tom and I had a call about it, and tested everything on the live environment


uses the ./jq parser to show node specific info

Uses the ./jq parser to show node specific info
At the moment the only function written is the pv|package_version function that shows the current node projects package.json version.
While inside the root of a node project (containing a package.json file) type:
> pv
or
> package_version
Displays the project version
v8.0.1

Has no interest.


FTL research for IR3 requires all packs

The earlier FTL researches requires all science packs, where i think the first one should only show a few?

If you compare it to the original Space Extension, yes. The FTL research there required fewer packs.
However, I personally found it a bit strange that, so far in the game, the tech would require only the basic science packs. I therefore changed it to require more of them but drastically reduced the amount of packs needed for each research tier. So that in the end it shouldn't make much of a difference. Especially with the newly added stage where you need to ramp up the production anyways.
I've tested this in vanilla and a few other modpacks, not with IR3 tho.
Is it too step for IR3 packs?
Would it be better to reduce the amount needed in IR3 or actually remove some science packs?
There's also a startup option for a "classic mode" which reverts these FTL changes back to the original behavior but also removes the new last stage I added.

Ah I see your reasoning. To start, I like the new final stage. But I also
liked that in the previous space extension the FTL research would start
with only 1 and then 2 and then 3 etc. packs.
Because when going for these final researches, you are faced with the fact
that your current base for example would only allow for like 100 SPM while
you will need 1000 SPM to make it bearable. So I go out to make new Sub
Factories per pack to supply 1000 SPM. And thus I will start building the
red pack one, which is done quickly, and i could start using this 1000 SPM
straight away, because the first FTL would only need red packs. Then I will
start building the second sub factory, which I can then use.. etc etc.
So in the current scenario, I've already built 3 sub factories, but they
are not yet activated, because all the FTL researches needs 5 packs...
To conclude, the ramping up of the packs needed, allowed for early use of
sub factories and to see if everything is working properly before moving on
to the next subfactory. It felt like a more gradual experience.  So perhaps
what is needed is to split up the classic mode option, to allow the final
stage, but with the classic FTL costs.
On Sat, Oct 28, 2023 at 10:02 AM elmodor @.***> wrote:

If you compare it to the original Space Extension, yes. The FTL research
there required fewer packs.
However, I personally found it a bit strange that, so far in the game, the
tech would require only the basic science packs. I therefore changed it to
require more of them but drastically reduced the amount of packs needed for
each research tier. So that in the end it shouldn't make much of a
difference. Especially with the newly added stage where you need to ramp up
the production anyways.
I've tested this in vanilla and a few other modpacks, not with IR3 tho.
Is it too step for IR3 packs?
Would it be better to reduce the amount needed in IR3 or actually remove
some science packs?
There's also a startup option for a "classic mode" which reverts these FTL
changes back to the original behavior but also removes the new last stage I
added.
—
Reply to this email directly, view it on GitHub
https://github.com/elmodor/factorio-space-extension/issues/1#issuecomment-1783741068,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHLRRVAU5V6ZFNTZXL7ZFULYBS323AVCNFSM6AAAAAA6S23WAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTG42DCMBWHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks! And yeah that makes sense.
Now I have to think which mode should be default, hah.
I will def. add a setting for this.

I set this as the new default behavior because, as you mentioned, it makes more sense if you are in the process of ramping up the science production to have something to research in the meantime.
Added a startup setting to include all science packs for all FTL researches tho.

Awesome, thanks for the lightning fast update!
On Sat, Oct 28, 2023 at 4:38 PM elmodor @.***> wrote:

I set this as the new default behavior because, as you mentioned, it makes
more sense if you are in the process of ramping up the science production
to have something to research in the meantime.
Added a startup setting to include all science packs for all FTL
researches tho.
—
Reply to this email directly, view it on GitHub
https://github.com/elmodor/factorio-space-extension/issues/1#issuecomment-1783832814,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHLRRVGAGBRTOE3D3YOCMTTYBUKH5AVCNFSM6AAAAAA6S23WAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTHAZTEOBRGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

sorry to bother you again. i would like to point out that the information
page on the mod portal should also reflect this change?
Again thanks, i'm really enjoying this mod.
On Sat, Oct 28, 2023 at 5:40 PM Sipke Sangers @.***> wrote:

Awesome, thanks for the lightning fast update!
On Sat, Oct 28, 2023 at 4:38 PM elmodor @.***> wrote:

I set this as the new default behavior because, as you mentioned, it
makes more sense if you are in the process of ramping up the science
production to have something to research in the meantime.
Added a startup setting to include all science packs for all FTL
researches tho.
—
Reply to this email directly, view it on GitHub
https://github.com/elmodor/factorio-space-extension/issues/1#issuecomment-1783832814,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHLRRVGAGBRTOE3D3YOCMTTYBUKH5AVCNFSM6AAAAAA6S23WAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTHAZTEOBRGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Sorry for the late reply, I had added the changes to the changelog as well as added following line to the main mod page:
Ability to use all science packs for FTL research (see startup settings)
Do you think there should be added something else/more?
Glad you are enjoying it!

Well im nearing the finish line, the last research is a stretch, as it should be. :-) This is how my IR3 base is looking now:

Looking good! Well done


Remove unused contract reads and code

Minor cleanup here - the main thing I noticed is that the Layout component had a couple contract reads that weren't being used. Per our chat this morning, removing those may help performance (slash alchemy usage)!
Also removed some unused packages, imports, and other code.
A couple future improvements I think could be nice to make, some just for DX and some actually impactful:

Update linting/formatting setup to ensure things like the unused reads don't make it back into the codebase
Update TW setup so we don't have to commit the generated code each time
Server render relevant pages. Can do this with Next 13 which would also allow us to simplify the Layout setup, remove next-seo, and improve page performance.
Update styling to reduce layout shift before the builder dao components load

Let me know what you think! Happy to continue working on any/all of these if you're down, I think they will help simplify things which will make it much faster to implement the Feed and other features in the future.

Looks great, LGTM! Thanks again. Also all of those improvements sound great -- I have a few other ideas I'll send you that might make sense not just for performance but also for the new UI updates we're making.


support using native tcp

Hi,
is there anyway to add support for native port(9000)
there are some performance improvements
so that there is this project:
https://github.com/housepower/ClickHouse-Native-JDBC
which supports it
however, it does not support secure connection
thanks, Itzik

It's going to take a while... We need to refactor the code to abstract protocol layer first, and then we should be able to add support for both grpc and native. #537 is the roadmap I can think of at this point.

It's going to take a while... We need to refactor the code to abstract protocol layer first, and then we should be able to add support for both grpc and native. #537 is the roadmap I can think of at this point.

0.3.2 supports two interfaces: http and grpc. I'll add tcp in 0.3.3.
As to performance, I think 0.3.2 performs well according to benchmark results at #768.

Second this. When this will be supported?

bump


Route state field should be just T

Description

Route has a state field that is currently Option<T>.
The reason that this is an option is because stdweb's API doesn't support getting the state outside of an event.
This can still be shimmed in using the js! macro.

This issue in stdweb is related: https://github.com/koute/stdweb/issues/371
If anyone sees this, I would be willing to port my implementation to stdweb after it is done here.

Given the description of the api here: https://developer.mozilla.org/en-US/docs/Web/API/History/state
It appears that either the Option must stay, or the type T must implement Default.
Since Default is already a bound on T, I'm inclined to go forward with removing the option


Bug(transloco-scoped-libs): transloco-scope-libs script failing

Is there an existing issue for this?

[X] I have searched the existing issues

Which Transloco package(s) are the source of the bug?
Scoped Libs
Is this a regression?
Yes
Current behavior
Since upgrading to v3.0.2 / v3.0.0 of transloco and transloco-scoped-libs respectively, when I execute the transloco-scoped-libs command, I get this error:
><EMAIL_ADDRESS>transloco:extract-scoped-libs /Users/crash/git/iko-travel-spa
> transloco-scoped-libs

/Users/crash/git/iko-travel-spa/node_modules/@ngneat/transloco-scoped-libs/src/index.js:11
const { watch, ['skip-gitignore']: skipGitIgnoreUpdate } = command_line_args_1.default(optionDefinitions);
                                                                                ^

TypeError: command_line_args_1.default is not a function
    at Object.<anonymous> (/Users/crash/git/iko-travel-spa/node_modules/@ngneat/transloco-scoped-libs/src/index.js:11:87)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
    at internal/main/run_main_module.js:17:47

Expected behavior
It should be copying the resources to its respective destinations as it did in the versions prior to 3.x.
Please provide a link to a minimal reproduction of the bug
https://github.com/bjornharvold/transloco-issue-515
Transloco Config
{
      provide: TRANSLOCO_CONFIG,
      useValue: {
        availableLangs: [{ id: 'en', label: 'English' }],
        reRenderOnLangChange: false,
        defaultLang: 'en',
        fallbackLang: 'en',
        prodMode: environment.production,
        scopeStrategy: 'shared'
      } as TranslocoConfig
    }

Please provide the environment you discovered this bug in
Transloco: 3.0.2
Angular: 12.2.9
Node: 14.5
Package Manager: yarn
OS: Mac OS

Browser
NA

Additional context
No response
I would like to make a pull request for this bug
No

Yes correct, previous versions work fine. Submitting a regression bug here.

I have the same error with transloco-optimize.
`
transloco-optimize dist/Name/assets/i18n
node_modules/@ngneat/transloco-optimize/src/index.js:10
const { dist, commentsKey } = command_line_args_1.default(optionDefinitions);
^
TypeError: command_line_args_1.default is not a function
at Object. (node_modules/@ngneat/transloco-optimize/src/index.js:10:58)
at Module._compile (internal/modules/cjs/loader.js:1068:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10)
at Module.load (internal/modules/cjs/loader.js:933:32)
at Function.Module._load (internal/modules/cjs/loader.js:774:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
at internal/main/run_main_module.js:17:47
`
    "@ngneat/transloco-optimize": "^3.0.0",     "@ngneat/transloco": "^3.0.6",


CI: Move tsan workflow to Engflow's remote execution

Description:
CI: Move tsan workflow to Engflow's remote execution
Same as https://github.com/envoyproxy/envoy-mobile/pull/1745 but using a couple of tsan flags instead of asan. Using a separate config for modularity.
Risk Level: Low
Testing: See tsan workflow
Docs Changes: N/A
Release Notes: N/A

@goaway This is identical to ASAN but with a few different flags. Please take a look
I also cleaned up some redundant flags and once we finish more flows we can see how to unify better the configs.

I think you can merge now.


libvisio: 0.1.3 -> 0.1.6

Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/libvisio/versions.
These checks were done:

built on NixOS
ran /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vsd2raw --version and found version 0.1.6
ran /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vss2raw --version and found version 0.1.6
ran /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vsd2xhtml --version and found version 0.1.6
ran /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vss2xhtml --version and found version 0.1.6
ran /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vsd2text --version and found version 0.1.6
ran /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vss2text --version and found version 0.1.6
found 0.1.6 with grep in /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6
directory tree listing: https://gist.github.com/a7d83a73b3560d8cfa739ca582d98dcd

Success on x86_64-linux (full log)
Attempted: libvisio
Partial log (click to expand)
shrinking /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vsd2raw
shrinking /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vss2raw
shrinking /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vsd2xhtml
shrinking /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vss2xhtml
shrinking /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vsd2text
shrinking /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vss2text
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/lib  /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin
patching script interpreter paths in /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6
checking for references to /build in /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6...

Success on aarch64-linux (full log)
Attempted: libvisio
Partial log (click to expand)
shrinking /nix/store/rjw01knr1a743fjk16s3q27chan5i9s9-libvisio-0.1.6/bin/vss2xhtml
shrinking /nix/store/rjw01knr1a743fjk16s3q27chan5i9s9-libvisio-0.1.6/bin/vsd2xhtml
shrinking /nix/store/rjw01knr1a743fjk16s3q27chan5i9s9-libvisio-0.1.6/bin/vss2raw
shrinking /nix/store/rjw01knr1a743fjk16s3q27chan5i9s9-libvisio-0.1.6/bin/vsd2raw
shrinking /nix/store/rjw01knr1a743fjk16s3q27chan5i9s9-libvisio-0.1.6/lib/libvisio-0.1.so.1.0.6
strip is /nix/store/3zq400fri5dv7d30lpxlqm2v9y1iis6j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/rjw01knr1a743fjk16s3q27chan5i9s9-libvisio-0.1.6/lib  /nix/store/rjw01knr1a743fjk16s3q27chan5i9s9-libvisio-0.1.6/bin
patching script interpreter paths in /nix/store/rjw01knr1a743fjk16s3q27chan5i9s9-libvisio-0.1.6
checking for references to /build in /nix/store/rjw01knr1a743fjk16s3q27chan5i9s9-libvisio-0.1.6...
/nix/store/rjw01knr1a743fjk16s3q27chan5i9s9-libvisio-0.1.6

Success on x86_64-darwin (full log)
Attempted: libvisio
Partial log (click to expand)
make[2]: Nothing to be done for 'install-exec-am'.
 /nix/store/ix13lzspi4vdn4wyn91l8vjl2dsfn0wa-coreutils-8.29/bin/mkdir -p '/nix/store/q0jm3dy8gw627kiik246i26ar2aq47s9-libvisio-0.1.6/lib/pkgconfig'
 /nix/store/ix13lzspi4vdn4wyn91l8vjl2dsfn0wa-coreutils-8.29/bin/install -c -m 644 libvisio-0.1.pc '/nix/store/q0jm3dy8gw627kiik246i26ar2aq47s9-libvisio-0.1.6/lib/pkgconfig'
make[2]: Leaving directory '/private/tmp/nix-build-libvisio-0.1.6.drv-0/libvisio-0.1.6'
make[1]: Leaving directory '/private/tmp/nix-build-libvisio-0.1.6.drv-0/libvisio-0.1.6'
post-installation fixup
strip is /nix/store/0fzpxnsanc02i4jsb1yhchjp4p62b2n3-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/q0jm3dy8gw627kiik246i26ar2aq47s9-libvisio-0.1.6/lib  /nix/store/q0jm3dy8gw627kiik246i26ar2aq47s9-libvisio-0.1.6/bin
patching script interpreter paths in /nix/store/q0jm3dy8gw627kiik246i26ar2aq47s9-libvisio-0.1.6
/nix/store/q0jm3dy8gw627kiik246i26ar2aq47s9-libvisio-0.1.6

NEWS: https://gerrit.libreoffice.org/gitweb?p=libvisio.git;a=blob;f=NEWS;h=9a232a7cb31f530ca6f9787c837242b3d9260d61;hb=85529f5490b7b5d8ec3e8231db3b5640bce58839

Tested with Inkscape.


cmd/cue: def not creating output

What version of CUE are you using (cue version)?

$ cue version
cue version v0.3.0-beta.5 linux/amd64

Does this issue reproduce with the latest release?
Yes.
What did you do?

cue get go k8s.io/api/apps/v1
cue def k8s.io/api/apps/v1 -o def.json

What did you expect to see?
def.json to exist and contain the def.
What did you see instead?
def.json does not exist.
If using - (stdout) it works fine.

did you go get k8s.io/api/apps/v1?
Cue does not fetch Go packages and expects them to be available locally already

Yep, I can see it in my cue.mod dir. Running without -o, or -o -, spits out what I would expect. Using k8s.io/apimachinery/pkg/util/intstr for the following snippet as the def is way smaller, but the exact same behaviour with -o is observed.
$ cue def k8s.io/apimachinery/pkg/util/intstr
package intstr

// IntOrString is a type that can hold an int32 or a string.  When used in
// JSON or YAML marshalling and unmarshalling, it produces or consumes the
// inner type.  This allows you to have, for example, a JSON field that can
// accept a name or number.
// TODO: Rename to Int32OrString
//
// +protobuf=true
// +protobuf.options.(gogoproto.goproto_stringer)=false
// +k8s:openapi-gen=true
#IntOrString: _

// Type represents the stored type of IntOrString.
#Type:     int64
#enumType: #Int | #String
#Int:      #Type & 0
#String:   #Type & 1

can you try adding the --out json flag to set the output format?

Yep.
$ cue def k8s.io/apimachinery/pkg/util/intstr --out json -o def.json
$ cat def.json
cat: def.json: No such file or directory

Can confirm, seeing the same thing on some of my configs. Applies to other formats as well, notably yaml in my tests

@verdverm Is there anything I can do to help fix this? I can't build my cue manifests at the moment because of it.

would this work for you?
cue def k8s.io/apimachinery/pkg/util/intstr --out json -o - | def.json

Unfortunately not. I'm using Bazel to build these files which does not support commands which print to stdout.

I'm not familiar with Bazel, you might try asking in Slack, there are people around who are

Actually, thank you for the suggestion. I've forked rules_cue and made this change to use output redirection. 😄

This issue has been migrated to https://github.com/cue-lang/cue/issues/802.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


"Error with nginx -s reload" or "No servers are inside upstream"

[Edited]
Hi.
I have a problem when I use a docker-compose.yml file or even a launch script.
The nginx reverse proxy give me Error running notify command: nginx -s reload when I launch the container with a script.
1. docker-compose.yml
version: '2'
services:
  nginx-proxy:
    image: jwilder/nginx-proxy
    container_name: proxy
    ports:
      - 80:80
      - 443:443
    volumes:
      - /home/proxy/certs:/etc/nginx/certs:ro
      - /etc/nginx/vhost.d
      - /usr/share/nginx/html
      - /var/run/docker.sock:/tmp/docker.sock:ro
      - /etc/localtime:/etc/localtime:ro
    environment:
      - DEFAULT_HOST=www2.lmilcent.com
      - MAX_UPLOAD_SIZE=200M
      - client_body_buffer_size=200m

  nginx-companion:
    container_name: letsencrypt
    restart: always
    image: jrcs/letsencrypt-nginx-proxy-companion
    depends_on:
      - nginx-proxy
    volumes_from:
      - nginx-proxy
    volumes:
      - /home/proxy/certs:/etc/nginx/certs:rw
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      - ACME_CA_URI=https://acme-v01.api.letsencrypt.org/directory

Log output
proxy       | dockergen.1 | 2016/09/05 19:20:19 Generated '/etc/nginx/conf.d/default.conf' from 5 containers
proxy       | dockergen.1 | 2016/09/05 19:20:19 Running 'nginx -s reload'
proxy       | dockergen.1 | 2016/09/05 19:20:19 Error running notify command: nginx -s reload, exit status 1
proxy       | dockergen.1 | 2016/09/05 19:20:19 Watching docker events

2.  Skipping notification 'nginx -s reload'

└─ $ ▶ docker exec -ti proxy nginx -s reload
2016/09/05 19:35:51 [emerg] 30#30: no servers are inside upstream in /etc/nginx/conf.d/default.conf:181
nginx: [emerg] no servers are inside upstream in /etc/nginx/conf.d/default.conf:181

It doesn't look like the letsencrypt companion is involved in your issue.

Oh, sorry, wrong repo. :/
That's because I used the exemple in the ReadMe to set up my reverse proxy container & companion.

I ran into the same issue. I started here, so initially assumed the issue was with the companion.
https://github.com/jwilder/docker-gen/issues/196

Finaly I find the solution. I added to my gitlab docker-compose file this line :
network_mode: bridge

Whatever is the network_mode name, if you have created a new network. In my case, I use the default network.


Ubuntu/kali linux run

How can run it on Ubuntu/Kali Linux? :(

In case you are still interested in an easy setup on Ubuntu, you could have a look at my fork of this repo: https://github.com/JackismyShephard/ultimate-rvc. The fork supports many new features, one of which is an easy setup using installer scripts for both windows and ubuntu :blush:


Websocket in Routers

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
# main.py
from random import randint
from fastapi import FastAPI, WebSocket

app = FastAPI()

@app.get("/", tags=["Test"])
async def index():
    return {
        "response": "Index"
    }

@app.websocket("/wsx")
async def test_socket(websocket: WebSocket, start: int = 1, stop: int = 100):
    await websocket.accept()
    while True:
        try:
            number = await websocket.receive_text()
            rndm = randint(start, stop)
            response = int(number) + rndm
            await websocket.send_json(
                {"number": response}
            )
        except Exception as error:
            break

# router.py
from random import randint
from fastapi import APIRouter, WebSocket

socket_router = APIRouter(
    prefix="/wsx",
    tags=["Socket"]
)

@socket_router.websocket("/")
async def test_socket(websocket: WebSocket, start: int = 1, stop: int = 100):
    await websocket.accept()
    while True:
        try:
            number = await websocket.receive_text()
            rndm = randint(start, stop)
            response = int(number) + rndm
            await websocket.send_json(
                {"number": response}
            )
        except Exception as error:
            break

Description
When I use this WebSocket inside of "mani.py", everything is Ok.
But when I move this WebSocket from "main.py" to "router.py" and I use APIRouter in "router.py" and then I include this router inside of "main.py", WebSocket doesn't work!
what's the solution
Operating System
Windows
Operating System Details
No response
FastAPI Version
0.73.0
Python Version
3.7.9
Additional Context
No response

Duplicated

i had the same problem, then i created class manager websocket


Install the Dapr CLI for Windows, Step 2 argument missing.

Describe the issue
In text

Step 2: Verify the installation
Verify the CLI is installed by restarting your terminal/command prompt and running the following:
dapr

It should be dapr --help instead of dapr
URL of the docs
https://docs.dapr.io/getting-started/install-dapr-cli/
Expected content

Step 2: Verify the installation
Verify the CLI is installed by restarting your terminal/command prompt and running the following:
dapr --help

Screenshots

Additional context
n/a

Complete


unsigned char printing behavior different from std::cout

If you print an unsigned char using a cstr_writer, you'll get the number printed; if you stream that value to std::cout, you'll get the character with that ASCII value.
I get this in a CUDA kernel, but it's probably the same in host-side code.

I checked that fmtlib  does as strf. It seems that it became this way at https://github.com/fmtlib/fmt/issues/217 , when a user complained that std::uint8_t was printed as char ( std::uint8_t is defined as unsigned char in many ( if not all ) compilers ).
I think it makes more sense to print unsigned char ( as well as signed char, which is used to std::int8_t ) as integers, despite std::cout doing differently.

I don't particularly mind. In that case, the host-side streaming into expected for the new testcase I introduced just needs to be altered.
Although... maybe a better possibility is for this to be controlled by a CMake option, or a preprocessor define, or even a template parameter/constructor parameter.


ci: added a custom dictionary in cspell to manage more words easily

Description
added a custom dictionary in cspell to manage more words easily
Checklist

[x] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[x] I have followed the Contributor Guide when preparing my PR.
[x] I have updated/added tests for ALL new/updated/fixed functionality.
[x] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[x] I have updated/added relevant examples in examples or docs.

Breaking Change?

[ ] Yes, this PR is a breaking change.
[x] No, this PR is not a breaking change.

Related Issues

Good idea!


Error on line, no closing quote

[Enter feedback here]
Line that contains the following:
<ItemGroup Condition="$(TargetFramework.StartsWith('net6.0-ios')) != true>
Is missing the closing quote after true.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bf87eb8f-c235-d80d-ca9f-827d4e55f74d
Version Independent ID: bf87eb8f-c235-d80d-ca9f-827d4e55f74d
Content: Configure .NET MAUI multi-targeting - .NET MAUI
Content Source: docs/platform-integration/configure-multi-targeting.md
Product: dotnet-mobile
Technology: dotnet-maui
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Thanks! I'll get this fixed.


setup.py change breaks installation on python 2.7

My team uses awscli-local in some automated tests, and version 0.19 failed to install where 0.18 succeeded.  The error we get is:
Downloading https://files.pythonhosted.org/packages/72/fe/c34701b02a6c5af1a89c6d14a02802f06b27a646a09380b2ecd957187cfc/awscli-local-0.19.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-sV1Llb/awscli-local/setup.py", line 5, in <module>
        with open('README.md', encoding='utf8') as f:
    TypeError: 'encoding' is an invalid keyword argument for this function

I'll admit I'm not a python expert, but I believe I've tracked it down to this change in setup.py:
https://github.com/localstack/awscli-local/compare/254273bce710eb69f50dcefe09e168f3d61bda60..master#diff-60f61ab7a8d1910d86d9fda2261620314edcae5894d5aaa236b821c7256badd7R5
with open('README.md', encoding='utf8') as f:

It looks like encoding is not accepted by open() on python 2.7: https://docs.python.org/2/library/functions.html#open
We have worked around the issue by pinning to version 0.18, but I wonder if our use-case is something that you are willing and able to support.

Thanks for reporting @cspotcode . We generally have dropped support for Python 2.x in LocalStack a while ago, but I think the awslocal CLI is a special case where we can continue trying to preserve backwards-compatibility. 👍 We'll release a patched version with a fix shortly.. (will ping you here once done)

Hi again @cspotcode . We have now pushed a version 0.20 which should (hopefully) fix this issue. Please let us know if the problem persists.. Thanks!

Thanks!  I likely will not be able to test the new version, since pinning to 0.18 got me unblocked and then I had to merge and close that ticket.  I realize that's not a great answer, but it is what it is.


Composition tests

Slide 6, speaker notes, describe the Prewritten Composition texts we are now up to.
https://docs.google.com/presentation/d/12jPo5RbKrfZOvbRwH3J0usuQhx0teVidiLKxgMD3Xe8
The raps need to change to cover 8-18 or so, in the “small” mode, and 19-144 in “large” mode.
Let me know if there any questions on this. I thought I also sent some sketches and stuff but I can’t find them right now.

Here I found my latest stuff, months newer than the slides, so consider the, both, thanks.
Compositions mock up.pdf


Connect wallets breaks mobile responsive

Current Behavior

Expected Behavior

Steps To Reproduce
No response
What package is effected by this issue?
@web3-onboard/core
Is this a build or a runtime issue?
Runtime
Package Version
"@web3-onboard/core": "^2.13.1-alpha.3"
Node Version
No response
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Anything else?
No response
Sanity Check

[X] If this is a build issue, I have included my build config. If this is a runtime issue, I have included reproduction steps and/or a Minimal, Reproducible Example.

Hey @magicpalmtree thanks for bringing this to our attention! Question: does the list of wallets scroll horizontally for you? This is the intended behaviour. If not then we'll fix the scroll 👍

Horizontal scrolling looks fine but is there any option to customize wallets-container class?


UNICEF Mexico - Update the Follow up forms with an additional question

Describe the bug
We need to add a question to the follow up forms - Child Follow up Visit, Pregnancy Follow up Visit, Lactating Mother Follow up Visit. There was a misunderstanding in the translation of the Koboform and feedback from the client.

[ ] We need to add a decimal question - Respiration Rate (English)/Frecuencia respiratoria (Spanish)
[ ] We need to add the following constraints:

[ ] Between 11 and 150 (inclusive 11<= x<= 150

[ ] It should be placed after the Heart Rate questions.
[ ] It should only appear for visits where the area selected Medical or Nutrition AND selected Yes to the consent at the beginning.

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
A question will appear as noted above:

[ ] We need to add the following constraints:

[ ] Between 11 and 150 (inclusive 11<= x<= 150

[ ] It should be placed after the Heart Rate questions.
[ ] It should only appear for visits where the area selected Medical or Nutrition AND selected Yes to the consent at the beginning.

Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Device: [e.g. Samsung Galaxy A2 emulator]
Android version: [e.g. Settings -> About phone -> Android version]
Build number: [e.g. Settings -> About phone -> Build number]
Version [e.g. 24]

Additional context
Add any other context about the problem here.

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."


Bring back join

The new join returns a pair of results for each side of the join. The returned result is flattened, where the fields from the left-hand side are prefixed with first. and the fields from the right-hand side are prefixed with second.
The syntax allows projection/filter over joins, however, in practice, they should all be pushed down to either the left-hand side or the right-hand side. This is not currently enforced. Not sure if we want to enforce it in typechecking or optimization, or simply leave it to genie.

Pull Request Test Coverage Report for Build 1500

156 of 182 (85.71%)  changed or added relevant lines in 9 files are covered.
67 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.05%) to 77.774%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/compiler/ops.ts
8
9
88.89%

lib/new-syntax/pretty.ts
6
7
85.71%

lib/ast/expression.ts
26
28
92.86%

lib/typecheck.ts
40
47
85.11%

lib/runtime/stream_table_ops.ts
1
16
6.25%

Files with Coverage Reduction
New Missed Lines
%

lib/new-syntax/parser.ts
67
74.01%

Totals

Change from base Build 1497:
0.05%

Covered Lines:
10504

Relevant Lines:
12984

💛  - Coveralls

Do you mind rebasing this so the "address PR comments" fixes are in the appropriate original commits? Thanks!

ugh...ok.. I need to split that commit...


[ZEPPELIN-5978] Remove support for old Flink 1.13 and 1.14

What is this PR for?
This PR proposes to remove the support for old Flink 1.13 and 1.14.
The current Flink Download Page only lists 1.16, 1.17, 1.18, and the community is discussing the final release of 1.16 called 1.16.3
Also, there are major differences in the implementation at the Zeppelin side for Flink prior to 1.15 and later versions. Thus, I suggest removing the support for old Flink 1.13 and 1.14 at this time.
Note: this PR focuses on build and docs changes, we can do code cleanup in the following PRs, e.g.

merge the flink-scala-2.12 and flink-scala-parents since Flink community decided to make the project scala-free instead of supporting new versions of scala in the future;
remove code for earlier versions of flink

What type of PR is it?
Improvement
Todos

[ ] - Task

What is the Jira issue?
ZEPPELIN-5978
How should this be tested?
Pass GA
Screenshots (if appropriate)
Questions:

Does the license files need to update? No
Is there breaking changes for older versions? Yes, it removes the support for some old versions of Flink
Does this needs documentation? Updated corresponddingly

cc @zjffdu @Reamer @jongyoul @huage1994 would like to get your review and advises

CI test  reported an error that appears to be related and I have rerun the CI test @pan3793
Error:  Errors:
Error:    ZSessionIntegrationTest.testZSession_Flink:332 »  Fail to init session, org.ap...
Error:    ZSessionIntegrationTest.testZSession_Flink_Submit:369 »  Fail to init session,...

@huage1994 I'm tackling the test failure

@huage1994 the test failure was fixed via https://github.com/apache/zeppelin/pull/4688/commits/a13175798b40359040ca6ed9b58194cd9e00a77e, the failures in this round look irrelevant, could you please help re-trigger the fail tests?

@huage1994 the test failure was fixed via a131757, the failures in this round look like irrelevant, could you please help re-trigger the fail tests?

Done

Good contribution. The latest stable version of Flink is 1.18.  I think it's time to remove support for old Flink 1.13 and 1.14.

thanks, @huage1994 and @zjffdu

Awesome PR. Many Thanks.


server: use  same initialcluster config to restart joined member

What problem does this PR solve?
detail in: https://github.com/pingcap/tidb-operator/issues/126
because some problem in etcd when joining a member. it may prepare to join failed. and we dynamically generate the join config for join member. and that's may cause the problem:
2018/10/18 03:43:15.239 main.go:92: [fatal] run server failed: couldn't find local name "demo-cluster-pd-3" in the initial cluster configuration

What is changed and how it works?
use the same join config after join success.
Check List
Tests

Unit test
Integration test(tidb-operator)

PTAL

@disksing are there any plans to put this into the next RC (assuming there is one)? This issue shows up frequently in our DinD setup, so we could also use this to produce a docker image specifically for that setup.

I think we can include it in RC5.  /cc @nolouch


Can we make a variable for imagePullSecrets for flagger helm chart?

Hi,
Can we parameterize imagePullSecrets for https://github.com/weaveworks/flagger/blob/master/charts/flagger/templates/deployment.yaml#L40 something like below so I can use your helm chart to deploy flagger from a private repository?
https://github.com/weaveworks/flagger/blob/master/charts/flagger/values.yaml
image:
  repository: weaveworks/flagger
  tag: 0.18.1
  pullPolicy: IfNotPresent
  pullSecret:

https://github.com/weaveworks/flagger/blob/master/charts/flagger/templates/deployment.yaml
...
{{- if .Values.image.pullSecret }}
imagePullSecrets:
        - name: {{ .Values.image.pullSecret }}
{{- end }}
...

Thanks.

Sure, do you want to make a PR for this?
Thanks

Sure, I think I don't have a write permission to this repo. Could you give it to me?
Thanks.

You don't need write permission to make a PR. Clone the Flagger repo, create a branch in your clone and submit your changes as a pull request.

@cmoonExpedia https://help.github.com/en/articles/creating-a-pull-request-from-a-fork


Fix finalizer doc

Follow-up to https://github.com/kubernetes/website/pull/31737 to fix glossary definition as well
xref https://github.com/kubernetes/kubernetes/issues/108025

Thank you for updating the glossary 🙏
/lgtm
/approve


Add new safe health check that doesn't disclose any system info

Changes
To enable us to turn healthchecks on in production without disclosing any sensitive information.We have added a new health check url that hides any detailed issues and
merely returns OK or DOWN for a healthcheck request, with
associated http codes of 200 and 500 respectively.
How to test

Run the app, check /health you should see a simple output of OK
Change the DEV_MODE environment variable
ReRun the app and check that you can't see /health and instead can see the current full healthcheck at /healthcheck

Who can test
Anyone but @dhilton

I can't run this outside of dev mode as I don't have keys

Can you modify your local version to trigger that scenario without having to generate a new set of encryption credentials? I realise this isn't a true test but given the change that will give a true reflection of the functionality added.

Right, got it!  The safe health check url is /status not /health, but I found it, I've seen it working, and I'm happy with it :)

LGTM :+1: Mergin'!


enabled strictHeaderCheck

#50

Coverage remained the same at 96.023% when pulling b28d467555f8b761b3a31d4cc747bf8aa42a9d8e on mreinstein:master into 3260bef62104f25bf6cd43e329783673ca2383e0 on alexa-js:master.

Needs changelog and a test please?

Coverage remained the same at 96.023% when pulling b84feda8924e8333297c28beba7de4b1bd534d08 on mreinstein:master into 3260bef62104f25bf6cd43e329783673ca2383e0 on alexa-js:master.

Much better. Still needs a CHANGELOG line.
I also winder whether we should add an UPGRADING document that describes breaking changes. Like this one. Feel free to obviously.

too much process.

LOL @mreinstein just trying to have bewildered users wondering why suddenly something returns 401 instead of 200 when they upgrade!

just trying to have bewildered users wondering why suddenly something returns 401 instead of 200 when they upgrade!

Better instead to have a broken alexa-app-server package that isn't capable of passing alexa certification? ;) Because that's the current situation.

Not trying to be difficult. Are you saying a changelog line is too much process? I can merge this as is, but I will be adding that CHANGELOG line next myself ;(

I know you're not trying to be difficult. And I'm not saying that a changelog in itself is a bad idea. It just feel like a lot more process is in place now.

2 issues I have with the current changelog:
a ) creating the changelog first, and then doing the release seems backwards to me. for one thing it's impossible to know what the version number will be, when the changes aren't done piling in. It's also confusing at first glance because when I look at a changelog I expect the top item to be the current release, not the upcoming release.
b) this isn't so much with the changelog itself but more with shipping modules. It's better to ship small changes frequently rather than piling up tons of stuff in any given release. There is virtually no costs to having additional module versions being published.
these are both hovering in the realm of opinion but I'd rather see quick agile releases that don't try to package too much at once.

I guess it's bound to happen at some point. As all these libraries grow and mature, we do eventually need more process in order to avoid development of such libraries to be a nightmare. IMO, I don't like more process but to an extent, it's necessary for the future of this library, and maybe others.

in order to avoid development of such libraries to be a nightmare

I guess that's where we differ in opinion. I believe these alexa modules are already quite mature and stable. They are in maintenance mode. They don't have extensive features that need to be added, and in fact I believe we should be resisting the urge to massively overhaul or bloat these with new capabilities.
Not having extensive process did not prevent these modules from being successful or stable, which is why most people are using them in their projects.

I agree with most things that you say @mreinstein. And we should discuss process in a separate issue, feel free to open one and propose something better.

Coverage remained the same at 96.023% when pulling e8680a26b1ff0574f80604d960ff2c37d008fe5c on mreinstein:master into 3260bef62104f25bf6cd43e329783673ca2383e0 on alexa-js:master.

Coverage remained the same at 96.023% when pulling e8680a26b1ff0574f80604d960ff2c37d008fe5c on mreinstein:master into 3260bef62104f25bf6cd43e329783673ca2383e0 on alexa-js:master.

Merged, thanks!


Bind hotkeys to enable/disable features

Currently, hotkeys that enable/disable continuous features don't actually do anything. ( Like Adblock or auto-timeframe-colors )

I've decided to separate that responsibility to another Feature instance or something else entirely.
For now, continuous features are no longer toggleable until this is implemented.


feat(streaming): backfill flow control

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

Use a rate limiter to do flow control for backfill.
The default value for stream_backfill_rate_limit is set to 200,000 rows per second.

Checklist For Contributors

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[x] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

[x] I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

[x] My PR DOES NOT contain user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

#8231

A more common approach to flow control is to use rate limit approach, e.g. limit the size of reads in some period.

A more common approach to flow control is to use rate limit approach, e.g. limit the size of reads in some period.

Yes, when using a rate limiter, the maximum quota needs to be set manually, whereas this method can adjust itself. However, I am still struggling.

I'm not sure whether it's a good idea of relying on physical time. 🥵 For example, I used to determine whether to back-pressure based on the ingestion rate of upstream & snapshot in https://github.com/risingwavelabs/risingwave/pull/3899.

I'm not sure whether it's a good idea of relying on physical time. 🥵 For example, I used to determine whether to back-pressure based on the ingestion rate of upstream & snapshot in #3899.

Hard to decide.🥵

A more common approach to flow control is to use rate limit approach, e.g. limit the size of reads in some period.

Yes, when using a rate limiter, the maximum quota needs to be set manually, whereas this method can adjust itself. However, I am still struggling.

But in the current approach, you still need to set the flow control time manually, and I think they are similar.

But in the current approach, you still need to set the flow control time manually, and I think they are similar.

Let's change it to a rate limiter which is more predictable.

I guess this is meant to address #8177, right? But I don't really understand the causality between this and #8177. Can you explain it?

I guess this is meant to address #8177, right? But I don't really understand the causality between this and #8177. Can you explain it?

This PR just provides a solution for implementing flow control, but it does not have a direct connection to #8177.

I guess this is meant to address #8177, right? But I don't really understand the causality between this and #8177. Can you explain it?

This PR just provides a solution for implementing flow control, but it does not have a direct connection to #8177.

In that case I would slightly object to this, because it doesn't solve an actual problem but probly introduce new problem.

In that case I would slightly object to this, because it doesn't solve an actual problem but probly introduce new problem. (saying, I am not sure whether it's good to limit it to 200k rows/sec)

Indeed. Let's close it until we have stronger motivation.

According to my recent experience, I'd like to add flow control as a last resort for some hard & urgent problems. The implementation may be basically the same except

The default behavior should be unlimited
It should be a session variable and only applies to the MV created on the session (Similar to set streaming_parallelism), because we only need this to fix the problematic MVs.

Additionally, as suggested by @kwannoel, Source backfilling (such as reading from Kafka with start = earliest) should also be considered. Is it possible to DRY?


fix for hooks on seed that use this var

As of 0.10.1 (presently unreleased), pre- and post- hooks on top of seed files are supported in dbt. Previously, dbt used a __dbt_tmp suffix for the {{ this }} variable in the seed's context, however, dbt creates seed tables without such a suffix. This PR treats the {{ this }} variable similarly to incremental models, wherein the suffix is not applied.

lgtm


fzf throws error on history search with commit-versioned Fish shell

[ x ] I have read through the manual page (man fzf)
[ x ] I have the latest version of fzf
[ x ] I have searched through the existing issues

Info

OS

[ x ] Linux

Shell

[ x ] fish

Problem / Steps to reproduce

Build and install Fish shell from source
Install fzf
Press Ctrl+R in Fish
fzf history widget starts, but with a few error lines at the top:

> Invalid argument: 'e19a2f9'
Invalid argument: 'e19a2f9'
Standard input (line 64):
      if [ "$FISH_MAJOR" -gt 2 -o \( "$FISH_MAJOR" -eq 2 -a "$FISH_MINOR" -ge 4 \) ];
         ^

This seems to happen when compiling Fish from source since the version output shows the commit it was compiled at instead of a version number:
[16:12:12] cat@bip /home/cat/src/fish-shell
> /usr/bin/fish --version
fish, version 3.1.2

[16:12:16] cat@bip /home/cat/src/fish-shell
> /home/cat/.local/bin/fish --version
fish, version ba2e7db

In shell/key-bindings.fish appears the cut operations grab the commit hash from Fish's version output, and tries to compare it to numbers, throwing an error like shown above. Offending code snippet:

https://github.com/junegunn/fzf/blob/7191ebb615f5d6ebbf51d598d8ec853a65e2274d/shell/key-bindings.fish#L58-L66

It might be better to match with a regex, or even just adding an if condition that checks if there's alpha characters in either the major or minor version strings.

This is still happening with the newest source: 9cb7a364a31bdb882d873807774bdcf6fad0c9e4

As a reference, the -z flag on the history command was added back in 2016 in this commit https://github.com/fish-shell/fish-shell/commit/a26f68d63fb3780a1eb0c092b31b99bc67290933, a bit before the release of fish 2.4.0 a few weeks later : https://github.com/fish-shell/fish-shell/releases/tag/2.4.0
This 2.4.0 version is quite outdate. The last 2.x release was 2.7.1 back in 2017 https://github.com/fish-shell/fish-shell/releases/tag/2.7.1 and the 3.xx line has been the beating heart of fish since.
So my take on this matter would be to remove this condition all together, assuming that fish users had plenty of time to migrate to more recent versions supporting this flag.


geometry2: 0.5.20-0 in 'lunar/distribution.yaml' [bloom]

Increasing version of package(s) in repository geometry2 to 0.5.20-0:

upstream repository: https://github.com/ros/geometry_experimental.git
release repository: https://github.com/ros-gbp/geometry2-release.git
distro file: lunar/distribution.yaml
bloom version: 0.6.8
previous version for package: 0.5.19-0

geometry2

No changes

tf2

No changes

tf2_bullet

No changes

tf2_eigen

No changes

tf2_geometry_msgs

No changes

tf2_kdl

No changes

tf2_msgs

No changes

tf2_py

No changes

tf2_ros
* Protect the time reset logic from a race condition.
  Fixes #341 <https://github.com/ros/geometry2/issues/341>
  This could incorrectly trigger a buffer clear if two concurrent callbacks were invoked.
* Contributors: Tully Foote

tf2_sensor_msgs

No changes

tf2_tools

No changes

Holding for sync exception requested.


Set request/connection time out by host

Is it possible to provide connection/request timeout option at host level in cluster.
Some host may have high traffic and may be slow, It would nice if user can set timeout at host level.

If you're using the configuration file, you can specify a different activity timeout for each cluster:
"myCluster": {
  "Destinations": {
    // ...
  },
  "HttpRequest": {
    "Timeout": "00:02:00" // 2 minutes
  }
}

If you mean the timeout to establish new connections, you can tweak the ConnectTimeout property like so
services.AddReverseProxy()
    .ConfigureHttpClient((context, handler) =>
    {
        if (context.ClusterId == "slowHost")
        {
            handler.ConnectTimeout = TimeSpan.FromSeconds(42);
        }
    });

Does that help?

@MihaZupan  Thank you for your reply.
This is very helpful.
Thanks

Triage: Answered, closing.


Incorrect Status Labels

Describe the bug
The status labels for "Moving" and "Seeding" show "Unknown" and "Stalled" respectively.
To Reproduce
Steps to reproduce the behavior:

Have one or more torrents either moving or seeding

Expected behavior
Correct labels should be shown
Actual behavior
The status labels for "Moving" and "Seeding" show "Unknown" and "Stalled" respectively.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Browser: Chromium
Build:   Ubuntu 20.04
Version: v1.10.1 .

Additional info
Thanks for your hard work :)

Those labels have been bothering me for some time! I'll go ahead an queue that up

Changes will appear in the next release 1.10.2!


[zh] sync persistent-volumes.md

Related to task-3 of issue https://github.com/kubernetes/website/issues/39985.
content/en/docs/concepts/storage/persistent-volumes.md

This link shall be synced too, which you can find by running ./scripts/lsync.sh:

@windsonsea thanks, but when I running ./scripts/lsync.sh ,it shows

This works right?

@windsonsea  thanks,./scripts/lsync.sh works on main branch. Now,I have corrected, please review.

please squash your PR into a single commit.

thanks I will squash PR

@asa3311 I was asking you to squash the PR into a single commit, not closing the PR.
Opening a new PR will lose all the review history. For large PRs, this wastes your own life and the reviewers.
Can you learn yourself some basics on git rebase -i and git push -f ?

@tengqm Sorry,I try to git rebase -i, but due to too much commits, there is something wrong. I will pay attention next time.All commits have been merged into #40016 .Please review #https://github.com/kubernetes/website/pull/40016.

/hold

/remove-approve

hi @tengqm ,Now I squashed commits , but you can review another pr https://github.com/kubernetes/website/pull/40016. because that  PR content is relatively complete. Please review~

I see open another PR, closing this one

/close


Emotion detection using Deepface module

Implementation of Deepface Module to enhance emotion detection. it is increasing the accuracy along with adding more emotions to detect.
Proposed Changes
Accuracy = 97%

Trained over 4 million images by Facebook
Additional parameter of confidence percentage
Gives dominant emotion along with percentage of all emotions
Able to recognise emotions of multiple faces from a single image

Changes are made as a part of GSSoC'24.

hey you created pr without the issue being assigned and you haven't mentioned the issue number

issue number: #1811   I introduced this module to get more accurate information through vast dataset with feature of confidence percentage.


mac osx use file type extension

 Issue by HawkenKing
Monday Mar 28, 2016 at 08:54 GMT
Originally opened as https://github.com/InfiniteAmmoInc/Yarn/issues/31

saving currently doesn't append any file type. Would be nice to have:
"test.json" instead of "test"

 Comment by blurymind
Friday Jun 22, 2018 at 09:10 GMT

This is probably fixed in the electron port (looks like a framework bug),
https://github.com/InfiniteAmmoInc/Yarn/pull/68
but I still havent made a mac build, also I dont have a mac to test with
I will try to build it in the weekend, but you will have to test it

this has been fixed for ages now


[harfbuzz] update to 5.3.1

I am sorry for my wrong operation.

Depends on https://github.com/microsoft/vcpkg/pull/28522


[WIP] Give reasons for resolving a group (#

Not sure what happened here in my browser; I didn't want to create this yet.


Document .rubyfmtignore and .gitignore behavior

Resolves #354
We added support for ignore-files some time ago, and I think some users will find them pretty useful, especially in bigger projects, so adding some docs to the README for them.

Hi, I'm trying out using .rubyfmtignore with VS code, however, it looks like the file is not being respected.

@matthewford is it respected if you run rubyfmt directly in the root directory?

@reese I suspect it is.

In that case, that sounds like something in the VSCode extension and should probably be filed as an issue there. I don't have a ton of context on how that extension works though.

Ah it looks like it passes things through stdin, which is probably why this doesn't work. I had a thought that we should support something like --stdin-filepath that prettier has, which is basically "format these contents but treat them like they're at this file path to handle e.g. file ignores," but we don't have that currently


upgrade versions:

Use play stand alone client so that clients will not have to bring the entire Play Framework in order to use the Play Json and WS libraries.
Cross build sbt (1.0.4 and 0.13.16)
Use scala 2.12 for sbt 1

I also ran scalafmt.
The generated client is injected with the standalone ws client and a simple configuration.

This looks great, haven't verified yet everything but looks nice!

Thanks @dvirf1 for this awesome PR. This is a great step towards sbt 1.x support and we are going to merge it.
Though, I kindly ask you to follow these guidelines:

submit saparate PRs for different issues, that is, one PR for sbt 1.x/Scala 2.12 support, and one PR for standalone WS client, since they are not related.

do not commit code that is simply a scalafmt reformatted code. This would make it easier for us to review the code. Scalafmt is disabled by default, since it is quite annoying to have the code automatically reformatted.

No problem. I believe I have time to do it tomorrow. I will update otherwise.

@fralken see the pull request for upgrading sbt.
After it is merged I will submit a new pull request for play 2.6 standalone client

Regarding the standalone client, I'm not sure it is a good idea to generate a case class like case class PetStoreClientConfig since it does not add anything to the generated code (unless it took the parameters somewhere from the swagger.yaml) but trivial defaults.
Actually I realised that the current implementation of the generated client cannot be injected (even if it has @Inject() (WS: WSClient) since it requires a baseUrl parameter (see the usage in the companion example).
It would be nice to implement an injectable configuration, so that I could write a client like:
class Controller @Inject()(client: PetStoreClient) where the client has its own WS (standalone) client and configuration injected.

@fralken It was separated since it can easily be injected. I'm using it with MacWire to create it (but you can also do it with Guice).

Indeed you are right. I easily injected a configuration into a PetStoreClient.

superseded by #59 and #60


[Durable Objects] pricing: clarify WebSockets pricing outside of DO

The docs only mention websockets pricing in the context of Durable Objects. For raw Workers themselves, each incoming message is billed as if it was a separate request.
This was mentioned by one of the cf support folks (green cloud) in the developer-week-2023-chat discord channel (link) just today but there's no documentation on it.

Note: I'm not sure if outgoing websocket messages are also billed.

@ignoramous this is not accurate (based on our testing, and intent). is that what you're seeing? if so, could you sent me a note with your account details at rita at cloudflare dot com?

Hi no, I am not observing otherwise, either. But it is great to know that websocket messages are free.
We were curious on how websockets would be billed if they are used standalone (without DOs). An admin (green cloud) on the group mentioned that since each websocket message is billed as a separate request for DOs, that should also be the case without DOs. I then pointed out the pricing page doesn't say so, and someone guessed that it was probably an oversight because websockets aren't meant to be used without DOs.
Hence, this PR to either clarify if websockets are billed per message (or not). I seems like they're not. So, should that be mentioned in the pricing page: WebSocket messages are unmetered and not billed. or something better?

Apologies for the confusion.

It's rare for Websockets to be used without DO since they're not nearly as useful without long running state. But yeah, happy to clarify that per message pricing is not the case for regular workers.

But yeah, happy to clarify that per message pricing is not the case for regular workers.

Thanks. I've updated the commit. If the wording isn't clear or if it is more confusing, I'm okay to change it or close this PR, even.

It's rare for Websockets to be used without DO since they're not nearly as useful without long running state

Gotcha. Outside of DO, WebSockets are now useful (to us at least) since there's possibility to make outgoing TCP connections from Workers.

I think this PR is confusingly worded as is, stateless worker websocket messages can still result in billing for duration, they just don't count towards request count

👋Hi there, we’re going to close this PR due to inactivity


Use normal composition in flavor classes

Now that we aren't backed by an array, normal composition is possible

why you not backed by an array now but future is ok ?

I'm sorry, I don't understand the question. The array backing was originally done as a way to get iteration but we have since moved to another way with listing the fields in a macro. In the future we'd want these to be as normal classes as possible.


sysctl missing

I have RHEL 7.4 with
Chef Development Kit Version: 2.2.1
chef-client version: 13.3.42
delivery version: master (73ebb72a6c42b3d2ff5370c476be800fee7e5427)
berks version: 6.3.1
kitchen version: 1.17.0
inspec version: 1.35.1
I am trying to role out an NFS server and hopefully some clients. However,
the server.rb depends on sysctl cookbook which I can no longer get.
Any work around?

I just grabbed sysctl 1.0.5 last night or so.  It should still be there.
I thought of just removing the dep in metadata and seeing how bad the wreckage was; I'm betting it'll just work, but not in Prod because #prod.  For now, I grabbed it, and I can deal with chef-14 complaining about it being there while the other cookbooks all update around the change.
cd ~/chef-repo
git submodule add \
    https://github.com/sous-chefs/sysctl.git \
    cookbooks/sysctl \
&& git add .gitmodules $_ \
&& git commit -m 'adding module' .gitmodules $_

And done!  Sooo easy to do the cheap workaround and get back to the main task, but I'm not sure whether that's sloth or pragmatism!
Roll/Role.  Heh.  I see what you did there.  :-D

Yeah, I got it too, I grabbed the code directly from GitHub too.
On Mon, Jun 18, 2018, 4:38 PM Bishop Clark<EMAIL_ADDRESS>wrote:

I just grabbed sysctl 1.0.5 last night or so. It should still be there.
I thought of just removing the dep in metadata and seeing how bad the
wreckage was; I'm betting it'll just work, but not in Prod because #prod.
For now, I grabbed it, and I can deal with chef-14 complaining about it
being there while the other cookbooks all update around the change.
cd ~/chef-repo
git submodule add
https://github.com/sous-chefs/sysctl.git
cookbooks/sysctl
&& git add .gitmodules $_
&& git commit -m 'adding module' .gitmodules $_
And done! Sooo easy to do the cheap workaround and get back to the main
task, but I'm not sure whether that's sloth or pragmatism!
Roll/Role. Heh. I see what you did there. :-D
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/atomic-penguin/cookbook-nfs/issues/109#issuecomment-398187782,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHnAoDWe0H3Z69vJuehoNYh_bo3RkaXRks5t-A_bgaJpZM4UprBL
.

sysctl 1.0.5 is on the supermarket.chef.io site.  You should be able to download it from there.

It is on the Supermarket site but probably will not work on Chef 14, as sysctl has been deprecated.  I am trying to find out what the right thing to do here, metadata wise, to maintain backwards compatibility.  That may mean a major version bump to officially support Chef 14.

probably will not work on Chef 14

We're running Chef 14.2.0 here.
I pulled down the repo as a submodule under /cookbooks, pushed it to my chefbox, and carried on (with nfs still depending on it).  It'll whine, but if we're eating the brownies before they're baked we should expect some softness in the center.
It'd be neat if things rolled into chef showed up as virtual-provides to satisfy the depends requirements.  We've got a great, long and successful history of virtual-provides and obsoletes working really well in RPM-land.

Removed dependency on sysctl in v2.6.1.  It will either use the sysctl resource on Chef-14, or file/execute resources on Chef-13.


Can't attach file in iOS

I tried to attach image file from path "/var/mobile/Containers/Data/Application/CFE323DCB-535A-4120-8532-8F8463E6B39/Documents/awik.png" in iOS.
But it throws exception called "invalid arguments (argument name: attachment)".
In detail, In iOSUnified project,  EmailTask.cs file, line no 50,
_mailController.AddAttachmentData(NSData.FromFile(attachment.FilePath), attachment.ContentType, attachment.FileName);
NSData always passed as null.
FYI, I'm using V 4.0.0

Closing due to lack of further feedback


Fixed overlapping issues occuring with BTKSA mod when QMStats are set to always show

vary lazy fix with close to no cleanup whatsoever
Changes:

fixed "AlwaysShowQuickMenuStats" not being initialized with correct value, causing overlapping issues if BTKSA preference is left untouched
version bump
don't forget to add 0Harmony.dll reference to the project, since harmony got it's own dll located in VRChat\MelonLoader\ with ml v0.5.4

The code checks out, will wait on @Kiokuu to do the final merge.


Fix(dialog, popover) restore focus when manually setting open to false

closes https://github.com/melt-ui/melt-ui/issues/1109
We now restore focus to the trigger (or using the closeFocus prop) in an effect that runs when open is false. In order to not focus the trigger on initial mount when open is false, I added a parameter skipFirstRun to the effect function that optionally skips the first run of the effect.
I also added regression tests for the dialog and popover.
Also, in the menu builder, we are already doing what I implemented with the dialog and popover, which removes the need in the menu builder to manually focus the trigger in multiple places. And I cleaned up the effect in the menu component.
Dialog Before
https://github.com/melt-ui/melt-ui/assets/53095479/584dd6ad-bd39-4901-9ff1-2a0e987f1a2e
Dialog After
https://github.com/melt-ui/melt-ui/assets/53095479/ac7ac1d1-f02e-4b2a-8f48-040438149a43
Popover Before
https://github.com/melt-ui/melt-ui/assets/53095479/89b2dc56-e1a8-47e3-9ce3-d4c42fbe41c3
Popover After
https://github.com/melt-ui/melt-ui/assets/53095479/fa3943a1-35d1-417b-afe9-cb4f5650b69d

@huntabyte I added an options parameter to effect as you requested!


[SCHEDULE] Fix boundary check

Should fix #2088.
Details about this bug are discussed in this comment.
Related issues: #1014, #2088. Related PR: #1091 (which is approximately correct when iv->dom->min == 0).
CC: @tqchen @were.

LGTM

Thanks for the contribution, please add a regression test-case https://docs.tvm.ai/contribute/code_review.html#ensure-test-coverage

@tqchen sorry I was thinking that the fix is 2-line, and the correctness should be obvious. Okay I will send an update later today

Just to make sure we don't stupidly change it back again, the regression test is also very useful during code refactor, when we might mistakenly reintroduce the bug

@tqchen Sure, I will use the example in our tutorial as the testcase, in which if ((0 <= scan.idx)) should not be there.

@tqchen added a unittest just now, CI passes, could you help review again? Thanks!


Deprecate return_str parameter in NLTKWordTokenizer and TreebankWordTokenizer

Hello!
I'd like to discuss a potential enhancements of NLTKWordTokenizer and TreebankWordTokenizer. For those unaware, the former is the tokenizer that is most frequently used, and is used in the word_tokenize function. It's also based on the latter class: TreebankWordTokenizer.
An example usage as can be found in the documentation:
>>> from nltk.tokenize import NLTKWordTokenizer
>>> s = '''Good muffins cost $3.88 (roughly 3,36 euros)\nin New York.  Please buy me\ntwo of them.\nThanks.'''
>>> NLTKWordTokenizer().tokenize(s)
['Good', 'muffins', 'cost', '$', '3.88', '(', 'roughly', '3,36',
'euros', ')', 'in', 'New', 'York.', 'Please', 'buy', 'me', 'two',
'of', 'them.', 'Thanks', '.']
>>> NLTKWordTokenizer().tokenize(s, convert_parentheses=True)
['Good', 'muffins', 'cost', '$', '3.88', '-LRB-', 'roughly', '3,36',
'euros', '-RRB-', 'in', 'New', 'York.', 'Please', 'buy', 'me', 'two',
'of', 'them.', 'Thanks', '.']
>>> NLTKWordTokenizer().tokenize(s, return_str=True)
' Good muffins cost  $ 3.88  ( roughly 3,36 euros ) \nin New York.  Please buy me\ntwo of them.\nThanks  .  '

The enhancement
As you can see from the example, if return_str is True, then the tokenize method returns a space-separated string. However, the number of spaces is very inconsistent. Perhaps we would be better off stripping spaces on the ends, and replacing all sequences of multiple spaces with just one space.
E.g.
>>> NLTKWordTokenizer().tokenize(s, return_str=True)
'Good muffins cost $ 3.88 ( roughly 3,36 euros ) \nin New York. Please buy me\ntwo of them.\nThanks .'

instead of
>>> NLTKWordTokenizer().tokenize(s, return_str=True)
' Good muffins cost  $ 3.88  ( roughly 3,36 euros ) \nin New York.  Please buy me\ntwo of them.\nThanks  .  '

I figured I would create an issue for this to find out if others agree with this idea, before I put in the time to make this change for no reason. So, I'd like to hear your thoughts.

Tom Aarsen

Could we also consider deprecating this usage... I wonder why we did this!

Yeah, sounds good. I can't really imagine a use case for this parameter to begin with.

Hi, I would like to pick this up as my first issue if possible. Does NLTK have a standard way of deprecating parameters already? I have seen the @Deprecated decorator but I am not sure how I could use it to deprecate the parameter only.

I don't believe so, no. The decorator are only for deprecating classes, methods and functions, iirc.
There's at least three options here:

Raising a warning when return_str is True, but having the functionality the same. In the future, we would remove this functionality, and for now we just warn users. This would be like a slow deprecation.
Raising a warning when return_str is True, and updating the functionality to ignore the return_str parameter. This would be like a fast deprecation.
Simply deleting all references of return_str. This would break implementations that currently use return_str without giving feedback. This would be like a sudden deprecation.

I really don't see the use of return_str, so I don't have issues with going for option 2, so we don't need to revisit this in a few months time. Perhaps other people disagree with me though.

As can be seen in the PR above, I have opted for option 2 in agreement with @tomaarsen's comment but am happy to rework if another solution is preferred.


Add MapBean Equal Method

Fixes #990

We should really use shared code in mordor and dl client... there is an AbstractEntityFX who solves all comparison issues.

I know but better fix it then leave it. Who knows when we are gonna find time for it

And chaning the data models is gonna be lots of work still.

While the proposed fix will work, I shy away from relying on equals/hashCode as it generally will cause trouble sooner or later.
Implementing equals/hashCode requires that the chosen identifier works for all use cases. When a new use cases requires it to be touched, it might or might not break other use cases.
Therefore, wherever code relies on it being implemented (like the use of MapBean in a Set, or the object being compared) I recommend to refactor it so that it explicitly uses the properties of interest.
For instance. Instead of
Set<MapBean> maps;

use
Map<String, MapBean> mapsByFolderName;

The above allows each use case to separately specify what the identity of an object is.
Could you do that, or at least point out where the problematic code is?

Like that?


Column layout problem with Bootstrap 4.beta

I'm submitting a ...  (check one with "x")
[X ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request

Current behavior
bootstrap example no longer lays out columns correctly under boostrap 4.beta and beta.2
Expected behavior

should layout row columns correctly - like the plunker does under bootstrap 4.alpha.4
Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

n/a
Please tell us about your environment:

macOS Sierra 12.6
VS Code
Angular CLI: 1.5.0
Node: 8.7.0
OS: darwin x64
Angular CLI: 1.5.0
Node: 8.7.0
OS: darwin x64
Angular: 4.4.6
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, tsc-wrapped

@angular/cli: 1.5.0
@angular/material: 5.0.0-rc0
@angular/service-worker: 1.0.0-beta.16
@angular-devkit/build-optimizer: 0.0.32
@angular-devkit/core: 0.0.20
@angular-devkit/schematics: 0.0.35
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.8.0
@schematics/angular: 0.1.1
typescript: 2.4.2
webpack: 3.8.1

Angular version: 2.0.X

yes

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Chrome (latest)

Language: [all | TypeScript X.X | ES6/7 | ES5]
all
Node (for AoT issues): node --version =

additional note: both 4.beta and 4.beta.2

just reproduced this in the bootstrap template  plunker (by swapping the versions)

see https://github.com/formly-js/ng-formly/issues/515#issuecomment-339782960


Build failure: pythonPackages.cffi on x86_64-darwin

Steps To Reproduce
Steps to reproduce the behavior:

build cffi (from 24.05, but unstable is the same at the moment) on x86_64-darwin (macOS 13.6.6)

Build log
building '/nix/store/1rbs81pi4axxxpj64lvc9x6vdwkp4q7i-python3.11-cffi-1.16.0.drv'...
error: builder for '/nix/store/1rbs81pi4axxxpj64lvc9x6vdwkp4q7i-python3.11-cffi-1.16.0.drv' failed with exit code 1;
              last 25 log lines:
              >      /nix/store/jnc0a7fgq1k8zgflgjkmkijghkmps6ha-python3.11-pytest-8.1.1/lib/python3.11/site-packages/_pytest/unraisableexception.py:80: PytestUnraisableExceptionWarning: Exception ignored from cffi callback <function TestNewFFI1.test_callback_decorator.<locals>.cb at 0x104d3ef20>, trying to convert the result back to C: None
              >
              >      Traceback (most recent call last):
              >          File "/private/tmp/nix-build-python3.11-cffi-1.16.0.drv-0/cffi-1.16.0/testing/cffi1/test_new_ffi_1.py", line 1341, in test_callback_decorator
              >              assert cb((1 << (sz*8-1)) - 1, -10) == 42
              >      OverflowError: int too big to convert
              >
              >          warnings.warn(pytest.PytestUnraisableExceptionWarning(msg))
              >
              > testing/cffi1/test_recompiler.py::test_macro_var_callback
              >      /nix/store/jnc0a7fgq1k8zgflgjkmkijghkmps6ha-python3.11-pytest-8.1.1/lib/python3.11/site-packages/_pytest/unraisableexception.py:80: PytestUnraisableExceptionWarning: Exception ignored from cffi callback <function test_macro_var_callback.<locals>.get_my_value at 0x105a15580>, trying to convert the result back to C: None
              >
              >      Traceback (most recent call last):
              >          File "/nix/store/jnc0a7fgq1k8zgflgjkmkijghkmps6ha-python3.11-pytest-8.1.1/lib/python3.11/site-packages/_pytest/python_api.py", line 960, in raises
              >              func(*args[1:], **kwargs)
              >      TypeError: initializer for ctype 'int *' must be a cdata pointer, not str
              >
              >          warnings.warn(pytest.PytestUnraisableExceptionWarning(msg))
              >
              > -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
              > =========================== short test summary info ============================
              > FAILED testing/cffi1/test_verify1.py::test_enum_usage - cffi.VerificationError: CompileError: command '/nix/store/h0a61pim6lj25qnnw...
              > FAILED testing/cffi1/test_verify1.py::test_named_pointer_as_argument - cffi.VerificationError: CompileError: command '/nix/store/h0a61pim6lj25qnnw...
              > = 2 failed, 1888 passed, 150 skipped, 4 xfailed, 11 warnings in 366.64s (0:06:06) =

Additional context
The Mac is an emulated system in KVM/QEMU, in case that is somehow relevant.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
marco@Marcos-iMac-Pro all % nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-darwin"`
 - host os: `Darwin 22.6.0, macOS 10.16`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.23.0`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

Add a :+1: reaction to issues you find important.

I forgot to ping the maintainers. I don't seem to be able to ping a team, so I hope it's OK I ping @mweinelt, you updated it last.

Oh, I just noticed: These are the two tests fixed by https://github.com/NixOS/nixpkgs/commit/0b499eb86239cae23e52ba7c8ad2c3d30e6ed5b8
So I guess somehow this patch isn't applied here even though it should be. I will investigate.

Clang 16 promoted these to an error:
Wnull-pointer-subtraction
Wimplicit-function-declaration
Wno-implicit-int
Wno-incompatible-function-pointer-types

Not sure which of these exactly causes the failure, I have absolutely no experience in C, but disabling all of those lets the test pass. Since I'm not really confident this is even correct, I will stop here and let somebody with more experience in this take over.

I couldn't really figure out why the tests are still failing, the patches are applied. I will leave this for somebody more experienced with C and Clang to investigate.

Okay I got it.
Instead of the patch in the commit above, pulling in this commit as a patch for all compilers fixes the issue:
https://github.com/python-cffi/cffi/commit/39bdab23615a83c1001ed822f974ae52020201ba
I don't really get why the patch that disables the warning doesn't work, but this commit just fixes why the warning is even raised.
This will be included in 1.17.0.

Seems to have been fixed via #322388


Update createServer.js

remove fivem

Because pterodactyl can't to make it and licensing is bad for ptero afaik

Because pterodactyl can't to make it and licensing is bad for ptero afaik

aren't they fine again

oh yes as i see, this should be closed @Sliden101 sussy


Set launch date

Pending auditor feedback.

➤ Chris Remus commented:
test from asana integration

https://medium.com/the-ethereum-name-service/announcing-the-ethereum-name-service-relaunch-date-4390af6dd9a2


BUG - incorrect error message for non-CAP generation into a CAP project folder that contains Fiori app(s)

Related Feature
#2427
Description
When non-CAP Fiori app is generated into a CAP project folder with pre-existing Fiori apps, incorrect error message is shown.
Steps to Reproduce

Clone or copy CAP Java project from https://github.com/SAP-samples/cloud-cap-samples-java/
Launch Fiori generator and choose a data source that is not Local CAP Project
On Project Attributes step, provide as Project folder path an app folder that is part of sample CAP Java project

Expected results
User is prevented from continuing with the following message: The selected project folder is part of an existing CAP project.  This application must therefore use the local CAP project as the data source
Actual results
User is prevented from continuing with the following message: The project folder path already contains an SAP Fiori application in the folder: c:\SAPDevelop\New\cloud-cap-samples-java-main\app. Please choose a different folder and try again.
Screenshots

Version/Components/Environment
Add any other context about the problem here
OS:

[x] Mac OS
[x] Windows
[ ] Other

Root Cause Analysis
Problem
{describe the problem}
Fix
{describe the fix}
Why was it missed
{Some explanation why this issue might have been missed during normal development/testing cycle}
How can we avoid this
{if we don’t want to see this type of issues anymore what we should do to prevent}

Hi, I have the same issue. Did you come across any solutions so far? Thanks!


Breaking changes from v5.0.3 to v6.0.0?

Getting these errors when compiling TS using spotify-api.js
src/spotify.ts:41:20 - error TS2554: Expected 2 arguments, but got 0.
const user = new Spotify.UserClient();
                      ~~~~~~~~~~~~~~~~~~

node_modules/spotify-api.js/dist/UserClient.d.ts:50:17
constructor(token: string | undefined, client: Client);
                                       ~~~~~~~~~~~~~~~~
An argument for 'token' was not provided.

src/spotify.ts:80:22 - error TS2554: Expected 2 arguments, but got 1.
const userPlayer = new Spotify.UserPlayer(token);
                                 ~~~~~~~~~~~~~~~~

node_modules/spotify-api.js/dist/UserPlayer.d.ts:11:28
constructor(data: any, client: Client);
                       ~~~~~~~~~~~~~
An argument for 'client' was not provided.

src/spotify.ts:86:16 - error TS2554: Expected 2 arguments, but got 1.
const user = new Spotify.UserClient(token);
                      ~~~~~~~~~~~~~~~~~~~~~~

node_modules/spotify-api.js/dist/UserClient.d.ts:50:44
constructor(token: string | undefined, client: Client);
                                          ~~~~~~~~~~
An argument for 'client' was not provided.

My version of spotify-api.js
Version 6.0.0
What i expected...
These errors are new since the update from v5.0.3 to v6.0.0. I'm not seeing any arguments that match "client: Client" in the docs here -> https://spotify-api-js-test.netlify.app/#/class/userplayer
But what happened is...
Getting an error stating that there are missing arguments for Spotify.UserClient & Spotify.UserPlayer. The docs do not address these arguments.

See first v6 is buggy as i said in the readme but tbh it works fine but you have made a mistake over there
You dont need initiate the UserClient class seperately you can do something like this:
const client = new Spotify.Client("TOKEN");
const userclient = client.user;
const userplayer = client.user.player;

This will work fine, if any errors report and docs is outdated. The docs ur viewing is of v5 and old one!
@abh80 is on leave, so he is not updating the docs. Docs is ready but, it will release it v7!

Thanks for the response. The readme states that v5 is buggy not v6!
I'll keep an eye open for updates.
Thanks for all of your work.

Planning to publish v7 tomorrow after testing

Ok @philmorley V7 is now released on npm so make sure to check it out

@philmorley v7 has published update it!

Open this issue again if you have any issue regarding this package and if the issue still persists.


Where do we write backend stuff?

Hi,
Where can I write backend node.js stuff like
(def path (nodejs/require "path"))
(def Electron (nodejs/require "electron"))
(def BrowserWindow (.-BrowserWindow Electron))
(def crash-reporter (.-crashReporter Electron))
(def Os (nodejs/require "os"))
(def *win* (atom nil))
(def app (.-app Electron))

As far as I can see descjop leiningen template creates two separate directories for backend and frontend code like my_project/src and my_project/src_front but I couldn't find that distinction in this project.
Closest thing I can find is app/app.js file but that means I have to write plain javascpript to handle things like saving state etc :(

electron_src > electron > core.cljs

I should have answered this earlier but here it is: It turns out there is no need to separate backend stuff from the rest of the code. Here is how I did it:

Created a namespace for common file operations:

(ns my-project.nodejs)

;(defonce path (js/require "path"))
(defonce fs (js/require "fs"))

(defn slurp [file]
  "Read file and return contents as string"
  (.toString  (.readFileSync fs file)))

(defn file-exists? [file]
  (.existsSync fs file))

(defn spit [file contents]
  "Write contents to file"
  (.writeFileSync fs file contents))

Then just use it:

(ns my-project.entry-store
  (:require [cljs.reader :as reader]
            [my-project.nodejs :as nodejs]
            [my-project.entry :as entry]))

(defn- load-from-file []
  (if (nodejs/file-exists? filePath)
    (into (sorted-map) (string-to-entries (nodejs/slurp filePath)))
    (println (str "File not found" filePath))))

(defn save! [entry-store]
  (nodejs/spit filePath (pr-str entry-store))
  (println (str "Entries saved to: " filePath)))


python3 deploy.py installWeBASE可视化部署webase失败

root@shangwu:~/tools/webase-tools/webase-deploy# python3 deploy.py installWeBASE
          _    _     ______  ___  _____ _____
         | |  | |    | ___ \/ _ \/  ___|  ___|
         | |  | | ___| |_/ / /_\ \ `--.| |__
         | |/\| |/ _ | ___ |  _  |`--. |  __|
         \  /\  |  __| |_/ | | | /\__/ | |___
          \/  \/ \___\____/\_| |_\____/\____/

============================================================
==============      checking envrionment      ==============
check git...
check finished sucessfully.
check openssl...
check finished sucessfully.
check curl...
check finished sucessfully.
check wget...
check finished sucessfully.
check dos2unix...
check finished sucessfully.
check Docker...
Try to start Docker...
check finished sucessfully.
check nginx...
check finished sucessfully.
check java...
check finished sucessfully.
check WeBASE-Web port...
check finished sucessfully.
check WeBASE-Node-Manager port...
check finished sucessfully.
check WeBASE-Sign IP for visual deploy...
check finished sucessfully.
check WeBASE-Sign port...
check finished sucessfully.
check database connection...
check finished sucessfully.
check database connection...
check finished sucessfully.
check mgr database user/password...
check finished sucessfully.
check sign database user/password...
check finished sucessfully.
check mgr mysql version...
node-mgr's mysql version is [5.6.16-1~exp1]
check finished sucessfully.
check sign mysql version...
sign's mysql version is [5.6.16-1~exp1]
check finished sucessfully.
==============      envrionment available     ==============
==============        starting  deploy        ==============
============ Download docker image from CDN... =============
wget https://osp-1257653870.cos.ap-guangzhou.myqcloud.com/WeBASE/releases/download/v1.5.5/docker-fisco-webase.tar
--2024-11-10 19:30:45--  https://osp-1257653870.cos.ap-guangzhou.myqcloud.com/WeBASE/releases/download/v1.5.5/docker-fis                 co-webase.tar
Resolving osp-1257653870.cos.ap-guangzhou.myqcloud.com (osp-1257653870.cos.ap-guangzhou.myqcloud.com)... <IP_ADDRESS>,                  <IP_ADDRESS>
Connecting to osp-1257653870.cos.ap-guangzhou.myqcloud.com (osp-1257653870.cos.ap-guangzhou.myqcloud.com)|<IP_ADDRESS>|                 :443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2024-11-10 19:30:45 ERROR 403: Forbidden.
Traceback (most recent call last):
File "/root/tools/webase-tools/webase-deploy/deploy.py", line 127, in
do()
File "/root/tools/webase-tools/webase-deploy/deploy.py", line 34, in do
commBuild.visual_do()
File "/root/tools/webase-tools/webase-deploy/comm/build.py", line 43, in visual_do
installDockerImage()
File "/root/tools/webase-tools/webase-deploy/comm/build.py", line 714, in installDockerImage
pullDockerImage(gitComm,"docker-fisco-webase.tar","fiscoorg/fisco-webase")
File "/root/tools/webase-tools/webase-deploy/comm/utils.py", line 239, in pullDockerImage
doCmd("docker load -i {}".format(fileName))
File "/root/tools/webase-tools/webase-deploy/comm/utils.py", line 111, in doCmd
raise Exception("execute cmd  error ,cmd : {}, status is {} ,output is {}".format(cmd,status, output))
Exception: execute cmd  error ,cmd : docker load -i docker-fisco-webase.tar, status is 1 ,output is open docker-fisco-we                 base.tar: no such file or directory

@CodingCattwo


Android: Copy resource files in the correct folder

Bug Report
I want to copy resources to the res directory of the android app.
Problem
I followed the documentation for the resource-file tag of the config.xml, where it shows an example to copy a resource file to res/values/ for Android:
<resource-file src="FooPluginStrings.xml" target="res/values/FooPluginStrings.xml" />

When I use this code, the resource file gets copied to platforms/android/res/values, but the correct folder would be platforms/android/app/src/main/res/values.
When I do the same for iOS with
<platform name="ios">
    <resource-file src="FooPluginStrings.xml" target="FooPluginStrings.xml" />
</platform>

It gets correctly copied to platforms/iOS/[AppName]/Resources (using cordova-ios 7.1.1).
Should there be not a similar behavior for Android? Must the documentation be updated to the correct path, or is this an issue in the Cordova-cli?
What is expected to happen?
The resource file should be put in the correct folder like the documentation says.
What does actually happen?
The resource file is copied in the wrong place.
Information
Command or Code
Environment, Platform, Device
Version information

macOS 15.2
MacBook Pro 2019 13"
cordova-cli 12.0.0<EMAIL_ADDRESS>
Checklist

[ ] I searched for existing GitHub issues
[ ] I updated all Cordova tooling to most recent version
[ ] I included all the necessary information above

There's some history here that's worth knowing. The Android platform moved from being an Eclipse (ant) project to being an Android Studio (gradle) project, and the project structure changed. Previously, res was a top-level folder, but now it's nested under app/src/main.
To avoid breaking all the existing plugins, there's a remapping system in cordova-android that will take "old" paths and rewrite them to the newer paths. That remapping appears to be used unconditionally resource-file in plugins, but not for resource-file declarations in config.xml.
The workaround is to specify the full path that you want for the file, i.e. app/src/main/res/values/FooPluginStrings.xml
It's not feasible to automatically prefix all resource files with app/src/main (which is what plugins are doing) because that prevents app authors from doing something like copying a google-service.json file into the app folder.
Maybe we could add a check for target paths that start with res/ and remap those?

I understand. On my opinion checking for res/ would be good, than it would be also backward compatible. The app developer should not care about the real res path, because the path can also change in future changes.


Circle chart - Shadow gradient

Hello,
thanks for you library!
Do you think it's possible to create circle chart with shadow gradient (and with shadow? 😄)  - not only shadow color? Something like this?
Also - is it possible to change countingLabel format? I see that this is hardcoded in "strokeChart".
Thanks!

I think you can use a imageView under The circleChart as the shadow , after all the circleChart.backgroundColor is clearColor;
The countingLabel format, you can use UICountingLabelAttributedFormatBlock like
self.circleChart.countingLabel.attributedFormatBlock = ^(float value){
    NSString *text = [NSString stringWithFormat:@"%d%%",(int)value];
    NSMutableAttributedString *str = [[NSMutableAttributedString alloc] initWithString:text];
    [str addAttribute:NSForegroundColorAttributeName value:[UIColor blueColor] range:NSMakeRange(0, text.length)];
    return str;
};


Movie File Finishing Error

I am getting this error when I try to record a very short video:
[SwiftyCam]: Movie file finishing error: Error Domain=AVFoundationErrorDomain Code=-11805 "Cannot Record" UserInfo={NSUnderlyingError=0x280490de0 {Error Domain=NSOSStatusErrorDomain Code=-16418 "(null)"}, NSLocalizedRecoverySuggestion=Try recording again., AVErrorRecordingFailureDomainKey=1, NSLocalizedDescription=Cannot Record}

Hello,
Add below 1 line code on Your viewDidLoad Method After Set camera
Code:-
configureVideoPreset()