Rename repo

If I understand correctly, this repository only contains code regarding https://profiles.impactstory.org/ ? If so, it might be useful to rename this repo to clarify this:
https://github.com/Impactstory/profiles

or
https://github.com/Impactstory/impactstory-profiles

Rather than impactstory-tng(the next generation). 😄
All existing links will continue to work

Thanks for the idea Peter!  Yup we might do that at some point, but swamped right now, and it'll make our internal directories confused, so going to hold off on this for now.
Heather

Thanks for the idea Peter!  Yup we might do that at some point, but swamped
right now, and it'll make our internal directories confused, so going to
hold off on this for now.
Heather
--
Heather Piwowar
cofounder of Impactstory http://impactstory.org/: share the full story of
your research impact.
working from Vancouver, Canada
@researchremix http://twitter.com/#!/researchremix and @Impactstory
https://twitter.com/ImpactStory
On Sat, May 19, 2018 at 4:03 AM, Peter Desmet<EMAIL_ADDRESS>wrote:

If I understand correctly, this repository only contains code regarding
https://profiles.impactstory.org/ ? If so, it might be useful to rename
this repo to clarify this:
https://github.com/Impactstory/profiles
or
https://github.com/Impactstory/impactstory-profiles
Rather than impactstory-tng(the next generation). 😄
All existing links will continue to work
https://help.github.com/articles/renaming-a-repository/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Impactstory/impactstory-tng/issues/27, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AANngdrjyZCE_spvJ1Ciu6ROpHzAhBflks5tz_wCgaJpZM4UFq6W
.


Bug when processing handlebars templates.

Bug report

What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?

The minimal working example can be found here: https://gist.github.com/pherman/30763567e1c5245c752be9ac693d5b3f
Run npm install to install the dev dependencies and then npm run build && npm start to test.
You should see something like this in the console:
<link href="71660f764fdd7f9399f45b22b5c50f83.css" rel="stylesheet">My name is Bourne.
When you open the css file, you will see:
:root {      content: '{{ color }}'; }
Thus far, everything works as expected.
Now to reproduce the bug, go into webpack.config.js and comment out VERSION 0 and remove the comments from VERSION 1.
Rebuild and rerun and you will again see html similar to the above in the console but if you open the css file, you will find this:
<link href="./some.css" rel="stylesheet" type="text/css">My name is .
This is the more.html file except that the variable is replaced with the empty string.  Here I would expect:
:root {      content: 'red'; }
Interestingly, if you then uncomment the first line in index.js that require some.css directly, rebuild, and rerun, the output is correct.  This implies that this can't be a bug in handlebars-loader.  Perhaps there is a caching issue here?

Other relevant information:
webpack version:  5.6.0
Node.js version: 6.14.8
Operating System: Ubuntu
Additional tools:

This doesn't seem to be a webpack issue. It looks like there is some global state in the output of handlebars-loader. Probably it's also using module.exports which overrides your loader code. Avoid using direct eval. Replace it with (0,eval)(...) and you probably get better errors. Also inspect the output of handlebars-loader (source).


fix: No update prompt if the target folder contains an unconfigured Higress instance

Ⅰ. Describe what this PR did
If anything goes wrong during the configuration phase of the standalone deployment, and user tries to reinstall Higress, an "update with -u" prompt would be shown.
However, Higress is not in fact "installed" in the target folder. So we use the "compose/.configured" file to determine whether the configuration phase has finished successfully or not, and only show the update prompt if configured.
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #583 (72f698e) into main (f685b03) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 72f698e differs from pull request most recent head 07df02c. Consider uploading reports for the commit 07df02c to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #583   +/-   ##
=======================================
  Coverage   37.46%   37.46%
=======================================
  Files          65       65
  Lines        9215     9215
=======================================
  Hits         3452     3452
  Misses       5497     5497
  Partials      266      266


Add RotaryPartPattern

Codecov Report
Attention: 12 lines in your changes are missing coverage. Please review.

Comparison is base (80372d0) 71.61% compared to head (594e82a) 71.95%.

Files
Patch %
Lines

...ntal_experiment/torch_exp/optimization_patterns.py
88.04%
11 Missing :warning:

...perimental_experiment/torch_dynamo/fast_backend.py
50.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #52      +/-   ##
==========================================
+ Coverage   71.61%   71.95%   +0.34%
==========================================
  Files          37       37
  Lines        5137     5235      +98
==========================================
+ Hits         3679     3767      +88
- Misses       1458     1468      +10

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Remove global 10 day timeout

This has been fixed upstream with https://github.com/microsoft/kiota-http-go/pull/71 . We don't need this hack anymore.

Does this PR need a docs update or release note?

[x] :white_check_mark: Yes, it's included
[ ] :clock1: Yes, but in a later PR
[ ] :no_entry: No

Type of change

[ ] :sunflower: Feature
[x] :bug: Bugfix
[ ] :world_map: Documentation
[ ] :robot: Test
[ ] :computer: CI/Deployment
[ ] :broom: Tech Debt/Cleanup

Issue(s)

fixes https://github.com/alcionai/corso/issues/2849
closes https://github.com/alcionai/corso/pull/2694
closes https://github.com/alcionai/corso/pull/2692
closes https://github.com/alcionai/corso/pull/2696
closes https://github.com/alcionai/corso/pull/2814

Test Plan

[x] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

The CI seems to be full of context deadline issues now. Let me do a bit more work on this.


Pagination .page-item doesn't visually contain the .page-link links

I am not sure if this is all good but as I was fixing a bug on my website, I came to realized that the <li class="page-item"> in .pagination doesn't show to be containing the inner .page-link anchors. This is due to the fact that each .page-link is floated within .page-item li.
I have couple of questions regarding this.( could be silly )

Is this a good thing? Shouldn't the parent show to be containing the floated children?
Is the float really need to be on the anchors? Couldn't it just be on the .page-item li ?
If at all it's necessary, could we float the li too so it shows to be containing the inner anchor? In that case, I can definitely send a PR.
Is there already something coming up in alpha 3 addressing it?

Example Instance :
http://v4-alpha.getbootstrap.com/components/pagination/#default-pagination

CC: @mdo


Make it easier for users to correlate an application to specific pod(s) in the cluster

Is your feature request related to a problem? Please describe.
Kubernetes operators (the humans that maintain the cluster) tend to see applications deployed to a kubernetes cluster as a list of Pods,  Deployments, Helm releases, etc. Currently the UI lists Resource Names in the Application tab that seem to either correlate to an app or name label on the pod, or falls back to the image tag in the absence of those. I can't go anywhere to see the actual pod name, so I either need the context to infer it from the information currently provided, or figure it out manually with kubectl.
Describe the solution you'd like
When you click on an Application in the table, you get a nice summary of the pod labels associated with that application. Just add another area in the UI there that provides a list of pod names.
Describe alternatives you've considered
Another option, and would perhaps be interesting to do as well as the solution I mentioned above, is to have a table very similar to the Applications tab that uses pod name as the primary key instead of application name. In the event that multiple pods are identical, such as pods owned by a ReplicaSet, it lists all identical pods as one row.
Additional context
N/A

The way the application name is determined is also very suboptimal for my use case. Kubeclarity simply tries to derive an application name from commonly used labels, and if the labels are not used, the pod name is used. This also leads to the fact that if different stages are mapped with different namespaces, but the app.kubernetes.io/name labels in these deployments are identical, Kubeclarity will package them all into one application. The result is that the environments are no longer distinguishable in Kubeclarity.
In this case, I would find it very handy to have a special, optional label that defines the name of the Kubeclarity application. Would this be something for which a pull request would be accepted?

If you look at Openclarity's project kanban board it kind of looks like they've abandoned this project entirely in favor of a different one "vmclarity" which obviously doesn't really relate to kubernetes at all so I'm starting to think a fork is more in order, in lieu of maintainers looking for contributions or feedback, personally. I've been thinking of doing just this but I am a bit hesitant to add yet another side project to fill the gaps in my personal time.

If you look at Openclarity's project kanban board it kind of looks like they've abandoned this project entirely in favor of a different one "vmclarity" which obviously doesn't really relate to kubernetes at all so I'm starting to think a fork is more in order, in lieu of maintainers looking for contributions or feedback, personally. I've been thinking of doing just this but I am a bit hesitant to add yet another side project to fill the gaps in my personal time.

I think perhaps this hasn't been well communicated but we're in a transition period. KubeClarity/VMClarity are merging together and becoming a unified platform under the OpenClarity brand.
The VMClarity infrastructure was more mature (better separation of concerns, pluggable, more supported scanners, finding history) so we're focusing the development on that as the underlying infrastructure for the unified platform. New features will be developed on top of that infrastructure.
We already have a Kubernetes driver and installer for VMClarity, please take a look, it even supports scanning running containers not just images as KubeClarity does. We have a ticket in the board to provide a migration script for existing KubeClarity users once we're happy that the new platform is stable enough for folks to migrate.
Regarding this ticket, the data model in VMClarity is a bit different from KubeClarity, we capture much more information about the discovered Assets (there is asset discovery in VMClarity without running a scan) and provide a robust user facing query language to let you search through discovered assets to find the ones you care about and select a sub-set of them for scanning.

I think perhaps this hasn't been well communicated but we're in a transition period. KubeClarity/VMClarity are merging together and becoming a unified platform under the OpenClarity brand.

A notice about this in kubeclarity's README might make this a bit more obvious? Simply by looking at the names, I deduced that these were two completely different products and you're correct that there was seemingly nothing signaling to me that I was wrong. But this is excellent news, and thank you for commenting here!

Thanks for reporting @Starttoaster, I captured the issue and will add the necessary details for future KubeClarity users. In the meantime, feel free to create this issue it in the VMClarity repo if the existing Kubernetes functionalities are insufficient for your use case.

Hi @ramizpolic  - I'm still missing the information about kubeclaritys future in the readme. I just found this issue and the info "by accident" after wondering why that repo is so inactive..

We are actively working on the migration efforts and will provide all the details in the upcoming weeks @grieshaber. Stay tuned in the Project discussion board where we will make the announcement.


