Change header in results page for Lets Get Set Whitelabel

Needs to eliminate reference to tax credits
suggested (please improve as you see fit): “XX programs with an estimated value of $YYYY monthly in cash or reduced expenses for you to consider.”
Subheader with path for additional info (suggested only):
“This presumed eligibility was calculated based on your 2023 tax filing.  You can see if you qualify for XX additional benefits by providing additional information here.”

@kbottagaro this is a dupe. I'm closing this


Some broken elements on todays update of Spotify

Seems a few elements broke. Re-ran the script twice to be sure, still broken.

Also, scrolling seems to still be bugged on the playlist bar.

#249

Show "About" window

Your spicetify is outdated and doesn't support theme extension feature. Update it to the latest v2.17.2 release

Ah, i see! Thank you! (now just the stuck scrolling is the only issue remaining on this theme)

This is a reminder to y'all: Remember to close the issues once they're resolved. This way we can keep reputation of our theme and have less clutter regarding open issues.

@windowz414 😊 true!


Add US bolt sizes (No 6, No 8, etc.) to the bolt list

This doesn't sound like it'd be a problem. I just checked out the BOLTS library (from which we source the data), and while they appear to support imperial nuts, there doesn't appear to be data for bolts.
Would adding just the nuts help you at all? It seems fairly straightforward, while adding bolts might require contributing to the BOLTS library.

All additions are helpful! Bolts would be a good long-term addition. Could open an issue over there and get them to add it to the library


CloudException vs HttpStatusCode.NotFound/etc.

Maybe I'm being daft here, but is there a reason why the library throws a CloudException and doesn't just return the associated StatusCode? It seems odd that I would have to encapsulate these calls in try/catch (which is arguably an expensive proposition) when a StatusCode result should be sufficient? Case in point:
using (var client = CloudContext.Clients.CreateWebSiteManagementClient(credentials))
{
    var parameters = new WebSiteGetParameters { PropertiesToInclude = new List<String>() };
    var response = await client.WebSites.GetAsync(webSpace.Name, webSiteName, parameters);
    // I should be able to check against response.StatusCode and not wrap this
    // in a try...catch
}

REST APIs are supposed to return 404, 200, etc. codes. It looks like you purposely throw an exception when anything but an OK response comes back, and I'd just like to know if there's a reason for it?

I agree, was looking to open this as issue as well today, but found it was already here.

It's as if it's generated like that, but I can't find any source for this Hyak generator that seems to be in use.

@Brad-Christie please open a new issue, if the problem still exists.


[Feature request] Only list recognized config options under Effective configuration

When making issue https://github.com/doitsujin/dxvk/issues/3767 i had missed that it was a simple spelling mistake since i just skimmed that the correct config was applied.
It would be a nice tweak to only list recognized options below Effective configuration: like so.
info:  Found built-in config:
info:    d3d9.maxFrameRate = 60
info:    d3d9.frogFilter = True
info:  Effective configuration:
info:    d3d9.maxFrameRate = 60

One could also expand on to that and explicitly point out any unrecognized entries.
info:  Found built-in config:
info:    d3d9.maxFrameRate = 60
info:    d3d9.frogFilter = True
info:  Unknown config options:
info:    d3d9.frogFilter = True
info:  Effective configuration:
info:    d3d9.maxFrameRate = 60

As discussed on DIscord, the problem here is that the config system doesn't have a centralized place where all the options are defined.
Honestly I don't think that one spelling error was a big deal, if in doubt you could just copy the actual names from the respective *_options.cpp or the sample dxvk.conf, but we also should really have caught this in the review.

The error was just an example that made me think about it in regards to my own testing and other peoples configs.
Personally i would still consider it a nice to have but it also isn't the biggest deal especially if the work involved isn't minor, so closing as rejected (which is fine).


Add support for SG rules

When exporting a minimal config, would it be possible to remove the default ingress rule:
  # List of IPv4 CIDR ranges to use on all ingress rules
  # type: list(string)
  ingress_cidr_blocks = ["<IP_ADDRESS>/0"]

Here is a Cloudcraft JSON respresentation, for an example export:
{"nodes":[{"type":"ec2","id":"e39584f4-208a-472d-a99d-7e963faa7867","mapPos":[5,5],"region":"us-east-1","transparent":false,"platform":"linux","instanceType":"m5","instanceSize":"24xlarge","color":{"isometric":"#ececed","2d":"#d86613"},"accentColor":{"isometric":"#4286c5","2d":"#d86613"},"billingOptions":{"type":"ri","utilization":1,"leaseContractLength":36,"purchaseOption":"All Upfront","offeringClass":"standard"}},{"type":"elb","id":"c2d0d77d-4627-470b-b1c3-553eac59d141","mapPos":[5,11],"region":"us-east-1","color":{"isometric":"#ececed","2d":"#693cc5"},"accentColor":{"isometric":"#4286c5","2d":"#ffffff"},"elbType":"classic","lcu":1,"dataGb":10},{"type":"vpc","region":"us-east-1","id":"2a0f9c73-5830-4ff5-8fda-8071b01e3921","nodes":["c2d0d77d-4627-470b-b1c3-553eac59d141","e39584f4-208a-472d-a99d-7e963faa7867","19d6b0a1-21b5-463f-9ddc-775c71a0a554","5346d5dc-a9e8-4417-97fc-a7d26c4e896c"],"color":{"isometric":"#9c27b0","2d":"#9c27b0"},"name":"vpc-web","peeringConnections":[],"padding":1.5,"shape":"rectangular"},{"type":"sg","region":"us-east-1","id":"19d6b0a1-21b5-463f-9ddc-775c71a0a554","nodes":["c2d0d77d-4627-470b-b1c3-553eac59d141"],"color":{"isometric":"#9c27b0","2d":"#9c27b0"},"name":"web-lb","inboundRules":[],"outboundRules":[],"padding":1.5,"shape":"dynamic"},{"type":"sg","region":"us-east-1","id":"5346d5dc-a9e8-4417-97fc-a7d26c4e896c","nodes":["e39584f4-208a-472d-a99d-7e963faa7867"],"color":{"isometric":"#03a9f4","2d":"#03a9f4"},"name":"web-ec2","inboundRules":[{"portRange":"80","protocol":"tcp","target":"19d6b0a1-21b5-463f-9ddc-775c71a0a554","targetType":"sg","description":"","hidden":false}],"outboundRules":[],"padding":1.5,"shape":"dynamic"}],"edges":[],"boundingRect":{"x":2,"y":2,"width":7,"height":13}}


added btc component on profile preferences

@Alan-AC7

I think the  needs a key prop since it is in an array

also, can you introduce what is this Bitcoin Connect trying to do?

also, can you introduce what is this Bitcoin Connect trying to do?

Includes web components for connecting to Lightning wallets.
Here is the repo of the component: https://github.com/getAlby/bitcoin-connect.git

@digi-monkey  Can we add a githook with husky to compile react before deploy to check for these errors?
Otherwise we can see them lol

@Alan-AC7
I think the <BitcoinButton /> needs a key prop since it is in an array

also, can you introduce what is this Bitcoin Connect trying to do?

Includes button and Modal to connect Lightning wallets.
Here is the repo of the component: https://github.com/getAlby/bitcoin-connect.git

sounds cool, so this can enable users to zap in their mobile phone?

@digi-monkey Can we add a githook with husky to compile react before deploy to check for these errors? Otherwise we can see them lol

@Alan-AC7
I think the <BitcoinButton /> needs a key prop since it is in an array

yea I think we need a CI that can run for every PR. I am not sure if we should do it in the .husky like every pre-commit we should run yarn build, that might be inconvinent. I am thinking something like github action that can be trigger for every PRs

Yes, with BitcoinConnect users of Alby, Mutiny or Umbrel wallets can zap on mobile in the PWA.

https://github.com/digi-monkey/flycat-web/assets/30165568/d7372e88-2b50-4bfa-8fc2-533fe82c5793


[Dash-Sonic] Introduce route group, pa validation tables

Add Route group table for grouping routes and binding to an ENI
Introduce PA validation table for special validation for certain scenarios

Currently the route table is modified w/routes belonging to an ENI (per ENI).
Controller calls each route update w/ENI key.
Group table & binding allows for atomic binding for an ENI (instead of updating 1 by 1)
(Not a subset of ENI routes).
Cx update their routes in the route table, and expect all or nothing to work.  Adding 1 by 1 we can end up in a non-complete/inconsistent goal state.
What if libsai has no resources to support an atomic update?
The controller will need to wait to determine whether this is a successful operation or not.
If unsuccessful, old route table will persist.

Are all comments resolved?  IF Y, I can merge :)

hi @r12f , @kperumalbfn , and @pranjal-git - would you mind reviewing for Prince please?
TY...


Switch to system fonts

Here's a nice post on the subject — Shipping system fonts to GitHub.com. Medium (System shock) and Booking.com (Implementing system fonts on Booking.com — A lesson learned) both have shared their experience as well. In fact, if you're up to know a whole lot more on the matter ― head over to A List Apart's Webfonts on the Prairie by Richard Fink.
A nice explanation of the term 'system fonts' can also be found in Craig Hockenberry's article I Left My System Fonts in San Francisco (make sure to also read the follow-up post as it has recent developments on the matter).
Basically, judging from my tests, Segoe UI will look almost identical to Open Sans, so switching to system fonts will save 8 requests (~100KB). Specific CSS rule can be obtained from the example shared by the guys from WordPress in Native Fonts in 4.6 (they also tested it extensively and they do have a large enough clients base to be a reliable source).

Given that I've switched to the system fonts already it might also be a good idea to also replace Semantic UI with Spectre.css — CSS framework that's smaller, provides all necessary features, is based on system fonts, etc.


Automagically detect latest P2Pool tag and use it

This patch clones the original P2Pool repository and then finds the latest tag (by date) and selects it checking out the submodules before building.
Latestes version had a flaw when the latest tag was the same commit as head and main. Now this issue is resolved and should build in any circumnstances.

@sethforprivacy I will look in some way to trigger build when P2Pool repository gets a new tag. The first approach would be to create a cron that checks it every day or hour and that would trigger a build.
Regarding the tip, here is my XMR address in case you haven't change your mind.
82dLbYNVgFPDMVbo5VRegwaozDnyeGKCVcLFo6BnKwxz2EcWDNKquisahetXSwcrLtRFU2JVj5h8cUVc3coXx5E12dzHUUV

Same issue here, let me setup a new action to test PRs:
buildx failed with: ERROR: invalid tag "ghcr.io/sethforprivacy/p2pool:$(git log --tags --simplify-by-decoration --pretty": invalid reference format

I'd prefer to keep that tag generation if at all possible, as I prefer to allow users to pin direct p2pool versions if they desire.

I think I have an idea for a change in Actions that would resolve this, testing now.

Ok, it built but broke the next action while getting the tag

Here is the problem, didn´t noticed that. If you want I can also change that.

Think I'm 99% of the way there with this commit but still messed something up with syntax :P
https://github.com/sethforprivacy/p2pool-docker/commit/df99368674f20a307c3a072d55b544290654b3c7

@sethforprivacy it won't work because it needs to be run on the P2Pool Git repository and not on this one.

Ahhh... I'll revert again for now then, have to log off for a while and likely won't be back at it till next week sadly.
Thank you for all your help on this, tip incoming!

@sethforprivacy I'll make it work on another PR


Add mega version dump to notebook metadata

Metadata for version dump is included in COMBINE archive. Still having trouble getting comms to work to be able to do this in the notebook.


Adding TyphoonFactoryDefinition to public headers

To test the Carthage built framework you can use this in a Cartfile:
github "akiraspeirs/Typhoon" "fix-public-headers"

I still get the following warnings after adding the framework, but I think they were present before (at least they were at 3.1.8):
<module-includes>:1:1: Umbrella header for module 'Typhoon' does not include header 'OCLogTemplate.h'
<module-includes>:1:1: Umbrella header for module 'Typhoon' does not include header 'TyphoonInstancePostProcessor.h'

I've checked that it builds correctly when included in a new project.

Thanks so much @akiraspeirs ! Tagging releasing 3.2.4

Glad I could help :)


Badge / count in facet with long text are displayed incorrectly

Describe the bug
When a facet value is very long the count badge go outside the facet component
To Reproduce
Steps to reproduce the behavior:

Do this https://demo7.dspace.org/search?query=&spc.page=1

4Science can work on that, estimation is 3-4 hrs

Thanks @abollini for reporting this & I can reproduce it in Chrome.  I'll assign to @atarix83 and add the estimate.


Purview error when scanning Azure File

I setup Purview with private endpoint as documented at the link below. All setup seems to be working with private Endpoints for account, portal and injestion. Also, setup a Self Hosted Runtime.
https://docs.microsoft.com/en-us/azure/purview/concept-best-practices-network#option-2-use-private-endpoints
Now, I am trying to run a Purview Scan from self managed runtime to Azure File and it is consistently failing. Unfortunately, there is not much help (logs) from the platform (Purview) other than a correlation id!
Both the Blob and File share are in the same storage account. I can get to scan the blob successfully using Service Principal.
As of now, you can't use anything but storage account key as credential to scan Azure File! Registration is able to discover the folders and files in Azure File share. However, I haven't have a success to scan Azure File. Any reason why Purview scanner is failing? Also, any clue where to look for debugging logs in Purview platform?
Related post at Stackoverflow

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

ID: 2aaa823b-dd5a-39f2-760b-1ba15e81554c
Version Independent ID: bd72379d-f2ff-7795-0a74-bebd66167713
Content: Connect to and manage Azure Files - Microsoft Purview
Content Source: articles/purview/register-scan-azure-files-storage-source.md
Service: purview
Sub-service: purview-data-map
GitHub Login: @viseshag
Microsoft Alias: viseshag

Spelling corrections

@aspnet4you
Thank you for your feedback . We will investigate and update the thread.

Same issue with scanning AWS S3. I have the proper IAM role with policy and Purview can read the metadata validated by Test Connection. Unfortunately, S3 scan always fails without much details in the error message!
Also, it takes way long time to scan Kilobytes and Megabytes of S3 buckets. Is Purview is really ready for prime time?

@aspnet4you  Since this issue is not related directly to the doc, I would recommend you to create a thread on the forums - Microsoft Q&A or Stack Overflow
Once you post your issue on forums, it will have visibility across the community which is a better suited audience for such types of issues.


Fix cumulative hourly reactive export energy entity name

Fixes #11

I might have missed something, but AFAICS, only one line needs to be changed.


Synthesis failed for Google.Cloud.ServiceDirectory.V1Beta1

Hello! Autosynth couldn't regenerate Google.Cloud.ServiceDirectory.V1Beta1. :broken_heart:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the Google.Cloud.ServiceDirectory.V1Beta1 API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-19 22:45:56,624 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/Google.Cloud.ServiceDirectory.V1Beta1
2021-03-19 22:45:57,173 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2021-03-19 22:45:57,177 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2021-03-19 22:45:57,180 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2021-03-19 22:45:57,183 autosynth [DEBUG] > Running: git config push.default simple
2021-03-19 22:45:57,187 autosynth [DEBUG] > Running: git branch -f autosynth-Google.Cloud.ServiceDirectory.V1Beta1
2021-03-19 22:45:57,190 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.ServiceDirectory.V1Beta1
Switched to branch 'autosynth-Google.Cloud.ServiceDirectory.V1Beta1'
2021-03-19 22:45:57,396 autosynth [DEBUG] > Running: git rev-parse --show-toplevel
2021-03-19 22:45:57,403 autosynth [DEBUG] > Running: git log -1 --pretty=%H
2021-03-19 22:45:57,407 autosynth [DEBUG] > Running: git remote get-url origin
2021-03-19 22:45:57,441 synthtool [ERROR] > Failed executing git checkout master:

error: Your local changes to the following files would be overwritten by checkout:
	google/cloud/dialogflow/v2/answer_record.proto
	google/cloud/dialogflow/v2/conversation.proto
	google/cloud/dialogflow/v2/conversation_profile.proto
	google/cloud/dialogflow/v2/participant.proto
Please commit your changes or stash them before you switch branches.
Aborting

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 312, in _inner_main
    git_source.enumerate_versions(sources, pathlib.Path(temp_dir))
  File "/tmpfs/src/github/synthtool/autosynth/git_source.py", line 202, in enumerate_versions
    source_versions = enumerate_versions_for_source(git_source, temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/git_source.py", line 166, in enumerate_versions_for_source
    local_repo_dir = str(synthtool_git.clone(remote))
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 85, in clone
    shell.run(["git", "checkout", "master"], cwd=str(dest), check=True)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'checkout', 'master']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


graphics: Strange image rendered before calling ebiten.Run

glfw.Window's SetSize seems to break the images created before.


docs: Update RFD-0 with specifics on publishing RFDs

Description

Update RFD-0 with specifics on publishing RFDs.
Motivation and Context

There is no clear wording on when RFDs enter in effect.
How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code has security implications.
[ ] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

Closing and re-opening to give EasyCLA a chance to wake up...


Clear old checkout components from dev-com-21 and check if IMPEX works correctly

Do after #2322

Clear dev-com-21 from any checkout leftovers
import IMPEX scipt from #2157
sync staged catalog
make sure checkout works correctly

Works good


Replace setup.py by pyproject.toml

That’s probably up to the build backend

I think this is now ready. @Natim, is this OK for you?


Convert avro to protobuf on the server

This updates the protobuf work done previously with the latest changes from master.

Hi @irene-lshift would you please make this PR against the protobuf topic branch? We would like to be able to accept your changes without changing the state of master.

Looks great @irene-lshift, thanks! I have some very minor comments above.
I agree with @david4096, let's remake this PR against the protobuf branch so we can merge it quickly without worrying about getting a wider consensus. My view would be that we should move over to this code ASAP though.

Yes we can make this PR against the protobuf brunch. It just might be a bit harder to review due to all the new code that's been merged from master.

The change I made to the requirements.txt / dev-requirements.txt seems to have made Travis unhappy (even though passing locally), I'm taking a look at it.

Thanks @irene-lshift, this is great. I agree that it will be harder to review on the protobuf branch, so it was very helpful to make this PR. I'm happy to merge this into the protobuf branch now.
@david4096, @macieksmuga, @dcolligan, @diekhans, @kozbo, what do you think? There's some work to be done to bring this up to release level --- performance is poor (but it's pretty obvious why, and it should be easy to fix), and there's some hard questions to answer about installation, given that proto3 isn't on pypi yet, as far as I know.  The sooner we deal with these problems the better, and having the code in master will avoid more painful merges.

@jeromekelleher Re; protobuf https://pypi.python.org/pypi/protobuf/3.0.0b2

The obvious performance issue I noticed is the call to re-generate the full response JSON on every call to addValue in the SearchResponseBuilder, so that its size can be compared against _maxResponseLength. I'd put a high priority on optimizing this bit, as it has a serious effect on search requests with larger page sizes.

@jeromekelleher I agree that #1243 should be our top priority. We saw the performance issues yesterday when @david4096 ran some quick tests but I haven't seen a show stopper yet. @macieksmuga found a likely culprit as mentioned earlier. Is that the same "obvious" reason that you saw? Anyway, I don't see any reason not to merge and then optimize, as far as performance goes. I will leave the more detailed code review to those who are more qualified.

@kozbo agree. Let's merge first into the ga4gh/server:protobuf branch, then optimize there.

I've been able to confirm that the compliance tests are passing. The failure is a known unimplemented feature.

The requirements.txt changes also worked for me. Great!

@macieksmuga, yes this is exactly the problem. Converting to JSON for every element added is hugely expensive. We'll be able to sort this out in no time, I'm sure.
@david4096, thanks this is fantastic news that protobuf is in pypi! Given this, I think we should be able to get this code into a releasable state in a matter of days.
So, it looks like we have consensus then? Let's merge this into the protobuf branch as soon as the final few wrinkles have been ironed out in this PR, fix the performance bottleneck (in a follow up PR), and then merge to master. Hopefully we can merge this into the protobuf branch tomorrow.

@irene-lshift, we definitely need to be at the latest protobuf version. The older ListValue JSON was incorrect in this version of protobuf. We need to fix any tests that are failing under this version.

@irene-lshift OK, I see the problem here. We just need to rerun the scripts/build_test_data.py. This has the older JSON embedded inside in the DB, which is causing failures. I've just run it there and it all works fine.

Re performance, replacing
return len(toJson(self._protoObject))

with
return self._protoObject.ByteSize()

dramatically improves things, and brings us back to where we were before more-or-less (I think). We'll need to rephrase the documentation a bit, but this gives us the same functionality (i.e., prevent memory starvation DOS attacks, provide a lever to approximately manage latency when the client doesn't provide a page size), and is cheap. It's certainly good enough to keep us going for now.
Anyway, this doesn't directly reflect on the PR, I just wanted to see what the effect of this change would be.

Thanks @jeromekelleher, I updated to the latest version of protobuf and reran scripts/build_test_data.py

Great, thanks @irene-lshift. How does porting SearchResponseBuilderTest look? I think we're ready to merge into the protobuf branch after this is done.
 There's no need to go through all of them, just the last group back to @peterolph's pep8 fix. These should squash cleanly. It's not worth the bother of squashing older commits.

I tried to find out why was this file originally deleted and found this earlier conversation: https://github.com/ga4gh/server/pull/799#discussion_r48847207
It seems that this used to test the integrity of our custom serialisation / deserialisation, but protobuf guarantees this?

Yes that's true @irene-lshift, most of the tests just check the integrity of the conversion process. However, I missed the SearchResponseBuilderTest when looking at it the first time, which tests the process of building response objects. It would be great if we could port this test to using protobuf. Apologies for going back on what I said in #790.
Given the notes about about getting rid of  getTypicalInstance(class_) and getRandomInstance I think it should be a quick job. If it is a lot of work, we can add an issue on it, and port the test later.

We restored SearchResponseBuilderTest, how does this look?

