Moving to .NET Core (v 1.1)

Fixes #1637
This is initial code that will take us away from the full .net framework and allow the projects to be built cross-platform. I have switched us to .net core 1.1 and as a result removed some non compatible dependencies and refactored code where the API surface changed.
I've cleaned my commits, but kept them quite verbose since it'll help see exactly what changed here.
With these changes I'm able to build and run the site use dotnet.exe + run the unit tests etc.
If anyone has a Mac and can pull this locally, would be good to know if it works as expected.
@tonysurma - I presume the Azure website can run a .net Core app?
If at all possible it would be nice to get this finalised and merged in this week, pre NDC if we're happy to do that? There are some risks though so if we feel safer waiting until after we can do that also (although rebasing will become more and more nasty!) One of the devs joining me is a Mac user so would be helpful if we could run native, rather than in a Windows VM.
Things we loose:

I have removed SMTP based code we were using purely to create a dev version that could send to local SMTP server during dev. We already have a fake SMTP client which write to the output so this isn't crucial. SMTP was removed in .NET core and while there are replacements, they are quite heavy for this single use.
I have removed the XZing dependency that was generating a QR code for the phone app. This was reliant on System.Drawing which is not in .net core.

Not yet done:

The service replacements for Twitter and Geocoding work locally for me. This code is initial WIP and I will be refining it further, adding some comments and also adding tests.

Not done (might need help):

I've never run the F# Scenario testing - I'm not sure if that will still work or not. Would welcome input on that if we need it running for v1.

@mgmccarthy and @MisterJames - Would welcome some local testing and a few sets of eyes on this since it's a fundamental change.

@tonysurma - I presume the Azure website can run a .net Core app?

Yes that is true/works so we are good there, I will probably do a test deployment to another website just to see what if anything needs updating but yeah it should be good

@stevejgordon, I have eyes on this now.

@stevejgordon, I didn't realize you could do this:
var request = new HttpRequestMessage(HttpMethod.Get, requestUrl.ToString());
request.Headers.TryAddWithoutValidation("Authorization", string.Concat("Bearer ", bearerToken));
response = await _httpClient.SendAsync(request);

you're passing in the http auth headers on the HttpRequestMessage, instead of setting the auth information on HttpClient itself. This might help me with a problem I've been having at work.
Have you tested the sign-on auth via Twitter at all, or did you just refactor the code?

@stevejgordon, wow! This is a HUGE effort/amount of work. After eyeballing it and walking through your commits, everything looks great.
I have not actually stood it up and smoke tested it yet (at least the parts that have the old API removals and the new API additoins)....
did you want me to use the site a bit before I give the thumbs up on the merge?

@mgmccarthy - Yep tested it through and I got the name details back from Twitter. Nothing through for email, but it doesn't look like that is always exposed (unless you found otherwise). Even with a manual call to Twitter I couldn't get one back.
r.e. the headers, yep it's useful since you can keep a static HttpClient around without it being tied to a specific use. I tend to build up the request with the headers it needs and then use a general client. I think this could help with the SendRequestStatusToGetASmokeAlarm also?

@mgmccarthy - Thanks, it went a little deeper than I expected to get everything up and running. I've stepped through some flows but if you're able to pull it and validate a) it builds for you and b) you can load the site that would be good for peace of mind since it's a big change.
I'm going to try and test as many flows manually before finally finishing it up. But if the code looks good I can begin on some unit tests for my services.

I think this could help with the SendRequestStatusToGetASmokeAlarm also?

you are correct, it could. Let me take a crack at that refactoring. I'll see if I can get what I need from building up the HttpRequestMessage and passing it to the IHttpClient held as a singleton with StaticHttpClient implementor.

Nothing through for email, but it doesn't look like that is always exposed (unless you found otherwise). Even with a manual call to Twitter I couldn't get one back.

at this point, I've given up on Twitter and the user's email. Twitter makes it so impossible to get what should be a simple piece of data for a user from it's API, I'm willing to live with the email being non-retrievable when a user is logging in via Twitter (@tonysurma, I assume you agree?)

@tonysurma, I want to have a chance to stand this up and excersise the changed part of the system before i say good to go for the code review. Give me a day or two and I'll let you know. I know that steve will also be smoke testing on his end as well

@stevejgordon Has anyone tried standing up everything on a Mac yet, as otherwise I could try and give that a go one of these days?

@YannickMeeus - It's not been tried yet so yes that would be great if you're able to, thanks. Would be great to validate that it gives the desired result. If you need any advise to be able to pull down this code, let me know.

@YannickMeeus that would be great, we have done it in parts and repeatedly run into issues but hopefully this PR with maybe some added bits) will clear that up.  I and others have done it in the past and we kept stumbling on the issues 'fixed' in this PR

@stevejgordon, I just tried to stand the site up and can't. I ran dotnet restore, rebuilt. When I pick IE for my brower the window opens, then immediately closes. When I pick Chrome for my browser, the site spins up then stops and I get this from Chrome:

my guess is I"m doing something wrong. Do I need to download/install anything new on my system in order to run the code in this PR?

@mgmccarthy - I think that's the fairly un-guessable sign that you might be missing the latest 1.1 SDK. If you go to https://www.microsoft.com/net/download/core#/current and download the latest SDK I hope you'll be good to go.

I think it might throw something into the output window to that effect. But otherwise it's pretty unhelpful!

@stevejgordon , got the SDK squared away. Just finished running through invocation of IGeoCodeService and everything worked great.
FYI, I used the same Google API key for:
"Mapping": {
    "GoogleDirectionsApiKey": "[directionsapikey]"

as I did for:
"Geocoding": {
    "EnableGoogleGeocodingService": "true",
    "GoogleGeocodingApiKey": "[geocodingapikey]"

so I'm not too sure if we need two separate ApiKey values for different Google services that both use the same API? Or maybe on the live server, there will be a different ApiKey per Google service?
Anyhow, figured I'd just bring it up.
Moving on to testing TwitterService

also, you can blow away SmtpEmailSender. I wrote that and added it to the project before I truly understood how Azure worked.

@stevejgordon, I have all my Twitter values set in my user secrets file that correspond to the Twitter values in config.json:
"Twitter": {
"ConsumerKey": "[twitterconsumerkey]",
"ConsumerSecret": "[twitterconsumersecret]",
"OAuthToken": "[twitteroauthtoken]",
"OAuthSecret": "[twitteroauthsecret]"
},
and the code is not throwing any errors, but I'm getting a null back for name and email. I know we already discussed email, and we're giving up on it b/c Twitter makes it impossible, but in your testing, could you at least retrieve the name of the user?

@mgmccarthy - Thanks for testing it. I'm very pleased to hear that it loaded and ran! I spent some time early this morning updating with some of your points. I found a bug in the twitter code and fixed that up too. I'll push at lunch and see if you can check that again.
I had the same thought on the API key for Google so I'll consolidate that as part of this work.

@mgmccarthy These changes should resolve the twitter issue and tidy a few things up. I'll get some tests in around the geocode stuff next.

@stevejgordon, the changes look good. Twitter is now pulling first/last name properly and the Google API key stuff looks to be consolidated.
@tonysurma :shipit:

Before we merge in do we have updated/clear guidance for what one has to do on their dev machine?  Also I want to try to get it working in a web app on azure as a test first but more worried about the guidance part.
Thank you, this is excellent!
@dpaquette  @MisterJames can you run this and add thumbs up so we make sure it works for as many folks as possible before we move the system over.
Again thanks @stevejgordon and @mgmccarthy for this.  Very excited

@tonysurma - No problem. More too it than I thought but ultimately got there in the end.
Local Dev Setup:

Visit https://www.microsoft.com/net/download/core#/current and download the latest SDK - Currently 1.1
Install the SDK
Open the AllReady Solution
Clean the solution
Perform a nuget package restore either through VS or if you prefer using dotnet restore
Build and run the application

Possible issues:
In some cases things can get a bit messed up in VS and not cleaned. If you have any problems, try a fresh clean and the navigate to the project folder and delete the obj and bin folders manually. Then nuget restore and rebuild the solution.

@tonysurma - I have some tests I'd like to add, but those are not critical and the sooner we merge once approved by everyone, the better. So I'll either add them to this PR if not yet merged or start a new issue to cover them.

@YannickMeeus - Did you manage to try this on your Mac?

@stevejgordon - wonder if there is a way we can add this to docs/wiki and link from readme maybe?

@tonysurma - Sure, I can take a look at doing that.

@tonysurma - I've added a small page to the wiki - https://github.com/HTBox/allReady/wiki/Developer-Setup - We can link there from readme once this goes live.
We also have a more detailed guide for a full setup that @digitaldrummerj put together - https://github.com/HTBox/allReady/blob/master/docs/prerequisite_install_guide/prerequisite_install_guide.md - We could update that also to ensure it mentions the latest SDK version and URL

great @stevejgordon thanks.  You can edit the readme as part of this PR and then it will go live at the same time.

@tonysurma clever!

@tonysurma Guides updated.

Sorry guys, I'm really late to the party here. What is our strategy going forward? Do we always want to be on the Current release our should we stick to LTS (Long Term Stable)? Something tells me that due to the nature of the application we should avoid the fast moving Current release and stick to LTS. Unless there is a compelling reason (i.e. new feature that we really need) I don't see why we would need to be on Current.
I'm curious what the rest of the team thinks about this?

@stevejgordon I have. I'm afraid it doesn't stand up correctly due to the following line in the sampleDataGenerator.cs class, which brings about a larger compatibility issue:
TimeZoneId = "Central Standard Time",
The reason why this value bricks the app is because the time zone Database on Mac OSX and Linux is different from the one used on Windows platforms. Linux and Mac will be using the IANA tz db. There's a Jon Skeet podcast floating about from a couple of months ago, which explains that particular issue in great detail, including how he's trying to tackle that in NodaTime.
Unfortunately, the corefx team are aware of this but have yet to commit to a fix, and are suggesting handling the windows CLDR <-> IANA tz mapping ourselves.
The future issue for handling mapping and updates to the tz dbs can be found here.

@dpaquette Fair question. I don't think there's a specific requirement for it. It's supposed to be quicker than 1.0.x and I thought that the Azure App Service logging feature could be useful as we do need to consider logging going forward. Otherwise we could stick 1.0.3 but targeting .net core. Even with that we've had to update with the security release versions a few times. If we think 1.0.x is better for supporting allReady I can make that change.
@YannickMeeus Oh [TODO: insert suitable cross-platform expletive here!]. That's a shame. We always said dates were hard. Agree, that it doesn't stop this merging in and getting close to the end goal, but it's a shame Mac development is still an issue. I listened to Jon on that podcast and it was very interesting. In fact we had an email thread with him over other datetime issues just after that was released.
I'll do a bit of reading as well.

@dpaquette @stevejgordon my two cents is when we finally launch this thing, we move to LTS as it will makes things easier on maintenance going forward.

@YannickMeeus
cc @dpaquette @stevejgordon
the plan is to move to NodatTime, but until they have a stable release for .NET Core, we're pretty much stuck with what we have.
That being the case, since the SampleDataGenerator class is not required for the functionality of the site (all it does is seed data), then this is not a show stopper for Mac users. They could easily comment out/not run this code.
If that is done, will the site run on Mac?
Thanks

That being the case, since the SampleDataGenerator class is not required for the functionality of the site (all it does is seed data), then this is not a show stopper for Mac users. They could easily comment out/not run this code.

However having seeded data is helpful for testing/using the site as you develop.  Is this a case where we could have some way of knowing we are on non-windows and run a different line (like a compiler directive),  or get a 'default' systemtimezone and just use that as we don't need to compare or jump between mac/windows with this seed data, and/or have an alternate line of code for Mac users OR is it just a pure bug and nothing we can do than comment it out?
Thanks all for testing this

@mgmccarthy @YannickMeeus - Not had chance to look yet but I thought we used TimeZoneIds for creation of campaigns etc as well, selected from the dropdown. So might be a wider issue?

So we think we should move back to 1.0.3 but targetting .net core? I have some time this evening so can update this PR if that's what we prefer. So far LTS hasn't seemed any more stable than current releases. But I guess the key thing is that when they do change they are small bug fix only level fixes, not API changes etc.

@YannickMeeus thanks for pointing out the timezoneid problem. On Windows, .NET gets the list of system timezones from the windows registry. I'm not sure how that works on Mac or Linux.
As @mgmccarthy mentioned, we will be transitioning to NodaTime and it's more standard timezone database in the near future (Once NodaTime 2.0 is out of Alpa). I will create a separate ticket to track this.

@mgmccarthy @stevejgordon I'll have a go without test data and see how far I get with testing before it bricks again. Earliest I can get some results on this will probably be tomorrow morning (GMT).

@tonysurma I've rebased this and also fixed up some failing unit tests after the rebase. I think those should have broken when I updated the context and Request model yesterday. Not sure why they didn't seem to. Anyway; all good now :-)

@stevejgordon to close this off, we discussed in slack and are set to make this move.
@dpaquette and @MisterJames any thoughts to add?

@tonysurma Reverted back to LTS. I also ran this up on Windows on VS code and add those launch files into the project.

@YannickMeeus Been thinking on this and chatting to @dpaquette - We might be okay as the only places we're hard coding a value for the time zone id is in the seed data and in tests.
If you do manage to try this, skipping the seed data we might be able to validate if the rest functions. Presumably the calls into TimeZoneInfo will return values which work for you locally. We believe if it does load, if you go to create a campaign, the time zone lister there should also give us a list of IANA values?
If you can see if any of those match a Windows TimeZone name we could perhaps just change sample data to use a commonly named timezone.


Added problem 54. SpiralMatrix.java

Added Leetcode problem 54. SpiralMatrix.java

Please read the NOTE FOR CONTRIBUTORS.md file, add the link to code, sample input/output along with required comments and Time/Space Complexity :)

