[KYUUBI #3950][FOLLOWUP] Check whether the state is INITIALIZED instead of builder process launched

Why are the changes needed?

Check the whether the state is INITIALIZED instead of builder process launched
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

thanks for the suggestion, updated

thanks, merging to master


Register controller cleanup

Rebound PR with code cleanup, this time in several commits.

Submitted a PR with fewer commits here #3468


Connection failed when enabling TLS

First of all thank you for making this provider.
The TLS part is actually mandatory for me.
Terraform Version
Terraform v0.12.13
Affected Resource(s)
Please list the affected resources and data sources.

activedirectory_provider

Terraform Configuration Files
Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code
# Configure the AD Provider
provider "activedirectory" {
  host     = "mydc.domain.local"
  domain   = "domain.local"
  use_tls  = true
  user     = var.user
  password = var.password
}

Expected Behavior
The plan should be executed
Actual Behavior
Plan not executed as terraform cannot access the active directory
Steps to Reproduce
Please list the steps required to reproduce the issue.

terraform plan

Error: providerConfigure - connection to active directory failed: connect - failed to use secure connection: LDAP Result Code 200 "Network Error": TLS handshake failed (tls: either ServerName or InsecureSkipVerify must be specified in the tls.Config)

Hi @jpatigny, thanks for your feedback. Let me have a look into this.

fixed


REFACTOR: global refactoring to be in line with modern JS projects

Done for now, more refactoring is needed after other issues are settled


[CH] Fix tpcds q67

What changes were proposed in this pull request?
Fix tpcds q67 failed on aqe enabled
How was this patch tested?
unit tests
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

Optimizations for partition 1 do not work

there is a pr about this in #2153

there is a pr about this part in #2153

the pr cann't work on ds q67, maybe we can remove this optimization directly.


Fix main screen layout twitch during launch

The GIF speaks for itself.
I'm not sure why this was perplexing to track down in the past, but I stumbled into the solution while working on something else. The refactor will obviate all of this anyway, but I figured I should PR it just in case.

For posterity, here's a GIF of the old erratic behavior for comparison

Test approved! 👍


Update Chatbot.jsx

Update ChatbotEmbed component with better practices, improved error handling, and proper React patterns
Issue Title
Update chatboat

[ yes] I have provided the issue title.

Info about the Related Issue
ChatbotEmbed component with better practices, improved error handling, and proper React patterns

[ yes] I have described the aim of the project.

Name
*Enter your name here- Asif Qamar

[ ] I have provided my name.

GitHub ID
Please mention your GitHub ID.
*Enter your GitHub ID here- AsifQamar

[ ] I have provided my GitHub ID.

Identify Yourself
Mention in which program you are contributing (e.g., WoB, GSSOC, SSOC, Hactoberfest).
*Enter your participant role here-*Gssoc , Hacktoberfest

[ ] I have mentioned my participant role.

Closes
Enter the issue number that will be closed through this PR.
*Closes: #522

[ ] I have provided the issue number.

Describe the Add-ons or Changes You've Made
ChatbotEmbed component with better practices, improved error handling, and proper React patterns

[ ] I have described my changes.

Type of Change
Select the type of change:

[ ] Bug fix (non-breaking change which fixes an issue)
[yes ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
runiing the chatbot

[ ] I have described my testing process.

Checklist
Please confirm the following:

[ ] My code follows the guidelines of this project.
[ yes] I have performed a self-review of my own code.
[ ] I have commented my code, particularly wherever it was hard to understand.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[ ] I have added things that prove my fix is effective or that my feature works.

@rishicds please review and merge it


Please restore sidebar customization

A ways back, before the new UI was introduced (maybe a year ago?), we were free to add/remove windows in the sidebar.  The most notable example was having the xref window and the minigraph window open and viewable at the same time, in separate little boxes.
However, the new UI introduced what I think the documentation refers to as "carousels".  There are now 2 boxes: one can only show xrefs OR the minigraph, one can show all the other windows but only one at a time (types, symbols, etc.).  The current UI makes it impossible to show both the xrefs and the minigraph at the same time in the sidebar, which really hampers my ability to reverse engineer.
I was able to use the tool much more effectively with the old UI.  I actually bought a large monitor specifically for being able to display a bunch of different things at the same time in Binary Ninja (back with the old UI); I used to have 3 boxes in the sidebar: one that always showed the minigraph, and the other 2 had groups of tabs I could toggle between, depending on what I needed in the moment.  Life was glorious.
In the meantime, I've been using hotkeys quite a bit to toggle between xref/minigraph windows, but it's not a great substitute for being able to see both at the same time.  I also only recently found out that it's possible to move the minigraph to the main window, but the shape of this window is awkward for the shapes of most functions, and also eats up a lot of valuable screen real estate in the main window.
The perfect solution (for me) would be going back to the old system, or at least providing the option to, which I guess looked a little uglier but I didn't really mind.  Another idea is letting users decide the options that each carousel can show; bonus points if a user can set the number carousels too.

Current design of the sidebar is very restrictive. For example, let's say I want to see symbols, debugger and tags at the same time, what do I do? We should be able to freely pin any of sidebar item induvidually like in IDA.

Documentation has been added and the feature has been live for a few weeks!


UI node bundle comment fix

Objective
Doc comment for the global_transform field in NodeBundle says:
/// This field is automatically managed by the UI layout system.

The GlobalTransform component is the thing being managed, not the global_transform field, and the TransformPropagate systems do the managing, not the UI layout system.

Checked the rendered docs. Looks good / makes sense to me.
While reviewing I noticed that the docs for the transform fields for these various bundles all make references to NodeBundle.

Oh yep I see, better fix that too.

/// To alter the position of the `NodeBundle`, use the properties of the [`Style`] component.
Changed this line for the Transform comments so it names the specific bundle each time.
For GlobalTransform I deleted it, as it seems odd to have the information there when you don't use GlobalTransform to change positions.

@ickshonpe once merge conflicts are cleaned up, I'll merge this.


Multiple files upload

What's in this PR?
Implementation of multiple files upload as mentioned in #147 . I created new method call sources so we can pass multiple files into sourceCallback.
Example
sources { request, url ->
   arrayOf(
      File(currentDir, "lorem_ipsum_short.tmp"),
      File(currentDir, "lorem_ipsum_long.tmp")
   )
}

I have left some comments. Thanks so much for helping us implementing this feature 👏

This is awesome! Welcome @babedev for your first PR 💯 . 🚢 🇮🇹  from me.


[blog] Fix images for the docs separation post

[x] I have followed (at least) the PR section of the contributing guide.

Follow up to https://github.com/mui/material-ui/pull/32044
https://deploy-preview-32257--material-ui.netlify.app/blog/docs-restructure-2022/

Could we take advantage of this PR to clarify what the difference is in the search result images?
Instead of: "Here is a comparison of before and after when searching for the "pagination" feature:"
"Previously a search for pagination returned results for the Material UI pagination component, followed by those for the data grid:
[first image]
Now when viewing the MUI X section, only results related to the data grid pagination feature are returned:
[second image]"

I'm on my Twitter feed, looking at our latest tweet: https://twitter.com/MUI_hq/status/1513971476038311939. What do you think about these two potential opportunities:

we remove the default social image for all blog posts. I feel like the core content of the tweet would work better without the image than with the current one:

We use the first image as a social card, it would work better than 1. and current:

We use the first image as a social card

I think that would work perfectly. If I'm not mistaken, the markdown files already support that, don't they?

If I'm not mistaken, the markdown files already support that, don't they?

@danilo-leal Correct, it needs a card.png image and
https://github.com/mui/material-ui/blob/6d9f42a637184a3b3cb552d2591e2cf39653025d/docs/pages/blog/2021.md#L6

you'll have a better chance of catching eyes while scrolling the feed

@samuelsycamore To explain my reasoning, I need to add two variables: Y: the percentage of people noticing the tweet, Z: the percentage of people clicking on the tweet. My concern is that people might read the content on the image; and not the content of the tweet, in the end, not click on it to read the content. So in the current model, the overall conversion could be like Y = 85, Z = 15, a conversion of 13% while in my proposal Y = 80, Z = 18, a conversion of 14%. Is this model true? I don't know, but food for thoughts.

it needs a card.png

Does the social card/image need to be within the markdown file, at the start of it, like in this 2021 post?

@danilo-leal I'm doing the change with a new commit to illustrate the process once.

@oliviertassinari cool, thanks! Are we good for merging? Feel like this one is 👍


Add: Identify First-Time PR Contributors for Last Week

Fixes #153
Description
This PR implements logic to identify first-time PR contributors whose first pr_merged activity occurred within the specified time frame (last week). It ensures accuracy by filtering contributors based on their activities and checks if their first contribution happened during last week.
Screenshots / Outputs

Also not a fan of the design. Let's not have @, seems out of context. Also placing above the name doesn't seem nice.

instead of directly keeping the logic here, let's add it to the contributor object itself. so that this value isNewContributor could be reused everywhere else when needed.

Shall I add this logic in getContributorBySlug function?

yup! that's the right place to be

@rithviknishad can you please review this PR?


Trying to Install gitscrum properly..

Hi @renatomarinho , thx for your great effort to build this awesome stuff..
I already follow your installation steps. and i got several issue :

Can't retrieve repositories list with Gitlab ( wizard/step1 ), i quick check on tables organization and its only store github.
I got error Exception Division By Zero in user-stories/list.
Cant't store sprint ( sprints/store )

I am using Centos 7, Nginx, Mysql 5.7...
I was trying every branch & possible steps in installation steps, changed the environments dependencies but no luck.
i deploy the gitscrum in g.dodol.in
Please tell me how to make this great tools work properly.. thx in advance !

Hi @Datazource,
I appreciate your comment, thanks so much.
Can you update the GitScrum? If continue issue, please send-me the log.

Still error
git clone git@github.com:GitScrum-Community/laravel-gitscrum.git
Cloning into 'laravel-gitscrum'...
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
ct-root@ct-dev:~$


ARROW-9017: [C++][Python] Refactor scalar bindings

TODOs:

[x] split PRs into two, one with simplified python to arrow conversions with benchmarks
[x] implement union scalar on the C++ side
[x] store the index value for dictionary scalar
[x] more tests

Closes ARROW-9017, ARROW-9153

Really nice!
Could we add a is_valid attribute to the python scalar as well? Now the only way to check for a null value is to do .as_py() is None ?

Definitely!

Might not be related to the changes in this PR, but reviewing this triggered me to test scalar casting:
In [2]: s = pa.scalar(pd.Timestamp("2012-01-01"))
   ...:
   ...: import pyarrow.compute as pc
   ...: pc.cast(s, pa.timestamp('ns'))
../src/arrow/compute/kernels/scalar_cast_temporal.cc:130:  Check failed: (batch[0].kind()) == (Datum::ARRAY)
...
Aborted (core dumped)

I think the cast kernel doesn't support scalars yet, on the other hand the scalars have custom CastTo implementation which we may want to remove in favor of compute.Cast?
cc @bkietz

Could we add a is_valid attribute to the python scalar as well? Now the only way to check for a null value is to do .as_py() is None ?

Added.

I'm considering to apply cython.freelist on the scalar extension classes.
@wesm @pitrou @jorisvandenbossche do you have any positive experience with it?
I assume we should measure its impact before using it, so I can defer it to a follow-up.

Ok, at a quick glance, it seems that null container tests work properly regardless:
>>> s = set()
>>> s.add(pa.scalar(None))
>>> s
{<pyarrow.NullScalar: None>}
>>> pa.scalar(None) in s
True
>>> s.add(pa.scalar(None, pa.int64()))
>>> s.add(pa.scalar(12, pa.int64()))
>>> s
{<pyarrow.Int64Scalar: 12>,
 <pyarrow.NullScalar: None>,
 <pyarrow.Int64Scalar: None>}
>>> pa.scalar(None, pa.int64()) in s
True
>>> pa.scalar(None, pa.int32()) in s
False

>>> l = [pa.scalar(None)]
>>> pa.scalar(None) in l
True
>>> pa.scalar(None, pa.int64()) in l
False

the null equality tests look like a nuisance for regular Python usage (__eq__ should return a boolean)

The reason that those scalars return null on equality check and not True/False, it to ensure consistent behaviour between arrays and scalars (to ensure (arr1 == arr2)[0] and arr1[0] == arr2[0]gives the same answer).
Our element-wise equality propagates null, and so IMO also the scalar should do.

The problem is that it breaks Python semantics in potentially annoying places:
>>> import pyarrow as pa
>>> na = pa.scalar(None)
>>> na in [5]
True

We could "fix" that one by raising in __bool__ (meaning: it will at least give an error instead of silently returning a wrong answer)

Yes, we could. That may have other annoying implications, though (such as __contains__ not working anymore). I've started a ML discussion.

Addressed the review comments and changed the equality checks to be strict, only allowing to compare scalars with scalars of the same type. One exception could be to compare invalid scalar values to pa.NA, but even if we consider to choose that behavior, it should be implemented on the C++ side.
@pitrou @jorisvandenbossche it should be ready for another review.

@pitrou added the C++ tests.

Looks like the PR needs rebasing and fixing for the latest union changes.

+1. Thanks @kszucs for this work!


PDF.JS exposing password in inspector debug.

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version:
Operating system and its version:
PDF.js version:
Is a browser extension:

Steps to reproduce the problem:
1.
2.
What is the expected behavior? (add screenshot)
What went wrong? (add screenshot)
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Sorry, but nothing more than a title really isn't sufficient to make an issue actionable/valid.
Furthermore, we're explicitly clearing out the password-input when closing the dialog so it's not really clear what the problem is here!? Note that the password-input obviously needs to, at least temporarily, contain the password since otherwise it can't work.


gofmt

Just ran
gofmt -w .

on the project root. That's all.
https://blog.golang.org/go-fmt-your-code

I made this PR with a project going on over at https://github.com/rotblauer/gofmt-att, and it's definitely a work in progress. So if I got something wrong, or this is annoying at all, please file an issue over there and we'll sort it out.

Thank you for sending the patch, but there are two reasons I think we won't merge it. I'll cross-link in the gofmt-att repo, as requested.
First, the code in the _tools directory is copied in automatically by retool. That means that this repo isn't the right place to make changes to that code—any changes should happen in the upstream source. Retool places the code in a directory that doesn't match ... (it starts with an underscore), so it's surprising that code there is inspected by scripts like gofmt-att.
Not wanting to maintain patches to tools like that is the main reason I think we won't merge this change.
Second, the code in question almost certainly is already go-formatted .. according to the rules in a different version of Go. Some of the rules changed in Go 1.10, and trusting a particular version of Go to see if code is formatted will lead to unnecessary churn.

Roger that @rhysh -- thanks for the feedback. Since running my last batch of PRs I've learned about this _ pre-/suffixing convention and have added it to my blacklist to avoid outcomes like this.

Also that's a really important link on the gofmt changes -- thanks for that.

@rhysh covered the reasons for closing this well.


Automated cherry pick of #8284: feature: qcloud create VM with tags

Cherry pick of #8284 on release/3.4.
#8284: feature: qcloud create VM with tags

/lgtm
/approve


ci test

This will like take more than 4 hours, but pretty sure we'll fail on memory requirements as well.

no longer needed


[#345] Fix broken provisioning on vagrant 2.2.13

For me, too!

The issue was fixed in Vagrant version 2.2.14.


managed node group: specific tags for ASG

Is your request related to a new offering from AWS?
No
Is your request related to a problem? Please describe.
No
Describe the solution you'd like.
In eks-managed-node-group module is an option to set a specific tags for IAM role or Security group. I would like to have a new option to be able to set specific tags for ASG.
Describe alternatives you've considered.
Add the tags to tags which is applied to all resources.
Additional context
This would help to set on ASG cluster-autoscaler ASG only relevant tags like k8s.io/cluster-autoscaler/node-template/taint/taint_name as such tags on other resources are irrelevant.

just found https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1558


[FEATURE REQUEST] Epiphany on AKS module MVP

Is your feature request related to a problem? Please describe.
There is need to prepare simplest possible Epiphany module to be able to install epiphany on top of AzBI and AzAKS modules.
 It means that by default epi module requires at least 1 machine to be available in state. By setting postgres=1 in epi init phase I in fact tell it that it needs to use 2 machines. Also init phase should be able to discover that there is AzAKS module applied and it should configure that it will use that created AKS cluster. If there is no AzAKS module already present it should fail.
All that means that after those 9 steps I should have Epiphany cluster with 1 repository machine, 1 postgresql machine and 3 nodes AKS cluster.
I think we can name that module m-classic-epiphany-on-aks
Describe alternatives you've considered
No.
Additional context
No.

This task implies that there will be 3 modules eventually:

m-classic-epiphany-on-aks (this task)
m-classic-epiphany-on-eks
m-classic-epiphany-on-prem

POC: https://github.com/sk4zuzu/m-classic-epiphany-on-aks/pull/1 :+1::innocent:

I left first review. This PR is huge but very valuable! Good job @sk4zuzu :+1:

Repository have been renamed and moved here https://github.com/epiphany-platform/m-generic-epiphany-on-aks.

Added support for running on Windows (under Git Bash)
Tests OK (checked k8s dashboard, Keycloak, Kibana, pod statuses)
During testing found and reported issue #1866 [Filebeat] [AKS/EKS] No logs from K8s apps in Elasticsearch


Vutuv Context

Because Phauxth is using Phoenix Context for authentication/authorization, not the pure Phoenix Schema. We have a chance to use context or a pure schema. There are pros and cons. The pros we can map the data structure to be more clearly, since a context will contain one or several schemas that are very close.
I don’t know the following items are appropriate or not for Vutuv Context design.

Accounts

User (username/primary-email, password_hash, confirmed)
EmailAddress (value, description, is_public)
Role (admin, user, etc)

Biographies

Profile (first_name, last_name, middlename, nickname, honorific_prefix, honorific_suffic, gender, birthday_day, birthday_monht, birthday_year, locale, avatar, active_slug, headline, noindex?, validated?)
PhoneNumber
Membership
URL
UserSkill
WorkExperience

Sessions

Session (expired_at)

Social

Post
Point
Badge
Vote
Share
Endorsement
Group
SocialMediaAccount

Services

Company
RecruiterSubscription
JobPosting
Coupon

Scheduler

Birthday
Work anniversary?

According to this article https://cloud.google.com/blog/products/gcp/12-best-practices-for-user-account, we can separate concept of user identity and account. All user information for authentication can be separated from user profile.

@riverrun What do you think of this?

I just realized that @riverrun is the one who created the Phauxth 🥇 :D
Such amazing work!

I will add a few comments about the benefits of using Phoenix context modules, some alternatives and how I think we should work with them.
The contexts serve as an api to the data layer, and the collection of context modules and database (schema / table) modules work almost as a separate app. Making the data handling separate in this way can help make reasoning about the code, testing and refactoring easier.
There are two alternative ways of keeping the data handling separate - using umbrella apps and actually separating the apps. In both these cases, you would work with two, or more, separate apps (with umbrella apps, these apps are integrated to a certain extent) - VutuvDB and VutuvWeb, for example.
Having separate apps can keep all the different parts isolated, but it is not necessary. Whatever we decide to do, I think we need to agree to certain guidelines about how we call other parts of the app. For example, we should not need to call anything in the VutuvWeb namespace from the data layer, we should only call the data layer through the context modules, and we should not call Ecto directly from the view or controller layers.
In sum, if we agree that keeping the data layer separate from the other parts is useful, then those are the choices, and I would use the context module way. How we organize it is a separate question, but @hendri-tobing 's seems like a good start.

I only have one though here: With 2.0 we start on a green field. This is THE chance to do it right. Of course we have to find the sweet spot between best-possible and doable. But as fare as I understand it the best possible way wouldn't mean more work in this case.

As of #588, we have the following structure:

Accounts

User (email, password_hash, confirmed)

Sessions

Session (expired_at)

I also added custom phoenix generator templates for the context and schema. Running mix phx.gen.context will now produce modules with specifications (@spec) and types for the schemas. In addition, the bang (get_*!) functions have been replaced with regular get_* functions. After running the context generator, you will need to edit the schema type - replacing any with the correct type.

I also added custom phoenix generator templates for the context and schema. Running mix phx.gen.context will now produce modules with specifications (@spec) and types for the schemas. In addition, the bang (get_*!) functions have been replaced with regular get_* functions. After running the context generator, you will need to edit the schema type - replacing any with the correct type.

Could you create a mini example of how to use it in the wiki or in the development document? For a new developer to read.

Thank you for the tooling and the installation of Phauxth. FYI, I am in progress to separate the email_address schema, so users are allowed to input many email addresses as well as can use their verified-email to login.

I can add an example of using the context generators later today.

FYI, almost done the email schema, update login, verify email, and bamboo smtp configuration for development (and README.md). I am still testing since Pre-Commit doesn't allow me to commit, if the tests fail 😆

How to pass "don't commit to branch", even all tests are passed, @riverrun ? Is there something missed in my configuration file?

Thank you.

Run git checkout -b develop and then try to commit.
The Don't commit to branch check is so that you don't commit changes to master.

From the contexts mentioned in the original post, we have completed the User, Biographies and Sessions contexts. That leaves the following contexts to be done.

* Social

  * Post
  * Point
  * Badge
  * Vote
  * Share
  * Endorsement
  * Group
  * SocialMediaAccount

* Services

  * Company
  * RecruiterSubscription
  * JobPosting
  * Coupon

* Scheduler

  * Birthday
  * Work anniversary?

Which ones of these do we want to prioritize? Are there any that we do not need?

Closing in favor of #675


Feedback:

"You walk ... before" / "You walk ... before"
Capitalization
Eh. Tepid ending.

(this was for far.md)


Few questions

Some of these things are not clear from the documentation or test cases.
Can you please clarify?

Do we support all these converters for source topic(s)? I know that control topic only uses Avro.

org.apache.kafka.connect.storage.StringConverter
org.apache.kafka.connect.json.JsonConverter
org.apache.kafka.connect.converters.ByteArrayConverter
io.confluent.connect.avro.AvroConverter
io.confluent.connect.protobuf.ProtobufConverter
io.confluent.connect.json.JsonSchemaConverter

Schema registry is supported?

autoCreateTable is not creating namespaces by default? Shall I raise a PR to fix it?

Buffering and polling is currently only time based (iceberg.control.commit.interval-ms)?
Do we have a plan for message count based threshold?

How to automatically add the ingestion time column? Should use SMT?

Do we support all these SMT?
https://docs.confluent.io/platform/current/connect/transforms/overview.html

Schema evolution with auto table creation may not work? Since we need to alter table's schema?

Framework capabilities like error tolerance, dead letter queue , deployment modes are supported with this connector too right?

How does commit retry works? I saw the commit-interval and commit-timeout config.
Do we have configurable retries?

Can JMX be used to monitor the conenctor?
https://docs.confluent.io/platform/current/connect/monitoring.html#use-jmx-to-monitor-kconnect

There are no specific limitations on which converters can be used by the sink, any of those should work
Yes
Feel free to open a PR if it is small, we're trying to limit disruptive changes during the Iceberg submission process
There are no plans currently
Yes an SMT makes sense here
There are no specific limitations on what SMTs can be used so any of those should work
If I'm understand the question right, schema evolution should work with auto table creation
There are no limitations around these so all should work the same way as with other sinks
Commit retries can be set via table properties, i.e. commit.retry.num-retries
JMX should work as with any other connector, this sink doesn't expose any custom metrics yet

Thanks.


Add core.BlockNumber type

let's change the Number field in header to be of type core.BlockNumber as well?
or, we can make ToBytes function just a standalone helper function without creating the BlockNumber type

or, we can make ToBytes function just a standalone helper function without creating the BlockNumber type

sounds easier to me

Any particular reason why we can't use cbor as we do for other structs?

cbor encodes uints to variable length byte streams. So if it doesnt need the full 8 bytes to represent a uint64, the resulting byte array will be smaller. That will mess up our sorted buckets.

I see, thanks!
@kirugan Instead of having ToBytes(), do you think it makes sense to have MarshalBinary() and UnmarshalBinary()

There are places in blockchain.go where we read block number from db, I think that should be replaced with UnmarshalBinary() so that we don't have to import encoding/binary

Instead of having ToBytes(), do you think it makes sense to have MarshalBinary() and UnmarshalBinary()

@IronGauntlets as far as I know, we don't use binary encoding interfaces (encoding.BinaryMarshaler, encoding.BinaryUnmarshaler) much. Compliance with the interface will bring little benefit IMO, but the ability to use a function call in one line affects readability:
db.Key(blockNumber.ToBytes())
Perhaps ToBytes() is not the best name for this method and it's better to call it Bytes() or something similar. What do you think?

This overall LGTM. I know I asked for core.BlockNumber to be used everywhere but I am now wondering if this is too big of a changeset just to remove 3 lines being duplicated in a handful of places.
We could achieve the same thing by making the MarshalBinary a standalone helper (something like MarshalBlockNumber(blockNumber uint64) ([]byte, error) ) and use that wherever needed.
WDYT @kirugan ?

late comment about this PR: @omerfirmak yep, agree that it turned out a lot of changes just to encapsulate mashaling logic into specific type


Hard IP Integration with OpenFPGA

Is it possible to add any hard-IP to be automatically elaborated by Yosys such as FIFO, UART in FPGA as sub-tiles. I want to have embedded FIFO and UART blocks that  can be used in the designs with higher performances. If possible, how can I generate technology map files for Yosys?

@msaideroglu Technology map files for yosys are hand crafted. You can read Yosys manual.


💡 [FEATURE] - Adding feedback form

Idea Contribution

[X] I have read all the feature request issues.
[X] I'm interested in working on this issue
[X] I'm part of GSSOC organization

Explain feature request
I observed that there is no feedback form in webpage.
I want to add it.
Explain your solution
No response
Any alternative approaches/features
No response
Additional Context
Please assign me this task.

Hello @jfmartinz,
Can this issue be assigned to me for Gssoc'24.
Regards,
V Meenakshi Iyer

We have a feedback form, ill  close this issue for now


No support for POST api/submit

Thanks for the gem! I've been enjoying using it.
Looks like there isn't support for POST /api/submit. I think I see where to add it, but I wanted to check that I wasn't missing something before digging in.

It already exists! submit is a method for the subreddit object.

Source
Documentation (for v0.7.8)

Gotcha. Thanks!
Definitely poked around to find it, but I think I expected to see it somewhere else. Makes sense that it's in the subreddit object.


[FEATURE] Export Finished TODOS?

Hi @liyunze-coding ,
What a FANTASTIC tool! I am using it for my stream regularly now and me and my chat love it. A quick question I had is would it be possible to create some sort of export function to export current todos to like a csv or text file? I use todo.txt to track my tasks and would love to be able to bring this into my task tracking workflow more easily (if possible).
Otherwise, no worries! Thanks for making this great tool!
~ tcp :deciduous_tree:

I considered doing that but it doesn't seem possible, to my understanding. It would require a backend such as Lua, Python or Node JS to be achievable. Thanks for the suggestion!


Page not indexed?

I cannot find this page when searching, e.g. for "upgrade compatibility matrix".
https://docs.microsoft.com/en-us/search/?search="Upgrade+Compatibility+Matrix"&category=All&scope=BusinessCentral

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

ID: 4c8868c4-fb29-4b1f-e8ba-7560642481fc
Version Independent ID: e838d8a4-07b9-02a8-f0b5-756220b3e64d
Content: Business Central 14.X to 15.X compatibility matrix - Business Central
Content Source: dev-itpro/upgrade/upgrade-v14-v15-compatibility.md
Service: dynamics365-business-central
GitHub Login: @jswymer
Microsoft Alias: jswymer

Hello, that's a little bit weird, I agree - I cannot search and make the page appear either. The metadata of this page is not different from other pages, so I am afraid that there is not so much we can do about it - other than making sure it is visible from other topics by linking to it. Then, I would expect the page to be picked up for indexing at some point. Thanks.

The page is finally indexed :-)

Yay, that took a long time, though - thanks for getting back :)


[Bug] Runtime Stuck

Checklist

[x] 1. I have searched related issues but cannot get the expected help.
[x] 2. The bug has not been fixed in the latest version.
[x] 3. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.
[x] 4. If the issue you raised is not a bug but a question, please raise a discussion at https://github.com/sgl-project/sglang/discussions/new/choose Otherwise, it will be closed.
[x] 5. Please use English, otherwise it will be closed.

Describe the bug
import sglang as sgl

@sgl.function
def multi_turn_question(s, question_1, question_2):
    s += sgl.user(question_1)
    s += sgl.assistant(sgl.gen("answer_1", max_tokens=256))
    s += sgl.user(question_2)
    s += sgl.assistant(sgl.gen("answer_2", max_tokens=256))

def single():
    state = multi_turn_question.run(
        question_1="What is the capital of the United States?",
        question_2="List two local attractions.",
    )

    for m in state.messages():
        print(m["role"], ":", m["content"])

    print("\n-- answer_1 --\n", state["answer_1"])

def stream():
    state = multi_turn_question.run(
        question_1="What is the capital of the United States?",
        question_2="List two local attractions.",
        stream=True,
    )

    for out in state.text_iter():
        print(out, end="", flush=True)
    print()

def batch():
    states = multi_turn_question.run_batch(
        [
            {
                "question_1": "What is the capital of the United States?",
                "question_2": "List two local attractions.",
            },
            {
                "question_1": "What is the capital of France?",
                "question_2": "What is the population of this city?",
            },
        ]
    )

    for s in states:
        print(s.messages())

if __name__ == "__main__":
    runtime = sgl.Runtime(model_path="xxxxxx/PLM/meta-llama/Meta-Llama-3.1-8B-Instruct",tp_size=1,dp_size=4,enable_torch_compile=False)
    print("\n========== End ==========\n")

I can use SGL by deploying in command line.
But when i try to use in python wrapper:  it stuck in creating Runtime. (Successfully load model and see the GPU memory increase, but not observe print)
Stuck in create runtime
Reproduction
pip install sgl as README and run the code above
Environment
Python: 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]
CUDA available: True
GPU 0,1,2,3: NVIDIA A800-SXM4-80GB
GPU 0,1,2,3 Compute Capability: 8.0
CUDA_HOME: /usr/local/cuda-12.1
NVCC: Cuda compilation tools, release 12.1, V12.1.66
CUDA Driver Version: 535.161.08
PyTorch: 2.4.0+cu121
sglang: 0.2.13
flashinfer: 0.1.5+cu121torch2.4
triton: 3.0.0
transformers: 4.44.1
requests: 2.32.3
tqdm: 4.66.5
numpy: 1.26.4
aiohttp: 3.10.2
fastapi: 0.112.0
hf_transfer: 0.1.8
huggingface_hub: 0.24.5
interegular: 0.3.3
packaging: 24.1
PIL: 10.4.0
psutil: 6.0.0
pydantic: 2.8.2
uvicorn: 0.30.5
uvloop: 0.19.0
zmq: 26.1.0
vllm: 0.5.4
multipart: 0.0.9
openai: 1.41.1
anthropic: 0.34.0
NVIDIA Topology:
GPU0    GPU1    GPU2    GPU3    NIC0    NIC1    NIC2    NIC3    CPU Affinity    NUMA Affinity   GPU NUMA ID
GPU0     X      NV8     NV8     NV8     PXB     NODE    SYS     SYS     0-31,64-95      0               N/A
GPU1    NV8      X      NV8     NV8     PXB     NODE    SYS     SYS     0-31,64-95      0               N/A
GPU2    NV8     NV8      X      NV8     NODE    PXB     SYS     SYS     0-31,64-95      0               N/A
GPU3    NV8     NV8     NV8      X      NODE    PXB     SYS     SYS     0-31,64-95      0               N/A
NIC0    PXB     PXB     NODE    NODE     X      NODE    SYS     SYS
NIC1    NODE    NODE    PXB     PXB     NODE     X      SYS     SYS
NIC2    SYS     SYS     SYS     SYS     SYS     SYS      X      NODE
NIC3    SYS     SYS     SYS     SYS     SYS     SYS     NODE     X
Legend:
X    = Self
SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
PIX  = Connection traversing at most a single PCIe bridge
NV#  = Connection traversing a bonded set of # NVLinks
NIC Legend:
NIC0: mlx5_0
NIC1: mlx5_1
NIC2: mlx5_2
NIC3: mlx5_3
ulimit soft: 1024768