Do not catch just to  throw

catch (DocumentClientException de)
{
throw;
}
Is anti-pattern; it is useless

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

ID: 557827fd-e323-7b37-2fb8-a2b6d5c10811
Version Independent ID: 9b04167b-a8f8-d252-971e-e39b181ce589
Content: Azure Cosmos DB: SQL API getting started with .NET Core tutorial | Microsoft Docs
Content Source: articles/cosmos-db/sql-api-dotnetcore-get-started.md
Service: cosmos-db
GitHub Login: @arramac
Microsoft Alias: arramac

@MNF Thank you for your feedback! I have assigned this issue to the author to investigate further and take the right course of action.

Emailed @arramac about this issue.

Emailed @kirankumarkolli about this issue.

@snehagunda will be making the fix to the document

@MNF we fixed the doc to remove the try/catch block, the updates will be live by EOD.

#please-close


indentation in ScintillaNet

Hi, indentation work in ScintillaNet in file opned from hard disk

Can you please clarify? I don't understand the question.

I think issue #35 is what you are looking for.
And here is the final code cause the issue is pretty long: https://gist.github.com/JohnyMac/f2910192987a73a52ab4
The indentation property has been added, So you can remove that region called CodeIndent Handlers

Thank's alot for help


This connector is unusable for all but trivial data operations

This is with regards to the dynamics 365 / CDM connector.
Please add a note that this connector cannot be used to populate any entity that contains a "polymorphic" attribute. This means this connector cannot be used to load data into any non-parent type of entity, for example, contact
TBH it makes this connector unsuable.
Please add a note early in the documentation that lists this constraint and contains examples of the entities that can't be loaded. This will stop data engineers assuming that this is a viable data integration option.
https://feedback.azure.com/forums/270578-data-factory/suggestions/37250212-azure-data-factory-dynamics-365-connector-dataset
https://stackoverflow.com/questions/62054515/loading-records-into-dynamics-365-through-adf

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

ID: 304d4c46-c0ac-05c9-15eb-d8b677ec5e90
Version Independent ID: 36a79d36-2b72-2722-68e5-e167f9a2cd41
Content: Copy data in Dynamics (Common Data Service) - Azure Data Factory
Content Source: articles/data-factory/connector-dynamics-crm-office-365.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@ElectricLlama Thanks for the feedback. We are currently investigating into the issue and will update you shortly.

@linda33wj Do you think adding a note here makes sense?

@ElectricLlama Thanks for the feedback. We have added support for writing data into lookup field.  Please refer to https://docs.microsoft.com/en-us/azure/data-factory/connector-dynamics-crm-office-365#data-type-mapping-for-dynamics section with pointer to guidance in details. Is it what you were looking for? Let know if any further issue.

Thanks for the doco update. I've tested and it does work. I'm curious as to how long this functionality existed before the doco was updated. Also, any reason you did not enable this on the existing (virtual ?) field? For example, contact has a field called parentcustomerid which we use to specify the parent account. But there is also a field called parentcustomeridtype. I spent a lot of time trying to use this to specify account or contact. It would've made more sense to incorporate it in this field.

@ElectricLlama good to know it works for you. The feature was released shortly before the doc is updated, and seems you posted this question at the same time as the doc went live. Sorry for the trouble earlier.
In your example, the parentcustomeridtype is kinda a virtual/sub field for parentcustomerid, ADF doesn't really write to such fields, nor retrieve such fields when importing schema. And Dynamics allow customer to create another field with such name, though rare. Thus we choose to use a pre-defined pattern to represent the entity reference relationship. Hope this makes sense.
#please-close


Inpainting inserts Smart Objects with layer mask matching the initial selection

When using a non-rectangular selection to perform inpainting, such as a lasso selection, the resulting Smart Object should come with a layer mask that masks out the parts that were not included in the selection. This would be especially useful when using more advanced selections such as a feathered lasso selection.

An alternative to this would be an option to keep the selection active after the smart object has been inserted, so that it can be used immediately to create this mask. Honestly, both of these options would be nice to have.

Every time I render the selection goes away, such that it needs to be made again.  Is this the intended use-model or am I doing it wrong?  The selection needs to persist after rendering, otherwise this is a very troublesome workflow.

@Alchete This is a Photoshop limitation - it itself removes the selection, but I am working on a workaround.
However, if you want just to generate more images with the same selection, then you can click "Generate more", and it will use the same selection but new parameters (e.g. prompt, steps, sampling method, etc).

Done. Could you test and give feedback on how it works for you?

Done. Could you test and give feedback on how it works for you?

Almost perfect, the process of creating an inpainting with a layer mask is exactly what I was hoping for. There is only one problem, I made this separate issue about it: #36


Improvements

Avoid duplicated log
Support HTTPS on RabbitMQ API
Search for queues using regex
Improvement on exception handling
Adjusted memory calculation

Hello there.
I see a lot of interesting features!
I'm going to fix the failing tests and also break the commit into commits for each feature to keep the history meaningful.
You will still be listed as the author.
Please let me close this pull request and add you as a reviewer to a new one with the broken down commits and fixed tests.
Thank you!


Issue 231: ensure ca.pem makes it to multi-masters

Closes #231

You're right again, the masters should have all the certs.
Instead of your change i  would do something like :
- name: certs | Copy certs on masters
  copy:
    content: "{{ item.content|b64decode }}"
    dest: "{{ item.source }}"
  with_items: '{{slurp_certs.results}}'
  when: inventory_hostname in groups['kube-master'] and sync_certs|default(false) and
        inventory_hostname != groups['kube-master'][0]

removing the condition:
when: item.item in master_certs and

Is this ok for you @rsmitty ?

Yeah, that works for me. That way every master would just have all the certs. Okay, stand by.

Good to go 😄

Great :)