It looks great, thanks @irene-lshift!
+1 to merge to the protobuf branch.
I realise now that I got confused, and that PR #1242 has different contents to this one. Just so I'm clear: if we merge #1242, then we'll be able to merge this PR onto the protobuf branch? Can we just merge the contents of this PR onto the protobuf branch, or do we need this two-step process?

Nope, looks like I got confused about being confused! Ignore the last comment. OK, since we're done reviewing this code, I think we can close this PR and move over to #1242. @kozbo, would you mind doing this, if you agree we're ready?

#1243 has been merge so I'm going to close this PR. Thanks to everyone involved, we've nearly completed the Avro purge!


HTTP Error 502.5 - Process Failure after copying ASP.NET Core 1.1 to another machine

I upgraded my ASP.NET Core app from 1.0 to 1.1 following procedures from Official ASP.NET site. The app runs fine on its original location on Windows 10 (upgraded from win 7). But when I copied the app on another machine (Win 7) that also has latest VS2015-Update3 installed and installed NET Core 1.0.1 tools Preview 2 , the app compiles fine but gives the following error: HTTP Error 502.5 - Process Failure
Moreover, the event log shows the following:
Failed to start process with commandline '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\ProjectSystem\VSIISExeLauncher.exe" -p "C:\Program Files\dotnet\dotnet.exe" -a "C:\DotNET2015\ABCTest\src\ABCTest\bin\Debug\netcoreapp1.1\ABCTest.dll" -wd "C:\DotNET2015\ABCTest\src\ABCTest" -wbe Global\Build500340c7-6e16-4a08-b314-ff5fd51b1dcb -lse Global\Launchb628508b-6e25-455f-9afa-6092434506ed', ErrorCode = '0x80004005'.
project.json:
{
  "userSecretsId": "aspnet-ABCTest-6af8ade3-87ff-4468-a9ce-8bb69c696ab8",

  "dependencies": {
    "Microsoft.NETCore.App": {
      "version": "1.1.0",
      "type": "platform"
    },
    "Microsoft.EntityFrameworkCore.SqlServer": "1.1.0",
    "Microsoft.EntityFrameworkCore.Tools": "1.1.0-preview4-final",
    "Microsoft.AspNetCore.Mvc": "1.1.0",
    "Microsoft.AspNetCore.Mvc.Core": "1.1.0",
    "Microsoft.AspNetCore.Server.Kestrel": "1.1.0",
    "Microsoft.EntityFrameworkCore.SqlServer.Design": "1.1.0",
    "Microsoft.AspNetCore.Authentication.Cookies": "1.1.0",
    "Microsoft.AspNetCore.Diagnostics": "1.1.0",
    "Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore": "1.1.0",
    "Microsoft.AspNetCore.Identity": "1.1.0",
    "Microsoft.AspNetCore.Identity.EntityFrameworkCore": "1.1.0",
    "Microsoft.AspNetCore.Razor.Tools": "1.1.0-preview4-final",
    "Microsoft.AspNetCore.Server.IISIntegration": "1.1.0",
    "Microsoft.AspNetCore.Server.IISIntegration.Tools": "1.1.0-preview4-final",
    "Microsoft.AspNetCore.StaticFiles": "1.1.0",
    "Microsoft.Extensions.Configuration.EnvironmentVariables": "1.1.0",
    "Microsoft.Extensions.Configuration.Json": "1.1.0",
    "Microsoft.Extensions.Configuration.UserSecrets": "1.1.0",
    "Microsoft.Extensions.Logging": "1.1.0",
    "Microsoft.Extensions.Logging.Console": "1.1.0",
    "Microsoft.Extensions.Logging.Debug": "1.1.0",
    "Microsoft.Extensions.Options.ConfigurationExtensions": "1.1.0",
    "Microsoft.VisualStudio.Web.BrowserLink.Loader": "14.1.0",
    "Microsoft.VisualStudio.Web.CodeGeneration.Tools": "1.1.0-preview4-final",
    "Microsoft.VisualStudio.Web.CodeGenerators.Mvc": "1.1.0-preview4-final"  },

  "tools": {
    "BundlerMinifier.Core": "2.0.238"
  },

  "frameworks": {
    "netcoreapp1.1": {
      "imports": [
        "dotnet5.6",
        "portable-net45+win8"
      ]
    }
  },

  "buildOptions": {
    "emitEntryPoint": true,
    "preserveCompilationContext": true
  },

  "runtimeOptions": {
    "configProperties": {
      "System.GC.Server": true
    }
  },

  "publishOptions": {
    "include": [
      "wwwroot",
      "Views",
      "Areas/**/Views",
      "appsettings.json",
      "web.config"
    ]
  },

  "scripts": {
    "prepublish": [ "bower install", "dotnet bundle" ],
    "postpublish": [ "dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%" ]
  }
}

You need to instal 1.1 runtime on the other machine. You can install it from here: https://www.microsoft.com/net/download/core (make sure to select Current and not LTS to get 1.1)

@moozzyk Thank you for coming to my rescue. It's working now.


[Improment] Log fatal when compaction memtracker not return zero

Proposed changes
Issue Number: close #xxx

run buildall

run buildall

run buildall


Delete native K3s, did not judge the return value of uninstalling k3s

Autok3s version:
Version: {"gitVersion":"v0.3.0-rc1","gitCommit":"4b82f5e5114e234da010e07e755b532e31c94bc9","gitTreeState":"","buildDate":"2020-12-15T06:16:35Z","goVersion":"go1.13.12","compiler":"gc","platform":"darwin/amd64"}

**Steps to reproduce: **

Use autok3s to start the k3s cluster, and wait for the K3s cluster to start successfully

autok3s create --debug \
    --provider native \
    --name native-1 \
    --ssh-user ubuntu \
    --ssh-key-path ~/.ssh/id_rsa \
    --master-ips <IP_ADDRESS> \
    --worker-ips <IP_ADDRESS>

ssh to <IP_ADDRESS> and <IP_ADDRESS> respectively to delete the corresponding uninstall K3s script

Delete k3s cluster through autok3s

 ksd@Ksd  ~/.autok3s  autok3s delete \
    --provider native \
    --name native-1 -d
[native] are you sure to delete cluster native-1 [y/n]: y
INFO[0001] [native] executing delete cluster logic...
INFO[0002] [native] successfully excuted delete cluster logic

Result:
The k3s uninstall script has been deleted in my k3s environment. Normally, it should report an error and prompt that the deletion of k3s failed.

native provider has been refactored, so this issue is invalid.

I need to verify this issue in the new version after refactoring

native provider has been refactored, so this issue is invalid.


Added quotes to - 'path', 'tx_search', and 'block_search'

PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments

Would it not be better to do this automatically with Mergify? i.e. add the backport-to-v0.38.x, backport-to-v0.37.x, and backport-to-v0.34.x labels to #1015 and Mergify will do this backporting for us automatically.

@thanethomson Yes - absolutely. Let's use mergify.


HandleFuncs can now be Type Methods as well.

http.HandleFunc documentation was not discovered because only
first class functions were traversed when building apib documentation.
Now both first class functions and type methods are traversed.
For example:
    type WidgetController struct {}

// GetTypeWidget retrieves a single Widget
    func (* WidgetController) GetWidget(w, r) { }

Hey @ivaningrooves, I'd love to get your PR merged in. If you don't want to do my requested changes, I can do the changes myself. Would that work better for you?

@adams-sarah This PR seems to be abandoned. Are you planning to address issues mentioned above?


python312Packages.thinc: 8.2.2 -> 8.2.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.thinc is: Library for NLP machine learning
meta.homepage for python312Packages.thinc is: https://github.com/explosion/thinc
meta.changelog for python312Packages.thinc is: https://github.com/explosion/thinc/releases/tag/v8.2.3
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 8.2.3 with grep in /nix/store/s06fhyzwb9pnrfxgfkr1al8yzryscbx4-python3.12-thinc-8.2.3
found 8.2.3 in filename of file in /nix/store/s06fhyzwb9pnrfxgfkr1al8yzryscbx4-python3.12-thinc-8.2.3

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.fastai
python311Packages.spacy
python311Packages.spacy-lookups-data
python311Packages.spacy-transformers
python311Packages.textacy
python311Packages.textnets
python311Packages.thinc
python312Packages.thinc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/s06fhyzwb9pnrfxgfkr1al8yzryscbx4-python3.12-thinc-8.2.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.thinc https://github.com/r-ryantm/nixpkgs/archive/35b4810e62c97fcd54d30db4b81ca7b93170c41c.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/35b4810e62c97fcd54d30db4b81ca7b93170c41c#python312Packages.thinc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s06fhyzwb9pnrfxgfkr1al8yzryscbx4-python3.12-thinc-8.2.3
ls -la /nix/store/s06fhyzwb9pnrfxgfkr1al8yzryscbx4-python3.12-thinc-8.2.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

16 packages built:

python311Packages.fastai
python311Packages.fastai.dist
python311Packages.spacy
python311Packages.spacy-lookups-data
python311Packages.spacy-lookups-data.dist
python311Packages.spacy-transformers
python311Packages.spacy-transformers.dist
python311Packages.spacy.dist
python311Packages.textacy
python311Packages.textacy.dist
python311Packages.textnets
python311Packages.textnets.dist
python311Packages.thinc
python311Packages.thinc.dist
python312Packages.thinc
python312Packages.thinc.dist

Maintainer pings
cc @aborsu for testing.

Already on staging-next.


Add selected items to selectize control when refreshing options

Bugfix: https://github.com/comerc/meteor-autoform-selectize/pull/6
Not fixed bug if multiple is true + isReactiveOptions is true

This works for me but it is a pain in the ass to figure out in the documentation how to get it to work...
I did it this way:
{{> afQuickField name='affiliations' options=affiliations_options type="selectize" multiple=true isReactiveOptions=true label=false }}

Template.mytemplate.helpers({
  affiliations_options: function(){
    var data = Affiliations.find().fetch();
    var affiliates = _.map(data, function(data){return {label: data.name, value: data._id};});
    return affiliates;
  }
});


Add common_name to generated ATC certificate

The tls-vars.yml operations file won't work as written, as it doesn't allow you to specify a common_name.

Error: Config Server failed to generate value for '/bosh-bbl-env-saimaa-2018-07-30t17-54z/concourse/atc_tls' with type 'certificate'. HTTP Code '400', Error: 'At least one subject value, such as common name or organization, must be defined to generate the certificate. Please update and retry your request.

This adds a new external_hostname variable that gets placed in the common name.
There is a little duplication, as we now have external_url (expected to contain a scheme and optionally a port) and external_hostname, but any attempt to combine the two variables leaves the user with less flexibility.

just remembered we have https://github.com/concourse/concourse-bosh-deployment/pull/70 waiting already - should I just merge that? it also configures alternative_names, not sure if that's a problem

Even better. Yes, merge that one.

thanks!


Add output content type

What this PR does / why we need it:

Add output content type

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #756
Special notes for your reviewer:
Release note:

Coverage increased (+0.008%) to 28.058% when pulling c40b8391c3d7e262f456b036afd5902069ef5f0c on xxwjj:content_type into 971e6a10d8b1976f230b9f0b90fc89df7affba64 on opensds:development.


The working with Webhooks link 404s

Clicking on "Working with Webhooks - Dynamics NAV" goes to a dead page:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/dynamics_subscriptions
[Enter feedback here]

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

ID: f8eb2c50-c0d1-7e64-0d00-8ad72f8a968a
Version Independent ID: f0fd2b39-733e-c38d-ad5f-02f6538d06e6
Content: API(V2.0) for Dynamics 365 Business Central   - Business Central
Content Source: dev-itpro/api-reference/v2.0/index.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Thanks for the feedback. The page in question does not contain that link Working with Webhooks, but we have fixed an issue that might be what you meant. This will be pushed with the next refresh. If the issue still pertains, feel free to open a new GitHub issue. Thanks.


Kafka bulk support documentation

What content needs to be created or modified?

TODO: add more details, to be triaged for v1.9
Describe the solution you'd like

Where should the new material be placed?

The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos

Additional context

@mukundansundar can you please assign this to yourself?

closed by #3071


About dataset

First, thank you so much for making such a great dataset, but I have a question now. I noticed that your dataset should not be up to date, it seems like you just updated the metadata.json and other files in hugging face, but the Chinese dataset just hasn't been updated yet, and my error is as follows

Finally, I hope you upload the latest dataset on Google Cloud Drive, thanks!

Hi, the image shows some missing files, but I noticed on Hugging Face that they do exist. You might want to double-check for further comparison. Regarding updates on Google Drive, we sincerely apologize for not being able to update it promptly. This is because we are still iterating on the annotation and cleaning of the dataset, and Google Drive is not well-suited for small incremental updates. We will update the final version on Google Drive once the dataset's annotation and cleaning are fully completed.

Hi, the image shows some missing files, but I noticed on Hugging Face that they do exist. You might want to double-check for further comparison. Regarding updates on Google Drive, we sincerely apologize for not being able to update it promptly. This is because we are still iterating on the annotation and cleaning of the dataset, and Google Drive is not well-suited for small incremental updates. We will update the final version on Google Drive once the dataset's annotation and cleaning are fully completed.
Thank you