Maximise return instead of minimising import rates

Describe the feature
This applies to intermittent slot selection.
Think about users who have Agile for both import and export.
Basically, for every 1/2 hour slot, I need to decide whether to use it or export it. I want to use if it's "the cheapest", otherwise I would be better off exporting it.
The problem is the meaning of "cheapest". At the moment, your automation selects the cheapest slots based on import rate only. My point is that it should, instead, choose them based on the difference between import rate of the slected slots and export rate of all the other slots in the selection period, and select the slots that minimise that difference.
Expected behaviour
The slots selected by a target rate sensor would no longer be the ones with the lowest import rates. Instead, they would be the ones that maximise the overall return over the whole selection period.
Use Case
So, suppose I have two 1/2 hour slots A and B, and that I need 1/2 hour to run my appliance:

Slot
Import rate
Export rate

A
1p
10p

B
2p
5p

Your current sensor would activate on slot A, but it would make much more sense exporting slot A and running my appliance on slot B: yes, I would pay more, but I would be better off overall, earning net 8p over the whole period instead of 4p.
Confirmation

[X] By submitting this feature request, you agree that you have read the documentation and confirmed it does not already exist
[ ] I am willing/able to help contribute to the solution of this feature

Thanks for raising. I haven't forgotten your original request. Implementing this would require a significant amount of work, so for now I'm marking this as requiring more demand.

@ccristal I'm interested in your use case here, purely from a point of view of finding a solution. I think I get what you're trying to do, but am getting caught up on the fact your examples show an import rate lower than the export rate - surely that's never the case (otherwise you could just import power and export it immediately for a profit)? I've seen edge cases where this does happen but the difference is usually <1p so I doubt it caters for the inefficiencies.

Oh, it happens all the time. I am on fixed export rate, I get 15p per KW
exported. The import rate is very often less than that. This is today's,
for example:
On Fri, 26 Apr 2024, 12:11 Chris Crocker-White, @.***>
wrote:

@ccristal https://github.com/ccristal I'm interested in your use case
here, purely from a point of view of finding a solution. I think I get what
you're trying to do, but am getting caught up on the fact your examples
show an import rate lower than the export rate - surely that's never the
case (otherwise you could just import power and export it immediately for a
profit)? I've seen edge cases where this does happen but the difference is
usually <1p so I doubt it caters for the inefficiencies.
—
Reply to this email directly, view it on GitHub
https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/issues/850#issuecomment-2079179498,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJKLYJWWJOVY4B6ICAHILTY7IY4PAVCNFSM6AAAAABGRNJ3QGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZZGE3TSNBZHA
.
You are receiving this because you were mentioned.Message ID:
@.***
com>

Oh, it happens all the time. I am on fixed export rate, I get 15p per KW exported. The import rate is very often less than that. It can go to 0, or even negative (i.e. you get paid to consume electricity). And yes, charge and resell is exactly what people may want to do (assuming it's not forbidden by the T&Cs).
Here's an example:

Oh, I was working on the basis you had said 'Think about users who have Agile for both import and export' - makes sense if you're using fixed price export.

I had thought about something similar when it comes to battery lifespan - i.e I want to know how much the energy in the battery cost, to know if it's worth it to discharge the battery (based on a cost per cycle estimation), or if it makes more sense to just import. You'd have a to have a spread between the charge cost and import cost that you're offsetting large enough to offset the cost of using a battery cycle. I guess ideally you'd even want to look forward and know that there's a spread large enough before you even charge in the first place!

With the release of v11.0.0, it brings the ability to set minimum/maximum rates for target rate sensors. This was mainly added due to demand and ease of adding the feature.
As this original issue was around fixed exports, I believe this can be achieved with a target rate sensor which

Targets the import meter
Has a maximum rate set of 0.15
Has Find last applicable rates set to true, which will find the most expensive rate in this scenario.

This will find the slots with the most expensive rates below 15p which will be the slots with your maximum return based on your examples. If there are not enough slots below 15p, then the sensor will not turn on.
Based on this, I'm not sure if this feature is required other than the convenience of not needing to set the maximum rate manually.
As for agile exports, my assumption is these would always increase/decrease inline with imports so not sure if this would be applicable, but would be interesting to know.
@chrisys with your feature, something like predbat might give you what you're after, but I'm not sure.

I attempted to implement a similar feature using the latest release, in my example below I am focusing primarily on the import side first. The same logic would be applicable for an export target rate sensor, but it would use a calculated minimum rate and target_hours from what was acheived on the import side.  These calculated minimum/maximum can ensure at least an x pence delta.
I was able to calculate the maximum rate required using a template and subsequently updated the target rate sensor by calling the service.
However, I'm puzzled as to why the rates aren't populated with as many slots as possible based on the maximum rate when there aren't enough slots. Even if only half of the slots match, there's still value in knowing this. Given that the values (e.g., hours) are always presented as a target, it seems logical to populate as many slots as possible up to the target hours when a maximum or minimum rate is set. For instance, if the maximum hours are 24, the system should find as many slots below the maximum as possible.
There could be an attribute called "target hours achieved", although a template could easily count the rates list and compare to the hours attribute.
I've managed to find a solution, albeit a bit messy. I used another template to calculate the number of hours below the maximum rate, then called the service to change the target rate sensor, including this calculated target_hours.
As a summary, if not enough slots are found when minumum/maximum is used, I think it should still populate the rates with as many as it can and toggle accordingly.

With the release of v11.0.0, it brings the ability to set minimum/maximum rates for target rate sensors. This was mainly added due to demand and ease of adding the feature.
As this original issue was around fixed exports, I believe this can be achieved with a target rate sensor which

Targets the import meter
Has a maximum rate set of 0.15
Has Find last applicable rates set to true, which will find the most expensive rate in this scenario.

This will find the slots with the most expensive rates below 15p which will be the slots with your maximum return based on your examples. If there are not enough slots below 15p, then the sensor will not turn on.
Based on this, I'm not sure if this feature is required other than the convenience of not needing to set the maximum rate manually.
As for agile exports, my assumption is these would always increase/decrease inline with imports so not sure if this would be applicable, but would be interesting to know.
@chrisys with your feature, something like predbat might give you what you're after, but I'm not sure.

Thank you, Dave! I'll let you know how I get on... :-)

However, I'm puzzled as to why the rates aren't populated with as many slots as possible based on the maximum rate when there aren't enough slots

@irata-coder Because if someone states they want 2 hours and I give them 1 hour worth of slots, they'll rightfully raise a bug :) It could be the device they're powering with the sensor might use the most amount of energy on slot 3 of 4, which could be expensive if the sensor didn't meet the required hours.
With the introduction of the min/max values, the target rate sensor could be updated to have hours be optional if min and/or max is specified. However I'm struggling to determine the use case.
The idea behind a continuous slot is for devices that run for a certain amount of time or requires to be on for a certain amount of time (e.g. a dishwasher). The idea behind an intermittent slot is a device that can turn on/off but is required for a set amount of time during the day (e.g. a charger). If you don't require a certain number of hours then it doesn't feel like a target rate sensor is needed. You shouldn't need a continuous slot and an intermittent slot should come on as much as possible. In this scenario you could simply look at the current rate sensor and perform checks on the rate would work. If you needed the slots up front, then you could filter the collection rates via a template sensor.
I've raised https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/issues/869, which if you're requiring this would be good to give a thumbs up and give your example scenarios.

@ccristal I made a slight mistake in my sample. You want to turn on Invert targeted rates not Find last applicable rates

I believe the specified scenarios are now covered by existing functionality in the integration. Therefore, I'll close this issue. Please comment if it's still needed


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1654 ms

Resolved: Bofrost.at performance has improved in 7bd25be after 16 minutes.


Slimefun multiblocks and machines not functioning

This is found to be due to outdated API use in dough as its using the 1.0 version of HuskTowns instead of 2.0.
Upon disabling the town plugin, slimefun works as intended.

Fixed via https://github.com/Slimefun/Slimefun4/pull/3959


Add Enap.ca

@bhebb I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host enap.qc.ca not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for understanding!


pip-dump not splitting requirements correctly

pip 6.0.8
pip-tools==0.3.5
I have a requirements.txt and a dev-requirements.txt (with a proper distribution of packages between the two).
pip-dump gets everything from pip freeze written to both files.
This happens after going to Python 2.7.9 and doing pip install --upgrade pip

:(

Same thing is happening for me

^^ To me too.

This appears to be fixed on master, we just need a new version to be cut and released to PyPI.

I've released the current master branch as 0.3.6 now. Thanks for the work!

hi @nvie
I've updated to latest release (v0.3.6).
The first time I ran pip-dump after upgrade, it emptied both of my requirements files (requirements/common.txt & requirements/dev.txt).  I was confused. So, just after that (and without resetting my requirements files to a good state), I ran pip-dumpfor a second time. Now, myrequirements/common.txtfile got populated with all the requirements, but therequirements/dev.txtfile remained empty. Then, after that, I fixed the files manually, by deleting dev dependencies fromcommon.txtand adding them back todev.txt.  So far, so good, and it was the time for a final test: I've re-run pip-dump, to see if it would mangle my files again, or if it would do nothing at all (which was expected, as both my common.txtanddev.txtwere now manually fixed and up-to-date). Thankfully,pip-dump` did nothing, probably because there was nothing to do, as the requirement files were up-to-date.
Of course, there is still initial the issue of pip-dump emptying my requirement files on first run. I was able to reproduce it several times, by reverting the contents back.
So, my guess (and maybe it's something you could try to do to reproduce my issue) is that pip-dump might be failing (by emptying the requirements files) when they are outdated.
The easy test would be to have an outdated requirements file and run pip-dump.
Let me know if you need more info.

pip-dump is gone with the release of 1.0: http://nvie.com/posts/pip-tools-10-released/


Check user credentials against ews

Hi there,
I was searching on methods which will allow me to check given user-credentials against the ews-api. But I currently did not find something nice. Perhabs it makes sense to have this implemented since I was wondering if many people would run into that?! I found some explanation on this here.

A simple request to EmailMessage.bind() with dummy id like below may be used.
This request responses with 401 Unauthorized when the credentials are wrong.
public boolean login(ExchangeService service) {
	try {
		EmailMessage.bind(service, new ItemId("__dummyId__"), PropertySet.IdOnly);
	} catch ( Exception e ) {
		if ( e.getMessage().contains("Unauthorized") ) {
			return false;
		}
	}
	return true;
}

thanks. I was aware that accessing a given resource would check credentials. In fact I was wondering if there would be a less noisy way to check this while not making expensive operations on the server. But just loading PropertySet.IdOnly seems reasonable.

Here another possible solution.
May require less effort on server.
public boolean login(ExchangeService service) {
    try {
        AlternateIdBase x = service.convertId(new AlternatePublicFolderId(IdFormat.EwsId, "__dummyId__"), IdFormat.EwsId);
    } catch ( Exception e ) {
        if ( e.getMessage().contains("Unauthorized") ) {
            return false;
        }
    }
    return true;
}

i've tested 4 cases with junit. (using id="_")
because of the id is wrong, the requests have same effort on server, and throw "id is malformed".
network elapsed time and response+request size of two methods are quite close.
however, the communication size of EmailMessage.bind a little less than convertId.
so EmailMessage.bind can be selected.

EmailMessage.bind(...)
service.convertId(...)

credentials
correct
wrong
correct
wrong

Request size:
545
545
557
557

Response size:
1066
0
1065
0

Total size:
1611
545
1622
557

It doesn't work for non-English OS (more accurate, for non-English .Net Frameworks).


<IP_ADDRESS> upgrade

Upgrade Quark to Bitcoin <IP_ADDRESS> base

I'm just asking if rpc mining could be reintegrated, my setup was entirely based on this ^^


feat(remix-react): Add array-syntax for meta export

This PR adds array-syntax to the meta export.
export const meta: MetaFunction = ({data}) => [
  { name: "description", content: data.description },
  { property: "og:image", content: "https://remix.run/logo.png" },
  { property: "og:type", content: "image/png" },
  { key: "http-equiv:refresh", httpEquiv: "refresh", content: "5;url=https://google.com" },
  { title: data.title },
  { name: "viewport", content: "width=device-width, initial-scale=1" },
];

@kiliman Could you fix conflicts here please?

Hello team, I want to mention a scenario I found, where open graph og:image accept multiple metatags with the same name, as described at: https://ogp.me/#array

If a tag can have multiple values, just put multiple versions of the same  tag on your page. The first tag (from top > to bottom) is given preference during conflicts.
<meta property="og:image" content="https://example.com/rock.jpg" />
<meta property="og:image" content="https://example.com/rock2.jpg" />

Put structured properties after you declare their root tag. Whenever another root element is parsed, that structured property is considered to be done and another one is started.
For example:
<meta property="og:image" content="https://example.com/rock.jpg" />
<meta property="og:image:width" content="300" />
<meta property="og:image:height" content="300" />
<meta property="og:image" content="https://example.com/rock2.jpg" />
<meta property="og:image" content="https://example.com/rock3.jpg" />
<meta property="og:image:height" content="1000" />

means there are 3 images on this page, the first image is 300x300, the middle one has unspecified dimensions, and the last one is 1000px tall.

Just want to mention that this PR might allow this open graph usage. Thank you.

@machour I've rebased onto latest dev
@felquis I added support for duplicate property names. It dedupes by property+content. If you need to override dupes, you can provide a unique key for each.
https://github.com/remix-run/remix/blob/87594af3f1f6f0ef06c1a712b67f5ef1657b5137/integration/meta-test.ts#L146-L159
https://github.com/remix-run/remix/blob/87594af3f1f6f0ef06c1a712b67f5ef1657b5137/integration/meta-test.ts#L253-L260

It dedupes by property+content. If you need to override dupes, you can provide a unique key for each.

@kiliman This seems like it could be error-prone across nested route boundaries.  For this to work would users need to provide keys for every tag, or just tags that support duplicates for array values?

Just want to mention that this PR might allow this open graph usage. Thank you.

@felquis Just so you know, you can already do this today with the existing API. You just need to pass an array to the tag's content.
export function meta() {
  return {
    "og:image": [
      "https://picsum.photos/300/300",
      "https://picsum.photos/200/200",
    ],
  };
}

@chaance thank you for mentioning me.
Can you show me how the usage you showed me can be
applied to reproduce the following usage suggested by Open Graph?
<meta property="og:image" content="https://example.com/rock.jpg" />
<meta property="og:image:width" content="300" />
<meta property="og:image:height" content="300" />
<meta property="og:image" content="https://example.com/rock2.jpg" />
<meta property="og:image" content="https://example.com/rock3.jpg" />
<meta property="og:image:height" content="1000" />

I don't want to make this discussion longer though, you can create another discussion/issue if you think it may be relevant to link in the future
Thank you so much for your help! ❤

For all interested, we have an RFC that will address a lot of the issues mentioned in this thread. https://github.com/remix-run/remix/discussions/4462


Automatic driver updates

Automatically check if new versions of the Firefox driver (geckodriver) or Edge driver are available and download them.

Implemented with https://github.com/TSerious/QuickFioriTimeEvents/releases/tag/v1.3

Implemented with https://github.com/TSerious/QuickFioriTimeEvents/releases/tag/v1.3 which uses https://github.com/SergeyPirogov/webdriver_manager to automatically load latest driver.


Feature request:  CLI tool

This library is rad sauce.  However, I am finding that when I want to use it, it's usually a one off where I don't want to write code.  I'd love to just do this:
$ npm install -g require-so-slow
$ rss googleapis

This would just drop a googleapis.trace in the CWD.  If I wanted, I could be explicit:
$ rss googleapis@24 g24.trace

Happy to contribute if you think this makes sense in this repo 👍

That would be awesome. Happy to take contributions :)


merging tracks

Hi! Thanks for the great library!
I have a feature request that might already be there, but I didn't find it: is it possible to merge all tracks in a score object into a single track? I'm aware this could create issues with the same pitch being played at the same time in different tracks, but for several of my files it should work.

If  you only cares about note, you could just use the extend method of note list.
tracks[0].notes.extend(track[1].notes)
Currently, extend's interface semantics are different from Python's, which will lead to a deep copy; I'll try to align it with the Python list later on.
Also, you may have conflicts when merging other events, such as pedals. Like miditoolkit, symusic parses it as an event with a duration, and the inner restriction is that there can't be a time overlap. Merging it directly will cause some problems. Of course, we now ignore pedals when writing to midi, because the original information is in the control change.


add ci badge

@all-contributors please add @mg-diego  as contributor
@all-contributors please add @Rabosa616  as contributor

@all-contributors please add @mg-diego for code

@all-contributors please add @Rabosa616  for code


Disable statement doesn't have vpiExpr node

According to 37.75, vpiDisable should have vpiExpr node with information what is disabled. Now there is no such node.
Here is example source:
module top;
   initial begin
      forever begin : loop
         disable loop;
      end
   end
endmodule // top

And here is uhdm:
slpp_all/surelog.uhdm: Restored design Pre-Elab:
design: (work@top)
|vpiName:work@top
|uhdmallModules:
\_module: work@top (work@top) disable.sv:1:1: , endln:7:10, parent:work@top
  |vpiDefName:work@top
  |vpiFullName:work@top
  |vpiProcess:
  \_initial: , parent:work@top
    |vpiStmt:
    \_begin: (work@top), line:2:12, endln:6:7
      |vpiFullName:work@top
      |vpiStmt:
      \_forever_stmt: , line:3:7, endln:3:14, parent:work@top
        |vpiStmt:
        \_named_begin: (work@top.loop), line:3:15, endln:5:10
          |vpiName:loop
<EMAIL_ADDRESS>          |vpiStmt:
          \_disable: , line:4:3, endln:4:16<EMAIL_ADDRESS>|uhdmtopModules:
\_module: work@top (work@top) disable.sv:1:1: , endln:7:10
  |vpiDefName:work@top
  |vpiName:work@top

Fixed by #2253


Round trip formatting / comments

This issue is in the open design phase and is a part of the project.json -> csproj  conversion effort.
We should preserve user authored content/whitespace in project files when saving.
E.g.
<PropertyGroup>
  <TargetFrameworkVersion>v4.5.2</TargetFrameworkVersion> <!-- 4.5.2 for back-compat -->
</PropertyGroup>

Today will be re-saved as:
<PropertyGroup>
  <TargetFrameworkVersion>v4.5.2</TargetFrameworkVersion>
  <!-- 4.5.2 for back-compat -->
</PropertyGroup>

We should investigate to see if there's an easy win here, but we should not be creating our own XML writer for this release.

It not only changes the location of comments, it also changes indentation, and removes non-significant whitespace.
I did some investigation, and looks like this is going to be an easy fix to preserve whitespace/comments, etc. CPS calls through ProjectRootElement Open(string path, ProjectCollection projectCollection) this path causes XmlDocument.PreserveWhitespace to default to false (here)[http://index/#Microsoft.Build/Evaluation/ProjectRootElementCache.cs,233]. If CPS has an overload where it could opt-into preserving whitespace (you'll probably want that for compat, rather than turning it on by default), then we can avoid changing the underlying project file.

It doesn't have to be an overload, it could just a mutable property on the ProjectRootElement.

@davkean Does CPS set the MSBUILDCACHECHECKFILECONTENT environment variable?  The code you pointed to is only active if that variable is set.

I have a work in progress fix for this at https://github.com/dsplaisted/msbuild/tree/AllowPreserveWhitespace
It turns out that single quotes are being converted to double quotes when a project is saved.  IE this:
<ProjectReference Include='..\CLREXE\CLREXE.vcxproj'>

Will be converted to this:
<ProjectReference Include="..\CLREXE\CLREXE.vcxproj">

I haven't figured out where the quote conversion is happening yet.

Not sure the relevance of MSBUILDCACHECHECKFILECONTENT, from what I see - it's just a test hook.
Not too worried about the single quote -> double quote conversion, I wouldn't block the check-in on that (it's probably in the XML writer). Can we get this in soon?


[memgraph-2-12 < api-path-pop] Add docs for path pop in API

Description
Add docs for path pop in API.
Pull request type
Please check what kind of PR this is:

[X] Fix or improvement of an existing page

Related PRs and issues
PR this doc page is related to:
PR1249
(especially necessary if the PR is related to a release)
Closes:
(paste the link to the issue it closes)
Checklist:

[x] Check all content with Grammarly
[x] Perform a self-review of my code
[x] Make corresponding changes to the rest of the documentation (consult with the DX team)
[x] The build passes locally
[x] My changes generate no new warnings or errors
[x] Add a corresponding label
[ ] If release-related, add a product and version label
[x] If release-related, add release note on product PR

I approve but will not merge until the product PR is not assigned a milestone confirming it will be 100% merged in v2.12


Tool to confirm a new model can be used for parameter estimation

Summary of this new feature
When we will create a new model to understand the outbreak deeply, we need a tool to confirm that the models can be used for parameter estimation. This is related to #276
c.f. If the model has too many parameters and few measurable varibles, parameter estimation fails.
Solution
A solution is as follows.

Simulate the number of cases with an user-defined parameter set.
Perform parameter estimation with the therotical data (the dataset created with step 1).
Compare the user-defined parameter set and estimated parameter set.
Repeat with anather set of parameters.

When the difference of the two parameter sets was small, we will confirm that the model can be used for parameter estimation.
Notes:

Theoritical data has only one phase.
Step 1 will be performed with ExampleData class.
Step 2 will be performed with Scenario.estimate() class.
For step 3, we need to decide the metrics. RMSLE etc.

Usage of ExampleData class is documented in https://lisphilar.github.io/covid19-sir/usage_theoretical.html

Okay, now I understand what exactly you meant by performing validation on theoretical data. I agree with that solution.

Yes, estimated paramerters (x parameter set you got finally) could be different from the applied x parameter set if the model or prameter estimation sstem have some errors.

With #292, I added covsirphy.analyse.model_validator.ModelValidator class in version 2.9.1-gamma.
With following codes, we can validate some models.
import covsirphy.as cs
# Set the number of parameter sets (n_trials=8 as default), random seed (seed=1 as default)
validator = cs.ModelValidator(n_trials=8, seed=1)
# Validate models
# timeout=60 as default: time-out of parameter estimation
# allowance=(0.98, 1.02) as default: this is the same as that of Scenario.estimate()
# while max(simulated) < 0.98 * max(theoritical) or max(simulated) > 1.02 * max(theoritical),
# parameter estimation continues
validator.run(cs.SIR, timeout=60, allowance=(0.98, 1.02)
validator.run(cs.SIRD, timeout=60, allowance=(0.98, 1.02)
validator.run(cs.SIRF, timeout=60, allowance=(0.98, 1.02)
# Summarize
validator.summary()

Methods of visualization and scoring are not prepared currently, but we can analyze the results using the output of validator.summary(), a pandas.DataFrame.
Example code are in example/model_validation.py script.
We need to improve SIR-F model and the estimator because the difference of "Rt" (setting) and "Rt_est" (estimated) is small, but the difference of parameter values are not small.

Can we close this issue about model validator and move to #291 ?

Yes I think we can close this issue now.


Integration is broken

Integration branch seems to be in pretty bad shape. Mostly related to unfinished database changes, I guess. For example, I can't even create a new page without running into exceptions. Not a good state to be in for other developers to work on.
I created a 2.7.x branch and milestone for backwards compatible changes and feature additions, and updated the due date for the 3.0.0 milestone to a more realistic date.
Doesn't necessarily mean we have to actually release a 2.7.0 if 3.0.0 gets back on track soon enough, but at least developers have something to work with and issue pull requests against.

Effort is better put in correcting integration than diverting effort to
2.7. I will not be back porting any features to 2.x. Community is welcome
too, but personally I have no interest in doing so, its time to move
forward.
On 1 May 2015 8:27 pm, "Jens Scherbl"<EMAIL_ADDRESS>wrote:

Integration branch seems to be in pretty bad shape. Mostly related to
unfinished database changes, I guess. For example, I can't even create a
new page without running into exceptions. Not a good state to be in for
other developers to work on.
I created a 2.7.x branch
https://github.com/symphonycms/symphony-2/tree/2.7.x and milestone
https://github.com/symphonycms/symphony-2/milestones/2.7.0 for
backwards compatible changes and feature additions, and updated the due
date for the 3.0.0 milestone
https://github.com/symphonycms/symphony-2/milestones/3.0.0 to a more
realistic date.
Doesn't necessarily mean we have to actually release a 2.7.0 if 3.0.0
gets back on track soon enough, but at least developers have something to
work with and issue pull requests against.
—
Reply to this email directly or view it on GitHub
https://github.com/symphonycms/symphony-2/issues/2416.

I will not be back porting any features to 2.x.

Agreed, no need to backport anything from 3.0.0 to 2.7.x. This is just meant as a more stable branch for adding new changes and features that don't break compatibility.

its time to move forward

Totally agree.
If integration had been stable enough to work with, I would have used integration instead.

Effort is better put in correcting integration

Sure, but if I have to put in half a day to debug and fix unfinished work from others before getting to work on my own changes, that's not a very good starting point for moving forward.

@brendo @jensscherbl Do not hesitate to tell me to fix things or do things. I am mostly doing maintenance these days and can only fix what I know about.

Do not hesitate to tell me to fix things or do things. I am mostly doing maintenance these days and can only fix what I know about.

Thanks :)
#2418
#2415

@jensscherbl I'll see what I can do!


WIP; so far I've done a few of the key tasks.  I also took the opportunity to refactor service.js and compattable.js to be promise based.
A few issues to address:

Options passed from gruntfile to task: Makes sense to use minimist for these (eg. service task), but others are unnecessary
Logging is less easily coloured and controlled, but we can get more flexibility, eg as we're already doing in the saucelabs task.  It might be worth creating a few useful higher level abstractions to replace things like grunt.verbose.  We still have the issue of differentiating the stdout of the child process from the output of the service task (and subsequent tasks like sauce), which is not handled well under grunt anyway, and maybe this is an opportunity to improve it.
Most grunt contrib modules can be trivially replaced by shell commands, eg simplemocha => mocha test/node/**/*.js.  I haven't thought about watch yet but maybe nodemon?

Going to pause this to see if @JakeChampion thinks it's worth finishing / is going in the right direction.

Seems good, what's the reasoning behind this? If this progresses could we test to see if it still works on Windows OS for development.
Would you have a programmatic way of displaying what tasks are available?

Reasoning:

No other Origami services use grunt (do they?) so it creates a learning curve
Grunt isn't really very popular anymore so it might limit community participation
It adds dependencies. I don't like unnecessary dependencies :-)
Generally the non-grunt versions of tasks are actually shorter than the grunt version

Displaying tasks: yes, run npm run

This all sounds great. Origami services have started using Make and Makefiles, not sure if this project should move in that direction or not, happy either way.

Oh, I thought you'd want to discuss this!  But great.  Do the tasks work for you?


feat: vec index trait

Pull Request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?
To fetch an element at a particular index in a Vec, one has to use at
Issue Number: N/A
What is the new behavior?
PR implements the Index trait to allow for using [] operator when fetching Vec elements:
let element_at_2 = a_vec[2];

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

Bump


Clean up hardcoded values in hgserver_nginx.conf

These were values we had in the comments. Looks better now.


Use semver logic to filter and sort repository tags

Version tagging runs into a problem on repositories that contain tags other than version tags. This patch uses a node.js one-liner to filter the tags down to those that are valid version strings, and sort them using semver's own logic.

Fixes #3


Example throws error:  EACCES

> electron-color-picker-example@ start /Users/~/Downloads/…/electron-color-picker/example
> electron ./main.js

[main:ipc-task:color-picker] start
[main:ipc-task:color-picker] done { result: undefined,
  error:
   { Error: spawn /Users/~/Downloads/…/electron-color-picker/example/node_modules/electron-color-picker/library/darwin/mockingbot-color-picker.app/Contents/MacOS/ColorPicker EACCES
       at Process.ChildProcess._handle.onexit (internal/child_process.js:246:19)
       at onErrorNT (internal/child_process.js:429:16)
       at processTicksAndRejections (internal/process/task_queues.js:81:17)
     errno: 'EACCES',
     code: 'EACCES',
     syscall:
      'spawn /Users/~/Downloads/…/electron-color-picker/example/node_modules/electron-color-picker/library/darwin/mockingbot-color-picker.app/Contents/MacOS/ColorPicker',
     path:
      '/Users/~/Downloads/…/electron-color-picker/example/node_modules/electron-color-picker/library/darwin/mockingbot-color-picker.app/Contents/MacOS/ColorPicker',
     spawnargs: [],
     cmd:
      '/Users/~/Downloads/…/electron-color-picker/example/node_modules/electron-color-picker/library/darwin/mockingbot-color-picker.app/Contents/MacOS/ColorPicker' } }

Clicking the button more than once creates this error
[main:ipc-task:color-picker] done { result: undefined,
  error:
   Error: color picker already running!
       at exports.getColorHexRGB (/Users/~/Downloads/…/electron-color-picker/example/node_modules/electron-color-picker/library/index.js:6:46)
       at EventEmitter.<anonymous> (/Users/~/Downloads/…/electron-color-picker/example/main.js:20:37)
       at EventEmitter.emit (events.js:194:13)
       at WebContents.<anonymous> (/Users/~/Downloads/…/electron-color-picker/example/node_modules/electron/dist/Electron.app/Contents/Resources/electron.asar/browser/api/web-contents.js:390:13)
       at WebContents.emit (events.js:194:13) }

Following https://github.com/npm/npm/issues/17268 does not fix the issue.
Using MacOS 10.14.5 with https://github.com/nodenv/nodenv node v11.13.0

Using sudo chmod -R 777 node_modules worked, but that’s really breaking glass for emergencies…

Consider running an initialization with shell chmod, similar to IBM-Design/Color-Bee

Thanks for reporting this!
In our internal usage there do have a snippet for resetting the permission, like this:
  const { chmodSync } = require('fs')
  const { join } = require('path')
  const rimraf = require('rimraf') // or other `rm -rf` code

  const BUILD_PLATFORM = process.platform // NOTE: or your target platform
  const PATH_ELECTRON_COLOR_PICKER = '/full/path/to/node_modules/electron-color-picker/'

  console.log('fix permission')
  BUILD_PLATFORM === 'linux' && chmodSync(join(PATH_ELECTRON_COLOR_PICKER, 'linux/linux-scrot/scrot'), 0o777)
  BUILD_PLATFORM === 'darwin' && chmodSync(join(PATH_ELECTRON_COLOR_PICKER, 'darwin/mockingbot-color-picker.app/Contents/MacOS/ColorPicker'), 0o777)

  console.log('trim extra platform (optional)') // Optional, to make output package smaller
  BUILD_PLATFORM !== 'win32' && rimraf.sync(join(PATH_ELECTRON_COLOR_PICKER, 'win32'))
  BUILD_PLATFORM !== 'linux' && rimraf.sync(join(PATH_ELECTRON_COLOR_PICKER, 'linux'))
  BUILD_PLATFORM !== 'darwin' && rimraf.sync(join(PATH_ELECTRON_COLOR_PICKER, 'darwin'))

Maybe this can be fixed by package the .tgz with correct permission, and some mentioning in README.md.
Will test for a fix later.

My only suggestion is to use a stricter permission than 777, but sounds great! 👍

Sorry for the long delay!
After checking some package like: https://github.com/sindresorhus/open.
It seems reasonable to pack executable with  0o755 permission directly into .tgz.
The npm pack is now forbidden to run from win32 platform, due to permission loss in .tgz file.
The release process of Electron app with this package is kind of complex.
A short description is added to #about-release-packaging.
And a more complete dev & packing process has been added to  example/, be sure to run & test that following #example.

Electron Builder
It would be great to include instructions for electron-builder as well.  I’ve been pouring over their documentation, and I’m not quite sure which configuration is best.

In Common Configuration, “Node modules, that must be unpacked, will be detected automatically, you don’t need to explicitly set asarUnpack - please file an issue if this doesn’t work.”
This medium article demo’d setting the executables inside extra-resources

Example
I haven’t had the time to thoroughly understand the example yet.  I noticed it depends on dr-js, which while I’m glad is helpful, makes it harder for beginners to understand without more documentation and adds a dependency to this module.
My question is—does the example build process change/patch the scripts since the locations of the executables change after being bundled?  If the example is actually doing something else, could you give a high level overview on how it works? 🙂
If we’re patching the location in the scripts in the build process, I think a more permanent and streamlined solution would be to add configuration/options for the location of the executables (and have default configurations available for tools like electron-builder, electron-packager, and electron-forge).
Other Considerations
We should warn about using asar: false in the readme.  It comes with drawbacks, such as node_modules failing due to long paths on windows.
Glad 0o755 works 👍
Thank you for your help on this!  I think we’re getting close to a permanent solution 💯

Haven't used electron-builder yet. (the doc is quite long though)
Can you run the example and get a working Electron package?

The idea of the example is to show a working Electron app project setup,
with most of the code inside app.asar,
but also can require and use electron-color-picker.
A special delegate require file is needed: example/source/main/electronColorPicker.js to switch path between dev/prod mode, to access the correct electron-color-picker code
This minimal setup is extracted from our app build script. It should allow:

Develop with unpacked electron
Build packed electron app

And will put output file to 2 extra folder:

./pack-0-source-gitignore/: prepared source code (main/renderer) ready for pack
./pack-1-output-gitignore/: packed Electron app

For develop, the step is like: (npm run run-dev)

npm run script-pack-0-source-dev:

delete & recreate to reset ./pack-0-source-gitignore/ content
build code & output to: ./pack-0-source-gitignore/ (npm run build-pack-0-source-dev)

run code with electron ./pack-0-source-gitignore/main/index.js

For Production/Release, the step is like: (npm run run-prod)

npm run script-pack-0-source:

delete & recreate to reset ./pack-0-source-gitignore/ content
build code & output to: ./pack-0-source-gitignore/ (npm run build-pack-0-source)
better optimize output file with code minify & remove unused file

npm run script-pack-1-output:

delete & recreate to reset ./pack-1-output-gitignore/ content
pack with electron-packager and output to ./pack-1-output-gitignore/
copy electron-color-picker from node_modules, and put under output resources/ folder
optionally delete unused platform code from copied electron-color-picker

Follow the steps there is no special modification required for electron-color-picker package, just extra copy & special require code to toggle path.
In our build setup, we want to have more control of the intermediate output, for optimize, debug and later inspection, so we used electron-packager for only the packing.
With electron-builder these custom steps should be possible to add, but may be harder, since it did a lot more than packing.

Will sort and add a more clear description to README.md later.

great!

Thank you @ThatBean 👍 that explanation helped a lot.
I’m moving into a new house this month, so all my free time is put into packing everything and collecting legal documents.  Once I’m settled down, I’ll try and see if I can get this package working with electron-builder.

I was able to get the resources copied over with electron-packager, but the picker still does not work when packaged with my app https://github.com/mockingbot/electron-color-picker/issues/6
I believe the process for electron-builder would be the same as electron-packager, where you can specify extraResource and have the files copied over.
Does anyone have this working on MacOS? I keep getting permissions issues, and no matter how many times I give permissions for input, I keep getting the popup asking for permissions.

Recent update for darwin platform is tracked in this issue: https://github.com/mockingbot/electron-color-picker/issues/6


Connection endpoints

Scaffolding of desired connection endpoints.
closing #48

@vineeth14 please have a look/do a code review when you find the time

@vineeth14 I can run the tests locally without a problem. Not sure yet why they fail in GH actions. I'll do some digging.

@vineeth14 ready for review 👍🤗

@vineeth14 you can merge it and make it generic afetr #58 is merged imo

@vineeth14 Please have a look and merge when ready

Cool, will have a look


ADR: Use Box + sx to author components

There are  2 common ways to create components with primer/react:

with styled-components
with Box + sx

This ADR recommends using the 2nd one exclusively. See rendered markdown →
Next step after ADR is accepted: Update contributor docs.

As discussed among the PRC maintainers group, let's try assigning a decision-maker here so we can move this ADR toward a conclusion.
ADR decision maker: @rezrah
Decision deadline: Friday, 22 April
I'm going to work on more enduring documentation about this process, but in the meantime:
Your role as decision maker is to gather feedback, probe for discussion and disagreement, and then make an informed decision based on the feedback, identified risks, and trade-offs about whether to adopt the ADR or not. Your role is not to decide based on your own personally preferred approach.
Keep in mind that ADR decisions can be reversed or changed in the future if new information is exposed that make the ADR worth revisiting.
You can fulfill your decision maker role by doing the following:

review the ADR, comments, and feedback closely
seek additional feedback from any necessary parties, as needed; for example, request a review from any individuals or teams that you know would be unduly affected by this ADR, or who have extensive experience in using either the preferred or non-preferred approach and may have perspective to share about it
follow up on any remaining concerns, questions, or unexamined risks around accepting the proposed approach
on or before the deadline, make a decision as to whether the ADR is accepted ✅ , which you should signal by approving this PR, or rejected 🚫 , which you should signal by closing this PR with a comment explaining the reason(s)

Is there any consideration for using sx but recommending it be defined in a static scope, with nested classnames, etc being updated instead of the actual sx object?
I think that avoids consumers using styled-components directly, but also avoids the runtime overhead of sx object equality?

Not yet, I only have that in a prototypes outside of primer/react 😅


Restore-DbaFromDatabaseSnapshot, fix for typo

merge this ASAP

thanks for the catch, i did fix it straight to dev!

oddly enough, it passed all sorts of tests (and failed one) and i couldnt find it until i synced. So weird.


fix(RHINENG-7680): Sort system OS column with new API 'os' sort param

Allows sorting by both name and version together

Before PR, sorting is done using OS version only, so CentOS and RHEL hosts are intermixed:

After PR, the sorting is done using both OS name and version (via the new Tasks API sort parameter 'os'):

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

Comparison is base (061c777) 82.70% compared to head (d6730cd) 82.59%.

:exclamation: Current head d6730cd differs from pull request most recent head c1e77c6. Consider uploading reports for the commit c1e77c6 to get more accurate results

Files
Patch %
Lines

src/SmartComponents/SystemTable/helpers.js
0.00%
2 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #143      +/-   ##
==========================================
- Coverage   82.70%   82.59%   -0.12%
==========================================
  Files          69       69
  Lines        1434     1436       +2
  Branches      467      469       +2
==========================================
  Hits         1186     1186
- Misses        217      219       +2
  Partials       31       31

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


Large indexes

We are using the GPTVectorStoreIndex and begin to hit some practical limits of using it since it is all stored in memory. E.g. loading a 7000 article index in our case needs 3GB RAM.
If we use a Pinecone (or similar) backend with LlamaIndex on top, will this avoid the issue by never loading the full index into memory and just dynamically querying what it needs from the vector database, or does LlamaIndex still attempt to load the whole index into memory?
If the latter any recommendations on how to keep the memory footprint down?

Yes, if you use an external vector store service, only the top-k documents will be loaded into memory.

Many thanks!


See about changing rider plugin id

I created the rider plugin with an id of 'com.intellij.csharpier`. This is now producing the following warning
Invalid plugin descriptor 'id'. The plugin ID 'com.intellij.csharpier' has a prefix 'com.intellij' that is not allowed.

However the documentation says that the plugin id should not be changed after it is created. Is there a path away from the unintentional com.intellij prefix?
https://plugins.jetbrains.com/docs/intellij/plugin-configuration-file.html#idea-plugin__id

Jetbrains let me know that they will be getting rid of this warning for existing plugins.


Improve Handling when Grails backend unavailable

We have two issues here --

Our error message is still too wonky ("EnvironmentService blah, blah..") We need to get right to the point about the "UI Server is Unavailable".

If you go ahead and try to submit the error, that just fails and annoyingly does nothing, and does not close the dialog.

I think 2 is probably something we can handle with better exception handling generally on that button action.... should never just fail silently like that!  Its just heaping more pain on an already suffering user....

Yana -- are you working on this yet?  if not, would like to give it to Don

not yet, it's all Don's!


Optionally implement terraform-provider-utils as a provider-defined function for Terraform 1.8+

Describe the Feature
Thank you for supporting the Terraform community with this data provider! If you were using the data provider construct to work around the lack of support in Terraform for external functions, please consider the following new feature of Terraform.
Terraform version 1.8 launches with support of provider-defined functions. It is now possible to implement this functionality as a function, rather than wrap the functionality in a data provider. Provider-based functions have the advantage of a simpler in-line syntax that does not require the data block (or any other resource blocks) to use.
The caveat is that, as provider-defined functions are new to Terraform 1.8, you would need to continue to maintain the current data provider functionality if you wished to continue to support earlier versions of Terraform.
Please see the provider-defined functions documentation to learn how to implement functions in your providers. If you have any questions, please visit the Terraform topic in our official forum.
We greatly appreciate your support of the Terraform community with your contributions. If you do not wish to implement this functionality as a function, please feel free to close this issue. This issue is simply to raise awareness of the new capability. Thanks again!
Expected Behavior
n/a
Use Case
n/a
Describe Ideal Solution
n/a
Alternatives Considered
No response
Additional Context
No response

I posted a similar issue to the template provider, apologies if this is one issue too many on this topic. :)


#16 Move everything under package cats.effect.testing

See: #16

@djspiewak , looks like this will result in binary incompatibilities. Feels like it should be possible to offer binary compat using a pattern similar to https://github.com/circe/circe/blob/4aae26ab3eed57a8320bc95645bf22af48754b54/modules/core/shared/src/main/scala/io/circe/package.scala#L3 . Dunno whether this would work for abstract classes though.
Any recommendations would be greatly appreciated!

I think it's better just to break compatibility! We're still in 0.x land. Once we get to 1.0 we'll lock things down a bit more aggressively.
So in order to break compatibility, you need to increment the baseVersion setting in build.sbt. That should make mima happy

@djspiewak , bumped the version for the mima check. Should be good to go now.

Thanks for the merge @djspiewak !


Refactor image_t

Goal: faster tensor to image transformations
Todo:

store luma and rgb/rgba patches as tensor3d_t objects
simplify image_t interface: just load/save from file, load/save from tensor, resize, fill, block<> ...

May remove image_grid_t

Still to do:

can remove fill and copy functionality from image_t -> should use plane() directly
cleanup image_grid_t' interface: should inline it all, maybe don't assume rgba color space
warp utility: the rotation transformation does not look right


⚠ Bofrost.nl has degraded performance

In d03d3ad, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1204 ms

Resolved: Bofrost.nl performance has improved in af35ddf.


Incorrect aspect ratio after going to landscape mode then back to portrait

Nexus 7 5.0 LPX13D
App starts up fine, after turning to landscape it recreates the activity ok, after turning back to portrait the sensor orientation does not match display orientation and swappedDimensions is true. The result is distorted/skewed preview display.

Is this possibly a repeat of Issue #9

This sample has been migrated to a new location where we can accept Pull Requests (check README for more information).
As recommended by GitHub, we are closing all issues and pull requests now that this older repo will be archived.
If you still see this issue in the updated repo, please reopen the issue/PR there. Thank you!


As a project coordinator, I want to see a summary of my answers before submitting a project revision, so that I can review the changes

Description:
Before submitting a project revision, best practices recommended to show a list of changes being applied to the new/edited project. An example can be found here.
For this iteration of the page, we only show the contents of the form_change records for the project_revision.
Rendering of the differences since the previous revisions (#397) and rendering of errors (#396) will be handled in separate user stories.
Rendering of the form data in a read-only version can be done via a custom react-jsonschema-form theme, which would render a <dl> instead of a <form>, <dt> instead of <label>, and a <dd> instead of an <input>.
Acceptance Criteria:
Given that I filled the project overview, project managers, and/or project contacts forms
When I visit the  /cif/project-revision/<id> page
Then I see the values I entered in the page
Given that I did not add any project manager or contact
When I visit the  /cif/project-revision/<id> page
Then a message indicates that the project manager or contacts were not added.
Development Checklist:

[ ] A custom react-jsonschema-form theme is used to display the form data
[ ] Meets the DOD

Design:

Personas:
Operations Team

Hey team! Please add your planning poker estimate with ZenHub @BCerki @dleard @gurjmatharu @pbastia

Please add your planning poker estimate with ZenHub @mikevespi

@suhafa, @matthieu-foucault, what information do you want shown when the project contact or manager has been added?

We can start with:

For managers, something like **<manager label>** <full name>
For contacts, **Primary Contact** <full name> and then a list for the secondary contacts

@matthieu-foucault, should I match the wireframe exactly or include all the all project information?

Thank you @BCerki ! Tested in dev by: Updating an existing projecting (updated project name, project summary, project status, Ops team secondary project manager. Worked as expected.


Compiler ERROR using @types/gapi -> @types/gapi/index.d.ts (243,23): ',' expected.

TypeScript Version: 2.3.4
Code
/**
* HttpRequest supports promises.
* See Google API Client JavaScript Using Promises https://developers.google.com/api-client-library/javascript/features/promises
*/
class HttpRequestPromise {
// Taken and adapted from https://github.com/Microsoft/TypeScript/blob/v2.3.1/lib/lib.es5.d.ts#L1343
then<TResult1 = T, TResult2 = never>(
onfulfilled?: ((response: HttpRequestFulfilled) => TResult1 | PromiseLike) | undefined | null,
onrejected?: ((reason: HttpRequestRejected) => TResult2 | PromiseLike) | undefined | null,
opt_context?: any
): Promise<TResult1 | TResult2>;
}
// A *self-contained* demonstration of the problem follows...

Expected behavior:
No errors.
Actual behavior:
ERROR in<EMAIL_ADDRESS>(243,23): ',' expected.

This isn't a self-contained repro of the issue so we wont be able to help with the issue until that's available.

@dpasquali did you find a solution for this issue? I'm also facing the same error.
I'm trying to deploy my angular 2 app on Ubuntu 16.4 and facing this error when running ng serve

same!

+1

+1

I fix this error , only change in package.json line "typescript": "~2.3.1"

cool thanks, Ill try it out.
On Tue, Aug 1, 2017 at 9:12 AM, Gabriel Rojas<EMAIL_ADDRESS>wrote:

I fix this error , only change in package.json line "typescript": "~2.3.1"
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/TypeScript/issues/16618#issuecomment-319381711,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASjgHBfAzQxwgQSDVKOQNb2nvgss70Vaks5sTzI-gaJpZM4N-cMV
.

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.

Hi,
I am still getting this error. The line number has changed from 243 to 267 .
It occurs at the same line of code. Can anybody help?

class HttpRequestPromise<T> {
        // Taken and adapted from https://github.com/Microsoft/TypeScript/blob/v2.3.1/lib/lib.es5.d.ts#L1343
        then<TResult1 = T, TResult2 = never>(
            onfulfilled?: ((response: HttpRequestFulfilled<T>) => TResult1 | PromiseLike<TResult1>) | undefined | null,
            onrejected?: ((reason: HttpRequestRejected) => TResult2 | PromiseLike<TResult2>) | undefined | null,
            opt_context?: any
        ): Promise<TResult1 | TResult2>;
    }

I am unable to reproduce this locally. can you please share a self contained reproduction of the issue.


Fix redundant entries in facet provider chain

I believe that this was intended to be outside the loop in the first place already.
Ping @immortius for a quick review.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/273/
Hooray Jenkins reported success with all tests good!

Seems likely.


Specification: Add better alt-text

I added more accessible alt text to the sample badges in the SPECIFICATION file, so it is more accessible to users who cannot see the images.

Messages

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

:book:
:sparkles: Thanks for your contribution to Shields, @ajs256!

  Generated by :no_entry_sign: dangerJS against 1bf9a1a6213589629f4af832db39e161200c5559

This may sound a little stupid, but I never realised that this was the way to add alt text to an image with markdown. Thanks for helping me join the dots! 😃


It's not working

https://github.com/FlyTechVideos/evil-clippy/assets/79092746/0b160eb5-7a1f-497b-be29-e9e2f3e0c193

Can you try pressing Control + , ?

It's not doing anything.

I also noticed that background processes spawn after opening but it still won't react.
https://github.com/FlyTechVideos/evil-clippy/assets/79092746/e4e03735-df44-40cc-9dd6-9ed3510799b2

Another test and it didn't even spawn a background process but this time I only opened it once.
https://github.com/FlyTechVideos/evil-clippy/assets/79092746/adac71fa-ac07-47f2-b73f-26ff2708ece5
After opening it again on the same machine it spawned a background process but there was no reaction.

Okay, this is weird, and I have never encountered this on any machine I tested with. Can you check event logs?

This would appear every time I open this application

Maybe WDAC?

@KwiatekMiki Sounds like a problem on your machine. Maybe this helps https://stackoverflow.com/q/64669672/3673616

Can confirm on Windows 10 22H2.

closing because i dont have time to test this


CUDA_VISIBLE_DEVICES isn't being respected / hostfile doesn't quite work for one node

I'm trying to experiment with DS/1gpu and it's not respecting CUDA_VISIBLE_DEVICES
I run the script as:
CUDA_VISIBLE_DEVICES=1 deepspeed --num_gpus=1 ./finetune_trainer.py ...

but it runs on GPU 0 ignoring CUDA_VISIBLE_DEVICES=1
Then I tried to use deepspeed launcher flags as explained here: https://www.deepspeed.ai/getting-started/#resource-configuration-multi-node and encountered multiple issues there:

I think the --hostfile cl arg in the example are in the wrong place, shouldn't they be right after deepspeed and not in the client's args? that is instead of:

deepspeed <client_entry.py> <client args> \
  --deepspeed --deepspeed_config ds_config.json --hostfile=myhostfile

deepspeed  --hostfile=myhostfile <client_entry.py> <client args> \
  --deepspeed --deepspeed_config ds_config.json

This is a launcher arg and not client arg.

it can't handle hostfile with 1 entry:

$ cat hostfile
worker-1 slots=2

$ deepspeed --hostfile hostfile  ./finetune_trainer.py ...
Traceback (most recent call last):
  File "/home/stas/anaconda3/envs/main-38/bin/deepspeed", line 7, in <module>
    exec(compile(f.read(), __file__, 'exec'))
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/bin/deepspeed", line 6, in <module>
    main()
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/deepspeed/launcher/runner.py", line 259, in main
    resource_pool = fetch_hostfile(args.hostfile)
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/deepspeed/launcher/runner.py", line 133, in fetch_hostfile
    raise err
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/deepspeed/launcher/runner.py", line 127, in fetch_hostfile
    hostname, slots = line.split()
ValueError: not enough values to unpack (expected 2, got 0)

it can't handle exclusion or inclusions w/o the hostfile (misleading docs)
Copy-n-pasting from docs - very last code example:

$ deepspeed --exclude="worker-1:0" ./finetune_trainer.py
Traceback (most recent call last):
  File "/home/stas/anaconda3/envs/main-38/bin/deepspeed", line 7, in <module>
    exec(compile(f.read(), __file__, 'exec'))
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/bin/deepspeed", line 6, in <module>
    main()
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/deepspeed/launcher/runner.py", line 272, in main
    active_resources = parse_inclusion_exclusion(resource_pool,
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/deepspeed/launcher/runner.py", line 240, in parse_inclusion_exclusion
    return parse_resource_filter(active_resources,
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/deepspeed/launcher/runner.py", line 187, in parse_resource_filter
    raise ValueError("Hostname '{}' not found in hostfile".format(hostname))
ValueError: Hostname 'worker-1' not found in hostfile

I think the docs are wrong/misleading - they suggest:

You can instead include or exclude specific resources using the --include and --exclude flags. For example, to use all available resources except GPU 0 on node worker-2 and GPUs 0 and 1 on worker-3:

but they don't specify that the hostfile is actually needed.
and the error message is misleading since what hostfile is it talking about? I haven't passed it any hostfiles in this experiment and if it found it in the current dir, that hostfile does have worker-1 in it - see cat hostfile earlier. So it should not just say "in hostfile" but in /path/to/hostfile
I think in this particular situation it should say: "hostfile hasn't been provided and it's required"

this is not the right solution since it tries to ssh to worker-1

subprocess.CalledProcessError: Command '['ssh worker-1 hostname -I']' returned non-zero exit status 255.

So how does one configure deepspeed to use a specific GPU on a single node?
Thank you!

Thanks for reporting this @stas00. There are a few different things going on here, let me try and address all of them here (if I miss one please let me know haha).
If you do not provide the deepspeed launcher with a hostfile (via -H/--hostfile) it will only launch processes within that local node. We will try to discover all the available GPUs on the box via torch.cuda.device_count(), see here for more details on this logic. Going forward the local node would be referred to as localhost.
The deepspeed launcher was primarily written to simplify multi-node training in interactive training environments. It supports arbitrary inclusion/exclusion of gpus/nodes. For example, I may want to exclude just the 3rd gpu on node 5 (maybe it has ECC errors) out of a total of 128 gpus and 32 nodes. This would be achieved via deepspeed --exclude worker-5:3 train.py.
In order to support this arbitrary inclusion/exclusion our launcher sets the appropriate CUDA_VISIBLE_DEVICES at process launch time on each node. This means that if the user sets their own CUDA_VISIBLE_DEVICES on the launching node it's not clear if they want to set this value on the local node or all nodes. We should update our docs to make this more clear though.
If you wanted to do something like CUDA_VISIBLE_DEVICES=1 deepspeed --num_gpus=1 ./finetune_trainer.py ... I would recommend running this as deepspeed --include localhost:1 ./finetune_trainer.py ....
Now if you wanted to use a hostfile to define your node list (even just 1 node) you can do that like you have. However, after seeing your ValueError stack trace I think you may have a trailing new-line at the end of the file. It seems our code was not tested with this case and it causes it to crash. I've submitted a PR to handle this case gracefully (see #669).
I think maybe one of the key missing pieces in our doc is our decision to reference the local node as localhost if no hostfile is given. So in the case of deepspeed --exclude="worker-1:0" ./finetune_trainer.py if you added your above hostfile I think it should work the way you want.

Thanks for reporting this @stas00. There are a few different things going on here, let me try and address all of them here (if I miss one please let me know haha).
If you do not provide the deepspeed launcher with a hostfile (via -H/--hostfile) it will only launch processes within that local node. We will try to discover all the available GPUs on the box via torch.cuda.device_count(), see here for more details on this logic. Going forward the local node would be referred to as localhost.
The deepspeed launcher was primarily written to simplify multi-node training in interactive training environments. It supports arbitrary inclusion/exclusion of gpus/nodes. For example, I may want to exclude just the 3rd gpu on node 5 (maybe it has ECC errors) out of a total of 128 gpus and 32 nodes. This would be achieved via deepspeed --exclude worker-5:3 train.py.
In order to support this arbitrary inclusion/exclusion our launcher sets the appropriate CUDA_VISIBLE_DEVICES at process launch time on each node. This means that if the user sets their own CUDA_VISIBLE_DEVICES on the launching node it's not clear if they want to set this value on the local node or all nodes. We should update our docs to make this more clear though.
If you wanted to do something like CUDA_VISIBLE_DEVICES=1 deepspeed --num_gpus=1 ./finetune_trainer.py ... I would recommend running this as deepspeed --include localhost:1 ./finetune_trainer.py ....
Now if you wanted to use a hostfile to define your node list (even just 1 node) you can do that like you have. However, after seeing your ValueError stack trace I think you may have a trailing new-line at the end of the file. It seems our code was not tested with this case and it causes it to crash. I've submitted a PR to handle this case gracefully (see #669).
I think maybe one of the key missing pieces in our doc is our decision to reference the local node as localhost if no hostfile is given. So in the case of deepspeed --exclude="worker-1:0" ./finetune_trainer.py if you added your above hostfile I think it should work the way you want.

As I don't have access to any clusters as of yet, I'm happy to just focus on the direct necessity of being able to specify which gpu to run on.

I would recommend running this as deepspeed --include localhost:1 ./finetune_trainer.py ....

Yes, that worked! Awesome!
Could we please document that or I could make a PR to add it to the launcher doc if it will save your time.

BTW, I tried first:
CUDA_VISIBLE_DEVICES=1  deepspeed --include localhost:1 ./finetune_trainer.py ...

as I had it already in the script and it crashed with:
Traceback (most recent call last):
  File "/home/stas/anaconda3/envs/main-38/bin/deepspeed", line 7, in <module>
    exec(compile(f.read(), __file__, 'exec'))
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/bin/deepspeed", line 6, in <module>
    main()
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/deepspeed/launcher/runner.py", line 272, in main
    active_resources = parse_inclusion_exclusion(resource_pool,
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/deepspeed/launcher/runner.py", line 240, in parse_inclusion_exclusion
    return parse_resource_filter(active_resources,
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/deepspeed/launcher/runner.py", line 190, in parse_resource_filter
    raise ValueError("No slot '{}' specified on host '{}'".format(
ValueError: No slot '1' specified on host 'localhost'

So ideally the launcher should detect such situation and tell the user to not set CUDA_VISIBLE_DEVICES.
I also tried to add a hostfile with localhost slots=2 and it tries to ssh to it.
I'd say documenting:
deepspeed --include localhost:1

as a way to run a specific single GPU on a local host is all that is needed.

I think you may have a trailing new-line at the end of the file

You're spot on! I used nano and it can't help but leave extraneous new lines.  I fixed that and it worked, but your PR is definitely a goodness. Not really needing at the moment but I'd add skipping commented out lines too.

let me try and address all of them here (if I miss one please let me know haha).

And as I mentioned in OP item 1. I think the --hostfile cl arg in the documentation example is in the wrong place

As I don't have access to any clusters as of yet, I'm happy to just focus on the direct necessity of being able to specify which gpu to run on.

I would recommend running this as deepspeed --include localhost:1 ./finetune_trainer.py ....

Yes, that worked! Awesome!
Could we please document that or I could make a PR to add it to the launcher doc if it will save your time.

BTW, I tried first:
CUDA_VISIBLE_DEVICES=1  deepspeed --include localhost:1 ./finetune_trainer.py ...

as I had it already in the script and it crashed with:
Traceback (most recent call last):
  File "/home/stas/anaconda3/envs/main-38/bin/deepspeed", line 7, in <module>
    exec(compile(f.read(), __file__, 'exec'))
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/bin/deepspeed", line 6, in <module>
    main()
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/deepspeed/launcher/runner.py", line 272, in main
    active_resources = parse_inclusion_exclusion(resource_pool,
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/deepspeed/launcher/runner.py", line 240, in parse_inclusion_exclusion
    return parse_resource_filter(active_resources,
  File "/mnt/nvme1/code/github/00optimize/DeepSpeed/deepspeed/launcher/runner.py", line 190, in parse_resource_filter
    raise ValueError("No slot '{}' specified on host '{}'".format(
ValueError: No slot '1' specified on host 'localhost'

So ideally the launcher should detect such situation and tell the user to not set CUDA_VISIBLE_DEVICES.
I also tried to add a hostfile with localhost slots=2 and it tries to ssh to it.
I'd say documenting:
deepspeed --include localhost:1

as a way to run a specific single GPU on a local host is all that is needed.

I think you may have a trailing new-line at the end of the file

You're spot on! I used nano and it can't help but leave extraneous new lines.  I fixed that and it worked, but your PR is definitely a goodness. Not really needing at the moment but I'd add skipping commented out lines too.

let me try and address all of them here (if I miss one please let me know haha).

And as I mentioned in OP item 1. I think the --hostfile cl arg in the documentation example is in the wrong place

Thanks. --include local:3 can set CUDA_VISIBLE_DEVICES=3 properly. However, the engine returned by deepspeed.initialize is on the wrong device.
Here is my code:
def debug():
    parser = argparse.ArgumentParser()
    parser.add_argument("--local_rank", default=0, type=int,
                        help="local_rank for distributed training on gpus")
    parser = deepspeed.add_config_arguments(parser)
    args = parser.parse_args()
    os.environ['MASTER_ADDR'] = 'localhost'  #
    os.environ['MASTER_PORT'] = '12345'  #
    os.environ['CUDA_VISIBLE_DEVICES'] = '0,1,2,3'
    args.local_rank = int(os.environ['LOCAL_RANK'])

    model = torch.nn.Linear(10,10)
    engine, _, _, _ = deepspeed.initialize(args=args, model=model, model_parameters=model.parameters())
    print("Engine is on device: ", next(engine.parameters()).device)

And I launch the code above with deepspeed --include="localhost:3" train.py  --deepspeed  --deepspeed_config config.json
I'm willing to run the model on device 3, but the engine is on device 0.

@skpig, if I may recommend opening a new Issue - it'd help with tracking and making sure your bug report doesn't fall between the cracks - as this Issue has been closed.

@stas00 Thank you for your advice. I have already opened a new issue #1761.

I fixed #4993 of Autotune hostfile not found bug in PR #4996, can this help you?


--pdb behavior

I think:

ptw --pdb -- [pytest args] waits for pdb to exit before re-running the tests
ptw -- --pdb restarts the test on any change, even if you're in the middle of debugging

Is that correct?
I actually find it v helpful - the second is useful if you always want a debugger ready to go with the latest as soon as you need one. But not sure that's consistent with https://github.com/joeyespo/pytest-watch/pull/64?
If so, we could make that explicit - I only discovered by accident

This seems to have reverted to the first behavior in 4.2.0, which is a shame. Is there any way to get the second?

Would you take a PR reverting to the old behavior, with the above added as instructions?
That way people can choose either option - if pdb is a ptw arg, then it'll wait on changes; if pdb is a pytest arg, it'll restart on changes as it generally does


Issue: Feature Request: SRTLA Support

Issue: Feature Request: SRTLA Support
Support the SRTLA Protocol, SRTLA is like SRT but with Link Aggregation (LA).. so you can use multiple connections at the source, split the feed then have the server put them all together again into a single SRT feed, it is used with the BELABOX software, IRL Pro App for Android and Moblin App for iOS. Reference Links: BELABOX / SRTLA on GitHub, IRL PRO, MOBLIN.

FFS, I give up.


Added address-mocks in README

Oh no, I didn't know there was a generator. I did it from scratch.

Good to know though! 👍


Add warmup for logits processors

What does this PR do?
Add warmup for logits processors. Do not slice input_ids to ensure static shapes.

@regisss please review


Chore ab checking user role for the menu manager

manually merged this branch in as unable to resolve conflicts in pbproject files. manually moved anas work into master


Turbolinks: Object has no method 'select2'

When using select2-rails with turbolinks, I see an error trying to use .select2() after a page is loaded with turbolinks (i.e., the first page load works fine, but the error always happens after clicking a link that causes the page to be loaded via turbolinks). The error is:
Object [object Object] has no method 'select2'

I've found that the following piece of code being executed on page:load prevents this error:
window.Select2 = undefined;

By unsetting the Select2 global, the select2 js constructs the select2() function again, preventing the error.

I moved my <script> to the <head> and that prevented the error but select2 still only displays when the page is visited from the address bar. It fails when addressed from a link till the page is refreshed or till I manually add in $('select').select2(); in the console

woo!! @rylwin this worked for me too!! thanks a lot
but what about all the benefits we were suppose to get by having the javascript actually being included at the end, faster pageload. I am loosing on them certainly. Is this a safe bet then?

@sanjusoftware It's a matter of rendering time. With JS in the head it delays the page rendering till all the scripts are loaded. Having the scripts at the head doesn't break your code, it just reduces your performance. A common and good example to explain this is a simple
<script>alert("hello");</script>
in a page with contents. Try loading in <head> and then try right before </body>
In my opinion, it is left on what you're willing to sacrifice. First load time speed over rest of web app survey (without turbolinks and script in head), or a slightly site-wide performance by not using turbolinks at all or moving to Express/Node for complete SPA feel.


PAYMENT AND REGISTRATION PAGE

Please take care of commit message standards

@babitarit Please change your PR titile.

Please fix this.

@Shurtu-gal after doing => HeroText has been changed to HeroText1 still deploy error exist

@Shurtu-gal after doing => HeroText has been changed to HeroText1 still deploy error exist

@babitarit I believe it is working.

closing as done


EmailAddress validator deprecations

Deprecates all option setters and getters
See #324

If the method setMessage also remains in the new version, then: 👍🏻

Once I've refactored all the remaining validators, I'll work on AbstractValidator, at which point this might change, but I'll deal with that when I get there.


python3.pkgs.scikit-optimize: mark broken

Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Build Status for python310Packages.scikit-optimize.x86_64-linux on master
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-27 - https://hydra.nixos.org/build/225708087

Last Builds:
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-18 - https://hydra.nixos.org/build/224631658
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-13 - https://hydra.nixos.org/build/224117774
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-06 - https://hydra.nixos.org/build/223074780
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-31 - https://hydra.nixos.org/build/222320223
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-19 - https://hydra.nixos.org/build/220620938
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-14 - https://hydra.nixos.org/build/220022972
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-10 - https://hydra.nixos.org/build/219150751
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-01 - https://hydra.nixos.org/build/218202952
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-04-27 - https://hydra.nixos.org/build/217554898
Build Status for python310Packages.scikit-optimize.aarch64-linux on master
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-27 - https://hydra.nixos.org/build/225752338

Last Builds:
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-18 - https://hydra.nixos.org/build/224452062
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-13 - https://hydra.nixos.org/build/224119250
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-06 - https://hydra.nixos.org/build/223087062
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-31 - https://hydra.nixos.org/build/222254828
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-19 - https://hydra.nixos.org/build/220619732
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-14 - https://hydra.nixos.org/build/219964458
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-10 - https://hydra.nixos.org/build/219099143
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-01 - https://hydra.nixos.org/build/218093285
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-04-27 - https://hydra.nixos.org/build/217462832
Build Status for python310Packages.scikit-optimize.x86_64-darwin on master
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-27 - https://hydra.nixos.org/build/225691794

Last Builds:
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-18 - https://hydra.nixos.org/build/224524904
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-13 - https://hydra.nixos.org/build/224124565
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-06 - https://hydra.nixos.org/build/223052671
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-31 - https://hydra.nixos.org/build/222383932
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-14 - https://hydra.nixos.org/build/219937236
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-10 - https://hydra.nixos.org/build/218995101
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-01 - https://hydra.nixos.org/build/218136147
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-04-27 - https://hydra.nixos.org/build/217449161
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-04-17 - https://hydra.nixos.org/build/215670739
Build Status for python310Packages.scikit-optimize.aarch64-darwin on master
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-27 - https://hydra.nixos.org/build/225707242

Last Builds:
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-18 - https://hydra.nixos.org/build/224625876
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-13 - https://hydra.nixos.org/build/224126786
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-06-06 - https://hydra.nixos.org/build/223083848
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-31 - https://hydra.nixos.org/build/222403572
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-14 - https://hydra.nixos.org/build/219853311
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-10 - https://hydra.nixos.org/build/219170066
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-05-01 - https://hydra.nixos.org/build/218046597
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-04-27 - https://hydra.nixos.org/build/217499709
✖ (Failed) python3.10-scikit-optimize-0.9.0 from 2023-04-17 - https://hydra.nixos.org/build/215578664

@ofborg eval


Update how-to-create-component-pipeline-python.md

Change git cloning to latest branch

@likebupt

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

PR review team emailed author

#sign-off


BUG: horizon client: error decoding horizon.Problem: EOF

To reproduce:

Create a payment that leads to an underfunded error. E.g., pay 100000 out of a new account.
Or try to submit this transaction (which does the same thing) with SubmitTransaction(): AAAAACA0ze5msDmFd+tg+ech00eGKehD3QmQLbvwNd9C7ryeAAAAZAB7H6UAAAAKAAAAAAAAAAAAAAABAAAAAAAAAAEAAAAATTWqHZvX3eEjb6KQWHyVryaGQFAmKW9gxN6vhdKyaNIAAAAAAAAA6NSlEAAAAAAAAAAAAULuvJ4AAABAlNmKQQzee4Vxvcfq8vgMYLh0lt1yBkacAitpmQqiEhkMT12SMhRN0NZQJPy9wd9nuQCib6m+6bPfyhA18Fq9Cg==

Sending 100000 from SDFQ7K4VZMRMFQP7VF6LBHHW7YWSODNW7VMPBJWVL2P4PAPSSUW2YBCG to GBGTLKQ5TPL53YJDN6RJAWD4SWXSNBSAKATCS33AYTPK7BOSWJUNFBHG
Payment: {false {<nil> {OperationTypeCreateAccount <nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil>}} {{PublicKeyTypePublicKeyTypeEd25519 0xc42022c1c0} native<PHONE_NUMBER>000} {native 0 {PublicKeyTypePublicKeyTypeEd25519 <nil>} native 0 []} <nil>}
Tx: &{0xc4201641c0 Test SDF Network ; September 2015 100}
submitting tx base64: AAAAACA0ze5msDmFd+tg+ech00eGKehD3QmQLbvwNd9C7ryeAAAAZAB7H6UAAAAJAAAAAAAAAAAAAAABAAAAAAAAAAEAAAAATTWqHZvX3eEjb6KQWHyVryaGQFAmKW9gxN6vhdKyaNIAAAAAAAAA6NSlEAAAAAAAAAAAAULuvJ4AAABAJKBI2Tkqiw4mQ6wtzo8S6yQX7k0lF6tytTvjC7AHqQXnf0xX/6UNgfHEOUzi5PZSiLopchmyGmdSdEienWu3BQ==
error decoding horizon.Problem: EOF
{{{ false}}  0   }
2018/03/23 20:08:30 error decoding horizon.Problem: EOF
exit status 1

Looks like this is an intermittent problem on the horizon testnet.
It's failing in the lab too (but occasionally.)

Closing because this isn't a client issue.


Option to enable column index based mapping for Parquet

Fixes https://github.com/facebookincubator/velox/issues/10388

@yingsu00

LGTM, @yingsu00 you can add read-to-merge if you are also good with this change

@agrawalreetika Can you please rebase this PR

@agrawalreetika just a reminder that the dependent PR is merged.

@Yuhta @yingsu00 I have rebased the PR on the latest but it looks like Ubuntu debug with resolve_dependency is still showing failure, I checked some of the recent PRs, and it seems the same case over there as well.
I am unsure about this failure here, do you have any suggestions for it?

@Yuhta @yingsu00 I have rebased the PR on the latest but it looks like Ubuntu debug with resolve_dependency is still showing failure, I checked some of the recent PRs, and it seems the same case over there as well.
I am unsure about this failure here, do you have any suggestions for it?

Hi Reetika, can you please rebase? It seems my PRs are good today.

Hi @yingsu00 & @Yuhta, Can we merge this PR now?


feat: Mock SMS

Update go-sms-sender to v0.3.0.
Fix: avoid page crash if not found provider info.

Signed-off-by: 疯魔慕薇<EMAIL_ADDRESS>

#1002

@hsluoyz Review pls, thx.


Signal parameter is missing in apicast executable (e.g. -s stop)

Since v3.2.0 -s parameter is missing, so if starting APIcast in daemon mode, it can't be stopped using bin/apicast command (it used to be possible with -s stop).
As a workaround, the corresponding signal (SIGHUP for restart / SIGQUIT for stop) can be send to the corresponding nginx master process.
NGINX docs for process control: http://nginx.org/en/docs/control.html

This also kind of depends on https://github.com/3scale/apicast/issues/772, because without it, you need to figure out the pid on your own.


Can't update to the version 1.0.4

Hello,
I got stuck with updating the package to the latest version.

On version 1.0.3 there is an error

error: property 'pageNumber' not found on object of type 'FlutterFullPdfViewerPlugin *'; did you mean to access instance variable 'pageNumber'?
        return self.pageNumber;

The version 1.0.4 is not published:

Because the app depends on flutter_full_pdf_viewer ^1.0.4 which doesn’t match any versions, version solving failed.
pub get failed (1)

If you go to the package page you will see it still on v1.0.3 https://pub.dartlang.org/packages/flutter_full_pdf_viewer
Not sure how long it takes for it to update

@l-k22  thank you for the reply, but don't you know why it shows error with pageNumber if use version 1.0.3?

@l-k22 thank you for the reply, but don't you know why it shows error with pageNumber if use version 1.0.3?

There were some changes made by another programmer but their work was not checked before merge. https://github.com/albo1337/flutter_full_pdf_viewer/issues/16#issuecomment-469264309

@l-k22 got it, thanks, will wait for the last release..

Has the update work for you guys?

@albo1337  1.0.3 no, we are waiting for 1.0.4, for now, we have downgraded to 1.0.2

Note: you can also do this while 1.0.4 arrives.
flutter_full_pdf_viewer:
git:
url: https://github.com/albo1337/flutter_full_pdf_viewer.git

@ezmegy thank you) it works)

Great! ;)
Don't forget to check from time to time though, you might want to switch back to the "officially" published dartlang version at some stage. (E.g. with 1.0.4 as mentioned)

Please check again. There went something wrong the first time. WTF! Sorry guys really!


Pressing enter in the command palette when focused on a notebook add new cell button triggers new cell

Steps to Reproduce:

Place focus on add new cell buttons
Open command palette and hit enter on any item
:bug: New cell is added

This applies to all toolbars, and all vs code components.
I guess it shares the same root cause as https://github.com/microsoft/vscode/issues/110427#issuecomment-726994727


Update HTTP/2 fallback warning

Suggested by @bfritz in #1106.

Codecov Report

Merging #1112 into release-0.15.x will increase coverage by 0.11%.
The diff coverage is 100%.

@@                Coverage Diff                 @@
##           release-0.15.x    #1112      +/-   ##
==================================================
+ Coverage           68.87%   68.99%   +0.11%
==================================================
  Files                 211      211
  Lines                4428     4428
  Branches              444      444
==================================================
+ Hits                 3050     3055       +5
+ Misses               1378     1373       -5

Impacted Files
Coverage Δ

...in/scala/org/http4s/server/blaze/BlazeServer.scala
37.33% <100%> (ø)
:arrow_up:

core/src/main/scala/org/http4s/Uri.scala
85.45% <0%> (+1.81%)
:arrow_up:

.../scala/org/http4s/testing/ArbitraryInstances.scala
82.35% <0%> (+23.52%)
:arrow_up:

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 656fc31...a0f7d67. Read the comment docs.


fix: Allow warn logging for requests which are failures, ensure debug…

… logging level for all other requests

Issue Number: DEV-1255
Pull Request Checklist
Basic Requirements
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix: represents bug fixes
[ ] Refactor: represents production code refactoring
[ ] Feature: represents a new feature
[ ] Documentation: documentation changes (no production code change)
[ ] Chore: maintenance tasks (no production code change)
[ ] Style: styles updates (no production code change)
[ ] Test: all about tests: adding, refactoring tests (no production code change)
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Does this PR change client-test-data?

[ ] Yes (don't forget to update the JS-LIB team about the change)
[x] No

Other information

One more thought: You might want to also warn, if the request takes more than e.g. 3 seconds. (We have some performance issues and it might be helpful to know what requests those are)

One more thought: You might want to also warn, if the request takes more than e.g. 3 seconds. (We have some performance issues and it might be helpful to know what requests those are)

Good idea, this might be interesting to know. I will leave it out for now and may add it in a follow up PR as I want to look into our monitoring first whether this is better/easier to be exposed as a metric.


What's the mean of levels and opacities?

I can not understand the effect of slides of levels and opacities? I think that the API is not clear about this part of content. Can anyone help me?

Hi,
I wanted to explain this by updating the docs on this, but let's start here first. A transfer function maps voxel values in the range [0, 1] to rgba (rgb+alpha) colors. In ipvolume, a volumetric cube is first normalized to the [0, 1] range, unless datamin, datamax is provided, where clipping is applied when the values are outside this range. The default transfer function exists of 3 gaussian bumps, where the location of the bumps are provided in level, the sigmas/widths by level_width, and the height/opacity by opacity. The first bump causes will result in red values, the 2nd in green, and the 3rd in blue. Note that this is the default transfer function, it should be possible (but haven't tested that for a while) to define your own transfer function.
Would really like to have an example reproducing for instance this
Does this help? I will keep this open until transfer functions are better documented.

Thanks for your help. I think I need to learn some details about the transfer functions.

it looks like the upperbound for opacity is hardcoded here. is there a way to modify this programmatically at present?
https://github.com/maartenbreddels/ipyvolume/blob/master/ipyvolume/transferfunction.py#L88

Hi Satrajit,
yes, I have to say that the transfer functions are something that needs more work, but I've added a max_opacity keyword to volshow(..) as you can see in the referenced commit. It would be possible btw to get a reference to this max opacity, but it's difficult to obtain, and this change makes more sense I think.
cheers,
Maarten

PS: Please raise a new issue next time :)

thanks. will do


Release new version sklearn-tranformer for Featuretools 1.0.0

Release new version (0.3.0?) that is compatible with Featuretools 1.0.0. This should be released before Featuretools, making sure to set the Featuretools version to >=1.0.0 in requirements.txt to prevent installation before featuretools is released.

Done


Questions

What is "size" in this context? is it that there are 10,000; rows/vectors with 64 bit values in each one? (each of the 10,000 has 64 0 or 1 values?)  I'm confused how you mention that it's suitable for 512 but the 512 value is not used here (Or I really don't understand C++)

	// ------------- Generation of Random Data ------------
	// obviously, this is not representative of real data;
	// it doesn't matter for brute-force matching
	// but the MIH methods will be much faster
	// on real data
	void *qvecs = malloc(64 * size), *tvecs = malloc(64 * size);
	srand(36);
	for (int i = 0; i < 64 * size; ++i) {
		reinterpret_cast<uint8_t*>(qvecs)[i] = static_cast<uint8_t>(rand());
		reinterpret_cast<uint8_t*>(tvecs)[i] = static_cast<uint8_t>(rand());
	}
	// --------------------------------

After matching, the m.matches contains an array of Match, how does that Match relate back to the tvecs ?

  std::cout << std::endl <<  m.matches[34].q  << std::endl; gives me the output of 242 (the 34 just a random number)
Warming up...
Testing...

242

Brute force K2NN found 1334 matches in 100.403 ms
Throughput: 0.995982 billion comparisons/second.

So what is that 242? is it an index so that like it would be tvecs[242] ?
So for example, if I loaded 2 sets of binary descriptors with 200 descriptors per set - it would have to scan 400 binary descriptors, 242 would mean its the 42nd descriptor of the 2nd set?

Hey,
So as the README says, "brute-force and a custom Multi-Index Hash Table accelerator system for matching 512-bit binary descriptors".
So each descriptor is 512 bits in length. This plays well with the rest of my faster-than-previous-state-of-the-art computer vision pipeline stuff, like LATCH/ULATCH/CLATCH/UCLATCH, that's why I'm focused on 512-bit at the moment.
size is the number of such descriptors.
512/8 = 64 bytes each, which is why the allocations are for 64 * size.
So after matching, you have a std::vector. The Match struct contains two integers: q, and t. These are the indices of the matches. For example, if you have a Match struct with q = 10 and t = 15, that means the 11th query descriptor has been found to match with the 16th training descriptor.
I should mention that the brute-forcer is mainly an easily verifiable reference solution. It's fast for CPU, but that's not saying much. CUDAK2NN achieves 54 billion (!!) comparison per second on a stock GTX 1080.
The main point of K2NN is actually the experiment with multi-index hashing. The jury is still out on whether that's worth it. My money says no given how insanely fast I was able to make CUDAK2NN. Sometimes you really can just steamroll time complexity with brute force. For very large datasets, perhaps the time complexity would come back to bite you and multi-index hashing might be worth it. I suspect that's particularly true for small (maybe 64-bit) descriptors.
Thanks!

Perfect!! Thanks!!


Insomnia is unable to sync in github or gitlab

{
"_type": "export",
"__export_format": 4,
"__export_date": "2021-09-23T04:39:16.139Z",
"__export_source": "insomnia.desktop.app:v2021.5.3",
"resources": []
}

I noticed the same behavior, I haven't had the time to debug it but it's on my bucket list for the next week.
I'm pretty sure it's something related to the recent version change of insomnia, but I have not confirmed it.

Hi! Thanks @PeterNgTr.
It is in process of releasing and the fix should be published in a couple of minutes.


Flutter Cloud_Firestore NotEquals support

In a September 17th update, it was was announced that Firestore now supports "Not Equal" queries.
-https://firebase.google.com/support/release-notes/js#version_7210_-_september_17_2020
The latest cloud_firestore Flutter plugin (0.14.1+3) doesn't look like it supports this yet, I wasn't able to spot its addition in the version log and the API calls aren't available. Is there any information on when this will be added?
Thanks!

Please find updates at https://github.com/FirebaseExtended/flutterfire/pull/3748


Col nested in card broken

Description
When adding a nested row col inside a card or card panel the card stays on top and the containing divs/content flows outside of the card
Repro Steps
See pen below
Screenshots / Codepen
https://codepen.io/anon/pen/Qgpzjw

Nope
Its perfectly normal

When you are using a shelf, you put the board first and after the books.

This is broken

and shouldn't be

Problem solved, You can close this issue 😄

Thanks, I'll give this a try later today.
FWIW, on an older version of materialize the way I was doing it previously worked just fine so something changed between then and 0.98.2.


What problem is being solved here? Place in README.md

You are doing good work on this keep pushing forward, this is an oscillator calibration that was done in an Application Note. You implemented it on your own microcontroller.

an2822-stm8s-and-stm8a-high-speed-internal-oscillator-calibration-stmicroelectronics.pdf