[LanguageBuild Calendar in React Using React-Calendar Library

Topic Suggestion
Build Calendar in React Using React-Calendar Library
Proposed title of article
Build Calendar in React Using React-Calendar Library
Use keyword research to improve your article's SEO.
Proposed article introduction
React-Calendar is a simple calendar library that provides the ability to pick days, months, years, or even decades. It also supports date range selection and a variety of languages for more complex use cases.
A React calendar component is a good choice when you need to allow users to select a specific date, like if your app has a form field for date of birth or employee start date. Another good example would be an application that allows users to book appointments. A user would be able to select a specific date and time slot from available options. For scenarios like this, a calendar component is probably the best bet.
It’s a very flexible and versatile library that you can use in virtually any application.
Key takeaways
The tutorial will show readers how to:

Integrate react-calender library into a react application.
How to enable date range feature using selectRange.
How to style and customize react-calendar

Article quality
The article will give a detailed guide into react-calendar library. It will explain key concepts to readers which is unavailable in the documentations and other platforms.
References
N/a
Conclusion
At the end of the tutorial, the reader should be able to achieve the goals listed above while also learning how to create useful calendars in their applications.
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

Sounds like a helpful topic - let's please be sure it adds value beyond what is in any official docs and/or what is covered in other blog sites. (the articles should go beyond a basic explanation - and it is always best to reference any EngEd article and build upon it). @codeInn001
Please be attentive to grammar/readability and make sure that you put your article through a thorough editing review prior to submitting it for final approval. (There are some great free tools that we reference in EngEd resources.)
ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.
Please be sure to double-check that it does not overlap with any existing EngEd articles, articles on other blog sites, or any incoming EngEd topic suggestions (if you haven't already) to avoid any potential article closure, please reference any relevant EngEd articles in yours. - Approved

@ahmadmardeni1 Can you please reopen this issue, I am almost through with article.
Thanks


Javascript blocks should always require new lines and curly braces

For consistency, the body of all blocks in javascript should require new lines and curly braces.
eg:
if (true) {
    callSomeFunction();
}

not
if (true) callSomeFunction();

Note: This discussion originally started on this PR.

We discussed in person and agreed that the curly rule set to all is our best option for now. We would be ok with allowing just the single line if syntax but there's no way to allow that without allowing undesirable syntaxes (the multi config comes closest).

I realized while testing the fix for this in #87 that just using the curly rule will still allow this syntax:
if (foo) { doSomething; }
Our options are:

Allow that syntax by only enabling the curly rule
Set 'brace-style': ['error', '1tbs', { allowSingleLine: false }] in addition to curly which forces the body and closing brace to be on subsequent lines.
Only set 'brace-style': ['error', '1tbs', { allowSingleLine: false }] but NOT curly, which allows single-line statements on the same line if they don't have braces.

// Example A. Allowed by 3
if (foo) doSomething();

// Example B. Allowed by 3
if (foo) doSomethingConditionally(); doSomethingUnconditionallyButItLooksConditional();

// Example C. Allowed by 1
if (foo) { doSomething(); }

// Example D. Allowed by 1
if (foo) { doSomething(); doSomethingElse(); }

// Example E. Always disallowed by Airbnb config for non-block-statement-body-position
if (foo)
   doSomething();

// Example F. Always allowed
if (foo) {
   doSomething();
}

The original bug report requested 2. That's my vote too because I don't like permitting example B above and find the example C syntax ugly. But if anyone wants to argue for 1 or 3, we can discuss it again. @rajsite @mure @TrevorKarjanis

We agreed in person to require the body to be on a new line (option 2). @jattasNI to revive the PR to make this happen.


Add assertions to help save lots of wasted time with known bad configurations.

Is your request related to a new offering from AWS?
irrelevant
Is your request related to a problem? Please describe.
The combination of the following things causes people to waste a lot of time while trying to get these modules working:

It's very easy to configure these modules in a non-functional way that is known to be non-functional to experts.
The main documentation sources (variable docs and examples) often don't provide enough information to know when you're doing something wrong.
Trying to troubleshoot can take an enormous amount of time.  A 1 line fix could take ~half an hour to do 1 cycle of try a fix->apply->wait 10+ mins->destroy->wait 10+ mins.

Some examples:

https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1972#issuecomment-1086239416

Note the mention of this taking "2 weeks" so far for that person.  also note several other people running into the problem, and note that the solution was a single missing line which several experts weren't able to see right away.

https://github.com/terraform-aws-modules/terraform-aws-eks/blob/v19.21.0/docs/faq.md#i-received-an-error-expect-exactly-one-securitygroup-tagged-with-kubernetesioclustername-

Note that the variable docs and examples don't mention the mutually exclusive nature of these settings.  This is not an exceptional case.

use_custom_launch_template = false will cause most security group variables on both the eks and the node group modules to be silently ignored.  Making the user's root module look very misleading.

Describe the solution you'd like.
Add assertions to catch obviously incorrect usage.
For example, for https://github.com/terraform-aws-modules/terraform-aws-eks/blob/v19.21.0/docs/faq.md#i-received-an-error-expect-exactly-one-securitygroup-tagged-with-kubernetesioclustername- check that only 1 of the two is set.  It would probably also allow deleting the FAQ entry then because the question will probably no longer come up at all.
There's probably an overwhelming number of assertions one could add, but at least adding the ones for common issues would already save a LOT of time.  If there's an issue filed, or an FAQ entry, those are clearly good candidates.
When transparent assertions aren't possible...
For https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1972, it's more challenging to implement the assertion because you have to check across resources.  module.eks.cluster_ip_family needs to correspond with module.vpc_cni_irsa.vpc_cni_enable_ipv(4|6).  I don't think there's any way to transparently add assertions to cases like this.
Option 1: change the module structure
Imagine a different approach to the IRSA module where the usage would look like:
module "irsa_vpc_cni" {
  source = "terraform-aws-modules/iam/aws//modules/iam-role-for-service-accounts-eks2/vpc-cni"
  eks = module.eks
}

Passing the full module.eks in would then allow running the necessary checks.
Side note
This approach would also avoid users having to do any of this stuff
  attach_vpc_cni_policy = true
  vpc_cni_enable_ipv6   = true

  oidc_providers = {
    main = {
      provider_arn               = module.eks.oidc_provider_arn
      namespace_service_accounts = ["kube-system:aws-node"]
    }
  }

because this would already be baked in to the VPC CNI specific IRSA module (and similarly for other cases where there currently exists an attach_*_policy boolean.
Option 2: separate assert-only modules
I imagine there would be some objections to passing the entire module.eks.  I can see good arguments on both sides of that battle. If it's not desired, then the current module structure could be maintained, but also add new assert-only modules that might look like:
module "irsa_vpc_cni_check" {
  source = "terraform-aws-modules/iam/aws//modules/iam-role-for-service-accounts-eks/vpc-cni-check"
  eks = module.eks
  irsa = module.irsa_vpc_cni
}

(a very rough sketch of an idea, I'm not saying to design it to look exactly like this).
Describe alternatives you've considered.
Completely rework the module design to follow the "make it hard to use wrong" principle so that assertions would be less necessary.  The Option 1 above goes in this direction but it could be applied in a broader scope across all the modules.  (That's a much bigger discussion though, it could help a lot with this problem, but it probably doesn't make sense to discuss here).
Additional context
none

We would never create an argument that relies on an entire module output - that would be a very poor, fragile, and restrictive choice. I also don't agree with the assumption that assertions fix the issues linked. We cannot do anything within a module that alerts users to a missing provider implementation (first issue referenced). I do not see the validity nor the feasibility of this request

Do you know of any precedent for requiring version syncing of co-released submodules? It seems like a handy tool that could help libraries written in Terraform to solve problems with a more user friendly API. Modules are roughly equivalent to functions in other languages, with complex input and output structs. In other languages if you produce a library that has functions and complex structs, you wouldn't worry about passing pointers to those complex structs between different parts of the API.

Terraform is not like other software languages. You don't have abstractions - you can't put something behind an interface and have free will to change that. Nearly anything you do, its felt by users. If I change the shape of an input or output, theres nothing that can transform that or mask it, users experience that. Theres also nothing I can do to refactor a module without users feeling that (save for some of the newer features such as move blocks but those are still quite basic - you cannot use them on looping constructs).
I'm not sure what the issue is thats trying to be solved here. Said differently - how would you prevent "bad configurations" with things like Ansible configurations or Kubernetes manifests?

thank you! closing this one out for now, we'll continue to evaluate the functionality that the Terraform core provides for future improvements


Support passkey or webauthn login

Feature Description
Passkeys login is the future passwordless way to auth user.
Describe the solution you'd like
Should like this project: https://github.com/teamhanko/hanko
Describe alternatives you've considered
https://github.com/teamhanko/hanko
Additional context
None

Thanks @iflamed I will start working on this feature from August :-)

Great feature suggestion. I am not good enough in Go, yet to support with a PR, but I was told that this library is a good starting point for Passkey integration: https://github.com/go-webauthn/webauthn.


Release 1.4.1

OPS 1.4.1 is a minor release to fix issues with imports when not all integrations are installed.
Miscellaneous improvements

Remove nose from test_helpers (#958)
Fix so SimStore tests pass without simtk.unit (#957)
fix omt is None error in test suite (#954 @sroet)

I want to get this out soon, so I'll just leave it open for discussion for 6 hours, merging no earlier than Wed 30 Dec 17:00 GMT (18:00 local).
(I can't imagine there's anything controversial in a patch release like this.)


Creation of users from organisation admin throws error

undefined index user_id and different error for duplicate entry for key email_unique in User.php line 52

Error:

Notice:  Undefined index: user_id in /home/rushil/Documents/PROJECTS/reading-charity-connect/rest/user_organizations.php on line 51

Fatal error:  Uncaught PDOException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'user_id' cannot be null in /home/rushil/Documents/PROJECTS/reading-charity-connect/entities/UserOrganization.php:44
Stack trace:
#0 /home/rushil/Documents/PROJECTS/reading-charity-connect/entities/UserOrganization.php(44): PDOStatement->execute(Array)
#1 /home/rushil/Documents/PROJECTS/reading-charity-connect/rest/user_organizations.php(52): UserOrganization->create()
#2 {main}
  thrown in /home/rushil/Documents/PROJECTS/reading-charity-connect/entities/UserOrganization.php on line 44

User is created in backend, but front-end does not close pop-up dialog and does not reload table with a new GET request.
Refresh is required to show new user.

When duplicate email is found, and user selects to continue creation of user, system creates user with the same name as the duplicate found user, overriding the username that was set.
eg. if John Smith<EMAIL_ADDRESS>exists, and I try to create Jonny Smith<EMAIL_ADDRESS>and hit Yes to the duplicate pop-up, it will create a second entry of John Smith (js@email.com).
is that intended?

No, it's not intended. It should not allow you to create a user with the same e-mail. Instead it should add the existing user to your organization.

Have fixed the error, but the postText denoting successful save does not show

No, it's not intended. It should not allow you to create a user with the same e-mail. Instead it should add the existing user to your organization.

@mmillmor If the user we're creating has the same email within the same organisation (eg from the org admin panel), surely we just don't want to allow them to create a dupe user in the first place?

If it's the same e-mail in the same organization, yes, you are correct - prevent them from creating the new user.


[FEATURE] Grammatical and spelling errors in the website

Description
Website content lots of grammatical and spelling errors, I want to resolve them, Kindly assign me
Screenshots

🥦 Browser
Brave
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (blank for no)

Cool, you can start working on it and make a PR ⚡
Please make sure that you have read our documentation on Commiting guidelines and Pull request guidelines, without proper format the PR might be closed.

Hi there, it has been a while. I would love to know what changes you are making and/or are working on this.


Union Types for the spec property

Adding the Specification part of the entities into GraphQL
Currently, it's kind of nice to query, but a little bit of a pain to manage as theres a lot of duplication
I think that most of this can be fixed with dataloaders and passing references from the entity down to decendent resolvers to it can query.

Instead of the query looking like this:
{
  catalog {
    list {
      metadata {
        name
        annotations {
          key
          value
        }
      }
      ... on ComponentEntity {
        spec {
        	owner
        }
      }
      ... on TemplateEntity {
        spec {
          templater
        }
      }
    }
  }
}

Which currently works, we could reduce the duplciation with the implementation types and make the query look like this:
{
  catalog {
    list {
      metadata {
        name
        annotations {
          key
          value
        }
      }
      spec {
        ... on ComponentEntity {
          owner
        }
        ... on TemplateEntity {
          templater
        }
      }
    }
  }
}

:heavy_check_mark: Checklist

[ ] All tests are passing yarn test
[ ] Screenshots attached (for UI changes)
[ ] Relevant documentation updated
[ ] Prettier run on changed files
[ ] Tests added for new functionality
[ ] Regression tests added for bug fixes

closes #1846


I asked for PRs to make the experience better not to just disable it.


Unexpected Error when trying to create PostgreSQL Flexi Server

I'm trying to create a PostgreSQL Flexi server using the SDK but I am running into an unexpected error when trying to do so.
This is the code that I'm using to create the server:
serverPoller, err := serverSVC.BeginCreate(
        ctx,
	data.ResourceGroup,
	data.ServerName,
	armpostgresqlflexibleservers.Server{
		Location: &data.Location,
		Properties: &armpostgresqlflexibleservers.ServerProperties{
			AdministratorLogin:         &data.AdminUsername,
			AdministratorLoginPassword: &data.AdminPassword,
			Version:                    &data.ServerVersion,
			Network: &armpostgresqlflexibleservers.Network{
				DelegatedSubnetResourceID:   &data.SubnetID,
				PrivateDNSZoneArmResourceID: &data.DnsID,
				PublicNetworkAccess:         &data.PublicIPDisabled,
			},
			Storage: &armpostgresqlflexibleservers.Storage{
				StorageSizeGB: to.Ptr[int32](1024),
			},
			HighAvailability: &armpostgresqlflexibleservers.HighAvailability{
				Mode: &data.HaDisabled,
			},
		},
		SKU: &armpostgresqlflexibleservers.SKU{
			Tier: &data.SkuTier,
			Name: to.Ptr("Standard_B1ms"),
		},
	},
	nil,
)

This is the response from the API call:
[GET https://management.azure.com/subscriptions/<subscription-id>/providers/Microsoft.DBforPostgreSQL/locations/westus/azureAsyncOperation/9f8525f1-c054-4256-935b-e4190535f57c
--------------------------------------------------------------------------------
    RESPONSE 200: 200 OK
    ERROR CODE: InternalServerError
--------------------------------------------------------------------------------
    {
      "name": "9f8525f1-c054-4256-935b-e4190535f57c",
      "status": "Failed",
      "startTime": "2022-07-06T11:39:29.997Z",
      "error": {
        "code": "InternalServerError",
        "message": "An unexpected error occured while processing the request. Tracking ID: '20c6992d-9c1c-483d-b11a-d9491bbbd178'"
      }
    }
--------------------------------------------------------------------------------
    ]

I'm using github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers v1.0.0 in my code
I am also able to successfully create a PostgreSQL server via the Azure Portal with the same parameters as my code.

Looks like this was an error due to the parameters I was passing for SKU.
There doesn't seem to be validations for which Tier/Name combinations work as defined by this document: https://docs.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-compute-storage#compute-tiers-vcores-and-server-types
It would be great to add these validations to the library instead of sending across an InternalServerError here.

@vishwakalyanaraman Thanks for your feedback. All our Go mgmt. SDKs are auto generated from service swagger definitions. In swagger, sku name is just a string. I'll let service team to take a look. @navba-MSFT I think there are two things here: 1. service need to return a clearly error to indicate the sku name is not valid instead of an internal server error. 2. either change sku name into an un-sealed enum or add some doc for the string value will help customer to know how to set the value.

@vishwakalyanaraman @tadelesh Thanks for bringing this to our attention. I am adding the service team to look into this.
@sunilagarwal, @lfittl-msft, @sr-msft, @niklarin @DaeunYim  Could you please look into this and provide some pointers when you get a chance ? Awaiting your reply.

@vishwakalyanaraman @tadelesh Thanks for bringing this to our attention. I am adding the service team to look into this.
@sunilagarwal, @lfittl-msft, @sr-msft, @niklarin @DaeunYim Could you please look into this and provide some pointers when you get a chance ? Awaiting your reply.

Any update?


Confidence vs degree of protection

We conflate confidence and degree of protection. Example:

if we find a commit with no PR we have high confidence it's not branch-protected
when we calculate confidence , e.g. for branch protection, we +1 for each sub test success. This seems to mean 'degree of protection'

We should disambiguate the two.

several teams are looking at using the results of scorecard, so let's make our results more consistent. Making this a q2 milestone.

several teams are looking at using the results of scorecard, so let's make our results more consistent. Making this a q2 milestone.

Who are the several teams? Could you please name some of them?

Closing as we fixed this as part of using score-based results.


Versions details outdated

It says: "Currently, only version 0301 is available for GPT-35-Turbo and 0314 for GPT-4 models."
However, I believe 0613 is available now.

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

ID: 13994f3e-a96a-8804-4deb-7e0adad7f479
Version Independent ID: e087d8ce-bf3a-f12c-41dc-3ea924c6f089
Content: How to work with the GPT-35-Turbo and GPT-4 models - Azure OpenAI Service
Content Source: articles/cognitive-services/openai/how-to/chatgpt.md
Service: cognitive-services
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@pamelafox
Thanks for your feedback! We will investigate and update as appropriate.

@mrbullwinkle
could you please review this and update as appropriate.

@pamelafox
I've delegated this to @mrbullwinkle, a content author, to review and share their valuable insights.

Thanks for reporting this. The associated docs have been updated.

#please-close


Refactor Enqueuers

Summary
Refactor both enqueuers to have a common backbone.
A notable change to the API is: _get_executor_init which handles the initialization of the ProcessPool.
Related Issues
PR Overview

[ ] This PR requires new unit tests [y/n] (make sure tests are included)
[ ] This PR requires to update the documentation [y/n] (make sure the docs are up-to-date)
[x] This PR is backwards compatible [y/n]
[ ] This PR changes the current API [y/n] (all API changes need to be approved by fchollet)

cc @datumbox @de-vri-es

For what's worth, I ran again this update on a multi-gpu setup and it's very quick. Thanks for cleaning up the mess Frederic, the code looks neat.


Doesn't seem to activate for the letter "r".

Not sure how many languages have an accent for the letter r, but Czech has the "ř" letter

It is working on my side. Which version are you using? Is it working for all other Czech special letters?

I am on PowerToys version v0.62.1
It seems to be working for other letters with háčky (typed with PowerAccent)


NavigationHistory class not being imported

After following the steps described in the Readme file to import the library I don't get the NavigationHistory.java file  under the com.lockwood.memorizingpager package, so I can't use the library.
Any idea what may be wrong?

Indeed ... Thanks for pointing out the error. Updated release, now there are no problems
Grab new version via Gradle:
allprojects {
	repositories {
		...
		maven { url 'https://jitpack.io' }
	}
}

dependencies {
    	implementation 'com.github.lndmflngs:memorizing-pager:2.0.1'
}


Update load-cesium-es6.js

Thanks for the pull request @TJKoury!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

Thanks for the fix @TJKoury!


Get rid of frontend-server standalone executable, call frontend-server/compiler as in-process dart package directly.

frontend-server was built to run as standalone executable because flutter tools and engine were running on different versions of dart sdk. Few months back the change was made to run flutter tools and engine on the same dart sdk. That means that there is no need to have frontend-server as standalone process, compiler can be invoked directly from flutter tools.

cc @a-siva

Is this still an issue?

@aam Is this issue still relevant?

Hello @markusaksli-nc
The issue seems to be non relevent to the current circumstances. It talks about the core flutter architecture and can not be considered an issue anymore.
Please go ahead and close this issue.
Thanks!

Not much changed since the issue was filed.
Main motivation for rolling frontend-server into flutter is to bypass and cut out all clumsy heavyweight stdin/stdout/file interaction that stands between flutter tools and dart compiler.
It feels like the change would be encapsulated in https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/compile.dart where instead of talking to externally running frontend server process via stdin/stdout, it would talk to compiler(might still make sense to keep frontend-server abstraction) via dart calls.
cc @jonahwilliams

I would be on board with this change, but we'd need to find a way to download or depend on the sources required (front_end, kernel, frontend_server are not published IIRC).
We could add the sources ourselves, but we'd need some way to keep it in sync with what the dart SDK is doing so that we can avoid breaking if new dependencies are added/removed.

Do we expect to see a performance difference by making this change?

Performance probably will be improved(not sure how much), but it will reduce complexity and allow for simpler/faster integration of new flutter-specific compiler optimizations(like recent widget cache change)

We might still want to run the server in a separate isolate to avoid blocking/being blocked other work the tool might be doing (spinner status? probably not that important). I think we could use TransferableTypedData to avoid writing to disk, but I dunno what the serialization costs are like.

I would be on board with this change, but we'd need to find a way to download or depend on the sources required (front_end, kernel, frontend_server are not published IIRC).

Ideally these sources should be coming as part of flutter engine (dart-sdk) download.

We might still want to run the server in a separate isolate

Yeah, possibly.

We might still want to run the server in a separate isolate to avoid blocking/being blocked other work the tool might be doing (spinner status? probably not that important). I think we could use TransferableTypedData to avoid writing to disk, but I dunno what the serialization costs are like.

With not clear performance gain characteristics and the issue mentioned above I am not sure I see the immediate need to make this change. Maybe we should mark this as a low priority issue to be done later.


Cherry-Picking: patch moby-engine to address CVE-2023-45288, CVE-2023-44487

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] If you are adding/removing a .spec file that has multiple-versions supported, please add @microsoft/cbl-mariner-multi-package-reviewers team as reviewer (Eg. golang has 2 versions 1.18, 1.21+)
[ ] Ready to merge

Summary

Cherry-pick moby-engine patches to address CVE-2023-45288 and CVE-2023-44487.
Change Log

cherry-pick moby-engine changes from https://github.com/microsoft/azurelinux/commit/a264db1f7576d5f22d5672c46718f020bd1a7b1c
cherry-pick moby-engine changes from https://github.com/microsoft/azurelinux/commit/c433706dbc544d5a4aefba91d28ee7a5716bcf30

Does this affect the toolchain?

NO
Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-2023-44487
https://nvd.nist.gov/vuln/detail/CVE-2023-45288

Test Methodology

BuddyBuild: 581849

Look like CVE-2023-45288 is already fixed: https://github.com/microsoft/azurelinux/pull/8866/commits/761ea7fce61c705468bdd801176818da0407f15d#diff-140ffa337afb24379285262d8c092d5f4516a67f42b707cd40ea9f9d7f089d2a


Improving Deque#delete

This is an attempt to improve Deque#delete a bit.  This eliminates the object lookup step index(obj), but probably could still use some improvement with the actual deletion (delete_at).
How is everyone benchmarking code execution?

:+1:
Deque   5.18  (± 0.78%)  1.70× slower
Dequ2    8.8  (± 2.45%)       fastest

require "benchmark"

class Dequ2(T) < Deque(T)
  def delete(obj)
    found = false
    i = 0
    while i < @size
      if self[i] == obj
        delete_at(i)
        found = true
      else
        i += 1
      end
    end
    found
  end
end

Benchmark.ips do |x|
  {% for cls in %w[Deque Dequ2] %}
  x.report({{cls}}) do
    c = {{cls.id}}(Int32).new
    10000.times do
      4.times do |i|
        c.push i
      end
    end
    c.delete(3)
  end
  {% end %}
end

Of course, this could be improved more. Index lookups are not exactly fast, neither is shifting a lot of items after every delete (as opposed to only once for each item)

@arktisklada Awesome! These performance improvements are always welcome, thank you! :-)


Use old constructor for java 1.8 compatibility

This was needed for me to use the library in an Android project. If you don't want to use a @deprecated method I understand, but all things considered I think it is a worthwhile change.

Merged


feat(staff): implemented custom id

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support null (string | number | undefined | null) for v-model of UInput

Description
Use case: some api returns null on properties that does not exist. It's convenient to populate the form state with the fetched data with possibly null data.
Currently, UInput's v-model only support string | number | undefined, and gives an type error if null is in the union type.
Example project:
https://stackblitz.com/edit/nuxt-ui-5bnxk6?file=components%2FFeatureRequest.vue
Additional context

May I handle this issue @benjamincanac ?

The reason why null isn't supported is because UInput uses the input HTML's tag under the hood. As per the HTMLInputElement documentation expects only String, Number or Boolean. The Undefined actually comes from UInput's props initialization as an empty string.
For the moment my best suggestion would be to manually handle the null as an undefined, but we could take a second look at this once the rewrite at #1289 is complete.

Also, closing it for now, but feel free to ping me or reopen

We also have the problem that we are using a graphql codegen which has the Maybe type which translates to string | null, and all graphql queries also come with null values


[RFC] Register scalars with boxed fn impl

Which issue does this PR close?

Closes #9892.
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

@alamb I would like an early comment before moving on.

Marking as draft as we sort out the details


Implement shellceck in CI/CD

This is a kind of insane pure bash repo. We should implement shell check to run on all pull requests and fix any recommendations from shellcheck (https://www.shellcheck.net/)
Shellcheck is pretty good at catching and helping guard against common bash gotchas and can also help us improve on standards compliance and cross platform support.
For example I get a bunch of suggestions from shellcheck for libexec/helpers.sh
[Line 17:](javascript:setPosition(17, 32))
    echo -e "tgenv: $(basename ${0}): [ERROR] ${1}" >&2
                               ^-- [SC2086](https://www.shellcheck.net/wiki/SC2086) (info): Double quote to prevent globbing and word splitting.

Did you mean: ([apply this](javascript:applyFixIndex([0])), apply [all SC2086](javascript:applyFixCode(2086)))
    echo -e "tgenv: $(basename "${0}"): [ERROR] ${1}" >&2

[Line 19:](javascript:setPosition(19, 32))
    echo -e "tgenv: $(basename ${0}): ${RED}[ERROR] ${1}${RESET}" >&2
                               ^-- [SC2086](https://www.shellcheck.net/wiki/SC2086) (info): Double quote to prevent globbing and word splitting.

Did you mean: ([apply this](javascript:applyFixIndex([1])), apply [all SC2086](javascript:applyFixCode(2086)))
    echo -e "tgenv: $(basename "${0}"): ${RED}[ERROR] ${1}${RESET}" >&2

[Line 26:](javascript:setPosition(26, 32))
    echo -e "tgenv: $(basename ${0}): [WARN] ${1}" >&2
                               ^-- [SC2086](https://www.shellcheck.net/wiki/SC2086) (info): Double quote to prevent globbing and word splitting.

Did you mean: ([apply this](javascript:applyFixIndex([2])), apply [all SC2086](javascript:applyFixCode(2086)))
    echo -e "tgenv: $(basename "${0}"): [WARN] ${1}" >&2

[Line 28:](javascript:setPosition(28, 32))
    echo -e "tgenv: $(basename ${0}): ${YELLOW}[WARN] ${1}${RESET}" >&2
                               ^-- [SC2086](https://www.shellcheck.net/wiki/SC2086) (info): Double quote to prevent globbing and word splitting.

Did you mean: ([apply this](javascript:applyFixIndex([3])), apply [all SC2086](javascript:applyFixCode(2086)))
    echo -e "tgenv: $(basename "${0}"): ${YELLOW}[WARN] ${1}${RESET}" >&2

@iokiwi thanks for share, to be honest I didn't know about this tool and would be interesting for us.

closed accidentally due to erroneous link from wrong pr

@weyderfs no hurry or anything but I just wanted to highlight that there is a pr open to close this issue that could use review when you get a chance


Update wgpu to 0.12

This PR updates wgpu to version 0.12
Most changes were simple renames of the various structs and enums for example wgpu::BackendBit::PRIMARY is now wgpu::Backends::PRIMARY
Some notable changes were frame.present() must be called explicitly prior to being dropped in release_frame or else nothing is shown.
Motivation:

The current version (0.9) dose not match the current documentation for wgsl particularly well this should help with this

Differences include things like no [[block]] and <storage, read_write> types

I wanted to work on SBBO (var<storage>) to make some interesting shaders but couldn't get any of the examples of how to do this to validate on the current version of wgpu

Follows ups

Should this get merged I intend to add the storage buffers so that larger data can be passed onto the shader than is supported in uniform
Also if I get the time I'd like to add some examples on how to add shaders since

I will merge it as is and then apply necessary changes. Thanks again!

Thanks for merging. I a working on a branch which enables the Storage buffer type. Just need to decide how to handle read only storage and read write storage. For now I have made all storages read write type but I think I store the kind on init like this:
enum StorageBufferKind {
  Read,
  ReadWrite,
}

#[derive(Default)]
pub struct StorageBuffer {
    kind: StorageBufferKind,
    wgpu_buffer: Option<wgpu::Buffer>,
}

impl StorageBuffer {
    pub fn new_readonly() -> Self {
        Self {
            kind: StorageBufferKind::Read,
            wgpu_buffer: Default::default(),
        }
    }

    pub fn new_readwrite() -> Self {
        Self {
            kind: StorageBufferKind::ReadWrite,
            wgpu_buffer: Default::default(),
        }
    }
}

I would only ask you to rename Kind to Mode, so it will fit the rest of the code.

Sure I have done the rename to Mode. I am going to run it through some tests then make the PR


Pages stuck when rapid swipe twice or fast

Hallo Pascal Gula, sorry to bother you again.
I found an issue when swiping pages that you can check it by below.
demo
app
This issue particularly happens in the page contain a lot of element ( Maybe 10 ~ 20 up images I'm not sure of that. )
best regard
Johnson

this is fixed in master, I will release a new 1.2.4 version, when I will close 2 ongoing Issue! Thanks for spotting the Issue! :)


Debian 9 (Stretch)

I'm trying to setup the panel and everything worked just fine until the moment I had to install Docker.
I'm using Debian 9 (Stretch) on a OVH server, and when I type docker info, I don't get all the warnings shown in this page:
https://daemon.pterodactyl.io/docs/installing-docker-on-debian-8
I only get:
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
Should I ignore it?

You need to update the kernel of OVH.
Here Info to update it for Debian 9:
First:
apt-get install linux-image-4.9.0-3-amd64
Then you must edit the grup with:
nano /etc/default/grub
And edit the value:
GRUB_DEFAULT=0
To:
GRUB_DEFAULT=1
Finally:
update-grub && reboot

Thank you!
But now when I type docker info I get another warning:
WARNING: No swap limit support

Edit the grup:
Add the "swapaccount=1 cgroup_enable=memory" on the GRUB_CMDLINE_LINUX_DEFAULT.
GRUB_CMDLINE_LINUX_DEFAULT="swapaccount=1 cgroup_enable=memory"

Ok, there were some commands there already
my GRUB_CMDLINE_LINUX_DEFAULT is as follows:
GRUB_CMDLINE_LINUX_DEFAULT="noquiet nosplash net.ifnames=0 biosdevname=0 swapaccount=1 cgroup_enable=memory"
after running update-grub and docker info, still the same: WARNING: No swap limit support

Do a:
reboot

This is not a bug with this software.


Support different styles for validation

:octocat: cibot: Thank you for posting issue #861. The person in charge will reply soon.

:octocat: cibot: Thank you for posting issue #861. The person in charge will reply soon.


🔨 Add Make targets to run the postgres sql scripts

These make targets will persist the data to the postgreSQL database.

Thanks a lot for your suggestions.
You've mixed unrelated concerns in a single pull request, mainly:

Whitespace change in readme, etc. Please refrain from doing that, it creates distractions when reviewing
A potential bug where you explicitly deleted an enum? Please create a new issue for this. It's not related to creating make targets
The main improvement of creating make targets

I will reject the make targets for these reasons:

They might work on some OS but not on others (e.g. Windows)
You only created them for PostgreSQL, not the other dialects

I'm open to improving such things, but in order to prevent unnecessary work in the future, I would expect the change to include several OS's, all dialects, and possibly even tests. It's also OK not to change anything in this area, so perhaps, let's just leave things.


CloudEvent(s)Envelope inconsistently named

What version of Dapr?
0.3
Expected Behavior
The same structure in different languages/repos should have the same name (perhaps other than language casing conventions).  The envelope used for pub/sub is named CloudEventEnvelope in protobuf's,
https://github.com/dapr/dapr/blob/2cdc91c3f41b97280fffed378bbc15c9fe074a64/pkg/proto/daprclient/daprclient.proto#L21
but is named CloudEventsEnvelope in components-contrib,
https://github.com/dapr/components-contrib/blob/e7639f90c9d08a01319e530a6e5ecb578a69b7d2/pubsub/envelope.go#L23
which is referred to by the runtime.

Because the Cloud Events spec has free form fields, it seems like CloudEventsEnvelop was removed in favor of map[string]interface{}. As indicated above, CloudEventsEnvelop is probably how the protobuf message should be named (since it is the CloudEvents spec), but renaming it is a breaking change.


screensaver active requirement

The article says "...then the user’s session locks by invoking the screen saver (screen saver should be active on the destination machine)."  If having the screensaver active is a requirement for the Interactive logon: Machine inactivity limit to work, then you should include instructions on how to make the screensaver active using GPO.

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

ID: 75ab75c2-3bfd-bde6-8341-65ba79e9fe65
Version Independent ID: 7224910c-ac05-26b2-f712-9a5993432615
Content: Interactive logon Machine inactivity limit (Windows 10) - Windows security
Content Source: windows/security/threat-protection/security-policy-settings/interactive-logon-machine-inactivity-limit.md
Product: w10
Technology: windows
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@officedocsbot assign @jvsam

Hello @jmjust, thank you for bringing this to our attention. I will forward your suggestion to the Windows content writing team for review. We always strive to improve the quality of the technical documentation of Microsoft Docs so your feedback is appreciated!

@jmjust
With the help of your feedback, the content has been updated with relevant changes accordingly. Thanks.


Create dauth_network.md

Project Abstract

Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[x] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @deanyyd:matrix.org (change the homeserver if you use a different one)

 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.

Hi @yyd106 how is milestone 1 coming along?

Hi @yyd106 how is milestone 1 coming along?

Hi @keeganquigley , We will need another week, but we will deliver both milestones at once. This is because we found a close correlation between the two milestones, and the project team needs to use the DAuth SDK. So we decide to deliver a finalized version. Is that work?

Thanks for the update @yyd106 yep that works.

Hi @yyd106 any news on the delivery?

Hi @yyd106 how is milestone 1 coming along?

Hi @keeganquigley , We will need another week, but we will deliver both milestones at once. This is because we found a close correlation between the two milestones, and the project team needs to use the DAuth SDK. So we decide to deliver a finalized version. Is that work?

Yes, we are work on the integration by Linea last few weeks. We provide attestation service for their Proof of Humanity and got 400K users authentication on our platform. Will finalize and submit the deliverables and docs this week.

Thanks for the updates @yyd106 are you still planning to submit the delivery this week?

Yes @keeganquigley

Hi @keeganquigley , The deliverables PR is submitted: https://github.com/w3f/Grant-Milestone-Delivery/pull/1105

Hi @yyd106 how is milestone 2 coming along?

pinging @yyd106

pinging @scott0927

Hi @yyd106 please let us know if you are still working on this grant. Otherwise we will cancel it in a few weeks due to inactivity. Thank you.

Hi @keeganquigley , I think dauth network has delivered all the milestones? Is there anything we have missing?

Hi @Metizen @yyd106 ah I see that our records didn't properly update due to both milestones being delivered at the same time. Thanks, please disregard. My apologies for the false alarm. Will fix this on our end.


Path parameter not accessible when using app.onError()

What version of Hono are you using?
3.8.0
What runtime/platform is your app running on?
Cloudflare Workers
What steps can reproduce the bug?
When using app.onError() within a nested route, the path parameters are not accessible.
c.req.param('assignmentId') does not work when app.onError(err, c) is in the nested route file
index.js
routes/example.js
See this project for example: https://github.com/justinwride/hono-path
What is the expected behavior?
I expect to access the path parameter for the route /assignments/:assignmentId? using c.req.param('assignmentId')
What do you see instead?
Instead, c.req.param('assignmentId') is undefined
Additional information
It works if app.onError() is put in index.js, but not if it is used in routes/example.js.
I have been experimenting with Hono and enjoy the simplicity and speed. I'm the CTO of an ed-tech company and hope to use it more in our tech stack.

Hi @justinwride
Thanks for the report. This appears to be a bug caused by #1566 and will be investigated.

Hi @justinwride!
Thank you for reporting with the kind explanation.
This issue has been fixed by @usualoma's implementation and the release v3.8.1 includes it. Please give it a try!

Thanks @yusukebe and @usualoma! 💯
The fix was very quick and works perfectly. Hono is awesome!


Is it possible to prepend an item / Remove specific items

With the way I'm implementing this search bar I'm unable to use the built in loading indicator so, I've been trying to implement my own but I'm having some trouble.
I'm using the noChoicesText to give some feedback if the search input is below the search floor

As soon as the input is over the search floor I call my API to retrieve the results that match that search. While that's happening I'm trying to have a 'Searching...' indicator replace the 'Please enter ... characters' text.

The best I've been able to do so far is to append another noChoices item to the list with the text that I want using
            notice = loadingText;             dropdownItem = choices._getTemplate('notice', notice, 'no-results');             choices.choiceList.append(dropdownItem);
But this just appends the loading indicator item to the bottom of the list and keeps the other "Please enter ... Characters" text until the items load in and resets the list.
The solution I'm looking for is either a way to prepend an item to the top of the list OR a way to remove the noChoicesText object without having to reset the whole list. Preferably both.
Any suggestions are welcome! I realize I'm not necessarily using the tool in the way it's meant to be, but it's the best option I have! I'm trying to get away from select2's jquery dependency.

The solution I've decided to use for right now is to change the noChoicesText and clear the list so it updates. I'm happy with how it is now, but not closing this just in case someone knows how to prepend items.
This is what I'm doing now to show that it's searching:
message = ('Searching...'); choices.config.noChoicesText = message; choices.clearChoices();


How About Loading the Whole Document

There should be a way in the Soothstate js to load the whole document if one need to? so we dont have to specify container Id it will just reload the whole content. I did some experiment and had to modify the script a bit.
I used this small piece of code to replace HTML content of whole document:
document.open("text/html", "replace");
document.write(data);
document.close();
This will execute all my scripts correctly and load the page like we normally do but with a transition giving user a transition experience without reload the page.
** onReady will be Like this **

onReady: {
duration: 0,
render: function ($container, $newContent) {
                $container.removeClass('is-exiting');

                var currentUrl = $container.data('smoothState').href;
                var cache = $container.data('smoothState').cache;

                var currentPageCache = cache[currentUrl];

                document.open("text/html", "replace");
                document.write(currentPageCache.doc);
                document.close();
            }
        }

Awesome!

I couldn't get it to work. But, would be sweet if it did.


The following StateError was thrown building: Bad state: field does not exist within the DocumentSnapshotPlatform

@Chandrakant123456
Please provide flutter doctor -v and a minimal complete reproducible code sample that shows the issue. Just stating the error without any description isn't helpful.

Error Report 👍:
E/flutter (18312): [ERROR:flutter/lib/ui/ui_dart_state.cc(177)] Unhandled Exception: Bad state: field does not exist within the DocumentSnapshotPlatform
E/flutter (18312): #0      DocumentSnapshotPlatform.get._findKeyValueInMap (package:cloud_firestore_platform_interface/src/platform_interface/platform_interface_document_snapshot.dart:82:7)
E/flutter (18312): #1      DocumentSnapshotPlatform.get._findComponent (package:cloud_firestore_platform_interface/src/platform_interface/platform_interface_document_snapshot.dart:98:41)
E/flutter (18312): #2      DocumentSnapshotPlatform.get (package:cloud_firestore_platform_interface/src/platform_interface/platform_interface_document_snapshot.dart:113:26)
E/flutter (18312): #3      DocumentSnapshot.get (package:cloud_firestore/src/document_snapshot.dart:49:43)
E/flutter (18312): #4      DocumentSnapshot.[] (package:cloud_firestore/src/document_snapshot.dart:56:41)
E/flutter (18312): #5      new Userr.fromDocument (package:fast_access/models/user.dart:100:20)
Error in Code:
factory Userr.fromDocument(DocumentSnapshot doc) {
return Userr(
id: doc.documentID,
email: doc['email'],
username: doc['username'],
url: doc['url'],
profileName: doc['profileName'],
bio: doc['bio'],
subject1: doc['subject1'],
subject2: doc['subject2'],

This is probably related to recent changes in DocumentSnapshot, your factory is looking for the data map, which used to be in doc, but nows its in doc.data() - except DocumentID
So for your factory, one way to change it would be to adjust to:
factory Userr.fromDocument(DocumentSnapshot doc, Map docdata) {
return Userr(
id: doc.id,
email: docdata['email'],
username: docdata['username'],
url: docdata['url'],
profileName: docdata['profileName'],
bio: docdata['bio'],
subject1: docdata['subject1'],
subject2: docdata['subject2'],

and when you call it, you'll need to do something like:
DocumentSnapshot doc = await usersRef.doc(u.uid).get();
Map _docdata = doc.data();
      newUserrr = Userr.fromDocument(doc, _docdata);

I have the same issue please someone help me?

Hey @jschnip , Thank you so much for your answer ! I was really having hard time due to recent changes in FlutterFire plugins !
One error was parsing the data using fromDoc method like this ! Thanks again mate.

I'm getting this error when i try to read a field that doesn't exist yet in the document. Previously it simply returned null and i think that was better.

I'm getting this error when i try to read a field that doesn't exist yet in the document. Previously it simply returned null and i think that was better.

Hey man facing same error, what does it return now? As I need it for an if statement.

I'm getting this error when i try to read a field that doesn't exist yet in the document. Previously it simply returned null and i think that was better.

@Alfie-AD Hey man facing same error, what does it return now? As I need it for an if statement.

Doesn't return anything, only throws that exception. I checked that the field existed first to try to work around
'doc.data().contains(the_field)' will return whether the the field exists or not. Pair it with the value you want in the if statement: 'if(doc.data().contains(the_field) && doc.data()[the_field] == the_value){}'

@Alfie-AD  I have tried and it did not work, so I had to reverse it, here is a screenshot of the code section please advice accordingly on how to fix.

@Alfie-AD I have tried and it did not work, so I had to reverse it, here is a screenshot of the code section please advice accordingly on how to fix.

In recent cloud firestore release the data getter was changed to a method data().
Try final profileDocs = profileSnapshot.data(); ...
if you recently updated your package, have a look at the changelog, there are a few more surprises there.

I get this error too. I was learning build a social media app.  I was now working to customize and add more fields to user profile so i added 10 more strings of data i want to collect. Followed the same steps i used to create a blank field for the users to be able to add information:
Debug Error log
════════ Exception caught by widgets library ═══════════════════════════════════
Bad state: field does not exist within the DocumentSnapshotPlatform
The relevant error-causing widget was
StreamBuilder<QuerySnapshot>
lib\pages\timeline.dart:70
════════════════════════════════════════════════════════════════════════════════

The Code Snippet from timeline.dart:70 reads:
buildUsersToFollow() {
  return StreamBuilder(
    stream: usersRef.orderBy('timestamp', descending: true)
    .limit(50)
    .snapshots(),
    builder: (context, snapshot) {
      if (!snapshot.hasData) {
        return circularProgress(context);
      }
      List<UserResult> userResults = [];
      snapshot.data.docs.forEach((doc) {
        User user = User.fromDocument(doc);
        final bool isAuthUser = currentUser.id == user.id;
        final bool isFollowingUser = followingList.contains(user.id);
        // remove auth user from recommended list
        if (isAuthUser) {
          return;
        } else if (isFollowingUser) {
          return;
        } else {
          UserResult userResult = UserResult(user);
          userResults.add(userResult);
        }
        });

        return Container(
          color: Colors.grey.withOpacity(0.2),
          child: Column(
            children: <Widget>[
              Container(
                padding: EdgeInsets.all(12.0),
                child: Row(
                  mainAxisAlignment: MainAxisAlignment.center,
                  children: <Widget>[
                    Icon(
                      Icons.person_add_alt_1_outlined,
                      color: Theme.of(context).primaryColor,
                      size: 20,
                    ),
                    SizedBox(width: 6.0,),
                    Text(
                      "Doctors to follow",
                      style: TextStyle(
                        color: Theme.of(context).primaryColor,
                        fontSize: 20,
                      ),
                    ),
                  ],
                ),
              ),
              Column(
                children: userResults
              ),
            ],
          ),
        );

    },
    );
}

  @override
  Widget build(context) {
    return Scaffold(
      appBar: header(context, isAppTitle: true),
      body: RefreshIndicator(
        onRefresh: () => getTimeline(),
        child: buildTimeline(),
      ),
    );
  }
}

Everything was working ok until i made the customization and look to add more

snapshot.data.docs.forEach((doc)

Instead, try to do snapshot.data.**data().**docs.forEach((doc)
I was also getting the same error and I tried with the updated method by adding .data() and it worked fine.

Same issue, I can't figure it out. This is my code:
StreamBuilder<QuerySnapshot>(
                stream: _commenti,
                builder: (context, snapshot) {
                  if (!snapshot.hasData) {
                    return Container(
                      width: double.infinity,
                      alignment: Alignment.center,
                      margin: EdgeInsets.only(top: 50),
                      child: Text(
                        "Nessun commento su questo corso.",
                        style: TextStyle(fontStyle: FontStyle.italic),
                      ),
                    );
                  } else if (snapshot.data.docs.length == 0) {
                    return Container(
                      width: double.infinity,
                      alignment: Alignment.center,
                      margin: EdgeInsets.only(top: 50),
                      child: Text(
                        "Nessun commento su questo corso.",
                        style: TextStyle(fontStyle: FontStyle.italic),
                      ),
                    );
                  } else
                    return ListView.builder(
                      physics: NeverScrollableScrollPhysics(),
                      shrinkWrap: true,
                      cacheExtent: 30,
                      reverse: true,
                      itemCount: snapshot.data.docs.length + 1,
                      itemBuilder: (context, index) {
                        if (index == snapshot.data.docs.length) {
                          return Column(
                            children: [
                              Text(
                                "I commenti degli studenti",
                                style: Constants.fontBold20,
                              ),
                              SizedBox(height: 20),
                            ],
                          );
                        }
                        return Container(
                          padding: EdgeInsets.all(16),
                          width: double.infinity,
                          margin: EdgeInsets.only(bottom: 15),
                          decoration: BoxDecoration(borderRadius: BorderRadius.circular(20), color: Theme.of(context).cardColor, boxShadow: [
                            BoxShadow(
                              color: Colors.black12,
                              offset: Offset.zero,
                              blurRadius: 10,
                              spreadRadius: 3,
                            ),
                          ]),
                          child: Column(
                            crossAxisAlignment: CrossAxisAlignment.start,
                            children: [
                              Row(
                                mainAxisAlignment: MainAxisAlignment.spaceBetween,
                                crossAxisAlignment: CrossAxisAlignment.start,
                                children: [
                                  Text(
                                    snapshot.hasData<EMAIL_ADDRESS>: "null",
                                    style: Constants.fontBold,
                                  ),
                                  Text(
                                    snapshot.hasData ? snapshot.data.docs[index]["data"] : "21/12/2012",
                                    style: TextStyle(fontSize: 12),
                                  ),
                                ],
                              ),
                              SizedBox(height: 10),
                              LinkWell(
                                snapshot.hasData ? snapshot.data.docs[index]["commento"] : "Lorem ipsum dolor sit amet...",
                                style: TextStyle(color: Theme.of(context).textTheme.bodyText1.color, fontSize: 15, fontFamily: "SF Pro"),
                                linkStyle: TextStyle(
                                    color: darkModeOn ? Colors.white : Colors.blueAccent,
                                    fontWeight: darkModeOn ? FontWeight.bold : FontWeight.normal,
                                    fontSize: 15,
                                    fontFamily: "SF Pro"),
                              ),
                            ],
                          ),
                        );
                      },
                    );
                },
              ),

I have the same issue, I think it's with the latest update or something like that, this issue really needs a solution, I am stuck with it for a really long time now, weird, it only started to happen about 2 or 3 days ago.

still facing same issue

still facing same issue

@Alfie-AD I have tried and it did not work, so I had to reverse it, here is a screenshot of the code section please advice accordingly on how to fix.

In recent cloud firestore release the data getter was changed to a method data().
Try final profileDocs = profileSnapshot.data(); ...
if you recently updated your package, have a look at the changelog, there are a few more surprises there.

Does it work by substituting data for data()??

@Alfie-AD I have tried and it did not work, so I had to reverse it, here is a screenshot of the code section please advice accordingly on how to fix.

In recent cloud firestore release the data getter was changed to a method data().
Try final profileDocs = profileSnapshot.data(); ...
if you recently updated your package, have a look at the changelog, there are a few more surprises there.

Does it work by substituting data for data()??


create-react-app

When running:
npx create-react-app my-app
This error appears:
npm ERR! 404 Object Not Found - GET https://skimdb.npmjs.com/registry/create-react-app/-/create-react-app-4.0.3.tgz - not_found
So seems like a file from the source is missing.
It was the same with installing 'axios' and 'webpack', but 'axios' I installed using source tarball file but with
create-react-app I can't find information on how to install it with using tarball...
Tried this :  npm i ~/Downloads/create-react-app-4.0.3.tar.gz -g
but anyway get error:
npm ERR! code 1
npm ERR! path /home/ultra/.nvm/versions/node/v15.10.0/lib/node_modules/undefined
npm ERR! command failed
npm ERR! command sh -c cd packages/react-error-overlay/ && yarn build:prod
npm ERR! ERROR: [Errno 2] No such file or directory: 'build:prod'
And that's my first bug report 'ever'.
Hope it will help in some way

Do you have space in your username?
Cuz most people with this error does,
see this fix https://github.com/facebook/create-react-app/issues/6512#issuecomment-789308070

Nope I don't have it.


[BREAKING] Code refactoring

DONE

dropped support for Laravel <= 8
dropped support for PHP <= 8.1 (Laravel ^9 || ^10 already supports PHP 8.2 https://endoflife.date/laravel)
updated all composer packages
added shared method getResponse()
fixed $response returned by Cache::remember() https://stackoverflow.com/a/74783008/3929620
used closure in $response->throw()
revised esceptions classes, now extend Illuminate\Http\Client\RequestException
used Http::withToken() instead of Http::withHeaders()
used Http::withQueryParameters() instead of http_build_query()
added Http::withOptions() and Http::baseUrl()
renamed parameter $type to $name, as it is more consistent with the field used by Strapi
renamed $queryData to $queryParams, as it is more consistent with Http::withQueryParameters()
removed almost all parameters (e.g. $sortKey, $sortOrder, $populate, etc.) in favor of $queryParams, which allows greater control over the API parameters used
now $queryParams also allows you to use pagination by offset values (pagination[start] and pagination[limit]), which previously conflicted with pagination by page values (pagination[page] and pagination[limit]) set directly within the method collection()
added optional $cacheTime parameter to override the global value defined in STRAPI_CACHE_TIME  per-call
removed the collectionCount() method, as the /api/$name/count entrypoint does not seem to exist anymore in Strapi v4 (?), and also the pagination[withCount] parameter exists and it's active by default
removed the entriesByField() method as it is superfluous, because it is possible to make the same call with the collection() method (see examples in README)
moved option STRAPI_FULL_URLS globally in .env file
removed $pluck parameter as it is superfluous to the primary functionality of this package: everyone is free to alter the response as they wish
incremented config('strapi.pagination.limit') from 20 to 25 (default Strapi pagination[pageSize])
revised the entire README file

TODO

update references in Strapi documentation https://github.com/strapi/documentation/blob/main/docusaurus/docs/dev-docs/integrations/laravel.md
might it be a good idea to add a F.A.Q. or Known issues section on the README? this could be included in this section, useful for those who have a local development setup (e.g. mkcert):

# .env.local
HTTP_CLIENT_VERIFY_SSL=false

// config/http.php
return [
    'client' => [
        'verify_ssl' => (bool) env('HTTP_CLIENT_VERIFY_SSL', true),
    ],
];

// app/Providers/AppServiceProvider.php
use Illuminate\Support\Facades\Http;

public function boot(): void
{
    Http::globalOptions([
	'verify' => config('http.client.verify_ssl'),
    ]);
}

Hi @dbfx, is there any problem accepting this pull request?

@frugan-dev We have forked this package over at BRFCS/laravel-strapi because it looks like this repo is deprecated and we needed Laravel 11 support. Feel free to contribute if you still use Laravel & Strapi. We're not on packagist yet though.

Hi @Stubbs , If you ask for my contribution, you should have included my changes in this PR in your fork..
Anyway, why waste our efforts if this repo already has a certain following and is also linked in the Strapi v4 docs?
Let's ask to @dbfx if he can add us as contributors to this repo, in case he doesn't have time to actively follow it, or not?


Can't Save Files Outside /home in Linux Mint

Hello. I am a begginer with linux. I am using Linux Mint 21 Cinnamon 5.4.12 . I generally store my susbtitles in external hard drives. When i first install snap, i can't open subtitles with aegisub. With solution below, aegisub became able to open subtitles.
https://askubuntu.com/questions/1228899/how-to-access-files-outside-of-home-in-snap-apps
sudo snap connect aegisub-procles:removable-media
It opens but can't change. It only preview subtitle. When i make a change, the save button won't activated. Is there any way to edit subtitles outside of /home?
Not: There is no issue under /home directories.

It seems to be a problem with Snap which I don't really know how to fix.
Try opening your files using File -> Open, this works fine on my device.
I'm going to look into making a Flatpak package in hopes it would be less glitchy.
And this also should be more convenient for users of Ubuntu-based distros which remove snapd by default (like Mint or Elementary).

I had tried File -> Open but i couldn't find other drives. But i figured out it was my mistake. The drive files can be reached from /home/media/username path. I open from there, and save button works just fine. After that even if i open subtitle with just clicking, it worked normally. So there is no issue now. Thank you for advice. And for your effort to make linux snap of course.
But an alternative installation method without snap would be nice indeed.


Adding a default value for a non-string config attribute fails

What happened?
I would like to add a default value for a non-string config attribute using Annotate():
type Config struct {
	Insecure          bool    `pulumi:"insecure"`
}

func (c *Config) Annotate(a infer.Annotator) {
	a.SetDefault(&c.Insecure, true, "ACI_INSECURE")
}

When using the provider (eg. pulumi up) I get the following error message:
    error: internal error: invalid property type: "boolean"

Removing the a.SetDefault() statement fixes the issue.
The full code is available here: https://github.com/netascode/pulumi-aci/blob/main/provider/pkg/provider/apic/config.go
Expected Behavior
No error message.
Steps to reproduce
Provided in description above.
Output of pulumi about
CLI
Version 3.78.1
Go Version go1.20.7
Go Compiler gc
Host
OS darwin
Version 13.4.1
Arch arm64
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Hey @danischm. Thanks for reporting this issue. We'll take a look and get this fixed.


Update porterstemmer.go

fix crash on some not valid english words such as "eeg", which will cause a index out range exception.

Sorry for the delay. Just getting around to this package again.
"eeg" doesn't seem to cause a panic() anymore (perhaps because of some other change already merged) but the addition of your change still passes the tests.


luci-app-nlbwmon: Add proper file names for json and csv exports.

Currently, the json and csv exports are just named data which is not intuitive. This adds proper file name extensions using Content-disposition HTTP header.

Merged with b3642f476 - thanks!


User agent string grows with each call of pyathena

The root cause of the issue below is caused by pyathena.
After building a bunch of models the header gets to big so that s3 listObjects api call fails. It is caused by an user-agent header that grows with every invocation of Pyathena.
So far I just hotfixed it by pinning the version of pyathena to <2.8.0
Where the config is created in dbt-athena and pyathena
Example request after some models are built:
 2022-12-27 15:18:27,965 botocore.endpoint [DEBUG] Sending http request: <AWSPreparedRequest stream_output=False, method=GET, url=https://*****.s3.eu-central-1.amazonaws.com/?prefix=datalakesensitive%2Foutput%2Fqueryresults%2Ftables%2Fbc32f394-cfc2-4e9e-b3dd-f67e09599921%2F&encoding-type=url, headers={'User-Agent': b'Boto3/1.26.37 Python/3.8.15 Linux/<IP_ADDRESS>-microsoft-standard-WSL2 Botocore/1.29.37 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1  PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 PyAthena/2.18.1 dbt-athena-community/1.3.3', 'X-Amz-Date': b'20221227T141827Z', 'X-Amz-Security-Token': b'****', 'X-Amz-Content-SHA256': b'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855', 'Authorization': b'****', 'amz-sdk-invocation-id': b'****', 'amz-sdk-request': b'attempt=1'}>
#############################
Initial problem:
#############################
It is caused by a boto3 call in the cleanup_table function of the adapter.
In our project with about 300 dbt models it failed when we build the full project. When we build it partially it is OK for some selectors and for others it failed.
The boto3 call:
   s3_bucket.objects.filter(Prefix=prefix).delete()
Here is the actual exception:
botocore.exceptions.ClientError: An error occurred (RequestHeaderSectionTooLarge) when calling the ListObjects operation: Your request header section exceeds the maximum allowed size.
Here the full stack trace:
[08:52:16.828249 [debug] [Thread-9  ]: Began running node model.climatepartner.stg_fpm__base_project_reservation_account
[08:52:16.839619 [info ] [Thread-9  ]: 392 of 573 START sql table model dev_datalakesensitive_fabi.stg_fpm__base_project_reservation_account  [RUN]
[08:52:16.854983 [debug] [Thread-9  ]: Acquiring new athena connection "model.climatepartner.stg_fpm__base_project_reservation_account"
[08:52:16.875331 [debug] [Thread-9  ]: Began compiling node model.climatepartner.stg_fpm__base_project_reservation_account
[08:52:16.884906 [debug] [Thread-9  ]: Compiling model.climatepartner.stg_fpm__base_project_reservation_account
[08:52:16.916737 [debug] [Thread-9  ]: Writing injected SQL for node "model.climatepartner.stg_fpm__base_project_reservation_account"
[08:52:33.177364 [debug] [Thread-9  ]: Athena adapter: Deleting table data from 's3://bucket-name/datalakesensitive/output/tables/dev_datalakesensitive_fabi/stg_fpm__base_project_reservation_account/ee9fab99-03d0-44eb-964a-47e71e0aa5d1/'
[08:52:34.331420 [debug] [Thread-9  ]: finished collecting timing info
[08:52:34.331870 [debug] [Thread-9  ]: On model.climatepartner.stg_fpm__base_project_reservation_account: Close
[08:52:34.332278 [error] [Thread-9  ]: Unhandled error while executing model.climatepartner.stg_fpm__base_project_reservation_account
An error occurred (RequestHeaderSectionTooLarge) when calling the ListObjects operation: Your request header section exceeds the maximum allowed size.
[08:52:34.332610 [debug] [Thread-9  ]:
Traceback (most recent call last):
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/dbt/task/base.py", line 385, in safe_run
    result = self.compile_and_execute(manifest, ctx)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/dbt/task/base.py", line 338, in compile_and_execute
    result = self.run(ctx.node, manifest)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/dbt/task/base.py", line 429, in run
    return self.execute(compiled_node, manifest)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/dbt/task/run.py", line 281, in execute
    result = MacroGenerator(
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/dbt/clients/jinja.py", line 326, in __call__
    return self.call_macro(*args, **kwargs)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/dbt/clients/jinja.py", line 253, in call_macro
    return macro(*args, **kwargs)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/jinja2/runtime.py", line 763, in __call__
    return self._invoke(arguments, autoescape)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/jinja2/runtime.py", line 777, in _invoke
    rv = self._func(*arguments)
  File "<template>", line 49, in macro
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/jinja2/sandbox.py", line 393, in call
    return __context.call(__obj, *args, **kwargs)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/jinja2/runtime.py", line 298, in call
    return __obj(*args, **kwargs)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/dbt/clients/jinja.py", line 326, in __call__
    return self.call_macro(*args, **kwargs)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/dbt/clients/jinja.py", line 253, in call_macro
    return macro(*args, **kwargs)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/jinja2/runtime.py", line 763, in __call__
    return self._invoke(arguments, autoescape)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/jinja2/runtime.py", line 777, in _invoke
    rv = self._func(*arguments)
  File "<template>", line 22, in macro
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/jinja2/sandbox.py", line 393, in call
    return __context.call(__obj, *args, **kwargs)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/jinja2/runtime.py", line 298, in call
    return __obj(*args, **kwargs)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/dbt/adapters/athena/impl.py", line 163, in clean_up_table
    s3_bucket.objects.filter(Prefix=prefix).delete()
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/boto3/resources/collection.py", line 561, in batch_action
    return action(self, *args, **kwargs)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/boto3/resources/action.py", line 134, in __call__
    for page in parent.pages():
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/boto3/resources/collection.py", line 171, in pages
    for page in pages:
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/botocore/paginate.py", line 269, in __iter__
    response = self._make_request(current_kwargs)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/botocore/paginate.py", line 357, in _make_request
    return self._method(**current_kwargs)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/botocore/client.py", line 530, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/home/fabi/workspace/bi-models/.venv/lib/python3.8/site-packages/botocore/client.py", line 960, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (RequestHeaderSectionTooLarge) when calling the ListObjects operation: Your request header section exceeds the maximum allowed size.

[08:52:34.422051 [error] [Thread-9  ]: 392 of 573 ERROR creating sql table model dev_datalakesensitive_fabi.stg_fpm__base_project_reservation_account  [ERROR in 17.50s]

@fbrueck given the fix in https://github.com/laughingman7743/PyAthena/issues/395, would it make sense to bump pyathena to v2.19.0 which should contain it?

@fbrueck the issue should be fix on the main branch, could you confirm that?
@mrshu Thanks for pointing out that pyathena was fixed.


fix shift and div instruction

Codecov Report

Merging #21 into master will increase coverage by 0.89%.
The diff coverage is 60%.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
+ Coverage   48.39%   49.29%   +0.89%
==========================================
  Files          39       39
  Lines        3810     3814       +4
==========================================
+ Hits         1844     1880      +36
+ Misses       1675     1643      -32
  Partials      291      291

Impacted Files
Coverage Δ

exec/num.go
11.4% <60%> (+10.72%)
:arrow_up:

exec/vm.go
75.08% <0%> (+1.38%)
:arrow_up:

Continue to review full report at Codecov.

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

spec ref: https://webassembly.github.io/spec/core/exec/numerics.html#op-idiv-s


Might should not use jQuery's trigger() in testing

I finished on() and off(), failed with test 3, 5, 6
And I found two repos on github which finished on and off , they failed with these testings too. repo1 reop2
Then I found issue #2 also mentioned jQuery's trigger() have some extra work.
We use our on and off, then use jQuery's trigger and Jasmine's spy function to test, there might have some bugs, I guess.
Did you have pass all testing? If yes, could you share the code?
And this is my repo, if you can pointout where are the bugs, very thanks.
And I will finish my trigger() and replace jQuery's, to see if this is the point.

Thanks for the report and you are correct - trigger() from jQuery should not be used in tests. I'll remove it.

Can you please check now?
Thanks! 😸

@andreicek All passed, good job! Thank you!