Color codes do not work in windows

Reading todo contents is more or less impossible when using 'xterm -bg lemonchiffon', or any bright background.
Is there a way to change or disable colors, without affecting the terminal?

Here's how I disabled colors in case any window users are desperate:
diff --git a/ultralist/screen_printer.go b/ultralist/screen_printer.go
index 7a9c429..4fc459c 100644
--- a/ultralist/screen_printer.go
+++ b/ultralist/screen_printer.go
@@ -37,6 +37,7 @@ type ScreenPrinter struct {

 // NewScreenPrinter creates a new screeen printer.
 func NewScreenPrinter() *ScreenPrinter {
+       color.NoColor = true // disables colorized output
        w := new(tabwriter.Writer)
        w.Init(os.Stdout, 0, 8, 0, '\t', 0)
        formatter := &ScreenPrinter{Writer: w}

If you used go get to install this like I did, you'll find the source in ~\go\src\github.com\ultralist\ultralist. Modify that file, run a go build, then copy the new ultralist.exe to ~\go\bin, and then it should start working without colors immediately.

i don't know the first thing about Go, but i managed to resolve this with the following changes:
diff --git a/ultralist/screen_printer.go b/ultralist/screen_printer.go
index 9e8f89c..acc03ff 100644
--- a/ultralist/screen_printer.go
+++ b/ultralist/screen_printer.go
@@ -7,6 +7,7 @@ import (
        "strconv"
        "strings"
        "time"
+       "text/tabwriter"

        "github.com/cheynewallace/tabby"
        "github.com/fatih/color"
@@ -48,7 +49,7 @@ func (f *ScreenPrinter) Print(groupedTodos *GroupedTodos, printNotes bool) {
        }
        sort.Strings(keys)

-       tabby := tabby.New()
+       tabby := tabby.NewCustom(tabwriter.NewWriter(color.Output, 0, 0, 2, ' ', 0))
        tabby.AddLine()
        for _, key := range keys {
                tabby.AddLine(cyan.Sprint(key))

maybe based on this you could solve this the idiomatic way...

@bothzoli I'll create a PR based upon this change and test it out.

thanks a lot.
i'm not sure how it'd affect other OS-s, and also i know almost nothing about Go that's why i didn't open a PR myself :)
but i hope you'll be able to resolve this issue with the above info.

@bothzoli give that PR a review.  if it looks good I'll merge it and build a release!

@00001 @cvrn @bothzoli @robertpateii just released 0.9.4 which includes this fix https://github.com/ultralist/ultralist/releases


Automated tests sometimes claim success on failure.

Describe the bug
Because there is a fundamental layer of robot framework code missing between the robot tests and the python test code, some tests report PASS when FAIL should be reported.
Application: Test Automation
Module/Network: N/A
To Reproduce
No need to reproduce, I will fix this myself.
Desktop (please complete the following information):

OS: Windows 10 Pro  20H2
Version 2021-06-05 master

Add any other context about the problem here.

All automated tests have now been rewritten to properly fail when needed.

GREAT!
Numerous technical issues are keeping me from trying it out and making AGI progress but I should be back up in a few weeks.
Charlie
Charlie


[PS UI] Componentize Tabbar

Description
Componentize Tabbar on Permission System in Figma
Technical Details

Componentize Tabbar component
Use DS rules, colors, spacing, typography
Original PS UI should use this component

Acceptance Criteria

Component should be identifiable in Figma
Original PS UI should use this component

References

Figma - https://www.figma.com/file/LRpO3E6SFcNs6KXCfolwyM/Permissions-System---Intermediate-Design?node-id=51%3A2641

This is tracked in https://github.com/MetaMask/design-tokens/issues/52


v7 behaviour

Deployer version:
v7.0.0-beta.13
Deployment OS:
linux

laravel project
on version 6 it tried to build locally and uploaded to server but version 7 is completely different
v.6.8.0
blackout@Workstation /srv/http/deployer % vendor/bin/dep deploy production -vvv
➤ Executing task whatBranch
Branch [master]
✔ Ok [1s 186ms]
➤ Executing task build
➤ Executing task deploy:prepare
[localhost] > echo $0
[localhost] < sh
[localhost] > if [ ! -d /srv/http/deployer/.build ]; then mkdir -p /srv/http/deployer/.build; fi
[localhost] > if [ ! -L /srv/http/deployer/.build/current ] && [ -d /srv/http/deployer/.build/current ]; then echo 'true'; fi
[localhost] > cd /srv/http/deployer/.build && if [ ! -d .dep ]; then mkdir .dep; fi
[localhost] > cd /srv/http/deployer/.build && if [ ! -d releases ]; then mkdir releases; fi
[localhost] > cd /srv/http/deployer/.build && if [ ! -d shared ]; then mkdir shared; fi
• done on [localhost]
✔ Ok [63ms]
➤ Executing task deploy:release
[localhost] > cd /srv/http/deployer/.build && (if [ -h release ]; then echo 'true'; fi)
[localhost] > cd /srv/http/deployer/.build && (if [ -d releases ] && [ "$(ls -A releases)" ]; then echo 'true'; fi)
[localhost] > cd /srv/http/deployer/.build && (if [ -d /srv/http/deployer/.build/releases/1 ]; then echo 'true'; fi)
[localhost] > cd /srv/http/deployer/.build && (date +"%Y%m%d%H%M%S")
[localhost] <<PHONE_NUMBER>5815
[localhost] > cd /srv/http/deployer/.build && (echo '20210216155815,1' >> .dep/releases)
[localhost] > cd /srv/http/deployer/.build && (mkdir /srv/http/deployer/.build/releases/1)
[localhost] > cd /srv/http/deployer/.build && (if [[ $(man ln 2>&1 || ln -h 2>&1 || ln --help 2>&1) =~ '--relative' ]]; then echo 'true'; fi)
[localhost] < true
[localhost] > cd /srv/http/deployer/.build && (ln -nfs --relative /srv/http/deployer/.build/releases/1 /srv/http/deployer/.build/release)
• done on [localhost]
✔ Ok [95ms]
➤ Executing task deploy:update_code
[localhost] > command -v 'git' || which 'git' || type -p 'git'
[localhost] < /usr/bin/git
[localhost] > /usr/bin/git version
[localhost] < git version 2.30.1
[localhost] > cd /srv/http/deployer/.build && (if [ -h /srv/http/deployer/.build/release ]; then echo 'true'; fi)
[localhost] < true
[localhost] > cd /srv/http/deployer/.build && (readlink /srv/http/deployer/.build/release)
[localhost] < releases/1
[localhost] > cd /srv/http/deployer/.build && (/usr/bin/git clone -b "master"  --recursive<EMAIL_ADDRESS>/srv/http/deployer/.build/releases/1 2>&1)
Cloning into '/srv/http/deployer/.build/releases/1'...

on version 7
it tries to establish ssh connection and run everything on the server
it creates ControlPath=/home/blackout/.ssh/deployer_apps.vm which is total B$
1 blackout@Workstation /srv/http/deployer (git)-[develop] % vendor/bin/dep deploy -vvv
Select hosts: (comma separated)
  [0] app.
  [1] demo
 > 1
[demo] /usr/bin/php /srv/http/deployer/vendor/deployer/deployer/bin/dep connect --host demo --decorated -vvv
[demo] ssh -O check  -A -o ControlMaster=auto -o ControlPersist=60 -o ControlPath=/home/blackout/.ssh/deployer_apps.vm echo 2>&1
[demo] Master running (pid=60209)
task whatBranch
[demo] /usr/bin/php /srv/http/deployer/vendor/deployer/deployer/bin/dep worker --task whatBranch --host demo. --port 39465 --decorated -vvv
[demo] Branch [master]
NULL
task deploy:failed
[demo] /usr/bin/php /srv/http/deployer/vendor/deployer/deployer/bin/dep worker --task deploy:failed --host demo. --port 39465 --decorated -vvv
done on demo
done deploy:failed 123ms
task deploy:unlock
[demo] /usr/bin/php /srv/http/deployer/vendor/deployer/deployer/bin/dep worker --task deploy:unlock --host demo --port 39465 --decorated -vvv
[demo] ssh -O check  -A -o ControlMaster=auto -o ControlPersist=60 -o ControlPath=/home/blackout/.ssh/deployer_apps.vm echo 2>&1
[demo] Master running (pid=60209)
[demo] ssh  -A -o ControlMaster=auto -o ControlPersist=60 -o ControlPath=/home/blackout/.ssh/deployer_apps.vm apps.vm  ': 8674d4c94690577957ae; bash -ls; printf  $?;'
[demo] run rm -f /var/www/demo/.dep/deploy.lock
[demo] zsh:1: no matches found:
[demo]  error  in lock.php on line 23:
[demo] exit code -1 (Unknown error)

your example from the Inverntory page
https://deployer.org/docs/examples/inventory.html
is executed as follows
blackout@Workstation /srv/http/deployer (git)-[develop] % vendor/bin/dep deploy
Select hosts: (comma separated)
  [0] project.com
  [1] staging.project.com
 > 0
The authenticity of host 'project.com (<IP_ADDRESS>)' can't be established.

there is strange behavior with the deploy_path..

I didn’t get it. Please explain in some other way with example of what is needed vs what is going on.


Development

This pull request includes several changes to improve the project's automation, documentation, and translation management. The most important changes include the addition of scripts for translation file management, configuration for Dependabot and CodeQL, and the introduction of new guidelines for deprecation and docstrings.
Automation and Configuration:

.euc.sh: Added a script to extract, update, and compile translation files using pybabel, along with git commands to commit and push the changes.
.github/dependabot.yml: Added configuration for Dependabot to manage version updates for Python packages on a weekly schedule.
.github/workflows/codeql.yml: Added a CodeQL workflow to analyze the codebase for security vulnerabilities on pushes, pull requests, and a weekly schedule.
.github/workflows/secu.yml: Added a security scan workflow using Bandit to check for security issues in the codebase on an hourly schedule, as well as on push and pull request events.

Documentation:

COC/depracating.md: Added detailed guidelines for deprecating features, including procedures for identifying, implementing warnings, notifying users, and providing migration paths.
COC/dosctrings.md: Added comprehensive guidelines for writing consistent and clear docstrings, including structure, examples, and best practices.

These changes aim to enhance the project's maintainability, security, and developer experience.

Closes

#200
#116

[!IMPORTANT]
Also includes other related changes.

Closes #177


feat: add image validation

Enhances
Make sure that you've checked the boxes below before you submit PR:
☑ Tests exist or have been written that cover this particular change.
This PR does the following:

adds a baked in validation to validate a file is a valid image
adds a unit test to cover the added validation
adds translations for image validation
adds tests to cover translations for image validation
updates the README.md document to include the added image validation

Motivation:

Go is increasingly becoming used as a back-end language. File validations are pretty common for many back-end services. This validation will allow developers to easily validate that a file is a valid image.

@go-playground/validator-maintainers

Coverage increased (+0.07%) to 74.244% when pulling d9a2ac4d5d925000ab7491c1b37ce068c6783855 on the-fanan:feat-add-image-validation into 9e2ea4038020b5c7e3802a21cfa4e3afcfdcd276 on go-playground:master.

@hjwk

@hjwk can you help review this please?

Let's ship this please :+1:


Unmatched token is parsed as modifier

Running the following code:
class C {
C(v) {
throw '');
}
}
gives the error message
Can't have modifier ''SymbolToken({)' isn't closed.' here.
The compiler should not complain about modifiers here - instead it should report the error associated with the unmatched token.
The error message is reported from
Parser.expectVarFinalOrConst (sdk/pkg/compiler/lib/src/parser/parser.dart:922:16)

Thank you! I've been looking for a small repo of this kind of error!


[CI] Uncomment /tests/unittests

Currently we don't run these because of how strict they are with changes of simulation results. Because this is stochastic models there is a lot of uncertainty about how it actually look like at the end (within reason).
We should refactor unittests in a way that they will always succeed unless someone makes meaningful change to results (one example would be, if mortality is 0, number of deaths should always be 0).
After that is done, we should uncomment these tests for CI

Fixed by various PRs


riff service invoke hides curl http error responses like 404

It would be helpful if riff service invoke relayed http error responses like 404 to stderr.
e.g. currently you see this with -v but nothing if you don't use -v.
$ pfs service invoke square --text -- -w '\n' -d 7 -v
curl http://<IP_ADDRESS>:32380/ -H 'Host: square.default.example.com' -H 'Content-Type: text/plain' -w '\n' -d 7 -v
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 32380 (#0)
> POST / HTTP/1.1
> Host: square.default.example.com
> User-Agent: curl/7.60.0
> Accept: */*
> Content-Type: text/plain
> Content-Length: 1
>
* upload completely sent off: 1 out of 1 bytes
< HTTP/1.1 404 Not Found
< location: http://square.default.example.com/
< date: Thu, 22 Nov 2018 13:31:05 GMT
< server: envoy
< connection: close
< content-length: 0
<
* Closing connection 0

~/riff/node-fun-square (master)$

Reopening as the current implementation prints every status other than 200.


not working ,where did i go wrong ?

so i followed exactly as discribed and its not working
what can i do and what additional info i should provide to u ?
tks in advance !

thats my discord webhooks
and thats my personal weibo

do you require any additional info ?

Because too many people has been using my code, the website which provides me proxy IP to get weibo info simply blocked heroku server from getting new IP. I will have to get a new proxy method or website to make this work again...

Hi, I'd like to know if the proxy is resolved. Really appreciate your project anyways! @theandychung


Escape repo description and issues' comments

Gitea version (or commit ref): 1.4.1
Git version: 2.11.0
Operating system: Debian Stretch
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist:

Description
Repository description and initialized README.md aren't properly escaped. Same for Issues' comments.
Kind of follow-up of #3486 and others.
Screenshots
I'll provide the links of try.gitea.io.
https://try.gitea.io/Testh1/Issue_report and https://try.gitea.io/explore/repos for description escaping.
https://try.gitea.io/Testh1/Issue_report/issues/1 for comments escaping.
This can also be abused / exploited like this ( see description ): https://try.gitea.io/Testh1/Abuse_example.
For the source code of that see https://try.gitea.io/Testh1/Abuse_example/issues/1.
Note: It's a private repo, so only an admin can visit it: I don't post here for security reasons.

Can you please send details to<EMAIL_ADDRESS>?

@lafriks Done.
I didn't send a mail first because sanitizing the input solved the security part anyway.

Also I see that writing markdown in the description get rendered as markdown in the README. Also a bug.
As I've reported a lot of escaping related stuff here, should I open an issue for each one? I've only updated the title with a more generic one.

Not sure what is happening behind the scenes, probably this comment is already outdated: wrapping all user-provided content in iframe Tag with sandbox attribute would solve this.
The alternative of complete sanitation seems much harder, or even impossible unless allowed html is restricted to a very small subset of static html (and even then the sanitation code would seem fragile and error-prone).

@lafriks @ghost I close this issue assuming that it got already fixed.


improve caching

when having an internet connection, use the lastModified information to check if the resource needs to be downloaded again.

no need to implement, as the caching mostly is for offline mode


Comment on art

As a User I want to Comment on the Art so that I can leave my personal impression, express emotion.
Acceptance Criteria :
-[ ] Create Model
-[ ] Create View
-[ ] Create Url?
-[ ] Create Form
-[ ] The Gallery item id to assign the comments to...

completed


FBP reconstructed tensor no grad

In this example https://github.com/LLNL/LEAP/blob/main/demo_leaptorch/test_project_and_FBP.py, the FBP-reconstructed  tensor f_recon is not differentiable:
    # run filtered back projection
    f_recon = proj.fbp(g_th)
    ......

Output of f_recon.requires_grad is False. I am wondering if I can simply solve this by calling f_recon.requires_grad_() or the fbp implemented in LEAP is no differentiable as it is.

The FBP function in the Projector class is not differentiable, it is just a feature that you can use.  If you want the differentiable version, then there is a class called FBP in leaptorch.py- use this instead.

The FBP function in the Projector class is not differentiable, it is just a feature that you can use. If you want the differentiable version, then there is a class called FBP in leaptorch.py- use this instead.

I checked the gradient of the FBP-reconstructed tensor using class FBP in leaptorch.py as you said, and it works just well. But I encountered some problems:
I am trying to implement a so-called FBP layer in a Pytorch pipeline: an intermediate CT image (maybe reconstructed from sparse-view or limited-view sinogram) is fed into this layer, and then it is projected onto the sinogram domain. The true CT measures on certain angles simply replace the corresponding ones and a filtered back projection will be performed to get a "corrected" CT image.
In this case, Do I have to define two classes: "Projector" and "FBP" in order to make this layer fully differentiable? The same CT geometry and volume settings should be passed twice to them, which is kind of confusing to me. Please kindly correct me if I am wrong. I really appreciate it if you could provide some help.

I'm not sure what the correct implementation should be, but all the building blocks are here for you to implement a custom differentiable layer.

I'm going to close this issue due to lack of activity, but feel free to reopen it if something comes up.


[Feature Request] Allow throughput_stress scenario to run against Cloud.

Is your feature request related to a problem? Please describe.
Currently running the throughput_stress scenario against cloud fails because it tries to add a search attribute using the OperatorService which is not permitted on Cloud.

Describe the solution you'd like
Either an option to skip adding the search attribute, relying on a user to add it, or support for using whichever API is required on Cloud.

Additional context

Fixed in https://github.com/temporalio/omes/pull/75


pip not installing files as executables

totalseg_ and TotalSegmentator are appearing as generic files rather than executables in Python311/Scripts after install via pip. As such, TotalSegmentator is not recognised as a command when executed from the command line (Python311/Scripts is in PATH). Any idea what's going on here?

I am not a windows user, therefore I do not really know the windows details around this.
One user reported that it worked by creating a batch file and inside calling TotalSegmentator:
Basically, one needs to make a batch file (a txt file with extension .bat).
The batch file contains the following line
call C:\ProgramData\Anaconda3\Scripts\activate MySegTool
C:\Users\YourUserName.conda\envs\MySegTool\python C:\Users\YourUserName.conda\envs\MySegTool\Scripts\TotalSegmentator -i %1 -o %2 --fast --body_seg --ml
call deactivate
C:\ProgramData\Anaconda3\Scripts\activate -> replace this folder by the directory where the activate function is found. MySegTool is the environment that you have created and where the totalsegmentator was installed. I created the environment with anaconda and installed TotalSegmentator with pip in that environment. This line is executed to activate the needed environment.
C:\Users\YourUserName.conda\envs\MySegTool\python -> replace by directory where the python.exe in your local environment can be found.
C:\Users\YourUserName.conda\envs\MySegTool\Scripts\ -> should be the directory where the TotalSegmentator script (=actually a python script, but without extension .py) can be found
%1 and %2 are the arguments that can be provided when running from command line...in my case input and output file name. I have preset some settings like --fast etc, but also these can be provided from arguments list when calling the batch file from command line.
How to use the script
open doswindow (cmd), then type:
RunTotalSegmentator inputfilename outputfilename
inputfilename is represented by %1 , outputfilename is represented by %2 within the batch script. Input and outputfilenames with full pathname.

Thanks @wasserth much appreciated 👍


Image Editor: Move Scale Skew Rotate and Spin with CSS Transform

Proposed title of article
Image Editor: Move Scale Skew Rotate and Spin with CSS Transform
Introduction paragraph (2-3 paragraphs):
An image editor will have a range of tools. It can be very basic with only tools like resize, rotate and crop. Or it can be super extensive like Photoshop.
Rotate is a basic and essential tool that is part of any image editor. Let us start with something easy and basic like rotate then add some more essential tools.
I will be using CSS transform property as the core and add JavaScript to enrich the tool.
This can become a basic starter toolkit that can be expanded to a full-fledged image editor in the future.
Key takeaways:

How to edit an image?
A quick glance at CSS transform and image editing
Examples and demo on image editing
Conditions and exceptions on applying transform property
Importance of respecting system preferences

References:
N/A

Good afternoon and thank you for submitting your topic suggestion. @Ethan-155
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

Image Editor Move Scale Skew Rotate and Spin with CSS Transform #3787.pdf
This topic suggestion seems to be published somewhere else.
We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.


Use Twitter Logger for all the logs

It allows us to change per-logger log level from the admin interface

Current coverage is 95.35%

Merging #122 into master will decrease coverage by -0.03% as of 69cd3ba

@@            master    #122   diff @@
======================================
  Files           36      36
  Stmts          888     882     -6
  Branches        40      40
  Methods          0       0
======================================
- Hit            847     841     -6
  Partial          0       0
  Missed          41      41

Review entire Coverage Diff as of 69cd3ba

Powered by Codecov. Updated on successful CI builds.


[Issue] azd pipeline config fails with error [codespaces]

[x] Make sure you've installed the latest version using instructions in the wiki

Output from azd version
Run azd version and copy and paste the output here:
azd version 1.4.1 (commit 1cbed85cf47ed235b5ed31868eda79619525bfcc)
Describe the bug
azd pipeline config and azd pipeline config --auth-type client-credentials both results in an error when ran in Codespaces (though the issue doesn't seem to be directly related):
$ azd pipeline config

Configure your GitHub pipeline

  (✓) Done: Checking current directory for Git repository

ERROR: service principal with client id '82a0a0d9-3a5a-4256-8307-8aa804c039cc' specified in environment variable 'AZURE_PIPELINE_CLIENT_ID' was not found

To Reproduce
I'm trying to setup the pipeline for https://github.com/Azure-Samples/azure-search-openai-javascript

@vhvb1989 can you triage it?

@sinedied , azd pipeline config is not 100% supported from codespaces. See: https://learn.microsoft.com/azure/developer/azure-developer-cli/troubleshoot?tabs=Browser#solution-6
The workaround we have running azd auth login --use-device-code=false should help you to make azd pipeline config work, but it is not recommended.

@vhvb1989 Thanks for the hint! azd pipeline config worked when disabling the device code.
But then even if the setup was successful, our CD still fails with a 401 error: https://github.com/Azure-Samples/azure-search-openai-javascript/actions/runs/6575825133/job/17863849594
Do you have any idea why?
Note that azd up works fine in Codespaces after logging in.

@sinedied , I suspect that the problem is related to the ServicePrincial is not authorized within the Azure-Samples org.
Ideally, you don't want to use the Azure-Samples/repo-name to keep a Github-action, as the sample-repo typically acts as a template.  A user uses the template to create their app instance, and for setting up their own repository where they can add CI.
When we think about a template repo (like Azure-Samples/foo) with a CI for deployment, there are a couple of questions, like:

Who set/maintain the tenant/subscription where the app is deployed
Is FederatedCredential enabled for Azure-Samples org?
Do you want to keep an application instance always live and running (hosting open-ai service, 24x7)?

Maybe try creating your own private repo to test the pipeline. When running azd pipeline config, you can select the option to create a new private repository.


Update to compatibility + extended to fix top level text

The top level attribute "full_text" should be "text" in compatibility mode to maintain backwards compatibility.

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


After update to 2.0.3 receive an error stating that .set does not exist in MockDate

I have the following two lines of code in a TS file
import * as MockDate from 'mockdate';

MockDate.set('12/18/2017');

After updating to 2.0.3 both VSCode and in building phase I receive an error stating:
TS2339: Property 'set' does not exist on type 'typeof import("/path/to/project/node_modules/mockdate/index")'.

If I either downgrade to 2.0.2 or manually remove the index.d.ts file the error goes away

The 2.0.2 --> 2.0.3 change also broke the resetDate API which is now reset.
This was not a backwards-compatible change.

It is because the recently added type definition is wrong. It shouldn't use export default for CommonJS module.exports =

After 2.0.4 still getting error from tsc.
> tsc --noEmit

node_modules/mockdate/index.d.ts:7:67 - error TS1005: '{' expected.

7   set(date: Date | string | number, timezoneOffset?: number): void,
                                                                    ~

BTW why needed index.d.ts here if there is already type @types/mockdate which always works well. index.d.ts here is redundant I suppose, moreover it is not working and prevents from using @types.

@types/* packages are meant to serve type definitions for packages without type defintions. If package maintainer can serve its definitions it's preferred because you don't have to install extra packages.
Though, if maintainers cannot maintain the type definitions it should go @types instead of building into package IMO.

I think maintainers should include their definitions so they are part of codebase and evolve with it.
The issue is that the definition file is incorrect.
this is what we use for overwrite
declare module 'mockdate' {
  export function set(
    date: Date | string | number,
    timezoneOffset?: number
  ): void
  export function reset(): void
}

Yes, that is ideal. But if maintainers cannot or are not capable of updating/correcting/reviewing type definition, it shouldn't be part of this codebase and have to be part of DefinitelyTyped (@types/*) (which is the reason why DefinitelyTyped exists)

Agree with @Hoishin it doesn't look like the maintainers want/can look after TS definitions. In this case, it is better to leave them to the community.
This issue screws up the CI, there are 3 open PRs for this and it they are pretty small to review compared to the benefit they bring.

I know this issue is old, but fwiw I just rewrote the library in TypeScript.

Well, thanks for doing so and letting us know @boblauer!

@boblauer Noice, thanks!


Library?

Any plans to make this a library?
How could the controls be added to an existing Svelte app?

Hi, thanks for the interest.
Well, it is a library, but good observation, I'll add the installation instructions in the README 12765aaabd7a304915aac0c4633d42d570ab4e4d.
The project includes an App.svelte as a demo and as documentation with examples of some of the components it provides.
You can download it from npm (npm i custom-uikit-svelte) and include any component in the script tag of your own .svelte file, just like this:
<script>
  import { Button } from 'custom-uikit-svelte';
</script>

<Button>Click Me!</Button>

Thanks for the reply and added instructions.
I am a long-time .Net developer and moving over to the world of Javascript,
frameworks, bundlers, etc is quite overwhelming.
How you guys figure all this out is truly amazing!
On Mon, Dec 21, 2020 at 1:53 PM cdellacqua<EMAIL_ADDRESS>wrote:

Hi, thanks for the interest.
Well, it is a library, but good observation, I'll add the installation
instructions in the README 12765aa
https://github.com/cdellacqua/custom-uikit-svelte/commit/12765aaabd7a304915aac0c4633d42d570ab4e4d
.
The project includes an App.svelte as a demo and as documentation with
examples of some of the components it provides.
You can download it from npm
https://www.npmjs.com/package/custom-uikit-svelte (npm i
custom-uikit-svelte) and include any component in the script tag of your
own .svelte file, just like this:

Click Me!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cdellacqua/custom-uikit-svelte/issues/1#issuecomment-749167415,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALJU4G2BCNIPFYVXVBN7HL3SV6RVJANCNFSM4VEULEMA
.


Switching between apps on different desktops causes some Win-snapped windows to go back to last known fanzyzone

Microsoft PowerToys version
0.72.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce

Set up fancyzones as listed in the settings images below.
Create fancyzones on multiple monitors and multiple desktops
Snap a window using snap layouts or moving the window to a edge or corner.
Alt-tab or us the quick switcher to switch to an application or window on another desktop.
Switch back to the previous window on the 1st desktop you were on.
The window will lose its assigned place and instead appear in a fancyzone, typically on another monitor.

This is on:

22621.2134
22H2
Windows Feature Experience Pack 1000.22659.1000.0
Windows 11 Pro

Here are the settings:

✔ Expected Behavior
I was expecting window positions to remain the same no matter how they were placed until I manually move them.
❌ Actual Behavior
The windows that have been placed using Windows Snap move to a fancyzone (seemingly) at random.
Other Software
No response

Wait, this might be a separate issue. I'm not using winsnap at all because
of that specific problem in the other case, but I am reporting a slightly
different issue related to only using fancy zones.
On Fri, Nov 1, 2024, 2:51 PM microsoft-github-policy-service[bot] <
@.***> wrote:

Hi! We've identified this issue as a duplicate of another one that already
exists on this Issue Tracker. This specific instance is being closed in
favor of tracking the concern over on the referenced thread. Thanks for
your report!
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/28222#issuecomment-2452415597,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASK63SGEQ7JNYDHGK5NTHDLZ6PETXAVCNFSM6AAAAABRAY6OHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSGQYTKNJZG4
.
You are receiving this because you authored the thread.Message ID:
@.***>


Moving hardcoded className's into defaultProps

Hello.
I have moved hardcoded classes to defaultProps. This modification will allow to use this component with css modules(I want make a wrapper component which should look great in material-ui so I need this kind of flexibility).
Is it ok to do it this way? If so I will update the documentation.
Thank you.

This is cool. But are the core styles broken if you set one of these props? You would be required to set it to the original class name and your new class name

See the changes in version 5. If this is still needed, reopen.


Selection: oxygen regulator

What has to be done
A pressure regulator needs to be selected for oxygen inlet.
Preliminarily, this unit has been ordered for 0.3 enclosed prototypes:
https://www.smcpneumatics.com/IR2010-N02B.html
Some testing should be done to confirm that it works as desired in the correct range.
Question has been raised whether one with integrated gauge might be preferred?
How do you know it has to be done
NEED MORE INFO
Code pointers
Decision should be reflected by update to this page:
https://github.com/RespiraWorks/Ventilator/tree/master/manufacturing/oxygen

Decision should likely be part of design report #787

Decision should likely be part of design report #787

Selection of different unit might affect #937 and/or #938

Selection of different unit might affect #937 and/or #938

Test data from the IR2010-N02B regulator in the CA enclosed vent build has been posted here: #991
Enclosed build sees some drop in performance vs the old pizzabuild data, which is to be expected due to all the extra resistance in the system from the added filters and check valve.  Performance is also basically on par with the old regulator placed in to the new Enclosed build.  We are still meeting the requirement of 60lpm delivery (1000cc/s) but only marginally.  I'm willing to say that this means that we can move forward with a purchase of this regulator, but in the style that is OXYGEN SAFE and includes a gauge: IR2010-N02BG-X1.
However, if we are willing to wait to test it out, based on the datasheet, the smaller cousin of this reg might also work, the IR1010-N01BG-X1

Test data from the IR2010-N02B regulator in the CA enclosed vent build has been posted here: #991
Enclosed build sees some drop in performance vs the old pizzabuild data, which is to be expected due to all the extra resistance in the system from the added filters and check valve.  Performance is also basically on par with the old regulator placed in to the new Enclosed build.  We are still meeting the requirement of 60lpm delivery (1000cc/s) but only marginally.  I'm willing to say that this means that we can move forward with a purchase of this regulator, but in the style that is OXYGEN SAFE and includes a gauge: IR2010-N02BG-X1.
However, if we are willing to wait to test it out, based on the datasheet, the smaller cousin of this reg might also work, the IR1010-N01BG-X1

Latest Data from regulator testing

Tested several configurations on the enclosed build, using Test #1 which is a high flow, high volume test.
Includes testing of the lower intermediate pressure / larger PSOL orifice configuration proposed in #993.
We are getting basically equivalent performance between the old reg and the IR2010.
In addition, we also get equivalent performance with the IR1010 at 45psi.
However, the proposed lower pressure configuration from #993 did not seem to achieve the same performance.  (this will be discussed further on #993)

General observations:

The IR2010 and IR1010 have similar performance at 45psi and both meet the requirement of 60lpm peak flow.
A regulator with flow characteristics similar to either of these should work fine for development going forward (note that this is not a final qualification)
However there is a significant problem with the IR-series regulators.  In normal operation, even when with no gas demand, there is a bleed that vents out of the regulator and is part of the precision control system of the regulator.  This bleed will accumulate 100% oxygen inside the housing of the ventilator and is probably not appropriate for use here.
A regulator with similar characteristics but without this bleed is desired.
Also of note, the IR2010 and IR1010 regulators are not oxygen safe.
SMC makes a line of cleaned regulators, without the bleed, that use fluorinated lubricants.  While they do not certify them as oxygen safe, they are probably closer to what we want.
A possible candidate is the SRH3110-N02.  It has a performance somewhere between the IR2000 and IR1000 series.

This has been suggested by @esc-works:
https://www.smcpneumatics.com/SRH3000-N02.html
With the caveat that there is an additional PSOL? @inceptionev can you add details about that?

Here is the bracket for this regulator: https://www.smcpneumatics.com/B21-1-T1.html

Use an adapter from #996 between regulator and  panel-mount oxygen inlet, and from regulator to PSOL.

Note: in March 31 2021, we purchased 8x of these for oxygen-safe prototyping: SRH3000-N02

Mount bracket CAD no longer available. Item appears to be discontinued.


Can't deploy app

Any suggestion?
`Failed to install the app on the device.
Domain: com.apple.dt.CoreDeviceError
Code: 3002
User Info: {
DVTErrorCreationDateKey = "2023-11-09 15:29:40 +0000";
IDERunOperationFailingWorker = IDEInstallCoreDeviceWorker;
NSURL = "file:///Users/a1121460/Library/Developer/Xcode/DerivedData/CycriptServer-bnmnxthuetkabvbyycwbrhaearce/Build/Products/Debug-iphoneos/CycriptServer.app/";
}
„Cycript“ kann nicht installiert werden
Domain: IXUserPresentableErrorDomain
Code: 1
Failure Reason: Versuche es später noch einmal.
Recovery Suggestion: Failed to load Info.plist from bundle at path /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.YPJk62/extracted/CycriptServer.app/Frameworks/Cycript.framework; Extra info about "/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.YPJk62/extracted/CycriptServer.app/Frameworks/Cycript.framework/Info.plist": Couldn't stat /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.YPJk62/extracted/CycriptServer.app/Frameworks/Cycript.framework/Info.plist: No such file or directory
Failed to load Info.plist from bundle at path /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.YPJk62/extracted/CycriptServer.app/Frameworks/Cycript.framework; Extra info about "/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.YPJk62/extracted/CycriptServer.app/Frameworks/Cycript.framework/Info.plist": Couldn't stat /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.YPJk62/extracted/CycriptServer.app/Frameworks/Cycript.framework/Info.plist: No such file or directory
Domain: MIInstallerErrorDomain
Code: 35
User Info: {
FunctionName = "-[MIBundle _validateWithError:]";
LegacyErrorString = PackageInspectionFailed;
SourceFileLine = 64;
}
Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : {
"device_isCoreDevice" = 1;
"device_model" = "iPad7,3";
"device_osBuild" = "17.1 (21B74)";
"device_platform" = "com.apple.platform.iphoneos";
"dvt_coredevice_version" = "348.1";
"dvt_mobiledevice_version" = "1643.2.4";
"launchSession_schemeCommand" = Run;
"launchSession_state" = 1;
"launchSession_targetArch" = arm64;
"operation_duration_ms" = 1474;
"operation_errorCode" = 35;
"operation_errorDomain" = "com.apple.dt.CoreDeviceError.3002.IXUserPresentableErrorDomain.1.MIInstallerErrorDomain";
"operation_errorWorker" = IDEInstallCoreDeviceWorker;
"operation_name" = IDERunOperationWorkerGroup;
"param_debugger_attachToExtensions" = 0;
"param_debugger_attachToXPC" = 1;
"param_debugger_type" = 3;
"param_destination_isProxy" = 0;
"param_destination_platform" = "com.apple.platform.iphoneos";
"param_diag_MainThreadChecker_stopOnIssue" = 0;
"param_diag_MallocStackLogging_enableDuringAttach" = 0;
"param_diag_MallocStackLogging_enableForXPC" = 1;
"param_diag_allowLocationSimulation" = 1;
"param_diag_checker_tpc_enable" = 1;
"param_diag_gpu_frameCapture_enable" = 0;
"param_diag_gpu_shaderValidation_enable" = 0;
"param_diag_gpu_validation_enable" = 0;
"param_diag_memoryGraphOnResourceException" = 0;
"param_diag_queueDebugging_enable" = 1;
"param_diag_runtimeProfile_generate" = 0;
"param_diag_sanitizer_asan_enable" = 0;
"param_diag_sanitizer_tsan_enable" = 0;
"param_diag_sanitizer_tsan_stopOnIssue" = 0;
"param_diag_sanitizer_ubsan_stopOnIssue" = 0;
"param_diag_showNonLocalizedStrings" = 0;
"param_diag_viewDebugging_enabled" = 1;
"param_diag_viewDebugging_insertDylibOnLaunch" = 1;
"param_install_style" = 0;
"param_launcher_UID" = 2;
"param_launcher_allowDeviceSensorReplayData" = 0;
"param_launcher_kind" = 0;
"param_launcher_style" = 99;
"param_launcher_substyle" = 8192;
"param_runnable_appExtensionHostRunMode" = 0;
"param_runnable_productType" = "com.apple.product-type.application";
"param_structuredConsoleMode" = 1;
"param_testing_launchedForTesting" = 0;
"param_testing_suppressSimulatorApp" = 0;
"param_testing_usingCLI" = 0;
"sdk_canonicalName" = "iphoneos17.0";
"sdk_osVersion" = "17.0";
"sdk_variant" = iphoneos;
}
System Information
macOS Version 14.0 (Build 23A344)
Xcode 15.0.1 (22266) (Build 15A507)
Timestamp: 2023-11-09T16:29:40+01:00`

Interesting- I'm also on macOS 14.0 (23A344), Xcode 15.0.1 (15A507), and I just deployed to iOS 17.1.1.
Did you change the Xcode project at all? There's not supposed to be a framework in the resulting app (it's supposed to be statically linked in).

Ok. I just tried it with a fresh and clean project and now it works.
Should'n the app greets you with an cycript interpreter when connecting? I tried to connect with cycript from my Mac but it does nothing. The iPad where the app is running is jailbroken. I tried different commands
 ./cycript -r <IP_ADDRESS>:31075 - nothing
 ./cycript -r <IP_ADDRESS>:31075 -p 1121 - nothing
 ./cycript -r <IP_ADDRESS>:31075 -p 1121 UIApp - nothing
I hoped that this app will run a valid cycript on my jailbroken iPad. On older devices I ran cycript from saurik cycript_0.9.594_iphoneos-arm.deb but since the codebase is now arm64 it not longer works.
Copying an arm64 version compiled on my Mac to the device runs into an issue that a dylib is missing:
./cycript dyld[4334]: Library not loaded: /usr/lib/libncurses.5.4.dylib   Referenced from: <203C16F8-B7A5-31BA-96B5-9583CA5FBFF5> /private/preboot/15C4E8BD455092F48176EAFD3FF8496C402D0840/jb-JHP37VM6/procursus/var/root/src/cycript   Reason: tried: '/usr/lib/libncurses.5.4.dylib' (no such file), '/usr/lib/libncurses.5.4.dylib' (wrong platform to load into process) zsh: abort      ./cycript
Compiling cycript from source on the device stucks because there is currently no executable version from node.js that will run on it.
nvm install --lts
Installing latest LTS version.
Downloading and installing node v20.9.0...
Downloading https://nodejs.org/dist/v20.9.0/node-v20.9.0-darwin-iPad6,7.tar.xz...
--2023-11-10 07:10:51--  https://nodejs.org/dist/v20.9.0/node-v20.9.0-darwin-iPad6,7.tar.xz
Resolving nodejs.org (nodejs.org)... 2606:4700:10::6814:172e, 2606:4700:10::6814:162e, <IP_ADDRESS>, ...
Connecting to nodejs.org (nodejs.org)|2606:4700:10::6814:172e|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-11-10 07:10:52 ERROR 404: Not Found.

Binary download from https://nodejs.org/dist/v20.9.0/node-v20.9.0-darwin-iPad6,7.tar.xz failed, trying source.
grep: /var/jb/var/root/.nvm/.cache/bin/node-v20.9.0-darwin-iPad6,7/node-v20.9.0-darwin-iPad6,7.tar.xz: No such file or directory
Provided file to checksum does not exist.
Binary download failed, trying source.
Detected that you have 2 CPU core(s)
Number of CPU core(s) less than or equal to 2, running in single-threaded mode
Clang v3.5+ detected! CC or CXX not specified, will use Clang as C/C++ compiler!
Local cache found: ${NVM_DIR}/.cache/src/node-v20.9.0/node-v20.9.0.tar.xz
Checksums match! Using existing downloaded archive ${NVM_DIR}/.cache/src/node-v20.9.0/node-v20.9.0.tar.xz
tar (child): xz: Cannot exec: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
nvm: install v20.9.0 `failed!

Have you any idea how to run cycript on the jailbroken device? I have to less experience in Xcode. Is it possible to compile the cycript framework to a valid cycript arm64 binary by Xcode - so not a full app but only the binary...

Shouldn't the interpreter connect?

Yes. I'm not sure why it's not.

cycript on my jailbroken iPad

if you're jailbroken, installing cycript normally on-device is preferable.
cycript is compiled for arm64 - I think the problem you're having is that the package has not been repackaged for rootless.
I'd try asking about this on the Jailbreak subreddit.

Closing as further issues are unrelated to this project.


update to 18.1

I replaced erlang:now/0 to erlang:timestamp/0.
warn_missing_spec gets in a way of rebar eunit and triq dependency missing

Looks like this is failing all Travis CI tests?
Even the 18.1 test fails with:
disco_worker.erl:243: The call worker_throttle:handle(T::'undefined' | worker_throttle:state()) does not have an opaque term of type queue:queue(_) as 1st argument

@ErikDubbelboer opaque declaration of worker_throttle:state() confuses Dialyzer because the opaque declaration expects to find some structure declaration in its right hand side, not another opaque term
Workaround committed!

Bump. Can this be merged? It seems to have passed your CI on the Erlang 18.1 instance. There's some discussion of "boneyarding" the Disco formula from Homebrew, since only Erlang 18.3 is currently supported in Homebrew core: https://github.com/Homebrew/legacy-homebrew/issues/46780#issuecomment-204744013
For what it's worth, I've opened a PR to Homebrew (https://github.com/Homebrew/homebrew-core/pull/181) applying the patch from this PR, but it's somewhat unlikely to be accepted unless at minimum upstream has expressed an intent to merge the patch being applied.
Also, any word on a new release tag?

For now we've opted to go with #637  over this PR :
https://github.com/Homebrew/homebrew-core/commit/18f6a55ae609ea4c8159e6fd093019972143d558
https://github.com/Homebrew/homebrew-core/pull/181
Please let us know when you decide how to handle Erlang >=18.1 support so we can remove the patching. Thanks.

Pull request #637 was merged. Thanks.

As of the release tag, I'll have to run the regression tests before tagging a release. It will have to happen soon because of the support for Erlang 18.

Great, thanks.


Test examples

Pull request for issue #24 - Add tests/ directory and sample tests.
I have added phpunit tests for the existing index route inside a tests/ directory.
I created a Tests/BaseTestCase class which implements a runApp() function which takes a request method and URI and processes the app and returns the response object.
Hopefully this satisfies the desire for an example test suite that can be extended from, and additionally provides tests for the existing 'functionality' in the skeleton application.
Please let me know if there is anything that could be improved upon here.

I like this a lot. Should we put the test code in tests/functional directory to make it clear that they are not unit tests?

Sounds fair to me, I'll submit some changes. :)

Thanks @maccath! Finally merged :)

:+1:  But have a problem after 9 commits :grin:
PHPUnit ^5.4 only test for PHP 5.6+ but this skeleton (and Slim) only require PHP 5.5+

Ah... are we able to use PHP unit 4.x?

Yup, I have tested this and the tests still work fine - created PR #39.


Fix #3980: Show watermark that docker isn't installed on Containers window instead of UI

Underlying logic + link

👍


Build random fixes 2 v5

v3:
upstream rebased;
fixed issue with in sequence reconfiguration issue - pointed by semaphore;
fixed appent_to typo - pointed by @lpereira;
simplifiled conf.get("defines") + if with conf.get("defines", []) - pointed by @lpereira;
changed the use of var i for non index usaged - pointed by @lpereira;
removed the wanted var/use from dep-resolver - pointed by @lpereira;
s/verbatin/verbatim - pointed by @lpereira;
fix issue with PREFIX changes;
removed patch "avoid log domain..." - pointed by @glima;
v4:
fixed test and bin builds;
fixed issue with !HAVE_DECL_IFLA_INET6_ADDR_GEN_MODE check;
v5
resorted the bin, test build fixes and the DECL_IFLA otherwise semaphore was pointing an intermediate state breakage;

I guess you can close this one now


How can I revert back to GSE2 [?]

The previous version of GSE worked perfectly for me. How can I revert back to GSE2 ?

https://github.com/TimothyLuke/GnomeSequencer-Enhanced/issues/890#issuecomment-872425832


Exception of type 'Microsoft.Mindaro.Client.ManagementClients.CommandExecuteException' when synchronizing files

I am trying to do a deploy to a Devspaces using a helm chart located in another folder. I updated the  azds.json file with the correct location of the chart:
install:
  chart: ../../../../k8s/helm/catalog-api

It worked. Chart did not install because it need an additional values file located in the same folder, so I added a new entry in install.values:
  values:
  - values.dev.yaml?
  - secrets.dev.yaml?
  - ../../../../k8s/helm/inf.yaml

After adding the command azds up fails with "CommandExecuteException":
Using dev space 'default' with target 'edu-devspaces3'
Synchronizing files...Exception of type 'Microsoft.Mindaro.Client.ManagementClients.CommandExecuteException' was thrown.

I tried (with no success):

Use windows backslash instead of unix slash
Use the question mark at the end

Note that If I use an invalid path in the file:
- ../../../../invalid-folder/helm/inf.yaml

I receive the error Synchronizing files...Required values file {0} not found. (so it seems is processing the path)

Thanks for reporting this issue. Our dev team is looking into it.

Hi! Gentle reminder! Would be great if you could share with us if this still repros for you and share the logs if possible.


FEATURE - Support use of existing fragments and code for extension creation

As a developer,
I want to use existing fragments and code for extension creation,
so that I can make use of previous efforts
Description
Creation of extensions shall allow the reuse of existing fragments and code to speed up development.
Reasons for reuse:

Copy code from another project
Use existing code already in project in case of delete/re-create, undo/redo, today only start from scratch is possible as existing code will be cleared and overwritten
Support cases where multiple extension need to share a single fragment or code (e.g. V2 custom columns)

Technical Design
What modules need to be created or enhanced?
How would the functionality be exposed and how can it be consumed?
Acceptance Criteria
GivenWhenThen format (https://martinfowler.com/bliki/GivenWhenThen.html)
Given I have a ready code snippet / fragment
when I create a new extension
then I can use these existing artifacts or let a fresh one being created
Notes
@stefanschreck @tobiasqueck
Tasks

[ ]
[ ] Unit Tests added
[ ] Test Cases defined

What modules need to be created or enhanced?
This is relevant for all extension types that include a fragment, i.e. custom page, custom section and custom column. But the same requirement is also valid for controller coding, thus the solution should be applied to custom actions as well. It must be a general pattern for all extension types.
How would the functionality be exposed and how can it be consumed?
What we discussed are the two options: either have an additional input parameter for controlling the overwrite, or not to introduce such a parameter and generally check the file existence.
Design proposal is to take the second option: for each view or controller, check the existence first, and do not overwrite if the file is there.

Fine, thanks. One additional remark, or special case: if the user passes the control content  in the interface and specifies an existing control by name, the expectation probably is that the content get overwritten. I will program it like this.

@cfg74 Issue can be closed now

@cfg74 does https://github.com/SAP/open-ux-tools/pull/269 sufficiently cover your request?

Lgtm, thanks!


Can't send messages to copilot chat

Type: Bug
Though it was working two days ago now I can no longer send messages in github copilot chat the send button hi lighted in green does not respond and the enter key doesn't work. I can still use copilot with cmd + I but not the chat.

Extension version: 0.12.2
VS Code version: Code - Insiders 1.87.0-insider (1cc266cc82838981034c2baa637f357a83711d5d, 2024-02-22T22:52:59.987Z)
OS version: Darwin arm64 23.3.0
Modes:

System Info

Item
Value

CPUs
Apple M1 Pro (10 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
42, 34, 15

Memory (System)
32.00GB (13.99GB free)

Process Argv
--crash-reporter-id 7808ae11-7f02-4084-9fc2-870122a8abc5 --crash-reporter-id 7808ae11-7f02-4084-9fc2-870122a8abc5

Screen Reader
no

VM
0%

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
vsaa593:30376534
py29gd2263:30784851
c4g48928:30535728
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonidxpt:30768918
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythontestfixt:30866404
pythonregdiag2:30926734
pyreplss1:30879911
pythonmypyd1:30859725
pythoncet0:30859736
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
bf62j303:30968145
pydisww2:30959801
cppperfnew:30963552
d34g3935:30961436
edj9j583:30969294
fegfb526:30952798
7j2b6412:30951517
e3gdj431:30946825
ccp1r6:30958151
pythonaic:30968499

having the same exact problem here

I think copilot went offline yesterday but should be working now.

same here

same

I just updated and restarted vs code and is working as expected

I also have the same problem, uninstalling and reinstalling are still the same, and even if I change my computer, I still cannot use the chat function

same here, and i got suspicious logs in copilot chat output:
[chat] Registration of chat agents failed:,TypeError: na.chat.createChatAgent is not a function

Switching to pre-release version worked for me, as suggested here

I'm experiencing this same behavior.
I've restarted VSC. I've signed out of Github and then signed back in.
I've restarted my laptop. I've checked to make sure I had the latest VSC and github copilot and chat.
Nothing seems to be working currently. If I try to pull up my chat history it only appears for a split second before going back to a blank chat. If I try to type in a new question I can't click to send that question to chat.

When you are using Insiders, please use the latest pre-release version of the extension

@roblourens   I am using the latest VSCode Insiders with the latest pre-release of Copilot and Chat extensions, but am seeing the same issue.
Additionally, I am unable to open any chat history entries. Clicking on the history icon does open the list to select from as expected, but selecting any of them, I just get a flicker of something then a blank grey panel. Is this a known issue?
(total coincidence btw, that I write this minutes after you close the issue)

Experienced this as well this morning, i just update to the new version and reload the new update. It run well now.

I experienced the exact same issue I could't send any messages to copilot chat. The problem was my settings sync wasn't turned on.
How to fix this:
Step 1: Click on settings on the bottom left corner in VS code
Step 2: Click on setting sync it will ask you to sign in with either microsoft or github
step 3: That should direct you back to VS code and the copilot chat should now work again
Step 4: if this still doesn't work try restarting VS code.
Hope this helps :)

same here. tried pre-release and also reenable setting sync


Passing variables during release creation

Is there any way to pass a variable during a release creation (the ones that are "settable during release time")
in a form
az pipelines release create --definition-id=24 --variables "foo=bar"

This kind of blocks us from using az pipelines create - thanks!

Just checking the REST api https://docs.microsoft.com/en-us/rest/api/azure/devops/release/releases/create?view=azure-devops-rest-6.0 and variables are able to be provided.

@EugenMayer: This is not supported yet in the extension will mark this as a feature request.

oh yes please, that would be nice if you added this feature

@matthewacme IMHO I can only encourage you to implement the REST api using your own client - that is what we did. I do not expect this ticket to be anyway fast moving, you might wait for a year or years.
We used a Go based client which we wrapped the REST api with - in the end, a lot of things would have been missing anyway. There is a lot that the client really is not doing or offering.

Hi @EugenMayer, sorry I maintain these extensions in my free time. Meaning that I do not have the time of the world to add new functionalities.
You can always contribute by forking the repo and making a pull request.

Hi @EugenMayer, sorry I maintain these extensions in my free time. Meaning that I do not have the time of the world to add new functionalities.
You can always contribute by forking the repo and making a pull request.

If you have taken the above as an offense, please do not.  I do not expect anything from you and I am not allowed to do so frankly.
It's totally fine that this feature is not implemented at all or very late - no hard feelings. If I would need it, I would implement it. But we decided to go with our own cli entirely and that is why I never contributed.

this is in production


Support newer Exchange servers

With WebDAV support gone in newer Exchange versions, EWS support should be added so newer Exchange servers can be used as well.

Exchange ActiveSync might be easier to add.
We have an old branch with initial EAS support: https://github.com/k9mail/k-9/tree/ms-eas
For more information on EWS vs. EAS:
https://msdn.microsoft.com/en-us/library/office/dn144954(v=exchg.140).aspx

Fair enough, I suggested EWS since ActiveSync need a patent license. Or is that not true for open source projects?

Please ensure this gets fixed before any sort of destructive UI overhaul is committed.

The patent issue requires further research. Where I live there are no software patents, so personally I'm not terribly concerned. But the project is using a lot of services hosted in the US, so this might become an issue.
@ocdtrekkie If you feel the need to provide comments like this, please use the mailing list. Let's use Github issues for technical discussions.

@cketti Aside from my general disagreement that Github isn't the place to discuss when PRs should or shouldn't happen and in what order, I would suggest that if you want to direct people to "the mailing list", a link to the mailing list should likely be available somewhere easily identifiable on Github, or linked in your comment. The repo doesn't seem to have a README file, which would be a good place for such links. Also, the organization here on Github has a Google Code link as it's web URL, which may be worth replacing since Google Code is about to go the way of the dodo.

This:
https://github.com/OfficeDev/ews-java-api
and to a lesser extent perhaps, this:
https://github.com/OfficeDev/Office-365-SDK-for-Android
may be helpful. As far as I can see, MIT and Apache licensing respectively.

The standard Android Email app seems to handle Exchange servers just fine in cases where K9 fails. Wouldn't it be possible to re-use the code from the AOSP?
http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android-apps/4.4_r1/com/android/exchange/ExchangeService.java
Support of Exchange as alternative protocol to IMAP seems important in order to get push mail to work; for those cases where IMAP idle does not work or is not supported by the server. (I am just now suffering from such a case).

Just re-using the code is no longer an option. We're too far apart now. But we can and do take bits and pieces where it makes sense.
In fact the ms-eas branch already does this. It has a file called Eas.java which is ported directly (it includes the copyright headers). We probably want to review the entirety of that codebase for improvements at some point and if we had a large team it would be something someone could do.
Anyway, back on topic:
I created a diff between the ms-eas branch and the last point it merged from master, to work out the changes that were done.  The entire codebase has been re-organised into a library module and an app module for example.
Instead I've started manually rebasing changes and trying to work out what needs to be brought in and what we can do without.
I want to minimise the amount of changes being done in a single PR to reduce risk. That means I want to submit PRs which change common code and other stores before I submit the main PR for EAS.

[ ] Introduce the concept of remote names.
[ ] Refactor the MessagingController

Finally, let's not confuse the issue by discussing EWS. If there is a use case for EWS we can create a new issue for that. But from the overview, EAS would seem to be a better choice for an e-mail client: https://msdn.microsoft.com/en-us/library/office/dn144954(v=exchg.140).aspx
Regarding the patents, both Germany and the UK have seen licensing action related to ActiveSync... This is something they appear to care about and enforce: https://www.microsoft.com/en-us/legal/intellectualproperty/mtl/technologylicensing.aspx
I don't particularly want to get sued, so if it turns out this is something we have to pay to license we may have to drop the feature. I expect either the person who merged the code or the person who uploaded the infringing APK would be liable... If we're lucky it's a percentage of revenue ;)

في الأحد، ١٧ ابريل، ٢٠١٦ ٦:١٠ م Philip<EMAIL_ADDRESS>كتب:

Just re-using the code is no longer an option. We're too far apart now.
But we can and do take bits and pieces where it makes sense.
In fact the ms-eas branch already does this. It has a file called Eas.java
which is ported directly (it includes the copyright headers). We probably
want to review the entirety of that codebase for improvements at some point
and if we had a large team it would be something someone could do.
Anyway, back on topic:
I created a diff between the ms-eas branch and the last point it merged
from master, to work out the changes that were done.  The
entire codebase has been re-organised into a library module and an app
module for example.
Instead I've started manually rebasing changes and trying to work out what
needs to be brought in and what we can do without.
I want to minimise the amount of changes being done in a single PR to
reduce risk. That means I want to submit PRs which change common code and
other stores before I submit the main PR for EAS.

Introduce the concept of remote names.
Refactor the MessagingController

Finally, let's not confuse the issue by discussing EWS. If there is a use
case for EWS we can create a new issue for that. But from the overview, EAS
would seem to be a better choice for an e-mail client:
https://msdn.microsoft.com/en-us/library/office/dn144954(v=exchg.140).aspx
Regarding the patents, both Germany
http://www.fosspatents.com/2013/02/googles-activesync-license-turns-german.html
and the UK
http://www.eplawpatentblog.com/eplaw/2013/01/uk-microsoft-v-motorola.html
have seen licensing action related to ActiveSync... This is something they
appear to care about and enforce:
https://www.microsoft.com/en-us/legal/intellectualproperty/mtl/technologylicensing.aspx
I don't particularly want to get sued, so if it turns out this is
something we have to pay to license we may have to drop the feature. I
expect either the person who merged the code or the person who uploaded the
infringing APK would be liable... If we're lucky it's a percentage of
revenue ;)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/k9mail/k-9/issues/606#issuecomment-211042212

I've still not got a response from Microsoft :(
However my work is moving to the Microsoft cloud platform so I will probably have a test platform (and a large incentive to develop this) soon...

The  response from Microsoft is 'sign the NDA'..
Just to summarise the situation:

Implementation of EAS is available in Android source code under a reasonable copyright licence
There's a branch of code implementing much of the functionality
EAS is however protected by patents
All Western handset manufacturers have licenced the patent for the email app.
This is one of the main way Microsoft makes money on Android.
Expecting a free licence for EAS on Android is therefore unlikely - the handset manufacturers might be tempted to drop their apps.
In any case asking for a patent licence involves signing an NDA saying you won't disclose the licensing terms outside your company.
This can't really reasonably apply to an open source team, especially one like this where there's no actual incorporated company
Hence it's legally complicated at best to sign the NDA let alone any subsequent patent license.

I live in the UK. @cketti lives in Germany. In both of these countries EAS-related patent activity has been enforced. As such I can't imagine us being able to merge the code and ship an app based on it.
If individuals want to maintain forks of K-9 that support EAS that's fine but I am sure Microsoft would shut down an unlicensed app.
I'm proposing to close this Won't Fix until the patents expire

Do you have any evidence that EAS-related patents have been enforced in court anywhere in the EU?

(This was discussed on IRC - there is some enforcement of an EAS patent outside the EU, and a license to the patent is referenced in a successful defence against another patent lawsuit)
We've not yet decided on a direction for this I think...

As a note - Office 365 supports IMAP (but not IMAP push). So this has slipped down my priority list (because work email still worked).

Not sure I understand this ticket. It suggests to add support for EWS (Exchange Web Services) but very quickly moves on to discuss various issues around EAS (Exchange Active Sync). The latter is riddled with licensing questions, the former has a liberal license.
As far as I understand the only downside to using EWS instead of EAS is that it is a little heavier on the bandwidth. Still this would be better than the current scenario where K-9 is left practically without support for corporate-type Exchange-based email.

I don't much mind which way whoever picks this up decides to take it. If we ended up with both in the long run that would not be a bad thing if they were both maintained. But it needs time from a developer who has a motivation to develop it (i.e. has an Exchange set-up that doesn't support IMAP as well).

I would very appreciate it to see EWS support in K-9 someday. I left M$ for business completely especially Outlook after I got Evolution with EWS working to browse my Exchange account.
For testing purpose and implementing EWS into K-9 you could also get an office365.com account. There are offers per year or per month, basic "Personal" account is 7 EUR per month, for free for testing. Maybe that is useful.
You can also ask the Evolution devs in #evolution on irc.gimp.org

Hmm, given Evolution supports EWS we should probably go down that route first. I do have an Office 365 work account.
Of course building a new store in K-9 from scratch will take a decently long time. I likely won't have time to work on this for a fair while.

Given that the upgrade to Exchange 2016 at work has left the stock Gmail app to not work correctly for me, I would like to start working on this.  I'm guessing Ubuntu would be the best platform to work on (although I only have Windows at my disposal right now due to work requirements).

How about re-using DavMail's code for EWS?
https://sourceforge.net/p/davmail/news/2016/11/davmail-473-released/

Gnome Evolution supports quite well exchange > 2010 (email, tasks, calendar, …). Maybe some code could be taken from here ?

Actually, I suspect K-9 would be better off starting from https://github.com/alipov/ews-android-api which is a fork and port to Android of https://github.com/OfficeDev/ews-java-api  -- I suspect this would be much easier to use (and start with) than the C code of EVO.
The ews-android-api is released under the MIT License, as is its upstream.

I started looking at this: https://github.com/k9mail/k-9/tree/ews
I've encountered https://github.com/OfficeDev/ews-java-api/issues/353 while testing locally. I'm probably going to have to fork the repo, then fork the android repo which submodules the main repo, then use that...

Just curious: what's the current state? The last few comments do really sound promising. 😃
I know that you guys are devoting your free-time to this and we better be patient. I'm very thankful for your hard work! I just want to kindly ask wether there's any further progress as this has become a necessary feature for me as well.
(I really don't want to have that MS Outlook app sitting around on my phone, if possible... 😅)

I spent a while trying to work around the bug I mentioned above which kind of stymied my progress. I think you have to replace the character stream reader and filter out the invalid characters which is a horribly involved bit of work. It's kind of lame that the repository doesn't get more support from Microsoft (but not that surprising given they really want you to use EAS).

@philipwhiuk Did you have any more success since December ?

Is this feature aborted? I am really interested in having k-9 work with my company`s email... they will all switch to m$...

Could we pull in the EWS for Android code to make this happen?
https://github.com/faisons/EWS-For-Android

Some nice update..
EWS for Exchange Online is deprecated so (will be turned off by Oct. 2020).. to support Exchange Online & On-Premise either EAS has to be implemented or two new store providers: EWS & MS Graph

Reference:
https://blogs.technet.microsoft.com/exchange/2018/07/03/upcoming-changes-to-exchange-web-services-ews-api-for-office-365/

fodinabor<EMAIL_ADDRESS>writes:

Some nice update..
EWS for Exchange Online is deprecated so (will be turned off by Oct. 2020)..
to support Exchange Online & On-Premise either EAS has to be implemented or
two new store providers: EWS & MS Graph

Actually, you did not properly read the reference.  Yes, EWS is
deprecated, but it will continue to be run in production and get
security updates.  It's only BASIC AUTHENTICATION that is being turned
off by October 2020 (in lieu of OAuth tokens).  They specifically say in
their FAQ that if your app is using OAuth then it will continue to work
after October 2020.

yeah, sorry.. I remember .. but if I'm right, then OAuth is not supported for on-premise?
So it's just two different auth providers to use..
But yeah.. still EWS is deprecated... and as far as I know MS pushing the Graph API really hard (had some discussions about Graph with MS employees), I could imagine, the next step will be disabling EWS for online totally.. but yeah - we'll have some time until then ;-)
so.. any way one could get the begun work fixed up and working? Or should one start from the base again?

There are lots of company still using old-school Exchange server and EWS
still an option for they. It would be better to put this into another
issue, i.g. OAuth2 support for Outlook, or MS Graph support for Office 365.
BTW, AFAIK, OAuth2 support for Gmail still in a very early stage, right?

afaik /e/'s fork implemented this, leading to being tested by some users right now: https://gitlab.e.foundation/e/apps/Mail/

https://azure.microsoft.com/en-us/blog/microsoft-joins-open-invention-network-to-help-protect-linux-and-open-source/
guess it will need some more research... but... possibly we could support active sync now?

@chromy234test
There is an old branch with EAS support:
https://github.com/k9mail/k-9/blob/ms-eas/src/com/fsck/k9/mail/store/EasStore.java
I'm also currently playing a little bit with this:
https://github.com/wiomoc/k-9/tree/ExchangeASBackend

For a contract I integrated the EAS implementation from AOSP into the K-9 code base. Parts of it are available under the Apache 2.0 license here: https://github.com/cketti/k-9/tree/eas_backend
In practice we had lots of issues with EAS. That, and the fact that EAS is not really an open standard made me decide not to include it in K-9 Mail.
I'm not generally opposed to adding support for semi-open protocols (although, in hindsight, EWS is probably a better choice for Exchange servers). But currently there are a lot of other issues in K-9 Mail that need to be addressed before I want to start a project like this.
I don't see this changing anytime soon. So I'm closing this issue in the hope that nobody else will start to do a substantial amount of work only to be told it won't get merged afterwards.


Design QA - Active Bets

Loss bets, Won bets, Claimed bets should not appear on Active Bets tab.

looks fixed


Code reorganization. Fixes #19, fixes #21, fixes #23.

fixes #19
fixes #21
fixes #23
Moved AFMulatorOCL_Simple, HighLevelOCL, RelaxOpenCL, fieldOCL and oclUtils to a submodule called ocl and simplified the names of the modules.
Moved AuxMap, CorrectionLoop, Corrector and GeneratorOCL_Simple2 to a submodule called ml and renamed GeneratorOCL_Simple2 to just Generator.
Removed other old versions of GeneratorOCL and AFMulatorOCL.
Renamed GUILJ.py to ppm-gui.

@NikoOinonen please resolve the merging conflicts, so we can merge the PR.
Thanks!

Perhaps I need some instruction, if I should review it, what exactly should I do? Simple checkout on my machine in separate copy of repo? Or can I look on it online on github?

Perhaps I need some instruction, if I should review it, what exactly should I do? Simple checkout on my machine in separate copy of repo? Or can I look on it online on github?

You can do whatever you want to make sure that you are happy with the changes. If simply looking at the changes on Github is enough for you, then that's good too.
Since @yakutovicha already approved, I could merge it, but I'll wait until @ProkopHapala is okay with the changes before merging.

@ProkopHapala, do you know how to approve?

Not sure If I did the right think. I perhaps merged it already. Approve is something else ?

@ProkopHapala It got merged already. I might have been better if it was squash and merge, but it's fine. It does not show an approval from you for me, though.

Yeah, Prokop just merged it directly.


Kestrel vs Beta8

dnx kestrel throws an exception when running beta 8, and my project.json showing beta8 "Microsoft.AspNet.Server.Kestrel": "1.0.0-beta8", - notably, it will run if I have beta7 in there for Kestrel, even though dnx is beta8. Running mono on Mac OS X Yosemite. I recall seeing something about the commands section being different for the kestrel commands, as a possible solution, but I can't seem to find it. Anyway, here's the first part of the exception:
System.FormatException: Could not parse the JSON file. Error on line number '0': 'server.urls=http://localhost:5000'. ---> Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: s. Path '', line 0, position 0. I can post the rest if anyone is interested.

Publish your project to a github repo

Here's the repo: https://github.com/rhires/kestrelvsbeta8. I realize that I didn't previously mention that I used yeoman to scaffold the thing, then went in and changed the dependencies to beta8 from beta7, and ran a dnu restore...

hosting.ini has changed to hosting.json.

Cool. What would be the proper format for the info already in that file? I guessed 	"server.urls":"http://localhost:5000" and it seems to be right, but when I updated yeoman, and it scaffolded out a new project, it doesn't bother with hosting.anything, and instead it seems that the server.urls is hard coded somewhere, because I can't see where it would be configured (I looked in all the different files that the scaffold provides...), and yet it still opens port 5000. As I stray off topic a bit (because yeoman is suggested by, but isn't controlled by, the aspnet folks), I also notice that the yeoman beta8 scaffold merely includes "web" as its command to activate kestrel, and no configuration.
Anyway, I'm able to go my merry way since I can run kestrel again. :-) Thanks!

http://localhost:5000/ is the default address if none are provided. You can specify server.urls in the command line, in the project.json command, in the Microsoft.AspNet.Hosting.json config file, in an environment variable, etc..


The problem of perfect match

Vue version: 3.2.47
Naive version: 2.34.3
For the first, thank you, guys, for the excellent work here, I'm really glad to know the incredible works that you are working, is it common case to build design system thinking in perfect component matches, it means that maybe the users will not break the usability the design and bla bla, but this case is not perfect for the world, the person who developed this filter maybe feel a little lost when he starts to mix tabs with feature flags, render less components, even for a simple case when I want to evolve the tab with a router-link.
So the question is, guys, can we remove these filters? I see some other filters applied in other components and I find it only turns the components difficult to reusable or just to customize something extended.
https://github.com/tusen-ai/naive-ui/blob/52d66c4e61b04b1602d7015caa9120b781f1c1ab/src/tabs/src/Tabs.tsx#L653
Right now my solution consists of:

Is it not good but I think it is enough.

I'm sorry for this pattern. If it's possible to redevelop the library, I'll never try to extract data from VNode.
I took this pattern only to make API looks nice in common use case. However this pattern is not maintainable. It hooks too much into the framework (like vue, react) implementation.
These filters are required to make component work in current API pattern, so we are not able to move it.

API should better not be exposed in view layer, but in data layer.


any chance of making SlackRtmConnectionActor not private?

I have a custom SlackRtmConnection and it stopped working as the actor was made private.

Hi, sorry for breaking your use case! My intention was to improve the api surface by hiding what I considered to be more implementation details and not part of the public facing api. I'm currently in the process of adding much more robust documentation, so that the generated scaldoc will be much more useful for new and existing users.
Are you constructing the SlackRtmConnectionActor directly in your code, or are you attempting to grab it from a SlackRtmClient (e.g rtmClient.actor)? If it's the latter case, I'd be willing to make the actor field on SlackRtmClient non-private. If it's the former case would you consider putting your custom SlackRtmConnection inside the slack.rtm package namespace to which it's limited to?
Also, if your willing to share, I'm curious what you're doing in your custom SlackRtmConnection. If there's anything you think might be an improvement that could be made to the one provided in this library so that it would better meet your needs.
Sorry again for the inconvenience!

I actually re-wrote/copied SlackRtmClient.

I added extra commands (list of Channels & list of Users)

I added a way so that an actor can 'listen' to messages for a specific user/channel. I also 'watch' them, and look for the Terminated message to remove the listener. So I actually moved the 'listeners' to SlackRtmClient from SlackRtmConnectionActor.

I added a way to send an attachment. (I have a web-server built in so I should be able to get the button notificiations/callbacks soon)

my use case here is to to have 1 SlackRTMClient per slack installation, and have multiple bots connect in via it to communicate, with most of the intelligence sitting in other places.
I might even add a command so that I can filter messages with a certain prefix to a specific listener.
(eg. $ XXX to actor X and ! XXXX to actor Y )
and then enable X to spawn a child actor which holds state about the connection and only 'sees' messages it cares about (which is the main part of #2)
I tried moving my SlackRtmClient to slack.rtm, but it still can't see the private SlackRtmConnectionActor for some reason.

I'll write a pull request to get this functionality into the right places in your implementation.
are you 'wed' to using a mutable to hold your listeners or would you prefer this to use context.become() and pass them into the receive function? (I think I have 2 new maps for specific channel/user -> actor & actor -> channel/user mapping.. and probably will add another 2 for user -> actor listen messages).

Thanks, I think these will be useful additions!
I'm not completely tied to using a mutable map to hold the listeners, although it is a fairly simple approach. I haven't taken the approach you mentioned before, but I'm open to it. You would essentially be replacing the current receive function each time a listener is added or removed with a new closure containing new immutable references to the updated listener maps?
Also, FWIW I created a simple project successfully using the SlackRtmConnectionActor directly from the slack.rtm namespace:
https://gist.github.com/7abe262e3c0bb383e65ab97015b23f2e
This may help you get up and running until the above changes are integrated.

A simpler option to add support for listening to specific users/channels might be to either add or enhance the existing HandlerActors in SimpleEventHandlers.scala . Eg:
private[rtm] object MessageHandlerActor {
  def apply(f: (Message) => Unit, channelId: Option[String] = None)(implicit arf: ActorRefFactory): ActorRef = {
    arf.actorOf(Props(new MessageHandlerActor(f, channelId)))
  }
}

private[rtm] class MessageHandlerActor(f: (Message) => Unit, channelId: Option[String]) extends Actor with ActorLogging {
  def receive = {
    case m: Message if channelId.isEmpty || m.channel == channelId.get =>
      try {
        f(m)
      } catch {
        case e: Exception =>
          log.error(e, "Caught exception in message handler")
      }
    case _ =>
  }
}

...
  // in the client
  def onMessageForChannel(channel: String)(f: (Message) => Unit): ActorRef = {
    val handler = MessageHandlerActor(f, Some(state.getChannelForName(channel)))
    addEventListener(handler)
    handler
  }

This might be simpler and wouldn't require multiple listener maps and wouldn't require all filtering to be added in inside the SlackRtmConnectionActor. Additionally this would make it easier to add more of this type of functionality in the future without changing or putting more logic in the Connection Actor each time.

Thanks for the tips.
I remember the other reason I rewrote it.
I made it a separate Actor so I could hold the state in one place, and have either other actors, or the website communicate it. (and it wouldn't know or care).
I think if I didn't do this, I would have to have multiple SlackRTMClient's around the place instead of just the actor reference.

Well apart from not having your additions, you should be able to share the Rtm client around fairly freely as it's mostly thread safe and doesn't maintain any state that another piece of code could manipulate directly. The only real caveat being if another piece of code were to call close.
All pieces of code would be communicating directly with the actor via the client and as such wouldn't affect each other in any way.
Although it's very possible that your use case is much more nuanced in ways that I'm not fully aware of. Is your project open source anywhere? Either way, I still think a lot of the changes you mentioned would be beneficial to the project.

the code is here - https://github.com/kryton/SlackBot2
It's still quite raw.
the aim of it is:

to be able to talk to multiple Slack instances at one time
to be able to talk to multiple external systems (for now our Incident DB, and commerce site, but will also be Jira, and other things)
and communicate via various messaging systems. (eg FB, WeChat, MicrosoftTeam etc)


Wrong URL in repository meta description

In repository meta description, you have
PHP client for the Tinify API. http://tinify.com/developers
Clicking that url leads me to https://tinify.com/ instead of https://tinify.com/developers

Thanks! We have updated the link.


get order review

i have success set billing,shipping,payment on postman, but when i get order review its return null, and saveOrder always send me to homepage

You can read at the source of the project by yourself , I have not been concerned about the dynamic magneto, and now updated a lot of magento's project

i don't understood php language


DateTimeField doesn't work as expected

Hi,
The following component show me "invalid date". Any problem with that?

The second question is how to get the input value if I use the default value which means no change event is issued?

The only way I could get things working was by passing a moment object via dateTime props. The README says it should be a string, but that did not work for me.
About your second question, I think PR #44  export a getValue method.

could we also remove in the components the datetime props to be a string if it actually requires a moment object?
Thanks


As a developer I want to differentiate test servers using theming

Decided this was not worth the effort. Would need pipeline and some kind of css packing


Suggest to include PowerfulSeal in the list

I would like to suggest to include PowerfulSeal in the list:

PowerfulSeal adds chaos to your Kubernetes clusters, so that you can detect problems in your systems as early as possible. It kills targeted pods and takes VMs up and down.

Full disclosure: I'm the main contributor, and I presented the tool last week at Kubecon 2017 North America.
Tell me what you think :-)

Hi @seeker89,
Thanks for the contribution, can you please rebase the branch so I can merge it?
Thanks,
Pavlos

@dastergon should be good to go 👍

Thanks 👍


[Generator] - Screen generator

Checklist
Ignite Base Change

[ ] Works on iOS/Android/XDE
[ ] Tests Pass (run: npm run test)
[ ] Code is StandardJS compliant (run: npm run lint)

Generator Change

[x] package.json lists all generators under "files"
[x] I have run and tested npm compile with latest src

CLI Change

[ ] I have run and tested npm compile with latest src

ability to generate screens, also cleaned up components.

Superb.


Installation stops at "Installing Packages: Configuring netfilter-persistent"

It's on a fresh reboot on Raspbian, just ran update & upgrade.
I ran the command multiple times: same issue that it stops.
The is a pi that has installed a lot of stuff like apache, mySQL.
Is a wrong configuration on the pi making it crash?

I re-imaged Raspbian on the pi, and the issue is solved.
I wish next time it would say what was wrong instead of just quitting.


added detailed post endpoint. Only fetches top level comments. Unit t…

…est added.
Part of #41
Proposed Changes
-Added endpoint for detailed post
-Added a unit test

Looking at the MongoDB docs, I still think we should follow a pattern similar to this and have a 'ref' to the 'Comment'. Doing this, we can automatically fetch all the comments for a post using the .populate() method. What are your thoughts?
https://mongoosejs.com/docs/populate.html

Do we want to leave changing to populate for a later group/issue?

Do we want to leave changing to populate for a later group/issue?

Yeah, I've removed my comment also. I realised if we want to support multi nested comments in the future as well, I"m not sure if the populate method will still work.

@andrewh318 are you happy with the work Kazuki has done? Am I merge it into the master?

@andrewh318 are you happy with the work Kazuki has done? Am I merge it into the master?

Yup, LGTM!


Implement Strategy Pattern for the GitHubRepoStore

Technical Story
When receiving an alert from the Alerter the AlertStore performs the following:

It stores the alert in Mongo
Stores the state of the alerted metric inside Redis. This is then used by the API/UI to display the problems in the Overview Dashboard.

Following the SRP (single responsibility principle) the AlertStore should perform one job only, that being of storing the alert in Mongo. Therefore, we need to create another component which continuously checks the values of each metric and compares them to the alertable thresholds/conditions.
In order to do this change we need to perform the following tasks:

Remove metric state storing logic from the AlertStore
Remove internal alerts mechanism as it would no longer be needed
Develop the MetricsStateStore by integrating each monitorable in a granular way using the Strategy pattern

Description
The aim of this ticket is to implement the Strategy Pattern for storing the GitHub repos' metric state. By using the Strategy Pattern we would be able to easily switch between storing strategies in the MetricStore, depending on what type of transformed data we are receiving
Resources:

https://refactoring.guru/design-patterns/strategy/python/example
https://auth0.com/blog/strategy-design-pattern-in-python/

Requirements
To achieve the aims of this ticket you need to implement a strategy that encapsulates the storing of GitHub repo metrics. The following code snippet can be used as an example:
class MetricStateStorer:
    """
    This is the Context class,  it defines the interface of interest to clients.
    """

    def __init__(self, strategy: MetricStateStoringStrategy) -> None:
        """
        Usually, the Context accepts a strategy through the constructor, but
        also provides a setter to change it at runtime.
        """

        self._strategy = strategy

    @property
    def strategy(self) -> MetricStateStoringStrategy:
        """
        The Context maintains a reference to one of the Strategy objects. The
        Context does not know the concrete class of a strategy. It should work
        with all strategies via the Strategy interface.
        """

        return self._strategy

    @strategy.setter
    def strategy(self, strategy: MetricStateStoringStrategy) -> None:
        """
        Usually, the Context allows replacing a Strategy object at runtime.
        """

        self._strategy = strategy

    def store(self, transformed_data: TransformedData, alerts_config: AlertsConfigs) -> None:
        """
        The Context delegates some work to the Strategy object instead of
        implementing multiple versions of the algorithm on its own.
        """

        self._strategy.store(transformed_data, alerts_config)

class MetricStateStoringStrategy(ABC):
    """
    The Strategy interface declares operations common to all supported versions
    of some algorithm.

    The Context uses this interface to call the algorithm defined by Concrete
    Strategies.
    """

   @abstractmethod
    def store(self,  transformed_data: TransformedData, alerts_config: AlertsConfigs) -> None:
        pass

class GitHubRepoMetricStateStoringStrategy(MetricStateStoringStrategy):
    def __init__():
        redis = Redis('localhost')

    def store(self, transformed_data: GitHubRepoTransformedData, alerts_config: GitHubRepoAlertsConfigs) -> None:
        github_repo_metric_state_storing_helper(transformed_data, alerts_config, redis)

Acceptance criteria
Scenario: The GitHubRepoStore storing procedure should satisfy the Strategy pattern

Another option is to implement the Strategy Pattern on the Existing GitHubRepoStore and implement two abstract algorithms for the context class, store_metric_state and store_metric_value


Possible solutions:

Give DK a modifier that makes him take 80% less damage.
 Maybe also passively increase his attack speed and damage for this section specifically.


Error to open browser

Hello, thank you for your hard work! I am having a minor issue, with Live Server 1.6.5. When I open live server it gives me the "Error to open browser"  It does work, just does not open the window like it should. I have to open the browser of my choice manually and go to the http://localhost:5500/.  I am on Chromium Version 59.0.3071.109 (Developer Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit).
Making a .vscode folder with settings.json file to Firefox has the same result. index.html is at the root of the folder and not inside any other folders.
{
"liveServer.settings.CustomBrowser" : "firefox"
}

ok! I got your problem! I need a few more information.

Is the chrome working for you?
Have you change anything to this settings - liveServer.settings.AdvanceCustomBrowserCmdLine:null?

I tried from my LINUX MINT. It is working.
Make a sure that, you have not chnaged this settings liveServer.settings.AdvanceCustomBrowserCmdLine.
And what about when you open terminal and enter 'firefox' .... does the firefox get started?

my file under C:\Users\xiangxiang\Documents>  got the error
in other dirctory is ok

Hi @cobola... Is the related to Live Server?

yes ,Live Server

sorry, I don't get that. Are you facing same issue?

@ritwickdey thank you so much for the work!  No it was a new install to test coding on Ubuntu. I did not make any changes to vs code or live server. Firefox launched from command line just fine. Chrome kept freezing at odd times so I installed Chromium and that was freeze free. I have gone back to VS Code on Windows 10 as my main OS instead of fighting with it and Live Server 1.6.5 works perfectly. If you have tested it on Mint and it works I believe you.  If @cobola has no issue, you may close this. Thank you again, Don

Sorry,  I can't understand what @cobola is saying. Please say more details about the error. When/How it is occurring?

I will go ahead and mark this closed. I appreciate the work you have done.


Variables is wrong for appwrite.json functions options

Github Doc with the wrong line
For Functions the option for the environment variables in this documentation has an error in its text.
It should be  "vars" and not "variables".
 "functions": [
    {
      "$id": "655dfe83ea1cd538c65c",
      "name": "createDocument",
      "runtime": "node-20.0",
      "execute": ["any"],
      "events": [],
      "schedule": "",
      "timeout": 15,
      "enabled": true,
      "logging": true,
      "entrypoint": "src/main.js",
      "commands": "npm install",
      "ignore": ["node_modules", ".npm"],
      "path": "functions/createDocument",
      "vars": { "apikey": "test" } // not variables
    }
  ]

If tried to deploy with variables the cli throws an error
✗ Error remoteVariables is not defined

Ahh I see the problem. There was a bug introduced in 4.2.0:
https://github.com/appwrite/sdk-for-cli/blob/ae7f9fecbbe5cc0cc702e878fd48cc8559fa18b2/lib/commands/deploy.js#L303-L316


Error in email regex

The email regex, line 58 is not correct for australian email like<EMAIL_ADDRESS>

http://output.jsbin.com/ozeyag/19

It works on this page: http://rickharrison.github.io/validate.js/
I think you are using a custom email regex that might not be working.

Oh sorry, it's a mistak, I don't understand.However I test on your demo website.

I understand, an error appear when I paste the email a space is add at the end<EMAIL_ADDRESS>"
A trim() is not appy on the string.


Change to the ownership of defaultMaterial to allow easier access to it

Fixes https://github.com/playcanvas/engine/issues/3683
Change:

defaultMaterial is created and owned DefaultMaterial class, instead of by the Scene. DefaultMaterial stores one defaultMaterial instance per device. This gets us closer to allow multiple Scenes, while still sharing single defaultMaterial, which some behaviours depend on
this fixes the issue where upon Material getting destroyed, some mesh instances would have null materials. Now they find a defaultMaterial from the device and assign it to the meshInstance.

API Change
The constructor of the Scene now takes the device as a parameter. This is not a breaking change - when this is not passed in, it's obtained from the current application, in the same way other engine classes (like Mesh) do it.

We don't want graphics device to store a material for the same reason we don't want graphics device to store an application!
How about material itself store the map of device->defaultMaterial instead?

We don't want graphics device to store a material for the same reason we don't want graphics device to store an application!
How about material itself store the map of device->defaultMaterial instead?

I agree as mention on the issue ticket.
Ok I'll move it to Material - it does not import pretty much anything, so no big advantage to having a separate class just for this.

DefaultMaterial, is very similar to StandardMaterial semantically. But they are very different things and is not meant to be instantiated.
If it is a namespace, it would be better to be similar to other APIs in the engine that uses namespace convention.
new DefaultMaterial() - definitely won't work.

DefaultMaterial is private class that is not exported to pc namespace .. so the users cannot even try to instantiate it.
But I agree on similar name .. any better suggestions? But the rest of the engine uses name defaultMaterial for it .. so maybe it should just match. Maybe DefaultMaterialCache.


Reorganization of the doc pages

Which area this feature is related to?
/area documentation
Which area is this documentation change is related to?

/area landing-page
Issue details

What mistake did you find / what is missing in the documentation?
After reviewing the organization of our doc pages it has become clear that there is a few items of reorganization to be done:

The ordering of our doc page sections needs changing

e.g. Getting Started should be second in the ordering after the Introduction section

Review of doc page / section assignment. The order of the sections on the left should be in the order that we think a typical user will read from the top.

Devfile perspective pages Application developer, Enterprise architect and runtime provider, and Registry administrator and Technology and tool builders should be under the General rather than Getting Started. They should be group together as persona docs that are probably referred to at the end of the *Devfile ecosystem
Move **Devfile ecosystem to under General as well
Move General to the third section after Getting Started
Move API reference after General
Move existing General, Events, Components, Commands to 2nd level section and group them under a new section of Authoring devfiles
Move Creating devfiles with templates and Innerloop versus outerloop to the new first level General section, i.e. same level as Devfile ecosystem

Any other changes needed such as section renaming or adding/removal of sections

Target Date: 2023-03-31

03/28
sorting content; some duplicated info with the Introduction and Get Started section

explored alternatives to adding a second layer of side bar nav (i.e. using overview page in detailed authoring section to link in higher level overview page)
will need to sort some details in the authoring devfile section needs to be sorted