[WIP][DO NOT MERGE] add rake task to move business sector subscriptions

Trello: https://trello.com/c/50YMokiC/218-direct-map-old-new-business-sector-email-subscriptions
We'll need this for direct mapping of sectors, so we can move subscriptions.
Things to look at:

Does just swapping out the sector name for new one work?? Or do we need to do other things, e.g: tags? Can test in integration.
Don’t think it will work as expected at the moment, as it fails if can’t find new destination subscriber list. We won’t have created one at that point…?

Unfortunately, you will need to do other things here to get it to work:
The slug of a subscriber list isn't actually that important when it comes to matching subscribers with content changes - the tags and the links (plus document_type, etc) are most important here.
What happens when you try and subscribe to a finder (once you've selected the facets you want) is finder-frontend asks email-alert-api for a subscriber list that matches all the tags that are selected. email-alert-api will then either return one that matches, or create a new one (automatically generating an appropriate title and slug) if there isn't one that already exists. Perhaps confusingly, finder-frontend then passes that subscriber list into email-alert-frontend using the slug (https://www.gov.uk/email/subscriptions/new?topic_id=) which renders the standard email sign up flow for all subscriptions.
There are effectively two ways of managing a change in the facets here:

You can change the tags of the subscriber list to correctly match with the new facets. Apart from that nothing needs to change, the subscribers will still be subscribed to the same subscriber list but with the new tags it will match correctly in finder-frontend. You don't even need to change the slug or title for it to work, but you probably should.

You can forcibly create a new subscriber list by being the first person to subscribe with the new facets and then move people across into the newly created subscriber list using the existing rake tasks. This has the benefit of preserving history, and there being a record of a new subscriber list being created and an old one being deleted, but it's more work if you have lots of facets that have changed.

@thomasleese Thanks Tom, that was really helpful! The scope of this has changed somewhat, in that we're now changing the way emails work and removing the ability to select facets. Am I right in thinking that in this case, as long as we create a subscriber list to this new subscription first, we can now just do a simple move using slugs (PR updated accordingly)?

@vanitabarrett Yep, that sounds about right to me!

@thomasleese @leenagupte Can one of you please do a quick re-review - the logic around sending the emails out has changed slightly due to changing the email body (which includes a link)


Issue with k8s.io/docs/tasks/tools/install-kubectl/

This is a Bug Report
Problem:
Powershell is throwing error in output. First command 'Install-Script' succeeded but did not show any lines in console output.
-- Error in output --
PS D:\kubernetesInstalled> install-kubectl.ps1 -DownloadLocation D:\kubernetesInstalled
install-kubectl.ps1: The term 'install-kubectl.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
PS D:\kubernetesInstalled>

Proposed Solution:
I want someone to look into this issue rather than installing using Chocolatey package manager which is more difficult. Not sure why 'install-kubectl.ps1' command is throwing error.
Page to Update:
https://kubernetes.io/...

Kubernetes version 1.18.0

/sig windows

Tim,
I understand that you have added a label sig/windows. But I don't know the further plan, how this is going to resolve the issue. Please tell me what do I do to overcome this issue.
Thanks
Prakash S.

Hi @prakashid2
It sounds like there is a shortcoming in the documentation. What I hope that happens next is that a Kubernetes contributor will review this issue and triage it (confirm that there is indeed a shortcoming).
The label I added helps volunteers who use Windows / contribute to the Windows special interest group, so they can find this issue as one particularly relevant to Kubernetes on Windows.

You can also ask for help on the Kubernetes Slack, the Discuss Kubernetes forum, or using Stack Overflow.

Tim.
I've not installed Power Shell from PSGallery. Instead using Power Shell 7(x64) installed from Microsoft's website. I'm trying 'Install-Script' and 'install-kuebctl' commands inside the Power Shell 7(x64). Would this be a problem?
Or do I have to install power shell from PSGallery? and try same commands. If yes, pls let me know what is the exact link to download power shell from PSGallery. Asking this because I don't know which file to take or what exact version of power shell is required for above commands to work fine. Please reply.
Thanks
Prakash S.

Hi @prakashid2
Writing personally, I don't plan to do any further work on this issue. I do hope that a different volunteer will offer their time to help.

closing as a dup of #20709
/close


feat: base settings for smtchecker and prebuild script for exporting …

Smtchecker and prebuild script for extracting contracts.
@pavlovcik two questions about the preferred solution.

I added the prebuild script on the npm run build to ensure that we always have an updated listing of the contracts. Would you like for me to separate it?
I configured the smtchecker with some targets, which greatly downgrade the build time. Do you want to keep it as it is?

Resolves #578

Delegating your questions to @rndquu

@jpldcarvalho
Hi, thank you for the PR

I added the prebuild script on the npm run build to ensure that we always have an updated listing of the contracts. Would you like for me to separate it?

Can't we use some regexp here https://github.com/ubiquity/ubiquity-dollar/pull/604/files#diff-5084a3d2809ef6c86199f46d1d985964c92c3a98247da067d6cb04b18b0a40a9R39 in order not to update the list of contracts on each build? Are all contracts analysed if we, for example, remove the profile.default.model_checker.contracts setting?

I configured the smtchecker with some targets, which greatly downgrade the build time. Do you want to keep it as it is?

So what is the downgraded build time? I can't see any successful builds in this PR so it is hard to say whether it is a significant change.

Can't we use some regexp here https://github.com/ubiquity/ubiquity-dollar/pull/604/files#diff-5084a3d2809ef6c86199f46d1d985964c92c3a98247da067d6cb04b18b0a40a9R39 in order not to update the list of contracts on each build? Are all contracts analysed if we, for example, remove the profile.default.model_checker.contracts setting?

Sadly, it is not possible to use a regex there. If we remove the profile.default.model_checker.contracts setting, it will be the same as we have now (source). I was not aware of that.

So what is the downgraded build time? I can't see any successful builds in this PR so it is hard to say whether it is a significant change.

I only tested on my machine (in the CI it seems like it times out). This occurs because of the mix model_checker.contracts and model_checker.targets, and the contracts have the most impact. E.g. results:
6 targets 6 contracts - 3m 43s
6 targets 3 contracts - 2m 17s
3 targets 3 contracts - 2m 8s
With that in mind, I still think the script is useful to gather all the contracts/files and list them, but it should be removed from the npm run build and it should be filtered somehow,e.g. only scanning the core contracts.
Any ideas?

in the CI it seems like it times out

GitHub Actions runners can run for six hours before timing out as a heads up.

I think we shouldn't add smt check directly to the CI build step because the forge build time increases greatly (I don't know the exact timing, but smt check has already been running for 60 mins for 8 targets for 217 contracts on my laptop)
What we can do:

Create a separate script like npm run build:smt which only runs smt check. We can modify foundry.toml via js to add profile.default.model_checker option (which is not a great solution) or use a plain solc with a shell script, whatever fits best.
Create a github workflow that runs smt check only onworkflow_dispatch (not on every PR, because build time is increased greatly)
Create a task "Fix SMT errors"

So steps 1 and 2 should be part of this task.

@rndquu
For step 1, do you prefer that I use foundry.toml or a sh script?
In case you prefer the sh script, do you want me to generate the target contracts from the files in the sources or do you want it hardcoded?

@rndquu For step 1, do you prefer that I use foundry.toml or a sh script?
In case you prefer the sh script, do you want me to generate the target contracts from the files in the sources or do you want it hardcoded?

I think it's easier to use js to edit foundry.toml and then run forge build, but you're free to use whatever you think works best.
Nothing should be hardcoded, contracts should be searched and dynamically added to the foundry.toml file

Closing it because of inactivity


Make it released as pip package?

Could you please make it release as Pip/python package? so we can easily install it?

Duplicate of #522


Check for requirements only of non-optional deps

See https://github.com/Homebrew/homebrew-core/pull/16205 : testbot skips build of ffmpeg on Yosemite because one of the optional deps requires El Capitan or later.

It's not a test-bot issue.


fix psalm issues

@muglug
something is weird about this error, it's been present for a while, but never caught in CI, it only happens locally, i assume you encountered this error as well because i can see it was added in your baseline here: https://github.com/muglug/psl/blob/1.6.x/psalm-baseline.xml#L4

Pull Request Test Coverage Report for Build 681082022

8 of 8 (100.0%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 672045579:
0.0%

Covered Lines:
2922

Relevant Lines:
2922

💛  - Coveralls

Do you think UnusedVarAnnotation should be a level 1 Psalm issue? Maybe I should backtrack and only make UnusedVariable (which can have other ramifications) a level 1 issue

I think UnusedVarAnnotation should be a level 7 issue, it's easy to solve.
UnusedVariable on the other hand should be a level 1 issue, the change would be to add _ as a prefix to the variable name, and people might not want to bother with it if they just added psalm to their codebase.
I previously added those @var annotations because psalm wasn't detecting the type correctly, so it makes sense to remove them.

Yeah, I guess people can always suppress them


Trust IP not returned boolean result.

Hi, i want to ask, is the result of :
proxyaddr(req, function (addr) { return addr === '<IP_ADDRESS>' })
is boolean type ? cause the result i get is ip client, not true or false.
Thankss.

https://github.com/jshttp/proxy-addr/blob/master/README.md#proxyaddrreq-trust

Return the address of the request, using the given trust parameter.

It is documented to return the address, not true/false.


Navigation through submissions of same guide

 Issue by flbulgarelli
Monday Feb 22, 2016 at 21:49 GMT
Originally opened as https://github.com/mumuki/mumuki-classroom/issues/3

It is particularly useful when correcting exams

 Comment by faloi
Tuesday Mar 22, 2016 at 13:07 GMT

You mean through exercises, per student, right?

 Comment by flbulgarelli
Tuesday Mar 22, 2016 at 14:22 GMT

right

Fixed


fix(executor): emissary - make /var/run/argo files readable from non-root users. Fixes #6238

Fixes #6238
In this PR, I verified a real workflow works end to end with non-root users.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: hello-world-
spec:
  entrypoint: hw
  templates:
  - name: hw
    container:
      image: curlimages/curl:latest
      command: [sh, -c, "echo hello"]

Tips:

Your PR needs to pass the required checks before it can be approved. If the check is not required (e.g. E2E tests) it does not need to pass
Sign-off your commits to pass the DCO check: git commit --signoff.
Run make pre-commit -B to fix codegen or lint problems.
Say how how you tested your changes. If you changed the UI, attach screenshots.

cc @alexec, after verification, I fixed remaining issues with emissary executor + nonroot


Add a button to launch the default browser to the given port-forward

It would be great if after launching a port-forward there was a button or menu item to launch the default browser to the local port.

Oops, looks like it already does!


Disable navigation and change months dynamically

I had a use case recently where I wanted to compare the data from one month to that of another month, with two multiple-date-picker directives loading on the same page, without letting the user navigate both calendars individually, so I edited my copy of the directive to include a "disable-nav" attribute, and added the following code to the directive template:

<

After I did this, I saw that I couldn't change the month of the MDP, so I added a watch to override the nextMonth and previousMonth functions:
if(scope.disableNav){                   scope.$watch('month', function(newMonth, old){                     scope.generate();                   }, true);                 }
And the monthChanged event on the 'master' MDP instance now updates the month on the 'slave' MSP instance, so when I navigate to a new month in one, it updates the other.
I don't know if this is too specific to be a PR, but it was an enhancement I needed, so I thought I'd offer it here for discussion!

Hi,
thanks for the suggestion.
Couldn't you use disallowBackPastMonths and disallowGoFuturMonths to disable navigation ?
And you wanted the user to navigate one "master" calendar that changes a "slave" calendar too ? Not quite sure I understood the need you had but would be glad to understand :)

Any news ?

Hi @mgohin,
Sorry I didn't follow up on this earlier this week. When I passed a month into the directive with disallowBackPastMonths and disallowGoFuturMonths, the user could still navigate to the current month even if I had passed, for instance {{month-1}} to the directive - this is why I disabled the nav bar altogether.
The need for a master/slave setup was so while the user was inspecting data from the current month, he could compare it to the same data from the month prior.

Ho right I got it now.
I'll add an option to disable navigation next week, I don't have much time

Should be good, check the demo


Disable project loading in a specific workspace

Ionide/FSAC may have issues (performance or otherwise) on very large solutions. In the long term, I hope that can be resolved, but the current workaround is to use VS or Rider instead.
However, VS Code often provides a better editing experience for other files, including .fsx scripts (so Ionide shouldn't be disabled entirely).
A workspace-specific flag to disable project loading would make it more feasible to use Code & VS/Rider at the same time.

I guess we could add a setting disabling workspace initialization. Marking an issue as up for grabs.

Hello @jcmrva,
by workspace do you mean a VSCode workspace? If yes, you can disable an extension for a specific VSCode workspace Documentation
This means that you can disable Ionide for C:/ProjectA but still use it for C:/ProjectB.
However, if you want to disable Ionide for a specific sln or fsproj and still be able to use it for fsx files inside the same VSCode workspace that solution will not work.


Add Toggl extension

Description
Extension that allows you to work with Toggl timers. Currently implemented commands: start a recently used Toggl timer, stop a running Toggl timer.
Type of change

New extension

Screencast
https://user-images.githubusercontent.com/72814106/149671989-dff7d615-e042-4391-a481-8eeae9028ecf.mov
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing

Thanks for suggesting that I check out #165, @pernielsentikaer! I've been trying to find a clean way to let the user start a completely new timer and that gives me some useful ideas to play around with. Will report back after some experimentation...

Awesome @ThatNerdSquared 💪

@ThatNerdSquared I've been working on a toggl track extension in parallell with you :O
It supports creating time entries with tags, project and name

It also supports showing the current running time entry

And you can stop it

I suggest joining forces together to create the ultimate extension, so we don't have to publish two competing extensions to the store. WDYT @ThatNerdSquared :)

Hi @franzwilhelm and @ThatNerdSquared 👋
It sounds like a good plan to join forces with the Toggle extension, there are good idea in them both 💪

@franzwilhelm also reached out to me on Slack, so I replied to him there. He has yet to respond back.
For now, I've fixed up the items from your last review, @pernielsentikaer. Thanks for the feedback! Requesting another review now; if everything works out, I think we can ship this extension. I'll work with Franz in the future to add/adapt features so that this extension meshes with his workflow and ideas as well.

Hi @ThatNerdSquared and @franzwilhelm 👋
As you both are aware of, we can't have two identically extensions in the store, so we have to figure out which one should be the “base” of the extension, and then we join forces as already said.
We do also have support for “contributors” in package.json, which is shown all the way around (also in the contributors store page)
Let me know your thoughts

Hi, I would be happy to make commits to @ThatNerdSquared, but as of now my extension has a lot more features. I also tested out this extension, and although I was able to create a new time entry, the following is missing from this extension that mine has to offer:

Support for all projects in all workspaces (this one only lists projects from one of my workspaces). Hence, I was not able to create a time entry for the project I wanted.
Support for showing the current running time entry with time elapsed, project and description. This is very useful to 1. know if you have any time entry to stop, and 2. to see the current status.
Support for adding tags to new time entries

Also when I tried out the newest version of the extension I got this error. This is probably also related to the lack of multiple workspace support as it can't find the project of one of my recent time entries. That project is in a workspace it didn't fetch the projects for:

This is the part where I concede to Franz, I suppose. Feel free to close this PR @pernielsentikaer. Interesting that you can have competing PRs on this repo, I'll keep that in mind in the future if I see somebody else contributing an extension similar to mine 😉
No need to add me as a contributor on the other extension, I will continue working on my own extension as a personal project locally, it makes a good learning project for TS/React.

Either way, I've been enjoying looking at your code after writing mine @ThatNerdSquared.  It's cool to see that many of the same issues have been solved in a similar manner. I would love if e.g. weekly/monthly stats were a part of the toggl track extension in the future. If you want to collaborate on that I would love to.

Actually, I don't see it that way at all – this is mostly driven by the awesome community, and I want what's best for the community – I don't see it as a competition at any level.
It's not the first time it happened, we had 3 extensions doing the exact same within three hours, where everyone chipped in and made an awesome extension for the community.
I hope above makes sense, otherwise catch me in Slack for a conversation about it

Closing in favour of #734


Add better call error handling

Deploy preview ready!
Built with commit 7b6047679154c4d7d48d6ca98eebc73409aa4022
https://deploy-preview-599--hopeful-hamilton-4090b9.netlify.com


Investigate if a domain certificate policy can be revoked

We are looking with @cescoffier at an option of using NGrok for the Let's Encrypt ACME integration testing.
NGrok intercepts ACME challenge requests, and I've confirmed, with the help from the Ngrok service support, that after
ngrok api --api-key <YOUR-API-KEY> reserved-domains delete-certificate-management-policy <YOUR-RESERVED-DOMAIN-ID>

I can use NGrok to test the ACME flow.
YOUR-RESERVED-DOMAIN-ID is an id starting from rd_ and is available in the NGrok dashboard's domain section.
If it were possible to get hold of <YOUR-RESERVED-DOMAIN-ID> then Quarkiverse Ngrok could be used to set up a devmode intergration test.

This sounds doable!  Do you want me to look at adding this?

@melloware It would be appreciated, please investigate, thanks

Sure thing let me look.

@sberyozkin @cescoffier a couple of questions.

Do you know your API_KEY and DOMAIN_ID?  meaning if I have optional configs and we detect the DOMAIN ID we can issue the revoke before starting ngrok?

    /**
     * API key for ngrok if you need to perform any API operations such as delete-certificate-management-policy.
     */
    @ConfigItem
    public Optional<String> apiKey;

    /**
     * Reserved domain unique identifier for revoking certificate upon startup. Example: 'rd_2hrGw0rqFLOm9pcXf4dlbdNfrus'
     * If this value is not null the certificate will be revoked upon dev service startup.
     */
    @ConfigItem
    public Optional<String> reservedDomainId;

And if reservedDomainId is detected we would issue the revoke command before starting ngrok automatically?

@all-contributors add @sberyozkin for idea


Add langchain-yt-dlp Document Loader Documentation

Overview
This PR adds documentation for the langchain-yt-dlp package, a YouTube document loader that uses yt-dlp for Youtube videos metadata extraaction.
Changes

Added documentation notebook for YoutubeLoader
Updated packages.yml to include langchain-yt-dlp

Motivation
The existing LangChain YoutubeLoader was unable to fetch YouTube metadata due to changes in YouTube's structure. This package resolves those issues by leveraging the yt-dlp library.
Features

Reliable YouTube metadata extraction

Related

Package Repository: https://github.com/aqib0770/langchain-yt-dlp
PyPI Package: https://pypi.org/project/langchain-yt-dlp/

Thanks @aqib0770. Do you want to also add a providers page as described here?

What info do I have to put there?

Thanks @aqib0770. Do you want to also add a providers page as described here?

What info do I have to put there?

There aren't stringent constraints on the provider page. You can start with the template here. Examples of other providers are here.
The idea is for it to be a landing page of the underlying technology / framework (e.g., yt-dlp) in case there are multiple LangChain components that use it-- maybe a tool or similar. Not urgent at this point IMO.


Fix endless spinner on "Send link" cause by not unpausing the request queue

Details
Unpause the request queue after clearing it
Fixed Issues
$ https://github.com/Expensify/App/issues/5324
Tests
Hard to reproduce consistently
For example:

Set a console.error or debugger inside Network.js::pauseRequestQueue to confirm that the problem happened.
Go to NewDot (localhost:8080)
Throttle network speed to "Slow 3G" using chrome tools (Network tab)
Log in, Log out, repeatedly until you notice pauseRequestQueue was called after logging out.
Try to log in with a new account
Click the "Resend link" button

Expected result: load, then finish. It shouldn't get stuck in an endless spinner.

It can be good also to hardcode the email and password so you don't have to type it for each login.
QA Steps
Same as Tests, but won't be able to modify the code to set the console.error or debugger to notice when the problem happened.
Tested On

[x] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

I'm not against this solution, but I does make me wonder if it's really necessary (and I have no idea what impact, if any, it could have on the rest of the app). Alternatively, could we just have the resend link command use forceNetworkRequest = true?

Alternatively, could we just have the resend link command use forceNetworkRequest = true?

I think this would be a fine fix for this particular infinite spinner, but I do think it's possible this issue is causing infinite spinners elsewhere. In the future, if anyone needs to fix an infinite spinner caused by this issue, we might waste some time arriving at the forceNetworkRequest = true solution.
I think we should make this change here and just be sure to test for regressions on staging.

I think this would be a fine fix for this particular infinite spinner, but I do think it's possible this issue is causing infinite spinners elsewhere. In the future, if anyone needs to fix an infinite spinner caused by this issue, we might waste some time arriving at the forceNetworkRequest = true solution.
I think we should make this change here and just be sure to test for regressions on staging.

This was exactly my thought, I would also prefer this because I don't think it makes sense to leave the queue "paused" permanently.
But I'm a bit hesitant because I don't know if there could be an unprocessed event that could end up adding a request to the queue that is not supposed to be processed. Leaving it pause, would prevent any further requests from being done.

For now, I think the possibility of "infinite infinite spinners" is low, so let's just fix what's in front of us for now. We can come back to this later if we need to, but let's not risk this change which could cause a bad regression that goes unforseen in testing (especially for this N6 launch).

I'm OK with taking that route, but I do think we should come back to this to determine if this is a legitimate oversight in the structure of our network requests. By that I mean, was there a deliberate decision made not to unpause the queue, and if so why? Alternatively, this could be read, 'did we just fail to think of this edge case when building this?'

this edge case

I think this needs to be defined better, because when the code was originally written, the "send link" functionality did not exist. So saying it was a missed edge case isn't really accurate (or very helpful).

I do think we should come back to this to determine if this is a legitimate oversight in the structure of our network requests

I agree with you here. If we wanted to make this change again in the future, I would just want to be sure we have plenty of testing around it and wouldn't want to do it around a big launch.

when the code was originally written, the "send link" functionality did not exist

Got it. I apologize for my last sentence seeming brash. It's not my intention to bad-mouth our code/design.
What I meant by "this edge case" is logging out before a request is processed by addDefaultValuesToParameters. I don't think this problem should really be seen as 'Resend link doesn't work'. It's more like 'We pause the queue unintentionally by logging out'. So any request that cant force itself would fail if it happens before we're authenticated (it just happens to be 'resend link' in this case).
But again, I do agree that just allowing 'resend link' to force itself is likely the safest (and thus the best) choice right now.

All right, I had a quick DM with Luke so we could get on the same page (and make sure neither of us was bothered by the candor of our comments).
I'm digging through the code so I can be more intimately familiar with the problem and solution. Stay tuned!

@aldo-expensify While investigating this, I'm wondering if you've re-tested this since the changes to the sign-out flow here
Side Note: I'm not sure if this is causing a problem but it did look strange to me. Right now redirectToSignIn() will race API.DeleteLogin. Here's my suggestion to fix that (again though, not positive this is a problem).
 /**
  * Clears the Onyx store and redirects user to the sign in page
  */
 function signOut() {
     Log.info('Flushing logs before signing out', true, {}, true);
     if (credentials && credentials.autoGeneratedLogin) {
         // Clean up the login that we created
         API.DeleteLogin({
             partnerUserID: credentials.autoGeneratedLogin,
             partnerName: CONFIG.EXPENSIFY.PARTNER_NAME,
             partnerPassword: CONFIG.EXPENSIFY.PARTNER_PASSWORD,
             doNotRetry: true,
+         }).then(() => {
+             redirectToSignIn();
+         }).catch(error => Onyx.merge(ONYXKEYS.SESSION, {error: error.message}));
     }
     Timing.clearData();
-    redirectToSignIn();
     console.debug('Redirecting to Sign In because signOut() was called');
 }

Sorry, for my absence in your conversation :P, I was struggling with another PR

While investigating this, I'm wondering if you've re-tested this since the changes to the sign-out flow here

No, I haven't, I guess it could be interesting to see if this is still happening.

Side Note: I'm not sure if this is causing a problem but it did look strange to me. Right now redirectToSignIn() will race API.DeleteLogin. Here's my suggestion to fix that (again though, not positive this is a problem).

I understand that redirectToSignIn is clearing the data locally and I would guess API.DeleteLogin is clearing something in the server? If that is the case, I don't see a reason why redirectToSignIn should wait for API.DeleteLogin to finish. does it matter who finishes first?

All right, I had a quick DM with Luke so we could get on the same page (and make sure neither of us was bothered by the candor of our comments).
I'm digging through the code so I can be more intimately familiar with the problem and solution. Stay tuned!

Thanks!

I don't see a reason why redirectToSignIn should wait for API.DeleteLogin to finish. does it matter who finishes first?

I agree with this as well! My guess is that it could fix this problem, but only in an accidental way (it would be similar to adding a setTimeout())
My Conclusion
I think that adding forceNetworkRequest still makes some sense. I know it's not very clear why we want to do this because forcing a network request for a command that doesn't require an authToken doesn't make a whole lot of sense. However, I think it's better than unpause() because I am very concerned that this would happen:
If the queue is unpaused, and another request is made that requires an authToken, it will just ignore the request (clear it from the queue).
And that could have some unintended side-effects.
Alternative
Another alternative to using forceNetworkRequest would be something like this:
function addDefaultValuesToParameters(command, parameters) {
    const finalParameters = {...parameters};
+    const skipAuthTokenCheck = Network.isQueuePaused() && !isAuthTokenRequired(command);

+    if (!skipAuthTokenCheck && isAuthTokenRequired(command) && !parameters.authToken) {
-    if (isAuthTokenRequired(command) && !parameters.authToken) {

I'm still leaning toward unpausing, but not so hard on it... so I'll leave some more thoughts on it, and if you still think that the better path is forceNetworkRequest, we can go that way 😬

The queue starts unpaused when you open the app. I would expect that if we logout, the queue should be left in that same state.
When we reach the code that leaves the queue paused after logout, in the cases I've seen, it is a request trying to fetch some information for the chat. If there was a second request trying to get this kind of information, I would think that we would want to get rid of that request also. Leaving the queue paused would queue that request until a new user logs in. I haven't come up with a case where could we want to queue a request because the authToken went missing after a logout? I would think that request mattered to the session that just finished, if a new user log in, we probably don't want that request.

I don't see a reason why redirectToSignIn should wait for API.DeleteLogin to finish. does it matter who finishes first?

Doh! Good point 😄. I don't know why but when I see async code without chaining it makes me shudder.
I think the 'unpause' strategy is the best strategy for the long term, but I agree with Tim that we can get by with a change that impacts less of the app (every request gets hit with addDefaultValuesToParameters so it's dicey to touch that method.
@tgolen I like your alternate idea because it solves for the 'resend link' case, and any others that may get hung up on a paused queue.

Alternative
Another alternative to using forceNetworkRequest would be something like this:
function addDefaultValuesToParameters(command, parameters) {
    const finalParameters = {...parameters};
+    const skipAuthTokenCheck = Network.isQueuePaused() && !isAuthTokenRequired(command);

+    if (!skipAuthTokenCheck && isAuthTokenRequired(command) && !parameters.authToken) {
-    if (isAuthTokenRequired(command) && !parameters.authToken) {

If you process that if condition like this:
const skipAuthTokenCheck = Network.isQueuePaused() && !isAuthTokenRequired(command);
if (!skipAuthTokenCheck && isAuthTokenRequired(command) && !parameters.authToken) {

that's the same as
if (!(Network.isQueuePaused() && !isAuthTokenRequired(command)) && isAuthTokenRequired(command) && !parameters.authToken) {

that's the same as
if ((!Network.isQueuePaused() || isAuthTokenRequired(command)) && isAuthTokenRequired(command) && !parameters.authToken) {

that's the same as
if (isAuthTokenRequired(command) && !parameters.authToken) {

Which is the original condition. The isAuthTokenRequired(command) is still required outside of the nested OR condition, so the value of Network.isQueuePaused() doesn't really matter.

OK, sounds like we've discussed this one to death, so we can try the unpause and see how well it performs.

OK, sounds like we've discussed this one to death, so we can try the unpause and see how well it performs.

hehe 😝 , ok!
Thanks for all the time spent figuring this out!

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @Luke9389 in version: 1.1.4-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


tech stack

i am planning to use next js with instant db and fast api
but if i use fastapi, i need postgresql too
so still considering to go with instant db or not but i wanna try it hahah

instantdb sucks, will proceed with postgres

not sucks, more to like not ready with what i need. instantdb good


Enable nested training functions with Dill

Difficulty: ★★☆☆☆

Background
Most PyTorch users are all about the functional API.
Problem
Currently we use Pickle with a single function, which doesn't support nested functions.
Solution
Switch serialization of functions to manually use Dill. Switch ORM field type to bytes. Have a look around to see if anyone using the ORM has a solution.

https://github.com/aiqc/aiqc/commit/a87e9494174f9dfed41a2b363ec6849d8a79042b


Can't Create Short URL

[x] Check you are using the LATEST release or the development branch.
[x] Make sure you have SEARCHED existing issues first.
[ ] Read the GUIDELINES linked in the yellow notice box above.
[x] COMPLETE this issue template.

Describe the bug
Using 1.7.3 when I type a valid HTTPS URL into the URL field and click Shorten the URL that button turns green and does nothing more.
To Reproduce
Steps to reproduce the behavior:

Go to mysite.com/admin
Enter a URL.  Then Click on Shorten the URL button
Notice how the button is green with a swirling icon.
And nothing more.
Enable debug.
See on re-freshed page:

Connected to database yourls on localhost
SQL: SELECT option_name, option_value FROM yourls_options WHERE 1=1 (0.00106 s)
Check for new version: no
SQL: SELECT COUNT(keyword) as count, SUM(clicks) as sum FROM `yourls_url` WHERE 1=1  (0.00020 s)
SQL: SELECT * FROM `yourls_url` WHERE 1=1  ORDER BY `timestamp` desc LIMIT 0, 15; (0.00015 s)

Click button again.
See that the debug message didn't change.

Expected behavior
I thought it would give me a shortened URL.
Environment (please complete the following information):

YOURLS version: 1.7.3

Plugins enabled: What is this?

PHP version: 7
Other relevant details depending on the context (server OS & version, MySQL version, browser version, …)  Ubuntu 16.04

I just experienced the same issue. I checked chrome dev tools and I saw that the problem was due to CORS error. I reopened the page using https and it worked fine. I checked again without https and problem persists. I don't know if this is the intended behavior or this is a bug.
Try opening the page using https and see if it works for you.

https://github.com/YOURLS/YOURLS/wiki/Endless-Spinning-Icon ?

Thank you but the problem is when I open https://short.com/admin, after login yourls redirects to non-https url http://short.com/admin. It'd be helpful if yourls automatically redirect to the https version after login.

@hemor the https version solved the problem.  Thank you.


MAP_ANONYMOUS not valid on Yosemite, define only if needed.

Andy Li is this better?

I think if missing on linux you would need alternate remap so it's better behind an if apple flag.

using #ifndef would be slightly better ;)

ah ok, amended, can't check the code on yosemite as I have now upgraded so likely no longer an issue for me but hopefully makes code more robust.

amended.


fix a crash bug when networking is down

When networking is down, getaddrinfo will fail leaving pResultList untouched. Calling freeaddrinfo on NULL will result in segment fault.

Thanks for submitting!
Checking for NULL is never a bad idea, but often it is unnecessary when deallocating memory.
Consider the following code that forces a call to freeaddrinfo with a NULL parameter:
#include <stdio.h>
#include <sys/types.h>
#include <sys/socket.h>
#include <netdb.h>
int main()
{
    freeaddrinfo(NULL);
    printf("Return from freeaddrinfo\n");
    return 0;
}

I compiled the following code on both Mac and Linux, it runs fine without crashing or issue.  Every deallocator function I know of (delete, free, etc...) will always check for NULL first.  Just like having delete NULL or free(NULL) is also safe code.  So it seems safe that freeaddrinfo(NULL) will also be safe.
Did you actually have a real crash as a result of the network being down?  If so, what platform , OS, and version did you get this to crash on?  And if that's the case, I'll happily take the change and republish.
Or is this a theoretical crash that you spotted from looking at the code?  If that's the case, I'll still pull the change, but I won't worry about publishing updates to the website.
Thanks,
jrs

The crash actually occurs on Android platform when network goes down. I'm using stunserver as jni lib, compiled with android ndk r9d and running on Android 4.4. After adding NULL checking, the crash goes away.

Thanks.  I will merge the code.


IPAM Address Searching

Issue type
[x] Feature request
[ ] Bug report
[ ] Documentation

Environment

Python version:
NetBox version:

Description
Would it be possible to allow for searching device types and device names within the scope of IP addresses?
I would like to be able to search for all IP addresses assigned to a device type or in the case of a device with multiple VLANs and whatnot, see what all IP addresses are assigned to a device from the IP address search page.

This isn't something we'd implement a built-in filter for because it spans too many relationships. However you can achieve this easily using the command shell:
$ ./manage.py nbshell
### NetBox interactive shell (jstretch-laptop)
### Python 3.4.3 | Django 1.11.4 | NetBox 2.1.4-dev
### lsmodels() will show available models. Use help(<model>) for more info.
>>> device_type = DeviceType.objects.get(manufacturer__slug='juniper', model='EX4300-48T')
>>> ip_addresses = IPAddress.objects.filter(interface__device__device_type=device_type)
>>> for ip in ip_addresses:
...   print(ip)
...
<IP_ADDRESS>/24
<IP_ADDRESS>/24
<IP_ADDRESS>/24
...


Very slow Direct2D back-end bitmap rendering compared to SkiaSharp

Avalonia: 0.5.1
Demonstration:
https://files.gitter.im/AvaloniaUI/Avalonia/E6US/Avalonia-0.5.1-SkiaSharp.mp4
https://files.gitter.im/AvaloniaUI/Avalonia/qm8E/Avalonia-0.5.1-Direct2D.mp4
Rendering code:
https://github.com/wieslawsoltes/Core2D/blob/master/src/Renderer.Avalonia/AvaloniaRenderer.cs#L605-L674
Binaries:
https://ci.appveyor.com/api/buildjobs/s5w2yaic67ovur4y/artifacts/artifacts%2Fzip%2FCore2D.Avalonia.Skia-Release-0.2.0-build1796.zip
https://ci.appveyor.com/api/buildjobs/s5w2yaic67ovur4y/artifacts/artifacts%2Fzip%2FCore2D.Avalonia.Direct2D-Release-0.2.0-build1796.zip
Project:
https://files.gitter.im/AvaloniaUI/Avalonia/oaHq/Rendering-Perf.project

I think this is because we convert WIC bitmaps to Direct2D bitmaps for each render. We probably need to cache D2D bitmaps.

This must be cached per render target and should be removed from the cache when the render target gets disposed. Quite hard to keep track.


NaCl Strace

As discussed the in the meeting today lets make a way to create a NaCl strace. The output should look as close as possible the output to calling strace on a program so we can compare Lind results to native.
The easiest way to do this would be adding some ifdefs top native client so that if we compile the sel_ldr with the strace option defined, it will print the trace to a trace file.
We can put these prints  in nacl_syscall_common.c for every syscall ie NaClSysOpen. These should output the cageid as pid, and the syscall name/number as well as any other info that native strace does.
Later on lets try to take this trace and possibly create a record replay system.

I had a few thoughts and wanted to chime in.  (Feel free to push back if you disagree.)
I wouldn't stress too much about looking like strace.  It does a bunch of odd things in places for historical reasons and it isn't very suitable for replay.  I would focus on easy to serialize / deserialize over being easy to read.
If you have serialized information, you can have a utility that prints this file in a nicely readable way which could be close to strace, if you desire.  Being able to replay is the main goal, of course.

Just seeing this.
I think trying to mirror strace would be really handy because then we could easily compare log files side by side. From our debugging experience this seems really useful and not that difficult for Coulson to implement.
The replay seems like a cool idea but seems like it could become a huge project which might not be the best allocation of resources. Once the new server is up I'll be able to tell if we can have Lind run some of these bigger application suites (ie the LAMP stack) in RR without crashing. If we can use RR then our handrolled replay wouldn't really be useful.

This was completed by @yizhuoliang @yashaswi2000 @rupeshkoushik07
Great job guys


Display the date and time for a Credential

Summary
The current display for Credential shows 2 fields as timestamps instead of datetimes.
Current behaviour
At the moment, the Display instance for the Credential struct only displays the timestamps for created and expired:
//TODO: write timestamps on human-readable format. Should we add a dependency for this?
writeln!(f, " Created: {}", u64::from(credential_data.created))?;
writeln!(f, " Expires: {}", u64::from(credential_data.expires))?;

Expected behaviour
It would be a lot nicer to display a formatted ISO datetime, using a minimal time library like https://crates.io/crates/time.
Bonus points 🚀 if you:

refactor the code so that the existing Display code is actually a Display instance on CredentialData
create another instance of Display for Credential simply delegating to the CredentialData Display instance
add a unit test for the formatting

hello, pls assign to me @etorreborre

Hi Kelvin, sure!

Hello @etorreborre
To understand how Credential print out, i was looked at this example
Run it, but it doesnt show me anything after waiting for awhile

Dont know any missing or any other steps i need to do first.

hello @etorreborre ^^

Hi @0xkelvin, sorry I missed your message. This works for me and displays something like
---
 Subject: P6474cfdbf547240b6d716bff89c976810859bc3f47be8ea620df12a392ea6cb7
 Issuer: P0db4fec87ff764485f1311e68d6f474e786f1fdbafcd249a5eb73dd681fd1d5d (OCKAM_RK)
 Created:<PHONE_NUMBER>
 Expires:<PHONE_NUMBER>
 Attributes: {"component": "control", "project_id": "ba875b38-0042-4aea-b4a9-3772bf9506da"}

 Signature: e599f69661f4b3729944586e09ba45dbb48eff1306e6e78fdd1bbf1ecdb23934ace3d0220fe1b599e6a15038fe7a0ae01dec1096ec911ce7c695bb1c76e1ae05
---

However the current instructions are missing the first step which is to run ockam enroll in order to create a project. Have you done that? Then you need to create a project.json file with ockam project information --output json  > project.json.
The project.json file must be in the same directory as the directory you use to start the "control_plane" node.
That being said you don't have to do all of this. You can write a unit test where you create a CredentialData struct and where you call the Display instance for CredentialData. That implementation does not exist yet but you can extract it from the Display implementation for Credential. Basically what I indicated in the "bonus points" section which is actually the simplest thing I can think of to get the job done :-).

hello @etorreborre
getting back on this.
i tried to run the 'cargo test' under 'ockam_identity' folder
but there are few errors :

i was removed
use crate::alloc::borrow::ToOwned; use crate::alloc::string::ToString;
then it is fine, but not so sure that we need to use above import or not ?

@0xkelvin I think this will fix that issue

Hello @sanjayatpilcrow @etorreborre

does it looks OK ?

@0xkelvin I would go for a ISO-8601 format: 2023-03-08T09:43:00Z. This is standard and uses a UTC time, as indicated by the Z)

@0xkelvin I would go for a ISO-8601 format: 2023-03-08T09:43:00Z. This is standard and uses a UTC time, as indicated by the Z)

@etorreborre , not so sure it is correct or not, i saw many zero

@0xkelvin can you please share your code? I don't know how you are producing the datetime formatting but I suspect that there must be a way to specify a less precise format.

@etorreborre i make a draft PR here : https://github.com/build-trust/ockam/pull/4429
please guide me if i am wrong

@0xkelvin thanks. It seems that you can configure the ISO default format and specify the precision for seconds: https://docs.rs/time/0.3.20/time/format_description/well_known/iso8601/struct.Config.html#method.set_time_precision

@etorreborre i see, how many number of decimal digits is good enough ?

For a credential I don't think that we need to go lower that a second, so I would say 0.

For a credential I don't think that we need to go lower that a second, so I would say 0.

@etorreborre

@etorreborre
could you please explain a bit the syntax that i highlighted:

i trying to understand to relationship between Credential and CredentialData

ah i see here :

@etorreborre could you please explain a bit the syntax that i highlighted:
i trying to understand to relationship between Credential and CredentialData

ah i see the relationship here

@etorreborre
regarding refactor, could you please help me look at latest commit on PR https://github.com/build-trust/ockam/pull/4429
I hope that is a right direction.
and I also would like to seeking your guide about this issue with decode:

i dont know what i should do

Yes I think that this is the right direction. To solve your current issue you can use the TryFrom instance allowing you to go from Credential to CredentialData and write:
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
    CredentialData::try_from(self).map_err(|_| fmt::Error)?.fmt(f)
}

(note that I'm mapping conversion errors to formatting errors as it was done before in the code)

as it was done before in the code

i think it getting better on latest commit in my PR https://github.com/build-trust/ockam/pull/4429
please help review

@0xkelvin that looks good indeed. Do you need any further help?

@0xkelvin that looks good indeed. Do you need any further help?

i made it as official PR https://github.com/build-trust/ockam/pull/4429
please review

@etorreborre can close this, since it merged


Add support for control frame

There is no feedback from Bijou about that but merging to move forward.


mongosh: init at 1.5.0

Motivation for this change
The MongoDB Shell, mongosh, is a fully functional JavaScript and Node.js 14.x REPL environment for interacting with MongoDB deployments. You can use the MongoDB Shell to test queries and operations directly with your database.
Resolves  #159419
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

Mongosh is kinda slow in support for newer node versions. I think keeping it separate from nodePackages would be good for maintenance.

@SuperSandro2000 Should we downgrade mongosh or mark it broken?

@aaronjheng naively I wonder why not just update mongosh to use nodejs-16_x?

Yeah, I don't see a blocker why we couldn't do this.

Actually, there is a blocking issue. See https://github.com/NixOS/nixpkgs/issues/132456.


Package not published for Python 3.5 on Linux

Package not published for Python 3.5 on Linux

Python 3.5 is no longer supported, sorry!


Rename Azimuth team to Platform and update Batch team members

╷
│ Error: Instance cannot be destroyed
│
│   on teams.tf line 1:
│    1: resource "github_team" "organisation_teams" {
│
│ Resource github_team.organisation_teams["Azimuth"] has
│ lifecycle.prevent_destroy set, but the plan calls for this resource to be
│ destroyed. To avoid this error and continue with the plan, either disable
│ lifecycle.prevent_destroy or reduce the scope of the plan using the -target
│ flag.

Maybe keep the old team around for now?


cc-wrapper.sh, ld-wrapper.sh: unexpand @files

When the initial invocation had an @file
To address https://github.com/NixOS/nixpkgs/issues/255359
Description of changes
Export NIX_RESPONSE_FILE_EXPANDED=1 when the original wrapper execution had an @file.
cc-wrapper and ld-wrapper check if $NIX_RESPONSE_FILE_EXPANDED >= 1 when deciding to make an @file.
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

I thought that this broke bison, but on staging it just breaks meson.

Currently running nixpkgs-review. Going to see how many failures there are and if it's not too many, I'll take this out of draft.

Ok I should relinquish the build server I was using to do other work. nixpkgs-review built ~6000 derivations successfully in addition to the stdenv and all the reproducer inputs. ~20 failed.
The reproducer still failed because collect2 is still not execveed by gcc in a way that avoids ARG_MAX on linux.
I submitted a patch proposal in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86030. I verified it used a response file when executing ld all the way in reproducer. Yet was _still_thwarted by some machinery in the way ld executed collect2.
In any case I think this patch and the proposed gcc patch (with some appropriate review) are good steps in the right direction.

Also cc @cdepillabout who has dealt with E2BIG using ghc tooling in the past.

cc @nh2 and @Gabriella439, who I think have also looked into this in various ways


Implement request list + sort by drop down

Task
Screenshot

Request List

Sort by

ToDo

[ ] Get Data From Database


Added in a couple of ENV variables for TeamCity

Can't have it failing when it should be passing! ;)

That's the spirit!


INSERT statement conflicted with the FOREIGN KEY constraint for Payment methods and Regions

Umbraco: v13.0.3
Deploy: v13.0.3
Commerce.Deploy: v13
TL;DR;
Deleted regions are not exported to UDAs but are still listed as dependencies in payment method UDAs
Full Info
When cloning my Cloud environment to my local PC the installer fails to deploy the schema to the fresh database.  This is before the Restoring content phase happens.  The same thing also happens when creating a new development environment in Umbraco Cloud.
The deploy.log output is at the bottom.  Looking at the UDA files I can see that the problem artifact umb://umbraco-commerce-payment-method/93b59042f0554000a0a2018c8757acd5 has umbraco-commerce-region dependencies listed that don't exist in the freshly created local database and aren't listed in the Live environment's backoffice either.
In total the artifact has 10 region dependencies, which matches the live database, however 2 of them have deletedTimestamp values.  Only 8 region UDA files are exported to disk, even after a fresh export to UDA performed in the live environment.  I can also confirm that the PaymentMethodAllowedCountryRegions table has entries for the deleted regions too.
I've had a support case with Umbraco Cloud since the beginning of January, but it's starting to feel like a bug to me so I thought I'd post here as well.
Can I safely remove the extra dependencies from the UDA file, or will they be added again with a fresh export?
EXCEPTION:

Umbraco.Deploy.Core.Exceptions.ProcessArtifactException: Process pass #4 failed for artifact umb://umbraco-commerce-payment-method/93b59042f0554000a0a2018c8757acd5.
   at Umbraco.Deploy.Infrastructure.Environments.CurrentEnvironment.ProcessArtifacts(IEnumerable`1 arts, String ownerEmail, IDeployContext context, CancellationToken token)
   at Umbraco.Deploy.Infrastructure.Environments.CurrentEnvironment.ProcessPackageAsync(Guid sessionId, Package package, CancellationToken token)
   at Umbraco.Deploy.Infrastructure.Work.WorkItems.DiskReadWorkItem.Proceed(List`1 artifacts, Manifest manifest)
   at Umbraco.Deploy.Infrastructure.Work.WorkItems.DiskReadWorkItem.ExecuteAsyncSub(IWorkContext context, List`1 resume, CancellationToken token)
   at Umbraco.Deploy.Infrastructure.Work.WorkItems.DiskReadWorkItem.ExecuteAsync(IWorkContext context, CancellationToken token)

INNER:
	Microsoft.Data.SqlClient.SqlException: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_umbracoCommercePaymentMethodAllowedCountryRegion_umbracoCommerceRegion". The conflict occurred in database "c:\[PATH REMOVED]", table "dbo.umbracoCommerceRegion", column 'id'.
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_umbracoCommercePaymentMethodAllowedCountryRegion_umbracoCommerceRegion". The conflict occurred in database "c:\[PATH REMOVED]", table "dbo.umbracoCommerceRegion", column 'id'.
The statement has been terminated.
The statement has been terminated.
	   at Umbraco.Commerce.Infrastructure.Resiliency.PollyExecutionStrategyBase.Execute[TResult](Func`1 operation, Func`1 verifySucceeded)
	   at Umbraco.Commerce.Core.UmbracoCommerceUnitOfWorkProvider.Execute(IUnitOfWorkOptions options, Action`1 action)
	   at Umbraco.Commerce.Core.UmbracoCommerceUnitOfWorkProvider.Execute(Action`1 action)
	   at Umbraco.Commerce.Deploy.Connectors.ServiceConnectors.UmbracoCommercePaymentMethodServiceConnector.Pass4(ArtifactDeployState`2 state, IDeployContext context)
	   at Umbraco.Commerce.Deploy.Connectors.ServiceConnectors.UmbracoCommercePaymentMethodServiceConnector.Process(ArtifactDeployState`2 state, IDeployContext context, Int32 pass)
	   at Umbraco.Deploy.Infrastructure.Connectors.ServiceConnectors.ServiceConnectorBase`3.Process(ArtifactDeployState dart, IDeployContext context, Int32 pass)
	   at Umbraco.Deploy.Infrastructure.Environments.CurrentEnvironment.ProcessArtifacts(IEnumerable`1 arts, String ownerEmail, IDeployContext context, CancellationToken token)

EXCEPTION:

Umbraco.Deploy.Core.Exceptions.ProcessArtifactException: Process pass #4 failed for artifact umb://umbraco-commerce-payment-method/93b59042f0554000a0a2018c8757acd5.
   at Umbraco.Deploy.Infrastructure.Environments.CurrentEnvironment.ProcessArtifacts(IEnumerable`1 arts, String ownerEmail, IDeployContext context, CancellationToken token)
   at Umbraco.Deploy.Infrastructure.Environments.CurrentEnvironment.ProcessPackageAsync(Guid sessionId, Package package, CancellationToken token)
   at Umbraco.Deploy.Infrastructure.Work.WorkItems.DiskReadWorkItem.Proceed(List`1 artifacts, Manifest manifest)
   at Umbraco.Deploy.Infrastructure.Work.WorkItems.DiskReadWorkItem.ExecuteAsyncSub(IWorkContext context, List`1 resume, CancellationToken token)
   at Umbraco.Deploy.Infrastructure.Work.WorkItems.DiskReadWorkItem.ExecuteAsync(IWorkContext context, CancellationToken token)

INNER:
	Microsoft.Data.SqlClient.SqlException: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_umbracoCommercePaymentMethodAllowedCountryRegion_umbracoCommerceRegion". The conflict occurred in database "c:\[PATH REMOVED]", table "dbo.umbracoCommerceRegion", column 'id'.
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_umbracoCommercePaymentMethodAllowedCountryRegion_umbracoCommerceRegion". The conflict occurred in database "c:\[PATH REMOVED]", table "dbo.umbracoCommerceRegion", column 'id'.
The statement has been terminated.
The statement has been terminated.
	   at Umbraco.Commerce.Infrastructure.Resiliency.PollyExecutionStrategyBase.Execute[TResult](Func`1 operation, Func`1 verifySucceeded)
	   at Umbraco.Commerce.Core.UmbracoCommerceUnitOfWorkProvider.Execute(IUnitOfWorkOptions options, Action`1 action)
	   at Umbraco.Commerce.Core.UmbracoCommerceUnitOfWorkProvider.Execute(Action`1 action)
	   at Umbraco.Commerce.Deploy.Connectors.ServiceConnectors.UmbracoCommercePaymentMethodServiceConnector.Pass4(ArtifactDeployState`2 state, IDeployContext context)
	   at Umbraco.Commerce.Deploy.Connectors.ServiceConnectors.UmbracoCommercePaymentMethodServiceConnector.Process(ArtifactDeployState`2 state, IDeployContext context, Int32 pass)
	   at Umbraco.Deploy.Infrastructure.Connectors.ServiceConnectors.ServiceConnectorBase`3.Process(ArtifactDeployState dart, IDeployContext context, Int32 pass)
	   at Umbraco.Deploy.Infrastructure.Environments.CurrentEnvironment.ProcessArtifacts(IEnumerable`1 arts, String ownerEmail, IDeployContext context, CancellationToken token)

[Failed]

EXCEPTION
Umbraco.Deploy.Core.Exceptions.ProcessArtifactException: Process pass #4 failed for artifact umb://umbraco-commerce-payment-method/93b59042f0554000a0a2018c8757acd5.
 ---> Microsoft.Data.SqlClient.SqlException (0x80131904): The INSERT statement conflicted with the FOREIGN KEY constraint "FK_umbracoCommercePaymentMethodAllowedCountryRegion_umbracoCommerceRegion". The conflict occurred in database "c:\[PATH REMOVED]", table "dbo.umbracoCommerceRegion", column 'id'.
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_umbracoCommercePaymentMethodAllowedCountryRegion_umbracoCommerceRegion". The conflict occurred in database "c:\[PATH REMOVED]", table "dbo.umbracoCommerceRegion", column 'id'.
The statement has been terminated.
The statement has been terminated.
   at Umbraco.Commerce.Infrastructure.Resiliency.PollyExecutionStrategyBase.Execute[TResult](Func`1 operation, Func`1 verifySucceeded)
   at Umbraco.Commerce.Core.UmbracoCommerceUnitOfWorkProvider.Execute(IUnitOfWorkOptions options, Action`1 action)
   at Umbraco.Commerce.Core.UmbracoCommerceUnitOfWorkProvider.Execute(Action`1 action)
   at Umbraco.Commerce.Deploy.Connectors.ServiceConnectors.UmbracoCommercePaymentMethodServiceConnector.Pass4(ArtifactDeployState`2 state, IDeployContext context)
   at Umbraco.Commerce.Deploy.Connectors.ServiceConnectors.UmbracoCommercePaymentMethodServiceConnector.Process(ArtifactDeployState`2 state, IDeployContext context, Int32 pass)
   at Umbraco.Deploy.Infrastructure.Connectors.ServiceConnectors.ServiceConnectorBase`3.Process(ArtifactDeployState dart, IDeployContext context, Int32 pass)
   at Umbraco.Deploy.Infrastructure.Environments.CurrentEnvironment.ProcessArtifacts(IEnumerable`1 arts, String ownerEmail, IDeployContext context, CancellationToken token)
ClientConnectionId:040941cd-1add-4552-9781-46e37639bb3e
Error Number:547,State:0,Class:16
   --- End of inner exception stack trace ---
   at Umbraco.Deploy.Infrastructure.Environments.CurrentEnvironment.ProcessArtifacts(IEnumerable`1 arts, String ownerEmail, IDeployContext context, CancellationToken token)
   at Umbraco.Deploy.Infrastructure.Environments.CurrentEnvironment.ProcessPackageAsync(Guid sessionId, Package package, CancellationToken token)
   at Umbraco.Deploy.Infrastructure.Work.WorkItems.DiskReadWorkItem.Proceed(List`1 artifacts, Manifest manifest)
   at Umbraco.Deploy.Infrastructure.Work.WorkItems.DiskReadWorkItem.ExecuteAsyncSub(IWorkContext context, List`1 resume, CancellationToken token)
   at Umbraco.Deploy.Infrastructure.Work.WorkItems.DiskReadWorkItem.ExecuteAsync(IWorkContext context, CancellationToken token)

Hi @BenWhite27
Had a look at this on my project and I was able to reproduce the issue by doing the following steps which you provided:

Create Region
Create Payment Method and a Shipping Method with the region assigned.
Check that the UDA schema is exported as expected.
Delete the Region
See that the Region no longer has a UDA file, but the region remains as a dependency in the UDA files for the Payment method and Shipping method

Additionally, when deleting the region, if you have not cleared the dependency from the Payment method as a allow country or shipping method allow region/country that reference will stay in the database and not be cleared out.

Quick update:
I worked with Umbraco Cloud support to resolve the conflicts in my database.  The instructions they provided have corrected the data in my database and permits a painless clone/restore of the cloud project once more.
In my case it was the Payment Method Allowed Regions table which still had references to some regions that were deleted.  The instructions for Support were as follows, repeated for each payment method:-

Unselect all regions
Save
Unselect all countries
Save
Re-select the original Countries and Regions
Save

This effectively rebuilds the relationships and clears the table of relationship related to the deleted regions.
I still believe there is a bug or two present here.

As there is no way to restore a region from the back office, I'm not sure what it was marked as deleted, instead of actually deleting the region record and cascading the deletes down to the Allowed region assignments.  If the region record is required still, then there's probably not much Umbraco Commerce can do for this one.
The Deploy package should either...

not export dependencies to UDA files if the principal of the dependency is deleted.
OR
also export the deleted principal along with the normal entities.


fix(go-sdk): add missing description field in SLI

It's also fixed in https://github.com/OpenSLO/OpenSLO/pull/288

I'll incorporate it into https://github.com/OpenSLO/OpenSLO/pull/285 to limit conflicts for myself. Good catch!


Similar document for M365

Is there a similar tool for M365?

No idea, this repo has been created by Azure engineers, who are in a whole different Microsoft organization than M365.


Update docs for new AMDC REV F hardware

We need to update the docs.amdc.dev website to have support for the new REV F hardware.

[x] Update https://docs.amdc.dev/hardware/revisions/firmware-upgrades-per-hardware-target.html
[x] Copy the Hardware / PCB Revisions / REV E Hardware pages and make a REV F version. Then, update the content for the new REV F pages---no changes to the bring-up or pin mapping, should only be the top level page.
[x] Look for pages that discuss "the latest hardware version" and update with the REV F etc
[ ] Maybe other updates...there are many docs pages...

Both REV F and REV E bring-up guides were using outdated images. I updated the references but the new images don't exist yet. I will need to capture them in the lab and add them to the docs repo.

[ ] REV E and REV F should each have their own REV silk image with SN sticker
[ ] REV E folder should get new images for jumpers and heatsink, and REV F can point to those images

So far I've updated everything under the hardware folder except subsystems, as this is all outdated with the last update being REV D

[ ] Update hardware/subsystems. To my knowledge, the page most needing updates here is expansion-port.md, since REV E and beyond have "GPIO" instead of "isoSPI". However, all pages would benefit from images of a newer AMDC REV and a general lookover.


Are there some kind of documents of utils/NodeList.js?

I'm actually using NodeList.js to write some components that need DOM interactive, but i can't find this repo on github, so i'm wondering if this utility is wrote by someone in this repo? Thanks.

NodeList was edited by me, but is based on that: https://github.com/eorroe/NodeList.js
The original nodelist have not event handlers, but the rest are close enought.


Diff syntax highlight in the commit message file

The diff that gets displayed in the commit window isn't highlighted.
I think git-savvy.make-commit & git-savvy.diff should be merged somehow, so that the diff can be properly highlighted during commits.

This can be fix with including the diff in make-commit.

I look like you studied it, Would you like to make a Pull Request on this?
https://www.sublimetext.com/docs/3/syntax.html look under section Include Patterns.

I can not see that this PR is making any difference. Could you add two screenshots of before and after?

Here you go:
Before:

After:

I am on git version 2.8.2 and my diff looks like this

## To make a commit, type your commit message and press SUPER-ENTER. To cancel
## the commit, close the window. To sign off on the commit, press SUPER-S.

## You may also reference or close a GitHub issue with this commit.  To do so,
## type `#` followed by the `tab` key.  You will be shown a list of issues
## related to the current repo.  You may also type `owner/repo#` plus the `tab`
## key to reference an issue in a different GitHub repo.

diff --git a/core/commands/inline_diff.py b/core/commands/inline_diff.py
index 4ff181c..0896e6e 100644
--- a/core/commands/inline_diff.py
+++ b/core/commands/inline_diff.py

Can you check your git version? $ git --version

I am on 2.8.1

I knew it was some custom setting that I had. Turns out there is a setting in git config called noprefix which removes those a, b characters.
Though I think that GitSavvy should handle both these cases.

Sure, I agree


php file_get_contents method

PHP is a server-side language, it's not read by the browser. Caniuse is only fol client-side technologies.


⚠ Fortnite has degraded performance

In d2a3dd2, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1574 ms

Resolved: Fortnite performance has improved in 5434f0b.


Training vmambav2_tiny_224 on CIFAR-10

Hi,
I want to train vmambav2_tiny_224 on CIFAR-10 and was wondering what minimal additional changes are required besides:

Changing _C.DATA.DATASET to 'CIFAR10'
Setting DATA.IMG_SIZE to 32
Setting MODEL.NUM_CLASSES to 10

Thanks!

I think these changes maybe enough for the dataset, but you'd better try it out yourself until you really met a problem.


CXF-8654: Ensure InputStreamDataSource is optional in JAXRSUtils to be able to run without activation dependency

Ensure InputStreamDataSource is optional in JAXRSUtils to be able to run without activation dependency

No TCK regressions:
[javatest.batch] Feb 9, 2022 7:26:09 PM Finished executing all tests, wait for cleanup...
[javatest.batch] Feb 9, 2022 7:26:09 PM Harness done with cleanup from test run.
[javatest.batch] Total time = 4,601s
[javatest.batch] Setup time = 0s
[javatest.batch] Cleanup time = 0s
[javatest.batch] Test results: passed: 2,638; failed: 25

@rmannibucau should be it, right? thank you!

+1, thanks a lot @reta


Transparency

I think changes made on the overflow where breaking scroll and transparency under the Bar Header.
Trying something slightly different here.

Looking


Add instructions on running tests from command line

I pulled the instructions from my own here https://github.com/machikoyasuda/awesome-fam/blob/master/documentation.md

Thank you!


Update DeveloperGuide.md - Use case

Add use case for save contact in the DeveloperGuide, add 2 NFR and 1 glossary.

add on to #32


onboarding description

this is a draft for onboarding guidelines. I added a citation.rst file and made links to the contributing site.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
0

Relevant Lines:
0

💛  - Coveralls

hi @sibirrer the onboarding page looks good as do the contributor guidelines which are super helpful. I made a few minor comments here. Not sure if I did it right.

Thank you very much @aprajita ! Yes, I can see your comments.
Instead of individual comments you could also have started a 'review' and then either stated 'request changes', 'approve' or 'comment'. Some comments are based on older code (or that I have not pushed before). I go through them and make the edits.

@aprajita I tried to make your requested changes. Can you approve the pull request (you should be able to do so). If you want, you can also merge it :) Thank you!


shrish.luitel

Seems good for now! Now we can all trace the code to see how we can properly integrate, as program still functions, but needs to update the friends list!


Fix 'ERR_STREAM_WRITE_AFTER_END' error in proxy

In my project when using the CRA proxy configuration my team has started to hit transient ERR_STREAM_WRITE_AFTER_END errors that crash the dev server. This would result in an stack trace like the following:
[wds] Proxy error: Could not proxy request /api/graphql from localhost:3000 to http://localhost:8080/.
[wds] See https://nodejs.org/api/errors.html#errors_common_system_errors for more information (ECONNRESET).
[wds]
[wds] events.js:377
[wds]       throw er; // Unhandled 'error' event
[wds]       ^
[wds]
[wds] Error [ERR_STREAM_WRITE_AFTER_END]: write after end
[wds]     at new NodeError (internal/errors.js:322:7)
[wds]     at writeAfterEnd (_http_outgoing.js:694:15)
[wds]     at ServerResponse.end (_http_outgoing.js:815:7)
[wds]     at ServerResponse.end (project_root/node_modules/compression/index.js:107:21)
[wds]     at ProxyServer.<anonymous> (project_root/node_modules/react-dev-utils/WebpackDevServerUtils.js:288:9)
[wds]     at ProxyServer.emit (project_root/http-proxy/node_modules/eventemitter3/index.js:210:27)
[wds]     at ClientRequest.proxyError (project_root/node_modules/http-proxy/lib/http-proxy/passes/web-incoming.js:165:18)
[wds]     at ClientRequest.emit (events.js:400:28)
[wds]     at TLSSocket.socketErrorListener (_http_client.js:475:9)
[wds]     at TLSSocket.emit (events.js:400:28)
[wds] Emitted 'error' event on ServerResponse instance at:
[wds]     at writeAfterEndNT (_http_outgoing.js:753:7)
[wds]     at processTicksAndRejections (internal/process/task_queues.js:83:21) {
[wds]   code: 'ERR_STREAM_WRITE_AFTER_END'
[wds] }

I've not been able to determine what is ending the request before it gets to the 'onError' function (it seems to correspond with making changes that trigger a reload at the same time as a network error), but I've confirmed that reproducing the CRA proxy using setupProxy.js with this change resolves the crash.

Hello, any news about how to fix this issues ?


call within the loop

optimize call within the loop

Can one of the admins verify this patch?

@tensorflow-jenkins test this please

Jenkins, test this please.


Question regarding Version One Collector

We're trying to deploy an instance of the version one collector with Docker, so on container creation the versionone-properties-builder.sh is applying properties for the collector jar. I noticed that many of the other properties builder scripts are applying a CRON setting
# from multiple files...
jenkins.cron=${JENKINS_CRON:-0 0/5 * * * *}
sonar.cron=${SONAR_CRON:-0 0/5 * * * *}
subversion.cron=${SUBVERSION_CRON:-0 0/5 * * * *}

However, the versionone builder script has no such property being set. Is this intentional? Am I missing something?

Closed.


feat: individual reward bands per denom

Description
closes: #95

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report

Merging #98 (61a16b8) into main (7513db9) will decrease coverage by 0.13%.
The diff coverage is 13.40%.

:exclamation: Current head 61a16b8 differs from pull request most recent head 25bb6c0. Consider uploading reports for the commit 25bb6c0 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #98      +/-   ##
==========================================
- Coverage   17.11%   16.98%   -0.13%
==========================================
  Files          40       41       +1
  Lines       10658    10901     +243
==========================================
+ Hits         1824     1852      +28
- Misses       8746     8958     +212
- Partials       88       91       +3

Impacted Files
Coverage Δ

x/oracle/keeper/params.go
64.28% <0.00%> (ø)

x/oracle/types/denom.go
72.22% <0.00%> (-17.44%)
:arrow_down:

x/oracle/types/reward_band.go
0.00% <0.00%> (ø)

x/oracle/types/oracle.pb.go
0.49% <0.48%> (+<0.01%)
:arrow_up:

x/oracle/abci.go
77.77% <76.92%> (-0.80%)
:arrow_down:

x/oracle/types/params.go
81.72% <81.25%> (-0.50%)
:arrow_down:

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


Update Dockerfile for ARM build

Update Dockerfile for ARM build
Adding these simple packages to Alpine allows to build k8dash on ARM machines.
Container image was successfully built and deployed on a K8S cluster based on Raspberry Pi 4.

After https://github.com/skooner-k8s/skooner/issues/278, we no longer need python to build node-sass and the Dockerfile on master builds just fine on Raspberry Pi 4.


Can I set a global proxy? Openai is completely inaccessible in China

use apiBaseUrl

use apiBaseUrl

Could you elaborate a bit more? If I have a local http proxy server, how can changing apiBaseUrl help with the situation?


lxc: fix glibc 2.25 incompatibility

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Pushed to master (0eefe9bc629388f60eaad99d0841cf1aae8592a2). Thanks!


Bastion: Primary Fire Rate of Fire

Created by: DpsDoomMain
In overwatch 1 bastions rate of fire was 8 bullets per second and now it’s 5 the way I think you could have his fire rate be increased is by if he’s looking at a target if does damage every 0.125 seconds considering he’s hitscan I don’t know you’ll do about headshots though

moved from ow1_emulator_backup#650

Created by: MaxwellJung
see MaxwellJung/ow1_emulator#652


Use global monorepo root as entry for test paths in a monorepo context

Previously, the ABQ jest extension would use the relative project path
as the root of a test file path in determining test identity. However,
in a monorepo context this an lead to duplicate test IDs. This patch
changes the logic to use the monorepo root, where jest is invoked.

Yeah, not sure why it happens but it shouldn't be material.


Patch up version 0.2.8 to make it behave like 0.2.9

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Apparently there are troubles releasing the wheel on windows:
https://github.com/chrisjbillington/desktop-app/pull/16

merging. If people with ppc computers need this package, they can ask for it to be rebuilt.

@conda-forge-admin please rerender


all images disappeared on debian package upgrade

Platform is Debian 9 on amd64, docker ce package grabbed from the repository on https://download.docker.com/linux
Upgrading docker-ce:amd64 from version 18.03.0~ce-0~debian to 5:18.09.0~3-0~debian-stretch did not report any errors, but all running and inactive containers are not shown by "docker ps" . "docker images" doesn't list any images, either. The data-root directory still contains 155GByte, so this is surely not as expected.
docker info shows
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 18.09.0
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: c4446665cb9c30056f4998ed953e6d4ff22c7c39
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: fec3683
Security Options:
 seccomp
  Profile: default
 userns
Kernel Version: 4.9.0-4-amd64
Operating System: Debian GNU/Linux 9 (stretch)
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 31.37GiB
Name: srvl043.ac.aixigo.de
ID: LTEW:JVYN:VPQA:KXL3:AHDO:KLZM:ETDA:2BSW:EUEB:GT3O:4GXZ:RSNC
Docker Root Dir: /export/docker-data/1017504.1017504
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false
Product License: Community Engine

The daemon.json file wasn't touched:
{
    "data-root": "/export/docker-data",
    "storage-driver": "overlay2",
    "bip": "<IP_ADDRESS>/16",
    "userns-remap": "default"
}

/var/lib/docker does not exist.

same isssue with me

This is the wrong repository report this issue in. Please open an issue in https://github.com/moby/moby/


Replace latest tag with centos7 for onprem assisted installer postgres image

The latest tag was removed which will cause deployments to fail
See: https://quay.io/repository/centos7/postgresql-12-centos7?tab=history
Test-Hints: assisted

@fredericlepied Thanks I was trying to find what the hint should be :)

@fredericlepied Thanks I was trying to find what the hint should be :)

For the record, you have them here: https://docs.distributed-ci.io/dci-openshift-agent/docs/development/#hints

recheck

It was worth a go :)
It seems to have setup assisted installer so I suspect its a random failure.

Build succeeded. https://softwarefactory-project.io/zuul/t/local/buildset/e3581c2c4cc94e2a997ec2a44d078031
✔ dci-rpm-build-el8  SUCCESS in 3m 29s ✔ dci-rpm-build-el9  SUCCESS in 3m 52s

It was worth a go :)
It seems to have setup assisted installer so I suspect its a random failure.

to restest, you just need to restart the "DCI / Maybe Schedule a DCI Job (pull_request) " job.

@fredericlepied Am I OK to merge this? It says I can now just wanted to double check :)

@fredericlepied Am I OK to merge this? It says I can now just wanted to double check :)

sure :-) no need to ask me ;-)


[Cosmos DB] Adds support to create containers with client encryption policy.

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Cosmos DB

Can you add test for the new parameter?

As I have mentioned in the PR description. Since we cannot support Client Encryption Key creation CLI command in Az Cli I have manually tested the command. The reason why it cannot be supported is because the Client Encryption Key creation process requires an encryption library which currently does not have python support. We currently support it in SDK and PowerShell Cmdlets since both have .NET support and the library is available only in C# .NET and Java.


training on coco

Has anyone tried to train on coco? I can't the AP(0.23) from the paper, is there anything special should be changed when dataset is coco?

We are working to get training on coco working right now, you can see our changes on the COCO branch.  We hope to merge these changes into master soon, once we have confirmed expected results from the paper

@ellisbrown hi~could you please show your training log with COCO? (loss with iterations, how much time, final evaluation results...)


AI ChooseRandomSpellFromList - range, has LOS and slots issues

In Orc Cave of IWD there is Orc Shaman, AI of whos is using this ChooseRandomSpellFromList way of determining of spell selection.
What I have seen in my playthroughs:

Shaman would target Hold Person onto PC even if Shaman is not visible due to FoW on the screen. Range in the spell allows that but the Game visibility - not sure, open for discussion.
Shaman would target Hold Person onto PC even if Shaman does not have Line of Sight. That should not be possible.
See Spell Aim \ Target: "You must be able to see or touch the target, and you must specifically choose that target." PHB p 175.
Shaman would use Sound Burst even if Shaman is way too far to be within a range of the spell. I saw same thing in ToEE.
Shaman would use Sound Burst several times although Proto specify the spell only once.

Can you verify his script doesn't replenish his memorized spells?

BTW just wanted to note that it's easy to add the check, but to truly fix this the AI must be able to approach just enough to cast the spell, and ideally also judge whether it should do it in the first place.

Sure it's obvious change, but it could potentially affect ToEE module. That's why I have not proposed solution. Just informed.
Moreover initial encounter in Orc Caves alerts EVRYBODY in the cave and there is continuous fight with 20+ orcs, a Shaman etc. I need to confirm such behavior in the vanilla IWD first before saying if it is design error. Right now it is unplayable.
The best fix would be to disable ChooseRandomSpellFromList as I do in zmod modules and do spell cast AI manually, where I check for all of these requirements. Not sure about this meddling at the moment.

They should not alert everyone in Orc Cave, see this: https://youtu.be/FDx90D9TzME?t=1041

They should not alert everyone in Orc Cave, see this ( time: 17:22): https://youtu.be/FDx90D9TzME?t=1041

Are you sure this is a Temple+ issue?
I think the Co8 guys purposely changed their positioning to trigger each other. I believe this is not the original layout:

I would say it's pretty close to vanilla:

I still see your point Sitra. Open question is does it work same as in vanilla ToEE...

In vanilla the groups have well defined separation: the first 3 is group 1, group 2 is the next 4 orcs, and only then you get the big chamber with the shaman. In the TC you can see there's potentially a continuous connection between all these groups.
Having said that, it is true that Temple+ allows to alert AI allies at a big distance when there is line of sight, which can chain trigger the main chamber even at vanilla IWD distances. I just tested what happens when removing the code that pulls in allies, there are indeed much fewer combatants. I'll have to think about what to do with that.

I thought you moved that part to Python

I moved ConsiderTarget to python, but not Subturn (see Subturn in combat.cpp) which also has code for adding combatants (originally just around the PCs, but I adapted it to also add AIs).
BTW, I looked at the history of that code. Apparently it started out at range = 12 tiles, which is more or less the fog of war distance I think, and then it got changed to 19 and finally 24 (current value). That's indeed quite a long range. Unfortunately I didn't document why, but I suppose it's due to testing some encounters and seeing AIs not recruiting their friends in open ground. The classic example is the Moathouse brigands - in vanilla ToEE you could usually pick them off one by one.
However even with 12, and the positioning I posted above, the main chamber will be triggered. If the Orcs patrol a little it might not however (e.g. the first group is supposed to approach you, so they should break off from the 2nd group at least).

Please consider moving that part to Python, and not rushing fixing that in cpp. That is crucial for new modules including IWD2.

Can you split this to multiple issues?

LOS issue: I've successfully added LOS checks to cast_fireball and cast_area.
But now I remember why I was reluctant to add that: the AI is not smart enough to tweak the AoE center so that it hits around the corner and such. Todo..

Oh, I did see that the Area picker has a flag for bypassing LOS check. But that'll also go through walls where it shouldn't...
I should probably prepare a coarse blockage grid for calculating this sort of stuff. ToEE's fine grained grid is visually nice, but it makes these sorts of calculations needlessly complex...

Can you verify his script doesn't replenish his memorized spells?

Not confirmed - it was due to two Shamans. I withdraw the claim, it works fine.


Strange path choice for engines-1.1/ on Windows

On Windows, binaries including shared dynamic object libraries live in bin/, while the lib/ directory
consists only of build-time artifacts, including non-executable link libraries.
In the Windows master build, lib/ includes;
engines-1_1   libssl.lib  libcrypto.lib
while bin/ includes
c_rehash.pl  libcrypto-1_1.dll  libssl-1_1.dll  openssl.exe  libcrypto-1_1.pdb  libssl-1_1.pdb  openssl.pdb
I would suggest Windows conventions suggest deploying to bin/engines-1_1/ and not lib/engines-1_1/
capi.dll  padlock.dll  capi.pdb  padlock.pdb

Well, errr, not quite.  The convention is to have shared libraries in the same spot as the programs that are linked with them, while there is no real convention for the location of dynamically loadable modules (which the engines are).
On Unix, it's not unusual to have dynamically loadable modules in a subdirectory of lib, and since all this bin, lib and so on business isn't really a Windows convention, but rather a direct copy of Unix layouts, I think it's appropriate to have engines in the same spot on both.


Basic authentication prompt

🐛 Bug Report
When a user is logged out (with cleared browser cache) and goes to the index, it is prompted both with basic authentication dialog from the browser before the redirect to the login screen from the app.

To Reproduce
Logout, clear the browser cache and navigate to the home.
Expected behavior
Only the app login screen is presented.
Your Environment

os: Mac
browser: chrome, firefox, safari

I would like to have a go at this.

Yours!

@fox1t I tried my best, but I cannot reproduce the issue. I'm using the latest version of Chrome on Mac. I logged into the local version on localhost:3000 using the default user 'username'. I then clicked 'logout', cleared my browser's cache and cookies, and then navigated to localhost:3000. I was immediately redirected to the login page without seeing the browser authentication pop up. Did I miss any steps.

I don't think so. Can you try a different browser? Have you any chance to install Firefox?

Yes I tested in Firefox and it also worked correctly. Could it be that this is caused by your computer being configured in a certain way? For example is your account lacking admin privileges? Might you have certain extra security settings enabled that are causing the system to show the extra dialogue? Are you able to reproduce this issue on other computers?

This issue was present some time ago and then suddenly disappeared. Now it is back but it seems only for me :)
Nothing special on my Macbook, by the way. I'll leave this issue open for a couple of days. After that period of time I am going to close it if no one reports it again.

@fox1t Just to make sure, I would like to test on staging.hospitalrun.io. How can I get the login credentials?

username: username
password: password

There seems to be an issue with authentication:

@fox1t So I actually was able to reproduce this issue by changing the api url in shared/config/pouchdb.ts from ${process.env.REACT_APP_HOSPITALRUN_API}/hospitalrun to https://couchdb.run.hospital so I'm connecting to the staging database from my local machine. When I do this, I see the browser pop up appear repeatedly. However, the issue I'm seeing is maybe slightly different than the one you reported. The pop up keeps appearing even after I'm logged in and when I click cancel, it goes away, but I see the following error in my network tab: {"error":"unauthorized","reason":"You are not a server admin."}

@blestab, it is safe to assume that it nginx that is adding a hader.
@tehKapa can you double check this?

Yes, I also have a similar problem locally. I had to specify https://couchdb.run.hospital**/hospitalrun** as env var


fix: Don't create PSP for kubernetes >= 1.25

Pod security policies were deprecated in k8s 1.21 and removed in 1.25.
This is a fix for the helm install error for clusters where PSPs are not present.

Closing. Will reopen again dev branch.


Added freesmsalert handler

@meatheadmike Could you also please make a PR against sensu-plugins-sms as well.
Thanks!

Sure thing. Should I just PR the same 3 files, or is there something
special I need to do with the separate release?
On Mar 19, 2015 7:24 AM, "Matt Jones"<EMAIL_ADDRESS>wrote:

@meatheadmike https://github.com/meatheadmike Could you also please
make a PR against sensu-plugins-sms
https://github.com/sensu-plugins/sensu-plugins-sms as well.
Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/sensu/sensu-community-plugins/pull/1069#issuecomment-83603421
.

It is a new repo, so add all your stuff in.  The only thing to watch for is the linting much tighter in the new org.
Thanks

So am I forking off of sensu-plugins/sensu-plugin and then PRing to
sensu-plugins-sms? I not clear on the new framework. Are there docs you can
point me to?
On Mar 19, 2015 7:48 AM, "Matt Jones"<EMAIL_ADDRESS>wrote:

It is a new repo, so add all your stuff in. The only thing to watch for is
the linting much tighter in the new org.
Thanks
—
Reply to this email directly or view it on GitHub
https://github.com/sensu/sensu-community-plugins/pull/1069#issuecomment-83613753
.

@meatheadmike
They are in the works, I created a sensu-plugins-sms repo, just fork and pr it like it was the community-plugins repo.  Each 'directory' and then some now has its own repo and will be built into a gem and released to ruby gems.