Why do partition and timestamp default to 0 and 11 in producer record?

See https://github.com/pyr/kinsky/blob/a5309073264a1d319d9303a839d9606331560212/src/kinsky/client.clj#L569
Timestamp defaulting to 11 and not 0 as specified by docstring seems weird.
More importantly, why do we need such defaults? They override Kafka API behavior with regards to default values, and they make (send! [this topic k v]) and (send! [this topic k v headers]) behave inconsistently (the first does not override Kafka API behavior, the second does).
Best is to not define any default values and let library clients handle them when needed.

Hi @fmjrey ,
Happy new year and thanks for the report!


Private reporting of a security vulnerability

Description
Dear Cupy team,
I have identified a security vulnerability in the codebase of cupy latest release.
I would like to report it privately. I suggest that you opt-in this Github feature in order that the process goes smoothly.

Kind consideration
@Sim4n6
To Reproduce
I rather do that privately please.
Installation
Source (pip install cupy)
Environment
# Paste the output here

Additional Information
No response

Hi @Sim4n6, just enabled the feature.  Thanks for reporting!


Test our OpenSSL random override more deeply

This change updates our OpenSSL override tests to check s2n's DHE
function directly. This now also passes our tests on Mac.

Note: travis build passed on Mac. Failed on Linux due to that intermittent mlock() issue we're dealing with separately.

Thanks!  I like this a lot better, merging!


Add other groups to the readme

This adds our group along with last semesters group to the readme
I put the names in a drop down so (hopefully) as more groups use this repo and append to it, it won't take up the entire readme

I just used the sorting I used for the meeting minutes, think I got it from some random website.
Where do you think the mysterious Lachlan Van Der Klift guys name should be placed?

just not last imo, i heard bad things happen at 3am to repositories that do that

Zero clue where else to put them :thinking: is there a place lower than bottom?
Just add a commit to change them or write suggestion with a review


fix(typography): refactored px to rem for font-size and no unit for line-height

Describe pull-request
Refactored both tegel font-vars and typography-package vars to use rem for font-size and unitless for line-height. This does introduce some pretty big changes in the typography package, meaning we would have to do a major release of it and clearly communicate that all fonts now are based on rem with the base of 16px.
Solving issue
Fixes: AB#2830
How to test
Screenshots
Additional context

I thought the old typography package was using rems, is this not the case? (before @theJohnnyMe  changed it some weeks ago)

If it did it was based on base 4. Which it's not anymore, so i guess this would have to be highlighted.

I thought the old typography package was using rems, is this not the case? (before @theJohnnyMe changed it some weeks ago)

I thought the old typography package was using rems, is this not the case? (before @theJohnnyMe changed it some weeks ago)

If it did it was based on base 4. Which it's not anymore, so i guess this would have to be highlighted.

Well I guess this would also mean we change the theme-light to not set base 4px. Which we might not wanna do now. So should this PR only update the font-vars that are inside the tegel package, and not poke around in typography package?


Direct users to all Project Pythia content gallery from landing page

This can take one of two forms:

We can filter the gallery by affiliation as in #156 and direct people to this filtered gallery from the landing page
We make this a separate gallery that is just a subset (this will allow the user to then filter this gallery by package, domain, format)

The tutorial videos are added in #157 to the resource gallery. We still need to add the foundations book pages that are complete to the resource gallery. This is some conversation about this issue over in #157.
My next step is to go through and add affiliation tags to several of the cards, and add an affiliation filter menu (Pythia, Pangeo, Unidata, etc). In doing this, I will change the current "affiliation" author information to "institution." I have started this in #160. This will require me to edit the auto-PR for submitting a resource to include this new tag and update the author keys.
Then I will take our filtered-to-Pythia-only content and link to that directly from the portal. It is possible that we might want to edit the yaml_gallery_generator to create an entirely new gallery of Pythia content (not one that renders as a filtered gallery) so that it is cleaner and allows filtering upon it.

Once #227 is merged (which highlights Pythia content directly on the landing page), should we close this, or do we still want to create a dedicated gallery page with Pythia-only content as described by @jukent above?

Would we want to add a button to the gallery that loudly says, "See all Project Pythia resources"? Right now we can filter to Pythia content using javascript (so it isn't actually a separate web page) but we don't make Pythia have any special treatment. I'm sure there is a way to then link to the page with the "pythia" checkbox already ticked from the home page, but I don't know how to do that yet.

Once #227 is merged (which highlights Pythia content directly on the landing page), should we close this, or do we still want to create a dedicated gallery page with Pythia-only content as described by @jukent above?

That's a good question. The original plan wrt this issue was to auto-select appropriate filtering on the Resource Gallery, and simply direct viewers to that. With #227 we're directing users to the Xdev tutorial site, which pretty much has all of the information that would be available from the gallery, but it doesn't have the Pythia theme, etc. My suggestion:

Close this issue or change the priority to low. Either is fine by me.
Add the Pythia logo prominently to Xdev tutorial site

Regarding @jukent's comment right above, I like the idea. An alternative to adding a button if that presents a technical challenge a simple callout that says something like "Want to see all of the Pythia produced content?. Simply set the affiliation to "Pythia".

a simple callout that says something like "Want to see all of the Pythia produced content?. Simply set the affiliation to "Pythia".

@clyne That does sound like the easiest step

@clyne I think that we should move the Xdev tutorial content to Pythia.  And we can direct people from the Xdev site to Pythia.  (Note that moving the page over is easy.   You just have to copy the cli/mktuts.py script from the Xdev repo into the Pythia repo.  The script will need to be modified to build the page for the Pythia site, but those changes are minor, such as the output filename and location.  Then add a step to the CI to run this new script when the site is built.)

@clyne I think that we should move the Xdev tutorial content to Pythia. And we can direct people from the Xdev site to Pythia. (Note that moving the page over is easy. You just have to copy the cli/mktuts.py script from the Xdev repo into the Pythia repo. The script will need to be modified to build the page for the Pythia site, but those changes are minor, such as the output filename and location. Then add a step to the CI to run this new script when the site is built.)

Sounds good to me. Probably something someone from XDev will need to handle.

I support this too! Seems Important to me that each of the buttons on the Pythia landing page purporting to lead users to Pythia content should point to Pythia-branded pages. Otherwise great confusion will ensue.

This is harder than I expected. Because the resource gallery filtering is done with Javascript, I'm not sure how to link to a version of the gallery with affiliation=Pythia checked.
Does anyone know how to do this?

This issue should be retitled to be more specific about using gallery tags in URLs, which is still a problem we'd like to have a solution for.


Add scroll margins

Changes

Made it so that we can define inside margins for scroll, meaning that the lib would start scrolling before the mouse surpasses the very edges of the container;

Motivation

I wanted to use it in a rich text editor, the vertical edge of which reached the very bottom of the page, and when I'd put my mouse at the very bottom the container won't scroll. Created this PR to make the user experience more comfortable for bigger containers.

Sorry for the late reply, I'll give it a review tonight!

@Simonwep fixed everything, you can check now! :)

I just rebased it and squashed the first 3 commits since they're basically "fixes" for themselves ^^

Thank you for this feature 🎉 Have a nice weekend ^^

Awesome, thanks have a great weekend you too 🚀🚀🚀

Hey, @Simonwep can this be released? Need it in my project :)

@MaxChu23 Sorry, will do tomorrow!

Thanks a lot!!!

v3.0.0-beta.10 is released :)


cfn-signal.service and set-aws-environment.service failed

With https://github.com/coreos/kube-aws/commit/9e618c93d723a6d02adb181635401e1f946a14dd, a node pool with a autoscaling group containing a single EC2 instance failed like:
REATE_FAILED AWS::CloudFormation::Stack kubeawstest1-fleet2 The following resource(s) failed to create: [AutoScaleWorker].
CREATE_FAILED AWS::AutoScaling::AutoScalingGroup AutoScaleWorker Received 0 SUCCESS signal(s) out of 1.  Unable to satisfy 100% MinSuccessfulInstancesPercent requirement

It seems to be caused by failures in cfn-signal.service and set-aws-environment.service:
CoreOS stable (1185.5.0)
Update Strategy: No Reboots
Failed Units: 2
  cfn-signal.service
  set-aws-environment.service

Full log from each service can be seen at:
https://gist.github.com/mumoshu/462fa1a599fea7ad3f3e82442a8c110c

I believe this is just an reliability issue as this is my first time failures like these are observed.

Both services seem to had failed because of the same error from awscli:
awscli[5]: ValidationError: Instance i-04055b663990f541f in not a member of stack arn:aws:cloudformation:ap-northeast-1:<account-id>:stack/<cluster-name>/93284620-c1cf-11e6-95bc-50d5ca9ff4ae

set-aws-environment.service for node pool is sending signals to the wrong CloudFormation stack!
{{.AWSCliImageRepo}}:{{.AWSCliTag}} -- cfn-init -v \
              --region {{.Region}} \
              --resource LaunchConfigurationWorker \
              --stack {{.ClusterName}}

It should send signals to {{.NodePoolName}} rather than {{.ClusterName}} for a node pool.

So, I had been confused among:

ClusterName: kube-aws/kubernetes cluster name
NodePoolName: kube-aws node pool name
stack name (no dedicated field in theConfig` struct)

Not very sure why this issue had not caused failures in these services consistently but anyways I'm going to fix this shortly.

It turns out that this case had been accidentally missing from our E2E test therefore this is not an reliability issue but rather an functional issue.


Chatterino closes immediately upon launching

I am on Windows 10 and I tried installing Chatterino 2.3.0. and the set-up was done succesfully, but whenever I try opening it, it just closes immediately.
I have tried opening it on another user account with the same role as the account I need it to work on, and it did stay open there, but it does not do so on my account. Trying to launch it as administrator did not work. Nor did reinstalling the program. I do not get a crash log, and the program seems to work for a second but then it's just gone.
When opening it with task manager open I saw that the entire program just shut down immediately, but it didn't use much any weird amount of CPU power beforehand or anything unexpected. I am genuinely at a loss.

My problem is similar, it doesn't close when I open it normally, but I have it attached to my browser and anytime I open a stream it closes unless I open the chat also in Chatterino in a new tab. So I can only use Chatterino in my browser if I open the chat seperately on Chatterino beforehand which is obnoxious...

My problem is similar, it doesn't close when I open it normally, but I have it attached to my browser and anytime I open a stream it closes unless I open the chat also in Chatterino in a new tab. So I can only use Chatterino in my browser if I open the chat seperately on Chatterino beforehand which is obnoxious...

Seconded, i have the exact same issue.

A workaround for this issue right now is adding the stream as an additional tab in main Chatterino window.

Me too -- only crashing on "watching" tab.

Me too -- only crashing on "watching" tab.

That's related more-so to the chatterino extension. There aren't really any plans to fix it.

can you try with nightly?

Works fine on nightly for me @fourtf

can you try the 2.3.1 beta?

There is no released build or I'm blind or you want me to build it myself. Which is it?

@Jagydvon you need to opt-in for beta updates in settings:

Alright did that, "Chatterino 2.3.1 (commit cf33566fd)", and it doesn't crash.

Hi, just noting that I have the same issue with latest stable. Nightly and beta 2.3.1 both seem to work fine.

still getting crashes 2.3.1

@apa420 that didn't work, though i suppose it's a whole other issue - sometimes the crashes happen to me after i switch away from a stream with chatterino in my browser. no crash logs, neither as separate files or in the last channel's logs


TYPE_USE annotations in TYPE_PARAMETER locations [working decision: unrecognized]

We have so far stayed away from allowing annotations in TYPE_PARAMETER positions at all.  In part that's because it's not strictly necessary when only tracking upper bounds, and for @Nullable, it seems a lot clearer what <T extends @Nullable Object> means than <@Nullable T>.
There's also the issue of what happens when both type parameter and bound are annotated.  We don't need to answer that question when disallowing annotations directly on type parameters.  For consistency, and to again sidestep this problem, we've also opted to rule out annotations on a wildcard (?) itself (even though they're considered TYPE_USEs).
By contrast checkerframework assigns a particular "lower bound" semantics to annotating type parameters, which allows defining type parameters that cannot instantiated with @NotNull simply with <@Nullable T>.  I'm not sure how <@NotNull T> is interpreted by checkerframework.  Either way, except with ? super wildcards, lower bounds don't need to be explicitly tracked when type parameters can't be annotated.
On a more technical note, javac makes it a lot harder to keep track of TYPE_PARAMETER annotations than annotations on type parameter bounds (because the latter are (sometimes) propagated into javac's Type objects), so excluding TYPE_PARAMETER technically simplify things a bit.
Note that support for TYPE_PARAMETER can seemingly be added later.  For now disallowing them avoids inconsistencies with how checkerframework (and possibly other tools) would interpret annotations on type parameters.

If we prohibit our annotations before a type parameter or wildcard, then are later convinced it's worth supporting, I think our adding it wouldn't directly break any existing code.
I think that's the plan right now. I'm going to close this for now -- and I think if someone wants to reopen it, it might actually be #85 they want to reopen instead?

Prohibiting annotations before type parameters or wildcards will be very burdensome to users, who will have to write a different @Nullable or @NonNull annotations at different locations in their program -- some of which will have to be fully-qualified since two annotations of the same name cannot be imported.
I don't see the benefit of prohibiting annotations on these locations, especially given the user burden.

Thanks for reopening. Let's separate two questions:

Should this project define semantics for @Nullable used in these positions. This is probably captured as #85 more or less.
If we don't, what happens when users put them there anyway?

This issue seems like a fine place to discuss question 2.
My last comment was confused. I'm sorry about that. Some things are coming back to me more slowly than others.
Suppose we simply state some phrasing of, "This annotation has no defined meaning if it is placed before a type parameter or wildcard". Then I think tools that want to ascribe such meaning at least have a couple options open (possibly not great ones):

They could provide their own @Nullable, marked with @Implies(org.jspecify.nullness.Nullable), and specifying additional semantics. They are only strengthening our contract, not contradicting it (as they might be if we were "prohibiting", again, sorry about that).
They could provide a class/package/module annotation saying some form of, "within the annotated scope, types annotated with org.jspecify.nullness.Nullable have the following additional properties unless marked otherwise..." I think this is legitimate as well.

For the first option, I think you mean that users would use a different annotation throughout their source code, and never use org.jspecify annotations.
Then, neither option forces users to have two different @Nullable annotations in their source code.  That is, both options address my concern.
For the first option, does that require JSpecify to define an @Implies annotation?
For the second option, I don't think an extra annotation is even necessary.  A tool could choose to behave that way always.  But, a tool could define such an annotation if it saw value in doing so.

Oh my, I think maybe we understand each other perfectly here! What is this feeling? :-)
Option 1: yes, I became personally convinced that we are not viable without it. I'll check back on that issue to see if there's been movement.
I did leave out your Option 3, only because I would expect us to discourage it to some degree (to what degree being a more fine-grained debate than we'd benefit from having today). But there may be a smooth continuum between Options 2 and 3 anyway: suppose a tool has a config option to treat code as if it has this annotation on every class. And maybe that option becomes the default. Etc.

I think the status remains as:

Use cases should be argued as use cases on #85 or other appropriate issue
We don't need to prohibit our annotations in these kinds of locations, only declare that they have no usable meaning on their own.

Thinking about the original request for a way to specify a collection of nullable subtype of Foo. Would a generic method like this work, without needing to apply type-use annotations to the type parameter itself?
<T extends Foo> void accept(Collection<@Nullable T> collection);

Probably. I think we'd want to tie this back to a specific use case to see if that satisfies its needs. As far as I know, the use cases that we've seen have been satisfied by various formulations, whether <T extends @Nullable Foo> or Collection<? super @Nullable T> or something else. If we do have other cases, we should probably discuss them in issues like #85 (referenced by kevinb9n above) or #145.

I see that in https://github.com/jspecify/jspecify/issues/85#issuecomment-562255814 you already proposed this idea. Thanks.

Current decision: Java generally doesn't support lower bounds on type parameters or specifying both lower and upper bounds on wildcards, and there isn't a strong enough case to support them. There are other ways to support the use cases for which this is suggested.
Argument for changing: We need a way for methods to accept parameters like collections of Foo into which they can add null. Allowing Collection<@Nullable ? extends Foo> would support that use case, which is otherwise unsupported.
Timing: This must be decided before version 1.0 of the jar.
Proposal for 1.0: Finalize the current decision. If you agree, please add a thumbs-up emoji (👍) to this comment. If you disagree, please add a thumbs-down emoji (👎) to this comment and briefly explain your disagreement. Please only add a thumbs-down if you feel you can make a strong case why this decision will be materially worse for users or tool providers than an alternative.

Does "unrecognized" here mean the same as "meaningless" there?
Possibly allowing the usage on TYPE_PARAMETERs in the future would be preferable to me.

As I just proposed here, I believe we should clarify that only type usages can be nullness-applicable, and a type parameter declaration is not a type usage.
I think (?) we settled on "unrecognized" instead of "meaningless". The idea is that a nullness annotation anywhere that isn't "nullness-applicable" is unrecognized (there are other cases of being unrecognized, too).

@kevinb9n Are you still 👀 on this issue? The working decision is that they are inapplicable/unrecognized, whatever the wording.

Sorry - the issue I linked to got resolved, so removing eyes.

Decision: JSpecify type use annotations (@Nullable and @NonNull) are inapplicable to type parameters (for example ~class Foo<@Nullable T>~).


fix for mongoid 5.0.0

Thanks for this! From a quick look all changes look good, though I haven't worked with Mongoid in many years.
Some questions:

Do all tests pass? (GitHub is reporting failures with Travis, but I don't recall setting it up, so I'm confused)
This seems to include #1. Would it make sense to integrate #2 as well?

Oh Sorry, I forgot this pr.


Latest Kusama updates broke the api server.

I'm seeing the following errors trying to start the API server.
2021-06-08 22:15:30        REGISTRY: Unable to resolve type MessageId, it will fail on construction
2021-06-08 22:15:31        API/INIT: RPC methods not decorated: state_getChildReadProof
2021-06-08 22:15:31        API/INIT: Error: FATAL: Unable to initialize the API: Unable to find closing matching <> on '(Vec<ProxyDefinition,BalanceOf)' (start 5)
at EventEmitter.value (/opt/polkadot_api_server/node_modules/@polkadot/api/base/Init.cjs:91:25)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
2021-06-08 22:15:31        API/INIT: Error: Unable to find closing matching <> on '(Vec<ProxyDefinition,BalanceOf)' (start 5)

Hi @bjweaver , this issue should be resolved with the new update.


False error after project files delete, create

When using an extension to delete/create new project files sometimes false errors appear.
One of them could be fixed #227
Another one is this:

This tag could not be resolved to an ActionScript class. It will be ignored.
This tag could not be resolved to an ActionScript class. It will be ignored.

Complete message:

{
"resource": "/c:/dev/vsc-extensions/test5/src/MyApp.mxml",
"owner": "generated_diagnostic_collection_name#0",
"code": "1450",
"severity": 8,
"message": "This tag could not be resolved to an ActionScript class. It will be ignored.",
"startLineNumber": 2,
"startColumn": 1,
"endLineNumber": 2,
"endColumn": 23
}

It is false error. Debug works. Error(s) disappear on folder close then open.
In this example code is:
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
   xmlns:s="library://ns.adobe.com/flex/spark"
   xmlns:mx="library://ns.adobe.com/flex/mx">

</s:Application>

One note is if you add XX after <s:Application error changes into:
<s:WindowedAppXXlication ...
but there is only Application tag. Not sure, but it could be that the just deleted project files main app was using WindowedApplication.
Animation:

Another error (while creating project files programmatically) is when error is reported in a file that was deleted on disk.
So it looks like the extension keeps project files indexed somewhere that don't get cleaned when deleted?
Note: In every "create project" process, the last written file is asconfig.json as I thought it could be the reason as it might try read some files that are not yet written, but it didn't help me resolve this rare false errors.

Are you using v0.12?

Nevermind. It doesn't matter. I'm actually working on this issue right now:

So it looks like the extension keeps project files indexed somewhere that don't get cleaned when deleted?

Are you using v0.12?
I am using latest version, few hours ago I downloaded and compiled, and using vsix.

Just so you know, I consider the latest code from Github to be very unstable right now. The refactoring for multi-root workspaces is changing things all over the codebase, and I'm still in the middle of the process.

Thanks for info. Anyway, my plan is to wait for v0.13. For fixed issues, and also because of multi-root workspaces as it enables me to add same support for 'create project' command (choose folder within workspace folders to create project into instead of use first folder).

This particular issue should be fixed now, so I'm closing. Deleted files were not properly cleared from memory, but now they should be.


Framework package to link against?

(Coming from .Net background, not sure if this is common for driver development)
Seeing that C++/WinRT is distributed as a NuGet package now, I'm wondering whether DMF could be released as a (NuGet) package as well?
Meaning - a packaged version of a compiled version together with the required headers?
Advantages for developers would be a easier consumption, a cleaner project repository and clear dependency management.

We will discuss internally and get back to you. Thank you for your suggestion. (Internally, we use Nuget packages for our own private DMF in our build system.)

Thank you!

I was wondering whether you’ve had the chance of discussing this, and what the outcome was?
(I can imagine that even if your colleagues approved it could still require effort since currently it is used for internal builds that probably need to stay separated?)

Hi Sam,
could you say something about the state of this issue?

Hi, Hans,
We have not had a chance to address this issue directly. However, it is on our list. We have been using Nuget internally with DMF and other libraries. There will not be any progress on this issue from our end for at least another couple of months due to our schedules. For this reason, this issue remains open.
We have discussed this issue and we plan to work on it. Our solution needs to work seamlessly in our organization which is very large and has many consumers including our build organization.

Thank you for making this clear!

Hi, Hans, we are still working on this task but making progress. Just fyi...

Not a 100% what you're after but I created a little helper to make DMF inclusion a breeze!

Hi nefarius,
Do you think we should include your file in the Dmf directory and and update the documentation to include what you wrote?
We could update all the sample drivers to use the .props file.
If you would like to create a PR with that it would be great. Or, I can do it.
I need to try it out myself, but I think what you did is simpler than the legacy manner in which the samples include DMF now.

Do you think we should include your file in the Dmf directory and and update the documentation to include what you wrote?
We could update all the sample drivers to use the .props file.

Sure, if it makes life easier for everyone!

If you would like to create a PR with that it would be great. Or, I can do it.
I need to try it out myself, but I think what you did is simpler than the legacy manner in which the samples include DMF now.

I'll try to migrate the samples in my fork and when successful will gladly provide a PR. Whoever makes it first 😉

Let put the Dmf.Props file next to the DmfVersion.h file. Then, lets update the documentation "Special Topics" section with the text you wrote. Does that sound good? I can do it if you like. I just don't want to do it if you started it.

Sounds good! No I haven't started any work on this yet.

There is a PR pending to resolve this issue: https://github.com/microsoft/DMF/pull/210
Samples have been updated to illustrate the use of this method. Documentation has also been updated. Thank you, nefarius for the suggestion.
Release v1.1.119 will have this change.

Master has the update. Next month it will be in Release v1.1.19.


Aligning with UTransport::register_listener() and UTransport::unregister_listener() with UListener (this time using generics)

Hey there :wave:
Based on #65, I took my (second) shot at aligning our UTransport trait closer to the spec.
In particular, I have removed the requirement for the implementation to explicitly manage listeners using String identifiers, instead leaning on concrete implementations of the UListener trait.
This change is to align with registerListener() and unregisterListener() by bringing in a UListener trait.
As you read the code, you can see that there was a need for a new wrapper type called ListenerWrapper around UListener in order to allow us to disambiguate between concrete impls of it. The wrapper is also hashable to make it easy to use within containers that require that such as HashSet and HashMap. The ListenerWrapper need only be used in the up-client-foo-rust implementation. uEs just impl UListener.
Largely resolves the issues I had with the first attempt over in #67 thanks to that wrapper type.
Note: Over in a PR onto the up-client-zenoh-rust repo, I'm working on fleshing out how the changes will effect a up-client-foo-rust implementation, to get a feel for if this is a reasonable approach. This is now out of date, see #69 for details
I'm looking to see how this would impact current and future implementations of UTransport for UPClients. Feedback would be great from @AnotherDaniel, @sophokles73, @evshary in particular :slightly_smiling_face:

Closing in favor of #69, where we use the same semantics as up-client-android-java of using reference equality of UListener instances instead of type equality as we were in this approach.


ScrollBar does not look/work properly (regression)

Operating system or device - Godot version:
Xubuntu 14.04 64-bit, compiled myself Godot 2.1.2 & templates.
Issue description:
I noticed the problem with ScrollBars in my android app when edited and exported from 2.1.2.  For no reason at all ScrollBars - when clicked on - drop to the value of 0 and the grabber part does not react to any clicking, dragging, moving etc. to change the value. It remains at 0 value no matter what. :(
App exported from 2.1 had no such problems and ScrollBars worked properly.
Trying to recreate the bug in newly created project (attached in this issue) I was not able to recreate exact behavior, but I found other, similar, but I guess related problem.
Check the attached project or take the steps below:
*When opening the project, notice that the left ScrollBar is just a dot in the upper left corner. I saved the project with it having the same parameters/values/look as the right ScrollBar.
Steps to reproduce:
Create ScrollContainer. Add a VScrollBar child to it. Set VScrollBar's position, size and/or rotation (or use the attached project).
Run the project. No matter of previous settings VScrollBar will be just a dot of size(12,12) in position (0, 0) and probably other parameters changed (default settings?)
Also:
You may change the settings of the VScrollBar and save the project. Then quit to the Project List and load the project again. You will see reset values of size, position etc.
I was not able to reproduce "zeroing" effect after clicking, but I guess this strange behavior is probably connected to the problems I found in my app.
Link to minimal example project:
scroller_test.zip

I can reproduce it on editor with 2.2 alpha.

created new project
make 2d node
zoom out a little bit
quit to project manager
open project again

no vertical scroll bar, horizontal scroll bar is just dot.

@volzhs i can also reproduce this behavior by just zooming out and then zoom in again one step at a time. By doing this the vertical scrollbar becomes a little dot, and the horizontal scrollbar jumps to the top of the window.

I was wondering about this, but never reproduced it.  I even clicked on the little dot once, it was as if it were daring me to do so, and got all sorts of buggy scrolling behavior until I relaunched Godot.

Thanks @volzhs @Keetz for the confirmation.
In checked again and can confirm that in version 2.1-stable scrolling works and looks properly.

Search for the "scroll" keyword in the changelog 2.1.1-stable, there are various potential culprits :) http://download.tuxfamily.org/godotengine/2.1.1/Godot_v2.1.1-stable_changelog.txt

I have a suspicious commit. I will look into it.

What I found is not about ScrollContainer or ScrollBar.
It's about weird scrollbar on 2D editor viewport.
I will make PR for it, but I guess it does not fix main issue.

From a simple search of the document given by @akien-mga I see two positions that could change something with ScrollBar behavior:

Elia Argentieri (1):
Make the step property useful for sliders as described in #5773
Mason Ashbridge (1):
Slider value accounts for grabber offset

@freemanfromgodotengine I can reproduce your issue with your sample project with 2.1 stable also.
no matter what position/size in editor is gone and be shown as dot size when run.

I don't know if this is related, but there is also weird behavior for horizontal scroll bars in code editor.
If you try to drag and drop a resource such as script/scene to the code editor to get the NodePath for say preload, if the path is too long, then it will be pasted correctly, but without horizontal bar. You have to add tabs/spaces manually for another line to see the text for the path.

@RebelliousX I think it would be somewhere in the codepath that handles the drag and drop of the resource.

@bojidar-bg I skipped 1 week of godot's updates, but for v2.1.2 I can't reproduce the issue. :/ I am glad though.
SInce this is fixed in ad899a0dd974a58674882cefe62ac0914fdd4a6e, why it is still open?

@RebelliousX Since it wasn't merged into master from what I could see. :smiley:

I edited  tools/editor/plugins/canvas_item_editor_plugin.h  according to https://github.com/godotengine/godot/commit/ad899a0dd974a58674882cefe62ac0914fdd4a6e and compiled Godot 2.1.2 from scratch. The problem I described previously remains.
Whenever I click on VSlider the value drops to 0 and the grabber stays there no matter what.
It looks like this in my app:

Nothing changed in my code or nodes settings, so I guess problem is not in my code.

The problem is still present in binary version 2.1_20170319 that were given in "Preparing for 2.1.3-stable" #8087 by @akien-mga

Just to be sure, is the problem fixed in master, or does it affect both branches similarly?

The problem is still present in a few day old v3.0.alpha.custom_build I compiled from master.
Faulty behavior is exactly the same in both versions.
I attache version 3 compatible project here:
scroller_bug_in_v3.0_test.zip
Again (and to make clear), the project I', saving and attaching looks like this:

Right scrollbar is outside of the ScrollContainer and behaves as expected.
Left scrollbar is inside the ScrollContainer and has a bug.
If project is run, it look like this (notice small dot in the upper left corner - that's the left  scrollbar):

When saved and opened again, it opens like this (even if save it with both scrollbars looking ok, like in the first picture):

Just checked again with master, and it's still there.
I also found #4954 that clearly is the same or related issue.

I checked today again. This problem still remains on Godot 3.0 alpha compiled from master yesterday.

All scrollbar logic is in the same place in Godot:
https://github.com/godotengine/godot/blob/master/scene/gui/scroll_bar.cpp
And the Range logic is here:
https://github.com/godotengine/godot/blob/master/scene/gui/range.cpp

Ok.. so what is this about? Is this about the VSlider issue or the ScrollContainer?
The VSlider issue seems fixed for me...
The ScrollContainer part is not really an issue as I understood (see #5942).
That's not how ScrollContainer should be used imho... in a scroll container should be a panel or something (with defined min size!) and the scroll container will do the rest, so you have a nice scroll bar, if needed.
If you anyway want to do that setup as described, you still would have to set min size - this is by design.

Please correct me if I get anything wrong.

The issue is simple. Just put VSlider in the ScrollContainer and VSlider stops working properly. Which one is wrong I don't know. Something seams to affect VSlider when it's put into the ScrollContainer.

...in a scroll container should be a panel or something

Yes, for example TextLabel with as many letter as you need that are off the screen (that's in my setup and working on 2.1 versions of Godot), but the problem is not about that. The problem is that VSlider does not keep the size, that you set and turns into 1 pixel dot.

Still there's no issue for me if I have a VSlider VScrollbar in a ScrollContainer and set min size!

+

->

@fodinabor  Which version of Godot is it?

Screenshots are from 2.1.4, same in current 3.0 though..
using your example project I just added min size and it's fine.

hmmm... I have to try that. But still, if you use VSlider out of the ScrollContainer you don't have to set the Min Size, for it to keep the set size, so at least it's inconsequent behavior.

On a newly build master 3.0, after setting Min Size, the size of the VSlider that is in the ScrollContainer is kept. However, it's position is not. VSlider inside the ScrollContainer is always relocated to 0,0 position.
The same happens when you relocate VSlider node in the Scene tree menu, and put it as a child of ScrollContainer. No matter of what is it's position, it changes to 0,0.
I don't think it's normal.

I checked today. The same happens on 2.1.4-stable.

In Godot, Containers are responsible for rearranging/resizing their children, and changing the position or size of those children directly is not supported.
As mentioned in another issue (which I can't find right now..), we might, one day, remove the ability to drag controls inside a container, and make resizing them change their min size instead.
Returning to this issue, I would suggest putting some other container (for example, an HBoxContainer) inside the ScrollContainer setting up a min size on the VScrolls (in case you want them to be that wide), and playing around with their "Size flags". That way, you would be able to tell the engine how you want them to arranged.
Another option might be to put a wrapper control node with min size equal to the area you want to be able to scroll through, and then just put the scrollbars inside it.

Yes, this behaviour is normal now, in the past, and probably in the future 😃

@bojidar-bg I still can't wrap my head around this issue. If like you say "Containers are responsible for rearranging/resizing their children", then why in my example Container rearranges and resizes only some of the children? Is there a reason that Sprite node does not get resized?

@freemanfromgodotengine Control nodes are only responsible for Control nodes, they can't manipulate Node2D's or other nodes.
Control nodes are meant for UI stuff, and the whole rearranging/resizing is actually pretty usefull in my opinion,  i have created some nice  responsible UI pretty easy because of it.

@Keetz @bojidar-bg I really appreciate your effort to explain to me what's going on. Thanks.
However I still think, that behavior of nodes of the saved scene when they rearrange into 0.0 position or rescale to 1,1 when edited or loaded into editor is a bug. Most users expect, that when they save something in some position or scale, it should be saved in such state and stay like that after loading again. They also do not expect that after normal operation of rearranging nodes in the scene's tree, some other nodes will be rearranged into 0,0 position or scale 1,1.
Current behavior is very unintuitive, misleading and inconsistent.
If the only solution is - like @nojidar-bg suggested -

"putting some other container (for example, an HBoxContainer) inside the ScrollContainer"

, then I propose editor to prevent users from placing any other kind of nodes as a child of ScrollContainer. At least some warning should be given, that position of children nor their scale will not be kept after saving etc..

@groud Were we not thinking of disabling gizmo editing for controls that are children of a container?

Closing as superseded by #20750


don't allocate vgpr in globalWriteBatch

globalWriteBatch will allocate most of vgpr in order to do batch write.
So allocate vgpr in globalWriteBatch is easily to met vpgr overflow.
We should allocate all needed vgpr outside of globalWriteBatch.

Can we have a check to disallow checkouts of vgprs during store, in case someone in the future doesn't know what kind of trap he'll walk into?

Can we have a check to disallow checkouts of vgprs during store, in case someone in the future doesn't know what kind of trap he'll walk i

Can we have a check to disallow checkouts of vgprs during store, in case someone in the future doesn't know what kind of trap he'll walk into?

not in this PR.

@TonyYHsieh please resolve the source conflict.  Thanks.


hardware watchdog

https://raspberrypi.stackexchange.com/questions/99584/rpi-freezes-every-now-and-then-how-to-fix-it-with-a-watchdog
https://diode.io/raspberry pi/running-forever-with-the-raspberry-pi-hardware-watchdog-20202/

#410

This was acting strangely, and I feel would cause a lot of confusion.


Output variables occassionally are not provided in the autocompletion

Describe the Bug

Under some circumstances, which are not clearly reproducible, output variables are not suggested in the autocompletion.
Steps to Reproduce

See video:
https://user-images.githubusercontent.com/56470362/194881389-164e4599-c959-4cfe-b8dd-556ea6a1c09b.mov
Expected Behavior

All output variables should be available, everywhere (or in allowed contexts)
Environment

Camunda Modeler 5.4.1

After switching task flow order, the accessibility of variables must be updated based on how tokens can flow.

We cannot decide such thing / it can generally not be decided "in which direction the token flows". Cf. also inability to decide when inclusive gateway joins.

I can not reproduce this on my Mac. In the screencast, the bar variable of Task 2 is an input variable. When you try to access that in an expression, it won't be visible as only output variables are extracted from the diagram.

As @nikku already stated, the order shouldn't matter at all.

@pinussilvestrus my example was dumb. I had a case before with output variables, and tried to reproduce it. Actually, the problem is something else: sometimes, variables are not suggested, and I tried to find a pattern, why.
See this:
https://user-images.githubusercontent.com/56470362/194881389-164e4599-c959-4cfe-b8dd-556ea6a1c09b.mov
I'll update the issue title and description

Hi @christian-konrad ,
from looking at the screen cast, the issue is that some is already an internal keyword, as shown by the different Highlight. We only add Suggestions when the node is of type "VariableName". This assumption seems to be to strict to cover all use cases
https://github.com/bpmn-io/feel-editor/blob/main/src/autocompletion/variables.js#L35-L38
Additionally, the suggestions are not updated when using backspace. Same as in https://github.com/camunda/camunda-modeler/issues/3218

@marstamm Is this something we want to pick up as part of our current initiative? If not, let's move it to backlog.

Let's move it to backlog for now, as it seems to only happen in very specific edge-cases.
However, I will keep it in mind the next time I touch the variable handling and see if it is easy to fix


⚠ Bofrost.at has degraded performance

In 21df6d4, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1237 ms

Resolved: Bofrost.at performance has improved in 757ada1 after 6 minutes.


fix(menu) Fix exception on menu items clicks

Fixes #

do we have tests there?

do we have tests there?

Added.
Who is authorized to merge this?
@yuval-rikover ?


Cleanup ChromeCasts.get() from previous discoveries

When a discovery completes, the discovered chromecasts are still accessible in the ChromeCasts.get() device list, and this is ok. But if the discovery is run again the device list could contain duplicate items, since the items from the previous discovery could not have expired yet. The code in this pr clears the device list before starting another discovery.

Makes sense. Thank you very much. Merged.

Change set was included in just released version 0.11.1, which will become available today.


[Bug]: Tuono dev crashes once with tuono dynamic

Description
I tested both React.lazy and tuono.dynamic with tuono 0.16.0 as described.
Dynamic component
// DynamicComponent.tsx
import { type JSX } from "react";

export const DynamicComponent = (): JSX.Element => {
	return <>DynamicComponent</>;
};

export default DynamicComponent;

Test 1: React.lazy
// testReactLazy.tsx

import React, { Suspense, type JSX } from "react";

const DynamicComponent = React.lazy(() => import("../components/DynamicComponent"));

const LoadingComponent = (): JSX.Element => {
	console.log("Loading");
	return <>Loading</>;
};

export default function IndexPage(): JSX.Element | null {
	return (
		<Suspense fallback={<LoadingComponent />}>
			<DynamicComponent />
		</Suspense>
	);
}

This approach works with tuono dev, but results in the following client side warning/error logged in console:
Uncaught Error: The server could not finish this Suspense boundary, likely due to an error during server rendering. Switched to client rendering.
Test 2: tuono.dynamic
// testTuonoDynamic.tsx

import { Suspense, type JSX } from "react";
import { dynamic } from "tuono";

const DynamicComponent: any = dynamic(() => import("../components/DynamicComponent"));

const LoadingComponent = (): JSX.Element => {
	console.log("Loading");
	return <>Loading</>;
};

export default function IndexPage(): JSX.Element | null {
	return (
		<Suspense fallback={<LoadingComponent />}>
			<DynamicComponent />
		</Suspense>
	);
}

This approach crashes tuono dev when starting the server, but after resetting it works, however with the same client side warning/error logged in console:
Uncaught Error: The server could not finish this Suspense boundary, likely due to an error during server rendering. Switched to client rendering.
The following is output by tuono dev upon start:
file:///project/node_modules/tuono-lazy-fn-vite-plugin/dist/esm/index.js:29
      if (init.callee.name === TUONO_DYNAMIC_FN_ID) {
                      ^

[vite-plugin-tuono-lazy-loading] unknown file: Cannot read properties of undefined (reading 'name')
file: /project/src/routes/fresh.tsx
    at file:///project/node_modules/tuono-lazy-fn-vite-plugin/dist/esm/index.js:29:23
    at Array.forEach (<anonymous>)
    at VariableDeclaration (file:///project/node_modules/tuono-lazy-fn-vite-plugin/dist/esm/index.js:27:28)
    at NodePath._call (/project/node_modules/@babel/traverse/lib/path/context.js:49:20)
    at NodePath.call (/project/node_modules/@babel/traverse/lib/path/context.js:39:18)
    at NodePath.visit (/project/node_modules/@babel/traverse/lib/path/context.js:88:31)
    at TraversalContext.visitQueue (/project/node_modules/@babel/traverse/lib/context.js:90:16)
    at TraversalContext.visitMultiple (/project/node_modules/@babel/traverse/lib/context.js:62:17)
    at TraversalContext.visit (/project/node_modules/@babel/traverse/lib/context.js:111:19)
    at traverseNode (/project/node_modules/@babel/traverse/lib/traverse-node.js:22:17)
    at traverse (/project/node_modules/@babel/traverse/lib/index.js:53:34)
    at NodePath.traverse (/project/node_modules/@babel/traverse/lib/path/index.js:120:24)
    at ImportSpecifier (file:///project/node_modules/tuono-lazy-fn-vite-plugin/dist/esm/index.js:50:18)
    at NodePath._call (/project/node_modules/@babel/traverse/lib/path/context.js:49:20)
    at NodePath.call (/project/node_modules/@babel/traverse/lib/path/context.js:39:18)
    at NodePath.visit (/project/node_modules/@babel/traverse/lib/path/context.js:88:31)
    at TraversalContext.visitQueue (/project/node_modules/@babel/traverse/lib/context.js:90:16)
    at TraversalContext.visitMultiple (/project/node_modules/@babel/traverse/lib/context.js:62:17)
    at TraversalContext.visit (/project/node_modules/@babel/traverse/lib/context.js:111:19)
    at traverseNode (/project/node_modules/@babel/traverse/lib/traverse-node.js:22:17)
    at NodePath.visit (/project/node_modules/@babel/traverse/lib/path/context.js:94:52)
    at TraversalContext.visitQueue (/project/node_modules/@babel/traverse/lib/context.js:90:16)
    at TraversalContext.visitMultiple (/project/node_modules/@babel/traverse/lib/context.js:62:17)
    at TraversalContext.visit (/project/node_modules/@babel/traverse/lib/context.js:111:19)
    at traverseNode (/project/node_modules/@babel/traverse/lib/traverse-node.js:22:17)
    at traverse (/project/node_modules/@babel/traverse/lib/index.js:53:34)
    at NodePath.traverse (/project/node_modules/@babel/traverse/lib/path/index.js:120:24)
    at PluginPass.Program (file:///project/node_modules/tuono-lazy-fn-vite-plugin/dist/esm/index.js:47:12)
    at newFn (/project/node_modules/@babel/traverse/lib/visitors.js:172:14)
    at NodePath._call (/project/node_modules/@babel/traverse/lib/path/context.js:49:20)
    at NodePath.call (/project/node_modules/@babel/traverse/lib/path/context.js:39:18)
    at NodePath.visit (/project/node_modules/@babel/traverse/lib/path/context.js:88:31)
    at TraversalContext.visitQueue (/project/node_modules/@babel/traverse/lib/context.js:90:16)
    at TraversalContext.visitSingle (/project/node_modules/@babel/traverse/lib/context.js:66:19)
    at TraversalContext.visit (/project/node_modules/@babel/traverse/lib/context.js:113:19)
    at traverseNode (/project/node_modules/@babel/traverse/lib/traverse-node.js:22:17)
    at traverse (/project/node_modules/@babel/traverse/lib/index.js:53:34)
    at transformFile (/project/node_modules/@babel/core/lib/transformation/index.js:80:31)
    at transformFile.next (<anonymous>)
    at run (/project/node_modules/@babel/core/lib/transformation/index.js:25:12)
    at run.next (<anonymous>)
    at transform (/project/node_modules/@babel/core/lib/transform.js:22:33)
    at transform.next (<anonymous>)
    at evaluateSync (/project/node_modules/gensync/index.js:251:28)
    at sync (/project/node_modules/gensync/index.js:89:14)
    at stopHiding - secret - don't use this - v1 (/project/node_modules/@babel/core/lib/errors/rewrite-stack-trace.js:47:12)
    at Module.transformSync (/project/node_modules/@babel/core/lib/transform.js:42:76)
    at Object.transform (file:///project/node_modules/tuono-lazy-fn-vite-plugin/dist/esm/index.js:63:27)
    at Object.handler (file:///project/node_modules/tuono/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:65683:15)
    at file:///project/node_modules/rollup/dist/es/shared/node-entry.js:20812:40 {
  code: 'PLUGIN_ERROR',
  pluginCode: 'BABEL_TRANSFORM_ERROR',
  plugin: 'vite-plugin-tuono-lazy-loading',
  hook: 'transform',
  id: '/project/src/routes/fresh.tsx',
  watchFiles: [
    '/project/.tuono/server-main.tsx',
    '/project/node_modules/tuono/dist/esm/ssr/index.js',
    '/project/.tuono/routeTree.gen.ts',
    '/project/node_modules/react/jsx-runtime.js',
    '/project/node_modules/fast-text-encoding/text.min.js',
    '/project/node_modules/react-dom/server.browser.js',
    '/project/node_modules/react-helmet-async/lib/index.esm.js',
    '/project/node_modules/tuono-router/dist/esm/index.js',
    '/project/package.json',
    '/project/node_modules/tuono/dist/esm/index.js',
    '/project/src/routes/__root.tsx',
    '/project/src/routes/fresh.tsx'
  ]
}

Node.js v20.17.0

  ⚡ Tuono v0.16.0
  Ready at: http://localhost:3000

  GET /fresh 200 in 32ms
  GET /installHook.js.map 200 in 50ms
  GET /installHook.js.map 200 in 34ms

Expected behaviour

It is expected that no Uncaught Error: The server could not finish this Suspense boundary, likely due to an error during server rendering. Switched to client rendering. warning is shown if possible.
It is expected that tuono dev does not crash when started with tuono.dynamic use.

How to reproduce

Add the described components.
Run tuono dev.

Screenshots
No response
Tuono version
0.16.0
OS
NixOS
Browser
Firefox
Node version
v20.17.0
Rust version
rustc 1.82.0 (f6e511eec 2024-10-15)
Crate version
0.16.0
Node Package Manger version
Yarn 1.22.22
Additional context
Note: It could be helpful to make it clear that lazyLoadComponent is an internal function and should not be used.

Logging here the initial investigation:

Uncaught Error: The server could not finish this Suspense boundary, This error seems to be due to the development react bundler. Still need to find the root cause, but it gets correctly rendered and stripped out on the production build
unknown file: Cannot read properties of undefined (reading 'name') This error appear when dynamic is the only function exported by the tuono library import { dynamic } from 'tuono'. We need to improve the internal vite plugin + adding this test case
lazyLoadComponent should be renamed. I'd propose something like tuono__internal__lazyLoadComponent

Update:

This issue is related to the way we are server side rendering the project. We are addressing this, but it will take longer than expected (you can use suspense, but you will have that log on the console in the development mode).
This is fixed here: https://github.com/tuono-labs/tuono/pull/223
This is fixed here: https://github.com/tuono-labs/tuono/pull/222

The last issue has been fixed with tuono v0.16.5. Please let me know if something still does not work


Foreign key in embedded struct

Hello,
I tried to embed a struct that contained a foreign key, but instead a getting a foreign key, the model got a jsonb field. For example, this code would trigger this problem :
type SoftDeleteMixin struct {
	Deleted   bool
	DeletedAt *time.Time
	DeletedBy *User `fk:"user_id,inverse"`
}

type Subject struct {
	kallax.Model `table:"subjects" pk:"id"`
	kallax.Timestamps
	SoftDeleteMixin

	[...]
}

Which results in this code being generated:
CREATE TABLE subjects (
	created_at timestamptz NOT NULL,
	updated_at timestamptz NOT NULL,
	deleted boolean NOT NULL,
	deleted_at timestamptz,
	deleted_by jsonb
);

Do you have an idea of what's happening here ?
Thank you,
Benjamin

Is the User model being recognized and used by kallax?


problem with facebook javascript sdk

I try to develop facebook app with coffeescript, and I got problem in the following.
The error is         Uncaught TypeError: Object [object DOMWindow] has no method 'fbAsyncInit'
This is my code below.
    window.fbAsyncInit ->
        FB.init({
            appId: 'APP_ID',
            status: true,
            cookie: true,
            xfbml: true
        })

    ((d) ->
        id= 'facebook-jssdk'
        if d.getElementById(id)
            return
        js = d.createElement('script')
        js.id = id
        js.async = true
        js.src = "//connect.facebook.net/en_US/all.js"
        d.getElementByTagName('head')[0].appendChild(js)
    )(document)

Well obviously window has no method fbAsyncInit. Did you not include the script that adds it? This appears to have nothing to do with CoffeeScript, so closing for now.

You have a function -> instead of an = and therefore trying to call window.fbAsyncInit instead of defining it. The Facebook js library will call window.fbAsyncInit when it is first initialized.

Thank you both.
I got my fail.


websocket_message_count  vs api_message_count - any idea what the difference is?

Hi All!
Any idea what the difference is between these two stats? I'm showing websocket message count as quite a bit higher, even at idle times but no idea what it means.

this is my question too
what the difference is between websocket_message_count and api_message_count
when we broadcast a message to users of the columns will be updated ?


Autoinstaller: Error when updating/downloading blockchain

Description
When updating/downloading blockchain with the auto-installer: receiving "Installing / Updating The BlockChain (This Might Take a While)rm: cannot remove 'xcash-blockchain.7z*': No such file or directory", then the auto-installer closes.
Fixes # (issue)
added lines to ignore if the command 'rm' throws errors
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Ran updated autoinstaller.sh. No errors given
Test Configuration:

Firmware version:
Hardware:

Checklist:

[ X ] My code follows the style guidelines of this project
[ X ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ X ] My changes generate no new warnings
[ X ] I have added tests that prove my fix is effective or that my feature works
[ X ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Thanks @element0355 this does seem to happen if the file is not there.


Few Small Bugfixes

Overview
Fixes three bugs:

public datasource filtering
setting export status incorrectly
requesting too many export jobs

Testing Instructions

Start server and log in with a non-root account in a non-default org
Go to filter and look for datasources
Try to export a project - ensure it gets picked up correctly in the airflow ui

I'm going to merge this so this gets deployed -- but I'll address comments if there are any in a subsequent PR


Item is weirdly offset from the grid

Was trying out gridpack until i decided to change up the script a little to be compatible with frames and it made the items follow some weird offset.

Could you please take a screenshot of your hierarchy/explorer and post it here? My best guess right now is that the UIGridLayout's horizontal and vertical alignment is centered.
If you want the grid to scale with the background then set the grid's SlotAspectRatio to nil.

changed alot of things regarding the gui but still facing the same problem.
my grid if it matters
local pocketsGrid = GridPack.createGrid({

	Parent = pocketsInventory,
	Visible = true,

	Assets = {
		Slot = game:GetService("ReplicatedStorage"):WaitForChild("Assets"):WaitForChild("GUI"):WaitForChild("gridCanvasGroup"),
	},

	GridSize = Vector2.new(10, 2),
	SlotAspectRatio = nil,

	AnchorPoint = Vector2.new(0,0),
	Position = UDim2.new(0,0),
	Size = UDim2.fromScale(1,1),
})

gridinventory.zip
i dumbed down the hierarchy a tad bit so its less clutter for you

I think I've found the problem! But I don't have time to fix it right now, so expect a fix tomorrow!

thanks!

Now fixed in v0.2.2-alpha!


Can librespot be built on FreeBSD?

I would like to install librespot on my headless FreeBSD machine.
So far i installed all dependencies but running ''cargo build'' results in the following output:
Compiling portaudio_sys v0.1.1 (https://github.com/mvdnes/portaudio-rs#2e163084)
Build failed, waiting for other jobs to finish...
error: failed to run custom build command for `portaudio_sys v0.1.1 (https://github.com/mvdnes/portaudio-rs#2e163084)`
process didn't exit successfully: `/usr/home/snapmaster/librespot/target/debug/build/portaudio_sys-e88d85f0bc483534/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'Failed to run `"pkg-config" "--libs" "--cflags" "portaudio-2.0"`: No such file or directory (os error 2)', /root/.cargo/git/checkouts/portaudio-rs-00e07e26853f2e98/2e1630843551a229bfe6cae6291fd157349bad60/portaudio_sys/build.rs:8
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Has anyone ever built librespot successfully on FreeBSD or has hints for me on how to do this?

the problem seems to be that I didn't have pkg-config installed on my system.
This is done via ''pkg install pkgconf''

@plietar you could add the following lines to your readme to show what is needed for FreeBSD:
pkg install rust cargo protobuff pulesaudio pkgconf


Refactor EventStore and Middleware to Classes

With the addition of Offchain events like ipfs, we now have need for storing different kinds of objects.

SolidityStruct persisted objects where EsEvent.ValueType === 'Object'
IpfsObjects EsEvent.ValueType === 'String', and StringValue === 'ipfs/....'

This means that middleware needs to be aware of user preferences for how objects are stored.
currently the framework is initialized like so:
TransmuteFramework.init({
                env: 'infura',
                esa: eventStoreArtifacts,
                esfa: eventStoreFactoryArtifacts
            })

TransmuteFramework.TransmuteIpfs.init({
                host: 'localhost',
                port: '5001',
                options: {
                    protocol: 'http'
                }
            })

This is problematic. Not all framework consumers will want IPFS.
When reading and writing objects, the objects should contain all information necessary to know where they are stored.
however, when writing a command, that is an object. currently the framework must be set to store objects on IPFS or on chain, but not both.
For the time being I'm assuming objects want to be stored in ipfs.
These configuration concerns need to be addressed, there should be a single init call which defines how the framework will be used. Middleware and whatever else need to be aware of that state.
This means that TypeScript modules need to be replaced with classes.

Here's how this should work:
TransmuteFramework.init({
    env: 'infura',
    esa: eventStoreArtifacts,
    esfa: eventStoreFactoryArtifacts,
    ipfsConfig: {
        host: 'localhost',
        port: '5001',
        options: {
            protocol: 'http'
        }
    }
})

When writing a command:
{
    type: 'IPFS:RECORD:CREATED',
    payload: {
        cool: 'story...bro'
    },
    meta: {
        handlers: ['ipfs']
    }
}

the meta.handlers is used to determine where the offchain data will be stored.
the config at the top level is used to determine how that data will be stored.

This is reasonable, we are going to need to end up providing an additional example for offchain data storage so that people can see how to easily set up something more familiar like Postgresql config in our init function.
I agree with storing the handlers in meta - I think we are going to want to integrate another familiar backend like what I mentioned to be able to show the utilization of multiple handlers in the framework. But I think this is something post pre-alpha.

This is done


Added sanity check for page index when loading pages from broken samples

There are certain samples where page index might go beyond available pages when trying to load them which will be prevented with this patch.

I added proper handling. Also, retdec-fileinfo now reports loader error properly.

LGTM


Loss of test coverage w.r.t. building FSharp.Core

Tracking issue for my comment here: https://github.com/Microsoft/visualfsharp/pull/3230#issuecomment-310028873

The one big thing that concerns me about this is that we have lost some test coverage for the compiler. If we insert a bug that affects the correct compilation of FSHarp.Core.dll, we won't detect it until much, much later when we adopt that compiler as the LKG. That could be after we've shipped the compiler to the world.
This isn't at all unlikely - FSharp.Core uses a number of features of the compiler that nothing else uses.
Could we still build the final FSharp.Core - the one we ship and test - with the proto compiler?
I understand that this change makes the logic of a from-source build easier. But there would be other ways to achieve that, wouldn't there, such as doing this conditionally?

Closing as only `Proto\net40\bin\FSharp.Core.dllis built this way,Release\net40\bin\FSharp.Core.dll`` is still built the same way AFAICS


Version number missing

I can not find a way to see which version of the program that I am running.
I might be blind and there is an obvious way if so please enlighten me.

On macOS you can view it over menu bar > Meta Grabber > About.
Not sure if/how this works on Windows and Linux, though.
I guess I can display the version number in the settings view.


heroku deploy button implementation to the readme

this would make easy and faster installations of journey onto heroku, docs for this action can be found here https://devcenter.heroku.com/articles/heroku-button

Good suggestion!
Do you want to take it on? I don't think I will get around to it until some time next week.

@kabukky sure, I'll get started on this now :+1:

@kabukky well I've started this via my fork of journey, but godoc is needed to be setup via the project for heroku's hosting which isn't hard to implement but time has been kicking me since I've been on vacation


Simplify CI detection

Pulled out of #50597.

Seems like this will make it more painful to run the CI lint rules locally but it also seems like no one cares.

What do you mean? We don't have any rules that are CI specific anymore, so npm run lint is equivalent to npm run lint -- --ci or what was npm run lint:ci. The only thing --ci changes is the reporter used.


feat: add create data attestation credential methods

feat:

add create data attestation credential method
add get credential method
update web-react  example to create and download data attestation credential

@HunnySajid and @rodolfomiranda can you review this?


Adding extra features

Hello @tot-ra ,
I am opening this issue to share the features the teams at @ManoManoTech have been doing in the later months, following issues #123 & #124 so when we started the repository was at the v3 and now it is in v4 and has diverged a lot from what we have now, so we would like to know if it is worth to focus on joining the features or not, so I will explain what we have done.
1 - Schema  Breakdown

In order to know if a breaking change can be allowed there is the need to store the different fields in every query/mutation/subscription so that when there is a push of a new schema this information is broken down into parts.
So there have been created tables starting with  type_def_* and I will explain its relationships.
1 service can contain n operations, defined in type_def_operations with an operation_id
1 operation stored in type_def_operations can have n parameters stored in type_def_operation_parameters .
A parameter can be an input field or the response of the operation, represented with the is_output field 0 means is an input, and 1 is the response type.
In the table, type_def_types is stored the naming and the type ( SCALAR, ENUM, DIRECTIVE, or OBJECT) of all the schemas, and its definition is stored in type_def_fields
So, let’s do an example, with the data of the request to push endpoint with an schema of the brand service:
{
  "name": "brands",
  "version": "latest",
  "type_defs": "\n  schema {\n  query: Query\n}\n\ndirective @extends on INTERFACE | OBJECT\n\ndirective @external on FIELD_DEFINITION | OBJECT\n\ndirective @key(fields: String!) on INTERFACE | OBJECT\n\ndirective @provides(fields: String!) on FIELD_DEFINITION\n\ndirective @requires(fields: String!) on FIELD_DEFINITION\n\ntype Brand @key(fields: \"id\") @key(fields: \"brandId\") @key(fields: \"id\") @key(fields: \"brandId\") {\n  brandId: Int!\n  description: String\n  id: ID!\n  logo: String\n  market: String!\n  platform: String!\n  slug: String!\n  title: String!\n}\n\n\n\n\ntype Query {\n  _entities(representations: [_Any!]!): [_Entity]!\n  _service: _Service!\n  brand(brandId: Int!, market: String!, platform: String!): Brand!\n  brands(brandIds: [Int!]!, market: String!, platform: String!): [Brand!]!\n}\n\nscalar _Any\n\nunion _Entity = Brand\n\ntype _Service {\n  \"\"\"The sdl representing the federated service capabilities. Includes federation directives, removes federation types, and includes rest of full schema after schema directives have been applied\"\"\"\n  sdl: String\n}\n\n",
  "url": "http://<IP_ADDRESS>:4003/api/graphql/brands"
}

So the values stored in the different tables are:
Services:
idnameis_activeupdated_timeadded_timeurl4brands1NULL2022-09-01 15:00:20http://<IP_ADDRESS>:4003/api/graphql/brands
type_def_operations
idnamedescriptiontypeservice_id1_entitiesNULLQUERY42_serviceNULLQUERY43brandNULLQUERY44brandsNULLQUERY4
type_def_types
idnamedescriptiontype1_AnyNULLSCALAR2IntNULLSCALAR3StringNULLSCALAR4IDNULLSCALAR5extendsNULLDIRECTIVE6externalNULLDIRECTIVE7keyNULLDIRECTIVE8providesNULLDIRECTIVE9requiresNULLDIRECTIVE10BrandNULLOBJECT11_ServiceNULLOBJECT12_EntityNULLOBJECT
type_def_fields
idnamedescriptionis_nullableis_arrayis_array_nullableis_deprecatedparent_type_idchildren_type_id1fieldsNULL0010732fieldsNULL0010833fieldsNULL0010934brandIdNULL00101025descriptionNULL10101036idNULL00101047logoNULL10101038marketNULL00101039platformNULL001010310slugNULL001010311titleNULL001010312sdlThe sdl representing the federated service capabilities. Includes federation directives, removes federation types, and includes rest of full schema after schema directives have been applied1010113
This will be reflected in the UI like this

If someone wants to know what is the "contract" of the query brands clicking on it can be seen the definition of it:

To give some numbers, we have in our organization around 30 queries and 60 objects provided by 14 subgraphs and this number is going to increase in the coming months
2 - Client awareness
The objective of this feature is to have information in the UI about who ( client & version ) is using a query or an object in the super-graph.
The architecture is summarized in this schema

Apollo Gateway receives all the requests the clients perform and there is a plugin from Apollo that is called usage reporting plugin, this plugin will take all the requests within a period of time and when this time comes or the data is larger than the configured value, it is sent to the schema registry to the /api/ingress/traces endpoint.
So as you can see there is no custom gateway needed as this is plugged with the already available tools from Apollo.
When the Usage reporting gets to the schema registry and is decoded the payload is something similar to:
{
  "header": {
    "hostname": "host-name",
    "agentVersion"<EMAIL_ADDRESS>    "runtimeVersion": "node v14.18.3",
    "uname": "darwin, Darwin, 21.2.0, x64)",
    "executableSchemaId": "1",
    "graphRef": "current"
  },
  "endTime": {
    "seconds": "1644511107",
    "nanos": 397000000
  },
  "tracesPerQuery": {
    "# homeBrands\nfragment HomeBrands on Brand{__typename brandId id logo title}query homeBrands($platform:Platform!){homepageB2cBrands(platform:$platform){__typename...HomeBrands}}": {
      "trace": [
        {
          "endTime": {
            "seconds": "1644511102",
            "nanos": 737000000
          },
          "startTime": {
            "seconds": "1644511102",
            "nanos": 690000000
          },
          "details": {
            "variablesJson": {
              "platform": ""
            }
          },
          "clientName": "test-gateway-client",
          "clientVersion": "0.0.1",
          "http": {
            "method": "GET"
          },
          "durationNs": "46907164",
          "root": {
            "error": [
              {
                "message": "request to http://<IP_ADDRESS>:4002/api/graphql failed, reason: connect ECONNREFUSED <IP_ADDRESS>:4002",
                "json": "{\"message\":\"request to http://<IP_ADDRESS>:4002/api/graphql failed, reason: connect ECONNREFUSED <IP_ADDRESS>:4002\",\"type\":\"system\",\"errno\":\"ECONNREFUSED\",\"code\":\"ECONNREFUSED\"}"
              }
            ]
          },
          "fullQueryCacheHit": false,
          "registeredOperation": false,
          "forbiddenOperation": false,
          "queryPlan": {
            "sequence": {
              "nodes": [
                {
                  "fetch": {
                    "serviceName": "graphql",
                    "sentTimeOffset": "13365436",
                    "sentTime": {
                      "seconds": "1644511102",
                      "nanos": 703000000
                    }
                  }
                },
                {
                  "flatten": {
                    "responsePath": [
                      {
                        "fieldName": "brands"
                      },
                      {
                        "fieldName": "@"
                      }
                    ],
                    "node": {}
                  }
                }
              ]
            }
          },
          "fieldExecutionWeight": 1
        }
      ],
      "referencedFieldsByType": {
        "Brand": {
          "fieldNames": [
            "id",
            "brandId",
            "title",
            "logo",
            "__typename"
          ],
          "isInterface": false
        },
        "Query": {
          "fieldNames": [
            "brands"
          ],
          "isInterface": false
        }
      }
    }
  }
}

As you can see here there is all the information we need to do the client tracking:
"clientName": "test-gateway-client",
"clientVersion": "0.0.1",
and also the query performed.
when the request is received the schema registry performs these actions:

Check if the client and the version exist on the database
Calculate a hash with the query performed
Calculate the Redis key ( this key is grouped by )

client id
hash of the query
timestamp ( by hour )

So if there is a key in the Redis store we do an increment of the operations and the errors accordingly to the message received.
The UI looks this way when the stats button is clicked:

At scale level if the gateway receives 5k requests, there is not done 5k requests to the schema registry it will depend on the configuration of the usage report plugin how it group all the information of those requests.
Right now we have found some bugs and we know that we need to dedicate some time in order to fix the bugs and perform enhances to this feature or else some architectural changes like using Kafka in order to not lose any usage message and prevent the main thread of the schema registry to process all the information.
About the payload we have in the apollo gateway right now in prod it is not too high, 2.5k req / min
3 - Breaking change control
As there is a control to know which data is used by the clients we can control when pushing a new version of the schema of a subgraph if there is some breaking change allow to push this new version only if there are no clients using this data otherwise this request will be rejected.
So finally, if you got to the end of this and there is a lot of data to digest, first of all, thank you and then we are very interested in knowing your opinion about putting all this stuff together with what there is in v4 and deciding how to move forward. If following this issue is getting too difficult we also propose to do a meeting in order to get an alignment together.
Thank you very much

Hey. Thanks for the very informative post!
✅ I think the UI part is good and something we do want to reach to get detailed, per-property information
❓ Schemas column in UI is a bit confusing.. as I understand its a link to a service that defines it? Or is it a link to Query.brands? If its a service, I'd name the column accordingly.

❓ What happens if you have brands service, but images service for example extends type Brand? You'll need to show multiple services linked to the type in UI in schemas column? Or is it going to be  under specific Brand.url property?

called usage reporting plugin, this plugin will take all the requests within a period of time and when this time comes or the data is larger than the configured value, it is sent to the schema registry to the /api/ingress/traces endpoint

Regarding architecture, I understand that this plugin seems useful and in small projects its simple to integrate. But putting it into the gateway seems like a risky move to me, because :
⚠  if it makes sync requests for every operation, then it can overload schema-registry/db, making it more like real-time service that we don't particularly want to do. This can cause service to fail responding to  /schema/compose and  /schema/latest requests which is very bad
⚠  if it does aggregation or sampling (throwing away some queries) before it makes requests to schema-registry, then we won't get sufficiently detailed information about usage
Thats why we're using async query processor - https://github.com/pipedrive/graphql-schema-registry/tree/master/src/worker/analyzeQueries where you can control the load / processing speed yourself. It doesn't have  performance (speed of queries) though ofc. but I think thats a better architecture though somewhat more complex for smaller projects as it needs an event bus (kafka) that would be responsible for storing queries. It can extract client name/version here https://github.com/pipedrive/graphql-schema-registry/blob/master/src/worker/analyzeQueries/index.ts#L77 if its passed down from gateway's headers.
Having said that, I think we can accept your sync solution the plugin into v4 only if UI in the end can show/work with both sync & async datasources. So for the end user, it should be a simple choice:

use your sync approach for small projects (simple, somewhat risky db load)
OR use async approach for bigger projects (more complex setup, less risky)

So I'd ask you to check & change async worker to add/update data in your DB tables too (see examples for the setup) such that you could see usage in your views.

P.S. I wonder how are you going to show in the UI types that migrate from one service to another and tie it to the usage too.


Made pausing a paused queue return a success rather than a failure.

It now matches resume. Apparently I missed a spot :(
@bigcommerce/tools @lord2800

:+1:


Add a class representing selection on FormControlLabel label portion

FormControlLabel the label span will have a "disabled" when the FormControl is disabled but there is no "selected" class if a selection is made. Request that a "selected" class is added to selected (checked) controls. This will allow users to provide better styling of labels when an option is selected.

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Current Behavior

Examples

Context

Our style specs require the selected label in a radio button be colored differently... currently disabled radio buttons can have a different color for label but selected and unselected radio buttons cannot have different colors. We currently achieve this by painfully changing the style class when a selection is made.

I'm closing as it didn't get much traction since last year. Thanks for the discussion.


[question] where is stored instagram fingerpring

Form
Put an [x] if you meet the condition, else leave [ ].

[x] I've searched the Issues
[x] I've read the basic concepts
[x] I'm using the latest version

Question
I would like to mock a real instagram app fingerprint in my project
by fingerprint i mean device_id,  adid  phone_id  uuid does anyone know which file instagram app persist these fields? so i can read it from a real phone (rooted)

Hey @bolds07 did you solve that situation? I'm searching these too.


Color of graph based on value

Is it possible to set the color of the bar/pie based on the value of a field? For example from the data below, set the color to Green if Score >= 95, Orange if  90 <= Score < 95 and Red if Score < 90?
[{
"Date" : "2014-09-01",
"State" : "Alabama",
"StateCode" : "AL",
"Operators" : [{
"Operator" : "CellServiceA",
"Score" : 88.94
}, {
"Operator" : "CellServiceB",
"Score" : 95.71
}, {
"Operator" : "CellServiceC",
"Score" : 95.36
}, {
"Operator" : "CellServiceD",
"Score" : 90.79
}
]
},...
]
I tried something like below, but it applies the same color to all bars.
'Operators[Operator=CellServiceA].Score': {
fillColor: function (value) {
if(value >= 95)
return 'hsl(114,100%,50%)'; // Green
if(value >= 90)
return 'hsl(63,100%,50%)'; // Yellow
else
return 'hsl(0,100%,50%)'; // Red
}
},
'Operators[Operator=CellServiceA].Score': {
fillColor: function (value) {
if(value >= 95)
return 'hsl(114,100%,50%)'; // Green
if(value >= 90)
return 'hsl(63,100%,50%)'; // Yellow
else
return 'hsl(0,100%,50%)'; // Red
}
},

I needed the same functionality, So i started to extend the L.BarchartDataLayer and override the _getMarkerMethod, but there is an issue. In the L.ChartDatalyer and L.BarChartDataLayer the _getMarkerMethod override removes the record parameter. In the ChartDataLayer the _getLayer method calls the _getMarkerMethod but with out the record parameter even though the record object is passed into the _getLayer Method..
It would be very helpful to add the record parameter back into the _getMarkerMethod of the ChartDataLayer and BarChartDataLayer
The code i was looking at is in the 1.0Dev branch.
Thanks
Rick Jones

Good point.  Thanks for pointing this out.  The latest code should have this change in it.

Thanks for responding so quickly.


Update/Upgrade not possible

brew config output
HOMEBREW_VERSION: >=2.5.0 (shallow or no git repository)
ORIGIN: (none)
HEAD: (none)
Last commit: never
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 337c9a0832b6a7c4f714957ea958e36f8b7ebfe6
Core tap last commit: 14 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 10
Homebrew Ruby: 2.6.8 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: 10-core 64-bit arm_firestorm_icestorm
Clang: 13.1.6 build 1316
Git: 2.32.1 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 7.79.1 => /usr/bin/curl
macOS: 12.5-arm64
CLT: <IP_ADDRESS>.1.1651278267
Xcode: N/A
Rosetta 2: false

brew doctor output
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Missing https://github.com/Homebrew/brew git origin remote.

Without a correctly configured origin, Homebrew won't update
properly. You can solve this by adding the remote:
  git -C "/opt/homebrew" remote add origin https://github.com/Homebrew/brew

Verification

[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
Wanted to upgrade outdated installations
What happened (include all command output)?
cka@/Users/wrks> brew upgrade
Warning: No remote 'origin' in /opt/homebrew, skipping update!
==> Homebrew has enabled anonymous aggregate formula and cask analytics.
Read the analytics documentation (and how to opt-out) here:
https://docs.brew.sh/Analytics
No analytics have been recorded yet (nor will be during this brew run).
fatal: not in a git directory
Error: Command failed with exit 128: git
==> Upgrading 26 outdated packages:
rubberband 2.0.2 -> 3.0.0
libtiff 4.4.0 -> 4.4.0_1
ffmpeg 5.0.1_2 -> 5.1
libidn2 2.3.2 -> 2.3.3
little-cms2 2.13.1 -> 2.13.1_1
nettle 3.8 -> 3.8.1
speex 1.2.0 -> 1.2.1
harfbuzz 4.3.0 -> 5.0.1
glib 2.72.2 -> 2.72.3
mbedtls 3.1.0 -> 3.2.1
srt 1.4.4 -> 1.5.0
tesseract 5.1.0 -> 5.2.0
webp 1.2.2 -> 1.2.3_1
sqlite 3.38.5 -> 3.39.2
xz 5.2.5 -> 5.2.5_1
libnghttp2 1.47.0 -> 1.48.0
libvpx 1.11.0 -> 1.12.0
librist 0.2.7 -> 0.2.7_1
ca-certificates 2022-04-26 -> 2022-07-19_1
isl 0.24 -> 0.25
btop 1.2.7 -> 1.2.8_1
leptonica 1.82.0 -> 1.82.0_1
jpeg-xl 0.6.1 -> 0.6.1_1
unbound 1.16.0 -> 1.16.1
fzf 0.30.0 -> 0.31.0
gnutls 3.7.6 -> 3.7.7
Error: snappy: undefined method `<=' for nil:NilClass
What did you expect to happen?
Installations to be updated.
Step-by-step reproduction instructions (by running brew commands)
cka@/Users/wrks> git -C "/opt/homebrew" remote add origin https://github.com/Homebrew/brew
error: remote origin already exists.

cka@/Users/wrks> brew update
Warning: No remote 'origin' in /opt/homebrew, skipping update!
Already up-to-date.

cka@/Users/wrks> brew upgrade
Warning: No remote 'origin' in /opt/homebrew, skipping update!
==> Upgrading 26 outdated packages:
rubberband 2.0.2 -> 3.0.0
libtiff 4.4.0 -> 4.4.0_1
ffmpeg 5.0.1_2 -> 5.1
libidn2 2.3.2 -> 2.3.3
little-cms2 2.13.1 -> 2.13.1_1
nettle 3.8 -> 3.8.1
speex 1.2.0 -> 1.2.1
harfbuzz 4.3.0 -> 5.0.1
glib 2.72.2 -> 2.72.3
mbedtls 3.1.0 -> 3.2.1
srt 1.4.4 -> 1.5.0
tesseract 5.1.0 -> 5.2.0
webp 1.2.2 -> 1.2.3_1
sqlite 3.38.5 -> 3.39.2
xz 5.2.5 -> 5.2.5_1
libnghttp2 1.47.0 -> 1.48.0
libvpx 1.11.0 -> 1.12.0
librist 0.2.7 -> 0.2.7_1
ca-certificates 2022-04-26 -> 2022-07-19_1
isl 0.24 -> 0.25
btop 1.2.7 -> 1.2.8_1
leptonica 1.82.0 -> 1.82.0_1
jpeg-xl 0.6.1 -> 0.6.1_1
unbound 1.16.0 -> 1.16.1
fzf 0.30.0 -> 0.31.0
gnutls 3.7.6 -> 3.7.7
Error: snappy: undefined method `<=' for nil:NilClass

cka@/Users/wrks> git -C "/opt/homebrew" remote add origin https://github.com/Homebrew/brew
error: remote origin already exists.

That's weird, considering your main error. What's the output of the following:
git -C /opt/homebrew rev-parse --show-toplevel
git -C /opt/homebrew remote -v

cka@/opt> git -C /opt/homebrew rev-parse --show-toplevel
/opt/homebrew
cka@/opt> git -C /opt/homebrew remote -v
origin	https://github.com/Homebrew/brew (fetch)
origin	https://github.com/Homebrew/brew (push)

Weirder and weirder. What's the output of git -C /opt/homebrew config -l?

Here we go :)
cka@/opt> git -C /opt/homebrew config -l
credential.helper=osxkeychain
user.name=Chris
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
core.ignorecase=true
core.precomposeunicode=true
core.autocrlf=false
remote.origin.url=https://github.com/Homebrew/brew
remote.origin.fetch=+refs/heads/:refs/remotes/origin/
branch.master.remote=origin
branch.master.merge=refs/heads/master
homebrew.analyticsmessage=true
homebrew.caskanalyticsmessage=true
homebrew.analyticsuuid=EF7FEA21-01DA-4CB9-8959-1806B9E95FC1
homebrew.donationmessage=true
homebrew.devcmdrun=true

Try brew update-reset, then brew config and brew doctor again.

cka@/opt> brew update-reset
Warning: No remote 'origin' in /opt/homebrew, skipping update and reset!
==> Fetching /opt/homebrew/Library/Taps/homebrew/homebrew-cask...
==> Resetting /opt/homebrew/Library/Taps/homebrew/homebrew-cask...
Branch 'master' set up to track remote branch 'master' from 'origin'.
Reset branch 'master'
Your branch is up to date with 'origin/master'.
==> Fetching /opt/homebrew/Library/Taps/homebrew/homebrew-cask-fonts...
==> Resetting /opt/homebrew/Library/Taps/homebrew/homebrew-cask-fonts...
Branch 'master' set up to track remote branch 'master' from 'origin'.
Reset branch 'master'
Your branch is up to date with 'origin/master'.
==> Fetching /opt/homebrew/Library/Taps/homebrew/homebrew-core...
remote: Enumerating objects: 4, done.
remote: Counting objects: 100% (3/3), done.
remote: Total 4 (delta 3), reused 3 (delta 3), pack-reused 1
Unpacking objects: 100% (4/4), 840 bytes | 35.00 KiB/s, done.
From https://github.com/Homebrew/homebrew-core

[new branch]              update-tflint.rb-1659103062 -> origin/update-tflint.rb-1659103062

==> Resetting /opt/homebrew/Library/Taps/homebrew/homebrew-core...
Branch 'master' set up to track remote branch 'master' from 'origin'.
Reset branch 'master'
Your branch is up to date with 'origin/master'.
==> Fetching /opt/homebrew/Library/Taps/homebrew/homebrew-services...
==> Resetting /opt/homebrew/Library/Taps/homebrew/homebrew-services...
Branch 'master' set up to track remote branch 'master' from 'origin'.
Reset branch 'master'
Your branch is up to date with 'origin/master'.
==> Fetching /opt/homebrew/Library/Taps/koekeishiya/homebrew-formulae...
==> Resetting /opt/homebrew/Library/Taps/koekeishiya/homebrew-formulae...
Branch 'master' set up to track remote branch 'master' from 'origin'.
Reset branch 'master'
Your branch is up to date with 'origin/master'.
==> Fetching /opt/homebrew/Library/Taps/sidneys/homebrew-homebrew...
==> Resetting /opt/homebrew/Library/Taps/sidneys/homebrew-homebrew...
Branch 'master' set up to track remote branch 'master' from 'origin'.
Reset branch 'master'
Your branch is up to date with 'origin/master'.
cka@/opt> brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!
Warning: Missing https://github.com/Homebrew/brew git origin remote.
Without a correctly configured origin, Homebrew won't update
properly. You can solve this by adding the remote:
git -C "/opt/homebrew" remote add origin https://github.com/Homebrew/brew
cka@/opt> git -C "/opt/homebrew" remote add origin https://github.com/Homebrew/brew
error: remote origin already exists.
cka@/opt> brew upgrade
Warning: No remote 'origin' in /opt/homebrew, skipping update!
==> Upgrading 26 outdated packages:
rubberband 2.0.2 -> 3.0.0
libtiff 4.4.0 -> 4.4.0_1
ffmpeg 5.0.1_2 -> 5.1
libidn2 2.3.2 -> 2.3.3
little-cms2 2.13.1 -> 2.13.1_1
nettle 3.8 -> 3.8.1
speex 1.2.0 -> 1.2.1
harfbuzz 4.3.0 -> 5.0.1
glib 2.72.2 -> 2.72.3
mbedtls 3.1.0 -> 3.2.1
srt 1.4.4 -> 1.5.0
tesseract 5.1.0 -> 5.2.0
webp 1.2.2 -> 1.2.3_1
sqlite 3.38.5 -> 3.39.2
xz 5.2.5 -> 5.2.5_1
libnghttp2 1.47.0 -> 1.48.0
libvpx 1.11.0 -> 1.12.0
librist 0.2.7 -> 0.2.7_1
ca-certificates 2022-04-26 -> 2022-07-19_1
isl 0.24 -> 0.25
btop 1.2.7 -> 1.2.8_1
leptonica 1.82.0 -> 1.82.0_1
jpeg-xl 0.6.1 -> 0.6.1_1
unbound 1.16.0 -> 1.16.1
fzf 0.30.0 -> 0.31.0
gnutls 3.7.6 -> 3.7.7
Error: snappy: undefined method `<=' for nil:NilClass

Sorry, I'm fresh out of ideas. Your Homebrew installation is b0rked so strangely that Git itself is giving contradictory messages.
Unless anyone else has any ideas, you may have to wipe and start from scratch, but run brew bundle dump --global first to dump your current Homebrew install state into your home directory first. Make sure it doesn't throw any errors though.

No problem, but when I try to dump the bundle I get these errors.
After I got errors in brew doctor before already from snappy,gcc and x265, I uninstalled them. But it seems they are still somewhere registered:
cka@/opt/homebrew> brew bundle dump --global
Warning: No remote 'origin' in /opt/homebrew, skipping update!
Warning: 'gcc' formula is unreadable: gcc: undefined method on_arm' for #<Resource::PatchResource:0x000000012142f6b8> Warning: 'snappy' formula is unreadable: snappy: undefined method <=' for nil:NilClass
Warning: 'x265' formula is unreadable: x265: undefined method `on_intel' for Formulary::FormulaNamespacea33e4b1aa88dfc4cf6083d9fa695245d::X265:Class

What is the output of
git -C /opt/homebrew status

?

cka@/opt/homebrew> git -C /opt/homebrew status
On branch master
Your branch is behind 'origin/master' by 210 commits, and can be fast-forwarded.
(use "git pull" to update your local branch)
nothing to commit, working tree clean

Try doing
git -C /opt/homebrew pull --ff-only

Thanks Carlo, not only the dump is working now. Also the upgrade runs now!
cka@/Users/christiankaufmann> brew bundle dump --global
fatal: not in a git directory
Warning: No remote 'origin' in /opt/homebrew, skipping update!
The file ha been created and it looks complete.
So, it looks like I still need to cleanup. Means uninstall all packages, remove the directory and then reinstall everything?

The file ha been created and it looks complete. So, it looks like I still need to cleanup. Means uninstall all packages, remove the directory and then reinstall everything?

You can use the uninstall script to do the uninstalling:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/uninstall.sh)"

This will remove all packages you have installed, but you can use the generated Brewfile and brew bundle to reinstall them after you've reinstalled brew.

I don't know the installation fails as well:
cka@/opt/Homebrew> /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
==> Checking for sudo access (which may request your password)...
Password:
==> This script will install:
/opt/homebrew/bin/brew
/opt/homebrew/share/doc/homebrew
/opt/homebrew/share/man/man1/brew.1
/opt/homebrew/share/zsh/site-functions/_brew
/opt/homebrew/etc/bash_completion.d/brew
/opt/homebrew
==> HOMEBREW_BREW_GIT_REMOTE is set to a non-default URL:
/opt/Homebrew/brew will be used as the Homebrew/brew Git remote.
==> HOMEBREW_CORE_GIT_REMOTE is set to a non-default URL:
/opt/Homebrew/homebrew-core will be used as the Homebrew/homebrew-core Git remote.
Press RETURN/ENTER to continue or any other key to abort:
==> /usr/bin/sudo /usr/sbin/chown -R christiankaufmann:admin /opt/homebrew
==> Downloading and installing Homebrew...
fatal: '/opt/Homebrew/brew' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Failed during: git fetch --force origin
ENV is set:
cka@/opt/Homebrew> env | grep HOMEBREW
HOMEBREW_BREW_GIT_REMOTE=/opt/Homebrew/brew
HOMEBREW_CORE_GIT_REMOTE=/opt/Homebrew/homebrew-core
What are then the correct access rights? I can do anything in /opt/Homebrew

Why do you have
HOMEBREW_BREW_GIT_REMOTE=/opt/Homebrew/brew
HOMEBREW_CORE_GIT_REMOTE=/opt/Homebrew/homebrew-core

?
Do
unset HOMEBREW_BREW_GIT_REMOTE HOMEBREW_CORE_GIT_REMOTE

and then try the install script again.

I had this because its in the documentation. However, without the env it worked. Thanks

I had this because its in the documentation.

Where in the documentation? If it's there, then the documentation is wrong and needs to be fixed.

https://docs.brew.sh/Installation
However, how I reinstall the dumped bundle? I can't find the brew bundle command to do that.

Those docs say this:

Git Remote Mirroring
You can use geolocalized Git mirrors to speed up Homebrew's installation and brew update by setting HOMEBREW_BREW_GIT_REMOTE and/or HOMEBREW_CORE_GIT_REMOTE in your shell environment with this script:
export HOMEBREW_BREW_GIT_REMOTE="..."  # put your Git mirror of Homebrew/brew here
export HOMEBREW_CORE_GIT_REMOTE="..."  # put your Git mirror of Homebrew/homebrew-core here
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"

The default Git remote will be used if the corresponding environment variable is unset.

I'm not sure how you concluded from there to set
HOMEBREW_BREW_GIT_REMOTE=/opt/Homebrew/brew
HOMEBREW_CORE_GIT_REMOTE=/opt/Homebrew/homebrew-core

Probably slightly misunderstud.


Copy-button animation repainting every frame

The animation on the copy-button is making a repaint of the DOM every frame. This is expensive because the browser must verify the visibility of all other nodes in the DOM tree.

It's cool tho

This actually seems to be a bug in Chrome, and work is underway to fix it:
https://bugs.chromium.org/p/chromium/issues/detail?id=1101002
Firefox works just fine ;)

Closing, as this has been fixed in Chromium 87 🥳


Implement a small distributed file system (supporting stand-alone) for resource uploading instead of hdfs.

Implement a small distributed file system (supporting stand-alone) for resource uploading instead of hdfs.
实现一个小巧的分布式文件系统(支持单机)，用于资源上传，替代hdfs

I would suggest use https://github.com/minio/minio to replace HDFS, since:

it is relatively easy. and it implements AWS S3 API
it also have wrapper around common fs, like, AWS, azure, even HDFS

+1

https://github.com/sjqzhang/go-fastdfs  扩容简单,  支持断点续传等.

+1

Details information about how to use HDFS/ Local FileSystem / AWS S3 (or Minio Server), please see pull request https://github.com/analysys/EasyScheduler/pull/267

这个单机版本可以用吗？具体怎么用呢？

这个单机版本可以用吗？具体怎么用呢？

Yes, please refer to https://github.com/apache/incubator-dolphinscheduler/pull/267 for the detailed usage. Especially part 3, how to use with Minio .
Note: that was based on dev-1.1.0 branch,  but in the newest 1.2.0 branch, the configuration files may be in different location, please double check.


Thanks for the help and efforts, please remove all api's and reset my accounts and balance to zero (0). Since, I was bugged or hacked.

Can i have fix please
Originally posted by @F0o0De in https://github.com/F0o0De/coinigyV2/issues/1

Sorry to hear.


Migrate to .NET Core 2.2 from .NET FW 4.5

Migrated project file format to VS 2017 format
Migrated to .NET Core 2.2
Migrated CI pipeline to dotnet core

Thanks for this PR. But I have to just close it, as the project has already migrated to .NET Core 3.1.


[2] Use resource expansion to remove explicit cover API usage

Closes #2

Added thumbnail as part of this PR, so it also closes #3