Documentation – outdated bits

Two things I just noticed regarding your documentation:

the "Read the Docs" menu on the start page of the Tweepy website links to https://tweepy.readthedocs.org/en/v3.2.0/ where the user is displayed a message saying "You are not using the most up to date version of the library. 3.5.0 is the newest version.". It would make sense to link to the most up-to-date version https://tweepy.readthedocs.org/en/v3.5.0/ from the start page.
for the Lists Methods on the User Methods page, it says "Creates a new list for the authenticated user. Accounts are limited to 20 lists.". This is very outdated info as that list limit was changed in 2013. (!) I would've submitted a PR but the "Edit on GitHub" link at the top right of the page leads to this file in your repo which doesn't actually reflect the text of the documentation...

It appears that the documentation for 3.5.0 also has not changed to reflect the deprecation of update_with_media: https://dev.twitter.com/rest/reference/post/statuses/update_with_media and inclusion of media_ids in update_status, despite these being included in the 3.2.0 release notes.

Regarding the first issue, the Default Version for Read the Docs is now set to latest. See #1134.
As for the issue about the documentation for API.create_list, I've just updated it with https://github.com/tweepy/tweepy/commit/7e1aba026163a024b43a481f68be700eb9cd4f92, which should now be reflected at https://tweepy.readthedocs.io/en/latest/api.html#API.create_list.
@thomaslawn The former should now be resolved by https://github.com/tweepy/tweepy/commit/805ed5c7a43e391a2b92b92887e0eae0c1545841 (#1028) and the latter by https://github.com/tweepy/tweepy/commit/292505d03b3f242ff5ee3afba9d30037ff1ea53f (#1176).
See https://tweepy.readthedocs.io/en/latest/api.html#API.update_with_media and https://tweepy.readthedocs.io/en/latest/api.html#API.update_status.


Enhancement: expose ID of window created by vim.ui.input

Hi,
I'm currently trying to add proper support for dressing.nvim in my plugin inc-rename.nvim (the current implementation has issues, see https://github.com/smjonas/inc-rename.nvim/issues/17). Basically, I need to control the window created by dressing.nvim from the command line and change the input text while the user is typing. For this to work, I need to get the ID of the window created by vim.ui.input.
At the moment, I am doing the following to find the ID:
-- Open the input window and find the buffer and window IDs
vim.ui.input({}, function() end)
vim.schedule(function()
  for _, win_id in ipairs(vim.api.nvim_list_wins()) do
    local bufnr = vim.api.nvim_win_get_buf(win_id)
    if vim.bo[bufnr].filetype == "DressingInput" then
      -- found the window ID
    end
  end
end)

This almost works but using vim.schedule is problematic as that doesn't work well with Nvim's command preview callback. Omitting vim.schedule won't work because you use schedule_wrap in input.lua here (so I need to schedule my code to run after yours):
https://github.com/stevearc/dressing.nvim/blob/96b09a0e3c7c457140303c796bd84f13cfd9dbc0/lua/dressing/input.lua#L276
Therefore, I am proposing the following enhancements:

add support for a boolean parameter no_schedule / synchronous / sync passed to the opts key in vim.ui.input which won't schedule wrap the function if set to true (let me know which name you'd prefer)
if no_schedule / synchronous / sync is set, return the window ID from vim.ui.input

Please let me know if you have any another ideas / suggestions! I can send a PR if you want :)

The original reason why vim.ui.input was wrapped was to work around an issue during neovim startup (see #15). I've updated the wrapper to only use schedule_wrap during startup, and to execute synchronously otherwise. I believe that inc-rename will only ever be called after startup, so this should make all vim.ui.input calls from inc-rename synchronous. Does that work for you?
I'm a little more hesitant to return the window ID from the call because this starts to change the default built-in API. There is some precedent for this, as I decided to add an API extension in e607dd99aeb5ce21e9a3d8f4c028650db12bd3af, but I want to be extra cautious about these sorts of things and preferably do it in a way that is guaranteed to never conflict with the built-in API.

Thanks a lot, this should resolve my main issue. I'm fine with leaving it like this if you don't want to change the API since there exists a workaround to get the ID. Still, I'm curious what exactly the API contract is here / why is returning something instead of  nil problematic?

Two reasons:

It's possible that neovim will refactor vim.ui.input to return some value in the future, at which point it will clash. Not incredibly likely, but not beyond the realm of possibility.
It introduces a non-standard API that users or plugin authors could start to depend on. They might start to expect that if vim.ui.input returns nil, it doesn't open a floating window. That in turn might cause bugs or unexpected behavior if someone uses a vim.ui.input implementation that isn't dressing.nvim.

These are small potential issues and I could be convinced otherwise, but in general I think that maintaining exact API compatibility is valuable and should not be broken lightly.

Note that I had to revert this change to vim.ui.select because it turns out we need the schedule_wrap for other reasons when opening the select windows. vim.ui.input is unchanged, so hopefully this will not affect you.

Thanks for letting me know! No, as it stands now this won't affect me :)


Opensearch sink: support ingest pipeline configuration option

Is your feature request related to a problem? Please describe.
In opensearch you can use ingest pipelines to process data. Fluent-bit, logstash etc support this via a property on the output/sink configuration. Data prepper does not.
Describe the solution you'd like
ingest_pipeline option for the opensearch sink
Describe alternatives you've considered (Optional)
Index templates through dataprepper, but this is overkill imho.
Additional context
N/A

To be sure, you mean using this feature, correct? https://opensearch.org/docs/latest/ingest-pipelines/index/
Also, is there a particular reason you want to use an ingest-pipeline along with Data Prepper? I would generally recommend using Data Prepper instead of ingest-pipelines.

Hi, yeah that's the one. Sometimes dataprepper is the choice, but not always. Ingest pipelines an supported and actively developed feature in opensearch which have their uses. i.e. the Elastic log source use ingest pipelines for data manipulation, so we have loaded them into opensearch. Every other log forwarder supports it (logstash plugin, fluent-bit, fluent-d, etc)
This is holding me back from stripping logstash-oss from our egress path from Kafka. Implementation can't be that hard I hope?


[BD-46] fix: remove ResizeObserver from useIndexOfLastVisibleChild hook

Description
Initially this PR aimed to fix ResizeObserver error that got reported in #1811, but turned out to be a good clean up opportunity for useIndexOfLastVisibleChild hook which resulted in removing ResizeObserver altogether, fixing the reported issue.
Deploy Preview
https://deploy-preview-1842--paragon-openedx.netlify.app/components/hooks/useindexoflastvisiblechild/
Note: ResizeObserver loop limit exceeded error is not logged to browser's console by default (it still gets caught by New Relic though). To actually check that this error is not reproduced anymore do the following:

Go to the deploy-preview link above
Open your browser's console
Run addEventListener('error', (e) => console.error(e))
Try to resize your window in multiple ways

Notice that nothing gets logged to your console. If you do the steps above on current version of useIndexOfLastVisibleChild hook you will see multiple errors.
Merge Checklist

[x] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[x] Does your change adhere to the documented style conventions?
[x] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[x] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[x] Were your changes tested in the example app?
[x] Is there adequate test coverage for your changes?
[x] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

Thanks for the pull request, @viktorrusakov!
When this pull request is ready, tag your edX technical lead.

@viktorrusakov 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 21.0.0-alpha.12 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


View is messy

The following informations are requested in a bug report

A brief bug description.
The view in 'week' scope is messy
Stack trace.
It is not a crash, so I think it is not required
Integration method.(manually/cocoapods/carthage)
Cocoapods
Full steps to reproduce.
Add a UIView in storyboard, associate it with FSCalender, and configure the calendar view with the following methods in viewDidLoad:

viewCalendar.appearance.weekdayTextColor = .lightGray
viewCalendar.appearance.weekdayFont = UIFont.systemFont(ofSize: 18)
viewCalendar.appearance.titleFont = UIFont.systemFont(ofSize: 22)
viewCalendar.scope = .week
viewCalendar.headerHeight = 0

Add extension:
extension AddUserVideoCallScheduleViewController: FSCalendarDataSource{
    func calendar(_ calendar: FSCalendar, boundingRectWillChange bounds: CGRect, animated: Bool) {
        calendarHeightConstraint.constant = bounds.height
        view.layoutIfNeeded()
    }
}

Device modal and iOS version.  e.g. iPhone 6s iOS9.1
iPhone 8Plus 13.3 Simulator
Xcode version.  e.g. Xcode 8.1
Xcode 11.3.1
FSCalendar version. e.g. FSCalenda 2.5.1
FSCalendar 2.8.1
Does this happen in the demo project? Which one? Or a link to another demo project.
No, it doesn't happen in demo project. It happens in my own project

I want to make the view like:

Please guide, what should I do?
Even I cannot give proper spacing between weekdays and dates

Anyone could help??

Ok, I have figured out what is the issue. In auto layout, it is mandatory to give your calendar view a bigger height, may be around 300. Then in viewDidLoad, you can choose your scope to be .week, then it should show properly.


Use the .net ASN reader instead of parsing it manually

Instead of parsing the EcDSA signature in DeserializeSignature() (in AccountController.cs) you could use the build-in .net AsnReader.
 RSA and EdDSA use the signature without any parsing. The odd behaviour of EcDSA is for compatibility reasons with the original U2F spec.
                var s = Base64Url.Decode(signature);
                var reader = new AsnReader(s, AsnEncodingRules.DER);
                var sequence = reader.ReadSequence(Asn1Tag.Sequence);
                var r = sequence.ReadIntegerBytes(Asn1Tag.Integer);
                var s = sequence.ReadIntegerBytes(Asn1Tag.Integer);

                // remove negative flags
                if (r.Span[0] == 0x0)
                {
                    r = r[1..];
                }

                if (s.Span[0] == 0x0)
                {
                    s = s[1..];
                }

                // combine r and s
                var signature = new byte[r.Length + s.Length];
                var signatureSpan = signature.AsSpan();
                r.Span.CopyTo(signatureSpan);
                s.Span.CopyTo(signatureSpan[r.Length..]);

                return signature;

Hi! Interesting stuff. I'm thinking about updating this repo and the accompanying article soon. Let me take a look into this, could be interesting to include 🙂

This worked perfectly! Thank you for the contribution 🙂
https://github.com/scottbrady91/fido2-poc/blob/master/src/ScottBrady.Fido2/Cryptography/SignatureValidationStrategies/EcdsaSignatureValidationStrategy.cs#L24


Sync error

I have a smal problem
App\Domains\Wallet\Action\Sync::productRelated(): Return value must be of type App\Domains\Product\Model\Product, null returned

on /sync

Fixed, now all products are added on sync.


Add prettier script

Adds prettier to a script at the top level of the repository, so fixing up style is now as easy as running npm run lint.

@SamyBouch @eudisley please let me know by commenting here when your changes are merged, and I can rerun this script without giving you merge conflict headaches!

@cjol I just merge the conflict the develop had the right info from @SamyBouch fix on the tutorial page.


Add authorization exceptions

Please, add several kind of authorization exceptions to project.
You need to adapt them in common logic of ReckueException and change their code according to our classification.
You must create :

UnauthorizedException (or other name, but it must be like 401 UNAUTHORIZED);
AccessDeniedException (or other name, but it must be like 403 FORBIDEN).

Closes #409


Upgrade to latest view-creation library and also updated others.

The latest view-creation library introduces some mandatory configs
in pinot view configs so added them as well.

FYI, Snyk failure is because we have hit our monthly quota for snyk jobs.

FYI, Snyk failure is because we have hit our monthly quota for snyk jobs.

that's bad messaging on there part, its OSS so the quota doesn't apply. Scroll up in the logs and you'll see the snyk issues.

FYI, Snyk failure is because we have hit our monthly quota for snyk jobs.

that's bad messaging on their part, its OSS so the quota doesn't apply. Scroll up in the logs and you'll see the snyk issues.

Oh wow.. thanks for pointing that. I've fixed the snyk failure now.

I'm guessing the snyk failures are because of pinot tools dependency. Are we going to ever report that to Pinot?

I'm guessing the snyk failures are because of pinot tools dependency. Are we going to ever report that to Pinot?

Good idea. We should report and if possible we can even fix them in the upstream so that in the next version we can get updates.


Adjust batch.size property description and validation.

According here : http://kafka.apache.org/082/configuration.html, batch.size should be in bytes with default value 16348.

Hello - thanks for contributing.  Some feedback:

The commit message and the PR will need to associate to some open JIRA.  If the JIRA were say NIFI-XYZ1 then the commit message should have "NIFI-XYZ1 ...the message"
The batch size does documentation does need to be changed.  The change to a new default number of 16KB is fine but changing the name of the property is not ideal as it would break compatibility.  You can change the display name safely but it is already appropriate.
The description you gave is good.
I like your change to using the data size validator but the problem is this would make all existing configurations invalid as they'd need to add the unit to their value.  I am +0 on changing that personally as we do have provisions to deal with it and can document it in a migration guide.  However, thinking further on it I'm told on older versions of Kafka that batch size really was about the number of messages so changing it may not be ideal.

You could choose to simply fix the description of the property and leave the rest for now.  There is an actively under work PR/JIRA to move to supporting the 0.9 Kafka producer and consumer API and that will give us a chance to tighten some of these behaviors up as well.  It will be two new processors and these will still be around for some time.

@owieboy First of all thank you for a contribution
Unfortunately this PR is now a duplicate and we would have noticed it a while back if it had an associated  JIRA. IN any event, the proposed changes are already incorporated into another PR https://github.com/apache/nifi/pull/366. Could you please verify that it covers what you wanted and if so go ahead and close this PR, otherwise let us know if there is anything else you believe is missing.

Hey @owieboy,
Just been doing some maintenance and wanted to check in to see if the PR changes of #366 satisfy the efforts for this PR.  If so, could you please close this item out and if not, please let us know where it is short of your needs?  Thanks!


scripthook v critical error

When loading and running the gtav.hk file with dxgi.dll and Scripthook V in my directory, I get the following error:

I'm currently running GTAV version 1.0.1493.1, but tried reverting to the previous version as well and no dice. Further inspection indicates that this issue is happening when hooking into GTAV.exe (the blacklisting code added to the repo seems to be running fine).
This error is only happening when ScripthookV.dll and gtav.hk are within the GTAV folder together - other *.hk files are loading & running just fine and I'm not noticing any issues if I use dxgi.dll and/or dinput8.dll with the Scripthook file alone.
Any help would be much appreciated! Thanks so much for all your work on this.

After digging around a bit more, it looks like I'm getting this same issue with any file that relies on ScripthookV.dll (including *.asi files). However, if I try to load and run these files using dinput8.dll, everything runs as expected.


Exception Unhandled

I am using a Win10/22h2 machine and tried to run the exe that came with the new 2023.11.14-2 release. It fails to run giving me this error:
Unhandled exception at 0x00007FFC7467286E (ucrtbase.dll) in piper.exe: Fatal program exit requested.
I tried to open it normally and also command line as well, it gives the same error.
Would anyone be able to assist on why this is failing?

Were you able to solve this? I'm having the same issue


unit test's for ssl support

Unit tests for the ssl support are still missing. @eighthave how about those unit tests you made yourself?

I only have some raw sketches, nothing worth sharing yet

sorry to hear that ...

Could you perhaps push the drafts to a branch? I might have some time to
work on the tests in the near future if there's something to start from.

because nothing was provided :-( I have implemented the tests myself.


Adding specialized functionality for when the per-user cap is one

One common ads use-case is to just count conversions. In this case, the "trigger value" is irrelevant. Every conversion counts the same, just one.
Furthermore, a common use-case is to count distinct users. Another way of saying this, is that each user can at most contribute a value of one to the output.
In this special case, we can completely avoid bit-decomposition, and indeed we can avoid large chunks of the IPA protocol entirely. As this is not a rare use-case, it seems worthwhile to specialise this, so that we can run a much faster, more communication efficient algorithm.
Testing out on 1000 rows, "Records Sent" drops from 2,286,120 to 1,652,889 - a 27.7% drop in total communication.
Looking at the breakdown by stage:

Accumulate drops from 77,796 to 2,997 (now it's just ONE multiplication per row!)
User Capping drops from 668,790 to 110,601 (no more bit-decomposition! Just a prefix-OR!)

do you want to add the baseline test for this feature?


chore(*) re-release 1.3.0 as 1.3.0-2

Summary

BREAKING: Bump lua-resty-worker-events dependency to 2.0.0. This makes  a lot of the APIs in this library asynchronous as the worker events post and post_local won't anymore call poll on a running worker automatically, for more information, see:  https://github.com/Kong/lua-resty-worker-events#200-16-september-2020

This is not needed. Worst case we upload new rockspecs for versions 0.3.2 to 1.3.0 and set the dependency as "lua-resty-worker-events >= 0.3.2, < 2.0", no code changes or anything else needed.
At most we'd include those new revisions in the repo when we release the version depending on 2.0.


Move TestData.py from framework to utilities

I wonder if there is a good reason that
https://github.com/vais-ral/CCPi-Framework/blob/master/Wrappers/Python/ccpi/framework/TestData.py
currently lives in ccpi.framework? Seems to me it more of a utility than a core functionality, so we might consider moving it to ccpi.utilities where it would seem to fit more logically?

Currently my proposal is to move TestData to utilities and have it as

from ccpi.utilities import example_data
from ccpi.utilities.example_data import DataLoader

loader  = DataLoader()
loader.load(example_data.BOAT, size=(128,130))

We decided to go for this

    from ccpi.utilities import dataexample
    from ccpi.utilities.display import plotter2D
    from ccpi.utilities import noise
    import numpy as np

    boat = dataexample.BOAT.get(size=(128,128))

    lvars = 0.1 * np.random.random(size=boat.shape)

    noisy = [boat]
    noisy.append( noise.gaussian(boat, var=0.1) )
    noisy.append( noise.poisson(boat) )
    noisy.append( noise.salt(boat))
    noisy.append( noise.pepper(boat))
    noisy.append( noise.saltnpepper(boat))
    noisy.append( noise.speckle(boat) )
    noisy.append( noise.localvar(boat, local_vars=lvars))

    plotter2D(noisy, titles=['orig', 'gaussian', 'poisson', 'salt', 'pepper', 's&p',
              'speckle', 'localvar'], cmap='inferno')

Also we discussed to add the Diamond dataset to the dataexample


Fixes 'teams channel get' command. Closes #3009

Fixes teams channel get command. Closes #3009
Set channelid as optional parameter.

Awesome we'll have a look asap!

Thank you. Merged manually


Stop using short open tags

Standard PHP installs default to short_open_tags Off so this is a bit of a headache.

Totally agree, will look for this in an upcoming release, thanks!

#15

I have created pull #15 which fixes this problem.


declaration option is not work when package.json set exports.types

Environment

Node.js:  v20.10.0
pnpm: v8.15.5
unbuild: v2.0.0

Reproduction
See  minirepo.
Describe the bug
The option declaration do not do anything because in the end it will be set according to exports in package.json.

Describe Bug

declaration: false will not work:
import { defineBuildConfig } from 'unbuild'

export default defineBuildConfig({
  declaration: false,
})

When in package.json:
{
  "exports": {
    "types": "./dist/index.d.ts",
    "import": "./dist/index.mjs",
    "require": "./dist/index.cjs"
  },
}

The declaration will be set true if the values of exports contains any files named *.d.(m|c)?ts in package.json.
Also, because of the same reason, declaration: 'node16' can not work too, it is same as true instead of the description in comments.
More details refer to:
https://github.com/unjs/unbuild/blob/bfb4a348421826ad48072ca1cf70973e6caa5b1d/src/auto.ts#L34
https://github.com/unjs/unbuild/blob/bfb4a348421826ad48072ca1cf70973e6caa5b1d/src/auto.ts#L154

Discussion

The problem is whether it is a bug or a deliberate design. I think when declaration is set as false explicitly, it should be false. It is counter-intuitive that set it as false but it still work. So in my option, user-initiated actions should have the highest priority.
Additional context
To fix it, refer to:
https://github.com/unjs/unbuild/blob/bfb4a348421826ad48072ca1cf70973e6caa5b1d/src/auto.ts#L34
If declaration is not undefined, it should use what user provided.
I am glad to provide a PR for that!
Logs
No response

Duplicate #339 #313. Will be fixed in #314 .


Fixed #33742 -- Added id to GeoJSON serializer.

@claudep sorry, I've just pushed an amended version which converts PK to a string, the same way we do further down - I think this may be safer for cases where the PK isn't the default integerfield? Let me know what you think.

I understand not converting the pk could be an issue if the pk type is not natively JSON serializable, but on the other side, forcing integers to strings is not very elegant IMHO. But as DjangoJSONEncoder is already handling several "alternative" types, I think I'd better see your latest changes reverted.

@claudep thanks for the feedback! I've reverted to the original set of changes.

@solarissmoke Thanks :+1: I pushed small edits to docs.

Hi,
Is there any option to keep the previous behavior?
I am serializing one of my model to geojson, but do not want to publish any internal id.
Thanks


NuGet Packages and Dependencies

Environment
-Visual Studio 2015
-.NET 4.6.2 Console Application
When installing a Google .NET package, such as Google.Apis.CloudKMS.v1, it wants to install a bunch of dependencies that don't really make sense. In the .NET Framework, these libraries and associated classes are already available, thus downloading these packages seems completely unnecessary.
System.Net.Http.4.3.3
System.Security.Cryptography.Algorithms.4.3.1
System.Security.Cryptography.Encoding.4.3.0
System.Security.Cryptography.Primitives.4.3.0
System.Security.Cryptography.X509Certificates.4.3.2

Through my research and cleaning, everything still works when the cryptography packages are removed, but there are issues with proxying net traffic without the NuGet version of System.Net.Http, so I left that in.
The main issue is when I update Google.Apis.CloudKMS.v1, I receive the following extremely uninformative error:

If the missing packages are installed, the update works fine. So if I add them in and then update, all is well, but I would prefer to update without having to go through this every time.
So in summary, I think you should review your NuGet configuration for the .NET Framework, and get rid of these unnecessary packages. Or, if they are absolutely required and I am mistaken, clarification would be appreciated as well.

Just to check, which Google packages are you using? All the ones maintained in this repo are Google.Cloud.. If you're only using Google.Apis., we should move this over to https://github.com/google/google-api-dotnet-client (I'm happy to create the new issue for you).
It does seem odd that we have a requirement for System.Net.Http, but I know that things get complicated for that particular packages for reasons I don't understand. @chrisdunelm Can you remember the details of that?
I suspect that System.Net.Http is the source of all the rest of the dependencies.

Looks like this is a Google.Apis issue, so needs transfering to google-api-dotnet-client. Will wait for confirmation from @EatonZ before investigating.

Oops, I guess it goes there. My impression from the readme in that client repository was that it was being discontinued and that this was the successor project.

Your impression is mostly correct. This repo contains the new Google.Cloud client libraries; and is where all (well, almost all) current and future development occurs. However, not all client libraries are available here yet; hence the Google.Apis repo is still maintained.
The Google.Apis.CloudKMS.v1 package you referred is a Google.Apis client library. I'll close this issue and open one in the other repo now.


Allow Infinity, -Infinity and NaN as Decimal values

Change Summary

This PR allows to use Infinity and NaN values for Decimal type.
Related issue number
#1885

Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

Added some feedback on the issue.

Closing this PR, discussion in #1885


Harshini borugadda patch 1

Updated README.md
Added new questions in ## Python

Thanks @HarshiniBorugadda  for your contribution. :tada:
Please star :star: the repository, then I will merge your Pull Request.

Yeah, starred the repository.


Latest and minimum dependency test

This PR is to add new tox environment to test a package against latest released dependent package on PyPI or minimum required version of a package on PyPI
Changes:

Two new tox environment
script to install either latest or minimum required version of dependent azure sdk packages

Can one of the admins verify this patch?


Cerebro has vulnerability

Cerebro has vulnerability,
please contact the author at https://cve.mitre.org/
CVE-2019-19618
or contact me.

Hi @charles2j :)
thanks for the input. Should we move this to email? mail at lmenezes.com

Give me your email address please.

mail at lmenezes.com ;)

Sorry，I can't find your email。

<EMAIL_ADDRESS>at = @ ;)

Vulnerability details have been sent to your email, please pay attention to check

Will the bug be fixed？

which versions are affected?

repaired?

Any public info about this ?


koordlet: cleanup cgroup path utils

Ⅰ. Describe what this PR does

Cleanup useless utility functions in the koordlet.
Move out the functions for cgroup parent generating for extensions.

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[X] I have written necessary docs and comments
[X] I have added necessary unit tests and integration tests
[X] All checks passed in make test

/lgtm
/approve


Fix xpath for menu elements

Because of this PR we now have a different xpath for submenu elements. This PR addresses that changes.
You can see the new intermediate tag element as below:

@ncounter thx. we will merge it after your pr right? I click Systems, under Systems node , i remember it, the magic xpath 😈

@MalloZup  yes, this is the magic xpath we coded together 😉  , and yes, we will merge it ASAP the related PR is merged. I will ping you when it's merged.


Checking out clipboard-agent to vendor/intel/external

Tracked-On: OAM-102872
Signed-off-by: ahs<EMAIL_ADDRESS>Change-Id: I469e25d11291be3edd75336d67d7a2d08b17cb5e

Valid Commit Message
Improper Jira Status, jira status not in ['In Progress','Implemented']

Merged internally, /absp/builders/celadon_smr0_stable-mergerequest/builds/12


Diffie-Hellman Key Agreement Primitives - Validated

Diffie-Hellman primitives - Validated

UIntBig implements unsigned arbitrary-precision integer modular exponentiation (ModPow)

ModPow is core function for anonymous Diffie-Hellman key agreement
Function computes (b ^ e) % m where b=base, e=exponent, m=modulo
Pure Java implementation without relying on Java BigInteger, native code, or 3rd party libraries
Developed for 32-bit architecture for cross-platform code and data compatibility with older and limited capability devices
Designed and implemented from ground up using bespoke algorithms optimised for unsigned multiplication, subtraction, modulo (without quotient), bit shifting, and comparison, using only primitive operators that are common across all target platforms
Validated against Java BigInteger for unsigned integers up to maximum long value
Performance tests showed this software implementation is slower than native hardware but acceptable for intended purpose

Tested using 64-bit exponent and modulo values
Software : 3000-4000ns/call
Hardware : 400-1500ns/call

Investigation into existing libraries showed the following issues which resulted in new Herald specific implementation

32-bit vs 64-bit : All cross-platform libraries are 64-bit only and rely on native code (usually OpenSSL)
License : Most libraries are MIT license
Abstraction : The most promising cross-platform libraries (e.g. Themis) implements additional functions (e.g. Secure Session) over Diffie-Hellman which adds complexity that are not required in Herald
Compatibility : Native functions and data formats on iOS and Android for key agreement are not compatible
Efficiency : Java BigInteger is immutable, thus using significant memory that is not desirable for wearables; Pure Swift libraries (e.g. Swift BigInt) are unacceptably slow (10+ minutes/call for 2048-bit ModPow test); new implementation has been optimised for ModPow function

Validated with iOS implementation for data format and function compatibility
Shall be raising new issue for DH over BLE

Signed-off-by: c19x<EMAIL_ADDRESS>closes #173

Resubmitting after #190 is approved


URL Insertion in CMS Text Editor Causes Modal to Stay Open

If you want to add a URL to a text in the text editor in CMS Layouts, it leads to staying open to the add link modal.
Step to reproduce

Go to the shopping experiences layout with a text editor
Highlight a text
Click the link from the text editor bar
Paste your link to the text field
Click the “Add“ button.

Expected: The link should be saved and the modal should be closed.
Actual: The modal stays open and not closing.
!Screen Recording 2024-05-29 at 14.04.36.mov|width=1678,height=1236,alt="Screen Recording 2024-05-29 at 14.04.36.mov"!

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-36475.
[created from NEXT-36475, comment 486618]


Dependency snippet wrong in README.md

Plugins are never used as deps, turn <dependency /> to <plugin />.

Issue fixed.


new issue

Sometimes I respond too fast for the page to update! If you perform an expected action and don't see a response from me, wait a few seconds and refresh the page for your next steps. @githubteacher

[x] hello** yes**

# #asjsaSometimes I respond too fast for the page to update! If you perform an expected action and don't see a response from me, wait a few seconds and refresh the page for your next steps.


Add mTLS and OAuth 2.0 support for direct connections to Kafka and SR

Resolves #125 #126
Summary of Changes
Adds preliminary support to allow Kafka and SR clients to use mTLS and OAuth 2.0 to authenticate for direct connections.
These changes have been unit tested to verify the expected client configurations are generated.
NOTE: However, those expected configurations have NOT yet been tested against CCloud or CP via integration tests.
Pull request checklist
Please check if your PR fulfills the following (if applicable):

Tests:

[x] Added new
[ ] Updated existing
[ ] Deleted existing

[ ] Have you validated this change locally against a running instance of the Quarkus dev server?make quarkus-dev

[ ] Have you validated this change against a locally running native executable?make mvn-package-native && ./target/ide-sidecar-*-runner

Superseded by #201


Add a link to an image, removes the image

When you add an image, then click the link button, the image is removed or the anchor tag is set before the image.
I now you can add a link when you edit the image, but this isn't obvious.
Jodit Version:  3.2.62
Browser:  Chrome
OS:  Windows
Expected behavior:
Link should be added correctly.
Actual behavior:
Link broken.

test.txt


Segmentation fault on "ng add @angular/pwa"

Command
add
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
I am trying to add a service worker to https://github.com/m-r-g-t/liquality-reversi
Upon running:
yarn
ng add @angular/pwa
The second command throws the following error:
Skipping installation: Package already installed
Segmentation fault
I am on a Debian WSL, using node 8.14.2. I have tried reinstalling, to no avail. Any ideas where I am going wrong?

No response

Please update @angular/cli to the latest version.

Thank you, upgrading the angular CLI to the current latest version (15.2.0) in line with the Angular version has resolved the issue.


cannot install using conda

I tried using conda install -c bioconda truvari
And it first jumped out

Solving environment: failed with initial frozen solve. Retrying with flexible solve.

Then it told me

Found conflicts! Looking for incompatible packages.
Specifications:
truvari -> python[version='<3|>=2.7,<2.8.0a0']
Your python: python=3.8

I am wondering what should I do then

I'm unfamiliar with conda, but it looks like it's trying to install an older version of truvari that required python 2 into your python3 environment. Truvari was updated some time ago to run on python 3.
I actually don't maintain the conda package and I'm unsure of how it got there. The package management I maintain is via PyPi so that the command pip install truvari is available. I can look into where that came from and maybe upload to anaconda. In the meantime, I'd recommend reading this and trying to use the documented installation procedure.

Thanks a lot. Please let me know when you have updated the Python3 version to anaconda.


fix(docs): update grpc output socket name

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind user-interface

/kind content

/kind translation

/kind event

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area blog

/area documentation

/area community

What this PR does / why we need it:
The default grpc unix socket path was changed in 0.33.0 from /var/run/falco.sock to /run/falco/falco.sock and there were still  some stale references to the old socket name.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

Welcome @jgornowich! It looks like this is your first PR to falcosecurity/falco-website 🎉

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jgornowich, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: c0a494b4221c46831fdbd3cab6a20fe7125b1e6d


ThumbmarkJS Collisions

Do we have any testing results on fingerprint collisions ? i.e., two different devices with the same software and hardware with the same fingerprint. If yes, What is the probability of having such a collision?  Has anyone faced such issues?

Hi.
It depends on the browser:

Chromium: will probably be rather unique, but browser updates & changing settings will result in a different ID.
Firefox: less fingerprint-able than Chromium, but given its low marketshare it may still be okay for small amounts of traffic.
Safari: No chance. You'll likely only get a couple possible fingerprints. Apple is serious about containing tracking.

ThumbmarkJS seems to favor stability and persistence, so it tends to collide a lot versus say CreepJS.
This is a self plug (sorry!) but I'm working on a project to address these issues and currently have a prototype API that seemingly works very well on Chromium. Safari remains elusive, at least for now.
You can look at testing the API for free for now: https://overpoweredjs.com/
Again, sorry for the self plug. I require some traffic for study and thought this may help someone.

@Joe12387 no harm in a bit of self-promotion :)
I've been thinking about extending this project with a back-end service for obvious reasons too, but the library gets 12 million hits per month right now, and I'm afraid making it that good would also mean service costs.
Though, if the back-end was also an open-source component, perhaps people could host it themselves easily.
I'll close this issue, but I wouldn't mind linking to this project in the Readme.


Live preview redirects to login page

Prerequisites
Please answer the following questions for yourself before submitting an issue.

[x] I am running the latest version
[x] I checked the documentation and found no answer
[x] I checked to make sure that this issue has not already been filed
[x] I'm reporting the issue to the correct repository (for multi-repository projects)

Expected Behavior
I can view the dashboard in the live preview.
Current Behavior
https://www.creative-tim.com/live/material-dashboard-react-nodejs flashes the dashboard briefly and then goes to the login page without changing the URL. The dashboard button on this page, which links to https://www.ctim.udevoffice.com/demos/material-free/admin/dashboard, flashes the dashboard briefly again and returns to the login page, all without changing the URL in the browser.
https://www.creative-tim.com/live/material-dashboard-react-nodejs/dashboard is a 404 error.

I have the same problem.
What was the solution?

@kaazkoo Never got a solution. ¯_(ツ)_/¯ They've never responded to a single issue on this repo, looks like. I guess they don't use GitHub for collaboration, just as a place to toss their code so they can call it "open source". Oh well.

@tywmick
Given that it's now over a year you asked, it may not be relevant for you anymore but, I thought I'd provide you closure and tell you how I fixed it :-)
Not sure what may be the root cause, update or else. I fixed it by modifying the root folder app.js
The issue is linked to the sessions handling with the Redis server. The Redis server wasn't registering ANY sessions. And it seems to have been omitted - or the original implementation logic doesn't work anymore. Any how...
First you need a client to exchange with the Redis server -- Squeeze this CONST between cookieParser and session

const redis = require('redis');

and under CONST RedisStore add

const redisClient = redis.createClient();

get rid of this line --> const redisStore = new RedisStore(redisStoreConfig);
and implement it like this instead, so that redis stores the client session not the config.
app.use(
session({
store: new RedisStore({ client: redisClient }),
Works perfectly now.
JF

@kaazkoo Hi. I just faced the same problem and read the solution you provided above but it does not work on my end. Did you face any issues after that with this dashboard? Please share any solution if you know.
Thank you in advance
Lyba


Exception after player connected to dedicated Forge server with Cubic Chunks.

A several exceptions catched after player successfully connect to dedicated Forge server with Cubic Chunks build 616 (MC1.11). Server works fine and ban player for floating too much. At player side no chunks rendered. Only sky and clouds.
Client side log
FML Server log

You need to set world type in server.properties to CustomCubic or VanillaCubic

I was wrong, sorry, turns out this is the cause:
[14:39:18] [Server thread/INFO] [cubicchunks/]: Skipping world net.minecraft.world.WorldServer@3d899a82 with type cubicchunks.world.type.CustomCubicWorldType@21352fa2 due to potential compatibility issues

So I'm looking at a code and could not understand where you set that Predicate...

It's a special forge thing - a proxy. A it's set reflectively by forge depending on the physical side, look at @SidedProxy javadoc.

After #225 fix compiled versions of server shut itself down after player connected due to abnormal long tick. Player successfully receive chunks and entity data and able to walk and look around but it seems that server is not ticking.
Crash reports and logs:
crash-2017-06-17_15.19.32-server.txt
crash-2017-06-17_15.49.30-server.txt
fml-server-3.txt
fml-server-latest.txt

Closed with #225


"

https://github.com/chaoss/wg-common/blob/master/focus-areas/who/contributors.md
The evolution working group has a question if repository authors are the same thing as "commit authors". We suspect so, but want to make sure.

@sgoggins we're not sure what this is - is this still a question for common?


Request to increase Disk space

Humble request  to PDW team to increase disk space so that docker image > 5Gb be able to be installed.
Instead of now allowing to create multiple PWD instance , why not allow one instance with more combined disk space ?
Appreciate if this can be considered as many docker images especially data science related docker images  e.g : cloudera, hadoop, and jupyter-spark could not be install into  PDW because of images size after been deflated exceeded 5GB.

@ManoMarks ?.


Update Kubebuilder go plugin

Operator currently uses go.kubebuilder.io/v2 plugin which is already deprecated, would be great to update to v3 or v4.

[Deprecation Notice] This version is deprecated and is no longer scaffolded by default since 28 Apr 2021.The go/v2 plugin cannot scaffold projects in which CRDs and/or Webhooks have a v1 API version.Be aware that v1beta1 API for CRDs and Webhooks was deprecated on Kubernetes 1.16 and areremoved as of the Kubernetes 1.22 release. Therefore, since this plugin cannot produce projects thatwork on Kubernetes versions >= 1.22, it is recommended to upgrade your project to the latest versions available.

Two ways to implement:

create a new v3 project and copy over the API and the reconciliation code, see https://book.kubebuilder.io/migration/legacy/migration_guide_v2tov3
updating all the files manually, see https://book.kubebuilder.io/migration/legacy/manually_migration_guide_v2_v3#migration-from-v2-to-v3-by-updating-the-files-manually

hey @Haleygo , Can i work in this?

I think we should go with second solution and use manual update.


Added a new login page

Made a login page using HTML CSS and JavaScript.

I have made this contribution for HacktoberFest 2021.
Please review my pr #74 @Karl-LoginRadius also label the hacktoberfest-accepted tag.
Thank you


Style the footer for the document producer preview. Add the project name to the footer.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2920  👈
#2919
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nickgraz and the rest of your teammates on  Graphite

Merge activity

Jul 31, 1:53 PM EDT: @nickgraz started a stack merge that includes this pull request via Graphite.


Add Praful to Codeowners

Signed-off-by: Haytham Abuelfutuh<EMAIL_ADDRESS>TL;DR
Add Praful to codeowners
Type

[ ] Bug Fix
[X] Feature
[ ] Plugin

CC @pmahindrakar-oss.


Figure out how to do testing

Testing will be interesting. There has to be a good balance of mocking and real integration (ideally). Start small and see where it goes

I don't think there's a real good way to perform an integration test for the lambda proper. We might be able to abstract it away and run a dummy server to mock calls, but that's about it.
With the MVP2 refactor, I intend on being very thorough with testing the main server code, especially since I intend to write it in a language I am very familiar with.

This will be partially done with #47 at least in the server side. Not sure how much can actually be done for true automated integration testing

This will be covered once we rewrite the song queue lambda code in Scala and add localstack for integration testing. We should be fine. Closing this since it should be covered


Create user friendly error if remote oca fails

Given the user starts the app without having connection to the oca repository:
if the wallet fails to load the oca index file then the user will be presented with an error message.
Given the user is in the application with a loaded oca index file but no connection to the oca repository:
if the wallet fails to load the branding for a given credential then the user will be prompted with an error message once.

Hey @wadeking98
As a side question, may I ask if there is any guide I can follow on how to set up OCA from a remote repository or any pointers around this would be appreciated, thanks! 🙌


Change step-size and max-epochs to get higher performance

Hello,
Thanks for this implementation.
Recently, I ran this repo with step-size=100 and max-epochs=2000 and got higher performance.
For 5way1shot train, I got 50.30% and for 5way5shot train I got 67.11%

Hello,
Training for more epochs will get higher performance, but is relatively marginal while costing much more time.
Thanks for your observation and results.


Feature/55 about app dialog

Added about app screen related elements from #55

Current coverage is 0.00% (diff: 0.00%)

Merging #97 into develop will not change coverage

@@           develop   #97   diff @@
====================================
  Files            1     1
  Lines           27    29     +2
  Methods          0     0
  Messages         0     0
  Branches         0     0
====================================
  Hits             0     0
- Misses          27    29     +2
  Partials         0     0

Powered by Codecov. Last update fd98b20...b2dc821


Any crossover with tantivy?

Hi, Elasticsearch is essentially a lot of infrastructure built around Lucene, does Tantivy (https://github.com/tantivy-search/tantivy) play any role in your project?

Hi @stephanbuys. No, there's no crossover with Tantivy at the moment. It was created some time after I had already begun building my own search engine.


module request: usb-modeswitch module

Describe the bug
I bought a usb wifi adapter that (seems to) require the use of usb-modeswitch. Otherwise, it just appears as a USB MSD.
It would be nice to have a services.usb-switchmode.enable, etc.

looks like we have one:
https://github.com/NixOS/nixpkgs/blob/27746002e1119c5871424bffec11fdbcb0644c4c/nixos/modules/hardware/usb-wwan.nix#L15
it also applies to regular wifi adapters as well. I will leave this open until I've added usb-modeswitch to this modules description so its more discoverable.

I still think hardware.usbWwan.enable is a bit hard to discover, but it is there and does work.


Fix cli init mkdir missing recursive: true and error message not showing

Apperance:
$ nue does nothing but exits
Steps to reproduce:
cd create-nue/simple-blog
nue  # here nue is linked from my local nue directory<EMAIL_ADDRESS>- 310d51f)

Before fix:

After fix:

Super. Thanks


Handle transfer to cupy view

When trying out host-to-device transfer with the syntax introduced in #2079, cupy_array[:] = numpy_array, I noticed that it gives the wrong result if cupy_array is a non-contiguous view of a contiguous cupy array. We use views to support pitched device memory.
This pull request makes it raise a ValueError instead. In future, we should check if the strides looks like pitched memory and use cudaMemcpy2D in that case.

As a side note for the future, one of the things I am concerned is that cuda only offers pitched memory copies for 2 and 3d (I might be wrong here).
But the general Nd case will require us to do multiple memory copies.

I think we should error out if it requires more than one call to cudaMemcpy. Then it might be more beneficial to do a device allocation + a linear host-to-device copy + unpacking on the device side by explicitly doing cupy_array[:] = cp.asarray(numpy_array)

Read the Docs build failure seems unrelated to this pull request, reported at https://github.com/readthedocs/readthedocs.org/issues/7445

I think the RTD CI is down for a few days, so don't worry about it.

I think you need to merge with (or rebase onto) master to fix Travis's error. The module util was renamed to _util (#3779).

Thanks for the heads up. What I don't understand though, is how travis could have gotten that change in, when it was testing my branch. Let me try the travis commands locally.

What I don't understand though, is how travis could have gotten that change in, when it was testing my branch.

I found the cause now. Travis doesn't test my branch head but instead does git fetch origin +refs/pull/3928/merge which is a preview of what a merge with master would look like. I shall do the merge then :)

Jenkins, test this please

Jenkins CI test (for commit 344b714d090aa25b8523abc8c60d6ba6401fb3b3, target branch master) succeeded!


How to register app.UseExceptionless("key") in .net core2.1 IHostBuilder?

.net core2.1 IHostBuilder does not have IApplicationBuilder, how can I register the service to the application?

Both 2.0 and 3.0 have public void Configure(IApplicationBuilder app) in Startup.cs. We do need to make some extensions for IHostBuilder.


CLOUD-881 handle default resource deletions

@biharitomi @doktoric
Template and blueprint default resources are handled the same way as networks and security groups. Once you delete a default one it won't bring back after a page refresh.

Jenkins build failed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1439/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1440/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1441/


Problem with making animations with VisIt due to using Dubiner basis

Hello,
I am currently working on a project that involves approximating the solution as a linear combination of orthogonal basis functions on triangular meshes (I use the Dubiner basis) instead of the standard Gauss Legendre basis.
I am currently testing my code with the DG linear advection equation in example 9. I want to create an animation of my solution from time t = 0 to t = 0.1 seconds. So I played around with VisIt in order to make a video. I set the visit flag to true in order to produce Example00000x directories and mfem_root files to create simulations in VisIt. I did the usual things, i.e Pseudocolor -> selected solution. Then Operators -> Transform -> Elevate and then selected Draw. However, it gave the error:
Verification failed: (0 <= b_type && b_type < 6) is false: unknown BasisType: 6
 ... in function: static int mfem::BasisType::Check(int)
 ... at line 39 of file: fem/fe_coll.hpp

After seeing this, I switch my basis functions back to Gauss Legendre (default) basis. With that, I was able to create the animation (note that the solution is wrong because my problem expects an orthogonal basis on triangular mesh).
Hence I suspected that this is an issue from adding and using my implementation of the Dubiner basis. In fe.hpp, in the BasisType class, I added a 6th basis type, Dubiner, and so b_type should be < 7 instead of 6. I tried commenting out the MFEM_ASSERT statement in BasisType::Check(int b_type) but it still didn't work.
Any clue of how to fix this?
Thanks in advance!
Regards,
Henry

Depending on your goals, another option could be to do convert to a known basis using GridFunction::ProjectGridFunction just for visualization.

Hello,
Thanks a lot!
Regards,
Henry


Always trigger, because now progress is capped at 0.

https://github.com/okiba-gang/okiba-components/blob/2bf5ebaa13c33ae6eaada0073c3c565e2c9f2cd9/packages/view-progress/index.js#L73
Dirty fix: const isInside = progress > 0 && progress <= 1

https://github.com/okiba-gang/okiba-components/blob/master/packages/view-progress/index.js#L72
Values are mapped and not capped so the value can be minor of 0 and major of 1 ;)
You can see that it works fine here (it remove correctly the css class) ;)

https://okiba-gang.github.io/okiba-components/view-progress.html


Adding custom URL for Instagram images using instafeed.js

Hi! I'm trying to achieve this: http://www.sriajith.info/blog/adding-custom-url-for-instagram-images-using-instafeed-js, however, I can't get the templating part to actually work.
Any jQuery gurus have any ideas on how I can achieve this? Would really like to be able to my link my Instagram images to custom URLs :) thank you!!

Hey @juliewampler! It sounds like your question would be better suited for Stack Overflow. Stack Overflow is the best place for general programming/library usage questions.
If you think this might be a bug with Instafeed.js itself, don't hesitate to re-open the issue!


Allow :form-params for :put requests also.

This patch will allow :put requests to also take a :form-params item as PUT requests can contain a body just like POST requests.
(Faced no way to send body to a PUT endpoint, on skytap API, so I patched this).

Thanks for adding this, I've merged it.

Great. Any hint on when this would be available on clojars?

I'm planning on doing a release today, so should be very soon :)

Sweet. Thanks a lot.
2012/3/9 Lee <
<EMAIL_ADDRESS>

I'm planning on doing a release today, so should be very soon :)

Reply to this email directly or view it on GitHub:
https://github.com/dakrone/clj-http/pull/51#issuecomment-4417551

Okay, I've release clj-http 0.3.3 with this fix in it.

You are quickety quick man. Thank you :)
--
:Shrikant Sharat, on his `droid
On 9 Mar 2012 20:41, "Lee" <
<EMAIL_ADDRESS>wrote:

Okay, I've release clj-http 0.3.3 with this fix in it.

Reply to this email directly or view it on GitHub:
https://github.com/dakrone/clj-http/pull/51#issuecomment-4417791


Modify docker version in docker-compose.yml file

What this PR does / why we need it?
replace latest version of docker to 0.2.15
Any background context you want to provide?
If someone fork or clone this project, they can use the latest version of docker then it causes an error.
But I have a question about this version issue.
Can we use v0.2.15 in this project or just apply another version?
What are the relevant tickets?
Checklist

[x] Added relevant tests or not required
[x] Didn't break anything

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@hackerwins I must have forgotten it. Thanks for checking this issue! Have the happiest Chuseok holiday 🙋🏻♀🙋🏻♀

@gollumnima 🙋🏻♀🙋🏻♀


Update eventsources.md noting varying JSON key case

Add note regarding varying JSON key case
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi Peter. Thanks for your feedback. The content in this topic has been incorporated into topics for each service in the Working with Other Services chapter.


Fix shadow image_tag bug in publish_multiarch_manifest

Signed-off-by: Gong Su<EMAIL_ADDRESS>

Jenkins Linux amd64 Build #96 [push] Fix shadow image_tag bug... started at 21:05

Jenkins Linux s390x Build #328 [push] Fix shadow image_tag bug... started at 22:06

Jenkins Linux s390x Build #328 [push] Fix shadow image_tag bug... passed after 42 min

Jenkins Linux amd64 Build #96 [push] Fix shadow image_tag bug... passed after 52 min


Fix of randomized depth each width

Fixes #13
We need to change a number of op as depth each width.
I fix depth randomizing each width.

@googlebot I signed it!

@googlebot I signed it!

Hi, @normster
Would you review this PR? And if it is clear, I want to merge this PR.
Regard,


Write valid JSON from kubectl cluster-info dump

What would you like to be added:
kubectl cluster-info dump writes out cluster info in JSON format, followed by one line:
Cluster info dumped to standard output

I would like that last line written to standard error
Why is this needed:
If the diagnostic is written to standard error, the output becomes valid JSON.
/sig cli

The relevant code is https://github.com/kubernetes/kubectl/blob/0555a86aaff9f0ba20dbc066dfaa1891222def87/pkg/cmd/clusterinfo/clusterinfo_dump.go#L292-L294

Precedence for using STDERR for verbosity
https://github.com/kubernetes/kubectl/blob/08c1f25495df730ea63fa7bb6b282e08ac4cd74e/pkg/cmd/plugin/plugin.go#L136

If dest is stdout, can we just suppress this message entirely?
Regarding the precedent for using stderr for verbosity, I actually just “fixed” that to use stdout 😆 in a recent PR, because I thought it was a mistake.
Kubectl does have a verbose flag that could be used for extra verbosity, and some commands make better use of that than others.

If dest is stdout, can we just suppress this message entirely?

Fine by me!

/assign

/area kubectl
/kind feature


First level of cascading memoization is broken when more props are passed

Hello,
Not sure it's an issue but want to highlight this small problem we faced recently.
So imagine you have two selectors:
const getSchema = createSelector([(state) => state.rawSchema], (rawSchema) => {...})

const getItem = createSelector([getSchema, (state, itemId) => itemId], (schema, itemId) => {...})

as a result whenever getItem is called it also calls getSchema with arguments: state and itemId which leads to invalidation of args memoization.
Usually overhead might be unnoticeable because second level of caching still works but for some 'hot' selectors we see some significant numbers.
Here is an example for one of our hottest selectors after reloading the page. And every dispatch generates few thousands of dependency recomputations

Right now I can see 3 ways how it can be fixed in userland:

just inline selector everywhere to make sure it's always called with required params. Leaves responsibility on consumer
add some utility like const acceptStateOnly = (selector) => (state) => selector(state) and wrap such hot selectors at place where they are defined
customize argsMemoize to care about first argument only

I don't really like them as they are pretty fragile so I wonder if it's something that can be improved on library side, e.g. by comparing length of incoming arguments with length of saved arguments or by stricter types or by advanced input stability check
Thanks in advance 🙇🏻
P.S. also the issue is so noticeable for us because we used to pass props as object  to selectors like useSelector((state) => selector(state, {prop1, prop2})) which basically leads to args cache invalidation on every react render

That sounds like things are working as expected:

All arguments get passed to all input selectors
Any new reference causes the reference comparisons to fail and that level of memoization to be recalculated

So yes, passing a new object reference to a selector is not a good idea. Have you tried passing them as separate arguments instead? selector(state, prop1, prop2).

Have you tried passing them as separate arguments instead? selector(state, prop1, prop2).

That's what we are migrating to right now. But this still doesn't solve the original issue. I understand why it works like that but many devs at first were a bit lost when I told them about first level of cache cascade and that prop selectors ideally should be written like
createSelector([(state) => getSchema(state), (state) => getSmthFromState(state), (state, prop1) => prop1], () => {})

instead of passing input selectors directly
createSelector([getSchema, getSmthFromState, (state, prop1) => prop1], () => {})

So what do you think, does it deserver some effort from library side? One more input dev check, note in docs or a solution?

I don't think there's anything we should change here.
Relying on function.length is always tricky, and it's not something I'd want to try to make use of in this case.

Got it, thanks for your opinion 🙇🏻
Closing the issue then


Incompatible with latest Intellij IDE builds

Hi,
first of all, thank you for the plugin, it's awesome.
Secondly I am using IntelliJ IDEA 2023.2 and it says:

Plugin 'Logstash Config Files Support' (version '0.8.1') is not compatible with the current version of the IDE, because it requires build 223.* or older but the current build is IC-232.8660.185

Could you please add support for newer versions?
Thanks

See https://github.com/ikorennoy/logstash-intellij-plugin/pull/41

Hi @nWmCZ  - I fixed the issue via https://github.com/ikorennoy/logstash-intellij-plugin/pull/41
Feel free to pull and build locally and "install from disk"

Thank you, it works.

The new version is available in the JetBrains Marketplace.


Fix Read The Docs

...does what it says on the tin.

Fixes RTD builds
Renames the main testing workflow action to "Tests"
Adds tests and docs build badges to the README
Updates the release doc file to be reST and makes the formatting/language similar to other docs in the library

Fixes #456

Hey @thornycrackers, @rachelannelise, or @lmontopo. I see you on #505 pretty recently. Mind giving this a quick gander? I fixed it to read the docs works again, as do the badges on the README.
I reformatted the recent entry a bit as well so that it builds correctly.

I ran a build with PYTHONPATH=$(pwd) sphinx-build -M html ./doc ./dist and everything seemed out build correctly with no warnings so :+1:


Relative offset for grammar source

In peggy-test and peggy-tag, I'd like to be able to pass in a grammar location along with the grammar source, so that offset, line, and column in reported errors start at something other than zero.  This is useful when the grammar is embedded into a larger document, and only a portion of that larger document is passed into peggy.
Proposal:

Add a grammarLocation to the API.  Carry it around all of the places grammarSource goes.  It will have the same shape as that returned by location() for easily passing it through from a wrapper grammar.  Only the start portion is likely to be used, however.
Do not apply the offset until the very last moment, on output in format.  Otherwise the arrow pointing to the error will be in the wrong place.
Default offsets are all zero.  Check for off-by-one errors in line, column, and offset of both start and end.

Compatibility:

Will break anyone currently using grammarLocation as a parameter to their grammar.  We should document that the grammar* namespace is for internal use.

I'm going about this a slightly different way that changes the interface a lot less.  There's a special type you'll be able to pass in for grammarSource, called GrammarLocation, which keeps the offsets and the name of the source file as text.


Add wait async with generic argument

Create branch from main
issue-45-add-wait-async-with-generic-argument


Ignore thirdparty library errors in clang-tidy

Hi,
we have written cpp code which includes the boost library and while running with clang-tidy,we are getting an error which i am unable to fix since the error is coming from the boost library.
However, we have used some flags in .clang-tidy file like
HeaderFilterRegex: '^(?!.*external).*'
Error:
external/boost/boost/assign/list_of.hpp:455:29: error: no matching constructor for initialization of 'boost::assign_detail::generic_list<std::pair<const std::basic_string_view<char16_t, std::char_traits<char16_t> >, std::shared_ptrsabre::base::parsers::ContextSAXHandler > >::Ty' (aka 'std::pair<const std::basic_string_view<char16_t, std::char_traits<char16_t> >, std::shared_ptrsabre::base::parsers::ContextSAXHandler >') [clang-diagnostic-error]
this->push_back(Ty(boost::forward(u0), boost::forward(u1), boost::forward(us)...));

Hi @ananta-code,
Thank you for reporting this problem.
I just want to make sure that you know what HeaderFilterRegex does.
HeaderFilterRegex :   Regular expression matching the names of the headers to output diagnostics from. Diagnostics from the main file of each translation unit are always displayed. Can be used together with -line-filter. This option overrides the 'HeaderFilter' option in .clang-tidy file, if any.
In this case, regex needs to include all your headers (except boost) to output diagnostics from.
Maybe you can try checks related to Boost library boost-
Let me know if this answer helped you.
Best regards,
Marina

checks related to Boost

Hi @mariru27 ,
my code is
`#include "retailing/mixer/ndc_parser/context_handler/party.h"
#include "base/parsers/ignore_sax_handler.h"
#include "retailing/mixer/ndc_parser/context_handler/sender.h"
#include <boost/assign.hpp>
namespace sabre::retailing::mixer::ndc_parser::context_handler {
PartySAXHandler::PartySAXHandler(OutputExtractor&& outputExtractor)
: base::parsers::ContextSAXHandlerWithMap(boost::assign::list_of<handlers_type::value_type>(
"Sender", SenderSAXHandler::create(outputExtractor { return outputExtractor(); })))
{}
}  // namespace sabre::retailing::mixer::ndc_parser::context_handler
`
i have an boost import ..the error i am getting has external and i mentioned this in the regex. even i also tried HeaderFilterRegex: '' and HeaderFilterRegex: '.*' still it is not working

Can you try to add just one header from your project in HeaderFilterRegex to see if the error still appears?
For example: HeaderFilterRegex: 'MyTestHeader.h'

HeaderFilterRegex: 'MyTestHeader.h'

i tried looks like it is not working
.clang-tidy:
--- Checks:          'boost-*,bugprone-* --bugprone-narrowing-conversions,cppcoreguidelines-* --cppcoreguidelines-avoid-c-arrays,clang-analyzer-*,modernize-* --modernize-use-trailing-return-type,performance-* --performance-unnecessary-copy-initialization --performance-unnecessary-value-param,readability-* --readability-magic-numbers,hicpp-* --hicpp-no-array-decay,concurrency-*' WarningsAsErrors: '*' HeaderFilterRegex: 'diagnostics.cpp' FormatStyle:     file ...
Cpp file:
`#include "retailing/mixer/ota_parser/context_handler/diagnostics.h"
#include "retailing/mixer/ota_parser/context_handler/diagnostic.h"
#include <boost/assign.hpp>
namespace sabre::retailing::mixer::ota_parser::context_handler {
DiagnosticsSAXHandler::DiagnosticsSAXHandler(OutputExtractor&& outputExtractor)
: base_type(boost::assign::list_of<handlers_type::value_type>(
"Diagnostic", DiagnosticSAXHandler::create(std::move(outputExtractor))))
{}
}  // namespace sabre::retailing::mixer::ota_parser::context_handler
`

@ananta-code You've given a cpp to the HeaderFilterRegex option, that is for headers.

Is this not the same as #589 ?
I would also love to exclude third party libraries from diagnostics. I have no control over their code style / code conventions, as such I should only be bothered about my own stuff.
Tried using a HeaderFilterRegex that matches anything not a third party library, yet diagnostic is still run on them and they produce output. Although I have no idea what that regex is actually applied to (e.g. header file names, full path, something else?).

Hi @Sil3ntStorm,
Thank you so much for sharing your concerns and providing detailed information about the issue you're facing. I completely understand your frustration with the current situation and the inconvenience caused by the diagnostic output from third-party libraries
We will investigate this problem and work towards finding a solution
Kind regards,
Marina

Hi @Sil3ntStorm,
Can you help us by providing a small project with now behavior and how it should work?
Kind regards,
Marina

It would appear that my HeaderFilterRegex solution does not work because apparently clang-tidy does not support negative lookaheads in regular expressions.
@mariru27 I will see what I can do over the weekend.


J F: Watch fordcreditcentre.com

J F requests the watch of the watch_keyword fordcreditcentre.com. See the Metasmoke search here and the Stack Exchange search here.

fordcreditcentre.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Coverage remained the same at 65.763% when pulling 53988dbc38cef605bb0f49c0d08c069a2aa4e00d on auto-blacklist-1527504501.2539907 into 8ca99aa45c74659a30d992f24a8baa41787ebce0 on master.

!!/approve


[Spanish] localize 'Digital Certificate'

Localize the content/en/digital-certificate.md" document to Spanish

@electrocucaracha, can I work on this?


HEVC ENC:10bit support

v1:
add support P010 input format
add HEVC 10bit encoding
Signed-off-by: Pengfei Qu<EMAIL_ADDRESS>

pengfei busy with other things, dongping will help to rebase this at #61


PHP configured/built with ZTS Zend Thread Safety

When PHP is configured and built with ZTS - Zend Thread Safety, it changes the PHP_EXT_DIR from /usr/local/lib/php/20180731 to /usr/local/lib/php/20180731-zts.
When Synth begins to build a port that depends on a PHP extension it builds the dependent extension and correctly installs it into 20180731-zts/ but then incorrectly searches for the dependent extension in 20180731/ and the build fails
===>   php73-xmlreader-7.3.1_1 depends on file: /usr/local/lib/php/20180731/dom.so - not found
===>   Installing existing package /packages/All/php73-dom-7.3.1_1.txz
Installing php73-dom-7.3.1_1...
Extracting php73-dom-7.3.1_1: .......... done
===>   php73-xmlreader-7.3.1_1 depends on file: /usr/local/lib/php/20180731/dom.so - not found
*** Error code 1

Stop.
make: stopped in /xports/textproc/php73-xmlreader

This happens with both PHP 7.2 and 7.3 and can be quickly replicated by configuring PHP with ZTS then running synth just-build textproc/php73-xmlreader which depends on textproc/php73-dom
textproc___php73-xmlreader.log
textproc___php73-dom.log

wouldn't this be a problem with the php framework? (as opposed to a problem with synth code)

to be clear, there's no difference building from the ports tree directory and using portmaster

I'm not saying it's not reproducible.  I'm insinuating the php maintainers the ones at fault.

see php.mk
#
# If you are building PHP-based ports in poudriere(8) with ZTS enabled,
# add WITH_MPM=event to /etc/make.conf to prevent build failures.

did you try adding WITH_MPM=event in the [profile]-make.conf ?

It all works when building directly from ports tree.
It all works when building/installing/updating with portmaster.
It does not work correctly when Synth attempts it
/etc/make.conf and /usr/local/etc/synth/LiveSystem-make.conf
WITHOUT_X11= yes
DEFAULT_VERSIONS+= php=7.3 python=3.7 python3=3.7 perl5=5.28 mysql=8.0 ssl=openssl111

failure ocurrs at the build depend phase.
logs attached in original post
I have been working on this issue on my own off and on for months now. It has persisted across multiple version of FreeBSD and PHP. The problem only occurs with Synth tries to build.

It all works when building directly from ports tree.
It all works when building/installing/updating with portmaster.

which is irrelevant because by design both environments are dirty and non-reproducible between users
All this means is synth is catching a developer error.
The WITH_MPM hack should fix your issue.  It's a hack they added to the php.mk  because somebody realized it's broken.

The problem only occurs with Synth tries to build.
Please understand that one possibility is synth (and apparently poudriere) are correct and the framework is broken for proper environments.  Don't shoot the messenger.

did you try adding WITH_MPM=event in the [profile]-make.conf ?

This worked. Issue resolved. :)
I guess you correctly surmised that the primary reason I configured PHP with ZTS is to accommodate apache event MPM.
I'm sorry, it did appear to me to be pointing to Synth. As you say, of course Synth's environment is pristine every time.
Thank you so much for your help


isRead in SMSMessage

Why is there a separate isRead for SMSMessage? A regular message like "WhatsApp" could also have this field.

I don't know if there is any specific reason for it to be in SMSMessage specifically rather than in Message.
I believe it originally came from mapping the Hansken model in and Hansken has 'read' as a property of  textMessage.
I would agree that it seems like it would be appropriate to move to Message.
If nobody disagrees we can add an issue to the UCO tracker proposing moving isRead from SMSMessage to Message property bundle and then deleting the SMSMessage property bundle since isRead is its only current property.

Agreed.


Alpine v3.12 is not supported by AWS

Hi, Recently I noticed that httpd:alpine was upgraded to v3.12, but this version is not yet supported by AWS, so I'm not able to run my containers anymore. I don't see a way to select a previous version of Alpine by keeping httpd in the latest version (2.4.43).
Is there any way to use httpd 2.4.43 with Alpine v3.11?
This is the error I'm getting from AWS: UnsupportedImageError: The operating system 'alpine' version 'v3.12' is not supported.

To clarify, this is when trying to scan the image with ECR, not when trying to run, right?  There shouldn't be any restrictions on what you're able to run on AWS, especially not OS version restrictions.
If you want to get the content digest of the older Alpine 3.11-based image, you probably want to check out https://github.com/docker-library/repo-info/commits/master/repos/httpd/remote/alpine.md, and I believe https://github.com/docker-library/repo-info/commit/c672430802b36d6c36a555eee6f908e1b6b3c151#diff-23f311476f33e5bdc059f2522f929ed9 in particular is probably what you're after:
$ docker pull httpd@sha256:30a98fa70cb11a4b388328c8512c5cd2528b3c0bd4c4f02def164f165cbb153e
sha256:30a98fa70cb11a4b388328c8512c5cd2528b3c0bd4c4f02def164f165cbb153e: Pulling from library/httpd
cbdbe7a5bc2a: Already exists
d675277ceb41: Pull complete
05d6ddf7a817: Pull complete
0da22ef96744: Pull complete
5f950d770af2: Pull complete
Digest: sha256:30a98fa70cb11a4b388328c8512c5cd2528b3c0bd4c4f02def164f165cbb153e
Status: Downloaded newer image for httpd@sha256:30a98fa70cb11a4b388328c8512c5cd2528b3c0bd4c4f02def164f165cbb153e
docker.io/library/httpd@sha256:30a98fa70cb11a4b388328c8512c5cd2528b3c0bd4c4f02def164f165cbb153e
$ docker run --rm httpd@sha256:30a98fa70cb11a4b388328c8512c5cd2528b3c0bd4c4f02def164f165cbb153e cat /etc/os-release
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.11.6
PRETTY_NAME="Alpine Linux v3.11"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://bugs.alpinelinux.org/"

Awesome!, thanks @tianon that's what I was looking for, regarding the clarification, you are right, ECR is not able to scan the image and due to internal company policies that specific images are being blocked from the registry.

Thanks! The issue was solved by using this image: httpd@sha256:30a98fa70cb11a4b388328c8512c5cd2528b3c0bd4c4f02def164f165cbb153e


Create pushing_packages.md

Added a more elaborate example on how to push packages.

Hi, thanks for opening this pull request. I'm concerned that this script is a little too specific for most users. The * wildcard feature on dotnet nuget push is probably enough for most people. What are your thoughts?

Hi, thanks for opening this pull request. I'm concerned that this script is a little too specific for most users. The * wildcard feature on dotnet nuget push is probably enough for most people. What are your thoughts?

Well the snippet is definitively useful because it deals in one place with many of the typical problems encountered when pushing nugets:

detect a test has failed,
clean, build, pack "Release" variants of all solution projects,
find the above and push to BaGet,
configuration steps for uploading nugets when the repository is protected with a key,
just gives a general idea and a starting point for many common nuget related matters, such as how to skip packing a project and creating and pushing symbol packages which is typically an afterthought.

dotnet nuget push definitively does not cut it most of the time, or I would not go through the hassle. For example, it might push debug variants if we are not careful, then there is the hassle with the key, which you have to find online, and just don't get me started on the star *, I wasn't even aware it exists.
To conclude, BaGet will get loads more stars just because of this script ;)

Your script is definitely useful, but I don't think it's a good fit for BaGet's documentation. I'd prefer to document the basics geared towards beginners. For example, how do I upload my first package? How do I import packages from some other server? How do I use MySQL?
Your script is more for advanced users that are looking for best practices. This would make for a great blog post though!

I will make a gist instead.


[Bug] 消息截断机制存在问题

Bug Description
Because models like Claude have strict definitions for the roles of messages in the message queue, such as the first message can only be from the system or user, and user and assistant must strictly alternate, the functional errors in the message queue controlled by NextChat were exposed by attaching the number of historical messages and the length of historical messages.
① The minimum unit of attaching historical message count is messages that do not distinguish roles, which means that once a user message at the head of the queue is popped out, the head message of the message queue will be the role of the assistant. A better solution is to use dialogue turns as the smallest unit, if the length exceeds the limit, the head of a dialogue turn should be popped out simultaneously, that is, a group of user and assistant QA messages should be discarded.
② max_tokens was originally the maximum number of replies for large models, but in the program, it is also used to determine whether to compress the message queue, which, on one hand, combined with the situation in ①, causes problems with the message queue, and on the other hand, it also affects the use of long-context models.
由于 claude 等模型对消息队列的角色有严格的定义，比如第一条消息的角色只能是system或者user，user和assistant必须严格交替，所以nextchat原先通过附带历史消息数和历史消息长度来控制消息队列存在的功能性错误被暴露出来。
① 附带历史消息数的最小单位是不区别角色的消息，这就导致了一旦队列头部的user消息被弹出后，消息队列的头部消息会是 assistant 的角色。一个更好的解决方案是以对话轮次为最小单位，如果长度超限，则应该将头部的一轮对话同时弹出，即抛弃一组user和assistant的QA消息。
② max_tokens 本是大模型的最大回复数量，在程序里却也被用来判断是否压缩消息队列，一方面与情况①叠加导致消息队列出问题，另一方面也会影响长上下文模型的使用。
{
  "error": {
    "message": "messages: first message must use the \"user\" role (request id:<PHONE_NUMBER>494530153478024102122)",
    "type": "invalid_request_error",
    "param": "",
    "code": null
  }
}

Steps to Reproduce
满足以下条件可能触发该问题：

调用对消息队列角色要求严格的模型，如claude-3相关模型
对话内容较长，上下文超过4000token
对话次数多，超过预设的历史消息数

Expected Behavior
User can effectively utilize a long-context model for extensive historical conversations.

Utilize dialogue rounds as the smallest unit of dialogue memory to prevent messages starting with "assistant" in the message queue (as it does not add value to the conversation);
Enhance the role of max_tokens in handling historical message queues.

能成功调用长上下文模型进行长历史对话

以对话轮次为对话记忆的最小单位，避免消息队列中出现 assistant 开头的消息（它对于对话其实也起不到什么作用）；
优化max_tokens 在历史消息队列处理中的作用。

Screenshots

Deployment Method

[ ] Docker
[X] Vercel
[ ] Server

Desktop OS
No response
Desktop Browser
No response
Desktop Browser Version
No response
Smartphone Device
No response
Smartphone OS
No response
Smartphone Browser
No response
Smartphone Browser Version
No response
Additional Logs
No response

we will resolve this problem soon ~~

Thank you for PR, but it seems not to solve the message truncation problem.  Hope to seriously consider the feasibility of treating a dialogue turn (a set of Q&A) as the smallest unit of the message queue.

Thank you very much for the author's attention to this issue. After updating to the latest version and conducting testing, I still frequently encounter this issue.
My testing method: Set max_token to a smaller value (I set it to 200), and after about 4-6 rounds of dialogue, the error can be stably reproduced.
The screenshot of Error is as follows:

I look forward to solving this problem and wish the author a happy life!


Pause rotation in AR mode (at least if a node is selected)

Filed #527 to just disable it for now (since it being disabled is probably better then the current behaviour), and then we can do a good version of it later.
I think a good implementation of this would:

Pause when a node is selected or a trace route is running
Pause if the camera moves "significantly" (say more than a few inches)
Pause if the camera is close to the surface of the globe


Eeasier theming with theme names

For our customers we want to get the ability to ship some themes based on bootstrap.
Since we don't want to exchange plain css files, it would be great to have a map of themes with the corresponding map for the colors you've declared here: https://getbootstrap.com/docs/4.0/getting-started/theming/
Our vision:
We want to ship some different themes and activate them by setting a class to the body. The themes are generated by scss compilation.
So basically an .theme-normal .alert would have other colors than .theme-dark .alert.
Is that possible?

Something like that is possible, but we don't currently support that or plan to.

@mdo any clue of hint how I can solve that?


Update openzfs to 1.7.1

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[ ] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[ ] Named the cask according to the token reference.
[ ] brew cask install {{cask_file}} worked successfully.
[ ] brew cask uninstall {{cask_file}} worked successfully.
[ ] Checked there are no open pull requests for the same cask.
[ ] Checked the cask was not already refused in closed issues.
[ ] Checked the cask is submitted to the correct repo.

This one wasn't in my fork. Oops, sorry.
Superseding PR here: https://github.com/caskroom/homebrew-cask/pull/44793


【TUILiveKit】【Android】Support API-based launching of live streaming pages and optimize the interaction in the Example Demo.

Support API-based launching of live streaming pages.
Optimize the interaction in the Example Demo.

+1


Feature: Code improvements (see log)

Improved the default values according rubocop aspects in gemspec file.
Added .idea (my IDE) to gitignore to do not add ide files in project.
Improved controller with D note in codeclimate.
Added syntax highlights in README for some code examples.

Thanks!

@brunoocasali also is there any reason why all double quotes are converted into single quotes?

Yes, according with rubocop style guide, the default in ruby apps you need to use single quotes in all the time, when you not need to interpolate values on it. Btw I'll open an issue with a propose to keep the gem in rubocop styles see: #66


Update contributing.ejs

It seems that you didn't run yarn admin templates

Addressed in https://github.com/angular/angular-cli/pull/18440


Add EthTransactionValidator::validate_all function

Describe the feature
Add a new function that works just as:
https://github.com/paradigmxyz/reth/blob/27a0a06ca44e9ee25f05abfbad8276c518a33eff/crates/transaction-pool/src/validate/eth.rs#L41-L50
but takes a vec of (origin, tx) pairs. For now this can just call validate_one individually, which could afterward be optimized so that state access is minimized (self.client.lastest)
Additional context
No response

i can take this


refactor(editor): pass buffer to Editor component

Makes things more consistent and simple by passing the buffer to the Editor component instead of finding it again.

Sorry for the slow reply, @SirFurness !
Thanks for the PR - this looks good 👍  Bringing in now.


another weird import cycle

on transforming MathHub/MiKoMH/CompLog/source/pl1/en/substitutions.tex I get the error
(Processing definitions /Users/kohlhase/localmh/MathHub/smglom/sets/source/union.tex...
Fatal::module "set" leads to import cycle!
Trace: set -> equal -> defeq -> argseq -> union -> set:
	/Users/kohlhase/localmh/MathHub/smglom/sets/source/union.tex#textrange(from=2;0,to=2;13)
	In<EMAIL_ADDRESS>from smglom.sty.ltxml line 28

and certainly there is no cycle. In particular, argseq does not import union.
please have a look.

Can you try this in the docker to see if it still occurs?
I cannot reproduce even in the docker:
Hangs-MBP:en Hang$ lmh omdoc --force substitutions.tex
sms-result: up-to-date /mounted/lmh/MathHub/MiKoMH/GenCS/source/logic/en/substitutions-base.sms
sms-result: up-to-date /mounted/lmh/MathHub/MiKoMH/GenCS/source/dmath/en/function-operations.sms
sms-result: up-to-date /mounted/lmh/MathHub/MiKoMH/CompLog/source/pl1/en/free-bound.sms
latexml-result: success /mounted/lmh/MathHub/MiKoMH/CompLog/latexml/pl1/en/substitutions.omdoc

indeed, it does not. I wonder what happened there.


If you know a short way

@yogeshkk We're using a combination of ArgoCD and kube-janitor to achieve this.
The ArgoCD application resource gets a timestamp through CI/CD:
---
apiVersion: argoproj.io/v1alpha1
metadata:
  name: 'foobar-{{ getenv "GIT_BRANCH" | strings.Slug }}'
  annotations:
    janitor/expires: '{{ ((time.Now).Add (time.Hour 24)).UTC.Format "2006-01-02" }}T12:00:00Z'
  finalizers:
    - resources-finalizer.argocd.argoproj.io
spec:

Janitor will then clean up resources after 24h.

Hello @estahn
Thanks for letting know. I am using Argocd heavily. Just come to know about kube-janitor nice project indeed.
One question though how you assign TTL? For us when we deploy we assume it will remain in cluster forever as there is no reason for it not be. Required removal only if request to from developer or stakeholder.
No doubt if you know how long a object will be in cluster your solution is perfect but if you don't know that or there are other cases where this project make some sense which I have highlighted under "Why you need this?" in Readme. (example you just inherited a cluster)
P.S. It also won't work if you deploy using kustomize's configMapGenerator secretGenerator. where old CM or secret is obsolete after new deployment.

We created something internally called "branch deployments". If a developer creates a branch, we will deploy an application with the code of that branch (all CI/CD). The TTL is always 24h from the point of deployment. If a change it committed to the branch, it's deployed again and the clock starts from the beginning.
re configMapGenerator, this is managed by ArgoCDs purge feature. We use ArgoCD with helm, kustomize and custom plugins.

I have heard about such strategy earlier. look like you have good developer who can understand and work with it ;-)
Also this will be for Development env and only for micro-services which you deploy. What about other apps and ton of k8s-addon? We have few environment where we don't have single MS just application such as kafka, supeset, nifi, dotcms and list goes on.. Where application come and go for POC or better alternative.
In short you have a unique env where this combination suit you and I don't disagree. This utility is more general purpose where I try to find out if resources is used or not based on some fixed assumption.
Yes we are using Argo to purge kustomize object ;-) but not everyone using ArgoCD (even we had kustamize apply in older CICD).

Just to be clear, I'm not advocating against the tool you have created. I thought it was interesting and you mentioned you wanted to hear about other ideas.
As for POCs, we have a playground namespace for people to do their evaluations and whatnot. That is being cleared out on a regular basis. But really almost everyone is using ArgoCD through CI/CD including for POCs. GitOps all the things :) ... We've built up governance around this by providing tools and locking down the cluster etc. Tools such as Open Policy Agent bring this even further.
Feel free to close this issue any time :)

@estahn Yes I understand that. I am happy that you mention this tool which I never know and indeed it is interesting.
I am just making out differences so if some have such requirement they can opt for it. I have no issue whatsoever (more the merrier)
I could have discard it earlier but frankly but I am having a good discussion after a while which I like. If you want we can take to other platform which are not public.


Lots of stalled Travis builds

Several times in the last couple of days, we've had Travis builds which have died after receiving no input for 10 minutes. I'm not sure why yet, but we should look into it - reliable CI is a must-have.

It's getting silly. Upping to P0, and looking into this immediately.

(Looks like the changes in #1432 have worked.)


Change remember me cookie's name.

I'm using ab-clientstate and I can see this in client_state.go:
// CookieRemember is used for cookies and form input names.
CookieRemember = "rm"

How can I do?

This isn't currently possible! authboss-clientstate dictates nothing around this, it's all the constant value that you see there.


Simplify sentinel check

Depends on #947 being merged and deployed.

Remove complex conditionals. These were previously required to avoid the issue of this job being skipped due to failures in previous jobs but a skip being considered as the required check completed.
The "Sentinel" check will only be considered as success if it's explicitly run which can naturally only happen if this step actually runs.

I will do this soon to show each different run 👍

I would bet we have obviously thought of this

I'm not so sure ... the simple thing is often only obvious once you've seen it 😉  .. but happy to gather any additional wisdom others around this!

Yes I think I've missed the "check-on-effect" idea that's indeed new! Thanks.

We did not think of going to an external action when designing the current (now old) sentinel check. Let's give it a try.


Seaport 1.5

This PR highlights changes from Seaport 1.3 to Seaport 1.4 and is meant to facilitate review and discussion of those changes.

Codecov Report
Patch coverage has no change and project coverage change: -0.04 :warning:

Comparison is base (92765ef) 100.00% compared to head (772438f) 99.96%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@               Coverage Diff               @@
##           seaport-1.4    #1225      +/-   ##
===============================================
- Coverage       100.00%   99.96%   -0.04%
===============================================
  Files               46       47       +1
  Lines             2657     2653       -4
  Branches           396      396
===============================================
- Hits              2657     2652       -5
- Misses               0        1       +1

Flag
Coverage Δ

foundry
77.85% <ø> (+0.07%)
:arrow_up:

production
99.91% <ø> (-0.09%)
:arrow_down:

reference
100.00% <ø> (ø)

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

Impacted Files
Coverage Δ

contracts/Seaport.sol
100.00% <ø> (ø)

contracts/interfaces/ERC165.sol
0.00% <ø> (ø)

contracts/lib/Consideration.sol
100.00% <ø> (ø)

contracts/lib/ConsiderationBase.sol
100.00% <ø> (ø)

contracts/lib/ConsiderationDecoder.sol
100.00% <ø> (ø)

contracts/lib/Executor.sol
100.00% <ø> (ø)

contracts/lib/OrderCombiner.sol
100.00% <ø> (ø)

contracts/lib/OrderFulfiller.sol
100.00% <ø> (ø)

contracts/lib/OrderValidator.sol
100.00% <ø> (ø)

reference/ReferenceConsideration.sol
100.00% <ø> (ø)

... and 5 more

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Update version to 1.0.98-3 on staging

Update version to 1.0.98-3

🚀 Deployed to staging by @OSBotify in version: 1.0.98-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Support configuration api

This PR is to add configuration api support in go sdk.
Don't merge this PR until the  configuration api proposal is appoved.
https://github.com/dapr/dapr/issues/2988

duplicate with https://github.com/dapr/go-sdk/pull/200


Is there a bug in the method BaseStub.getDefaultChannel()?

Is this a bug? The variable $channel_opts has not been used.
    /**
     * Creates and returns the default Channel
     *
     * @param array $opts Channel constructor options
     *
     * @return Channel The channel
     */
    public static function getDefaultChannel($hostname, array $opts)
    {
        $channel_opts = self::updateOpts($opts);
        return new Channel($hostname, $opts);
    }

It appears so, would you like to send a PR to fix it?


Include Dashdb (DB2) drivers in the node.js (and other) runtimes

Developing a customer solution on Bluemix that need to access a Dashdb database. Our current workaround is to create a docker image with the drivers (not sure whether license allows that), but the cold start time is absolutely horrible (20secs).
Please include the DB2 driver binaries (and Node modules) in the standard Node.js Openwhisk runtime.

@mpuittinen thanks for reaching out. You probably want to open this issue in the core repository at https://github.com/openwhisk/openwhisk/issues

Posted that to the openwhisk registry https://github.com/openwhisk/openwhisk/issues/1932


feat: waf support custom rule

Submit a pull request :rocket:
Thank you for help us contribute! Please give us more information about this PR.

What :kissing:
Adds

Resource xxxx

Fixes

Resouces yyyyyy

Changes

Changes var terraform_depecated to terraform_new

Why :pleading_face:

Add resource xxx to make the terraform more
Fix bug on resource yyyyy
Change depecated var

Other Info

Please see about the version of terraform x.x.x for depecated var

Will update doc after everythin complete


Update Set-SPOSiteDesign.md

Added new parameter in relation to the new site templates UI.

Docs Build status updates of commit 8f3939a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteDesign.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 21f15f2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteDesign.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@Kateyanne

Docs Build status updates of commit 61b0484:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteDesign.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel