Update bigquery-profile.md

Adding https://www.googleapis.com/auth/iam.test scope to gcloud auth application-default login to get rid of the following error
These credentials will be used by any library that requests Application Default Credentials (ADC).
/Users/sova/google-cloud-sdk/lib/third_party/google/auth/_default.py:69: UserWarning: Your application has authenticated using end user credentials from Google Cloud SDK without a quota project. You might receive a "quota exceeded" or "API not enabled" error. We recommend you rerun `gcloud auth application-default login` and make sure a quota project is added. Or you can use service accounts instead. For more information about service accounts, see https://cloud.google.com/docs/authentication/
  warnings.warn(_CLOUD_SDK_CREDENTIALS_WARNING)
ERROR: (gcloud.auth.application-default.login) User [*********] does not have permission to access projects instance [********:testIamPermissions] (or it may not exist): Request had insufficient authentication scopes

@VasiliiSurov I don't see iam.test listed among the auth scopes here. Could you say a bit more about why this is required in your case? I see the error message mentions ********:testIamPermissions, that's not a method I was familiar with.

@jtcohen6
I have a standard use case: authanticating dbt via oauth. Even it's not mandatory and application got authenticated but I want to avoid this frightening message.
Please check the following page https://cloud.google.com/resource-manager/reference/rest/v1/projects/testIamPermissions
Am I the only one who's getting this notification? Just updated SDK and got the same notification
(dbt) sova@sova dbt % gcloud --version
Google Cloud SDK 335.0.0
bq 2.0.66
core 2021.04.02
gsutil 4.60
kubectl 1.17.17
(dbt) sova@sova dbt %

Ah you're right, I was using an old version of gcloud. I just upgraded and now see the error message you saw.
When I try to run with the new scopes, however, I get this error:
$ gcloud auth application-default login   --scopes=https://www.googleapis.com/auth/bigquery,https://www.googleapis.com/auth/drive.readonly, https://www.googleapis.com/auth/iam.test
ERROR: (gcloud.auth.application-default.login) unrecognized arguments: https://www.googleapis.com/auth/iam.test

To search the help text of gcloud commands, run:
  gcloud help -- SEARCH_TERMS

That's definitely the scope listed on this page, but I can't find it anywhere on the main page for OAuth2 scopes.

@jtcohen6
you need to remove space before https://www.googleapis.com/auth/iam.test
All scopes have to be passed as a single parameter


Add model name used in generated plots

Context
Currently, I'm using three models for CLV analysis and generating calibration_purchases_vs_holdout_purchases for comparison. I thought that it might be a good idea to display the model name in the chart title for additional differentiation. Any thoughts?
If this sounds good. I will go ahead and make the necessary changes.

Heya, I think I know what you mean, but do you have a screenshot of your idea?

We could and might do that in the future, but you already can kind of do that by customizing the title of the plot. You could also use labels and plt.legend().

I am interested in this as well. I forked the library and made the update in my own copy. @psygo, could you provide an example of how we can customize the title of the plot through the lifetimes library as-is? Thank you.

@Samanvay96 , I got it to work with the following code:
plot_calibration_purchases_vs_holdout_purchases(
    model=bgf_monthly_train,
    calibration_holdout_matrix=cal_holdout_monthly).title.set_text('hi')


Screensaver error

Screen saver not working.
I set it based on the description below:
https://github.com/D3VL/wtfos-image-configurator
Spalshscreen appears but the screensaver never starts.
It only works when I remove the MSP-OSD package.
Someone has a screen saver working?
Thanx,

This is due to how MSP-OSD works, it uses the same rendering layer that the screensaver uses, effectively blocking it from working.
At this time, it's a wontfix.

Jack


Expired code if internal was set more than 1 minute

When set interval is 300
test_time = 'Wed, 12 Apr 2023 11:49:59 +08 +08:00'.to_datetime
otp = ROTP::TOTP.new(token, issuer: 'test', interval: 300)
code = otp.at(test_time)
now = 'Wed, 12 Apr 2023 11:50:01 +08 +08:00'.to_datetime
otp.verify(code, at: now) => nil
above code is only valid in 11:45:00-> 11:49:59

Yeah, an interval doesn't mean it's valid for any 300 seconds, but it's valid for an interval of 300 seconds. So for example Unix time 0 to 299, and then it's invalid again at 300.
So if you pick a random time, you don't actually know where it falls in the interval until you do the conversion to unix time and 'round' it down to the nearest 300 second interval.
You can see this in the totp.rb code - https://github.com/mdp/rotp/blob/main/lib/rotp/totp.rb#L77
Using your example above
irb(main):041:0> Time.parse("Wed, 12 Apr 2023 11:49:59 +08 +08:00").to_i / 300
=> 5604237
irb(main):042:0> Time.parse("Wed, 12 Apr 2023 11:50:00 +08 +08:00").to_i / 300
=> 5604238

11:49:59 is just on the edge of a new 300 second interval. But the code at 11:50:00 will work until 11:54:59 as expected.
irb(main):044:0> Time.parse("Wed, 12 Apr 2023 11:54:49 +08 +08:00").to_i / 300
=> 5604238
irb(main):045:0> Time.parse("Wed, 12 Apr 2023 11:55:00 +08 +08:00").to_i / 300
=> 5604239


Fix OS X Travis CI builds

Currently, all of our Travis CI OS X builds are failing for whatever reason (I haven't actually taken a look yet). We should probably fix this and mark those builds as "mandatory pass" for the future.

Actually going to re-open this since I think we should still mark the OS X builds as mandatory pass, so we can ensure this doesn't happen again in the future.

OSX builds mandatory in https://github.com/rusoto/rusoto/pull/426 . We're all good.


Add a top-level class for metrics similar with all the other packages.

@SergeyKanzhelev I reverted the class name change, fix some warnings in the tests as well (unused variables).


⚠ Bofrost.de has degraded performance

In 08a590e, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2157 ms

Resolved: Bofrost.de performance has improved in cccfe94 after 13 minutes.


FEATURE: scaling/replication trigger configuration

Please consider an abstraction for auto-scaling of containers and/or trigger rules using Kubernetes KEDA (locally) and/or Azure Container Services, Amazon Web Services EKS etc.

Do you want to help design this? In order to design an abstraction for something like this the capabilities of each of those services (and others) need to be analyzed so there's an understanding of what commonalities can be abstracted to build such an abstraction. I would start by trying to understand what it would mean to model a single environment (there's no support for that today) and I don't even have an understanding of what that would look like.

I would definitely be interesting in helping define and implement scaling; as I personally see scaling to be a key cloud feature, my initial idea would be to extend the ReplicaAnnotation(int x) with a ReplicaAnnotation(int min, int max) which would serve as the limiter for any scaling trigger configuration bound to the service.

@davidfowl I've created a fork of aspire for work on the scaling feature at https://github.com/3GDXC/aspire and have started with the ReplicaAnnotation mentioned above; including tests for the annotation etc.

basic starter

what to scale
need to determine what types of resource can/should be scaled.

nodes
pods

what types of scaling
need to determine the types of scaling operations.

up
out

when to scale
need to determine the events that can be used to trigger a scaling operation.

cpu
memory
external event

what/where the annotations should be placed

@davidfowl would it be better to control this via compute customization. I think it would be difficult to come up with a model that was abstract enough to work across the variety of compute resources we'll eventually target.

@mitchdenny I see this as a possible configuration and deployment of keda/triggers for keda to then listen and respond to in a Kubernetes deployment senario; and when deployed to other container/non-container senario the tooling for that deployment using the keda configuration to (attempt) to acheive the same scaling.  If the Keda scaling triggers etc. can't be acheive by the deployment (target) tooling then a message/exception should detail the scaling option/trigger is not availible for the deployment (target). I see the inital triggers CPU, memory, request queue, hooking into the health checks, these health checks would have tags associated with them to determin which check is linked to which scaling action; as this would allow for custom/complex health checks to perform some scaling action.


Backport ReadonlyRecord & Record

Backports ReadonlyRecord from 3.0.0 based on the 2.11 roadmap https://github.com/gcanti/fp-ts/issues/1446
I agree w/ the Ord idea outlined in the roadmap, but I can change if desired.
Notes:

I used Ord constraints in Record as well, I can change it to use Ord.trivial if desired
I wasn't sure why ReadonlyRecord.wilt and ReadonlyRecord.wither use Ord.trivial  in 3.0.0, but I mirrored that - I'm not sure if that was correct
I also added Ord instances to these, which were unspecified - we can use Ord.trivial instead if desired

traverse
sequence
getShow
typeclass instances (Traversable -> getTraversable: (O: Ord<string>) => ...)

I agree w/ the Ord idea outlined in the roadmap

We can't just change the signatures though, this PR contains the following breaking changes:

keys
collect
toReadonlyArray
toUnfoldable
reduceWithIndex
foldMapWithIndex
reduceRightWithIndex
traverseWithIndex
traverse
sequence
reduce
foldMap
reduceRight
getShow
Foldable -> getFoldable
FoldableWithIndex -> getFoldableWithIndex
Traversable -> getTraversable
TraversableWithIndex -> getTraversableWithIndex
Witherable -> getWitherable

I wasn't sure why ReadonlyRecord.wilt and ReadonlyRecord.wither...

This was a mistake, thanks for pointing out (fixed now in v3)

Oh, ok - I misunderstood the roadmap & the release process, my bad. Do you think it would make sense to new functions w/ *WithOrd signatures (e.g. keysWithOrd)? Or maybe it's best to leave all that out for the moment?

Yeah, I'm sorry, the roadmap wan't clear on this point, I put a "?" on the item list because I'm not even sure is possible to backport the new constraint.
In general we can do whatever we want in the 3.0.0 branch (with an eye on the migration path though) but in the 2.x series we can't introduce breaking changes.
In the past I used the following technique:

add a new signature as an overload to the API
deprecate the old signature

Let's pick keys for example:
export const keys = <K extends string>(r: ReadonlyRecord<K, unknown>): ReadonlyArray<K> =>
  (Object.keys(r) as any).sort()

The new definition would be something like:
declare const isOrd: (r: Ord<string> | ReadonlyRecord<string, unknown>) => r is Ord<string>

/**
 * @since 2.5.0
 */
export function keys(O: Ord<string>): <K extends string>(r: ReadonlyRecord<K, unknown>) => ReadonlyArray<K>
/**
 * Use the other overload instead
 *
 * @deprecated
 */
export function keys<K extends string>(r: ReadonlyRecord<K, unknown>): ReadonlyArray<K>
export function keys(
  or: Ord<string> | ReadonlyRecord<string, unknown>
): ((r: ReadonlyRecord<string, unknown>) => ReadonlyArray<string>) | ReadonlyArray<string> {
  return isOrd(or) ? keys(or) : (Object.keys(or) as any).sort()
}

The problem is the isOrd guard: how can we reliably distinguish between an Ord and a ReadonlyRecord?

No worries! Oh good question. Maybe something like this?
const isOrd = <A>(a: Record<string, unknown> | Ord<A>): a is Ord<A> =>
  keys(a as Record<string, unknown>).length === 2
  && 'equals' in a
  && typeof a.equals === 'function'
  && 'compare' in a && typeof a
  && typeof a.compare === 'function'

I know it's super kludgy, but we could probably assume that would work

I would:

keep as is:

keys (you can always sort the output, or, if you want the insertion order, use Object.keys)
toReadonlyArray (you can always sort the output, or, if you want the insertion order, use Object.values)
toUnfoldable, traverseWithIndex, traverse, sequence (it doesn't worth it)

apply the technique to:

collect (this first parameter is a function so we are safe)
reduceWithIndex, reduceRightWithIndex, reduce, reduceRight (checking the arguments length I guess)
foldMapWithIndex, foldMap, getShow (checking compare? ugly...)

add a new API and deprecate the old one (which we keep as is to not introduce breaking changes):

Foldable -> getFoldable
FoldableWithIndex -> getFoldableWithIndex
Traversable -> getTraversable
TraversableWithIndex -> getTraversableWithIndex
Witherable -> getWitherable

I would...

btw I know this is an horrible task, so feel free to close this PR or just clean it up by keeping only the new additions like union, intersection, etc...

Not at all - it's my pleasure! It should be good now.
By the way, I saw your comment in the Roadmap - please feel free to close this or steal from it if that'd be easier for you. Or I can remove the Ord stuff if that's easiest

@anthonyjoeseph awesome, thank you!


[SPARK-14454][1.6] Better exception handling while marking tasks as failed

Backports https://github.com/apache/spark/pull/12234 to 1.6. Original description below:
What changes were proposed in this pull request?
This patch adds support for better handling of exceptions inside catch blocks if the code within the block throws an exception. For instance here is the code in a catch block before this change in WriterContainer.scala:
logError("Aborting task.", cause)
// call failure callbacks first, so we could have a chance to cleanup the writer.
TaskContext.get().asInstanceOf[TaskContextImpl].markTaskFailed(cause)
if (currentWriter != null) {
  currentWriter.close()
}
abortTask()
throw new SparkException("Task failed while writing rows.", cause)

If markTaskFailed or currentWriter.close throws an exception, we currently lose the original cause. This PR fixes this problem by implementing a utility function Utils.tryWithSafeCatch that suppresses (Throwable.addSuppressed) the exception that are thrown within the catch block and rethrowing the original exception.
How was this patch tested?
No new functionality added

cc @davies @rxin

Test build #55427 has started for PR 12272 at commit 0defe22.

Test build #55427 has finished for PR 12272 at commit 0defe22.

This patch fails build dependency tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/55427/
Test FAILed.

Test build #2772 has started for PR 12272 at commit 0defe22.

Test build #2772 has finished for PR 12272 at commit 0defe22.

This patch fails build dependency tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #2773 has started for PR 12272 at commit 0defe22.

Test build #2773 has finished for PR 12272 at commit 0defe22.

This patch fails build dependency tests.
This patch merges cleanly.
This patch adds no public classes.

cc @JoshRosen any idea what's going on?

We need to backport my mvn download change to branch-1.6, which is not as simple as a cherry-pick because those branches have diverged.

LGTM.

Since this is a cherry-pick from master (after fixing some conflicts), will not wait for the build come back, merging this into branch-1.6 now, thanks!

Could you close this PR?

yes, thanks


TW polygon missing Lienchiang County and parts of Kinmen County (Wuqiu)

Of the "TPKM" areas the TW polygon currently includes Taiwan, Penghu and the main island of Kinmen County, but there are a few islands missing. In keeping with the objectives of this library the motivation here is to power consistent locale information for mapping, so this doesn't include some unpopulated islands; the civilian population is 10,000+ of these in total and there is significant detail in OSM:
Wuqiu relation on OSM
Lienchiang (Matsu) relation on OSM
Screenshot of proposed polygon change with OSM Carto as a reference, using a minimal number of vertices:

done in #127


Lighting / Shadows

Implementing lights & shadows into the framework. Let me know if you want to delegate this work!

this is a huge deal, I have to spend more time with the framework before I can implement that

Considering this is a huge implementation/feature and not an "issue", this can be closed


add to python package index

[x] Fixes #264

Thanks to Nic(@nryoung), we are live in PyPI!
He also agreed to join us as a maintainer, so please welcome!
now you can install the package with simple pip install algorithms.

Pull Request Test Coverage Report for Build 454

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 91.771%

Totals

Change from base Build 452:
0.06%

Covered Lines:
2922

Relevant Lines:
3184

💛  - Coveralls


Improve error messages by supporting ErrorInfo and AIP-193

https://google.aip.dev/193 describes the recommended way for Google services to return additional error information to users. The additional data is sent in the https://github.com/googleapis/api-common-protos/blob/master/google/rpc/status.proto details field, which is a repeated google.protobuf.Any. This is exposed to in C++ via grpc::Status's .error_details() method (https://grpc.github.io/grpc/cpp/classgrpc_1_1_status.html), which returns std::string. As of today, our google::cloud::Status class drops the error details on the ground.
So I think we need to do the following:

[ ] Add "error_details" to google::cloud::Status. This is covered by https://github.com/googleapis/google-cloud-cpp/issues/1912
[ ] We need to provide some API that easily (or automatically?) extract and print ErrorInfo fields IF they are present in the Status's "error_details". We should consider options for how we want to do this. If we change the default op<< for g::c::Status, might that break customers who depended on the output (but is that something we should worry about)?

This is a useful link for where grpc does a lot of manipulation of its Status object using upb and absl in some places too: https://github.com/grpc/grpc/blob/master/src/core/lib/gprpp/status_helper.cc

I believe the error_details is set to the serialized google::rpc::Status from which it was created, and that would have an Any that may contain the ErrorInfo.
Related to: https://github.com/grpc/grpc/issues/24007

Some answers to questions that I had

Any grpc Status object will have at most on ErrorInfo object. Even though the underlying field is a repeated field of Anys, there will be a max of one ErrorInfo.
We do need to give users programmatic access to the "Error Info" fields (reason, domain, metadata).
We need to change Status::op<< to print the ErrorInfo details if its present.

Even JSON requests will gain an "ErrorInfo" (equivalent) JSON object


Cross-build nightly builds (arm64, s390x, ppc64el)

This adds a few more architectures for Linux builds.
Example: https://github.com/mxpv/containerd/runs/303871920
ref: https://github.com/containerd/containerd/pull/3827 https://github.com/containerd/containerd/pull/3828
cc: @estesp

Codecov Report

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

@@            Coverage Diff             @@
##           master    #3829      +/-   ##
==========================================
- Coverage   41.99%   41.98%   -0.02%
==========================================
  Files         130      130
  Lines       14577    14577
==========================================
- Hits         6122     6120       -2
- Misses       7542     7543       +1
- Partials      913      914       +1

Flag
Coverage Δ

#linux
45.42% <ø> (-0.02%)
:arrow_down:

#windows
36.94% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

snapshots/btrfs/btrfs.go
57.39% <0%> (-0.9%)
:arrow_down:

Continue to review full report at Codecov.

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

Thanks!


how to improve reconstruction precision

When asking for help or submitting a bug report, please provide the following important information about your system:

Operating system version (for example, Ubuntu 18.04 LTS)
ROS version (for example, ROS Melodic)
CUDA version (for example, CUDA 11.4)
Nvidia driver version (for example, Driver 470.141)
_Graphics card type (for example, Nvidia GeForceGTX 1650)

this is the outpu ply file by

I use franka +L515 +yak_ros
with two pc , one of them run franka_ros and L515  and another pc run yak_ros ,subscribe /camera/depth/image_rect_raw,
and this is the real environment:

and this is the launch file

<node name="tsdf_node" pkg="yak_ros" type="yak_ros_node" output="screen">
  <!-- remap realsensen topic  -->
  <remap from="~input_depth_image" to="/camera/depth/image_rect_raw"/>
  <!-- <remap from="~input_point_cloud" to="/camera/depth_registered/points"/> -->
  <param name="tsdf_frame" value="tsdf_origin"/>
  <rosparam param="camera_matrix">[457.046875, 0.0,<PHONE_NUMBER>5, 0.0, 456.90625,<PHONE_NUMBER>75, 0.0, 0.0, 1.0]</rosparam>
  <param name="cols" value="640"/>
  <param name="rows" value="480"/>
<param name="volume_resolution" value="0.002"/>
<param name="volume_x" value="640"/>
<param name="volume_y" value="640"/>
<param name="volume_z" value="768"/>
</node>

<node pkg="tf" type="static_transform_publisher" name="link1_broadcaster" args="0.32714 -0.26846 0.002 0.0 0.0 0.0 1.0 world tsdf_origin 100" />
<!-- <node type="rviz" name="rviz" pkg="rviz" args="-d $(find jil_object_tracking)/rviz/yak_demo.rviz" /> -->
<arg name="rviz" default="true" />
<group if="$(arg rviz)">
    <node launch-prefix="nice" pkg="rviz" type="rviz" name="rviz_meng"/>
</group>

we can see many large holes and in the surface after resconstruction, and plane becomes curved
can you give me some advice to improve the reconstruction precision
and quesiont2:
there are so many faces in the ply file ,how can we combine them into a few surfaces

Increase the tsdf resolution from 0.002 to something larger that the sensor depth noise. If this is smaller that the expected noise in the depth then the noise decays seen areas resulting in holes in the data. Also this is directly propositional to the mesh resolution since it use marching cubes using the tsdf to generate the mesh.


Add a --org flag to hub fork

Fixes #505

@mislav thanks for the comments.
I think I address all the issues.
Just a though... how do you feel about using --org flag? which is not short nor long??
I feel it should be something like -o, --organization, but:

organization is really super long to type.
the -o is usually used for --open in a browser.
Based on the comments on this issue https://github.com/ogier/pflag/issues/17 the short flag -o should work with a space, but not the long one.

The other syntax I played with that I feel could work well is
hub fork [<ORGANIZATION>]
hub fork acme

Just like the create command accept [<ORGANIZATION/>USER]
well, let me know if we need more changes and before merging so I can squash the commits.

Done, I went ahead and squash the commits...
Let me know if there is something else...

Thanks for your patience and prompt updates!

Your welcome! thank you!

Hey, thanks for this. Very useful. This doesn't yet work with hub pull-request. Is that right?


Include project id for GCP in data output

Context
Overview
In order to better analyze the data and understand the most valuable ways to look at it, many users, including our TechOps stakeholder and the ThoughtWorks data team are looking at the raw data itself. They would like to combine the data provided by our tool with other data, but for GCP without the project id, the only unique identifier, they cannot. This ticket will address adding in the project id to the set of data returned from the various ways of receiving CCF data.
Out of Scope:

[ ] No changes should appear on the UI

Related issues/Dependencies:
Acceptance Criteria

[x] When I hit the API, and request GCP data, I should receive both the project name and the project id

[x] When I hit the API, and request AWS data, I should receive both the account name and no value for the account id (or should this be switched or duplicated?)

[x] When I hit the API, and request Azure data, I should receive both the subscription id and subscription name

[x] When I request GCP data via the CLI, I should receive both the project name and the project id

[x] When I request AWS data via the CLI, I should receive both the account id and no value for the project id (or should this be switched or duplicated?)

[x] When I request AWS data via the CLI, I should receive both the subscription id and subscription name

[x] (Probably not possible - spend very short time testing) When I download data from the emissions breakdown chart, I can see both project id and name for all cloud providers if provided

Tech Tasks

[ ] Run Changesets, bump any packages that have been updated/changed
[ ] Did you make changes to the client, api or cli package? If so, considering updating the create-app templates.
[x] Test for performance implications - if so, let's talk about it

Tech Notes
Review Tasks

[ ] eg. specific QA details, update methodology, or update microsite

For this, I think we can introduce a new attribute to the ServiceData type inside packages/common/src/EstimationResult.ts, for AcountId. How is how it will be handled for each cloud provider:

GCP: accountId: populated, accountName: populated
AWS: accountId: populated, accountName: undefined
Azure: accountId: populated, accountName: populated

I've implemented this as specified in the previous comment. A few notes:

The account name and id aren't exposed in the results via the CLI, in any of the options for how to render the tables. So those checklist items didn't need to be implemented. It should be a different issue to expose these, but only if we want to add that feature.
When downloading the data from the emissions breakdown chart, the project ID is not included in the results, after testing this.
There shouldn't be any noticeable performance implications from this, because GCP is the only cloud provider that now returns an additional object attribute when getting data from BigQuery, and GCP is already highly performant compared to AWS and Azure. AWS and Azure already returns the data we need from their APIs to populate the accountId field.

Moving to review!


Refactor agent forms

When I started studying Huginn to be able to start contributing, I noticed one part that I felt I could jump into right away: cleaning up the views and controllers.
This goes through and cleans up the agent form by introducing a form object (and collaborators) that encapsulate all the logic in the view. This makes the view more declarative, so it's hopefully easier to understand and debug. There's still some refactoring that can be done (the AgentForm class is pretty long as it has a lot to do) but I think it's a good start.
I hope you are open to this type of contribution! I think the project is really interesting and am planning to help out more as I get a better understanding of it.

Thanks @michaelherold, and welcome!
I think this is a good contribution.  I'm trying to decide if it makes the code harder to understand.  I think the general direction makes sense, but may have some comments on specific parts of the change as I dig into it.

I think this is a good contribution. I'm trying to decide if it makes the code harder to understand.

I was worrying about this as well when I first read the changes, but now think it makes sense. Even though new contributors have to understand the presenter layer, the template is now much easier to read. Also the presenter pattern should be familiar to most rails developers.
👍 for the approach you are using @michaelherold

Thank you for the feedback @cantino and @andrewcurioso !

I'm trying to decide if it makes the code harder to understand.

In my experience, it requires a little bit of shift in thinking, but the benefits pay off when you're writing new views. If you expect there to be a form/facade/"page presenter" for every view, there is an expected place to look for where to add tough logic instead of adding it to your view code.
This "view model" pattern also allows you to have collaborator objects that can encapsulate concerns. I tried to limit it here, but I'm sure there are places where it's pertinent.
An alternative to this ad hoc object model is to use something like reform for a structured approach, but that style of solution requires a lot of shift in the app architecture.
I look forward to hearing more of your thoughts!

I agree-- this is a good direction.  How close is this to done @michaelherold?

I just need to address the few comments that you all left. I'll do that tomorrow and push an update.

Whoops I accidentally deleted the branch last night for a minute, hence the random close.
I've made the changes that you all suggested for the lines that I touched. Thanks for all the feedback!

This is great work @michaelherold!
Do you think we should some specs on the new classes?

Thanks!

Do you think we should some specs on the new classes?

I can spec them out, but we hit nearly every line in the feature tests so I thought they might just end up being burdensome. What is the attitude of the project on this? Unit tests or integration tests?

I prefer to have both.  Maybe just add light specs for the new classes on methods that are complicated, but don't try to reproduce everything that the controller / feature specs cover?

Sounds good! I'll get to it soon ... I'm in the middle of a move right now so life is a little hectic.

Understood! I'm moving soon too, so much work :)


Force -Werror for CI

-Werror should be turned on for CI and --variant=debug
Users are supposed to do: ./waf configure (implying --variant=release); bug reporting => ./waf configure --variant=debug; If -Werror bites them, CXXFLAGS=-g ./waf configure --variant=debug

maybe just make some deploy/deploy-debug configs and inherit release/debug configs from it
in that case debug/release can just add -werror flag

On Windows with GCC/Clang, this isn't possible yet because of https://github.com/emilk/loguru/blob/2c35b5e7251ab5d364b1b3164eccef7b5d2293c5/loguru.hpp#L2807


💡 [REQUEST] - Footer Section

[x] I am from GSSoC'23.
[x] I would like to be assigned this task.

Section
Description

Concise Description
There is no Footer Section on the website. There should be a Footer Section on the website.

Solution Proposed
I will create Footer Section. Which will contain Social media links, Quick links, and many other things.

Somewhat like this will definitely make changes accordingly

|
Code of Conduct
By submitting this issue, you agree to follow our Code of Conduct.

[x] I follow the Contributing Guidelines of this project.
[x] I have checked the current issues for duplicate problems.
[x] I have read the readme of this repository.

Hi @parthpathakpp1
Thank you for creating the issue but this issue is already present #89


Start tagging releases on git

The current repo doesn't have any git release tag

Good idea. Will do going forward.


Add declaration DUNS validation

Depends on the following changes to declaration being merged:

[ ] https://github.com/alphagov/digitalmarketplace-frameworks/pull/273

This adds validation to the new DUNS number field introduced with the latest declaration content changes.

:+1:


clean up option handling

Whenever you find yourself branching and then immediately return (), you can use when :: Bool -> m () -> m ().

Cheers! Heaps better!


chore: add generic github issue templates to backstage-plugins

Description
Adds generic github issue templates to the backstage-plugins repo
What issue(s) does this fix?
Fixes #555

Should we keep the old feature_request template over the generic enhancement template? If we keep it, should we change it to an enhancement template with the kind/enhancement label for consistency across all repositories?

@tumido can you PTAL?

@josephca / @hmanwani-rh ^^ if you wanna take a look at templates for docs/QA


ReadableStream uploading is not supported (Safari 11.1.1)

I'm submitting a bug report

Library Version:
major.minor.patch-pre
1.4.0

Please tell us about your environment:

Operating System:
OSX 10.13.5

Node Version:
8.2.1

NPM Version:
3.8.9

JSPM OR Webpack AND Version
Aurelia CLI 0.31.3

Browser:
Safari 11.1.1

Language:
TypeScript 2.6.2

Current behavior:
main.ts
import 'fetch';
aurelia.json
{             "name": "fetch",             "path": "../node_modules/whatwg-fetch",             "main": "fetch"           },
My call to fetch
return this.httpClient.fetch( 			this.userUrlStem, { 				method: 'post', 				body: json(userDetailsRequest) 			}) 				   .then(handleErrors) 				   .then( 					   response => response.json());
When using Safari 11.1.1 I get the error
Unhandled rejection NotSupportedError: ReadableStream uploading is not supported     fetch@[native code]
Expected/desired behavior:
The fetch polyfill should be called to make this work in Safari.

not supported fetch@[native code] so, not using the polyfill. i presume the polyfill has like if (!window.fetch) add the polyfill. try deleting the native one before importing like delete window.fetch maybe double check gobal.fetch and self.fetch)

Thanks.
I did wonder if it was using it's own fetch method. But I had thought Safari didn't provide one.
I followed the instructions at https://aurelia.io/docs/plugins/http-services#aurelia-fetch-client that implied that it was a simple as adding import 'fetch'; to the main.js. Is the documentation out of date?
I will experiment with deleting window/global/self fetches.

out of date? yes/no, i guess having unimplemented parts wasn't anticipated.
anyways, found this https://github.com/jonnyreeves/fetch-readablestream

I found a reference to the same issue here https://stackoverflow.com/questions/49850705/fetch-in-safari-11-1-request-with-console-log-doesnt-work-readablestream-upl
I had an interceptor in my httpClient that was console logging the request. With that console.log removed the Safari fetch implementation works fine.


client.Dispose

client.Dispose does not accept argument anymore, it should be called like client.Dispose(true)

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

ID: cbd5007c-82e5-a0c1-2156-7df4bbbcc2da
Version Independent ID: eba98e03-3cc2-bebe-3dcd-45eda9c9c378
Content: HttpClient Class (System.Net.Http)
Content Source: xml/System.Net.Http/HttpClient.xml
Product: dotnet-api
GitHub Login: @karelz
Microsoft Alias: ncldev

@atiq-cs I don't understand what you mean. Can you maybe create PR to clarify your suggested changes?

updated description


removed broken link

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not have more than 100 characters
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Hi @VBota1
Thanks for your contribution ;)
We have some problems with Public APIs, so we won't be able to review/add this improvement right now.
Read this issue for more information, please: https://github.com/public-apis/public-apis/issues/3104


new taxon constraints, never in yeast

It is a joy to be able to see all of the nuclear descendants easily  now the complexes are grouped.
Please add the following taxon restrictions:
Never in yeast, nucleus descendants

[ ] GO:0046808    assemblon  - obsolete ?  #20746
[x] GO:0031039 macronucleus (+ only in protozoa?)
[x] GO:0031040 micronucleus (+ only in protozoa?)
[x] GO:0045120  pronucleus  (+ only in metazoa?)
[ ] GO:0098537 lobed nucleus (seems to be immune cells so only in multicellular organisms with immune system)

also

[x] GO:0060418    yolk plasma (+ only in metazoa?)
[x] GO:0045180    basal cortex   -> only in metazoa
[x] GO:0090652    basolateral cytoplasm  -> only in metazoa
term says "Used in reference to animal polarized epithelial cells." but has no annotation
[x] GO:0016323    basolateral plasma membrane
[ ] GO:0009925    basal plasma membrane
[x] GO:0044297    cell body
[ ] GO:0033012    porosome
[x] GO:0046868    mesosome (+ only in bacteria?) -> artifact, see https://en.wikipedia.org/wiki/Mesosome, but a few papers exist, see PMID:33309146, PMID:33327493
[x] GO:0031911     cytoproct (+ only in tetrahymena?) -> also found in other unicellulars, such as Euglenozoa, so I will add 'never in metazoa'

GO:0009925 basal plasma membrane is also found in plants. I dont know what's the taxonomic range
@AndreaAuchincloss is it found in bacteria?

GO:0009925 basal plasma membrane is also found in plants. I dont know what's the taxonomic range
@AndreaAuchincloss is it found in bacteria?

Nope, nor in archaea.

Nope, nor in archaea.

Not sure where to put porosome. PMC4580239 states "Discovery of the universal secretory machinery in cells –the porosome, came as no surprise since porosome-like ‘canaliculi’ structures for secretion from human platelets, the secretory machinery in single-cell organisms like the secretion apparatus in bacteria and Toxoplasma gondii, and the contractile vacuole in paramecium, have been demonstrated."
Maybe 'only in Eumetazoa '? There are no annotations; the papers I find talk about mammalian systems (pancreatic and neuronal cells).

Not sure where to put porosome. PMC4580239 states "Discovery of the universal secretory machinery in cells –the porosome, came as no surprise since porosome-like ‘canaliculi’ structures for secretion from human platelets, the secretory machinery in single-cell organisms like the secretion apparatus in bacteria and Toxoplasma gondii, and the contractile vacuole in paramecium, have been demonstrated."
Maybe 'only in Eumetazoa '? There are no annotations; the papers I find talk about mammalian systems (pancreatic and neuronal cells).


Deadlock after un-linking failed source from streammux (NVIDIA Bug)

Last log leading up to deadlock
0:00:24.266614123  7787     0x3ac7c260 INFO                     DSL src/DslServices.h:660:GetMainLoopHandle:  : Returning Handle to MainLoop
0:00:24.269812098  7787     0x3ac7c260 INFO                     DSL src/DslBintr.h:223:SetState:  : Changing state to 'NULL' for Bintr 'pipeline'
0:00:24.270290283  7787     0x3ac7c260 INFO                     DSL src/DslBintr.h:229:SetState:  : State change completed synchronously for Bintr'pipeline'
0:00:24.270582164  7787     0x3ac7c260 INFO                     DSL src/DslPipelineSourcesBintr.cpp:230:UnlinkAll:  : Unlinking stream_muxer from src-0
0:00:24.270930034  7787     0x3ac7c260 INFO                     DSL src/DslSourceBintr.cpp:144:UnlinkFromSink:  : Unlinking and releasing request Sink Pad for StreamMux stream_muxer

This is an old issue that was supposed to be fixed in the latest release.  see here

Nvidia has finally agreed that this is their bug... https://forums.developer.nvidia.com/t/releasing-nvstreammux-request-pad-results-in-a-deadlock/155271

Was resolved by NVIDIA... which DS release is unknown


Android: Initial render with scale 0 does not work

React Native version: 0.61.4 (also tried with 0.61.2)

Steps To Reproduce

On Android, render a component with scale 0

Describe what you expected to happen:
The item should not be visible. This works fine on iOS.
What actually happens:
The item renders normal size. Changing the value to something like 0.0001 works, but too many zeros will break it. Also the threshold for the number of zeros that break it seems to be related to how complex the children are but I'm not 100% sure with this one. I just know that some of my views break even with scale set to 0.1.
This seems very similar to https://github.com/facebook/react-native/issues/6278 but it looks like that issue was supposedly fixed by https://github.com/facebook/react-native/commit/ab80001c905dbfb9354232c7a6c7e887736642b5
Snack, code example, screenshot, or link to a repository:
I have been unable to reproduce this in a basic example so I will paste one of the use cases along with some gifs.
Component being rendered:
import React, { Component } from 'react';
import { Animated } from 'react-native';

import style from './loading.style';

const dotKeys = ['dotOne', 'dotTwo', 'dotThree'];
const dotMin = 1;
const dotMax = 1.5;
const duration = 250;

const flatten = arr => [].concat(...arr);

export class Loading extends Component {
  private timeout: any;

  state = {
    hidden: true,
    width: new Animated.Value(0.00001),
    dotOne: new Animated.Value(1),
    dotTwo: new Animated.Value(1),
    dotThree: new Animated.Value(1),
  };

  componentDidMount() {
    this.timeout = setTimeout(() => {
      this.setState({ hidden: false });
    }, 2000);
  }

  componentWillUnmount() {
    clearTimeout(this.timeout);
  }

  componentDidUpdate(_, { hidden: prevHidden }) {
    if (prevHidden && !this.state.hidden) {
      const appear = Animated.timing(this.state.width, {
        toValue: 1,
        duration: 100,
        useNativeDriver: true,
      });
      const animations = dotKeys.map(dotKey => [
        Animated.timing(this.state[dotKey], {
          toValue: dotMax,
          duration,
          useNativeDriver: true,
        }),
        Animated.timing(this.state[dotKey], {
          toValue: dotMin,
          duration,
          useNativeDriver: true,
        }),
      ]);
      appear.start(() => {
        Animated.loop(Animated.sequence(flatten(animations))).start();
      });
    }
  }

  render() {
    return (
      <Animated.View style={[style.container, { transform: [{ scaleX: this.state.width }] }]}>
        {dotKeys.map(dotKey => (
          <Animated.View key={dotKey} style={[style.dot, { transform: [{ scale: this.state[dotKey] }] }]} />
        ))}
      </Animated.View>
    );
  }
}

============================================
Gifs
Working:

Broke - Scale 0:

Broke - Scale Nearly 0:

+1

For some reason this also happen with the initial value of an opacity animation on Android.
Fading out a view with an initial value of 1 doesn't work. 0.99 works fine.

I think React Native Paper had problems with this too: https://github.com/callstack/react-native-paper/pull/1440

+1

Here's a snack that reproduces the problem for me on a Galaxy S8:
https://snack.expo.io/@wodin/rn-27146
It seems there might be a race condition involved, because sometimes deleting/changing lines that should have no effect and then reloading causes the scaleX: 0 Blocks to be different lengths. Usually they seem to be the same length as the Block rendered immediately above each scaleX: 0 Block, though.

Just bumped into this! Any workarounds?

The workaround is basically to use 0.1 or 0.01 etc. instead of 0.


Solution for Record Breaker python - Pedro Lucena

Issue Number for which I'm assigned & worked: #7

🚀 merging


Images are not displayed in a table

Images break when they're in a table. They then try to load via http://host:port/file.png
https://user-images.githubusercontent.com/34944988/215868632-ff846f0f-1921-413d-9f3c-ae633623de16.mp4

That’s a different issue, could you create a new issue for it?


experimental client: Write a proper README that describes the package/directory

...and explains the difference between new client and old client

Closed with #1405.

Closed with #1405.


Optimize Chip

https://www.figma.com/file/xZ0IW0MJO0vnFicmrHiKaY/Components?node-id=10370%3A49294&t=siEMKepaonFnEEmr-1

please review @Cian77

See comments on page

thanks for the comments, I worked it trough. could you please have another look at it @Cian77 ?

Input Rouven: Dark mode

could you please check the Figma implementation and the accessibility requirements @Cian77 🙏

[ ] Discuss component variant name

@rouvenpost AX-Check nötig

[ ] how big has the click are to be?

@oliverschuerch, @alizedebray, @imagoiq please take over.

Here are the differences between the Chip component and his sibling, the Badge component.
Architecture

Missing a notion of set or radio group (aka "Filter")
Disabled state should be implemented

Filter type styles to change
General

Gap between items should be 8px
Line-height should use 150% instead of 100%

Per variant
Big/default

Font should use $font-size-regular (16px) instead of 15px
Padding vertical should be 8px instead of 0

Small

Font should be 12px instead of 13px
Padding horizontal should be 12px instead of 7px
Padding vertical should be 7px instead of 8px

Hover

Background should be Black/20% #ccc
Border should black-60 and size 2px

Disabled and not selected

Border should be black-20 and 2px size
Background should be white
Font-color should be black-40

Disabled and selected

Font color should be black-40
Border should be black-20 and 2px size
Background should be background-dark

Focused

Font color should be black
Background should be black-20

Counter/nested badge
Every variant

Counter font color should be black

Big

Counter has an unneeded negative margin
Counter font size should be 12px not 10px (10px is for small variant)
Counter Height should be 24px instead of 22px
Counter should not have vertical padding
Counter horizontal padding should be 8.5px

Small

Gap between icon and text should be 6px not 12px
Counter has an unneeded negative margin
Counter Height should be 16px instead of 22px
Counter should not have vertical padding
Counter horizontal padding should be 5px

Hover

Border should be border black-60 and 2px size
Counter should not have a border
Counter should have a white background

Focus

Similar to default focused state
Counter should be similar to counter hover state

Disabled and not selected

Similar to "Disabled and not selected"
Counter background should be background-dark

Disabled and selected

Similar to "Disabled and selected"
Counter background should be white

Input type styles to change

Dismissible action should be before the text
Click area from dismissible action should be 44px instead of 24px
Gap between items should be 8px
Icon should come from post
Icon should have black-80% color
Padding-start of the icon should be 8px
Icon should not have negative margin

Per variant
Small
*Icon size should be 16px
Hover
*Round background with black-20
Focused
*Same as hover state
*Border + outline similar as other Filter variants

Dev changes: https://github.com/swisspost/design-system/issues/1864

UX tasks:

[ ] write a documentation for the component
[ ] publish the component


[Sema] Quick conditional conformance associated type inference fix

Always allow the extension where a conformance is declared to be checked for witnesses to that conformance.

Resolves SR-8337.
(Previously the code in that bug failed because isExtensionUsableForInference() returned false just after the added check since it is constrained. Presumably when the TODO for 'is as specialized as'  gets implemented it would be equally specialized and this identity test could be reverted, if desired.)

@swift-ci Please smoke test and merge.

@DougGregor Thanks!


add app icon

the icon that would appear on your phone home screen

Is your feature request related to a problem? Please describe.
The app does not have an icon, splash screen, or appropriate title for the home screen.
Describe the solution you'd like
Add the app icon, title, and splash screen for android and IOS
Additional context
We will need to get an icon from the Hendrix Today people or make one if we do not already have one.

I think using a lowercase white h from the Museo Slab thick font, with an orange background, would look nice. Something like this:

Here's my current version

I didn't realize you were working on this but ended up making something remarkably similar:

I made it in MS Paint, so it might be a bit off-balance.

Cleaned up the ht logo version


Feature Request -- Export Info Field

It would be helpful if we could export the "Info" field as well in the CSV. So when someone asks to see DNS requests to specific domains or specific URI/URLs those can be provided along with the Source/Destination IP info.
Thank you,
Suchit

This has been implemented. The csv now contains the columns that are displayed in the sessions table. So, if the info column is present when exporting the csv, all the fields that are displayed in the info column will be in the csv.
Please let me know if this does not address your issue.


Self-compiled version of VSCode fails to launch extension host on Arch Linux

VSCode Version: 1.1.0-insider
OS Version: Arch Linux (kernel 4.5.4-ck)

Hi,
I installed VSCode using this PKGBUILD and while VSCode seems to be running fine, I have noticed that whenever I try to install extensions in the command pallette by typing ext install ... (where ... is the extension's name) I get the result "No extensions found". To get some debugging information I ran scripts/code.sh, which returned (only including the last few lines of code as they are those that include an error):
atever hasn't been checked yet
[22:51:17] [tsb] time: 24351ms mem: 659MB Δ621
*** Finished with 0 errors.
[22:51:19] Finished 'compile-client' after 30 s
[22:51:19] Starting 'compile'...
[22:51:19] Finished 'compile' after 7.43 μs
[14903:0512/225119:ERROR:browser_main_loop.cc(217)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the sandbox on.
[14903:0512/225123:INFO:CONSOLE(207)] "%c[Extension Host] %cdebugger listening on port 5870", source: file:////home/fusion809/GitHub/mine/PKGBUILDs/visual-studio-code-oss/src/vscode-1.1.0-insider/out/vs/workbench/services/thread/electron-browser/threadService.js (207)

the last line is what I think is most relevant to this extension issue. How do I fix it? Is there some command I should have run while building VSCode besides scripts/npm.sh install and gulp vscode-linux-x64.
Thanks for your time,
Brenton

ping @Tyriar

The OSS build does not specify the extensions marketplace is the issue. I think the reasoning behind this is to do with licensing. Leaving open for @joaomoreno for further comment when he's back.

Exactly. Extension gallery is an official product thing only. I wanna change this. cc @chrisdias

@joaomoreno ditto

Hello @chrisdias,
I'm felinus jeong.
I got the same issue.
Did you fix this issue?
Best regards,
Felinus Jeong

Just add extensions config in the product.json (under buildout/resources/app/) and reload app.
"extensionsGallery": {
    "serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
    "cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
    "itemUrl": "https://marketplace.visualstudio.com/items"
},
"extensionTips": {
    "ms-vscode.csharp": "{**/*.cs,**/project.json,**/global.json,**/*.csproj,**/*.sln,**/appsettings.json}",
    "ms-vscode.mono-debug": "{**/*.cs,**/*.csproj,**/*.sln}",
    "msjsdiag.debugger-for-chrome": "{**/*.ts,**/*.tsx**/*.js,**/*.jsx,**/*.es6,**/.babelrc}",
    "lukehoban.Go": "**/*.go",
    "ms-vscode.PowerShell": "{**/*.ps,**/*.ps1,**/*.ps.config,**/*.ps1.config}",
    "austin.code-gnu-global": "{**/*.c,**/*.cpp,**/*.h}",
    "Ionide.Ionide-fsharp": "{**/*.fsx,**/*.fsi,**/*.fs,**/*.ml,**/*.mli}",
    "dbaeumer.vscode-eslint": "{**/*.js,**/*.jsx,**/*.es6,**/.eslintrc.*,**/.eslintrc,**/.babelrc,**/jsconfig.json}",
    "dbaeumer.jshint": "{**/*.js,**/*.jsx,**/*.es6,**/.babelrc,**/jsconfig.json,**/.jshintrc,**/.jshintignore}",
    "eg2.tslint": "{**/*.ts,**/*.tsx,**/tslint.json,**/tsconfig.json}",
    "felixfbecker.php-debug": "{**/*.php,**/php.ini}",
    "ikappas.phpcs": "{**/*.php,**/php.ini}",
    "tht13.python": "{**/*.py}",
    "donjayamanne.python": "{**/*.py}",
    "magicstack.MagicPython": "{**/*.py}",
    "saviorisdead.RustyCode": "{**/*.rs,**/*.rslib}",
    "mitaki28.vscode-clang": "{**/*.cpp,**/*.cc,**/*.h}",
    "ms-vscode.cpptools": "{**/*.c,**/*.cpp,**/*.cc,**/.cxx,**/*.hh,**/*.hpp,**/*.hxx,**/*.h}",
    "ms-vscode.Theme-MarkdownKit": "{**/*.md}",
    "DavidAnson.vscode-markdownlint": "{**/*.md}",
    "PeterJausovec.vscode-docker": "{**/dockerfile,**/Dockerfile,**/docker-compose.yml,**/docker-compose.*.yml}",
    "EditorConfig.EditorConfig": "{**/.editorconfig}",
    "HookyQR.beautify": "{**/.jsbeautifyrc,**/*.js,**/*.jsx,**/*.es6,**/.eslintrc.*,**/.babelrc,**/jsconfig.json}",
    "donjayamanne.githistory": "{**/.gitignore, **/.git}",
    "felipecaputo.git-project-manager": "{**/.gitignore, **/.git}",
    "waderyan.gitblame": "{**/.gitignore, **/.git}",
    "codezombiech.gitignore": "{**/.gitignore, **/.git}",
    "rebornix.Ruby": "{**/*.rb,**/*.erb,**/*.reek,**/.fasterer.yml,**/ruby-lint.yml,**/.rubocop.yml}",
    "lonefy.vscode-JS-CSS-HTML-formatter": "{**/.jsbeautifyrc,**/*.js,**/*.jsx,**/*.es6,**/.eslintrc.*,**/.babelrc,**/jsconfig.json}",
    "DotJoshJohnson.xml": "{**/*.xml}",
    "shinnn.stylelint": "{**/.stylelintrc,**/stylelint.config.js}",
    "eg2.vscode-npm-script": "{**/package.json}",
    "fknop.vscode-npm": "{**/package.json}",
    "donjayamanne.bower": "{**/.bowerrc}",
    "ms-mssql.mssql": "{**/*.sql}",
    "ms-vscode.jscs": "{**/.jscsrc}",
    "waderyan.babelrc": "{**/.babelrc}",
    "ms-vscode.sublime-keybindings": "{**/.sublime-project, **/.sublime-workspace}",
    "k--kato.intellij-idea-keybindings": "{**/.idea}",
    "dzannotti.vscode-babel-coloring": "{**/.babelrc}",
    "christian-kohler.npm-intellisense": "{**/package.json}"
},
"extensionImportantTips": {
    "ms-vscode.csharp": {
        "name": "C#",
        "pattern": "{**/*.cs,**/project.json,**/global.json,**/*.csproj,**/*.sln}"
    },
    "lukehoban.Go": {
        "name": "Go",
        "pattern": "**/*.go"
    },
    "donjayamanne.python": {
        "name": "Python",
        "pattern": "{**/*.py}"
    },
    "redhat.java": {
        "name": "Language Support for Java(TM) by Red Hat",
        "pattern": "{**/*.java}"
    },
    "ms-vscode.PowerShell": {
        "name": "PowerShell",
        "pattern": "{**/*.ps,**/*.ps1}"
    },
    "ms-vscode.cpptools": {
        "name": "C/C++",
        "pattern": "{**/*.c,**/*.cpp,**/*.cc,**/.cxx,**/*.hh,**/*.hpp,**/*.hxx,**/*.h}"
    },
    "PeterJausovec.vscode-docker": {
        "name": "Docker",
        "pattern": "{**/dockerfile,**/Dockerfile,**/docker-compose.yml,**/docker-compose.*.yml}"
    },
    "ms-mssql.mssql": {
        "name": "SQL",
        "pattern": "{**/*.sql}"
    }
},
"keymapExtensionTips": [
    "vscodevim.vim",
    "ms-vscode.sublime-keybindings",
    "ms-vscode.atom-keybindings",
    "ms-vscode.vs-keybindings",
    "k--kato.intellij-idea-keybindings",
    "hiro-sun.vscode-emacs",
    "alphabotsec.vscode-eclipse-keybindings",
    "alefragnani.delphi-keybindings"
],
"extensionKeywords": {
    "md": [
        "Markdown"
    ],
    "js": [
        "JavaScript"
    ],
    "jsx": [
        "JavaScript"
    ],
    "es6": [
        "JavaScript"
    ],
    "html": [
        "Html"
    ],
    "ts": [
        "TypeScript"
    ],
    "tsx": [
        "TypeScript"
    ],
    "css": [
        "CSS"
    ],
    "scss": [
        "SASS"
    ],
    "txt": [
        "Text"
    ],
    "php": [
        "PHP"
    ],
    "php3": [
        "PHP"
    ],
    "php4": [
        "PHP"
    ],
    "ph3": [
        "PHP"
    ],
    "ph4": [
        "PHP"
    ],
    "xml": [
        "XML"
    ],
    "py": [
        "Python"
    ],
    "pyc": [
        "Python"
    ],
    "pyd": [
        "Python"
    ],
    "pyo": [
        "Python"
    ],
    "pyw": [
        "Python"
    ],
    "pyz": [
        "Python"
    ],
    "java": [
        "Java"
    ],
    "class": [
        "Java"
    ],
    "jar": [
        "Java"
    ],
    "c": [
        "c",
        "objective c",
        "objective-c"
    ],
    "m": [
        "objective c",
        "objective-c"
    ],
    "mm": [
        "objective c",
        "objective-c"
    ],
    "cpp": [
        "cpp",
        "c plus plus",
        "c",
        "c++"
    ],
    "cc": [
        "cpp",
        "c plus plus",
        "c",
        "c++"
    ],
    "cxx": [
        "cpp",
        "c plus plus",
        "c++"
    ],
    "hh": [
        "cpp",
        "c plus plus",
        "c++"
    ],
    "hpp": [
        "cpp",
        "c++"
    ],
    "h": [
        "cpp",
        "c plus plus",
        "c++",
        "c",
        "objective c",
        "objective-c"
    ],
    "sql": [
        "sql"
    ],
    "sh": [
        "bash"
    ],
    "bash": [
        "bash"
    ],
    "zsh": [
        "bash",
        "zshell"
    ],
    "cs": [
        "c#",
        "csharp"
    ],
    "csproj": [
        "c#",
        "csharp"
    ],
    "sln": [
        "c#",
        "csharp"
    ],
    "go": [
        "go"
    ],
    "sty": [
        "latex"
    ],
    "tex": [
        "latex"
    ],
    "ps": [
        "powershell"
    ],
    "ps1": [
        "powershell"
    ],
    "rs": [
        "rust"
    ],
    "rslib": [
        "rust"
    ],
    "hs": [
        "haskell"
    ],
    "lhs": [
        "haskell"
    ],
    "scm": [
        "scheme"
    ],
    "ss": [
        "scheme"
    ],
    "clj": [
        "clojure"
    ],
    "cljs": [
        "clojure"
    ],
    "cljc": [
        "clojure"
    ],
    "edn": [
        "clojure"
    ],
    "erl": [
        "erlang"
    ],
    "hrl": [
        "erlang"
    ],
    "scala": [
        "scala"
    ],
    "sc": [
        "scala"
    ],
    "pl": [
        "perl"
    ],
    "pm": [
        "perl"
    ],
    "t": [
        "perl"
    ],
    "pod": [
        "perl"
    ],
    "groovy": [
        "groovy"
    ],
    "swift": [
        "swift"
    ],
    "rb": [
        "ruby"
    ],
    "rbw": [
        "ruby"
    ],
    "jl": [
        "julia"
    ],
    "f": [
        "fortran"
    ],
    "for": [
        "fortran"
    ],
    "f90": [
        "fortran"
    ],
    "f95": [
        "fortran"
    ],
    "coffee": [
        "CoffeeScript"
    ],
    "litcoffee": [
        "CoffeeScript"
    ],
    "yaml": [
        "yaml"
    ],
    "yml": [
        "yaml"
    ],
    "dart": [
        "dart"
    ],
    "json": [
        "json"
    ]
},

Closing due to inactivity, nothing will be done here.


[INTERNAL] ComponentContainer: JSDoc link fix

Previously, the link was pointing to https://<demokithost>/api/sap.ui.core.ComponentSupport which doesn't exist.
Fixes: https://github.com/SAP/openui5/issues/2908

Merged.


Add wavelength-dependent limb-darkening to inject_transit

Since I don't think we're aiming to do super fancy fitting, I'd vote that it's probably OK just to go with quadratic limb-darkening, maybe feeding in the two coefficients in the same way you do the planet_radius?

Closed by #21 !


Mention somewhere that TWEAK should not be used in roles (trap?)

Context: https://github.com/perl6/whateverable/blob/177b77cb2ebc045736b8e7a1cf6eb8e25fdce7b6/lib/Whateverable.pm6#L77
IRC discussion: https://irclog.perlgeek.de/perl6-dev/2018-02-24#i_15854365
To be honest I'm not even sure if this is something that should be doc-ed. I consider it as a bug. But still, that's a too major thingie for it to be mentioned nowhere at all.

Maybe in the Roles page? Is that the only thing that can't be used in Roles?

OK, I read the discussion. The situation right now is that TWEAK (or any submethod) overwrites that of the class it's mixed into. The ideal situation would be one in which all mixed-in TWEAKs are "glommed" together (whatever that means). I don't think this is really a NOTSPECCED, it's rather a wishlist. The situation now is that it's better not to TWEAK in roles. Can I document that as a trap?

Ref #2601


feat: removed stabetokenregistry code

Description
removed StableTokenRegistry contract/proxy/test/migrations across the codebase, since there was no more need for it.
Other changes
n/a
Tested
n/a
Related issues

Fixes 85

Backwards compatibility
n/a
Documentation
n/a

This was just left off off the other reversion pr right?

hey @aaronmgdr yes but looks like the ci isn't happy so have to look into that tomorrow.


rpc server metrics impl

skeleton draft PR for #3907, please excuse the formatting changes my IDE's auto save rust fmt applied. If needbe - I can change to the repo's fmt standard, not sure what's different with my setup
@mattsse if this looks on the right path I can keep at it - questions I have rn revolve around:

does the adding type param RpcServerMetrics to the jsonrpsee::server::Server<Identity, L: ()> in WsHttpServerKind seem OK or is there a cleaner way to do it

the metrics scope implementation rn changes relative to whether the WS/HTTP servers are combined or not, should it be that way?

and generally haven't started thinking through what exact metrics we want to track in RpcServerMetrics

rebased against mainline and pushed up to pull in the commits that were just merged in

ah I see - my rust-analyzer plugin should've picked up those warnings/compiler errors that you fixed, but it was yelling about some other issue which I didn't notice:

I assumed it was all good and didn't rerun a cargo build woops.
thanks for the touchups


footer was removed from the playgamepage need to render it again

this will be a bitch... of course :(

fixed with https://github.com/simon-kyger/brawlhallacrewbattle/commit/235a9bb9614e0b207adb2b716cf393b14813c382


Phoebemirman/ch15193/adjust orphaned order workflow

https://app.clubhouse.io/augur/story/15193/adjust-orphaned-order-workflow

Coverage remained the same at 66.553% when pulling 4589c917a0713fa13cb0a2b2187dc4631efbce53 on phoebemirman/ch15193/adjust-orphaned-order-workflow into 9dca068bd2b6cd09e0e42bfacc503f66da7efd72 on master.

Still lgtm


Fix update checker not working when no new primary file is found

Hey, I noticed the update checker will crash when there is no new file marked as a primary file (I'm not sure why this would happen, but it does, apparently). This PR fixes this by ignoring that specific case.
[21:18:24] [Worker-Main-1/ERROR]: Caught exception in thread Thread[#73,Worker-Main-1,5,main]
java.util.NoSuchElementException: No value present
	at java.util.Optional.get(Optional.java:143) ~[?:?]
	at com.terraformersmc.modmenu.util.ModrinthUtil.lambda$checkForUpdates$4(ModrinthUtil.java:86) ~[transformed-mod-modmenu.i0:0/:?]
	at java.util.Map.forEach(Map.java:716) ~[?:?]
	at com.terraformersmc.modmenu.util.ModrinthUtil.lambda$checkForUpdates$5(ModrinthUtil.java:79) ~[transformed-mod-modmenu.i0:0/:?]
	at java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1423) ~[?:?]
	at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387) ~[?:?]
	at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312) ~[?:?]
	at java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843) ~[?:?]
	at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808) ~[?:?]
	at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188) ~[?:?]

Seems other people also ran into it at #607.


Other Linux OSes

Does this procedure basically work on other Linux OSes as well? We have a customer asking about CentOS.
From general searches it seems like the initial installation commands are different (i.e. using yum not sudo?) but are the steps under "Generate and export certificates" the same once you have strongswan installed?

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

ID: ff2a3f07-8dd7-a2f9-236d-4e6dc3c8bdec
Version Independent ID: b442cc75-f969-ca55-7416-b91d79c6e3a5
Content: Generate and export certificates for Point-to-Site: Linux: CLI: Azure
Content Source: articles/vpn-gateway/vpn-gateway-certificates-point-to-site-linux.md
Service: vpn-gateway
GitHub Login: @anzaman
Microsoft Alias: alzam

@dcbrown16 , We are looking into this query and will update you as soon as possible.

@dcbrown16 , Appreciate your patience. Strongswan for CentOS is a bit different while installing Strongswan and setting up the IPSEC configuration. I have reproduced your scenario and here are the commands for CentOS,
Install Strongswan on CentOS:
yum -y install epel-release
yum -y install strongswan

Use the following command to install the Azure command-line interface:
sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
sudo sh -c 'echo -e "[azure-cli]
name=Azure CLI
baseurl=https://packages.microsoft.com/yumrepos/azure-cli
enabled=1
gpgcheck=1
gpgkey=https://packages.microsoft.com/keys/microsoft.asc" > /etc/yum.repos.d/azure-cli.repo'
sudo yum install azure-cli

Generate and export certificates,
strongswan pki --gen --outform der > caKey.pem
strongswan pki --self --in caKey.pem --dn "CN=VPN CA" --ca --outform pem > caCert.pem

Print the CA certificate in base64 format. This is the format that is supported by Azure. You upload this certificate to Azure as part of the P2S configuration steps.
openssl x509 -in caCert.pem -outform der | base64 -w0 ; echo

Generate the user certificate.
export PASSWORD="password"
export USERNAME="client"
Strongswan pki --gen --outform pem > "${USERNAME}Key.pem"
Strongswan pki --pub --in "${USERNAME}Key.pem" | Strongswan pki --issue --cacert caCert.pem --cakey caKey.pem --dn "CN=${USERNAME}" --san "${USERNAME}" --flag clientAuth --outform pem > "${USERNAME}Cert.pem"

Generate a p12 bundle containing the user certificate. This bundle will be used in the next steps when working with the client configuration files.
openssl pkcs12 -in "${USERNAME}Cert.pem" -inkey "${USERNAME}Key.pem" -certfile caCert.pem -export -out "${USERNAME}.p12" -password "pass:${PASSWORD}"

We are closing this issue for now.If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


[1.16.5] Mod attempting to load non-existent config files

Versions

Minecraft: 1.16.5 Dedicated Server
Forge: 36.2.23
Botania: Botania-1.16.5-420.2
Botanical Machinery: botanicalmachinery-1.16.4-0.4.4
LibX: LibX-1.16.3-1.0.76
Modpack: Custom ATM6

Describe the bug

Log is showing the mod is complaining about the config being incorrect, but it appears to be looking in the wrong place?
[13:29:44] [modloading-worker-27/WARN]: Configuration file \Minecraft\config\botanicalmachinery-client.toml is not correct. Correcting
[13:29:44] [modloading-worker-27/WARN]: Incorrect key numericalMana was corrected from null to its default, true.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key advanced-rendering was corrected from null to its default, SimpleCommentedConfig:{}.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key advanced-rendering.all was corrected from null to its default, true.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key advanced-rendering.alfheim-market was corrected from null to its default, true.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key advanced-rendering.industrial-agglomeration-factory was corrected from null to its default, true.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key advanced-rendering.mechanical-apothecary was corrected from null to its default, true.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key advanced-rendering.mechanical-brewery was corrected from null to its default, true.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key advanced-rendering.mechanical-daisy was corrected from null to its default, true.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key advanced-rendering.mechanical-mana-pool was corrected from null to its default, true.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key advanced-rendering.mechanical-runic-altar was corrected from null to its default, true.
[13:29:44] [modloading-worker-27/WARN]: Configuration file \Minecraft\defaultconfigs\botanicalmachinery-server.toml is not correct. Correcting
[13:29:44] [modloading-worker-27/WARN]: Incorrect key working-duration-multiplier was corrected from null to its default, SimpleCommentedConfig:{}.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key working-duration-multiplier.alfheim-market was corrected from null to its default, 1.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key working-duration-multiplier.industrial-agglomeration-factory was corrected from null to its default, 1.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key working-duration-multiplier.mechanical-mana-pool was corrected from null to its default, 1.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key working-duration-multiplier.mechanical-runic-altar was corrected from null to its default, 1.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key working-duration-multiplier.mechanical-daisy was corrected from null to its default, 3.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key working-duration-multiplier.mechanical-brewery was corrected from null to its default, 1.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key working-duration-multiplier.mechanical-apothecary was corrected from null to its default, 1.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key alfheim-market was corrected from null to its default, SimpleCommentedConfig:{}.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key alfheim-market.recipe-cost was corrected from null to its default, 500.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key max-mana-capacity was corrected from null to its default, SimpleCommentedConfig:{}.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key max-mana-capacity.alfheim-market was corrected from null to its default, 100000.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key max-mana-capacity.industrial-agglomeration-factory was corrected from null to its default, 1000000.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key max-mana-capacity.mechanical-mana-pool was corrected from null to its default, 100000.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key max-mana-capacity.mechanical-runic-altar was corrected from null to its default, 250000.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key max-mana-capacity.mechanical-brewery was corrected from null to its default, 100000.
[13:29:44] [modloading-worker-27/WARN]: Incorrect key max-mana-capacity.mana-battery was corrected from null to its default, 10000000.

Meanwhile configs are actually located in:
"\Minecraft\config\botanicalmachinery\client.json5"
"\Minecraft\config\botanicalmachinery\server.json5"
However, for the server config, should that not be loaded from "\Minecraft\world\serverconfig\botanicalmachinery-server.toml", which does exist- if it is loading that later on, it is never mentioned in the logs.
How to reproduce

Add mods.
Start dedicated server
Watch logs.

Expected behavior

Loading the correct configs from the correct location
Screenshots

N/A

I think it was enough time for everyone to switch to newer versions. I think I could remove the old config now. Thank you for this reminder, will remove the old config soon.


OR-39: W3C Context Push Method

Create a method that handles W3C and other standard context pushing in switch statment; follows similar design to context pushing conditionals in cheqd resolver
Create mock context for test sets
Create set of unit tests
Document

whoop whoop
On Fri, Apr 19, 2024, 1:03 PM Adrian Ross @.***> wrote:

@.**** approved this pull request.
No more comments yay!
—
Reply to this email directly, view it on GitHub
https://github.com/mikeKaufman310/aries-framework-oracle/pull/3#pullrequestreview-2011948310,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVWTGN5Z5J2QTLZAOUYFPS3Y6FE5DAVCNFSM6AAAAABGGPK4BKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDAMJRHE2DQMZRGA
.
You are receiving this because you authored the thread.Message ID:
@.***
com>


Getting error when container is body

When i use data-container="body", Uncaught TypeError: Cannot read property 'jquery' of undefined pops up and dropdown doesn't show up, basically .show class doesn't toggle. This JS error comes from bootstrap.bundle.min.js, not from plugin itself.
Is this a known bug or something local on my side?

Did not tried the data-container attribute yet. But you are right it is not working. Tried to fix, without success yet. The problem is inside selectPosition() where the element is moved inside the bs-container that is appended to the container. The dropdown already created and attached to the button. Popper requires providing an invalid element as reference or popper. The moment the element is moved, reference seems to be broken.

Perhaps updating dropdown position will help, if popper causes the issue.

Nope already tried that. Currentl short on time, will give this later a view.


Fix tree reporter line highlighting

Update tree reporter snapshots for Textual 0.49 (the TextArea no longer shows a cursor - yay!) and fix two bugs I noticed while looking at the snapshot diff: sometimes we don't show any lines, and sometimes we highlight the wrong line! Whoops.

My test program for making sure the line number handling is now right was:
import mmap

def a():
    b()
    b()

def b():
    c()

def c():
    e()

def e():
    f()

def f():
    g()

def g():
    h()

def h():
    i()

def i():
    j()

def j():
    mmap.mmap(-1, 1024 * 1024)

a()

That made it easy to test both the case where there's not enough lines above the active frame's line to fill out our context and the case where there are (and the case where the active frame's line is close to the end of the file rather than the start, too, but that doesn't need any special handling).

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

Comparison is base (41248ed) 92.55% compared to head (d6f05d1) 92.68%.
Report is 6 commits behind head on main.

Files
Patch %
Lines

src/memray/reporters/tree.py
72.72%
3 Missing :warning:

tests/conftest.py
75.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #544      +/-   ##
==========================================
+ Coverage   92.55%   92.68%   +0.13%
==========================================
  Files          91       91
  Lines       11304    11111     -193
  Branches     1581     2022     +441
==========================================
- Hits        10462    10298     -164
+ Misses        837      813      -24
+ Partials        5        0       -5

Flag
Coverage Δ

cpp
92.68% <78.94%> (+6.74%)
:arrow_up:

python_and_cython
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Action bar is pushed off screen when editing the multiline text box

Relevant to the EditSectionActivity too.

Fixed in #80.


[CONTRIB] NNPack Test Flaky

http://ci.tvm.ai:8080/job/tvm/job/PR-2103/1/consoleText
cc @ajtulloch can you take a look?

The error is nnp_status_unsupported_hardware, I’ll send a diff which exposes nnp_initialize() to TVM and add a check that nnp_initialize succeeds before invoking the rest of the year. Does that sound good?

that sounds good

Fix in https://github.com/dmlc/tvm/pull/2119/


Add futures crate to playground.

I don't know what your policy is for adding more crates but it seems like a good idea to have futures since it underpins the async ecosystem.

I don't know what your policy is

From the README:

The top 100 popular crates (ranked by all-time downloads) and their dependencies are available for use

Closing as a dupe of #101.


Reroute Users to Application Page If Authenticated

If the user is already authenticated with IntelliSlides, then it would be nice to reroute them to the app page instead of the landing page.

The PR for this was successfully made, reviewed, and merged. Thanks @alittlerocket!


Corvus key distribution algorithm

Hi.
We are currently working with nutcracker (twemproxy) in order to create our own redis cluster. However we are experiencing some scaling problems due to twemproxy is not multithreaded. In order to start testing with Corvus using the same existing cluster, we would like to know which key distribution algorithm is being used currently in order to know if we can use the same existing cluster to test in parallel both solutions.
If corvus use ketama as algorithm we would use is without any complex migration procedure for our persistent keys.
Thanks in advance.

Corvus is a proxy for cluster mode Redis(>=3.0). So the key distribution algorithm is determined by the sharding mechanism of Redis. And I think you have to prepare a migration process as the ketama algorithm is not used by Redis.

OK, totally understood. Twemproxy does not use redis cluster and so distribution is done by proxy.
If we want to migrate to Corvus we should take care of non-persistent keys currently inside our twmproxied redis cluster.


Version * for package not found.

Greetings!
I use a self-hosted Repman.
I have a package with the tag 1.0.0 in my self-hosted Gitlab.
After I add this package to Repman, I get an error: RuntimeException - Version <IP_ADDRESS> for package {package-name} not found.
What could be the problem?
Thanks in advance.

Can you write in what environment the application works? (docker ?, vm?, have you used ansible?)
Please check:

symfony logs in var/log/prod.log
is distribution file exist in var/repo dir?
is version exist in database?

Same here, launched repman with docker-compose. Everything works fine with github packages, but packages from our private bitbucket errors

nothing in logs:
<IP_ADDRESS> -  30/Jul/2021:02:55:36 +0000 "POST /index.php" 302

I experience the same problem. The version reported in error is always with one or more 0 than what really should be.
In the repo I have arleady tag with 1.1 and Repman reports that 1.1 as a version but shows also the error for missing version <IP_ADDRESS>
How can we solve this problem?

I forgot to mention that I run it on Docker

@akondas
I face the same problem.
Running RepMan locally with docker (any version), no ansible.
Symfony logs (consumer.log, prod.log) do not contain relevant information regarding this issue.
There are package-name.json files under var/repo.
Packages exists in database but no version exits inside organization_package_version table.
I can provide more information if needed. A few months ago everything worked fine.

I have the same issue. Running repman locally with docker.
My repository type by the way is git. The git server is gitlab.

@akondas for us this was related to a problem with the docker-image setup. The cron runs as root whilst php-fpm runs under a different user. Since /var/ is mounted between the images this causes permissions issues.
There are a couple of other problems relating to this issue as well, I think tweaking the docker-composer.yml will fix most of these issues!

Estou com o mesmo problema! alguem pode me auxiliar ?


Support custom statuses

PR for #3625
Added the possibility to set custom status from command line option --addstatus. The new status is set based on tags and displayed both in console output and log.html. The color can be customized but only in the log file, in console it maintains the old colors.

Codecov Report

Merging #3869 (f17e11a) into master (0fabf9f) will decrease coverage by 0.46%.
The diff coverage is 48.94%.

@@            Coverage Diff             @@
##           master    #3869      +/-   ##
==========================================
- Coverage   75.27%   74.82%   -0.45%
==========================================
  Files         222      221       -1
  Lines       18716    18710       -6
  Branches     3036     3040       +4
==========================================
- Hits        14087    13998      -89
- Misses       4096     4159      +63
- Partials      533      553      +20

Impacted Files
Coverage Δ

src/robot/run.py
80.40% <ø> (ø)

src/robot/running/suiterunner.py
74.36% <ø> (ø)

src/robot/running/status.py
69.46% <33.34%> (-2.35%)
:arrow_down:

src/robot/conf/settings.py
70.77% <42.86%> (-1.51%)
:arrow_down:

src/robot/running/statusreporter.py
82.09% <60.00%> (+0.28%)
:arrow_up:

src/robot/output/console/highlighting.py
70.68% <100.00%> (-4.51%)
:arrow_down:

src/robot/reporting/jsmodelbuilders.py
98.24% <100.00%> (-0.01%)
:arrow_down:

src/robot/utils/encodingsniffer.py
66.16% <0.00%> (-21.53%)
:arrow_down:

src/robot/utils/robotinspect.py
47.62% <0.00%> (-19.04%)
:arrow_down:

src/robot/version.py
55.56% <0.00%> (-11.11%)
:arrow_down:

... and 11 more

Continue to review full report at Codecov.

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

The hard part with this issue is designing how to store information about custom statuses internally. For example, should the status attribute tests have get these custom statuses or should it always be one of the base statuses PASS/FAIL/SKIP? The former initially feels better, but it would require changes in all code looking for statuses. In the latter case test could/should have a separate attribute that returns possible custom status based on configs and test base status and tags. We could consider renaming the current status to e.g. base_status and using status with the new attribute, though.
We also need to design how to pass the custom status information to tests. Most likely it could be given to the top level result suite where tests could query it. We used similar approach with criticality information earlier.
We can discuss all this further here or on Slack. It seems pretty clear that there's so much work still to be done that it's nevertheless best to move this issue from RF 4.1 to RF 5.0 scope.


How to include styling in a component-like way

I'm Submitting a ...

[ ] Bug report
[ ] Feature request
[ X ] Support request

Other than including the CSS globally in the head of the HTML document, how can we getting working in a react/component like way? I've tried using css-loader and styled-components without much luck.

