Clarify how auto should be resolved

It may be worth an additional clarification in here noting that 'auto' doesn't need to be included in the constraints as it's defined in the schemas for the transport types.


Simplify the ReadableStream polyfill

At this point in time, all of the supported browsers (in the PDF.js project) have native ReadableStream implementations; see https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream#browser_compatibility
Hence the polyfill is only necessary in Node.js environments now, and we shouldn't need to do any detailed feature detection either (since that was only done for the non-Chromium versions of the MS Edge browser).
Finally, we can slightly reduce the size of the Chromium-extension since the polyfill shouldn't be needed there either.

/botio unittest

Thank you for improving this!


fix: createPages only for docs content

Changes proposed

Add sourceInstanceName: { eq: "docs" } filter to the query when looking for pages to generate in gatsby-node.js. Fixes an issue where adding another source with markdown/mdx content may cause the plugin to fail during build.

Additional context

Hey guys, thanks for this PR! I am going to take a look at it soon!


Cli for Microsoft 365 release blog post 7.6

Category

[X] New article

Cool stuff @Adam-it! A few tiny comments from my side.
done ✅

@waldekmastykarz done ✅
@Jwaegebaert done ✅


Ternary with sibling classes warns of incompatible types

Godot version
3.4.4
System information
macOS 10.15.7
Issue description
Sibling classes extending the same base class report incompatible types when assigning using a ternary. A warning is produced stating the following.

Values of the ternary conditional are not mutually compatible

The same does not occur for a ternary producing type of superclass or subclass as follows.
var _dummy: DummySuper = DummySuper.new() if true else DummySub0.new()

Steps to reproduce

Create a superclass.extends Node
class_name DummySuper

Create two subclasses that each extend the superclass.extends DummySuper
class_name DummySub0

extends DummySuper
class_name DummySub1

Instatiate a variable of type superclass as one or the other subclass in a ternary.var _dummy: DummySuper = DummySub0.new() if true else DummySub1.new()

Minimal reproduction project
ternary_repro.zip

At first glance it looks like the type compatibility check in the gdscript parser only checks for parent-child relationships, not siblings?
You can avoid the warning by casting to the super class:
var _dummy: DummySuper = DummySub0.new() as DummySuper if true else DummySub1.new() as DummySuper

Still happens on Godot 4b12. The workaround works for now.


Update getting-started-with-the-rest-api.md

Why:
Closes [issue link]

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Děkujeme za otevření této žádosti o stažení! Člen týmu dokumentů GitHub by měl brzy poskytnout zpětnou vazbu. Mezitím si prosím přečtěte pokyny pro přispívání .


Fix: Transfered Orgs Not Visible for New Owner

Transferred org (PFP Deployer) from danner.eth to directdeposit.eth
https://polygonscan.com/tx/0x42caa0ac4a359ab14580c212cb5fbc09e00a2b3165fae93690b61216adb6e223
org: 0x90ffdF48A1660A2759d82c1aF78318F414B1a9b5
original owner: 0x581bef12967f06f2ebfcabb7504fa61f0326cd9a
new owner: 0x34744Dd0Fb927366228A2eAee0D142620FF26077
view from new owner

view from old owner

(note: before logging out and back in to danner.eth, I could still see the PFP Deployer org and I could only see the item in it that danner.eth was a holder of, but not a manager of)

This issue has been claimed and is in progress with PR #174.

Resolved in #174


Delineate Candidates/Voters

This effort should change up the format of the elections, where voters can be distinct from the candidates.
Currently, every voter is automatically a delegated candidate.
We need to allow large communities to be able to vote on a specific subset of candidates.

I made this change on the off-chain version at https://github.com/scaffold-eth/scaffold-eth/tree/qd-off-chain-voters-and-candidates
You have two lists. One for the voters and one for the candidates:

And the rewards page, the information is split too.

Maybe we can add a checkbox "Use voters as candidates too" and if you check that you have to fill just one list and if you leave this unchecked, you have the two lists.
@hansmrtn what do you think?


supporting target image type qcow2

@ygal - I updated the relevant test to use DoAndReturn and check the target image type


[dunfell] {melodic} libsensors-monitor, cpu-temperature-diagnostics: remove bba…

…ppend

lmsensors recipe was fixed with:
https://lists.openembedded.org/g/openembedded-devel/message/93942
we no longer need to remove the runtime dependency on it

Signed-off-by: Martin Jansa<EMAIL_ADDRESS>

Included in newer branches since https://github.com/ros/meta-ros/pull/975


Soft Channel labels

Hi,
thanks for your very interesting work. I was wondering whether you could release your code for the soft channel labels.
Also, in https://github.com/PRIS-CV/Mutual-Channel-Loss/issues/15 you mentioned that it is not very good, even though the reported accuracy was increased. Could you explain the drawbacks of that method?
Greetings

Sorry for being late.
The MC-Loss will make the channels class-aligned, which will hurt the fine-tuning process. (Fine-tune needs slight variation in features, but MC-Loss will make the variation in features very large.)
Therefore, the current version of MC-Loss is not very suitable for fine-tuning. When we train the model from scratch, we can obtain huge improvements.


Error API Call blocked for Keep-Alive seconds

I followed the steps but cannot succeed.
The function in node red return this message
I tried to wait 60 minutes between calls, but same issue.
Is this addon still working ?
"Error API Call blocked for Keep-Alive seconds"

Hello,
2 things, the Enedis API as changed to V5, I will change this but it looks like the new API doesn't work like the previous version, I will investigate.

Hi,
API call updated to V5, please upgrade your Node into Node-Red, ping me if you have issues.

Closed

Hello,
Ecowatt node is now updated to V5 of RTE's API , keep me post if you have
any issues.
You must uninstall the node, update your palet list and install again.
Best regards
Vital
Le lun. 28 oct. 2024 à 14:25, Comawhite54 @.***> a
écrit :

I followed the steps but cannot succeed.
The function in node red return this message
I tried to wait 60 minutes between calls, but same issue.
Is this addon still working ?
"Error API Call blocked for Keep-Alive seconds"
—
Reply to this email directly, view it on GitHub
https://github.com/Vital91/node-red-contrib-ecowatt/issues/1, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AOPB3XGEPQGEL75KKHCYLZ3Z5YUMPAVCNFSM6AAAAABQXNKWWGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGYYTQNBSGM2TAMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


fix(quic/stream): return error on read

Description

Links to any relevant issues

Open Questions

Change checklist

[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] A changelog entry has been made in the appropriate crates

Friendly ping @kpp any objections merging here?


Not sorted DNS data in outbound gossip merge

While investigating #1603, a similar issue was found:

If gossip data is queued outbound, and we have more to send, GossipData.Merge() gets called.  This checks that g.Entries is sorted case-sensitively, then calls g.Entries.merge() which checks that it is sorted case-insensitively.  With entries of mixed case, it is impossible to satisfy both checks.

(not seen in the wild - requires blocking-back of outbound data together with mixed-case names)

Updated description; this code will fail faster than I thought.

Fixed by #1615.


Remove the temporary code for the selection fix

Remove the temporary code introduced in the selection fix: #4629

Codecov Report

Merging #4696 into master will increase coverage by 0.2%.
The diff coverage is 50%.

@@             Coverage Diff             @@
##             master    #4696     +/-   ##
===========================================
+ Coverage     64.75%   64.95%   +0.2%
  Complexity       16       16
===========================================
  Files          1061     1061
  Lines         56673    56609     -64
  Branches       8418     8408     -10
===========================================
+ Hits          36696    36768     +72
+ Misses        17268    17118    -150
- Partials       2709     2723     +14

Impacted Files
Coverage Δ
Complexity Δ

...e/pinot/core/query/reduce/BrokerReduceService.java
83.86% <50%> (-0.87%)
0 <0> (ø)

...ache/pinot/common/utils/TarGzCompressionUtils.java
68.23% <0%> (-12.95%)
0% <0%> (ø)

...mpl/dictionary/DoubleOffHeapMutableDictionary.java
45.16% <0%> (-11.83%)
0% <0%> (ø)

.../impl/dictionary/LongOffHeapMutableDictionary.java
66.66% <0%> (-6.46%)
0% <0%> (ø)

...troller/helix/core/retention/RetentionManager.java
75% <0%> (-4.17%)
0% <0%> (ø)

...inot/transport/netty/NettyTCPClientConnection.java
81.45% <0%> (-3.98%)
0% <0%> (ø)

...org/apache/pinot/client/DynamicBrokerSelector.java
69.69% <0%> (-3.04%)
0% <0%> (ø)

.../main/java/org/apache/pinot/client/Connection.java
47.61% <0%> (-2.39%)
0% <0%> (ø)

...pache/pinot/core/realtime/stream/StreamConfig.java
95.18% <0%> (-1.81%)
0% <0%> (ø)

...java/org/apache/pinot/common/utils/DataSchema.java
83.15% <0%> (-1.06%)
0% <0%> (ø)

... and 33 more

Continue to review full report at Codecov.

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


Java support?

I have java server-side and c++ clients. Can i use gRPC in this scenario?

yes. you can.
On Wed, May 6, 2015 at 11:18 PM, Anton Smirnov<EMAIL_ADDRESS>wrote:

I have java server-side and c++ clients. Can i use gRPC in this scenario?
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/issues/1507.

Can i have a brief tutorial on this?
Having .proto with messages and server definition:

How to generate C++ server RPC available on port N
How to generate Java client to send request to host H port N

There's a few examples over there: https://github.com/grpc/grpc-common

FYI: gRPC Java is in a different repo: https://github.com/grpc-java


featureadd mtmvJobManager to DEPRECATED_MODULE_NAMES

Proposed changes
Issue Number: close #xxx
Inherited from：26041
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


I655 ctrl vent changes

issue #655
This should work. Please update from master and test.

@daren-thomas and @JIMENOFONSECA tests are failing because I changed the only function that actually has a unit test ;-)
How can I run dodo without the test_sensible_loads.py?

it looks good, just it needs to pass the unittests

@gabriel-happle you can't. but you can update the expected results to be the new ones... huh. I just ran the tests and it seems you changed the signatures of the functions. so. your next step would be to figure out:

are the tests still the right tests for the code?
if not, what tests should be there instead?
update the tests to run through

Exactly @daren-thomas we changed the signatures because we got rid of the hard coded values that these functions were looking up in a dict. They are now just getting something from inside the bpr object. Therefore it's hard to check for correct inputs in the function, as the bpr can basically contain anything.
I'm sorry I changed the only function with unit tests :(
But I don't know what to check now. The relationship between inputs and outputs is taken care of in the Excel database.
Basically there should be some check during the creation of bpr that checks whether all necessary data is present.

C:\Users\Gabriel\Anaconda2\envs\cea\python.exe C:/Users/Gabriel/Documents/GitHub/CEAforArcGIS/cea/tests/test_calc_thermal_loads.py
read input files
Building B06 has no heating system, Hs corrected to 0.
done
..
Ran 2 tests in 11.127s
OK
Process finished with exit code 0


[Mention The Feature]: Add Signup and Login form for view status of course completion.

Is your feature request related to a problem? Please describe.
Yes, the feature request for a Signup and Login form for users to view the status of course completion is related to several common problems faced by online learning platforms and users.
Describe the solution you'd like.
I propose implementing a Signup and Login system that allows users to securely create accounts and access their personalized dashboard. This dashboard will display their course completion status and progress, motivating them to stay engaged with their learning. Additionally, the system will enhance security and provide valuable data for course administrators to improve the platform.
Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots

Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

Thank you for raising this issue.
But we are not looking for this.
So I am Closing this issue
Please understand.


Failed: Update autorest version to prerelease 3.0.0-alpha.20240529.3

Triggered from pull request: https://github.com/Azure/autorest.csharp/pull/4735

API change check
API changes are not detected in this pull request.


[Bug]: react/jsx-no-target-blank doesn't seem to work?

Is there an existing issue for this?

[X] I have searched the existing issues and my issue is unique
[X] My issue appears in the command-line and not only in the text editor

Description Overview

It seems as if no matter how I add the react/jsx-no-target-blank rule to my eslintrc, it doesn't seem to enforce the rule.
I think the docs also show this is a default rule so it should be enforced by default unless disabled?

If you add test to your jsx, the linter is not enforcing rel="noopener" and/or rel="noreferrer"

Expected Behavior

If you add test to your jsx, the linter should enforce rel="noopener" and/or rel="noreferrer"

eslint-plugin-react version
^7.31.11
eslint version
^8.23.1
node version
16.19.1

This plugin is on v7.33.2. Have you tried updating?

Yeah admittedly we're a bit dated on all our dependencies for this app. Let me work on upgrading and get back with you. Thanks for the quick reply!

Upgrading and tweaking the rule config (e.g. adding  warnOnSpreadAttributes: true) appeared to fix the issue.
One other small note is that when I was first testing the rule I added something like this to my jsx test and eslint wasn't detecting an issue. However, when I changed to proper URL (e.g.  test), the linter rule began to work again.

/ is a proper URL - it's the root of the site. Generally you want all URLs for the same site to be root-relative (starts with /)

Sure - well there seems to be a bug with relative path urls then..

Relative links are on your own site, so you don't need noopener/noreferrer - because you can't distrust yourself.

@ljharb seems like this can be closed then?


feat: supported keystore service

this PR implemented KeystoreService, we can find use cases in tests
To merge this PR, we should first

[x] review and merge https://github.com/ckb-js/nexus/pull/44
[x] change this PR target to main

this PR is ready for review,  @zhangyouxin can you review it, it is dependent by fullOwnershipService and ruleBaseService


Verify 'derived_data_path' option

If 'derived_data_path' argument was indicated but the path was inexistent,
we got this message:

Unable to find any .xccoverage file.
Make sure you have enabled 'Gather code coverage' setting on your scheme settings.
Alternatively you can provide the full path to your .xccoverage file.

This patch adds a verification block to 'derived_data_path' option in
order to give faster and more accurate feedback.

Clean, thanks for this @thelvis4 👍


Coverage

a cover metatask for rebar3
used like do so:
$ rebar3 cover eunit --verbose, ct
...

this runs eunit and ct tasks and generates coverage analysis (in ./coverage)
the ct and eunit providers had to be modified slightly in order to accommodate the task

I think this looks good. And adds tests for parsing tasks! :)
@ferd you?

@talentdeficit oh, actually, can you add cover to the list of commands in the README?

done

@talentdeficit I missed the conversation on IRC, were you working on an update to this?

me and @ferd talked about an alternate approach that doesn't require the meta command. i'll try to get that done today or tomorrow and we can discuss which we like better

closing this in favor of #139


PWA not available due to failing to load manifest.json

Just started trying out your app, Its great!
I wanted to "install" your app as desktop app, however the option isn't available. I see that the service worker that is packaged with the Create React App exists sw.js, but the manifest.json is missing.
Looking a bit deeper I see that you do have a manifest.json and the file loads correctly on the landing page. But when using the player it does not load the manifest.json. It may be something with being in the /app directory and/or some url rewrite rules in express 🤔

@Khaoz-Topsy Thanks for reporting this issue. Yeah I see that manifest.json is hosted at /app/manifest.json but my manifest "start_url" is set to /app/library which doesn't make sense since the entire app is hosted at /app.
I think this may be the problem but I'm not entirely sure.

@Khaoz-Topsy Thanks for reporting this issue. Yeah I see that manifest.json is hosted at /app/manifest.json but my manifest "start_url" is set to /app/library which doesn't make sense since the entire app is hosted at /app.
I think this may be the problem but I'm not entirely sure.

c18ab3d6491a77e16b46e611fedd1b60458d927b Allows "installation" from the landing page which will redirect to /app/library. Still having trouble getting the manifest to load correctly from /app but this will do for now

c18ab3d6491a77e16b46e611fedd1b60458d927b Allows "installation" from the landing page which will redirect to /app/library. Still having trouble getting the manifest to load correctly from /app but this will do for now


Feature request: Allow to customize appearance of WSTagView's

currently it's not possible to change for instance corner radius of WSTagView.  One way of customization is to update
open var onDidAddTag: ((WSTagsField, _ tag: WSTag) -> Void)?
func and include WSTagView as additional parameter.

+1. Ability to customize is essential. Would be even better to allow subclass WSTagView and provide class as default for tag.


can't make, edit or delete pages

I can't do anything on the pages part on the admin panel.
Error when I try to edit a page:

Error when I try to create a page:

Hi @protected22
Can you please let us know what version you're running for:

Laravel
Voyager
Voyager  Frontend

"php": "^7.1.3",
"fideloper/proxy": "^4.0",
"laravel/framework": "5.6.*",
"laravel/tinker": "^1.0",
"pvtl/voyager-blog": "^0.2.1",
"pvtl/voyager-frontend": "^0.8.1",
"pvtl/voyager-pages": "^0.2.0",
"tcg/voyager": "^1.1"

Hey @protected22
Would you mind installing fresh with the latest:

"pvtl/voyager-frontend": "^0.8.2",
"pvtl/voyager-blog": "^0.2.3",
"pvtl/voyager-pages": "^0.2.5",

To see if that helps.

By doing Composer update in my cmd?

I've used Composer Update, but looks like its still on this:
"laravel/framework": "5.6.*",
"laravel/tinker": "^1.0",
"pvtl/voyager-blog": "^0.2.1",
"pvtl/voyager-frontend": "^0.8.1",
"pvtl/voyager-pages": "^0.2.0",
"tcg/voyager": "^1.1"

@mcnamee Do you know how I can update to the versions you mentioned? Looks like composer update didn't work

When i try to install the frontend version 0.8.2 I get the following error:
C:\Users\Gebruiker\Desktop\php frmework\Laravel Projects\Voyager-frontend_new>composer require pvtl/voyager-frontend:0.8.2
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for pvtl/voyager-frontend 0.8.2 -> satisfiable by pvtl/voyager-frontend[0.8.2].
- Conclusion: remove laravel/framework v5.5.42
- Conclusion: don't install laravel/framework v5.5.42
- pvtl/voyager-frontend 0.8.2 requires spatie/laravel-sitemap ~5.2.0 -> satisfiable by spatie/laravel-sitemap[5.2.0, 5.2.1].
- spatie/laravel-sitemap 5.2.0 requires spatie/crawler ^4.1.0 -> satisfiable by spatie/crawler[4.1.0, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.1.6, 4.1.7].
- spatie/laravel-sitemap 5.2.1 requires spatie/crawler ^4.1.0 -> satisfiable by spatie/crawler[4.1.0, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.1.6, 4.1.7].
- spatie/crawler 4.1.0 requires tightenco/collect ^5.6 -> satisfiable by illuminate/support[v5.6.0, v5.6.1, v5.6.2, v5.6.3], tightenco/collect[v5.6.0, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.18, v5.6.19, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.27, v5.6.28, v5.6.29, v5.
6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9]
.
- spatie/crawler 4.1.1 requires tightenco/collect ^5.6 -> satisfiable by illuminate/support[v5.6.0, v5.6.1, v5.6.2, v5.6.3], tightenco/collect[v5.6.0, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.18, v5.6.19, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.27, v5.6.28, v5.6.29, v5.
6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9]
.
- spatie/crawler 4.1.2 requires tightenco/collect ^5.6 -> satisfiable by illuminate/support[v5.6.0, v5.6.1, v5.6.2, v5.6.3], tightenco/collect[v5.6.0, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.18, v5.6.19, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.27, v5.6.28, v5.6.29, v5.
6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9]
.
- spatie/crawler 4.1.3 requires tightenco/collect ^5.6 -> satisfiable by illuminate/support[v5.6.0, v5.6.1, v5.6.2, v5.6.3], tightenco/collect[v5.6.0, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.18, v5.6.19, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.27, v5.6.28, v5.6.29, v5.
6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9]
.
- spatie/crawler 4.1.4 requires tightenco/collect ^5.6 -> satisfiable by illuminate/support[v5.6.0, v5.6.1, v5.6.2, v5.6.3], tightenco/collect[v5.6.0, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.18, v5.6.19, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.27, v5.6.28, v5.6.29, v5.
6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9]
.
- spatie/crawler 4.1.5 requires tightenco/collect ^5.6 -> satisfiable by illuminate/support[v5.6.0, v5.6.1, v5.6.2, v5.6.3], tightenco/collect[v5.6.0, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.18, v5.6.19, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.27, v5.6.28, v5.6.29, v5.
6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9]
.
- spatie/crawler 4.1.6 requires tightenco/collect ^5.6 -> satisfiable by illuminate/support[v5.6.0, v5.6.1, v5.6.2, v5.6.3], tightenco/collect[v5.6.0, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.18, v5.6.19, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.27, v5.6.28, v5.6.29, v5.
6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9]
.
- spatie/crawler 4.1.7 requires tightenco/collect ^5.6 -> satisfiable by illuminate/support[v5.6.0, v5.6.1, v5.6.2, v5.6.3], tightenco/collect[v5.6.0, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.18, v5.6.19, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.27, v5.6.28, v5.6.29, v5.
6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9]
.
- don't install illuminate/support v5.6.0|don't install laravel/framework v5.5.42
- don't install illuminate/support v5.6.1|don't install laravel/framework v5.5.42
- don't install illuminate/support v5.6.2|don't install laravel/framework v5.5.42
- don't install illuminate/support v5.6.3|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.0|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.11|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.12|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.13|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.14|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.15|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.16|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.17|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.18|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.19|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.20|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.21|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.22|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.23|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.24|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.25|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.27|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.28|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.29|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.30|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.31|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.32|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.33|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.4|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.5|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.6|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.7|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.8|don't install laravel/framework v5.5.42
- don't install tightenco/collect v5.6.9|don't install laravel/framework v5.5.42
- Installation request for laravel/framework (locked at v5.5.42, required as 5.5.*) -> satisfiable by laravel/framework[v5.5.42].
Installation failed, reverting ./composer.json to its original content.
C:\Users\Gebruiker\Desktop\php frmework\Laravel Projects\Voyager-frontend_new>

Ive made a fresh installation with the latest versions.
After starting the webserver using php artisan serve i get an error:
Argument 2 passed to Symfony\Component\HttpFoundation\Request::setTrustedProxies() must be of the type integer, array given, called in C:\Users\Gebruiker\Desktop\php frmework\Laravel Projects\Voyager-frontend_new\vendor\fideloper\proxy\src\TrustProxies.php on line 54

@protected22 Your fideloper/proxy package appears to be out of date. Laravel 5.6 requires the $headers property in App\Http\Middleware\TrustProxies to be set to a bit property. If you're using Laravel 5.6, you need to make sure you're using "fideloper/proxy": "^4.0" in your composer.json.

Okay i've done that, But now I get some new errors and things:
the first one is this: A script code on every page on the footer.

Other thing is, I can make pages and posts. but I get this error every time: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry

page error: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'meta_keywords' in 'field list' (SQL: insert into pages (title, excerpt, body, slug, meta_description, meta_keywords, status, image, author_id, updated_at, created_at) values (test page, exerp text, body text, test-page, m,eta text, keyword, ACTIVE, pages\August2018\K9vp6jy0BxvaVXJwwX8X.jpg, 1, 2018-08-17 06:25:16, 2018-08-17 06:25:16))

Also when I try to change the site logo in the voyager dashboard settings I get this error:
Declaration of TeamTNT\Scout\Engines\TNTSearchEngine::map(Laravel\Scout\Builder $builder, $results, $model) must be compatible with Laravel\Scout\Engines\Engine::map($results, $model)


contaminated test set

I have checked the  https://github.com/wiio12/LEGO-Prover/tree/master/data/full_data and compare with the origin one https://github.com/openai/miniF2F/tree/main/isabelle/ and find the test split imo_2007_p6 is replaced with numbertheory_sqmod3in01d in valid set, leading to total 487 problems.
The accuracy reported in your paper might be wrong?

The miniF2F dataset LEGO uses can be found in this repository: https://github.com/albertqjiang/miniF2F. This repository is a fork from the original OpenAI miniF2F dataset. In this fork, there are approximately 10 to 15 problems that differ (the exact number escapes my memory), and I'm unsure of the reasons behind these changes (I should ask Albert for clarification). We've been utilizing this fork to conduct experiments with LEGO-Prover since its early stages, and only recently discovered discrepancies between some problems in this fork and the original OpenAI miniF2F dataset. However, LEGO-Prover fails to prove most of these differing problems, suggesting that reverting them to the original dataset may not significantly impact performance.


chore(Data/Finset): split lattice file

The file Data/Finset/Lattice contained two disjoint developments, with disjoint imports, forming one natural cut location. We also split max and min into a separate file.

[x] depends on: #17048

bot fix style

Thanks :tada:
bors merge

bors merge
bors d+


Build libzmq from source, generate SwiftZMQ.framework for macosx and iphoneos platforms.

Current coverage is 6.52%

Merging #2 into master will decrease coverage by -0.10% as of 3f52759

@@            master     #2   diff @@
=====================================
  Files            7      7
  Stmts          891    674   -217
  Branches         0      0
  Methods          0      0
=====================================
- Hit             59     44    -15
  Partial          0      0
+ Missed         832    630   -202

Review entire Coverage Diff as of 3f52759

Powered by Codecov. Updated on successful CI builds.

This is awesome man! Thanks.

So brew is not required of OSX anymore, right?

brew is still required for autotools and the building toolchain, but not for running an app with swiftzmq

I mean this:
brew install zeromq --with-libsodium --HEAD
I should remove from the README, right? The Xcode build phase script builds the lib, doens't it?

yes, though the compiled libzmq does not include libsodium

is it possible to include it?


[e2e]: nodejs push branch1 default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/branch1
Run: https://github.com/slsa-framework/example-package/actions/runs/7765028386
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.branch1.default.slsa3.yml
Trigger: push
Branch: branch1
Date: Sat Feb  3 06:14:02 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/branch1
Run: https://github.com/slsa-framework/example-package/actions/runs/7772090274
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.branch1.default.slsa3.yml
Trigger: push
Branch: branch1
Date: Sun Feb  4 06:10:50 UTC 2024
Tests are passing now. Closing this issue.


Move install instructions to site

There is a bunch of duplication between the READMEs and the website. We should move the install instructions from the README to the website, and remove the duplicated documentation.

We should add docker instructions to this installation too.

Closed with #284.

Closed with #284.


GUI documentation link updates

[ ] Update launch documentation screen
[ ] Update link to doxygen (api_docs42)
[ ] Any updates to tutorials 1, 2, 3?

Info on this page: https://simtk-confluence.stanford.edu/display/DevPlans/Steps+for+New+Release
(We might also move this info to Github.)

@aymanhab Here is a link placeholder for the Welcome to OpenSim! documentation page that shows up on GUI launch (What's new):
https://simtk-confluence.stanford.edu/pages/viewpage.action?pageId=48988768
I think the other links are OK as is.
Do we distribute the tutorials with tutorials 1, 2, 3?
Please note we also need to update the link to doxygen (it doesn't exist yet, but you could put in the link).

Thanks @jenhicks I made a PR to update. We distribute the tutorial pages
but these have not changed AFAIK.
-Ayman
On Mon, Dec 21, 2020 at 12:37 PM Jen Hicks<EMAIL_ADDRESS>wrote:

@aymanhab https://github.com/aymanhab Here is a link placeholder for
the Welcome to OpenSim! documentation page that shows up on GUI launch
(What's new):
https://simtk-confluence.stanford.edu/pages/viewpage.action?pageId=48988768
I think the other links are OK as is.
Do we distribute the tutorials with tutorials 1, 2, 3?
Please note we also need to update the link to doxygen (it doesn't exist
yet, but you could put in the link).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/opensim-org/opensim-gui/issues/1241#issuecomment-749184614,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6JY4CXIWA3LZJKNHZSO7DSV6WYHANCNFSM4U3LAZ2A
.


Zowe.org Contribute Page Refresh

The contribute page (https://zowe.org/contribute/) could be revamped in several ways:

[x] Add links and descriptions on the slack channels
[ ] Add graphic for squads and brief description of how the interact?
[ ] Add link to squad Waffle boards/backlog
[ ] Add link to groups.io for list of list of scheduled squad meetings

Review issue #10

Need to note that the only way to get calendar invites to community meetings is to be part of the zowe-dev mailing list.

This issue was moved to zowe/docs-site#76


Document dart:io/CompressionOptions in changelog

Along with methods that use it...

@sgjesse Ping?


Added my code for Decision Tree algorithm

I used this code in a Kaggle competition. want to participate in hacktober so I am submitting a pull request after reading your readme that you had a decision tree on the to-do list.

@SanaaShah I'm sorry but I'm looking for from scratch algorithm and not using the built-in functions


support access local html file by file:///path/simple.html

use file:/// protocal to access local file , load assets like http protocal

I would revive this. Perhaps hosting the contents of the source to a web page would get around this without redesign? What limitations would that face, what other approaches do you recommend?

Hello @datocrats-org 👋
Do you have an example of a use case in mind?

It should be fixed thanks to the following property:
--chromium-allow-file-access-from-files bool    Allow file:// URIs to read other file:// URIs


[Bug]: Targetters can target Spectators

Is there an existing issue for this?

[X] I have searched the existing issues

Have you tried to reproduce this without OP?

[X] I have tested without OP

Current Behavior
No response
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- Server Software:
- ProSkillAPI Version:
- ProMCCore Version:
- Plugins:

latest.log
latest.log

# paste log here...

Anything else?
No response

I assume this refers to players in Spectator mode and not just invisible players. For sake of plugins/skills I think invisible players should still be targeted. Does it also target players on Creative mode?

Yes I mean spectator gamemode and ot does also target creative people. Which I guess should also be removed I see no point where you would need a skill to work on you in creative unless its a self target which should work regardless of gamemode.


[MWPW-159265] Callout text in RTL not properly aligned

For RTL, make callout texts right aligned
Resolves: MWPW-159265
Test URLs:

Before: https://main--milo--adobecom.hlx.page/ae_ar/drafts/mili/kitchen-sink/merch-card
After: https://MWPW-159265--milo--rohitsahu.hlx.page/ae_ar/drafts/mili/kitchen-sink/merch-card

Mobile icon is also not horizontally aligned with the text, regardless of RTL/LTR:

@rohitsahu please take care of PR feedback from @overmyheadandbody in a subsequent PR.

@rohitsahu please take care of PR feedback from @overmyheadandbody in a subsequent PR.

Fixed in https://github.com/adobecom/milo/pull/2982
cc: @overmyheadandbody


Figure out why 9453acf1 regressed perf

That patch, which only touches the compiler, regressed the method_call benchmark by 20%:
binary_trees - wren            ..........  3531  0.28s  103.76% relative to baseline
delta_blue - wren              ..........  8126  0.12s  101.28% relative to baseline
fib - wren                     ..........  3262  0.31s   98.84% relative to baseline
for - wren                     ..........  8627  0.12s  100.48% relative to baseline
method_call - wren             ..........  5599  0.18s   81.39% relative to baseline

That benchmark doesn't even use subscript operators. WTF?

...and the unrelated change to fix WREN_PIN magically fixed this. I'll chalk this up to caching/alignment. :astonished:

Oh, well... :see_no_evil:


fetchGroups with callGroups

fetchGroups do not seem to work for methods. Every peer can fetch all methods even without logging in.

can you provide an example?
The tests pass. Here a Method is added:
https://github.com/lipp/node-jet/blob/master/test/authentication-tests.js#L121
and here the method is NOT visible:
https://github.com/lipp/node-jet/blob/master/test/authentication-tests.js#L155
So everything seems to be ok/

@markert ping?!

My mistake. I defined a setGroup instead of a callGroup. Since a path can describe either a method or a state, I do not see, why there must be a distinction between setGroups and callGroups. I guess it would be sufficient to define two types of groups. Those, who can fetch and those, who can call/set.

yes. from implementation point of view this is even easier.
i just could not find a suitable name xxxGroup. suggestions?

Maybe:
fetchGroup -> readGroup
callGroup/setGroup -> writeGroup

i don't like this too much because the relationship between the matching call/message name ('set', 'call', 'fetch') get lost.


Added config to lazy README

Not including config = function(_, opts) and require("emoji").setup(opts) created an either/or situation with cmp_integration and telescope. If the config is provided with the default* config = function() + telescope registration, it wouldn't run the plugin's internal setup function which means the cmp source wouldn't be registered.
* Idk if it's really the default, this is the first time I've seen anything other than
This is the config I originally tried:
{
    "allaman/emoji.nvim",
    ft = "markdown",
    dependencies = {
        "hrsh7th/nvim-cmp",
        "nvim-telescope/telescope.nvim",
    },
    opts = {
        enable_cmp_integration = true,
    },
    config = function()
        require("telescope").load_extension("emoji")
        vim.keymap.set("n", "<leader>fe", function()
            vim.cmd(":Telescope emoji")
        end)
    end,
},

Sorry for the minuscule pull request and thank you for having your nvim config on github cause this was really bugging me

Hello,
thank you for your PR. I think my README was not clear enough
Lazy calls the setup function with the opts automatically when not specifying the config option so ergo this config is "valid" and enables the cmp integration.
return {
  "allaman/emoji.nvim",
  ft = "markdown",
  dependencies = "hrsh7th/nvim-cmp",
  opts = {
    enable_cmp_integration = config.enable_cmp_integration,
  },
}

However, when specifying the config option to do further customizations (like telescope integration or keybindings) one is responsible to call setup manually as you correctly figured out.
  config = function(_, opts)
    require("emoji").setup(opts)
    require("telescope").load_extension("emoji")
  end,

I think this is the intended behavior of Lazy and a common plugin pattern, but as I said, the README is not clear about this so your PR is appreciated 👍


DALL-E request mech tool

Proposed changes
Adding DALL-E as a mech tool. To be utilized as a text to image generation tool.
Fixes
N/A
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[x] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING doc
[x] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works

Further comments
There is currently OpenAI GPT support but no DALL-E support

Added unit test


Guides RFC - #7 WIP

RFC background
We have published the 1st version of JSS Guides & Recommended Practices. This content will ultimately be merged into the JSS Documentation site, and we'd love for the community to be a part of this milestone. We welcome your feedback, questions, change suggestions, and additional content.
Docs vs Guides
During this project we realized that although it seems beneficial to separate docs and guides, the current docs already contain some guide-style content. So we're not sure if this is a good idea. What do you think? Do you like the separation? Would you be ok with some pages from docs moving to guides, thereby breaking some existing URLs?
If you like the idea of keeping them separate, how do you differentiate docs and guides in your mind? Help us come up with a clear definition that will help us organize the content better for you.
Category - Work in Progress... and beyond
We’ve create GitHub issues for the 7 topic categories to facilitate group discussion - this issue is for discussing the Work in Progress category. This is a special issue because this is where we want to hear about additional topics that you think should be in guides. What did we miss? What needs more content? (Ordering by priority would be appreciated)
Topics in this category:

Deployment Topologies
Migration Guide

How to contribute

Post your comments here, or
Use this link to leave inline comments in the markdown files, or
Use the Edit this on GitHub link at the bottom of each guide page to submit edits for specific pages, or
Submit pull requests to the guides branch

:arrow_left: Go to previous category

tant to you) - Federated Authentication with JSS

I would love to see an example (preferably including a reference example using Sitecore Identity) that explains how Federated Authentication and JSS in headless mode works.
The current documentation (https://jss.sitecore.com/docs/techniques/authentication/federated-auth) only describes integrated mode and almost suggests that this mode is preferred when using Federated Authentication.

Not completely sure if this belongs in a migration guide: a step by step guide for a couple of standard scenarios more tailord to React/Angular/Vue developers would be nice, for example:

A guid to Use Sitecore JSS with your existing app to get your labels and content managed (item access via GraphQL)

Add placeholders & content to your existing NextJS  or NuxtJS project.


Downgrade levels of too often logs

Motivation

Related: #2633

Some logs currently happen too often and fill the whole screen. Example:

Here, the whole screen was filled with a repetitive log within ~100ms. This makes logs storage and lookup more complex.
This PR downgrades levels of such logs.
Changes

Downgrade levels of too often logs

Test Plan

DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[ ] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

bors merge

bors merge


Move common member into base and modify launch function

I made a few changes

Move common members into the launch_param_base_t class (shared_memory_bytes).
Remove context as a member and instead use it as an argument of the launch function. This makes sense because we might want to use multiple contexts with the same launch box, and rather that re-instantiating a new launch box for each context, we can use the same object.
Changed the launch function to use a tuple of args rather than a variadic pack of args. This design choice is based around my expectation that most kernels will have a lot of arguments, and it will look cleaner if they are wrapped into a tuple. If this wasn't for launching cuda kernels I would have been able to use std::apply in C++17, but I had to reimplement it to be able to use the chevrons <<<>>>.

The only issue I have still that I'd like to discuss here is how to efficiently declare the launch functions. Currently across the two types of launch boxes the functions are exact copies from one another. The only difference between the classes is that the functions reference member types that are declared in those classes, so they cannot easily be moved into the shared parent class.

3. Changed the launch function to use a tuple of args rather than a variadic pack of args. This design choice is based around my expectation that most kernels will have a lot of arguments, and it will look cleaner if they are wrapped into a tuple. If this wasn't for launching cuda kernels I would have been able to use std::apply in C++17, but I had to reimplement it to be able to use the chevrons <<<>>>.

This is cool, I like std::apply, I am just wondering what is the benefit of the tuple versus direct forwarding the arguments? Isn't it less code if I just forward it?

Changed the launch function to use a tuple of args rather than a variadic pack of args. This design choice is based around my expectation that most kernels will have a lot of arguments, and it will look cleaner if they are wrapped into a tuple. If this wasn't for launching cuda kernels I would have been able to use std::apply in C++17, but I had to reimplement it to be able to use the chevrons <<<>>>.

This is cool, I like std::apply, I am just wondering what is the benefit of the tuple versus direct forwarding the arguments? Isn't it less code if I just forward it?

Yes it is a bit less code from the user perspective when you just forward it directly, but since I was adding the context argument I thought it would make it clearer which args are for the actual kernel in the case where there are a bunch of them.

Changed the launch function to use a tuple of args rather than a variadic pack of args. This design choice is based around my expectation that most kernels will have a lot of arguments, and it will look cleaner if they are wrapped into a tuple. If this wasn't for launching cuda kernels I would have been able to use std::apply in C++17, but I had to reimplement it to be able to use the chevrons <<<>>>.

This is cool, I like std::apply, I am just wondering what is the benefit of the tuple versus direct forwarding the arguments? Isn't it less code if I just forward it?

Yes it is a bit less code from the user perspective when you just forward it directly, but since I was adding the context argument I thought it would make it clearer which args are for the actual kernel in the case where there are a bunch of them.

Ok, I'll try it out.


Options page text

Draft text for options page emailed through to Richard.

closing issue as was done in last sprint


Feature: Endpoint to load results from iRacing API

Description
Load the results for a single session from the iracing API given the subsession id
Tasks

[x] #120
[x] Add internal query to iracing API to get the results
[x] Add endpoint that accepts a event-id and a iracing-subsession-id to perform and automatic result upload to the specified event

has been resolved with #122 and #123


Issues with geometry of an IFC

Describe the bug 📝
Hi I finished the advanced course of IFC.js using react. I managed to load differents IFC without errors except this one. There is parts of the IFC that are missing from the model. If I use the web-ifc demo the parts are showing perfectly. I'm using the latest openbim-components package showed in the course (0.0.51) that has web-ifc version 0.0.36.

Reproduction ▶
No response
Steps to reproduce 🔢
No response
System Info 💻
--

Used Package Manager 📦
npm
Error Trace/Logs 📃
--
Validations ✅

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a IFC.js components issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
[X] Check that this is a concrete bug. For Q&A join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hey @FirebirdCS any chance I can get access to that model to take a look? Thanks in advance!

Hi @FirebirdCS! Are you experiencing the same problems if you update to<EMAIL_ADDRESS>

Sorry for not replying but in the new app viewer it shows perfectly the IFC. Thank you!


Clean up non-existing guild commands when using guilds property

Feature
When using command guilds property, then changing name after command has been registered doesn't remove the old one.
Ideal solution or implementation
Maybe remove all guild commands and re-register all current one?
Alternative solutions or implementations
No response
Other context
No response

my bad it was working as intended


Update sbt-jmh to 0.4.0

Updates pl.project13.scala:sbt-jmh from 0.3.7 to 0.4.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "pl.project13.scala", artifactId = "sbt-jmh" } ]

labels: sbt-plugin-update, semver-minor

Codecov Report

Merging #1527 into master will decrease coverage by 0.09%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1527      +/-   ##
==========================================
- Coverage   85.58%   85.49%   -0.10%
==========================================
  Files          58       58
  Lines        2206     2206
  Branches      107      107
==========================================
- Hits         1888     1886       -2
- Misses        318      320       +2

Impacted Files
Coverage Δ

...rc/main/scala/io/circe/shapes/SizedInstances.scala
78.57% <0.00%> (-14.29%)
:arrow_down:

.../core/shared/src/main/scala/io/circe/Decoder.scala
85.05% <0.00%> (-0.55%)
:arrow_down:

...les/core/shared/src/main/scala/io/circe/Json.scala
80.44% <0.00%> (ø)

...re/shared/src/main/scala/io/circe/JsonNumber.scala
93.97% <0.00%> (+1.20%)
:arrow_up:

...d/src/main/scala/io/circe/cursor/ArrayCursor.scala
69.23% <0.00%> (+7.69%)
:arrow_up:

Continue to review full report at Codecov.

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


Deletion from tagged_objects fails with multiple tags

Bug description
If there are multiple tags for a dataset and the dataset is deleted, the 'after_delete' action fails because it attempts to delete more than 1 row.

Screenshots/recordings
No response
Superset version
4.0.2
Python version
3.11
Node version
16
Browser
Not applicable
Additional context
No response
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Is there a way to still use the DeleteCommands but have this work? If not, I would need to delete all tag rows before I can delete the chart/dataset, right?

@eschutho @yousoph do we have anyone actively looking at bugs around tags still?

There is a solution to this problem :https://github.com/apache/superset/pull/29117


Can't enable gitlab module

Hello,
Whenever I try to enable the gitlab module, it fails to install with the error : The unique option services.postgresql.package' is defined multiple times, in /nix/store/igd20r92j317ks59qqfr69bkb5sbralf-nixos-16.03pre70421.e57024f/nixos/nixpkgs/nixos/modules/services/misc/gitlab.nix' and /nix/store/igd20r92j317ks59qqfr69bkb5sbralf-nixos-16.03pre70421.e57024f/nixos/nixpkgs/nixos/modules/services/databases/postgresql.nix'.`
The configuration.nix and full trace can be found at https://gist.github.com/roblabla/0acfd800aa1114a784e0 .

Will you submit a PR for that commit?

That commit alone wasn't enough to fix all the issues with gitlab (therubyracer (a gem) failed to compile, leading to gitlab being uninstallable). I ended up updating gitlab to 8.0.5. That PR contains the changes I made.

Gitlab does not build on 15.09 and the service failed to start when i switched to the nixos-unstable-small channel.
Receiving objects:   0% (1/54229)
Receiving objects:   1% (543/54229)
Receiving objects:   2% (1085/54229)
Receiving objects:   3% (1627/54229)
Receiving objects:   4% (2170/54229)
Receiving objects:   5% (2712/54229)
Receiving objects:   6% (3254/54229)
Receiving objects:   7% (3797/54229)
Receiving objects:   8% (4339/54229)
Receiving objects:   9% (4881/54229)
Receiving objects:  10% (5423/54229)
Receiving objects:  11% (5966/54229)
Receiving objects:  12% (6508/54229)
Receiving objects:  13% (7050/54229)
Receiving objects:  14% (7593/54229)
Receiving objects:  15% (8135/54229)
Receiving objects:  16% (8677/54229)
Receiving objects:  17% (9219/54229)
Receiving objects:  18% (9762/54229)
Receiving objects:  19% (10304/54229)
Receiving objects:  20% (10846/54229)
Receiving objects:  21% (11389/54229)
Receiving objects:  22% (11931/54229)
Receiving objects:  23% (12473/54229)
Receiving objects:  24% (13015/54229)
Receiving objects:  25% (13558/54229)
Receiving objects:  26% (14100/54229)
Receiving objects:  27% (14642/54229)
Receiving objects:  28% (15185/54229)
Receiving objects:  29% (15727/54229)
Receiving objects:  30% (16269/54229)
Receiving objects:  31% (16811/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  32% (17354/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  33% (17896/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  34% (18438/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  35% (18981/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  36% (19523/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  37% (20065/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  38% (20608/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  39% (21150/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  40% (21692/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  41% (22234/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  42% (22777/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  43% (23319/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  44% (23861/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  45% (24404/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  46% (24946/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  47% (25488/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  48% (26030/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  49% (26573/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  50% (27115/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  51% (27657/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  52% (28200/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  53% (28742/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  54% (29284/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  55% (29826/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  56% (30369/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  57% (30911/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  57% (31445/54229), 5.44 MiB | 10.87 MiB/s
Receiving objects:  58% (31453/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  59% (31996/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  60% (32538/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  61% (33080/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  62% (33622/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  63% (34165/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  64% (34707/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  65% (35249/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  66% (35792/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  67% (36334/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  68% (36876/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  69% (37419/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  70% (37961/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  71% (38503/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  72% (39045/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  73% (39588/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  74% (40130/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  75% (40672/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  76% (41215/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  77% (41757/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  78% (42299/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  79% (42841/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  80% (43384/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  81% (43926/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  82% (44468/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  83% (45011/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  84% (45553/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  85% (46095/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  86% (46637/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  87% (47180/54229), 11.32 MiB | 11.32 MiB/s
Receiving objects:  88% (47722/54229), 17.16 MiB | 11.44 MiB/s
Receiving objects:  89% (48264/54229), 17.16 MiB | 11.44 MiB/s
Receiving objects:  90% (48807/54229), 17.16 MiB | 11.44 MiB/s
Receiving objects:  91% (49349/54229), 17.16 MiB | 11.44 MiB/s
Receiving objects:  92% (49891/54229), 17.16 MiB | 11.44 MiB/s
Receiving objects:  93% (50433/54229), 17.16 MiB | 11.44 MiB/s
Receiving objects:  94% (50976/54229), 17.16 MiB | 11.44 MiB/s
Receiving objects:  95% (51518/54229), 17.16 MiB | 11.44 MiB/s
Receiving objects:  96% (52060/54229), 17.16 MiB | 11.44 MiB/s
Receiving objects:  97% (52603/54229), 17.16 MiB | 11.44 MiB/s
Receiving objects:  98% (53145/54229), 17.16 MiB | 11.44 MiB/s
Receiving objects:  99% (53687/54229), 17.16 MiB | 11.44 MiB/s
remote: Total 54229 (delta 89), reused 183 (delta 4), pack-reused 53879
Receiving objects: 100% (54229/54229), 17.16 MiB | 11.44 MiB/s
Receiving objects: 100% (54229/54229), 18.84 MiB | 11.44 MiB/s, done.

From https://github.com/bundler/bundler
 * [new branch]      0-8-stable -> origin/0-8-stable
 * [new branch]      0-9-stable -> origin/0-9-stable
 * [new branch]      1-0-stable -> origin/1-0-stable
 * [new branch]      1-1-stable -> origin/1-1-stable
 * [new branch]      1-10-stable -> origin/1-10-stable
 * [new branch]      1-11-stable -> origin/1-11-stable
 * [new branch]      1-12-stable -> origin/1-12-stable
 * [new branch]      1-2-stable -> origin/1-2-stable
 * [new branch]      1-3-stable -> origin/1-3-stable
 * [new branch]      1-5-stable -> origin/1-5-stable
 * [new branch]      1-6-stable -> origin/1-6-stable
 * [new branch]      1-7-stable -> origin/1-7-stable
 * [new branch]      1-8-stable -> origin/1-8-stable
 * [new branch]      1-9-stable -> origin/1-9-stable
 * [new branch]      1-99-dev   -> origin/1-99-dev
 * [new branch]      171        -> origin/171
 * [new branch]      2-0-dev    -> origin/2-0-dev
 * [new branch]      2-0-dev-archived -> origin/2-0-dev-archived
 * [new branch]      2813-fix-self-dependency-bug -> origin/2813-fix-self-dependency-bug
 * [new branch]      3982-clean-rubylib -> origin/3982-clean-rubylib
 * [new branch]      4064       -> origin/4064
 * [new branch]      align-hash -> origin/align-hash
 * [new branch]      auto       -> origin/auto
 * [new branch]      autobundle -> origin/autobundle
 * [new branch]      checksum   -> origin/checksum
 * [new branch]      dont_run_git_commands_during_runtime -> origin/dont_run_git_commands_during_runtime
 * [new branch]      execless   -> origin/execless
 * [new branch]      fetchers_fetchers_everywhere -> origin/fetchers_fetchers_everywhere
 * [new branch]      fix-backtracking-from-child -> origin/fix-backtracking-from-child
 * [new branch]      fix-bug-with-bundle-cache-erroring -> origin/fix-bug-with-bundle-cache-erroring
 * [new branch]      fix-path-caching-3900 -> origin/fix-path-caching-3900
 * [new branch]      fix-thread-safety-parallel-install -> origin/fix-thread-safety-parallel-install
 * [new branch]      fix-worker-cleanup-error -> origin/fix-worker-cleanup-error
 * [new branch]      fix-worker-index-jruby -> origin/fix-worker-index-jruby
 * [new branch]      fix_missing_gem_dir -> origin/fix_missing_gem_dir
 * [new branch]      further_disablement -> origin/further_disablement
 * [new branch]      gem_tasks  -> origin/gem_tasks
 * [new branch]      gemfile_hashing -> origin/gemfile_hashing
 * [new branch]      gh-pages   -> origin/gh-pages
 * [new branch]      issue-3671 -> origin/issue-3671
 * [new branch]      make-paralle-fetch-jruby -> origin/make-paralle-fetch-jruby
 * [new branch]      master     -> origin/master
 * [new branch]      molinillo  -> origin/molinillo
 * [new branch]      new-index  -> origin/new-index
 * [new branch]      old-gem-version -> origin/old-gem-version
 * [new branch]      parallel_threads -> origin/parallel_threads
 * [new branch]      platforms  -> origin/platforms
 * [new branch]      refactor-resolver -> origin/refactor-resolver
 * [new branch]      removing_the_spec_gil -> origin/removing_the_spec_gil
 * [new branch]      reraise-orig-exception -> origin/reraise-orig-exception
 * [new branch]      resolve-running-ruby -> origin/resolve-running-ruby
 * [new branch]      retry_network -> origin/retry_network
 * [new branch]      rgb-manpage-additions -> origin/rgb-manpage-additions
 * [new branch]      rubygems22_exts -> origin/rubygems22_exts
 * [new branch]      seg-gemspec-ruby -> origin/seg-gemspec-ruby
 * [new branch]      segseparate-lockfile-sources -> origin/segseparate-lockfile-sources
 * [new branch]      sources    -> origin/sources
 * [new branch]      spec-for-3896 -> origin/spec-for-3896
 * [new branch]      test_default_gems -> origin/test_default_gems
 * [new branch]      travis-docker -> origin/travis-docker
 * [new branch]      travis-new-setup -> origin/travis-new-setup
 * [new branch]      travis-trusty-env -> origin/travis-trusty-env
 * [new branch]      unsupported_sources -> origin/unsupported_sources
 * [new branch]      user_agent -> origin/user_agent
 * [new branch]      user_agent2 -> origin/user_agent2
 * [new tag]         v1.1.5     -> v1.1.5
 * [new tag]         v1.11.2    -> v1.11.2
 * [new tag]         v1.12.0.pre.2 -> v1.12.0.pre.2
 * [new tag]         v1.2.5     -> v1.2.5
 * [new tag]         v1.6.9     -> v1.6.9
 * [new tag]         v1.9.10    -> v1.9.10
 * [new tag]         0.3.1      -> 0.3.1
 * [new tag]         0.4.0      -> 0.4.0
 * [new tag]         0.4.1      -> 0.4.1
 * [new tag]         0.5.0      -> 0.5.0
 * [new tag]         0.6.0      -> 0.6.0
 * [new tag]         0.7.0      -> 0.7.0
 * [new tag]         0.7.2      -> 0.7.2
 * [new tag]         0.8.0      -> 0.8.0
 * [new tag]         0.8.2      -> 0.8.2
 * [new tag]         0.8.5      -> 0.8.5
 * [new tag]         0.9.10     -> 0.9.10
 * [new tag]         0.9.11     -> 0.9.11
 * [new tag]         0.9.12     -> 0.9.12
 * [new tag]         0.9.13     -> 0.9.13
 * [new tag]         0.9.14     -> 0.9.14
 * [new tag]         0.9.15     -> 0.9.15
 * [new tag]         0.9.16     -> 0.9.16
 * [new tag]         0.9.17     -> 0.9.17
 * [new tag]         0.9.18     -> 0.9.18
 * [new tag]         0.9.19     -> 0.9.19
 * [new tag]         0.9.20     -> 0.9.20
 * [new tag]         0.9.21     -> 0.9.21
 * [new tag]         0.9.22     -> 0.9.22
 * [new tag]         0.9.23     -> 0.9.23
 * [new tag]         0.9.24     -> 0.9.24
 * [new tag]         0.9.25     -> 0.9.25
 * [new tag]         0.9.26     -> 0.9.26
 * [new tag]         0.9.3      -> 0.9.3
 * [new tag]         0.9.4      -> 0.9.4
 * [new tag]         0.9.5      -> 0.9.5
 * [new tag]         0.9.6      -> 0.9.6
 * [new tag]         0.9.7      -> 0.9.7
 * [new tag]         0.9.8      -> 0.9.8
 * [new tag]         0.9.9      -> 0.9.9
 * [new tag]         1.0.0      -> 1.0.0
 * [new tag]         1.0.0.beta.1 -> 1.0.0.beta.1
 * [new tag]         1.0.0.beta.10 -> 1.0.0.beta.10
 * [new tag]         1.0.0.beta.2 -> 1.0.0.beta.2
 * [new tag]         1.0.0.beta.3 -> 1.0.0.beta.3
 * [new tag]         1.0.0.beta.4 -> 1.0.0.beta.4
 * [new tag]         1.0.0.beta.5 -> 1.0.0.beta.5
 * [new tag]         1.0.0.beta.6 -> 1.0.0.beta.6
 * [new tag]         1.0.0.beta.7 -> 1.0.0.beta.7
 * [new tag]         1.0.0.beta.8 -> 1.0.0.beta.8
 * [new tag]         1.0.0.beta.9 -> 1.0.0.beta.9
 * [new tag]         1.0.0.rc.1 -> 1.0.0.rc.1
 * [new tag]         1.0.0.rc.2 -> 1.0.0.rc.2
 * [new tag]         1.0.0.rc.3 -> 1.0.0.rc.3
 * [new tag]         1.0.0.rc.4 -> 1.0.0.rc.4
 * [new tag]         1.0.0.rc.5 -> 1.0.0.rc.5
 * [new tag]         1.0.0.rc.6 -> 1.0.0.rc.6
 * [new tag]         v0.9.0     -> v0.9.0
 * [new tag]         v0.9.0.pre3 -> v0.9.0.pre3
 * [new tag]         v0.9.0.pre4 -> v0.9.0.pre4
 * [new tag]         v0.9.0.pre5 -> v0.9.0.pre5
 * [new tag]         v1.0.0     -> v1.0.0
 * [new tag]         v1.0.1     -> v1.0.1
 * [new tag]         v1.0.10    -> v1.0.10
 * [new tag]         v1.0.11    -> v1.0.11
 * [new tag]         v1.0.12    -> v1.0.12
 * [new tag]         v1.0.13    -> v1.0.13
 * [new tag]         v1.0.14    -> v1.0.14
 * [new tag]         v1.0.15    -> v1.0.15
 * [new tag]         v1.0.16    -> v1.0.16
 * [new tag]         v1.0.17    -> v1.0.17
 * [new tag]         v1.0.18    -> v1.0.18
 * [new tag]         v1.0.19.rc -> v1.0.19.rc
 * [new tag]         v1.0.2     -> v1.0.2
 * [new tag]         v1.0.20    -> v1.0.20
 * [new tag]         v1.0.20.rc -> v1.0.20.rc
 * [new tag]         v1.0.21    -> v1.0.21
 * [new tag]         v1.0.21.rc -> v1.0.21.rc
 * [new tag]         v1.0.22    -> v1.0.22
 * [new tag]         v1.0.3     -> v1.0.3
 * [new tag]         v1.0.4     -> v1.0.4
 * [new tag]         v1.0.5     -> v1.0.5
 * [new tag]         v1.0.6     -> v1.0.6
 * [new tag]         v1.0.7     -> v1.0.7
 * [new tag]         v1.0.8     -> v1.0.8
 * [new tag]         v1.0.9     -> v1.0.9
 * [new tag]         v1.1.0     -> v1.1.0
 * [new tag]         v1.1.1     -> v1.1.1
 * [new tag]         v1.1.2     -> v1.1.2
 * [new tag]         v1.1.3     -> v1.1.3
 * [new tag]         v1.1.pre   -> v1.1.pre
 * [new tag]         v1.1.pre.1 -> v1.1.pre.1
 * [new tag]         v1.1.pre.10 -> v1.1.pre.10
 * [new tag]         v1.1.pre.2 -> v1.1.pre.2
 * [new tag]         v1.1.pre.3 -> v1.1.pre.3
 * [new tag]         v1.1.pre.4 -> v1.1.pre.4
 * [new tag]         v1.1.pre.5 -> v1.1.pre.5
 * [new tag]         v1.1.pre.6 -> v1.1.pre.6
 * [new tag]         v1.1.pre.7 -> v1.1.pre.7
 * [new tag]         v1.1.pre.8 -> v1.1.pre.8
 * [new tag]         v1.1.pre.9 -> v1.1.pre.9
 * [new tag]         v1.1.rc    -> v1.1.rc
 * [new tag]         v1.1.rc.2  -> v1.1.rc.2
 * [new tag]         v1.1.rc.3  -> v1.1.rc.3
 * [new tag]         v1.1.rc.4  -> v1.1.rc.4
 * [new tag]         v1.1.rc.5  -> v1.1.rc.5
 * [new tag]         v1.1.rc.6  -> v1.1.rc.6
 * [new tag]         v1.1.rc.7  -> v1.1.rc.7
 * [new tag]         v1.1.rc.8  -> v1.1.rc.8
 * [new tag]         v1.10.0    -> v1.10.0
 * [new tag]         v1.10.0.pre -> v1.10.0.pre
 * [new tag]         v1.10.0.pre.1 -> v1.10.0.pre.1
 * [new tag]         v1.10.0.pre.2 -> v1.10.0.pre.2
 * [new tag]         v1.10.0.rc -> v1.10.0.rc
 * [new tag]         v1.10.1    -> v1.10.1
 * [new tag]         v1.10.2    -> v1.10.2
 * [new tag]         v1.10.3    -> v1.10.3
 * [new tag]         v1.10.4    -> v1.10.4
 * [new tag]         v1.10.5    -> v1.10.5
 * [new tag]         v1.10.6    -> v1.10.6
 * [new tag]         v1.11.0    -> v1.11.0
 * [new tag]         v1.11.0.pre.1 -> v1.11.0.pre.1
 * [new tag]         v1.11.0.pre.2 -> v1.11.0.pre.2
 * [new tag]         v1.11.1    -> v1.11.1
 * [new tag]         v1.12.0.pre.1 -> v1.12.0.pre.1
 * [new tag]         v1.2.0     -> v1.2.0
 * [new tag]         v1.2.0.pre -> v1.2.0.pre
 * [new tag]         v1.2.0.pre.1 -> v1.2.0.pre.1
 * [new tag]         v1.2.0.rc  -> v1.2.0.rc
 * [new tag]         v1.2.0.rc.2 -> v1.2.0.rc.2
 * [new tag]         v1.2.1     -> v1.2.1
 * [new tag]         v1.2.2     -> v1.2.2
 * [new tag]         v1.2.3     -> v1.2.3
 * [new tag]         v1.2.4     -> v1.2.4
 * [new tag]         v1.3.0     -> v1.3.0
 * [new tag]         v1.3.0.pre -> v1.3.0.pre
 * [new tag]         v1.3.0.pre.2 -> v1.3.0.pre.2
 * [new tag]         v1.3.0.pre.3 -> v1.3.0.pre.3
 * [new tag]         v1.3.0.pre.4 -> v1.3.0.pre.4
 * [new tag]         v1.3.0.pre.5 -> v1.3.0.pre.5
 * [new tag]         v1.3.0.pre.6 -> v1.3.0.pre.6
 * [new tag]         v1.3.0.pre.7 -> v1.3.0.pre.7
 * [new tag]         v1.3.0.pre.8 -> v1.3.0.pre.8
 * [new tag]         v1.3.1     -> v1.3.1
 * [new tag]         v1.3.2     -> v1.3.2
 * [new tag]         v1.3.3     -> v1.3.3
 * [new tag]         v1.3.4     -> v1.3.4
 * [new tag]         v1.3.5     -> v1.3.5
 * [new tag]         v1.3.6     -> v1.3.6
 * [new tag]         v1.4.0.pre.1 -> v1.4.0.pre.1
 * [new tag]         v1.4.0.pre.2 -> v1.4.0.pre.2
 * [new tag]         v1.4.0.rc.1 -> v1.4.0.rc.1
 * [new tag]         v1.5.0     -> v1.5.0
 * [new tag]         v1.5.0.rc.1 -> v1.5.0.rc.1
 * [new tag]         v1.5.0.rc.2 -> v1.5.0.rc.2
 * [new tag]         v1.5.1     -> v1.5.1
 * [new tag]         v1.5.2     -> v1.5.2
 * [new tag]         v1.5.3     -> v1.5.3
 * [new tag]         v1.6.0     -> v1.6.0
 * [new tag]         v1.6.0.pre.1 -> v1.6.0.pre.1
 * [new tag]         v1.6.0.pre.2 -> v1.6.0.pre.2
 * [new tag]         v1.6.0.rc  -> v1.6.0.rc
 * [new tag]         v1.6.0.rc2 -> v1.6.0.rc2
 * [new tag]         v1.6.1     -> v1.6.1
 * [new tag]         v1.6.2     -> v1.6.2
 * [new tag]         v1.6.3     -> v1.6.3
 * [new tag]         v1.6.4     -> v1.6.4
 * [new tag]         v1.6.5     -> v1.6.5
 * [new tag]         v1.6.6     -> v1.6.6
 * [new tag]         v1.6.7     -> v1.6.7
 * [new tag]         v1.6.8     -> v1.6.8
 * [new tag]         v1.7.0     -> v1.7.0
 * [new tag]         v1.7.1     -> v1.7.1
 * [new tag]         v1.7.1.pre -> v1.7.1.pre
 * [new tag]         v1.7.1.pre.2 -> v1.7.1.pre.2
 * [new tag]         v1.7.1.pre.3 -> v1.7.1.pre.3
 * [new tag]         v1.7.10    -> v1.7.10
 * [new tag]         v1.7.11    -> v1.7.11
 * [new tag]         v1.7.12    -> v1.7.12
 * [new tag]         v1.7.13    -> v1.7.13
 * [new tag]         v1.7.14    -> v1.7.14
 * [new tag]         v1.7.15    -> v1.7.15
 * [new tag]         v1.7.2     -> v1.7.2
 * [new tag]         v1.7.3     -> v1.7.3
 * [new tag]         v1.7.4     -> v1.7.4
 * [new tag]         v1.7.5     -> v1.7.5
 * [new tag]         v1.7.6     -> v1.7.6
 * [new tag]         v1.7.7     -> v1.7.7
 * [new tag]         v1.7.8     -> v1.7.8
 * [new tag]         v1.7.9     -> v1.7.9
 * [new tag]         v1.8.0     -> v1.8.0
 * [new tag]         v1.8.0.pre -> v1.8.0.pre
 * [new tag]         v1.8.1     -> v1.8.1
 * [new tag]         v1.8.2     -> v1.8.2
 * [new tag]         v1.8.3     -> v1.8.3
 * [new tag]         v1.8.4     -> v1.8.4
 * [new tag]         v1.8.5     -> v1.8.5
 * [new tag]         v1.8.6     -> v1.8.6
 * [new tag]         v1.8.7     -> v1.8.7
 * [new tag]         v1.8.8     -> v1.8.8
 * [new tag]         v1.8.9     -> v1.8.9
 * [new tag]         v1.9.0     -> v1.9.0
 * [new tag]         v1.9.0.pre -> v1.9.0.pre
 * [new tag]         v1.9.0.pre.1 -> v1.9.0.pre.1
 * [new tag]         v1.9.0.rc  -> v1.9.0.rc
 * [new tag]         v1.9.1     -> v1.9.1
 * [new tag]         v1.9.2     -> v1.9.2
 * [new tag]         v1.9.3     -> v1.9.3
 * [new tag]         v1.9.4     -> v1.9.4
 * [new tag]         v1.9.5     -> v1.9.5
 * [new tag]         v1.9.6     -> v1.9.6
 * [new tag]         v1.9.7     -> v1.9.7
 * [new tag]         v1.9.8     -> v1.9.8
 * [new tag]         v1.9.9     -> v1.9.9
Switched to a new branch 'fetchgit'
git revision is a2343c9eabf5403d8ffcbca4dea33d18a60fc157
git human-readable version is v1.7.9-390-ga2343c9
Commit date is 2015-01-11 17:25:27 -0800
Deleted remote-tracking branch origin/0-8-stable (was 74de75e).
Deleted remote-tracking branch origin/0-9-stable (was 6b60c60).
Deleted remote-tracking branch origin/1-0-stable (was 43a74f9).
Deleted remote-tracking branch origin/1-1-stable (was bbce585).
Deleted remote-tracking branch origin/1-10-stable (was cea53ed).
Deleted remote-tracking branch origin/1-11-stable (was 1b021b2).
Deleted remote-tracking branch origin/1-12-stable (was 3f05b6a).
Deleted remote-tracking branch origin/1-2-stable (was 50ce456).
Deleted remote-tracking branch origin/1-3-stable (was 2df02a3).
Deleted remote-tracking branch origin/1-5-stable (was 7235f9e).
Deleted remote-tracking branch origin/1-6-stable (was 7e67be5).
Deleted remote-tracking branch origin/1-7-stable (was 26cb8f8).
Deleted remote-tracking branch origin/1-8-stable (was e10618f).
Deleted remote-tracking branch origin/1-9-stable (was 0aec2b1).
Deleted remote-tracking branch origin/1-99-dev (was 50c9389).
Deleted remote-tracking branch origin/171 (was ef9e90f).
Deleted remote-tracking branch origin/2-0-dev (was 20b3078).
Deleted remote-tracking branch origin/2-0-dev-archived (was b909438).
Deleted remote-tracking branch origin/2813-fix-self-dependency-bug (was b88481e).
Deleted remote-tracking branch origin/3982-clean-rubylib (was 3ae70bb).
Deleted remote-tracking branch origin/4064 (was d08f95d).
Deleted remote-tracking branch origin/align-hash (was 000a8f4).
Deleted remote-tracking branch origin/auto (was f819834).
Deleted remote-tracking branch origin/autobundle (was 7cec62a).
Deleted remote-tracking branch origin/checksum (was 7dd7e49).
Deleted remote-tracking branch origin/dont_run_git_commands_during_runtime (was eaa91b9).
Deleted remote-tracking branch origin/execless (was 8bbd5b7).
Deleted remote-tracking branch origin/fetchers_fetchers_everywhere (was 20f628c).
Deleted remote-tracking branch origin/fix-backtracking-from-child (was 7a98d5d).
Deleted remote-tracking branch origin/fix-bug-with-bundle-cache-erroring (was a4ee812).
Deleted remote-tracking branch origin/fix-path-caching-3900 (was 6578473).
Deleted remote-tracking branch origin/fix-thread-safety-parallel-install (was 487862b).
Deleted remote-tracking branch origin/fix-worker-cleanup-error (was b6f0a56).
Deleted remote-tracking branch origin/fix-worker-index-jruby (was d4fb9f9).
Deleted remote-tracking branch origin/fix_missing_gem_dir (was 2f62ac5).
Deleted remote-tracking branch origin/further_disablement (was e46a40c).
Deleted remote-tracking branch origin/gem_tasks (was a3c2fd8).
Deleted remote-tracking branch origin/gemfile_hashing (was 3d88ab9).
Deleted remote-tracking branch origin/gh-pages (was 6d2c016).
Deleted remote-tracking branch origin/issue-3671 (was 9ed886f).
Deleted remote-tracking branch origin/make-paralle-fetch-jruby (was 57d8890).
Deleted remote-tracking branch origin/master (was a69ec8f).
Deleted remote-tracking branch origin/molinillo (was 178247b).
Deleted remote-tracking branch origin/new-index (was aaad341).
Deleted remote-tracking branch origin/old-gem-version (was 5df697b).
Deleted remote-tracking branch origin/parallel_threads (was b1e7b7b).
Deleted remote-tracking branch origin/platforms (was c3b003c).
Deleted remote-tracking branch origin/refactor-resolver (was 1c121ea).
Deleted remote-tracking branch origin/removing_the_spec_gil (was 5b7f695).
Deleted remote-tracking branch origin/reraise-orig-exception (was 1f1f748).
Deleted remote-tracking branch origin/resolve-running-ruby (was f96d84f).
Deleted remote-tracking branch origin/retry_network (was 833b69c).
Deleted remote-tracking branch origin/rgb-manpage-additions (was 6cefe6f).
Deleted remote-tracking branch origin/rubygems22_exts (was 9007c94).
Deleted remote-tracking branch origin/seg-gemspec-ruby (was c3eb370).
Deleted remote-tracking branch origin/segseparate-lockfile-sources (was ec289da).
Deleted remote-tracking branch origin/sources (was eefe9c6).
Deleted remote-tracking branch origin/spec-for-3896 (was f494205).
Deleted remote-tracking branch origin/test_default_gems (was e2cf0b1).
Deleted remote-tracking branch origin/travis-docker (was f426548).
Deleted remote-tracking branch origin/travis-new-setup (was fbf2374).
Deleted remote-tracking branch origin/travis-trusty-env (was 8939173).
Deleted remote-tracking branch origin/unsupported_sources (was 39e7f6e).
Deleted remote-tracking branch origin/user_agent (was 8b1d376).
Deleted remote-tracking branch origin/user_agent2 (was 2441ff1).
Deleted tag 'v1.10.0' (was b0cd4c6)
Deleted tag 'v1.10.0.pre' (was fdbf44b)
Deleted tag 'v1.10.0.pre.1' (was 2ba9dad)
Deleted tag 'v1.10.0.pre.2' (was 2c19e41)
Deleted tag 'v1.10.0.rc' (was 79b973e)
Deleted tag 'v1.10.1' (was 68a0808)
Deleted tag 'v1.10.2' (was 4b257c7)
Deleted tag 'v1.10.3' (was fccd113)
Deleted tag 'v1.10.4' (was 729b008)
Deleted tag 'v1.10.5' (was fc32d6a)
Deleted tag 'v1.10.6' (was bed96cb)
Deleted tag 'v1.11.0' (was ae7e4a6)
Deleted tag 'v1.11.0.pre.1' (was 1cf71bd)
Deleted tag 'v1.11.0.pre.2' (was 9edfb5e)
Deleted tag 'v1.11.1' (was 85cf122)
Deleted tag 'v1.11.2' (was 04f0d0d)
Deleted tag 'v1.12.0.pre.1' (was ef8b71f)
Deleted tag 'v1.12.0.pre.2' (was cef0615)
Deleted tag 'v1.8.0' (was 25e30aa)
Deleted tag 'v1.8.0.pre' (was 3930ccc)
Deleted tag 'v1.8.1' (was 12edaff)
Deleted tag 'v1.8.2' (was 629365b)
Deleted tag 'v1.8.3' (was 86fbeb7)
Deleted tag 'v1.8.4' (was 047c935)
Deleted tag 'v1.8.5' (was 94abab8)
Deleted tag 'v1.8.6' (was 8bc00cb)
Deleted tag 'v1.8.7' (was 5247b43)
Deleted tag 'v1.8.8' (was 72a0f2c)
Deleted tag 'v1.8.9' (was cddab74)
Deleted tag 'v1.9.0' (was 34922d2)
Deleted tag 'v1.9.0.pre' (was 8765197)
Deleted tag 'v1.9.0.pre.1' (was b49e03c)
Deleted tag 'v1.9.0.rc' (was 554f40e)
Deleted tag 'v1.9.1' (was a4bc7ec)
Deleted tag 'v1.9.10' (was 25d45a7)
Deleted tag 'v1.9.2' (was 6373035)
Deleted tag 'v1.9.3' (was 9421a08)
Deleted tag 'v1.9.4' (was c52f49f)
Deleted tag 'v1.9.5' (was 2f0654a)
Deleted tag 'v1.9.6' (was b27e814)
Deleted tag 'v1.9.7' (was 8e3abbb)
Deleted tag 'v1.9.8' (was 86982a6)
Deleted tag 'v1.9.9' (was bf1239b)
output path ‘/nix/store/v7kmrgydx4zdfnvbfby3rh7aj1gnps7f-bundler-a2343c9’ has r:sha256 hash ‘0l3jxk77jaf757kcbbmz0m3pdf0mx5p2zlbj5scxslhdv456422d’ when ‘1p7kzhmicfljy9n7nq3qh6lvrsckiq76ddypf6s55gfh1l98z4k9’ was expected
building path(s) ‘/nix/store/ywnjmfy3ilqswkjil98c05wydy7syh9a-gitlabhq-477743a’
cannot build derivation ‘/nix/store/fp2isj2fp8d3zw39hn8f4vp127x855dy-ruby_2.1.3_p0-bundler-2015-01-11.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/yvnjqrllx6cvys18kpsk6q6nmhjwwyy7-gitlab.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/50p7hgf33yl146mdhlgg56cfyi542myc-gitlab-runner.drv’: 1 dependencies couldn't be built
building path(s) ‘/nix/store/3bncdirac9g895fx8v25gi7nf2w3hkbf-pg_hba.conf’
cannot build derivation ‘/nix/store/9hd5vkw8qa68s5h7rz102fh14mgw3gzb-unit-gitlab-sidekiq.service.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/rn397m2aznzs266xhwkijs1gcj1vx73b-unit-gitlab.service.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/9abc7sj590azqxpmba443gvp58bik382-system-path.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/qymk5dbzhqkfg2m4chhq4akaskpazrld-system-units.drv’: 1 dependencies couldn't be built
building path(s) ‘/nix/store/3vvliwya3p45sw4ja514w6cfvql44hm2-udev-rules’
cannot build derivation ‘/nix/store/85ljfjaiz3g7d6572j5ay3m94li4nwy6-nixos-15.09.1076.9220f03.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/85ljfjaiz3g7d6572j5ay3m94li4nwy6-nixos-15.09.1076.9220f03.drv’ failed


applicabilitymanager: add "indirect-cve-whitelist" to scanner YAML configuration

[v] All tests passed. If this feature is not already covered by the tests, I added new tests.
[v] All static analysis checks passed.
[v] This pull request is on the dev branch.
[v] I used gofmt for formatting the code before submitting the pull request.

I have read the CLA Document and I hereby sign the CLA

Thank you for this PR @srmish-jfrog srmish-jfrog!
Will you be able tio add a full description foir this PR? Note that if PR is eventually merged, it'll be referenced automatically from the release notes, and will receieve high visibility.

Thank you for this PR @srmish-jfrog srmish-jfrog! Will you be able tio add a full description foir this PR? Note that if PR is eventually merged, it'll be referenced automatically from the release notes, and will receieve high visibility.

Sure, done


style: :art: ran pre-commit, only fixes trailing whitespaces and end of file newlines

Description
This is a stacked PR. There's a lot that was changed. Thankfully, it is only trailing whitespaces on lines and fixes end of file newlines.

This PR needs a quick review.

@signekb the SVGs had trailing whitespace/incorrect file ending, which were fixed by the pre-commit. They weren't deleted and re-added :relaxed: SVG is plain text, that's why.


0.7.2 + 0.7.3

Purpose
Merge hotfixes into main
Changes

Exported functions
Added missing dependency (used in generated grpc code)

Checklist

[x] My code follows the style of this project.
[x] The code compiles without warnings.
[x] I have performed a self-review of the changes.
[x] I have documented my code, in particular the intent of the
hard-to-understand areas.
[x] (If necessary) I have updated the CHANGELOG.

Remember to create tags for the releases you have made.


The PostgressDB with JSONB colums is throwing errors in generate phase

Connected the mvn speedment:tool and  tolls is throwing the  following

Hi! The tool is showing warnings like this because it finds columns that it doesn't know how to map. I agree that this is a bit irritating since the messages cover the entire screen. The problem however is easily fixed. Speedment maps columns it doesn't recognize to Object, but they can be cast to the appropriate type when the entity is constructed. To do this automatically, you can create your own TypeMapper that maps from Object to String by casting and then select it in the tool. Instructions on how to add a custom type mapper can be found here.
The long-term fix would be to fix the Speedment PostgreSQL Connector so that it recognizes JSON and JSONB-columns as String-types.
I have created two issues in response to this:

Limit the number of warnings to show to one column (#531)
Make PostgreSQL recognize JSON and JSONB types (#532)

You are very welcome to look at issue #532 if you are interested. It is not very hard to implement and a good thing to start with if you would like to contribute. :)


Unable to import external key into Azure Key Vault.

I followed the same steps as mentioned in this issue.
#108113
1.Generate and download the KEK (Key Encryption Key) as documented
az keyvault key create --vault-name byok-vault-hsm --name byok-kek-key --kty RSA-HSM --size 2048 --ops import
az keyvault key download--vault-name byok-vault-hsm--name byok-kek-key--file KEK.pem

As vaguely described in the documentation, I generated a target RSA key and an ephemeral AES key using the openssl command.

openssl genrsa -out byok.pem 2048
openssl rand -out temp-aes-key.key 32

2.1 Convert the target key to DER format
openssl pkcs8 -inform PEM -outform DER -in byok.pem -out byok.der -nocrypt

Wrap the target key with ephemeral AES key using the CKM_RSA_AES_KEY_WRAP_PAD

export EPHEMERAL_AES_HEX=$( hexdump -v -e '/1 "%02x"' < temp-aes-key.key )

openssl enc -id-aes256-wrap-pad -iv A65959A6 -K $EPHEMERAL_AES_HEX -in byok.der -out key.byok

4.Wrap the ephemeral AES key with the KEK from KeyVault
openssl pkeyutl -encrypt -pubin -inkey KEK.pem -in temp-aes-key.key -out wrapped-temp-key.byok -pkeyopt rsa_padding_mode:oaep -pkeyopt rsa_oaep_md:sha1 -pkeyopt rsa_mgf1_md:sha1
5.Concatenate the both wrapped key together and base64 the result
cat wrapped-temp-key.byok key.byok > final-key.byok
cat final-key.byok | base64 | tr '/+' '_-' | tr -d '=' > ciphertext.byok

Create the BYOK blob JSON file as described in the documentation

{
  "schema_version": "1.0.0",
  "header":
  {    "kid": "https..................",
    "alg": "dir",
    "enc": "CKM_RSA_AES_KEY_WRAP"  },
    "ciphertext":"NXb8CJBxXo9gxdVrs3_rLnDJvlCkWtYkLFPchfhGAjF4xuJHn2GQwLfZY5DpgTuqBP1XztD7ph32XYf80HlauyvCaaUQa9UOF0VbfzXKXpFvq9TYCFyT7Qh3TfQcGr7ihEVw6QJ1nkCgNbFmsrMzG4y9Bp..............",
  "generator": "BYOK tool aemsec; source HSM aemsec"
}

Import the BYOK into KeyVault
az keyvault key import --vault-name key-vault-name --name aemsec-byok-key --byok-file byok.byok --ops encrypt decrypt --debug

The import command returns the following error:
knack.util.CLIError: (BadParameter) Unable to import BYOK blob with this KEK.
Code: BadParameter
Message: Unable to import BYOK blob with this KEK.
cli.azure.cli.core.azclierror: (BadParameter) Unable to import BYOK blob with this KEK.
Code: BadParameter
Message: Unable to import BYOK blob with this KEK.
az_command_data_logger: (BadParameter) Unable to import BYOK blob with this KEK.
Code: BadParameter
Message: Unable to import BYOK blob with this KEK.
Can you please assists how to fix this?
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
ID: 1477e35b-7aba-4968-ce0d-53e1c2f27dec
Version Independent ID: a0590d26-8fd9-df75-1641-6e3738d06cfa
Content: Bring your own key specification - Azure Key Vault
Content Source: articles/key-vault/keys/byok-specification.md
Service: key-vault
Sub-service: keys
GitHub Login: @mbaldwin
Microsoft Alias: mbaldwin

@maheshlode
Thanks for your feedback! We will investigate and update as appropriate.

@maheshlode the BYOK is for HSM import : "This document describes specifications for importing HSM-protected keys from customers' on-premises HSMs into Key Vault."
If you want to just import the key, there is an import method which accepts PEM files https://learn.microsoft.com/en-us/rest/api/keyvault/keys/import-key/import-key?tabs=HTTP

For coding/developer issues, questions we recommend to open an item on Stack Overflow.
#please-close

@jlichwa
I intend to import BYOK-protected keys exclusively. I have already reviewed issue #108113, where I noted that @ccojocar successfully accomplished this using OpenSSL. However, I have encountered some challenges while attempting the same. Could you kindly provide assistance with this matter?
Many Thanks...


Move hydrogen-template-default to templates folder instead of examples

We still want to house examples in the monorepo, but we don't want to make them part of the Yarn workspace. This is because each example can add numerous dependencies, which weighs heavily on CI and local development.

Essentially rename examples to templates
This also involves updating the Stackblitz GH Action, and the create-hydrogen-app release script which copies the files over before publishing to NPM

I like Option 2, as packages should really be reserved for things distributed as NPM packages (I am to blame for introducing packages/playgrounds/* initially 😭 )


DataFusion repo got 40MB larger

Describe the bug
We accidentally have checked in a 40MB binary docs.tgz file in https://github.com/apache/datafusion/pull/10407
https://github.com/apache/datafusion/pull/10416 removed the file but it is still in git history
Thus the DataFusion repo is significantly larger than it used to be
To Reproduce
No response
Expected behavior
No response
Additional context
No response

That's unfortunate, but fixing this requires rewriting git history.
Is this issue about such a rewrite? or preventing similar mistake in the future?

That's unfortunate, but fixing this requires rewriting git history. Is this issue about such a rewrite? or preventing similar mistake in the future?

I suggest we use this particular issue for fixing the history -- I recommend a seprate ticket for ways to prevent a similar mistake in the future

if we want to fix this, this will require a force push to main branch and also doing something about tags that reference the commit that includes docs/docs.tgz file (39.0.0, 39.0.0-rc1, 40.0.0, 40.0.0-rc1).
Fixing main is simple (but painful)
i prepared a main branch copy with the docs archive removed (based on main as of today, commit 133128840ca3dbea200dcfe84050cb7b82bf94a8), someone would need to push that into the main
git fetch https://github.com/findepi/datafusion findepi/main-without-docs
main_fixed=$(git rev-parse FETCH_HEAD)
current_main=133128840ca3dbea200dcfe84050cb7b82bf94a8 # commit on `main`
fork_point=$(git merge-base $main_fixed $current_main)

# verify
git show $main_fixed
git diff $current_main $main_fixed # same content

# verify history -- this should show `remove docs archive` commit omitted
git diff <(git log $fork_point..$current_main --format=%s) <(git log $fork_point..$main_fixed --format=%s)

# apply
git checkout main
git reset --hard $main_fixed

# apply commits from real current main
git fetch https://github.com/apache/datafusion main
git cherry-pick $current_main..FETCH_HEAD

# publish
git push https://github.com/apache/datafusion main:main --force-with-lease

once we do the above, then we need to delete (replace?) the release tags mentioned above

I think the branch protections would need to be updated temporarily too -- I don't think we can force push to main
I also  think if we force push to main all outstanding PRs will become quite messed up until after a rebase
THank you @findepi  for preparing this
@andygrove  / @comphead  / @jayzhan211  do you have any thoughts on this matter?

I think it was a precommit github hook checking large files, please allow me some time to investigate it

I also think if we force push to main all outstanding PRs will become quite messed up until after a rebase

that's correct.
also, editing release tags is something to think about.
if we re-use tag names, existing forks/clones will choke on this.
i'd be tempted not to solve this problem.

precommit github hook checking large files

is this something we can configure in the repo itself?
cause we should not rely on git commit hooks -- a contributor may not set them up.
we could have a CI check for this (like https://github.com/ppremk/lfs-warning , https://github.com/james-callahan/gha-prevent-big-files  or something similar, perhaps our own)

Git action looks even more promising as you right, the precommit checks are not reliable as they running locally.
Imho I like the way  https://github.com/james-callahan/gha-prevent-big-files it seems simpler for now and we have much control of it.
Would you like to experiment with this @findepi ?

@comphead sure
created https://github.com/apache/datafusion/pull/11508 with the check

Talking about the size and "cleanliness" of the repo, should we do a git gc? I find conflicting information on the Internet about whether GH does this automatically. In my experience GH doesn't seem to do this.

Yep, git gc and cleaning up history are different things, but I wanted bring this up as we make efforts into cleaning up the repo in general

Talking about the size and "cleanliness" of the repo, should we do a git gc? I find conflicting information on the Internet about whether GH does this automatically. In my experience GH doesn't seem to do this.

My understanding is that what comes from github is automatically gcd. Your local checkout also periodically builds up garbage (e.g. from local commits, etc) that you can clean up by locally running git gc
So I don't think there is anything we need to do with gc on github but I ma be mistaken

I keep seeing notifications on commits with the notice "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.", which basically says that this is an unreachable commit/garbage. I think these commits accumulate because people fork the repo to try things, and when the fork repo is deleted, we get into this state. This prompts me to think GH doesn't do git gc, but I'm not sure either.

It's more complicated. It seems that all forks' objects are stored together on github backend.
If i make a commit and push it to my fork, you can read it from this repo if you know the commit id.
I assume github does git gc internally (or equivalent), but it doesn't prevent the "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository." situation.

If i make a commit and push it to my fork, you can read it from this repo if you know the commit id.

Yes, there is actually no problem until the fork is deleted. When the fork is then deleted, it seems like the commit still stays on the "mother" repo as an unreachable commit and these things accumulate over time. Googling it suggests gc would solve this, but that may be wrong.


Fix directory permissions after assemble is complete

Add exec permission to subdirectories and perform the fix after the assemble has completed.
Depends on https://github.com/openshift/sti-base/pull/70

@bparees @jhadvig

lgtm, tests will fail until the base image PR is merged.

[test]

@sdodson one of the assemble script PRs we want to get into the 3.1images.
@jhadvig can you make the parallel PRs to the other repos?

@csrwng E1023 10:27:38.440017 03934 util.go:85] /usr/libexec/s2i/assemble: line 54: fix-permissions: command not found

might be because the new base image isn't pushed yet.

@bparees will do

[test]


⚠ Spryr has degraded performance

In bb5a8c4, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 6141 ms

Resolved: Spryr performance has improved in 4e5cf3d after 7 minutes.


run dnf upgrade before installing in fedora

- What I did
Right now, building docker-engine rpms for fedora 25 are broken because fedora 25 repo has a new vim-common-8.0 package that cannot be installed if vim-minimal-7.4 is already installed. To work around this, need to do a dnf upgrade before installing vim-common to get vim-minimal up to version 8.0. This is similar to doing a apt-get update before doing a apt-get install.
This PR will add dnf -y upgrade for all fedora Dockerfile files used for building fedora docker-engine RPMs.
I've also filed a bugzilla ticket to fedora team about this: https://bugzilla.redhat.com/show_bug.cgi?id=1401323
- How I did it
Added a case statement to contrib/builder/rpm/amd64/generate.sh and re-ran the generate.sh script to generate the Dockerfile files.
- How to verify it
Just build a fedora-25 rpm. If it can build, then this PR is successful.
$ make DOCKER_BUILD_PKGS=fedora-25 rpm

Without this PR, you will get an error like this:
Error: Transaction check error:
  file /usr/share/man/man1/vim.1.gz from install of vim-common-2:8.0.118-1.fc25.x86_64 conflicts with file from package vim-minimal-2:7.4.1989-2.fc25.x86_64

- Description for the changelog

N/A
- A picture of a cute animal (not mandatory but encouraged)
😿

/cc @vieux @crosbymichael @tiborvass

This is similar to doing a apt-get update before doing a apt-get install

Is this the same as apt-get update or apt-get upgrade? apt-get update only updates the index, but doesn't upgrade existing packages.
FWIW, if this is the same as apt-get update, should this be combined with the install lines?
RUN dnf -y upgrade && dnf install -y .....

The dnf upgrade will update the index and upgrade all currently installed packages to the latest version, which will get vim-minimal to to v8.0 making it possible to install vim-common v8.0 easily.

fyi these are the packages that are updated by this PR https://gist.github.com/andrewhsu/e2e7d9fee2685c17187aef8b8ec6fdb9
As a summary, this is the diffstat:
$ diffstat docker-fc25-upgraded.diff
 unknown |   73 ++++++++++++++++++++++++++++++++--------------------------------
 1 file changed, 37 insertions(+), 36 deletions(-)


Fix/header css

Description
Fixed the negative margins on the css header

closing somethings not going right.


Refactor Code

Changed

v1.0.0 in CHANGELOG 'technically' had the wrong date.

While released today, the code was published (with license) on 2020-06-12.

More like refactored files...


creating user model migrations table

creating user model

@victorazangu could you maybe do the user model for demonstration of what's expected?