DBZ-1707 Ensuring correct Kafka record timestamp for outbox events;

Depending on the width of the configured TIMESTAMP column, a microsecond or nanosecond timestamp could have been returned before, whereas this should always be milliseconds.
https://issues.redhat.com/browse/DBZ-1707

Hey @renatomefi, just in case you wanted to take a look at that one. A user reported a small issue with the outbox routing SMT.

Hey Gunnar, that's intersting, maybe we should add a note in the bug fix for people to check their current records timestamps?

Yes, we'll add something to the release notes on that one.

Added a proposal for the migration notes entry to the JIRA issue.


fix(frontend): fix requests to services

:tada: This PR is included in version 3.1.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Added two variants of Coin change problem

Star the repo this is mandatory and you can also follow me.


Fix various issues before release

Fix crash when opening stats
Fix incorrect header
Fix executable not working
Remove outdated format converter

Also fixed stats not showing, and use glob rather than hardcoding the chapters name to find the files.


[Linear] Custom Search Issues logic

Extension
https://www.raycast.com/linear/linear
Description
Assuming #5371 gets resolved, I would love to be able to customize some of the filters for searching for issues. Specifically, I would like to bind a keyboard shortcut to a Search Issues action that was fine-tuned to only search for issues in a certain project, with certain status values. This would let me rapidly search the backlog of my main project and not get other stuff (other projects, completed/in-flight work, etc) polluted in the results.
Thanks!
Who will benefit from this feature?
No response
Anything else?
No response

The main search I do all the time is for stuff in a specific project that has status in either Triage, Backlog, or Todo. Basically, I'm looking for stuff we aren't working on so that I can link it up with inbound support requests / feature requests.


mime: should be able to determine an appropriate extension for a given MIME type

Currently it is possible to go from a file extension to a MIME type using TypeForExtension, but the converse is missing. This is useful in applications where it is saving or producing new content of variable type, and needs to know the expected extension.
Proposed API:
func ExtensionsForType(typ string) ([]string, error)
This is the symmetric partner of TypeForExtension, it determines the file extensions for the given type (formatted per RFC 1521, so accepted by ParseMediaType). It does not consider any optional parameters.
The error return value is used solely where the provided MIME type does not parse, distinct from 'no extensions registered', which is an empty slice.

Testing ExtensionByType() with mime text/html under OS X 10.10.4. running go1.5beta1 darwin/amd64 produces inconsistent results. I noticed that in about 1/10 cases it returns .html instead of .htm.


SEC-1646 Merged from upstream, and removed our own (now-dupe) gitleaks.

deploy-DEV-slim.yml and deploy-DEV-standard.yml are broken for reasons I cannot explain. Well, I think I have an explanation in my head, it's that I can't explain why they work in upstream (or why they used to work), because I think those should have been broken too.
Oh well, I can't be bothered to untangle all the global state vars everywhere and/or all the places we differ from upstream super-linter and how they affect things.
Point is, the image builds successfully now, and runs successfully and comments on findings, so good enough for me for now.


Emoji style guide

This PR adds an emoji style guide to CONTRIBUTING.md and adapts the guide to the existing code.

Wait with merging until tomorrow (after the meetup)

I like it!
Could we create a list of string constants for the emojis somewhere, and use the constants in the prints?

@viccuad I like the idea, I will add a card to incoming.


A crossbrowser ellipsis helper

The CSS3 ellipsis is very practical when you want to truncate a line of text and show "..." to mean that the text is longer.
The following class ables to gracefully truncate the text at the parent width
.ellipsis { overflow: hidden; white-space: nowrap; text-overflow: ellipsis; }

Added in 2.0.1-wip as a mixin.


Dependencies and react version

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.

Dependencies are not installed directly with the library? Also the react version is old.

They are peer dependencies. Some versions of NPM install them automatically.
They are peer dependencies to reduce package size and allow you to have a version of the dependencies that you would like.
This is to prevent multiple versions of the same dep been installed.
I hope this helps :)


Use context in SQL #73

resolve: #73
adding context in SQL

Thanks for the pull request. Really appreciate it mahn. Can you do the same for SQL transactions as well? I think we merged it recently.

You  missed line 90 in read.go


v5.0.0-beta Is there no documentation? The installation method is the same

Documentation Section
想尝试 5.0版本
What is the current documentation state?
No response
What is your suggestion?
No response
Why is this change beneficial?
No response
Additional information
No response

https://sealos.io/docs/self-hosting/installation  这个就是最新版的


Layer reprojection broken by commit bef4d8a4

Describe the bug
I tried to update my app to use the current 'dev' version from npmjs. I found that it introduced rendering problems for the Azimuthal Equal Area projection in areas at the edge of the world (the world is projected into a circle with severe distortion at the edge of the circle).
If I revert
diff --git a/src/ol/proj/proj4.js b/src/ol/proj/proj4.js
index ca7c17c..f4fb255 100644
--- a/src/ol/proj/proj4.js
+++ b/src/ol/proj/proj4.js
@@ -60,8 +61,18 @@ export function register(proj4) {
           addCoordinateTransforms(
             proj1,
             proj2,
-            transform.forward,
-            transform.inverse
+            createSafeCoordinateTransform(
+              proj1,
+              proj2,
+              transform.forward,
+              transform.inverse
+            ),
+            createSafeCoordinateTransform(
+              proj2,
+              proj1,
+              transform.inverse,
+              transform.forward
+            )
           );
         }
       }

then it works correctly again. I'm not sure of what the use of createSafeCoordinateTransform is, but it seems to prevent transforms from behaving correctly at the edge of their validity. There are some transforms that repeat in x coordinates and I suspect that that is the case that createSafeCoordinateTransform handles. However, not all transforms behave like that. The reprojection code makes use of the fact that some points in the reprojected plane (i.e. the canvas) do not map to any valid point on the globe.
I can try and put together a jsfiddle if needed....

Thanks for reporting this @pjsg. Please provide a codesandbox with a minimal example to reproduce the problem.
The use of createSafeCoordinateTransform is to clamp source projection points that exceed the destination projection's validity extent to the validity extent, to avoid NaN or Infinity/-Infinity coordinates. That way, proj4 coordinate transforms should behave the same way as built-in transforms. Note that without global set to true on the OpenLayers projection object, that function should not modify proj4's transform at all.

If you look at https://codesandbox.io/s/dev-ol-canvas-reproj-g99e3?file=/index.js then what you should see is a circle (i.e. the globe projected onto Azimuthal Equidistant'. Instead there are lots of nasty spikies:

If you go back 2 dev versions of ol, then you get this:

(https://codesandbox.io/s/dev-ol-canvas-reproj-nbwni)

Shouldn't if (destExtent) { at https://github.com/openlayers/openlayers/blob/main/src/ol/proj.js#L668 be if (destProj.canWrapX()) {?  If the destination is not a global projection is it quite reasonable that a coordinate from global projection is unprojectable in the local projection and it should remain unprojectable.


Support creating the changelog based on pull requests only

Is there an existing issue or pull request for this?

[X] I have searched the existing issues and pull requests

Feature description
It's very common to use branch protection rules with GitHub to require a pull request before merging. With this in place, it's actually not that relevant to use the individual commits to create the changelog. Instead, you would rather use the PR titles alone with the commit-parsers to get the group, scope and so on. However, currently there is no support for doing this as

You can not limit the commits to pull requests only
The commit parsers don't allow parsing the pr_title attribute (maybe they do, but as not all commits are pull requests it doesn't work)

Desired solution
When using GitHub, add a config flag that allows you to fetch only pull requests, e.g pull_requests_only = true. Furthermore, allow the commit parsers to use the pr_title field instead of the message field to set the group and scope.
Alternatives considered
Have tried pre-processing to modify the commit message, but sometimes there's a lot of commit messages in there when there's an associated PR, and it makes it very hard to make any sense of the contents of the message.
Additional context
No response

I think adding a new configuration option for this might be too much.
Instead, you can simply achieve this by filtering by the github attribute in the template. For example:
{% if commit.github.pr_number %}
  [#{{ commit.github.pr_number }}]({{ self::remote_url() }}/pull/{{ commit.github.pr_number }})
{%- endif -%}

The commit parsers don't allow parsing the pr_title attribute (maybe they do, but as not all commits are pull requests it doesn't work)

The example I gave above will likely work in this case because we are checking if the pr_number exists.
Hope this helps! 🐻

I'm already using the suggested technique to filter out the commits, but it doesn't solve the case where the commit message don't allow me to use a parser to group them properly. So my fallback now is to use a catch all and assign a miscellaneous group, but the result is that PR:s that clearly should have a different group now end up in the miscellaneous group. If I could use the pr_title for the parser it wouldn't be a problem.

Can you share some example commits and snippet from your configuration (especially commit_parsers)?

If I could use the pr_title for the parser it wouldn't be a problem.

That would be straightforward to implement actually 🤔

I'm also interested in this one, we have the exact same problem.
We would like to mimic what Githubs built-in changelog generator does, which is to to list only the PRs, with the titles and some other metadata, grouped based on a label.
https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes

This should be now possible after #758 (simply use github.pr_title for the parser)
See https://git-cliff.org/blog/2.5.0#-grouping-by-arbitrary-fields

@orhun Awesome! 😄

That's good news. Thanks!


Inconsistent displaying of existing files and folders.

Storage Explorer Version:
Platform/OS:
Architecture:
Regression From:
Bug description
Inconsistent displaying of existing files and folders.
Steps to Reproduce
The problem is that the behavior is not consistent. One day I can see 14 folders in a parent folder, the next day I can only see 11 folders. Then if I go to the next pages and come back to the 1st page, I can again see 14 folders. These inconsistent displaying of files or folders makes me unsure of whether the file exists or not, I have to write a  program to figure out the existing files or folders by printing out them. But this is a pain if the number of files or folders gets really large.
Expected Experience
I expect to see a comprehensive list of files and folders, just like the experience with Windows folders explorer.
Actual Experience
Please see the description the Steps to Reproduce
Additional Context

Hi there,
The problem is that the behavior is not consistent so it is hard to repeat,
here is some snapshot I have.
First I can see only 11 folders (see first.PNG attached)
Then, after going to some pages behind and come back to the 1st page, I can
see all 14 folders (see second.PNG attached).
I am working at B44, and my alias is jiyili, could we talk on Teams?
Thanks,
Jiying
On Thu, Nov 29, 2018 at 12:27 PM jinglouMSFT<EMAIL_ADDRESS>wrote:

Can you tell us how to reproduce this? I can't seem to make this happen on
my end. Also, I assume you are not switching the views between "Active
blobs (default)" and "Active and deleted blobs", right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/AzureStorageExplorer/issues/926#issuecomment-442981334,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIZPEKdG_f5FoevWU7sgLkOwtL9jBoBTks5u0EMwgaJpZM4Y6bsQ
.

@laserljy, your attached images did not show up on the thread. Can you send them through GitHub instead of attaching them to an email?

@laserljy we're going to close this since you haven't replied in a while and we cannot repro the problem. If you're still having issues feel free to setup an in person meeting with us. Thanks!

This issue persists, I have some evidences too,
I'm using azure storage explorer to get files from my blob storage.
I'm uploading blockblobs from my application. I think the issue is on the query, it's not sorting properly.


Impossible to initialize Client with from_env()

Pretty sure this code is broken:
let plaid_environment = match &std::env::var("PLAID_ENVIRONMENT")
        .expect("Missing environment variable: PLAID_ENVIRONMENT. Must be set to SANDBOX, DEVELOPMENT or PRODUCTION")
        .to_string().to_lowercase()[..] {
            "SANDBOX" => Environment::Sandbox,
            "DEVELOPMENT" => Environment::Development,
            "PRODUCTION" => Environment::Production,
            s => panic!("Environment variable PLAID_ENVIRONMENT must be set to SANDBOX, DEVELOPMENT or PRODUCTION. Is actually {}", s),
        };

...as the environment is lower-cased before being matched agains the upper-cased environment names

Hey @thomasmost Amol just gave me access to take over maintenance of this library.
The 2.x branch is now at https://github.com/libninjacom/plaid-rs, but the crate name remains plaid.
You'll see that this bug is fixed from that version forward. Note, it uses PLAID_ENV, not PLAID_ENVIRONMENT.

Hi @kurtbuilds—I have a fork that is now significantly more advanced, with several bug fixes here: https://github.com/Bend-Green/plaid-rs
Recommendation on how to proceed?

I looked at your fork. The features I see you added:

de/serialize for some of the structs
bugfix for environment
adding/fixing the transactions_sync endpoint
cursor support for transactions_sync

All of those should already work/be implemented in the new implementation. If you're comfortable updating to 2.x and any of that doesn't work, let me know and I'll work on fixes.

Thanks, @kurtbuilds. There are quite a few errors when I upgrade, so I'll have to set aside time for it later this week or next.

Let me know if you encounter issues!


Two clients disconnecting without sending client.disconnect() breaks renet

Renet breaks when two clients disconnect without using the proper client.disconnect() function and a new client subsequently connects.
I have included a video demonstrating running the demo_bevy.
One potential cause of this issue could be that all of the clients and the host have the same IP address.
Important to note: I´m exiting the client with ctrl+C, witch causes the client to exit with sending client.disconnect().
https://user-images.githubusercontent.com/51098127/210580106-a30edbd8-76a5-4a96-8f00-8089bd771e8c.mp4

This is probably related to https://github.com/lucaspoffo/renet/issues/63#issue-1474803207

Fixed by https://github.com/lucaspoffo/renet/pull/82
Tested using Windows, doing the same steps as the GIF and no problem occurred


docs: Fix example

