This version has an issue when there are errors thrown

I already had a version of "any" that I made myself but I tried yours because it's shorter. However, I went back to my own version because yours has an issue when an error is thrown - it doesn't show it, instead I got an error from one of the failed promises that went into "any".
Here's my use case:
I have files named after their own SHA256 and I don't know which directory they are in. So I simply start the I/O operation (read or delete) on all directories and use the one that succeeds.
But before returning the contents of the file I add a little check. If I have an error in that then(...) I will see a "file not found" error from one of the failed promises instead of the error I throw.
module.exports.getHash = function (hash) {
    // Try all directories - see if any one attempt succeeds. We fail only if we
    // can't find the file anywhere.
    return any(Object.keys(STORAGE_DIR).map(type => {
        return readFile(
            path.join(STORAGE_DIR[type], hash)
        )
        .then(txt => {
            // Before returning the contents of the file verify its crypto-hash
            const verify = crypto
                .createHash('sha256')
                .update(txt, 'utf8')
                .digest('hex');

            if (hash !== verify) {
                throw new Error(`Crypto-hash verification of file stored as ${hash} failed, actual hash is ${verify}`);
            }

            return txt;
        });
    }));
};

It works fine with my much more explicit version of "any":
const any = function (promises) {
    return new Promise((/**Function*/ resolve, /**Function*/ reject) => {
        let countDown = promises.length;

        promises.map(promise => {
            return promise
            .then(resolve)
            .catch(err => {
                countDown -= 1;
                if (countDown === 0) {
                    reject(err);
                }
            });
        });
    });
};

Hi....i am not yet 100% sure if i understood your problem correctly. I have some test code made up:
var test = function() {
    return any([
        Promise.reject('fail')
    ], [
        Promise.resolve('ok').then(
            function() { throw new Error('Throw'); }
      )
    ]);
}

Is this a minimal testcase for your problem? If so i don't really get the problem about it. None of the promises succeeded so it is returning one of the errors (the first). if you change the order of the promises you will get the "throw" error.
Your version however is simply returning the error of the last promise :S
As to your use case i think your promise setup is simply wrong :o
wouldn't it make more sense to do an exists check wrapped in any() to first determine the correct location and then continue working on the correct location?

The test case is the code I gave. It works with my "any" and has the issue I described with yours. Your test case has none of the promises succeed, as you yourself pointed out.

As to your use case i think your promise setup is simply wrong :

Why?

wouldn't it make more sense to do an exists check wrapped in any() to first determine the correct location and then continue working on the correct location?

No. That's not how node.js works. You can read node.js documentation:

fs.exists() is an anachronism and exists only for historical reasons. There should almost never be a reason to use it in your own code.

PS: I added the readFile() that I'm using as helper function to my code sample.

You are right about the exists. Still I think your promise setup is wrong.
any() has been implemented for a use case "i don't care which of the promises is returned. any of them is ok". You seem to not care about where the file is located BUT that the hash is ok.
So (as far as i understood) are doing multiple things in the any() and using exists() or readFile() is not the point. The point is mixing up two things in the any().
you are doing:
any(
  multiple times
    readfile
    AND
    checkhash
)

So any() will only succeed if all of the above is true and if none worked out than it is returning one of the errors. And that's working. Your any() implementation just returns the error of the last promise (which is the throw() only because by coincidence the last promise returned the existing file). Try adding another directory which will be added at the end of the map and you will also get the same error with your version.
And this would be how I think (!) it should be done (though i am not completely into your use case obviously):
any(
   multiple times
      readfile
)
.then(
   checkHash
)

So first check and read (that's where I would have done an exists() only - which is not idiomatic to node as you pointed out correctly) all possible files determining the existing one and then check the hash separately and NOT in the any() as well.

The point is that my version of "any" works and yours does not. You can argue all you want but it won't change that simple fact. As for your calling what I do "wrong" - well, you are entitled to your OPINION. What is a FACT is, however, that my version of "any" works and yours does not. "Mixing up two things" -- YES, I'm programming and I do TWO things in one function. As I said you can have your opinion, for MY code this is the best solution. AND IT WORKS, when you use promises. It does NOT work with our version of "any".
Your analysis is frankly speaking, BULLSHIT:

Your any() implementation just returns the error of the last promise (which is the throw() only because by coincidence the last promise returned the existing file).

Can you read code? I DELIBERATELY LOOK FOR THE PROMISE THAT WORKS! It is NOT a "coincidence".
Useless conversation. Your stuff DOE SNOT WORK, period. And you can't even read code.

It is PERFECTLY ACCEPTABLE to chain a then() on a promise and do what I do!!! Learn about promises, child.

This might be a case of feeding the troll, but well...
@TimeForAChange
This implementation of ".any()" doesn't care for the errors which caused the rejection. The error returned is chosen at random for all intents and purposes (in this case, it's the first error, but it really doesn't matter).
Another valid approach is to return a list of all errors thrown, which is used here: http://www.effectiveui.com/blog/2014/11/11/promise-any-a-missing-use-case/
Kris Kowal's approach in his .any() implementation is to simply throw a new generic error. This is probably intentional to prevent exactly the thing you are doing in your code, i.e. using the any function for specific error handling.
       function onRejected() {
            pendingCount--;
            if (pendingCount === 0) {
                deferred.reject(new Error(
                    "Can't get fulfillment value from any promise, all " +
                    "promises were rejected."
                ));
            }
        }

As we can see, error handling varies wildly between .any() implementations. However, all implementations have in common that they are not geared towards specific error handling of the collated promises. Or, simply put, if you need to handle a specific rejection, don't use .any(). Which is exactly what @m0ppers suggests for your code with his pseudo-code example:
any(
   multiple times
      readfile
)
.then(
   checkHash
)

Using that approach you can handle errors thrown by checkHash explicitely. That way you don't rely on the details (or side-effects) of various any-implementations. I'd argue, that this would result in more robust code. If your code indeed relies on handling the "Crypto-hash verification"-error, I'd consider it brittle, because the order of elements in the array passed into the any function matters. That's the part which is "coincidental".
I'd claim, that you simply are not using .any() correctly, by expecting it to result in a specific rejection. Indeed with any (haha) other implementation of the any-function than your own, your approach would fail. So your version of any() is tailored to your odd usage of .any(). It doesn't mean that this implementation is not generic. Quite the opposite.
Given that you didn't even bother to provide a minimal test case (your example is full of noise and doesn't highlight the core issue), your little meltdown in the end is quite appalling. After @m0ppers provided some good critique of your code, you resorted to ad hominem attacks and shouting. I have therefore reported you.
Nightynight.

I have therefore reported you.

LoL, how HORRIBLE! Am I going to Guantanamo now?
 Yes, that DOES get me every time.

Yes, I think you are right. It's cleaner to append the then() after the any(). I changed my code.

However, after looking at it some more I continue to believe that my "any" is far clearer (to read) and that what I did was perfectly okay. It's slightly more logical to append the .then() but I see no reason why it should fail.
So in my "any" I only changed the variable name (your "pending" is better) and that I return a new error message tailored specifically for the "any".
const anyPromise = function (promises) {
    return new Promise((/**Function*/ resolve, /**Function*/ reject) => {
        let pending = promises.length;
        promises.forEach(promise => {
            return promise
                .then(resolve)
                .catch(err => {
                    pending -= 1;
                    if (pending === 0) {
                        reject(new Error('Cannot get fulfillment value from any promise'));
                    }
                });
        });
    });
};

and
module.exports.getHash = function (hash) {
    return anyPromise(Object.keys(STORAGE_DIR).map(type => {
        return readFile(
            path.join(STORAGE_DIR[type], hash)
        );
    }))
    .then(txt => {
        // Before returning the contents of the file verify its crypto-hash
        //....
        return txt;
    });
};

But even after accepting your suggestion, when the then() is with the readFile() there is nothing technically wring with this so an any that doesn't work... doesn't work.


retrieveTokenStatus Logic Not Matching Expectation

Summary
The logic to retrieve a token delegation status does not make sense in the current implementation as it strictly enforces a delegation to be made for a single token on the collection. This means that if I delegate for all tokens on a collection, this view function will return false for a specific token. In my opinion, this is broken logic and does not match the interface description.
Relevant Source Code
https://github.com/6529-Collections/nftdelegation/blob/50e3d171077b72cd043562cd0801fc188934bc94/smart_contracts/DelegationManagement.sol#L619
for (uint256 i = 0; i < globalDelegationHashes[hash].length; ) {
    if ((globalDelegationHashes[hash][i].allTokens == false) && (globalDelegationHashes[hash][i].tokens == _tokenId)) {
        status = true;
        break;
    } else {
        status = false;
    }

    unchecked {
        ++i;
    }
}
return status;

You can see that in the first if statement that the check requires that the property allTokens must be false. This means that all delegations currently coming from https://seize.io/delegation/delegation-center will cause this retreieveTokenStatus to return false as the frontend supplies a value of true for _allTokens in the call to registerDelegationAddress.
In addition, the expiration date is not checked in this function, which could be damaging based on how it is being used either off-chain or on-chain.
Potential Solution
for (uint256 i = 0; i < globalDelegationHashes[hash].length; ) {
    if ((globalDelegationHashes[hash][i].allTokens || globalDelegationHashes[hash][i].tokens == _tokenId) && globalDelegationHashes[hash][i].expiryDate > block.timestamp) {
        status = true;
        break;
    } else {
        status = false;
    }

    unchecked {
        ++i;
    }
}
return status;

This fix simply checks that the delegation hash for all tokens OR the specific token id passed into the function AND ensures that the expiry time is greater than the current block timestamp. In my opinion, this matches the expected use case for a function like this and doesn't require other function calls to check allTokens or expiry time.

The retrieveTokenStatus() function was designed as an additional function to check directly the delegation status given a token id. There are other retrieve functions which can help you check delegations either on all tokens or on a specific token as well as expiry date.
For example the retrieveDelegatorsTokensIDsandExpiredDates(...) function returns arrays of all delegators, tokenids, if they delegated on allTokens or on a specific token id as well as the expiry dates of the delegations. A developer can get those data and treat them as he/she wants :)

The retrieveTokenStatus() function was designed as an additional function to check directly the delegation status given a token id. There are other retrieve functions which can help you check delegations either on all tokens or on a specific token as well as expiry date.

This comment makes it seem like the purpose of the function is to check the current delegation status. If so, this MUST check all tokens and expiry date in my opinion. Otherwise, you are just returning invalid data that can be incorrectly used by third party devs.


ebiten: deprecate SetFPSMode and ScheduleFrame, and undeprecate SetVsyncEnabled

We discussed #2338 and FPSModeVsyncOffMinimum is useless: as the vsync is off, tearing happens and GPU power is consumed more than necessary. We might want FPSModeVsyncOnMinimum but it is odd that a FPS mode affects Update behavior in the first place.
Instead, let's give up blocking Update call for input, and instead, let's focus on a new API to handle input (#1704). This (Update is still called 60 times per second) might not be the best efficiency but is acceptable.
At the same time, ScheduleFrame should be deprecated too.

If we are in an FPS area, I would like to remind that it would be really useful to be able to explicitly set the maximum FPS somehow, https://github.com/hajimehoshi/ebiten/issues/1562 .
Players with old computers are deliberately reducing their FPSes to be able to use the system while the game is running, and game developers (especially beginners) would be able to debug the game and check if FPS has any negative impact on the game (ie. if there is any logic in Draw that should be in Update)

But how do I adjust FPS (refresh rate)?

We'll rever the optimization of skipping to swap buffers.

I think we should make another issue.


SAP UI5 Framework support

Hello!!
For supporting UI5/OpenUI5 framework, I did some changes and creating this pull request, please review the same and let me know.
PS: I am kind of new to this world of Type Script, VSCode and Open Source projects. So please let me know if i did any mistakes :)

LGTM! Your code looks very clean. Nice work! I will test it out tomorrow. Thanks!
It would be great if you can help with updating the wiki (it should be open for editing)

https://github.com/antfu/i18n-ally/wiki/Supported-Frameworks
https://github.com/antfu/i18n-ally/wiki/Locale-Formats

And for frameworks, a logo for UI5 would be preferred. You can upload it to the screenshots branch. Thanks!

Thanks :) I will start updating those documents.
Could you please me if there is any way to default the below config in framework itself, instead of manually entering in .vscode settings everytime.?
{     "i18n-ally.localesPaths": "webapp/i18n",     "i18n-ally.keystyle": "flat" }

Good point. I will make it possible

Released in v2.1.2. Now frameworks can contribute to default localesPaths keystyle dirStructure.
https://github.com/antfu/i18n-ally/blob/31e3d2e0e6b885ac092ec7d15bd95f5938b7d760/src/frameworks/ui5.ts#L54-L59

Released in v2.1.2. Now frameworks can contribute to default localesPaths keystyle dirStructure.
https://github.com/antfu/i18n-ally/blob/31e3d2e0e6b885ac092ec7d15bd95f5938b7d760/src/frameworks/ui5.ts#L54-L59

Awesome man, u r too fast.
I see you already have updated the screenshot as, <I am kind of still struggling to understand these branches and stuff in git, so couldn't do quickly>
BTW, I have a small doubt, not sure if this is the right place to ask, in VScode while extending i18n ally, i did f5 to start the extension, but when i put normal breakpoints they are not getting triggered, they are getting dimmed and mentioning that js source mapping issue..
If i hardcode a 'breakpoint' then it is getting triggered, (sadly i did changes like that :D)
I can see that it is building a single minimified file, but is  there any way to debug the typscript code directly here in the extension? (i already searched and found that the tsconfig you maintained is correct only, and couldn't find solution to this :( )
Thanks in advance,
Keep up the great work!!

I personally didn't use breakpoints. Just did a quick search but no luck either, I doubt whether vscode+webpack support that in the first place. But anyway, you can always use hardcoded debugger to do that job.
For the minified code in the debug, maybe you can try to uncomment the following line and try again: (I did that mainly for performance and I should probably revert it)
https://github.com/antfu/i18n-ally/blob/46ab268a57229e1d87d8ed33d9c24776591aa491/webpack.config.js#L19
Besides that, you are always free to ask me If you got any questions regarding the code.  I would love to help.
Oh, thanks so much for the donation btw. XD

Thanks man for the pointers, will try checking it out. I will surely reach out to you! Your project really made me curious in the vscode extension development and hope to start some small extension to learn more 😀
PS: it's not a donation, just a coffee on me for you 😉


No endpoint description with Nginx + uWSGI

There's something weird going on with my attempt to use swagger.
I'm using Django 1.8.2, Django Rest Swagger 0.3.2, and DRF 3.1.3
When running my app locally (runserver) I get the documentation just fine:

But when trying to use it on my development server with Nginx + uWSGI I get no documentation at all for the endpoints, but they are listed just fine:

Here's the response for /api-docs/api/v1/jobs:
{
    "swaggerVersion":"1.2",
    "apis":[
        {
            "operations":[
                {
                    "type":"object",
                    "notes":"",
                    "nickname":"Job_Resource_list",
                    "method":"GET",
                    "summary":""
                }
            ],
            "path":"/api/v1/jobs/",
            "description":""
        },
        {
            "operations":[
                {
                    "parameters":[
                        {
                            "paramType":"path",
                            "required":true,
                            "type":"string",
                            "name":"pk"
                        }
                    ],
                    "nickname":"Job_Resource_retrieve",
                    "notes":"",
                    "summary":"",
                    "type":"object",
                    "method":"GET"
                }
            ],
            "path":"/api/v1/jobs/{pk}/",
            "description":""
        }
    ],
    "models":{

    },
    "basePath":"http://xxxxxxxxx.cloudapp.net/api/v1",
    "resourcePath":"/api/v1/jobs",
    "apiVersion":"1"
}

Found it on http://stackoverflow.com/questions/8864628/empty-docstrings-when-running-django-piston-docs-under-nginx
uWSGI is starting up the interpreter in way equivalent to -OO option to Python command line. This second level of optimisation removes doc strings.
-OO    : remove doc-strings in addition to the -O optimizations
Change:
--optimize 2
to:
--optimize 1


Delete old easy-rsa remove

It isn't packaged anymore with openvpn in the supported distros

We also change the path of our easy-rsa in #653


Config JSON: Limit logging when there's no custom JSON file

Atm, if you retrieve a Config JSON setting and there's no custom JSON file, it logs this every time to try to retrieve that setting. This can flood your debug log.
I propose that it only logs once. The log message can be useful, but once it's been stated the first time, there's no need to repeat that statement.

Closed by: #138


feat(modulify-ui): library updates

Description:

Update the modulify-ui library:

Each method in ComponentBuilder can only be executed once; add a check for this.
Pre-render JSS styles on the server; add wrappers in _app.tsx and _document.tsx.

Update the patch file:

Fix RxJs error.
Enable server-side debugging in Next.js.

Apply modulify-ui to the most sought-after components for customization.

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[ ] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review


Fixes: Hiera errors on empty yaml files

If a completely empty yaml file is loaded then it will return false,
and if a yaml file is loaded with only '---' in it, it returns nil.
In either case hiera should handle the cases as expected instead of
erroring. This commit causes these answers to be considered the same as
if the file didn't exist at all.
This also fixes puppet hiera functions borking on empty yaml files.

Thanks, could you add some tests for this?
next unless data
Would probably be more inline with existing style


Cannot read property 'left' of undefined with react-virtualized Grid

Integration with react-virtualized Grid seems to work pretty smooth for me.
However an error occurs when you drag and scroll an item. The nodes are being unmounted and there is no prevNode when scrolling down.
Changing this:
translate.x = prevNode.edgeOffset.left - edgeOffset.left;
translate.y = prevNode.edgeOffset.top - edgeOffset.top;

https://github.com/clauderic/react-sortable-hoc/blob/master/src/SortableContainer/index.js#L637-L638
to this:
if (prevNode) {
  translate.x = prevNode.edgeOffset.left - edgeOffset.left;
  translate.y = prevNode.edgeOffset.top - edgeOffset.top;
}

and for scrolling up look for nextNode and change it to this:
if (nextNode) {
  translate.x = nextNode.edgeOffset.left - edgeOffset.left;
  translate.y = nextNode.edgeOffset.top - edgeOffset.top;
}

fixes the issue. Animation doesn't seem to be affected.
Maybe there is a better fix but at least react-sortable-hoc is working with react-virtualized Grid and +1000 items ✌
I will dig further into this to figure out why the Grid is causing this issue and the List doesn't.
@clauderic if you have any ideas or can point me in the right direction that would be great.
Seems to be the same as this https://github.com/clauderic/react-sortable-hoc/pull/326.
If anyone wants to test it, use my fork:
https://github.com/superandrew213/react-sortable-hoc/tree/fix-react-virtualized-grid-with-dist

@superandrew213
Hi, I try to integrate react-sortable-hoc with react-virtualized  Grid but I failed, do you mind if you can share basic code of the integration of react-sortable-hoc and react-virtualized Grid
Many Many Thanks :)


Documentation:  Add to programming strategy more examples on how we design a function

Please select a category the issue is focused on?
Developer Guides
Let us know where something needs a refresh or put your idea here!
Add to programming strategy: More of the good, the bad and the ugly examples of what we are aiming for with new functions in relation to all the guidance added for #954. Examples will help people to better visualize the points.
@bms63 @thomas-neitmann - @koegerr suggested best one of you guys take this on later as technical co-leads (fine to do this after the upcoming April release).

One thing I have noticed about admiral (and I don't know if this was intentional or not), is that it often wraps the tidyverse. So rather than call functions within mutate statements you will have a new_parm parameter. If this is intentional then, it should be added to the guidance, if it isn't intentional then we should probably discuss it. {metatools} does have some function like create_var_from_codelist that is like this, but also there are some smaller functions like create_subgrp which is vectorized.

I started working on a package template for pharmaverse packages.  Just a skeleton!  Nothign set in stone.   Maybe this issue should be moved over there https://github.com/pharmaverse/pharmaverse_templates

@bms63 i think your comment relates more to https://github.com/pharmaverse/admiral/issues/949 doesn't it? and for that i would suggest we make it more admiral specific (rather than pharmaverse) as we want to add in our specific pieces like our PR checklist and common package dependencies etc. happy to work with you on that one after the upcoming release, as i had it on my list to come back to this with learnings from admiralonco so far.
the issue here more relates to building on what we're adding for https://github.com/pharmaverse/admiral/issues/954 by adding some more examples to better explain how we want our new functions to be designed.

I was thinking that the functions that are used in all pharmaverse packages try to adhere to the similar design philosophy.  So the template would be a great spot to have these example functions.  A template within a template.  :)  This could still live inside our development guides in the admiral site or other guides with pharmaverse universe.

@rossfarrugia @thomas-neitmann  Can we close this issue?  I think our programming strategy captures most of our needs for "designing" a function to adhere to our admiral standards.

OK by me, sure this is something that will always continue to improve over time.


[WIP] Add Spelling check CI

Hi @shahzebsiddiqui, currently spellcheck runner has been integrated as part of Github Action workflow. However, is still failing right now because PySpelling detected a lot of false positive cases. We can either add all these words into .wordlist.txt so that these cases can be ignored or we need to kinda go through them one by one to decide.

Hi @shahzebsiddiqui, workflow is now working with the new github action. Currently, we only check on README.rst and CHANGELOG.md files. Please let me know if you want to include other folders/docs. Thank you!

Overall this looks good and checks are passing. Let's try to add the python directory for the code-base buildtest and then let's see what errors come up.

I am trying to see the useful of this CI check i think for most part there are a ton of errors that are not useful however i do see a few such as this one below where there is a spelling error recieved -> received
In that case we can fix the errors later and refine this list with the words such that we can avoid as much of these errors. We can let this check fail and over time the spelling error will cut down. Overall i think this check can still be useful even with alot of noise at first.

Hi @shahzebsiddiqui, I have made made changes based on your suggestions. Please review again!

Hi @shahzebsiddiqui, updated. Please review again!


Allow passing decimal precision as a prop for CategoryWidgetUI

Description:
Currently, the CategoryWidgetUI component of react-ui package does not provide a way to set the decimal precision when displaying the "Other" category that contains the sum of all remaining categories. This can result in an issue where adding two numbers with decimal precision can lead to unexpected results due to the limitation of JavaScript's floating-point arithmetic.
Below is the screenshot of this issue:

In order to avoid this issue, I would like to request an enhancement in the CategoryWidgetUI component that allows users to set the decimal precision for the "Other" category. This would enable users to ensure that the sum of all remaining categories is displayed accurately, without the need to manipulate the data beforehand.
Below is the code snippet which is causing this floating-point arithmetic issue:
File: https://github.com/CartoDB/carto-react/blob/master/packages/react-ui/src/widgets/CategoryWidgetUI.js
Snippet:
// Showing top or selected categories
        if (!blockedCategories.length) {
          const main = list.slice(0, maxItems);
          if (main.length < list.length) {
            const rest = list.slice(maxItems).reduce(
              (acum, elem) => {
                acum.value += elem.value;
                return acum;
              },
              { name: REST_CATEGORY, value: 0 }
            );
            return [...main, rest];
          } else {
            return main;
          }

Proposed Solution:
Ideally, this enhancement could be implemented by adding a new prop to the CategoryWidgetUI component, such as decimalPrecision, which would allow users to set the number of decimal places to display for the "Other" category. For example, if decimalPrecision is set to 2, the sum of the other categories will be rounded to two decimal places. If this is not feasible, I would appreciate any alternative solutions that can achieve the same goal.
Benefits:
This enhancement will provide greater control over the display of the sum of the other categories and prevent potential issues due to the limitation of JavaScript's floating-point arithmetic.
Thank you for your consideration.

Hi @azhars21, I am willing to work on this issue, Can you please let me know if this issue fixed on or is it still open?

@SibilSoren This is still open.

Hi @azhars21 , as per your proposed solution, the decimalPrecision which you mentioned should be provided by the user or we are just hard coding its decimalPrecision to 2?

@SibilSoren we can allow the user to pass the decimalPrecision(optional). If not passed we can default it to 2


Cannot add brackets to IPv6 address

Hello Everyone,
I tried to set brackets after a full ipv6 address, because otherwise the server not accept my connection.
Is there anyway how this is possible with the given arguments?
As i understand the source code message get lost after parsing the uri.
I fixed the problem temporaly by editing client.py in line 253 and adding the brackets manually.
from:
request_headers["Host"] = f"{wsuri.host}:{wsuri.port}"
to:
request_headers["Host"] = f"[{wsuri.host}]:{wsuri.port}"
After this everything works fine.
If you could provide me with a more accurate solution, I would be really glad.

The question is whether this is a bug in websockets or a bug in the server you're connecting to. What server is this?

Its a implemented Server, i don`t know the implementation of it only the protocol.
I only checked with a quick googlesearch, but on wikipedia there is a part claiming that urls should have brackets (or could I´m not quite sure).
I need to double check it with the IPv6 spezification to ensure if its a bug of the websocket lib or a bug on the server site.

So it seems that websockets has the same bug Firefox had... 20 years ago: https://bugzilla.mozilla.org/show_bug.cgi?id=45891

Oh okay. I will try to trace down deeper, where the brackets get lost. I think by parsing to URI and back. Quick solution would be check for IPv6 and add then the brackets, but it sounds for me like a quickhack.

This is the proper solution. Excerpt from the bug I linked to:

Note in particular the "Host" header.  RFC 2617 (HTTP) defines the syntax of the
"Host" header as:
      Host = "Host" ":" host [ ":" port ] ; Section 3.2.2
Section 3.2.2 gives the grammar of the http URL.  Therefore, for IPv6 literal
addresses the Host header needs to follow the RFC 2732 grammar for "host", just
as with URLs:
      host          = hostname | IPv4address | IPv6reference
      IPv6reference = "[" IPv6address "]"

So we have three cases for the host variable in websockets: hostname, IPv4 address, IPv6 address, and in the third case we have to turn it into an IPv6 reference by adding brackets.

Thanks for the bug report! That was a good catch.

Thank you very much for this great libary and the quick response. I was really impressed by the quick reply.


[WIP][HUDI-5357] Optimize deployment of release artifacts

Change Logs
Optimize upload release artifacts.
Impact
Release artifacts
Risk level
High.
Needs proper validation of the artifacts.
Documentation Update
NA
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Still need to verify if different avro versions should be set for hive, presto, trino bundles


Improved documentation and slightly improved documentation generator …

…to also generate descriptions.

@panilya  I've now added the descriptions to the generator too. Thanks, that was quite easy after you created the generator, nice work!

Codecov Report

Merging #315 (260223d) into master (d053424) will increase coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #315      +/-   ##
============================================
+ Coverage     94.88%   94.93%   +0.05%
- Complexity     1927     1928       +1
============================================
  Files           202      202
  Lines          3853     3853
  Branches        383      383
============================================
+ Hits           3656     3658       +2
+ Misses          100       99       -1
+ Partials         97       96       -1

Impacted Files
Coverage Δ

src/main/java/net/datafaker/Battlefield1.java
100.00% <ø> (ø)

src/main/java/net/datafaker/CNPJ.java
100.00% <ø> (ø)

src/main/java/net/datafaker/Code.java
97.70% <ø> (ø)

src/main/java/net/datafaker/Community.java
100.00% <ø> (ø)

src/main/java/net/datafaker/Computer.java
100.00% <ø> (ø)

src/main/java/net/datafaker/Fallout.java
100.00% <ø> (ø)

src/main/java/net/datafaker/FinalSpace.java
100.00% <ø> (ø)

src/main/java/net/datafaker/GarmentSize.java
100.00% <ø> (ø)

src/main/java/net/datafaker/MassEffect.java
100.00% <ø> (ø)

src/main/java/net/datafaker/SoulKnight.java
100.00% <ø> (ø)

... and 3 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

I moved logic to Column enum and it makes it much easier to add new column
now in case there is a need then just add one line at https://github.com/datafaker-net/datafaker/pull/315/commits/eea396763e677f3ebd575ed2cba5e6344e4e642a#diff-829e8c91f3a1a76f619adccc4050e582f420b47530179dff7d50155d03928f19R126-R127
and a new column will be generated
also i left only one flush instead of flushing after each write

I moved logic to Column enum and it makes it much easier to add new column now in case there is a need then just add one line at eea3967#diff-829e8c91f3a1a76f619adccc4050e582f420b47530179dff7d50155d03928f19R126-R127 and a new column will be generated
also i left only one flush instead of flushing after each write

Thanks. I think there's a few other ways to improve it, but this could potentially be a good class for learning some solid coding or so in the future. Good news is that the code works well, no we only have to add 100s of descriptions to the fakers and the documentation will be even better.


Use malloc/free in leak checker

Because I have a pending global gpr_mu allocated in #17308 and it never gets freed. Using gpr_malloc/gpr_free here will cause our memory counters to report an leak.
Since asan should still be able to report the leak_checker object is leaking when there is a real leak. I think this PR does not break that.

@hcaseyal Yes. Based on this PR, I reverted the changes of test/core/end2end/inproc_callback_test.cc and ran with asan and it still fails with a reported leak.

Test failures: #18111 #17561


i can't send mail it shows hard fail ,,,help me please

when i send mail it shows hard fail on my postal smtp help me please

If you click on Show Technical Details you will get more information about why the message hard failed which should tell you why it did.


Typo fix

[x] Closes #1814

[x] I am familiar with the contributing guidelines

[x] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).

[x] Pull request is nearly complete and ready for detailed review.

[x] Maintainer: Appropriate GitHub Labels (including remote-data) and Milestone are assigned to the Pull Request and linked Issue.

See linked issue.

By the way @echedey-ls you rock! Thanks for all the work you've been doing, its appreciated 😄

Thanks to y'all! Contributing has made me learn a lot of things and now is one of my favourite ways to spend my free time ;)


copr: implement macro match_template_collator

Signed-off-by: Dian Luo<EMAIL_ADDRESS>
What have you changed?

Add a new pattern to proc macro match_template.

For example,
match_template! {
    T = [Foo, Bar => Baz],
    match Foo {
        EvalType::T => { panic!("{}", EvalType::T); },
    }
}

generates
match Foo {
    EvalType::Foo => { panic!("{}", EvalType::Foo); },
    EvalType::Bar => { panic!("{}", EvalType::Baz); },
}

Add a new decl macro match_template_collator!() which maps collation variant to
a concrete Collator type, and it's used as

fn map_string_compare_sig<Cmp: CmpOp>(ret_field_type: &FieldType) -> RpnFnMeta {
    match_template_collator! {
        TT, match ret_field_type.as_accessor().collation() {
            Collation::TT => compare_fn_meta::<StringComparer<TT, Cmp>>()
        }
    }
}

For consistency, make match_template_evaluable!() and match_template_hashable!() decl macro 2.0 also.

What is the type of the changes?

Engineering (engineering change which doesn't change any feature or fix any issue)

How is the PR tested?

Unit test
Integration test

Please resolve the conflict, and it's better if you'd like to update map_string_compare_sig to use the macro.

Please resolve the conflict, and it's better if you'd like to update map_like_sig to use the macro.

It worth rewriting the map_like_sig; we can do it in other PR.

@sre-bot /approve

/approve

/merge

/merge


There is no directive with "exportAs" set to "routerLinkActive"

I am using the material angular tab nav list component in my application, it's working as expected but while executing the test case throws error.
Html:
<nav mat-tab-nav-bar>
        <a        mat-tab-link
            *ngFor="let tab of tabs"
            [routerLink]="tab.path"
            routerLinkActive #rla="routerLinkActive"
            [active]="rla.isActive"
            selectedIndex="0" >
            <i class="{{tab.icon}}"></i>
            {{ tab.label }}
        </a>
    </nav>

Error Message:
There is no directive with "exportAs" set to "routerLinkActive" ("          *ngFor="let tab of tabs"
[routerLink]="tab.path"
routerLinkActive [ERROR ->]#rla="routerLinkActive"
[active]="rla.isActive"
selectedIndex="0"
May I know why this error on only spec.

The routerLinkActive directive is defined in the RouterModule. You probably forgot to include it in your testing module, which is why it ends up throwing.

Worked after importing RouterTestingModule  not with RouterModule.
Reference: https://stackoverflow.com/questions/45159960/angular-4-error-no-provider-for-childrenoutletcontexts-in-karma-jasmine-test


chore: Have semantic-release regenerate files after version bump

The generated files have version number embedded in them. This should ensure (if it works correctly, semantic-release configuration is very difficult to test) they are updated after version bump.
Also, fixes the problem of package-lock.json getting committed.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Save whitelist/blacklist info in storage

Coverage remained the same at 91.936% when pulling 8b7f99c1750c0419b02e3e4513d0f5eca10e036e on jaivigneshvenugopal:save_wl_bl into 17e7e929c743a3c21702a99776106be67066f51f on CS2103AUG2017-T17-B1:master.


chore: use built-in types

What does this PR do?
This PR uses built-in types instead of using the ones from the typing module.
It also implements the adherence to PEP 604.
General Changes

..

Breaking Changes

..

Checklist before submitting final PR

[ ] My PR is minimal and addresses one issue in isolation
[ ] I have merged the latest version of the target branch into this feature branch
[ ] I have reviewed my own code w.r.t. correct implementation, missing type hints, proper documentation, etc.
[ ] I have run a sample config for model training
[ ] I have checked that all tests run through (python tests/tests.py)
[ ] I have updated the internal changelog (CHANGELOG_DEV.md)

When running the test suite there are a few things that stand out:
Traceback (most recent call last):
  File "/home/operation/modalities_old/tests/tests.py", line 136, in <module>
    main(**args)
  File "/home/operation/modalities_old/tests/tests.py", line 113, in main
    assert isfile(
AssertionError: ERROR! /home/operation/modalities_old/examples/getting_started/run_getting_started_example.sh does not exist.

PR #265 fixes this issue.
However, the getting_started_example is not working

=== RUN GETTING STARTED EXAMPLE ===
cd /home/operation/modalities_old/tutorials/getting_started; bash run_getting_started_example.sh 0 1
run getting_started_examples on CUDA_VISIBLE_DEVICES=0,1
/home/operation/miniconda3/envs/modalities2/lib/python3.10/site-packages/pydantic/_internal/fields.py:161: UserWarning: Field "model_checkpoint_path" has conflict with protected namespace "model".

[...]

[rank1]: Traceback (most recent call last):
[rank1]:   File "/home/operation/miniconda3/envs/modalities2/bin/modalities", line 8, in
[rank1]:     sys.exit(main())
[rank1]:   File "/home/operation/miniconda3/envs/modalities2/lib/python3.10/site-packages/click/core.py", line 1157, in call
[rank1]:     return self.main(*args, **kwargs)
[rank1]:   File "/home/operation/miniconda3/envs/modalities2/lib/python3.10/site-packages/click/core.py", line 1078, in main
[rank1]:     rv = self.invoke(ctx)
[rank1]:   File "/home/operation/miniconda3/envs/modalities2/lib/python3.10/site-packages/click/core.py", line 1688, in invoke
[rank1]:     return _process_result(sub_ctx.command.invoke(sub_ctx))
[rank1]:   File "/home/operation/miniconda3/envs/modalities2/lib/python3.10/site-packages/click/core.py", line 1434, in invoke
[rank1]:     return ctx.invoke(self.callback, **ctx.params)
[rank1]:   File "/home/operation/miniconda3/envs/modalities2/lib/python3.10/site-packages/click/core.py", line 783, in invoke
[rank1]:     return __callback(*args, **kwargs)
[rank1]:   File "/home/operation/modalities_old/src/modalities/main.py", line 60, in entry_point_run_modalities
[rank1]:     with CudaEnv(process_group_backend=ProcessGroupBackendType.nccl):
[rank1]:   File "/home/operation/modalities_old/src/modalities/running_env/cuda_env.py", line 33, in enter
[rank1]:     torch.cuda.set_device(self.local_rank)
[rank1]:   File "/home/operation/miniconda3/envs/modalities2/lib/python3.10/site-packages/torch/cuda/init.py", line 420, in set_device
[rank1]:     torch._C._cuda_setDevice(device)
[rank1]: RuntimeError: CUDA error: invalid device ordinal
[rank1]: CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
[rank1]: For debugging consider passing CUDA_LAUNCH_BLOCKING=1
[rank1]: Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

Traceback (most recent call last):
File "/home/operation/modalities_old/tests/tests.py", line 136, in
main(**args)
File "/home/operation/modalities_old/tests/tests.py", line 123, in main
check_existence_and_clear_getting_started_example_output(run_getting_started_example_directory, date_of_run)
File "/home/operation/modalities_old/tests/tests.py", line 43, in check_existence_and_clear_getting_started_example_output
assert checkpoint_to_delete is not None, f"ERROR! could not find a checkpoint with datetime > {date_of_run}"
AssertionError: ERROR! could not find a checkpoint with datetime > 2024-11-04__11-37-23

@thomaschhh I wasn't able to reproduce your error. All tests including the getting started example seem to run through using python tests/tests.py --multi-gpu. Could you try again with the latest commit (I merged main into type-annotations)? If the problem persists, feel free to open a new issue as the problem seems to be unrelated to this PR.

I am still getting the same error, however, I cannot test the multi-gpu scenario because I only have access to one and not multiple gpus. I guess that is is where the error stems from.

Yes, that might be what causes the problem. We do not explicitly check that there are 2 GPUs available if you run python tests/tests.py --multi-gpu --devices 0,1, it is assumed.

What do you think, can we merge then? I mean if you have access to multiple GPUs and the tests all pass on your end then we should be good, right?

Yes, we should perhaps merge the latest main into this branch first, double-check that are no new "typing mistakes", and potentially get a quick second review from e.g. @le1nux?

I just merged main into this feature branch and also saw there that are no occurrences of Dict, List, etc.


Applying a policy on the Settings model has no effect

I could not get a Policy working on the Settings model. I tried the automatic way just by making a SettingsPolicy, and also tried registering the policy in the AuthServiceProvider.
I quick fixed it with a temporary solution by wrapping the fields in NovaServiceProvider in an if statement dependent on the user permissions, but this still has the drawback of the settings page still being visible, albeit empty.
Am I missing something, or is this simply not implemented? or is there maybe a way to do this that I haven't found yet?

@Sitethief you can use authorization for tool
like this (app/Providers/NovaServiceProvider.php)
public function tools(): array
{
    return [
        NovaSettings::make()->canSee( fn() => is_user_can_settings() ),
    ];
}

Hi @Sitethief!
I added support for per-field authorization in version 3.1.0. If you want to hide the whole thing from the sidebar, I think @medvinator provided a pretty good solution.
I also added it to the README: https://github.com/optimistdigital/nova-settings#authorization
Thanks and good luck guys!

Yes, that works!
Thanks!


Census build S3 deletion recovery

Motivation
If an LTS build release gets deleted by accident, it would be time-advantageous to have a script ready to enumerate deleted releases and undelete a given release.
Definition of Done
A script or, minimally, a set of instructions (a playbook) to:

Enumerate deleted releases. Note that we can inspect all past versions of release.json, which can be used to infer what LTS releases should exist.
Undelete a specific Census release in the versioned S3 bucket.
Restore a (potentially) deleted release.json

Tasks

Do we need to this any time soon, or should we do this when needed i.e. when and it it actually happens?

Do we need to this any time soon, or should we do this when needed i.e. when and it it actually happens?

Well, if we delete a LTS accidentally, how long are we willing to wait for an engineer to figure out how to undelete it reliably? 😄 Practically, this shouldn't be too hard, but an ounce of prevent...  Suggest we timebox this issue's effort to a couple hours.

This will not be required once #242 is implemented. Closing per triage.


God job! In mac,is very useful! But in windows,I get N errors!

God job! In mac,is very useful! But in windows,I get N errors!

#16


Enable building and running on Mono/Mac

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

Hi !

are these changes covered by tests ?
do owners of the repo need to do anything to set up CI for this ? e.g. log in to Travis for the Mac builds ?

thanks a lot and looking forward to getting this merged !

@ahmelsayed I made a few changes to get this working again: https://github.com/mhutch/azure-functions-cli/commit/8b517d08fbe314223129aa8648201f45814ab45c

Perfect! Thank you @mhutch. I'll get that in.
@cyplo not at the moment. I'll see if I can get a Linux CI running.


obsidian: 0.7.3 -> 0.8.0

Motivation for this change
Updating Obsidian to 0.8.0, while reducing the final closure size. Since the app is based on Electron (without extra native dependencies), I replaced the AppImage with an Electron wrapper.
I still rely on the AppImage for building the derivation as it includes both the .asar file and the icon file. I found an icon in their official forum. This will reduce the required bandwith for building too.
I also added an updateScript.
cc @conradmearns
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@zimbatm You updated in to 0.8.2 in 873cca6e032dba597804fc46ed133b3e07d40560, what do you think of this approach?

sounds good to me! The only downside is that it's a bit more work to maintain.

@zimbatm how would you like to continue with this PR? Should I rebase on master and we try to get it merged? Otherwise I will just close it.

yeah, rebase it on master and pingback when it's working

@zimbatm ping

thanks!


Update Tidier installation on README

Simplifying installation instructions now that Tidier is registered will be the installation much more straightforward. Thanks for working on this package!

Great point. I will move this up so that it comes before the “or” statement. And will also do the same for our documentation home page (index.md). After I do that, will plan to merge.

Getting this git error when trying to merge the main branch: "fatal: refusing to merge unrelated histories".
Going to close this PR and will open a new one. Thanks @camilogarciabotero!


Demo didn't show any plots by default (difficult for first-time User)

When I installed the package and tried running the Demo, I was confused by seeing no plots.  Took me a long time to figure out that I needed to set the Plot Names in the giant config cluster to certain names like "Sine Wave" or "White Noise".  There is no documentation on this; I had to dig deep into the BluePlotDemo code.

because I sometimes question whether or not the community would really look at this code.

The README looks very good, but note that a typical User story (which I tend to follow) is:

What is this package?  Let's install it.
Where's the examples?  Are they easy to find.
If so, run the example; does it show me something interesting?
If interesting, look at the block diagram of the example.  Is it easily understandable?
If understandable, maybe I'll read the documentation.  Maybe.

So if you want community interest, the example is very important, and you can't rely on the User actually reading anything at all unless they impressed by your example.

Insightful, thanks!
Hopefully the example is a bit easier to engage with now that it loads a plot config on startup.


hollow knithg

game is crashing when i put mod

Please reach out at the modding discord #support channel https://discord.com/invite/RppAb2vNqz


Perms on imported pkgs 600

Makes it hard to actually deliver files when they're imported as 600... I don't think there's a pref to change that behavior, is there?

MunkiAdmin is not setting any permissions, it's just copying. Clearly a bug since I've heard this multiple times now.
Is your repo local (where in file system?) or on a network share? Are both the pkginfo and the installer item having this or just the installer? Any ACL's set on parent paths, or umask?

local(default /Users/Shared/repo), just pkg, no ACLs, tried root and subfolders, all dirs are 755. Any other way I can assist?

Thanks. I'll do some digging on this tomorrow. It's definitely possible to have a preference option to force specific permissions after copying.

I can't replicate this no matter how hard I try. What are the original file permissions on the package before you import?
I will add the permission change option and let you know when there's something to test.

Not sure if this is the exact same bug, but I get this is the munki repo is mounted over smb:
https://dl.dropboxusercontent.com/u/21533299/Vids/munkiperms.mov
Over AFP all is fine

Old issue, but as it's still open...
Running into the same thing on SFTP. Issue is described here: https://superuser.com/a/1076092
My desired solution would be a preference setting for default permissions of files + directories, where we could set 644/755, 664/775, or whatever else we need in our environment.

You can set a custom permissions for the imported file by running defaults write com.hjuutilainen.MunkiAdmin installerItemFilePermissions "0644". This is a preference key that is not set at all by default so that MunkiAdmin will skip any permission change. When that preference key is set, MunkiAdmin will try to modify the permissions of the imported installer item.

Good to know! I should have clarified our issue is with all files, not just imported installers… also manifests, catalogs, pkginfo files, etc.


Fix worker panic and add timeout for git commands

This fixes https://jira.twitter.biz/browse/DX-2266, which is a straightforward panic bug, and provides a mitigation for https://jira.twitter.biz/browse/DX-2282, which is a more complicated issue - see ticket for details.  The root cause of that issue is hanging git processes which this addresses to a degree.

Codecov Report

Merging #282 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #282   +/-   ##
=======================================
  Coverage   59.11%   59.11%
=======================================
  Files          90       90
  Lines        5687     5687
=======================================
  Hits         3362     3362
  Misses       2020     2020
  Partials      305      305

Impacted Files
Coverage Δ

common/stats/stats.go
62.3% <ø> (ø)
:arrow_up:

workerapi/server/server.go
54.36% <ø> (ø)
:arrow_up:

runner/runners/queue.go
80.23% <100%> (ø)
:arrow_up:

snapshot/git/gitdb/checkout.go
43.13% <100%> (ø)
:arrow_up:

snapshot/git/gitdb/create.go
60.78% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Darwin compilation issue with Xcode 15.3 or 14.3.1

Submitted per conversation with andy.xyz on discord
Describe the bug:
When trying to compile an application for the Darwin platform, there is a compilation error with Xcode.
Versions of Xcode tried:
14.3.1
•	12.3
•	13.3
15.3
•	13.3
•	14.4
To Reproduce:
Steps to reproduce the behavior:

Create a sample application file
Commands run to try various Xcode versions:

fyne-cross darwin --debug --no-cache -arch amd64 --macosx-sdk-path ./resources/AppleXcode/SDKs-14.3.1/MacOSX12.3.sdk/ -app-id hello.app -output build ./cmd/testapp/ > 14.3.1-12.3.sdk.log 2>&1
fyne-cross darwin --debug --no-cache -arch amd64 --macosx-sdk-path ./resources/AppleXcode/SDKs-14.3.1/MacOSX13.3.sdk/ -app-id hello.app -output build ./cmd/testapp/ > 14.3.1-13.3.sdk.log 2>&1
fyne-cross darwin --debug --no-cache -arch amd64 --macosx-sdk-path ./resources/AppleXcode/SDKs-15.3/MacOSX13.3.sdk/ -app-id hello.app -output build ./cmd/testapp/ > 15.3-13.3.sdk.log 2>&1
fyne-cross darwin --debug --no-cache -arch amd64 --macosx-sdk-path ./resources/AppleXcode/SDKs-15.3/MacOSX14.4.sdk/ -app-id hello.app -output build ./cmd/testapp/ > 15.3-14.4.sdk.log 2>&1

See the error in attached log files

Example code:
Sample app:
package main

import (
	"fyne.io/fyne/v2/app"
	"fyne.io/fyne/v2/container"
	"fyne.io/fyne/v2/widget"
)

func main() {
	myApp := app.New()
	myWindow := myApp.NewWindow("Hello Fyne")

	myWindow.SetContent(container.NewVBox(
		widget.NewLabel("Hello Fyne!"),
		widget.NewButton("Quit", func() {
			myApp.Quit()
		}),
	))

	myWindow.ShowAndRun()
}

Device and debug info (please complete the following information):
Device info

OS: OpenSuse Tumbleweed (updated)
Version: Latest version of Tumbleweed
Go version: go version go1.22.5 linux/amd64
fyne-cross version: v1.5.0 plus custom build from master
Fyne version: 2.5.0

Debug info
See attached logs

[15.3-13.3.sdk.log](https://github.com/user-attachments/files/16482664/15.3-13.3.sdk.log)
[15.3-14.4.sdk.log](https://github.com/user-attachments/files/16482665/15.3-14.4.sdk.log)
[14.3.1-12.3.sdk.log](https://github.com/user-attachments/files/16482666/14.3.1-12.3.sdk.log)
[14.3.1-13.3.sdk.log](https://github.com/user-attachments/files/16482667/14.3.1-13.3.sdk.log)
Hopefully, this is just a mistake on my part, but I can't seem to figure out what the issue is.  If you could point me in the right direction, I would very much appreciate it.

This is strange, it seems to be failing to compile in the SDK code not ours...
SDK 15 has caused trouble elsewhere but 14 should have worked.
Can you try the latest version of 12 as well? That was heavily used for a long time and is known to work.
Just trying to eliminate possible issues at your end...

Ok , I will give that a try.  It will be a couple of days before I can get to it though.
From: Andy Williams @.>
Sent: Tuesday, August 6, 2024 11:06 AM
To: fyne-io/fyne-cross @.>
Cc: Jextter @.>; Author @.>
Subject: Re: [fyne-io/fyne-cross] Darwin compilation issue with Xcode 15.3 or 14.3.1 (Issue #266)
This is strange, it seems to be failing to compile in the SDK code not ours...
SDK 15 has caused trouble elsewhere but 14 should have worked.
Can you try the latest version of 12 as well? That was heavily used for a long time and is known to work.
Just trying to eliminate possible issues at your end...
—
Reply to this email directly, view it on GitHub https://github.com/fyne-io/fyne-cross/issues/266#issuecomment-2270769890 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AHDXTIAUYG6HYN3ILMTFZCLZQCGXDAVCNFSM6AAAAABL6FGESKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZQG43DSOBZGA .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AHDXTIC3OKJBLX5OZPNI3XTZQCGXDA5CNFSM6AAAAABL6FGESKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUHLEZOE.gif Message ID: @.*** @.***> >

I downloaded version twelve and tried it also.  It also fails.
Here are some notes:

during the extraction process, I noticed that there was an new image being downloaded. So to be thorough, I ran a "docker system prune -a --volumes -f" to force clean everything and start over.
I then extracted the sdks from these packages:
Command_Line_Tools_for_Xcode_12.5.dmg
Command_Line_Tools_for_Xcode_13.2.dmg
Command_Line_Tools_for_Xcode_13.4.dmg
Command_Line_Tools_for_Xcode_14.3.1.dmg
Command_Line_Tools_for_Xcode_15.3.dmg
Command_Line_Tools_for_Xcode_16_beta_5.dmg
I then proceeded to try each and every SDK in these packages after extraction, using these commands:
fyne-cross darwin --debug -arch amd64 --macosx-sdk-path ./resources/AppleXcode/SDKs-12.5/MacOSX10.15.sdk/ -app-id cvs.report.pdf -output build ./cmd/csvtopdf > 12.5-10.15.sdk.log 2>&1
fyne-cross darwin --debug -arch amd64 --macosx-sdk-path ./resources/AppleXcode/SDKs-12.5/MacOSX11.3.sdk/ -app-id cvs.report.pdf -output build ./cmd/csvtopdf > 12.5-11.3.sdk.log 2>&1
fyne-cross darwin --debug -arch amd64 --macosx-sdk-path ./resources/AppleXcode/SDKs-13.2/MacOSX11.3.sdk/ -app-id cvs.report.pdf -output build ./cmd/csvtopdf > 13.2-11.3.sdk.log 2>&1
fyne-cross darwin --debug -arch amd64 --macosx-sdk-path ./resources/AppleXcode/SDKs-13.2/MacOSX12.1.sdk/ -app-id cvs.report.pdf -output build ./cmd/csvtopdf > 13.2-12.1.sdk.log 2>&1
fyne-cross darwin --debug -arch amd64 --macosx-sdk-path ./resources/AppleXcode/SDKs-13.4/MacOSX11.3.sdk/ -app-id cvs.report.pdf -output build ./cmd/csvtopdf > 13.4-11.3.sdk.log 2>&1
fyne-cross darwin --debug -arch amd64 --macosx-sdk-path ./resources/AppleXcode/SDKs-13.4/MacOSX12.3.sdk/ -app-id cvs.report.pdf -output build ./cmd/csvtopdf > 13.4-12.3.sdk.log 2>&1
fyne-cross darwin --debug -arch amd64 --macosx-sdk-path ./resources/AppleXcode/SDKs-14.3.1/MacOSX12.3.sdk/ -app-id cvs.report.pdf -output build ./cmd/csvtopdf > 14.3.1-12.3.sdk.log 2>&1
fyne-cross darwin --debug -arch amd64 --macosx-sdk-path ./resources/AppleXcode/SDKs-14.3.1/MacOSX13.3.sdk/ -app-id cvs.report.pdf -output build ./cmd/csvtopdf > 14.3.1-13.3.sdk.log 2>&1
fyne-cross darwin --debug -arch amd64 --macosx-sdk-path ./resources/AppleXcode/SDKs-16_beta_5/MacOSX14.5.sdk/ -app-id cvs.report.pdf -output build ./cmd/csvtopdf > 16_beta_5-14.5.sdk.log 2>&1
fyne-cross darwin --debug -arch amd64 --macosx-sdk-path ./resources/AppleXcode/SDKs-16_beta_5/MacOSX15.0.sdk/ -app-id cvs.report.pdf -output build ./cmd/csvtopdf > 16_beta_5-15.0.sdk.log 2>&1

Oddly, there is a different issue.  It seems that there are only warning in the compilation of the code but there is a link option being used that is not recognized:
<EMAIL_ADDRESS> $WORK/b258
 /usr/local/zig/lib/include
 /usr/local/zig/lib/libc/include/x86_64-macos.10-gnu
 /usr/local/zig/lib/libc/include/any-macos-any
 /sdk/usr/include
 /sdk/System/Library/Frameworks (framework directory)
End of search list.
# CSVToPDFReports/cmd/csvtopdf
flag provided but not defined: -w"
usage: link [options] main.o
  -B note
    	add an ELF NT_GNU_BUILD_ID note when using ELF; use "gobuildid" to generate it from the Go build ID
  -E entry
    	set entry symbol name

I have attached new logs for review:
16_beta_5-15.0.sdk.log
12.5-10.15.sdk.log
12.5-11.3.sdk.log
13.2-11.3.sdk.log
13.2-12.1.sdk.log
13.4-11.3.sdk.log
13.4-12.3.sdk.log
14.3.1-12.3.sdk.log
14.3.1-13.3.sdk.log
16_beta_5-14.5.sdk.log
16_beta_5-15.0.sdk.log
is there some other link command executable I need to hunt down?

Also:
jextter@localhost:~/Desktop/Workspace/Jextter/CSVToPDFReports> link --version
link (GNU coreutils) 9.5
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later https://gnu.org/licenses/gpl.html.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Michael Stone.

Also:
jextter@localhost:~/Desktop/Workspace/Jextter/CSVToPDFReports> link --version link (GNU coreutils) 9.5 Copyright (C) 2024 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later https://gnu.org/licenses/gpl.html. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
Written by Michael Stone.

Please don't get confused with local tools - fyne-cross uses completely container-based compilation so your developer setup won't matter.

I can't see where the error is coming from or what the problem is, hopefully @lucor, @Jacalz or @Bluebugs will have some idea.
It is incredibly strange that you are getting similar errors across a large range of different versions and that one we know works also isn't functioning for you.
I guess it is possible that there is a bug on master - did you try with the 1.5.0 release not master?

Yes, you are right; I wasn't thinking clearly about that.  I don't usually do my development or compilation in a docker container, so it was just a knee-jerk thing to get that while trying to be thorough.

I had not tried the 1.5.0 release again.  I will try that and let you know.

Hello All!  I am pleased to report progress.  It does successfully compile with a fresh build from master on some of the Xcode SDKs.  It seems that 10.15 -> 12.3 compile just fine.  Then at 13.3, something is definitely not happy in the Xcode SDK.  I have attached the updated logs for your review.  Thank you guys for getting this fixed so quickly!  Let me know if there is more I can do to help you guys.
Same commands as before:
13.4-12.3.sdk.log
14.3.1-12.3.sdk.log
14.3.1-13.3.sdk.log
16_beta_5-14.5.sdk.log
16_beta_5-15.0.sdk.log
12.5-10.15.sdk.log
12.5-11.3.sdk.log
13.2-11.3.sdk.log
13.2-12.1.sdk.log
13.4-11.3.sdk.log
I am not sure if you guys would like me to close this or not or have this as an open ticket to come back to on the newer SDKs.  In some searches I did, the compilation issue appears to correlate to the same time they eliminated 32-bit support and added new support for IOS15.  I suspect they changed up the tooling quite a bit.  But, not being an Apple person, I just don't know the actual details.
Anyway, Thanks!

As far as I'm aware the Fyne toolkit itself works great with these more recent versions, so perhaps there is an issue with the image or fyne-cross initialisation and the SDKs?
Possibly it relates even to the way we are extracting the data to create a viable image?
Any thoughts @lucor or @Bluebugs ?

Could this be related to https://github.com/fyne-io/fyne-cross/pull/246
The error message contains the parameter -w  which was removed in the upper pr:
# CSVToPDFReports/cmd/csvtopdf
flag provided but not defined: -w"

The pr is merged, but no new version has been released, yet.


fix: making it compatible to newer version of @asyncapi/react-component

Description
Should be merged only after https://github.com/asyncapi/asyncapi-react/pull/1078 is merged.

Will need to change the version of @asyncapi/react-component

Creating an immature PR for tracking purposes
Related issue(s)
https://github.com/asyncapi/asyncapi-react/pull/1078
#200

@ivangsa
added the newest version of @asyncapi/react-component
ptal

/rtm


Add Application Insights

Add Application insights to Nether.Web

Add package
Read instrumentation key from config (and only wire up if key is set)

Add Application insights to deployment

add to template
make it optional

Closed in #404


fix FAQ section by reordering questions

The FAQ section on the organization's website currently displays questions in a disordered sequence, which may disrupt user experience and clarity. To address this issue, I have reordered the questions to improve the flow and organization of the FAQ section and added mail to link.

I kindly request @Anushkabh @nandu-99  to review the changes and provide feedback. If any further adjustments are needed, please let me know, and I will be happy to make them.
Thank you for your attention to this matter.

@MehekFatima  kindly mention the issue number

@Anushkabh I've mentioned the issue number (8). Please review the changes.

Fixes #8


Add a sessionId on the search request

For the moment, all search statistics and analytics made on the server are not specific enough. We cannot know if the search "pants" is unique or if it's preceded by "p" then "pa" then "pan" then "pant" and finally "pants". It's mean we are unable to find the most searched words for an index.
It should be great to add on the search requests headers a sessionId to keep a history of what user search. The goal is not to spy the users but just to have enough information to know what the final search is.

This is no more relevant, we close it, feel free to comment here or open a new issue.


feat: show service number on icon when first key of switch service hotkey held

Description of Change

display shortcut index on 1s longpress of ctrl/cmnd key
add .tab-item__shortcut-index styling to tabs.scss

Motivation and Context
Closes https://github.com/getferdi/ferdi/issues/308
Showcase

Checklist

[x] My pull request is properly named
[x] The changes respect the code style of the project (npm run prepare-code)
[x] npm test passes
[x] I tested/previewed my changes locally

Please add a screenshot in the description for future reference - if possible. lgtm

I added a short explanatory gif above.


Parsing 'daylight saving date' returns wrong date and time on Android.

🐛 Bug Report

Parsing 'daylight saving date' returns wrong date and time on Android.
If a run:
console.log(new Date(2019,1,17));

In the browsers, or in node js, it returns Sun Feb 17 2019 00:00:00 GMT-0300 (Brasilia Standard Time).
But, in React Native app it returns Sat Feb 16 2019 23:00:00 GMT-0300 (-03).
Note thats the timezone is correct GMT-0300, but the datetime returned is wrong.
The source problem here, is that the daylight saving date ended on February 17. So in '2019-02-17 00:00:00' we had to go back an hour on the clock. Returning to '2019-01-16 23:00:00'.
To Reproduce

Setup the Android timezone to 'America/Sao_Paulo GMT-03:00' (-02:00 when in daylight saving date)
Run console.log(new Date(2019,1,17)) in a React Native app.
The output will be Sat Feb 16 2019 23:00:00 GMT-0300 (-03) or 2019-02-17T03:00:00.000Z.
Expected Behavior

The output should be Sun Feb 17 2019 00:00:00 GMT-0300 (Brasilia Standard Time).
Code Example

Strangely, using an Expo Snack the problem does not occur.
Snack: https://snack.expo.io/Bkj8saGIV
Environment

Tested with real devices with Android P, and with emulators API 16 and API 28.
  React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: (4) x64 Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz
      Memory: 187.17 MB / 8.00 GB
      Shell: 3.0.0 - /usr/local/bin/fish
    Binaries:
      Node: 8.14.0 - /usr/local/bin/node
      Yarn: 1.13.0 - /usr/local/bin/yarn
      npm: 6.5.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
      Android SDK:
        API Levels: 16, 17, 18, 19, 21, 22, 23, 24, 25, 26, 27, 28
        Build Tools: 23.0.1, 23.0.3, 24.0.3, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.0, 28.0.0, 28.0.1, 28.0.2, 28.0.3
        System Images: android-16 | Google APIs Intel x86 Atom, android-17 | Google APIs Intel x86 Atom, android-19 | Google APIs Intel x86 Atom, android-21 | Google APIs Intel x86 Atom, android-24 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 3.2 AI-181.55<IP_ADDRESS>14246
      Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.3 => 16.6.3
      react-native: 0.58.5 => 0.58.5
    npmGlobalPackages:
      react-native-cli: 2.0.1

Can you verify using the 0.59 RC? 0.58 and earlier interpret your JS code using a 4 year old build of JavaScriptCore, but starting with 0.59 we've switched to a newer build based on https://github.com/react-native-community/jsc-android-buildscripts.

Bingo! The problem does not occur in version 0.59.
  React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: (4) x64 Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz
      Memory: 167.62 MB / 8.00 GB
      Shell: 3.0.0 - /usr/local/bin/fish
    Binaries:
      Node: 8.14.0 - /usr/local/bin/node
      Yarn: 1.13.0 - /usr/local/bin/yarn
      npm: 6.5.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
      Android SDK:
        API Levels: 16, 17, 18, 19, 21, 22, 23, 24, 25, 26, 27, 28
        Build Tools: 23.0.1, 23.0.3, 24.0.3, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.0, 28.0.0, 28.0.1, 28.0.2, 28.0.3
        System Images: android-16 | Google APIs Intel x86 Atom, android-17 | Google APIs Intel x86 Atom, android-19 | Google APIs Intel x86 Atom, android-21 | Google APIs Intel x86 Atom, android-24 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 3.2 AI-181.55<IP_ADDRESS>14246
      Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.1 => 16.8.1
      react-native: 0.59.0-rc.2 => 0.59.0-rc.2
    npmGlobalPackages:
      react-native-cli: 2.0.1

Any chance of getting a "hotfix" for stable old versions?

I tried to follow the instructions to use the most recent jsc-android version in my RN project, but the date problem continues.

There are no plans to bring the newer JSC to older RN releases. You'll need to upgrade it manually following those instructions, but getting that done is out of scope for this issue tracker. You're unlikely to be the only one desiring to patch older releases, so perhaps discussing this in https://github.com/react-native-community/jsc-android-buildscripts/issues will be productive.

Upgrading to the jsc-android following the instructions @douglasjunior posted resolved my issue (running RN 0.58.3)

Yes, I also managed to solve by following the jsc-android installation instructions.
Before I was not getting due to some cache of Android Studio.


The text in the important section is identical

The only difference in the text is the usage of "as workaround" vs "in the meantime"
Given both are same text, keeping the one which sounds better.

Learn Build status updates of commit 593d5dc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/aks/cluster-container-registry-integration.md
:white_check_mark:Succeeded

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

#sign-off


EP-320:Android: Page Viewed (change_payment)

📲 What
Added the change_payment property to Page Viewed
🤔 Why
Handling Change payment for backed project pledge data
🛠 How
Create  trackChangePaymentMethod and call it

👀 See

📋 QA
Instructions for anyone to be able to QA this work.
Open Profile chosse backed prokect
mange backer
update payment
https://user-images.githubusercontent.com/1075310/110999470-16ba5300-8389-11eb-9ba8-e53fe8e08dd6.mp4
Story 📖
https://kickstarter.atlassian.net/browse/EP-320

Can we add some unit tests? , the test class is ProjectViewModelTest


Manual mode certificate renewal removes existing bindings without configuring a new binding

We have used letsencrypt-win-simple using the --manualhost flag for several hosts and corresponding webroots to install certificates initially. This went well and we have been using the certificates for a few months now. The Windows registry does seem to contain all the right data.
Upon renewal the certificates are renewed successfully (now; we had some trouble using the 1.9.3 version, currently we're using the 1.9.4 beta4 version), because we see a new expiry date in the future within the Windows certificate store.
The problem is that the existing HTTPS binding for the website is removed as soon as the new certificate is created in the certificate store. Is this a known problem, or should we move away from the Manual mode? Is there another way to keep using the Manual mode, but keep IIS from breaking the bindings?
Upon using the new version in interactive mode we found out there are now dns-01 challenges included, which were taken as the default. Could a possible solution be to use the IIS plugin instead and let the win-simple client perform IIS management tasks?

I can't really explain why the bindings would get removed when using the Manual mode, as it is not supposed to touch IIS, nor the certificate store for that matter. Can you show us the script that you run for installing?

In my experience, only the most-recent cert exists in the store when using manual mode. Is that not the case?
If it works the way I expect, then IIS would have the thumbprint configured on the binding, but the cert wouldn't exist and IIS would serve the old cert until the app recycles.

We performed the installation a while ago; the command executed back then was similar to this:
letsencrypt.exe --manualhost lets-encrypt-live1.example.com --webroot "C:\path\to\webroot" --emailaddress<EMAIL_ADDRESS>--accepttos
We performed this for several domains. To renew the certificates we run the following in a .bat script:
letsencrypt.exe --renew
The 1.9.3 version was problematic, as it would fail and still set the renewal date into the future. That particular issue was solved by deploying 1.9.4 beta4 (nice job on fixing that one :smile:).
The registry has multiple entries similar to the one below:
{"Date":"2017-10-01T13:18:58.5892533Z","Binding":{"Host":"lets-encrypt-live1.example.com","WebRootPath":"d:\\websites\\lets-encrypt-live1","SiteId":0,"AlternativeNames":null,"PluginName":"Manual","Plugin":{"Name":"Manual"}},"CentralSsl":null,"San":"False","KeepExisting":"False","Script":null,"ScriptParameters":null,"Warmup":false}

We also performed some tests with domains that wouldn't resolve. The registry was not altered in those cases and they were retried on the next run, so the content of the registry looks OK to us.
So, certificate renewal is in fact working, but the binding in IIS breaks. If I'm correct, letsencrypt-win-simple imports the certificates into the certificate store after renewing the certificate, overwriting the old certificate, right? Could it be the case that IIS loses the reference to the old certificate upon the import by the client?

Importing into the certificate store doesn't delete or overwrite the old certificate. However, by default LEWS will delete the old certificate. See the --keepexisting option.

The --keepexisting option makes sense! Totally missed that one.
So, when we use that we will still get a renewed certificate, but the certificate in IIS will remain. This means that in manual mode we will have to manually change the certificate within the IIS bindings configuration?
I've browsed the code for a bit and saw there are multiple plugins. I think we will switch to automatic configuration IIS in the end; our IIS admin first wanted to run a trial with Let's Encrypt before moving all domains over. I think it should be possible to switch to the IIS plugin by changing the registry entries, or is this considered a bad practice?

Manual mode... yes that's how I understand it.
Switching plugins... I suspect it's not going to be that simple, yes, you should be able to change the setup but a plugin does more than just switching where the certificate is placed. It also makes changes as to how the certificate is validated and downloaded.

I wouldn't recommend changing the registry manually, as the first (interactive) run when setting up a certificate can provide valuable feedback about the validation and installation process. If you want to use manual mode without LEWS doing anything with the certificate store, yet still use the certificates in IIS, you can use the Central SSL store.

The manual input with IIS install scenario should be supported out of the box with the final phase of #398. Meanwhile there is a workaround described in #612.


importing doesn't work anymore

When importing as
import URLSearchParams from 'url-search-params'
and using it further in the code as
const urlParams = new URLSearchParams(window.location.search)
I get the following error:
TypeError: _urlSearchParams2.default is not a constructor
This started after the version update from 0.10.0 -> 0.10.1

Please open a ticket to whatever bundler you are using:
https://github.com/WebReflection/url-search-params/blob/master/package.json#L22
The package.json clearly state which CJS module you should import, and there is no ESM (or module) entry there so it's a problem of your bundler.

How it is not a breaking change?

How it is not a breaking change?

It's very simple, nothing broke here, or in travis, and no API changes whatsoever were made.
I've made the module usable through unpkg CDN and that relvealed a bug of your bundler.
However, I've reverted the change in 0.10.2, but since this is an absurdity I've put the change back in 1.0.0 so now it's officially a breaking change, and bundlers need to fix their issue.

Thanx @WebReflection
In my case I've updated webpack to 4.15.0 and url-search-params to 1.0.2 this is no more an issue for me.


2022092501

add missing sig from #7799

@6CornerDefender @denylist-maintainer looks like this list is not released yet.

@6CornerDefender any plan for this unsuccessful PR release? This is one good list and we have been waiting…


What is TGI's graceful shutdown behavior?

When SIGKILL arrives,

does TGI process all pending inputs?
does TGI blocks incoming inputs?

I saw a PR that adds graceful shutdown but it did not specify the exact program behavior.

does TGI process all pending inputs?

Yes all inputs in the queue until a timeout which is currently set at 90 seconds.

does TGI blocks incoming inputs?

Yes


Fix expected response on groups endpoint specification and some tooling

Description
OpenAPI spec was outdated and refers to a redirection that is not done. Fixing and adding some tooling to manually check the OpenAPI specification
Fixes #72
Type of change

Bug fix (non-breaking change which fixes an issue)

Testing steps
Regular CI

Codecov Report

Merging #73 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #73   +/-   ##
=======================================
  Coverage   41.95%   41.95%
=======================================
  Files          12       12
  Lines         882      882
=======================================
  Hits          370      370
  Misses        469      469
  Partials       43       43

Continue to review full report at Codecov.

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


Update SNMP Check docs

What does this PR do?
Update SNMP Check README
Update link in SNMP example yaml file
Motivation
Trello request
Review checklist

[x] PR has a meaningful title or PR has the no-changelog label attached
[ ] Feature or bugfix has tests
[x] Git history is clean
[x] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo

Additional Notes
Anything else we should know when reviewing?

@nmuesch I have migrated the configuration file for this check.. which is quite tricky since it has to support 3 SNMP version. We should connect to talk about this.


lines combined when one ends with [] (square brackets) within a function

Given this sample input, the top-level snippets are left alone properly, but the 2 statements within the function are erroneously combined into one line.
input
var fine = process.argv[0]
var noprob = 2

function blah () {
  var oops = process.argv[0]
  var goestolineabove = 2
}

output with bug (no longer valid JS)
var fine = process.argv[0]
var noprob = 2

function blah () {
  var oops = process.argv[0]var goestolineabove = 2
}

esformatter version 0.7.3

already fixed on master. not sure which commit fixed it tho.. I guess it should be #334. thanks for reporting!


feat: implemented slider widget from mantine ui

Description
Implemented Slider widget with inspiration from mantine ui - https://mantine.dev/core/slider/
Fixes #3349
Type of change

New feature (non-breaking change which adds functionality)
This change requires a documentation update

How Has This Been Tested?

Tested Manually on the canvas

Checklist:

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

Loom Recording - https://www.loom.com/share/4e62e1ec49fd4446bfbebd3dab31bb7e

@yaldram : This is fantastic! Suggestion, we can have a single widget with two options range slider & slider.

I would not merge these widgets into a single widget. Both of them have 2 different use-cases. Also the range slider exposes two values namely start & end whereas the slider widget exposes only one value. Though we are using same components internally the logic is different.  Having 2 separate components make for good readable code & separation of concerns inline with the single responsibility principle.  Having 2 separate widgets make for good discoverability.

Slider Widget Design: https://www.figma.com/file/1aTQ6vksqqAMtgB243PtHm/UI-|-Widget-Style-Updates-0.1?node-id=5458%3A87091


Bible Parser for Bibles in json formats [C#]

Hi @Honza,
Thanks for providing us with these priced items, I thought it would be great for me to also share the code written to consummate it.
This unit test should pass for all the Json versions of the uploaded bible.
I am intending to push them to MongoDB as am not too sure of how it will scale on SQL SERVER given that I would love users to be able to switch translations.
Should there be any need to further add resource, please let me know.
Regards

This is awesome! Would you mind moving the file to a contrib directory, and giving it a nicer name? Something like contrib/example.cs?

Thanks, perfect. Before I merge: I just realized that my repo doesn't have a license. Are you happy with MIT?

Oh sure..!!

Thanks!


cursor arrow not hidden during full screen playback

the cursor arrow is not hidden after a period of inactivity in full screen mode during playback
it happens on all browsers OSX/Win
is there a way to do it via css or a configurable parameter ?

@krish0005 Closing old issues. If you'd like to reopen this, let us know. Thanks!


Added listtasks command to list open tasks for a Phabricator or Slack…

… user.
'listtasks' command has the following properties:
Takes Phabricator username as input and displays the currently open tasks for that user.
If no username is provided, their Slack username is used to look up tasks (assumption being that their Slack username matches their Phabricator username).
If username is not found, an error message is displayed.

I'll work on adding tests.

Great. Thanks a lot!

@schemar anything more needed from me on this PR?

I don't think so. I hope that I will have time to review it soon and make a new release that includes it 👍


[bug]FGS211

Hello,
since the last update of JS Zwave my FGS211 / FGS221 not return the status of one switch.
He works but I don’t know if is switch on or off.
Any idea ?
Thx

without any log it's difficult to debug

Sorry for my bad English
I can't see anything in the logs when I flip the switch.
No information

Please read and follow the troubleshooting section on missing updates from devices:
https://zwave-js.github.io/node-zwave-js/#/troubleshooting/no-updates
You're going to need the zwave-js logs for that.

Seems to be the same issue as https://github.com/zwave-js/node-zwave-js/issues/2267

Might be, but I'll need the full zwave-js logs including a re-interview to verify.


Fix Export Printing of All Domains/All Vulnerabilities Tables

🐛 Summary
What's wrong? Please be specific.
Default formatting prevents all columns from being displayed when attempting to print results from table.
To reproduce
Steps to reproduce the behavior:

Click Export in Data Grid Toolbar
Select Print
Examine Print Dialogue

Expected behavior
What did you expect to happen that didn't?
Either wrap columns or adjust font and spacing to include all columns in at least landscape mode.
Any helpful log output or screenshots
Add any screenshots of the problem here.

Here are some considerations following testing of and experimenting with possible solutions:

It may be misguided to code print export configurations given the following:

The wide range of possible printing preferences depending on the user, i.e. page layout and paper size.
The wide range of columns the user decides to print, i.e. they may not need to print the full table.

Chrome's print dialogue is sufficient to scale the grid to portrait or landscape layout and offers multiple page sizes.

Other browser's need to be tested.

If other browser's follow suit, this issue should be closed with stock behavior intact.
Below are screenshots of the scaled print preview, both portrait and landscape, using Chrome's print dialog:

Safari print dialogue scales appropriately:

But safari does not:


Missing F# Examples

Hi,
I tried to translate the C# examples into F#, but it doesn't work. It seems that the extensions to IEnumerable are not visible to the F# interpreter for some reason.

What's the correct way of using the extension from F#?

@vhogemann Did you find a solution?


Nick: Watch franklindental-supply.com

Nick requests the watch of the watch_keyword franklindental-supply\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

franklindental-supply\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by cigien in Charcoal HQ


special: fix chgm fortran routine for large negative argument

Reference issue
Closes gh-17120
What does this implement/fix?
See the explanation in #17120.
I think having the value be slightly wrong (>1e-15 rtol) is better than being completely off, but I could also try to increase the number of terms used in the series, or return some error if the series fails to converge.

I found this error while trying to debug a version of this function that was translated to rust (f2c from the original fortran and then manual translation from C to rust), so here is the fix ported to Fortran.

So I found a way to integrate the expansion for large X in CHGM, so this PR now also fixes #14149! @Noxbru might be interested in these changes.
There are a couple of semi-arbitrary choices here that I would like to discuss with people more experienced in numerical analysis than I am:

the choice of X>500 for the switch from DLMF 13.2.2 to DLMF 13.7.1;
the number of iterations in 13.7.1 loop (for the values in the test, this loop converges in ~10 iterations)
The applicability of the formula and what to do if a=0, -1, ... (see FIXME in code)
The applicability of the call to cgama to get gamma(a) and gamma(b)

Thanks @Luthaf.
We now have the Boost library available.  Instead of maintaining our vendored copy of CHGM from the specfun library, I think a better solution is to use the function hypergeometric_1F1 as the backend of scipy.special.hyp1f1 in the case of real inputs.
I put a small C++ demo program at hyp1f1.cpp.  With it, we can verify that the Boost function would fix #14149 and #17120:
$ ./hyp1f1 1 0.3 -10000
-7.001190321419e-05
$ ./hyp1f1 9 8.5 -355
-4.595407159813e-20

I would be completely fine with scipy using the boost::math implementation instead of Fortran! But I do not have time to write the corresponding PR.

If this PR fixes the current implementation let's get it in and open an issue for replacing it with Boost.

I started working on a pull request to use Boost as the backend of hyp1f1.  With https://github.com/scipy/scipy/pull/16017 merged, replacing the backend does not take a lot of work.  So far the only issue that I have run into is some inconsistent handling of a special case in the Boost function hypergeometric_1F1; see https://github.com/boostorg/math/issues/829.

Closing since https://github.com/scipy/scipy/pull/17302 fixes the same issue!


Unnecessary and duplicate workflow-dispatch-inputs-example.md file

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_dispatchinputs
https://docs.github.com/en/actions/using-workflows/triggering-a-workflow#defining-inputs-for-manually-triggered-workflows
What part(s) of the article would you like to see updated?
Going through the docs, I noticed that the example used to define inputs for manually triggered workflows is duplicate and serves no extra purpose.
Looking at the docs this extra example comes from file workflow-dispatch-inputs-example.md and was just added last month for some reason.
So my proposed fix for this would be

delete the file workflow-dispatch-inputs-example.md, as if we search for this file, it is only being used in 2 places, and on both of them it is only working as a duplicate, and workflow-dispatch-inputs.md seems to be useful as it also contains come extra common content.
or
Instead of deleting it, update the yaml part of the code in workflow-dispatch-inputs.md file with this

{% data reusables.actions.workflow-dispatch-inputs-example %}

Delete these lines from workflow-syntax-for-github-actions.md file.
Not sure if the text Example of on.workflow_dispatch.inputs is important so you can confirm on that.
Delete this line from triggering-a-workflow.md file.

Additional information
If you look at the video, except spacing of options values, both are same example
https://user-images.githubusercontent.com/46301285/225749771-16ed2877-aa99-4f63-a211-c0b31100f15b.mp4

I'd be more than happy to contribute a PR if you confirm 🙏🏼

Hey @Aashu-Dubey, thank you so much for opening this issue and proposing a well-thought-out solution. I'm wondering if it would work to just delete the example from /data/reusables/actions/workflow-dispatch-inputs.md? I think if we did that, we wouldn't need to touch anything else.
Definitely feel free to open a PR for this if you are interested, we'd really appreciate it! ✨

Ah, I just noticed @drarig29 opened a PR for this. 🚀 I'll review that and get this issue closed.


Fix test workflow (caused by libsodium modification)

    CI fails due to the latest changes of workflow in rc9/v0.46.0.

Originally posted by @0Tech in https://github.com/line/lbm-sdk/issues/784#issuecomment-1318141371

Related: #793

The cause seems to be that libsodium is not installed. I'll fix it.

@0Tech
How about adding test.yml to diff target in test.yml?

I think it's better to add itself to diff target in other each yml file as well.

Resolved by https://github.com/Finschia/finschia-sdk/pull/803


added target="_blank"

Like previous html assets have, added target="_blank" to two of links here

noice


seriously need help!

Describe your problem here.
source/flixel/sound/FlxSound.hx:601: characters 16-24 : flash.media.SoundChannel has no field __source
export/release/windows/haxe/ApplicationMain.hx:153: characters 5-36 : ... Called from macro here
source/flixel/sound/FlxSound.hx:605: characters 19-27 : flash.media.SoundChannel has no field __source
export/release/windows/haxe/ApplicationMain.hx:153: characters 5-36 : ... Called from macro here
C:/HaxeToolkit/haxe/lib/flixel-ui/2,5,0/flixel/addons/ui/FlxUICursor.hx:564: characters 9-11 : Warning : Potential typo detected (expected similar values are flixel.addons.ui.SortMethod.ID)

I've done everything such as re-downloading everything of haxelib and openfl including the stuff in [(https://github.com/ShadowMario/FNF-PsychEngine/wiki/Libraries-versions)]
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

Go to (SourcePath)/setup/setup-windows


Action inserts new change log entry before latest rather than after

As an example, in one of my repos, it will attempt to place change log notes for 1.0.9 between 1.0.7 and 1.0.8 rather than after 1.0.8: https://github.com/Fdawgs/node-unrtf/pull/46/commits/c28c3618df1bd81ba5cdbb334304a14534ec33a0
Config used: https://github.com/Fdawgs/node-unrtf/blob/master/.github/workflows/cd.yml

Resolved. Needed to add a H1 header # at the top, similar to how yargs does in the nodejs example.


no rndc key found in master's named.conf

Hello guys !
When I executed the command on globodns server,  ruby script/importer --remote     there was an error.
globodns server error:
no rndc key found in master's named.conf
no rndc key found in master's named.conf
[ERROR] import failed
DEPRECATION WARNING: #deliver is deprecated and will be removed in Rails 5. Use #deliver_now to deliver immediately or #deliver_later to deliver through Active Job. (called from rescue in import at /home/tao.yang02/globodns/lib/globo_dns/importer.rb:272)
Rendered notifier/import_failed.en.text.erb (2.1ms)
my bind server named.conf
/var/named/chroot/etc/named.conf
options {
directory "/var/named";
pid-file "/run/named/named.pid";
statistics-file "/var/named/data/named.stats";
notify no;
version "xxxxxxxxxx";
check-names master warn;
zone-statistics yes;
edns-udp-size 4096;
max-ncache-ttl 300;
forwarders  { NN.NN.NN.NN;
NN.NN.NN.NN;
};
allow-query { any; };
};
logging {
category lame-servers { null; };
channel warning
{
file "/var/log/named.log" versions 3 size 204800k;
severity info;
print-category yes;
print-severity yes;
print-time yes;
}
;
channel query
{
file "/var/log/query.log" versions 3 size 204800k;
severity info;
print-category yes;
print-severity yes;
print-time yes;
}
;
channel security
{
file "/var/log/security.log" versions 3 size 204800k;
severity info;
print-category yes;
print-severity yes;
print-time yes;
}
;
category default { warning; };
category queries { query; };
category security { security; };
};
include "/etc/init_zone.conf";
key "rndc-key" {
algorithm hmac-md5;
secret "XXXXXXXXXXXXX";
};
controls {
inet <IP_ADDRESS> port 953
allow { <IP_ADDRESS>;<IP_ADDRESS>; } keys { "rndc-key"; };
};
How can I solve this problem? I look forward to your reply. Thank you.

well well ···

Please check if the key name on your named.conf file is the same set on globodns.yml on the :rndc_key_name  parameter.

@ernestothorp  Thank you for your reply.The problem has been solved. You're right，my globodns.yml is wrong.


businessText panel not loading svg file

The below mentioned approach worked well till grafana 11 intial version but in the latest grafana 11.1.x  its not loading
https://volkovlabs.io/blog/dynamic-text-d3-community-20240121/

@samant-rags Blog updated: https://volkovlabs.io/blog/dynamic-text-d3-community-20240121/#grafana-11


Week 4 - Free Response Question No. 1

My Fastpages
Score: /3 - based on crossover grade
Score: /3 - based on review

[x] FRQ 1
[x] Deployment on AWS for team
[x] 2D Arrays Hacks
[x] 2D Arrays Lesson
[x] Agile Methodology

Team Scrum Board

2.7 +
Score: 2.7+/3
FRQ - Did 2019 FRQ Q1s + explained the code in comments of code
Team Deployed Website
2D Arrays hacks displayed horizontally
Agile Methodology demonstrated in team scrum board