Features does not work with proxy MITM certificate on windows

Since the introduction of 'features', I am unable to use VS code devcontainers as it does not seem to access the Windows certificate store to get the CA certificates.

[2022-12-14T09:49:28.955Z] --- Processing User Features ----
[2022-12-14T09:49:28.956Z] * Processing feature: ghcr.io/devcontainers/features/node:1
[2022-12-14T09:49:28.956Z] > input: ghcr.io/devcontainers/features/node:1
[2022-12-14T09:49:28.956Z] >
[2022-12-14T09:49:28.956Z] > resource: ghcr.io/devcontainers/features/node
[2022-12-14T09:49:28.956Z] > id: node
[2022-12-14T09:49:28.956Z] > version: 1
[2022-12-14T09:49:28.956Z] > owner: devcontainers
[2022-12-14T09:49:28.956Z] > namespace: devcontainers/features
[2022-12-14T09:49:28.956Z] > registry: ghcr.io
[2022-12-14T09:49:28.956Z] > path: devcontainers/features/node
[2022-12-14T09:49:28.956Z] manifest url: https://ghcr.io/v2/devcontainers/features/node/manifests/1
[2022-12-14T09:49:28.957Z] No oauth authentication credentials found.
[2022-12-14T09:49:28.957Z] url: https://ghcr.io/token?scope=repository:devcontainers/features/node:pull&service=ghcr.io
[2022-12-14T09:49:29.068Z] Failed to get registry auth token with error: Error: unable to get local issuer certificate
[2022-12-14T09:49:29.139Z] (!) WARNING: Falling back to deprecated GitHub Release syntax. See https://github.com/devcontainers/spec/blob/main/proposals/devcontainer-features.md#referencing-a-feature for updated specification.
[2022-12-14T09:49:29.139Z] Github feature.
[2022-12-14T09:49:29.139Z] Could not resolve Feature 'ghcr.io/devcontainers/features/node:1'.  Ensure the Feature is published and accessible from your current environment.

Accessing the specified URL with any other application works.

ℹ  Looks similar to the issues reported in https://github.com/microsoft/vscode-remote-release/issues/7648

I sadly have not been able to reproduce the issue yet.  Are there any other details about your windows environment or network that you think could be useful to get a repro? (ie: Is this your personal computer, or corporate-managed, which version of Windows/VS Code/Dev Containers are you on?)
Also, is this intermittent, or consistently ending up in the same state for you?
Lastly, to help me gather more data, would you mind sending me the results of http://github-debug.com/ over email? (@github.com)

I sadly have not been able to reproduce the issue yet. Are there any other details about your windows environment or network that you think could be useful to get a repro? (ie: Is this your personal computer, or corporate-managed, which version of Windows/VS Code/Dev Containers are you on?)

Corporate-managed Windows 10 22H2. CA root certificates in question are distributed via GPOs to the Windows Local Machine Certificate Store. VS Code 1.74.2 , Dev Containers v0.268.0 pre-releae or v0.266.1 (no difference).

Also, is this intermittent, or consistently ending up in the same state for you?

It consistently fails to the same state. The component in question does not seem to respect the setting "Application -> Proxy -> System Certificates". ?

Lastly, to help me gather more data, would you mind sending me the results of http://github-debug.com/ over email? (@github.com)

Will send you an email, once I find it. ;-)

It seems like I do have the same problem. Switching back to Dev Containers 0.255.4 works and I can use "Add Dev Container Configuration Files..." command again. I'm on a Win 10 21H2 Build 19044.2075 corporate managed system. Access to internet is through MITM proxy with managed certificates.

This seems related to https://github.com/microsoft/vscode-dev-containers/issues/1745.


Asyncio support

Support SDK work in async mode
Need to design async interface and implement it

Async SDK version is also planned for implementation?


avoid overwriting images

Is your feature request related to a problem? Please describe.
I use this for my notes and so it can happen that I have a lot of different images from different files together. Now when I get prompted for the filename it can happen that I enter a filename of an already existing file. This then overwrites the existing image and it is lost.
Describe the solution you'd like
Detect when the file already exists and do sth like e.g. appending increasing numbers
Describe alternatives you've considered
Just live with it or hack together my own solution e.g. by appending a timestamp to the image (if that is possible, haven't checked that out yet)

You can do something like this to always append a timestamp to the filename:
opts = {
  default = {
    file_name = function()
      local file_name = vim.fn.input("File name: ")
      local timestamp = os.date("%Y-%m-%d-%H-%M-%S")
      return file_name .. "-" .. timestamp
    end,
    prompt_for_file_name = false,
  },
}

Does that help?


Recording: skip response cache toggle

Backstory & use case:

I use Mocket for recording responses from our third party services, these responses are then used on our dev environments
What I wanted was the ability to record every request<->response pair, even if the request structure is the same, as in some cases subsequent requests to the same resource will yield different results (as an example polling for a status of an async worker/job)
This gives the ability to then work on the recorded responses and tailor them to suit our needs

coverage: 98.418% (-0.8%) from 99.255%
when pulling 86872cd952aa769d3b8821bd79f65fc4cfd47e62 on e-z-health:feature/skip_response_cache
into 0da27224ad800297c4d120e740e1ba263da0327a on mindflayer:main.

Hi @wojciak, could we step back for a while and discuss what you have in mind under a proper issue?

@mindflayer This will be handled also by the recording class PR I think, I'll wait for that


Add Cairo Support Windows

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Attempt fix of #66

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Ah, there's a real build error here:
.\utils\pdftocairo.cc(890): error C3861: 'strcasecmp': identifier not found

The Windows version of libc is different than the standard glibc and, for instance, does not provide this particular function.
This individual issue could be fixable by patching the pdftocairo.cc file. This error is a warning sign, though, that the program probably isn't designed to run on Windows, so other issues might crop up. Once again it's hard to know how much of a challenge it will be without plunging in and seeing how things progress.

Okay I will investigate. Thanks.
pdftocario was built in older versions so theoretically it is possible. We will see.

Whoops! This drives me crazy constantly. Good catch.
Glad that it builds. Didn't have confidence there for a bit.

Do I need to rerender? I am still a bit confused about how that differs from the CI/CD?

@oschwartz10612 The "rerender" process uses automated tools to update the support files in the feedstock repo to track the evolution in the conda-forge infrastructure and guidelines. The CI/CD processes actually execute the recipe and build the packages.
The intention is that it should never hurt to rerender, and the tool will gracefully bow out if there's nothing to do. So, might as well.

@conda-forge-admin, please rerender

Ahh. Thanks for the clarification.

Ready to merge?


Use speed_limit, fall back to speed

@rmglennon how does this sound for helper text for the speed option? (shown via a question mark helper icon) "The speed limit is used when one exists. If there is no speed limit information available for a given segment, the speed attribute value is used."

Add: "default speed value for that category/type/whatever the term is of road"


Initial setup

@all-contributors add @davnn for code, test, docs, research, maintenance

@take

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/34680
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" a25509dcb5201bca0226c4595af41c8b48b66350
git push origin v0.1.0

@JuliaRegistrator register
Release notes:

split package into multiple sub-packages
provide wrappers for MLJ

Error while trying to register: Changing package repo URL not allowed, please submit a pull request with the URL change to the target registry and retry.

@JuliaRegistrator register
Release notes:
split package into multiple sub-packages
provide wrappers for MLJ

Registration pull request created: JuliaRegistries/General/44745
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" 0642f1377a8e2a2aa7ab6b8054f864de927b3e4b
git push origin v0.2.0

@all-contributors add @ablaom for code, research

@JuliaRegistrator register

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/48070
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.3 -m "<description of version>" 1add78370892ccbba8fb3be980106c62c023fcef
git push origin v0.2.3

Also, note the warning: Version 0.2.3 skips over 0.2.2
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/48072
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.2 -m "<description of version>" aa8b082c0ed52e267d26cab57355c949ee1b7d34
git push origin v0.2.2

@JuliaRegistrator register

Added label utilities, e.g. to count outliers with n_outlier

Registration pull request created: JuliaRegistries/General/54822
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.3 -m "<description of version>" 7a65ccbe2facae1cd38099f9127dce1dac733f93
git push origin v0.2.3

@JuliaRegistrator register

Allow more flexible categorical types for labels

Registration pull request created: JuliaRegistries/General/55796
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.4 -m "<description of version>" c041e7e1cb536659203d91eff99fc913d5506896
git push origin v0.2.4

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/55796
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.4 -m "<description of version>" 4db778eec438d2d5531e0fd67a06a6bb2a002d7c
git push origin v0.2.4

@JuliaRegistrator register

Bump MLJ version

Registration pull request created: JuliaRegistries/General/57211
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.5 -m "<description of version>" a47dfde22cbdfa5ee7f33ff16c7e1a02e467abca
git push origin v0.2.5

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/57299
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.6 -m "<description of version>" e82c98ce77a38730451e1d971aa8277abf2a694e
git push origin v0.2.6

@JuliaRegistrator register

Error while trying to register: "Tag with name v0.2.5 already exists and points to a different commit"

Error while trying to register: "Tag with name v0.2.5 already exists and points to a different commit"

@JuliaRegistrator register

Error while trying to register: Version 0.2.6 already exists

Error while trying to register: Version 0.2.6 already exists

@JuliaRegistrator register

drop julia 1.5 support
improvements to tests
better support for surrogate detectors

Registration pull request created: JuliaRegistries/General/57420
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" 2a0deabe14652d0703d43b9cd4bc16eb79ba4deb
git push origin v0.3.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/57436
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.1 -m "<description of version>" e32fcb380d28cebb69295be78e08e943fbb4b9a8
git push origin v0.3.1

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/57436
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.1 -m "<description of version>" fec9b5e2f6f615ad88fc088bc5a6340e2f44783e
git push origin v0.3.1

@JuliaRegistrator register
Release notes:

Update docs to reflect the 0.3 changes

Registration pull request created: JuliaRegistries/General/57440
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.2 -m "<description of version>" 4c73ad88178124b2f2a796151279146cb4143d3b
git push origin v0.3.2

@JuliaRegistrator register
Release notes:

Upgrade MLJ to 0.20
Adapt composite reports to work with MLJ 0.20

Registration pull request created: JuliaRegistries/General/70485
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.3 -m "<description of version>" 49f44f1bfb26612bbcac5b25261aedb19c75a988
git push origin v0.3.3

@all-contributors add @tylerjthomas9 for code

@JuliaRegistrator register
Release notes:
Upgrade MLJBase to 1.0
Adapt to new OutlierDetectionInterface

Registration pull request created: JuliaRegistries/General/97774
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.0 -m "<description of version>" 99249aec55f970d9eb0b30bb5ab6f9531b4a8d38
git push origin v0.4.0

@JuliaRegistrator register
Release notes:
Updated docs

Registration pull request created: JuliaRegistries/General/97781
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.1 -m "<description of version>" 9a3c7ce4f12242f1c4df9b1b2a9b5f64eade873a
git push origin v0.4.1


[bn] Localization of certificate.md

Localized certificate.md in Bangla
fixes #45729

/lgtm

/approve


fix incorrect error popup for farmer restart

Here is the fix for the scenario: when farmer is restarted, an error page appears, saying that farmer could not be restarted.
The issue is simple, but I will explain them in comments, please see below.
Draft, because I have better ideas on how to handle this, and probably you can do a much better job than me Serge. This is just to point out how to fix the error

Maybe we simply should not render Dashboard or PlottingProgress while node and farmer are restarting. Instead, we can display the loading page the same as on restart.
I think store logic is correct - we should not farm if we can't get syncState, we can definitely add specific try-catch blocks if we want to identify a particular step when an error occurred, but probably not right now.

Maybe we simply should not render Dashboard or PlottingProgress while node and farmer are restarting. Instead, we can display the loading page the same as on restart.

the backend cannot call the frontend functions. So when a new node name is set, the application should stop the syncing part of the farming function (the one that is continuing on the frontend, not the backend) and render a loading page for 5-10 seconds.
But i guess all these would complicate the application both for us and for the users.

I think store logic is correct - we should not farm if we can't get syncState, we can definitely add specific try-catch blocks if we want to identify a particular step when an error occurred, but probably not right now.

If the farmer started successfully, that means in the frontend -> node was successfully started, and farmer is fine. Then if we encounter a syncState error, that means node is restarting, and we can wait for 20-30 seconds, and during this time, ignore the errors. That was my suggestion, and I think it is the most simple way of not distracting the users throughout this restart process, and hide it as a backend complexity

I think it's simpler if UI reflects the state of node and farmer without extra assumptions, also I am not a big fan of ignoring errors - might be harder to debug if smth is wrong. I believe we can utilize tauri event module to let UI know when node has restarted

Yes that should be the ultimate goal, i agree.
Let's focus on this one after finishing our current tasks then.


Bring Back AnimeKhor

Source name
AnimeKhor
Source link
https://animekhor.xyz/
Source language
English
Other details
Great Chinese anime website with good English subs and many sources
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a title with source name.
[X] I have checked that the extension does not already exist on the website extensions list or the app.
[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I will fill out all of the requested information in this form.

What? The extension never went away and still exists.


express.static enables homepage route?

That's how my file looks like:
app.use(express.static("usr/IOT/public/"));

app.get("/test", (req, res) => {
  res.sendFile(path.join(__dirname + "/public/index.html"));
});

Without express.static my homepage route ("/") returns 404 and my test route loads, but the javascript fails to load.
When I enable express.static to load files everything works well, but my index.html is loaded on my homepage route ("/") aswell, although I have none enabled.
Is this intentional behaviour?

Checkout the  "index" option http://expressjs.com/en/4x/api.html#express.static

I see, thank you for the quick response!


Fix wrong error messages.

Description

Motivation and Context

Fix wrong NotImplementedError message.
Looks like it is a copy-paste bug.
How Has This Been Tested?
<! ---  Put an x in all the boxes that apply: --->

[ ] Pass the test by running: pytest qlib/tests/test_all_pipeline.py under upper directory of qlib.
[ ] If you are adding a new feature, test on your own test scripts.
N/A

Screenshots of Test Results (if appropriate):

Pipeline test:
Your own tests:

Types of changes

[x] Fix bugs
[ ] Add new feature
[ ] Update documentation

Thanks so much!


release: prepare for v2.0.1

To bring fixup https://github.com/dragonflyoss/image-service/pull/447
Signed-off-by: Yan Song<EMAIL_ADDRESS>

DCO check failed


Move Best Practices content into Style Guidelines Document - Fixes #448

Pull Request (PR) description
This PR moves the Best Practices content into the Style Guidelines document to make searching in a single place for guidance and best practice.
This Pull Request (PR) fixes the following issues

Fixes #448

Task list

[x] This PR changes documentation
[ ] This PR changes DscResource.Template

[ ] Updated documentation as necessary in the TEMPLATE_README.md.
[ ] An descriptive entry has been added to the change log
in the TEMPLATE_README.md.

[ ] This PR changes Tests.Template

[ ] The template version number has been increased appropriately.
[ ] An descriptive entry has been added to the CHANGELOG.md under the
Tests.Template folder.

@johlju - would you mind reviewing for me?

This change is

@PlagueHO Thanks for this, much easier to search one document now!


Multiple Selection Widget

Is your feature request related to a problem? Please describe.
To select multiple items from a drop down list I need to create multiple drop down lists.
Describe the solution you'd like
A UI element that allows selection of multiple items from the options list.

Basic test coverage done.


Add course description for RSE Leadership Training.

This PR resolves issue #791.
To the existing consulting page, a section has been added, with information about the Research Software Engineer (RSE) Leadership Training Course.
Deploy preview here...
Note for reviewer(s)

I haven't linked to the training materials yet. Are we ready to go live with it.

Thanks for the review!

I am not that should go there. It might be better as an event. What do you think?

I am not that should go there. It might be better as an event. What do you think?

🤔 Good thinking.
I do feel like it fits into the current location. Could we do a compromise and also add it under events?
That doesn't make for DRY code, but it does give the program visibility everywhere that matters.

My suggestion:

Make a page in events for the specific event with dates
Add to the consulting page the description of the course but without details of the dates and add a list to list events running this course with link to the event page

Does that make sense?

@yochannah  and @NPDebs - I have an idea - please bear with me:
I'm thinking:

This leadership course is possibly the first in the world to provide an intersectional framework that underpins a leadership course for those working as RSEs and those in the tech industry.
It is also unique in that we meet with you first to understand what challenges you are facing and to to create an individual development plan just for you.

Course will run weekly from 17th of October to 28th of November.

Topics covered include:

Using a Diversity and Inclusion framework to unearth talent.
Using Continuous Improvement skills to identify talent.
Setup and maintain pipelines to attract talent.
Project Management.
People managing high-performance teams.
How to deal with difficult change management situations and build relationships.

Pricing:

£499 GBP for initial skills consult and personal development plan.
£1999 GBP for the practical training course designed just for you and a small group of other leaders.

Does that make sense?

It does, @bebatut. I'll implement and await your feedback. 👍

These are minor changes, @rowlandm. No worries at all. :)
I'd like to clarify one thing though.
Do you want to replace "Couse content:" with "Topics covered include:"?

Make a page in events for the specific event with dates.

@bebatut I do have a concern about this approach. If we make a new .md file for each of these dates, we will end up having unique standalone events, when in reality, they are all part of a series.
It might be better to have a single .md file, which will ultimately contain all the details of the workshop.
Curious to hear what you think. 🙏

First image: Events page

Second image: RSE workshop page

Question:

Who is the contact person for this workshop? Their email should go here: 👇
contact_email<EMAIL_ADDRESS>

Will there be a deadine for registration? The registration link and deadline should be added here: 👇

                 registration:
                         link: https://some-streaming-app/registration
                         deadline: YY-MM-DD

What questions do we have about the structure so far?

These are minor changes, @rowlandm. No worries at all. :)
I'd like to clarify one thing though.
Do you want to replace "Couse content:" with "Topics covered include:"?

Yes please.

Feedback:

Might want to move "LMIC discounts are available for all offers. If you are interested in any of the services, please contact us at<EMAIL_ADDRESS>to the event page.
Are you sure you want an event page instead of the registration page of the event on Humanitix when it is ready?

Are you sure you want an event page instead of the registration page of the event on Humanitix when it is ready?

I was thinking we could have both. A main events page, from which we can link to the ticketing platform.
Does this approach sit well with you? @rowlandm

Yeah - I'm OK with that!

I'll be trying to setup the humanitix ticketing soon.

I've just changed the topics slightly:

Using a Diversity and Inclusion framework to improve your team.
Using Continuous Improvement skills to identify talent.
Setup and maintain pipelines to attract talent.
Project Management in complex scenarios.
Managing high-performance teams.
How to deal with difficult change management situations and build relationships.

Is it ok if they can go into this PR please?

I'm good with this now.

Suggestions applied - I'm happy with everything here! :) I suspect we need to differentiate between this and open seeds a little, but that's not urgent.

I'm good with these changes. Thanks everyone!

Good question I think the days will either be possibly up to the group but
preferentially on Tuesdays or Fridays.
Duration would probably be an hour for the first part with the break of
maybe 5 to 10 minutes and then an hour for the second part so probably
about two and a half hours maximum.
El sáb, 6 jul 2024, 6:55 p. m., Bérénice Batut @.***>
escribió:

@.**** commented on this pull request.
In _events/2024-10-research-software-engineer-training-course.md
https://github.com/open-life-science/open-life-science.github.io/pull/792#discussion_r1667333120
:

+We will then craft a practical training course just for you and a small group of other leaders to ensure all your needs are being met as an individual and as a group.
+
+# Topics
+
+The course will cover
+* Using a Diversity and Inclusion framework to improve your team.
+* Using Continuous Improvement skills to identify talent.
+* Setup and maintain pipelines to attract talent.
+* Project Management in complex scenarios.
+* Managing high-performance teams.
+* How to deal with difficult change management situations and build relationships.
+
+# Organization
+
+Course will run weekly from 17th of October to 28th of November.
When will the course be during the weeks? How long will be the sessions?
—
Reply to this email directly, view it on GitHub
https://github.com/open-life-science/open-life-science.github.io/pull/792#pullrequestreview-2161501797,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADGRUQW3YHVEKKCESXQ5PDZK6WIJAVCNFSM6AAAAABJV7XSBCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCNRRGUYDCNZZG4
.
You are receiving this because you were mentioned.Message ID:
<open-life-science/open-life-science.github.io/pull/792/review/2161501797@
github.com>

If we incorporate the availability note from @rowlandm above in response to @bebatut, then I'm happy to merge this.

Resolves #791

If we incorporate the availability note from @rowlandm above in response to @bebatut, then I'm happy to merge this.

Yeah, but is it Tuesdays, Fridays or based on participant availability? 😅

Maybe: Tuesdays or Fridays, based on participant availability.

Maybe: Tuesdays or Fridays, based on participant availability.

Thanks, Rowland! ✨

This is the link to the Humanitix event.  The deadline for the event is set as 20th September 2024. You can see it on the Humanitix event, although it is not that clear.....

Thanks, everyone! Looks like we're good to merge now.


Problem: Test ASTs are distributed all around tests, hard to reuse them

The test grew naturally and now the AST files are cross referenced between tests, let's make thing easier by having a central place for the,
Solution: Put all ASTs in one place, make them easy to reference
(possible repository injected into base test class)
SuccessCriteria: All ast json files are stored together, tests pass

Tests pass. Repository file created. This will make things a lot easier. Closing the issue.


Generic way to write contents of conf.d from a kubernetes configmap

We leverage dd-agent as a daemonset in kubernetes.  This is a lovely way to run dd-agent, but it has a couple challenges:

I can't update the /etc/dd-agent folder after launch with a postStart command, and have the process refresh it's config.
autodiscovery is amazing, but some pods/containers I can't modify their annotations to leverage it (like etcd pods in a kops deploy)

What I'd love is to lay out in a configmap something like:
---
apiVersion: v1
data:
  "conf.d/etcd.yaml": |
    init_config:
    instances:
      - "http://localhost:4001"
      - "http://localhost:4002"
kind: ConfigMap

Then feed the dd-agent daemonset something like "KUBERNETES_CONFIGRUATION_CONFIGMAP: $NAMESPACE/$CM_NAME".  dd-agent on startup would read the CM, write out the relevant files, then start dd-agent as normal.

Hi @zapman449
Thanks for reaching out! It is possible to create a config map with check files, configuration files, or even datadog.yaml as explained here. Does that fit your use case?


About the image of demo data.

Hi,
great work. I'd like to know which part of Nusence you have used. And What are the images of your demo data. Thanks

we provide scene token as well as corresponding cam front timestamp in the json.

Yeah I see. Thanks very much. Sorry to interrupt.


chore(main): release 2.4.0

:robot: I have created a release beep boop
2.4.0 (2022-11-17)
Features

add assembly and nucleotide info from gbk file (ad8505a)
add assembly info (d9d03dd)
add assembly info (9d81e61)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/socialgene/sgpy/releases/tag/v2.4.0 :sunflower:


Remove Sphinx live view port forwarded to API container

Problem

The API docker-compose service is still configured to forward to port 3000, but nothing runs there anymore because our documentation exists and is built elsewhere now.
Description

Remove the port 3000 entry in the web service of the docker-compose stack.

Can you assign me to this issue ?

Removed the port 3000 entry in the web service of the docker-compose stack.

Fixed in #2808.


BitBar instead of iStat Menus

Look into using BitBar instead of iStat Menus for the fuzzy time.

This is done, but I'll probably end up replacing BitBar with hammerspoon. See #29.


Solace Read connector: adding Basic Authentication support

This is the 3rd PR for the Solace Read connector (addresses #31440).
It depends on the #31539 and #31476 (root).
The files that are added/modified in this PR, comparing to the #31539:

BasicAuthJcsmpSessionService.java
BasicAuthJcsmpSessionServiceFactory.java
SolaceMessageReceiver.java

These are implementations of SessionService, SessionServiceFactory and MessageReceiver. SessionServiceFactory can be used as an argument to SolaceIO.withSessionServiceFactory(...).

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @damondouglas

R: @damondouglas

@bzablocki Could you click the "re-request" review next to my GitHub username above, after addressing comments when this PR is ready for review again.

Merging after checks pass...


chore: set 2.5.0 as the latest version of the spec

This PR updates next-spec branch with the latest changes from master. It also sets all references to 2.4.0 as being the latest version to 2.5.0, including examples.

What are all these changes? Did you create the branch from master maybe?

What are all these changes? Did you create the branch from master maybe?

Yes, as the next-spec branch was completely out of date.

can we have update of branch separate, and then 2.5 changes?

done. https://github.com/asyncapi/spec/pull/810

@derberg @fmvilas @dalelane this is ready to be reviewed

/rtm


fix: free memory from internal cache when disconnecting

Details

In this PR I added some new internal tracking of data and forgot to release the data on disconnect.
Related Issues

https://github.com/Expensify/react-native-onyx/issues/569
Automated Tests

Not really testable as it's an internal.
Manual Tests

n/a - only a small memory improvement
Author Checklist

[x] I linked the correct issue in the ### Related Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos
n/a - only a small memory improvement. Let me know if I am wrong, then I can test on all platforms.

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Gonna go ahead with the merge as its quite quick change here, thanks @srikarparsi for the ping

@mountiny before updating in newdot I'd need this PR to be merged as well please:

https://github.com/Expensify/react-native-onyx/pull/574


Use lookahead token to decide which error message to use

Today when we use menhir's compile_errors option to generate error messages table in ocaml, the only input is the error state. It generates something like:
let message =
fun s->
  match s with
  | 0 ->
    "syntax error blah blah blah"
  ...

But sometimes for the same state, we want to have different error messages for different lookahead token. I'm thinking maybe we can use lookahead token as another input to error messages. So the generated ocaml error table file would look like this:
let message =
fun s token ->
  match (s, token) with
    | (0, MINUSGREATER) ->
      "Doesn't expect '->' here! Maybe you mean '=>' ?"
    | (0, DIV) ->
      ...
    | (0, _) ->
     ...

Touch based with Menhir people. For now I think the we should just develop our own interpretation tool to generate an augmented ".ml" to achieve this.


CurvedAnimation leaks in flutter framework

Steps to reproduce
Run the below tests
Expected results
Animations a disposed properly
Actual results
Leak tracker detects leaks
Code sample
Code sample
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';

class SimpleButtonPage extends StatefulWidget {
  const SimpleButtonPage({super.key});

  @override
  _SimpleButtonPageState createState() => _SimpleButtonPageState();
}

class _SimpleButtonPageState extends State<SimpleButtonPage> {
  int counter = 0;

  void incrementCounter() {
    setState(() {
      counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('Simple Button Test'),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text('You have pushed the button this many times:'),
            Text(
              '$counter',
            ),
            ElevatedButton(
              onPressed: incrementCounter,
              child: const Text('Increment'),
            ),
          ],
        ),
      ),
    );
  }
}

void main() {
  testWidgets('Button click increases counter', (WidgetTester tester) async {
    await tester.pumpWidget(const MaterialApp(home: SimpleButtonPage()));

    expect(find.text('You have pushed the button this many times:'), findsOneWidget);
    expect(find.text('0'), findsOneWidget);

    await tester.tap(find.byType(ElevatedButton));
    await tester.pump();

    expect(find.text('1'), findsOneWidget);
  });
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
notDisposed:
              total: 3
              objects:
                CurvedAnimation:
                  test: Button click increases counter
                  identityHashCode: 445682550
                CurvedAnimation:
                  test: Button click increases counter
                  identityHashCode: 340990049
                CurvedAnimation:
                  test: Button click increases counter
                  identityHashCode: 36430547

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.22.2, on macOS 14.5 23F79 darwin-arm64, locale en-NG)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] IntelliJ IDEA Ultimate Edition (version 2024.1.3)
[✓] VS Code (version 1.89.0)
[✓] Connected device (4 available)

From my understanding, CurvedAnimation is meant to be disposed once its parent controller has been disposed so maybe this is an issue with leak_tracker?
@polina-c
As an aside, I am also seeing same behaviour with ImageInfo object.


Install npm globally or locally?

In the step "Ensure your version of npm is up to date." above, is the intention to have the reader update npm on their machine? That should be "npm i -g npm". If the intent is to bind to the latest version of npm, there is no package.json yet, so you get errors running "npm i npm".

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

ID: dfaad3f2-75c5-e958-4734-8925d03d95c6
Version Independent ID: 8d98b390-5368-1fa4-8cce-3b0cff252eaa
Content: Create a bot using Bot Builder SDK for JavaScript - Bot Service
Content Source: articles/javascript/bot-builder-javascript-quickstart.md
Service: bot-service
Product: bot-framework
GitHub Login: @JonathanFingold
Microsoft Alias: jonathanfingold

Fixed. This update should go live in a few days.


The Container logs is Confused

Bug description
The Container logs sometimes are not immediate
Expected behavior
The Container logs are always immediate
Portainer Logs
PS: now time is 2020-07-23T09:30:19,but i get this:
2020-07-22T04:08:19.607309030Z   File "/usr/lib/python3.6/logging/init.py", line 1061, in _open
,2020-07-22T04:08:19.607312470Z     return open(self.baseFilename, self.mode, encoding=self.encoding)
,2020-07-22T04:08:19.607315986Z OSError: [Errno 28] No space left on device: '/home/kafka_custom/logs/info.log'
,2020-07-22T04:08:19.607319923Z Call stack:
,2020-07-22T04:08:19.607323183Z   File "/usr/lib/python3.6/threading.py", line 884, in _bootstrap
,2020-07-22T04:08:19.607326806Z     self._bootstrap_inner()
,2020-07-22T04:08:19.607330095Z   File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
,2020-07-22T04:08:19.607333726Z     self.run()
,2020-07-22T04:08:19.607337050Z   File "/usr/lib/python3.6/threading.py", line 864, in run
,2020-07-22T04:08:19.607346610Z     self._target(*self._args, **self._kwargs)
,2020-07-22T04:08:19.607350185Z   File "/usr/local/lib/python3.6/dist-packages/pykafka/producer.py", line 621, in queue_reader
,2020-07-22T04:08:19.607353839Z     self.producer._send_request(batch, self)
,2020-07-22T04:08:19.607357345Z   File "/usr/local/lib/python3.6/dist-packages/pykafka/producer.py", line 529, in _send_request
,2020-07-22T04:08:19.607360995Z     self._update()
,2020-07-22T04:08:19.607364875Z   File "/usr/local/lib/python3.6/dist-packages/pykafka/producer.py", line 275, in _update
,2020-07-22T04:08:19.607368502Z     self._cluster.update()
,2020-07-22T04:08:19.607371849Z   File "/usr/local/lib/python3.6/dist-packages/pykafka/cluster.py", line 518, in update
,2020-07-22T04:08:19.607375406Z     self._update_brokers(metadata.brokers, metadata.controller_id)
,2020-07-22T04:08:19.607378852Z   File "/usr/local/lib/python3.6/dist-packages/pykafka/cluster.py", line 397, in update_brokers
,2020-07-22T04:08:19.607382475Z     log.info('Reconnecting to broker id %s: %s:%s', id, meta.host, meta.port)
,2020-07-22T04:08:19.607385950Z Message: 'Reconnecting to broker id %s: %s:%s'
,2020-07-22T04:08:19.607389372Z Arguments: (0, b'x.x.x.x', 9092)
,2020-07-22T04:08:19.608612874Z --- Logging error ---
,2020-07-22T04:08:19.608684723Z Traceback (most recent call last):
,2020-07-22T04:08:19.608724140Z   File "/usr/local/lib/python3.6/dist-packages/pykafka/producer.py", line 494, in _send_request
,2020-07-22T04:08:19.608731969Z     response = owned_broker.broker.produce_messages(req)
,2020-07-22T04:08:19.608737410Z   File "/usr/local/lib/python3.6/dist-packages/pykafka/broker.py", line 45, in wrapped
,2020-07-22T04:08:19.608743069Z     return fn(self, *args, **kwargs)
,2020-07-22T04:08:19.608748252Z   File "/usr/local/lib/python3.6/dist-packages/pykafka/broker.py", line 341, in produce_messages
,2020-07-22T04:08:19.608753963Z     return future.get(ProduceResponse)
,2020-07-22T04:08:19.608759021Z   File "/usr/local/lib/python3.6/dist-packages/pykafka/handlers.py", line 74, in get
,2020-07-22T04:08:19.608764611Z     raise self.error
,2020-07-22T04:08:19.608769507Z   File "/usr/local/lib/python3.6/dist-packages/pykafka/handlers.py", line 214, in worker
,2020-07-22T04:08:19.608774864Z     res = shared.connection.response()
,2020-07-22T04:08:19.608779917Z   File "/usr/local/lib/python3.6/dist-packages/pykafka/connection.py", line 226, in response
,2020-07-22T04:08:19.608785134Z     raise SocketDisconnectedError("<broker {}:{}>".format(self.host, self.port))
,2020-07-22T04:08:19.608816281Z pykafka.exceptions.SocketDisconnectedError: <broker b'x.x.x.x':9092>
,2020-07-22T04:08:19.608824417Z
,
Steps to reproduce the issue:

Go to http://x.x.x.x:9000/#/containers
Click on 'your container' and logs
Change the lines number, you will find difference logs(it's difference time!!!)
See error

Technical details:

Portainer version:1.24.0
Docker version (managed by Portainer):19.03.6 (API: 1.40)
Platform (windows/linux):linux x86_64 Ubuntu 18.04.1 LTS
Command used to start Portainer :docker run -p 9000:9000 portainer/portainer
Browser: chrome 83.0.4103.116

Additional context
As we can see,i get different logs at the 'same' time
https://github.com/nsf-github/nsf-github/blob/master/Peek 2020-07-23 09-42.gif

Hi @nsf-github ,
We were unable to reproduce this problem inside our environment. Already create some container with image chentex/random-logger:latest for generate dummy log and try change the line in Portainer like u do in this: https://github.com/nsf-github/nsf-github/blob/master/Peek 2020-07-23 09-42.gif but everything was good.

what image did you use on that running container?

Hi @ametdoohan,
Thank you for your reply.My other container logs are good beside this(a):https://github.com/nsf-github/nsf-github/blob/master/Peek 2020-07-23 09-42.gif.
Their base image is ubuntu18.04.There are some thing in a:
python3.6(it is runing a python script)
cassandra-driver==3.24.0
pykafka==2.8.0
python-dateutil==2.8.1
PyYAML==5.3.1
I explain it simply as i can.I read a txt as a producer of kafka,then consume it,get data and wirte it to pykafka.
If other people can't reproduce this problem, i think we should remember the problem because i believe it will happen in the future, i wish i can supply some help.

Why container logs goes lost? The only last log items are available. How can I fix it?

Why container logs goes lost? The only last log items are available. How can I fix it?

I did not lost the container logs（maybe your logs is too many？） .The container logs is what your program print, maybe you can write it to log file to avoid it if your logs is importmant.


[Need help] Create / Destroy FrameBuffer with native handle on android.

I'm trying to make a video recorder for Android. But there are some problems with creating and destroying FBO with NWH.
Specifically, the following problems arose. All those problems occurred while drawing camera inputs on the main window. NWH used what was received from android media codec.
With reference to bgfx Example 22, FBO was created when window was valid and destroyed before window was released. And when destroyed, bgfx::frame() was called twice to release the associated resources.

Case : When I just called createFrameBuffer and drew nothing there.
Main window freezes. If drawing begins in FBO, it will operate normally.

Case : Destroy FBO and release window to end recording.
Main window freezes. Normal behavior when I restart recording and create a new FBO. Recorded video can be played normally.

Case : If I release the recording window but didn't destroy the FBO. Since then, nothing has been drawn on the FBO.

Main window works normally.
Below are my create and destroy codes.
bool Puff::createWindowFrameBufferObject(const std::string& windowName, void* nativeWindowHandle, int width, int height)
{
    auto frameBufferHandle = bgfx::createFrameBuffer(nativeWindowHandle, width, height, bgfx::TextureFormat::BGRA8, bgfx::TextureFormat::D24S8);

    if(!bgfx::isValid(frameBufferHandle))
        return false;
    _windowFrameBuffer[windowName] = frameBufferHandle;
    return true;
}

bool Puff::destroyWindowFrameBufferObject(const std::string& windowName)
{
    auto frameBufferHandle = _windowFrameBuffer.find(windowName);

    if(frameBufferHandle != _windowFrameBuffer.end() && bgfx::isValid(frameBufferHandle->second))
    {
        bgfx::destroy(frameBufferHandle->second);
        _resourceManager->resetViewInfo();

        bgfx::frame();
        bgfx::frame();
        _windowFrameBuffer.erase(frameBufferHandle);
        return true;
    }

    return false;
}

I found problem. When creating swapChain, makeCurrent() is called from within, but no action is taken to reverse its behavior. For example, updating m_glctx's m_current.

For the test, I have modified the code in glContext_egl.cpp as follows and it works well for me.
From :
void GlContext::makeCurrent(SwapChainGL* _swapChain)
{
    if (m_current != _swapChain)
    {
        m_current = _swapChain;

        if (NULL == _swapChain)
        {
            if (NULL != m_display)
            {
                eglMakeCurrent(m_display, m_surface, m_surface, m_context);
            }
        }
        else
        {
            _swapChain->makeCurrent();
        }
    }
}

To :
void GlContext::makeCurrent(SwapChainGL* _swapChain)
{
    if (m_current != _swapChain)
    {
        m_current = _swapChain;
    }

    if (NULL == _swapChain)
    {
        if (NULL != m_display)
        {
            eglMakeCurrent(m_display, m_surface, m_surface, m_context);
        }
    }
    else
    {
        _swapChain->makeCurrent();
    }
}

Fix seems fine, you can send PR.

Thank you for reply. This modification will cause render thread to call eglMakeCurrent every time it calls m_glctx.makeCurrent(), so I will see if I can fix this problem in a different way and then I'll send PR.

This modification will cause render thread to call eglMakeCurrent every time it calls m_glctx.makeCurrent()

Yeah this would be bad.

When creating swapChain, makeCurrent() is called from within, but no action is taken to reverse its behavior. For example, updating m_glctx's m_current.

So when destroying any window you need to just invalidate m_current afterwards?

Exactly. I have yet to check the code for the part where the swapchain is released.

May I add parameter to the makeCurrent function in GlContext? Like below
void makeCurrent(SwapChainGL* _swapChain = NULL, bool _forced = false);

I want to call this with true after create or destroy the frameBuffer that has NWH. Or I want to set this parameter to true when it is first called in the submit function.
I don't like adding flags for control, since bgfx is a cross-platform library, it seems that the solutions available are quite limited. Or is there a way to suggest otherwise?


Handling System.Web to Core [best practices]

From @narenkv on July 20, 2016 5:11
Hello all,
Is there any best practices or steps or senarios which would help people to migrate from .NET 4.x.y versions.
Responding this will help many people in the world :-)
/Naren
Copied from original issue: dotnet/corefx#10166

From @narenkv on July 20, 2016 23:4
Hello Lextm
Yes, But it helps to one extent. however the alternatives and not clearly articulated. Example System.Web references how to handle is not given. May be a sample conversion project with bare minimal code is shared will be of great help
Also heading mentions the documentation is limited to .0.0-rc2 versions and updates are yet to come.
/Naren

From @lextm on July 20, 2016 13:23
Have you gone through these?
https://docs.asp.net/en/latest/migration/index.html
If not, you should. Issues or questions on those materials can be submitted to
https://github.com/aspnet/Docs/issues

From @joshfree on August 2, 2016 19:45
@muratg can you help route this to an asp.net repo?

@narenkv not sure what you mean with "example System.Web references how to handle". System.Web is not used anymore, if that's what you're asking.

Hello muratg,
Yes, We are looking for a example implementation.
/Naren

This needs to be a thing that gets built up based on specific scenarios. ASP.NET Core is a different framework so it would be good to explain exactly what you're trying to convert.

Closing for other higher priority issues.


generator succcessor replacement for PR #2606

split into two generateOnFront, generateOnPopFront

https://github.com/D-Programming-Language/phobos/pull/2606

I appreciate your attempt to mediate, but we better decide for only one of the functions.
There are good reasons for doing the computation in front and there is std.range.cache when an optimization is needed.
https://github.com/D-Programming-Language/phobos/pull/2606#issuecomment-61406577
If really necessary, then it should be a template Yes.onPopFront argument with a default value.

I am not convinced this is worth it. I might be missing some information, there might be legitimate reasons for this. From what I can tell the generate function can easily be build with the tools at hand. There is map and no shortage of means to generate ranges like cycle or iota. Why not just use those functions?

Ok, I have been too short-sighted. There is value in generate. I opt for a very simple version with evaluation in front, to match map. When is comes to the name, I'd opt for repeatedly. This matches the repeat function nicely.

Yes, please get rid of the popFront variant.

popFront is gone

Looks nice, thanks.
Nicely documented, concise and well tested.

updated

Auto-merge toggled on

thx

thank you


Clean some errors in benches

add html output for json and fix two issues in http://gresil.org/jenkins/job/nit_bench/120/testReport/

ping @Morriar  because markdown is you
pinte @R4PaSs because json is you.

:shipit:


Replace all hero icons by bitcoin icons

Uses the new "react components" implementation.
Removes extra Hero Icons lib.
Unifies icon style.

Awesome, once this gets merged I can add the dark mode styling for these. #360

@johnsBeharry do you have time to click through and review this?


[Websocket] Support All Opcodes

This PR is just handling the basic/simple essentials for receiving and sending all the opcodes.
Things that are out of scope for this PR:

Logging
Any Reconnect/Resume logic
Handling the dispatch Events
a discord.status (or discord.user_status) string "enum" equivalent

👍


Add TS declaration for setupMirage

This PR ensures that import { setupMirage } from 'ember-cli-mirage/test-support'; works as expected for TypeScript users. It also adds a small types-tests suite to verify that they work as expected.
@SergeAstapov if I were to open a second copy of this PR against the v2 branch, is there a chance you'd be willing to include it in a 2.x release as well, since 3.0 is still in alpha? 🙂

@SergeAstapov if I were to open a second copy of this PR against the v2 branch, is there a chance you'd be willing to include it in a 2.x release as well, since 3.0 is still in alpha? 🙂

Yes! I'm 100% up for this as v2 is still fully supported and I think we'll support it for some time until v2 surpasses v2


Email address placeholder localization

Localize “email address” placeholder -  #20175

/lgtm
/language uk
/assign idvoretskyi

Haven't got Ukrainian localization team approvals sorted yet
/approve

/language uk

/language uk


Improve camel-example-cdi-cassandraql readme

Working on CAMEL-13234 I had to run camel-example-cdi-cassandraql example, so run into problem with memory limits.
Added information about limiting memory to Cassandra docker container.

Thanks


extend API to spawn process with specific initial terminal size

Hello,
I'm currently working on https://github.com/uutils/coreutils to provide a terminal simulation on the tests also for windows.
I decided to use conpty for this, but I stumbled accross the issue that there is no way to initially provide the desired terminal size.
It is important for us to change the terminal size from the default one.
conpty provides a Process::resize function that allows to change the terminal size after it has started.
But this I can't use because of two major issues:

it causes raise conditions as child process has already started and might have queried the terminal size already before it was changed.
it causes additianl ANSI-Escape sequences to appear for clearing the buffer and other stuff triggered by the resize.

Therefor I would like to introduce this change to conpty.
I introduced an new function leaving the existing one untouched such that its backwards compatible.

Hi @cre4ture
Thanks for contribution.
I guess it'd be better to add a field into Process, then add a setter, and use it while do spawn.
I think it'll be much better don't you think?
https://github.com/zhiburt/conpty/blob/4ce6806b12d0e0c74c760609ccffd7a8d554afdf/src/process.rs#L48

I guess it'd be better to add a field into Process, then add a setter, and use it while do spawn.

The issue I see is that the Process currently is instanciated only after console was created.
The spawn call is the constructor of the Process struct.
We would need to change/extend the API with a constructor that doesn't spawn, a setter and an other spawn function that is a real member function. AND we probably need to implement for the existing member function a check for if the process is already started or not.
If we want to be more generic. we could introduce a struct called e.g. SpawnParams that is injected to a new functon called spawn_with_params().
What do you think?

The issue I see is that the Process currently is instanciated only after console was created.
The spawn call is the constructor of the Process struct.

So you're right;
Sorry; somehow forgot ....

If we want to be more generic. we could introduce a struct called e.g. SpawnParams that is injected to a new functon called spawn_with_params().

Yees but a bit different.
How about ProcessOptions, and have ProcessOptions::spawn.
Process::spawn would be just ProcessOptions::default().spawn()

@zhiburt PR is ready for another review. let me know if it makes sense to you

Looks good to me.
Except that I'd not make the fields public :smile:
Just provide setters.
But'll do it myself, if you're not against of it.
And release probably tommorow.

Out of topic;

I'm currently working on https://github.com/uutils/coreutils to provide a terminal simulation on the tests

But what do you use for linux?
Sort of interested in an approach cause of https://github.com/zhiburt/expectrl

And yes thanks once again

Except that I'd not make the fields public 😄

I almost expected this ;-)

But what do you use for linux?

For linux its quite easy, we just use the nix-crate for nix::pty::openpty
https://docs.rs/nix/latest/nix/pty/fn.openpty.html
This is even more flexible, because it provides filedescriptors that you can fully flexibly connect to the process-stdio in the exact way you need it. The windows world is more restrictive as you need to create the console and its child process in the same step.
But I'm working on a workaround to avoid this. I'm spawing a dummy process inside of the console, attach the main process afterwards to the new console useing FreeConsole and AttachConsole and then spawn the real child process with inheriting the stdio. afterwards the main process can switch back to its original console.


Socker errors reported during perf testing

When conduct a simple test to understand the performance of go-zero, I recevied below socket errrors, the greet service is a wrap without any logic
wrk -c 1024 -d 10s -t 16 http://localhost:8888/greet/from/you
Running 10s test @ http://localhost:8888/greet/from/you
16 threads and 1024 connections
Thread Stats   Avg      Stdev     Max   +/- Stdev
Latency   140.87ms   65.42ms 364.28ms   80.74%
Req/Sec   478.43    246.45     2.62k    69.67%
70993 requests in 10.06s, 12.25MB read
Socket errors: connect 19, read 0, write 0, timeout 0
Requests/sec:   7057.06
Transfer/sec:      1.22MB
Run same test against go-kit, has no socket errors reported, same for gin and grpc.

It turns out a ulimit issue, after setting hard and soft for nofile /etc/security/limits.conf, everything runs smoothly now


Use our own KeyboardAwareScrollView everywhere and remove react-native-keyboard-aware-scroll-view

Expected Behavior
Remove react-native-keyboard-aware-scroll-view and use our custom KeyboardAwareScrollView everywhere.
Current Behavior
For #1225 I added a custom KeyboardAwareScrollView which better fit our needs.
However the verifier is still using react-native-keyboard-aware-scroll-view.

Looks like it's only in our package.json and not used anymore. We can just delete it.


Do not remove the captcha field from the form fields

As discussed on #16, we should only remove the captcha field from cleaned_data, not fields (see code).

Blocked until wagtail/wagtail#4313 is fixed.


Stone near Fog Owl is missing collision

Also fix any other missing collisions that may be there

Is this the rock that's missing a collider? Checked a few of the other maps and they didn't have colliders for them either, so I wanted to check before making any changes

@MarvJohnson It is! I was planning to fix this too but didn't have a chance to check the collision on the other maps yet. If you want to tackle this one let me know and I'll leave it out of the updates I'm planning!

I can knock this out pretty quickly! There are a few things I'm working on right now that require a lot of scouring maps anyhow

Sounds good! Thanks Marvel :)


feat: create docker images when new tag is released

Description
This will create new docker images when new tag is released.
closes: #1356
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

@gsk967 please rebase & sign your commits so this can be merged

@gsk967 please rebase & sign your commits so this can be merged

It is done, can you approve and merge this pr


[Sluggable] Enable gedmo-like "unique_base" feature

Hi!
I'm migrating away from the Gedmo-DoctrineExtension and noticed that there is no equivalent to the unique_base option of Sluggable.
Switching the DefaultSluggableRepository would be fine for my usecase, but that's not possible because the class is marked as final.
I created an interface for the SluggableRepository with the isSlugUniqueFor-Method for checking against the database, and an additional isSlugUnique-Method which is used to check against other entities in the current changeset.
Testcases are provided. :)

Hi, I don't know the feature in gedmo.
What is it for?
I wonder if slug should be non-unique anytime. Thought?

Hi!
You can think of it as a namespace for slugs.
Example:
Website promoting companies, each company can has serveral pages.
URL structure: /[company-slug]/[page-slug]
Assume every company has an about-page.
Company-Entity:
 - name
 - slug

Page-Entity:
 - name
 - slug
 - company

Without "unique_base":
/acme/about
/contoso/about-1
With page.company used as the base:
/acme/about
/contoso/about

Closing for lack of feedback for last ~8 months

@TomasVotruba I want to use custom SluggableRepository but with current setup (subscriber depends on exact final class) it is not possible.
My use case is to use same SLUG for translation entities with different locale. UNIQUE constraint obviously does not work as SLUG is generated in prepersist event.
What do you suggest?

Hi, I'm not sure as I don't use this specific behavior. It seems like extracting an interface would help

Thats what I think. Would you accept a PR? I would need a helping hand, as Im locked on PHP 7.4 and cant use master... would be possible to back merge?

PHP 8 is needed to be able contribute, or you can try Docker


Do not recommend adding ex_machina to the applications list

It is mostly a test only dependency, so we can start it in the test helper.

@josevalim thanks for the PR! We've gone back and forth on this and it's a bit tricky. If we change the Readme to this then if they put their factory in lib/my_app/factory.ex it will fail in dev and prod because the dependency isn't there.
In Phoenix you could put it in test/support/factory.ex, but not everyone uses Phoenix.
We have it the way it is now because it's the least error prone that we've found so far, and because it lets you use the factory for seeds in dev/prod if you want. If we can figure out a recommendation that is simple to get started and won't cause errors once they use dev/prod environments then I'm totally up for discussing that though.
What do you think? Also, feel free to open other issues if you have any other thoughts or suggestions. We're always looking for feedback :)

What if we define both modes explicitly in the README then? Test only and
all environments? I have only opened the issue because folks were running
into issues. They specified the dependency as only test and added it to
applications then their app couldn't boot!
On Sunday, January 17, 2016, Paul Smith<EMAIL_ADDRESS>wrote:

@josevalim https://github.com/josevalim thanks for the PR! We've gone
back and forth on this and it's a bit tricky. If we change the Readme to
this then if they put their factory in lib/my_app/factory.ex it will fail
in dev and prod because the dependency isn't there.
In Phoenix you could put it in test/support/factory.ex, but not everyone
uses Phoenix.
We have it the way it is now because it's the least error prone that we've
found so far, and because it lets you use the factory for seeds in dev/prod
if you want. If we can figure out a recommendation that is simple to get
started and won't cause errors once they use dev/prod environments then I'm
totally up for discussing that though.
What do you think? Also, feel free to open other issues if you have any
other thoughts or suggestions. We're always looking for feedback :)
—
Reply to this email directly or view it on GitHub
https://github.com/thoughtbot/ex_machina/pull/87#issuecomment-172287283.

--
José Valimwww.plataformatec.com.br
http://www.plataformatec.com.br/Founder and Director of R&D

@josevalim It's definitely tricky because we had complaints when we had in test env too haha. So yeah I think including both is probably the best bet.
If running in all environments:
Add dep, add to applications list, put factory in lib
If running in just test
Add test dep, start in test_helper, make sure test/support is added when in test env, and add factory to test/support
I know you're busy. I'm happy to do this myself if you don't have time. Just LMK. :)

Also where did you hear about folks having issues? I've only seen a couple comments on an issue. I'd love to know where to look so I can catch future issues like this more quickly :)

Maybe we should have 3 instructions then?

All environments
Test environment with Phoenix
Test environment for non Phoenix projects

That's because non Phoenix projects do not include test/support by default.

Also where did you hear about folks having issues? I've only seen a couple comments on an issue. I'd love to know where to look so I can catch future issues like this more quickly :)

Private discussions at @plataformatec. ;)

Yeah I think 3 sections sounds best. I was thinking of keeping it just two, with a note about adding test/support, but breaking it into 3 sections probably makes it simpler. Good idea.
And thanks for bringing it to our attention! Let me know if you have any other feedback that your team has mentioned. Both good and bad helps :D

On Jan 18, 2016, at 12:06 PM, José Valim<EMAIL_ADDRESS>wrote:
Maybe we should have 3 instructions then?
All environments
Test environment with Phoenix
Test environment for non Phoenix projects
That's because non Phoenix projects do not include test/support by default.
Also where did you hear about folks having issues? I've only seen a couple comments on an issue. I'd love to know where to look so I can catch future issues like this more quickly :)
Private discussions at @plataformatec. ;)
—
Reply to this email directly or view it on GitHub.

Closed in favor of #87


Create a FatBeacon emulator for Arduino or Node?

There seems to be some interest in people playing with FatBeacon. We're about to release a 'demo' version of the PW app that will let you easily bring up a sample FatBeacon but clearly, something a bit more flexible would be helpful for people to play with.
I'm curious if anyone out there is currently toying around with Arduino or Node and would be willing to replicate the FatBeacon characteristic? Something that would just let people try a few things out. We really want to do this but won't be able to get to it for a few weeks. i was hoping this would be easy for some of you.
Thanks,
Scott

I'll give it a go with the bleno nodejs code if you can let me know the characteristics. I've been waiting for the spec to have a go.

There are two UUID's that are associated with FatBeacon. The UUID for the service is ae5946d4-e587-4ba8-b6a5-a97cca6affd3 and the UUID for the html characteristic is d1a517f0-2499-46ca-9ccc-809bc1c966fa.
Another thing worth noting here is that due to some limitations on android, the FatBeacon server transfers packets that are 5 bytes smaller than the MTU size. Therefore to read the full characteristic value, the app reads the html characteristic repeatedly until it receives a packet that is more than 5 bytes smaller than the MTU size. The FatBeacon server also needs to maintain the state of the characteristic for the connection.
The FatBeaconBroadcastService is the FatBeacon server code for the app and BluetoothSite is the FatBeacon client code.

Thanks, I'll see what I can run up at the weekend

This 5 byte issue is a good example of this API being in flux. This is what we had to do in order to get it working on Android. As we move to beacon based solutions, we may (likely) remove this type of workaround.

+1 to try out with bleno in node. \o/

For me Go or Node.
On Fri, Sep 2, 2016 at 5:42 AM, Francisco Jordano<EMAIL_ADDRESS>wrote:

+1 to try out with bleno in node. \o/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/physical-web/issues/814#issuecomment-244317971,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgjWTmmoVnprn8qAl0q2nSdsYaCvTnhks5ql-GLgaJpZM4JzKZJ
.

First pass -> https://github.com/hardillb/FatBeacon
It's not working just yet, but the bones should be there. I'll add a README.md in a few mins but if anybody wants to try and debug it while I get some "real" work done this afternoon.

I think a better start would be don's node-eddystone-beacon which already solved a lot of the eddystone issues on all platforms. I moved some of your stuff over here, feel free to PR them so your authorship is intact, etc.
https://github.com/jacobrosenthal/node-eddystone-beacon/tree/fatbeacon
It advertises, but cant connect yet ;)
Use DEBUG=* node examples/fatBeacon/simple.js to see some debug output.. For some reason were getting 2 accepts and on osx I get a kCBMsgId82 which isnt handled by bleno. Trying to figure out whats up with that.
Any help appreciated :)

Do we need anything above normal service advertisement? I know there is an open issue on the node-eddystone-beacon stuff about advertising a URL and services at the same time (interleaved) that is still open (I want that for some easier Eddystone + WebBluetooth stuff).
Anyway, I'll pull it and have a look

@jacobrosenthal I've got your modified version of my code transposed to the @don's eddystone code working on my Pi. I've not tried things closer or bigger than the MTU but it's working with small payloads.
https://github.com/hardillb/node-eddystone-beacon/tree/fatbeacon/examples/fatBeacon
I'll stick in a pull request to don later today if nobody spots anything really wrong with it.

For info, I've created a simple web that reads FatBeacon content at https://beaufortfrancois.github.io/sandbox/physical-web/fatbeacon/
Let me know what you think.

Excellent, thank you! I'll try to get some eyes on it.


Add link to information on latency issues

@kbaley : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@EdPrice-MSFT - Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
#assign:@MicrosoftDocs/public-repo-pr-review-team

The following users don't have valid GitHub IDs, or are not collaborators on this repo: microsoftdocs/public-repo-pr-review-team

It's a good overview, but it's there to advertise the company's services. It's not really about microservices on Azure.

@EdPrice-MSFT It's a link to a blog post on a very well-known topic in distributed computing that I believe is directly relevant to the text in that it's backing up the claim that latency can become a problem. I also don't believe it's promotional as the discussion focuses solely on the concepts with most of the links going to further discussions on the fallacies of distributed computing. It's not without precedent on Microsoft's docs.

Hi everyone. Would it be possible to re-consider based on my previous comments?

@ShannonLeavitt I understand this is closed but was wondering if it could be reconsidered

Hi @kbaley - That's a question for @EdPrice-MSFT :)


Flush Metrics

I am using the DD Metrics function to publish metrics scraped from a Prometheus endpoint over to Datadog via a lambda.
Is there a way to flush the metrics into batches as in each scrape I am getting around 35,000 metrics which If I just call
		ddLambda.Metric(
			v.Name,  // Metric name
			v.Value, // Metric value
			tags..., // Associated tags
		)

Then I get the error -
"datadog: failed to flush metrics to datadog API: with no retry: Failed to send metrics to API. Status Code 413
Along with Payload to large.
Thanks :)

@pixie79 I'm not sure our solution was designed to support that use case. Just curious, https://www.datadoghq.com/blog/monitor-prometheus-metrics/ doesn't work for you?

Sorry not in our situation as we have a no internal apps so we cant run the datadog agent :(

@pixie79 Sorry for the late reply. I assume you are sending the metrics directly to the API? Perhaps you can try sending metrics over the Datadog Lambda Extension instead? I think the Extension does aggregate the metrics before sending them to the API, and in general it is more optimized for handling large volume of data.

Hi,
No I am using the DataDog-lambda-go package which I think is the extension?
Mark

Do you have a Lambda layer named with Datadog-Extension installed to your Lambda function?

Hi,
Sorry, yes i have checked that layer is present as well.
Regards
Mark

@pixie79 I'm so sorry that I missed your last reply and dropped the ball here. I hope that you have figured out a solution on your own. If not, could you open a support ticket for follow up? Github issue is apparently not a great place for back and forth discussions. I'm closing this issue in favor of following up over our support channel. Again, sorry for the super late response.


disable "Time" and "Time and Distance" selection

Let's disable these selections for demo purposes. We can still display them so that we allude to the eventual capabilities, but I don't want to mix dummy data with real data-- it's just confusing to track what's actually computed vs. what's placeholder.
corresponding issue in backend: https://github.com/bayesimpact/time-distance-standards/issues/89

Should we also remove min/max/average time from report drawer and csv download?

Good idea- can we just add "-" as the values, but keep the columns?

@bcherny It appears that "Distance" was also disabled, which shouldn't have been. I would expect that we can still adjust the 15 mi, 30 mi, and 45 mi distance parameters-- I just wanted to disable the calculations we weren't actually calculating.

My mistake - looks like @akegan fixed it!


Review and correct (if needed) the new Wiki Home

Contact Details (optional)
No response
Background
@RISC-OS-Community/code-reviews-team / @RISC-OS-Community/docs-team ,
If someone has time, could you please review and correct the new Wiki Home for the DME Project?
link here: https://github.com/RISC-OS-Community/DME-Core/wiki
Thanks!
Definition of Done

[x] Task A is done when. the wiki page is reviewed :)

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I have had a look and updated the wiki a bit. Looks good to me.

Thanks @skymandr for your help!
Closing this issue as fully resolved :)


Add option to disable <Hint />

We provide options for most other features, so maybe we should for this as well if people request it.

Is there a user need for an option? I think this might be something where research shows its just best to show a hint all the time or not?

@joelanman we don't have evidence of a need but I think it's OK to provide the option; gives users one less reason to potentially have to fork the component to get the behaviour they want. Quite a few users will not communicate on our issue tracker if something about it isn't to their liking. Rather, they will just not bother using it.


[Avocado] Make Avocado support permanent suppressions via config

AutoRest plugins like LintDiff can be suppressed according to these instructions:

https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/85/Swagger-Suppression-Process
https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/828/How-to-suppress-validation-rules

Avocado cannot be suppressed like that (i.e. via AutoRest config file, i.e. the README). It can only by be suppressed for given PR by adding Approved-Avocado label.
Avocado cannot be suppressed permanently as it is not an AutoRest plugin.
The Avocado call chain looks like that:

Avocado.yml invocation from .azure-pipelines.yml
script: './node_modules/.bin/avocado -f pipe.log --excludePaths "/common-types/" "/scenarios/" "/package.json" "/package-lock.json" "/cadl/examples/" --includePaths "data-plane" "resource-manager"' invocation from Avocado.yml
avocado function definition

This work item is about making it possible to suppress Avocado permanently.
One possible way to solve this is to make Avocado read and interpret the AutoRest suppression syntax. Avocado is already reading the AutoRest config file (the README) as part of its implementation. This would require reimplementing the AutoRest suppression parsing logic, including json path parsing, inside Avocado.

For example, multiple default tags error should be suppressed for Microsoft.Resources namespace. See this Teams thread.

Delaying this item as we made Avocado non-blocking few months ago.


alternative to termios dependency

hi,
so im trying to get it to run in pycharm on windows which needs termios and termios is Linux only...
i´d normally just switch over to Linux but the finished tool has to work on both so i can´t realy do that here.
is it possible to substitute termios for windows or have a version with some more compatible library? i´d be fine with using 2 seperate libraries for Linux and Windows if this allows me to have it work properly.

You're right, this does not currently run under windows. There are two things that stop it from working immediately:

It relies on the readline module, which isn't part of the Windows build of Python. This could be overcome by listing pyreadline as a prerequisite for the Windows platform.
It relies on the curses module, which again isn't part of the Windows build of Python. This one is more difficult to replace. I think the solution would be to replace the use of curses with some other library that does the same sort of thing but also works on Windows. I'll have to look into that. In the short term, it could be possible to just try/except the import of curses and if it can't be found, disable the man page feature while allowing the rest of the library to work.

I'll try playing with these a bit and see what I can come up with.

On point 2 above, the windows-curses package seems to work fine, so that's good.
There didn't seem to be a good alternative for the termios module. This is probably OK, I just commented out the one place that used it, and for most cases it shouldn't be a big deal.
There's also no ability to handle the SIGQUIT signal in Windows. This means that you can't start the debugger inside the application by pressign ctrl+\ like you can on unix. This feature is not essential though and you can always put a breakpoint in code.
There's no ability to handle the SIGTSTP signal in Windows either. This means that async commands don't work quite the same since you can't put them in the background while they are already running. You can start a command in the background when you execute it with -background, but if you start it in the foreground (the default), you can't send it to the background.

I've released version 2021.4 which should work around the issues you were having. Please test it and let me know if you run into additional issues (probably in a separate issue).


Pointless cast warning

Original issue created by<EMAIL_ADDRESS>on 2013-02-26 at 08:59 PM

Casts degrade program readability, and ones that are not automatically removed by the JRE hurt performance.
Here's an example extracted from real code:
class A {}
class B : A {}
List<B> someList;
for (A a : someList)  // Line 1
{ ... ((B)a) ... }    // Line 2
Line 2 should trigger the warning, citing the needless up-cast on Line 1.

Can this "RedundantCast" be included now?


Order of multiple posts from the same day

Hi, maybe we need to save the time as well, because when you do more than one post per day they come out in an reversed alphabetical order.

What is your opinion on how to handle this issue, would it be better to change all the filenames to include the time or just add it to the front matter on top of the file and go from there?

I feel like the front-matter makes more sense. It might be pretty ugly having both the time and date in the filename.
I also like the idea of removing the date stamp from the filename all together.

Would be nice to get rid of the date stamp, but then we would need something like a folder structure to keep the posts organised, something like posts/year/month/title.markdown

Yeah I agree, I also like the idea of keeping the filenames as they are and using the front matter for ordering.

This issue has now been resolved. It'll be included in the next release (not sure when that will be but it wont be long)


[stable/aerospike] StatefulSet is now redeployed when confFile is updated

Is this a new chart
No
What this PR does / why we need it:
Redeploys StatefulSet when config is updated. Makes for a more convenient workflow
Which issue this PR fixes
No related issue filed
Special notes for your reviewer:
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

@okgolove @prydonius

/ok-to-test

/lgtm


Application to multispectral imagery

@BradNeuberg I've been looking into your blog post regarding this project, and it seems really nice. I wonder if you guys have applied this to multispectral imagery, which could narrow down the classification errors.

We haven't applied this to multispectral imagery but I'm interested in that
domain. Are you planning to try it?
On Thu, Jun 29, 2017 at 8:25 AM Ricardo Barros Lourenço <
<EMAIL_ADDRESS>wrote:

@BradNeuberg https://github.com/bradneuberg I've been looking into your
blog post regarding this project, and it seems really nice. I wonder if you
guys have applied this to multispectral imagery, which could narrow down
the classification errors.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/BradNeuberg/cloudless/issues/14, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJD0ZYPftN13OQuiRNF3gHa1GTm5m81ks5sI8HxgaJpZM4OJeEz
.

I'm working on a cloud classification problem for my master's paper. Perhaps working on the top of your findings would be good. Did you publish these findings in a journal?

I didn't get to publish my findings as I don't think they were quite strong
enough.
On Thu, Jun 29, 2017 at 10:50 AM Ricardo Barros Lourenço <
<EMAIL_ADDRESS>wrote:

I'm working on a cloud classification problem for my master's paper.
Perhaps working on the top of your findings would be good. Did you publish
these findings in a journal?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/BradNeuberg/cloudless/issues/14#issuecomment-312044542,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJD0Tb5yjTkwEP2PmR2AnZARK-8UIDrks5sI-PogaJpZM4OJeEz
.

Ok. Anyway is interesting even on the subject of image segmentation. I'm willing to reproduce your experiment, with the models you've provided. My research is regarding cloud classification, and the segmentation would be an initial part. I assume that on your models, you are working with a png rib visible composite, right? Because my assets come from MODIS, and probably on GeoTIFF, so I need to map the scheme you've used.


File replacement for prod release not working

🐞 Bug report
Command (mark with an x)

[ ] new
[X] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?
NA
Description
Need to replace index.html with index.prod.html  when build with ng build
"configurations": {
            "production": {
              "fileReplacements": [
                {
                  "replace": "src/environments/environment.ts",
                  "with": "src/environments/environment.prod.ts"
                },
                {
                  "replace": "src/index.html",
                  "with": "src/index.prod.html"
                }
              ],
              "outputHashing": "all"
            },

🔥 Exception or Error

Schema validation failed with the following errors:
  Data path "/fileReplacements/1" must have required property 'src'.
  Data path "/fileReplacements/1/replace" must match pattern "\.(([cm]?j|t)sx?|json)$".
  Data path "/fileReplacements/1" must match exactly one schema in oneOf.de>
🌍 Your Environment

Angular CLI: 13.1.4
Node: 16.15.0
Package Manager: npm 8.5.5
OS: win32 x64

Angular: 13.1.3
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.1301.4
@angular-devkit/build-angular      13.3.5
@angular-devkit/core               13.1.4
@angular-devkit/schematics         13.1.4
@angular/cdk                       13.3.6
@angular/cli                       13.1.4
@angular/material                  13.3.6
@angular/material-moment-adapter   13.3.6
@schematics/angular                13.1.4
rxjs                               7.4.0
typescript                         4.5.5

This is working as intended.
See: https://github.com/angular/angular-cli/issues/14599

@alan-agius4

It seems while using index property we need to make sure have similar index.html. So let say you build with
"index":"src/index.prod.html",
So when you run ng build  the output file will be  index.prod.html and it won't work. We need index.html
In that case we need to use a different folder with index.html that we need to deploy for prod and update the path in angular.json
"index":"src/prod/index.html",
So not having the option under filereplacements seems to add complexity and pretty fussy.

You can use specify the output name when using the index output option.
{
    "index": {"input": "src/index.prod.html", "output": "index.html"
}

fileReplacements is intended to only replace files that are in the TypeScript program.

Thanks.


Allow a list of a vararg type to satisy varargs.

function f(list[integer] values...) {
    ...
}

list[integer] integer_list = [1, 2, 3]
f(integer_list)

The above should work, because list[integer] is wanted, and a single list of integers has been given. This won't be fixed to work for passing multiple satisfying lists or anything complicated. This is mostly so that it's possible to filter varargs.
I can't think of a use case for this, but at the same time I can't think of a reason to not do this.

I originally added this because I thought that it would be really easy to do. However, now that generics have been thrown into the mix, such is no longer the case. Type inference has also gotten a lot stronger.
The problem with implementing this is that it's gonna go down a not so great path...
varargs has to descend into the tree that's given and determine if it's tree_list. In such a case, it has to keep descending and matching to determine if there are as many list entries as there are lists that are needed. If list[list[integer]] is wanted and [[1]] is given, then pass that as the one and only argument. But...this is a bit harder with generics. Especially in cases where the generic hasn't been solved yet. Suppose that A is called for (and unsolved), but [] is given. That's a bit tricky to figure out, in terms of the internals.
The alternative is to walk a tree expecting, say, integer, not getting it, then trying again with list[integer]. But, wait, some trees damage the ast to make things work (call, specifically). Worse, this allocates storages, and it's not possible to determine what storages that a given walk will have added without some considerable work.
In contrast, the benefits of this aren't that big. One obvious winner is that vararg-styled functions could pass their vararg parts to each other. I can't think of anything else that would benefit from this in the short term.
My final verdict, in case anyone happens to dig through these is this: I'm open to doing this if there's an easy, sane way to do it, or there's a compelling case for it. However, as it stands, the only ideas I have are nasty (it's not an easy idea to implement), and the benefits are currently none. Therefore, I'm closing this as 'wontfix'.


How to show Red icon in Allure report, say when some test cases steps are failing

We can use the below code to Write logs to Allure report for Appium framework.
 @Step("{0}")
    public void log(final String message) {
        //Kept empty Intentionally

    }

This will print the message in allure as i want. Now suppose there is some fail test steps and i want to represent them in my allure report. How can i do that?
When some line throws Exceptions then allure will say test case failed which is fine, but i need a single step to be show as failed.

public void log(final String message, final Status status) {
    Allure.getLifecycle().fire(new StepStartedEvent().withName(name));
    Allure.getLifecycle().fire(new StepEvent() {
        @Override
        public void process(Step step) {
            step.setStatus(status);
        }
    });
    Allure.getLifecycle().fire(new StepFinishedEvent());
}

for latest 2.50 the above code not working please help me on this