Tested and working. This fixes the below error with the previous example:
│ Error: creating IAM Policy (foo-20230823192221893600000002): MalformedPolicyDocument: Syntax errors in policy.
│ 	status code: 400, request id: 6448aac6-961f-4fe0-9b72-f37dfd22d78c
│
│   with module.foo.module.eks_blueprints_addon.aws_iam_policy.this[0],
│   on .terraform/modules/foo.eks_blueprints_addon/main.tf line 237, in resource "aws_iam_policy" "this":
│  237: resource "aws_iam_policy" "this" {
│

What does this PR do?
Sets create_policy to false, so the module doesn't try to create a policy when the user is trying to pass in a existing policy.
Motivation

Resolves #16

Test Results

Additional Notes

Thanks!


Nasty ERR msg for sudo ros service subcommands due to missing -vm-tools

RancherOS Version: (ros os version)
v1.1.0
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
linode, docker-machine
I tried to create a service via sudo ros service create <servicename> and got the following error:
ERRO[0000] non-200 http response: 404
ERRO[0000] Failed to load service(kvm-vm-tools): non-200 http response: 404

I noticed the service enabled in the list from sudo ros service list so I tried to disable it:
$ sudo ros service disable kvm-vm-tools
FATA[0000] kvm-vm-tools is not a valid service

Does this error message prevent your command from working? or is it just extra noise? (When I tested, it seemed like noise that I didn't have time to squash)

You're right!  It did create the service.  I figured after the big scary red ERRO that it didn't work.

I'm running ROS as a kvm guest (Proxmox VE), trying v. 1.1.0 for a first time. I found nothing is running on port 8080 so I've tried to install service rancher-server or rancher-server-stable ... both somehow depends on kvm-vm-tools which is enabled but I can't stop/disable/delete that service ... I'm getting the same result ... HTTP 404.

Same with https://github.com/rancher/os/issues/2168

@niusmallnan thanks for solving the isuue.
side note: marking the older (#2076) issue as a "same with" (aka "duplicate of") the your younger (#2168) issue is very funny. :)


Surface Radiation Unit Testing

Compares surface exchange radiation problems with analytical solutions for multiple geometries and MPI process numbers.

Requires DMSwarm patch in order to pass tests.


MembersListCard fix

Hey, I just made a Pull Request!

Changed static route in MembersListCard to use a dynamic route. Solves this bug: https://github.com/backstage/backstage/issues/19289
Updated test classes to work with dynamic route

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Happy to contribute @Rugvip 😃. Thank you both for the feedback @freben @awanlin.


check-tomcat-app-deployment.rb: password misspelled in: long: '--passowrd PASSWORD',

Password is misspelled in check-tomcat-app-deployment.rb
long: '--passowrd PASSWORD'

Sorry I need to update the README stating that I have actually released this plugin to the sensu-plugins team to allow for better community support.  You can see it here https://github.com/sensu-plugins/sensu-plugins-tomcat
The bug you listed has been corrected and a new version of the GEM has already been released.
Thanks so much for  helping improve this project !


feat(nuxt): automatically install optional features on StackBlitz

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[x] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
In StackBlitz we could assume the envoriment is isolated and safe, we could install optional deps when enabled automatically to provide better overall experience when opening playgrounds.
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Is there a way to test this on StackBlitz?
I have some doubts about the compatibility with WebContainers, since the current prompts are failing when accepted manually.


fix(apiserver): fix StorageNodeList api

What this PR does / why we need it:
The StorageNodeList API returns a LocalDiskNode infomation but not a LocalStorageNode information. It is not a reasonable result in StorageNode API
fix #1328
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (4d8e24b) 28.74% compared to head (82abac4) 28.74%.
Report is 27 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1337   +/-   ##
=======================================
  Coverage   28.74%   28.74%
=======================================
  Files          34       34
  Lines        3079     3079
=======================================
  Hits          885      885
  Misses       2077     2077
  Partials      117      117

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


'HF_MODEL_QUANTIZE' value error

The value of HF_MODEL_QUANTIZE in huggingface-large-model-inference.ipynb needs to change from 'true' to 'bitsandbytes' due to a version update.

I just submitted PR #17 to fix this issue. Please review and accept. Thanks!


toggleChildPropsOnInView toggles class names

Using InViewMonitor to trigger component props on a Video player. When toggleChildPropsOnInView={true} it toggles classes even when toggleClassNameOnInView={false}. It is possible to have both? Toggle childProps, but not css classes?
Usage:
<InViewMonitor
  childPropsInView={{ isPlaying: true }}
  toggleChildPropsOnInView={true}
  toggleClassNameOnInView={false}
  classNameNotInView="animated fadeOut"
  classNameInView="animated fadeIn"
>
    <Video key={item + index} src={item} />
</InViewMonitor>

So to clarify, you don't want the class name toggling, so what you would want to use would be:
<InViewMonitor
  childPropsInView={{ isPlaying: true }}
  toggleChildPropsOnInView={true}
  toggleClassNameOnInView={false}
>
    <Video key={item + index} src={item} />
</InViewMonitor>

Let me know if that seems right.
I do think this is reasonable, so I'll look into fixing this.

Thanks for the response!
Correct, no class name toggling. But it would be nice if classes still apply on first InView.

Pushed a fix for this bug. It will still apply the clas on first inView - as long as you provide the classNameInView prop.
``jsx
<InViewMonitor
childPropsInView={{ isPlaying: true }}
toggleChildPropsOnInView={true}
classNameInView="animated fadeIn"

<Video key={item + index} src={item} />

```
(`toggleClassNameOnInView` defaults to `false`, so doesn't have to be passed as a prop)

But it would be nice if classes still apply on first InView.

This however is currently not supported in this library.

Okay, pushed commits for this too now, published a release candidate version<EMAIL_ADDRESS>@austinmayer do you think you could try that one and test that it does what you wanted; before I publish a new latest version?

Alright, we're in business<EMAIL_ADDRESS>looks good, thanks for the rc!
No worries re: the class functionality if it doesn't fit or contradicts this fix. My use case was to have a video fadeIn and start playing, stop playing when out of view while retaining visibility.

No worries re: the class functionality if it doesn't fit or contradicts this fix. My use case was to have a video fadeIn and start playing, stop playing when out of view while retaining visibility.

The release candidate should support exactly this: combination of classNameInView and toggleChildPropsOnInView. Did you test it?

Got mixed up in the thread copy edits.
Yes, seeing the proper combination of classNameInView and toggleChildPropsOnInView
Thanks!

Got mixed up in the thread copy edits.

Understandable. :)
Great that it all works now then, will release the new version.

<EMAIL_ADDRESS>is out!


base_deatils and product_details implementation Question

I would like to implement 2 modules: base details and product_details, follow the instruction available in each modules as reference for the implementation, also try to installs the product_details module,  but i only have blank  Details field (can not select anything or create the the details as similar to other m2one fields.
Is the product_details module miss the details model or still need to be created (or need to extend the modules) in order to see how it will work?
I am very new to coding, please give a more lines of clue or guide to implement it correctly. As example with this product_details....how to add and edit the details then?
Thanks and regards,

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Hi,
you need to inherit _model_selection. I've updated the documentation https://github.com/it-projects-llc/misc-addons/blob/10.0/product_details/doc/index.rst


Calculation Table with support the icons

Dax code with result icon

Created rules

Don't work  - "error when rendering the report"

This question does not seem to be related to Tabular Editor.


Typo

Hi,
just a small thing:
In the README is a type:
 // Support REGEX Route params
  mux.Get("/index/#id^[0-9]$", http.HandleFunc(IndexHandler))

->
 // Support REGEX Route params
  mux.Get("/index/#id^[0-9]$", http.HandlerFunc(IndexHandler))

i'll fix this, thanks !


Repeat the loop by some workers

hi @walkor
I have a database entry program that uses 8 workers
In the program, a for loop is used, which is responsible for entering information (a line is added with each loop rotation).
Sometimes the system randomly repeats each loop two or more times (instead of the loop being executed only once, it is also executed by other workers, for example, the second loop is executed three times)
This happens in some cases and most of the time the program works properly
My question is, is there a problem with my program ??
And how can this problem be solved?

Sorry. From the information you provided, I can't determine whether there is a problem with your program and can't give any comments.

In general, when we use several workers
Are the loops run separately by each worker?

Yes
Message ID: @.***>

Thanks @walkor


Please add a license

I've converted your code to Delphi but you're missing a license. Thank you

I'll do asap, thank you very much

added license file (MIT license)


NPM package should not ship development files

We should ship just the "active" parts of the module; i.e., those used at run time.  To do this, we need an .npmignore file that prevents publishing the tests, examples, Makefile, etc.

With the following .npmignore rules:
examples/
tools/
test/
Makefile*

We are down to shipping only the needed files:
$ npm pack && tar tfz *.tgz
package/package.json
package/.npmignore
package/README.md
package/LICENSE
package/lib/forkexec.js


[Question] How to make it work with IE11?

I have SJOT implemented and working fully on chrome. I have a requirement to make same work on IE11 too. When I load SJOT in IE11 it gives error at class keyword. Can you please advice? Thanks.

I've updated sjot.js to replace all ES6 features and tested it against IE11. The update will be released once the code reviews and regression testing are complete. For a sneak peak: our interactive demo at https://www.genivia.com/get-sjot.html uses the updated version to validate JSON and check SJOT schemas. We may update the SJOT schema converters also, but not very soon. These still use ES6 features.

Fixed in 1.3.16.


Add emoji picker to chat composer

Many thanks to @nucleartux!

Played around with it and ended up here:

✌


Split akv verification tests to fix SSL issue

Removed *_verification.phpt and replaced with _usernamepassword.phpt and _clientsecret.phpt.

This change is

Codecov Report

Merging #781 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #781   +/-   ##
=======================================
  Coverage   80.06%   80.06%
=======================================
  Files          25       25
  Lines        7323     7323
=======================================
  Hits         5863     5863
  Misses       1460     1460

Impacted Files
Coverage Δ

...ev/vc14/x86/php-7.1.17-src/ext/sqlsrv/php_sqlsrv.h

...c14/x86/php-7.1.17-src/ext/pdo_sqlsrv/pdo_util.cpp

...x86/php-7.1.17-src/ext/sqlsrv/shared/core_sqlsrv.h

...x86/php-7.1.17-src/ext/sqlsrv/shared/core_conn.cpp

.../php-7.1.17-src/ext/sqlsrv/shared/core_results.cpp

...c14/x86/php-7.1.17-src/ext/pdo_sqlsrv/pdo_stmt.cpp

...php-7.1.17-src/ext/pdo_sqlsrv/shared/core_init.cpp

...phpdev/vc14/x86/php-7.1.17-src/ext/sqlsrv/init.cpp

...x86/php-7.1.17-src/ext/pdo_sqlsrv/php_pdo_sqlsrv.h

...x86/php-7.1.17-src/ext/sqlsrv/shared/core_util.cpp

... and 40 more

Continue to review full report at Codecov.

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

Regarding strsize, it's 64 just to make sure the column size is large enough to accommodate the string values in values.php that are used for this test. But it changes in other AE tests that use other longer strings in values.php.

Coverage remained the same at 74.697% when pulling bd9d85b862c7c9d1999457543bdf82a52ff2f2ed on david-puglielli:akv-verification-test-fix into f0eefafa2e1ca3b77fc1bac0fdc873ae7730580d on Microsoft:dev.


Type error when 'npm run' command is used

Github issues for [JS]
Sample information

Sample language: nodejs
Sample name: 	21. Luis-with-appinights:

Describe the bug
TypeError: Cannot read property 'appId' of null
To Reproduce
Steps to reproduce the behavior:

Get all the Prerequisites.
Run the nmp install command after specifying the path to the sample.
3 Run the az login and az subscription commands.
4 Run the msbot clone command.

No information about how to get the path location for the sample in the bot-builder-samples folder.
5: Run the npm start command. It gives error,
TypeError: Cannot read property 'appId' of null
In index.js file.

Expected behaviour
The sample should work according the readme.

Closing as this is a non-blocking issue that has had PRs merged for a fix. Regarding the intended behavior mentioned above, .bot files and msbot are both on their way out, so even if the behavior is unintended, it won't likely be addressed.


Python 3.8+ port

Implement FlexVer in Python via a FlexVer class which implements total ordering and a compare(str, str): int function which is like the Java FlexVerComparator.compare() implementation.
This was tested on Python 3.8 up to 3.11, using the files in the tests folder as input.
If this is accepted, We will publish it to PyPi under the flexver name.

[x] I own the full rights to my contribution, and agree to release it under the terms of the Creative Commons Zero Public Domain Dedication

for the spaces between parentheses, its for readability, they help us understand divide symbols and words, make things easier to parse.
although can remove if needed.
the ccamelCase is just personal preference, will change the casing as we've also noticed that the PEP says to use snake_case

moved to snake_case and fixed workflow/tests

Thanks!

published! as said, can be found under flexver on pypi: https://pypi.org/project/flexver


New collective flow

Here is the wireframe version open for feedback.
Please have a look.
Prototype:
https://www.figma.com/proto/KinuveYf4WUlRIXzMTnmIsmO/OC.COM-XX1-Lab?node-id=1198%3A18753&viewport=743%2C489%2C0.08176331967115402&scaling=min-zoom
Figma overview:
https://www.figma.com/file/KinuveYf4WUlRIXzMTnmIsmO/OC.COM-XX1-Lab?node-id=638%3A12661

Good! We like it

Overall, it's great! So much better than the current experience!
I especially like:

That you get up and running very quickly with minimal data entry.
How you arrive to your new Collective page and the design guides to add more content and activate sections.
Splitting all the questions out into different screens so you're not overwhelmed with too much info at once.
Putting extra options in places where it feels natural, like suggesting they add tiers after they've activated financial contributions.

Notes:

When creating new user instead of "add" it should be "invite". The person should receive an invitation and click accept. At that point we will show them the terms of use, etc.
We decided not to use the word "team" to refer to core contributors. The terms are "core contributor" and "Collective Admin" (or just 'contributor' and 'admin' is fine here).
Why add other core contributors before the page has been created, while we push everything else to after the creation step? To me it makes more sense to treat it like all the other sections on the blank new Collective page that are encouraging you to take actions, such as activating financial contributions, making an update, etc. Adding more contributors could be like this, to make the initial startup experience even more simple and quick.
What is the purpose of including the "values" screen here? Is it meant to just be a friendlier version of the content of the terms of service? I think we should be careful of the wording because not all Collectives allow anyone to join and contribute, sometimes for good reasons.
The 'contribute' section should come first when you arrive at the new Collective page. Activating financial features is the first thing most people will want to do, so it doesn't make sense to put it below updates.
Should be "select or create organization" (so people who know they don't have one yet aren't confused) and if they are creating one it should say "create organization" not "create user".
If they select an existing organization that they are not already an admin of, will it send some kind of validation to the org admin to accept them? Or should we assume no one would have a reason to say their money is held by an organization if it's not true? Would this be a "side door" way to get your Collective in a fiscal host without going through their approval process?
Next to "connect stripe" and "add bank account" can we have "add paypal" since it's the next most common? The truly ideal feature would be user-defined payment methods, so a group who uses Venmo or whatever can just define that. Then these would show up as the contribution options. This is probably out of scope, but we're also facing this with the expense redesign (we will need to enable hosts to define their accepted payout methods so expense submitters can select from them) so I'm wondering if we should just take it on properly.
One issue with applying to a fiscal host - as designed here, I don't think the user has had a chance or been asked to input much info about their Collective, such as description, website, etc. It seems likely this will result in host admins getting applications without any information to judge the Collective by. How can we deal with this? My dream solution would be to enable hosts to define some questions the applicant needs to fill out when applying, but I assume that's more part of the host dashboard project than this project, right?
If a user clicks "apply" to select a fiscal host in this flow, does it take them out of the flow? Currently I think you end up going to the fiscal host's page, but if it's possible to keep them in this flow and just trigger the application, I think that would be better, because if they end up on the host's page then we kind of lose them before completing this creation experience.
It seems like this design "silently" creates a host for self-hosted Collectives without really talking to them about "fiscal hosting" as a concept. That's perfect, and will be great for that use case. I assume this will set the toggle for "accept applications from Collectives" to OFF in their fiscal host settings?
Instead of "go back to your Collective page" how about the button says "finish"? It's a pretty complex process they've just gone through and it should be clear when they've reached the conclusion.

When we will be able to see the screens for after they click the "open source" option at the start? I think there are some issues to sort out there, like:

Not all Open Source projects want to join Open Source Collective. What happens to them if they click the open source option at the start? Some will want to be self-hosted, some will want to join OC EU, etc. (Although the majority will be looking to join OSC).
Can we please fix the bad experience people are having who want to join OSC but do not want to verify using the Github stars flow? This comes up a lot and our current design is confusing.

Great progress, this is brilliant. Two comments:
Page 9: should be People not Peoples
Page 11: Account holder should be bank account holder, otherwise it's confusing with the holder of the open collective account (owner of the profile)

When we will be able to see the screens for after they click the "open source" option at the start? I think there are some issues to sort out there, like:

+1

This is good! The only feedback I'd have is that having the Create an account and Login forms on the same page is confusing to me (too many fields, two primary calls to action).

Thanks for this extended review @alanna ! :-)
See my responses below.

When creating new user instead of "add" it should be "invite". The person should receive an invitation and click accept. At that point we will show them the terms of use, etc.

ok

We decided not to use the word "team" to refer to core contributors. The terms are "core contributor" and "Collective Admin" (or just 'contributor' and 'admin' is fine here).

ok

Why add other core contributors before the page has been created, while we push everything else to after the creation step? To me it makes more sense to treat it like all the other sections on the blank new Collective page that are encouraging you to take actions, such as activating financial contributions, making an update, etc. Adding more contributors could be like this, to make the initial startup experience even more simple and quick.

The idea is to make sure that after the creation process flow you know and you can already share:

the URL of your collective
the email address of your collective (which requires you to understand who will receive the emails sent to this address)

What is the purpose of including the "values" screen here? Is it meant to just be a friendlier version of the content of the terms of service? I think we should be careful of the wording because not all Collectives allow anyone to join and contribute, sometimes for good reasons.

The goal is to make a more fancy "please accept the terms and conditions" and share the general values in plain English.
Those should be values that can apply to all collectives. Do you want to take a stab at suggesting what those should be?
If one shares code on Github, they share the value of "transparency", "anyone can contribute" (which doesn't mean that all contributions are accepted), etc.

The 'contribute' section should come first when you arrive at the new Collective page. Activating financial features is the first thing most people will want to do, so it doesn't make sense to put it below updates.

That might be true for the OSC because collectives haven't had any financial contribution/transaction before creating an open collective. And their goal when creating an open collective is to collect money.
So let's definitely make sure that this is the first section for them.
For self hosted collectives, the priority should be given to the budget (and manually recording transactions).
Updates should be the first thing returning users see on a collective page, in the same way that when you open facebook, their first show you "new things you haven't seen yet".

Should be "select or create organization" (so people who know they don't have one yet aren't confused) and if they are creating one it should say "create organization" not "create user".

ok

If they select an existing organization that they are not already an admin of, will it send some kind of validation to the org admin to accept them? Or should we assume no one would have a reason to say their money is held by an organization if it's not true? Would this be a "side door" way to get your Collective in a fiscal host without going through their approval process?

You can only select an organization that you are an admin of.

Next to "connect stripe" and "add bank account" can we have "add paypal" since it's the next most common? The truly ideal feature would be user-defined payment methods, so a group who uses Venmo or whatever can just define that. Then these would show up as the contribution options. This is probably out of scope, but we're also facing this with the expense redesign (we will need to enable hosts to define their accepted payout methods so expense submitters can select from them) so I'm wondering if we should just take it on properly.

Out of scope, but yes, I would totally love to add that. This design makes it easy to do so in the future.

One issue with applying to a fiscal host - as designed here, I don't think the user has had a chance or been asked to input much info about their Collective, such as description, website, etc. It seems likely this will result in host admins getting applications without any information to judge the Collective by.

That's a great point.
Note that in this process, you first get to see your collective page (and therefore get the opportunity to make it look good with logo/cover/description) before you get to apply for fiscal host.
However, it is indeed very possible that some people may apply before providing all that info.
I'd suggest that we disable the 3rd option with a message "before you can apply for fiscal sponsorship, please make sure that you have added a proper description to explain in more details the activities of your collective and how you plan to spend the money that you will be collecting".

How can we deal with this? My dream solution would be to enable hosts to define some questions the applicant needs to fill out when applying, but I assume that's more part of the host dashboard project than this project, right?

That would be indeed great. But yes, I'd keep that for another project.

If a user clicks "apply" to select a fiscal host in this flow, does it take them out of the flow? Currently I think you end up going to the fiscal host's page, but if it's possible to keep them in this flow and just trigger the application, I think that would be better, because if they end up on the host's page then we kind of lose them before completing this creation experience.

There is one default / recommended host where they can just apply and then they end up in the screen where they can edit their tiers.
If it's not one of the recommended hosts, they can click on it to know more about them.
Maybe you'd prefer that we show directly the apply button below each host card, assuming that they can open in a new tab the page of the host if they want to check them out?

It seems like this design "silently" creates a host for self-hosted Collectives without really talking to them about "fiscal hosting" as a concept. That's perfect, and will be great for that use case. I assume this will set the toggle for "accept applications from Collectives" to OFF in their fiscal host settings?

Yes. By default, most people don't want to bother with someone else's collective. They will start by hosting their own, maybe a second one where they are also involved. It's a much more advanced feature to start hosting other people's collectives.

Instead of "go back to your Collective page" how about the button says "finish"? It's a pretty complex process they've just gone through and it should be clear when they've reached the conclusion.

I like that.

Not all Open Source projects want to join Open Source Collective. What happens to them if they click the open source option at the start? Some will want to be self-hosted, some will want to join OC EU, etc. (Although the majority will be looking to join OSC).

Yes, just added that in the flow. If you select "manually", it goes to the default flow for creating a new collective and the default host that will be recommended if you want a fiscal host will be the OSC.

Can we please fix the bad experience people are having who want to join OSC but do not want to verify using the Github stars flow? This comes up a lot and our current design is confusing.

This is fixed with the link below the "connect with Github" so that it gives a way for people to skip that flow (see screenshot above).

"Create Account" will still be confusing. People not familiar with our platform don't understand if they're creating a personal account or a collective there. We need to provide some hints.

The "Recommended fiscal sponsor" screen is too close to what we have today and doesn't address any issue that were highlighted in our preliminary discussions.

@znarf We cannot address all issues at once. What issues in particular do you think that we should address in this first iteration in regard to that "Recommended fiscal sponsor".
I see your point for the create account. Then I'd suggest we simply reuse what we have today (but without the first name / last name since we are consolidating everything within Collective.name):

@xdamman The magic recommendation with one host based on tag and currency is just wrong and should be absolutely re-considered.
I would recommend to not try to filter by tag and currency, display a full list of hosts open for applications, with an highlight on "OSC / Europe / UK / Brussels / Paris" on top.

For what I've been reading, it seems that this "Fiscal Host Application" needs to be designed as an individual experience and connect with different parts of the platform like this flow. Still, I imagine that this is a future project.
In that case, I would keep it as simple as possible and take the proper care to design this, and other flows to be navigated as a smooth, nicely wrapped experiences.

Thanks @xdamman ! Responses below....

adding contributors

The idea is to make sure that after the creation process flow you know and you can already share the URL of your collective and the email address of your collective (which requires you to understand who will receive the emails sent to this address)

Personally I would still put adding contributors alongside all the other actions to expand your Collective after the initial creation, because lowering the barrier to initial creation is such an important goal of this redesign. As long as one admin at least (the creator) is getting the messages, it will be fine. If it's a priority for them to add people, they can do that first thing after creation.

fancy terms & conditions screen

The goal is to make a more fancy "please accept the terms and conditions" and share the general values in plain English. Those should be values that can apply to all collectives. Do you want to take a stab at suggesting what those should be?

I support the impulse to make this interaction more human and warm, since accepting Tc&Cs is so cold usually. However, due to the importance of simplification in this project, I suggest leaving this out for now. There are too many variables to get right and also if we're changing it here we should change it every time we ask someone to accept the terms. Let's treat this as a seperate project for the future.

order of sections after creation

For self hosted collectives, the priority should be given to the budget (and manually recording transactions).

Collectives using our system for manual expense recording, including self-hosted ones, are extremely rare. The vast majority some to us specifically for the financial features, namely enabling contributions. Until we have any other evidence, I think we have to respect how people actually use the platform. I understand you're trying to shift that with this redesign and I support that effort, but we still need to make sure the most common use cases can easily find what they are looking for.
Maybe trying to solve this with section order is the wrong approach, however. Upon initial creation there could be some kind of banner or helpful guide bubbles or something to help users understand all the actions they can take at that point to expand their Collective, regardless of which they want to focus on first. I have seen this in other apps and it seems to work well.

ensuring Collectives have info hosts can judge by

I'd suggest that we disable the 3rd option with a message "before you can apply for fiscal sponsorship, please make sure that you have added a proper description to explain in more details the activities of your collective and how you plan to spend the money that you will be collecting".

I don't think this is the way to go, because it puts up a big barrier to the flow if someone is creating a new Collective and applying to an existing host. Instead, if they choose the fiscal host option can we just require them to fill out their "about" section as part of the flow? I'm wondering if we should actually ask all Collectives to fill that out as part of creation - you say you want them to be able to share their link immediately, so don't they need at least a basic description from the start? The other main field I'd suggest requiring in setup is website (they can leave it blank if they don't have one, but if they do have one it's the key info for fiscal host consideration).

applying to host from within flow

Maybe you'd prefer that we show directly the apply button below each host card, assuming that they can open in a new tab the page of the host if they want to check them out?

Yeah I think this would be good, to keep them in the flow. It's important users check out the details of the host acceptance criteria, but they can click into their page to see that if they need to.

Open source projects trying to join non-OSC host or self-host

If you select "manually", it goes to the default flow for creating a new collective and the default host that will be recommended if you want a fiscal host will be the OSC.

I still am not clear on how these flows will work for different cases. Can you create screens for:

Open source project joins OSC

option 1: using github verification
option 2: using manual verification

Open source project joins OC EU
Open source project self-hosts

I would recommend to not try to filter by tag and currency, display a full list of hosts open for applications, with an highlight on "OSC / Europe / UK / Brussels / Paris" on top.

@znarf ok - on it

lowering the barrier to initial creation is such an important goal of this redesign. As long as one admin at least (the creator) is getting the messages, it will be fine. If it's a priority for them to add people, they can do that first thing after creation.

@alanna I see. What about this:
Instead of asking the creator of the collective to add people (which I agree could take time and get in the way of getting things done quickly), what about we focus this second step on "email" (step one is "collective name / url", step two would be "collective email"). We could offer 3 options:

info@:collectivelSlug.opencollective.com (default) (in which case we should show the current design where people can add more people that will receive the forwarded emails)
another email address (simple email input field)
a public url (e.g. link to your github issues page, or contact form on your website)
none (people can only contact you by creating new conversations on your collective page)

Then the "continue" button. If people just click on it, the default will be the collective email will forward only to the creator of the collective.

fancy terms & conditions screen

We anyway need a step to accept those. So let's get something simple done here.
I'll create a dedicated issue for it.
It's only text anyway so it's not blocking.

order of sections after creation

I took note of your input and I'll make sure it will be working great for the OSC.

ensuring Collectives have info hosts can judge by

Good idea. Let's make sure we ask them for a description and url if they haven't provided one yet.

Open source projects trying to join non-OSC host or self-host

That's the flow. Unless they use the github auth, they fall back to the manual create collective flow

Whenever they will want to activate financial contributions, they will be given the classic options of self host or find a fiscal sponsor. If they choose the latter, they will be given the option to apply to OSC or OC Europe or others.

Ok sounds good @xdamman
I still think people are going to trip up trying to escape Github validation. To further improve the experience, I request the following:

Instead of a big button for github and tiny text for manual, have two buttons of equal weight on that screen.
Change the text to "Verify using GitHub stars" and "Request manual verification".
I'll do an update to the text on that screen soon to help it be even more clear (no need to wait on that to move forward with your flow though).

Instead of a big button for github and tiny text for manual, have two buttons of equal weight on that screen.

@xdamman + 1 to this - The current design you shared is optimized for github integration, but both pathways should have the same weight.

We think these illustrations should come with a short description of the decision users are making: "This option work with organizations that..."

What do you think


VPN will prevent updates, dictionary downloads and audio playback

VPN will prevent updates, dictionary downloads and audio playback even if i split-tunnel JL

Tried with Windscribe but cannot reproduce the problem.
What OS and VPN do you use? What is the exact error you get when you try to do those things? Can you send me the relevant log file (it should be located in "...\JL\Logs")?

Using Win11 & NordVPN.
log20230129.txt

I neither use Windows 11 nor NordVPN and NordVPN does not seem to have a free trial.
Can other programs (excluding the browsers) check for updates and do things that require Internet connection when you use NordVPN?
Can you install Windscribe just to see if you get the same error while you use it? If you do not get the same error, then it should mean the problem is related to VPN you use. If you do get the same error, then the problem is related to your system configuration (your OS, firewall settings, proxy settings etc.)

was able to figure it out. the problem is caused by nordvpn´s split-tunnel feature. if i enable it breaks things and JL won´t be able to connect to the internet it seems (doesn´t matter whether i include in the list of programs that should be ignored by nord or not).
so i basically have to disable split-tunneling in nordvpn in order to use JL properly, which is not ideal but related to nord and not JL. will change my vpn provider soon anyway, until then i will just use this workaround for my reading sessions.


Get-LocalGroupMember - Failed to compare two elements in the array, v2

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Join a Windows Server 2016 Core server to a domain.
Added 3 domain groups to the local administrators group.
Moved the server back into a workgroup.
Ran Get-LocalGroupMember -Group Administrators
Expected behavior
It should return the group members as it would prior to moving to a workgroup and just display the unresolved SIDs for the old domain. Then ideally allow you to reference those unresolved SIDS for Remove-LocalGroupMember.

Actual behavior
Throws an exception:
Failed to compare two elements in the array

Error details
See: https://github.com/PowerShell/PowerShell/issues/2996

Environment data
See: https://github.com/PowerShell/PowerShell/issues/2996

Visuals
See: https://github.com/PowerShell/PowerShell/issues/2996

Reference to unreasonable and unexplained closure of https://github.com/PowerShell/PowerShell/issues/2996

Reference to unreasonable and unexplained closure of #2996

It's a module shipped with Windows and not covered by this repo.


Burp Extension to scan GraphQL Endpoints

NOTE: Please search for the problem you want solved first to see if a tool already exists. There are a lot of tools out there, so please try and avoid requesting the wheel be reinvented. Additionally, tool ideas like "I want something like X but does Y" is probably better suited as a feature request for X not a new tool here.
Have you, the best of my ability, searched online for a pre-existing tool that meeting your requirements?
Describe the use case for the tool you want built.
A clear and concise description of what you want the tool to do and what problem it is solving. Consider this the design specification for what you want built. The less detailed you are, the more room for ambiguity in the final product.
Example input data.
If you have examples of what input this tool will be operating on that will significantly help potential developers.
Potential runtime environments
Where this potential tool will run can impact language or compiler decisions so please list the environment(s) this tool will be running in.

/IVolunteerAsTribute

/IVolunteerAsTribute

/IVolunteerAsTribute


high start_offset may cause OOM

Very large start_offset are very expensive and can cause the server to crash.
E.g. this query costs more than 6GB memory and takes more than 3 minutes:
curl -sS 'http://localhost:7280/api/v1/hdfs/search?query=*&max_hits=0&start_offset=40000000'

We should limit start_offset to values that we can handle or improve the start_offset algorithm.
This may also be an issue for data extraction, which would be naively handled with increasing start_offset.

Closed via https://github.com/quickwit-oss/quickwit/pull/1539


Check if image exists in ECR

The current implementation only checks if it's available via in-memory cache. If it is not then a download will be initiated – which effectively only syncs the latest layers. But ideally, no download should be initiated as this seems to count towards the rate-limiting of some providers.

Does this change address this issue by adding a break in the workflow if the image is already in the target repo?
https://github.com/estahn/k8s-image-swapper/commit/a133c782be4e3001a9ce829c50fd7ae79c0a4c75

From practical experience this does not appear to be an issue. If so, I will reopen it.


add unit test to cmd/placement/options

Description
Test whether each variable is filled with default value. This test is not covered so the coverage of this file is only 25% currently.

Thanks @MregXN!