bower: not found

npm ERR! Linux 4.4.13+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "install-libs"
npm ERR! node v6.3.1
npm ERR! npm  v3.10.3
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>install-libs: bower install
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install-libs script 'bower install'.
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 pogo-optimizer package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     bower install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs pogo-optimizer
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls pogo-optimizer
npm ERR! There is likely additional logging output above.

Did you take a look @ https://github.com/justinleewells/pogo-optimizer/issues/113


Querying not usable Stamp returns 400

Summary
When querying stamp by ID that was newly created and is still not usable the HTTP request fails with 400 instead of returning the Stamp object with usable: false.
This happens because there is a check in GetStampIssuer for usability which fails because of it.
Steps to reproduce

Create stamp
Query the stamp by ID before it becomes usable

Expected behavior
Returned object with usable: false
Actual behavior
HTTP 400 with
time="2021-07-29T07:14:50Z" level=debug msg="get stamp issuer: get issuer: not usable"
time="2021-07-29T07:14:50Z" level=error msg="get stamp issuer: get issuer"
time="2021-07-29T07:14:50Z" level=info msg="debug api access" duration=0.0004778 ip=<IP_ADDRESS> method=GET proto=HTTP/1.1 size=44 status=400 uri=/stamps/b75f5afe387b19057aed57f68f3704a0920b0b0bfab856bc905e6f76e327d61d user-agent=curl/7.64.1

Would suggest to cover these cases with tests...

Fixed in #2375


use Graph.jl

Should be easy enough -- just get the adjacency matrix from the graph using built-in functions

Boy are the data types a mess. Not sure I want to go this way yet.


Vent Tutorial and RTD documentation written.

Vent tutorial mostly written.

Codecov Report

Merging #793 into master will decrease coverage by 0.1%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #793      +/-   ##
==========================================
- Coverage   77.44%   77.33%   -0.11%
==========================================
  Files          51       51
  Lines        4783     4783
==========================================
- Hits         3704     3699       -5
- Misses       1079     1084       +5

Impacted Files
Coverage Δ

vent/menus/tutorials.py
100% <100%> (ø)
:arrow_up:

vent/menu.py
97.61% <100%> (ø)
:arrow_up:

vent/menus/tutorial_forms.py
100% <100%> (ø)
:arrow_up:

vent/menus/main.py
73.47% <100%> (ø)
:arrow_up:

vent/api/plugins.py
90.34% <0%> (-1.24%)
:arrow_down:

Continue to review full report at Codecov.

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


More NPM vulnerabilities

npm audit on the latest NPM is much more thorough than Github's (#1340).  I get:
[!] 399 vulnerabilities found [13870 packages audited]
    Severity: 379 Low | 8 Moderate | 11 High | 1 Critical

Most of them are on the build/testing side, so don't directly affect us, but we should probably comb through them and cleanup.

Good find.  Can you link to audit?

@kevinbarabash What do you think about automating dependency management, like Greenkeeper? It automatically sends in PRs and open an issue if it breaks the tests.

@ylemkimon that sounds great!

@kevinbarabash Here's a paste (5827 lines!): https://gist.github.com/edemaine/dd1c998483c7fc694584e33a69a2d7dc
You can get it by running npm audit.
#1337 will fix the webpack ones at the top, I imagine.
@ylemkimon Sounds awesome!

@edemaine I tried running npm audit locally but that doesn't seem to be a command in npm v5.6.0.  What version of npm are you running?

@kevinbarabash It is introduced in npm v6.
With #1368 and #1374:
                       === npm audit security report ===

found 0 vulnerabilities
 in 42827 scanned packages


Identify a way to indicate when a data site is down.

MCW is currently down. I was able to know that by asking @gkowalski, but this information would be more difficult to get by a user of the NLP Sandbox.
Task

[x] Create a new page on the website to report the status and history of issues related to the data sites.
[x] Include a section to the website that indicates the status of the data site. Example:

Column 1: Name of the data site
Column 2: Status of the data site: Running or Down

[x] Add a section that include the History of events. See Docker Hub service status page as an example.
[x] Let data sites know how they must provide information about data site up/down status

Done: https://www.synapse.org/#!Synapse:syn22277123/wiki/611634


Without the "config" file

The file "config.js" and "config.json" did not come in the repository. If possible place it please

I'll create the example config file


footer: fixed typo

@erciccione Ok, I've the changed the PR title accordingly.

You changed the title of the PR, but not of the commit, which still says only Fix typo. If you are using github's interface, i'm afraid the easier way to fix this is to close this PR, redo the commit and then open another PR.

@erciccione Happy now?


organize imports

Codecov Report

Merging #34 (27d42c2) into main (8ddd418) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #34   +/-   ##
=======================================
  Coverage   90.74%   90.74%
=======================================
  Files           7        7
  Lines         702      702
=======================================
  Hits          637      637
  Misses         45       45
  Partials       20       20

Continue to review full report at Codecov.

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


Adding in backup prune commands

Codecov Report
Patch coverage: 17.64% and project coverage change: -2.15 :warning:

Comparison is base (a2ec890) 47.75% compared to head (2b98b83) 45.61%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main       #8      +/-   ##
==========================================
- Coverage   47.75%   45.61%   -2.15%
==========================================
  Files           4        4
  Lines         758      809      +51
==========================================
+ Hits          362      369       +7
- Misses        396      440      +44

Impacted Files
Coverage Δ

src/cmcserver/backup.py
9.94% <8.77%> (-1.17%)
:arrow_down:

src/cmcserver/configuration.py
71.62% <50.00%> (-0.61%)
:arrow_down:

src/cmcserver/main.py
81.43% <71.42%> (+0.14%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Update PeerSharing for protocol version 13+

The CBOR format changed for IPv6 peers in protocol version 13 from what was in 11-12

This was done elsewhere


Fix top level return

It seems @sokra doesn't expose any clean hooks for extending the config, so for now we overload the method.
This makes the path-platform integration test pass.

I think we need a test for this 🤔

@timneutkens The test is in https://github.com/zeit/ncc/commit/0a4c78989b548e524140f9f9f2eb4a11a243e0bc

Awesome! Work again in 0.14! Please don't break :)


Cache server env for usage stats collection

Describe your changes and why you are making these changes
When running server with --env , we will cache the env into a file, and the user doesn't need to specify the env again in the future. If the user wants to update the env, they will run the server with --env again and the cache will be updated. If the cached entry doesn't exist, the prod env will be used.
Related issue number (if any)
Loom demo (if any)
Checklist before requesting a review

[x] I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
[x] I have performed a self-review of my code.
[ ] I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
[ ] If this is a new feature, I have added unit tests and integration tests.
[ ] I have run the integration tests locally and they are passing.
[x] I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
[ ] All features on the UI continue to work correctly.
[ ] Added one of the following CI labels:

run_integration_test: Runs integration tests
skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

@kenxu95 good idea. Added it.


Require Validation for Converted Leads Error

Hello! So declarative lookup roll-up summaries was installed on our salesforce way before I took over the account. Unfortunately, I am not familiar with it at all and when I turn on the "Require Validation for Converted Leads" setting I am getting the following error message:
Error: System.DmlException: Insert failed. First exception on row 0; first error: REQUIRED_FIELD_MISSING, Required fields are missing: [Trigger]: [Trigger] Class.leadconvert.BulkLeadConvert.handleOpportunityInserts: line 740, column 1 Class.leadconvert.BulkLeadConvert.convertLead: line 104, column 1
Thoughts on where I might go from here?
Thanks!!

Based on the error message i don't see anything related to DLRS? The easy way to confirm this is to untick the Active field on the rollups and retry your problem. On the face of it, it looks like you have class call leadconvert in your system that is trying to update a record and has not provided all the field values needed. Try reviewing the code around line 740 in the leadconvert class. Sorry i cannot be more help based on the available information. Please feel free to ping back here if you find anything that does point to DLRS and i can try to help further. Thanks! 👍


Sourcemap not working with awesome-typescript-loader

loaders: [
      {
        test: /\.[tj]s$/,
        loaders: ['ng-annotate', 'awesome-typescript-loader'],
        exclude: /node_modules/,
      },

i'm using  devtool: 'cheap-module-source-map', option.
And see in console:

Failed to parse SourceMap: ...

awesome-typescript-loader is version 1.1.1, with typescript 1.8

@thekip does this work without 'ng-annotate' loader?

Surely

Actually it's not so easy to reproduce, i've created a small application and bug is not appear.
Also i turned cheap-module-source-map to inline-cheap-module-source-map and looks like now it works.
I will research more.

Looks like now it works  with cheap-module-source-map as well. I don't know what was the problem.
But now has another problem, file listed twice in source maps, and source map weight is twice bigger.
Symptoms looks same as in this issue: https://github.com/huston007/ng-annotate-loader/issues/23 :

"webpack:///./index.js",
"webpack:///./index.js?2645",
"webpack:///../~/angular/index.js",
"webpack:///../~/angular/index.js?08f2",
"webpack:///../~/angular/angular.js",
"webpack:///../~/angular/angular.js?58d0",

But in my case SourceMaps still work.

Can confirm that this commit fixed the issue for me. What's the status on a npm release of 0.1.2?

Glad to hear! Let's publish it in a next few hours then.

@LucasThielmann Published as 0.2.0


feat(kubernetes): add manifest docs to index

We should wait to merge until 1.6 is released

https://github.com/spinnaker/spinnaker/issues/2231

Merging since 1.6 is out


Unable to 'desactivate' a bank account

I followed the recommendations of your api documentation.
But when I'm trying to 'desactivate' a bank account, I'm getting a Warning and a Fatal Error on MangoPay/Libraries/ApiBase.php file.
Please tell me what I'm doing wrong.
Input:
$bank_account = new ExternalSystemBankAccount();
$bank_account->Id = $bank_account_id;
$bank_account->Active = false;

$result = $this->MangoApi->Users->UpdateBankAccount($user_id, $bank_account);

Output:
PHP Warning:  get_object_vars() expects parameter 1 to be object, null given in .../vendor/mangopay/php-sdk-v2/MangoPay/Libraries/ApiBase.php on line 398 PHP Fatal error:  Uncaught Error: Call to a member function GetReadOnlyProperties() on null in .../vendor/mangopay/php-sdk-v2/MangoPay/Libraries/ApiBase.php:399

Hi @wiseKid,
Could you explain what's on your ExternalSystemBankAccount object? I can't remember this is an object from our SDK / API.
As a reminder, if you want to update an existing bankaccount, you have to get it first thanks to its ID (and not only put its ID on a new object).
Then, put a false value on this bankaccount object, and update it.
If you could provide me some extra details about the way you try to update it, feel free to answer here.
I'll try to help you as fast as I can.
Mickaël

Here you can find some fresh code which tests exactly the functionality that you are targeting:
https://github.com/Mangopay/mangopay2-php-sdk/pull/181/files#diff-1711d9646049db3731a911f79fb57c48R250
Please note that the $this->getJohn() and $this->getJohnsBankAccount() methods both launch API calls through the MangoPayApi->Users service class to retrieve the data.


Fix classes param for checkbox selects

What is the context of this PR?
Bug in checkbox selects where classes aren't being passed because of typo
How to review
Check that checkbox selects work correctly with classes being passed correctly

 Checkbox select class bug


Publisher latching

I see a few instances of latching in the code but there isn't logic to actually publish a latched message, it only sets the flag in the connection header so far?
It looks like it would be a modification to the listener handle https://github.com/Carter12s/roslibrust/blob/master/roslibrust/src/ros1/publisher.rs#L91 to support, have hold onto the last sent message and publish it like in rospy topics.py: https://github.com/strawlab/ros_comm/blob/master/clients/rospy/src/rospy/topics.py#L809-L811 and https://github.com/strawlab/ros_comm/blob/master/clients/rospy/src/rospy/topics.py#L851-L852
I've been trying out dynamic reconfigure here and it mostly works (with lots of boiler plate to move somewhere else later), except I have to publish parameter_description and parameter_updates in a loop instead of latched as they ought to be, and the update interrupts and overwrites whatever the user was doing in the rqt dynamic reconfigure client (though even latched I need to figure out the right time to send the parameter update, maybe right in the service callback or immediately after).

Yup great callout, we defo should support that.
I'd like to support it for both the ros1 and rosbridge backends with the same API, but should be easy to add.
Probably won't be able to tackle for a few days, but will get to this soon.

I wonder if we should use a builder pattern for the API or if that would be more confusing....
We could do something like:
nh.advertise().latch().await;

Do we care about being able to turn latching on/off after a publisher is created? - Probably not...
Maybe it should be .advertise_latched()??

MR for this fix is up I'll merge after CI passes.
After playing around with the API and understanding the implications of calling .advertise() multiple times (were copying ROS1's cpp API but I don't love it), I decided to add latching as another required parameter to advertise(), this will be a breaking API change, but I think a pretty reasonable one at this stage.


[Configuration] Support immediate reaction to certain properties

The spec states the following:

DO NOT change behavior based on configuration changes that occur after the client is constructed. Hierarchies of clients inherit parent client configuration unless explicitly changed or overridden. Exceptions to this requirement are as follows:

Log level, which must take effect immediately across the Azure SDK.
Tracing on/off, which must take effect immediately across the Azure SDK.

This suggests to me that we need some way of not holding the log level and tracing settings directly in the configuration map, but rather to have a Supplier that will compute them every time, upon request.

This is already done in Configuration is a slightly more roundabout way so that the logging -> check log level -> log configuration was loaded -> check log level doesn't infinite loop.
Those two configurations are checked each time they are requested. If the value in the environment is that same as the configuration store the log level is returned. If the environment value is different than the configuration store the new value is stored and a message is logged about loading a configuration before the value is returned.


Dont allow upload incompatible plugins

1. Why is this change necessary?
Its a earlier requirements check for the shop owner, to not upload incompatible plugins. Also some plugins depends on other plugins and needed installed before otherwise the shop throws a Exception #foundationplugins
The check in install is also too late, because already the plugin files are replaced. This should solve also the support requests like "I have installed the 5.4 version of the plugin on a 5.3 shop"
2. What does this change do, exactly?
Check for plugin requirements before unzipping the plugin.
Example screenshot
3. Describe each step to reproduce the issue or behaviour.
Set a high minVersion in plugin.xml and try to upload it
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[X] I have read the contribution requirements and fulfil them.

200 Pull Requests 🙌

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-21336
Please use this issue to track the state of your pull request.

@shopwareBot  please merge this PR very soon. Our clients ran exactly in this trap. A big thanks to @shyim for fixing this.

CLA already signed.

Hey @shyim,
Thanks for your contribution 💙
Could you please squash your commits?

Moin @shyim, thank you for your contribution! 💙 💋


Retrospective recruitment and bias adjustment

https://github.com/pacific-hake/hake-assessment/blob/ba1b65a6b01ede59a9c2ce1ad7bb62658da4f197/R/retrospectives.R#L65 already removes the last year of recruitment. We should insert these two lines after line 65 to change the bias adjustment ramp ...
ctl[["last_yr_fullbias_adj"]] <- ctl[["MainRdevYrLast"]] - 1
ctl[["first_recent_yr_nobias_adj"]] <- ctl[["MainRdevYrLast"]]

These changes should be made to the retrospectives whether we are using MLE or MCMC. In theory, if we were going to use the MLE runs you could estimate the full ramp, but that could lead to problems in automated code because it tends to be finicky.

Maybe @aaronmberger-nwfsc could run the MLE bias adjustment with the new code in my last post and we could look at the differences in an MLE context if we want to. I think that the runs will be better behaved.

Maybe @aaronmberger-nwfsc could run the MLE bias adjustment with the new code in my last post and we could look at the differences in an MLE context if we want to. I think that the runs will be better behaved.

As you suspected @kellijohnson-NOAA adding those two lines improved retro performance in an MLE context.  Below is a comparison, noting that most of the difference came with the a more stable estimate of ln(R0) retrospectively when additionally adjusting the last of year of full bias adjustment year along with the first recent year of no bias adjustment.  However, I believe the equations above are switched as I used the following in my trials:
ctl[["last_yr_fullbias_adj"]] <- ctl[["MainRdevYrLast"]]
ctl[["first_recent_yr_nobias_adj"]] <- ctl[["MainRdevYrLast"]] + 1

As you suspected @kellijohnson-NOAA adding those two lines improved retro performance in an MLE context.  Below is a comparison, noting that most of the difference came with the a more stable estimate of ln(R0) retrospectively when additionally adjusting the last of year of full bias adjustment year along with the first recent year of no bias adjustment.  However, I believe the equations above are switched as I used the following in my trials:
ctl[["last_yr_fullbias_adj"]] <- ctl[["MainRdevYrLast"]]
ctl[["first_recent_yr_nobias_adj"]] <- ctl[["MainRdevYrLast"]] + 1

For further background info on bias adjustment in retrospectives (and related weird initial bumps at beginning of squid plot) see issue #694.

For further background info on bias adjustment in retrospectives (and related weird initial bumps at beginning of squid plot) see issue #694.


heatin/cooling unit device type (CON-364)

I'm working on developing a smart heating unit for in-home use to which I'd like to add matter functionality. When looking in the matter device library specifications the category that suits this best would be a heating/cooling unit. However I can't find this device type in the esp-matter endpoints. I've noticed google doesn't support this device type either.
Is there any way I can implement this device type in my heater? Or is there any way for me to just give it basic on/off functionality?

@stage-01 As per the Matter v1.0 specification, the support for Heating/Cooling Unit is provisional. This means that it is a part of the specification, but the implementation is not certifiable in the v1.0 release. This can be the reason that the ecosystems don't support it yet.

Or is there any way for me to just give it basic on/off functionality?

Basic on/off functionality can be achieved through On/Off Plug-in Unit

Thanks for de confirmation. I will close this issue because my question has been answered.
It's too bad that there is not a way to just have a standard "matter device" that can have the on/off functionality seeing as it would be a bit weird to buy a heater and have to set it up in google home as a smart plug. Guess matter v1.0 and the implementation in google home is still lacking a bit too much features for it to be useable for most home appliances.

@stage-01 Even though it is not directly supported, Google Home (as well as Apple Home) gives an option to represent the outlet as per the connected accessory type. After commissioning the outlet, click on it and then choose settings and then the device type. List has Light, AC, Fan, Dehumidifer, Heater, Kettle, TV, Switch etc. You can choose as per your accessory. Then it changes the icon for the accessory accordingly and you can control it using the voice commands too. Hope this helps.

Yes I've found that feature and that is what I will be using for test purposes. That sadly wont really work for an end product :( Thank you very much for your help!

Would the "Thermostat" device type meet your needs? Your application would need to operate autonomously based on the set temperature, but you could control that set temperature through Google Home and the like.

I might be able to get that to work. It wont be as good of a fit as the heating/cooling unit device type but it's better than nothing. Thanks for the suggestion


Update introducing-spring-modulith.adoc

Replaced the deprecated matchingMapped with matching, and adapted the way the orderId is read from the event

That's merged, thanks!


Options for various functions are not documented

It appears that the options available for the various functions include :prefix and :suffix, but I learned that only by reading through the source code.

I just updated the documentation!

Terrific, thanks! And thanks also for this very useful library.


Different compiling outputs (may be related to OS)

Hi, here I met some really interesting situation when working with my colleagues using gulp-sass.
Since node-sass serves as gulp-sass's dependency so I think this issue may be more likely better to put it here, because gulp-sass only cares about the task running IMO.
As background information - my colleague is using Windows 10 / node 0.12.7, while I am using Mac OS X El Capitan / node 0.12.4.
We have some scss file code like this :
.msg,
.text {
  font: 16px/24px 'Microsoft Yahei','Helvetica Neue',Helvetica,Arial,sans-serif;
}

We use gulp as task runner so we're using gulp-sass. We found our compiled css would be a little different ( I capture this from my git diff ):
/* my colleague's output */
.msg,
.text {
  font: 16px/24px "Microsoft Yahei", "Helvetica Neue", Helvetica, Arial, sans-serif;
}

/* my output */
.msg, .text {
  font: 16px/24px 'Microsoft Yahei','Helvetica Neue',Helvetica,Arial,sans-serif;
}

Noticed that there are 3 difference between our outputs:

the selector ( 2 lines vs. 1 line );
the quote mark ( double quote mark vs. single quote mark );
there is a space after the comma in my colleague's output.

We double-checked the following fact:

the source scss code is 100% identical
we are using the same version of gulp-sass ( so node-sass's version is the same )

Any tips or ideas?
UPDATE: I've updated the node version to 0.12.7 which is the same with my colleague's. But it doesn't help.

Looks like you're running different version of node-sass. You can confirm this with
npm ls node-sass

@xzyfer Thank you very much!
You are right - the problem is about having different node-sass, even we have same version of gulp-sass.
In<EMAIL_ADDRESS>package.json it writes:
"dependencies": {
    "node-sass": "^3.0.0",
    // ...
},

So we bump gulp-sass to v2.2.0 (thus node-sass to 3.4.2) and the problem is gone. Again thank you very much!


Data downloading speed is super slow

Thanks for your great work and nice code.
I have one question regarding dataset downloading speed. When I try to download  the dataset of activitynet and msrvtt, the downloading speed is super slow, which is only around 150 kb/s.  I might need 19 days to download the whole activitynet dataset if there is no crashdown. Is it possible to share the data in a google drive or any other places to increasing the downloading speed?

Hi @junchen14,
We don't have an alternative download yet. I tried to download activitynet on my end, it is around 3MB/s for me.
Add my co-author Linjie @linjieli222, do you have any tips on improving the download speed?
Best,
Jie

thanks jie for your help
I have fixed this issue.


JSON: fix the deserialization of JSON::ArrayType

In the context of the JSON::ArrayType type, a previous change was added as part of this PR -> https://github.com/rdkcentral/Thunder/pull/1112 for the serialization of empty array ie: to differentiate, between a set but empty and a null JSON array container. The resulting implementation, however, failed to deserialize properly, because when finding a empty JSON array (i.e. someArray: []), the resulting object would be equivalent to someArray: null, which is incorrect.
To fix this, this commit adds the setting of the _state data member in the Deserialize method when a matching pair of square brackets are correctly parsed.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@arjun-tata good catch and thank you for the contribution. Thanks for adding this to the master and the detailed commit message, this made the review easy!
Do you need this on any specific relese as well so we can cherry-pick it there ?

@arjun-tata good catch and thank you for the contribution. Thanks for adding this to the master and the detailed commit message, this made the review easy! Do you need this on any specific release as well so we can cherry-pick it there ?

Hi @pwielders, yes, it would be good for us to get this on R2 as well, but for that, you'll need not only this change, but also the one from https://github.com/rdkcentral/Thunder/pull/1112 to go there as well, and first.

@arjun-tata good catch and thank you for the contribution. Thanks for adding this to the master and the detailed commit message, this made the review easy! Do you need this on any specific release as well so we can cherry-pick it there ?

Hi @pwielders, yes, it would be good for us to get this on R2 as well, but for that, you'll need not only this change, but also the one from #1112 to go there as well, and first.

hello @pwielders , as mentioned could you please help to migrate these two changes to the R2 branch as well, it will be helpful to us.


fix comments, switch to for-of loop that appears to now work, fix attributes with " characters

small fix. for-of loop appears to work now (not sure why it seemed not to work for me before)
This is needed for https://github.com/ryansolid/dom-expressions/pull/146

more byte removed :partying_face:

Thanks


feat: Custom item kinds

Fixes #985 among others
This PR allows sources to return custom completion item kinds by returning a string instead of a int in the kind field. Currently, if you have a source which does not fit into the categories of a normal snippet or lsp kind there is no way to add an additional field. This fixes that. Here is an example in my copilot plugin:
source.format_completions = function(_, params, completions)
  return {
    label = label,
    kind = "Copilot",
    ...
  }
end

The benefits to this implementation (besides being 2 lines of code) are that highlight groups will be automatically added, for instance:
vim.api.nvim_set_hl(0, CmpItemKindCopilot, '#A5BA93')
Since cmp doesn't read config for formatting until immediately after determining type, this is by far the easiest way of making everything work in a non-invasive manner.
lspkind users will also be happy to know that I tested adding a custom group to it, and it works fine there as well:
require('lspkind').init({
  symbol_map = {
    Copilot = "[ﯙ]",
  },
})

I looked at a lot of different ways of doing this, but any method based on adding another entry and passing kind = 26 for instance, resulted in hardcoding or overcomplication.

@hrsh7th Would it be possible for you to review this? Beyond the shown use case I need the functionality to write some custom comparators for ranking completions for just the copilot source.

The LSP specification defines [CompletionItemKind] (https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#completionItemKind).
I don't think it's a good idea for the source to return a non-compliant response.
For example, nvim-cmp already uses the CompletionItemKind as highlight definition.
The kind highlight definisions are also used from some of the colorschemes.
This feature is not fit current ecosystem, I think... (so I worried about merghing this)

I think you could add other kinds
because this isn't just for lsp (as far as I understood)

I think we shouldn't add the hack but I can add the protocol extension point.
What do you about the following solution?
{
  label = 'if ... then`
  kind = lsp.CompletionItemKind.Text,
  cmp = {
    kind_text = 'Copilot'
  }
}

I think we shouldn't add the hack but I can add the protocol extension point.
What do you about the following solution?

{

  label = 'if ... then`

  kind = lsp.CompletionItemKind.Text,

  cmp = {

    kind_text = 'Copilot'

  }

}

How would it work to differentiate between Text responses for highlights or adding icons?

This is nothing to difference. We can do the same thing to achive.
require('lspkind').init({
  symbol_map = {
    Copilot = "[ﯙ]",
  },
})

Your suggested solution modifys the kind field type. It's defined as number type but this PR make to allow string type value.
My solution does not modify the LSP.CompletionItem definition but adds ability to customize vim_item.kind value. (In my knowlege, lspkind uses this value.

I can modify the PR to do that instead, but there is still the issue of hl_groups. Is it alright with you if I also modify it to allow for:
{
  label = 'if ... then`
  kind = lsp.CompletionItemKind.Text,
  cmp = {
    kind_hl_group = "CmpItemKindCopilot",
    kind_text = 'Copilot'
  }
}

I think we can have the kind_hl_group.

@hrsh7th I implemented it as you described, and it is working. vim_item.kind must be set to be the value of cmp.kind_text, rather than using view.kind.text for lspkind to work with this change. This is because the format function is called on the vim_item immediately after its creation in entry.get_vim_item
I added the fields and classes where necessary inside of the type declarations, but you may want to double check that I did it exactly how you would prefer.

@hrsh7th Just wanted to check in on this, it's a bit outdated now but I can rebase if you like. Did you have a chance to look over the implementation and see if it matches what you were looking for?

LGTM. The last point is unnecessary type hints. Could you remove it?
Sorry for the late review.

LGTM!


When running with 512x512, the code errors out

Hi, I'm trying to run domain_specific_deblur.py with styleGAN2 on 512x512 dimension with pretrained models. However, after I fixed the latent and noise dimentions in dsd_stylegan2.py, the code still errors out on unet_parts.py. Is 512x512 supported?
The stacktrace is as below:
Traceback (most recent call last):
  File "domain_specific_deblur.py", line 84, in <module>
    for j, (HR, LR) in enumerate(model(ref_im)):
  File "/deblur/blur-kernel-space-exploring/models/dsd/dsd.py", line 188, in forward
    self.optimize_x_step(epoch)
  File "/deblur/blur-kernel-space-exploring/models/dsd/dsd.py", line 150, in optimize_x_step
    loss, loss_dict = self.loss_builder(latent_in, self.gen_im, self.gen_ker, epoch)
  File "//anaconda3/envs/torch/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/deblur/blur-kernel-space-exploring/models/losses/dsd_loss.py", line 108, in forward
    "gen_im_lr": self.D.adaptKernel(gen_im, kernel),
  File "/work/deblur/blur-kernel-space-exploring/models/kernel_encoding/kernel_wizard.py", line 157, in adaptKernel
    out = self.adapter(x_sharp, kernel)
  File "/anaconda3/envs/torch/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "//work/deblur/blur-kernel-space-exploring/models/kernel_encoding/kernel_wizard.py", line 99, in forward
    return self.model(x, k)
  File "/anaconda3/envs/torch/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/work/deblur/blur-kernel-space-exploring/models/backbones/unet_parts.py", line 103, in forward
    return self.up(self.submodule(self.down(x), noise))
  File "/anaconda3/envs/torch/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/work/deblur/blur-kernel-space-exploring/models/backbones/unet_parts.py", line 109, in forward
    return torch.cat((self.up(self.submodule(self.down(x), noise)), x), dim=1)
  File "/anaconda3/envs/torch/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/work/deblur/blur-kernel-space-exploring/models/backbones/unet_parts.py", line 109, in forward
    return torch.cat((self.up(self.submodule(self.down(x), noise)), x), dim=1)
  File "/anaconda3/envs/torch/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/work/deblur/blur-kernel-space-exploring/models/backbones/unet_parts.py", line 109, in forward
    return torch.cat((self.up(self.submodule(self.down(x), noise)), x), dim=1)
  File "/anaconda3/envs/torch/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/deblur/blur-kernel-space-exploring/models/backbones/unet_parts.py", line 107, in forward
    return torch.cat((self.up(torch.cat((self.down(x), noise), dim=1)), x), dim=1)
RuntimeError: Sizes of tensors must match except in dimension 2. Got 2 and 4 (The offending index is 0)

Thank you for your help!

Thanks for your interest,
Currently, the domain-specific deblurring method only works with 256x256 images. However, if you choose StyleGAN (instead of StyleGANv2) in the config file, the output image will have size 1024x1024, so you can downsample your input image to 256x256 first and then use the domain-specific deblurring algorithm with StyleGAN, the output will be 1024x1024 (then you can downsample it to 512x512).


Automatically encode a HTTP body

Good day!
As I understand Hyper automatically decode HTTP1.1-response Body with "content-encoding". So Body comes to my handler in decoded (i.e. unzipped) form.
My proxy needs to edit it, then gzip it and translate HTTP-response to client. Is there enough to keep "content-encoding: gzip" header and Hyper automatically gzip it? Or I need to compress it handy?
Can you give me example please?

hyper doesn't automatically decode or encode anything besides Transfer-Encoding: chunked. To handle zipped content, you'd need to pass chunks you receive in the Request to something that can decode, and likewise pass content to something that can encode before being used as a body in the Response.
For the Response, it's possible to implement hyper::body::Payload to encapsulate that encoding, instead of passing a hyper::Body directly in the Response.
(As this isn't a bug in hyper, I'm going to close the issue.)


Nostr sleep

Codecov Report
Base: 49.59% // Head: 49.59% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (b1776a2) compared to base (da2d003).
Patch coverage: 50.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #112   +/-   ##
=======================================
  Coverage   49.59%   49.59%
=======================================
  Files          34       34
  Lines        2591     2593    +2
=======================================
+ Hits         1285     1286    +1
- Misses       1306     1307    +1

Impacted Files
Coverage Δ

cashu/wallet/cli/nostr.py
21.33% <0.00%> (-0.29%)
:arrow_down:

cashu/wallet/cli/cli.py
51.23% <66.66%> (+0.13%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


which are “Ollama Embedder” models?

which models are embedding models? except in ollama?

snowflake-arctic-embed
mxbai-embed-large
nomic-embed-text
are the usual ones, there may be more but you'll have to check with their project to be sure.


Use rollup ?

It's possible to use rollup instead of uglify ?

what do you mean? how's uglify related rollup here?

Sorry I make a mistakes. It's possible to just use rollup in vbuild to bundle the app ?

You can try rollup-loader with <script lang="rollup"></script>, but I never tested this.

Thanks. Otherwise, is it possible to do tree-shaking in vbuild or is some-shose of similar is done basic?
Sorry for my question but I search to remove all unued code and I don't know if it's make basically (I'm noob with webpack)

Webpack 2 natively support tree-shaking (only if you use ES6 modules).

Thanks :)

Can we close?

Yes 😊Le 28 janv. 2017 8:49 PM, Zephraph<EMAIL_ADDRESS>a écrit :Can we close?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.


Calibration save location popover looks broken

After successfully calibrating the device the user is prompted to select a location to save the calibration data.  This used to use a drop-down popover but since it is in a modal this did not work correctly on firefox.
The current solution works on all supported browsers but if the user clicks on or to the right of the down arrow inside the select box the options popover is rendered with its upper left corner on the down arrow icon and overlaps the UI elements to the right of the select.  This is still completely functional but looks unintentional / broken.
Consider revamping the UI to prevent this from looking broken.

In Chrome, the browser captures the arrow element in the on click event whereas other browsers capture the containing div. The captured element is used to position the dropdown, so in Chrome the dropdown is improperly positioned when the user clicks on the arrow.
To fix the issue of the dropdown covering other UI elements, a redesign of the success slide in the calibration component was done. Now, the save location select, calibration results and the option to apply calibration on boot reside within an Advanced options expander. When expanded, clicking on the arrow will still cause the select to use the arrow for positioning (in Chrome) but won't cover the Done button.
commit: e6f617d


Define main entry module to be a js file

Although node.js understands if "main" is a directory name, some tools (madge) requires that it is an actual module file. This is how it is specified in https://docs.npmjs.com/files/package.json also.

Coverage remained the same at 100.0% when pulling f70f13b55b696539885c34b8c855ae36bfb85b14 on langma:master into d0f6b6c5ab4d292efdd83b0eeeb7b0e5dcfd823a on jaredhanson:master.

Closing for the same rationale listed here


portuguese dictionary

Hello all
I am using onlyoffice and installed languagetool.
but where I can get and install dictionary for portuguese and english language?
tks
paulo

Hi, could you clarify something for me?
This plugin uses API of https://languagetool.org/ service, so there is no possibility to install own languages
But I don't quite get - portuguese and english language is available:

Yes, in the onlyoffice site show this plugin, but really I can't find dictionaries

I'm sorry, I dont understand you
You've installed this plugin and cannot find Portuguese language in it?
Didn't my screenshot helped?
Please describe step by step what operations you've done and what do expect, because we may expect different things than you

Yes, I installed the plugin in the office and didnt find any language.
Here is the screens.

I see that you've already closed this issue, but I think problem was that plugin sources was not the latest ones

no problem, it is not urgent.

SO you still have problems? You shouldn't close this issue in that case
Could you attach plugin file? Seems that it's just old. You can compare it's internals (as zip archive) with this repo sources


Update branch alias

PR #10 was adding a new method to an interface. That is a BC break which means the next version should be a new major.
This PR updates the branch alias to reflect that.
FYI: https://travis-ci.com/github/symfony/symfony/jobs/495483562#L7297

@Nyholm
Indeed but I do not plan already to release it .
And it's impact might make me reconsider adding it now. But it will definitely be part of the next major release.

Cool Thank you for the quick merge.
No rush with the release. =)


Can't start Locust on localhost - getting an OSError

Describe the bug

I am trying to run locust with the command locust -f locustfile.py. My locustfile looks as below

    from locust import HttpUser, TaskSet, task
    import urllib.parse
    from locust.env import Environment
    import json
    import urllib3
    from locust.contrib.fasthttp import FastHttpUser

    global_header = None
    class RecommenderTasks(TaskSet):
        def __init__(self, parent):
            super().__init__(parent)
            self.global_header = None
            self.cold_start_url = "https://my-web-site"

        def on_start(self):
            urllib3.disable_warnings()
            self.global_header = self.login()

        def login(self):
            call_url = urllib.parse.urljoin(self.cold_start_url, "/oauth/token")
            headers = {'Authorization': 'Basic (my-token)=='}
            response = self.client.post(call_url, {'grant_type': 'client_credentials'}, headers=headers, verify=False)

            access_token = json.loads(response.text.encode('utf8'))['access_token']
            headers = {'Authorization': 'Bearer ' + access_token}
            return headers

        @task
        def test_recommender_multiple_platforms(self):

            params = {'rec_id': str(0)}
            response = self.client.request("GET", '/recommendations',
                                    params=params,
                                    headers=self.global_header,
                                    verify=False)
            print(response)

    class RecommenderUser(HttpUser):
        tasks = [RecommenderTasks]
        min_wait = 0
        max_wait = 0

        host = "https://my-web-site"

Expected behavior

I should be able to start the locust service
Actual behavior

I am getting the following error
[2021-05-31 20:25:34,146] d6ad3fb4f0cf/INFO/locust.main: Starting web interface at http://<IP_ADDRESS>:8089 (accepting connections from all network interfaces)
[2021-05-31 20:25:34,156] d6ad3fb4f0cf/INFO/locust.main: Starting Locust 1.5.3
Traceback (most recent call last):
  File "src/gevent/greenlet.py", line 906, in gevent._gevent_cgreenlet.Greenlet.run
  File "/usr/local/lib/python3.8/site-packages/locust/web.py", line 339, in start_server
    self.server.serve_forever()
  File "/usr/local/lib/python3.8/site-packages/gevent/baseserver.py", line 398, in serve_forever
    self.start()
  File "/usr/local/lib/python3.8/site-packages/gevent/baseserver.py", line 336, in start
    self.init_socket()
  File "/usr/local/lib/python3.8/site-packages/gevent/pywsgi.py", line 1545, in init_socket
    StreamServer.init_socket(self)
  File "/usr/local/lib/python3.8/site-packages/gevent/server.py", line 180, in init_socket
    self.socket = self.get_listener(self.address, self.backlog, self.family)
  File "/usr/local/lib/python3.8/site-packages/gevent/server.py", line 192, in get_listener
    return _tcp_listener(address, backlog=backlog, reuse_addr=cls.reuse_addr, family=family)
  File "/usr/local/lib/python3.8/site-packages/gevent/server.py", line 284, in _tcp_listener
    sock = GeventSocket(family=family)
  File "/usr/local/lib/python3.8/site-packages/gevent/_socket3.py", line 133, in __init__
    self._sock = self._gevent_sock_class(family, type, proto, fileno)
OSError: [Errno 97] Address family not supported by protocol
2021-05-31T20:25:34Z <Greenlet at 0x7f11128f47b0: <bound method WebUI.start_server of <locust.web.WebUI object at 0x7f1112877e50>>> failed with OSError

May I know what would be the cause of such an exception?
Environment

OS: Windows
Python version: 3.8
Locust version: latest
Locust command line that you ran: locust -f locustfile.py
Locust file contents (anonymized if necessary):

Could be some ipv6 issue? Are you really on windows (and not on WSL or something)? Those file locations look like unix paths :)
Try adding --web-host localhost to bind only to that interface (no idea if that will help, but maybe...)

Perplexed as I am, a system restart resolved the issue. Closing it ! Thanks :)


App Crashed on Android 12

My App crashed when starting on Android 12 without throwing any error (but it works fine on Android 11 and iOS)
Here is my environments:
Developement Environment:

MacBook Pro (14-inch, 2021) M1 Pro 16GB RAM
Mac OS 12.3.1 (21E258)
XCode 13.3 (13E113)
React Native Environment:
Homebrew 3.4.5
Node 17.8.0
NPM 8.5.5
Watchman 2<IP_ADDRESS>
React Native CLI 2.0.1
React Native 0.68
Pod 1.11.3
And I am using react-native-maps 0.30.1

When I install react-native-maps, I need to install with "--force" parameter:
npm install react-native-maps --save-exact --force
https://github.com/react-native-maps/react-native-maps/blob/master/docs/installation.md
I followed the "Build configuration on Android" (and iOS as well) to setup my android environment:
ext {
    buildToolsVersion = "31.0.0"
    minSdkVersion = 21
    compileSdkVersion = 31
    targetSdkVersion = 31
    ndkVersion = "21.4.7075529"

    supportLibVersion   = "23.1.1" // default: 23.1.1
    playServicesVersion = "17.0.0" // or find latest version
    androidMapsUtilsVersion = "2.3.0"
}

I found this updates: https://github.com/react-native-maps/react-native-maps/commit/7ccc65d83b409735034912279d72a7c6dc232066
And I tried to update my android build settings as following:
ext {
buildToolsVersion = "31.0.0"
minSdkVersion = 21
compileSdkVersion = 30 // changed this from 31 to 30
targetSdkVersion = 30 // changed this from 31 to 30
ndkVersion = "21.4.7075529"
supportLibVersion   = "23.1.1" // default: 23.1.1
playServicesVersion = "17.0.0" // or find latest version
androidMapsUtilsVersion = "2.3.0"

}
Seems the crash fixed


close menu button

close menu button is not aligned properly on mobile screens:

fixed:

on home page hovering over the icons translates them below get started let me know if that is intentional.

assign this issue to me so I can work on it.

i would like to resolve this issue

I would like to work on this issue under gssoc , please assign it to me.


fix: Add cache control header to css and js assets in caddy

Description

[!TIP]
Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).
Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
or
Fixes Issue URL

[!WARNING]
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

Summary by CodeRabbit

New Features

Enhanced the Caddy server configuration to improve serving static assets with appropriate headers.

/build-deploy-preview skip-tests=true

/build-deploy-preview skip-tests=true

/build-deploy-preview skip-tests=true

/build-deploy-preview skip-tests=true

/build-deploy-preview skip-tests=true

Closing this and adding the header through the CDN's response header policy.


Enabling DMA on stm32f3 series

These commits enable DMA on STM32F3 series.
This has been tested with tests/drivers/dma/chan_blen_transfer and tests/drivers/dma/loop_transfer on stm32f3_disco platform and is working as expected.
tests/drivers/dma/loop_transfer
*** Booting Zephyr OS build zephyr-v2.6.0-1333-g66eae393d634  ***
Running test suite dma_m2m_loop_test
===================================================================
START - test_dma_m2m_loop
DMA memory to memory transfer started on DMA_1
Preparing DMA Controller
this platform do not support the dma channel
Starting the transfer on channel 4 and waiting for 1 second
Each RX buffer should contain the full TX buffer string.

 PASS - test_dma_m2m_chan0_burst8 in 2.13 seconds
===================================================================
START - test_dma_m2m_chan1_burst8
Preparing DMA Controller: Chan_ID=2, BURST_LEN=1
Starting the transfer
DMA transfer done
It is harder to be kind than to be wise........
 PASS - test_dma_m2m_chan1_burst8 in 2.13 seconds
===================================================================
START - test_dma_m2m_chan0_burst16
Preparing DMA Controller: Chan_ID=4, BURST_LEN=2
Starting the transfer
DMA transfer done
It is harder to be kind than to be wise........
 PASS - test_dma_m2m_chan0_burst16 in 2.13 seconds
===================================================================
START - test_dma_m2m_chan1_burst16
Preparing DMA Controller: Chan_ID=2, BURST_LEN=2
Starting the transfer
DMA transfer done
It is harder to be kind than to be wise........
 PASS - test_dma_m2m_chan1_burst16 in 2.13 seconds
===================================================================
Test suite dma_m2m_test succeeded
===================================================================
PROJECT EXECUTION SUCCESSFUL

@erwango @FRASTM for your review.

I have fixed the error on buildkite/zephyr — Build  failed with the https://github.com/zephyrproject-rtos/zephyr/pull/37165

I have fixed the error on buildkite/zephyr — Build failed with the #37165

Looks like below failures are still present.
3 failures:

tests/drivers/dma/chan_blen_transfer/drivers.dma in nucleo_f070rb:tests/drivers/dma/chan_blen_transfer/drivers.dma
tests/drivers/dma/chan_blen_transfer/drivers.dma.interactive in nucleo_f070rb:tests/drivers/dma/chan_blen_transfer/drivers.dma
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer in nucleo_f070rb:tests/drivers/dma/loop_transfer/drivers.dma

I have fixed the error on buildkite/zephyr — Build failed with the #37165

Looks like below failures are still present.

@ikmdani #37165 is not merged yet. You can help to fasten the merge by adding your review.

It seems better now enable the dma with
&dma1 {
	status = "okay";
};

directly in the
./boards/arm/stm32f0_disco/stm32f0_disco.dtsinstead of adding a overlay in the testcase. Just keep the .conf with the channel configuration.

F0 DMA seem to be different from other series and has build issues. It is better to raise another PR for F0 DMA.

yes for the f0 refer to https://github.com/zephyrproject-rtos/zephyr/pull/37169
This PR is for F3 so expecting ./boards/arm/stm32f3_disco/stm32f3_disco.dts
instead of adding a overlay in the testcase. Just keep the .conf with the

Please @ikmdani rebase since the https://github.com/zephyrproject-rtos/zephyr/pull/37165 is merged


[Feature request] Show Windows' WSL user home directory as '~'

Describe Your Issue

What is happening?

This is not an issue, but more of a feature request.
WSL - Windows Subsystem on Linux, it's known that the two systems doesn't share the same home folder, but I usually setup my code in my Windows partition (and I can't get access to the Linux partition for file system compatibility issues, obviously), so I hope that powerlevel9k can support custom user home directories (or just show /mnt/c/Users/WINDOWS_USER_NAME as "~ plus a different icon" would be nice).
Screenshot below:

Have you tried to debug or fix it?

Have you tinkered with your settings, and what happened when you did? Did you find a bit of code that you think might be the culprit? Let us know what you've done so far!

I'm not that familiar with zsh or bash grammar, but I'm willing to give it a shot. I will need some time (a lot of time) to figure out how to implement this by myself ... Also it came to me that not all WSL users' home path are /mnt/c, so I really have no idea how to implement this ⊙﹏⊙∥
Environment Information
This information will help us understand your configuration.

What version of ZSH are you using? You can use zsh --version to see this. zsh 5.6.2 (x86_64-pc-linux-gnu)
Do you use a ZSH framework (e.g., Oh-My-ZSH, Antigen)? OH-MY-ZSH
How did you install P9k (cloning the repo, by tarball, a package from your OS, etc.,)? Via the Install for OH-MY-ZSH section's instructions
What version of P9k are you using? The latest. (I just installed P9k 2 days ago.)
Which terminal emulator do you use? Fluent Terminal.

Disclaimer: I'm not commenting on the feature idea, just what possibilities there are that might help you now.

WSL - Windows Subsystem on Linux, it's known that the two systems doesn't share the same home folder, but I usually setup my code in my Windows partition (and I can't get access to the Linux partition for file system compatibility issues, obviously), so I hope that powerlevel9k can support custom user home directories (or just show /mnt/c/Users/WINDOWS_USER_NAME as "~ plus a different icon" would be nice).

I'm not quite sure if you imply by "incompatibility issues" that your files are inaccessible/unreachable in your "Linux/WSL home" from your Windows system or if you have other worries like permissions, file corruptions, etc.
If it is just the former, you can access it, e.g. for Ubuntu %LocalAppData%\Packages\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc\LocalState\rootfs\home. I guess it's something similar for Arch. I am not sure if it is a good idea to work with these directories directly from Windows. (More on WSL fs)
Some more (bad) ideas, that you should not quote me on and might want to try (or to avoid):

changing home in passwd file
export HOME="/mnt/c/Users/WINDOWS_USER_NAME"

@Syphdias Thank you for your suggestions. ♥

I am not sure if it is a good idea to work with these directories directly from Windows. (More on WSL fs)

Yes, it's definitely not recommended to access Linux files from Windows' side.

changing home in passwd file
export HOME="/mnt/c/Users/WINDOWS_USER_NAME"

I'm trying not to mess up my Windows environments with my Linux ones. And Linux can't chmod Windows' files, so for programs like ssh, I can't just use the keys on both sides. Thus I think simply changing the $HOME is not an option.
An update:
I configured p9k to truncate path to 2 words, so when I'm in Windows' home folder, it looks like this:

As a matter of fact, I am kind of satisfied. Do wish there's a better way implement this.

Yes, it's definitely not recommended to access Linux files from Windows' side.

I corrected that statement shortly before your answer ;)

I configured p9k to truncate path to 2 words, so when I'm in Windows' home folder, it looks like this:

As a matter of fact, I am kind of satisfied. Do wish there's a better way implement this.

You might want to play around with some dir shorten strategies, especially truncate_with_folder_marker:
touch "/mnt/c/Users/WINDOWS_USER_NAME/.shorten_folder_marker"
POWERLEVEL9K_SHORTEN_STRATEGY="truncate_with_folder_marker"
cd "/mnt/c/Users/WINDOWS_USER_NAME/Documents"

Another interesting one might be truncate_with_package_name, though currently, this needs a git repository which is a(nother) bad idea to have in your home directory. (This changes with ab6c1b779c3869d5792edbfbfa2e4f6576d219e4 which is currently only on the next branch)

@spencerwooo This is a perfect use case for named directories. First, put this in your ~/.zshrc.
hash -d w=/mnt/c/Users/spenc

(You can use any name instead of w. I went with w as a shorthand for Windows.)
Now ZSH will automatically perform bidirectional mapping between ~w and /mnt/c/Users/spenc the same way and in the same context where it performs mapping between ~ and /home/spencer. That is, commands like cd ~w and ls -d ~w/* will work. File completion after ~w will work, too.
Unfortunately, there is a bug in Powerlevel9k that will prevent ~w being shown in your prompt. You can either switch to Powerlevel10k where this bug is fixed (it'll work with your existing config without any changes; you'll get the same prompt as before but it'll be much faster and with many bugs being fixed) or as a workaround you can set POWERLEVEL9K_SHORTEN_STRATEGY=default and POWERLEVEL9K_SHORTEN_DIR_LENGTH=9999.

@romkatv Thank you so much, I've switched to Powerlevel10k for now and it's really faster. ❤


Change circle radius - method?

Question

Is there any method to change the radius of a Circle (by reference)?

radius is a property, so you can change it via any method you create.  I use state to manage the radius:
radius={this.state.radiusInMeters}

radius is a property, so you can change it via any method you create. I use state to manage the radius:
radius={this.state.radiusInMeters}

The issue is that i have a list/array of circles that are loaded dynamically inside the map. they already have the radius, i want to be able to change the radius via a method using the reference.
i.e.: this.circleRef.setRadius(200) <- this is a method available on web api i think but its not working on react-native in this library

We're talking about different circles then. I assumed from your title you meant the singleton circle for the user.

@richardbumm I think we are talking about the same: https://github.com/react-native-community/react-native-maps/blob/master/docs/circle.md.
What I want to do is change the radius property of a circle already present on the map(without deleting and recreating it).
Im guessing there isn't any method to do that but it could be useful to have it in the future. (Also changing the radius with animation could be cool)


[eigen3] Eigen is not found by a CMake find_package(Eigen3)

The Eigen library installed by vcpkg is not found by a CMake find_package(Eigen3).
Before version 3.3 (vcpkg is currently installing 3.2.10) Eigen was installing a file named signature_of_eigen3_matrix_library in the include directory, and this file was then used by the official FindEigen3.cmake to find the right location in which the Eigen header were installed.
The signature_of_eigen3_matrix_library file is not installed because the installation procedure provided by the official build system are ignored by the port introduced in https://github.com/Microsoft/vcpkg/pull/26 . However this may be a good thing, as having a random non-include file in ${_VCPKG_INSTALLED_DIR}/${VCPKG_TARGET_TRIPLET}/include may be brittle.
The best solution could be to wait for Eigen 3.3 that should be released shortly and switch to use the official build solution that installs a Eigen3Config.cmake file following CMake standards. In that case we need to check if the file is actually relocatable, and eventually patch it.

Thinking more about this, it still make sense to install signature_of_eigen3_matrix_library in ${_VCPKG_INSTALLED_DIR}/${VCPKG_TARGET_TRIPLET}/include, as many projects copy pasted the FindEigen3.cmake file before this PR : https://bitbucket.org/eigen/eigen/pull-requests/213 , and so they will ignore any existing Eigen3Config.cmake .

I completely agree, fundamentally we do need a working solution at the end of the day. Thanks for the detailed write-up yet again; I fixed the eigen3 port to deploy the signature_of_eigen3_matrix_library file and tested it using the old official FindEigen3.cmake you linked above.

Thanks a lot for the quick fix. 👍


IndexMissingException[[development] missing]" spree elasticsearch

I have getting this error.
Showing /home/project/.rvm/gems/ruby-2.2.1/gems/spree_frontend-3.0.0/app/views/spree/home/index.html.erb where line #8 raised:
[404] {"error":"IndexMissingException[[development] missing]","status":404}
Extracted source (around line #135):
    def __raise_transport_error(response)
      error = ERRORS[response.status] || ServerError
      raise error.new "[#{response.status}] #{response.body}"
    end

elasticseach.yml file
defaults: &defaults
hosts: localhost
port: '9200'
bootstrap: true
development:
<<: *defaults
index: development

I believe I removed bootstrapping, because I couldn't get it right. What I personally do is include the following block of code in my config/application.rb file, inside the to_prepare block. This allows for fine grained control in setting up your index. Hope this helps.
    config.to_prepare do
      # Load application's model / class decorators
      Dir.glob(File.join(File.dirname(__FILE__), "../app/**/*_decorator*.rb")) do |c|
        Rails.configuration.cache_classes ? require(c) : load(c)
      end

      # Load application's view overrides
      Dir.glob(File.join(File.dirname(__FILE__), "../app/overrides/*.rb")) do |c|
        Rails.configuration.cache_classes ? require(c) : load(c)
      end

      unless Elasticsearch::Model.client.indices.exists index: Spree::ElasticsearchSettings.index
        Elasticsearch::Model.client.indices.create \
          index: Spree::ElasticsearchSettings.index,
          body: {
            settings: {
              number_of_shards: 1,
              number_of_replicas: 0,
              analysis: {
                analyzer: {
                   nGram_analyzer: {
                      type: "custom",
                      filter: ["lowercase", "asciifolding", "nGram_filter"],
                      tokenizer: "whitespace" },
                   whitespace_analyzer: {
                      type: "custom",
                      filter: ["lowercase", "asciifolding"],
                      tokenizer: "whitespace" }},
                filter: {
                   nGram_filter: {
                      max_gram: "20",
                      min_gram: "3",
                      type: "nGram",
                      token_chars: ["letter", "digit", "punctuation", "symbol"] }}}},
            mappings: Spree::Product.mappings.to_hash }
      end
    end

    require 'elasticsearch/rails/lograge'

When i search the product it show empty list

Are the products in the index (bundle exec rake spree:elasticsearch)?
Does the elasticsearch query return anything if you run it directly
against the ES cluster?

Jan Vereecken
Clubit bvba
<EMAIL_ADDRESS>On Tue, Jun 30, 2015 at 8:22 AM, joshua<EMAIL_ADDRESS>wrote:

When i search the product it show empty list
—
Reply to this email directly or view it on GitHub
https://github.com/javereec/spree_elasticsearch/issues/22#issuecomment-117008127
.

Query looks ok.


Add parameter to forward request header to source image server

Introduces a parameter to configure a list of headers to forward to the image server.
Resolve issue https://github.com/flyimg/flyimg/issues/357
Security note:
if the list includes the Authorization header the path of the temporary file is modified with the hash of the value

@lrealdi probably we are missing an update on the documentaion, I'll check later

@lorello thank you for fixing the linting error, I've merged your PR!
I'll try to add coverage tests for the code you added, if you have already documentation would be great to add it in another PR.
Thank you again!


[BugFix] Fix wrong result local-dictionary exceed max(int16)

Fixes https://github.com/StarRocks/starrocks/issues/26251
the interface for ColumnPredicate is int16_t
    virtual Status evaluate(const Column* column, uint8_t* selection, uint16_t from, uint16_t to) const = 0;

if elements size for local-dictionary gt than int16_t. we will got wrong result
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[x] 3.0
[x] 2.5
[x] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5

@Mergifyio backport branch-2.4


Error querying the blockchain

I'm having the same problem, but different from transactions, it appears when I try to import my wallet, I'm not able to log in the wallet in the app, this message appears right after I type the private words. I can't access my wallet, I'm desperate! Can someone help me?

With me too. I think that this project died!

I had the same issue, but I could import my wallet to Electrum BitcoinZ https://github.com/btcz-electrum/electrum-btcz/releases/tag/v3.1.3
At the seed select Options/BIP39 then on the next page I set m/44'/0'/0' for Derivation.

I had the same issue, but I could import my wallet to Electrum BitcoinZ https://github.com/btcz-electrum/electrum-btcz/releases/tag/v3.1.3
At the seed select Options/BIP39 then on the next page I set m/44'/0'/0' for Derivation.

Excelent. I get too. Thanks

Works for me, although the phone wallet has it's instability from time to time.
It's recommended to move to the Full-node desktop wallet for now

The project isn't dead. The co-pay wallet is no longer supported. Use
Electrum, Vidulum, full node or coinami
On Sun, Feb 27, 2022, 2:16 PM raulcs @.***> wrote:

With me too. I think that this project died!
—
Reply to this email directly, view it on GitHub
https://github.com/bitcoinz-wallets/bitcoinz-copay-wallet/issues/71#issuecomment-1053666886,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJP7EPEZ5AVUXF6R4PEYJ5DU5KBBDANCNFSM5PPEKS4Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>


cmd/vet: warn about capturing loop iterator variables

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?
go version go1.6 darwin/amd64
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/ryangao/go"
GORACE=""
GOROOT="/Users/ryangao/homebrew/Cellar/go/1.6/libexec"
GOTOOLDIR="/Users/ryangao/homebrew/Cellar/go/1.6/libexec/pkg/tool/darwin_amd64"
GO15VENDOREXPERIMENT="1"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common"
CXX="clang++"
CGO_ENABLED="1"
What did you do?
Run "go vet" on code from https://play.golang.org/p/mUiuNfZDHT
What did you expect to see?
Expect "go vet" warns about error mentioned in
https://golang.org/doc/faq#closures_and_goroutines
What did you see instead?
No warning issued.

This does seem like it would catch real problems if done well.
/cc @adonovan

Actually, note that those captures - at least when they are definite bugs - should usually show up in the race detector. It's not clear vet can contribute more than the race detector does without significant false positives.

Although this bug pattern most often manifests with go statements (leading to data races), sequential (non-racy) instances are possible too, such as with defer or the simple example presented in this Issue.
vet already checks for patterns of the form:
for k, v := range seq {
    go/defer func() {
        ... k, v ...
    }()
}

The problem for analysis

We've had multiple bugs caused by this at Uber without it being detected by the race detector.
it's easy to imagine cases where the pointer escapes to a e.g. map without any concurrency being involved.
It will also catch the beginner's mistake of wanting to modify a slice of value objects by iterating over it and pass a pointer to a helper function:
for _, val := range vals {
	changeVal(&val)
}

which should be
for i, _ := range vals {
	changeVal(&vals[i])
}

I would argue that taking the addresses of range variables are so rarely useful that it would be good to require the intent to be made explicit as follows:
var val typeOfVal
valptr := &val
for _, val = range vals {
	// Use valptr if you must
}

(Same for the index variable.)

It seems to me like we're late to add a new vet check in 1.11, given that the tree is frozen.
Is anyone intending to work on this for 1.12?

Does anyone even know how to solve this problem? I don't.

How about we do this for the simple t.Parallel case as a start? It happens often (just this week I've spotted two manually during code reviews at work), and I think a simple and conservative algorithm like the one in #18106 could have near-zero false positives.

I'd like to document a possible false positive with the algorithm as described in #18106:
for _, v := range x {
    t1.Run("", func(t2 *testing.T) {
        t2.Run("", func(t3 *testing.T) {
            t3.Parallel()
            println(v)
        })
    })
}

t1.Run will wait for t2 and t2's subtests to complete, so even though t3 is a parallel test and references a range variable, everything works correctly, as t3 only runs parallel to t2, not the loop. This would not be the case if we also called t2.Parallel.

Here's another example that go vet does not catch. If you have nested loops and use a variable from the outer loop in a closure, go vet does not return the expected loop variable i captured by func literal error:
https://play.golang.org/p/l3830Ij64qg

vet could easily be made a little smarter to catch @dmowcomber's example. The checker looks only at the last statement in the loop body because it can't prove that any later statements don't wait, but we could define "last" recursively: if the last statement is an if statement, we could look at the last statement in both of its branches; or if the last statement is a nested loop, then we could look at the last statement of that loop's body; and so on for select, switch, etc.

@alandonovan We have a version of the loopclosure check within Monzo that uses a bunch of heuristics to avoid false positives and has good coverage of most bugs. Across our codebase it has 2 false positives and detected more than 50 bugs that hadn't already been discovered.
We are comfortable that the safety this provides outweighs the very occasional false positive but I don't think it's accurate enough to meet the go vet bar. I'm keen to contribute something to go vet so am looking at exploring a modified version of the check that is targeted at:

improper t.Run and t.Parallel usage
adds (*errgroup.Group).Go alongside defer and go as unsafe uses of function literals at the end of a loop

Does this sound potentially reasonable? If so, I'll draft a change.

@alandonovan We have a version of the loopclosure check within Monzo that uses a bunch of heuristics to avoid false positives and has good coverage of most bugs. Across our codebase it has 2 false positives and detected more than 50 bugs that hadn't already been discovered.
We are comfortable that the safety this provides outweighs the very occasional false positive but I don't think it's accurate enough to meet the go vet bar. I'm keen to contribute something to go vet so am looking at exploring a modified version of the check that is targeted at:

improper t.Run and t.Parallel usage

adds (*errgroup.Group).Go alongside defer and go as unsafe uses of function literals at the end of a loop

Does this sound potentially reasonable? If so, I'll draft a change.

@danielchatfield would you consider open sourcing this as a standalone linter? Possibly something that could be added to golangci-lint?

adds (*errgroup.Group).Go alongside defer and go as unsafe uses of function literals at the end of a loop

Is now supported in loopclosure.

improper t.Run and t.Parallel usage

This is something we have been considering adding support for in vet. This would most likely need to follow roughly the same pattern as loopclosure does.  Someone from the community could contribute this.
We are currently in 1.18 code freeze, but this may be able to make it into 1.19.

Fwiw the specific case that led me to this issue was that my loop contained an if statement as the last statement, and my goroutine(s) we're the last statements in each if branch.

@glenjamin Can you provide or point to a [possibly simplified] example? (This checker is quite sensitive to syntax to keep false positives down.)

@timothy-king sure - The body of the loop here is almost identical to my real code (I deleted a couple of lines of logging from the top of the loop body)
This compiles and passes vet, but is incorrect.
package main

import (
	"context"
	"sync"

	"golang.org/x/sync/errgroup"
)

func main() {
	var nodes []interface{}

	ctx := context.Background()
	critical, ctx := errgroup.WithContext(ctx)
	others := sync.WaitGroup{}

	for i, node := range nodes {
		// i, node := i, node
		if IsCritical(node) {
			critical.Go(func() error {
				return run(ctx, i, node)
			})
		} else {
			others.Add(1)
			go func() {
				// We don't care about errors in non-critical nodes
				_ = run(ctx, i, node)
				others.Done()
			}()
		}
	}
}

func IsCritical(node interface{}) bool {
	return false
}

func run(ctx context.Context, i int, node interface{}) error {
	return nil
}

@glenjamin That specific example is supportable in loopclosure. This would require extending the logic of looking for the "last" statement within the RangeStmt to include statements that unconditionally lead to the end of the RangeStmt if they are executed. If branches fit into this. Both branches do not need to match. Just one.
IMO the justification is fairly solid. We can rework the above example into something I expect loopclosure to warn on:
	for i, node := range nodes {
		// i, node := i, node
		if IsCritical(node) {
			critical.Go(func() error {
				return run(ctx, i, node)
			})
			continue // minor refactor
		}
		others.Add(1)
		go func() { // now the last statement
			// We don't care about errors in non-critical nodes
			_ = run(ctx, i, node)
			others.Done()
		}()
	}

Again we welcome community contributions on this (and we are currently in the 1.18 freeze).

Actually, note that those captures - at least when they are definite bugs - should usually show up in the race detector.

Unfortunately @rsc , they don't, in a typical buggy table test case:
func TestParallel(t *testing.T) {
	tests := []struct {name string}{{name: "case1"}, {name: "case2"}}
	for _, tt := range tests {
		t.Run(tt.name, func(t *testing.T) {
			t.Parallel()
			fmt.Println(tt.name)
		})
	}
}

This buggy output and no warning from race detector:
$ go test -race -v .
=== RUN   TestParallel
=== RUN   TestParallel/case1
=== PAUSE TestParallel/case1
=== RUN   TestParallel/case2
=== PAUSE TestParallel/case2
=== CONT  TestParallel/case2
case2
=== CONT  TestParallel/case1
case2
--- PASS: TestParallel (0.00s)
    --- PASS: TestParallel/case2 (0.00s)
    --- PASS: TestParallel/case1 (0.00s)
PASS

@porridge they would, if you run subtests in parallel.

@invidian do they for you?
Adding -test.parallel=3 to that command line does not help on my end.

Ah, I misread and haven't noticed t.Parallel(). Race detector does not trigger indeed. Sorry for the noise.

We have a version of the loopclosure check within Monzo that uses a bunch of heuristics to avoid false positives and has good coverage of most bugs.

@danielchatfield any updates on making this available to the community?

@invidian, the t.Parallel issue in general is #35670. (It masks other kinds of races too, not just races on loop variables.)

See #56010 for a different approach.

Given the interest in possibly changing redefining for loop variable semantics (#56010), I thought it might be useful to try to complete the sketch for extending the loopclosure checker that @alandonovan suggested above in https://github.com/golang/go/issues/16520#issuecomment-507426574.
Rather than the checker examining the last statement in a loop body, the "last" statement examined by the checker becomes defined recursively (e.g., if the last statement in the loop body is a switch statement, then the analyzer examines the last statements in each of the switch cases).
I sent CL go.dev/cl/452155, which does that, and now properly flags the example above from @dmowcomber.
One question @timothy-king raised in the Gerrit discussion is whether or not that change would need to go through the proposal process.  Are there any quick opinions on that?
I'd be happy to open a proposal if that's the recommendation.
(I will likely open a separate proposal for some possible follow-on approaches, but my more immediate question is if CL 452155 should have a proposal).

Hi @glenjamin, FYI, https://go.dev/cl/452155 also seems to properly flag your example from above as well, and stops complaining if you uncomment the  i, node := i, node line:
func main() {
	var nodes []interface{}

	ctx := context.Background()
	critical, ctx := errgroup.WithContext(ctx)
	others := sync.WaitGroup{}

	for i, node := range nodes {
		// i, node := i, node
		if IsCritical(node) {
			critical.Go(func() error {
				return run(ctx, i, node) // vet now warns i and node captured by func literal
			})
		} else {
			others.Add(1)
			go func() {
				// We don't care about errors in non-critical nodes
				_ = run(ctx, i, node) // vet now warns i and node captured by func literal
				others.Done()
			}()
		}
	}
}

func IsCritical(node interface{}) bool                       { return false }
func run(ctx context.Context, i int, node interface{}) error { return nil }

Given that this is improving the precision of an existing vet check, without introducing any new false positives, I don't believe it needs to go through the proposal process.

Is this no longer relevant with go1.22 / should be closed? @adonovan
https://go.dev/blog/loopvar-preview
https://go.dev/blog/go1.22

The long-standing “for” loop gotcha with accidental sharing of loop variables between iterations is now resolved.

Yep. It is fine to close this with the 1.22 lifetime rules.


Prompt looks broken with multiline input

I have a similar issue.

copy-paste multiline bash code (pasted multiline text looks good)

something like this:
git clone https://github.com/jnewland/alfred-open-windows
cd alfred-open-windows
make

enter

Following command tried to execute:
git clone https://github.com/jnewland/alfred-open-windows cd alfred-open-windows make

I have to scroll pasted text, also.


First run: Server Error in '/' Application.

This is what I get when I run the application.
It's a clean 2012 R2 server with .NET and GIT installed.
Just for the kicks I added Everyone with full control to permissions.

Got it fixed.
But now I get this error

hi, sorry but there's a long time since I used this app, I don't actually have an easy way to reproduce that error.
The url shown there seems to be a normal Mvc one, but without an extension (/_self), could that be forbidden by your IIS configuration? what version of IIS are you using?

I'm running a 8.5

I'd start by checking extensionless urls are working with your IIS configuration, I remember IIS6 didn't support them without some work.
Check:
http://haacked.com/archive/2008/11/26/asp.net-mvc-on-iis-6-walkthrough.aspx/

I'm not sure that extensionless URL's are the problem, since I already have other websites running on that server that are extensionless.
I'll try to install it on a 2007 server before the weekend.

Well, I have the same problem on a Windows 7 running IIS 7.5 so I have no idea what to problem might be.
I'm running this website on the same server:
http://basic1.sheriffone.com:81/
So I don't think it's the extensions URLs that's causing this.

Done a little digging.
Extensionless URLs are working fine: http://gitdeploy.sheriffone.com:81/Instance/ChangeLog/_self

awesome, I can see your dashboard, I see you have a different error now, about github auth on git fetch.
remember you''d need to log into the server, and git clone the repo yourself the first time (the user running the web app just needs permissions to do git fetch after that).


uninitialized constant VerboseMigrations::MigrationExtension (NameError) with ruby 3.2.4 and Rails 7

Error on running rake db:migrate after adding verbose_migrations to gemfile and running a new migration
/Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/verbose_migrations-1.0.0/lib/verbose_migrations/railtie.rb:5:in `block in <module:VerboseMigrations>': uninitialized constant VerboseMigrations::MigrationExtension (NameError)
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/lazy_load_hooks.rb:95:in `class_eval'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/lazy_load_hooks.rb:95:in `block in execute_hook'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/lazy_load_hooks.rb:85:in `with_execution_control'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/lazy_load_hooks.rb:90:in `execute_hook'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/lazy_load_hooks.rb:60:in `block in on_load'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/lazy_load_hooks.rb:59:in `each'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/lazy_load_hooks.rb:59:in `on_load'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/verbose_migrations-1.0.0/lib/verbose_migrations/railtie.rb:4:in `<module:VerboseMigrations>'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/verbose_migrations-1.0.0/lib/verbose_migrations/railtie.rb:3:in `<main>'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/verbose_migrations-1.0.0/lib/verbose_migrations.rb:8:in `require_relative'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/verbose_migrations-1.0.0/lib/verbose_migrations.rb:8:in `<main>'
	from <internal:/Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
	from <internal:/Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/zeitwerk-2.6.17/lib/zeitwerk/kernel.rb:34:in `require'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/bundler-2.5.5/lib/bundler/runtime.rb:60:in `block (2 levels) in require'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/bundler-2.5.5/lib/bundler/runtime.rb:55:in `each'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/bundler-2.5.5/lib/bundler/runtime.rb:55:in `block in require'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/bundler-2.5.5/lib/bundler/runtime.rb:44:in `each'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/bundler-2.5.5/lib/bundler/runtime.rb:44:in `require'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/bundler-2.5.5/lib/bundler.rb:187:in `require'
	from /Users/me/ph/app-workflow/config/application.rb:21:in `<top (required)>'
	from <internal:/Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
	from <internal:/Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/spring-4.2.1/lib/spring/application.rb:97:in `preload'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/spring-4.2.1/lib/spring/application.rb:171:in `serve'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/spring-4.2.1/lib/spring/application.rb:153:in `block in run'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/spring-4.2.1/lib/spring/application.rb:147:in `loop'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/spring-4.2.1/lib/spring/application.rb:147:in `run'
	from /Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/gems/spring-4.2.1/lib/spring/application/boot.rb:25:in `<top (required)>'
	from <internal:/Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:86:in `require'
	from <internal:/Users/me/.asdf/installs/ruby/3.2.4/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:86:in `require'
	from -e:1:in `<main>'

new migration:
class AddTableFoo < ActiveRecord::Migration[6.1]
  verbose!

  def change
    create_table :foo do |t|
      t.string :external_id, null: false, index: { unique: true }
      t.jsonb :raw_data

      t.timestamps
    end
  end
end

Hmm. Seems like a load issue, since the module is defined here. Give me a few hours and I'll dig in and figure out what's going on here.

Should be fixed in 3e6fe3c95379b992dc3ede6a83208c1beae2fb12. Could you try using master and lmk?
gem 'verbose_migrations', git: 'https://github.com/keygen-sh/verbose_migrations', branch: 'master'

I tested myself and this seems to resolve the issue. Cut release v1.0.1. I'll reopen if the issue persists.

Very cool, thanks!


How to best estimate an average carbon intensity over the duration of a job

We have been discussing with @tlestang about what the data collected by the carbon intensity.org.uk represents, and therefore how best to calculate the average CI over a long period of time.
The API sends data for 30min periods, each value having a from and a to parameter (e.g. 50 gCO2e from 7:00am to 7:30am).
There are at least two ways these values can have been obtained (figure below).

Assuming the blue line is the real (continue) CI forecast:

The values provided can be timepoints on that curve (red dots) that are then provided for the next 30min (in the example above, the value for 9:00-9:30 would be 40)
Or they could have already been averaged over the 30min (green lines). In the example above, the value for 9:00-9:30 would be 45.
The consequence is that in case (1), it is best to approximate the blues curve by using some form of integration between the red dots (trapezoidal was used so far), while in (2), it is best to sum the respective averages (easier).

Probably best to have both options implemented for when/if we add now APIs, but also good to have a good understanding of what's best.
I'm emailing the people in charge to ask about that, but good to hear everyone's thoughts about that! (as it's quite an important part of the tool!)

carbonintensity.org.uk says (under Methodology):

The demand and generation by fuel type (gas, coal, wind, nuclear, solar etc.) for each region is forecast several days ahead at 30-min temporal resolution [...]. The forecasts are updated every 30 mins using a nowcasting technique to adjust the forecasts a short period ahead.

The natiogridESO report (link) says:

The GB carbon intensity $C_t$ at time $t$ is found by weighting the carbon intensity $c_g$ for fuel type $g$ by the generation $P_{g,t}$ of that fuel type. This is then divided by national demand $D_t$ to give the carbon intensity for GB

To me this is indicating that intensity values provided by the API are point estimates rather that the result of an average over the 30min period.
Let's see what they say

@Llannelongue did you hear from the people behind carbonintensity.org.uk about this?

Their paper on the methodology says "Estimated carbon intensity data is provided at the end
of each half hour settlement period." - which I think means it's a point estimate but with the dots at the other end of the red lines.


Shard indices with relations

Resolves https://github.com/wellcomecollection/platform/issues/4930

This appears to be overridden just below :thinking:
https://github.com/wellcomecollection/catalogue/blob/02d003419978dc7cc5d463bc31bb5a82248113ff/common/elasticsearch/src/main/scala/uk/ac/wellcome/elasticsearch/ElasticsearchIndexCreator.scala#L39-L50


Creating Kits v1.1 and v2.2 that just pin "missing" plugins into the versions most suitable for the CLIs used

Most of the PR is Just copying templates/default into templates/fixed-whitelist.

Were you also going to add a<EMAIL_ADDRESS>for cordova 5.4.1, or are we waiting until cordova 6.0 or that?

We are waiting...

:+1: