[Feature Request] Include more similarity measures such as cosine similarity

I absolutely love this API and I think it might be a good idea to include some other measures of similarity and let the user chose the desired one when comparing faces.

I would love to work on it as well :) if approved...


What is outside option?

"Pos {line: 0, ch: 42, sticky: "before", xRel: -86.53125, outside: true}"
When outside becomes true then the editor line becomes uneditable, how to prevent this?

posAtCoords adds this when the coordinates queried lie outside of the line's bounding rectangle.
What you mean by the line becoming uneditable isn't clear to me. You're going to have to provide some more details.

Got it. when outside: true the editor line does not focus but looks like that is expected. I fixed it but not encountering outside: true.

Looks like this is something else,
when the Pos {line: 0, ch: 6, sticky: "before", xRel: -33.9375, outside: true} I am not able to focus on the line with the cursor.

Is there any issue if we use 'focus()' and 'setCursor()' at the same time?

No, you can do that.

'Keyup' is working but Want to achieve the focus without 'Keyup'.

Refreshing after Focussing works.
this.editorInstance.focus();
this.editorInstance.refresh();


White space change

Also, some files remain with space after the values (like in comfig.cfg) there are spaces right after the first commands.

Are you sure this won't remove all spaces?
Like: net_maxpacketdrop 0 -> net_maxpacketdrop0?
And I'm talking about spaces, and not lines.
Like: net_maxpacketdrop(aspacehere)0(anotherspacehere), where (anotherspacehere) is unnecessary.

@mastercoms

https://github.com/mastercoms/mastercomfig/commit/4cf63f531c9aa9a86e59516ff315e1fa9ae13025


Add pagination for the workers controller

This is my proposal for the workers pagination #28.
I tried to create a system test for the pagination, but if I create more workers an SQLite exception is raised.
If you think it didn't add too much value I can delete it.
I hope you like my proposal and please if you have any feedback just go ahead!

Hey @pmareke, thanks a lot for working on this and sorry for the delay in reviewing, I've been working on other stuff but I'm finally back to this 😌
This looks good but I think you could re-use a lot more. In particular, Jobs::Page and Workers::Page are almost identical. Do you think you could generalise Jobs::Page instead to be over a generic collection and use it for both?

Hey @pmareke, thanks a lot for working on this and sorry for the delay in reviewing, I've been working on other stuff but I'm finally back to this 😌
This looks good but I think you could re-use a lot more. In particular, Jobs::Page and Workers::Page are almost identical. Do you think you could generalise Jobs::Page instead to be over a generic collection and use it for both? You could do something similar with the toolbar, could be shared for both.

Sure, thanks!

I'll create a new

Hi again @rosa, sorry for the delay but it was a busy week!

I created a new class called WorkersRelation with the minimum code possible and its tests.
I rename the JobsPage to be more generic and use it too with the Workers and Queues.
I have to add filter_param" {} in the index view of the Jobs and Workers to avoid some errors, but I'm not sure why this is necessary.

Hi again @rosa, sorry for the delay but it was a busy week!

Oh, of course, please don't apologise! Thanks for taking the time to work on this 🙏

I have to add filter_param: {} in the index view of the Jobs and Workers to avoid some errors, but I'm not sure why this is necessary.

Ahh, this seems to be because you renamed the helper jobs_filter_param to filter_param in the partial and that doesn't exist. Passing it as parameter works but in the index view of jobs, you'd want to pass the actual job filters rather than {}, or the job filters will break.

Hi @rosa sorry for the delay!
I fixed all the comments, so please let me know what do you think in order to fix something else if it's necessary!
Have a nice day!

Hey @pmareke sorry for the delay now from my side 😅  This is looking good! I think it's ready to go 🎉  Thanks a lot for all your work on this one 🙏

There's a test failing because it's using Server#workers, that no longer works. I think that might be the only thing pending (and the small thing about Ruby 3.0 that I commented separately on).

Thanks @rosa fixed the Ruby compatibility!

There's a test failing because it's using Server#workers, that no longer works. I think that might be the only thing pending (and the small thing about Ruby 3.0 that I commented separately on).

Sorry, which one?

def workers_relation
MissionControl::Jobs::WorkersRelation.new(queue_adapter: queue_adapter)
end

Fixed!

There's a test failing because it's using Server#workers, that no longer works. I think that might be the only thing pending (and the small thing about Ruby 3.0 that I commented separately on).

Fixed!!!

Hi @rosa I saw the pipeline broken so I fixed my code to pass the 5 failing tests.
It should be ok now, sorry for the back and forth.

Ooh, thanks a lot @pmareke, and so sorry for the delay! I was on-call last week and had to work on a bunch of unrelated stuff. I'm now finally back into this 😅

Ooh, thanks a lot @pmareke, and so sorry for the delay! I was on-call last week and had to work on a bunch of unrelated stuff. I'm now finally back into this 😅

Don't say sorry!!! You're helping me A LOT.
Thanks so much.


FIPS enable computers fail due to md5 use

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Red Hat Enterprise Linux Workstation release 7.7

Python 2.7.5 (default, Jun 11 2019, 14:33:56)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow as tf
>>> tf.version.GIT_VERSION
'v1.14.0-rc1-22-gaf24dc91b5'

Installed using virtualenv? pip? conda?: pipenv install tensorflow

tflearn fails to import due to tensorflows use of md5 on an fips enabled machine
Python 2.7.5 (default, Jun 11 2019, 14:33:56)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import tflearn
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File ".../lib/python2.7/site-packages/tflearn/__init__.py", line 4, in <module>
    from . import config
  File ".../lib/python2.7/site-packages/tflearn/config.py", line 5, in <module>
    from .variables import variable
  File ".../lib/python2.7/site-packages/tflearn/variables.py", line 7, in <module>
    from tensorflow.contrib.framework.python.ops import add_arg_scope as contrib_add_arg_scope
  File ".../lib/python2.7/site-packages/tensorflow/contrib/__init__.py", line 31, in <module>
    from tensorflow.contrib import cloud
  File ".../lib/python2.7/site-packages/tensorflow/contrib/cloud/__init__.py", line 28, in <module>
    from tensorflow.contrib.bigtable.python.ops.bigtable_api import BigtableClient
  File ".../lib/python2.7/site-packages/tensorflow/contrib/bigtable/__init__.py", line 29, in <module>
    from tensorflow.contrib.bigtable.python.ops.bigtable_api import BigtableClient
  File ".../lib/python2.7/site-packages/tensorflow/contrib/bigtable/python/ops/bigtable_api.py", line 44, in <module>
    resource_loader.get_path_to_datafile("_bigtable.so"))
  File ".../lib/python2.7/site-packages/tensorflow/contrib/util/loader.py", line 56, in load_op_library
    ret = load_library.load_op_library(path)
  File ".../lib/python2.7/site-packages/tensorflow/python/framework/load_library.py", line 73, in load_op_library
    module_name = hashlib.md5(wrappers).hexdigest()
ValueError: error:060800A3:digital envelope routines:EVP_DigestInit_ex:disabled for fips

replacing all md5 calls with sha1 calls should work?

I ran into this in load_library. Adding the optional argument used_for_security=False solved this for me.

Any movement on this?  I still get it importing the latest version of TF.

#31803 was an attempt at this but it required more work due to internal usages.
I'm currently working on that, should be done by the time TF 2.5 lands

I am confused as to what was done to fix this and why my issue was closed?
https://github.com/tensorflow/tensorflow/pull/31803/files
So instead of merging in my PR, you do the same thing (but in less places?).
Why couldn't this have been merged over a year ago if you were just going to do the same thing?

There are internal fixes in parallel with these ones that didn't get exposed.
Also, a year ago there were more files that needed change but they got replaced in the meanwhile.
There is one more public change to arrive, was delayed by a broken test.

Hi,
Can someone confirm that TF 2.5 has this fix? Reading the release note for 2.5, and I don't see FIPS mentioned.
Thanks.

I can confirm that with v2.5 I no longer see the FIPS errors whereas with 2.4.1 I do.
2.4.1 errors:
File "/data/users/jprosser/tf/venv/lib64/python3.6/site-packages/tensorflow/python/framework/load_library.py", line 67, in load_op_library
module_name = hashlib.md5(wrappers).hexdigest()
ValueError: error:060800A3:digital envelope routines:EVP_DigestInit_ex:disabled for fips


Refactored ContextVars

Added tests
Moved ctx_stack from ContextVars to Context and renamed to stack
Simplified implementation
Context and Timing can now be used as decorators
Updated documentation

Draft notes:
Related to #844 and I believe this fits under the "Conceptual Cleanups" umbrella.
But with recent changes it now also introduces a new feature in that Context and Timing can be used as decorators.
Tell me if I should have split this up. I totally see that the Timing stuff could have been put in a separate PR from the rest.

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/helpers.py                        9               8
------------------------------------------------------------
lines added in the tinygrad folder: 1

Can you see if you can implement #1321 as part of these changes?

I am happy to force-push an update that only includes the tests if that is the only part you want.
But I have some ideas that I put down into code that I think might be useful.
contextlib.ContextDecorator can be used to make a contextmanager be usable as a decorator too without any extra work.
So I put that into Context and Timing too!
I added some examples in the current documentation and also showed how in one instance adding Timing as a decorator removed one level of indentation in load_state_dict.
I know this is outside the scope of the original PR so tell me if I should have just put the tests here instead and done a separate PR.

I don't think there is a specific reason why the ContextVars are set like that, but yea .set() would probably be better/clearer.
On the second point, probably not, Context is pretty clear in what it does and something like Env makes it seem like an environment variable when it may not be.

Oh another thing u could look into is that looking up the value in the stack every time a context var is accessed is quite expensive, storing the value inside the var itself would make it a lot faster.

Great suggestion @dosier I have now locally developed what you suggested and it performs much better than what is on master.
tl;dr: Still working on it. it's faster now. here is a pretty picture

The reference comparisons are against
reference minimal
    class Derp():
        __slots__ = 'value'
        def __init__(self, value): self.value = value
        def __ge__(self, x): return self.value >= x
        def __bool__(self): return bool(self.value)
    DEBUG = Derp(0)

    [test('reference minimal solution') for test in [test_gt, test_bool]]

which unsurprisingly is equivalent to my new solution in speed and probably the best we can do in terms of a pure python solution for lookup?
reference int
DEBUG = 0

Which shows how fast the old DEBUG = getenv("DEBUG", 0) solution would be on lookups again just for reference.
This is the code right now but I still want to work on it as I really would like to not store the default_value in the tuple but instead inside the stack.
class Context(contextlib.ContextDecorator):
  stack: ClassVar[List[dict[str, int]]] = [{}]
  _vars: ClassVar[Dict[str, Tuple[ContextVar, int]]] = {}
  def __init__(self, **kwargs): self.kwargs = kwargs
  def __enter__(self):
    Context.stack.append(self.kwargs)
    for k, (o, _) in Context._vars.items(): o.value = self.kwargs.get(k, o.value)
  def __exit__(self, *args):
    Context.stack.pop()
    for k, (o, dv) in Context._vars.items(): o.value = Context.stack[-1].get(k, dv)

class ContextVar:
  __slots__ = "value"
  def __new__(cls, key, default_value):
    if key in Context._vars: return Context._vars[key][0]
    Context._vars[key] = (instance := super().__new__(cls), getenv(key, default_value))
    instance.value = Context.stack[-1].get(key, default_value)
    return instance
  def __call__(self, x): self.value = x
  def __bool__(self): return bool(self.value)
  def __ge__(self, x): return self.value >= x
  def __gt__(self, x): return self.value > x
  def __lt__(self, x): return self.value < x

That is much easier to solve when using ChainMap
class Context(contextlib.ContextDecorator):
  stack: ClassVar[ChainMap[str, int]] = ChainMap()
  _vars: ClassVar[dict[str, ContextVar]] = {}
  def __init__(self, **kwargs): self.kwargs = kwargs
  def __enter__(self):
      for k,v in self.kwargs.items(): Context._vars[k].value = v
      Context.stack.maps.insert(0, self.kwargs)
  def __exit__(self, *args):
      for k,v in Context.stack.maps.pop(0).items(): Context._vars[k].value = Context.stack.get(k, v)

as it will just handle arbritary nested contextmanagers without issue. Not that that really is important.
I also kindof like that in my chainmap solution here that the body of the exit method is just one line. Would like to do that in the proposed solution above too if it does not get too code golfy.
Also above I choose to keep the same behaviour as the original but I would propose to remove __call__ and not replace it with anything. We can now DEBUG.value = 6 directly and that will just work.
I will push my stuff once I have cleaned up a bit. Not today though but wanted to give an update.

Can you submit this as a minimal PR? Like that Timing change above shouldn't be needed, right? You can resubmit it after.

Looking much better! This ready to merge?

Is the name and location of the test file ok?
If it is I will remove a TODO comment and then I think it's ready.

I think just putting it at test/test_helpers.py should be fine, it shouldn't conflict with extras cuz that's in its own directory.


Support for Table Footers

I realize I could simply use HTML, but I'm curious if there has been any consideration for the support of table footers. Perhaps something like:
| Expense             | Bridgeport, Chicago | Denpasar, Bali      |
| :------------------ | :------------------ | :------------------ |
| Rent                | $650/mo.            | $216/mo.            |
| Utilities           | $100/mo.            | Included with rent  |
| Cable/Internet      | $60/mo.             | Included with rent  |
| Vehicle[^1]         | $405/mo.            | $55/mo.             |
| Gasoline            | $100/mo.            | $8/mo.              |
| Cellphone/LTE       | $90/mo.             | $15/mo.             |
| Drop-off laundering | $10 + tip per load  | $1.90 per load      |
| Cigarettes          | $12 per pack        | $1.80 per pack      |
| Regular coffee      | $1 per cup          | $0.45 per cup       |
| Water               | Free                | $1.50 per 12 liters |
| "Visa runs"         | N/A                 | $165 bi-monthly     |
| :------------------ | :------------------ | :------------------ |
|                     | $1,428.00           | $382.15             |

Hello,
Sorry but as you might have noticed, this project has pretty limited resources so adding new features is not a priority as this will increase the maintainance burden.
Thus, we are going to give this ticket a close. We might consider reopening it in the future if it makes sense.
Thank you very much for your proposal and understanding.


Romero et al. (2024) published in GBE

https://academic.oup.com/gbe/article/16/9/evae172/7748369?login=false

https://malariagen.github.io/vobs-updates/2024/09/03/romero.html


Value of $config.taskNameFormat Not Written in Colour for Scriptblocks

According to the sample psake-config.ps1, I can set $config.taskNameFormat to a string or a scriptblock in order to control the output of task headers. While setting to a string appears to work just fine, setting to a scriptblock does not.
Outputs in colour:
$config.taskNameFormat = "Executing {0}"

Does not output in colour:
$config.taskNameFormat = { param($taskName) "Executing $taskName at $(get-date)" }

The reason for this is easy to see in the psake.psm1 (line 89):
if ($currentContext.config.taskNameFormat -is [ScriptBlock]) {
    & $currentContext.config.taskNameFormat $taskName
} else {
    WriteColoredOutput ($currentContext.config.taskNameFormat -f $taskName) -foregroundcolor Cyan
}

It's plain to see that the result of $config.taskNameFormat is being evaluated and left to go to the pipeline where it is being rendered as a standard string when it is defined as a scriptblock, but it is being passed to WriteColoredOutput in all other cases. Should the scriptblock case also pass the result to WriteColoredOutput? If not, then we probably need a different variable for the scriptblock case.

I submitted a pull request (#190).

Thanks @damianh. Merged.


React: Render HTML Elements to the DOM Not Responding

I Have Been trying to Complete the Lesson on React: Render HTML Elements to the DOM and i am Correct but it is not Just Accepting it. what should i do
https://learn.freecodecamp.org/front-end-libraries/react/render-html-elements-to-the-dom/

@Pheonix73 , You can see the error in ur screenshot. It is ReactDOM not ReactDom

@Pheonix73 it should be ReactDOM.render(component, target) with DOM in capitals.
Tip - Ask these questions in the forum and if it is an issue, then post it here.

@sesn  and @Nirajn2311 thanks a lot, for your feedback it really helped and  noted.


Amendment to Supported Devices page in the Wiki

Sorry if this is not the right place...
The "Supported Devices" page in the Wiki includes Android phones under "devices using IRK". I don't think there is any user access to the IRK of an Android device. For practical purposes the only option is to set up an iBeacon - I imagine most Home Assistant users would do this in the companion app (or the HA Wear OS app for watches).
Is it possible to submit edits to the Wiki?

Howdy! Thanks for prodding me into action on this! 😀
There are definitely ways to get IRK from Android so the wiki isn't incorrect, but certainly incomplete. Quite a few users are using IRK with Androids, myself included.
I've updated the wiki with the methods I'm aware of, and I have plans to create an easier way that's more integrated with ESPHome / HA in the future.
The main method I prefer currently is to use https://github.com/fryefryefrye/Decoding-Random-Bluetooth-Address but it does require doing a one-off flash of an esp32 and connecting via serial to see the results.
FWIW I think the method of getting the iPhone IRK by digging around the insides of a macbook will also work with an Android that has been paired with it. But that doesn't help those of us without a macbook handy!

Is it possible to submit edits to the Wiki?

Huh. I had assumed it would be, but it appears there isn't a straightforward way. I guess that's why projects usually end up putting their docs either in the repo or in a separate repo. I expect I'll end up doing the same at some point :-/
I'll mark this as closed for now, but feel free to add further comments etc if you find new info or run into problems.

Hi,
is it also possible to get the irk from an android wear device, like the samsung galaxy watch 7? I did the enroll method from espresence for my phone. Unfortunately this doesn't work with wearos because espresense cannot be selected for connection

Well...
When I said "user access" I kind of meant methods that don't involve a soldering iron... ;)
I've used the iBeacon approach with both an Android phone and with Wear OS. Both work, but both have long "unknown" gaps, in spite of not being included in battery saving etc. To be honest, I've given up on the phone and now have a tag attached to it - Tile do one the size and shape of a credit card, which fits nicely into the case.


[SPARK-24235][SS] Implement continuous shuffle writer for single reader partition.

What changes were proposed in this pull request?
https://docs.google.com/document/d/1IL4kJoKrZWeyIhklKUJqsW-yEN7V7aL05MmM65AYOfE/edit
Implement continuous shuffle write RDD for a single reader partition. (I don't believe any implementation changes are actually required for multiple reader partitions, but this PR is already very large, so I want to exclude those for now to keep the size down.)
How was this patch tested?
new unit tests

Can one of the admins verify this patch?

Test build #91131 has started for PR 21428 at commit 63d38d8.

Test build #91132 has started for PR 21428 at commit f3ce675.

Test build #91131 has finished for PR 21428 at commit 63d38d8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #91132 has finished for PR 21428 at commit f3ce675.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

Test build #91135 has finished for PR 21428 at commit e0108d7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

@HeartSaVioR @arunmahadevan @xuanyuanking

addressed comments

Test build #91174 has started for PR 21428 at commit af1508c.

Test build #91278 has started for PR 21428 at commit 65837ac.

Test build #91278 has finished for PR 21428 at commit 65837ac.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Test build #91368 has started for PR 21428 at commit 629455b.

Can one of the admins verify this patch?

Test build #91745 has started for PR 21428 at commit 4bbdeae.

Test build #91745 has finished for PR 21428 at commit 4bbdeae.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #91748 has started for PR 21428 at commit e57531d.

Test build #91748 has finished for PR 21428 at commit e57531d.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #91742 has finished for PR 21428 at commit 59d6ff7.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Test build #91772 has started for PR 21428 at commit e57531d.

Test build #91772 has finished for PR 21428 at commit e57531d.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

LGTM pending tests

Test build #91781 has finished for PR 21428 at commit cff37c4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Thanks! Merging to master.


React-native 0.44.2 and react-native-fbsdk 0.6.0 troubles.

Hi Guys. I was working with RN 0.37.x and react-native-fbsdk 0.5.0.
It was neat but I upgraded my project to RN 0.44.2 recently and fbsdk 0.6.0 as well but it didn't work. I had to uninstall it and to install react-native-facebook-login. In android Studio console, I saw some errors:
Error:(3) Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Borderless.Colored'.
Error:(4) Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Colored'.
Error:(3) Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Borderless.Colored'.
Error:(4) Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Colored'.
I have been editing build.gradle according to others forums about this. But I could not solve this.
In the meantime, I am using RN Facebook Login but It is limited. FBSDK has a lot of advantages.

Hey, thanks for reporting this issue!
It looks like your description is missing some necessary information. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.
I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!


Public property has or is using name but cannot be named - intersection types

TypeScript Version:  2.8.3

Search Terms: exported variable but cannot be named
Code
animal.ts:
export interface Dog {
    type: "dog";
    ...
}
export interface Cat {
    type: "cat";
    ...
}
export type Animal = Dog | Cat;

otherFile.ts:
import { Animal, Cat, Dog } from "./animal"

export class MyClass {
    pulbic checkAnimal = (animal: Animal | undefined): void => {
        ...
    }
}

NOTE: if I use function syntax instead of arrow syntax, or if I remove | undefined, there is no error:
// This works fine:
public checkAnimal(animal: Animal | undefined): void {
}
// So does this:
public checkAnimal = (animal: Animal): void => {
}

Expected behavior: Behaviour should be the same whether function syntax or arrow syntax is used. Ideally no error.
Actual behavior:
ERROR in [...]/otherFile.ts
./otherFile.ts
[tsl] ERROR in [...]/otherFile.ts(170,5)
      TS4029: Public property 'checkAnimal' of exported class has or is using name 'Cat' from external module "[...]/animal" but cannot be named.

(Only when using arrow syntax. When using function syntax, there is no error. However in this situation I need to use arrow syntax to preserve this.)
Playground Link:
Related Issues: https://github.com/palantir/tslint/issues/3854

I can not get a repro for this issue locally. my guess is that Cat or Dog are not imported in the actual case.
c:\test\23679>type animal.ts
export interface Dog {
    type: "dog";
}
export interface Cat {
    type: "cat";
}
export type Animal = Dog | Cat;

c:\test\23679>type index.ts
import { Animal, Cat, Dog } from "./animal"

export class MyClass {
    public checkAnimal = (animal: Animal | undefined): void => {

    };
}

c:\test\23679>tsc --v
Version 2.9.0-dev.20180422

c:\test\23679>tsc --declaration

c:\test\23679>echo %ERRORLEVEL%
0

Regardless of the details of the repro, this seems to be a duplicate of https://github.com/Microsoft/TypeScript/issues/9944.  see https://github.com/Microsoft/TypeScript/issues/9944#issuecomment-244448079 for more context.
Also the fix here is to write an explicit type annoation. i.e.:
    public checkAnimal: (animal: Animal | undefined) => void = (animal: Animal | undefined): void => {

    };


IM go corrupt when exporting a bogey

The .IM file for a bogey corrupts when exported

(for IM editor this is as it worked earlier!)

Make sure you have the latest version of the exporter. If you're using the latest and the error still occurs, please send the .im and/or .blend file so I can take a look.


question: drachtman weinblatt sitarz syndrome

@galyea-gard
is there any additional info about this disease:
https://rarediseases.info.nih.gov/diseases/1913/drachtman-weinblatt-sitarz-syndrome
It isn't in OMIM record for it and it doesn't seem to exist elsewhere either.
Is this still considered a proper disease or was it just based on a case study and could possibly be something else? I found this paper:
https://pubmed.ncbi.nlm.nih.gov/2264478/
Thanks for any clarifying information!

Hi Nicole!  This is indeed one example of the conditions that most likely will be retired; because we are still in the review process I can’t tell when it will be retired. Thank you for this one! Gioconda
From: Nicole Vasilevsky @.>
Sent: Tuesday, August 24, 2021 5:04 PM
To: monarch-initiative/mondo @.>
Cc: Alyea, Gioconda (NIH/NCATS) [C] @.>; Mention @.>
Subject: [monarch-initiative/mondo] question: drachtman weinblatt sitarz syndrome (#3568)
@galyea-gardhttps://github.com/galyea-gard
is there any additional info about this disease:
https://rarediseases.info.nih.gov/diseases/1913/drachtman-weinblatt-sitarz-syndrome
It isn't in OMIM record for it and it doesn't seem to exist elsewhere either.
Is this still considered a proper disease or was it just based on a case study and could possibly be something else? I found this paper:
https://pubmed.ncbi.nlm.nih.gov/2264478/
Thanks for any clarifying information!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/monarch-initiative/mondo/issues/3568, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APG3MG7RCLWANJP3AHHVYGTT6QCMHANCNFSM5CXU2PLQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

Thanks @galyea-gard! We'll keep it for now then, thanks! Please let us know when you have a list of retired terms in GARD and we can update them in Mondo.


Fix/dataset index: Index values were faulty when indexing the original samples instead of blocks.

What does this PR do?
The index values in the pbin files had the wrong values. They did start with an offset and additionally, we added another offset of HEADER size when reading from the file buffer.
See here for the initial offset during pbin index creation:
https://github.com/Modalities/modalities/blob/4aa2e88efe13c3eaab4c6b425fdb82caf0d2a443/src/modalities/dataloader/create_packed_data.py#L145
and the additional offset that is used when reading from the memmap during training:
https://github.com/Modalities/modalities/blob/4aa2e88efe13c3eaab4c6b425fdb82caf0d2a443/src/modalities/dataloader/create_packed_data.py#L262
This PR fixes this issue and makes the index always start at byte 0, only applying the offset once when reading from the memmap file.
General changes

index tuples are now always in bytes and the start of the first sample in the data section starts at byte 0 (before the was a wrong offset)
added test for indexing the original samples
the documentation was updated accordingly
removed block_size from abstract classes that don't need to see the block_size concept

Breaking Changes

None

Checklist before submitting final PR

[x] My PR is minimal and addresses one issue / enhancement in isolation
[x] I have merged main into this feature branch
[x] I have reviewed my own code w.r.t. correct implementation, missing type hints, proper documentation, etc.
[x] I have run a sample config for model training
[x] I have fixed all failing tests (python tests/tests.py)

fixes #163

Yes, the inheritance structure can be improved. I suggest we do this in a separate PR together with improving the "packing" terms in those cases when there is no actual packing happening.
I added the issue https://github.com/Modalities/modalities/issues/167 for addressing this.


Vid-Enhancement-Mod with Randy Rossi's VIC II KAWARI - huge artifacts, flickering characters

Hello,
So, I'm a dabbler in the art of restoring and building c64 machines just for the heck of it. I don't do vlogging nor am I a youtuber, just a "humble" IT tech with Operating Systems Development background.
Recently I've had the chance to get a few of these C64-Vid-Enhancement-Mods which have been made of unobtainium for a very long time - so, it's been more or less smash'n'grab while the grabbing is good (and no, no violence was involved, just the usual quid quo pro of giving money, getting items).
Now, I've buildt two of those nice  sixtyclone-boards and provided them with the mods. Booting up on first try with a plain old VIC II. Works like a charm and gives a fine and chrystal clear image. Then I've tried one of the Kawaris out of my stash (older firmware, not yet flashed an upgrade) and 'lo! the machines boot up, but the screen is corrupted: flickering characters - despite the background color AND the border color being right. Other than that, the c64 boards been working and even accepting keyboard input.
I wonder if you've already encountered this issue. If yes, what can we do to get a grip on this weird effect? I have a feeling as if the KAWARI has a slightly different signal pattern on it's pins - and my VHDL is rusty as hell so I dare not to do anything with the code.
If need be I can provide photos of the screen, if that helps.
Remark: currently, KAWARIs seem to be made of unobtainium too - at least on the videogameperfection.com-site if I am not mistaken.

Hi!
I have not used a Kawari yet, but this sounds like it has different timings for memory accesses than a regular VIC-II. So my board misses the relevant data. The only solution that I can image is to adjust the Kawari's firmware to better match the behaviour of the VIC-II.
best regards,
Reinhard

Hi,
Then, ere I'll bring this issue to Randy Rossi's attention, I shall try
the following two things:

flash one of my small kawaris with the latest firmware (1.17 IIRC)
Configure the "emulated" VIC-Version with the kawari config tool.
Maybe another VIC version in the KAWARI results in working vid output.
on the 250466 sixtyclone board, I'll replace the PLAnkton with a
plain old PLA from 1986 even thou, as far as I understand, the PLA has
no interaction whatsoever with the VIC-II - but then, I might be in
error. Faulty timings can throw a sabou into the workings anyways.

gunna keep ya posted.
br
Thomas
Am 2023-10-21 17:26, schrieb c0pperdragon:

Hi!
I have not used a Kawari yet, but this sounds like it has different
timings for memory accesses than a regular VIC-II. So my board misses
the relevant data. The only solution that I can image is to adjust the
Kawari's firmware to better match the behaviour of the VIC-II.
best regards,
Reinhard

Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
You are receiving this because you authored the thread.Message ID:
@.***>
Links:
[1]
https://github.com/c0pperdragon/C64-Video-Enhancement/issues/96#issuecomment-1773830302
[2]
https://github.com/notifications/unsubscribe-auth/ABGOXUGCPIMDMR53W77FGJTYAPSRBAVCNFSM6AAAAAA6KF7Y3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTHAZTAMZQGI

to be continued on Randy Rossi's KAWARI GitHub Site - opened an issue there.
issue closed.


⚠ SceneTime has degraded performance

In 92307f4, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1160 ms

Resolved: SceneTime performance has improved in a54ff18 after 6 minutes.


[Core] Removes utils/extend.js

This commit removes the extend.js utility. We already have enough existing merge alternatives such as our own style merger, lodash.merge, react-addon-update, Object.assign, and ES6 spread operators. I replaced each use of utils/extend with the "most appropriate" alternative according to code consistency and then removed utils/extend.js.
Note: Technically extend.js is a recursive merger. lodash.merge is also a recursive merger. Based on use cases, it seems like styles/theme-manager is the only case that actually requires recursive merging.

@newoga Yeah! Let's get rid of this technical dept :tada:.

"debt". Getting rid of the technical department is probably not what you want :winking:

@newoga Thanks :grin:

@mbrookes I would rather be a native speaker :grin:

@newoga @oliviertassinari are you sure that this didn't break anything? Removed extend util was always returning a new object, without mutating the base (https://github.com/callemall/material-ui/blob/v0.14.2/src/utils/extend.js). lodash.merge is actually mutating the base (https://lodash.com/docs#merge).

@igorbt This code has gone through a few refactorings (for example neither Extend and mergeStyles() in this PR is being used in master at the moment). Currently Object.assign is being used and it is creating new objects when necessary. Could you open a new issue and describe the problem you're having in detail and what version you're having it in?


Extend profile features

extend profile features for end users are missing. I would like to show my GitHub, Twitter and LinkedIn account on my own profile page and a picture of me or even do a sync with my GitHub account information. I think it has a positive effect on socializing of an end user.

I agree this would be nice. Admins can do this, and there is a free text field to add details like that.
It'd also be nice to allow login via github or twitter so that the user doesn't have to enter info.
Any other ideas please do post them as issues, thanks for participating on the site.


Is load testing in Azure DevOps depreciated?

The text at the top of this pages that says "Start running cloud-based load tests in almost no time with Azure DevOps" directs you to https://azure.microsoft.com/en-au/services/devops/test-plans/.
The content of the page https://azure.microsoft.com/en-au/services/devops/test-plans/ suggests that load tests are run in Azure Devops under the Test Plans -> Load test section.

In Azure Devops the Load test page tells you you can upload a Visual Studio webtest. If you click the Create test button you will be shown a dialog that says "Author user scenario using webtest. Learn more".

If you click "Learn more" you are taken to https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2008/ms182539(v=vs.90). This page tells you it is not being updated regularly.

I'm a little confused by all this and can not find any concrete explanation as to whether the depreciation of the web performance and load test functionality in Visual Studio impacts Azure Devops. The two offerings seem to be tightly coupled, but I haven't seen any indication that load testing in Azure is depreciated.
If anyone can shed some light on the future of the load testing solution in Azure it would be much appreciated.

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

ID: 938662b3-8e6d-aebf-062b-d00b4ed4c22e
Version Independent ID: fe2487bf-0d3d-24f3-6cf1-4cd18973ef79
Content: Load test in the cloud with Visual Studio - Azure Test Plans
Content Source: docs/test/load-test/getting-started-with-performance-testing.md
Product: devops
GitHub Login: @alexhomer1
Microsoft Alias: ahomer

https://devblogs.microsoft.com/devops/cloud-based-load-testing-service-eol/

@mcasperson  - Yes, the service is deprecated. The announcement was made last week https://devblogs.microsoft.com/devops/cloud-based-load-testing-service-eol/
The docs team is helping with updating the docs to show the deprecated status - it should be done in the next couple of days.

@mcasperson - Yes, the service is deprecated. The announcement was made last week https://devblogs.microsoft.com/devops/cloud-based-load-testing-service-eol/
The docs team is helping with updating the docs to show the deprecated status - it should be done in the next couple of days.

Any chance of extending the EOL date from March 31 2020?

In the above notice, it says
"Running a load test in the cloud using Visual Studio (both auto-provisioned agents and self-provisioned ‘bring-your-own’ agents): You can continue to run the tests but self-hosted with Test Controller/Test Agent option outlined above."
After reading this I am further confused. If we have our load test agents created in Azure - then can we use them to perform the load test? Can someone please clarify?


Upgrade AssertJ 3.25.3 -> 3.26.0

This PR contains the following updates:

Package
Type
Update
Change

AssertJ (source)
import
minor
3.25.3 -> 3.26.0

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade AssertJ 3.25.3 -> 3.26.0

See:
- https://github.com/assertj/assertj/releases/tag/assertj-build-3.26.0
- https://github.com/assertj/assertj/compare/assertj-build-3.25.3...assertj-build-3.26.0

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


[FLINK-24992] StreamingWithStateTestBase compiles on later Scala versions

The subSequence method is no longer available for arrays.
The code in question was rewritten to just work on strings.

@flinkbot run azure


OAI_CONFIG_LIST details in documentation

It would be helpful to add details about the OAI_CONFIG_LIST in documentation so that users can quickly starts with the OAI functions.

Could you read https://microsoft.github.io/autogen/docs/Use-Cases/enhanced_inference#runtime-error and see if the issue is addressed?

Is there a working example of this file, in JSON format? I can get this file to work or parse right when I create it.

I was a bit confused on how this works. It would be nice to just have something like load_dotenv() to handle the keys. But anyways - Just going off the examples in the /notebooks directory i made a file called OAI_CONFIG_LIST (with no filetype)
[
    {
        "model": "gpt-4",
        "api_key": "***"
    },
    {
        "model": "gpt-3.5-turbo",
        "api_key": "***"
    }
]

In my notebook:
# Setting configurations for autogen
config_list = autogen.config_list_from_json(
    env_or_file="OAI_CONFIG_LIST",
    file_location=".",
    filter_dict={
        "model": {
            "gpt-4",
            "gpt4",
            "gpt-4-32k",
            "gpt-4-32k-0314",
            "gpt-4-32k-v0314",
            "gpt-3.5-turbo",
            "gpt-3.5-turbo-16k",
            "gpt-3.5-turbo-0301",
            "chatgpt-35-turbo-0301",
            "gpt-35-turbo-v0301",
            "gpt",
        }
    }
)

config_list

When printing config_list
[{'model': 'gpt-4',
  'api_key': '***'},
 {'model': 'gpt-3.5-turbo',
  'api_key': '***}]

And then i pass the config_list to the initiate_chat function.
assistant = AssistantAgent("assistant")
user_proxy = UserProxyAgent("user_proxy")
user_proxy.initiate_chat(assistant, message="Plot a chart of META and TESLA stock price change YTD.", config_list=config_list)

This worked for me

This is tremendously helpful, thank you.

I was a bit confused on how this works. It would be nice to just have something like load_dotenv() to handle the keys. But anyways - Just going off the examples in the /notebooks directory i made a file called OAI_CONFIG_LIST (with no filetype)
[
    {
        "model": "gpt-4",
        "api_key": "***"
    },
    {
        "model": "gpt-3.5-turbo",
        "api_key": "***"
    }
]

In my notebook:
# Setting configurations for autogen
config_list = autogen.config_list_from_json(
    env_or_file="OAI_CONFIG_LIST",
    file_location=".",
    filter_dict={
        "model": {
            "gpt-4",
            "gpt4",
            "gpt-4-32k",
            "gpt-4-32k-0314",
            "gpt-4-32k-v0314",
            "gpt-3.5-turbo",
            "gpt-3.5-turbo-16k",
            "gpt-3.5-turbo-0301",
            "chatgpt-35-turbo-0301",
            "gpt-35-turbo-v0301",
            "gpt",
        }
    }
)

config_list

When printing config_list
[{'model': 'gpt-4',
  'api_key': '***'},
 {'model': 'gpt-3.5-turbo',
  'api_key': '***}]

And then i pass the config_list to the initiate_chat function.
assistant = AssistantAgent("assistant")
user_proxy = UserProxyAgent("user_proxy")
user_proxy.initiate_chat(assistant,
    message="Plot a chart of META and TESLA stock price change YTD.",
    config_list=config_list
)

This worked for me
Update
If you'd rather use load_dotenv() this worked for me.
import json
from dotenv import find_dotenv, load_dotenv
load_dotenv(Path('../../.env'))

env_var = [
    {
        'model': 'gpt-4',
        'api_key': os.environ['OPENAI_API_KEY']
    },
    {
        'model': 'gpt-3.5-turbo',
        'api_key': os.environ['OPENAI_API_KEY']
    }
]

# needed to convert to str
env_var = json.dumps(env_var)

# Setting configurations for autogen
config_list = autogen.config_list_from_json(
    env_or_file=env_var,
    filter_dict={
        "model": {
            "gpt-4",
            "gpt4",
            "gpt-4-32k",
            "gpt-4-32k-0314",
            "gpt-4-32k-v0314",
            "gpt-3.5-turbo",
            "gpt-3.5-turbo-16k",
            "gpt-3.5-turbo-0301",
            "chatgpt-35-turbo-0301",
            "gpt-35-turbo-v0301",
            "gpt",
        }
    }
)

Thanks. You can also have a single env var which contains the entire json and load it directly:
load_dotenv(Path('../../.env'))
config_list = autogen.config_list_from_json(YOUR_ENV_VAR_NAME_FOR_JSON)

I'm trying to solve the same problem using fastchat with a local llm as in the documentation but it fails because I don't provide an openai key:
from autogen import AssistantAgent, UserProxyAgent, oai
config_list=[
    {
        "model": "chatglm2-6b",
        "api_base": "http://localhost:8000/v1",
        "api_type": "open_ai",
        "api_key": "NULL", # just a placeholder
    }
]

response = oai.Completion.create(config_list=config_list, prompt="Hi")
print(response) # works fine

assistant = AssistantAgent("assistant")
user_proxy = UserProxyAgent("user_proxy")
user_proxy.initiate_chat(assistant, message="Plot a chart of META and TESLA stock price change YTD.", config_list=config_list)
# fails with the error: openai.error.AuthenticationError: No API key provided.

I'm trying to solve the same problem using fastchat with a local llm as in the documentation but it fails because I don't provide an openai key:
from autogen import AssistantAgent, UserProxyAgent, oai
config_list=[
    {
        "model": "chatglm2-6b",
        "api_base": "http://localhost:8000/v1",
        "api_type": "open_ai",
        "api_key": "NULL", # just a placeholder
    }
]

response = oai.Completion.create(config_list=config_list, prompt="Hi")
print(response) # works fine

assistant = AssistantAgent("assistant")
user_proxy = UserProxyAgent("user_proxy")
user_proxy.initiate_chat(assistant, message="Plot a chart of META and TESLA stock price change YTD.", config_list=config_list)
# fails with the error: openai.error.AuthenticationError: No API key provided.

Please add llm_config={"config_list": config_list} in the constructor of AssistantAgent

Thanks, that worked!

Added to FAQ: https://microsoft.github.io/autogen/docs/FAQ/#set-your-api-endpoints

Update: i found that my previous example was throwing an error because the json was being parsed as a string. Here is working example of setting up your config list using dotenv. This will allow you to dynamically create the json file required by autogen.config_list_from_json() when you're using a .env file
import tempfile
from dotenv import find_dotenv, load_dotenv
load_dotenv(find_dotenv())

env_var = [
    {
        'model': 'gpt-4',
        'api_key': os.getenv('OPENAI_API_KEY')
    },
    {
        'model': 'gpt-3.5-turbo',
        'api_key': os.getenv('OPENAI_API_KEY')
    }
]

# Create a temporary file
# Write the JSON structure to a temporary file and pass it to config_list_from_json
with tempfile.NamedTemporaryFile(mode='w+', delete=True) as temp:
    env_var = json.dumps(env_var)
    temp.write(env_var)
    temp.flush()

    # Setting configurations for autogen
    config_list = autogen.config_list_from_json(
        env_or_file=temp.name,
        filter_dict={
            "model": {
                "gpt-4",
                "gpt-3.5-turbo",
            }
        }
    )

assert len(config_list) > 0
print("models to use: ", [config_list[i]["model"] for i in range(len(config_list))])

models to use:  ['gpt-4', 'gpt-3.5-turbo']

How to set Google Bard AI in the OAI_CONFIG_LIST file? It is possible ?

import autogen
import getpass
import tempfile
from dotenv import load_dotenv
import os
import json

load_dotenv(dotenv_path='../../API_KEYs.env')

OPENAI_PROJECT_KEY = os.getenv('OPENAI_PROJECT_KEY')
OPENAI_API_KEY = os.getenv('OPENAI_API_KEY')

OAI_CONFIG_LIST = [{
        'model': 'gpt-4o-mini',
        'api_key': OPENAI_API_KEY
    }]

with tempfile.NamedTemporaryFile(mode='w+', delete=True) as temp:
    env_var = json.dumps(OAI_CONFIG_LIST)
    temp.write(env_var)
    temp.flush()

    # Setting configurations for autogen
    config_list = autogen.config_list_from_json(
        env_or_file=temp.name,
        filter_dict={
            "model": {
                "gpt-4o-mini",
            }
        }
    )

gpt4_config = {"seed": 42,
               "config_list": config_list,
               "temperature": 0}

Gives me this warning now:
[autogen.oai.client: 09-26 14:19:56] {184} WARNING - The API key specified is not a valid OpenAI format; it won't work with the OpenAI-hosted model.

@cjy8s You can just use the config_list_from_dotenv function instead of writing a temporary file.


Add open/closed state for open_cover and close_cover in SERVICE_TO_STATE

Note: I've never contributed to home-assistant before and have tried to follow the CONTRIBUTING.md as well as possible. Please give some constructive criticism if I've done anything wrong.
Description:
This allows for a cover's state to be set through a scene by adding the cover's open_cover and close_cover services to the SERVICE_TO_STATE dict in helpers/state.py.
Related issue (if applicable): fixes #3177
Example entry for configuration.yaml (if applicable):
scene:
  - name: test
    entities:
      cover.open_this:
        state: 'open'
      cover.close_this:
        state: 'closed'

Checklist:
If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

I wasn't sure where to add the tests needed, if any were. The tests for helpers/state.py seem to be fairly generic and don't specifically target any component.

Could you please also include the tilt services?

I've tried my best to include them, but unfortunately I don't have any covers that support tilting to test with or any relevant documentation at the moment. I assume they still follow the regular open/closed convention in regards to state.

Gah, don't merge yet. It seems adding the tilting has broken the mapping for normal covers.

Yeah, it looks like adding that mapping for SERVICE_OPEN_COVER_TILT AND SERVICE_CLOSE_COVER_TILT has caused those services to be called for covers that don't support tilting.
Relevant log entries:
[homeassistant.core] Bus:Handling <Event call_service[L]: domain=scene, service_call_id=140212719087968-20, service_data=entity_id=['scene.lounge_evening'], service=turn_on>
[homeassistant.core] Bus:Handling <Event call_service[L]: domain=cover, service_call_id=140212719087968-22, service_data=entity_id=['cover.lounge_side', 'cover.lounge_main'], service=close_cover_tilt>

I have reverted that problem commit. The PR in it's current form supports scenes for basic covers that don't expose the open_cover_tilt and close_cover_tilt services.

Hi,
I can confirm that nvella's first patch (841374d) fixes the cover state issue for me. I'm using the homematic cover component and got 'unable to reproduce state' errors when changing the cover state in a scene in home assistant 0.27.2.
I vote for merging nvella's patch into the next release.
As for the tilt: I've not tested that yet. I'm not sure if the homematic cover component supports tilt (or what home assistant means with tilt). However, what I have on my agenda is to add a cover state to my scenes where the blinds are "semi closed". (i.e., some light is coming through but most of the sun is blocked out). The cover tilt feature sounds like going in that direction. Please let me know if I can help here by testing experimental code.

I haven't decided yet but if we do a 0.27.3 this will go out with it, so I attached this to the milestone.

@yellowlexx Homematic currently does not support tilting. As far I understand, tilting is exactly what you have on your agenda (tilting the blinds to "semi closed").
The problem with the Homematic-actors is, that they don't have a dedicated tilt-function. With them tilting is achieved by running the motor in direction x for time y. But the time it takes depends on the used blind. We haven't come to a solution for that. Basically a set_position(current_position-1) would already perform the tilting. But this 1% should be configurable per entity, which is currently not possible with the auto-detection the Homematic-component uses.

I'm really sorry, the tilt should not be added to the dict, because it does not affect the state at all, only attributes.

If a service requires an attribute, those can be added to the other dict in the state helper to enable scene support for that attribute.

Hi DanielPerna84,
As for the tilt in case of homematic I think its is even more complicated. While moving downwards, my blinds are "closed", i.e., the individual elements of the blind are positioned such that I can't "see through" while the blind is moving downwards.
When the blind is moving up, the individual blind elements are positioned such that I can "see through" while the blind is moving up.
To achieve the desired result (tilt) we would have to do a set_position(current_position+1) if the blind's previous movement direction was downwards and set_position(current_position-1) if the previous movement direction was upwards.
What would satisfy my needs for now would be something that drives my blinds into a "shading" position. This is achieved by first bringing the blind into a state closed and then tilting it by, e.g.
set_position(2). The two problems I have is that (a) set_position is not accessible in a scene (I have not figured out how to make this attribute accessible) and (b) I'm not aware how to define a sequence in a scene (first close the blind and then to a set_position(2).

Not sure if anything else should be done on this PR. As far as I'm aware the issue with the open/close_cover_tilt services lies in the fact that they translate to the same cover states as the regular open/close_cover services, causing the open/close_cover_tilt services to be called on covers that don't have them implemented, like MQTT. Maybe this should be pulled out into a separate issue?

#3177


fork-observer: reduce query interval

For S-C-A-L-I-N-G
Reduce query interval to every 60 seconds by default. Helps on larger networks.

lgtm
I might want to add some randomness to the query interval for each node in fork-observer so you don't end up firing 200 RPC calls exactly ever 60s.

Also, keep in mind that fork-observer currently has a limit of 256 nodes per network. It's trivial to increase it but I haven't gotten to it yet. https://github.com/0xB10C/fork-observer/issues/22

Oh right, I think I will also add a commit here to disable if the graph is >256 nodes then

Do we still need this now that fork observer was updated? There's also https://github.com/bitcoin-dev-project/warnet/pull/177

Yeah we want this. Updated FO lets us attach more nodes (256 limit), this queries the nodes less frequently. You know how you saw FO was using the most CPU/bandwidth on the graphs earlier... ;)
#177 is different

Would be even nicer (for us) if FO would query on a chill scheduler, e.g. If you configure 100 nodes and query every 60 seconds it could query one node every 0.6 seconds to keep resource usage as flat as possible. Vs currently where every n seconds it will query all nodes at the same time (or as fast as it can).
But I haven't thought about side effects of that for wider FO usage and that's a PR for another repo in any case!

can remove this commit though? https://github.com/bitcoin-dev-project/warnet/pull/175/commits/bf2e05873f690022059a05df3d5e60378da874c6

ohhhhh, sure

rebased and dropped commit

Would be even nicer (for us) if FO would query on a chill scheduler, e.g. If you configure 100 nodes and query every 60 seconds it could query one node every 0.6 seconds to keep resource usage as flat as possible. Vs currently where every n seconds it will query all nodes at the same time (or as fast as it can).

Agree, I made an issue for this https://github.com/0xB10C/fork-observer/issues/23 the other day.


Adjust for new GCC 8 descriptor

Avg response time
coverage on master

Summary of changes
Modified several C-preprocessor definitions in libcaf-gfortran-descriptor.h.
Rationale for changes
These changes adapt to the descriptor change that expands the
maximum (co)array dimension from 7 to 15 as applied to the GCC
trunk in svn revision 257065 (git commit d9c7c3 on the GCC git
mirror).
Additional info and certifications
This pull request (PR) is a:

[X] Bug fix
[ ] Feature addition
[ ] Other, Please describe:

I certify that
@zbeekman This is not been fully tested.  I'll finish testing with GCC 8 later, but it should be safe to merge if the tests pass with GCC 6 and 7:

[x] I reviewed and followed the contributing guidelines, including
- Increasing test coverage for all feature-addition PRs
- Increasing test coverage for all bug-fix PRs for which there
does not already exist a related test that failed before the PR
- At least maintaining test coverage for all other PRs
- Ensuring that all tests pass when run locally
- Naming PR  to indicate work in progress (WIP) and to attach the PR
to the appropriate bug report or feature request issue
- White space (no trailing white space or white space errors may
be introduced)
- Commenting code where it is non-obvious and non-trivial
- Logically atomic, self consistent and coherent commits
- Commit message content
- Waiting 24 hours before self-approving the PR to give another
OpenCoarrays developer a chance to review my proposed code

This branch is being abandoned in favor of the descriptor-surgery branch.  I'm closing this pull request and will submit a new one based on the latter branch.
[descriptor-surgery]:

@rouson can we delete the gcc8-descriptor branch?


[Tracing] Enable tracing in a cloudfunction

Create a flag or config option to allow tracing to Cloud tracing using open telemetry.

testing using the flask instrumenter, which resulted in
app._original_wsgi_app = app.wsgi_app
AttributeError: 'Goblet' object has no attribute 'wsgi_app'

so we will need to build our own wrapper/ instrumenter for goblet


hygiene: fix #[pymethods(crate = "...")]

Got to the bottom of the hygiene issue in test of #2914
Turns out that #[pymethods] #[pyo3(crate = "...")] works, but #[pymethods(crate = "...")] was ignoring the argument.
Added a tweak to fix this and a snippet in the hygiene test (which fails on main).

bors r+


Is standard c++(-std=c++ or /STD:c++11) only needed to run mkldnn  on both windows and linux? Or higher versions 14,17 also supported?

Hi,
I'm trying to run  simple_net.cpp example on Windows from command line using visual studio 15. I'm   not using any /STD:c++11 compiler flag. But Visual studio default takes c++14 as  c standard, example working fine. Means does mkldnn supports c++11 and it's higher versions?

Hi @tensor-go,
The minimum required version of C++ standard is C++11. So it is perfectly fine if you use C++14 or above.

Thanks @emfomenk


Why do I get "Bitmap too large to be uploaded into a texture" error

I use picasso to load the bitmap from network. Small images are loaded, with larger images I get "Bitmap too large to be uploaded into a texture" error (a lot of them). Tiling is not disabled.
Bitmap too large to be uploaded into a texture (5000x2813, max=4096x4096)

The view can't tile the image if you provide it as a Bitmap object. You should save it to temporary storage and provide the file URL instead.

I will see if it's possible to tile a Bitmap object when it's larger than the max texture size. However, you should be aware that an image this large will cause OutOfMemoryErrors on many old or budget devices, and it is always best to write the raw image data to disk then use the file path instead of creating a Bitmap from it.

If OutOfMemoryError  is still on the table when you tile the Bitmap, think it is not needed. I did what you suggest. Thank you.

You're welcome, thanks.


ENH: sparse.linalg: support 64-bit BLAS in isolve

Reference issue
Part of gh-11193
What does this implement/fix?
Support 64-bit BLAS in scipy.sparse.linalg.isolve

LGTM, merged. Thanks @pv


Disable console clearing

Hey! Is it possible to disable console clearing?

If clear is disabled, a lot of information for detection will appear in the console (every detection loop)
If you want the your debugging information not to cleared, you can turn off the detection in the development environment
if (!__DEV__) {  devtoolsDetector.launch() }

Got it, thanks for the reply. However, the library clears the console before I call the launch method, is there any way to get around this?

I just tried it won't clear the console before call the launch method

I am using a package which uses devtoolsDetector (@d-i-t-a/reader) and so I do not have control over devtoolsDetector.launch() nor do I see that anywhere in the reader code. Is there another way to configure devtools-detector not to clear the console?

you can rewrite devtoolsDetector.launch method before import @d-i-t-a/reader
e.g.

devtoolsDetector.launch = () => void

const reader = require("@d-i-t-a/reader")

This disables other functionality used by the module for its content protection which requires detecting when the dev tools are open. What I really need to do is disable the console clearing. I actually found a way to do this by just pointing console.clear to an empty function, ilke you did with the launch method. In the index.html for the whole React app I simply add a script like so:
<!-- Disable console.clear() for debugging purposes -->
<script type="text/javascript">console.clear = () => void;</script>

Thanks for the great tool! And for the good idea of overriding the method like that :)

Hey! Is it possible to disable console clearing?

@Valar353 You can do this by overriding console.clear().

@AEPKILL  this question can be closed as there is a suitable workaround (imo)

Note that pointing to void did not work for me and I actually had to override to an empty function with () => {}.


Add dynamic routing of hug.cli arguments from hug router

Add ability to add defined commands such as test and build that get routed via the hug runner.
For example:
 hug -f my_api.py build --db my_db

Enabled by
@hug.cmd():
def build(db):
     # do db build here

Thanks @BrandonHoffman for the idea!

hug now will automatically collect and expose all commands written as @hug.cli() so that they can be accessed with hug -f my_api.py -c $COMMAND_NAME $COMMAND_ARGUMENTS


xworkspaces does not display workspace as occupied when using send_to_workspace

Describe the issue
when you sent a window to a workspace using send_to_workspace the xworkspaces module doesn't show said workspace as occupied, but when you go to the said workspace and open a window on it, then leave the workspace, it shows it as occupied (displays the label-occupied-background and label-occupied-foreground).
Expected behavior:
being in a workspace (for example 0) sending a window to another workspace (for example 4)
the xworkspaces should display the label-occupied-background and label-occupied-foreground for the workspace the window was sent to (workspace 4)
Actual behavior:
The xworkspaces does not display the abel-occupied-background and label-occupied-foreground for the workspace the window was sent to.
To Reproduce
A minimal but complete config with which the problem occurs:
type = internal/xworkspaces
pin-workspaces = true
format = <label-state>

label-active = %name%
label-active-foreground = #3b4252
label-active-background = #88c0d0
label-active-padding = 2
label-active-margin = 1
label-occupied = %name%
label-occupied-background = #5e81ac
label-occupied-padding = 2
label-empty = %name%
label-empty-background = #3b4252
label-empty-foreground = #81a1c1
label-empty-padding = 2
label-urgent = %name%
label-urgent-background = #bf616a
label-urgent-padding = 2

to reproduce
Open a window on a workspace, send the window to another workspace
Environment:

WM: Berry
Distro: Linux Mint
Output of polybar -vvv:

polybar 3.4.0-24-g2b31a3f
Features: +alsa -curl -i3 -mpd +network(wireless-tools) +pulseaudio +xkeyboard
X extensions: +randr (+monitors) +composite +xkb +xrm -xcursor
Build type: Release
Compiler: /usr/bin/clang++
Compiler flags:  -Wall -Wextra -Wpedantic -Wno-error=parentheses-equality -Wno-zero-length-array
Linker flags:

Just to be sure, send_to_workspace is a cmd from your window manager?

Just to be sure, send_to_workspace is a cmd from your window manager?

yes, it is.

I'll try to recheck this week-end but it seems that polybar doesn't receive the event from Xorg when a window is moved to another workspace using berry.

I actually explicitly tested this behavior on herbstluft, so either berry is not sending an event in this case or we don't listen to the right events.

I also remember testing this for xmonad. Then again: xmonad emits a lot of events for everything.

I'm the berry developer - this was an issue on our end and fixed as of https://github.com/JLErvin/berry/pull/78/commits/5ab590cea3bcb7282108ee837e131d514389747c. Should have nothing to do with polybar.

@JLErvin Thanks for letting us know :smiley:
@ronniedroid Please let us know if you still have this issue and I will reopen this again.


Add support for Chrome on IOS devices

Currently, detect-incognito is not detecting Chrome incognito on IOS devices. Do you have some ideas on how to achieve this?

Yes, I have a fix for this. Will implement within the next 24 to 48 hours.

A preliminary Safari method has been added to detectIncognito.js. Changes are not yet reflected in detectIncognito.min.js nor in TypeScript. If anyone wants to update the TypeScript, feel free to submit a pull request.

@Joe12387 thank you! I've tested your update and now it works correctly.


Use sccache on all CI platforms

MSVC on Windows was previously omitted from the list of CI platforms that use sccache. Unify the CMAKE_CACHE_OPTIONS used for all CI platforms.
In the case of a 100% cache hit, this cuts down the average checks time from 8 minutes to 4 minutes, example:
https://github.com/ahesham-arm/OpenCL-CTS/actions/runs/9896449792

Merging as discussed in the July 16th teleconference.


Use new logo

Fixes #518

Is it possible to have transparent background of the logo in this image with a light grey background?

@emmasundqvist You are right. That was a silly attempt of mine to convince DrawIO to remove pointer-events: none from the SVG and make the "Created by Elastisys" logo clickable.
I removed it now. PTAL.


WIP: test coordinator::core::Service

This is much harder than expected... I had to wrap the rpc client mock into an mutex, which is much more verbose and makes the api much more complicated.
There's a lot of documentation work to do here.

Closing in favor of https://github.com/xainag/xain-fl/pull/352


Top level Makefile is broken?

$ pwd
/home/kiwamu/src/ivory
$ make
cabal sandbox init
Writing a default package environment file to
/home/kiwamu/src/ivory/cabal.sandbox.config
Creating a new sandbox at /home/kiwamu/src/ivory/.cabal-sandbox
echo "tests: True" >> cabal.sandbox.config
cabal sandbox add-source  ivory/  ivory-artifact/  ivory-backend-acl2/  ivory-backend-c/  ivory-eval/  ivory-examples/  ivory-hw/  ivory-model-check/  ivory-opts/  ivory-quickcheck/  ivory-serialize/  ivory-stdlib/
cabal: Error adding source reference.
Failed to read cabal file of add-source dependency:
/home/kiwamu/src/ivory/ivory-backend-acl2
Makefile:28: recipe for target 'build' failed
make: *** [build] Error 1

I can build them with following patch.
diff --git a/Makefile b/Makefile
index db883e9..9cdab14 100644
--- a/Makefile
+++ b/Makefile
@@ -6,7 +6,6 @@ BIN=.cabal-sandbox/bin
 PACKAGE= \
   ivory \
   ivory-artifact \
-  ivory-backend-acl2 \
   ivory-backend-c \
   ivory-eval \
   ivory-examples \

@master-q: Try running git submodule init and git submodule update first. That should pull in the dependency ivory-backend-acl2 via a git submodule.

The issue is fixed by your advice. Thanks.

Welcome! What brings you back to Haskell? Are you still working with ATS?

I use both of them. Today, I try Ivory programming on Arduino. https://github.com/fpiot/arduino-ivory

Good! I have wanted to try this myself soon - so far I've only used Ivory on ARM Cortex-M0. I'll be paying attention to that repo.


fix: network unreachable when add egress qos for pod

when add egress qos for pod, the pod network is unreachable.
through research, the container's virtual nic's qlen is 0 is
the root reason. so set the nic's qlen to 1000(default for linux)
when create pod.

Thanks! @qsyqian


TimeSpeed: Extended key configuration

Since there is a request #3 to change key functionality and cantorsdust decided to use x2, /2 for a reason I thought about adding extended hotkey configuration.
Basically, it should look something like this:
"Keys": {
  "TickInterval": {
    "Alt+Z": "-10", // add 10 seconds to tick interval
    "Alt+X": "+10", // subtract 10 seconds from tick interval
    "Ctrl+Z": "/2", // halves tick interval
    "Ctrl+X": "*2" // doubles tick interval
  }
}

It will support custom number after operation sign (+, -, *, /) and any number of hotkeys for any operation. It can contain not only regular modifiers, but also custom key groups like: A+B or Z+X+C.
Such implementation should be quite intuitive to use and allow wide range of customizations.
This can go as 2.2-beta after non-beta 2.1 is released.
@Pathoschild, what do you think about the idea?

That looks good; it would be useful for users who need more control over the tick length, and we could preconfigure some keys by default. The parser would need to be pretty flexible to handle edge cases (e.g. having spaces like + 10 or missing signs like 10), and show useful errors if parsing fails. I'd suggest considering controller support if you're revisiting input, though.

The only problem I see it will require reference to JSON.NET again.
Can you give any links on how controller support can be handled in mods?

You could avoid referencing Json.NET by mapping the TickInterval field to a Dictionary<string, int> (or Dictionary<string, string> to show friendlier errors for invalid values) and parsing it after it's deserialised, maybe using the [OnDeserialized] attribute like we do in TimeSpeedConfig.
I usually add controller support by creating a generic input mapping model like InputMapConfig<T>, then my config model has an InputMapConfig<Keys> and InputMapConfig<Button>. I have an intermediate model which replaces invalid values with the defaults, but you could simplify if you don't want that. Your implementation would be a bit different since you'll be parsing the keys yourself, but the basic principle would work.

You could avoid referencing Json.NET by mapping the TickInterval field to a Dictionary<string, int> (or Dictionary<string, string> to show friendlier errors for invalid values) and parsing it after it's deserialised, maybe using the [OnDeserialized] attribute like we do in TimeSpeedConfig.

I usually add controller support by creating a generic input mapping model like InputMapConfig<T>, then my config model has an InputMapConfig<Keys> and InputMapConfig<Button>. I have an intermediate model which replaces invalid values with the defaults, but you could simplify if you don't want that. Your implementation would be a bit different since you'll be parsing the keys yourself, but the basic principle would work.
You can receive controller input with SMAPI's ControlEvents.ControllerButtonPressed and ControlEvents.ControllerTriggerPressed events. I usually create a generic input-handling method like ReceiveInput<T>(T input, InputMapConfig<T> map) to handle keyboard/controller input in one place.

Thanks for invitation to comment on this idea. I think it is a great one.
What about using mouse, like wheel for example? With modifiers like shift and control?
And since we would have some nice config options like you propose, what about static values, like for example:
"Keys": {
"TickInterval": {
"Alt+Z": "-10", // add 10 seconds to tick interval
"Alt+X": "+10", // subtract 10 seconds from tick interval
"Ctrl+Z": "/2", // halves tick interval
"Ctrl+X": "*2" // doubles tick interval
"Ctrl+Z": "0.5s", // sets tick interval to 0.5s
"Ctrl+X": "600s" // sets tick interval to 600s
}
}

Closing this since community mods are discontinued. All TimeSpeed changes have been merged into the original repository.


[AIRFLOW-XXX] Fix Minor issues with Azure Cosmos Operator

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:
Fixed Documentation in integration.rst
Fixed Incorrect type in docstring of AzureCosmosInsertDocumentOperator
Added the Hook, Sensor and Operator in code.rst
Updated the name of example DAG and its filename to follow the convention

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.
All the public functions and the classes in the PR contain docstrings that explain what it does

Code Quality

[x] Passes flake8

thanks @kaxil, cc @tmiller-msft , btw, I can't close others jira with my current account, do I need to file any specific request to apache for that?

@feng-tao You should have the permission. Can you give it a try on https://issues.apache.org/jira/browse/AIRFLOW-3408 . Click on Resolve Issue

This is what I see for a jira filed/assigned by others.

@feng-tao Hmm.. that is strange. Raise a ticket with Apache-Infra to give you permissions to Resolve Issues

Codecov Report

Merging #4289 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4289   +/-   ##
=======================================
  Coverage   78.08%   78.08%
=======================================
  Files         201      201
  Lines       16462    16462
=======================================
  Hits        12854    12854
  Misses       3608     3608

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 788bd6f...da1511b. Read the comment docs.

@feng-tao Can you review this one - has minor changes :-)

lgtm


Custom dataset and pretrained weights

HI,
im a newbie to deep learning.i want to train my own dataset and evaluate it.Can u elaborate on how it can be done and how do i pass the model path,my query and target images to the evaluation script?

Hi, you can follow these steps:

Create your custom dataset in datasets folder (you may take mini_imagenet as a reference)
Create your custom config and write down the args for building the dataset (you may take configs/train_classifier_mini.yaml as a reference)
Run the code

If you have the dataset with image folders, it should be more convenient that you can reuse ImageFolder class (see train_classifier_im800.yaml for example), which requires a json file that defines the base classes and novel classes.
The code is sampling tasks during testing, if you want to test a specific task, you may need to feed them directly in the code.
I guess these steps would be a bit challenging for a beginner. Good luck!

Thanks for the instant reply will try it out.I only have a single 12gb GPU will that be sufficient for training the model.

You can try to run the code on your single GPU.
If the memory is not enough, you can try to reduce batch_size/ep_per_batch in configs, or to add gradient accumulation in the code.


Allow to save a list of opened editors in a group and switch between them

VSCode Version: 1.3.1
OS Version: all

There are many times I have a set of open editors in the middle of working on something but need to stop and look at a completely different part of the project.
Currently, I can:

Just open the new set of files I need, which clutters up the open editors
Close my open editors and open the new set of files, which makes it easier to work on the second part but very difficult to get back to the previous state when I need to

It would be nice to be able to save a state of which editors and files are open to retrieve later so I could save the state, close everything, and switch to the new set of files, then easily restore the initial state when I'm finished.
This is my main use case for wanting to be able to open multiple windows. See #7330 #2686

Sounds much like "Working Sets" in Eclipse.

@bpasero It's similar. The feature also exists in Nuclide (Facebook's Atom extension) and it is fairly nice for removing noise in monolithic apps when you're focused on just a portion of it (i.e. frontend vs backend).

This sounds like #13951. Seems there's an experimental extension available.

I noticed https://marketplace.visualstudio.com/items?itemName=eamodio.restore-editors which seems to work - haven't tested it much yet. the experimental extension mentioned by @georgemarrows above looks like https://github.com/devtanc/vscode-tab-hero which didn't look like it went very far.

.sublime-workspace config represents the equivalent functionality in Sublime - saving opened tabs and their properties tied to a project (vs code workspace).
.sublime-project is what vs code now has with the .code-workspace - a way to open previously saved folders in a workspace. Similar implementation as .sublime-workspace will be great - having 2 config files:

one containing opened folders in the workspace (.code-workspace)
one for the tabs and their properties for the same workspace (the missing part)

Then by exporting the workspace you get both files generated. Importing them back should have the choice of restoring the workspace as a whole including both tabs and folders or only one of them.

I'm building VS Code plugin that will remember your whole "workspace" in VS.
In short, everything is based on the “mental snapshots” concept as cornerstone idea. Mental snapshot include:
– last opened files
– windows position, state and order
– breakpoints
– bookmarks
– debug variables etc.
Every “mental snapshot” could be easily restored from plain JSON file. They are easily diffable and could be added to source control to share with entire team. ContextKeeper idea is about to take developer context to the pedestal next to the source code.
You could check out how the big picture looks like at http://contextkeeper.io

Any progress with this? I've been using Save All The Tabs for Visual Studio and having switched to VS Code I'm really missing this functionality.

I would like to be able to save the current state of workspace (such as layout + open editors) by a branch or issue number I am working on.
Currently, VSCode already saves everything and allows us to continue work after restart, so why could it not be saved and restored on demand by name?

+1 I need this.

I found this extension https://github.com/jsaulou/vscode-tasks-context which can create tasks and associate files relevant to those tasks. The best part is It stores the config file at perProject/.vscode/tasks-context.json with relative path. Thus I no longer need to worry about  the change of project name and path.

i think workspace could resolve this question，create different workspace for every project.

One more extension is Tab Groups - similar to Restore Editors, but supports multiple, named, tab groups.

I need this, this will be a very useful feature.

One more comment here to keep it alive! Restore the open file for each task (per git branch) would be awesome. Time saver.

This feature keeps me from switching from Sublime Text 3 to VS Code. I have 20+ projects/workspaces in ST3 in which I have open files of several size (some have 32+ MiB) and I want to save some of my resources by not opening of these files in the background.

This feature keeps me from switching from Sublime Text 3 to VS Code. I have 20+ projects/workspaces in ST3 in which I have open files of several size (some have 32+ MiB) and I want to save some of my resources by not opening of these files in the background.

One more extension is Tab Groups - similar to Restore Editors, but supports multiple, named, tab groups.

Thanks that's exactly what I needed! 👍🏻

I, too, want to see a robust implementation since some of us need to open a bunch of different files every time we work on a project so being able to save the editors (and their position, etc) is quite the time-saver.

I agree. This feature would be very useful, reducing clutter and freeing up more screen space by getting rid of tabs unrelated to the project at hand.

I do look forward to this feature too! I just wonder if VSCode support this, and googling it, this issue comes up. Please considering it.

Apologies if I missed this already being discussed, but one question I had is how does vscode currently "remember" editor group layouts when opening a workspace?
Even if we ignore tabs within editor groups, it seems like all the extensions that try to implement some form of "editor layout saving" can't save the real layout because the window api only provides a list of texteditors, each of which only have an integer viewcolumn as a positional identifier (I'm guessing this is a legacy of the original column-based design before we had horizontal splits).
But this makes it impossible to distinguish between e.g. 3 editor groups split among 2 columns, and the horizontal split being located in either the let or right column. In both cases, looping over vscode.windows.texteditors, the viewColumns will be [1,2,3].
As an aside (and maybe this is a known issue already), if one of those editor groups was just a terminal, it wouldn't even show up in the list of texteditors, and does get lost when vscode reloads, (though it seems like the editor group that should contain the terminal does appear, but then closes before the terminal actually loads).

Keeping this alive, could really use a feature like this, definitely helps with context switching.

I'd love to see this feature, but another extension that works well for this -
https://marketplace.visualstudio.com/items?itemName=suhay.vscode-editor-group-minimizer

This is called task-focused-interface, original idea (afaik) from Mik Kersten, creator of the mylyn project on eclipse ide. Is simply a brilliant idea but poorly promoted the name of the tool in eclipse is 'tasks' which gives you no clue what it is for apart from a todo list. The tools allows you to save 'contexts' (set of opened editors) and switch between them fast so there is less mental friction. Im exited to see this on vscode im even thinking to code this myself if needed

Would like to see this natively in VS Code as well.

For anyone interested this extension works almost the same as the eclipse mylyn tool
https://marketplace.visualstudio.com/items?itemName=marlom.keep-context

Agree this would be very useful natively. Choosing, adding, and learning a plugin is also a context switch, which I don't have time for atm.

See https://github.com/microsoft/vscode/issues/35307 for a related issue with a slightly different trigger in that it depends on git branch.
I do think a native implementation similar to the eclipse mylyn tasks tool would be sufficient for this ask.

I've found this one, and using it for several months:
https://marketplace.visualstudio.com/items?itemName=ctf0.save-editors-layout
this is the best. :]

Im the only wanting this but opened windonws?
I usually work on 3 out of 6 rotating proyects (worksets), so i have 6 open windows (thank god they are remembered when reopening vscode), The problem is when the projects rotate because they are done for the moment, and then later you want them back, it's a pain to remember where these project are to reopen, and worse if on the same say you have to switch on 4 projects to another 4 and then back to another 2.
Also, would be great if the icon would change color depending on the project type or some custom setting for that workspace, algo more great if it would show an aditional bar based on memory usage for that window.


[ENG-6892][eas-json] add Xcode 14.1 image

Checklist

[ ] I've added an entry to CHANGELOG.md if necessary. You can comment this pull request with /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message] and CHANGELOG.md will be updated automatically.

Why
Companion to https://github.com/expo/turtle-v2/pull/1142
How
Add Xcode 14.1 image. Change latest and default tags.
Test plan
Run test builds

/changelog-entry chore Add Xcode 14.1 image to eas-json.


Release Google.Cloud.Monitoring.V3 version 3.1.0

Changes in this release:
New features

Added support for evaluating missing data in AlertPolicy (commit ed778dd)

Created release for Google.Cloud.Monitoring.V3-3.1.0


Envoy: Failed task within macro doesn't stop execution

Macros don't stop execution if one of the tasks returns non-zero code. I'm not sure if this is intended or not but for most of the use cases that I can think of this is not ideal.
If I have a deploy macro that needs to run a few tasks in sequence I would want each task to complete successfully before running the next one. Wouldn't you agree?

Please provide an example.

How about one from Laravel's documentation:
@servers(['web' => '<IP_ADDRESS>'])

@macro('deploy')
    git
    composer
@endmacro

@task('git')
    git pull origin master
@endtask

@task('composer')
    composer install
@endtask

Composer task should not run if git task fails.
I actually found solution to this problem via:
@error
    echo "$task failed";
    exit(1);
@enderror

This satisfies my use case and if no one else is interested we can close this for now.


Update documentation and scripts for alpha.10

Do not merge until after release is posted

Hi @andschwa, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Andy Schwartzmeyer). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

Hi @andschwa, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Andy Schwartzmeyer). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


add createApiKeyInterceptor

I'm not sure the process for updating the changelog and cutting a release

example usage:

const testHub = async (hubRpcEndpoint, ssl) => {
    let interceptors = [createApiKeyInterceptor('YOUR API KEY HERE')];

    let client = ssl
        ? getSSLHubRpcClient(hubRpcEndpoint, {
              interceptors,
          })
        : getInsecureHubRpcClient(hubRpcEndpoint, {
              interceptors,
          });

    let fid = 3;

    let prettyEndpoint = ssl
        ? `https://${hubRpcEndpoint}`
        : `http://${hubRpcEndpoint}`;

    client.$.waitForReady(Date.now() + 5000, async (e) => {
        if (e) {
            console.error(`Failed to connect to ${prettyEndpoint}: ${e}`);
        } else {
            console.log(`Connected to ${prettyEndpoint}`);

            try {
                const castsResult = await client.getCastsByFid({ fid });
                console.log(
                    `${castsResult.value?.messages.length} casts for fid ${fid} from ${prettyEndpoint}`
                );
            } catch (err) {
                console.error(`Error on ${prettyEndpoint}: ${err.message}`);
            }
        }

        client.close();
    });
};

this looks good - one thing, can you add the usage to the README?

is the main readme the right place? I figured there were some actual docs pages that would probably make more sense

doing this in hub-monorepo instead


Add debug logging

What is this feature about?
Debug logs are very useful in examining behavior in all kinds of possible use cases.
This helps in eventual user-encountered bugs.
Additional context/references
Add debug logging like in the Node version:

(just a simple example of logging something)
The log crate would be perfect for this, I don't know any better alternatives.

Is this for just debug logging as we could just add a cfg assertion and print it.

eg
fn debug_print<T: std::fmt::Debug>(msg: T) {
    if cfg!(debug_assertions) {
        println!("{:?}", msg);
    }
}

fn main() {
    debug_print("This will only be printed in debug mode");
}

the log crate would be perfect for this

There's also tracing but that is a lot more complex.

eg

I wouldn't use something like this as the user couldn't control this with their log facade.
Many libraries already use the log create for debug and stuff.

Debug logging has been implemented on #217 with log, it will be further refined as more is implemented. Will close this for now as completed


Final round of docs reading and contributions

I've now almost read all of the new docs, and here are a few more contributions ;)

@olberger I'm back in the office now, any chance to look at my comments above?

Glad you're back with full thrust ;-) Go ahead !


Added Moneyou iDEAL provider

Thanks!

It's released in the new version 1.2.4, you can update your composer packages of your project to get the latest version.


Sign Transaction UI Test

Sign Transaction UI Test

[x] flow for the XDR with one operation that also checks its final signed xdr with two signatures signed from secret keys and signature
[x] flow for the XDR with 3 operations that also checks its final signed xdr with two signatures signed from secret keys and signature
[x] flow for the non transaction enveloper XDR

For Ledgers and Wallet Extension, it checks its happy path - making sure the dropdown works and trezor to open the new link. Ledger opens an extension so i skipped the new tab flow for ledger. Wallet Extension checks to make sure the modal pops up and it lists 6 wallets that it supports.

Preview is available here:http://laboratory-pr1172.previews.kube001.services.stellar-ops.com/

Preview is available here:http://laboratory-pr1172.previews.kube001.services.stellar-ops.com/

Preview is available here:http://laboratory-pr1172.previews.kube001.services.stellar-ops.com/

Preview is available here:http://laboratory-pr1172.previews.kube001.services.stellar-ops.com/


update gitignore.

Coverage remained the same at 99.749% when pulling 4c065bbd7655ea33b5147f8691dbc9a25a3e590d on hsim13372:master into 199dbc3ef4082cc485e82247d5cc1824cffed1bc on cs207-group11:master.

Coverage remained the same at 99.749% when pulling 29dd4f8c661735b9eed2604333ac92f708f0956c on hsim13372:master into 199dbc3ef4082cc485e82247d5cc1824cffed1bc on cs207-group11:master.


Step 5 on 2093: Package discovery and namespace package userguide now ready

Step 5 on #2093
Summary of changes
Created user guide for automatic package discovery and namespace package supported by setuptools. It covers the following aspects in both setup.py and setup.cfg style:

automatic package discovery with find_packages
overview on namespace package
automatic package discovery with find_namespace_package
legacy use of namespace package

The quickstart guide's package discovery section references this file
Pull Request Checklist

[ ] Changes have tests
[ ] News fragment added in changelog.d. See documentation for details

If these looks good I can do the rebasing myself to make merging easier.

This is great, but it misses a third technique for namespace packages, the pkgutil-based design, and I would say that the pkgutil-based design is preferable to the pkg_resources-based design. It might be best to minimize the guidance here to anything setuptools-specific and otherwise defer to the packaging users guide on namespace packages.

thanks for pointing that out @jaraco. In fact I omitted the pkgutilstyle considering that it isn't part of setuptools. Should I briefly mention it and defer to the linked article?
Also just out of curiosity, was there a reason pkg_resource style became so wide-spread when pkgutil seems to offer better compatibility?

Also just out of curiosity, was there a reason pkg_resource style became so wide-spread when pkgutil seems to offer better compatibility?

If I recall correctly, the pkg_resources technique was more compatible with earlier Python versions. I see pkgutil was added in Python 2.3 (2003), so it could be the case that pkg_resources added support for older Pythons. I do believe there were other levels of sophistication that pkg_resources offered, such as support for multi-install environments (on-demand package inclusion), so that may have been another use-case it supported.
I wasn't around at the time and the first technique I encountered was that in setuptools.

thanks for pointing that out @jaraco. In fact I omitted the pkgutilstyle considering that it isn't part of setuptools. Should I briefly mention it and defer to the linked article?

That sounds good to me.

@jaraco I have made the changes and it should be ready for merging:)


FIxing HTTP 406 error while runing the test suite (npm test)

This is to fix issue #95
Solution
I modified the scraping.js file to use more browser-like User-Agent and Accept headers. Here are the key changes:

Added constants for user agent and accept header:
const userAgent = 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36';
const acceptHeader = 'text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8';

Created a getWithHeaders function to make requests with these headers:
function getWithHeaders(url) {
    return preq.get({
        uri: url,
        headers: {
            'User-Agent': userAgent,
            'Accept': acceptHeader
        }
    });
}

Updated all preq.get() calls to use getWithHeaders() instead.

Modified the meta() function calls to include the headers:
return meta({
    uri: url,
    headers: {
        'User-Agent': userAgent,
        'Accept': acceptHeader
    }
})

This should improve the reliability of the test suite, especially when dealing with websites that have stricter requirements for incoming requests.

Hello @mvolz would you please do the PR review for the changes made ?

@mvolz, can you review my PR? I also think a styling lint should be added to help in other future changes. I'm thinking of introducing one to this project. What do you think?

@mvolz, I guess this PR is done


chore: bdd-spring-1586096659 to 0.0.1

chore: Promote bdd-spring-1586096659 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment