Ensemble Script

Regarding the ensemble script, an explanation of the types could be added, and also, when I use the “fft” types, the following error occurs
Traceback (most recent call last):
  File "G:\ensemble\ensemble.py", line 162, in <module>
    ensemble_files(None)
  File "G:\ensemble\ensemble.py", line 156, in ensemble_files
    res = average_waveforms(data, weights, args.type)
  File "G:\ensemble\ensemble.py", line 89, in average_waveforms
    spec = stft(pred_track[i], 2048, 1024)
  File "G:\ensemble\ensemble.py", line 14, in stft
    spec_left = librosa.stft(wave_left, nfft, hop_length=hl)
TypeError: stft() takes 1 positional argument but 2 positional arguments (and 1 keyword-only argument) were given

With the following command
python ensemble.py --files "1_01. Wings of Reality_(Vocals).flac" "1_01. Wings of Reality_MDX23C-8KFFT-InstVoc_HQ_(Vocals).flac" --type avg_fft --weights 2 1

Yes, this is the installed version 0.10.2.post1

I tested it on librosa version 0.9.2 and it didn't give me the problem, but this warning appeared:
ensemble.py:15: FutureWarning: Pass n_fft=2048 as keyword args. From version 0.10 passing these as positional arguments will result in an error
Also, I had to install a version of numpy lower than 1.24
But then an error appeared that I couldn't fix:
Traceback (most recent call last):
  File "G:\ensemble\ensemble.py", line 162, in <module>
    ensemble_files(None)
  File "G:\ensemble\ensemble.py", line 158, in ensemble_files
    sf.write(args.output, res.T, sr, 'FLOAT')
  File "C:\Users\User\AppData\Local\Programs\Python\Python310\lib\site-packages\soundfile.py", line 343, in write
    with SoundFile(file, 'w', samplerate, channels,
  File "C:\Users\User\AppData\Local\Programs\Python\Python310\lib\site-packages\soundfile.py", line 658, in __init__
    self._file = self._open(file, mode_int, closefd)
  File "C:\Users\User\AppData\Local\Programs\Python\Python310\lib\site-packages\soundfile.py", line 1216, in _open
    raise LibsndfileError(err, prefix="Error opening {0!r}: ".format(self.name))
soundfile.LibsndfileError: Error opening 'res.wav': Format not recognised.

Can you check if res.wav is correct wav file? Can you post it here?

res.zip
Here, this is the file generated. Apparently it's just a corrupt file

How did you generate res.wav?

Can you post results of this line:
print('Result shape: {}'.format(res.shape))

@ZFTurbo Here, the shape result
Result shape: (15631980, 2)
about how I generated the file, I just ran the command, after installing the versions of librosa and numpy, it started generating the file, only this way, corrupted

Can you try change line:
sf.write(args.output, res.T, sr, 'FLOAT')

to
sf.write(args.output, res, sr, 'FLOAT')

I will check myself later today

It worked! In fft, because in wave, it had the problem that fft had now. It seems that changing this results in solving the problem of one and making the other stop working

Oh, and also, what does fft do? I think wave is an ensemble of waveforms, but I have no idea what fft is, and the same goes for median, which UVR doesn't have. It would be good to add a description of the types in the readme

I've tested the latest commit, and the script is working in the latest version of librosa, both wave and fft! Now all that's needed is an explanation of the types to close this issue!

I added documentation:
https://github.com/ZFTurbo/Music-Source-Separation-Training/blob/main/docs/ensemble.md

Thanks, that cleared up my doubts about the types! I'll close the issue


Add filtering to the Data tab

Adds filtering to the Data tab of the Client.  As requests are selected, the Client will track what database-related messages have been observed across requests and show those databases in a "filter bar" above the operations table, along with the number of operations pertaining to each for that selected request.  The user can then show/hide operations associated with each database.

Associated with #106.

Ok finally done. I've made a few comments, nothing too major just some observations.


POC: prometheus integration for server with k8s

Status:

added counter on k8s events.
added a test for pod, a test for node.

@davidbtucker @bmoyles0117 here is the current implementation on k8s event counter

this one need to rebase from master because there are couple changes already merged into tests.


Integrate a Storybook for our components.

We have a lot of components that are not standardized for our pages and we have requested to refactor them, to make them smaller and more useful.
I'm proposing to add Storybook and integrate it into our app.
Before starting to refactor dropdowns or text components that we copy-pasting, it's better to summarize where and which functional components, with different styles we have in our system. After this task, we can start to work on refactoring and scaling our components.

hey @brusherru , what do u think about this step?


AssertionError: HappyPlugin[js]; you have not specified any loaders and there is no matching loader entry with this id either.

HappyPack does not seem to work when trying to "infer" the loaders from preLoaders. Is this true? Can it be made to work? If not, I can easily specify it, just wondering.
  new HappyPack({ id: 'js' }),

      preLoaders: [

       /*
      * Source map loader support for *.js files
      * Extracts SourceMaps for source files that as added as sourceMappingURL comment.
      *
      * See: https://github.com/webpack/source-map-loader
      */
     {
       test: /\.js$/,
       loader: 'source-map-loader',
       exclude: [
         // these packages have problems with their sourcemaps
         helpers.root('node_modules/rxjs'),
         helpers.root('node_modules/@angular2-material'),
         helpers.root('node_modules/@angular')
       ],
       happy: { id: 'js' } // HappyPack middleware

     }
   ],

Happy[js]: Version: 2.1.1. Using cache? yes. Threads: 3

D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\happypack\lib\HappyPlugin.js:165
      assert(loaders && loaders.length > 0,
      ^
AssertionError: HappyPlugin[js]; you have not specified any loaders and there is no matching loader entry with this id either.
    at normalizeLoaders (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\happypack\lib\HappyPlugin.js:165:7)
    at D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\happypack\node_modules\async\lib\async.js:713:13
    at Immediate.iterate [as _onImmediate] (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\happypack\node_modules\async\lib\async.js:262:13)
    at processImmediate [as _immediateCallback] (timers.js:383:17)

Oh no the infer option only works on loaders not pre / post. Hmm. Personally I'm not a fan of this option altogether because it irreversibly mutates the options which is bad in some contexts (like running behind grunt-watch or similar) so if you could get rid of it (yes I know, more typing!) you might be better off.
If you feel strongly about it, we can add support for inferring from preLoaders and postLoaders but I would rather not.

Thanks for the reply. Actually it's not a big deal, I was just curious. It was because I am using source-map-loader and they put their loader into in preLoaders

I just noticed that it had trouble interring from the [awesome-typescript-loader](https://github.com/s-panferov/awesome-typescript-loader) but when I specify maunally in the webpack plugin, it works fine. Seems to work fine for the other loaders. Just letting you know.
==================================================
            Building for DEVELOPMENT
==================================================

Happy[js]: Version: 2.1.1. Using cache? yes. Threads: 3
Happy[js]: No cache was found, starting fresh.
Happy[js]: All set; signalling webpack to proceed.
Happy[ts]: Version: 2.1.1. Using cache? yes. Threads: 3
Happy[ts]: Loaded 1 entries from cache. (0 were stale)
Happy[ts]: All set; signalling webpack to proceed.
Happy[json]: Version: 2.1.1. Using cache? yes. Threads: 3
Happy[json]: Loaded 0 entries from cache. (0 were stale)
Happy[json]: All set; signalling webpack to proceed.
Happy[css]: Version: 2.1.1. Using cache? yes. Threads: 3
Happy[css]: Loaded 0 entries from cache. (0 were stale)
Happy[css]: All set; signalling webpack to proceed.
Happy[html]: Version: 2.1.1. Using cache? yes. Threads: 3
Happy[html]: Loaded 0 entries from cache. (0 were stale)
Happy[html]: All set; signalling webpack to proceed.
Happy[jpg]: Version: 2.1.1. Using cache? yes. Threads: 3
Happy[jpg]: Loaded 0 entries from cache. (0 were stale)
Happy[jpg]: All set; signalling webpack to proceed.
Happy[png]: Version: 2.1.1. Using cache? yes. Threads: 3
Happy[png]: Loaded 0 entries from cache. (0 were stale)
Happy[png]: All set; signalling webpack to proceed.
Happy[scss]: Version: 2.1.1. Using cache? yes. Threads: 3
Happy[scss]: Loaded 0 entries from cache. (0 were stale)
Happy[scss]: All set; signalling webpack to proceed.
813ms build modules
2ms seal
3ms optimize
3ms hashing
2ms create chunk assets
3ms additional chunk assets
3ms optimize chunk assets
103ms optimize assets
37ms emit
Hash: 6c2cd446ebd48e9e5802
Version: webpack 1.13.1
Time: 4487ms
                                 Asset       Size  Chunks             Chunk Names
    assets/icon/apple-icon-180x180.png      11 kB          [emitted]
                        _Layout.cshtml  994 bytes          [emitted]
                     assets/humans.txt  268 bytes          [emitted]
                  assets/manifest.json  810 bytes          [emitted]
                     assets/robots.txt   34 bytes          [emitted]
              assets/service-worker.js   45 bytes          [emitted]
                   assets/css/.gitkeep   15 bytes          [emitted]
       assets/mock-data/mock-data.json   48 bytes          [emitted]
  assets/icon/android-icon-144x144.png    8.43 kB          [emitted]
  assets/icon/android-icon-192x192.png    9.71 kB          [emitted]
    assets/icon/android-icon-36x36.png     2.3 kB          [emitted]
    assets/icon/android-icon-48x48.png    2.92 kB          [emitted]
    assets/icon/android-icon-72x72.png    4.23 kB          [emitted]
    assets/icon/android-icon-96x96.png     5.6 kB          [emitted]
    assets/icon/apple-icon-114x114.png    6.55 kB          [emitted]
    assets/icon/apple-icon-120x120.png    6.92 kB          [emitted]
    assets/icon/apple-icon-144x144.png    8.43 kB          [emitted]
    assets/icon/apple-icon-152x152.png    8.99 kB          [emitted]
                      assets/data.json   33 bytes          [emitted]
      assets/icon/apple-icon-57x57.png     3.4 kB          [emitted]
      assets/icon/apple-icon-60x60.png    3.56 kB          [emitted]
      assets/icon/apple-icon-72x72.png    4.23 kB          [emitted]
      assets/icon/apple-icon-76x76.png    4.46 kB          [emitted]
assets/icon/apple-icon-precomposed.png    10.3 kB          [emitted]
            assets/icon/apple-icon.png    10.3 kB          [emitted]
         assets/icon/browserconfig.xml  282 bytes          [emitted]
         assets/icon/favicon-16x16.png    1.52 kB          [emitted]
         assets/icon/favicon-32x32.png    2.07 kB          [emitted]
         assets/icon/favicon-96x96.png     5.6 kB          [emitted]
               assets/icon/favicon.ico    1.15 kB          [emitted]
       assets/icon/ms-icon-144x144.png    8.43 kB          [emitted]
       assets/icon/ms-icon-150x150.png    8.88 kB          [emitted]
       assets/icon/ms-icon-310x310.png    24.1 kB          [emitted]
         assets/icon/ms-icon-70x70.png    4.12 kB          [emitted]
           assets/img/angular-logo.png      19 kB          [emitted]
    assets/img/angularclass-avatar.png    32.8 kB          [emitted]
      assets/img/angularclass-logo.png    36.7 kB          [emitted]
    + 1 hidden modules

ERROR in ./src/webpack.entry.bundle.ts
Module parse failed: D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\happypack\lib\HappyLoader.js?id=ts!D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\src\webpack.entry.bundle.ts Unexpected token (1:8)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (1:8)
    at Parser.pp.raise (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:920:13)
    at Parser.pp.unexpected (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:1483:8)
    at Parser.pp.expect (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:1477:26)
    at Parser.pp.parseExprList (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:647:12)
    at Parser.pp.parseExprAtom (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:309:28)
    at Parser.pp.parseExprSubscripts (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:225:19)
    at Parser.pp.parseMaybeUnary (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:204:17)
    at Parser.pp.parseExprOps (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:151:19)
    at Parser.pp.parseMaybeConditional (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:133:19)
    at Parser.pp.parseMaybeAssign (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:110:19)
    at Parser.pp.parseExpression (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:86:19)
    at Parser.pp.parseStatement (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:1753:23)
    at Parser.pp.parseTopLevel (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:1648:21)
    at Parser.parse (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:1616:17)
    at Object.parse (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\acorn\dist\acorn.js:882:44)
    at Parser.parse (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\lib\Parser.js:902:15)
    at DependenciesBlock.<anonymous> (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\lib\NormalModule.js:104:16)
    at DependenciesBlock.onModuleBuild (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\webpack-core\lib\NormalModuleMixin.js:310:10)
    at nextLoader (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\webpack-core\lib\NormalModuleMixin.js:275:25)
    at D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\webpack-core\lib\NormalModuleMixin.js:292:15
    at context.callback (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\webpack-core\lib\NormalModuleMixin.js:148:14)
    at D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\happypack\lib\HappyLoader.js:44:5
    at HappyPlugin.compileInBackground (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\happypack\lib\HappyPlugin.js:266:12)
    at HappyPlugin.compile (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\happypack\lib\HappyPlugin.js:255:17)
    at Object.HappyLoader (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\happypack\lib\HappyLoader.js:23:15)
    at WEBPACK_CORE_LOADER_EXECUTION (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\webpack-core\lib\NormalModuleMixin.js:155:71)
    at runSyncOrAsync (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\webpack-core\lib\NormalModuleMixin.js:155:93)
    at nextLoader (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\webpack-core\lib\NormalModuleMixin.js:290:3)
    at D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\webpack-core\lib\NormalModuleMixin.js:259:5
    at Storage.finished (D:\Source\POC\ASP.Net.Core1.Angular2.Webpack.Starter\src\starterproject\node_modules\webpack\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:38:16)

awesome-typescript-loader doesn't really work with HappyPack yet I'm surprised you got this far... see #33 .
By the way, if you have that many happy plugins, you should really use a shared thread pool of, say, 5 threads instead of the 24 you're using! That's an overkill and it will likely be slower. See https://github.com/amireh/happypack#shared-thread-pools for more information

Okay gonna close this one as there's no real harm done, the inferLoaders is a convenience and if it doesn't work we can just resort to the manual plugin approach.
Thanks for reporting! :)

@amireh Thanks for the tip about shared threads, I didn't realize it was 3 PER happypack instance, I thought it was sharing 3 already! Now it makes sense. I'll follow the thread #33 for updates on typescript integration.


fix(create): add metadata rollback for errors after metadata write in create operation

Description
This PR will add functionality that will roll back the metadata in the event an error occurs during archiving or the user cancels during archiving. It also moves testdata for each package under the package root.
Fixes #200
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

[X] Unit test for Create with Cancel

Instructions to manually test:

Use stateless mode
Run a an oc-mirror mirror to disk operation
Cancel the operation during archiving
Ensure that when you run again there are not sequence errors

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Rollback works, but archiving operations continue after interrupt. This solution needs to cleanup the interrupted PR and exit when an interrupt is received.

/retest


infinite stack recursion in upgradable_dependents

[x] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[ ] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new/choose. If it's a brew cask problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

I only reproduced with libpng, but this seems to me like an issue with the core framework, or something that should be detected in the core framework.
What you were trying to do (and why)
upgrade libpng ... from source ... I know you guys seem to not like that anymore, but I started with gentoo about 15 years ago ...
What happened (include command output)
libpng upgrade worked, then homebrew hit an apparently infinite stack recursion while checking dependents
==> make install
...
/usr/local/Cellar/libpng/1.6.36: 27 files, 1.2MB, built in 1 minute 33 seconds
Error: stack level too deep
/usr/local/Homebrew/Library/Homebrew/options.rb:26:in `hash'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:313:in `add'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:388:in `block in merge'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:96:in `each'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:96:in `each_entry'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:96:in `do_with_enum'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:388:in `merge'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:90:in `initialize'
/usr/local/Homebrew/Library/Homebrew/options.rb:64:in `new'
/usr/local/Homebrew/Library/Homebrew/options.rb:64:in `initialize'
/usr/local/Homebrew/Library/Homebrew/options.rb:60:in `new'
/usr/local/Homebrew/Library/Homebrew/options.rb:60:in `create'
/usr/local/Homebrew/Library/Homebrew/tab.rb:256:in `used_options'
/usr/local/Homebrew/Library/Homebrew/formulary.rb:355:in `from_keg'
/usr/local/Homebrew/Library/Homebrew/keg.rb:416:in `to_formula'
/usr/local/Homebrew/Library/Homebrew/cmd/upgrade.rb:200:in `map'
/usr/local/Homebrew/Library/Homebrew/cmd/upgrade.rb:200:in `block in upgradable_dependents'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:306:in `each_key'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:306:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/upgrade.rb:190:in `upgradable_dependents'
/usr/local/Homebrew/Library/Homebrew/cmd/upgrade.rb:217:in `block in upgradable_dependents'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:306:in `each_key'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:306:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/upgrade.rb:190:in `upgradable_dependents'
/usr/local/Homebrew/Library/Homebrew/cmd/upgrade.rb:217:in `block in upgradable_dependents'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:306:in `each_key'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/set.rb:306:in `each'
/usr/local/Homebrew/Library/Homebrew/cmd/upgrade.rb:190:in `upgradable_dependents'
... repeats ...

What you expected to happen
Maybe nothing after the successful install, I expect libpng-1.6.36 to be fully ABI compatible with libpng-1.6.35, or maybe homebrew automatically re-builds all the formula which depend on libpng:
$ brew uses --installed --include-optional libpng | cat
cairo
freetype
gd
graphviz
gst-plugins-good
qrencode
webp

$ brew uses --installed libpng | cat
cairo
fontconfig
freetype
gd
gobject-introspection
graphviz
gst-libav
gst-plugins-base
gst-plugins-good
gst-plugins-ugly
gst-rtsp-server
harfbuzz
libass
libbluray
libsoup
mpv
pango
qrencode
vala
webp

interesting how --include-optional just avoids including transitive dependents in this case
Step-by-step reproduction instructions (by running brew commands)
I did this a couple times to check it wasn't just a fluke. I still have libpng-1.6.35 installed, so first:
$ brew uninstall --ignore-dependencies libpng
Uninstalling /usr/local/Cellar/libpng/1.6.36... (28 files, 1.2MB)
libpng 1.6.35 is still installed.
Remove all versions with `brew uninstall --force libpng`.

Then:
$ brew upgrade libpng
==> Upgrading 1 outdated package:
libpng 1.6.36
==> Upgrading libpng
...

$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: You have HOMEBREW_BUILD_FROM_SOURCE set. This environment variable is
intended for use by Homebrew developers. If you are encountering errors,
please try unsetting this. Please do not file issues if you encounter
errors when using this environment variable.

Warning: Some installed formulae are missing dependencies.
You should `brew install` the missing dependencies:
  brew install p11-kit

Run `brew missing` for more details.

$ brew config
HOMEBREW_VERSION: 1.8.6-14-ga2b4d4a
ORIGIN: https://github.com/Homebrew/brew.git
HEAD: a2b4d4aac294ec0872cd84d44f65bd5bd507e166
Last commit: 3 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: a4af237fa6836920fdec9d9c8a3c14260123ac11
Core tap last commit: 70 minutes ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_BUILD_FROM_SOURCE: 1
HOMEBREW_DEV_CMD_RUN: 1
HOMEBREW_NO_ANALYTICS: 1
HOMEBREW_NO_AUTO_UPDATE: 1
HOMEBREW_NO_EMOJI: 1
CPU: quad-core 64-bit haswell
Homebrew Ruby: 2.3.7 => /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
Clang: 10.0 build 1000
Git: 2.20.1 => /usr/local/bin/git
Curl: 7.54.0 => /usr/bin/curl
Java: 1.8.0_192
macOS: 10.13.6-x86_64
CLT: <IP_ADDRESS>.1.1539992718
Xcode: N/A
XQuartz: 2.7.11 => /opt/X11

I was in the process of upgrading stuff:
$ brew outdated
awscli (1.16.60) < 1.16.70
bison (3.2.2) < 3.2.3
cmake (3.13.1) < 3.13.2
fdk-aac (0.1.6) < 2.0.0
ffmpeg (4.1) < 4.1_1
glib (2.58.1) < 2.58.2
gnu-sed (4.5) < 4.6
gobject-introspection (1.58.1) < 1.58.2
graphite2 (1.3.12) < 1.3.13
gst-plugins-ugly (1.14.4_1) < 1.14.4_2
harfbuzz (2.1.3) < 2.2.0
icu4c (62.1) < 63.1
media-info (18.08.1) < 18.12
meson (0.48.2) < 0.49.0
node@8 (8.12.0) < 8.14.1
opam (2.0.1) < 2.0.2
pixman (0.34.0_1) < 0.36.0
x264 (r2854) < r2917

I hacked in a print to get some clue about the formulae causing this loop:
--- a/Library/Homebrew/cmd/upgrade.rb
+++ b/Library/Homebrew/cmd/upgrade.rb
@@ -186,12 +186,13 @@ module Homebrew
   def upgradable_dependents(kegs, formulae)
     formulae_to_upgrade = Set.new
     formulae_pinned = Set.new

     formulae.each do |formula|
       descendants = Set.new
+      puts "considering formula: #{formula.full_name}"

       dependents = kegs.select do |keg|
         keg.runtime_dependencies

the output is confusing because this is a recursion inside a loop, but it eventually did come to a consistent repeating pattern:
...
considering formula: gst-rtsp-server
considering formula: gst-rtsp-server
considering formula: gst-plugins-bad
considering formula: gst-plugins-base
considering formula: gst-libav
considering formula: gst-plugins-bad
considering formula: gst-plugins-good
considering formula: gst-rtsp-server
considering formula: gst-plugins-good
considering formula: gst-rtsp-server
considering formula: webp
considering formula: libtiff
considering formula: little-cms2
considering formula: emacs
considering formula: mpv
considering formula: libsoup
considering formula: gst-plugins-good
considering formula: ghostscript
considering formula: webp
considering formula: libtiff
considering formula: little-cms2
considering formula: emacs
considering formula: mpv
considering formula: libsoup
considering formula: gst-plugins-good
considering formula: ghostscript
considering formula: webp
considering formula: libtiff
considering formula: little-cms2
considering formula: emacs
considering formula: mpv
considering formula: libsoup
considering formula: gst-plugins-good
considering formula: ghostscript
considering formula: webp
considering formula: libtiff
considering formula: little-cms2
considering formula: emacs
considering formula: mpv
... repeats ...

I think an interesting question is: how did libtiff get into that output ...
$ brew info libtiff
libtiff: stable 4.0.10 (bottled)
TIFF library and utilities
http://libtiff.maptools.org/
/usr/local/Cellar/libtiff/4.0.10 (246 files, 3.5MB) *
  Built from source on 2018-11-28 at 21:06:13
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/libtiff.rb
==> Dependencies
Required: jpeg (installed)
Optional: xz (installed)

eh well it's just HOMEBREW_BUILD_FROM_SOURCE, the "p11-kit" one is erroneous:
$ brew info gnutls
gnutls: stable 3.5.19 (bottled)
GNU Transport Layer Security (TLS) Library
https://gnutls.org/
/usr/local/Cellar/gnutls/3.5.19 (1,104 files, 7.3MB) *
  Built from source on 2018-07-19 at 00:39:41 with: --without-p11-kit
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/gnutls.rb
==> Dependencies
Build: pkg-config (installed)
Required: gmp (installed), libtasn1 (installed), libunistring (installed), nettle (installed)
Recommended: p11-kit (uninstalled)
Optional: guile (uninstalled), unbound (uninstalled)
==> Options
--with-guile
	Build with guile support
--with-unbound
	Build with unbound support
--without-p11-kit
	Build without p11-kit support

I have the same issue with a simple brew upgrade. The upgrade command declared upgrading ffmpeg 4.1 -> 4.1_1, rust 1.31.0 -> 1.31.1, gnu-sed 4.5 -> 4.7, libssh 0.8.4 -> 0.8.5, gnutls 3.5.19 -> 3.6.5.
I have the following installed:
adns			ffmpeg			graphite2		libgcrypt		libvo-aacenc		opencore-amr		readline		theora
asciidoc<EMAIL_ADDRESS>gti			libgpg-error		libvorbis		openh264		rlwrap			tree
autoconf		flac			gtk-doc			libgsm			libvpx			openjpeg		rsync			two-lame
autoconf-archive	fontconfig		harfbuzz		libidn			libxml2			openssl			rtmpdump		unrar
automake		freetype		htop			libidn2			libyaml			openvpn			rubberband		util-linux
bat			frei0r			httpie			libksba			little-cms2		opus			ruby			vapor
boost			fribidi			hugo			libmodplug		lz4			p11-kit			rust			watch
cabextract		game-music-emu		icu4c			libogg			lzo			p7zip			sdl			wavpack
cairo			gdbm			intltool		libpng			makedepend		pango			sdl2			webp
carthage		gdk-pixbuf		itstool			libressl		meson-internal		pass			sl			wget
chromaprint		gettext			jpeg			librsvg			mpg123			pcre			snappy			wine
cimg			git-lfs			jq			libsamplerate		nasm			phash			source-highlight	winetricks
cloc			glib			lame			libsndfile		ncdu			pigz			speedtest-cli		x264
cmake			gmp			leptonica		libsoxr			nettle			pinentry		speex			x265
coreutils		gnu-getopt		lftp			libssh			ninja			pixman			sphinx-doc		xmlto
ctls			gnu-sed			libass			libssh2			nmap			pkg-config		sqlite			xvid
cython			gnupg			libassuan		libtasn1		node			postgresql		swiftlint		xz
dep			gnutls			libbs2b			libtiff			npth			pstree			swig			yasm
docbook			go			libcaca			libtool			ocaml			pv			tcl-tk			youtube-dl
docbook-xsl		gobject-introspection	libcroco		libunistring		ocaml-findlib		python			tesseract		zeromq
doxygen			gpac			libdvdcss		libusb			ocamlbuild		python@2		texi2html		zimg
fdk-aac			gpgme			libffi			libvidstab		oniguruma		qrencode		the_silver_searcher

I also have the HOMEBREW_BUILD_FROM_SOURCE var set to 1.

I also have the HOMEBREW_BUILD_FROM_SOURCE var set to 1.

As the docs note: that’s an unsupported configuration.

@Frizlab If someone can provide a simple reproduction without HOMEBREW_BUILD_FROM_SOURCE set we've got something we can look at fixing.

Additionally we need a fuller backtrace in a Gist, thanks.

Will try and do that when/if I find the time.


Plugin fails to load if "Settings" is open

I noticed that when you open your editor and the "settings" tab/page/whatever is open, the plugin won't load because it tries to get the "path" from the pane item, and "settings" doesn't have a path.
The exception thrown is:
Uncaught (in promise) TypeError: item.getPath is not a function
    at ~/.atom/packages/open-files/lib/open-files-pane-view.js:64:48
    at Pane.module.exports.Pane.observeItems (/opt/atom/resources/app.asar/src/pane.js:211:9)
    at OpenFilesPaneView.setPane (~/.atom/packages/open-files/lib/open-files-pane-view.js:50:25)
    at OpenFilesView.addTabGroup (~/.atom/packages/open-files/lib/open-files-view.js:28:9)
    at ~/.atom/packages/open-files/lib/open-files-view.js:17:9
    at PaneContainer.module.exports.PaneContainer.observePanes (/opt/atom/resources/app.asar/src/pane-container.js:92:9)
    at Workspace.module.exports.Workspace.observePanes (/opt/atom/resources/app.asar/src/workspace.js:374:33)
    at new OpenFilesView (~/.atom/packages/open-files/lib/open-files-view.js:16:35)
    at ~/.atom/packages/open-files/lib/open-files.js:19:25

BTW the current workaround is to close the "Settings" tab (or any other tab that could have no path) and restart/refresh the editor (Normally you can refresh with Ctrl+Alt+R).

Thanks for the report. I added a try-catch clause around item.getPath() so that the package now works and lists the 'settings' tab.


chore: adjustments for development in corporate environments

This PR contains some improvements to local developer environment for contributors sitting in corporate network environments.

Blocked by https://github.com/k3d-io/k3d/pull/1199

Can use the new envvar supported by k3d after https://github.com/k3d-io/k3d/pull/1199.


VISUALS: InVision Visuals Source Files Clean up

Verification Conditions:

Go through each source Photoshop file
Clean out any extraneous layers, unnecessary elements
Post files to Google Drive in appropriate folders

Completed cleanup of Photoshop source files and posted here:

Add a Work Item - Quick & Full Desktop
Add a Work Item - Mobile
Assign User
Epics
Icons-Draft
Iterations

Added Bonus:
InVision Basics Doc Screens


behavior/arrangement of mcliccfg.nlbits/scliccfg.nlbits/ucliccfg.nlbits

separating additional question raised in issue #304 into a new issue:
Additionally, can you please clarify the behavior of the xcliccfg.nlbits fields; specifically:
Are xcliccfg.nlbits fields independent of each other, or are they aliases of the same thing? and:
If xcliccfg.nlbits fields are independent, is it the case that mcliccfg.nlbits is used to determine the level of interrupts targeting M-mode, scliccfg.nlbits is used to determine the level of interrupts targeting S-mode and ucliccfg.nlbits is used to determine the level of interrupts targeting U-mode?
Thanks.

Reformatted cliccfg in https://github.com/riscv/riscv-fast-interrupt/commit/9d0784113d5ac87296ab4b2c1844a2e4ef833c8e

closed by #316 and text updates.


Add dropUp property to new dateInput

Merging this, but my guess is we are about to whack this branch shortly :-(


Front - V1 - iOS - Home Page

• create all components in the page
• CRA/Congés/Mes collègues/Note de frais -> all is blocked so in grey color.

[ ] When disconnect button is clicked

[ ] remove the token from the iOS Keychain
[ ] return to Login Page

[ ] "XpeApp" title text can be created from .navigationDestination() method of List() function
[ ] Create the grid of buttons (Grid documentation)
[ ] add Qvst button and breadcrumb


AllowAuthorSkip and InstaSkip do not work

Please tick all applicable boxes.

[x] I am using Python 3.5 or higher (run python --version on the command line)
[x] I have followed the official guides to install the bot for my system
[x] I have updated my dependencies to the latest version using the appropriate update script

Which version are you using?

[x] The latest master version (1.9.8)
[ ] The latest review version

What type of issue are you creating?

[x] Bug
[ ] Feature request
[ ] Question

Description of issue
AllowAuthorSkip in options.ini and InstaSkip in permissions.ini do not work as described.
Steps to reproduce
InstaSkip

Configure user in role in permissions.ini with InstaSkip = yes
Restart bot, queue song and observe that the song does not instaskip

AllowAuthorSkip

Configure setting in options.ini with AllowAuthorSkip = yes
Restart bot, queue song and attemtp to skip with the same user
Observe that the song does not instaskip

Also, other users should be present in voice, otherwise the songs will skip regardless because of the skip ratio being met.

Log file
musicbot.log
Please attach your MusicBot log file (located at logs/musicbot.log) to this issue. You can do so by dragging and dropping the file here. If you do not include your log file, you WILL be asked to provide one.

Use skip f instead of skip

Ah, thanks! Did not realized that had changed.


Title: Youtube Bookmarker

Is your feature request related to a problem? Please describe.
Dear sir/ma'am,
I would like to make a Chrome extension that can bookmark the fragments of a youtube video.
Describe the solution you'd like.
Firstly I will design it with a good UI using proper HTML, and CSS. Then, I will add new features.
Describe alternatives you've considered.
I will add new features to it like a button to bookmark the timestamp inside the video and a dropdown to see and manage bookmarked videos.
Add any other context or screenshots about the feature request here.
No response

Can you please assign this issue to me?

hey @Architsharma7 , please drop the screenshot of your project.

@Architsharma7 hope you are working on this issue

Yes I'm, it'll be completed by this week's end


code formating support?

hey,CodeMirror is wonderful !
I was using it...
but,code formating support? I think it's useful.

Nope, that's not something CodeMirror does (but there are, for most languages, great JavaScript-based pretty-printing modules available)


executeCommand  error

hi .
when i want use executeCommand get this error :
PHP Fatal error:  Uncaught Error: Call to a member function getChat() on null
my callbackquery file :
    public function execute()
    {
        $callback_query = $this->getUpdate()->getCallbackQuery();
        $chat_id = $callback_query->getFrom()->getId();
        $query_id = $callback_query->getId();
        $query_data = $callback_query->getData();

        if ($query_data = "test") {
                return $this->telegram->executeCommand('help');
        }
    }

please help me . best regards .

Your help command expects message object.
When you call it from callbackquery message object is not present.

thanks jacklul .
i just use StartCommand for example .
how i can fix it ?

Easiest would be to check within help command if it's a callbackquery and get chat id from query instead of message.

i'm newbie in php-telegram-bot .
if you can please tell me how i can send chatid and form id with executeCommand ?

i fixed my problem with :
https://github.com/php-telegram-bot/core/issues/631#issuecomment-329164101


Add 8.4.4 to the Windows-friendly make script

Thanks!
I'll merge this right away since it looks good to me and there is no need for waiting for the CI to pass on this change.

Thanks for merging @lorenzo
I also wanted to ask about this: I'm very interested in this whole thing working on Windows, and I'd be willing to put some hours towards it.
In particular, this .bat tingles my spidey sense, it could be written in PowerShell (which is the current Windows shell of choice) much more elegantly and DRY. Would you be interested in that?
In addition, the main readme offers a way to build on Windows by installing make and running make build-all, but that doesn't really work, since Windows executables have the .exe extension, but Makefile refers to them by the UNIX extension-less names. Is that something that was missed, or am I the one who is missing something?

@fsoikin Definitely, that would be great to have!

Is that something that was missed?

Most likely, since most of use are not currently using windows. It will be really helpful if you could help us fixing those oversights.

Great, thank you @lorenzo !


Add Copy/Move for content - Remove HtmlTextWriter

Currently we overload the definition of WriteTo on IHtmlContent
implementation classes to either represent a "real" write or a "flatten"
by checking if the writer inherits HtmlText writer.
This overloading is a bit of an odd fit and hides the real semantic we
want for flattening.
Additionally, we want to gradually make the concept of a pooled
backing-buffer for IHtmlContent first-class - using pooled buffers
dictates that we support move-semantics to some degree.
This change makes the work that we do for flattening into pooled buffers
explicit rather than hidden.

Hi @rynowak, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

:watch:

@dougbu updated

:shipit: once all the reactions are ready.

Will merge later.


Update creep for Retina

I've recently upgraded my laptop to a retina macbook pro and creep looks horrible on it.
I would like to update creep to work with retina too, but have no clue how to do this.
@chase : any ideas?

@romeovs I would argue that on a "retina" high density display, bitmap fonts are unnecessary. I find the benefit of having a low resolution font is to match a low pixel density of a screen around 72-75 PPI.
That being said, I'm not entirely sure. You are jumping from ~72 PPI to about ~220 PPI, so scaling tiny, aliased bitmap glyphs would be painful in just about any sense.
It might just be time to say goodbye to bitmap fonts on your MBP and use something that is spline/vector-based. That was my solution at least.

Cool thing about retina is that you can have something like DejaVu look really nice even at smaller font sizes, because of the pixel density.

I know. But I like creep also because I added some nice features like for haskell syntax etc. Currently I'm using Source Code Pro and it looks nice, I just miss creep :/
I also do not want to fall short on maintaining creep, which might happen if I stop using it myself.

I'm sure that if you stop maintaining it but it is still loved and used, somebody will take up the burden in a fork.

Closing this, because it seems there's no real answer here!


tests: add restart test case for #6648

What is changed and how it works?
Add restart test case for #6648.
Related changes
#7457
Check List
Tests

Unit test
Integration test

/run-unit-test


Fix bundling issues

Trying to resolve a bug which a user reported in the build process of vite lead to nextjs builds failing for another user.
The best practices to support both es modules and commonjs still seem to have pitfalls here and there.
Two approaches that look the most promising:

use the .mjs extension for the es module to make it unmistakably clear that it actually is a module
create a package.json file as part of the build step and place that into a folder next to the bundled module. This would mean we need a file structure like /dist/esm/bundle.js with /dist/esm/package.json right next to it. setting type: module in this package.json file would then only affect the bundle.js file in the /esm folder and signal to other bundlers that they should treat it as a module.

This PR implements the first solution and is tested with the latest nextjs and sveltekit frameworks.

I didn't quite follow the details of the issue. but I agree that this seems better than the alternative

for context, this is a writeup outlining the pitfalls https://www.sensedeep.com/blog/posts/2021/how-to-create-single-source-npm-module.html


mad cert "flag provided but not defined: -commonName"

mad cert miss the option --commonName

--commonName / CN, for example Google's:

Based on the information displayed in your screenshot, the root CA is indicated within the red box. Same with mad:
mad ca --ca ./ca.pem --key ./ca_key.pem --commonName "GTS CA 1C3"

And you want to issue a cert(cert.pem) to www.google.com by "GTS CA 1C3"(ca.pem)
mad cert --ca ./ca.pem --ca_key ./ca_key.pem --cert ./cert.pem --key ./cert_key.pem --domain www.google.com

Then, please inspect the cert.pem file, and it should be the same as shown in your screenshot.

ca.pem

cert.pem

BTW, the --domain parameter actually refers to the Common Name (CN). It is named as such because in typical scenarios, certificates are issued for domain names, and it also supports issuing certificates for multiple domains. mad will use the first domain specified as the value for the Common Name

I wanna to customize the Common Name (CN) of cert. I just sent the wrong screenshot, it should be:

I can put the domain to the first pos, thanks.


feat(sink): jsonb column to avro record/map/union type

I think I am facing a similar issue. I am trying to sink jsonb values from a materialized view into an avro schema in kafka, with map and record types. I am getting the following errors:
Encode error: encode foo error: cannot encode jsonb column as {"name":"foo","type":"record","fields":[{"name":"id","type":"string"},{"name":"name","type":"string"}]} field

Or
Encode error: encode foo error: cannot encode jsonb column as {"type":"map","values":"string"} field

Originally posted by @maingoh in https://github.com/risingwavelabs/risingwave/issues/11699#issuecomment-2130325570

@maingoh In your specific case, could you try converting the loosely-typed jsonb to a struct before sinking?
jsonb_populate_record(null::struct<id varchar, name varchar>, foo)

(Note the function jsonb_populate_record is only available since 1.9.0.)
As for a general case, note that true and 23 are also valid jsonb values but would not be able to be sinked as an avro record or map. In the workaround above we are explicitly saying null shall be used as a default in these unexpected cases.
Does this address your issue?

Thank you, I managed to sink a simple struct as an avro record but I don't find a way to generate a type that is convertible to an avro map. Is a jsonb object directly convertible to a map ? I actually have a joined table with a name, and some other columns. I would like to build a map<name, record<column_2, column_3, ...>>. I tried building a jsonb object of struct but it does not seem to work.
I would also need a way to union different types as avro allow it. For example we have a jsonb column which can be different types. I feel it does not exist (yet ?), what would be the best way to sink such values ?

As for a general case, note that true and 23 are also valid jsonb values but would not be able to be sinked as an avro record or map. In the workaround above we are explicitly saying null shall be used as a default in these unexpected cases.

Good to know! I actually didn't need to use jsonb_populate_record yet as I was building my record manually.

a type that is convertible to an avro map

You are right it is not available in RisingWave yet. Although jsonb feels close, there can be ambiguous cases, like {"foo": "AA=="} into avro map<bytes>. Instead, we plan to support a native map data type in RisingWave https://github.com/risingwavelabs/risingwave/issues/13387#issuecomment-1884348800

I would also need a way to union different types as avro allow it. For example we have a jsonb column which can be different types. I feel it does not exist (yet ?)

There is no native union data type either and it is not part of the plan. The plan is to allow sinking specific types, i.e. both int columns and bool columns can be sinked as avro ["null", "int", "boolean"]. If the upstream is a jsonb column, it would need to be split into strongly typed streams beforehand:
create sink variant_int as select foo::int from mixed where jsonb_typeof(foo) = 'number' ...
create sink variant_bool as select foo::bool from mixed where jsonb_typeof(foo) = 'boolean' ...

To clarify:

The ability to sink specific types in avro union (as shown above) does not exist today.
Alternatives are open to discuss. Given jsonb to avro struct/union is a very generic topic we would like to avoid implementing it a way that only works in one specific use case. We need to clearly define the data type mapping rules. The one defined in avro spec is an option, but very likely not what people want: it requires {"int": 42} or {"boolean": true} for avro union ["null", "int", "boolean"]. Such complexity and unclarity is why we prefer not to touch jsonb <-> avro and support strongly typed columns first.

Although jsonb feels close, there can be ambiguous cases, like {"foo": "AA=="} into avro map

Is it really possible to store bytes into a jsonb field ? At least JSON support only strings (usually bytes are b64 encoded strings). So for me it sounds quite natural to convert it natively to map<string, string>. And if the user want to cast it to bytes, he can ask for it explicitely eventually.

If the upstream is a jsonb column, it would need to be split into strongly typed streams beforehand

I agree that the union type is not very needed as a risingwave type. However doing the conditional check on types is something that RW could support natively for most types, it is not very user friendly to do so in SQL. If the jsonb column is compatible with the avro format, why not try to serialize it without needing some strong casts ? And having a way to default to null the uncompatible ones like in the example with jsonb_populate_record(null::struct<id varchar, name varchar>, foo). In my case I am sure that the avro will match the jsonb column, but one field can be from different types.
There could be a parameter on the sink side to treat jsonb columns as avro ones while sinking. This way it would still be stored as unstructured JSONB on RW (allowing a single json field to have different type) but would be converted in the sink only using this mapping:

JSONB
AVRO

array
array

object
record/map

integer
int or long ?

boolean
boolean

number
float

string
string

null
null

All other very specific (dates, bytes, smallint, float) would need an explicit conversion in the query itself. But since most JSON column only have the types above, it would save a lot of boilerplate to not have to handle this on the user side.
In a similar way, on the source side, RW would find the best native type if possible otherwise fallback to JSONB in case it is not possible.
It could be an optional parameter allow_jsonb_fallback_conversion=True. Or maybe a more explicit way of selecting which columns can be converted or not to/from jsonb. Just an idea :)

Here is another mapping that would fit my use case https://materialize.com/docs/sql/create-sink/kafka/#avro:

They have a native map type
Any nullable type is sinked as an avro union type of [my_type, "null"]
All other complicated cases (union of many types) are stored as a json string with a "connect.name": "io.debezium.data.Json" to be able to automatically decode it as json on consumer side

We will be working on a native map type soon.
Sinking nullable as avro-union-with-null is already supported today.
Sinking jsonb as avro-string is trivial and the support of connect.name is also work in progress.

My major concern above is about adding a native union type, or sinking arbitrary jsonb as avro union. There was one core difference I did not mention and may have led to some confusions:
RisingWave does not automatically generate and register the avro schema to schema registry. Instead, it accepts an existing one read from schema registry, so it need to do the following validation before seeing any concrete records:

Can a RisingWave int column fit into avro int field? Yes.
Can a RisingWave int column fit into avro boolean field? No. create sink fails.
Can a RisingWave jsonb column fit into avro ["int", "boolean"] field? It depends...

If we were to generate the avro schema, we could generate a ["null", {"type": "string", "connect.name": "io.debezium.data.Json"}] so that all possible jsonb values can fit in it. The schema auto-register deature is also in plan.
Does this address your concern?

We will be working on a native map type soon.
Sinking nullable as avro-union-with-null is already supported today.
Sinking jsonb as avro-string is trivial and the support of connect.name is also work in progress.

If 1. and 3. land quickly I feel handling union is less of a priority. In any case the native union type feels too much and can be handled using jsonb. I have not seen any database supporting it (I didn't spend much time though).
However I feel being able to source and sink array/maps/union as jsonb might be faster to implement than having a fully integrated native RW map, and will handle the union case.

Can a RisingWave jsonb column fit into avro ["int", "boolean"] field? It depends...

In this case I would say:

RW does not allow it by default, sink fail
Having some extra config in the sink that:

Allow the creation of the sink if it cannot know in advance
Could say which jsonb field can be converted to avro. Example: allow_jsonb_conversion = {'foo': {'default': null}, 'bar': {'raise': true}} (could be a more SQL like syntax).
Try to convert the jsonb value (foo and bar) to the corresponding avro schema. If fails raise an error for bar or default to null for foo.

@xiangjinwu any approximate idea when 1. and 3. would be available ?


AngularFire2 - Firestore - LLRBEmptyNode is not a constructor

From @patrickmichalina on April 4, 2018 0:31
Summary
I get a catastrophic error when importing the AngularFirestoreModule. This does NOT happen when using the AngularFireDatabaseModule.
Version info
    "@angular-devkit/build-optimizer": "^0.4.6",
    "@angular/animations": "6.0.0-rc.1",
    "@angular/cdk": "5.1.1",
    "@angular/common": "6.0.0-rc.1",
    "@angular/compiler": "6.0.0-rc.1",
    "@angular/compiler-cli": "6.0.0-rc.1",
    "@angular/core": "6.0.0-rc.1",
    "@angular/forms": "6.0.0-rc.1",
    "@angular/http": "6.0.0-rc.1",
    "@angular/material": "5.1.1",
    "@angular/platform-browser": "6.0.0-rc.1",
    "@angular/platform-browser-dynamic": "6.0.0-rc.1",
    "@angular/platform-server": "6.0.0-rc.1",
    "@angular/router": "6.0.0-rc.1",
    "@angular/service-worker": "6.0.0-rc.1",
    "@firebase/app": "^0.1.10",
    "@firebase/auth-types": "^0.2.0",
    "@firebase/database": "^0.2.1",
    "@firebase/database-types": "^0.2.0",
    "@firebase/firestore": "^0.3.7",
    "@firebase/firestore-types": "^0.2.2",
    "@firebase/messaging-types": "^0.1.2",
    "@firebase/storage-types": "^0.1.2",
    "@nguniversal/common": "5.0.0-beta.8",
    "@nguniversal/express-engine": "5.0.0-beta.8",
    "angularfire2": "^5.0.0-rc.6.0-next",

What is the expected behavior?
AOT compiles nicely
Actual behavior
App fails at runtime

Copied from original issue: angular/devkit#618

Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information.
If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.


Programming exercises: Improve details page layout

Checklist
General

[x] I tested all changes and their related features with all corresponding user types on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Client

[x] I strictly followed the client coding and design guidelines.
[x] I added multiple screenshots/screencasts of my UI changes.
[x] I translated all newly inserted strings into English and German.

Motivation and Context
Unify the layout of the programming exercise details- and edit-page by displaying information in the details page in the same sections as on the edit page.
Reducing the scope of some sections by introducing the new section Build Details, which is displayed directly after the General section, making the repository, checkout directory and Repository Diff more prominent on the details page.
Description

Moved the short name, auxiliary repositories, and recreate build plans to a new section Build Details that is added as second section
Moved the selection of categories up in the edit mode (within the General section) to be aligned with the details page

Steps for Testing
Prerequisites:

1 Instructor

View the details page of a programming exercise
See that a new section Build Status is introduced
Go to the create/edit page of a programming exercise
See that the section Build Status is reflected in the create/edit page
Verify that creating / editing / importing exercises still works

Testserver States

[!NOTE]
These badges show the state of the test servers.
Green = Currently available, Red = Currently locked
Click on the badges to get to the test servers.

Review Progress
Code Review

[x] Code Review 1
[x] Code Review 2

Manual Tests

[x] Test 1
[x] Test 2

Screenshots

Change
Before
After

Added Build Details Section in Details View

Added Build Details Section in Create/Edit/Import View

Summary by CodeRabbit
Summary by CodeRabbit

New Features

Introduced a method for displaying detailed build configuration information for programming exercises.
Enhanced interaction by integrating a build details component, providing real-time validation feedback during the update process.
Improved organization and clarity of the programming exercise detail presentation, enhancing user experience.
Added a user-friendly interface for managing build configurations and auxiliary repositories.

Bug Fixes

Resolved issues with form validity tracking across multiple sections of the programming exercise update interface.

Chores

Removed auxiliary repository management components to streamline the user interface.
Added a new build details component to improve functionality and user insights.

Thank you for the detailed feedback!

The name of the new section does not appear to be well-chosen, I agree that it is confusing to have a section Build Details and mainly configuring the build in the Language section. As we are actually editing the repositories here (defining the repository names via the short name and optionally adding auxiliary repositories), Repositories might be a better name for the section and prevent confusion?
The described problem of the interrelation between the sections Language and Repositories is something we should discuss for the auxiliary repositories, as the chosen language might have an impact on the configuration of the checkout directories (which is the case for the previous and the new solution), for this advanced case it would be more intuitive to define the language and package name first. In other cases, where no checkout directories are manually defined, I am not aware of differences for the user in the configuration based on the language selection.

I was not aware that having 5 sections was an active design decision. While the number of sections would be aligned with text-, modeling- and file-upload-exercises I am not sure if unifying the number of sections prevails the clarity in the programming exercise overview, as currently the Language section can be quite long in the exercise details view, and we might be able to allow for a quicker and more intuitive access to chosen configurations by deriving another section, which is the goal of this PR (together with displaying the Review Changes/Template-Solution-Diff feature at a more prominent place in the details section).

I did not test the responsiveness beforehand, as I relied on the extended form-status-bar to handle width changes properly. I did now test it with the following result:

With the 6th section Build Status (12 chars, such as Repositories)

horizontal scrollbar visible for the width 767px - 790px, but section titles still clickable without scroll (2 Tablets: Acer Picasso, Apple iPad Mini, 6 phones: LG Nexus 4, LG Nexus 4 AR, BlackBerry Z10, Nokia Lumia 1020, Nokia Lumia 1020, Nokia Lumia 920, Nokia Lumia 925, no issue for half screen on 14-inch device)
horizontal scrollbar from a width smaller than 540px (phones)

This is how it looks like 1px before the breakpoint is applied (767px):

With the existing 5 sections

horizontal scrollbar from a width smaller than 421px (phones)

If the horizontal scrollbar for 767px - 790px widths is an issue, we might be able to resolve this by improving the responsiveness of the form-status-bar or adjusting the breakpoint in this case. For phones, I would argue that it doesn't make a reasonable difference.

Ramona mentioned that the section titles have been intentionally chosen to be only one word. I misunderstood that this is the case to ensure that the section titles are short and easy to memorize. I was not aware that a single word for the section title is a fixed requirement.

Thanks for pointing out the previous thoughts that would have been violated! I am sorry about neglecting previous ideas with this PR, which was not my intention. I was not aware of #2 and only touched #3 in a discussion with Ramona, after which I thought Build Details would be a reasonable section title.
Follow-up Questions
For my understanding the reduced configuration options of the Simple Mode should be reflected in the details view, which would result in the Language section being reduced anyways (Sequential Test Runs, Build Script, and Docker Image would not be displayed in the details view). Do we have the same understanding?
If we decide to limit ourselves to 5 sections, I do think that the sections Mode, Problem, and Grading are well-defined and blend in nicely with the other exercise types. This would leave the open question if we want to move the definition of the Short Name and Auxiliary Repositories to the Language section, due to the dependence on the Programming Language and Package Name selection.

pro

might be more logical when editing
more consistent with the details view, where the repositories are already listed under the language section

contra

makes the configuration of the Language section longer in advanced mode

I would be in favor of moving the short name and auxiliary repository selection to the language section, as I would rate the pro bullet-points as more important. However, I have no strong opinion on this topic.


merge origin master

Please answer these questions before submitting pull request

Why submit this pull request?

[ ] Bug fix

[ ] New feature provided

[ ] Improve performance

Related issues

Bug fix

Bug description.

How to fix?

New feature or improvement

Describe the details and related test reports.

merge


Toast remove and timeout

Closes https://jira.corp.adobe.com/browse/RSP-1471
📝 Test Instructions:
Storybook toast provider stories have 5 second timeout and close removes them.
Storybook toast provider timeout stories demonstrate different timeout cases.
🧢 Your Team:
React Spectrum
Notes - No CSS transitions due to issue with the project changing classnames and the react transition code updates div class names outside of that. This is followup work.
Docs are out of scope and followup work.
Focus being a shift tab is out of scope and followup.

This PR will need some follow up changes but merging this for now.


orderNumber validation to alpha_dash

https://github.com/SzuniSOFT/laravel-szamlazzhu/blob/b9e4f7f4b2c49be91dfeec0fd71c55298a688771/src/Internal/Support/InvoiceValidationRules.php#L71
Is it possible to change the orderNumber validation from alpha_num to alpha_dash ? szamlazz.hu allows to use underscores & dashes in the orderNumber.

Hey gergotar,
My apologies, but the organization owner decided to exclude the package maintainers so we're not allowed to perform any hotfix / further development anymore. For now, the best I can advice to you is to clone the entire repository and make your desired changed.

Fixed at https://github.com/redmenta/laravel-szamlazzhu


[Feature Request]: Analysis and Prediction of Open Source Contribution

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Target Variable: OpenSource Contribution
Predictors: Variables such as Employment, FormalEducation, CompanySize, DevType, Exercise, etc.
Objective: Analyse and predict the likelihood of contributing to open-source projects based on personal and professional attributes.
Use Case
This analysis provides insights into the factors that encourage or discourage participation in open-source communities. This analysis can help organisations and open-source project maintainers understand the professional backgrounds of contributors, which can inform strategies to increase participation.
Benefits
Informed Strategies: Organisations and project maintainers can develop strategies to support and encourage contributions.
Supportive Environments: Creating environments that enhance contributor engagement and participation.
Priority
High
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

@sanjay-kv  Please assign this issue to me under GSSOC'24

hi


How to send 2 emails from a form (PHP)

I am facing an issue. I have a form and I want to send 2 emails -

to the admin with all the data
to the user who fills the form as a confirmation email

now i am able to send email to admin but stuck how to send email to user simultaneously.
Using Sendgrid with PHP cURL.

Hi @pbengani,
Please report this issue to our support team at: https://support.sendgrid.com
Thanks!


fix tsconfig.json#extends file reference

What issue does this pull request resolve?
What changes did you make?
Is there anything that requires more attention while reviewing?

I think this relies on the undocumented behavior here of appending a file name when extends is a path or package: https://github.com/microsoft/TypeScript/issues/51782


[Feature] Add the favicon to each calculator's page

Description
Favicon is not there in all the calculators , It is only there in the home page
@Rakesh9100 assign this issue to me I will make it in all the pages
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Proceed @Meetjain1

Status of your PR @Meetjain1

Working @Rakesh9100 will raise PR soon .


[Feature] Bar marker line

What problem does this feature solve?
There is no way to create marker lines for each bar with an appropiate width. There is a workaround with marker pointers, but the width has to be hardcoded, which means that it doesn't respond to changes in number of bars, redimension, etc.
The workaround:
option = {
  title: {
    text: 'Rainfall vs Evaporation',
    subtext: 'Fake Data'
  },
  tooltip: {
    trigger: 'axis'
  },
  legend: {
    data: ['Rainfall', 'Evaporation']
  },
  toolbox: {
    show: true,
    feature: {
      dataView: { show: true, readOnly: false },
      magicType: { show: true, type: ['line', 'bar'] },
      restore: { show: true },
      saveAsImage: { show: true }
    }
  },
  calculable: true,
  xAxis: [
    {
      type: 'category',
      // prettier-ignore
      data: ['Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec']
    }
  ],
  yAxis: [
    {
      type: 'value'
    }
  ],
  series: [
    {
      name: 'Rainfall',
      type: 'bar',
      data: [
        2.0, 4.9, 7.0, 23.2, 25.6, 76.7, 135.6, 162.2, 32.6, 20.0, 6.4, 3.3
      ],
      markPoint: {
        data: [
          { type: 'max', name: 'Max' },
          { type: 'min', name: 'Min', coord: [10,10]  }
        ],
        symbol: "rect",
        silent: true,
        symbolSize: [40,3],
        itemStyle: {color: "black"},
        label: {show: false },
      },
    },
    {
      name: 'Evaporation',
      type: 'bar',
      data: [
        2.6, 5.9, 9.0, 26.4, 28.7, 70.7, 175.6, 182.2, 48.7, 18.8, 6.0, 2.3
      ],

    }
  ]
};

Result:

What does the proposed API look like?
Add a new option for the bar series barMarker, which would have a data property with the ordered value of the markers. It could also just have a reference to a dataset with datasetIndex.  Another option would be to have a list of objects with the dimension name and the value to assign (this way you would be able to omit columns).
It should have styling options similar to the ones offered by markPoint:

Specify symbol (it could be a circle, line, dotted line, etc.)
Label
Color
Etc.

This would allow us to create things like this (photo from apexcharts):

Another way of doing this would be with the markPointer like the workaround but allow to set a custom string for the size (something like ['barWidth', 3])

I found a workaround but it is a VERY DIRTY WORKAROUND. It is prone to break in the future and it just hurts my eyes to look at it in my code, but it works 😁
I found it looking at the source code:
https://github.com/apache/echarts/blob/1047e897b90fe250f89a369e3646a7fbbfdc2b35/src/chart/bar/BarView.ts#L1119-L1123
So basically I do the same they do to calculate the barWidth. Maybe there is better way of getting the bar width, but for now I just found this.
After calling setOption or resize:
const barSize = this.echart["_chartsViews"][0]["_model"].getData().getLayout("size");

    const sizeOption: ECOption = {
      series: [
        {
          id: this.MAIN_SERIES_ID,
          markPoint: {
            symbolSize: [barSize, 3]
          }
        }
      ]
    };
this.echart.setOption(sizeOption);

I'm accessing at the chartsView index 0 because I know I have my BarChartView, but you should put the index of your bar dataset I guess.
Again, this is just dirty and not a good fix, but I guess it will just work until echarts provides a proper solution


REST API documentation

I'd like to create a dedicated issue for this to keep track of information and links for this topic.
Things taken from #303:

https://developers.helloreverb.com/swagger/
http://zacstewart.com/2012/04/14/http-options-method.html
http://www.restdoc.org/
http://restdesc.org/
WSDL (?)

More:

https://twitter.com/zdne/status/442739968654725121

I am surprised, i was trying to decide between swagger  and NelmioApiDocBundle to create an api.
Doesn't NelmioApiDocBundle uses symfony components? is there a php conflict on that or makes it too slow?

There are a few things that are missing here:

API Blueprint, https://apiblueprint.org/, https://github.com/apiaryio/mson
RAML, http://raml.org/about/about-raml
Not so much about docs but a bit related: http://jsonapi.org/

Update for OpenAPI Specification (fka Swagger RESTful API Documentation Specification) http://swagger.io/specification/

https://github.com/zircote/swagger-php Compatible with the Swagger 2.0 specification.
https://github.com/fsbahman/apidoc-swagger Inline Documentation for RESTful web APIs base on https://github.com/apidoc/apidoc-core (http://apidocjs.com)

citing @nostop8 from https://github.com/yiisoft/yii2/issues/62#issuecomment-245076528:

Simple REST API on-fly generator: https://packagist.org/packages/nostop8/rest-api-doc
Takes all the generated rules from urlManager, grabs information about the endpoint using Reflection. Very primitive, yet a good overview of what you've built and provides ability to test it quickly without having to write any single line of code. Additionally you can provide description of the service, it's params, model(s) etc.


[fix][doc] Use JDK 11 in system requirements

Signed-off-by: Zixuan Liu<EMAIL_ADDRESS>Motivation
Run the Pulsar 2.9.1 requires JDK 11, not JDK 8.
Modifications

Update JDK 8 to JDK 11 in getting started and deploy doc

Documentation

[x] doc

As it is the requirement to run Pulsar 2.9.1 and later versions, will you apply this change to the versioned docs as well?

This just applies to Pulsar 2.9.1 and later versions.

@nodece this PR only updates master docs, will you update 2.9.1 docs? https://github.com/apache/pulsar/tree/master/site2/website/versioned_docs/version-2.9.1

@nodece 2.9.2 is on the way. Will this change apply to the 2.9.2 doc set as well? (currently, we do not have the 2.9.2 doc set yet. I can generate if needed）

@momo-jun @Anonymitaet Thanks for your point! I double-check that the Pulsar Docker image, the Pulsar 2.8-lastest requires JDK 11, not JDK 8.
This PR has been updated, please take a look if you have time.

@codelipenghui I suggest that the version here should be consistent with the version in the Docker image, avoid don't support some features like some TLS configuration.

@codelipenghui I suggest that the version here should be consistent with the version in the Docker image.

But the Requirments section is updated.

Can we add a suggestion version of JDK?

Can we add a suggestion version of JDK?

Yes, look good to me.


integrate adding managed ID to AAD group in an AzureDevOps pipeline

hi -
we are running into a challenge right now.  We want to automate adding the managed identity from the app we create into the aad group as part of an Azure DevOps pipeline - but we seem to be running into a need to manually add the managed ID.
This is a one time task - but manual == bad.
Do you guys have any guidance on how to do this?

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

ID: 31b0d33c-f88e-d50c-2926-7933940f3b92
Version Independent ID: 4aaef906-f501-6947-5d23-1b704470f09d
Content: Secure SQL Database connection with managed identity - Azure App Service
Content Source: articles/app-service/app-service-web-tutorial-connect-msi.md
Service: app-service-web
GitHub Login: @cephalin
Microsoft Alias: cephalin

@benjamin-goldman Thanks for the feedback! We are currently investigating and will update you shortly.

Hi @benjamin-goldman, thanks for your patience. This documentation shows you different ways to   configure managed identity for Azure App Service:
Azure portal
Azure CLI
Azure PowerShell
Azure Resource Manager template
Hope that helps. Please let us know if this works for you.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

None of those can be automated as they require being logged in as a full AD user - it won't work as a service principal or as another MSI user.
This is a huge issue for us, we are unable to automate any database deployments to use managed identity - we've spent weeks on this issue trying every documented path but none of them work.

https://blog.bredvid.no/handling-azure-managed-identity-access-to-azure-sql-in-an-azure-devops-pipeline-1e74e1beb10b
maybe this will help?


Think about entry points

As someone looking into the hidden modularity, I'd like to know a few entry points from which I could start my research.

Describe the solution you'd like
For each of the following rough parts of squeak/smalltalk, there should be at least one entry point documented:

User Input
Graphics Output
Network Access

Conditions of satisfaction

[x] Each of the rough parts has at least one entry point
[x] There is a wiki page documenting the entry points
[x] For each entry point there is an extra issue that is at least a rough idea on how to tackle it

(FYIO, in case you have not seen it yet, there is also a generic entry point in TraceDebugger class >> #exampleWorldCyclesFor: and you could extract a relevant subset of the trace afterward, e.g., using #borderContexts:. However, tracing entire world cycles is pretty slow right now ...)


FAB - Send to Trash/Delete/Mark as Read/Unread

When the user longpresses a webmail, or clicks on the icon, currently the fab only allows send to trash
Implement a menu fab that allows for this - Use this library.

https://android-arsenal.com/details/1/965

Inside the FAB -

Trash
Delete
Mark as Read
Mark as Unread

Done :D


dotenv-rails v2.3.0

Hello,
dotenv 2.3.0 published on rubygems, but where dotenv-rails 2.3.0?

Yup, we had a little hiccup in the release process but got it fixed this morning and I just published the updated dotenv-rails https://rubygems.org/gems/dotenv-rails


Wrong export types (CJS vs ESM modules)

The package.json export field seems to be misconfigured for the ESM export. I've run into the issues importing zod in one of my projects.
The publint is giving following warning (https://publint.dev/zod@3.23.8).

The types is interpreted as CJS when resolving with the "import" condition. This causes the types to be ambiguous when default importing the package due to its implied interop. Consider splitting out two "types" conditions for "import" and "require", and use the .mts extension, e.g. pkg.exports["."].import.types: "./index.d.mts" (More info)

Fixing that should solve the problem. Would you accept a PR?

Possibly related https://github.com/colinhacks/zod/issues/2557

Confirming that this is an issue. Currently, zod is masquerading as CJS when used in a ESM project with module: nodenext or module: node16 set in the tsconfig. For more context: https://arethetypeswrong.github.io/?p=zod

@marcomuser are you aware of a workaround? Just ran into this myself.

You can patch the package.json of zod in your node_modules by changing the type reference to "types": "./index.d.mts". This should fix the package import in esm projects (but break it in cjs projects). Not sure if there is a sensible workaround besides fixing this upstream.

@colinhacks can we get a quick fix for this?

@marcomuser could you give me a snippet of code to show exactly what package.json needs to look like? I'm unfamiliar with how this works.


How do I include a package that uses a package which is also found in vcpkg

I am using cereal for serialization of objects, and this uses rapidjson internally. I would also like to use rapidjson natively since cereal makes a couple of changes inside its reference to rapidjson.
This results in my linker process freaking out with some defined allready defined and what not.
Is there any way to handle this (lack of proper word) "package reuse"?

 I could imagine this happens because cereal links statically to rapidjson and you are also linking to it statically. What triplets are involved?

@invy It's all header only, but cereal uses its own moded internal version (which then clashes with the vcpkg one).

@degski I see.
Looks like to be known problem:
https://github.com/USCiLab/cereal/issues/121

@Laro88, see cereal issue https://github.com/USCiLab/cereal/issues/121,  you might need to update cereal to point the native rapidjason version that you want, I don't have a good suggestion for this, please let me know if you expect VCPKG to do something here.

@Laro88, feel free reopen this issue if you think vcpkg could do something here.

Hey @PhoebeHui, we just started running into this issue as well. Vcpkg could explicitly define a cereal-flavored namespace for cereal's rapidjson inside of rapidjson.h. This will ensure that it does not conflict with direct rapidjson usage in the same binary. Here is the patch that contains the fix which has been tested with the latest cereal portfile:
diff --git a/include/cereal/external/rapidjson/rapidjson.h b/include/cereal/external/rapidjson/rapidjson.h
index 3eefe60a..69b9ed91 100644
--- a/include/cereal/external/rapidjson/rapidjson.h
+++ b/include/cereal/external/rapidjson/rapidjson.h
@@ -115,7 +115,7 @@
     \see CEREAL_RAPIDJSON_NAMESPACE
 */
 #ifndef CEREAL_RAPIDJSON_NAMESPACE
-#define CEREAL_RAPIDJSON_NAMESPACE rapidjson
+#define CEREAL_RAPIDJSON_NAMESPACE cereal::rapidjson
 #endif
 #ifndef CEREAL_RAPIDJSON_NAMESPACE_BEGIN
 #define CEREAL_RAPIDJSON_NAMESPACE_BEGIN namespace CEREAL_RAPIDJSON_NAMESPACE {


Transform -> C++

[DRAFT][WIP]
This is the initial effort to pull through the "Transform -> C++".
The current revision has all the necessary pieces (ROUGH DRAFT) that I'd need to slowly churn out a final C++ equivalent of the transform dialect script we have.
I'm not sure if this repository is the ideal place for this support to be in or it should be in IREE, but there are bigger fishes to catch right now -> at least get through with each invocation step properly.

Not required.


Support for hiding on-going events

A simple patch to add a new config variable to calendar.js to hide events that have already started. They are removed in the same location as private events and thus should work analogously.

Warnings

:warning:

Please include an updated CHANGELOG.md file.This way we can keep track of all the contributions.

  Generated by :no_entry_sign: dangerJS


Use native css custom properties when available

Currently, even when native css custom properties are available, Polymer still shims css custom properties. We cannot simply turn off the shimming in this case because Polymer uses an unimplemented but proposed native feature @apply.
We'll need to shim @apply as css custom properties to be able to use native css custom properties.

Great, glad to see this is high priority! :+1:

:+1:

:+1:

:+1:

Any word on this @sorvell? I think some of this has landed?

This landed as an opt-in features in 1.6.0!
https://www.polymer-project.org/1.0/docs/release-notes#v-1-6-0

It does have several issues, so buyer beware: #3803 #3800  #3801 #3802  #3806 #3807 (some fixed in master)

Reopening for @sorvell to close when he things this is ready for mass exposure.

@ebidel ready? :)

Seems like all the open issues are closed.

we switched it on in Chrome WebUI and nothing has caught fire yet

Nice! 🎉


Fix minor url issues in app utils and api oauth file

Just fixes minor issues.

@techytushar If this looks good to you, I'll go ahead and merge


[FLINK-23111][runtime-web] Fix missing table component's nzFrontPagin…

What is the purpose of the change
After bumping runtime-web Angular and NG-Zorro-Antd to v12, some table components which set [nzShowPagination]="false" have a missing [nzFrontPagination]="false" config, causing such tables to show at most 10 records (default page size value). This information can be found at https://ng.ant.design/components/table/zh#api.
Brief change log
Add the missing [nzFrontPagination]="false" config.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

Hi, @twalthr and @Airblader . I did a bug fix regarding the runtime-web's framework modernization. Please review it when you have the time. Thanks.


feat(sort-by): implement InstantSearch.css

Specs
https://instantsearch-css.netlify.com/widgets/sort-by/
Stories
https://deploy-preview-3120--algolia-instantsearch.netlify.com/v2/dev-novel/?selectedStory=SortBy.default

Done @bobylito.

I'll let you merge the changes :)

The story seems broken on deploy:
Uncaught ReferenceError: You can't access 'instantsearch.widgets' directly from the ES6 build.
Import the widgets this way: 'import {searchBox} from "instantsearch.js/es/widgets"'
    at Function.get (index.js:19)
    at sort-by.stories.js:15
    at wrap-with-hits.js:78
    at e.value (dev-novel.js:170)
    at index.js:55
    at O (mobx.module.js:911)
    at n (mobx.module.js:902)
    at Object.<anonymous> (index.js:42)
    at t (bootstrap 78695c623afd6e3f043e:19)
    at bootstrap 78695c623afd6e3f043e:62

On my local machine:
ERROR in ./dist-es5-module/src/components/Slider/Slider.js
Module not found: Error: Can't resolve 'react-nouislider' in '/Users/francoischalifour/Development/algolia/instantsearch.js/dist-es5-module/src/components/Slider'
 @ ./dist-es5-module/src/components/Slider/Slider.js 37:23-50
 @ ./dist-es5-module/src/widgets/range-slider/range-slider.js
 @ ./dist-es5-module/src/lib/main.js
 @ ./dist-es5-module/index.js
 @ ./dev/app/builtin/stories/sort-by.stories.js
 @ ./dev/app/builtin/init-stories.js
 @ ./dev/app/index.js

I'm not sure to understand.


WIP: Debug package installation

What does this PR do?
WIP
Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

But you are not running any app tests, right?
I believe that the fix is https://github.com/Lightning-AI/lightning/pull/15435#discussion_r1009982968 :rabbit:


Add "typings" to package.json

Summary
I'm using loadStripe with Angular, and Angular's build system expects packages to conform to the Angular Package Format.  Part of that requirement is to specify the path to the typings file using the "typings" property in the module's package.json.  @stripe/stripe-js has "types" but not "typings", and as a result AOT builds fail.
Other information
There's a StackBlitz here that demonstrates the error: https://stackblitz.com/edit/angular-kezmsy?file=src%2Fapp%2Fapp.module.ts  The error can be reproduced as follows:

Download the following project from StackBlitz: https://stackblitz.com/edit/angular-kezmsy?file=src%2Fapp%2Fapp.module.ts
Extract the zip file: unzip angular-kezmsy.zip
Install dependencies: npm i
Do a production build: npm run build -- --prod

That results in a difficult-to-diagnose error:
ERROR in ./src/app/app.module.ngfactory.js
Module not found: Error: Can't resolve '@stripe/stripe-js/types/index' in '/home/user/Downloads/angular-kezmsy/src/app'

I also files a bug report against angular-cli, which requests that the build process support both "types" and "typings."  The TS doc suggests that the two are synonymous.  Here's that report: https://github.com/angular/angular-cli/issues/17353
And I have a SO question with some additional context: https://stackoverflow.com/questions/60940657/angular-8-and-stripe-js-v3s-loadstripe-module-not-found-error-cant-resolve
Thanks for any help.

Hey @benbotto, I've added the typings field to the package.json file and will publish this change shortly. Thanks for the report!


New behavior for closing requests

This is an attempt at addressing #192. I've also experienced the problem where certain requests are just "left hanging", they're never closed and cause the process to keep running indefinitely unless timed out.
My solution here was to always close HTTP responses on their "end" event.
I don't see any obvious holes in the old logic, my best guess is that the complete property for some reason isn't always set on the response when it is in fact complete. I don't see why that would be, but on the other hand I couldn't find any documentation for that property, so there might be some unpredictable behavior there.
The diff is noisier than my actual changes because of an indentation change, but the basic changes are:

call processReceivedData directly on the request's "end" event
always assume that the chunk argument to receiveData is defined
remove the logic in receiveData that calls processReceivedData

Thanks! I'll check this out when I get to work today. :)

If the complete property is the actual culprit, then the response.finished might be what we're really looking for. However, I still don't see a reason to not use this new behavior, it's also clearer from a developer's perspective


HDDS-9582. OM transport factory configuration mismatch

What changes were proposed in this pull request?
Fix OM transport factory configuration mismatch.
See HDDS-9582
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9582
How was this patch tested?
CI, plus local run to verify that S3 still works normally.

@duongkame Thanks for the changes, it LGTM! Can you update your branch to the latest master? Changes are on top of a commit from last month. Although there are no conflicts with master, there could be a change that along with this patch, breaks the tests.

We may want to change the two new log messages to debug to avoid polluting the output by default.

@adoroszlai I tested it locally, these logs will appear only once at the creation of a new RpcClient. I don't see them in OM logs.

these logs will appear only once at the creation of a new RpcClient. I don't see them in OM logs.

Yes, they appear only once.  But I'm not sure users running hdfs dfs -put and other operations are interested in this detail.  (The fact that Hadoop metrics system logs at info level is also a pain...)
$ hdfs dfs -put /opt/hadoop/NOTICE.txt ofs://omservice/volume1/bucket1/ozone-72528
2023-12-20 00:38:45 INFO  OmTransportFactory:62 - Loading OM transport implementation org.apache.hadoop.ozone.om.protocolPB.Hadoop3OmTransportFactory as specified by configuration.
2023-12-20 00:38:46 INFO  MetricsConfig:120 - Loaded properties from hadoop-metrics2.properties
2023-12-20 00:38:46 INFO  MetricsSystemImpl:378 - Scheduled Metric snapshot period at 10 second(s).
2023-12-20 00:38:46 INFO  MetricsSystemImpl:191 - XceiverClientMetrics metrics system started
2023-12-20 00:38:46 INFO  MetricRegistries:64 - Loaded MetricRegistries class org.apache.ratis.metrics.dropwizard3.Dm3MetricRegistriesImpl

I don't think it's necessary. CI run for PR builds/tests merge into current master:

HEAD is now at https://github.com/apache/ozone/commit/be72540658e3e98aa9687afa146844279f43cf41 Merge https://github.com/apache/ozone/commit/f04f4afca262908c551ec7c8c8010681012a4893 into https://github.com/apache/ozone/commit/b55437f06b4ad524ebf4af42b31a92541160bede

https://github.com/apache/ozone/actions/runs/7269033371/job/19806008549#step:2:494

@adoroszlai Thanks for the clarification.

But I'm not sure users running hdfs dfs -put and other operations are interested in this detail.

Yes, you are right, switching the log level to debug would be best.

these logs will appear only once at the creation of a new RpcClient. I don't see them in OM logs.

Yes, they appear only once. But I'm not sure users running hdfs dfs -put and other operations are interested in this detail. (The fact that Hadoop metrics system logs at info level is also a pain...)
$ hdfs dfs -put /opt/hadoop/NOTICE.txt ofs://omservice/volume1/bucket1/ozone-72528
2023-12-20 00:38:45 INFO  OmTransportFactory:62 - Loading OM transport implementation org.apache.hadoop.ozone.om.protocolPB.Hadoop3OmTransportFactory as specified by configuration.
2023-12-20 00:38:46 INFO  MetricsConfig:120 - Loaded properties from hadoop-metrics2.properties
2023-12-20 00:38:46 INFO  MetricsSystemImpl:378 - Scheduled Metric snapshot period at 10 second(s).
2023-12-20 00:38:46 INFO  MetricsSystemImpl:191 - XceiverClientMetrics metrics system started
2023-12-20 00:38:46 INFO  MetricRegistries:64 - Loaded MetricRegistries class org.apache.ratis.metrics.dropwizard3.Dm3MetricRegistriesImpl

Got your point. I just think in production these logs can be informatic on the server-side. In a happy time, no one cares. But in case of any problem, it's a good assertion, even for a command client as the example above. Transport protocol is an important piece of information when clients talk to OM.

Transport protocol is an important piece of information when clients talk to OM.

OK, log level can be changed in config if needed.
Thanks @duongkame for the patch, @xBis7 for the review.


Broken links in Universities.csv > Inflation_Source

Thank you for conducting your in-depth investigation and providing this rich dataset.
The links under the Inflation_Source column in the Universities table appear to be broken. It looks like the material hosted on OSU's website changed. Perhaps the relevant data was moved to this PDF?
If needed, updated links could point to specific PDF pages by appending the URL with #page= followed by the numeral of the page number (for example, #page=7).
Are pull requests encouraged for this repository? If so I'm willing to submit one with updated links, though I am not sure which column denotes the year to look up in the table.

It looks like the links were updated in f35a544


[Bug]: Python breaks on windows

What happened?
if you press shift or control when in python thing on windows, q>q breaks
OS
Windows
OS version
Edition	Windows 10 Home
Version	20H2
Installed on	3/23/2021
OS build	19042.1165
Experience	Windows Feature Experience Pack 120.2212.3530.0
What version are you seeing the problem on?
No response
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

this could be because this is a pr build for #3! let me send a normal build

Might try to test on windows

python was removed from the app due to other bugs


Card title resize

Closes #3266
Summary
This PR fixes a bug in the logic for useHasTextOverflow hook and updates the card to handle the changes from this fix.
Change List (commits, features, bugs, etc)

Updated the useHasTextOverflow.jsx to make more dynamic
Updated Card.jsx to handle changes need for text overlfow
Wrote some jest unit test to test if it would change via prop update
Wrote cypress test since our jest test manually update the values for clientWidth and scrollWidth to ensure it behaves well in actual browser.

Acceptance Test (how to verify the PR)

Go to
this story
click on subtitle and see that there is a tooltip
click on isExpanded knob
Check that tooltip is off for subtitle
then:
Click on title and see tooltip
Update the title in knobs to something short
click on title and see tooltip has gone away

Things to look for during review

[ ] Make sure all references to iot or bx class prefix is using the prefix variable
[ ] (React) All major areas have a data-testid attribute. New test ids should have test written to ensure they are not changed or removed.
[ ] UI should be checked in RTL mode to ensure the proper handling of layout and text.
[ ] All strings should be translatable.
[ ] The code should pass a11y scans (The storybook a11y knob should show no violations). New components should have a11y test written.
[ ] Unit test should be written and should have a coverage of 90% or higher in all areas.
[ ] All components should be passing visual regression test. For new styles or components either a visual regression test should be written for all permutations or the base image updated.
[ ] Changes or new components should either write new or update existing documentation.
[ ] PR should link and close out an existing issue

Regarding the Acceptance Test:

Story link does not work. Assume you meant this https://deploy-preview-1824--carbon-addons-iot-react.netlify.app/?path=/story/watson-iot-card--with-ellipsed-title-tooltip-external-tooltip
I don't see a subtitle, there is only the title

@bjornalm added.


Check docusaurus build on pull requests

I just broke the whole web site (fixed in #345) but I don't think any automatic checks failed.

Looking into this, we already validate that the docs build on pull requests. Unfortunately, the breakage in question was still a successful build, so the checks we have didn't catch it.
Reading through the docusaurus docs, it's unclear to me that changing any settings would fix this. Supposedly, the build should already be failing when any broken link is detected. The only thing I can think of that might help is also causing a failing build on broken markdown links, though I would assume the former setting should also cover this case. I guess it might not have caused a failure because of this?

URL paths are unprocessed by Docusaurus, and you can see them as directly rendering to , i.e. it will be resolved according to the page's URL location, rather than its file-system location.

see https://docusaurus.io/docs/markdown-features/links

Unfortunately the logs for that build are gone at this point, but I'm guessing because the path was about and not about.md it interpreted that link as a URL path and didn't check it.
In any case, hopefully causing a failure on links in markdown sources themselves will prove better anyways.
See:  #369

Note: It also looks like we don't currently protect branches from merges on failing builds. We should add a branch protect condition that requires build actions to pass before permitting a merge: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule

Thanks, I just set it up to block on the success of the "Build Documentation" check. (I didn't immediately see a way to block on the code build and tests, but I did not look hard at all.)
I also took the opportunity to do the other thing I'd said I would do, which is to require an approved PR before merging. (And I turned on the requirement for linear history, which we've tried to stick to already.)

Blocking PRs on the doc build hasn't gone as well as I'd anticipated: https://github.com/jspecify/jspecify/pull/371 ended up blocked on that build, which was "expected" but not run. I overrode it to merge anyway, but maybe we need to configure the docs build to run in more cases?

Ah, I guess it's currently restricted to changes to docs/**, logically enough :) Maybe we just turn it on for everything, or we go to the effort to make it run but no-op for changes outside that directory?

Ah, I guess it's currently restricted to changes to docs/**, logically enough :) Maybe we just turn it on for everything, or we go to the effort to make it run but no-op for changes outside that directory?

I think we could do that. Right now the entire workflow triggers only when docs/ is affected, instead we could trigger the workflow regardless and simply skip jobs/steps if the dir isn't affected.

@cpovirk in https://github.com/jspecify/jspecify/pull/369 I've disabled the path requirement since there wasn't an obvious way to factor that down to the job level. This means we'll run a doc build on all PRs to main, but that shouldn't be too costly (at least not yet). We can always revisit if it proves to add too much additional wait time to non-doc PRs.