Question: is there a way to hide a property at runtime?

I have a use case where I want to use the same form for both "add" and "update" operations using an EF model.
It works fine as long as I use the DataType attributes to set which properties to show, but what I would like to do is to set one of the property to be shown only in "add" mode and not on "update".
Is there any way to tell FormFactory that kind of information at runtime?
Thanks!

I'm answering my own question but I'm open to suggestions to improve my way, if any :)
I've modified Form.Property.cshtml to have the first few lines to look like this:
  bool IsHiddenOnEdit = false;
  var attrs = Model.GetCustomAttributes().Where(a => a.GetType().Name == "DataTypeAttribute").ToList();
  foreach(var a in attrs)
  {
    DataTypeAttribute dta = (DataTypeAttribute)a;
    if (dta.CustomDataType == "HiddenOnEdit")
    {
      IsHiddenOnEdit = true;
    }
  }
  if (Model.IsHidden || (IsHiddenOnEdit && ViewBag.EditMode == true))
  {

@Html.BestProperty(Model)

And I've annotated the propety with [DataType("HiddenOnEdit")] where needed.

Glad you managed to get it to work for you!
It would be great to create a base class, so that new attributes wouldn't have to modify the template, and could be added by users without modifying the core.
FormFactory core project:
public abstract class FormFactoryPropertyAttribute : Attribute
{
    public abstract void ApplyToProperty(PropertyVm vm);
}

Form.Property.cshtml
 foreach(var a in attrs.OfType<FormFactoryPropertyAttribute>())
  {
      a.ApplyToProperty(Model);
  }

And then in your project
class IsHiddenOnEdit : FormFactoryPropertyAttribute {

    public override void ApplyToProperty(PropertyVm vm, FfHtmlHelper htmlHelper)
    {
       if (htmlHelper.ViewData["EditMode"] as bool? ?? false)
           vm.IsHidden = true;
    }
}

```

I'll add this when I get a chance, but it might not be for a while. If you're up for the challenge, pull requests are gratefully accepted!


Update to debian:jessie to fix doc build

Python sphinx > 1.2.x is only available in jessie so I made the move.
Doc is building fine but "not found" in fauxton ...
NOTE: I'am really not sure why we keep this :  libssl0.9.8_0.9.8o-4squeeze14_amd64.deb instead of the 1.0.1 available in jessie

Thanks again! :) I'll take care of the openssl thing.


Update prose scope usage

We don't have confidence that the prose scope is well understood – without further research / better documentation it's safer to remove it for now.
This PR:

moves prose-scope into the Design System as it's being removed from Frontend
removes guidance on using it

Trello ticket
https://trello.com/c/v7tR99UO/955-remove-prose-scope

rebased with master


Integration Test - Release - 2020/06/08 17:57:23

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

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


Implement connection heartbeating.

open questions
Heartbeats are great, and are working as of this PR; however, until we implement an auto-reconnect algorithm, heartbeats are not super effective. Do we want to include an auto-reconnect implementation here as well? Or does it suffice to simply close the underlying TCP connection for now?
TODO:

[x] resolve build failure (simple issue related to openssl).
[ ] add pertinent changelog entries.
[ ] update README and docs on heartbeating. Note that a heartbeat interval of 0 disables heartbeats for the connection.
[ ] look into adding connection recovery pattern.
[ ] explore idea for removing the channel number param in Session.open_channel. Use an internal mutex for keeping track of used channels, reclaiming dropped channels, and allowing Session to be Sync so that we can follow the "channel per thread" more practically.

Should close #50.

Hey, I am interested in this change. What is the status of it?

I started resolving some of @Antti's and my comments in my fork.
https://github.com/andir/rust-amqp/commits/heartbeat
Feel free to cherry-pick them into this PR.

@andir @MicroJoe @Antti hey all, just wanted to reach out since I haven't moved on this PR for a while.
I actually ended up going with a different AMQP lib for the stuff I was hacking on at the time. I needed futures based async as opposed to threading and such.
@andir sounds like you have forked and have made some progress. That's awesome! Please feel free to open a PR which supersedes this one. I don't think I will have the time to address some of the deeper issues I was concerned with here.
@Antti feel free to close this PR whenever you would like. I'll leave it open until I hear back from @andir on what their plans are for moving forward with the fork.
Thanks all!


Fix issue with convert function when converting string to date, datetimeoffset, datetime2, datetime, smalldatetime or time

Description
This PR fixes the issues in CONVERT function for converting string to date, datetimeoffset, datetime2, datetime, smalldatetime and time.
Authored-by: Rohit Bhagat<EMAIL_ADDRESS>Signed-off-by: Rohit Bhagat<EMAIL_ADDRESS>Issues Resolved
BABEL-4896
Test Scenarios Covered

Use case based - YES

Boundary conditions - YES

Arbitrary inputs - YES

Negative test cases - YES

Minor version upgrade tests - NA

Major version upgrade tests - NA

Performance tests - NA

Tooling impact - NA

Client tests - YES

Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.01%) to 72.78%

Files with Coverage Reduction
New Missed Lines
%

contrib/babelfishpg_tsql/src/collation.c
1
84.97%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
41784

Relevant Lines:
57411

💛  - Coveralls


Encoding for IRIs/CURIEs

Overview
Need to properly adhere to this as closely as possible: https://www.w3.org/TR/REC-xml/#NT-NameChar
[4] | NameStartChar | ::= | ":" | [A-Z] | "_" | [a-z] | [#xC0-#xD6] | [#xD8-#xF6] | [#xF8-#x2FF] | [#x370-#x37D] | [#x37F-#x1FFF] | [#x200C-#x200D] | [#x2070-#x218F] | [#x2C00-#x2FEF] | [#x3001-#xD7FF] | [#xF900-#xFDCF] | [#xFDF0-#xFFFD] | [#x10000-#xEFFFF]

[4a] | NameChar | ::= | NameStartChar | "-" | "." | [0-9] | #xB7 | [#x0300-#x036F] | [#x203F-#x2040]

That is, the first character has certain allowed values, and the rest of the string has other (more lax) allowed values.
Additional info
https://robot.obolibrary.org/errors#invalid-element-error

@ShahimEssaid FYI I'm going to do a fix for a simple subset of this now. Probably will only stick to just fixing enough of these cases just to get it to run for us. But in an ideal world, I'd have it adhere to this.


Is there any computation speed comparision between NumSharp and numpy ?

Is there any computation speed comparision between NumSharp and numpy ?

Hey, unfortunately we do not have recorded benchmarks. During development I did do benchmarks and numpy always beat NumSharp by being at-least 50% faster in most of the cases. If you are targeting trading with it (time-critical computation) then I suggest you either try Numpy.NET or numpy on python.


Freehand sculpter

This PR introduces a new tool, the freehandSculpter, which can manipulate freehand ROIs. The demo speaks for itself: Click here!.
In words: One can ctrl+click an ROI and then begin editing it by holding down the mouse. A circle will appear around the mouse with a radius equal to the distance from the mouse to the nearest point on the ROI. Moving the mouse will push the edges of the ROI, creating and removing new points as needed. Releasing the mouse will complete the edit. By starting an edit with a mouse close to the edge of the ROI, fine adjustments can be made. By clicking far away/near the center of the ROI, one can make coarser, rough adjustments.
@dlwire , this PR also exposes pointNearTool for you to use!
Sorry this one took a while to get out. Its been 99% ready (and actually in use) for a while, but hadn't had time to get it up to PR standard!

P.S. This is pretty similar to Osirix's repulser tool, in that you can mess up an roi if you aren't being precise (try editing and moving the mouse around the whole screen fast). This just emphasises how good a global deleting tool (ala @dlwire suggested) would be.
I tried adding limitations to stop self-intersection, similar to what I did with the freehand tool itself, but any way I tried felt too restrictive. I think it feels better to just let the user do what they want in this case and be able to delete and start over.

Looks good! Thanks!


Added a constraint for limiting Authorized Networks in Cloud SQL

The constraint will provide the ability of specifying a whitelist for the authorized networks in Cloud SQL instances . In particular, it will also allow to specify that no authorized networks should be added, and force all connections via the Cloud SQL proxy.

Push a new set of changes. The new changes address Tony's comments, and also use CIDR functions for checking whether an authorized network is allowed.


[Question] Is ngrok / pyngrok still not valid in google colab enviroment?

I tried the colab notebook to use google colab together with my vscode environment.  Is it still banned because i failed to connect it to the notebook machine.

Hi @timtensor . Colab is not blocked on our end, could you share some additional detail about what you are trying to do and what kinds of errors/issues you are running into?

Actually i was trying to run vscode via pyngrok to run my local code in remote server. Everytime pyngrok runs, colab mentions that is not permitted and gets disconnected.

Is there a way to run vscode remotely on ngrok ?

Hi @timtensor apologies for the delayed response. So pyngrok is not an officially supported ngrok library, for that we recommend ngrok-python. However, pyngrok is using our agent under the hood, so there are a few things that could be happening:

We require that you have a valid authtoken to connect to ngrok. In the past you could connect without authenticating so this could be a reason.
We have an agent version support policy for free accounts. Pyngrok installs a very old version of ngrok by default. You might need to upgrade to a more recent version to make it work.

With respect to using VSCode and ngrok, we have a guide

@timtensor thanks for the issue. I'm going to close this as stale. if you are still having issues with running in colab, please open a new issue with updated details.


Screenshots

It`s possible to add any screenshots at readme?

Sure, of course. I will realize this soon


Enable API Doc view

Description:
Enable API Doc view in VSCode plugin.
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Removed the API Doc preview https://github.com/ballerina-platform/plugin-vscode/issues/124

Removed the API Doc preview https://github.com/ballerina-platform/plugin-vscode/issues/124


Add document/absolute_path_migrate_me_to_uri

This fixes an error returned when this value is missing:
{"code":"unknown","message":"no absolute path"}

I had a look at the values the vim plugin sends, and it seems that the value was missing here.
(see https://github.com/Exafunction/codeium.vim/blob/8c01979323b2b480c8bf160d3ff85bd1668baa49/autoload/codeium/doc.vim#L106)

 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.


Issue Please Read

Hello I have found this and think it is great but there is a big bug
When using it with a long list of usernames it will eventually start showing they are all avaliable after about maybe 20 usernames in due to instagram having a limit on how many profiles an account can search before you it gives you an error telling you you have to wait. I was wondering if you could find a work around this and if not I have a suggestion that could bypass this and wondering if you can implement it.
Hit me up on here or email:
Contact<EMAIL_ADDRESS>Thank you :)

Hmm, I haven't really looked at this code for a few years so if I were to fix it I would probably re-write it.
I will post back here if I decide to do this but in the meantime, you can use proxies to avoid this error.


Content changes locations

remove some repetition of 'current cycle', 'next cycle' etc.
make definitions of 'placement schools' and 'training centres' into actions
make the choice between showing 'precise locations' and 'general areas' really clear by using these terms

Thanks @EmmaFrith!


Convert python structures to json

This request has been added to update our metadata sidecar file payload (in warc_metadata_sidecar.py). Since the payload for these files are changing, we also had to update the script (sidecar2cdxj.py) that takes in these files. What is changing are the values in the payload. We are changing them to json strings.

@ldko @somexpert This is ready for review.


Menus: submenus should not close when mouse moves out of them

Refs: #52854
Steps:

epxand a submenu
move the mouse somewhere outside that menu
the submenu closes

This makes it very hard to actually move the mouse into a submenu to select something

Agreed. I think it makes more sense to hide the submenu when you move mouse on other items above/below Editor Layout in the main menu.

I think the new behavior from https://github.com/Microsoft/vscode/commit/069a812bd723606d1bf4940ca9425dde6cd2a7bb and some extra polish that came later has addressed the spirit of this issue.


New Domains Added By Nandu (i am back)

All domains had gone through Google Transparency Check and shows that they are unsafe.
Except 2 domains which still had sketchy redirects to unsafe websites.

By The way all the domain extention are starting by letter A
I will probably will make a another pull request by the domain extention starting with letter B tommorow

Can you provide a proof of those domains + the source where you got it from?

Also those are just discord.sometld domains? I mean sure list every possible TLD and append it to discord. ?

Can you provide a proof of those domains + the source where you got it from?

I take up the list of the TDLs from ![here] (https://www.domain.com/domains/new-domain-extensions)
And manually go to the domains if my browser shows like this

Then I add it to the list (if it shows like that it means that it has failed the Google Transparency Check)


From widget pages cannot add link to custom pages

I cannot add link to custom page from widget pages. E.g., in the experience widget, I want to show only 2 recent experiences and add link to full experience, but that's not possible.

Yes, lets say this works, e.g.  [Another section]({{< relref "experience.md" >}}).  But I put experience.md in content, it doesn't work. I put it in the folder experience with index.md inside it doesn't work either. I put that folder inside home folder and it again doesn't work. (Page not found).

@milanm recently, Hugo changed the way references work. Without seeing your repo, it sounds like you may now need to prefix your path with a slash when using ref, e.g. "/experience/index.md". For further help, please post this on the support forums with a link to your website repo.

I tried with that but stil get 404 page not found. Tried with putting experience.md in the root of the content folder with link "/experience.md", still the same. O.K. Thanks, will ask.

@gcushen Just, I still think this is Academic bug. As this link works:
[Full education and certificates >>]({{< ref "/education/index.md" >}})
but this not:
[Full experience >>]({{< ref "/experience/index.md" >}})
and both directories/files exists on the disk.


Add TypeScript Definition for Vue

SimpleBar's mission statement is to keep things simple and stick to the native scroll behaviour as much as possible. However if you have a suggestion that falls within this approach that hasn't already been proposed, we'd love to hear it!
Is your feature request related to a problem? Please describe.
I see that the React version has TS definitions, but the Vue version does not. Is there scope to add them? I've created my own definition file, but it's a little lacking comparatively to the React version
Describe the solution you'd like
A TS definition for the Vue library
Describe alternatives you've considered
I've created my own TS definition, which works well enough, but I think it would be useful for everyone if there were a definition included in the lib.
Additional context
This is my implementation for anyone that ends up here
declare module 'simplebar-vue' {
    import Vue from 'vue';
    import SimpleBar from 'simplebar';

    export class SimpleBarComponent extends Vue {
        SimpleBar: SimpleBar;
        contentElement: HTMLDivElement;
        scrollElement: HTMLDivElement;
    }

    export default SimpleBarComponent;
}

Released in<EMAIL_ADDRESS>


[Bug] Find Unique: Query engine exited with code 255 - Could not canonicalize path dir

Bug description
I recently updated from prisma 2.9.0 to 2.14.0 and I am now seeing the following error when using findUnique
app | 2021-01-14 17:15:54 22:15:54.928Z ERROR App-Backend:
app | 2021-01-14 17:15:54   Query engine exited with code 255
app | 2021-01-14 17:15:54   PANIC in /root/.cargo/registry/src/github.com-1ecc6299db9ec823/tide-0.15.0/src/listener/unix_listener.rs:152:22
app | 2021-01-14 17:15:54   Could not canonicalize path dir
app | 2021-01-14 17:15:54   --
app | 2021-01-14 17:15:54   Error: Query engine exited with code 255
app | 2021-01-14 17:15:54   PANIC in /root/.cargo/registry/src/github.com-1ecc6299db9ec823/tide-0.15.0/src/listener/unix_listener.rs:152:22
app | 2021-01-14 17:15:54   Could not canonicalize path dir
app | 2021-01-14 17:15:54       at PrismaClientFetcher.request (/app/backend/node_modules/@prisma/client/runtime/index.js:78136:15)
app | 2021-01-14 17:15:54       at processTicksAndRejections (internal/process/task_queues.js:97:5)

Any idea what is happening here? This doesn’t seem to happen to me locally on my macbook but does occur when on my alpine linux docker container
I am planning on turning on the debug env var and getting more log data as well as update the version from 2.9.0 -> 2.10.0 etc to determine which version broke the build.
How to reproduce
Run a Node.js Alpine docker container (see dockerfile below) and attempt to use the findUnique command.

Environment & setup

OS: Alpine Linux
Database: PostgreSQL
Node.js version: 12
Prisma version: v2.14.0

@pantharshit00 This seems to have been fixed when I updated to v2.15. Thanks
Not sure how to get my host operating system but when running  cat /etc/os-release I get this
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.11.7
PRETTY_NAME="Alpine Linux v3.11"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://bugs.alpinelinux.org/"

@pantharshit00 This seems to have been fixed when I updated to v2.15. Thanks
Not sure how to get my host operating system but when running  cat /etc/os-release I get this
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.11.7
PRETTY_NAME="Alpine Linux v3.11"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://bugs.alpinelinux.org/"

I am going to close this for now as we have closed the other UDS related issues in 2.15.
By "host" I mean which OS your machine is running which is running the docker image and not the OS of the docker image.

I am going to close this for now as we have closed the other UDS related issues in 2.15.
By "host" I mean which OS your machine is running which is running the docker image and not the OS of the docker image.

Any updates on this issue? I struggling the same right now. I would appreciate any help.

@zwanzigg This is should not happen in the latest version. If you experiencing this on the latest version, please share a reproduction.


Plasma exit events

changes

Subgraphs for catching :arrow_down: events, emitted during Plasma Exit

ExitStarted
ExitCancelled
ExitUpdated
Withdraw

Requested changes implemented @jdkanani .
Also added more fields ( timestamp, txHash ) in entities.
Not sure what to do with TokenMapped event, due to the fact tokens can be remapped, in that case what to use as id for graphQL entity, so that we get to update old entry. We need to have two way one - to - one mapping for this.

@jdkanani interested in learning about your opinion for last point.

@jdkanani added subgraph for tracking token mapping events.

@itzmeanjan Is it working locally?


hugo command usage in bibtext import does not check cmd return

Usage of hugo with subprocess should ideally wait for process completion and check for errors. This would eliminate the sleep cruft there too.
https://github.com/wowchemy/hugo-academic-cli/blob/93acb29fd7833d3932868bf96875f284a4dabcb5/academic/import_bibtex.py#L80-L82
Currently when the hugo command fails to create the index.md (if hugo isn't installed for example) an error without this needed info is thrown: FileNotFoundError: [Errno 2] No such file or directory: 'content/publication/.../index.md'.
It would be better to show the error from the hugo subprocess:
[tylar@tylar-pc www_marinebon2]$ python
Python 3.8.3 (default, May 17 2020, 18:15:42)
[GCC 10.1.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import subprocess
>>> subprocess.call(f"{hugo} new {markdown_path} --kind publication", shell=True)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'hugo' is not defined

Oh... weird. subprocess.call is supposed to wait for completion and throw errors. Not sure what is happening here.

I have done some experiments to better understand how subprocess.run behaves with different options and errors. It is not yet clear to me how to fix this issue, however. My best guess at this point is to remove shell=True. But will that break something?

no close please, mr bot.


chore: bake inso-cli on older macos [INS-3931]

Closes INS-3931
Tested in https://github.com/Kong/insomnia/releases/tag/v9.3.0-alpha.0-experimental
Related pr - https://github.com/Kong/insomnia/pull/7469

@jackkav

this one would make an additional inso-cli artifact
macos-13 is its own build, macos-latest is currently macos-14 (which runs on Apple sillicon)
ubuntu - we could do it for Insomnia.app in a separate PR perhaps

Is there a reason it needs to also run the macos-14 build? Its not good to support multiple builds when one will suffice. Makes things less intuitive.

@jackkav we can make it macos-13 only as its better for compatibility


Newsflash none only

@carmelp16 please fix pylint test

Other than that looks good :) @ziv17 any thoughts?

The insert_new_newsflash() is not needed any more, together with the cache per news_flash. We only use infographics per location now. I will remove it in a future PR.

Other than that looks good :) @ziv17 any thoughts?

Very nice. Elegant test!


Repalce OdspDocumentInfo with OdspFluidDataStoreLocator

Overview
The OdspDocumentInfo type has to be replaced with OdspFluidDataStoreLocator interface.
Proposed Solution
There are no known instances of these OdspDocumentInfo type being used in the internal repositories searched (FluidExamples, Bohemia, OneNote). Bohemia uses OdspFluidDataStoreLocator interface. Therefore, the type declarations can simply be removed from the FluidFramework repository.
Methodology
The OdspDocumentInfo type will be removed in the following files:

packages\drivers\odsp-driver\src\contractsPublic.ts
packages\drivers\odsp-driver\src\odspDriverUrlResolverForShareLink.ts

Currently, OdspDocumentInfo is used as the type of a parameter to OdspDriverUrlResolverForShareLink.createDocumentUrl().  Is the plan to remove that function entirely (preferable if we can, and I don't see any usage currently)?  Or change the param type to OdspFluidDataStoreLocator?
@jatgarg might want to take a look too.

It looks like those types are aliased so it would probably be fine just to replace it there.  Then as usual, please make sure to add an entry in the BREAKING.md with info on the change, the affected packages, and how to migrate from the old type to the new type

Currently, OdspDocumentInfo is used as the type of a parameter to OdspDriverUrlResolverForShareLink.createDocumentUrl(). Is the plan to remove that function entirely (preferable if we can, and I don't see any usage currently)? Or change the param type to OdspFluidDataStoreLocator?
@jatgarg might want to take a look too.

I was planning on changing the param to OdspFluidDataStoreLocator. Please let me know your thoughts.

Yes we can remove it and put that info in Breaking.md. It was already deprecated:
/**

@deprecated - use OdspFluidDataStoreLocator
*/
export type OdspDocumentInfo = OdspFluidDataStoreLocator;


Make ADAMContext and JavaADAMContext constructors public

Fixes #1296
This came up again when I was making code style fixes to adam-apis (e.g. https://github.com/bigdatagenomics/adam/blob/master/adam-apis/src/test/java/org/bdgenomics/adam/apis/java/JavaADAMAnnotationConduit.java#L44).

lgtm

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1655/
Test PASSed.

Merged! Thanks @heuermh!


Dynamic attrs in factories (functions) are called twice

This arose while doing this:
Factory.extend({
  id() {
    return autoincrementalIdSharedBySeveralModels();
  }
});

This code generates ids [2, 4, 6, 8, 10] etc...
I dig a bit into why this happens and it's because mirage allows functions to be called out of order. By example, the next code is allowed:
  let BazFactory = Mirage.Factory.extend({
    bar() {
      return this.foo + 2; // This function calls foo as a property despite of being a function
    },

    baz: 6,

    foo(i) {
      return this.baz * i;
    }
  });

To allow this mirage has to evaluate the functions twice, once to generate a Directed Acyclic Graph to know the exection order and the second to actually call them in order.
It's not easy to fix, but I think that if there functions were defined using getters/setters, none of this would be needed. However this outcome seems so obvious and the current solution so unintuitive that It makes me think that there is a reason I don't see why things are the way they are.
Was it because of IE8 support? Other?

Someone else implemented the graph code here and I haven't looked at it in a while. The change was made to allow dynamic factory attrs, like in your example (bar depends on foo so foo needs to be calculated first). It's basically a lightweight computed property system.
When you say they're called twice you're saying the array should be [1, 2, 3, 4]? Also I'm not clear what you mean by using getters - are you referring to the code internal to Mirage's factory?

Yes, the generated sequence should be [1,2,3,4], but since for every server.create invocation the functions are called twice (the first time the result is discarded, it's just to figure out the execution order), the generated values are [2, 4, 6, 8].
By using getters I mean that functions are stored as getters in the factory.
By user a getters, there is no need of swiping the attribute definitions twice, one to create the dependency graph and another to get the actual values. Since getter functions can access another getters, the dependency graph is implicit. Circular dependencies wouldn't be supported, but neither are now.

I see.
Guarav just made an update to the factory - I wonder if it addressed the issue? And if not, I could use some help to re-work the system the way you describe. Maybe when you (or anyone else!) has some time?

I'm in the middle of a secret project that I'd like to release this week in ember-fest, so I don't foreseen having enough time in the next 2 weeks, but I'll try to get back to this, maybe during office ours.

I verified the behavior and agree it's confusing. I think at this point the path forward of changing the API to use getters instead of functions is a big enough change that it should be considered alongside other plans to change Mirage classes over to vanilla ES6 classes.
For now I'm going to mark this as a feature request, and we can come back to it when we move the rest of the objects over to ES6.


In Android, the bottom sheet opens behind a Shell modal page

Suppose a Shell page with PresentationMode=Modal. If I open a bottomsheet from this page, then it does not show on top of the modal page. Instead, i have to close the modal page and then the bottom sheet is displayed.
Expected behavior:
Bottom sheet opens on top of Shell Modal page.
iOS works fine

Hi,
Can you confirm which version you noticed this?
I have just tested on the latest version and cannot reproduce

I reproduce an issue similar : bottom sheet appear behind a modal page push modal page push bottom sheet.
On iOS the bottom sheet appear in front of all page correctly.

same issue here.

Tried rc5 and noticed this on android.
To reproduce: Create a new ContentPage and in its constructor set the shell presentation mode to modal:
Shell.SetPresentationMode(this, PresentationMode.Modal); // this is the page
or in xaml: Shell.PresentationMode="Modal"
Then make the modal page half transparent: BackgroundColor = new Color(255, 0, 0, 128); and from the page, trigger a bottom sheet to show up. You will see that it shows up behind the red tint.
By the way in rc2 the bottomSheet.Show() still worked when called from the OnNavigatedTo event of the page. Now with rc5 it does not work anymore, except with a Task.Delay() before calling bottomSheet.ShowAsync().
Do you have any recommendations on how to most reliably trigger a bottom sheet when entering a page?

I have release rc6. In this release, I attach the BottomSheet to the Window of the Android Activity instead of adding it to the navigation manager's root.
This should ensure an open BottomSheet stays on top of pages inside the navigation view.
Please try it out and let me know if that solves it

unfortunately no improvement on my side,
the bottom sheet is always displayed behind the modals
cf my video ...
https://github.com/the49ltd/The49.Maui.BottomSheet/assets/37982988/2d3556fb-af01-4d56-a6f6-4936f22d387d

I have pushed some changed to a branch called window. It rewrites a bunch of Android logic, so I'll hold off on making a release just yet.
I've tested the modal pages scenario and it works locally. If anyone here could give it a go and feedback it would be greatly appreciated.

@paulvarache  it's works fine !
Can you merge this branch ?

I just have pushed 1.0.0-rc8 with that fix in


feat: Add more slice methods to the stdlib

Description
Problem*
Summary*
Adds filter and join for slices to the stdlib along with the new Append trait to abstract over joining types.
Additional Context
These are methods I found would be useful while working on metaprogramming
Documentation*
Check one:

[ ] No documentation needed.
[x] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

I'm not entirely sure why we need this Append trait over just adding an append method to the Quoted type tbh.

@TomAFrench it can be useful in some cases to abstract over it. Monoid a isn't the most common constraint in Haskell for example but it's one of the somewhat more common / well known ones I think. Not really a game changer or anything, just figured I'd add it for completeness. I thought it'd be more useful since slices implement it as well but we don't allow nested slices so it isn't as useful there. I suppose you could still join/concat/append an array of slices together.


Avoid running the HACS action in forks, because forks don't have releases

Forks don't have releases. If a pull request is created from another repo avoid running the HACS action because it will always fail.

coverage: 99.901%. remained the same
when pulling 989b5eb8f88bd6cb72a9abc0a043cbf5e58df2ba on elchininet-patch-1
into 4b246c5211fd5bd6df05e322b385514e09f961c0 on master.


0.5 Support

Updates dioxus-charts to use Dioxus 0.5
Closes #5

It's not the cleanest it could be (and there are probably tons of better ways to do stuff) but it has support for 0.5 now.

Can't find a request review button so I'll do this: @marc2332

Ah wait, I need to run some commands, let me try

All good!


switch to semantic release and semantic commit messages

https://www.conventionalcommits.org/en/v1.0.0/
https://semantic-release.gitbook.io/semantic-release/

resolved by 3ceebb464166b7e7bb2e7a720a7d975ff9b5b920


[i2c] Controller mode cleanup of NACK handling and transaction boundaries

Consolidate NACK handling events into a single "controller halt" status
interrupt. The event bits in the CONTROLLER_EVENTS CSR combine to drive
the interrupt. Clear the bits to acknowledge the interrupt.
Change up the NACK handling to finish the current byte, force transition
to the Idle state, and hold there, as well as beginning the timeout
counter's incrementing there. SCL will be held low if the transaction
was not stopped already.
Track automatic Stop generation to eliminate races with software, since
changes to the control bits could occur while the Stop symbol was being
generated, leading to a transition to the PopFmtFifo state and the
discarding of an unused FMT FIFO entry. Proceed directly to Idle if the
current Stop symbol was automatically generated.

Thanks for making these changes! I find this PR a bit difficult to review because of a few reasons:

Autogenerated files are mixed in with functional changes.

Note that the autogenerated changes are related and should be in the same commit for atomicity. You don't generally have to look at files like interfaces.md, registers.md, _reg_top.sv, and _reg_pkg.sv, though, unless you have reason to suspect the reggen output, hehe.

Reorganizational changes are mixed in with functional changes. (For example implementing the unhandled NACK counter and moving the unexpected NACK.)

Sorry about that, but recent commits ignored the file's stated structure. One always block was supposed to be only about the state transition (my bad for not catching it on review!). This PR redoes how those NACK features work, in the file's stated style.
The current file structure doesn't follow our coding guidelines, and I think you have the same complaints I do: It's hard to read! We ought to collapse the two always blocks down to one, so state transitions are present in the same screen as state outputs. However, I won't do that until at least after I finish cleaning the DV regressions, so we can rely on them again to tell us if we have broken something.


configurable Access-Control-Allow-Origin

Since v1.0, Access-Control-Allow-Origin header in server responses is *. This has benefits:

We can make complex Web portals that use jsonmon to integrate
We're able to test the UI in development

We may want to make this configurable as not everyone wants this. Maybe we should even set the new default to no such header (and have some environment variable to specify it's value if we really need this), but not really sure about it now.

thought it again and will close it for now. I really doubt this will change anything in real life and will only complicate the code.


engine: Volumes stuck in termination stage

Version:
0.3-rc5
➜ kubectl -n longhorn-system delete volumes.longhorn.rancher.io --all

volume.longhorn.rancher.io "pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c" deleted
volume.longhorn.rancher.io "pvc-c93a8048-a6d7-11e8-a416-de2b4c2c400c" deleted

➜  kubectl -n longhorn-system delete volumes.longhorn.rancher.io --all

volume.longhorn.rancher.io "pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c" deleted
volume.longhorn.rancher.io "pvc-c93a8048-a6d7-11e8-a416-de2b4c2c400c" deleted

➜  kubectl -n longhorn-system describe volumes.longhorn.rancher.io

Name:         pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c
Namespace:    longhorn-system
Labels:       longhornvolume=pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c
Annotations:  <none>
API Version:  longhorn.rancher.io/v1alpha1
Kind:         Volume
Metadata:
  Creation Timestamp:             2018-08-23T13:15:47Z
  Deletion Grace Period Seconds:  0
  Deletion Timestamp:             2018-08-24T06:34:56Z
  Finalizers:
    longhorn.rancher.io
  Generation:        2
  Resource Version:  1048348
  Self Link:         /apis/longhorn.rancher.io/v1alpha1/namespaces/longhorn-system/volumes/pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c
  UID:               a5fd3fd9-a6d6-11e8-bb2a-de2b4c33000b
Spec:
  Base Image:
  Engine Image:        rancher/longhorn-engine:v0.3-rc5
  From Backup:
  Frontend:            blockdev
  Migration Node ID:
  Node ID:
  Number Of Replicas:  3
  Owner ID:            scw-4gb-ams1-node3
  Recurring Jobs:
    Cron:                 00 00 * * *
    Name:                 c-v53b7q
    Retain:               14
    Task:                 backup
  Size:<PHONE_NUMBER>
  Stale Replica Timeout:  30
Status:
  Conditions:
    Scheduled:
      Last Probe Time:
      Last Transition Time:  2018-08-23T13:15:48Z
      Message:
      Reason:
      Status:                True
      Type:                  scheduled
  Current Image:             rancher/longhorn-engine:v0.3-rc5
  Robustness:                unknown
  State:                     detached
Events:                      <none>

Name:         pvc-c93a8048-a6d7-11e8-a416-de2b4c2c400c
Namespace:    longhorn-system
Labels:       longhornvolume=pvc-c93a8048-a6d7-11e8-a416-de2b4c2c400c
Annotations:  <none>
API Version:  longhorn.rancher.io/v1alpha1
Kind:         Volume
Metadata:
  Creation Timestamp:             2018-08-23T13:24:02Z
  Deletion Grace Period Seconds:  0
  Deletion Timestamp:             2018-08-24T06:34:56Z
  Finalizers:
    longhorn.rancher.io
  Generation:        2
  Resource Version:  1048349
  Self Link:         /apis/longhorn.rancher.io/v1alpha1/namespaces/longhorn-system/volumes/pvc-c93a8048-a6d7-11e8-a416-de2b4c2c400c
  UID:               cd1bb1c6-a6d7-11e8-bb2a-de2b4c33000b
Spec:
  Base Image:
  Engine Image:        rancher/longhorn-engine:v0.3-rc5
  From Backup:
  Frontend:            blockdev
  Migration Node ID:
  Node ID:
  Number Of Replicas:  3
  Owner ID:            scw-4gb-ams1-node3
  Recurring Jobs:
    Cron:                 0 0 * * *
    Name:                 c-npgks9
    Retain:               5
    Task:                 backup
  Size:<PHONE_NUMBER>
  Stale Replica Timeout:  30
Status:
  Conditions:
    Scheduled:
      Last Probe Time:
      Last Transition Time:  2018-08-23T13:24:04Z
      Message:
      Reason:
      Status:                True
      Type:                  scheduled
  Current Image:             rancher/longhorn-engine:v0.3-rc5
  Robustness:                unknown
  State:                     detached
Events:                      <none>

➜  kubectl -n longhorn-system delete volumes.longhorn.rancher.io --all

volume.longhorn.rancher.io "pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c" deleted
volume.longhorn.rancher.io "pvc-c93a8048-a6d7-11e8-a416-de2b4c2c400c" deleted

I've tried even deleting longhorn, but now namespace stuck on deletion.
For thouse of you, who's having same issue.  This is how you can fix it:
➜  kubectl -n longhorn-system get volumes.longhorn.rancher.io pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c -o json > tt.json

{
    "apiVersion": "longhorn.rancher.io/v1alpha1",
    "kind": "Volume",
    "metadata": {
        "creationTimestamp": "2018-08-23T13:15:47Z",
        "deletionGracePeriodSeconds": 0,
        "deletionTimestamp": "2018-08-24T06:37:02Z",
        "finalizers": [
            "longhorn.rancher.io" .      <-- REMOVE THIS LINE
        ],
        "generation": 2,
        "labels": {
            "longhornvolume": "pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c"
        },
        "name": "pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c",
        "namespace": "longhorn-system",
        "resourceVersion": "1048713",
        "selfLink": "/apis/longhorn.rancher.io/v1alpha1/namespaces/longhorn-system/volumes/pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c",
        "uid": "a5fd3fd9-a6d6-11e8-bb2a-de2b4c33000b"
    },
    "spec": {
        "baseImage": "",
        "engineImage": "rancher/longhorn-engine:v0.3-rc5",
        "fromBackup": "",
        "frontend": "blockdev",
        "migrationNodeID": "",
        "nodeID": "",
        "numberOfReplicas": 3,
        "ownerID": "scw-4gb-ams1-node3",
        "recurringJobs": [
            {
                "cron": "00 00 * * *",
                "name": "c-v53b7q",
                "retain": 14,
                "task": "backup"
            }
        ],
        "size": "5368709120",
        "staleReplicaTimeout": 30
    },
    "status": {
        "conditions": {
            "scheduled": {
                "lastProbeTime": "",
                "lastTransitionTime": "2018-08-23T13:15:48Z",
                "message": "",
                "reason": "",
                "status": "True",
                "type": "scheduled"
            }
        },
        "currentImage": "rancher/longhorn-engine:v0.3-rc5",
        "robustness": "unknown",
        "state": "detached"
    }
}

Save it to new file, then push it back into that volume:
curl -H "Content-Type: application/json" -X PUT --data-binary @tt.json http://<IP_ADDRESS>:8001/apis/longhorn.rancher.io/v1alpha1/namespaces/longhorn-system/volumes/pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c

I have to do it couple time, when volume finally gets deleted.
➜  kubectl -n longhorn-system get volumes.longhorn.rancher.io
No resources found.

➜  kubectl -n longhorn-system get engines.longhorn.rancher.io
NAME                                                  AGE
pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c-e-f5b48ed0   17h
pvc-c93a8048-a6d7-11e8-a416-de2b4c2c400c-e-9ee1829c   17h

➜  kubectl -n longhorn-system get replicas.longhorn.rancher.io
NAME                                                  AGE
pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c-r-333b1c13   15h
pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c-r-b880e025   17h
pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c-r-c0db5c25   15h
pvc-c93a8048-a6d7-11e8-a416-de2b4c2c400c-r-4a31b2bb   15h
pvc-c93a8048-a6d7-11e8-a416-de2b4c2c400c-r-dc68ec61   17h
pvc-c93a8048-a6d7-11e8-a416-de2b4c2c400c-r-fb03d09a   15h

Longhorn manager in mean time doing this:
E0824 06:49:23.913824 1 reflector.go:205] github.com/rancher/longhorn-manager/vendor/k8s.io/client-go/informers/factory.go:87: Failed to list *v1.Job: Unauthorized
E0824 06:49:23.938584 1 reflector.go:205] github.com/rancher/longhorn-manager/vendor/k8s.io/client-go/informers/factory.go:87: Failed to list *v1beta1.CronJob: Unauthorized
E0824 06:49:23.980517 1 reflector.go:205] github.com/rancher/longhorn-manager/vendor/k8s.io/client-go/informers/factory.go:87: Failed to list *v1.Pod: Unauthorized
E0824 06:49:23.983570 1 reflector.go:205] github.com/rancher/longhorn-manager/k8s/pkg/client/informers/externalversions/factory.go:74: Failed to list *v1alpha1.EngineImage: Unauthorized
E0824 06:49:24.008624 1 reflector.go:205] github.com/rancher/longhorn-manager/vendor/k8s.io/client-go/informers/factory.go:87: Failed to list *v1beta2.DaemonSet: Unauthorized

Even after all this magic, all 3 volumes still present and stuck:
{
"accessModes": [
"ReadWriteOnce"
],
"annotations": {
"pv.kubernetes.io/provisioned-by": "rancher.io/longhorn"
},
"awsElasticBlockStore": null,
"azureDisk": null,
"azureFile": null,
"capacity": {
"storage": "5Gi"
},
"cephfs": null,
"cinder": null,
"claimRef": {
"apiVersion": "v1",
"kind": "PersistentVolumeClaim",
"name": "grafana-grafana",
"namespace": "monitoring",
"resourceVersion": "860054",
"type": "/v3/cluster/schemas/objectReference",
"uid": "a12f7630-a6d6-11e8-a416-de2b4c2c400c"
},
"created": "2018-08-23T13:15:47Z",
"creatorId": null,
"csi": {
"driver": "io.rancher.longhorn",
"readOnly": false,
"type": "/v3/cluster/schemas/csiPersistentVolumeSource",
"volumeAttributes": {
"fromBackup": "",
"numberOfReplicas": "3",
"staleReplicaTimeout": "30",
"storage.kubernetes.io/csiProvisionerIdentity": "1535025566987-8081-rancher.io/longhorn"
},
"volumeHandle": "pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c"
},
"fc": null,
"flexVolume": null,
"flocker": null,
"gcePersistentDisk": null,
"glusterfs": null,
"hostPath": null,
"iscsi": null,
"local": null,
"mountOptions": [ ],
"name": "pvc-a12f7630-a6d6-11e8-a416-de2b4c2c400c",
"nfs": null,
"nodeAffinity": null,
"ownerReferences": [ ],
"persistentVolumeReclaimPolicy": "Delete",
"photonPersistentDisk": null,
"portworxVolume": null,
"quobyte": null,
"rbd": null,
"removed": "2018-08-23T23:08:46Z",
"scaleIO": null,
"state": "removing",
"status": {
"phase": "Released",
"type": "/v3/cluster/schemas/persistentVolumeStatus"
},
"storageos": null,
"transitioning": "error",
"transitioningMessage": "waiting on external-attacher/io-rancher-longhorn",
"uuid": "a61544de-a6d6-11e8-a416-de2b4c2c400c",
"vsphereVolume": null
}

I've deleted previous longhorn install (which was stuck on deleting) and installed it once again. It did start, 2 nodes of 5 keep crashing. In a couple hours all nodes appear to have issues with permission. It may be not related to the stuck issue (I think kubernetes deleted roles)

@stiks If there is not enough permission for Longhorn to operate on Kubernetes resources, it won't be able to clean up the resource when volumes are deleted. We've put finalizer in the Kubernetes objects to make sure it was cleaned up properly before removed. That's why the deleted volume won't disappear, because managers cannot clean up after it without Kubernetes permission.

@stiks Also, since there are finalizers in place for resource cleanup, you would need to follow the uninstall instruction to delete the Longhorn, otherwise, it won't be able to complete deletion correct (get stuck).
Though we should mention that you need to delete PVC/PV in the Kubernetes first, before cleanup the Longhorn. I will update the uninstall instruction.

I did delete all PVC before. This is what I did.
I've replaced 2 nodes in the cluster. Added few extra disks. Longhorn kept previous nodes in the list even they no longer exist in the cluster. 3 PVC I have had on these nodes has been moved to new instances, but I have had issues with them. I've decided to redo them. This is where volumes get stuck, I cannot longer delete them. Even when I did all that magic with finalizers, PVC has been stuck and don't want to be deleted. I tried deleting longhorn, but that didn't helped

@stiks Sometime Kubernetes is stubborn...
Longhorn is definitely not in a working state in your system right now. Can you try to reinstall it using the latest instruction? I think PVC is trying to communicate with Longhorn but cannot find it, so it's stuck there. And previously because Longhorn somehow lost the permission to work with Kubenetes, so it cannot work. That's maybe why PVC stuck in the first place.

Yeah, in the end, so many things were stuck, couldn't move anywhere. I've to rebuild cluster. Now I'm on 0.3, will let you know if there'll be any issues with setup.

I reproduced this issue on my Rancher Cluster - the volumes were in Terminating state.

pvc-1822b0b0e53f11e8                       10Gi       RWO            Delete           Terminating   volume-test/pvc-6gflk           sc-4n6v6                    3d
pvc-1f7ac678e54711e8                       5Gi        RWO            Delete           Terminating   default/pvc-vbdpj                     sc-4n6v6                    3d
pvc-21581baa-e08b-11e8-aca0-000c2937d4e3   10Gi       RWO            Delete           Terminating   volume-test/volume-test   longhorn                    3d

I was able to delete volumes from Rancher interface by editing PVC  with kubectl and deleting following finalizer section from yaml for above PVC's. I hope it will help you with your cases.

@ppotaki Yeah, remove finalizer would work but it may result in leftover data on the node. How did you get into this state? If you deleted the Longhorn before the volumes, it will behave like this.
Now you can follow the uninstallation instructions here to uninstall Longhorn properly.

Same problem. I have created a new issue so people can find the issue faster:
https://github.com/longhorn/longhorn/issues/722
I have not found a solution yet. I followed the uninstallation instructions here to uninstall Longhorn properly.
Related issue:
https://github.com/longhorn/longhorn/issues/344

I had to remove the finalizers using rancher kubectl console because even if the PVs were deleted from GKE they still were present in rancher, so I guess rancher has an internal cache and was not able to sync state with GKE.
https://github.com/longhorn/longhorn/issues/722

@josecelano I think GKE is the problem (and has the cache). Rancher reads all the information from kubectl which is a standard Kubernetes interface to the Kubernetes API. Rancher didn't control the result of kubectl. If kubectl say the PV still exists but GKE think it's gone, then GKE is wrong.


(Bug) (Easy) Button Size

The moment right before the window size makes the UI change for phone sizes there is a small bug where the text + image are bigger than the button and they overlap it.
To recreate simple adjust your window size slowly to the point right before the UI change.

What browser are you using? I'm getting slightly different behavior where only the challenges appears on two lines

Chrome, I can do the same thing. I was playing around with it and was able to do both.

oh interesting, it's just a width of window based thing? Because I tried decreasing the width 1 pixel at a time and never got both overflowing.

@leeschumacher this issue could be probably closed/resolved


C program for substring recurssion

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
Yes
(Write your answer here.)
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#1086

There was a mistake in this PR and so I had to close it. It would be great if you could assign it the "invalid" tag or otherwise it will affect the number of PRs in my hackoctoberfest profile. Thanks!


support arm64 architecture

I build jruby dockerfile to support arm64 from arm64v8/openjdk:8-jdk and arm64v8/openjdk:8-jre-alpine success,but I don't know this file https://s3.amazonaws.com/jruby.org/downloads/<IP_ADDRESS>/jruby-bin-<IP_ADDRESS>.tar.gz -o /tmp/jruby.tar.gz whether or not support arm64 architecture. so I need some message about support arm64 architecture.

Thanks this is supported now using docker's multi-arch image support.


Backward compatibility

Fix for old WLED versions like 0.13
I have one and can't update it to latest one, so, it will help to prevent fatal error and Homebridge constant restart.

Thanks for supporting this plugin. I will do the review this weekend.


Add recipe to add final modifier to private fields

There is currently a FinalizeLocalVariables recipe but nothing for private fields. I think that would be nice to have, as currently the RenamePrivateFieldsToCamelCase will otherwise end up renaming corresponding SCREAMING_SNAKE_CASE fields (probably intended as final fields) to camel case. Many such examples can be found in the Netflix/astyanax repository. So this recipe should be added to org.openrewrite.java.cleanup.CommonStaticAnalysis before the RenamePrivateFieldsToCamelCase recipe.
Maybe it would also make sense with an option to rename the fields to SCREAMING_SNAKE_CASE.

@kunli2 Thanks a lot for the fix! I tested the recipe and found one false positive case, where the final modifier is added although it shouldn't. If the field is reassigned from some context using the this keyword:
    @Test
    void fieldReassignedByAMethodUsingThis() {
        rewriteRun(
          java(
            """
              class A {
                  private String name = "ABC";

                  void func() {
                      this.name = "XYZ";
                  }

                  String getName() {
                      return name;
                  }
              }
              """
          )
        );
    }

One small improvement would also be to check if all constructors (directly or indirectly via this()) assign a given private field and in that case also add the final modifier. Here a few tests for that (probably overlapping with some of the existing tests):
    @Test
    void fieldAssignedInConstructorViaThis() {
        rewriteRun(
          java(
            """
              class A {
                  private String name;

                  A() {
                    this.name = "XYZ";
                  }
              }
              """,
            """
              class A {
                  private final String name;

                  A() {
                    this.name = "XYZ";
                  }
              }
              """
          )
        );
    }

    @Test
    void fieldAssignedInAllAlternateConstructors() {
        rewriteRun(
          java(
            """
              class A {
                  private String name;

                  A() {
                    name = "XYZ";
                  }
                  A(String n) {
                    name = n;
                  }
              }
              """,
            """
              class A {
                  private final String name;

                  A() {
                    name = "XYZ";
                  }
                  A(String n) {
                    name = n;
                  }
              }
              """
          )
        );
    }

    @Test
    void fieldAssignedIndirectlyInAllAlternateConstructors() {
        rewriteRun(
          java(
            """
              class A {
                  private String name;

                  A() {
                    this(name);
                  }
                  A(String name) {
                    this.name = name;
                  }
              }
              """,
            """
              class A {
                  private final String name;

                  A() {
                    this(name);
                  }
                  A(String name) {
                    this.name = name;
                  }
              }
              """
          )
        );
    }

Let me know if you would like me to create a separate enhancement issue for this.
Finally, I think it would be very nice if this recipe could be added to org.openrewrite.java.cleanup.CommonStaticAnalysis (in rewrite-java/src/main/resources/META-INF/rewrite/static-analysis-cleanup.yml) somewhere before RenamePrivateFieldsToCamelCase, so that this new recipe gets a chance to add the final modifier to private static fields which were intended as final, before RenamePrivateFieldsToCamelCase converts them to camel case.

Hi @knutwannheden, great findings.
I will make a fix to the case of an assignment using the this keyword.
I will also try to make an enhancement to cover multi-constructor cases, the last test case you provide would be a challenge, will think about it.

Sounds great! Not having any false positives is of course the primary concern, so covering multiple constructors could then maybe be addressed with a separate issue. The this logic should also cover the qualified this like in A.this.x, if possible.

@kunli2 I thought of one more false positive in the new recipe. Real code would certainly never look exactly like this (but I think it makes the point clear) and I suspect there would indeed not be many real world cases where this problem would actually crop up. Anyway, here it goes:
    @Test
    void fieldAssignedInLambdaInsideConstructor() {
        rewriteRun(
          java(
            """
                class A {
                    private int x;
                    A() {
                        Runnable r = () -> x = 2;
                    }
                }
              """
          )
        );
    }

This test currently fails, as the recipe makes x final.

@kunli2 I tried to test the two recipes together in the public SaaS, but it looked to me like it didn't work as I was expecting. I haven't analyzed this any further and possibly I did something wrong: https://public.moderne.io/results/794D5/details/eyJfX3R5cGVuYW1lIjoiR2l0SHViUmVwb3NpdG9yeSIsImlkIjoiR2l0SHViUmVwb3NpdG9yeX5+Z2l0aHViLmNvbX5+TmV0ZmxpeC9hc3R5YW5heH5+bWFzdGVyIiwib3JpZ2luIjoiZ2l0aHViLmNvbSIsInBhdGgiOiJOZXRmbGl4L2FzdHlhbmF4IiwiYnJhbmNoIjoibWFzdGVyIiwib3JnYW5pemF0aW9uIjoiTmV0ZmxpeCIsIm5hbWUiOiJhc3R5YW5heCJ9?referrer=%2Fresults%2F794D5

Let me know if you want me to look into this.

Hi @knutwannheden, thanks for testing them together, let me look into this next.

hi @knutwannheden, I think we have done everything, can we close this ticket? thanks

Yes, very nice, thank you!


WMS ID:11026 - Get Started with Oracle Exadata Database Service on Cloud@Customer.

WMS ID:11026
All changes were made from the last PR. This PR is for the workshop WMS ID:11026 - Get Started with Oracle Exadata Database Service on Cloud@Customer.
General requirements

Information in the workshop is adequate and updated
Code is correct and working
Links are correct
Make sure you enter the help email link in your manifest.json
Please make sure WMS URLs are updated as needed after your PR is approved

Checklist - Refer to the QA document for the complete list
Please confirm that the following is completed before submitting your PR

[x] All filenames are lower case (including folders, images, files, etc.)
[x] Filenames are descriptive
[x] Your workshop folder structure should be similar to the one used in the sample workshop (https://github.com/oracle-livelabs/common/tree/main/sample-livelabs-templates/sample-workshop)
[x] Are you using multiple versions (desktop/, sandbox/, tenancy/)? Make sure that each of them contains a manifest.json and an index.html
[x] Image references in markdown contain an alternate text

Added All the changes mentioned in PR #30 WMS ID:11026

Everything looks good from my POV.

@anooshapilli can we go ahead and approve?

Added all the changes and got reflected in the page thank you!


View all 4 cameras as normal

Is there a way to combine all 4 cameras as non mirrored? Also is the quality of the video altered? When submitted footage it cannot be altered. ex. Mirrored. The only --mirror works without the front camera.
+---------------+----------------+----------------+
|               |  Front Camera  |                |
+---------------+                +----------------+
|   Right Camera |----------------| Left Camera   |

          +  Rear Camera   +                +

|---------------|                |----------------|
+---------------+----------------+----------------+

Use --rear option for this.
Quality overall is not altered but in the end it is re-encoding. Y can define quality using --quality and thus setting it higher then default for the re-encoding.
Further, using --scale you can also set the size for each camera (different sizes or all same size). Providing the value of 1 leaves the camera size to 1280x960.


Paste button isn't shown on mobile web

Tested on example app.
On iOS, the long press shows the paste button.
On web iOS, the long press does nothing.
iOS app (works as expected):
https://github.com/Tkko/Flutter_Pinput/assets/2883524/e266e8c3-2e32-400a-82b5-1c98372baf5e
iOS web app (doesn't work as expected):
https://github.com/Tkko/Flutter_Pinput/assets/2883524/9a12c690-b6fc-4745-bd4e-cd2c7a9d708e

Hi @agordeev, Sorry for the late reply, on the web you have to disable the default context menu
  @override
  void initState() {
    super.initState();
    BrowserContextMenu.disableContextMenu();
  }

  @override
  void dispose() {
    BrowserContextMenu.enableContextMenu();
    super.dispose();
  }

Flutter-rendered paste button does not work ((
https://github.com/user-attachments/assets/e3bd5a3b-a893-460b-80d0-a44bf1894d68


Make entities equatable

We can override Equal method for entities. So they will became easiear to test

[ ] Comment
[ ] CommentLike
[ ] LikeBase
[ ] Photo
[ ] PhotoLike
[ ] User
[ ] Message
[ ] Subject

I think it could be done in generic way
We can implement template method patter, for example override Equal method only in abstract class using reflaction


Footer keep staying up

First of all thanks for this masterpiece implementation of lte! It's definitely best one so far.
Well.. you know we are all developers and we often use use browser's dev tool.
Sometimes i'm facing the issue in the picture and i don't have any pattern how and when it happens.
I press F12 to show dev tool and again press F12 to hide it but footer keep staying up like in the picture.
Thanks in advance.

I have exactly the same problem and have found the origin of the problem :
The calculation of the height of the content wrapper is done when router triggers navigationEnd event. Unfortunately this event has been triggered before adminLTE's content component suscribed to router event ! This is probably due to the suscribing at isCustomLayout (layout service)...
To be continued !

@gcanu fixed thanks a lot! i hope @mledour will do something about this :)

Hi,
fixed in the latest release ;)

@mledour thanks man! :)

Hi @mledour, unfortunately this issue still existing. as i remember i tested it after your commit and it was working. but yesterday i faced with this issue again.  could you please test it with an empty home page with the new code as i did below. thanks.


Navigation and Routing

I will like to contribute to this section

This has been implemented: https://flet.dev/blog/navigation-and-routing


Automated gardener integration test cannot access the cluster

Description
Gardener test fails when getting access to the new cluster

it also fails in the docker-registry repo because of the same reason


gha: fix docs generation

ammaraskar/sphinx-action requires docs/requirements.txt that was missing.
GHA now runs on PRs too, just to make sure we don't mess up docs.

Ok, turns out docs generation was completely not operational before 🙁

I hope you folks don't mind me messing with this directly, just want to help improve this project for everyone. 🙏

https://fsspec.github.io/adlfs/ works now, but looks like our aim is RTD, similar to gcsfs


Fix: fastapi exception handling and printing

Properly reports the last line of the exception in html and prints the stack trace in the terminal.

Codecov Report

Merging #1197 (fa7bbb6) into main (cc60e11) will decrease coverage by 2.77%.
The diff coverage is 44.44%.

@@            Coverage Diff             @@
##             main    #1197      +/-   ##
==========================================
- Coverage   52.44%   49.66%   -2.78%
==========================================
  Files         254      254
  Lines       14426    14425       -1
==========================================
- Hits         7565     7164     -401
- Misses       6861     7261     +400

Impacted Files
Coverage Δ

lnbits/app.py
67.85% <44.44%> (+1.19%)
:arrow_up:

lnbits/extensions/boltz/mempool.py
32.75% <0.00%> (-50.00%)
:arrow_down:

lnbits/extensions/boltz/crud.py
29.23% <0.00%> (-49.24%)
:arrow_down:

lnbits/extensions/boltz/utils.py
23.52% <0.00%> (-41.18%)
:arrow_down:

lnbits/extensions/boltz/boltz.py
17.91% <0.00%> (-39.31%)
:arrow_down:

lnbits/wallets/cln.py
19.00% <0.00%> (-29.76%)
:arrow_down:

lnbits/wallets/lndrest.py
17.09% <0.00%> (-29.06%)
:arrow_down:

lnbits/wallets/lndgrpc.py
22.72% <0.00%> (-27.93%)
:arrow_down:

lnbits/extensions/boltz/views_api.py
31.40% <0.00%> (-18.19%)
:arrow_down:

...nbits/wallets/lnd_grpc_files/lightning_pb2_grpc.py
38.22% <0.00%> (-12.25%)
:arrow_down:

... and 8 more

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


REQUEST: Static naming convention for the EvtxHussar executable

Hello,
I just made a KAPE Module for EvtxHussar.
https://github.com/EricZimmerman/KapeFiles/blob/master/Modules/Apps/GitHub/EvtxHussar.mkape
Ideally, the binary would be evtxhussar.exe so the KAPE Module doesn't have to be updated every time new features/bug fixes are released.
https://github.com/EricZimmerman/KapeFiles/blob/a6a8d079c87c2c298488dbb1c06e5d620b5b6f71/Modules/Apps/GitHub/EvtxHussar.mkape#L10
Also, not a huge Sabaton fan (mostly due to lack of experience with them) but I'm a fellow metalhead so I appreciate the Sabaton reference \m/
Andrew

Hello,
Wow, I will be part of KAPE ;)
I created a new release with new file name and directory structure. If those changes won't be enough I will made any additional changes.
Jarek

https://github.com/EricZimmerman/KapeFiles/blob/master/Modules/Apps/GitHub/EvtxHussar.mkape
Adjusted to match the new change. I really appreciate it! It helps keep things simple :)


Add get all stories controller function

Add a controller function to get all the stories. Add a route as well. Attach a screenshot of the response in the PR. (response from postman)

I would like to work on this!

Complete already allotted task first

completed!

There are many beginners. So I will be allotting this task to them. Don't worry you will be allotted some other task. Let us help everyone contribute and learn, especially the beginners

fine!

I'd like to take this, if it's still open?

Yes


Fix #132

Fixes #132
improve readability
improve performance

Criterion report on my computer:
 Benchmarking decode a 512x512 progressive JPEG: Collecting 100 samples in estimated 27.108 s (5050 i                                                                                decode a 512x512 progressive JPEG
                         time:   [5.3440 ms 5.3549 ms 5.3669 ms]
                         change: [-24.307% -23.085% -21.920%] (p = 0.00 < 0.05)
                         Performance has improved.
 Found 3 outliers among 100 measurements (3.00%)
   2 (2.00%) high mild
   1 (1.00%) high severe

Just to confirm, are you sure that the logical OR operation what this code is supposed to be doing? I posted that as a guess in the issue thread, but I don't actually know how jpeg decoding works so I was just speculating based on the shape of the surrounding code.

No, I did not check... The specification for the part in the code in in G 1.2.3 of the JPEG specification, if you want to have a look yourself :  https://books.google.fr/books?id=AepB_PZ_WMkC&pg=PA484&lpg=PA484&dq=Jpeg+Section+G.1.2.3&source=bl&ots=USKKer5RuP&sig=ACfU3U27xg2SO6Xh3LzRCXmCkqZxwFmspg&hl=en&sa=X&ved=2ahUKEwjv4bb11s7nAhUDXqwKHXnjClQQ6AEwCnoECAsQAQ#v=onepage&q&f=false

I also gave maintainers edit rights on this pull request, so if you want to fix something, you can commit directly on lovasoa:master if you want

I added the whitespace. But what I think we need is someone reviewing that against the JPEG specification.


chore: pre-commit autoupdate [ci skip]

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

v5.6.0
GitHub release

Your semantic-release bot :package::rocket:


Question: how can I get a copy of flags.png? AIso, is there a compiled css file I can edit and use?

See the build folder...

thanks


The script needs to convert some setting - error message

I get the error message when running the script for the first time like in title. To be exact :
The script needs to convert some settings for an updated feature but it couldnt correctly read yout client-resolution. It will now restart.

Ok i think my resolution is not supported, nvm. well thats sucks but what you gonna do .. cheers

You can re-download it via the front-pages download button. There is a way to run the client with a custom resolution to make it work. There was just a bug that wouldn't let you get to the settings.


Configure postgresql to stop queries when the connection drops

Description
Configure postgresql to stop queries when the connection drops
Should I wait with merging this until after the release?
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[x] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Should I wait with merging this until after the release?

I didn't see you were asking the same question. I think we should wait, especially considering that the issue should become less relevant after the release is out. We could choose to add an other-note to the changelog that this is a known issue, that it will be fixed in 6.5 and to restart the postgres service when you run into it on 6.4?

no, this is fairly obscure

Processing this pull request

Pull request rejected by merge tool. Multiple change entry files found (changelogs/unreleased/241-handle-max-clients-limit-in-agents.yml,changelogs/unreleased/392-document-config-private-package-repo.yml,changelogs/unreleased/5102-docs-make-sure-dot-in-path.yml,changelogs/unreleased/5493-get_events_accross_incremental_deploys.yml,changelogs/unreleased/5514-doc-warning-multiple-indexes.yml,changelogs/unreleased/5774-add-support-archive-doc.yml,changelogs/unreleased/5787-drop-equals-injection.yml,changelogs/unreleased/6022-use-python-311-fix.yml,changelogs/unreleased/6022-use-python-311.yml,changelogs/unreleased/6025-add-docs-discoveryhandler.yml,changelogs/unreleased/6025-implement-discovery-resource-handler.yml,changelogs/unreleased/6025-implement-top-level-handler-abc.yml,changelogs/unreleased/6074-iso6-docs-reference-iso7.yml,changelogs/unreleased/6123-fix-incorrect-rewrite-requirements-agent.yml,changelogs/unreleased/6199-dependabot.yml,changelogs/unreleased/6202-repair-loop.yml,changelogs/unreleased/6211-support-not-in,.yml,changelogs/unreleased/6215-dependabot.yml,changelogs/unreleased/6221-dependabot.yml,changelogs/unreleased/6224-drop-instance-dump-method.yml,changelogs/unreleased/6232-bump-asyncpg-to-0-28.yml,changelogs/unreleased/6234-drop-copy-in-method.yml,changelogs/unreleased/6235-dependabot.yml,changelogs/unreleased/6236-dependabot.yml,changelogs/unreleased/6237-dependabot.yml,changelogs/unreleased/6238-dependabot.yml,changelogs/unreleased/6250-dependabot.yml,changelogs/unreleased/6251-dependabot.yml,changelogs/unreleased/6252-dependabot.yml,changelogs/unreleased/6253-dependabot.yml,changelogs/unreleased/6259-dependabot.yml,changelogs/unreleased/6260-dependabot.yml,changelogs/unreleased/6271-dependabot.yml,changelogs/unreleased/6273-fix-env-creation-same-name.yml,changelogs/unreleased/6274-dependabot.yml,changelogs/unreleased/6275-dependabot.yml,changelogs/unreleased/6276-dependabot.yml,changelogs/unreleased/6281-dependabot.yml,changelogs/unreleased/6285-dependabot.yml,changelogs/unreleased/6286-dependabot.yml,changelogs/unreleased/6287-dependabot.yml,changelogs/unreleased/6288-dependabot.yml,changelogs/unreleased/6289-dependabot.yml,changelogs/unreleased/6290-dependabot.yml,changelogs/unreleased/6297-dependabot.yml,changelogs/unreleased/6298-dependabot.yml,changelogs/unreleased/6299-dependabot.yml,changelogs/unreleased/6312-dependabot.yml,changelogs/unreleased/6316-dependabot.yml,changelogs/unreleased/6317-dependabot.yml,changelogs/unreleased/6335-dependabot.yml,changelogs/unreleased/6336-dependabot.yml,changelogs/unreleased/6343-add-time-zone-to-discovered-at-column.yml,changelogs/unreleased/6345-dependabot.yml,changelogs/unreleased/6349-release-only-once.yml,changelogs/unreleased/6352-dependabot.yml,changelogs/unreleased/6359-dependabot.yml,changelogs/unreleased/6365-dependabot.yml,changelogs/unreleased/6369-dependabot.yml,changelogs/unreleased/6374-repair-runs-specific-timerange.yml,changelogs/unreleased/6376-dependabot.yml,changelogs/unreleased/6382-dependabot.yml,changelogs/unreleased/6389-dependabot.yml,changelogs/unreleased/6392-dependabot.yml,changelogs/unreleased/6393-dependabot.yml,changelogs/unreleased/6397-dependabot.yml,changelogs/unreleased/6398-dependabot.yml,changelogs/unreleased/6405-dependabot.yml,changelogs/unreleased/6406-dependabot.yml,changelogs/unreleased/6407-dependabot.yml,changelogs/unreleased/6408-dependabot.yml,changelogs/unreleased/6409-improve-language-reference-documentation.yml,changelogs/unreleased/6414-dependabot.yml,changelogs/unreleased/6421-dependabot.yml,changelogs/unreleased/6422-dependabot.yml,changelogs/unreleased/6423-dependabot.yml,changelogs/unreleased/6427-split-delete-in-small-transactions.yml,changelogs/unreleased/6430-dependabot.yml,changelogs/unreleased/6437-dependabot.yml,changelogs/unreleased/6438-dependabot.yml,changelogs/unreleased/6441-store-files-in-db.yml,changelogs/unreleased/6445-dependabot.yml,changelogs/unreleased/6446-dependabot.yml,changelogs/unreleased/6454-dependabot.yml,changelogs/unreleased/6465-dependabot.yml,changelogs/unreleased/6466-dependabot.yml,changelogs/unreleased/6467-dependabot.yml,changelogs/unreleased/6475-prevent-too-eager-overwrite.yml,changelogs/unreleased/6475-release-masking-failure.yml,changelogs/unreleased/6477-increment-with-events.yml,changelogs/unreleased/6481-dependabot.yml,changelogs/unreleased/6482-dependabot.yml,changelogs/unreleased/6491-dependabot.yml,changelogs/unreleased/6492-dependabot.yml,changelogs/unreleased/6496-dependabot.yml,changelogs/unreleased/6502-dependabot.yml,changelogs/unreleased/6522-dependabot.yml,changelogs/unreleased/6528-dependabot.yml,changelogs/unreleased/6537-dependabot.yml,changelogs/unreleased/6545-dependabot.yml,changelogs/unreleased/6546-dependabot.yml,changelogs/unreleased/6549-add-missing-migration-script.yml,changelogs/unreleased/6549-fix-issues-with-deploy-or-repair-interval-cron-expressions.yml,changelogs/unreleased/6551-dependabot.yml,changelogs/unreleased/6552-dependabot.yml,changelogs/unreleased/6558-dependabot.yml,changelogs/unreleased/6569-dependabot.yml,changelogs/unreleased/6570-dependabot.yml,changelogs/unreleased/6575-dependabot.yml,changelogs/unreleased/6584-dependabot.yml,changelogs/unreleased/6585-dependabot.yml,changelogs/unreleased/6586-document-in-and-not-in.yml,changelogs/unreleased/6589-undeployable-resource-handling.yml,changelogs/unreleased/6599-increase-timeout-get-status-method.yml,changelogs/unreleased/6603-dependabot.yml,changelogs/unreleased/add-documentation-annotations.yml,changelogs/unreleased/backward_compat_put_version.yml,changelogs/unreleased/build-master-2023-09-19-fix-brittle-test.yml,changelogs/unreleased/build-master-fix-broken-link.yml,changelogs/unreleased/build-master-investigate-docs-builds-failure.yml,changelogs/unreleased/change-default-fact-expire-time.yml,changelogs/unreleased/dependabot-fix.yml,changelogs/unreleased/deploy-command-shutdown-race.yml,changelogs/unreleased/docs-confpy-allow-version-injection.yml,changelogs/unreleased/dont-run-handler-when-no-code.yml,changelogs/unreleased/drop-pg10-support.yml,changelogs/unreleased/ensure-str-type-on-attribute-value.yml,changelogs/unreleased/fix-compatibility-python-39.yml,changelogs/unreleased/fix-coverage-reporting-issue.yml,changelogs/unreleased/fix-performance-issue-delete-and-clear-env.yml,changelogs/unreleased/fix-race-in-incremental-deploy-test.yml,changelogs/unreleased/fix-timestamp-issue-in-tests.yml,changelogs/unreleased/improve-error-reporting-release-command.yml,changelogs/unreleased/improve-visual-appearence-compiler.yml,changelogs/unreleased/increase_max_iterations.yml,changelogs/unreleased/issue-build-master-pin-execnet-to1-9-0.yml,changelogs/unreleased/issue-doc-quick-fix.yml,changelogs/unreleased/make-stop-method-of-featuremanager-async.yml,changelogs/unreleased/make_postgresql_drop_dead_queries.yml,changelogs/unreleased/move-validate-type-method-to-core.yml,changelogs/unreleased/move_to_no_key_update.yml,changelogs/unreleased/pytest-inmanta-extensions-fix.yml,changelogs/unreleased/race_in_server_tests.yml,changelogs/unreleased/remove-old-relationship-syntax.yml,changelogs/unreleased/schedulertotrace.yml,changelogs/unreleased/session_timer_to_monotonic_time.yml,changelogs/unreleased/sphinx.yml,changelogs/unreleased/support-rounded-timestamps.yml,changelogs/unreleased/test-assertion-verbosity.yml,changelogs/unreleased/update-doc-ignore-resource-exception.yml,changelogs/unreleased/update-minimal-python-version.yml). This may happen when a change entry was removed from the remote repository due to a reverted change. In that case, make sure the latest changes from origin/master are merged into issue/make_postgresql_drop_dead_queries before triggering merge bot.

Processing this pull request

Merged into branches master in 813d637ddd2dc387aa5f6e3afcebd92d6eeb2e1d

Processing #6633.


Data Transformation

Join datasets from multiple sources based on common identifiers and apply necessary transformations

All 5 data frames are transformed and combined into one final data frame.


File "/tmp/pip-build-env-2uefdgt0/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 215, in _build_with_temp_dir
    self.run_setup()
  File "/tmp/pip-build-env-2uefdgt0/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 267, in run_setup
    super(_BuildMetaLegacyBackend,
  File "/tmp/pip-build-env-2uefdgt0/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 158, in run_setup
    exec(compile(code, __file__, 'exec'), locals())
  File "setup.py", line 461, in <module>
    setup_package()
  File "setup.py", line 453, in setup_package
    setup(**metadata)
  File "/tmp/pip-install-q5auxtts/numpy_3ab23e763f114c98ba773072600c68d4/numpy/distutils/core.py", line 169, in setup
    return old_setup(**new_attr)
  File "/tmp/pip-build-env-2uefdgt0/overlay/lib/python3.9/site-packages/setuptools/__init__.py", line 153, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib/python3.9/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib/python3.9/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/tmp/pip-build-env-2uefdgt0/overlay/lib/python3.9/site-packages/wheel/bdist_wheel.py", line 299, in run
    self.run_command('build')
  File "/usr/lib/python3.9/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/tmp/pip-install-q5auxtts/numpy_3ab23e763f114c98ba773072600c68d4/numpy/distutils/command/build.py", line 61, in run
    old_build.run(self)
  File "/usr/lib/python3.9/distutils/command/build.py", line 135, in run
    self.run_command(cmd_name)
  File "/usr/lib/python3.9/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/tmp/pip-install-q5auxtts/numpy_3ab23e763f114c98ba773072600c68d4/numpy/distutils/command/build_src.py", line 144, in run
    self.build_sources()
  File "/tmp/pip-install-q5auxtts/numpy_3ab23e763f114c98ba773072600c68d4/numpy/distutils/command/build_src.py", line 155, in build_sources
    self.build_library_sources(*libname_info)
  File "/tmp/pip-install-q5auxtts/numpy_3ab23e763f114c98ba773072600c68d4/numpy/distutils/command/build_src.py", line 288, in build_library_sources
    sources = self.generate_sources(sources, (lib_name, build_info))
  File "/tmp/pip-install-q5auxtts/numpy_3ab23e763f114c98ba773072600c68d4/numpy/distutils/command/build_src.py", line 378, in generate_sources
    source = func(extension, build_dir)
  File "numpy/core/setup.py", line 708, in get_mathlib_info
    raise RuntimeError(
RuntimeError: Broken toolchain: cannot link a simple C program.
----------------------------------------
ERROR: Failed building wheel for numpy

Failed to build numpy
ERROR: Could not build wheels for numpy which use PEP 517 and cannot be installed directly
WARNING: Discarding https://files.pythonhosted.org/packages/78/e4/a935f1701fac697c6c5458f86968bec5d2b4cb66e7f738225216ebaa20b4/pandas-1.2.2.tar.gz#sha256=14ed84b463e9b84c8ff9308a79b04bf591ae3122a376ee0f62c68a1bd917a773 (from https://pypi.org/simple/pandas/) (requires-python:>=3.7.1). Command errored out with exit status 1: /usr/bin/python3 /usr/lib/python3.9/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-0ifjhvka/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- setuptools wheel 'Cython>=0.29.21,<3' 'numpy==1.16.5; python_version=='"'"'3.7'"'"' and platform_system!='"'"'AIX'"'"'' 'numpy==1.17.3; python_version=='"'"'3.8'"'"' and platform_system!='"'"'AIX'"'"'' 'numpy==1.16.5; python_version=='"'"'3.7'"'"' and platform_system=='"'"'AIX'"'"'' 'numpy==1.17.3; python_version=='"'"'3.8'"'"' and platform_system=='"'"'AIX'"'"'' 'numpy; python_version>='"'"'3.9'"'"'' Check the logs for full command output.
Using cached pandas-1.2.1.tar.gz (5.5 MB)
Installing build dependencies: started
Installing build dependencies: still running...
Installing build dependencies: finished with status 'error'
Using cached pandas-1.2.0.tar.gz (5.4 MB)
Installing build dependencies: started
Installing build dependencies: still running...
ERROR: Command errored out with exit status 1:
command: /usr/bin/python3 /usr/lib/python3.9/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-jeob5h80/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- setuptools wheel 'Cython>=0.29.21,<3' 'numpy==1.16.5; python_version=='"'"'3.7'"'"' and platform_system!='"'"'AIX'"'"'' 'numpy==1.17.3; python_version=='"'"'3.8'"'"' and platform_system!='"'"'AIX'"'"'' 'numpy==1.16.5; python_version=='"'"'3.7'"'"' and platform_system=='"'"'AIX'"'"'' 'numpy==1.17.3; python_version=='"'"'3.8'"'"' and platform_system=='"'"'AIX'"'"'' 'numpy; python_version>='"'"'3.9'"'"''
cwd: None
Complete output (276 lines):
Ignoring numpy: markers 'python_version == "3.7" and platform_system != "AIX"' don't match your environment
Ignoring numpy: markers 'python_version == "3.8" and platform_system != "AIX"' don't match your environment
Ignoring numpy: markers 'python_version == "3.7" and platform_system == "AIX"' don't match your environment
Ignoring numpy: markers 'python_version == "3.8" and platform_system == "AIX"' don't match your environment
Collecting setuptools
Using cached setuptools-62.1.0-py3-none-any.whl (1.1 MB)
Collecting wheel
Using cached wheel-0.37.1-py2.py3-none-any.whl (35 kB)
Collecting Cython<3,>=0.29.21
Using cached Cython-0.29.28-py2.py3-none-any.whl (983 kB)
Collecting numpy
Using cached numpy-1.22.3.zip (11.5 MB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing wheel metadata: started
Preparing wheel metadata: finished with status 'done'
Building wheels for collected packages: numpy
Building wheel for numpy (PEP 517): started
Building wheel for numpy (PEP 517): finished with status 'error'
ERROR: Command errored out with exit status 1:
command: /usr/bin/python3 /usr/lib/python3.9/site-packages/pip/_vendor/pep517/_in_process.py build_wheel /tmp/tmpo1e1y1xw
cwd: /tmp/pip-install-0wm40mma/numpy_0cd06392267c474da11ad4209b21112b
Complete output (247 lines):
Running from numpy source directory.
Cythonizing sources
Processing numpy/random/_bounded_integers.pxd.in
Processing numpy/random/_pcg64.pyx
Processing numpy/random/_philox.pyx
Processing numpy/random/bit_generator.pyx
Processing numpy/random/mtrand.pyx
Processing numpy/random/_bounded_integers.pyx.in
Processing numpy/random/_common.pyx
Processing numpy/random/_sfc64.pyx
Processing numpy/random/_mt19937.pyx
Processing numpy/random/_generator.pyx
INFO: blas_opt_info:
INFO: blas_armpl_info:
INFO: customize UnixCCompiler
INFO:   libraries armpl_lp64_mp not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
INFO: blas_mkl_info:
INFO:   libraries mkl_rt not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
INFO: blis_info:
INFO:   libraries blis not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
INFO: openblas_info:
INFO:   libraries openblas not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
INFO: accelerate_info:
INFO:   NOT AVAILABLE
INFO:
INFO: atlas_3_10_blas_threads_info:
INFO: Setting PTATLAS=ATLAS
INFO:   libraries tatlas not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
INFO: atlas_3_10_blas_info:
INFO:   libraries satlas not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
INFO: atlas_blas_threads_info:
INFO: Setting PTATLAS=ATLAS
INFO:   libraries ptf77blas,ptcblas,atlas not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
INFO: atlas_blas_info:
INFO:   libraries f77blas,cblas,atlas not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
/tmp/pip-install-0wm40mma/numpy_0cd06392267c474da11ad4209b21112b/numpy/distutils/system_info.py:2077: UserWarning:
Optimized (vendor) Blas libraries are not found.
Falls back to netlib Blas library which has worse performance.
A better performance should be easily gained by switching
Blas library.
if self._calc_info(blas):
INFO: blas_info:
INFO:   libraries blas not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
/tmp/pip-install-0wm40mma/numpy_0cd06392267c474da11ad4209b21112b/numpy/distutils/system_info.py:2077: UserWarning:
Blas (http://www.netlib.org/blas/) libraries not found.
Directories to search for the libraries can be specified in the
numpy/distutils/site.cfg file (section [blas]) or by setting
the BLAS environment variable.
if self._calc_info(blas):
INFO: blas_src_info:
INFO:   NOT AVAILABLE
INFO:
/tmp/pip-install-0wm40mma/numpy_0cd06392267c474da11ad4209b21112b/numpy/distutils/system_info.py:2077: UserWarning:
Blas (http://www.netlib.org/blas/) sources not found.
Directories to search for the sources can be specified in the
numpy/distutils/site.cfg file (section [blas_src]) or by setting
the BLAS_SRC environment variable.
if self.calc_info(blas):
INFO:   NOT AVAILABLE
INFO:
non-existing path in 'numpy/distutils': 'site.cfg'
INFO: lapack_opt_info:
INFO: lapack_armpl_info:
INFO:   libraries armpl_lp64_mp not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
INFO: lapack_mkl_info:
INFO:   libraries mkl_rt not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
INFO: openblas_lapack_info:
INFO:   libraries openblas not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
INFO: openblas_clapack_info:
INFO:   libraries openblas,lapack not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
INFO: flame_info:
INFO:   libraries flame not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
INFO: atlas_3_10_threads_info:
INFO: Setting PTATLAS=ATLAS
INFO:   libraries tatlas,tatlas not found in /usr/local/lib
INFO:   libraries tatlas,tatlas not found in /usr/lib
INFO: <class 'numpy.distutils.system_info.atlas_3_10_threads_info'>
INFO:   NOT AVAILABLE
INFO:
INFO: atlas_3_10_info:
INFO:   libraries satlas,satlas not found in /usr/local/lib
INFO:   libraries satlas,satlas not found in /usr/lib
INFO: <class 'numpy.distutils.system_info.atlas_3_10_info'>
INFO:   NOT AVAILABLE
INFO:
INFO: atlas_threads_info:
INFO: Setting PTATLAS=ATLAS
INFO:   libraries ptf77blas,ptcblas,atlas not found in /usr/local/lib
INFO:   libraries ptf77blas,ptcblas,atlas not found in /usr/lib
INFO: <class 'numpy.distutils.system_info.atlas_threads_info'>
INFO:   NOT AVAILABLE
INFO:
INFO: atlas_info:
INFO:   libraries f77blas,cblas,atlas not found in /usr/local/lib
INFO:   libraries f77blas,cblas,atlas not found in /usr/lib
INFO: <class 'numpy.distutils.system_info.atlas_info'>
INFO:   NOT AVAILABLE
INFO:
INFO: lapack_info:
INFO:   libraries lapack not found in ['/usr/local/lib', '/usr/lib']
INFO:   NOT AVAILABLE
INFO:
/tmp/pip-install-0wm40mma/numpy_0cd06392267c474da11ad4209b21112b/numpy/distutils/system_info.py:1902: UserWarning:
Lapack (http://www.netlib.org/lapack/) libraries not found.
Directories to search for the libraries can be specified in the
numpy/distutils/site.cfg file (section [lapack]) or by setting
the LAPACK environment variable.
return getattr(self, 'calc_info{}'.format(name))()
INFO: lapack_src_info:
INFO:   NOT AVAILABLE
INFO:
/tmp/pip-install-0wm40mma/numpy_0cd06392267c474da11ad4209b21112b/numpy/distutils/system_info.py:1902: UserWarning:
Lapack (http://www.netlib.org/lapack/) sources not found.
Directories to search for the sources can be specified in the
numpy/distutils/site.cfg file (section [lapack_src]) or by setting
the LAPACK_SRC environment variable.
return getattr(self, 'calc_info{}'.format(name))()
INFO:   NOT AVAILABLE
INFO:
INFO: numpy_linalg_lapack_lite:
INFO:   FOUND:
INFO:     language = c
INFO:     define_macros = [('HAVE_BLAS_ILP64', None), ('BLAS_SYMBOL_SUFFIX', '64')]
INFO:
Warning: attempted relative import with no known parent package
/usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution option: 'define_macros'
warnings.warn(msg)
running bdist_wheel
running build
running config_cc
INFO: unifing config_cc, config, build_clib, build_ext, build commands --compiler options
running config_fc
INFO: unifing config_fc, config, build_clib, build_ext, build commands --fcompiler options
running build_src
INFO: build_src
INFO: building py_modules sources
creating build
creating build/src.linux-aarch64-3.9
creating build/src.linux-aarch64-3.9/numpy
creating build/src.linux-aarch64-3.9/numpy/distutils
INFO: building library "npymath" sources
WARN: Could not locate executable armflang
WARN: Could not locate executable gfortran
WARN: Could not locate executable f95
WARN: Could not locate executable ifort
WARN: Could not locate executable ifc
WARN: Could not locate executable lf95
WARN: Could not locate executable pgfortran
WARN: Could not locate executable nvfortran
WARN: Could not locate executable f90
WARN: Could not locate executable f77
WARN: Could not locate executable fort
WARN: Could not locate executable efort
WARN: Could not locate executable efc
WARN: Could not locate executable g77
WARN: Could not locate executable g95
WARN: Could not locate executable pathf95
WARN: Could not locate executable nagfor
WARN: Could not locate executable frt
WARN: don't know how to compile Fortran code on platform 'posix'
[Errno 2] No such file or directory: 'gcc'

Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/pip/_vendor/pep517/_in_process.py", line 280, in <module>
    main()
  File "/usr/lib/python3.9/site-packages/pip/_vendor/pep517/_in_process.py", line 263, in main
    json_out['return_val'] = hook(**hook_input['kwargs'])
  File "/usr/lib/python3.9/site-packages/pip/_vendor/pep517/_in_process.py", line 204, in build_wheel
    return _build_backend().build_wheel(wheel_directory, config_settings,
  File "/tmp/pip-build-env-203xh2xu/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 230, in build_wheel
    return self._build_with_temp_dir(['bdist_wheel'], '.whl',
  File "/tmp/pip-build-env-203xh2xu/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 215, in _build_with_temp_dir
    self.run_setup()
  File "/tmp/pip-build-env-203xh2xu/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 267, in run_setup
    super(_BuildMetaLegacyBackend,
  File "/tmp/pip-build-env-203xh2xu/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 158, in run_setup
    exec(compile(code, __file__, 'exec'), locals())
  File "setup.py", line 461, in <module>
    setup_package()
  File "setup.py", line 453, in setup_package
    setup(**metadata)
  File "/tmp/pip-install-0wm40mma/numpy_0cd06392267c474da11ad4209b21112b/numpy/distutils/core.py", line 169, in setup
    return old_setup(**new_attr)
  File "/tmp/pip-build-env-203xh2xu/overlay/lib/python3.9/site-packages/setuptools/__init__.py", line 153, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib/python3.9/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib/python3.9/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/tmp/pip-build-env-203xh2xu/overlay/lib/python3.9/site-packages/wheel/bdist_wheel.py", line 299, in run
    self.run_command('build')
  File "/usr/lib/python3.9/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/tmp/pip-install-0wm40mma/numpy_0cd06392267c474da11ad4209b21112b/numpy/distutils/command/build.py", line 61, in run
    old_build.run(self)
  File "/usr/lib/python3.9/distutils/command/build.py", line 135, in run
    self.run_command(cmd_name)
  File "/usr/lib/python3.9/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/tmp/pip-install-0wm40mma/numpy_0cd06392267c474da11ad4209b21112b/numpy/distutils/command/build_src.py", line 144, in run
    self.build_sources()
  File "/tmp/pip-install-0wm40mma/numpy_0cd06392267c474da11ad4209b21112b/numpy/distutils/command/build_src.py", line 155, in build_sources
    self.build_library_sources(*libname_info)
  File "/tmp/pip-install-0wm40mma/numpy_0cd06392267c474da11ad4209b21112b/numpy/distutils/command/build_src.py", line 288, in build_library_sources
    sources = self.generate_sources(sources, (lib_name, build_info))
  File "/tmp/pip-install-0wm40mma/numpy_0cd06392267c474da11ad4209b21112b/numpy/distutils/command/build_src.py", line 378, in generate_sources
    source = func(extension, build_dir)
  File "numpy/core/setup.py", line 708, in get_mathlib_info
    raise RuntimeError(
RuntimeError: Broken toolchain: cannot link a simple C program.
----------------------------------------
ERROR: Failed building wheel for numpy

Failed to build numpy
ERROR: Could not build wheels for numpy which use PEP 517 and cannot be installed directly
WARNING: Discarding https://files.pythonhosted.org/packages/75/bc/abf2e8cc6a9d918008774b958613cfdbd3a8c135cffb0757f78fabd8268f/pandas-1.2.0.tar.gz#sha256=e03386615b970b8b41da6a68afe717626741bb2431cec993640685614c0680e4 (from https://pypi.org/simple/pandas/) (requires-python:>=3.7.1). Command errored out with exit status 1: /usr/bin/python3 /usr/lib/python3.9/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-jeob5h80/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- setuptools wheel 'Cython>=0.29.21,<3' 'numpy==1.16.5; python_version=='"'"'3.7'"'"' and platform_system!='"'"'AIX'"'"'' 'numpy==1.17.3; python_version=='"'"'3.8'"'"' and platform_system!='"'"'AIX'"'"'' 'numpy==1.16.5; python_version=='"'"'3.7'"'"' and platform_system=='"'"'AIX'"'"'' 'numpy==1.17.3; python_version=='"'"'3.8'"'"' and platform_system=='"'"'AIX'"'"'' 'numpy; python_version>='"'"'3.9'"'"'' Check the logs for full command output.
Using cached pandas-1.1.5.tar.gz (5.2 MB)
Installing build dependencies: started
Installing build dependencies: still running...
ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
pandas from https://files.pythonhosted.org/packages/09/39/fb93ed98962d032963418cd1ea5927b9e11c4c80cb1e0b45dea769d8f9a5/pandas-1.1.4.tar.gz#sha256=a979d0404b135c63954dea79e6246c45dd45371a88631cdbb4877d844e6de3b6 (from efinance):
Expected sha256 a979d0404b135c63954dea79e6246c45dd45371a88631cdbb4877d844e6de3b6
Got<PHONE_NUMBER>17612f2d89cfeb5435d65f31db7a5d89eb7996d03fad96435137ed
依赖安装失败，结束时间 2022/5/8 14:57:01，耗时 1064.121 秒

试试装一下 miniconda 再用它创建 python 环境，最后激活创建的环境、安装。

好的，试一试

再请教一下，此项目在m1上运行是否正常？谢谢

再请教一下，此项目在m1上运行是否正常？谢谢

我没有这个机器来测试。正常来说，能使用 numpy 和 pandas 即可正常安装。


Add initial CONTRIBUTING.md

Closes #4

 Add instructions for contributing (what if someone wants to fix a bug or develop a new feature?)


add macro defhookfn

[x] I haven't tested it yet Tested
[x] I made sure there are no errors or warnings when compiling the macro itself and when you compile (define-ll-keyboard-proc ll-kbd-callback (ncode wparam lparam))
[x] Feel free to ask for changes (like the name)
[x] remove flet ((call-next-hook

Related changes in win32

@Zulu-Inuoe I think this should be good to merge (squash the commits).

Semi-annual boop

boupe

:eye:


Updates for iOS12/XCode 10/Swift 4.2?

I am having rendering issues, any chance this wonderful package will be updated for the new stuff?  Thanks.

Hi @johnbanks, I will update the project soon.
If you would like to contribute don't hesitate, I will be happy to see your PRs.

Done

thanks @nmullaney  for reporting, I updated the pod, the new version 2.1.0 is available


Added API details for the LINQ examples to make it easier to follow

#33560

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

@random82 - Thanks so much for making these changes!
#sign-off