Added question link with sample input/output and time,space complexity.

Please create the issue first, get this assigned to you and then commit it! (Just read the NOTE FOR CONTRIBUTORS.md file once). I'll accept it for sure 🥇

@ana2407 For now, I need to close this!


Bumping all gems to newest versions

Bumping gems to the following versions:
rspec to version 3.9
bunny to version 2.15.0
hashie to version 4.1
multi_json to version 1.14.1
faraday to version 1.0.1
faraday-middleware to version 1.0

I undid the changelog change and added a new changelog entry with a mention of the exception class change. Thank you!


[Bug]: Can't deploy extension to production environment

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Extension
Expected behavior
When following the guidance at this link: https://shopify.dev/docs/api/checkout-ui-extensions#scaffolding-extension
There is never an option to chose the correct store to login with or deploy to. I make sure I am logged in to the right store in my browser. When the CLI gets to the point that it needs to go to the browser to log in, it does, but choosing the store is never allowed. It just says I logged in successfully and can close the window.
Yet no matter what I do, when using the shopify CLI to attempt to deploy our extension to our production store, the CLI will not find or auth in to the correct store.

Actual behavior
As an admin for a store that is on Shopify+, has extensibility turned on already, and has active/working API calls going on, I would expect there to be a very easy way to pick the shop I want to deploy the extension to, and yet there isn't.
There seems to be a solid disconnect from Shopify devs and the way the product is presented to the end user.
Support sent me here because they said the issue is that I wasn't registered as a "partner", but I don't want to be a partner. I am a store admin. In our store, I can see all the language suggesting we already have this feature turned on:

Yet there is no way to actually login and deploy to this store from the CLI for some weird and undocumented reason.
Verbose output
Pasting that here would publish our API key.

Reproduction steps

Follow steps from your docs: https://shopify.dev/docs/api/checkout-ui-extensions#scaffolding-extension
Try to deploy to a store you are already the admin of.
Fail sauce.

Operating System
Mac, latest
Shopify CLI version (check your project's package.json if you're not sure)
3.57.1
Shell
zsh
Node version (run node -v if you're not sure)
20.9.0
What language and version are you using in your application?
No response

I'm afraid the CLI is only compatible with Partner development stores or Shopify Plus Partner sandbox stores as explained here: https://shopify.dev/docs/apps/tools/cli/commands#dev
That's why your store can't be found. I know it's annoying and we are working to improve the experience. Sorry for the inconvenience!

It's not an simply an "inconvenience" when you're charging $30k+/annually
for the featureset - and it's honestly offensive to treat this so
passively.
If you want to target enterprise customers, you need to be prepared to
offer a much higher level of personal customer service and empathy than
this.
On Fri, Mar 22, 2024 at 10:47 AM Gonzalo Riestra @.***>
wrote:

I'm afraid the CLI is only compatible with Partner development stores
https://shopify.dev/docs/apps/tools/development-stores or Shopify Plus
Partner sandbox stores
https://help.shopify.com/en/partners/dashboard/managing-stores/plus-sandbox-store
as explained here: https://shopify.dev/docs/apps/tools/cli/commands#dev
That's why your store can't be found. I know it's annoying and we are
working to improve the experience. Sorry for the inconvenience!
—
Reply to this email directly, view it on GitHub
https://github.com/Shopify/cli/issues/3574#issuecomment-2015378567, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BCQCH2YBSJI6I3FDZQBDKW3YZRHANAVCNFSM6AAAAABE4B2KU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGM3TQNJWG4
.
You are receiving this because you authored the thread.Message ID:
@.***>


GitHub Action to deploy mdbook docs from master

What was wrong?
mdbook isn't building. 404 at https://ethereum.github.io/trin
How was it fixed?
Add the default GitHub Action recipe for mdbook. It's the first time I'm doing it, so this may not work. 🤷🏻♂
I don't really have a theory for how to test a GitHub Action, besides merging it and seeing what happens.

Closing in favor of #590


Support account prop to be of AIP-62 AccountInfo type

The adapter returns the current connected wallet account address and public key as a string type. With the latest AIP-62 upgrade, the Wallet now returns the account address as a AccountAddress type and the public ket as PublicKey type.
This change is to support the 2 new types to be returned correctly from the adapter.
With this change, the account type returned by the adapter is of type AccountInfo | NewStandardAccountInfo
Before
const {account} = useWallet();
account.address // string type
account.publicKey // string type

Now
const {account} = useWallet();
account.address // string | AccountAddress type
account.publicKey // string | PublicKey type

so, if people continue provide a string version, then you won't know the type of key?
Should we provide an optional key type? There's not going to be any loss of type conversion across this boundary is there?

It should come from the wallet side, the new standard requires the wallet to provide a typed public key


US-M3: Research contributions

This PR implements US-M3.
A section simple list overview of contributions has been added. The title of the contributions is displayed and each entry links to the relevant page on research.rug.nl.
A python script for scraping contributions from the RSS feed on research.rug.nl has been added. It uses no external dependencies and can be ran with python3 contributions.py from the top level directory of the project. The script has a hardcoded link to the datasets RSS feed of the SEARCH group.
The scripts stores the output in the _data directory in the project root.

@kakka0903, I merged M4 (submitted first) and it caused a conflict with M3. Could you have a look? Thanks!

@kakka0903, I merged M4 (submitted first) and it caused a conflict with M3. Could you have a look? Thanks!

Should be resolved now ✔


torch._standard_gamma() has accuracy gap compared to scipy and torch.cpu

🐛 Describe the bug
test_distributions_xpu.py::TestDistributionsXPU::test_gamma_gpu_sample_xpu FAILED                                                                               [100%]
============================================================================== FAILURES ===============================================================================
___________________________________________________________ TestDistributionsXPU.test_gamma_gpu_sample_xpu ____________________________________________________________
Traceback (most recent call last):
File "/home/gta/daisyden/rebase/n1_ci/third_party/torch-xpu-ops/test/xpu/test_distributions_xpu.py", line 119, in _test_gamma_gpu_sample
self._check_sampler_sampler(
File "/home/gta/daisyden/rebase/n1_ci/third_party/torch-xpu-ops/test/xpu/../../../../test/distributions/test_distributions.py", line 1289, in _check_sampler_sampler
self.assertLess(-threshold, bias, message)
File "/home/gta/miniforge3/envs/n2/lib/python3.10/unittest/case.py", line 1232, in assertLess
self.fail(self._formatMessage(msg, standardMsg))
File "/home/gta/miniforge3/envs/n2/lib/python3.10/unittest/case.py", line 675, in fail
raise self.failureException(msg)
AssertionError: -0.06743384440339613 not less than -0.259 : Gamma(alpha=1.0, beta=0.1).sample() is biased:
[-0.259 -0.264 -0.243 -0.059  1.     0.951 -0.279 -0.274 -0.296 -0.277]
To execute this test, run the following from the base repo dir:
python test/distributions/test_distributions.py TestDistributionsXPU.test_gamma_gpu_sample_xpu
Versions
with 2024/12/09 nightly wheel, no such issue on preci.

Tried cpu _standard_gamma tensor, no such issue.

fixed：https://github.com/intel/torch-xpu-ops/pull/1161

Seems this issue exists or not on different driver versions, investigation is WIP.


Local api socket:54321 permission denied

Description
Was working on a project and all was going well. Until today when suddenly I started getting the following error:
listen tcp <IP_ADDRESS>:54321: socket: permission denied
which occurs during the sam start local-api in the GO process. What I mean by this is that the process seems to start, but gets stuck and yields this error at lambda.start(handler).
All the development was done in a VM, so the actual "changes" since last tested were installing snapd and nodejs. I also checked the logs and there doesn't seem to be any other app using the port.
P.S.

Tried running sam start local-api as sudo.
used chmod 777 on the handler

Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

OS: Deepin
sam --version: 0.22.0

Is this just that port? Does using other ports work as expected? Does installing the previous version of sam cli negate the current problem with port 54321

I tried switching the port to 8080 or 4200, same result (with a different port error).
I tried uninstalling / installing the 0.22.0 version - same result
I'm installing using homebrew and I can't seem to find an earlier version of the cli. Thing is, it worked with this version for a while and suddenly stopped working. Other than installing node, angular cli, and generating an angular project I didn't do anything. Seems a bit weird to suddenly lose permissions :-?

@taigi100 Is this still happening? start-api does not use the port by default so something else, either docker or your code, is getting hung up on port 54321.

which occurs during the sam start local-api in the GO process.

What go process? Docker or your function code?

I have the same issue, is there any solution ?

@diegotony do you still face this issue? if yes, please reopen


How can i publish a photo with usertags ?

const res = await ig.publish.photo({
		file: fs.readFileSync('./test.jpg'),
		caption: 'This is a test',
		usertags: ?
	})

There's an example in /examples


Plain pip install from repo fails to load LiquidHandler - Missing pylibftdi dependency

I'm not sure if this is a bug, but I was not expecting it.
When installing with pip install . from the repo's directory and running my tests, I get an import error.
The pylibftdi module seems to be required, even though it is part of extras_plate_reading in setup.py. I could install it with pip install .[dev] to get going, but it does not seem optimal for the general case.
Traceback:
/usr/local/lib/python3.9/importlib/__init__.py:127: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
pylabrobot/resources/pipettin/pipettin_tests.py:4: in <module>
    from pylabrobot.liquid_handling.backends.piper_backend import PiperBackend
pylabrobot/liquid_handling/__init__.py:2: in <module>
    from .liquid_handler import LiquidHandler
pylabrobot/liquid_handling/liquid_handler.py:18: in <module>
    from pylabrobot.plate_reading import PlateReader
pylabrobot/plate_reading/__init__.py:2: in <module>
    from .biotek_backend import Cytation5Backend
pylabrobot/plate_reading/biotek_backend.py:6: in <module>
    from pylibftdi import Device
E   ModuleNotFoundError: No module named 'pylibftdi'

It is used in liquid_handler.py for a validation, and perhaps elsewhere.

I'm not sure how to fix this without adding that module in install_requires. I've added it for now.
Best!

thanks for flagging, made it similar to how we handle optional dependencies in other cases: https://github.com/PyLabRobot/pylabrobot/commit/f6f4693e65ccaacf1f861777ee89e6f67fef4540

Thanks Rick, you're the best!


Added nav bar to sharing page

tmp merge

temp

testing conflict

Anshul is looking at it from his side


Add the private docker registry for three VMs under Apache

A private docker registry has been set up for the VMs dedicated to
OpenWhisk deployment. This PR adds the feature to  push the controller
and invoker images into this private registry, so that they can be
accessed by all the VMs.

Description

Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[ ] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

Codecov Report

Merging #4356 into master will decrease coverage by 4.25%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #4356      +/-   ##
=========================================
- Coverage   85.56%   81.3%   -4.26%
=========================================
  Files         169     169
  Lines        7833    7833
  Branches      536     536
=========================================
- Hits         6702    6369     -333
- Misses       1131    1464     +333

Impacted Files
Coverage Δ

...core/database/cosmosdb/RxObservableImplicits.scala
0% <0%> (-100%)
:arrow_down:

...core/database/cosmosdb/CosmosDBArtifactStore.scala
0% <0%> (-95.24%)
:arrow_down:

...sk/core/database/cosmosdb/CosmosDBViewMapper.scala
0% <0%> (-92.6%)
:arrow_down:

...whisk/core/database/cosmosdb/CosmosDBSupport.scala
0% <0%> (-84.62%)
:arrow_down:

...abase/cosmosdb/CosmosDBArtifactStoreProvider.scala
4% <0%> (-52%)
:arrow_down:

...in/scala/org/apache/openwhisk/common/Counter.scala
40% <0%> (-20%)
:arrow_down:

.../scala/org/apache/openwhisk/utils/Exceptions.scala
20% <0%> (-20%)
:arrow_down:

...whisk/connector/kafka/KafkaProducerConnector.scala
72.5% <0%> (-15%)
:arrow_down:

...nwhisk/core/database/cosmosdb/CosmosDBConfig.scala
94.11% <0%> (-5.89%)
:arrow_down:

...in/scala/org/apache/openwhisk/common/Logging.scala
76.05% <0%> (-0.71%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

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


[iOS11] Update project settings and fix errors

Changes in this pull request
Updated the main project lib settings for iOS 11, fixed all errors (which are from warnings-as-errors).
Checklist

[x] All tests pass. Demo project builds and runs.
[x] I added an entry to the CHANGELOG.md for any breaking changes, enhancements, or bug fixes.

Failures fixed in #946

Whoops, looks like you are right. Closing the ticket :)


Demo for styling bqplot objects

As @nmearl suggested to @patudom , here's an issue to make a request to @nmearl to provide a simple code demo how to format features of a bqplot object.

Resolved by #16.


Remove jQuery from the image pasting functionality

Switched to plain JavaScript
Tested the image pasting functionality and it works as before

Demo using JavaScript without jQuery

Nice work as always.

🫡 Glad to be of service.

Offtopic, but: Did I forget to approve any of these PRs?

https://github.com/go-gitea/gitea/pull/29230


When adding draw interaction, it flickers while zooming in and out (Version 9.0.0)

This happens only with the newest version 9.0.0. Adding a draw interaction, like drawing polygon, the map flickers while zooming.
The polygon is still visible, but the map under it disappears and flickers. Sometimes it even is blank when I stop zooming.
Style:
  styleRedOutline: Style = new Style({
    fill: new Fill({
      color: [0, 0, 0, 0.1]
    }),
    stroke: new Stroke({
      color: [255, 0, 0, 0.5],
      width: 5
    })
  }

Initialization:
   const osmLayer = new TileLayer({
      source: new OSM()
    });

    let that = this;

    this.vectorLayer = new VectorLayer({
      source: this.source,
      style: function (feature) {
        return that.styleRedOutline;
      }
    });

    this.view = new View({
      center: [-472202, 7530279],
      zoom: 12
    });
    this.map = new olMap({
      layers: [
        osmLayer,
        this.vectorLayer
      ],
      view: this.view,
      controls: []
    });

Adding drawing interaction:
this.interaction = new Draw({
      type: 'Polygon',
      source: this.source
    });

    let draw: Draw = this.interaction;

    draw.on('drawend', evt => {
      console.log("drawEnd")
      this.lastSelectedFeature = evt.feature;
    });

    this.map?.addInteraction(this.interaction);

I tried to trigger layer change and other stuff, but it seems to be a problem with the version 9.0.0. With 8.2.0 it does not happen.

Can you please try if the problem goes away when you npm install ol@dev?

Reproducible in 9.0.0 version of Draw and Modify Features example: https://openlayers.org/en/v9.0.0/examples/draw-and-modify-features.html
The same example in 8.2.0 is OK: https://openlayers.org/en/v8.2.0/examples/draw-and-modify-features.html

@radokostelnik What exactly are the steps to reproduce? Also, does it work as expected in https://openlayers.org/en/main/examples/draw-and-modify-features.html

@ahocevar Steps:

Open the page
Zoom in/out using mouse wheel or the zoom -+ buttons or "zoom to area" interaction.

The OSM map flickers and randomly ends up blank. I can reproduce the same also in the main version.
Further info: I tried to build the example locally, but I could not reproduce it in that trimmed version.

Thanks @radokostelnik. So you‘re saying when running the example from a local clone of OpenLayers with npm start, it works as expected?

@ahocevar Not exactly a local clone. I created the 3 files from the example on the disk, ran 'npm start'. In this case, the behavior is not reproducible with<EMAIL_ADDRESS>When running npm run serve-examples from a local clone, the behavior is reproducible.

I saw flickering when upgrading to 9.0.0 as well. A possible workaround (works for me) is to use the WebGL renderer, import TileLayer from "ol/layer/WebGLTile".
I tried the "Draw and Modify Features" example on my laptop at work, and it did not flicker. At home, it flickers, and goes blank at some zoom levels, but after I've drawn a circle it stops flickering and doesn't go blank. Very odd.
The page linked by @karussell flickers constantly and "reliably" ends up with a blank map (I can try it at work tomorrow).
Using Chromium (at home, didn't try it at work), both pages work fine.
Maybe it has something to do with Nvidia drivers?
Desktop at home, flickers: Fedora, Sway, Wayland, Firefox Nightly, Nvidia proprietary drivers.
Laptop at work, doesn't flicker: Fedora, Sway, Wayland, Firefox, Intel graphics.

Thanks for all the reports so far. I suspect this is a duplicate of #15593.
I'm still not sure whether the issue has been fixed since v9.0.0 or not. Can anyone who experiences the flickering please try https://deploy-preview-15620--ol-site.netlify.app/en/latest/examples/draw-and-modify-features.html ?. Thanks!

@ahocevar that works the same for me at least - flickers on zoom and the map sometimes disappears, but again it stops flickering once I've placed a marker (I guess doing so triggers some sync/redraw on zoom changes that doesn't happen otherwise?).

Thanks for all the reports so far. I suspect this is a duplicate of #15593.
I'm still not sure whether the issue has been fixed since v9.0.0 or not. Can anyone who experiences the flickering please try https://deploy-preview-15620--ol-site.netlify.app/en/latest/examples/draw-and-modify-features.html ? Thanks!

I still see random flickering on the preview-15620 page. After placing a geometry it usually stops, but after panning to another location and/or zooming in it starts again.
Windows + Chrome or Edge, Nvidia graphics.

Thanks everyone so far. Can anyone do a git bisect with npm start and a local clone of the library to find out which commit introduced the flickering?

git bisect points to 628deb063.

Thanks @wjoel, this confirms my suspicion. If you have the test setup still available, can you please try if #15649 fixes the problem?

If anybody else wants to test a potential fix, please try https://deploy-preview-15649--ol-site.netlify.app/en/latest/examples/draw-and-modify-features.html.

@ahocevar it unfortunately doesn't help, same issue. Maybe there are other changes made since that could affect this, as to my eyes your PR seems to revert the problematic change? I double checked and 9aa5f20e72 works for me, no flickering on that one.

@wjoel Ok, can you try to continue bisecting and see when it broke again?

@wjoel and everyone else affected by this issue, can you please test #15651: https://deploy-preview-15651--ol-site.netlify.app/en/latest/examples/draw-and-modify-features.html

@ahocevar Looks good to me, no flickering.

Ok, thanks for the feedback @radokostelnik. What about https://deploy-preview-15652--ol-site.netlify.app/en/latest/examples/draw-and-modify-features.html, does that fix the issue too?

@ahocevar thank you very much, both examples works fine, no flickering before or after drawing features.

@ahocevar This is strange. I see flickering in the #15652 version, but only in Chrome (Version 122.0.6261.129 (Official Build) (64-bit)). Edge (Version 122.0.2365.92 (Official build) (64-bit)) on the same machine does not flicker.

@radokostelnik So you're saying that #15651 works reliably and #15652 does not?

@ahocevar Yes, that's what I'm seeing here.

https://github.com/openlayers/openlayers/assets/2410648/7478c80a-5d4f-496b-bd29-90b2c7ad9569
@ahocevar Attached a screen capture video from the #15652 version.

@radokostelnik When the test website for #15652 has been rebuilt in a few minutes, can you please try again? I made a change so the transform matrix will be the same as in #15651.

@ahocevar Tested now on https://deploy-preview-15652--ol-site.netlify.app/en/latest/examples/draw-and-modify-features.html, still seeing the flickering.

@radokostelnik Did you clear the cache? And you‘re sure there is no flickering with #15651?

@ahocevar Yes, "Empty Cache and Hard Reload", multiple times, in both Chrome and Edge. I don't see flickering in 15651, I do in 15652, in both of them.
TBH, I'm not "sure" about no flickering in 15651, but based on my quick tests, I can't see it there.

@radokostelnik For both versions: what’s the output of document.querySelectorAll('.ol-layers canvas').length?

@ahocevar 1 for 15652, 2 for 15651

@ahocevar Looks good, I can't reproduce flickering on https://deploy-preview-15652--ol-site.netlify.app/en/latest/examples/draw-and-modify-features.html.

Thanks @radokostelnik, anyone else want to try?

@ahocevar Confirm, looks good

Nice work! I can confirm, no flickering on https://deploy-preview-15651--ol-site.netlify.app/en/latest/examples/draw-and-modify-features.html or https://deploy-preview-15652--ol-site.netlify.app/en/latest/examples/draw-and-modify-features.html


Support Node v4

Transition to this once all dependencies are verified to work with it.

Looks like this was a non-issue, node v4 is working fine for me.


[Fixes #459] Include JsonTemplateLayout for log4j2

Signed-off-by: Sascha Vogt<EMAIL_ADDRESS>

Figure out how to merge Log4j2Plugins.dat

With ugly workaround, it now works :) Was able to get Json output without further changes other than specifying an appropriate appender config

We are eager to see this change released.  Can you tell us

when this will be released?
Which versions it will be released in (2.x, 1.11.x)?

Thank you.

for now, #459 is fixed in the main branch and it's targeted to version 2.1.1.
I see no problems adding it to 2.0.x branch (I even should do it - thanks for reminder).
I can also do it in 1.11.x/1.12.x - just let me know.

Backports:

to 2.0.x: #472
to 1.12.x: #473
to 1.11.x: #474


add apply method to NoOpLogger

This always trips me up :)

Okay, we'll get this into 1.2.0.

Okay, we'll get this into 1.2.0.


Widgets save graph

Some annoyingly-implemented save functionality.
You can just call graph.save(filename='whatevs'). We might want the save call signature to match py.plot, not sure.

@chriddyp , wanna give it a look? when this PR is merged, it'll work: https://github.com/plotly/streambed/pull/1192

@chriddyp , I was making the tutorial for widgets, when i realized we never merged this guy in. should i fix it up and we can finally let users save graphs made in widgets : )

yeah, that sounds good

cool, i'll try and fix it up tonight.

@chriddyp , want to take a peek? I added the fadeTo functionality interface on top of the message protocol. A little sloppy maybe? I'm less familiar with how the messaging works though, so there may be a cleaner way.

Note, there seems to be an issue in Python 2.6 with requests where requests[security] needs to be installed (so, beyond just requests). Perhaps a change in circle caused this to pop up? Should be fixed by the last two commits.

:dancer:


Update contribution-guide.md

This change is

@midoblgsm and @aswarke you can review this PR \ branch to see the changes in text.
@alonm  please approve this PR.

Coverage remained the same at 48.352% when pulling 5b262e1ce0453b5e1963ecba339e467b3b271258 on fix/update_readme_cont into 28767feb20e59f06bb0edef7a030350ba4b5c0eb on dev.

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Cleanup containers and demos

This PR cleans up and improves the usability of the containers produced by the docker files included in this repo.

This is still pending some modifications to the demo setups so setting to draft for now.

This will address #52


feat(pubsub): add support for pubsub

I don't understand why this PR is here and not a part of epsagon-node.

Because this acts as a consumer wrapper, which can run async in parallel, and we need asynchooks and run in context


How to use FirewallD on Ubuntu?

Is it possible to use FirewallD on platforms other than rhel? I'd like to use FirewallD on Ubuntu. The package is available in repositories, but the cookbook seems to ignore it if platform is not rhel (firewall 'firewalld' configures ufw instead).

Hello! The resource name is arbitrary -- firewall 'firewalld' just makes a chef resource named firewalld. You probably want to override the provider for the resource, e.g.:
firewall 'default' do
  provider Chef::Provider::FirewallFirewalld
end

Please be aware that Ubuntu often makes subtle changes when they implement things like this, so it's entirely possible that this cookbook won't work on Ubuntu with firewalld. But you're welcome to try or submit PRs to make it work better :+1: Thanks!


librealsense won't install successfully on 16.04.5

This is due to the upgraded LTS kernel.
There's a tracking issue here: https://github.com/IntelRealSense/librealsense/issues/2402
If we can't get this installable we'll likely need to strip this as a default installation element from the turtlebot stack and make it an optional addon.

If we can't get this installable we'll likely need to strip this as a default installation element from the turtlebot stack and make it an optional addon.

please do.
I've had to help quite a few people here in the lab that broke their ROS installation by installing all of the turtlebot 2 stack on it and have it fail with librealsense and not recover.

@gavanderhoorn I tested it on a fresh 16.04.5 machine and it appeared to not block the system from installing other packages, just that package was errored: https://github.com/IntelRealSense/librealsense/issues/2402#issuecomment-432045561 Are you seeing different behavior?

I have seen this behaviour in Docker images with Ubuntu 16.04. The image doesn't build because of this require modifications on the package configuration and they fail, like already mentioned. I ended up making a custom with some fixes and ignoring the rosdep installation using skip_keys but it was still not working until last time I tried.

I have seen this behaviour in Docker images with Ubuntu 16.04. The image doesn't build because of this require modifications on the package configuration and they fail, like already mentioned. I ended up making a custom with some fixes and ignoring the rosdep installation using skip_keys but it was still not working until last time I tried.

Same here. We're still having trouble with librealsense in all our containers since the post-install script fails to detect it's running in a container

I spent some time trying to fix it but at this point I think it makes more sense to pull the dependency until the problem is resolved.

Upstream ticket marked as resolved.


[Enhancement] Allow whitespace in key/token/password input

Description
Allows whitespace in security scheme key/token/password input.
Motivation and Context
See #350 for context
How Has This Been Tested?
Tested with petstore API

Works as expected:
https://user-images.githubusercontent.com/9343811/205142319-cabdfa57-3919-400b-a031-2f7ab76dc920.mov

One other consideration is that spaces may need to be url-encoded in order for the code samples to work as expected.


python3Packages.pytest: 6.2.2 -> 6.2.3

Motivation for this change
https://github.com/pytest-dev/pytest/releases/tag/6.2.3

pytest used to create directories under /tmp with world-readable
permissions. This means that any user in the system was able to read
information written by tests in temporary directories (such as those created by
the tmp_path/tmpdir fixture). Now the directories are created with
private permissions.

Doesn't sound too bad, flagging as security anyway, until we can agree that it isn't.
Things done

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

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

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

Building home-assistant to test how much breaks this time.


[Bug] [remote-rpc] the asynchronous call's method can't use other return type except Boolean

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
env:
macos monterey 12.0.1
java version 1.8.0_241
when I add a method in org.apache.dolphinscheduler.rpc.IUserService and implement in UserService
public interface IUserService {

    @Rpc(async = true, serviceCallback = UserCallback.class)
    Boolean say(String s);

    Integer hi(int num);

    @Rpc(async = true)
    Boolean callBackIsFalse(String s);

    //the method i add
    @Rpc(async = true, serviceCallback = UserCallback.class)
    String returnType(String type);
}

in test, it happend a error

What you expected to happen
it should be success no matter what type the method return !
the bug is because the dynamic proxy mechanism.When it calls a asynchronous rpc method,it should return a null value firstly,and wait for the really response to callback.
in this module,it wirte the true to result,which only suitable for Boolean return type.
org.apache.dolphinscheduler.rpc.client.ConsumerInterceptor::intercept()
//...other code
while (retries-- > 0) {
    RpcResponse rsp;
    rsp = nettyClient.sendMsg(host, protocol, async);
    //success
    if (null != rsp && rsp.getStatus() == 0) {
        return rsp.getResult();
    }
}
//...other code

org.apache.dolphinscheduler.rpc.remote.NettyClient::sendMsg()
if (Boolean.TRUE.equals(async)) {
      result = new RpcResponse();
      result.setStatus((byte) 0);
      result.setResult(true);
      return result;
}

the intercept()'s result should be the type of method return. but the code is always 'true' , so it happens the error: string can't be cast to boolean
How to reproduce
just add a test method which return type is not Boolean in IUserService.
Anything else
No response
Version
dev
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Right now, the rpc module is not used, I not sure do we need to maintain this. @caishunfeng

Right now, the rpc module is not used, I not sure do we need to maintain this. @caishunfeng

How do you think?

Right now, the rpc module is not used, I not sure do we need to maintain this. @caishunfeng

I think the RPC part can be used for lightweight protocols or cross-language support, so we should keep it although it is not yet perfect.

Right now, the rpc module is not used, I not sure do we need to maintain this. @caishunfeng

How do you think?

It's good to introduce an RPC framework to replace the current communication mechanisms. But suggest using the existing RPC framework like GRPC or others, we would better not develop a new RPC framework, unless someone is willing to maintain this.


[Sprint: 46] XD-2777: Document Trigger Source

JIRA: https://jira.spring.io/browse/XD-2777
Add documentation for trigger source.
Change the way the default date value is set up to provide a useful default in the documentation.
Tested with
xd:>stream create foo --definition "trigger --payload=foo | log" --deploy

for immediate trigger, and
xd:>stream create foo --definition "trigger --payload=foo --date='03/30/15 17:52:00' | log" --deploy

for a delayed trigger.

Merged as is as 8c2c021.
Will create another JIRA/PR to

handle cron validation early
handle 1 out of 3 mutually exclusive options


Allow to disable plugin via environment variable

When discussing about the unpatch method of each plugin, i said that which make me think that it would be useful to disable plugin but via environemnt variable.
The use cases is pretty simple: modifying the code can take more than 10min for some CI setup (time to rebuild, push images etc) so removing plugins can take quite some times.
Having a environment variable to do that allows engineer to test out quickly by just re-deploying their app.
Datadog actually implemented that recently: https://github.com/DataDog/dd-trace-js/pull/733 so i believe i'm not the only one having this need.
WDYT ?

I think we should wait for the named tracer PR to merge since this is the use case it is designed for

Is this ready to be looked at now? This is something I am interested in as well so I can stub something out if you haven't already @vmarchaud.

@markwolff I didnt started any work on that so you can do it if you want to :)

I'd say go for it


Update load-balancer-multivip-overview.md

A small correction

@Maestro100 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


How get frame size?

I'm trying to filter barcodes that only in square layout, but I don't have frame size, and position in barcodes do not equal screen size or screen resolution

I could indeed pass the frame as a second argument to the onBarcodeScanned callback so you can access it easily.
Meanwhile you can also write your own frame processor leveraging scanCodes to access the frame directly, eg. https://github.com/mgcrea/vision-camera-barcode-scanner/issues/5#issuecomment-1761004490.
Regarding the barcode bonding boxes they are quite messy and need pretty complex translations to actually match the camera frame, it is something that is done to compute highlights but I guess I should do it by default in the returned object so that you get useable coordinates outside the box.


LinkTokenCreateAsync for the Identity Verification product fails without a valid DateOfBirth for LinkTokenCreateRequestUser

When trying to create a LinkToken (LinkTokenCreateAsync) for the Identity Verification product
client.LinkTokenCreateAsync()

without including a valid DateOfBirth in
new LinkTokenCreateRequestUser {}

as follows

  var client = new PlaidClient(Going.Plaid.Environment.Sandbox, sSecrets, sPlaidClientID);
  string ps = "IdentityVerification";
  string sCountryCodes = "US";

  var response = await client.LinkTokenCreateAsync(
      new LinkTokenCreateRequest()
      {
          User = new LinkTokenCreateRequestUser { ClientUserId = Guid.NewGuid().ToString(),},
          IdentityVerification = new LinkTokenCreateRequestIdentityVerification{TemplateId = sTemplateID},
          ClientName = "Test Client",
          ClientId = sPlaidClientID,
          Secret = sSecrets,
          Products = ps.Split(',').Select(p => Enum.Parse<Products>(p, true)).ToArray(),
          Language = Language.English, // TODO: Should pick up from config
          CountryCodes = sCountryCodes.Split(',').Select(p => Enum.Parse<CountryCode>(p, true)).ToArray()
      });

The following is returned
{
  "link_token": null,
  "expiration": "0001-01-01T00:00:00+00:00",
  "error": {
    "error_type": 0,
    "error_code": 27,
    "error_message": "user.date_of_birth must be a date after 1850 and not in the future.",
    "display_message": null,
    "request_id": "3UQuz25nAcoGHZ4",
    "causes": null,
    "status": null,
    "documentation_url": null,
    "suggested_action": null
  },
  "request_id": "3UQuz25nAcoGHZ4",
  "StatusCode": 400,
  "IsSuccessStatusCode": false
}

Looks to be a disagreement between API spec and API expectations - namely that date_of_birth should be nullable. I'll fix as part of update to new version this week.

Please update to version 4.16.0 - this should address your issue. Thanks!

I just updated to version 4.16.0 and it appears the issue has been addressed.  Thanks!


Rename project

I've been learning about this project and I'm excited to try it out. I think it has great potential. Unfortunately, the name is pretty bad. It's not imaginative nor is it searchable and discovery is key. Even removing the dot and using PureDI makes it more searchable.
Some other alternatives might be:

PurDI (maybe pronounced purr-dee or pure-dee)
DIGen
InjectGen
Injectinator

Keep up the good work!

Thank you. It is good idea. Now the difficulty is only in finding this project or does the name sound really bad? What does Google search find for the search query "Pure DI"? I'm asking because there is difficulty - some customers already uses the NuGet package with id Pure.DI and I don't want to inconvenience them. Renaming the project itself to GitHub is not difficult. We can temporarily release packages with 2 IDs, new and old one Pure.DI.

Your search results have increased greatly in the last 10 days. :) And I'm not a fan of the name, but that isn't enough reason to break things. The only other issue is that DI is both a namespace and a type.
At this point, I would say, don't rename the project, but maybe rename the namespace to just PureDI.


Fix attached files names in mail_handler.php

Convert attached files names to human readable format, i.e. "Тест.txt" instead of "=?UTF-8?B?0KLQtdGB0YIudHh0?="

https://secure.phabricator.com/book/phabcontrib/article/contributing_code/#no-pull-requests


Release build documentation

Currently, when I go to http://brm.io/matter-js/, I can get the documentation for the edge build. I can see no where to find the documentation for the release build. Could a link be added either to the release page or the navigation for people wanting to develop against a "stable" version?

The current stable version is 0.13.0 and the docs for the stable build are always at http://brm.io/matter-js/docs/. To clarify, the current 'edge' build is actually just the same as 0.13.0 as there have been no changes since.

Perhaps the site should then update the release link to 0.13.0 rather than
0.10.0?
On Sep 24, 2017 4:33 PM, "Liam"<EMAIL_ADDRESS>wrote:

The current stable version is 0.13.0 and the docs for the stable build
are always at http://brm.io/matter-js/docs/. To clarify, the current
'edge' build is actually just the same as 0.13.0 as there have been no
changes since.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/liabru/matter-js/issues/493#issuecomment-331744920,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AO5FYucSTnucNnM3OikUWc-BezVqW7UQks5sltivgaJpZM4Ph9VW
.

Actually it looks like the releases page is just not up to date, I think my release build system must have stopped working, will look into it.

I have revisited this and resolved, see #697. Also to be clear, after this was originally posted the hosted docs are always for the latest release (rather than edge builds).


Support arbitrary signal length in count_leading_zeros

Currently this function requires power of 2 length.

update PriorityEncoder to use more efficient count_leading_zeros instead of m.If loop
refactor  FPURounding to use new count_leading_zeros

I will open a PR solving the issue sometime this week.
@Durchbruchswagen would you like the PR to target #741 instead of master branch to also do things like removing nearestpow2 that you had to add there?

Notes from meeting: revisit PriorityEncoder and LZA


Unset AFL_CC

If we install QEMU mode later after having already done some fuzzing runs and setting AFL_CC, QEMU mode installation will fail if AFL_CC is something else than TEST_CC.

Thanks!


Fixing emscripten on windows to use the right files.

This fixes up a small issue where we don't resolve .bat files from PATH since windows is a bit picky.

Thanks!


[Autocomplete] controlled doesn't set initial value.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

Expected Behavior 🤔

Steps to Reproduce 🕹
https://codesandbox.io/s/material-demo-yj6sq
Steps:
1.Set value before first load
2. Render control
3. Expect to see selection
Context 🔦
Using in an edit form with existing data.
Your Environment 🌎
Latest as per codesandbox

Duplicate of #18173


Unable to seed rows using CURRENT_TIMESTAMP

Hello, I'm trying to write a simple seeder:
class MySeeder extends AbstractSeed
{
    public function run(): void
    {
        $data = [
            [
                'user_name' => 'Administrator',
                'user_creation' => 'CURRENT_TIMESTAMP',
            ]
        ];
        $table = $this->table('users');
        $table->insert($data)->saveData();
    }
}

Executing this seeder fails:
[PDOException (22007)]
  SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: 'CURRENT_TIMESTAMP' for column 'user_creation' at row 1

I explored the code a bit, and tried using Literal and Expression, but got the same result.
Is there a way to achieve this?

The bug here is in this block of code:
https://github.com/cakephp/phinx/blob/5f9ee844fdf3a34af7aac211f9463758c35bc18b/src/Phinx/Db/Adapter/PdoAdapter.php#L378-L415
The root here is that when inserting, we create a prepared statement where all values are then binded. Stuff like CURRENT_TIMESTAMP (or any function really) cannot be a binded parameter, but should be in the SQL directly. As such, the fix would be that when we go to construct the SQL statement, instead of just saying all values are going to be binded, we need to step through each, and either insert the literal (if using Literal) or a ? to be binded.

I think the bug also exists in the PdoAdapter::insert method as well, so will want to fix it in both places.

Using literals is now supported as of 0.16.3 released today.


Replaced trace visualization code with the one in gh-pages script.js

I have noticed that the first trace and the remaining ones differ in visualization. Even if all the traces are the same, the subsequent traces appear to have a darker shade than the first one. As far as I could observe, this was not the case with your demo page, therefore I believe having visualization that way could be the fix, if there is any issue to begin with.

Hi, thanks for the contribution. The reason I didn't implement it this way in the data collection code is because the performance hit from re-rendering every single trace is pretty big when you have more than a few traces. Maybe we could do this but only if there are fewer than 10 traces in total? Also, could you fix the indentation in your contribution? Thanks.


Fixed a few java warning messages

Fixed a few warning messages.

Added a header comment.
Added 2 default case statements
Removed unnecessary @SuppressWarnings("unused") annotation.

Shouldn't #230 have caught https://github.com/sjardine/gwtbootstrap3/commit/dd4b8e694d81fd4a41b664d3036a2ebb1bc2e277?
Rest looks good to me.

Yes, it should have. Let me double check and test it out later today. Good catch.

gwtbootstrap3 » gwtbootstrap3 #468 SUCCESS
This pull request looks good
(what's this?)

I am going to look into better CI and even deployment for this library so that everything can be as seemless as possible. Right now, deploying a demo and api docs is tedious!

We should look into using travis CI.
https://github.com/rgladwell/m2e-android has a great example of how they do their site deploys. The interesting parts are https://github.com/rgladwell/m2e-android/blob/master/me.gladwell.eclipse.m2e.android.update/pom.xml#L51 and https://github.com/rgladwell/m2e-android/blob/master/.travis.yml#L52


There's no "motivation" for players to quickly end up the round

Sometimes there are just two players on the map and they are evading themselves.
It would be nice if there was some kind of motivation or/else some mechanism, which would force the players to engage in close combat.
IE inner blocks can disappear making all the players to fall at the bottom of the screen, so they will have to settle things down. Or some suicidal counter. I don't know.

This has been addressed by raising the water level when there are last two players remaining.


Add previous answer to earliest and latest date

What is the context of this PR?
Implements functionality which allows users to validate the earliest and latest date against a previous answer.
How to review

Run tests
Ensure feature works as per https://trello.com/c/UzNS13t8/451-validation-earliest-date-before-previous-answer-4 and https://trello.com/c/bnSemkJw/675-validation-latest-date-before-previous-answer-6

Dependencies

[ ] https://github.com/ONSdigital/eq-author-api/pull/162

 Validation - Earliest and Latest Date


Allow for a setting for functions to default to galus or Israel

@justlevine and @tam5 can you both look at this to see if this looks good?

Codecov Report

Merging #14 into master will decrease coverage by 2.75%.
The diff coverage is 83.33%.

@@              Coverage Diff              @@
##              master      #14      +/-   ##
=============================================
- Coverage     100.00%   97.25%   -2.75%
- Complexity       236      245       +9
=============================================
  Files             23       24       +1
  Lines            371      400      +29
=============================================
+ Hits             371      389      +18
- Misses             0       11      +11

Impacted Files
Coverage Δ
Complexity Δ

src/Moadim/Moadim.php
60.00% <60.00%> (ø)
2.00 <2.00> (?)

src/Getters/Holidays.php
83.33% <62.50%> (-16.67%)
9.00 <9.00> (+2.00)
:arrow_down:

src/Getters/Getters.php
85.36% <75.00%> (-14.64%)
20.00 <0.00> (+6.00)
:arrow_down:

src/Getters/MDY.php
100.00% <100.00%> (ø)
6.00 <0.00> (ø)

src/Getters/Parsha.php
100.00% <100.00%> (ø)
42.00 <41.00> (ø)

src/Helpers/LeapYears.php
100.00% <100.00%> (ø)
1.00 <0.00> (ø)

src/Helpers/helpers.php
100.00% <100.00%> (ø)
0.00 <0.00> (ø)

src/Moadim/CholHamoed.php
100.00% <100.00%> (ø)
10.00 <10.00> (ø)

src/Moadim/Holidays.php
100.00% <100.00%> (ø)
39.00 <10.00> (ø)

src/Moadim/Yuntif.php
100.00% <100.00%> (ø)
11.00 <11.00> (ø)

... and 4 more

Continue to review full report at Codecov.

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

Looks good and is (so far) working as expected. Thanks for getting this PR out so quickly!

closes #14

Wow! Time flies. I'm finally responding to your comments here. I updated the code and I'll push it in a minute or two to my branch.


This is a plain revert of the change that supposedly broke things

(BROKEN) @ build-time:
Please choose a version of "@storybook/components"
Issue:
What I did
How to test
Is this testable with Jest or Chromatic screenshots?
Does this need a new example in the kitchen sink apps?
Does this need an update to the documentation?
If your answer is yes to any of these, please make sure to include it in your PR.
For maintainers only: Please tag your pull request with at least one of the following:
["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

@RuslanBakhar
Are these PRs intended?


adding support for helm chart save

Added support for helm chart save. It does the following

Save chart to local.
Login to Helm Registry in ACR.
Push chart to ACR.
Remove the local chart.

For login to Helm Registry in ACR, it uses service principal provided during pipeline task creation.
This support is only for Helm v3 and when HELM_EXPERIMENTAL_OCI variable is set to 1.
This is required for issue #12870

LGTM


Add autmated lifecycle tagging and autoclosing to issues

What is missing?
Automated tagging and closing of issues that are inactive
Why do we need it?
With a current of 287 open issues, this is a lot to go through for maintainers, current as well as new contributers.
It is hard and time consuming which issues are actively being investigated,discussed or worked on.
An automation in form of a bot could help to groom out stale issues and have them automatically closed.
This way it will be easier to find issues that need work/help to them.

I would love this! Open to any suggestions :)

@brancz https://github.com/probot/stale https://probot.github.io/apps/stale/

There are a couple of projects doing that. Often it's quite annoying that these bots just close issues. I would rather do some grooming (again, did that a few months ago) to close issues.
In what way is having that many issue open an issue? If someone is not sure if something is still investigated, then simply ask? :thinking: :blush:

You can configure it to close issues/PR after X days of inactivity, any activity on the PR/Issue resets that clock (In my experience)
There is also support for exempt labels...
I have used this tool in the past (in private repos with a large eng team), found it very useful.

I'd be totally fine with labelling issue stale. Closing them based on time is something, that I've found really annoying over at https://github.com/gopasspw/gopass. Then people constantly need to comment to keep things open, which creates a lot of noise.
No hard feelings though. We should definitely do something about those stale issues. :+1:

makes sense @metalmatze
How about "staged rollout" for the bot?
stage 1: the bot only tags the issues as stale/rotten/dead (not sure about the naming) and a human can then easily groom them at some point.
stage 2: the bot tags the issues as stale/rotten/dead (again not sure about the naming) and then closes them.
Starting with stage 1 and manually grooming, I'd should be relatively easy for the human who does the grooming, to find out if it'd be safe to have a bot close those issues.


Creating tvm.target twice will create empty params

Calling target = tvm.target.create('llvm') twice will create empty params.
The following is the code snippet I used, which was copied from the quick start tutorial: https://docs.tvm.ai/tutorials/relay_quick_start.html
opt_level = 3
target = tvm.target.create('llvm')
with relay.build_config(opt_level=opt_level):
    graph, lib, params = relay.build_module.build(
        mod, target, params=params)

I ran it in jupyter notebook on both Mac and Linux platform.
Only if I ran this segment twice, the value of params will be {}
Trying to look into the code of autotvm.task.dispatcher, seems that there is somthing wrong with the context cache.

Thanks for reporting this, please open a new troubleshooting thread on https://discuss.tvm.ai/

One troubleshooting thread created in discuss.tvm.ai


test close connection

add close connection code to ClientExample

The only change I see is commented out.

Yes, I just add this for remaind me InboundClient has close method


Remove lodash from global object

When CLI require's ios-sim-portable, it already had added lodash in the global object. So ios-sim-portable resets it to the version specified in its own package.json, so CLI's code will no longer work.
Do not use the _ from the global object - require it in each file instead.

👍


Maximum number of arguments in Stan Math Functions

Feature Request
Increase the maximum number of arguments for C++ functions that can be added to the Stan/math library.
Version
2.7.0
Description
I am writing a function that computes dosing events for compartmental models used in pharmacometrics. Using a .hpp file, I created a function that takes in 9 arguments, but it seems the limit is set to 7. The add() function used in functions_signatures.hpp seems to take between 2 and 9 arguments, the first argument being the name of the function and the second one the return type.
Is there a reason why this limit exists? And if not,  would editing the add() function be the best approach?
Steps
The line in function_signatures.hpp that returns an error is:
add("PKModelTwoCpt", MATRIX_T, MATRIX_T, VECTOR_T, VECTOR_T, VECTOR_T, VECTOR_T,       VECTOR_T, VECTOR_T, VECTOR_T, VECTOR_T);
The following error message appears when I try to install RStan using the edited StanHeaders directory:
~/StanHeaders/include/src/stan/lang/function_signatures.h:960:1: error: no matching member function for call to 'add' add("PKModelTwoCpt", MATRIX_T, MATRIX_T, VECTOR_T, VECTOR_T, VECTOR_T, VECTOR_T, ^~~ ~/StanHeaders/include/src/stan/lang/ast_def.cpp:259:31: note: candidate function not viable: requires 9 arguments, but 11 were provided     void function_signatures::add(const std::string& name,                               ^ ~/StanHeaders/include/src/stan/lang/ast_def.cpp:242:31: note: candidate function not viable: requires 8 arguments, but 11 were provided
The error message repeats itself until the required number of arguments is 2.

There isn't a limit.  You're just need to use this signature:
 void function_signatures::add(const std::string& name,
                                   const expr_type& result_type,
                                   const std::vector<expr_type>& arg_types);

P.S.  This was a stan-dev/stan issue, beause the funciton signatures are defined there, not in stan-dev/math.  Sorry that's not clear coming from StanHeaders, which is presumably the RStan packaged version.

Hi Bob,
Thank you for your quick response and apologies for not posting this under stan-dev/stan.
I'm under the impression the signature you posted is the function I used: name for the first argument, return type for the second argument, and then argument types. (I didn't make this clear in the original post and did a quick edit to clarify).

Your description has this:
add("PKModelTwoCpt", MATRIX_T, MATRIX_T, VECTOR_T, VECTOR_T, VECTOR_T, VECTOR_T, VECTOR_T, VECTOR_T, VECTOR_T, VECTOR_T);

What I'm suggesting is:
std::vector<expr_type> arg_types;
arg_types.push_back(expr_type(MATRIX_T, 0U));
arg_types.push_back(expr_type(VECTOR_T, 0U);
...
arg_types.push_back(expr_type(VECTOR_T, 0U));
add("PKModelTwoCpt", MATRIX_T, arg_types);

I think you may be able to get away without the expr_type wrappers and just (MATRIX_T), etc., because there's a unary implicit constructor taking the basic type.

Thank you for the clarification !
I was able to install RStan both with and without the expr_type wrappers.


modify for compiling on archlinux [DNM]

What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
What is changed and how it works?
Proposal: xxx
What's Changed:
Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch:

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Side effects

Release note
Please add a release note, or a 'None' if it is not needed.

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


[Hateoas] Do you know the Hateoas lib?

Hi!
I quickly read your blog post, and saw that you were about to implement Hateoas features into this lib.
Did you consider the Hateoas library? Or are you aware of it, at least?
Cheers,
William

@philsturgeon how was it? Any support for HATEOAS and is there already a stable version of Fractal for Laravel 5.1?

For now, HATEOAS is still achieved via adding links : [] to your serializer.


Add option not to include timestamp in logs

I have written up a PKGBUILD for Arch to simplify installation. Since in this case, FediFetcher is running as a systemd service, its logs are written to the systemd journal that already include timestamps for each line:
Apr 21 14:21:28 myhostname fedi-fetcher[186448]: 2024-04-21 14:21:20.736995 CEST: Added context url https://very.cool.instance/asdf/jkl

I suggest to add an option in the configuration / command line that removes the timestamp from the logging behavior.

Great idea, especially after the introduction of the python logger as contributed by @AndrewKvalheim very recently. Maybe even a more general purpose log-format option? Would need to be carefully thought through, to get the balance right between on the one hand being powerful enough to be actually helpful, and on the other hand not being so difficult that noone understands how it work...

Questions re the pkgbuild if you don't mind (please assume I know nothing in your answers, because I do know literally nothing about PKGBUILD for Arch):

How does updating that build work? Can it potentially be automated using a git workflow?
How re-usable is this for other users? Might it make sense to add it as an option to the README file?

(Whether adding to the readme would be sensible and acceptable would probably depend on the answer to the first question though.)

How does updating that build work? Can it potentially be automated using a git workflow?

Yes I have seen that it can be done with workflows, but I have no experience there. I'm just watching this repository and would update the PKGBUILD manually. Usually, this only means setting pkgver to the new version, given that nothing else needs to be changed.

How re-usable is this for other users? Might it make sense to add it as an option to the README file?

It absolutely is meant to be re-usable, any other user can install this either via
$ git clone https://aur.archlinux.org/fedi-fetcher.git
$ cd fedi-fetcher
$ makepkg -si

or
$ paru -Syu fedi-fetcher

depending on what they like to use. The latter uses paru which is one of many AUR helpers that simplify installing from user-submitted build scripts. Then, the only thing left to do is to edit /etc/fedi-fetcher/config.yaml and to systemctl enable --now fedi-fetcher.timer for it to run every hour by default. It's lock file path is set to /run/fedi-fetcher/.lock and state dir is /var/lib/fedi-fetcher, for it to be unix-like :)
Feel free to mention it in the README 👍🏼

Sorry for the delayed response. I had completely missed yours.
Thanks for taking the time to respond. I think given the above at this stage I would not want to mention it in the readme, unless there was a way of automating the updates. It is an interesting concept though.
Still very happy to look into changing the timestamp logging though

@Sir-Photch, are you able to update the PKGBUILD for Arch to 7.1.3, please?

This is now possible by supplying the argument "log-format": "%(message)s" in your config.json (or running it fedifetcher with --log-format="%(message)s" if that's your preferred way of running FediFetcher).

Very cool. I will update the PKGBUILD and the respective service file accordingly. Thanks!

Thanks @Sir-Photch


cval as parameter to init

[Enhancement] It would be nice if cval was added to the __init__ function as a parameter with a description. I understand you can set it manually at the moment but it takes a while to even see if the code supports setting the background color.

There is now an alpha of the newest version of the library online, which allows to do that.
Code to resemble the old behaviour with custom cval would be:
from imgaug import augmenters as iaa

seq = iaa.Sequential([
    iaa.Fliplr(0.5), # horizontal flip
    iaa.Flipud(0.5), # vertical flip
    iaa.Affine(
        scale={"x": (0.8, 1.2), "y": (0.8, 1.2)}, # scale images to 80-120% of their size, individually per axis
        translate_px={"x": (-16, 16), "y": (-16, 16)}, # translate by -16 to +16 pixels (per axis)
        rotate=(-45, 45), # rotate by -45 to +45 degrees
        shear=(-16, 16), # shear by -16 to +16 degrees
        cval=0.5 # set this to (0, 1.0) to sample random cvals between 0 and 1.0
    )
])

images = load_batch() # expected to be of shape (N, height, width, channels) or a list [(height, width, channels), ...]
images_aug = seq.augment_images(images) # returns a 4d array or list of 3d arrays, depending on what form 'images' had
images_aug = images_aug / 255.0 # project to 0-1 range


Bump wordpress 6.4.x

53 commits.
6 files changes.
0 PR description.
Closing this PR, life's too short.


Fix most and skip some unit tests for Windows

Motivation
Some unit tests fail in CI on Windows
Changes
Fixed most unit tests. Tests that require more work are skipped. I created bug tickets for skipped tests:

https://github.com/spacemeshos/go-spacemesh/issues/3624
https://github.com/spacemeshos/go-spacemesh/issues/3625
https://github.com/spacemeshos/go-spacemesh/issues/3626
https://github.com/spacemeshos/go-spacemesh/issues/3628
https://github.com/spacemeshos/go-spacemesh/issues/3629

Test Plan
unit tests
DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

bors try


ChatGPT Error 429: Too many requests

Verify it's not a duplicate bug report

[X] I searched for similar bugs reported on GitHub and nobody has reported a similar issue. Search all issuees.
[X] I read Troubleshooting guide on Readme and there is not a guide on how to solve my problem.

Describe the Bug
I just installed the extension. I added an API key. I immediately get the following error. I am a ChatGPT plus subscriber. Is this indicating I can't do ANY API calls for free? Even for personal use in a tool like VSCode? Or am I missing something? Or is this a bug?
An error occured. ChatGPT error 429: { "error": { "message": "You exceeded your current quota, please check your plan and billing details.", "type": "insufficient_quota", "param": null, "code": null } }
Please tell us if you have customized any of the extension settings or whether you are using the defaults.
Initially when I got the error I was using the defaults. I have since made some changes trying to troubleshoot.
Additional context
No response

The HTTP Error 429 is about your account/request frequency. There could be multiple reasons but OpenAI tells you that you have insufficient_quota in their response. Check if you have enough credit, non-expired account. If your account is expired you will see this
You could also try making a Curl request to see if you have enough credits, following the troubleshooting guide here: https://github.com/gencay/vscode-chatgpt/issues/192

I really do not understand those downvotes. You got clear instructions on checking if your API access is expired.
It is clearly written in the FAQ that OpenAI API is not part of the ChatGPT Plus subscription
Is the ChatGPT API included in the ChatGPT Plus subscription?

No, the ChatGPT API and ChatGPT Plus subscription are billed separately. The API has its own pricing, which can be found at https://openai.com/pricing. The ChatGPT Plus subscription covers usage on chat.openai.com only and costs $20/month.

Are you attempting to imply that the answers to my questions are as follows?
Is this indicating I can't do ANY API calls for free?
YES
Even for personal use in a tool like VSCode?
CORRECT
Or am I missing something?
NO
Or is this a bug?
NO

I am just stating the facts.
Is this indicating I can't do ANY API calls for free?
Chat GPT Plus subscription and OpenAI API are two separate products, which is obviously not clear to most Chat GPT Plus subscribers. To use Open AI API, you need to pay for it separately. You can open a new trial account with a different email and get some free API calls.
As you can see in this screenshot, I got $18 as a free trial credit, but I lost everything without even using it since my trial expired. I was very confused since I was unaware that API returns a 429 error, even when your trial API is expired.
Even for personal use in a tool like VSCode?
Unfortunately, that is correct.
Or am I missing something?
You were not aware that API is not part of your subscription, but it should be clear now.
Or is this a bug?
This is not a bug, and you will get the same results with any other software that uses OpenAI API. That's why you were instructed to try cURL to see if you will get the same error.

Hi @ScottBeeson - I was thinking of my earlier post as an answer to all of your questions. Sorry if that wasn't clear enough. The problem being about your account, I still believe, answers all of them. And I was asking you to verify your account/API Key and then we could build on top of that and thus I kept the issue open with a question label. If you were able to verify it's not related to your account, and you are indeed able to make a request with the same API Key, let us know and we could investigate further.
We try to be as verbose as possible in the extension about errors, so you know what you could do to troubleshoot and mitigate them when you face them.
We will add the Q&A for ChatGPT Plus subscription being different than OpenAI's API pricing in the Readme. Also please let us know if you have any ideas how to improve our documentation apart from that.

I am having the exact same problem, and I just installed it (never used it before). I tried to logout/login from their website I tried closing down VS and the error still persists.

For those of you who added an API key before you subscribed to OpenAI, it will return the 429 error as well. It wasn't until I made another API key after subscribing to OpenAI - I admit I was confused at first as I am a chatgpt subscriber too, so I was very confused.
Came to this thread and realised I'd done everything right in the end - but why was I still getting the error? Then I thought, hmm maybe it does need a new API key (I made one about an hour ago, but I wasn't subscribed then).
Hope this helps anyone else.

Updated our readme with more questions from this thread. for future reference please confirm that your account is active and usable with OpenAI APIs

Since 2-3 days I have a similar issue. I can only use ChatGPT on my phone, which again uses the same public IP addresses as my Desktop PC, as they are using both the same router. On my Desktop I always get back 429 error on my phone it's working like a charm. No idea what the problem is, I already tried using a different internet connection, a different, Desktop/laptop computer etc. etc. The only device I can use ChatGPT with is my Android phone ... What's going on here?

I even created a new ChatGPT account and still have the same issue going on

Since 2-3 days I have a similar issue. I can only use ChatGPT on my phone, which again uses the same public IP addresses as my Desktop PC, as they are using both the same router. On my Desktop I always get back 429 error on my phone it's working like a charm. No idea what the problem is, I already tried using a different internet connection, a different Desktop/Laptop computer etc. etc. The only device I can use ChatGPT with is my Android phone ... What's going on here?

had the same issue, now i've disabled ipv6 and it's working

@m0ezk Did you disable it on router side or did you simply disable the ipv6 functionality at your system's interface settings?

same here, i got this issue on MY PC, but on my android phone its working fine, i also do all @venomone do , and nothing works too

Even If I fully switch Off ipv6 I have no luck :(

i assume our MAC address get BLOCKED ?

@m0ezk Did you disable it on router side or did you simply disable the ipv6 functionality at your system's interface settings?

I disabled ipv6 in grub parameters, so yeah, system wide

Even If I fully switch Off ipv6 I have no luck :(

What OS and browser are you using and did u try all standard browsers already?

Now Things loose even more logic.
I tried it using Linux, Windows 11 and OSX all with the same outcome, I even tried a different Internet Connection, also a VPN, still same result. This makes no sense at all.

Now Things loose even more logic.
I tried it using Linux, Windows 11 and OSX all with the same outcome, I even tried a different Internet Connection, also a VPN, still same result. This makes no sense at all.
Whats funny, I tried my Windows 11 VPS using RDP I can now again use ChatGPT...

I spent 2 hours of my life looking for a mistake in myself, in the code, in my own attitude to things to realize that the mistake is that you can create an api key for free but you have to pay to make it work, its awful


Typings issue in Chart-Geo Extension plug-in

Expected behavior
No issue when using 'geofeature' in Elements of the chartoptions.
Current behavior
As of today, in typescript I have this error:
**Object literal may only specify known properties, and 'geoFeature' does not exist in type '_DeepPartialObject<ElementOptionsByType<"choropleth">>'.
The expected type comes from property 'elements' which is declared here on type '_DeepPartialObject<CoreChartOptions<"choropleth"> & ElementChartOptions<"choropleth"> & PluginChartOptions<"choropleth"> & DatasetChartOptions<...> & ScaleChartOptions<...> & IGeoChartOptions>'
**
Reproducible sample
Playground Link
Optional extra steps/info to reproduce
No response
Possible solution
No response
Context
I opened an issue on the github plug-in, but I think the developper is expecting some help to fix this case.
https://github.com/sgratzl/chartjs-chart-geo/issues/106
Can someone drive us in the right direction to fix this?
I already check that he declare his interface in the chart registry like asked on the docs but I can't dig further as I'm not an expert in ChartJs extension.
More, this guys wrote 5 or 6 plug-in for ChartJs, so if he is not confortable in fixing this I think we need some help from you guys. You might find the issue in few minutes I hope.
Thanks,
chart.js version
v3.7
Browser name and version
No response
Link to your project
No response

Pretty sure you can register your own custom elements with Chart.registry.elements.register(customElement) and if I understand it correct from what I looked at it should resolve your issue

thanks, I will forward that to the dev.

The problem here is that the GeoFeature element in chartjs-chart-geo doesn't update the ElementOptionsByType interface. They already do this for the scales, so just need a similar block for the element.
Corrected example https://www.typescriptlang.org/play?ts=4.4.4#code/JYWwDg9gTgLgBAbzgYQBYENYBoUdgeTBmAgDsBnOAXzgDMoIQ4ByAYzxgDoArc5gbgCwAKFCRYiXNAhgANgFMYqZGRgNZCqDhWzoAZVboFOAOLyIAMXnoYAVyjycASTOXrdh4WJlyOAAoM3PKs3qQGRo5wMDIQvGTUdAxMAETsmDC8ALRpsJkA5ubJQsIiuOmcDnnA5DDyUAAUaNJyisqq6pqm5lY29pE6+obGcAGxwaHhCgCUxaUAJsGymPJwIBBztgosOVy8zIilcHDyAB7i8MCktVC06KwrrgCiCiDyV14kFABCAJ4AKj8wCsEIcjnACm5eg4AFxwFzddx9D4+UFUESg07nOCXa63e5wZ7yV7vIifci-AFAgA8f0p8gAfMcTrVSHNKE8Xm8YMjvv9AcC0cJqOjhAA3TBwEInOAAXjgcwgrFsxK4BRghJVvycc3qyRAPzQ6WSUzg6EoAAk-gBZAAyyHQpHF5A1XOK4qgqwNHBkMFhZQIpJ8VNSqGaCiUyUZcpBQrB8k5V3IsJjYLBEJ6HnkydBqbgACNoAsoAMoLDkgBiABsAA4azXklgc0cqI3Y83W83+EA

Thanks for the help


Rename: Konnect introduction section

This PR skips the changelog.
Renames the elements in the introduction section of the Konnect docs.
Runtime Manager to Gateway Manager
Runtime Groups to Control Plane
Composite Runtime Groups to Control Plane Group
Runtime Instances to Data Plane Nodes

https://konghq.atlassian.net/browse/DOCU-3369

@cloudjumpercat please do review also. I mainly wanted to look over this PR to make sure we cover the context for the terminology based on our existing content + historical uses of the terms data plane & control plane.


Improved size limit messages

What do you think about changing the messages to the following?
In the hierarchy:

Please provide additional filtering - the hierarchy level exceeds allowed size of 5.

Maybe the one in the dialog could be conditional?

When the limit is exceeded:

Estimated hierarchy level size: 5+. Please provide additional filters.

When the limit is not exceeded:

Estimated hierarchy level size: 4.


Fixed an issue where text field component did not recognize rules

There are lint errors but they are from files which this PR does not involve.
I think this PR shouldn't fix the lint errors because it may introduce conflicts.


Fix #1655, Size unit test table load buffer based on config

Describe the contribution
Fix #1655 - Supports larger table configurations (in passing unit tests) by sizing the unit test buffer used for table loads based on the configuration values.
Testing performed
Increased CFE_PLATFORM_TBL_MAX_SNGL_TABLE_SIZE to where when multiplied by CFE_PLATFORM_TBL_MAX_SIMULTANEOUS_LOADS it would break the 128 * 1024 limit hard coded in ut_support.c.  Built and ran unit tests, confirmed they now pass.
Expected behavior changes
Unit tests will pass for a configuration supporting larger tables
System(s) tested on

Hardware: Intel i5/Docker
OS: Ubuntu 18.04
Versions: Bundle main + this commit (plus a modified config)

Additional context
Still not unlimited since table register uses the default buffer size, but an improvement.
Third party code
None
Contributor Info - All information REQUIRED for consideration of pull request
Jacob Hageman - NASA/GSFC

CCB:2021-07-07 APPROVED


Automatically download correct operator-sdk version to bin dir, if not found

What type of PR is this?
/kind chore
What does this PR do / why we need it:

Update Makefile to automatically downloaded the specific version of operator-sdk into (repo root)/bin
Update codegen.yaml to automatically use the Go version defined in go.mod

Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

Thanks @svghadi!


build process choking on SVG images?

I have some SVG images in /assets/images/, and running the build process generates the following error:
[11:52:52] Starting 'images'...
[11:52:53] 'images' errored after 458 ms
[11:52:53] CssSyntaxError in plugin 'gulp-imagemin:'
Message:
Colon is expected
Details:
parseError: [object Object]
fileName: [...]/wp-content/themes/FoundationPress/src/assets/images/arc-lines-top-r2.svg
domainEmitter: [object Object]
domain: [object Object]
domainThrown: false
[11:52:53] 'build' errored after 6.09 s
If I remove 'images' from the gulp build task, it runs fine. Is there perhaps an issue with optimizing SVGs?

@adambundy I'm closing this out. If you have more information or if you want to share the SVG's that were causing it to choke, feel free to reopen.


create_image() on Android Q API 29

Hi,
Thanks for your work. I'm a complete beginner at Android developement and tried to build a webview app with aswv.
Something went wrong when i tried to upload a photo taken with the camera.
Seems that the Environment.getExternalStorageDirectory() used in the create_image() method is deprecated in Android Q. I instead had to use getExternalFilesDir to make it work.
FYI This is where i found the solution
Just so you know.

you are a life saver this was cracking my head

thank you soo much that was 1 problem i was having with SWV

updated in last commit. thanks!


fix wbolster#45

file-directory-p try to initiate a connection so I moved the file-remote-p before it.

wow, nice debugging since this is non obvious 👍
while at it, any chance you can move the string-equals-p up (right after the non-nil check) so that this cheap check runs before the (potentially slower) file path checks?

Is it better now?

thanks!


Typo "Azure storage explorer"→"Azure Storage Explorer"

https://docs.microsoft.com/en-us/azure/cognitive-services/metrics-advisor/data-feeds-from-different-sources
#PingMSFTDocs

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


New version: Microsoft.AzureMonitorAgent version <IP_ADDRESS>

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Resolve #172834

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Manually validated in Windows Sandbox.


Pub Build on Windows failing to cleanup files correctly

From a Windows user - I think it's most likely to be Pub, but it is possible this is an Editor issue.
It has happened 3 times now. First build was fine, the rest haven't. Here it
goes.
Reproduced here with empty project:
Step 1. Create new project
Step 2. Tools -> Pub build  [ this is going to work ]
Step 3. Tools -> Pub build  [ this will work as well ]
Step 4. Open the html page from build/web/test.html that has been
generated in a web browser.
Step 5. Close the browser tab and exit the build folder from windows explorer
Step 6. Tools -> Pub build  [ this is going to fail ]
Details from Step 6 below:

Tools -> Pub build
Error from editor:
--- 18:13:20 Running pub build ... ---
Pub build failed, [1] Deletion failed, path =
'G:\Working\ProjectName\build'
(OS Error: The directory is not empty.
, errno = 145)
Build folder appears greyed out in Dart Editor, and still exists in
windows explorer tree, but is empty.
Trying again:
Tools -> Pub build
Error from editor:
--- 18:16:11 Running pub build ... ---
Pub build failed, [1] Exists failed, path =
'G:\ProjectName\build'
(OS Error: Access is denied.
, errno = 5)
The build folder is however deleted, both from Dart editor and from
the filesystem.
Third time's a charm. Tools -> Pub build works.

This issue has been moved to dart-lang/pub#881.


& does not call to_proc on symbol

works in ruby:
["a ", " s"].map(&:strip)

in mruby, we need to do
["a ", " s"].map(&:strip.to_proc)

This issue is already solved, isn't it?