recovered an old conditional statement lost in previous updates

this updates the checkbox values again from the settings.json file, however not yet for the initialization, as this problem might correspond to the default values in the layout settings dict. however I'm not completely sure and have to look into it.
So this is a partial fix.

will be fixed in other PR


Revert upgrade of guile

This reverts commit 00a8a4484c63632f72bce894e88b71b891104f64.
The existing and latest release of autogen requires guile version <= 2.2 to build. This upgrade breaks autogen, hence reverting.
I did try to build the latest unreleased version 5.18.98 of autogen to see if the dependency has been removed but it isn't the case. I ran into several issues trying to build v5.18.98 which has additional deps on gnulibs etc. The only supported lib versions of guile are:
_guile_versions_to_search="m4_default([$1], [2.2 2.0 1.8])

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary
Revert the guile version back to 2.0.x
Unblocks building autogen on which several packages depend.
Note: Ideally, would like to fix the cgmanifest error separately as I want it to be a clean revert.
Change Log
Only removes a commit. No changes.
Does this affect the toolchain?
NO
Associated issues

Links to CVEs
Test Methodology

Buddy build to build both guile and autogen -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=485423&view=results

Instead of reverting, can we patch autogen to support guile 3?

As suggested by Andrew, patching autogen to work with guile 3.x instead of downgrading guile.


Configuration file issue - no script issues

Expected Behavior
A working configuration file. I think I've made a mistake somewhere. It's not an actual error somewhere in a script or something, so I hope I'm creating this issue at the right place.
Actual Behavior
Multiple errors.
Your config.json (remove your credentials and any other private info)

Steps to Reproduce
I tried to close the pieces code with {, etc., not working :(
Other Information
OS: Linux
Branch: dev
Git Commit: 0292c2f426b2432be70b0ca867fa62d8436cb5bfe)
Python Version: Python 2.7.10

Solved it by my own.


Regression: Webpack 5.52.1 takes a full minute to shut down

Bug report
Webpack 5.52.1 introduced an issue not seen in 5.52.0.

What is the current behavior?
It takes full minute to wait for webpack to shut down after printing message "compiled successfully".
If the current behavior is a bug, please provide the steps to reproduce.

Run node node_modules/webpack-cli/bin/cli.js --progress a couple of times to fill the cache.
Run again and notice message: webpack 5.52.1 compiled successfully in 3467 ms.
Wait a minute until Webpack returns.

What is the expected behavior?
Return after "compiled successfully" message as in 5.52.0.

Other relevant information:
webpack version:  5.52.1
Node.js version: v12.22.6
Operating System: Linux
Additional tools:

Expected, https://github.com/webpack/webpack/releases/tag/v5.52.0

automatically close an active watching when closing the compiler

You need to close compiler too

If you need help, please provide full steps to reproduce

repro
webpack.config.js:
module.exports = function(env = {}) {
  return {
    mode: 'development',
    cache: {
      type: 'filesystem',
    },
    entry: {
      "bundle": "./empty.js",
    },
  };
};

npm install<EMAIL_ADDRESS><EMAIL_ADDRESS>touch empty.js
node node_modules/webpack-cli/bin/cli.js --progress # returns correctly
node node_modules/webpack-cli/bin/cli.js --progress # waits for a minute

using filesystem cache the second build will have a long delay


all docker stuff

Oh boy. I'm still learning git. I had some problems rebasing but I understand it now.
I reverted all my commits and am making a new pull request. I also added one more thing on the permissions for docker-entrypoint.
Sorry for the multiple pull requests.

This is awesome ! Dont worry about the multiple commits. I do that all the time. My git-fu is pretty week too ! 😉
The changes look good. Can I ask you to add make container, make container_run and make container_clean targets to the Makefile ? Make them do what you specified in the README.md doc.
It would make it easier for the user to kick-off and run a container using make.
Once you have that we can also add it to the README.md instructions.

Yes! I'll get on that. That sounds awesome

LGTM


Is punycode.decode() a reasonable test for valid punycode FQDNs?

I'm trying to check if a hostname string is a valid punycode/non-punycode FQDN. I can see that running:
 punycode.decode('☃')

Properly throws a RangeError which seems like it. But as this is a complex spec and I'm not sure after reading the docs: would punycode.decode() be considered a reasonable test of whether a string contains characters that would be invalid for punycode?
I'm aware of other restrictions on URLs, eg, string length.

Well decode is for converting Punycode ASCII labels into Unicode labels, so throwing any non-ASCII text into decode should throw an error.  If you are starting with a string that may contain non-ASCII characters, run it through toASCII, which should throw an error if any characters are not allowed.

What @indolering said.

Having just figured out that domain name labels are supposed to be passed through Nameprep first, I think the answer to this question is "no" or at least "Don't use punycode.js to lint unicode DNS labels because it doesn't perform normalization."

Thanks @indolering! I kind of felt but couldn't turn into words what was wrong with the previous answer. I now think punicode only does punicode, i.e. it has no idea what a valid domain name is. I'll check out nameprep too!

I gather nameprep is this spec: https://en.wikipedia.org/wiki/Nameprep ?

@mikemaccana Correct.
https://github.com/mathiasbynens/todo/issues/9 seems relevant.


Move package core-bentley to normal dependencies.

Move package core-bentley to normal dependencies.
Uniformize error handling.

@EricPaquetB core-bentley shouldve been added as a peer dep

@aruniverse , for which reason ? The way I understand peer dependencies, core-bentley is not one; it is a direct dependency. It would be a peer dependency if it was a host hosting a reality-data-client "plugin" ... ?

@aruniverse , for which reason ?

Typically a bad idea to have a direct dep on a pkg if it uses statics and the usage isn't pure. Sicne you're returning instances of BentleyError, there might be collisions with BentleyError from other versions (even patches). I think it's best to make core-bentley here a dev+peer. I will review again tomorrow morning to make sure if its safe or not to do so.

@EricPaquetB @MarcBedard8 @aruniverse this change should have been a minor version bump to go to 0.8.0 since this is a breaking change.


Remove Android Studio files

All *.iml files, as well as import-summary.txt shouldn't be at repository :P

Thank you for you advice :+1:


[beta] UX: slow legacy pagination needs loading spinners

Issue: AAH-2062
https://issues.redhat.com/browse/AAH-2062
Correct spinner in Legacy Roles and Namespaces.

Now all of them are have radix 1 instead of 10 ;)


Code splitting support for live server

CRA v2 uses code splitting, producing 3 assets by default when the live server is run:
bundle.js
Bootstrapping/liveserver code presumably.
main.chunk.js
Main application code.
0.chunk.js
Vendor code.
Currently django-cra-helper only supports returning the bundle path in generate_manifest.
More details
Unfortunately this is complicated by a lack of a coherent asset manifest in CRA2.

Thanks for raising this. Right off the top of my head, the "easy" solution would be to add in a couple of more hard-coded paths to generate_manifest() to use when the liveserver is detected. I wonder if there's a way to do it in a way that'll future-proof this library to accommodate potential future changes to CRA...
I'll have to mull over this for a couple of days and see if anything doesn't come to mind.

I've released django-cra-helper v1.2.0 that includes support for the various forms that asset-manifest.json has taken over the last few releases of Create-React-App. Give it a try and let me know what you think! 🎉


Add icon for XLSX files (Fixes #5124).

@LeviWB this looks fair but if you want to go above and beyond, would you feel like updating all of the icons in images/app_icons? They're inconsistent at the moment in size and visual style. Notably half of them are 16x16 but the name implies otherwise. A nice improvement might be to replace them all with open source icons from a single set, and make them PNGs with an alpha background. That part would require a small tweak to File::Icon(). Interested?
@scott1702 thoughts?

Yes I agree, a lot of those images are quite outdated and inconsistent and while this is something we're probably looking to update for 4.0 with the new assets area, it would still be cool if somebody wanted to update them in the 3 branch.

Have you guys settled on an icon set already for 4, or have some favourites? If you want to share a link we may as well get it going in a similar direction in 3 branch.

There are some custom-made icons here (ignore treeicons folder and blue-folder...png which were ported over from the cms module). Currently I'm uncertain as to whether we're going to pull in an icon set to handle the rest of the images, but I'm guessing for images for files like these we're going to have custom images.
/cc @clarkepaul?

Sweet, thanks @scott1702. Whaddya say @LeviWB, want to give this a go? Otherwise I can do it when I get a chance.

We haven't sided with a single icon set yet partly due to not really having a complete idea of what we require at this stage and at what size (even though they are vector sets are usually created to be optimal at certain sizes). The majority of the new icons have come from the set Entypo which isn't going to be varied enough for the CMS by itself. If you want to update icons you could use svg's from nounproject.com possibly and credit the authors? (I have created customised ones from icons on there).
Icons in context of the upcoming design (icons Scott shared are at the bottom): https://projects.invisionapp.com/boards/9GX68PTXUQFH/

How about these for 3 so they blend in to existing look:

Based on the icon used in file admin gridfield for all files that aren't images or folders currently.

https://github.com/silverstripe/silverstripe-framework/pull/5186

Superseded with https://github.com/silverstripe/silverstripe-framework/pull/5186


Node switcher popup not opening

The connected node popup doesn't reliably appear on https://console.fairground.wtf/ when the node is down.

Seen using chrome Version 103.0.5060.134
Easily replicated in an incognito window
Failed to fetch message remains on screen when visiting https://console.fairground.wtf/ rather than the expected behaviour of the "connected node" popup opening

Screenshots attached

redeployed fairground with the config url, and cannot reproduce this anymore. closing this for now.


lack of "crypto/ed25519" file

Tag 4.0, missing the "crypto/ed25519" file at auth.go，
....\marten-seemann\qtls\auth.go:11:2: cannot find package "crypto/ed25519"

Actually I had this problem when updating qtls to the latest master today. I changed the imports as a workaround to "golang.org/x/crypto/ed25519"

@marten-seemann I don't have crypto/ed25519 but I do have it inside golang.org/x external package folder. What about a PR changing the import path to that of external packages?

Beginning with Go 1.13, the functionality of this package was moved to the standard library as crypto/ed25519.
Just upgrade to Go 1.13.

Alright. Looks like I was running an older version. It wasn't older than 1 month though. Thank you so much @dmalykh


Observers,repeaters and comparators aren't rotated properly

Observers are always facing the same direction and same goes for repeaters and comparators

Are you using the current version or an ancient one with this bug
On Sun, Sep 24, 2023, 9:20 AM Nobody2000IQ @.***> wrote:

Observers are always facing the same direction and same goes for repeaters
and comparators
—
Reply to this email directly, view it on GitHub
https://github.com/RavinMaddHatter/Structura/issues/204, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBUC5FQBQ35DXYKOOBOB73X4BMWRANCNFSM6AAAAAA5FBCKDE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

The latest version 1.6.3

Fixed  use the update button to get the fix.


One drive upload

With One drive file saver, we can be able to see the uploading process such as uploaded percent. Is it possible to retrieve this same process (uploaded percent) with upload end point (PUT /drive/items/{parent-id}:/{filename}:/content) ?
Thanks,

If you're PUTing directly to /content it would be up to your client to keep track of progress. If, however, you're using the session based uploading you can query for status although that's targeted more for allowing a client to know where to resume and not so much for displaying an accurate upload percent.

Hi,
I also tried to use optional query string parameters to rename a file with the same content but it always returned 200 status for me instead of 201 as expected. Below is the request example, not sure what I missed or anything is wrong.
<EMAIL_ADDRESS>

If you're calling the OneDrive API directly instead of via Graph you'll want to take note of the differences outlined on this page. In this instance you'll want to use @name.conflictBehavior instead of @Microsoft.graph.conflictBehavior.

Cool, I got it working. Thank you.


General improvements

Creates CMakeLists file, since QMake will be deprecated.
Connects QPushButton::clicked() signal to slots explicitly, which is a better practice than the implicit connection.
Handles the memory used by QProcess objects, avoiding memory leaks.

Great contribution, thank you very much.


add support for request body

Added optional -body param to include a request body

Thank you @jffmrk !


[Add]

Site URL
https://www.youtube.com/playlist?list=PL0b6OzIxLPbzDsI5YXUa01QzxOWyqmrWw
Description of the above provided site
This playlist is valuable resource for understanding the concepts of CSS in Hindi language
Category
Youtube
Sub Category
CSS
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)
[X] I am participating in Hacktoberfest 2023

Hi @JoyelJohny! :) Welcome to LinksHub!:) We're so glad to have you here. Please keep the following in mind as you make your PR:

Create a separate branch with Git before you push your commits. If you need help with this, check out this article, How to Create a Local Branch in Git
Follow the directions in the PR template to fill it out completely. If you need more tips, check out the blog post, Writing Your First Pull Request: Tips, Best Practices, and AI-Powered Tools for Success


Support for NON type message

Coverage decreased (-1.25%) when pulling bbcdce4497c259bfeb16bd3ee17fe2eae617a76b on milaw:master into e894c96b0f7ed0ce9bd2c4747231a83d62a61177 on gatesense:master.

Can you add a test as well?

Coverage decreased (-1.25%) when pulling da316bafd0b2499b286167f8ab4a770aaa314112 on milaw:master into e894c96b0f7ed0ce9bd2c4747231a83d62a61177 on gatesense:master.

@milaw I was planning to merge this PR (conflicts are resolved on my local copy), but I noticed it was posted before the license changed from Apache 2.0 to MIT. Is MIT ok for you?


Do you have the implementation code of "Path Integral Guided Policy Search"

Do you have the implementation code of "Path Integral Guided Policy Search"

No, I do not have.

Thank you anyway.
------------------ 原始邮件 ------------------
发件人: "Vektor<EMAIL_ADDRESS>发送时间: 2019年11月6日(星期三) 凌晨5:00
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [tttor/rl-foundation] Do you have the implementation code of "Path Integral Guided Policy Search" (#1)
No, I do not have.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Enable support for custom properties

Enable support for custom properties:
Add to provider response the ability to add additional fields. So provider can decide what extra fields should be added

Done


How to provide appropriate source prompts and target prompts

Your work looks impressive. I would like to ask, in the summer2winter task, what kind of source prompts and target prompts are provided?

For baselines like prompt2promt and cyclediffusion that need these prompts, we used "summer" as the source prompt and "winter" as the target prompt. For baseline pix2pixzero, we followed the authors' practice by first generating the embedding of summer and winter and then used them to edit the image.


Performance degradation between 0.2.4 and 0.2.5: heap out of memory.

It seems that https://github.com/atomiks/rehype-pretty-code/commit/8885e75ce9491986d6cb2aed1fd3d1e39e6e5309 has drastic performance degradation on memory usage.
Reproduction: https://github.com/brillout/rehype-pretty-code_performance-degradation-reproduction.
(Btw. thanks for rehype-pretty-code, FYI I'm using it for https://vite-plugin-ssr.com/ and https://telefunc.com/ and I really like the code blocks :-).)

cc @silvenon

Should work after the fix in the PR, I tried it. 👍

I can confirm it works again. Thanks!


Edits to not enough tips error

As a user i'd like to know which tip rack i need to place on the deck
Acceptance criteria

Change body of the error banner to read "Add another {Tip rack type} to an empty slot in Deck Setup"

Spoke with Morgan & Brian about this, having timeline errors display dynamic info (like tiprack type) would add a moderate amount of complexity to them, it'd be nicer to do this later when either we see several timeline errors needing this or after we do internationalization

@howisthisnamenottakenyet @umbhau where should punted/backlogged tickets go?


Incorrect Nomenclature for the 'Msv2 Medium Memory Diskless'

'Msv2 Medium Memory Diskless' VMs should not have a 'd' in their naming convention.
Otherwise they end up with the same name as those in the table below it.
Please correct.

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

ID: e7457bf0-dc21-6f49-d4e5-4de493219ef1
Version Independent ID: f5969121-2e88-8bf3-77f0-428ae4cc59ad
Content: Msv2-series (Preview) - Azure Virtual Machines
Content Source: articles/virtual-machines/msv2-mdsv2-series.md
Service: virtual-machines
Sub-service: sizes
GitHub Login: @ayshakeen
Microsoft Alias: jushiman

@brianlo-ms
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.We will update you accordingly.

@ayshakeen Can you please check and add your comments on this doc update request as applicable

Thanks for pointing this out! Fix is submitted. Changes will be live tomorrow morning.
#please-close


[feat] initialize from an existing environment

In this PR

implement conda-project init --from-environment <name or prefix>
update to conda-lock 2.5.6

2.3.0 removes the need for a temporary lockfile
2.5.6 fixes input hash updates on re-lock

timestamp now added to lockfile
on conda-project install only re-lock if the current platform needs to be re-locked

previously the lockfile was re-solved if any platform needed it

Using the --from-environment <name or prefix path> flag the environment.yml and conda-lock.<env-name>yml files will be generated from an existing conda environment.
The conda-lock.<env-name>.yml for the current platform is constructed by performing a full conda env export so that the environment is captured as-is into the lockfile. Only packages for the current platform are written in to the lock. When someone attempts to install on another platform conda-project will automatically lock the missing platforms, but not modify the original platform, unless the environment.yml file was changed.
The environment.yml captures the requested conda and pip packages as follows. You'll see that conda packages are prefixed with its channel and the full version is captured in the spec even if a specific version was not originally requested. This helps keep the environment close to the original if the original platform is re-locked and when other platforms are locked.
You'll see that all four major platforms are listed in the environment.yml, but a full cross-platform solve is not attempted by default. The user could do conda project init --from-environment <env-or-path> --lock, which will capture the current platform according to the above procedure and then lock the remaining platforms.
name: data-science-work
channels:
  - defaults
  - anaconda-cloud
  - conda-forge
dependencies:
  - defaults::hvplot=0.9.2
  - defaults::pip=23.3.1
  - defaults::scikit-learn=1.3.0
  - defaults::pandas=2.1.4
  - conda-forge::wheel-filename=1.4.1
  - defaults::panel=1.3.8
  - defaults::python=3.11.5
  - defaults::python-libarchive-c=2.9
  - defaults::ipykernel=6.25.0
  - defaults::intake=0.6.8
  - conda-forge::ratelimit=2.2.1
  - pip:
    - anaconda-catalogs==0.2.0
    - torch==2.2.2
variables:
prefix: /Users/adefusco/Applications/miniconda3/envs/data-science-work
platforms:
  - osx-arm64
  - linux-64
  - osx-64
  - win-64

LGTM


added organizations detach_policy response, model, and tests, issue #…

…3239

Coverage decreased (-0.3%) to 94.122% when pulling 343d50919b17523821a206b4b5b2d164bd26fecb on fidelity:enhancement/awsorganizations-detach-policy into 3fb7cf75d43562ba0dc494be6021a86fb0bc3436 on spulec:master.

@bblommers @harvester843 Can you all confirm that this should be?
if policy in account.attached_policies:
https://github.com/spulec/moto/blob/5aefbb1e51e0b97583bb96bd8c3c596dbca44a31/moto/organizations/models.py#L868
attach_policy has the same issue, but it defaults to working due to the not in condition.


Block uploads from external users

This block sync is inadequate in the face of how Sharepoint is used. Will a blocked extension be effective in blocking external users with permission to upload to a site. Is it possible to prevent external users from uploading specific file types? Sync is only one part, a smaller part, of the security questions. The more significant need is to restrict external uploads.

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

ID: 31fd97e0-7bfe-0d85-a52c-1ba28f3337c3
Version Independent ID: 696ee19b-4364-d548-0dcb-afa6a9fff031
Content: Block syncing of specific file types - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/block-file-types.md
Service: one-drive
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

Hello @scottw-at-ivetoplaysports-dot-com
Here we are limited to documentation changes and fixes, is there any fix to the documentation that you see is necessary?
Otherwise, if it is a feature request, the best resource would be https://feedbackportal.microsoft.com/feedback/forum/06735c62-321c-ec11-b6e7-0022481f8472

We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


GH-35868: [C++] Occasional TSAN failure on asof-join-node-test

Rationale for this change
AsofJoinNode may run into a data race when invalidating the key hasher.
The key hasher queried from one thread but invalidated from another. This might be simplified so that the key hasher would only be used from one thread, but this is out of scope for this PR.
What changes are included in this PR?
The invalidated member of the key hasher is made atomic.
Are these changes tested?
Yes, by existing testing.
Are there any user-facing changes?
No.

Closes: #35868

cc @pitrou

Adjusted your PR description to add the explanation you gave in https://github.com/apache/arrow/pull/35874/commits/380aa94bd04df435a0be7c6ee05a5e2581008f77#r1218255714

@github-actions crossbow submit test-ubuntu-20.04-cpp-thread-sanitizer


Feedback on Develop

Hi guys,
I just wanted to say that I've spent a couple of days on this project and specially on the Develop branch. I know that you're still working on it. Keep up the good work :-)
There are a few problems with the code and therefore the result is wrong. To give you an example in GenericTradeManager.GetAdvice which is one of the most important part of the project this code is used: (at this moment)
private async Task<ITradeAdvice> GetAdvice(string tradeMarket)
    {
        var minimumDate = DateTime.UtcNow.AddHours(**-120**);
        var candleDate = new DateTime(DateTime.**Now**.Year, DateTime.**Now**.Month, DateTime.**UtcNow**.Day, DateTime.**Now**.Hour, 0, 0, 0);
        var candles = await _api.GetTickerHistory(tradeMarket, minimumDate, Core.Models.Period**.Hour**);

        // We eliminate all candles that aren't needed and the last one (if it's the current running candle).
        candles = candles.Where(x => x.Timestamp > minimumDate && x.Timestamp < candleDate).ToList();

        // Get the date for the last candle we have left.
        var signalDate = candles[candles.Count - 1].Timestamp;

        // This is an outdated candle...
        if (signalDate < DateTime.**UtcNow**.AddMinutes**(-120)**)
            return null;

        // This calculates an advice for the next timestamp.
        var advice = _strategy.Forecast(candles);

        return advice;
    }

Shouldn't you use Utc datetime all the time?
And are you always use -120 hours minimumDate and minutes for outdated candles? Are these not the base values for most strategy calculations?
You did a fine job with this project, but adding more and more features doesn't help it I'm afraid. The current basic features doesn't work well. Another example is the dryRunning. It gave me a lot of errors when tryParse the OrderId from "DRY_RUN_SELL_123456" to a long variable and a few other things as well. But don't remember them now.
Another thing was the fact that somehow I get many runtime exceptions on the strategies. But I'm not sure why. Somehow the SMA(200) on The Scalper strategy is always null and there is not null check on it I guess.

All of the above issues are fixed in develop as far as I can tell. If you find any new issues please create new issues for them, thanks!


Create hnxxc.txt

@kawa11 First stage of verification passed, official domain is hnxxc.com as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@kawa11 Pull request merged. Thank you.


Add support for initial-letter CSS property

There's a W3C proposal for a new initial-letter property to introduce proper dropcap support in CSS.
Apparently this will be a feature of the upcoming iOS 9 Safari.
For those who think: but haven't we already got the :first-letter pseudoselector? You're right: but styling a dropcap also needs to take in account all the text surrounding the character, and that's notoriously tricky with regular CSS properties. This property will, for once and for all, allow 'proper' styling of dropcaps in CSS.

+1

+1

+1

+1

It now is in Safari.

+1

+1

+1

I posted a demo of this property at http://labs.jensimmons.com/progressinglayout/example-initial-letter.html with a note about a current bug.

@jensimmons i'm getting a 404 on that page :/

Sorry about that — I'm half-way through setting up a new site of layout examples, and moved things around after posting here. Durp!
The initial-letter demo is here now: http://labs.jensimmons.com/examples/initial-letter.html

+1

+1

Looks like the bug in Safari will be fixed in 9.1.1. It's fixed in the new Safari Technology Preview.

I'm a sucker for things like this – sounds like a lovely idea. I'm sure there is a request somewhere here for :nth-letter(n) and possibly :range-letters(2.10)

+1

+1

+1

https://webkit.org/status/#feature-initial-letter

+1

+1

+1

Some news about Initial Letter:
It is being added to Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1040714
The fix for the Safari 9 bug shipped in Safari 10.

+1

Now available at http://caniuse.com/#feat=css-initial-letter

Thanks @Fyrd!


kade dev should add these

Please check for duplicates or similar issues before creating this issue.
What is your suggestion, and why should it be implemented?

i wish kade dev add this on kade engine its cool tho

That idea is week 7 so they ain't gonna do that

development for kade engine is cancelled


Time not using Critical Data Store

Describe the bug
The following requirements specify that TIME should be using CDS:
cTIME2502
Upon a Processor Reset the cFE shall verify the Critical Data Store used to store time values.
cTIME2501
Upon a Processor Reset the cFE shall acquire the following time elements from the <MISSION_DEFINED> Critical Data Store:

Time Status Data
STCF
Leap Seconds

cTIME2700
During normal operation, the cFE shall preserve the following time elements in the <MISSION_DEFINED> Critical Data Store:

Time Status Data
STCF
Leap Seconds
MET

cTIME2502.1
If the critical data store is not valid, all of the time elements shall be initialized in the same fashion as following a power-on reset.
There is no CDS for time – the respective variables are preserved through the Reset Area.
Expected behavior
The requirements or FSW should be updated to reflect intended implementation.
Reporter Info
Dan Knutsen
NASA/Goddard

I'm going to guess that this evolved this way because the "Reset Area" is always memory-mapped (i.e. accessible via pointer) whereas the CDS only has an indirect read/write API via the PSP.
But in reality the CDS and reset area are effectively the same thing on the three platforms in the framework - they are allocated together and use the same underlying storage mechanisms for both.
That being said - this use of the "Reset area" by TIME (and I think EVS too) is one of the few remaining things that require a sort of "backdoor" or private/non-public interface between CFE core apps - as ES technically "owns" this data structure.
There are a couple approaches that could work:

Use table services with a "critical" table to store these time variables.  This should in turn be backed by a CDS, with the advantage that all of the regular TBL management stuff will apply too (e.g. dumps, etc).  But will have to review the code to make sure it won't add overhead - it is important that these TIME variables can be accessed quickly with low overhead, and they change frequently with every time at tone message.  The "page flipping" of the reference data implemented in TIME is somewhat similar to a double buffered table already.

Just formalize what is already there, and divide the current ES "reset area" into a separate area for each of the core apps.

I think option 1 is better long term but it is more work and involves more risk of regressions.  Because these extra internal-only interfaces (like the reset area) are a maintenance issue and increase the complexity of the code and the difficulty of porting to new platforms.  Making everything work through TBL services and the existing CDS simplifies things.

Marked as enhancement to reflect that the spirit of the requirement is met (persistent time data) it's just not in what the implementation calls  the "critical data store".  Should address this along with the planned major TIME refactor work #302 and others.

Marked as enhancement to reflect that the spirit of the requirement is met (persistent time data) it's just not in what the implementation calls  the "critical data store".  Should address this along with the planned major TIME refactor work #302 and others.


Image preview doesn't work

I haven't been able to preview images from the public folder. Is there any solution?

What are you using? Absolute URL linked to the static folder or relative links to the images:

OR

OR

I will take a look at this soon.

I'm using mac. Tried all of them but no luck :(

It should be working now with the last release, tell me if it is still not working

Great! I'll check it out and let you know. Thanks!
On Fri, Sep 24, 2021, 12:21 AM rafalou38 @.***> wrote:

It should be working now with the last release, tell me if it is still not
working
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rafalou38/svelte-preview/issues/3#issuecomment-926049747,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUHA22GM5DJE2IZVCJMTM23UDNV3PANCNFSM5EIV5LWQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Typo in README.md

[LICENSE file](https://githib.com/microsoft/msdos/license.txt)
GitHib?
The correct link should be -
[LICENSE file](https://github.com/Microsoft/MS-DOS/blob/master/LICENSE.md)
And maybe you will want to fix the LICENSE.md file? It looks really messy.

Please close, patch was already submitted: https://github.com/Microsoft/MS-DOS/pull/6

Fixed by @bitcrazed merging #6, please close

Thanks. Fixed.


Fix checkfail with tf.raw_ops.Conv2DBackpropInput with MKL enabled.

The API tf.raw_ops.Conv2DBackpropInput with oneDNN enabled causing checkfail if strides<4. This is due to trying to access channel dimension 'C' with NHWC format without validating the strides dimension.
Fixes #62950 .

Hi @SuryanarayanaY Can you please take a look on the above comments from @mihaimaruseac, @cantonios. Thank you!

cc: @TensorFlow-MKL

Done the changes as reviewed and suggested by MKL team.

Hi @SuryanarayanaY Can you please check @cantonios's comments. Thank you!


Ui Issue | Rectangular outline around progress bar

Description:
There is a Rectangular outline around progress bar when loading pages in Publisher. Visible in Chrome on windows.
This was not visible in Edge browser.

Affected Product Version:
API-M 4.0.0
Environment details (with versions):

OS: Windows 10
Browser: Chrome

Suggested Labels:
API-M 4.0.0

This is fixed with latest release.


Update diagrams after API unification

And make some minor changes to README text

Lgtm.  Will leave it to a non-rher to do the honors.

good diagram. It LGTM.
One question: where is the link to docs/images/propagation.png from the doc? I think we need such kind of description and link.

LGTM. Thanks @pmorie. You might have missed linking docs/images/propagation.png. is that the case?

LGTM. Thanks @pmorie. You might have missed linking docs/images/propagation.png. is that the case?

@shashidharatd yep, I'm just adding it for now. I'll make a small doc PR that contextualizes it as a follow up.

/lgtm
Thanks @pmorie


v18.0.1

Pull Request
Description
Makes the element array buffer bind and unbind with its vertex array object.
Relevant Issues
List relevant issues here, if any exist.
N/A
Details
N/A


docs: improve community pages

issues templates, contributing, security, code of conduct

:tada: This PR is included in version 1.39.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


"On this Page" content is inaccurate

With TypeScript as the selected target, the following content is shown:

No longer relevant after switch to Docusaurus.


The configuration format is yaml. A date string is included in the configuration. When you obtain the configuration, the date string is converted to a date object.

Which Component
jdk :1.8
spring-cloud-starter-alibaba-nacos-config :2.2.1
Describe the bug
The configuration format is yaml. A date string is included in the configuration. When you obtain the configuration, the date string is converted to a date object.
配置格式是yaml 配置内容中有日期字符串在获取配置时会把日期字符串转换成日期对象
转换之前是日期字符串

转换之后变成了Date对象

user.version='2020-09-10'

user.version='2020-09-10'

ok


doc: add pypet/BRIAN2 example pipeline

Hello @Franko1307! Thanks for submitting the PR.

In the file pipelines/pypet-brian2/scripts/example_23_brian2_network.py, following are the PEP8 issues :

Line 4:10: E261 at least two spaces before inline comment
Line 10:80: E501 line too long (90 > 79 characters)
Line 14:1: E302 expected 2 blank lines, found 1
Line 18:30: E225 missing whitespace around operator
Line 19:23: E225 missing whitespace around operator
Line 22:33: E231 missing whitespace after ','
Line 23:34: E231 missing whitespace after ','
Line 24:34: E231 missing whitespace after ','
Line 25:34: E231 missing whitespace after ','
Line 26:38: E231 missing whitespace after ','
Line 27:36: E231 missing whitespace after ','
Line 28:33: E231 missing whitespace after ','
Line 29:33: E231 missing whitespace after ','
Line 30:33: E231 missing whitespace after ','
Line 31:36: E231 missing whitespace after ','
Line 31:49: E261 at least two spaces before inline comment
Line 31:80: E501 line too long (80 > 79 characters)
Line 32:33: E231 missing whitespace after ','
Line 34:8: E225 missing whitespace around operator
Line 43:1: E302 expected 2 blank lines, found 1
Line 46:8: E225 missing whitespace around operator
Line 51:11: E225 missing whitespace around operator
Line 51:80: E501 line too long (80 > 79 characters)
Line 53:14: E225 missing whitespace around operator
Line 54:13: E225 missing whitespace around operator
Line 55:14: E225 missing whitespace around operator
Line 55:32: E231 missing whitespace after ','
Line 55:41: E231 missing whitespace after ','
Line 55:49: E261 at least two spaces before inline comment
Line 60:35: E261 at least two spaces before inline comment
Line 63:11: E225 missing whitespace around operator
Line 66:52: E231 missing whitespace after ','
Line 66:62: E231 missing whitespace after ','
Line 66:64: E231 missing whitespace after ','
Line 71:19: E231 missing whitespace after ','
Line 75:37: E231 missing whitespace after ','
Line 81:30: E251 unexpected spaces around keyword / parameter equals
Line 81:32: E251 unexpected spaces around keyword / parameter equals
Line 84:5: E303 too many blank lines (2)
Line 89:30: E251 unexpected spaces around keyword / parameter equals
Line 89:32: E251 unexpected spaces around keyword / parameter equals
Line 90:80: E501 line too long (90 > 79 characters)
Line 97:80: E501 line too long (99 > 79 characters)
Line 98:66: E231 missing whitespace after ':'
Line 98:70: E231 missing whitespace after ','
Line 99:28: E128 continuation line under-indented for visual indent
Line 99:58: E231 missing whitespace after ':'
Line 99:65: E231 missing whitespace after ','
Line 114:1: W391 blank line at end of file

we will rework this as a popper 2.x workflow


We are using IndicatorSeekBar in recyclerview item with navigation drawer and Indicator stays on the top of all Views ?

We are using IndicatorSeekBar in Recyclerview item with navigation drawer and Indicator stays on the top of all Views when we open the drawer?
Screen shot : -

@aakashy85 hi , sorry for late recently is busy. Now the lastest verion is supported this excelently, hope this library is helpful to you. thanks


Monthpicker in popup only with global configuration?

I'm trying to use the  datepicker in monthpicker-mode as a popup, but the only working way someone found was to configure this globally.
The problem is that this is not the only picker in my application. I need datepickers and monthpickers in different locations of the app, so I cannot configure the mode globally.
The related stackoverflow question:
http://stackoverflow.com/questions/24180416/angularui-monthpicker-in-popup-shown-as-datepicker
Is this a bug or a missunderstanding on my side?

Closing as an outdated issue. If this is still relevant, @maklemenz please provide a plunkr reproducing your problem and we'll be able to take a look at it. Also, test this in the latest UI Bootstrap 0.13 and AngularJS 1.3.


grpc-c++: Support exporting master keys of TLS

Wireshark is an open source network protocol
analyzer, which can be used for protocol development, network troubleshooting,
and education. Currently Wireshark can analyze gRPC messages transmitted in plain text (https://gitlab.com/wireshark/wireshark/-/wikis/grpc), but it will be helpful if there is a way to export TLS master keys into a key log file which can be read by Wireshark for analysis gRPC traffic. (The grpc-go already supports this feature referring to the wiki page.)
The SSL_CTX_set_keylog_callback (since openssl 1.1.1) or SSL_get_client_random/SSL_get_server_random/SSL_SESSION_get_master_key methods of openssl or boringssl can be used to export the master keys (into key log files).
The possible way might be that let user register a master key callback function in TlsCredentialsOptions and tsi_ssl_client_handshaker_options, and grpc(c++) calls the SSL_CTX_set_keylog_callback function in tsi_create_ssl_client_handshaker_factory_with_options of 'src\core\tsi\ssl_transport_security.cc'. Using tsi_create_ssl_server_handshaker_factory_with_options instead if exporting master keyes in the server-side.

Hope someone to implement this feature.

Could we please reopen this and add the appropriate labels to prevent the bot from closing it again?

This feature itself seems fine, while I will note a comment that is already covered at tls.Config.KeyLogWriter in Go:
Use of KeyLogWriter compromises security and should only be used for debugging.

We will probably have to document heavily on this to avoid users exporting their TLS keys in production environments.
Our team is currently busy with some other works, and probably won't be able to implement such features in the next couple of months. @huangqiangxiong @tamird Is it possible for your team to come up with a design and drive the implementation, once we agree to add this feature?
@yihuazhang FYI.

For me: no.
I am not a regular used of c++ grpc; I landed on this issue while debugging an internal issue at Google (which required me to modify the guts of grpc to exfiltrate the SSL log).

I might have someone... Touch base tomorrow?

@ctiller Sure thing!

I'm glad to find that this feature is about to be released.

Yeah, credits to @Vignesh2208 who landed this end to end!
And thanks everyone who is involved here. Amazing work! I am going to close this issue now :)


Check if config map is empty before retrieving secrets.

Why do we need this PR?
If config map is not being created in the job, retrieving secrets should skipped.
Failed here:
https://jenkins.portworx.co/job/Torpedo/view/Torpedo 2.2/job/tp-2-2-sysbench/68/console
Signed-off-by: Rohit-PX<EMAIL_ADDRESS>

Testing here: https://jenkins.portworx.co/job/Torpedo/view/Torpedo 2.2/job/tp-2-2-sysbench/69/console


Test Flake: Multicluster security tests

Bug description
Test Flake: https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/32165/integ-security-multicluster-tests_istio/1382383815300747264
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ X ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade

Moving to 1.12 milestone due to recent inactivity

https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/34662/integ-security-multicluster-tests_istio/1427390643587518464

cc @JimmyCYJ @yangminzhu can you take a look? we see these a lot

@incfly @yangminzhu @liminw @JimmyCYJ How is this looking for 1.12? Should it be moved to 1.13?


support for task groups (and a couple other super minor tweaks)

PR Summary

support for task groups
a typo fix
a minor tweak to my last PR: I didn't _applyTypesToVarGroup on the object returned.
Last PR (support for name when getting var groups) I didn't specifically verify that I could generate the help files.  I tried to this time, but received a number of errors.  I'm OK to not troubleshoot it further if it generates fine for you, as I don't have any further PR's in mind as of now.

PR Checklist

[x] Write Help
[x] Write Unit Test
Update VSTeam.psd1 (N/A)
[x] Update CHANGELOG.md

@DarqueWarrior, I'm guessing you already saw the failed job, but figured I'd mention you just in case.
I'm at a loss as to what the issue is.  I see this pipeline worked for you on 9/6 (https://loecda.visualstudio.com/Team Module/_build/results?buildId=1635&view=results) and the last change was 9/5 (https://github.com/DarqueWarrior/vsteam/commits/master/azure-pipelines.yml), so I'm not sure why it would magically fail now.
I can only think some under the hood AzD change?

Going to look at it now

Working on the requested changes.
Should I worry if .docs\gen-help.ps1 has a ton of errors?  If it does, does that mean I'm doing something incorrectly?  Maybe it's only meant to be run in the AzD build process?

I have pulled the latest changes and looking around now. Thanks again for the support.

Working on the requested changes.
Should I worry if .docs\gen-help.ps1 has a ton of errors? If it does, does that mean I'm doing something incorrectly? Maybe it's only meant to be run in the AzD build process?

I just r

Working on the requested changes.
Should I worry if .docs\gen-help.ps1 has a ton of errors? If it does, does that mean I'm doing something incorrectly? Maybe it's only meant to be run in the AzD build process?

I just ran it on your master branch and everything worked as expected.

Weird.  In any case, I'm sure you'd let me know if the documentation isn't as you were expecting.  Thanks for checking it out!

Oh, I see you closed the pull request, but I haven't implemented "SupportsShouldProcess = $true and a ConfirmImpact value" yet.  Sorry if my last commit message was unclear; it was only the documentation changes.  I guess I'll just do a separate pull request for the Force / ShouldProcess code.

Sorry, I'm realizing that I'm a bit confused as to where we are.  I see that you've closed this request rather than merged.  I guess you're just planning on looking into the TFS 2017 support, as you mentioned above.  You also wrote, "If I determine it is not supported in TFS 2017 we will leave "" and throw when someone tries to use in an unsupported version."  I guess you mean in that case, that VSTeam won't support task groups?  I guess, in any case, I'll hold off on implementing Force / ShouldProcess for the Add and Update functions.

Sorry, I'm realizing that I'm a bit confused as to where we are. I see that you've closed this request rather than merged. I guess you're just planning on looking into the TFS 2017 support, as you mentioned above. You also wrote, "If I determine it is not supported in TFS 2017 we will leave "" and throw when someone tries to use in an unsupported version." I guess you mean in that case, that VSTeam won't support task groups? I guess, in any case, I'll hold off on implementing Force / ShouldProcess for the Remove and Update functions.

Correction: looks like I had already implemented Force / ShouldProcess.  I'm now just fixing some unit tests in my environment-specific wrapper module to make sure my implementation is OK.  I guess I should make a new pull request for that?

@DarqueWarrior, no rush at all.  Just making sure you saw the above comments so we don't duplicate effort on Force / ShouldProcess.  I'm guessing maybe GitHub doesn't notify you on my comments to my own PR?

Can you make sure I have commit permissions to this PR.

Can you make sure I have commit permissions to this PR.

Googling how to set that up...

Can you make sure I have commit permissions to this PR.

Googling how to set that up...

Done.

I made several changes and updated the formats for you. I think I could be able to merge the changes when you re-open it.

Super weird: I've clicked the checkbox below multiple times, and it appears to take effect, but if I refresh the page, it reverts to being unchecked:

I also don't see an obvious way to re-open:

Maybe since you closed it, I don't have permission to re-open?  Maybe once it's re-opened the permission to let you commit will stick?

Yeah, I see that there should be a "Reopen pull request" button:

... that I don't have:

... so, I'm guessing you have the power :)

@DarqueWarrior, no rush at all, just for clarity: just let me know if you can't re-open this PR (which I'm hoping will let us fix your ability to commit to it). If you can't re-open, I'll just make a new PR.


Deployment Docs Update

Made changes to Step 3 per the discussion in #743, as well as some
grammar/formatting adjustments and an update to the buildpack version
mentioned in Step 2 (v91 is the latest stable)

Coverage remained the same at 98.947% when pulling f1d2e7ee099d2a3d743c6d0f5479141f23ac4799 on sethmcleod:master into 4487d298980ed002a7423c46bebe880ad4de81a2 on mxstbr:master.

Coverage remained the same at 98.947% when pulling 7406ca8a841e373841ec535900871ef4a6bf8f6c on sethmcleod:master into 4487d298980ed002a7423c46bebe880ad4de81a2 on mxstbr:master.

Awesome, thank you! Would you mind submitting this PR against the dev branch?

Done @mxstbr :)

Don't forget to resolve merge conflicts 😉

Coverage remained the same at 99.177% when pulling 4487d298980ed002a7423c46bebe880ad4de81a2 on sethmcleod:master into 56f3f68f5d1170a084e081a9525842aca63784b6 on mxstbr:dev.


feat: add quorum_up and quorum_down in virtual_server

add missing virtual_server option: quorum_up and quorum_down.
Tests have been corrected accordingly.

Do we are agreed to use Optional[String[1]] as datatype for quorum_up/quorum_down? (I also made a mistake in the test corrections)
Should I just revert my last commit?

thanks @rotulet !


Add support for uuid::Uuid

Close #33

Thanks for the PR! Here are a few thoughts:

I'm in favor of accepting this impl if uuid doesn't want to derive it :+1:
The binary representation you chose differs from https://github.com/uuid-rs/uuid/pull/739. Theirs encodes a [u8; 16] whereas yours encodes a u128. There may be an alignment difference and, for that and other reasons, performance difference. I'll personally benchmark this before merging.
I'd like to use the strategy I used in https://github.com/SoftbearStudios/bitcode/pull/30 to avoid writing custom code each time we need to encode one type in terms of another. That's not reviewed/merged yet so this will have to wait.

Hi @finnbear, I use the new approach as you mentioned. Essentially just move ConvertFrom related code to a new mod and use that for encode/decode uuid. I let you decide which binary representation to go (u128 vs [u8;16]) but I think it is done on my side.

Thanks for this! Regarding the encoding process, @caibear has recently started experimenting with using uuid's support for bytemuck to make it more efficient than what I suggested. I'll keep you updated :)


Will IBM block storage CSI driver be supported in OCP4.6 on IBM Z?

Hello!
I am now trying to use OCP4.6 on IBM Z.
I tried installing IBM block storage CSI driver 1.4.0, and even pv and pvc were installed, but the POD is not mounted.
Is that because the provided documentation says that only OCP4.5 is supported?
If so, I am curious when it will be supported in OCP4.6.
Thank you.
OCP 4.6 equipment
-IBM Z
Storage equipment
-FS7200

I tried installing with OCP4.5 because it was a problem with the OCP version, but the same problem appeared.


Update example_fivetran_dbt.py

Moves dag initialization to only be with context creation

Thanks for the approval, nbd

I do not have merge access, so please do so as you're ready


Endless server-like lag when entering an empty machine (Singleplayer world)

Compact Machines version: 1.12.2-3.0.8-b200
(idk if it is a beta version but in the last version happened too)
Modpack: Enigmatica 2 Expert
Forge version: <IP_ADDRESS>73
I am not using Optifine: Without optifine
Link to Crashlog: I can't upload a log because the game does not crash, it stays there forever.
But with the minecraft log console says this:

14:35:22
FML
Server thread
warn
CoFH World loaded a new chunk [129, -4] in dimension 0 (overworld) while populating chunk [129, -3], causing cascading worldgen lag.

14:35:22
FML
Server thread
warn
Please report this to the mod's issue tracker. This log can be disabled in the Forge config.

14:35:27
net.minecraft.server.MinecraftServer
Server thread
warn
Can't keep up! Did the system time change, or is the server overloaded? Running 11922ms behind, skipping 238 tick(s)

Screenshot (if possible): https://imgur.com/a/j9kwDL5
Description of the problem including expected versus actual behavior: I have 2 compact machines of maximum size. With garden cloches and other with only a pulverizer and a furnace. When I tried to do the 3rd one I entered into it and the game lags forever, like in a server (is a singleplayer world). I tried to reproduce this bug in creative but in other world does not happen. I don't know why but if I turn the render distance to 2 chunks before entering the bugged machine it works normally.  And no, my pc is not a potato (i5-6600, 16gb ram with 8gb dedicated to mc, gtx 1050ti). On top of this post I put the log from minecraft console with the warning.
Steps to reproduce: As a said the steps are:
Playing a normal SP world, make 3 machines, the third one empty, when you enter it lags.

I guess this is a compatibility issue with some other mod in the pack. I can not reproduce this with Compact Machines alone. No idea which one though. Guesses?

This is actually a duplicate of #316 and a Ice and Fire Mod issue.


Multiple files in .require()

So, me and Sindre discussed the possibility of pulling in several files within one .require(). It would look something like this:
basket.require({
    "foo-1.2.3.js": {
      key: "foo"
    },
    "bar-3.2.1.js": {
      key: "bar",
      overwrite: true
    }
  })
  .wait(function() {
    // use pulled-in files
  });

I love it! One very very minor concern: would supporting so many signature variations confuse people? Like..could/would someone use an inline callback in any of the objects passed to require in the below?
On 8 Mar 2012, at 19:37, Andrée<EMAIL_ADDRESS>wrote:

So, me and Sindre discussed the possibility of pulling in several files within one .require(). It would look something like this:
basket.require({
   "foo-1.2.3.js": {
     key: "foo"
   },
   "bar-3.2.1.js": {
     key: "bar",
     overwrite: true
   }
 })
 .wait(function() {
   // use pulled-in files
 });

Reply to this email directly or view it on GitHub:
https://github.com/addyosmani/basket.js/issues/25

I guess it could, we might need to streamline the API a bit if we choose to support this. If we support inline callbacks, I don't really see a reason to use .wait() for individual callbacks at all. I.e.:
basket
  .require('foo')
  .wait(fn)
  .require('bar')
  .require('baz')
  .wait(fn);

would become moot.
Maybe we should only support the .require({}) syntax? With additional: .require({}, <callback when all has been pulled in>) and just ignore .wait() all together.

We definitely should go the Python way and only have one true way of doing it.
I'm in favor of only supporting the .require({}) syntax.

Actually, using an object straight up might be bad, that's not guaranteed to be parsed in that order, right? So...
basket.require([
  {
    url: 'foo-1.2.3.js',
    key: 'foo',
    overwrite: true
  }
]).wait(fn);

?

Correct, good eye. Though since we only accept on argument to require, we could drop the array, and just use infinite arguments?
basket.require({},{},{});

Yeah, that would make sense. I'll say go for that syntax. And while someone are at it, make .add and .require use the same logic behind the scenes. Or do we actually need both?

I've also noticed there are some duplication between them. It is however useful to be able to only load a script into localStorage for later use. Preloading. But we could drop the .add() method and instead just have a property in our .require() method:
basket.require({
    url: 'http://website.com/foo.js',
    id: 'foo.js',
    execute: false
});

I actually like that suggestion. Perhaps include add() as merely a convenience method that pipes back to the below if it stays?
On 8 Mar 2012, at 22:36, Sindre<EMAIL_ADDRESS>wrote:

I've also noticed there are some duplication between them. It is however useful to be able to only load a script into localStorage for later use. Preloading. But we could drop the .add() method and instead just have a property in our .require() method:
basket.require({
   url: 'http://website.com/foo.js',
   id: 'foo.js',
   execute: false
});

Reply to this email directly or view it on GitHub:
https://github.com/addyosmani/basket.js/issues/25#issuecomment-4404453

We could, but I'm not sure we should, although I don't really have that strong opinion about it. We should be careful about having sugar that doesn't really save that much typing and it gives the user multiple ways to do one thing.
The point of having a powerful .require method is that they can do all the loading in one method. If we introduce the .add sugar. User will start to do this:
basket.add({
    url: 'http://website.com/foo.js',
    key: 'foo.js',
    hash: '123'
}).require({
    url: 'http://website.com/foo2.js',
    key: 'foo2.js',
    hash: '123'
});

When this, in my opinion, looks better:
basket.require({
    url: 'http://website.com/foo.js',
    key: 'foo.js',
    hash: '123',
    execute: false
},{
    url: 'http://website.com/foo2.js',
    key: 'foo2.js',
    hash: '123'
});

I'm a -0 on this.

I think .store() instead of .add() would be a bit clearer on what the difference is, but I do agree that they'd be rather confusing at first glance.


Update reference to dbt version on Mac upgrade instructions

Description & motivation

I was visiting these instructions and noticed they referenced 0.15.1
I can't imagine that you're planning on keeping this up to date, but I thought I'd submit an PR to help get this up-to-date
To-do before merge

Approve?

@clrcrl I can't assign to you but tagging you 😄


[request] service discovery

feedback  from a developer:
There is one really cool use-case for kong I see: providing service discovery for Mesos. Currently there are several solutions for this like mesos-dns, bamboo, haproxy script that comes with marathon or even my own marathoner. DNS-based solutions suffer from delayed updates of service map and haproxy-based solutions suffer from often reloads of haproxy. Old instances of haproxy stay alive for a while and eat up resources and pid table, spawning new instances requires creation of a new process. Deploying 100-instance app over a cluster of 120 machines really shows how inefficient things are.
Kong could be a really good solution for the problem, taking in account all the plugins, efficiency of nginx and lua scription and all other goodies. The only problem is that you cannot dynamically set upstreams, same problem with haproxy. When this is fixed, kong would shine for service discovery.
Take a look at zoidberg, combined with could it could be a good solution.

Related to #157

:+1:

:+1:

yes, ability to modify upstreams from plugin would be really beneficial, is it will allow discovery service integration

I don't think I grasp the full request made here.
Currently Kong can already be used for service discovery by creating an upstream with several targets. Say you create an upstream (a Kong loadbalancer) by name my-service-v1. To this upstream you can add target entities; ip/port/weight combinations. So add for example <IP_ADDRESS>:80 and <IP_ADDRESS>:80.
If you then configure a route and a service, where the service has a hostname specified as my-service-v1, Kong will route the traffic to the 2 IP addresses configured.
The dynamic part is that new containers spinning up can be added to the my-service-v1 upstream by a call to the Kong management api. Either the container themselves do it, or the orchestration tool you use. Kong will start routing traffic there, without any reloads etc.
Does this cover this topic, or are there additional features regarding service discovery, that are missing?

@Tieske - in real cloud env. we usually have dedicated server registry/discovery service, like Eureka or Consul or Something. Kong upstreams/targets are not really a replacement, at least now, for the dedicated discovery service.
Upstreams/Hosts, I know it is based on nginx capability and I think it has only REST API, not sure if functional access is available.
What we're testing is following, global plugin scans "a registry" service, and updates/creates upstreams and hosts based on some logic and registry information, yes it does HTTP calls to http://localhost:.
First Question, is this approach sound to you?
Why I think this is important, it allows flexibility, support of the legacy infrastructure and allows to serve "dynamic" services that are produced in a cloud environment via Kong, including containers.
Also it allows automatic Red/Black and Canary deployment, you just specify some predefined tag in registry metadata and Kong plugin will provide correct weight for the host, allowing correct traffic.
Second Question, should be such methods, that are, manipulation of upstream/host to be part of PDK


Basic extrapolation of join button functionality into component

src/components/Group/GroupHeader

Removed join btn from header, imported component
Refactored header styling Burhan to fix

pages/group/index.tsx

Added JoinBtn component, # of members

Urge to merge rising

Urge to merge rising

feel free to review!


[BUG] Abnormal nodes stats in indexing/search metrics during on-going index/shard closure.

Describe the bug
Node level stats are supposed to be monotonically increasing in nature until the node is restarted but this principle doesn't hold during a race condition when there are index or shard closures going on in parallel.
If there are one or more shard closures or index closures happening in parallel with nodes stats execution then during fetch of any stats of shards whose states have changed to closed, either an IllegalIndexShardStateException or an AlreadyClosedException is thrown which is ignored here and stats of the respective shard are skipped in the response. This inconsistency of lower nodes stats values being returned in response only stays until beforeIndexShardClosed of oldstats is invoked.
How is this still possible when beforeIndexShardClosed is updating old shard stats before shard is closed ?
Delta shard stats are computed here by iterating over in-memory map of indices of IndicesService and then over in-memory map of shard ids present in IndexService against each Index. Before method beforeIndexShardClosed gets invoked index gets removed from the indices map here and similarly shard gets removed from shard id map here . Between removing an index or shard from the respective in-memory map and invoking beforeIndexShardClosed if any stats request comes in, it will only be able to return yet to be updated value of old shard stats.
Related component
Indexing
To Reproduce
This isn't easy to reproduce as stats needs to be invoked at certain intermediate state. An integ test can reproduce this.
Expected behavior
Lets explore what options we have:

Swapping execution of removing index or shard id from in-memory maps with closing index/shard. We probably don't want to delay removing shard or index from node on a close request and this will also not completely resolve the issue as there are still multiple race conditions such as a shard gets closed and by this time old shard stats are not yet updated, etc.
Changing sequence of shard stats fetch and old node stats fetch will also not work because of similar race conditions.
Unless we develop a coordination between index/shard closure and stats update, there isn't any solution which can resolve this and building this seems an over kill. The simplest approach would be to gracefully handle this scenario on the client side by maintaining a shard_count field in node stats so that whenever client sees a lower node stats value and a lower shard_count then it can simply ignore that event (or decide whatever it wants to do with it).

Sequence in which stats are fetched today is old stats which store stats of the shards previously assigned on the node are copied to a local variable, stats of current shards are fetched and then these are merged to old stats local variable and returned.
Assuming R-> Remove index/shard from map, O -> Copying old stats in local variable, C-> Shard or index closure, D-> Delta stats of the current shard. And (R happens before C and O happens before D)
Following combinations are possible and all result either in lesser shard_count and lesser node stats value or correct node stats.

ORCD -> Less
ROCD -> Less
RCOD -> Correct
ORDC -> Less
ODRC -> Correct
RODC -> Less

On receiving lesser shard_count and lesser node stats, client can either choose to re-invoke stats or ignore the event.
Edit 1:
Even with just shard_count we won't be able to distinguish between node restart case and shard closing case. We need to keep another in-memory counter which tracks count of removed shards and increments whenever an index or a shard is removed from indices or shard map. In stats execution, we can match removed count with oldShardStats shard_count and if match fails then we can return a field partial_results set to true in the response. We can still send shard_count as an additional info. We also need to distinguish b/w an index closure and a shard closure and prevent counting shards again when index is closed in the parent path.
Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@vikasvb90 Nice find!
I have couple of thoughts in regard to proposed solution:

Instead of maintaining shard_count in stats, we can maintain a inflight_shards_closure variable, the value is incremented post shardId removal from shards Hashmap here and decremented at the end in beforeIndexShardClosed. inflight_shards_closure will be reset to default value 0L on process restart. Additionally, I propose that close/remove state management should operate at shard level as a shard can be closed for reasons other than index removal (Stale Shard copy, Routing update failure) - the index removal proceeds the shard closure, so in case where index is removed from hashmap(A) but shards have not been closed (B), and a stats request comes in, the response is computed ignoring the removed index.
Instead of partial_results, we should respond with field stale_results to hint 'the cumulative statistics also account for shards that are no longer on this node, which is tracked by oldShardsStats'. This information is present as a code comment, we can look into adding this to public documentation in context of newly added field stale_results.
On Client side handling of stale_results, it should be treated as missing data and re-tried with back-off.
I am wondering if we need the additional field shard_count in stats response; should it map to shard_count in oldShardStats or a f(oldShardStats, statsByShard, inflight_shards_closure) ? Alternatively, partial_results field would suffice to communicate to client that the result returned is Stale due to currently inflight shard actions.

@khushbr

As we discussed, there are race conditions in incrementing and decrementing inflight_shards_closure. Also, we in case of failures in shard closure, we can't guarantee the variable to get decremented. If we return partial_results as true and if client as built retries on it then client will repeatedly invoke stats and can never have get a proper response resulting in missing metric points indefinitely.
stale denotes something is outdated but in our case something is missing (stats of some shards) and hence, the name partial. Open to other thoughts.
We cannot afford to just have counting only at shard level as there may be race condition between an index close and a shard close.
shard_count I proposed this just to return an additional info in stats

Also, we can completely eliminate even this rare condition by swapping removal from map and updating in-memory closed shard count.

What happens if the stats API requests lands between removal from Index Map and before updating the in-memory closed shard count. Within an index, we can have 'n' shards and closing each shard(And the corresponding 'oldShardsStats' update) is sequential operation.  Maintaining 2 counters - Index closed and shard closed will still not guarantee strong consistency.

We don't need two counters. Just one counter for overall shard count. Also, as I said, we first update the in-memory shard closed count and then update index or shard map.

Thanks @vikasvb90 and @khushbr for discussion on the possible solutions. This gives good context.
The stats APIs are not strongly consistent API but considering these are cumulative metrics at node level, it doesn't provide good user experience if the value goes down. @vikasvb90 you can return partial but it doesn't give any idea which metric is impacted, would this partial status be at node level or for overall stats API? In order to figure what partial means here user would need to compare against previous value of each metric to understand partial here. Bulk API is different, you get doc level status, you know exactly which doc passed/ failed. Similarly, searches can be partial but user decides on which query to get partial response and application would have handling for the same as well. In either call you dont need previous state to understand the impact of partial.
Lets explore the closed shard count counter approach further (as long as it doesn't impact applying the cluster state).

I did a dirty POC for a fix based on keeping track of shard stats b/w Index removal from Hashmap and update of OldShardStats. PendingShardClosure is a ConcurrentLinkedQueue storing the shards pending closure, the new IndexShard elements are inserted at the tail of the queue.
Add IndexShard to pendingShardClosure queue in removeIndex()
                // For this Index, add all IndexShard refs to pendingShardClosure queue
                IndexService indService = newIndices.get(index.getUUID());
                while (indService.iterator().hasNext()) {
                    pendingShardClosure.add(indService.iterator().next());
                }
                indexService = newIndices.remove(index.getUUID());
                assert indexService != null : "IndexService is null

Remove IndexShard from pendingShardClosure before adding to OldShardStats in beforeIndexShardClosed()
public synchronized void beforeIndexShardClosed(ShardId shardId, @Nullable IndexShard indexShard, Settings indexSettings) {
            if (indexShard != null) {
                // First remove IndexShard from pendingShardClosure queue before updating OldShardsStats
                final boolean removedShard = pendingShardClosure.remove(indexShard);
                if (removedShard)
                    getStats.addTotals(indexShard.getStats());
                    indexingStats.addTotals(indexShard.indexingStats());
                    // if this index was closed or deleted, we should eliminate the effect of the current scroll for this shard
                    searchStats.addTotalsForClosingShard(indexShard.searchStats());
                    mergeStats.addTotals(indexShard.mergeStats());
                    refreshStats.addTotals(indexShard.refreshStats());
                    flushStats.addTotals(indexShard.flushStats());
                    recoveryStats.addTotals(indexShard.recoveryStats());
            }
        }
    }

Make local copy of pendingShardClosure; For each IndexShard, add the stats to commonStats in stats(). This is done after OldShardStats computation.
        final IndexShard[] pendingShards = pendingShardClosure.toArray(new IndexShard[0]);
        for(IndexShard shard: pendingShards) {
            for (Flag flag : flags.getFlags()) {
                switch (flag) {
                    case Get:
                        commonStats.get.add(shard.getStats());
                        break;
                    case Indexing:
                        commonStats.indexing.add(shard.indexingStats());
                        break;
                    case Search:
                        commonStats.search.add(shard.searchStats());
                        break;
                    case Merge:
                        commonStats.merge.add(shard.mergeStats());
                        break;
                    case Refresh:
                        commonStats.refresh.add(shard.refreshStats());
                        break;
                    case Recovery:
                        commonStats.recoveryStats.add(shard.recoveryStats());
                        break;
                    case Flush:
                        commonStats.flush.add(shard.flushStats());
                        break;
                }

In summary, without taking a lock, we cannot guarantee consistency. In this solution, depending on the order of execution of events - the response can end up having double or missing data.
A - Remove IndexShard from pendingShardClosure queue in beforeIndexShardClosed()
B - Add stats of IndexShard  to OldShardStats in beforeIndexShardClosed()
C - Make Local copy of OldShardStats in stats()
D - Make Local copy of pendingShardClosure in stats()
To reduce the chances of adding double value, we enforce (A) must happen before (B) and (C) must happen before (D).
In following scenarios we will see missing data: ACDB, ACBD, CABD, CADB.

Alternatively, we can solutionize to track for inconsistent race condition state with greater accuracy.  On detecting such scenario, the engine will throw an Exception, which for Node local stats with show up as 5XX and in cluster stats, the co-ordinator will handle the exception and return empty json for this node in response.
@shwetathareja  @vikasvb90  Let me know what you think.

I agree. Higher the number of different in-memory state updates and higher the execution b/w these updates and updates in the in-memory maps, higher will be possibilities of race conditions.
That's why initial solution of keeping a single monotonically increasing counter right before map updates drastically reduces inconsistency in determining state of stats based on which an indication in the form of 4xx and an empty response can be provided which would be close to 100% accurate.


More random player choices

The original version would iterate through the player list for distance determination, so that the player list would always be in a certain order when the server was not restarted, resulting in the players at the top of the list being given the right to choose the mini-game every time the lobby was launched
The new version shuffles the player list before each traversal, so that each traversal of the player list is done in a different order, ensuring fairness and randomness
原来的版本遍历玩家列表判断玩家的距离，但是玩家列表在重启前保持一个特定的顺序不变，于是导致在列表前的玩家更容易获得选择小游戏的机会，新的版本在每次遍历前打乱玩家列表，这样就保证了选择的随机性

Hello friend, write to me in the discord risottomen.

If you can, correct the schematics and code. Thanks


Name defination suggestion for this doc

What is the purpose of the change
We should keep name of variable defination style as same.  On this doc, you use  for azure adls gen2 storage container name. However, you add more charactor $ for storage name($). I think it is unreasonable and it will cause the confusion for the reader. Therefore, I recommend to remove this charactor($) of the storage number for keeping same name defination style.
Brief change log

remove the $ for the storage acount name reference.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes)

Closed due to inactivity


[stable/drone] Bump drone version to latest available image v1.6.1

What this PR does / why we need it:
Use the latest stable drone release from the official repo: https://github.com/drone/drone/releases
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @christian-roggia

/ok-to-test

/lgtm


Support for tr-181 SoftwareModules datamodel for DAC

Adding the code changes from this commit, which were asked to upstream to this repo.
'81951: RDKBDEV-1645: Support for tr-181 SoftwareModules datamodel for DAC | https://code.rdkcentral.com/r/c/rdk/components/generic/rdk-oe/meta-rdk/+/81951'
https://code.rdkcentral.com/r/c/rdk/components/generic/rdk-oe/meta-rdk/+/81951

 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.

Closing this, and I shall commit with my work account, which has signed the CLA


The number of reactions remains at 0

Hello,
The proposed script works very well so far.
However, the reactions (likes, love, haha, etc.) remain at 0.
Is it because of Facebook's language?
If so, I've set it to English. However, the pop-ups remain in French when scraping.
Any advice?
Thanks for helping!
#import Facebook_scraper class from facebook_page_scraper
from facebook_page_scraper import Facebook_scraper

#instantiate the Facebook_scraper class

page_name = "ffkarate"
posts_count = 10000
browser = "firefox"
proxy = "user:password@IP:PORT" #if proxy requires authentication then user:password@IP:PORT
timeout = 100000 #600 seconds
headless = False
meta_ai = Facebook_scraper(page_name, posts_count, browser, proxy=proxy, timeout=timeout, headless=headless)

Hi @uroux Sorry for the late reply Yes, language is a blocker for parsing reactions here. Please consider using proxies


azmq: init at unstable-2023-03-23

Description of changes
C++ language binding library integrating ZeroMQ with Boost Asio.
https://github.com/zeromq/azmq

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofborg build azmq
@ofborg test azmq

@ofbord build azmq.passthru.tests

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/1016/71


Scaling is not restored under resizing in equal-scale mode

ScottPlot 4.1.09-beta
In order to display some tool path data in an intuitive way, I try to maintain equal scaling of axes of a WpfPlot by calling Plot.AxisScaleLock(). It turns out that although the scaling is equal under several resizing operations, the shared scaling could not be restored when the plot was restored to some previous size after downsizing, which leaves the object in a smaller state.

The above gif was recorded with Polar axis demo of WPF demo 4.0.22 and the same can be observed with the one of 4.1.09-beta.
The reason that I tested with 4.0.22 is that the scaling change shown in #272 does look as expected, which I believe introduced this mode originally.  In fact, in the same WPF demo 4.0.22, the WpfConfig demo works in a more natural way and is shown in the following two gifs (as the behavior is different for x and y resizing).

It seems that two demos use different implementations of equal-scale mode. WpfConfig demo uses the previous implementation Plot.AxisEqual() where scaling (UnitsPerPixel) of y is applied to both axes. And Polar axis demo uses the newer implementation Plot.EqualAxis which adopts the larger one, a strategy inherited by the current implementation Plot.AxisScaleLock().
So is it possible to have the option of maintaining equal scale in the old way? Thanks.

Hi @ricecakebear,
Unfortunately, I found time to return to this question just now, I made a PR #933 that allows you to select an axis that will be the source of the equal scale. If you select YAxis it will be close to the old Control level behavior as you described.
If you can find time for tests, I would be happy to receive feedback from you,

Thanks @ricecakebear for the original suggestion and @StendProg for your PR #933! I got unexpectedly busy this last week so I haven't had much time to work on this, but I'm starting to be more free again and I think I came up with a good solution...
I'm adding an enumeration to define the scale mode:
void AxisScaleLock(bool enable, EqualScaleMode scaleMode = EqualScaleMode.PreserveY) { /* */ }

I agree with @ricecakebear that the present default behavior ("zoom out") is astonishing. I'm changing the default scale mode to be preserve Y which is consistent with previous versions of ScottPlot. These screenshots show all the scale modes available:
AxisScaleLock: Disabled

AxisScaleLock: Preserve Y

AxisScaleLock: Preserve X

AxisScaleLock: Zoom Out


Adjust ci script for core deprecation removals

Just checked there should be no automatic config applied for the http cache config changes, so this should be all that's needed, let's merge and see if the schedule is fixed


add copy 📋 button the text fields

What is the current behavior?
https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#webhook-payload-example-32
pre blocks in docs look like they did a year ago in GitHub issues

What changes are you suggesting?

GitHub issues (like this one) have a 📋 at the top right of
pre
blocks

Which lets users copy their contents
Additional information

#3056

👋 @jsoref Thanks for opening an issue! To clarify, are you saying that you think our code blocks should include a copy button?

Yes.

https://liff.line.me/1454988218-NjbXbq18/v2/page/hotclip?utm_source=copyshare

echo "# Karitt-Sununta" >> README.md
git init
git add README.md
git commit -m "first commit"
git branch -M main
git remote add origin https://github.com/Karitta123/Karitt-Sununta.git
git push -u origin main

@adsingh14: Not understanding the repo, I naively assumed it would require work by engineering, but, perhaps I'm wrong.
Guessing (quite likely wrong again), it might be possible to do the work here:
https://github.com/github/docs/tree/main/components/ui
If I were investigating, I'd start by looking into how https://github.com implements this feature, since, ideally other github sites would share behavior/implementation.

No
3/2021

It seems like they do have copy buttons, but only when they are explicitly set. It would be nice if every code block had a copy button.
Reference
https://github.com/github/docs/blob/da5fb554bf6ced2d3ef8f550461617971590cca0/contributing/content-markup-reference.md?plain=1#L77-L83
Live Example
Configuring issue templates for your repository
https://github.com/github/docs/blob/da5fb554bf6ced2d3ef8f550461617971590cca0/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md?plain=1#L86-L95

Indeed. The code is here:
https://github.com/github/docs/blob/main/lib/render-content/plugins/code-header.js
I'd suggest changing the code to honor :nocopy and adjusting it so that unless it sees {:nocopy}, it always adds a copy block. That'd be the easiest thing. If there's no language specified, the left edge could either be empty ( ), or have Example or Text or something similar (I don't have a strong opinion).
A fancier thing would involve adding code for the case where the language isn't tagged and convincing the copy widget to hang inside the block and autohide unless the mouse hovers over where it'd be. Looking at the acrobatics that the current code is performing, it wouldn't shock me if that isn't possible, so, I think the simple approach is best.

👋 Thanks all for the feedback in this issue. I spoke with the team and we are going to work on this internally. So I'm going to go ahead and close this issue.
Thanks again! 💛


Pinned and updated bingo to v0.2.1

Signed-off-by: Bartlomiej Plotka<EMAIL_ADDRESS>

Thanks Kemal, yea I need to fix bingo first ;p https://github.com/bwplotka/bingo/issues/25


Update README.md

Description
Please include a summary of the changes and which issue is fixed or feature introduced. Include relevant motivation and context, and explain how it benefits all/most users, not just yourself.
Fixes #(issue number)
Type of change

[X] Documentation or repository updates
[ ] Bug fix: non-breaking change which fixes an issue (patch version)
[ ] New feature: non-breaking change which adds functionality (minor version)
[ ] Breaking change: fix or feature that would cause existing functionality to not work as expected (major version)

Checklist

[X] I have read and comply with the contributing guidelines.
[ ] I have tested my code for new features & regressions on my local installation, using the latest version of Homebridge.
[ ] I have made corresponding changes to the documentation (README.md and plugin settings descriptions).

Moving recommended comments to a separate read me for beta versions


Negative values

Thanks for sharing this awsome project.
Is there a way to have negative values? say from -100 to -10? (app:sv_maxSpeed="-10" and app:sv_minSpeed="-100")
It seems that it only accept positive values.
Thanks!

It seems changing both max & min speed from xml has an issue.
I'll fix this issue in the next version. For now you may assign the values from your code using setMinMaxSpeed(min, max) method.
Thanx for contributing.

Awsome! Thanks a lot for your quick reply!
It works from the code. Not a big deal for now if it doesn't work from the layout.
Thanks!

Workaround: Can be changed from the code.


Faster rebuild (and hot-loading) infrastructure

This is a question.
My mind is blown by the performance in Metro.  I want that in CRA apps, so badly.  Instead, out of the box on a moderate-sized codebase (<100kloc), we're seeing ~9s rebuilds.

But is the rest of the slowdown inherent to webpack?  I'm also seeing Vue 3 CLI demoing sub-second rebuilds (though on a small example codebase; webpack 4 still likely doesn't scale as well as Metro):
https://twitter.com/TheLarkInn/status/995463935535996928
What's the path to better rebuild (and thus hot reloading) performance?  I just wanted to start this discussion to better understand how to get there/what the issues are.

@zxti sucrase isn't solution, you right, performance & speed of building will be improved by almost 75%, but sucrase is only for modern browsers (even async/await not transforming). For DEV env i want to be nothing should be used for JS, as Chrome 74+ supports almost any ES2018+ features, so for production sucrase isn't solution.


SECURITY.md

Reference Issues/PRs
What does this implement/fix? Explain your changes.

SECURITY.md added

Any other comments?

@AHReccese GitHub has changed the 'macOS-latest' alias to 'arm64' architecture which doesn't contain some Python versions. Consequently, the 'macOS' version has been fixed to a stable version (13).

@AHReccese GitHub has changed the macOS-latestalias to arm64 architecture which doesn't contain some Python versions. Consequently, the macOS version has been fixed to a stable one (13).

Impressive, well done.

I thought it was a simple cache miss, which I ran into before and by re-running it gets fixed(which it doesn’t here).
@sepandhaghighi


在mac上运行make image搭建环境时失败了

(you don't have to strictly follow this form)

Bug Report
Briefly describe the bug
The result you expected
How to Reproduce
Version

since FoundationDB cannot work propertly in Docker on Apple Silicon machines, docker build does not work on mac m1/m2.

Fails on installing dev dependencies, is there a network issue?

since FoundationDB cannot work propertly in Docker on Apple Silicon machines, docker build does not work on mac m1/m2.

Thanks, maybe I need to change a developing environment.


push mean, std deviation and error codes to graphite.

linked to this:
https://github.com/gatling/gatling/issues/2670
https://github.com/gatling/gatling/issues/2663

treat them as two separate issues. apologies.

Mean and std dev are pretty straightforward. Status codes aren't.

OK, I'll take Mean and std dev.


iOS7 support?

It is possible to add support for iOS7?

Definitely it's possible !!! We can add iOS 7 support, but I don't know when we have time to do it. We are open for pull requests. Thank you.

I was able to run the project in iOS Simulator with iOS 7.1 without any modifications.

Well I think this issue can be closed now. Thank you art-divin.

@maximletushov, I've tested on Simulator (iOS 7.0) and it works perfectly. Have you got some trouble on a device?

Resolved by #22
Thanks


first stab at migrating to TypeScript

@trevormunoz I migrated the code base to TypeScript. Dealing with the query results is... complex to put it mildly. I think we can identify better strategies to

produce a tighter graphql schema so that the resulting types are better defined (lots of nullable types that don't need to be so, for example, or inferred string | number types that can more firmly be one or the other.
come up with different strategies for merging data, e.g. associating people with their affiliations from a different table column

There's always benefits to using TypeScript, and I caught a couple of minor errors where the code looked up the wrong field, or where the field was missing. But dealing with these complex structures from AirTable may be more of a pain than needed.
Take a look if you can and see what you think!
NB the query types are generated the first time you run yarn develop npm run develop so make sure to do that before opening your IDE.

This looks worth merging so we can take advantage of the Typescript for ongoing development. One question: are the names of the interfaces all automatically generated? (I only skimmed the docs on this.) I would be in favor of not having them all named just Props but rather something more descriptive.

The name of types for queries are generated automatically. For example query PeoplePast will generate a type called PeoplePastQuery.
On the other hand, I added interfaces called Props. They are limited to component files and they model the properties that each component will receive, so it seems a fairly self-explanatory name to me. We could do something like ComponentNameProps instead?

Got it. Yes, I was thinking something along the lines of ComponentNameProps
On Mon, Jul 29, 2024 at 2:56 PM Raff Viglianti @.***>
wrote:

The name of types for queries are generated automatically. For example query
PeoplePast will generate a type called PeoplePastQuery.
On the other hand, I added interfaces called Props. They are limited to
component files and they model the properties that each component will
receive, so it seems a fairly self-explanatory name to me. We could do
something like ComponentNameProps instead?
—
Reply to this email directly, view it on GitHub
https://github.com/umd-mith/mith-static/pull/24#issuecomment-2256678734,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACVXEF2TUH5FKVXJM6D4ADZO2F6ZAVCNFSM6AAAAABLNC5MDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJWGY3TQNZTGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@raffazizzi Being able to run the type checker locally and in GitHub Actions (see https://github.com/umd-mith/mith-static/commit/cbdb0d607ab1dcd659f032aa17b6bea41e55506e) caught a few additional errors: https://github.com/umd-mith/mith-static/actions/runs/10166800582

Thanks for looking at this thoroughly, @trevormunoz. I'll merge for now and I will open a couple of issues for improving the code.


Using with Objective-C

Can I use it with Objective-C? If yes How?
I successfully import the file but did not get nay method. Please

Hi @imuhammadjabbar, I suggest to you to use Stack Overflow.
Open a question on SO and specify how have you include the library, errors and everything that can be useful.

@imuhammadjabbar to be more helpful to you, you can view this link:
https://github.com/pkluz/PKHUD/issues/83
Additionally, I am not aware of how to use the static methods present on the HUD class itself, only the ones available through PKHUD as shown in the issue above.


Update cluster-autoscaler.md

If running az aks update with "--enable-cluster-autoscaler", az CLI returns "Please run "az aks update --update-cluster-autoscaler" if you want to update min-count or max-count."

Thank you for the feedback!
I've confirmed the doc works as is.
The section you're suggesting changes to is for existing clusters without cluster auto-scaler enabled. For those clusters, the command works as docuemented.
The next section shows how to update settings on an existing cluster with cluster auto-scaler already enabled.
#please-close


[1.19.2] Alfheim - I'm getting blindness put on me always.

Any clues on what mod can cause it or how to get rid of it?

Note: When drinking milk, I see everything rendered normally, just for a moment. Then blindness re-applies immediately.

This happens, when you access the Alfheim dimension without properly playing through MythicBotany. (You haven't drunk from the mead of kvasir and therefore, you aren't able to experience Alfheim.)
Anyway: There is a config option (alfheim_locked) to disable this behaviour.

Thanks!
Would be good to inform about it somewhere on the mod description. Unaware admins checking if mod works may consider it is malfunctioning, like me did, LoL.


LESS styling Operation on an invalid type

Reproduction link
stackblitz does not want to change to less :/
Steps to reproduce
Install Antd-Zorro using ng add ng-zorro-antd
What is expected?
No error while compiling less styles (needed for custom themes).
What is actually happening?
[start:hmr:web] Module build failed (from node_modules/@angular-devkit/build-angular/node_modules/less-loader/dist/cjs.js):
[start:hmr:web]
[start:hmr:web]
[start:hmr:web]   &-round {
[start:hmr:web]     .btn-round(@btn-prefix-cls);
[start:hmr:web]   ^
[start:hmr:web] Operation on an invalid type
[start:hmr:web]       in node_modules/ng-zorro-antd/button/style/index.less (line 77, column 4)

After commenting the first thing out:
[start:hmr:web] Module build failed (from node_modules/@angular-devkit/build-angular/node_modules/less-loader/dist/cjs.js):
[start:hmr:web]
[start:hmr:web]
[start:hmr:web]   &-circle-outline {
[start:hmr:web]     .btn-circle(@btn-prefix-cls);
[start:hmr:web]   ^
[start:hmr:web] Operation on an invalid type
[start:hmr:web]       in node_modules/ng-zorro-antd/button/style/index.less (line 82, column 4)
[start:hmr:web] ℹ ｢wdm｣: Failed to compile.

After commenting both cases out, compiles successfuly.

Environment
Info

ng-zorro-antd
8.0.1

Browser
Not related

our doc site is built with 8.0.1 and custom theme, I am afraid you have to provide an repro repo

That's really weird, because while following the tutorial, after including the file: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/scripts/site/_site/doc/theme.less
I'm getting an error.
Here is an example:
bug.zip
The stacklitz... no words ... just crashes after when I want to import that LESS file directly.

@TheAifam5
I have check your zip file, your styles.less file is not the same as https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/scripts/site/_site/doc/theme.less plz check it again.

VS code extension Beautify will cause this problem,suggest to use Prettier for format.


ticdc: fix cleartext Transmission

What problem does this PR solve?

Issue Number: close #11428
What is changed and how it works?
Only allow local servers to access it to avoid attackers.
Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
 `None`.

/check-issue-triage-complete


Can not edit upgrade policy for workload

Rancher versions:
rancher/rancher:v2.0.1-rc2
Steps:

Create a workload with upgrade strategy Rolling: start new pods, then stop old
Upgrade the workload and change the strategy to Kill ALL pods, then start new

Results:
Upgrade failed with error Validation failed in API: Deployment.apps "abcd" is invalid: spec.strategy.rollingUpdate: Forbidden: may not be specified when strategy type is 'Recreate'

As mentioned in https://github.com/kubernetes/kubernetes/issues/24198 this error is not seen when updating the k8s deployment resource with:
spec:   replicas: 1   strategy:     type: Recreate     rollingUpdate: nil

Tested with latest build from master
Able to edit upgrade policy for workload when upgrading workloads.