Hi
If you are using Webpack (I assume you are as you're using css-loader), you should be able to require/import react-datetime/css/react-datetime.css from a js file and Webpack will add it to your bundle or extracted CSS file like any other CSS that you import.
You can also import from within an SCSS file using @import "~react-datetime/css/react-datetime";.  I have a global SCSS styles file in my project and am using this method as I import the react-datetime js file from several js components in my project.
Cheers,
Bren

So you're adding the wrapper in case you want to switch out this DateTime for another later on? Not sure if I understood that correctly.
So here's what my code looks like, styling is not applied.
import Datetime from 'react-datetime';
import 'react-datetime/css/react-datetime.css'

export default class EventSearchForm extends React.Component {
  render() {
    return (
      <div>
        <Datetime/>
      </div>
     );
}

If I instead use
import styles from 'react-datetime/css/react-datetime.css'
...
<Datetime className={styles.rdt} />

No improvements are made. Am I doing this wrong, or is there probably an issue with my Webpack/CSS loading dependencies not working?

It seems like its a problem with your webpack setup.
Are you including other css/scss files ok or are you using some CSS in JS system?
Are you using the Webpack ExtractTextPlugin and not adding the output css file in your HTML?
Cheers,
Bren

I am using Webpacker 3.0 in a Rails 5.1 App. Just tried to integrate this Webpack configuration for my dev environment.js: https://github.com/rails/webpacker/issues/756 . Unfortunately that doesn't seem to be working. I am using styled-components but also have css-loader installed locally. My package.json:
{
  "name": "asdf",
  "private": true,
  "dependencies": {
    "@rails/webpacker": "^3.0.1",
    "moment": "^2.18.1",
    "prop-types": "^15.6.0",
    "react": "^16.0.0",
    "react-datetime": "^2.10.3",
    "react-dom": "^16.0.0",
    "react-google-maps": "^8.3.4",
    "styled-components": "^2.2.1"
  },
  "devDependencies": {
    "babel-plugin-styled-components": "^1.2.1",
    "babel-preset-react": "^6.24.1",
    "css-loader": "^0.28.7",
    "webpack-dev-server": "^2.9.1",
    "webpack-merge": "^4.1.0"
  }
}

It was an issue with my Rails setup. Got it all working here - https://github.com/rails/webpacker/issues/775#issuecomment-336904122. Now I'm facing the issue of styling an external library's child elements given that react/css-loader seemingly can only style the top level className

From your list of dependencies, I think the problem is your webpack config's CSS module rule. You normally use css-loader with style-loader (https://github.com/webpack-contrib/style-loader).  Something like:
  module: {
    rules: [
      {
        test: /\.js$/,
        use: 'babel-loader',
        exclude: /(node_modules/
      },
      {
        test: /\.css$/,
        use: ['style-loader', 'css-loader']
      },
      ...
    ]
  }

This Stack Overflow post explains it well:
https://stackoverflow.com/questions/34039826/webpack-style-loader-vs-css-loader
css-loader just loads the css file as a module into your source but doesn't really do anything with it.  style-loader takes the output of css-loader and wraps it in a block of code that inserts it into the HTML DOM's <head> in a <style> tag when that file is run.
You can also add sass-loader to the end of the css loaders and update the test to /\.s?css$/ to support SASS/SCSS styles. There's other loaders for Stylus and other CSS alternatives.  Another helpful loader is postcss-loader along with autoprefixer that will automatically add browser vendor specific prefixes to all your css rules if they are needed (eg css transitions etc).
Instead of using style-loader, you can also extract all of the static CSS into a separate CSS bundle file if you use the Webpack ExtractTextPlugin (npm extract-text-webpack-plugin). You will need to manually add this CSS to your Rail's project's layout file's <head> section like <link rel="stylesheet" href="/assets/bundle.css">. I used to prefer using ExtractTextPlugin to keep CSS out of my JS (reduced code size etc), but now I think it really doesn't matter.  It's more convenient to leave it in and have one less thing to manage the deployed version etc.
If you are using some other CSS in JS library, they may have some other way to import static styles.
Cheers,
Bren

I'm learning this stuff so I had no idea there was a style loader too, thanks for the links! Is there anything I need to do to make style-loader insert into the <head>?
After checking I think style loader is already included. I believe the way it works in Rails is that it has default NPM dependencies and then you can add additional ones in package.json. When I print out the default 'style' loaders this is what I receive.
{ test: /\.(scss|sass|css)$/i,
  use:
   [ { loader: '/home/james/Documents/comity.fit/node_modules/extract-text-webpack-plugin/dist/loader.js',
       options: [Object] },
     { loader: 'style-loader' },
     { loader: 'css-loader', options: [Object] },
     { loader: 'postcss-loader', options: [Object] },
     { loader: 'resolve-url-loader' },
     { loader: 'sass-loader', options: [Object] } ] }

Ok, as you said style-loader must already be installed from some other dependency and is already in the list of loaders for css etc and sass is already supported.  The loaders are applied from last/bottom to top so it seems it already has extract text webpack plugin unless you added this?
You shouldn't use style-loader and extract-text-webpack-plugin at the same time.  If you remove the extract-text-webpack-plugin loader then the style loader should be working.  The styles will be embedded in the JS output bundle (you can search for them in the text to make sure) and when the page loads the JS bundle that you've added to your HTML page, the JS code will add


support severs with different passwords

#9

Thanks for the simple solution. Passing :password property has a side-effect of Redis with no password setup complaining if password is provided, so it kind of breaks backward compatibility but I think it's fine.
Using : as the delimiter requires that we specify the port even when we use the default port, so I'm going to change the format to HOST[:PORT][/PASS]. I'll also remove some code that is no longer necessary with the use of :password property.


feat: support tarfiles of thirdparty dependencies

support tarfiles of thirdparty dependencies
closes https://github.com/aspect-build/rules_js/issues/792

Thanks for the PR!
For future reference, the npm_import in the @npm/:repositories.bzl file generated by npm_translate_lock in the new e2e/vendored_tarfiles e2e test looks like the following:
def npm_repositories():
    "Generated npm_import repository rules corresponding to npm packages in //:pnpm-lock.yaml"
    npm_import(
        name = "npm__lodash__4.17.21",
        root_package = "",
        link_workspace = "",
        link_packages = {
            "": ["lodash"],
        },
        package = "lodash",
        version = "4.17.21",
        url = "file:lodash-4.17.21.tgz",
        npm_translate_lock_repo = "npm",
        integrity = "sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==",
        transitive_closure = {
            "lodash": ["4.17.21"],
        },
    )

with the url set to "file:lodash-4.17.21.tgz" which is passed to the url of rctx.download in npm/private/npm_import.bzl:
    download_url = rctx.attr.url if rctx.attr.url else utils.npm_registry_download_url(rctx.attr.package, rctx.attr.version, {}, utils.default_registry())
    ...
    rctx.download(
        output = _TARBALL_FILENAME,
        url = download_url,
        integrity = rctx.attr.integrity,
        auth = auth,
    )

This looks great. I'll have to land a prefactor so that npm_translate_lock can copy over binary files from data so that this feature will be compatible with update_pnpm_lock = True.: https://github.com/aspect-build/rules_js/pull/819

This looks great. I'll have to land a prefactor so that npm_translate_lock can copy over binary files from data so that this feature will be compatible with update_pnpm_lock = True.: #819

Yeah I was going to comment about this, since I kept getting a corrupt lock file error when update_pnpm_lock = True

Landed #819 so it should work now. I have the additional test case in the main WORKSPACE working in an additional commit and I have rebased this branch so I will force push and this is good to land.


Enabling Continous deployment (CD) for Hyperledger fabric using Spinnaker

Is your feature request related to a problem? Please describe.
Running all the kubectl commands can get repetitive and prone to errors. If we use a tool to deploy the helm charts and k8s manifests using a deployment tool, it will improve the developer workflow.
Describe the solution you'd like
Have Continous Deployment pipelines setup using spinnaker(or any other open-source tool) which deploys the Hyperledger Fabric Network on Kubernetes

@sanusatyadarshi Thanks a lot for this feature request. Could you please clean up the description to be a bit more detailed? And remove the line "A clear and concise.... ", these are for example/guidance only.

Sure.

Thanks. We do use Weaveworks Flux and Ansible so that no kubectl commands are run. If you are going to work on Spinnaker, it will be great if you can add a comparison between Spinnaker and Flux/Ansible.

Sure. I have not used Weaveworks Flux. I have used Ansible but more for configuration management of servers and not as a deployment tool. So I will spend some time to create a comparison between them.
Thanks

@sanusatyadarshi  Are you progressing on this? Otherwise we will be closing the issue as wontfix

Closing this issue as stale. Please re-open if needed.


made diff generic and used it for dist

Not sure that I implemented this in the best way, so check that out. It does a copy (via deref) on both values, there may be a better way.

@kylecarow , nicely done!
@robinsteuteville, check out the cool trait stuff Kyle did in this PR.

@kylecarow - Sorry I'm late looking at this but I'm wondering if you could implement the Diff trait by operating on cloned references instead of copying the underlying type?
pub trait Diff<T> {
    fn diff(&self) -> Vec<T>;
}

impl<T: Sub<Output = T> + Clone> Diff<T> for Vec<T> {
    fn diff(&self) -> Vec<T> {
        self.windows(2)
            .map(|vs| {
                let x = &vs[0];
                let y = &vs[1];
                y.clone() - x.clone()
            })
            .collect()
    }
}

Cloning the reference vs copying a float are probably similar performance wise but it might make a big difference if T is a bigger heap allocated type.

@nreinicke , when we have
    fn diff(&self) -> Vec<T> {
        let mut v_diff: Vec<T> = vec![Default::default()];
        v_diff.extend::<Vec<T>>(
            self.windows(2)
                .map(|vs| {
                    let x = &vs[0];
                    let y = &vs[1];
                    y.clone() - x.clone()
                })
                .collect(),
        );
        v_diff
    }

we get
warning: using `clone` on type `T` which implements the `Copy` trait
   --> fastsim-core/src/traits.rs:393:21
    |
393 |                     y.clone() - x.clone()
    |                     ^^^^^^^^^ help: try dereferencing it: `*y`
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#clone_on_copy
    = note: `#[warn(clippy::clone_on_copy)]` on by default

warning: using `clone` on type `T` which implements the `Copy` trait
   --> fastsim-core/src/traits.rs:393:33
    |
393 |                     y.clone() - x.clone()
    |                                 ^^^^^^^^^ help: try dereferencing it: `*x`
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#clone_on_copy

I guess this makes a good point in that if you're implementing this trait on a datatype that implements Copy, like f64, you're probably better off just doing it the original way (de-referencing) but if you're implementing this on a datatype that is heap allocated and expensive to clone, cloning by reference would be better.


See Image of Donuts

Card:
As a frugal donut-seeker, I want to see the prices of potential donuts I can purchase so I can make the appropriate choice based on my current financial situation.
Conversation:
The prices should be next to the donut so that the price of each donut is clear.
The price should be large enough to see no matter the device.
Donut shops should be able to update the prices of their donuts (but this should probably be its own user story).
The price should be in US dollars, no need to deal with currency conversion.
Confirmation:
If we open the application and can clearly see the prices of the donut and these prices match those of the donut shop.

This looks identical to https://github.com/CMU-17-356/dronuts-2023-krispykopters/issues/6, maybe you posted the wrong user story?

This looks identical to #6, maybe you posted the wrong user story?

Thanks for catching that

Completed as of sprint 1 release


ENH: update package version

Hi! This is the friendly automated conda-forge-webservice.
I've started a version update as instructed in #14.
I'm currently searching for new versions and will update this PR shortly if I find one! Thank you for waiting!
Fixes #14

@conda-forge/nebari team, this one is ready for review?

Thanks @ocefpaf !!!

@jaimergp, sorry for pinging you directly but is there any reason to not update to the latest version? It seems that some folks require this one.

You mean https://github.com/conda-forge/nebari-feedstock/pull/16? I don't think there are any more recent versions.

You mean #16? I don't think there are any more recent versions.

This one was here before the bot automerged one, that's why I missed it. It seems that there is a  new dependency on packaging that the bot did not add though.

Let me check with the team, thanks for the tag!


Getting error: Cannot destructor property 'name' of 'undefined' as it is 'undefined'

In the SQL Console: Message output the following error happens with some basic MySQL DDL failing:
Cannot destructor property 'name' of 'undefined' as it is 'undefined'

The MySQL that is being executed is:
DROP TABLE IF EXISTS album;
CREATE TABLE album (
  id         INT AUTO_INCREMENT NOT NULL,
  title      VARCHAR(128) NOT NULL,
  artist     VARCHAR(255) NOT NULL,
  price      DECIMAL(5,2) NOT NULL,
  PRIMARY KEY (`id`)
);

(This works fine if executed using MySQL CLI.)
To Reproduce
Steps to reproduce the behaviour:

Create MySQL Schema DB and open connection to it
Paste the MySQL SQL code above and execute it
See that it fails with error mentioned above

Expected behaviour
Expected the Script to execute and a new DB Table called 'album' to be created. If the Table already existed it would be dropped and new one created.
No error was expected.
Desktop (please complete the following information):

SQLTools Version v0.23.0
VSCode Version: 1.62.3
OS: Windows 11 (up to date)
Driver:

[ ] MySQL/MariaDB

Database version:  MySQL Community Server v8.0.18

Additional context
After doing some searching around I found that the error message is most likely a Typescript/Javascript one. My project is not using this as its a basic Go project, actually I don't have much in the way of code in it yet and the code I have is working fine.

If it helps, I can add some further experience to the original report. I too am encountering this error when interacting with MySQL (MacOS 12.1, VS Code 1.63.2, SQLTools 0.23.0, SQLTools MySQL/MariaDB 0.2.0, MySQL Community Server 8.0.27).  In my experience, the error arises whenever there are multiple SQL statements in the SQL file being run. With only a single SQL statement in the file, the error does not arise. Also, in every case I've so far encountered where it was not the output of the statements but rather their side effects that concerned me, I have found that the side effects are actually occurring. That is, if I give it several CREATE TABLE statements in a single file, all of the tables will be created as expected, despite the error. However, if the several statements include one or more SELECT statements, I am not able to see their result sets due to the error. With any luck, that will help you narrow things down more efficiently.

See also #864

Fixed in the 0.4.0 MySQL driver which was published today.


[FLOC-3291] Benchmark read request parametization

This PR allows the user to select a method to be called during a benchmark read request operation.  The allowed methods are the zero-parameter methods of the interface IFlockerAPIV1Client.
The default method is the relatively simple version method, but other methods can be set to observe if they behave differently during the benchmarks.

Nice, thanks. Please address comments & merge when tests are OK.