Missing technologies in "map_tec_time" are excluded from capacity calculations

It seems in the GAMS formulation some technologies are omitted from capacity_factor, even though defined by the user. These technologies do not have input, output commodity defined and do not appear in relation_activity; that's why they are not in the set map_tec_time, and hence, mapped out from capacity_factor in this equation. I believe this is not correct, as some technologies can play a role with their capacity, e.g., in parameter relation_total_capacity, and should not be excluded from capacity equations if they don't have input/output commodity, or because not appearing in relation_activity.

Since this map_tec_time is created in JAVA backend, it's not easy to see how it is calculated.

A thought on implementation: since the change here is to expand (i.e. to change the set elements from the union of {A, B, C} to the union of {A, B, C, D}), we can implement the full logic in Python using the mechanism introduced in #561/#514. This runs before the Java code linked above. So the Java code linked above becomes redundant; it will simply re-add elements to these mapping sets that have already been added. This would partly address #254.
This approach will not work in other cases where the desired behaviour is not a superset of the behaviour implemented in Java. E.g. here if we wanted to go from union {A, B, C} to union {A, C}, this would not be a viable approach.

Thanks @khaeru for the thoughts. I checked this through the equations again. As I understand, map_tec_time is the mapping of technologies to sub-annual time slices. Therefore, we can't add capacity related parameters like relation_total_capacity to this mapping, because capacity is dealt with only the annual level in the formulation. The use of this mapping in the equation for capacity_factor means that those technologies without input/output commodity, and with no entries in relation_activity do not need capacity_factor. In other words, these technologies write to the CAPACITY_MAINTENANCE equation, so the model can invest and build them; however, it is not important what their capaicty_factor is because their activity is not needed anywhere in the formulation. So my initial impression that it is a bug may not be correct, and I removed the tag. I will check this further and come back if we need to do something.
But I like your general idea if we can change some mapping/masking sets after being created in java. I thought these sets are created when writing the GDX file and there is no chance to edit them in python after being generated in java.


Update Firebase iOS SDK to v10.23.0

This SDK depends on the older iOS Firebase SDK version 10.19.0.

https://github.com/GitLiveApp/firebase-kotlin-sdk/blob/d13f931245a8bfcf390c4cbf5b271f2c1d9aeaa6/firebase-app/build.gradle.kts#L90

It is necessary to update to the latest available version 10.23.0.

https://github.com/firebase/firebase-ios-sdk/releases/tag/10.23.0

Closing as the following item has been addressed:

https://github.com/GitLiveApp/firebase-kotlin-sdk/pull/481


Birth abroad Cambodia and PNG amends

PT story: https://www.pivotaltracker.com/story/show/109534752
Update outcome section "Return of your documents" so the text for Cambodia and Papua New Guinea becomes the same as the other ORUs.
Fact check
https://pt-109534752.herokuapp.com/register-a-birth
Expected changes

URL on gov.uk
First sentence under "Return of your documents" starts with "It usually takes 5 working days for the birth to be registered"

Before

After

Looks ok, but has conflicts

Just rebasing this master, will merge once CI completes


invalid discord invte link

support server link in readme is invalid

Yo, @cow03haha. I've deleted my support server...
Do you need any help? You can DM me on Discord or Twitch. Or just @ me here.

@luissilva1044894
getLatestPatchNotes is not work, I am not sure if I am using this method correctly
here is my code
from pyrez.api import PaladinsAPI, StatusPageAPI
from pyrez.enumerations.Language import Language

paladins = PaladinsAPI(devId = 'devId', authKey = 'authKey')
data = paladins.getLatestPatchNotes()
print(data)
paladins.close()

and here is error
$ /usr/bin/python3 /media/cow03/NoobCow_CodeSpace/python/misc/paladins_api.py
Traceback (most recent call last):
  File "/media/cow03/NoobCow_CodeSpace/python/misc/paladins_api.py", line 5, in <module>
    data = paladins.getLatestPatchNotes()
  File "/home/cow03/.local/lib/python3.7/site-packages/pyrez/api/PaladinsAPI.py", line 88, in getLatestPatchNotes
    __ = self.getWebsitePost(language=language or Language.English, slug=PaladinsWebsitePost(**_[0]).slug)
  File "/home/cow03/.local/lib/python3.7/site-packages/pyrez/api/PaladinsAPI.py", line 105, in getWebsitePost
    __ = [ PaladinsWebsitePost(**___) for ___ in (_ or []) ]
  File "/home/cow03/.local/lib/python3.7/site-packages/pyrez/api/PaladinsAPI.py", line 105, in <listcomp>
    __ = [ PaladinsWebsitePost(**___) for ___ in (_ or []) ]
TypeError: type object argument after ** must be a mapping, not str

@cow03haha Hey, it's being a while. Sorry for the delay...
My old server was never active and I'm not planning to create a new one. But there one that I'm in. Not mine, but there some Hi-Rez devs too. https://discord.gg/52Vz34W
I've commited a fix for your issue, can you check it?
Also, there are some non-public endpoints, such as:
https://nonsocial.herokuapp.com/api/paladins/patch_notes?lang={LANG}
https://nonsocial.herokuapp.com/api/smite/patch_notes?lang={LANG}
Where LANG are the same as supported: es, pt, pl & en. Defaults to en.
So, free feel to use it.


Sanitation of URL via ODataUriFactory

Issue Description
I’ve come across a doubt while implementing some changes for migrating to Cloud SDK.
I tried to implement the creation of a URL using the ODataRequestRead class with the base URL example as below:
Base URL : https://sap1.fgvms.com/api/vc
The ODataRequestRead class is used for creating the request as shown below :
ODataRequestRead request = new ODataRequestRead(baseUrl, structuredQuery.getEntityOrPropertyName(), queryString, ODataProtocol.V2);
(The ‘queryString’ has been created using StructuredQuery class)
After creating the request like above, we do a REST template call to hit the URL. We are facing a problem in this part.
If we try getting the request URI from the above created request using the method - request1.getRelativeUri() , some sanitation of URL happens and we get a malformed URL as such :
/https:/sap1.fgvms.com/…
Even though the base URL has the “https” part correctly, relative URI from the ODataRequestRead request gives out a different URI with the “https” part altered.
I tried debugging and found that a piece of code in ODataUriFactory does some sanitation to the URL :

Impact / Priority

It is affecting our productive code.

<!-- Application Logs
Please make sure you [set your log level to debug](https://sap.github.io/cloud-sdk/docs/java/guides/logging-overview#configuring-logback) and attach the resulting log output as .txt or .log file to this issue.
This is _very important_ as it usually gives a lot of information that is necessary to get to the root cause of an issue. Be sure to redact confidential information before posting.
-->

<!-- Maven Dependency Tree
Please attach the Maven dependency tree of your project. You can obtain that by running "mvn dependency:tree" on the command line. Kindly note that you could have several pom.xml files in your project.
If so, please provide the dependency tree for the pom.xml of the root module and the module named like `application´ or `srv` that contains the application logic.
-->

## Project Details

<!--
Please provide as much information about your project as possible.
If you cannot share your project for confidentiality reasons, please consider providing a minimal working example https://en.wikipedia.org/w/index.php?title=Minimal_working_example&oldid=893866607
-->

* SDK Version: <your SAP Cloud SDK version here>
<!-- The group id of the modules of the SAP Cloud SDK start with "com.sap.cloud.sdk" -->
* Link to GitHub repo: <your link here>
* Project type, for example:
    * [ ] CAP Project
    * [ ] SDK Maven Archetype
    * [ ] None of the above:
* Platform:
    * [ ] Cloud Foundry
    * [ ] Deploy with Confidence (Cloud Foundry)
    * [ ] None of the above:

-----

### Checklist

- [ ] Checked out the [documentation](https://sap.github.io/cloud-sdk/docs/java/sdk-java-troubleshooting-frequent-problems) and [Stack Overflow](https://stackoverflow.com/questions/tagged/sap-cloud-sdk)
- [ ] Description provided with all relevant information
- [ ] Exception and stack trace provided
- [ ] Attached debug logs
- [ ] Attached dependency tree
- [ ] Provided Cloud SDK version & link to relevant source code

Hi @AmnaNizarHussain,
You are using the Generic OData Client, which we also call expert API and we usually don't advertise it to our users. That means the following:

for some cases, as a developer you would need expert knowledge - or carefully read the JavaDoc
API convenience is not in focus
not all edge-cases are considered

In your case, please find the correct parameters:
  public ODataRequestRead(
     @Nonnull final String servicePath,
     @Nonnull final String entityName,
     @Nullable final String encodedQuery,
     @Nonnull final ODataProtocol protocol )

First argument is a relative or absolute path.
While the execute(HttpClient) method assumes a generic HttpClient object according to API, internally we require it to come from HttpClientAccessor.getHttpClient(HttpDestination). We're extracting the server address (hostname) from the provided destination. Destination API is one of our central concepts in SAP Cloud SDK.
Code suggestion:
  ODataRequestRead request = new ODataRequestRead(
-   "http://foo/bar", [...]
+   "/bar", [...]

  HttpClient httpClient =
-   HttpClient.newBuilder().build();
+   HttpClientAccessor.getHttpClient(DefaultHttpDestination.builder("http://foo").build());

  request.execute(httpClient);

However I would recommend to checkout the convenience API for OData v2/v4 instead of using the expert API:
https://sap.github.io/cloud-sdk/docs/java/features/odata/overview
But use whatever works best for you :+1:
Kind regards
Alexander

I will close this issue, as there was no update since two weeks here anymore.
If you still have questions, feel free to raise another issuer or re-open this one.


End of Line For CSV Loading/Parsing

The Polars CSVReader lets you define an eol_char. I can't test this due to the mac build bug so I am opening a WIP PR.
Related to #577

@jeregrine please run mix ci to fix the issues.

@jeregrine please try with an older version of nightly. We are using nightly-2023-02-14 in the CI.

Hey that worked. Pushed up the format

I'll work on adding a couple tests probably tomorrow.

I just get "Argument Error" whenever I try to set this.
Also I suspect I will need to fix this upstream in polars since u8 isn't enough to handle \r\n.

@jeregrine the Argument Error comes from passing eol_char as a string, a utf8 encoded binary.
You can check how it's done for the delimiter option.

@jeregrine the Argument Error comes from passing eol_char as a string, a utf8 encoded binary. You can check how it's done for the delimiter option.

A single character of a utf8 encoded binary is a 8 bitunsigned number.
Rust:
delimiter_as_byte: u8,

Elixir:
delimiter: ",",
The only real difference I can see is the pattern match before the call.
    <<delimiter::utf8>>,

You can understand my confusion then

I'm going to close this cause I think we're better spent fixing this upstream AND THEN making all the required changes.

The only real difference I can see is the pattern match before the call.
<delimiter::utf8>,

@jeregrine Yeah, we pass that delimiter, assuming that is one char long, as an u8 number (delimiter is going to be a number in this pattern matching).
I think we want to be able to set  \r\n if needed, so would be cool to be able to do that in Polars.
But, for the case that you mentioned in #577, I think this change would suffice. I'm OK to support a single char, and then we add support for multiple when fixed upstream.

:+1: for eol_delimiter as a string which we still enforce to be single byte.

@jeregrine would you mind to just add a test? I think something around load_csv is enough. You can generate a string that uses, for example, \r as the eol_delimiter.
Also, I think we can change to eol_delimiter like José suggested. WDYT?

I need to update the spots to use u8 and I need to swap it out. But yea Ive got tests locally I havent pushed up. On Apr 24, 2023, at 4:32 PM, Philip Sampaio @.***> wrote:
@jeregrine would you mind to just add a test? I think something around load_csv is enough. You can generate a string that uses, for example, \r as the eol_delimiter.
Also, I think we can change to eol_delimiter like José suggested. WDYT?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@philss I added the changes you requested.

accepted your changes

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:

<3 Happy to help anyway I can.


Implement PEP560 inheritance (mro_entries)

Fixes https://github.com/cython/cython/issues/3537
Both the C code and the tests are largely copied from CPython
so hopefully should be pretty reliable.
This doesn't backport perfectly so I've hard to disable a few
tests of Python 2 (and may have to on earlier Python 3 versions too).
I think that's OK.
I haven't applied this at all to cdef classes. Maybe it could be
applied to the second+subsequent bases but I don't think it's
needed for the initial implementation.

Just a few nits.

Changed

I think the test failures are the same as in current master, right?

The failures are the same as master (unless I broke it with the current lot of changes...)

(master is in a really bad shape right now – we need to address that somehow.)

https://github.com/cython/cython/pull/4006 clears up some simple bugs one of the tests for in 2.7 and 3.4/3.5 I think. The C++ tests are largely failing because something changed in Pythran (but I don't think there's a good fix for that yet...) But I think there's a few other things too

Thanks!


Remove needs triage label

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description

LGTM :+1:


Add radio button object

Hello,
This is the radio-button, let me know if you find it suitable !
Thanks !

I would like the shown value and the payload to be different. In case I want to show "one" and the payload to be "1" or if I have a 2nd thought on wording, I shouldn't have to change any of the other nodes.
Otherwise, it looks good.

Makes sense ! Will add that !

Just did the modification !
Thanks !


workload - cannot set node scheduling when creating deployment

rancher:master-3375-head
Steps:

set the node scheduling when creating a deployment for the dashboard

Couple issues here:

there is no node showing in the list when choosing run pods on specific node(s)

there is no option for operators when choosing run pods on nodes matching those scheduling rules

UI shows  the error message if trying  to create the deployment
Deployment.apps "jiaqi-test" is invalid: spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].operator: Invalid value: "": not a valid selector operator

on rancher master-5e1b21b931ac58ba0aa3f89c827a0f65dd42051b-head
Issue 1 is fixed.
we can set the node scheduling when creating a deployment for the dashboard

on rancher master-5e1b21b931ac58ba0aa3f89c827a0f65dd42051b-head
Issue 2 is fixed.

on rancher master-5e1b21b931ac58ba0aa3f89c827a0f65dd42051b-head
issue 3 still exists.

{"type":"error","links":{},"code":"BadRequest","message":"Deployment in version \"v1\" cannot be handled as a Deployment: v1.Deployment.Spec: v1.DeploymentSpec.Template: v1.PodTemplateSpec.Spec: v1.PodSpec.Affinity: v1.Affinity.NodeAffinity: v1.NodeAffinity.RequiredDuringSchedulingIgnoredDuringExecution: v1.NodeSelector.NodeSelectorTerms: []v1.NodeSelectorTerm: v1.NodeSelectorTerm.MatchExpressions: []v1.NodeSelectorRequirement: v1.NodeSelectorRequirement.Operator: ReadString: expects \" or n, but found {, error found in #10 byte of ...|perator\":{\"label\":\"=|..., bigger context ...|ons\":[{\"key\":\"kubernetes.io/hostname\",\"operator\":{\"label\":\"=\",\"value\":\"In\"},\"values\":[\"<IP_ADDRESS>|...","status":400,"type":"error"}

@mantis-toboggan-md Here are the requirements for validation of this:

Field
Description

keystring
The label key that the selector applies to.

operatorstring
Represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.

valuesstring array
An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.

I'm not seeing this issue anymore, it appears to have been fixed inadvertently a few weeks with this commit https://github.com/rancher/dashboard/commit/565520c47afb42fe2c27c9bd0cddabb4bc73fc4c

This bug fix is validated in rancher-master ec04f78
The node scheduling part works as expected.


docs(update): add feature

Update the docs.

Waiting for the latest version of google fonts to add this feature.


Added favicon

There was no particular logo  so i used this svg

it will work on all browsers and devices

Looks good to me. 👍

Hi @gunwant11 , I mistakenly closed the PR, Can you PR again?


Upgrade curl beyond 7.35 to avoid regression

7.35 introduced a regression ( see https://github.com/guzzle/RingPHP/issues/26)
Can we upgrade to 7.36 or above?

@johnmcteague, we use the latest patched packages from Canonical (Ubuntu creator). For the trusty distro, they've version locked it to 7.35.0. We only receive the security patches for 7.35.0.
Are you experiencing the issue with curl and RingPHP?

Its actually curl under the hood of https://github.com/onoi/http-request that causes the issue (I gave the RingPhp reference as an example).
We run SemanticMediaWiki (https://semantic-mediawiki.org) on CF using the PHP buildpack. SMW cuses onoi/http-request lib.

@johnmcteague Thanks for asking this question.
Unfortunately, as @jtarchie points out, the rootfs is derived from Canonical's Ubuntu 14.04 (trusty) distribution, which ships curl 7.35.
It's currently not our policy to cherry-pick individual packages, and we're unlikely to change that policy unless there are compelling security issues involved.
Can you help us understand the severity of this problem? How is it affecting you? Are there any known workarounds?

We verified a workaround on Friday that involves downgrading http to 1.0 via a curl option. For now that will suffice. This issue has helped clarify our understanding of the LTS position of the rootfs, so its been benefical.
Out of curiosity when 16.04 LTS is released in April, is it proposed rootfs would move with it at some point? LTS for Ubuntu is technically 5 years and 12.04 was skipped for rootfs.

We haven't started discussions of supporting 16.04 yet. There are some related issues I'd like to work on before we start supporting two Linux stacks in earnest.


architectural block diagram

Is there any chance I could check an architectural block diagram image for the model structure, aside from the training strategy image in Figure 3?

Hi @degull
Unfortunately, I don't have an architectural block diagram as the model is simply composed of a standard ResNet50 and a linear regressor on top of it. The closest thing that I have is this figure of the method overview. Feel free to ask more questions if needed.


ignore .css files when building route manifest -

fixes #3997. I think we can punt on the question of whether we want to treat all .js/.ts files similarly — I think the .css case is fairly unambiguous. If we decide to make it more expansive in future, .css files would be included in that, so this is forward-compatible
then again this could be a can of worms if people start asking about .scss and what-have-you...
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[x] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

I'm not sure where the line is between stuff that should happen in the default https://kit.svelte.dev/docs/configuration#routes function vs stuff that should be stripped out in a separate step.

What happens to file types besides .js/.ts and .css/.scss/etc.? Do we want to generate routes for .json files? I don't know what we do today, but I would expect that we don't and that they should just go into static/. It seems potentially safer to me to whitelist .js / .ts than to blacklist .js?

If we include rather than exclude, then we need a way to make it extensible to handle edge cases like .res (ReScript) files and whatever other wacky shit people want to use

Do we want to generate routes for .json files?

no, they will always belong in static

Should I ask if we also need to exclude image files? I have a feeling we'll need a config option either way whether it's to add stuff like .res or .scss. It seems less common to use other JS formats like .res than the combined use of all other extensions like .scss, so it might be the option that works out-of-the-box more of the time.

Just my two cents as another possible avenue, we could tidy up the error to say "hey, that .css file doesn't belong under routes/, consider static/ or somewhere outside routes/ if you want to import it"
The route manifest and this directory are doing a lot of heavy lifting, and it wasn't obvious from the outset that I was interfering with it - in retrospect, it makes sense why this broke, and I think noping this use case doesn't detract from the developer experience
I'd like to think that could also reduce collateral continuing to implement advanced features (looking at you, shadow endpoints) with this directory

Opened https://github.com/sveltejs/kit/pull/4197 as a possible alternative

Closing this in favour of #4197


Converted tags/_form to haml

Also in battles/show removed the special z character
Added a break

:+1:


Transfer ownership to Databricks

The repository of record will be the fork currently owned by the Databricks repository.
I hope this will not affect current users and branches.

Finished.


Enable TCP Fast Open

Unbound supports the TCP Fast Open feature [0] which can be enabled at build time with:
--enable-tfo-client
--enable-tfo-server
TFO is generally considered as worthwhile feature and doesn't require any additional dependencies.
[0] https://lwn.net/Articles/508865/

Sure! Fixed the whitespace. Where would be a good place for the test case?

I guess there are no runtime options for this, is it only build time? Is there any way to test if it is enabled?
Test cases usually live in the docker-compose test file. We also load some optional config overrides in there to test some features.

It's only a build-time flag.
The daemon prints TCP Fastopen feature available when the binary is built with the respective flag. The configure options define USE_TCP_FASTOPEN flag and the code uses setsockopt(s, IPPROTO_TCP, TCP_FASTOPEN). As long as there is a test which tests a successful request/response, it should be good. The code path is not conditional at runtime.

FWIW, this popular image also enables the flags, which should provide some reassurance that they work for many https://github.com/MatthewVance/unbound-docker/blob/53fcae708e87d7fcf5ebbbeccb4090c4714b54b5/1.20.0/Dockerfile#L91-L92

Sounds simple enough. You can go ahead and rebase on main and I'll approve.

Thanks for the contribution!


Introduce context

Why
This changeset was motivated by the proliferation of inherited @variables in many of our controllers, eg @system_setting.
It's bad practice to reference superclass instance variables because it creates very tight coupling up and down the inheritance chain. These variables essentially become globals.
In rails, this problem is usually solved in one of several ways. Taking @system_setting as an example:

Wrap variables in attr_readers, eg attr_reader :system_setting. This is an improvement but still maintains coupling between super and sup classes.
Mix in a module containing an accessor. This is an improvement because it doesn't force accessors onto other classes in the inheritance chain that don't need it. There are still a couple of downsides:

There are usually a number of accessors in play; authors have to discover and bring in multiple modules.
Because accessors are mixed directly into the controller, the coupling is still tight; there isn't a distinct 'seam' between the controller and the dependency, so we have to mock/override accessors. Again, if there are several accessors in play, this can get cumbersome.

Dropping the accessor and getting the underlying data directly, usually via a class method, eg SystemSetting.current_settings. Eliminates the sub/super coupling, replacing it with direct coupling; the coupling shifts from 'vertical' to 'horizontal'. This makes the seam much clearer but still suffers violates the Dependency Inversion principle and can also lead to duplication.

Further, all the solutions above only help at the controller layer. We often need to access some of these variables in other layers such as Interactors or Serializers. A good example of this is needing access to current_user outside of controllers.
This changeset outlines an alternative that i believe minimizes all these concerns.
What and How

Introduces Context, a thin wrapper providing access to 'globals' such as system_settings and current_user. This serves as a single point of access to any 'context' we might need.
Context can be initialized with data or filled out later via attr_writers.
It can also lazily retrieve and memoize data (see Context#system_settings).
This new class turns out to be a practical and semantic superset of UserContext, so they've been consolidated.
Shows a simple example of usage in AnnouncementsController

Testing

[x] app/models/context_spec.rb

Next Steps

[x] Refactor AnnouncementsController to drop @admin_status in favor of context.can_admin? #845
[ ] ?

Outstanding Questions, Concerns and Other Notes
?
Meta
Very open to discussion and feedback. I realize this approach bucks the typicals 'rails way'.
Pre-Merge Checklist

[x] All new features have been described in the pull request
[x] Security & accessibility have been considered
[x] High quality tests have been added, or an explanation has been given why the features cannot be tested
[ ] New features have been documented, and the code is understandable and well commented
[ ] Entry added to CHANGELOG.md if appropriate
[ ] All outstanding questions and concerns have been resolved
[ ] Any next steps that seem like good ideas have been created as issues for future discussion & implementation

H/T @h-m-m for bringing CurrentAttributes to my awareness: TIL!
While it is certainly solving the same problem i fundamentally disagree with its design (which actively violates the dependency inversion principle). That said, i'm open to using it instead if folks see value in sticking to rails conventions.

H/T @h-m-m for bringing CurrentAttributes to my awareness: TIL!
While it is certainly solving the same problem i fundamentally disagree with its design (which actively violates the dependency inversion principle). That said, i'm open to using it instead if folks see value in sticking to rails conventions.

Realized this PR was doing too much and the policy related changes were distracting from the primary design suggestion. Extracted #849 to hold the ?admin=false related changes.

As discussed, i'm going to merge this but wanted to document an answer to the question @h-m-m raised in person: why do i prefer this approach to the rails CurrentAttributes?
They both solve the same problem.
In short, CurrentAttributes violates the Dependency Inversion Principle.
Here's an example contrasting each solution when an interactor needs SystemSettings (as an example of a 'global').
Current
# interactor
class EmailNewSubmission < ActiveInteraction::Base
  object :submission

  def execute
    SubmissionMailer.new_submission_confirmation_email(submission, Current.system_settings)

# controller
class OffersController < PublicController
  def create
    EmailNewSubmission.run! submission: submission

(Unrelated code ommitted)
Here you can see system settings being retrieved from within the interactor via Current.system_settings.
Note this dependency is not visible when looking at the controller, nor when scanning the params defined at the top of the interactor. The dependency is buried within the execute method.
Context
# interactor
class EmailNewSubmission < ActiveInteraction::Base
  object :submission
  object :system_setting

  def execute
    SubmissionMailer.new_submission_confirmation_email(submission, system_setting)

# controller
class OffersController < PublicController
  def create
    EmailNewSubmission.run! submission: submission, system_setting: context.system_settings

In contrast, here the dependency is explicit and obvious.
The downside tradeoff is that if a dependency needs to be passed through multiple layers of code, this can be cumbersome. Imagine for example that the interactor calls another interactor which then calls a mailer which needs system settings. All of these intermediate objects would then need to pass-through a param, whereas with the Current solution, the mailer could directly retrieve system settings.
IMO, the 'pain' of having to pass that param through is actually very useful; it acts as a 'smell', encouraging us to rethink our design. There are certain cases, such as some cross-cutting concerns, where there aren't clear alternatives but these are the exception to the general rule.
A secondary argument is that CurrentAttributes uses 'magic' to make sure Current.system_settings is isolated across requests although it's accessed through a class method (which in plain ruby would usually access global data). Where possible, i prefer to avoid such magic that goes against the grain of plain ruby.
context on the other hand is a just an accessor around an instance variable lazily initialized in ApplicationController which already guarantees request isolation (because each request get's a new instance of the corresponding controller).


Handle cases when required params are missing in conn or options

@banzay I updated this issue https://github.com/rpelyush/gardien/issues/6

@banzay Also I would suggest renaming all functions that raise to have ! at the end. Seems like this is convention (should check it out).


Binary Vector Support - Fix $binary to Support 4096 Vector Dimensions

When users encode a 4096-dimensional vector into Base64, the resulting binary string length reaches 21848 bytes. This exceeds the maximum allowable string length of 8000 bytes for the $binary field, resulting in the following error:
astrapy.exceptions.DataAPIResponseException: Document size limitation violated: indexed String value (property '$binary') length (21848 bytes) exceeds maximum allowed (8000 bytes)

Quick question: is this when updating $vector field of a Collection? (I assume so)
I don't think we really can increase indexable limit (it's a SAI setting limited by database). But perhaps we can instead make sure that $vector is, by default, not indexed as a String by Data API -- it will be ANN indexed anyway so there seems to be little need.

Note: this already occurs with vectors of length 1536, which become Base64-encoded Strings of length 8192, exceeding 8000 limit.


Infinite Loop in find_min_trust_region

I have a process running which continuously solves optimization problems with solve_least_squares_lm. I noticed that this process stalls seemingly at random with approximately with 12 hours in between (though this varies drastically).
This process runs on an embedded system so debugging is difficult but I managed to track down the culprit by inserting logging statements into dlib. Sometimes, the loop in dlib/optimization/optimization_trust_region.h runs indefinitely. The loop in question is
while(stale_x || stop_strategy.should_continue_search(x, f_value, g))

I use a custom stop_strategy which limits the number of iterations to a predefined value (5 in my case). Apparently, this limit is not effectuated. I have a log statement as the first thing inside should_continue_search. When the stall occurs, I notice that should_continue_search isn't called anymore yet the operations inside the loop are still executed over and over. From that I infer that stale_x must be true and in turn short-circuiting the expression so that the stop_strategy isn't evaluated.
It is easy to track stale_x in the code. Inside the loop, it only occurs here
if (rho > 0)
{
    x = x + p;
    f_value = new_f_value;
    model.get_derivative_and_hessian(x,g,h);
    stale_x = false;
}
else
{
    stale_x = true;
}

So it must be that 0 >= rho indefinitely when the loop never returns. rho is defined as
const type rho = measured_improvement/std::abs(predicted_improvement);

Most likely, 0 >= measured_improvement (though predicted_improvement could be really large as well). Apparently, the solver gets stuck (can't improve further x further) and this stalls the entire process.
To me it seems strange that we repeat the loop at all when x is stale. Why not simply
if (0 >= rho)
{
    break;
}

and let go of stale_x completely? If no improvement could be made in this iteration, how could there be any improvement in the next (assuming that the subproblem solver is a pure function)?

You need the stale check to deal with numerical failures in the trust
region sub-problem solver.  They are rare but can happen for some badly
conditioned problems.
If rho <= 0 then this code should be executing over and over:
https://github.com/davisking/dlib/blob/ca498ac2d214fd679f8c641f90d08fb63cac11f6/dlib/optimization/optimization_trust_region.h#L304
which would lead to termination once radius gets small enough.  Which
happens quickly.  But for some reason that doesn't happen on your machine?
Are you sure the initial radius isn't zero?

Thanks for the quick reply!
I have log statements as follows:
<<LOG Start of loop>>

while(stale_x || stop_strategy.should_continue_search(x, f_value, g))
{
    <<LOG Start of subproblem>>
    const unsigned long iter = solve_trust_region_subproblem(h,
                                                             g,
                                                             radius,
                                                             p,
                                                             0.1,
                                                             20);
    <<LOG End of subproblem>>

    const type new_f_value = model(x+p);
    const type predicted_improvement = -0.5*trans(p)*h*p - trans(g)*p;
    const type measured_improvement = (f_value - new_f_value);

    // If the sub-problem can't find a way to improve then stop.  This only happens when p is essentially 0.
    if (std::abs(predicted_improvement) <= std::abs(measured_improvement)*std::numeric_limits<type>::epsilon())
        break;

    // predicted_improvement shouldn't be negative but it might be if something went
    // wrong in the trust region solver.  So put abs() here to guard against that.  This
    // way the sign of rho is determined only by the sign of measured_improvement.
    const type rho = measured_improvement/std::abs(predicted_improvement);

    if (rho < 0.25)
    {
        radius *= 0.25;

        // something has gone horribly wrong if the radius has shrunk to zero.  So just
        // give up if that happens.
        if (radius <= initial_radius*std::numeric_limits<double>::epsilon())
            break;
    }
    else
    {
        // if rho > 0.75 and we are being checked by the radius
        if (rho > 0.75 && iter > 1)
        {
            radius = std::min<type>(1000,  2*radius);
        }
    }

    if (rho > 0)
    {
        x = x + p;
        f_value = new_f_value;
        model.get_derivative_and_hessian(x,g,h);
        stale_x = false;
    }
    else
    {
        stale_x = true;
    }

    DLIB_ASSERT(is_finite(x), "The objective function generated non-finite outputs");
    DLIB_ASSERT(is_finite(g), "The objective function generated non-finite outputs");
    DLIB_ASSERT(is_finite(h), "The objective function generated non-finite outputs");
}

<<LOG End of loop>>

When the process stalled the last time, the log was as follows:
Start of loop
stop_strategy.current_iteration is 0
Start of subproblem
End of subproblem
stop_strategy.current_iteration is 1
Start of subproblem
End of subproblem
stop_strategy.current_iteration is 2
Start of subproblem
End of subproblem
Start of subproblem
End of subproblem
Start of subproblem
End of subproblem
Start of subproblem
End of subproblem
Start of subproblem
End of subproblem
Start of subproblem
End of subproblem
Start of subproblem
End of subproblem
...

It never reaches End of loop. So I think it's safe to say that the break statement that you linked is never reached... At least not within a reasonable amount of time (the process runs out of memory a couple of minutes later since a buffer keeps filling up in the background while the main loop is stalled).

But for some reason that doesn't happen on your machine?

Apparently, yeah. It's an ARM Cortex A9. The binary is compiled with GCC 5.1. Nothing too exotic.

Are you sure the initial radius isn't zero?

Now that I have found the source of the issue, I will add additional logging statements. I can try to log the radius as well. However, it is a long and tiresome process since the stall only happens rarely.
Also, since the loop didn't break the first iteration, then radius couldn't be zero to begin with.

How many iterations were executed?  radius should be driven below machine
epsilon in under 30 iterations if it's stuck.  Which is maybe more
iterations than it should wait, but it shouldn't be infinite.

How many iterations were executed?

244927 iterations. Took 8 minutes and 20 seconds before the parent process gave up.
I'm going to let it run overnight and hope for a stall. Anything that you'd like to see logged?

Just see if the radius is shrinking and why that check that it's <= epsilon
isn't triggering.

Finally the error occurred again (almost took a week).
Initial state. That is, before the while loop starts:
stale_x:	false
f_value:	8.649034330750594e-08
radius:		1
x:			8.064693875695084e-06
<PHONE_NUMBER>.20756
			0.001052001393936634
			0.04356275194584994
			0.002204298973083496

Everything seems reasonable and g and h contain reasonable values as well. Note that x[1] is a timestamp (seconds since the Unix epoch).
First iteration. Subproblem solver gives:
p:			-1.35385201211673e-05
			0.0009906467668197901
			0.002325868762470198
			-2.537947130037535e-08
			-0.001856744283307625
rho:		0.09188805324971834

Since rho < 0.25, the radius is decreased to 0.25. Likewise (since rho > 0), x, g, h and f_value are updated:
x:			-5.473826245472216e-06
<PHONE_NUMBER>.208551
			0.003377870156406832
			0.04356272656637863
			0.0003475546897758709

g:				-8.563441858534694e-05
			-7.307040067143083e-08
			-1.027289586940727e-07
			-4.232278142863449e-05
			1.340170728027009e-06

h:			2.447542384577117		0.0007765437907045539	0.003024926738394633	6.201796400720923		-0.03830073394130407
			0.0007765437907045539	9.768330939878049e-06	-1.666246606188446e-06	-0.01507927763086306	-1.224227225957858e-05
			0.003024926738394633	-1.666246606188446e-06	1.045564101416769e-05	-0.01569309473596635	-4.71047006169862e-05
			6.201796400720923		-0.01507927763086306	-0.01569309473596635	330						-0.09785363617659867
			-0.03830073394130407	-1.224227225957858e-05	-4.71047006169862e-05	-0.09785363617659867	0.0005993627431313574

f_value:	8.559709740312501e-08
stale_x:	false

All values are within reason (not too far from the initial state).
Second iteration. Subproblem solver gives:
p:			-0.02195688289153057
			0.004313228981041453
			0.04841471545391627
			-3.083927417442201e-07
			-1.401491371459836

rho:		0.2546974645290118

The radius remains at 0.25 (since 0.75 > rho >= 0.25). Everything is good so far. When updating the model, however, the derivative and hessian matrices (g and h) become unstable:
x:			-0.02196235671777605
<PHONE_NUMBER>.212864
			0.0517925856103231
			0.04356241817363689
			-1.401143816770061

g:			-1.744080646805953e-160
			1.979263582875392e-159
			5.287980188763079e-158
			-0.0001101448302976288
			1.977586404125327e-159

h:			7.843276780543929e-311	-8.91288575585488e-310	-2.388463147849715e-308	-8.318066745969836e-155	-8.912788740948281e-310
			-8.91288575585488e-310	1.012838721518276e-308	2.714187220539983e-307	9.472393158122636e-154	1.01282553022157e-308
			-2.388463147849715e-308	2.714187220539983e-307	7.273448837563741e-306	2.536502340476404e-152	2.714157438630012e-307
			-8.318066745969836e-155	9.472393158122636e-154	2.536502340476404e-152 	330						9.458758110400953e-154
			-8.912788740948281e-310	1.01282553022157e-308	2.714157438630012e-307	9.458758110400953e-154	1.012814461441429e-308

f_value:	8.51832924170149e-08
stale_x:	false

x is still reasonable but g and h contain values very close to 0.
Third iteration. Subproblem solver gives:
p:			-1.561150676956899e+157
			6.319687295858829e+152
			5.129372402031413e+154
			-1.388538990733689e-05
			-2.749024730721683e+156

rho:		-nan

Now p contains unreasonable large values (due to the unstable g and h from the previous iteration). The rho: -nan is the real offender. Digging deeper, rho becomes -nan because the residual function returns -nan for extreme values (parameters of approx. e+150 and above).
All comparisons with a nan value returns false. Thus the radius is never updated (since -nan < 0.25: false and -nan > 0.75: false). For the same reason, rho > 0: false and thus stale_x gets set to true indefinitely. This causes the infinite loop.
My take on this: I don't think it's unreasonable to expect these kind of instabilities in the residual and its derivative. Add an opt-out if rho is nan at the same place of the  opt-out if p is small. Alternatively, opt-out if std::abs(p) is ridiculously large (e.g., within an order 10 of std::numeric_limits<type>::max()).
Moreover, I think that the while loop should be re-structured so that the stop_stategy.should_continue_search function is called on each iteration. That is, stale_x should not be able to short-circuit the stop strategy. Otherwise, it is impossible to implement a max_iterations parameter for the stop strategy.

Cool, nice work debugging this : )
Yeah, that would be a problem.   I just pushed a fix to github that adds a check for non-finite rho values.
I'm not so sure about removing stale_x though.  I suppose the stopping strategies could return the max number of iterations to the solver and it can count and break based on that itself.

I just pushed a fix to github that adds a check for non-finite rho values.

Cheers! I know it took a while to get to the root if this problem so I appreciate your patience.

I'm not so sure about removing stale_x though. I suppose the stopping strategies could return the max number of iterations to the solver and it can count and break based on that itself.

That would work for me. For long-running processes it is nice to have an upper bound on this kind of loop. Better safe than sorry. That's another issue, however, so I'm closing this one. Thanks again!


Only want to remove the script tag.

so i want to use all the html tags and their attributes except script tag, but for this i need to add all the tags and attributes in default settings. is there a way through which i did not need to do that

Maybe https://github.com/messense/nh3 would work better for you since it only sanitizes and doesn't do additional, more opinionated cleanups?

okay will check that,
thank you.


Falcon7b t3000 demo tests failing sporadically

In the last 5 runs of T3K demo pipeline on main (https://github.com/tenstorrent/tt-metal/actions/workflows/t3000-demo-tests.yaml), falcon7b tests have failed 2 times due to timing out. They timed out on calculating perplexity, and throw this message:
2024-06-29 08:03:24.368 | INFO     | conftest:run_timer:512 - Timing out test case
Passing runs took ~25 min to complete, while failing ones ran for ~29 mins before timing out.

@skhorasganiTT Increased the timeout so the tests stop failing

The last few runs in the pipeline (latest: https://github.com/tenstorrent/tt-metal/actions/runs/9886738452/job/27307454598) have completed the perplexity tests in < 15 min. Other pipelines were also seeing timeouts last week so I think this is safe to close for now. We can update the timeout values once we move the perplexity tests to the new correctness/stress-test pipeline that is being added.


Update wording and docs for v1 archival

Signed-off-by: Daniel Holbach<EMAIL_ADDRESS>

:stop_sign:  To be merged Nov 1.

Merge after https://github.com/fluxcd/flux/pull/3648 and https://github.com/fluxcd/helm-operator/pull/669 have been landed.


Replace lang with introspection

This seems obvious in retrospect, but instead of having settings for different languages (as we currently do for French), we should just parse the time formats in the Moment locales. For example...
> moment.langData('fr')._longDateFormat.LL
'D MMMM YYYY'
> moment.langData('en')._longDateFormat.LL
'MMMM D YYYY'

...tells us what "slot" the month, date, and year go in. We can do something similar for 24 hour time vs AM/PM by checking LT. That gets me out managing locale files gets us a whole bunch of locales for free.
/cc @leo-naeka

I'm getting this warning as well:  Deprecation warning: moment().lang() is deprecated. Instead, use moment().localeData() to get the language configuration. Use moment().locale() to change languages.
Is there any updates on this?

@niemyjski @wizonesolutions Finally got around to releasing 0.6.0 - should fix that warning.

Awesome Thanks!

Not going to do this.


Explain native AWS sample in detail; w/ test events

Updated with info from convo with OlegZ. I think this version will help Cx be successful in building, deploying, and testing.

Thank you once again Tim!


Install node-sass 4.5.0 failed on window 7, "Binary has a problem: Error: %1 is not a valid Win32 application.".

After update dependencies in package.json, run "npm install" failed when installing node-sass. I tried a few times, it seems download 'win32-x64-48_binding.node' always failed.
My node registry is set to cnpm 'http://r.cnpmjs.org/', does it influence the installation? But I can installed node-sass successfully few weeks ago  when I didn't update dependencies .
Here is my dependencies in package.json.
  "dependencies": {
    "isomorphic-fetch": "^2.2.1",
    "react": "^15.4.2",
    "react-dom": "^15.4.2",
    "react-redux": "^5.0.2",
    "react-router-redux": "^4.0.7",
    "redux": "^3.6.0",
    "redux-logger": "^2.8.1",
    "redux-thunk": "^2.2.0"
  },
  "devDependencies": {
    "babel-core": "^6.22.1",
    "babel-loader": "^6.2.10",
    "babel-preset-es2015": "^6.22.0",
    "babel-preset-react": "^6.22.0",
    "babel-preset-stage-0": "^6.22.0",
    "css-loader": "^0.26.1",
    "extract-text-webpack-plugin": "^1.0.1",
    "file-loader": "^0.10.0",
    "html-webpack-plugin": "^2.28.0",
    "node-sass": "^4.5.0",
    "react-router": "^3.0.2",
    "sass-loader": "^5.0.1",
    "style-loader": "^0.13.1",
    "url-loader": "^0.5.7",
    "webpack": "^2.2.1",
    "webpack-dev-server": "^2.3.0"
  }

The error log.
E:\teach\myLearn>npm install node-sass
npm WARN deprecated<EMAIL_ADDRESS>This package is deprecated. Use Object.
assign.
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g

><EMAIL_ADDRESS>install E:\teach\myLearn\node_modules\node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.5
.0/win32-x64-48_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.5.0/win3
2-x64-48_binding.node":

ESOCKETTIMEDOUT

Hint: If github.com is not accessible in your location
      try setting a proxy via HTTP_PROXY, e.g.

      export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

      npm config set proxy http://example.com:8080

><EMAIL_ADDRESS>postinstall E:\teach\myLearn\node_modules\node-sass
> node scripts/build.js

Binary found at E:\teach\myLearn\node_modules\node-sass\vendor\win32-x64-48\bind
ing.node
Testing binary
Binary has a problem: Error: %1 is not a valid Win32 application.
\\?\E:\teach\myLearn\node_modules\node-sass\vendor\win32-x64-48\binding.node
    at Error (native)
    at Object.Module._extensions..node (module.js:583:18)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at module.exports (E:\teach\myLearn\node_modules\node-sass\lib\binding.js:19
:10)
    at Object.<anonymous> (E:\teach\myLearn\node_modules\node-sass\lib\index.js:
14:35)
    at Module._compile (module.js:556:32)
Building the binary locally
Building: C:\Program Files\nodejs\node.exe E:\teach\myLearn\node_modules\node-gy
p\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_l
dflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ 'C:\\Program Files\\nodejs\\node.exe',
gyp verb cli   'E:\\teach\\myLearn\\node_modules\\node-gyp\\bin\\node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library=' ]
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| win32 | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` failed Error: not found: python2
gyp verb `which` failed     at getNotFoundError (E:\teach\myLearn\node_modules\w
hich\which.js:13:12)
gyp verb `which` failed     at F (E:\teach\myLearn\node_modules\which\which.js:6
8:19)
gyp verb `which` failed     at E (E:\teach\myLearn\node_modules\which\which.js:8
0:29)
gyp verb `which` failed     at E:\teach\myLearn\node_modules\which\which.js:89:1
6
gyp verb `which` failed     at E:\teach\myLearn\node_modules\isexe\index.js:44:5

gyp verb `which` failed     at E:\teach\myLearn\node_modules\isexe\windows.js:29
:5
gyp verb `which` failed     at FSReqWrap.oncomplete (fs.js:123:15)
gyp verb `which` failed  python2 { Error: not found: python2
gyp verb `which` failed     at getNotFoundError (E:\teach\myLearn\node_modules\w
hich\which.js:13:12)
gyp verb `which` failed     at F (E:\teach\myLearn\node_modules\which\which.js:6
8:19)
gyp verb `which` failed     at E (E:\teach\myLearn\node_modules\which\which.js:8
0:29)
gyp verb `which` failed     at E:\teach\myLearn\node_modules\which\which.js:89:1
6
gyp verb `which` failed     at E:\teach\myLearn\node_modules\isexe\index.js:44:5

gyp verb `which` failed     at E:\teach\myLearn\node_modules\isexe\windows.js:29
:5
gyp verb `which` failed     at FSReqWrap.oncomplete (fs.js:123:15) code: 'ENOENT
' }
gyp verb check python checking for Python executable "python" in the PATH
gyp verb `which` succeeded python C:\python27\python.EXE
gyp verb check python version `C:\python27\python.EXE -c "import platform; print
(platform.python_version());"` returned: "2.7.11\r\n"
gyp verb get node dir no --target version specified, falling back to host node v
ersion: 6.7.0
gyp verb command install [ '6.7.0' ]
gyp verb install input version string "6.7.0"
gyp verb install installing version: 6.7.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version is already installed, need to check "installVersion"
gyp verb got "installVersion" 9
gyp verb needs "installVersion" 9
gyp verb install version is good
gyp verb get node dir target node version installed: 6.7.0
gyp verb build dir attempting to create "build" dir: E:\teach\myLearn\node_modul
es\node-sass\build
gyp verb build dir "build" dir needed to be created? 若要启用并行生成，请添加“/m”开关。
生成启动时间为 2017/2/9 16:53:05。
节点 1 上的项目“E:\teach\myLearn\node_modules\node-sass\build\binding.sln”(默
认目标)。
ValidateSolutionConfiguration:
  正在生成解决方案配置“Release|x64”。
MSBUILD : error MSB3428: 未能加载 Visual C++ 组件“VCBuild.exe”。要解决此问题，
1) 安装 .NET Fram
ework 2.0 SDK；2) 安装 Microsoft Visual Studio 2005；或 3) 如果将该组件安装到了
其他位置，请将其位置添加到系统
路径中。 [E:\teach\myLearn\node_modules\node-sass\build\binding.sln]
已完成生成项目“E:\teach\myLearn\node_modules\node-sass\build\binding.sln”(默认
目标)的操作 - 失
败。

生成失败。

“E:\teach\myLearn\node_modules\node-sass\build\binding.sln”(默认目标) (1) ->
(_src_\libsass 目标) ->
  MSBUILD : error MSB3428: 未能加载 Visual C++ 组件“VCBuild.exe”。要解决此问题
，1) 安装 .NET Fr
amework 2.0 SDK；2) 安装 Microsoft Visual Studio 2005；或 3) 如果将该组件安装到
了其他位置，请将其位置添加到
系统路径中。  System Windows_NT 6.1.7601
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "E:\\teach\\myLearn\\node
_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--
libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd E:\teach\myLearn\node_modules\node-sass
gyp ERR! node -v v6.7.0
gyp ERR! node-gyp -v v3.5.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fseve
<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>bu
t none was installed.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\
node_modules\\npm\\bin\\npm-cli.js" "install" "node-sass"
npm ERR! node v6.7.0
npm ERR! npm  v3.10.3
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'node scripts/build.js
'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs node-sass
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     E:\teach\myLearn\npm-debug.log

When reporting an bug, you must provide this information:

NPM version (npm -v):
3.10.3
Node version (node -v):
6.7.0
Node Process (node -p process.versions):
{ http_parser: '2.7.0
node: '6.7.0',
v8: '5.1.281.83',
uv: '1.9.1',
zlib: '1.2.8',
ares: '1.10.1-DEV',
icu: '57.1',
modules: '48',
openssl: '1.0.2j' }
Node Platform (node -p process.platform):
win32
Node architecture (node -p process.arch):
x64
node-sass version (node -p "require('node-sass').info"):
module.js:583
return process.dlopen(module, path._makeLong(filename));
^

Error: The process cannot access the file because it is being used by another pr
ocess.
\?\E:\teach\myLearn\node_modules\node-sass\vendor\win32-x64-48\binding.node
at Error (native)
at Object.Module._extensions..node (module.js:583:18)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at module.exports (E:\teach\myLearn\node_modules\node-sass\lib\binding.js:19
:10)
at Object. (E:\teach\myLearn\node_modules\node-sass\lib\index.js:
14:35)
at Module._compile (module.js:556:32)

npm node-sass versions (npm ls node-sass):
<EMAIL_ADDRESS>E:\teach\myLearn
+--<EMAIL_ADDRESS>`-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>
npm ERR! peer dep missing<EMAIL_ADDRESS>required by extract-text-webpack-plu
<EMAIL_ADDRESS>When encountering a syntax, or compilation issue:

Open an issue on LibSass. You
may link it back here, but any change will be required there, not here

If you delete this text without following it, your issue will be closed.

The problem is that the binary download part way through. So the binary on
disk is faulty. Delete your node_modules and try again.
On 9 Feb. 2017 8:29 pm, "sdhhqb"<EMAIL_ADDRESS>wrote:

After update dependencies in package.json, run "npm install" failed when
installing node-sass. I tried a few times, it seems download
'win32-x64-48_binding.node' always failed.
My node registry is set to cnpm 'http://r.cnpmjs.org/', does it influence
the installation? But I can installed node-sass successfully few weeks ago
when I didn't update dependencies .
Here is my dependencies in package.json.
"dependencies": {
"isomorphic-fetch": "^2.2.1",
"react": "^15.4.2",
"react-dom": "^15.4.2",
"react-redux": "^5.0.2",
"react-router-redux": "^4.0.7",
"redux": "^3.6.0",
"redux-logger": "^2.8.1",
"redux-thunk": "^2.2.0"
},
"devDependencies": {
"babel-core": "^6.22.1",
"babel-loader": "^6.2.10",
"babel-preset-es2015": "^6.22.0",
"babel-preset-react": "^6.22.0",
"babel-preset-stage-0": "^6.22.0",
"css-loader": "^0.26.1",
"extract-text-webpack-plugin": "^1.0.1",
"file-loader": "^0.10.0",
"html-webpack-plugin": "^2.28.0",
"node-sass": "^4.5.0",
"react-router": "^3.0.2",
"sass-loader": "^5.0.1",
"style-loader": "^0.13.1",
"url-loader": "^0.5.7",
"webpack": "^2.2.1",
"webpack-dev-server": "^2.3.0"
}
The error log.
E:\teach\myLearn>npm install node-sass
npm WARN deprecated<EMAIL_ADDRESS>This package is deprecated. Use Object.
assign.
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g

<EMAIL_ADDRESS>install E:\teach\myLearn\node_modules\node-sass
node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.5
.0/win32-x64-48_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.5.0/win3
2-x64-48_binding.node https://github.com/sass/node-sass/releases/download/v4.5.0/win32-x64-48_binding.node":
ESOCKETTIMEDOUT
Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.
  export HTTP_PROXY=http://example.com:1234

or configure npm proxy via
  npm config set proxy http://example.com:8080

<EMAIL_ADDRESS>postinstall E:\teach\myLearn\node_modules\node-sass
node scripts/build.js

Binary found at E:\teach\myLearn\node_modules\node-sass\vendor\win32-x64-48\bind
ing.node
Testing binary
Binary has a problem: Error: %1 is not a valid Win32 application.
\?\E:\teach\myLearn\node_modules\node-sass\vendor\win32-x64-48\binding.node
at Error (native)
at Object.Module._extensions..node (module.js:583:18)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at module.exports (E:\teach\myLearn\node_modules\node-sass\lib\binding.js:19
:10)
at Object. (E:\teach\myLearn\node_modules\node-sass\lib\index.js:
14:35)
at Module._compile (module.js:556:32)
Building the binary locally
Building: C:\Program Files\nodejs\node.exe E:\teach\myLearn\node_modules\node-gy
p\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_l
dflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ 'C:\Program Files\nodejs\node.exe',
gyp verb cli   'E:\teach\myLearn\node_modules\node-gyp\bin\node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library=' ]
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| win32 | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb which failed Error: not found: python2
gyp verb which failed     at getNotFoundError (E:\teach\myLearn\node_modules\w
hich\which.js:13:12)
gyp verb which failed     at F (E:\teach\myLearn\node_modules\which\which.js:6
8:19)
gyp verb which failed     at E (E:\teach\myLearn\node_modules\which\which.js:8
0:29)
gyp verb which failed     at E:\teach\myLearn\node_modules\which\which.js:89:1
6
gyp verb which failed     at E:\teach\myLearn\node_modules\isexe\index.js:44:5
gyp verb which failed     at E:\teach\myLearn\node_modules\isexe\windows.js:29
:5
gyp verb which failed     at FSReqWrap.oncomplete (fs.js:123:15)
gyp verb which failed  python2 { Error: not found: python2
gyp verb which failed     at getNotFoundError (E:\teach\myLearn\node_modules\w
hich\which.js:13:12)
gyp verb which failed     at F (E:\teach\myLearn\node_modules\which\which.js:6
8:19)
gyp verb which failed     at E (E:\teach\myLearn\node_modules\which\which.js:8
0:29)
gyp verb which failed     at E:\teach\myLearn\node_modules\which\which.js:89:1
6
gyp verb which failed     at E:\teach\myLearn\node_modules\isexe\index.js:44:5
gyp verb which failed     at E:\teach\myLearn\node_modules\isexe\windows.js:29
:5
gyp verb which failed     at FSReqWrap.oncomplete (fs.js:123:15) code: 'ENOENT
' }
gyp verb check python checking for Python executable "python" in the PATH
gyp verb which succeeded python C:\python27\python.EXE
gyp verb check python version C:\python27\python.EXE -c "import platform; print (platform.python_version());" returned: "2.7.11\r\n"
gyp verb get node dir no --target version specified, falling back to host node v
ersion: 6.7.0
gyp verb command install [ '6.7.0' ]
gyp verb install input version string "6.7.0"
gyp verb install installing version: 6.7.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version is already installed, need to check "installVersion"
gyp verb got "installVersion" 9
gyp verb needs "installVersion" 9
gyp verb install version is good
gyp verb get node dir target node version installed: 6.7.0
gyp verb build dir attempting to create "build" dir: E:\teach\myLearn\node_modul
es\node-sass\build
gyp verb build dir "build" dir needed to be created? 若要启用并行生成，请添加“/m”开关。
生成启动时间为 2017/2/9 16:53:05。
节点 1 上的项目“E:\teach\myLearn\node_modules\node-sass\build\binding.sln”(默
认目标)。
ValidateSolutionConfiguration:
正在生成解决方案配置“Release|x64”。
MSBUILD : error MSB3428: 未能加载 Visual C++ 组件“VCBuild.exe”。要解决此问题，

安装 .NET Fram
ework 2.0 SDK；2) 安装 Microsoft Visual Studio 2005；或 3) 如果将该组件安装到了
其他位置，请将其位置添加到系统
路径中。 [E:\teach\myLearn\node_modules\node-sass\build\binding.sln]
已完成生成项目“E:\teach\myLearn\node_modules\node-sass\build\binding.sln”(默认
目标)的操作 - 失
败。

生成失败。
“E:\teach\myLearn\node_modules\node-sass\build\binding.sln”(默认目标) (1) ->
(src\libsass 目标) ->
MSBUILD : error MSB3428: 未能加载 Visual C++ 组件“VCBuild.exe”。要解决此问题
，1) 安装 .NET Fr
amework 2.0 SDK；2) 安装 Microsoft Visual Studio 2005；或 3) 如果将该组件安装到
了其他位置，请将其位置添加到
系统路径中。  System Windows_NT 6.1.7601
gyp ERR! command "C:\Program Files\nodejs\node.exe" "E:\teach\myLearn\node
_modules\node-gyp\bin\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--
libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd E:\teach\myLearn\node_modules\node-sass
gyp ERR! node -v v6.7.0
gyp ERR! node-gyp -v v3.5.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fseve
<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>bu
t none was installed.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\
node_modules\npm\bin\npm-cli.js" "install" "node-sass"
npm ERR! node v6.7.0
npm ERR! npm  v3.10.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'node scripts/build.js
'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs node-sass
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     E:\teach\myLearn\npm-debug.log
When reporting an bug, you must provide this information:

NPM version (npm -v):
3.10.3
Node version (node -v):
6.7.0
Node Process (node -p process.versions):
{ http_parser: '2.7.0
node: '6.7.0',
v8: '5.1.281.83',
uv: '1.9.1',
zlib: '1.2.8',
ares: '1.10.1-DEV',
icu: '57.1',
modules: '48',
openssl: '1.0.2j' }
Node Platform (node -p process.platform):
win32
Node architecture (node -p process.arch):
x64
node-sass version (node -p "require('node-sass').info"):
module.js:583
return process.dlopen(module, path._makeLong(filename));
^

Error: The process cannot access the file because it is being used by
another pr
ocess.
?\E:\teach\myLearn\node_modules\node-sass\vendor
win32-x64-48\binding.node
at Error (native)
at Object.Module._extensions..node (module.js:583:18)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at module.exports (E:\teach\myLearn\node_modules\node-sass\lib\binding.
js:19
:10)
at Object. (E:\teach\myLearn\node_modules\node-sass\lib\index.js:
14:35)
at Module._compile (module.js:556:32)

npm node-sass versions (npm ls node-sass):
<EMAIL_ADDRESS>E:\teach\myLearn
+--<EMAIL_ADDRESS>`-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>
npm ERR! peer dep missing<EMAIL_ADDRESS>required by
extract-text-webpack-plu
<EMAIL_ADDRESS>When encountering a syntax, or compilation issue:

Open an issue on LibSass https://github.com/sass/LibSass/issues/new.
You
may link it back here, but any change will be required there, not here

If you delete this text without following it, your issue will be closed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/1888, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWAx2UB1Ar_Pieff9NsZuOEOlas1aks5ratxogaJpZM4L75BP
.

I have found a solution.
After installed failed, a node-sass\4.5.0 folder is still created in npm-cache folder. So I download win32-x64-48_binding.node manually, put it in C:\Users\Administrator\AppData\Roaming\npm-cache\node-sass\4.5.0 folder.
Then I can install node-sass successfully.

+1
i have tried many times，but still error
Binary found at D:\app\tp-social-recruit\node_modules\node-sass\vendor\win32-x64-48\binding.node
Testing binary
Binary has a problem: Error: %1 is not a valid Win32 application.
\\?\D:\app\tp-social-recruit\node_modules\node-sass\vendor\win32-x64-48\binding.node

then i install it offline，it log error
Module build failed: Error: ENOENT: no such file or directory, scandir 'D:\application\demo\node_modules\node-sass\vendor'

Getting the same issue on Windows 8 x64

@sdhhqb put win32-x64-48_binding.node  into npm-cache, it can work by using npm, but not yarn

Getting the same issue on Windows 10 x64.
"node-sass": "^4.5.0"

When I run npm install node-sass I get

<EMAIL_ADDRESS>install /usr/home/****/node_modules/node-sass
node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.5.0/freebsd-x64-51_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.5.0/freebsd-x64-51_binding.node":
HTTP error 404 Not Found
so the file freebsd-x64-51_binding.node does not exist. Where can one find this file?
Regards,
Daniele.

As work around run npm cache clean.

Ok here is what worked for me.

Download the binary file and put into temp directory
Set the sass binary path in CMD: SET SASS_BINARY_PATH=C:/temp/win32-x64-51_binding.node
For bash/powershell (https://github.com/sass/node-sass/issues/1106#issuecomment-134559641)
npm install

Thank you @xzyfer, this works for me
$ npm cache clean && npm install node-sass

Hey thank you @Pizdetss its working now

i worked with cnpm install

@Pizdetss, it works for me on Win7, thanks

@sdhhqb oh my goodness, thank you baby jesus .  I have been trying to get past this issue for hours, you saved me!

Why is this issue closed?
I just got this after trying to update my application from Node-4.2.2 to latest LTS. No idea how to solve this on a project with more than hundred dependencies.

Delete your node_modules, clear your npm caches, and npm install
On 4 Jul. 2017 8:50 pm, "Daniel Sundberg"<EMAIL_ADDRESS>wrote:

Why is this issue closed?
I just got this after trying to update my application from Node-4.2.2 to
latest LTS. No idea how to solve this on a project with more than hundred
dependencies.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/1888#issuecomment-312847552,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWLJvk9uRJ6QO8tKOFmkww4FyndoJks5sKhi0gaJpZM4L75BP
.

@xzyfer yes done that, doesn't work

Yes, 3.6.0 doesn't have official Node 6 support https://github.com/sass/node-sass/releases/tag/v3.6.0
You should update if you want to use that version of Node

@nschonni, yes I realize that. However, I don't like to change more than one variable at a time so I started with node version. Now I changed strategy and start with updating dependencies instead.

I had same issue for<EMAIL_ADDRESS>Downloading win32-x64-48_binding.node manually and putting it in C:\Users\Administrator\AppData\Roaming\npm-cache\node-sass\4.5.3 folder fixed the issue.

I had the same issue on WIn7 x64 and I have downloaded as others have mentioned https://github.com/sass/node-sass-binaries/blob/master/win32-x64-48_binding.node
and place it inside C:\Users<myUserID>\npm-cache\node-sass\4.5.5 folder fixed the issue.
I did find the location of my cache by running : npm cofig list

Is that (on the website https://github.com/sass/node-sass-binaries/)
win32-x64-48_binding.node	Windows, Linux, and OSX binaries for LibSass 3.4.0-RC1

the current version? Updated one year ago and still release candidate ?
thank you for your feedbacks,..


[Web Portal] fix job v2 detail page rendering error

job v2's config file may not have taskRoles property

Coverage remained the same at 52.647% when pulling d40ca325383f218d8c1258489d31ffb5cc00774d on qinsu/v2-master into 4b45100869ae33b3654c5b7aa04d84366263bf0a on master.


WIP docker support

Still to do

[x] Pull in vega js libraries for offline use
[x] Make img url prefix configurable
[x] Mock up StolenCameraFinder page(s)
[ ] Push to dockerhub

Hey @jeffbaumes there are a ton of commits here - best to commit this now so we have something to baseline from. If I don't hear objections I will commit this in the next 24 hours.


Outputs from cells suddenly only displaying text

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.65.0
OS Version: macOS 12.2.1

Steps to Reproduce:
Previously when doing df.head() or df.plot.line() I would see the output right away. Now all I get are descriptions of what the object type is.

This is what I see when I click on "Change presentation"

I'm not seeing this with the latest releases so I'll close for now since this issue is several months old. Could you comment or open another issue if this is still occurring?


Resolve The request-body formulation for callback bequeath-your-data-and-die should be modified

Fixes #281

Reviewer is @PrathibaJee


nixos/hardware/hackrf: new module

This is a very this module to enable the
hackrf udev rules and ensure the "plugdev"
group they use exists.

Motivation for this change
Want to use HackRF device as a normal user.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

imho we don't need to document this in the release notes, since it will appear to the people looking for it in the the options?

Any chance to backport this to 21.11?

Not sure if just adding the label is enough to make the bot pick it up


DBSCAN - Documentation

Can I work on this issue???

Task : Create detailed documentation of the DBSCAN ML algorithm by updating readme.md
Level-1 : 10 points

May i work on this documentation?

@aanchalsethi Let's get #83 merged first,you have claimed both base and documentation,then you can work on either of your choice

I would like to work on this Issue

Hii...I am a GSSOC'21 participant, and I would like to work on this issue. Please assign this issue to me.

Hi @ashwani-rathee I am eager to contribute to this issue. Kindly assign it to me.

@Charanjeev-2k2 Sure,go ahead

Sir i already have pulled the request for this document.
On Fri, Apr 16, 2021 at 10:45 AM Ashwani Rathee @.***>
wrote:

@Charanjeev-2k2 https://github.com/Charanjeev-2k2 Sure,go ahead
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Algo-Phantoms/Algo-ScriptML/issues/69#issuecomment-820911532,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP7JVTUAZ3OZ24FHK3GNC23TI7BY3ANCNFSM4ZEF63MA
.

@Charanjeev-2k2 what are the updates?

@Charanjeev-2k2 what are the updates?
On it
Had semester end exams in between. Will be putting up the pr before May 31st
Sorry for the delay

Can I work on this @yukti845 @geekquad @ashwani-rathee?

Already there @Manasi2001.


[JavaScript][Author] TypeScript Tutorial Added By Sepehr Ashrafzadeh , Ali Alaee , Mohsen Larni

Midterm Paper.pdf

Dear Sepehr,
Since markdown files are more readable in github than PDF, would you please compose a readme.md file and then create a PR?
Thanks,
Mostafa

Hi ,
Sorry , I wrote it in the latex . It's quite difficult . Is it possible for you to accept it the way it is ?

As I've mentioned in the telegram group, there isn't problem if you don't want to contribute in the repository. The key thing is just having translated a rich source of the main topic (in your case TypeScript). The content should have more details and it can be delivered in any format, such as:
PDF, markdown, docx, etc.


Feat: Enhancing About Section, Feature Section, Customized Scroll Bar

Describe the feature

About Section Makeover:

The current about section lacks visual appeal and needs a refresh.
We propose revamping it to be more engaging and informative.
This could involve:
Compelling visuals like high-quality images or a short video.

Feature Section Enrichment:

Currently, the feature section only displays icons. This doesn't effectively communicate the value proposition of these features.
We propose enriching the section to provide more context for each feature.
This could include:
Short, descriptive text explaining the functionality and benefits of each feature.
Interactive elements like tooltips or hover effects for additional details.

Customizable Scrollbar:

The current scrollbar may not be visually integrated with the website's overall theme.
We propose allowing customization of the scrollbar.
This includes:
The ability to adjust the width of the scrollbar for a cleaner or more prominent look.
Options to choose a color for the scrollbar that complements the website's color scheme.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@Its-Aman-Yadav Sir request you to assign this task to me under GSSOC'24.


Firebase best practices

Let's create a Firebase / Miscellaneous doc with best practices, including:

https://gitlab.com/c-hive/firebase-paypal/merge_requests/3#note_172773804
https://gitlab.com/c-hive/firebase-paypal/issues/4

Same format as https://github.com/c-hive/guides/blob/cefa90fdd6c8cec9ac87ef23cfc0871a7fdc5b7a/js/error-handling.md#best-practices-and-anti-patterns
@gomorizsolt could you take care of this?

Resolved by #16.


Requirements update + relocation

This PR is a follow up to an email sent to the maintainers of this certified collection notifying them of a few new changes that will be needed for the next Ansible Automation Platform release. Contained in this PR is an example python requirements file built specifically for your collection. You can elect to merge this as is and edit as needed or close the PR and use it as an example to base your own commit off of. if you have any questions about why this PR was sent or confused about its necessity, please don't hesitate to ask in the comments here or email us at<EMAIL_ADDRESS>Change Summary
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes)
[ ] Documentation content changes
[x] Other (please describe): Ansible requirements

Related Issue(s)
Replace PR #769
Checklist:

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have updated molecule CI testing accordingly
[x] All new and existing tests passed (pre-commit, make linting and make sanity-lint).

Issue in MKDOC check is expected as requirements file is not yet available in devel.


Error during randomizations

Using this command:
python /home/nlpm/packages/OmicsIntegrator2/src/parameter_sweep.py -e /home/nlpm/OI2_Networks/interactome/iref14_Recon2_Htt_mzMatchedMet_OI2_interactome.txt -p /home/nlpm/OI2_Networks/terminals/Cypro_all_terminals.txt -o /home/nlpm/OI2_Networks/networks/Cypro/randomizations/ -w 3 6 9 12 -b 0.25 0.5 0.75 1 2 -g 5 10 20 --noisy_edges=100 --random_terminals=100 -noise=0.04567861 --seed=1

I got this error:
10:59:30 - Graph: INFO - {'w': 12.0, 'b': 2.0, 'g': 20.0, 'noise': 0.04567861, 'exclude_terminals': False, 'seed': 1, 'noisy_edges_repetitions': 100, 'random_terminals_repetitions': 100}
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
  File "/net/dorsal/apps/python361/lib/python3.6/multiprocessing/pool.py", line 119, in worker
    result = (True, func(*args, **kwds))
  File "/net/dorsal/apps/python361/lib/python3.6/multiprocessing/pool.py", line 44, in mapstar
    return list(map(*args))
  File "/home/nlpm/packages/OmicsIntegrator2/src/graph.py", line 525, in _eval_randomizations
    forest, augmented_forest = self.randomizations(params["noisy_edges_repetitions"], params["random_terminals_repetitions"])
  File "/home/nlpm/packages/OmicsIntegrator2/src/graph.py", line 492, in randomizations
    forest, augmented_forest = self.output_forest_as_networkx(vertex_indices.node_index.values, edge_indices.edge_index.values)
  File "/home/nlpm/packages/OmicsIntegrator2/src/graph.py", line 322, in output_forest_as_networkx
    forest.add_nodes_from(list(set(self.nodes[vertex_indices]) - set(forest.nodes())))
  File "/home/nlpm/packages/OmicsIntegrator2/venv/lib/python3.6/site-packages/pandas/core/indexes/base.py", line 1700, in __getitem__
    result = getitem(key)
IndexError: arrays used as indices must be of integer (or boolean) type
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/nlpm/packages/OmicsIntegrator2/src/parameter_sweep.py", line 116, in <module>
    main()
  File "/home/nlpm/packages/OmicsIntegrator2/src/parameter_sweep.py", line 102, in main
    results = graph.grid_search_randomizations(args.prize_file, params)
  File "/home/nlpm/packages/OmicsIntegrator2/src/graph.py", line 561, in grid_search_randomizations
    results = pool.map(self._eval_randomizations, all_params)
  File "/net/dorsal/apps/python361/lib/python3.6/multiprocessing/pool.py", line 260, in map
    return self._map_async(func, iterable, mapstar, chunksize).get()
  File "/net/dorsal/apps/python361/lib/python3.6/multiprocessing/pool.py", line 608, in get
    raise self._value
IndexError: arrays used as indices must be of integer (or boolean) type

@natashapm did we manage to resolve this?

Yes, that error was resolved.  I might've come across another error, but I'll revisit it in the next couple of days.  I need to fully debug my side of it.


Make sure datatables are fixed on master

See #1367 (specifically this comment) for details, make sure that datatables work after merging in the fix for #1378 onto master.

Yup we're all good!


Getting object null error when creating a new instance of TabItem

I'm creating a control using AuraTabView. I'm trying to add a default tab in C# but keep getting object null error when creating a new AuraTabItem. Should I not be adding it here?

This is my fault. Didn't set the Content property. Sorry


Telogator2 performance across different sequencing coverage

Hello,
I have a question regarding the performance of Telogator2 under varying coverage. While Figure 10 of your paper illustrates that the number of identified telomere alleles increases with higher coverage, I was wondering if you had conducted any tests to assess how the accuracy of the estimates changes with coverage. Specifically, is there an observed bias/trend?
I apologize if this is not the best platform to ask, but before proceeding with my analyses, I’d like to better understand how coverage might influence the estimate itself.
Any insight would be helpful!
Thank you!!

At one point we had a figure that showed the variance of ATL values at the same coverage points as the #alleles plot. I don't recall the precise values but the results were as expected in that the variance increases a lot as coverage gets lower. In older experiments (that predate Telogator2) we tested simulated data and found that at ~5-10x coverage the average error in TL measurement was around a kilobase, at 10-20x range it decreased to a few hundred bp, and at 30+x was maybe 100bp. Though real data is not going to be as uniformly distributed across alleles, and alleles with lower read counts are going to be rougher estimates.

Thank you, this is really helpful!


When using dynamic imports, dead code elimination no longer works for chunks.

Bug report
When using dynamic imports, tree shaking no longer works for generated chunks.
A small reproducible example can be found here.
Working:
If the entrypoint does not use dynamic imports and imports statically, the dead code is removed from the bundle.
Expected:
Each chunk should have its own static analysis context, and the sum.js chunk should not include the product function from lib.js, and vice versa for the product.js chunk.
Versions
webpack version:  4.11.1
Node.js version: 10.2.0
Operating System: macOS 10.12
Additional tools:

This is the expected behavior. Tree shaking is not supported on async chunks.

Why? I'm using dynamic imports as the mechanism to split journeys, where the main entrypoint loads the journey and configures the app in a way common to all journeys (ReactDOM render, store setup, etc.).
The chunks being loaded are effectively standalone, and could be statically analysed and have dead code marked per-chunk.
Is there a technical reason that DCE can't be achieved in this configuration?
Are we worried that the main chunk will try to get something out of the dynamic bundle that's been eliminated?
What if there was an option to say we won't do that, like /* webpackChunkSideEffects: false */ in the import?

cc @sokra

The chunks being loaded are effectively standalone, and could be statically analysed and have dead code marked per-chunk.

Sadly this is not true. You could load both chunks at the same time. In this case module caching kicks in and same module must not be evaulated twice.
Note that this doesn't matter in your case because you only exporting pure functions, but technically both function could share a common counter. Because of this (edge-case) modules must be equal in all chunks (or at least in all chunks sharing a runtime chunk).
Currently you have to split your module into two if you want to have per-chunk tree shaking. You can do export * from "./sum"; export * from "./product" if "sideEffects": false is specified in package.json. In this case webpack will only include the used module.

That is a shame 😕.
It looks like to get the sort of configuration I want I'll have to look at using bundle-loader for this, and have a separate entry for each of these bundles.
Thanks for weighing in.


mongomock throws error on count operation

I have a method where i need to find the count of document in a collection
i have  a team collection Class Team and mocking using mongo mock it throw the error'Cursor' object has no attribute '_Cursor__spec' query used isTeam.objects.count()

I'm facing the same problem using MongoEngine as described in https://github.com/MongoEngine/mongoengine/issues/2425

Same here, it seems to be that from mongoengine==0.21.0 the crash appears

I've pinged the original bug on mongoengine: I believe it's not a feature that mongomock should implement given that _Cursor__spec is not part of the public API of pymongo

The original bug MongoEngine/mongoengine#2425 has been fixed another way. Closing this.


Windows msvc 2019 build broken [again]

Master branch, latest - I've also tried several others.  cmake 3.20.0-rc1. (edit: just updated to cmake 3.20.3 release as a sanity check, same behavior)
Additionally - tess v4.1.1 doesn't build with cmake + sw. (line 61 of sw.cpp needs to concat _slib, not _l) so I'm working from 5 alpha + master.

Can anybody point me to a commit that will compile?
Hiccup appears to be here: loc.sw.self.f28e64-0.0.28.dll
Visual Studio 16 2019 Generator.

FWIW, this appears to be an issue with sw - the vcpkg route worked for me, and resulted in a clean build of 4.1.1.

Update VS2019 to 16.10.


mid360 support

LIO-Livox now supports Mid360 sensors. Do you plan to reintegrate with the updated version of LIO-Livox.
I am trying to do it myself https://github.com/dbaldzhiev/Livox-Mapping but with no success.
My fork compiles fine but then :
[pcl::SampleConsensusModel::getSamples] Can not select 0 unique points out of 0! [pcl::RandomSampleConsensus::computeModel] No samples could be selected! [PoseEstimation-3] process has died [pid 16720, exit code -11, cmd /root/ws_livox_mapping/devel/lib/livox_odometry/PoseEstimation __name:=PoseEstimation __log:=/root/.ros/log/e1984e1e-e8be-11ed-84b0-0242ac110002/PoseEstimation-3.log]. log file: /root/.ros/log/e1984e1e-e8be-11ed-84b0-0242ac110002/PoseEstimation-3*.log

Currently, no.
Please check your input point cloud status, like whether it is empty

When I used the MID-360, the following warning message appeared：
[ WARN] [1716780577.472366015]: TF_REPEATED_DATA ignoring data with redundant timestamp for frame aft_pgo (parent camera_init) at time<PHONE_NUMBER>.395308 according to authority unknown_publisher

It seems to be due to the inconsistent frame base name? Since in this repo, we hard-coded some famebase names


Unable to find app on Marketplace

Plugin is no longer able to be found on Marketplace

Hmm, I still see it in the marketplace though.

Odd, after restarting the Logseq app out about 3 times it has appeared - now im having trouble getting my settings to stick!

Oh so sorry to hear that. Did you click Save and Close? You can then go into the settings.json file after that to see if it really got saved.

If you are still experiencing this, please try v3.2 in the marketplace.


Remove Params from Handler and use ctx.UserValue instead

This PR uses: func(ctx *fasthttp.RequestCtx)
Instead of: func(ctx *fasthttp.RequestCtx, ps fasthttprouter.Params)
And
Replaces Params with RequestCtx.UserValues
So that:

Chaining of other fasthttp based middleware functions is much easier.
Removes the only major memory allocation that is happening in fasthttprouter/httprouter

Coverage remained the same at 100.0% when pulling a4aeb2133700127fdb724f12bacad6bdac831277 on gofury:master into 0729217d031ab353a3e34b94e8544e167f7ce9a4 on buaazp:master.

Closing and re-submitting from a branch


Driver: DigitalOcean Volume Support

This is a first pass at adding DigitalOcean Volume support to Convoy. I tried as best as possible to adhere to the practices in the ebs and other Drivers. Currently, DigitalOcean does not support Snapshots or Backups in their Volume product, so those are not implemented.
The Driver requires an API token, DO_TOKEN be set in the environment of the daemon. If additional configuration methods are important, I am happy to add support for a file somewhere, but there is no convention in the DO driver like in the AWS driver.
There are not integration tests (yet) as there are with AWS. If there is interest, I am happy to look at adding them.
This is light on documentation - upon acceptance of this code, I am happy to add some literature to the README and elsewhere.
If anyone from Rancher or the Convoy project would like to test, I am more than happy to supply some DigitalOcean credit to your testing account(s).
Let me know if there are any questions!

Test failures after vendoring godo seem to be due to space issues on the host running Docker.

Thanks @nickvanw , sorry for late reply, Github notification for PR never works...
I am reviewing the code, and fixing Drone

Hi @nickvanw
In general the driver looks great! I think we can have some unit tests like in ebs_service_test.go for the first step, as well as some document for the topic.
We can look into integration test later. I can merge upon the available of unit test and documents.
Thanks!

Hi @yasker - awesome! I will get on that today or tomorrow and ping you when the commits are available for review. Thanks!

Hi @nickvanw
I think there are other vendors you need to pull in.
digitalocean/digitalocean_client.go:8:2: cannot find package "github.com/digitalocean/go-metadata" in any of:
       	/go/src/github.com/rancher/convoy/vendor/github.com/digitalocean/go-metadata (vendor tree)
       	/usr/local/go/src/github.com/digitalocean/go-metadata (from $GOROOT)
       	/go/src/github.com/digitalocean/go-metadata (from $GOPATH)
vendor/github.com/digitalocean/godo/godo.go:15:2: cannot find package "github.com/google/go-querystring/query" in any of:
       	/go/src/github.com/rancher/convoy/vendor/github.com/google/go-querystring/query (vendor tree)
       	/usr/local/go/src/github.com/google/go-querystring/query (from $GOROOT)
       	/go/src/github.com/google/go-querystring/query (from $GOPATH)
vendor/github.com/digitalocean/godo/godo.go:16:2: cannot find package "github.com/tent/http-link-go" in any of:
       	/go/src/github.com/rancher/convoy/vendor/github.com/tent/http-link-go (vendor tree)
       	/usr/local/go/src/github.com/tent/http-link-go (from $GOROOT)
       	/go/src/github.com/tent/http-link-go (from $GOPATH)
digitalocean/digitalocean_client.go:10:2: cannot find package "golang.org/x/net/context" in any of:
       	/go/src/github.com/rancher/convoy/vendor/golang.org/x/net/context (vendor tree)
       	/usr/local/go/src/golang.org/x/net/context (from $GOROOT)
       	/go/src/golang.org/x/net/context (from $GOPATH)
digitalocean/digitalocean_client.go:11:2: cannot find package "golang.org/x/oauth2" in any of:
       	/go/src/github.com/rancher/convoy/vendor/golang.org/x/oauth2 (vendor tree)
       	/usr/local/go/src/golang.org/x/oauth2 (from $GOROOT)
       	/go/src/golang.org/x/oauth2 (from $GOPATH)

Good catch! wasn't able to get Drone to continue running and it worked in my local env. Will get this added in soon as well!

Hey @yasker, sorry for the delay! I should have everything vendored (in a single commit, to make it easier to review) properly now.
In addition, I added a basic test in the style of the EBS tests, as well as some light documentation to the README.md. Let me know if there is anything else I can/should do!

💯
Fantastic work here @nickvanw!

README.md Typos have been fixed as well!

LGTM. I will merge it soon.
It's better to have more documents, like ebs. And enable integration test for it. We can work on those later though.


Plugin Refactor to use arbitrary state machines

Goal:
Propeller should support more types of transitions so that plugin
writers can handle cases where it is not possible to get idempotency
from downstream services. Also provide a simplified API that makes
writing plugins easy.
Done:

New Node handler interface
Implemented Task handler
Implemented Dynamic handler
modified node executor
Unit tests for end to end

It seems this big change has not been reflected in sandbox deployment because it keeps crashing due to configuration structure change. @kumare3


Allow using version catalog plugins without version

Fixes #18236
Fixes #18467
Changes:

plugins can now have no version in version catalog: with API this can be done with alias("alias").toPluginId("id").withoutVersion(), in TOML you can do any of:

[plugins]
my-plugin1 = "plugin.id"
my-plugin2 = { id = "plugin.id" }
my-plugin3 = { id = "plugin.id"  version = ""}

generated accessors for plugins now implements PluginDependencyProvider that have getWithoutVersion() method, so you can do:

plugins {
    alias(libs.my.plugin.withoutVersion)
}

PluginDependenciesSpec now implements alias as default method due to #18467

I am not perfectly happy with alias(libs.my.plugin.withoutVersion) it feels verbose, but other solutions are trickier.
Maybe alternative alias(libs.my.plugin).withoutVersion() could be interesting, but in that case we should change logic of alias(libs.my.plugin).version(null): now it fails, but it could set version to unspecified. Interestingly docs of PluginDependencySpec already say that null does that.

Closed in favor of #19015


Kafka <IP_ADDRESS>

Currently RC, which is why we build from source

Test results with e8b6fb4 reverted are "3332 tests completed, 57 failed". Same if I use the scala version from gradle.properties and the gradle version that the build downloads anyway:
-ENV KAFKA_VERSION=<IP_ADDRESS>-rc2 SCALA_VERSION=2.12.2
+ENV KAFKA_VERSION=<IP_ADDRESS>-rc2 SCALA_VERSION=2.11.11

 RUN set -e; cd /usr/local; \
-  GRADLE_VERSION=4.0 PATH=$PATH:$(pwd)/gradle-$GRADLE_VERSION/bin; \
+  GRADLE_VERSION=3.5 PATH=$PATH:$(pwd)/gradle-$GRADLE_VERSION/bin; \

Built as solsson/kafka:<IP_ADDRESS>-rc2@sha256:713869ff8d04840f3dfd6d002463124dbad0a5b7182fcdb5f15b200b35dbe65d. No layer optimizations done, so both build environment and source there.

Todos:

[ ] Keep only the stuff necessary for ./bin stuff we want to support (jars, config)
[ ] Disable logging to files. Log everything to stdout. Reduces runtime overhead.

This PR and https://github.com/solsson/dockerfiles/pull/4 might trigger need for an update to https://github.com/kubernetes/charts/tree/master/incubator/kafka, see https://github.com/kubernetes/charts/pull/144 for history there.

Kafka <IP_ADDRESS> has been released. Latest build from that tag is solsson/kafka:<IP_ADDRESS>@sha256:4c194db2ec15698aca6f1aa8a2fd5e5c566caed82b4bf43446c388f315397756.

Splitting this effort into #5 (solsson/kafka) and #6 (solsson/kafka-alpine).