Pause/Play command

Is it possible to send a Play/Pause command to deej when pressing a button connected to the Arduino?

I understand, but it would be nice if this feature gets added to deej though 😊

i second this, although it would like expand it to general media buttons such as end call, stop & skip song, and mute for the different sliders

The main repo is mostly abandoned, but there are many forks of Deej with extensive changes:
https://github.com/Miodec/deej
This one adds the keybd_event library for configurable button mapping.

Aah I see, I didn't know this is mostly abandoned , thanks for letting me know, and I will check out other forks.

Aah I see, I didn't know this is mostly abandoned , thanks for letting me know, and I will check out other forks.

Hi there.
I was facing the same issue before I decided to Fork this amazing (but abandoned) project myself as plenty other did. It is unfortunate that we cannot consolidate features into one single repo which should be the goal of github instead of having hundreds of tiny mods all over the place.
It is indeed very possible to have touch buttons, hardwired, capacitive or anything you want. You can checkout the code on my repo I have implemented such a possibility in the Go portion of the project, along with various interesting mods I have gathered around. I am working on Linux so not sure yet if the code properly deploys on Windows. There might be some sticky bits with one architecture or another such as key mappings different in these systems for some functions, but with proper testing it should all be solvable quite easily.
Keep in mind that Arduino while a great tool for starters and also because of its decent ADC chip, seems quite a bit outdated compared to current possibilities offered by various MCU devboards. Arduino is not much simpler than other MCU as long as you have a good grasp on C++.
Keep in mind that while my code is in a working state (I have it running for several weeks now), it needs some cleanup as I used to be totally new to Go Language apart from compiling Loki Docker driver for a Raspberry Pi once in a while. Also you will have to modify your Arduino code but it is quite simple. Let me know if you need some tips.
The architecture of this project code is dual.  It is by far the most remarkable piece of software of the project. The other part is the client side which is by default a simple Arduino script. There are millions of possibilities with such an architecture. Some people hardwired their switch to pulldown the fader (ghetto style),, but you can go as far as you like. At the moment I have implemented software defined fader curve and it allows you to tweak the response of any fader you have in your build.
I intend to refactor the server code for good once I have my hardware complete with all the features I wantto implement. I will update my repo with all information soon.

Hi there @Adib-C, @neroes, @TheScabbage and @Lefuneste83 - thank you for writing.
First and foremost please let me address the primary subject of this issue - media controls (and more broadly, key bindings). They're something I consider to be out-of-scope for the vanilla version of deej at this point in time. I might opt to add them in a future release, but until then - as mentioned above there are forks with support for this functionality and I encourage you to use those forks instead.
I'd like to also take the time to address the above comments regarding the project's state and to clarify - deej is not an abandoned project. The notion that it's abandoned is honestly quite preposterous to me. A project not receiving issue comments from its maintainer for a few weeks doesn't make it abandoned - nor that it hadn't had pushed commits in an admittedly long time, and thirdly nor that it has a non-standard contribution policy.
Let's talk about that third point briefly - specifically to address this comment:

It is unfortunate that we cannot consolidate features into one single repo which should be the goal of github

Well, yes but not really. GitHub is a collaborative platform, but on the other hand - open-source can mean a wide range of things and its most basic definition is "the source code is freely available". It doesn't necessarily imply open collaboration. The reasons I outlined in my above document (for not wanting to receive direct contributions to this main repository) have not changed since that document was written.
The notion of "consolidating features into a single repo" sounds like a wonderful thing, but the nature of how customizable and how personalized this project can be simply means that there is no sane way to support and maintain the large amount of features thought up by the thousands of users within the deej community - all in one place. I see the existence of hundreds of different forks which accomplish different features - some with broad appeal and some extremely niche - as a good thing, in spite of their discoverability leaving a lot to be desired.
Finally, I'd like to point out a couple of other things that should (in my opinion) signal that deej is nowhere near being at an abandoned state:

it has an active Discord community with over 6000 members, including an extensive build showcase channel which sees new builds by members posted almost daily, as well as including several authors of prominent forks who often answer community-posted questions regarding functionality in their forks
there is behind-the-scenes work by me on the next deej release, which includes a massive overhaul to the connection mechanism aimed at improving robustness and stability as well as a decent amount of bug fixes (there is no designated ETA for this version's release - I work on it alone and at my own discretion, as mentioned in the document linked above)

If you'd like to continue the discussion on the project's state, I encourage you to DM me through the project's Discord server; I realize this response is very defensive, it's just difficult for me to see the "abandoned" term being thrown around in this manner - deej is extremely dear to me and so it was important for me to take the time and clear up my own point-of-view. If you took the time to read through all of this - thank you.


[feature request] Support other cryptocurrencies like Zcash

Ideally, the market could be currency-agnostic. Zcash uses zero-knowledge security for privacy. There is a Bitcoin API for multisig transactions. While these transactions don't yet have privacy it is being worked on

Thanks for the suggestion. I'd like to support Monero in the new web version of Bitmarkets when they add multisig support and there is a javascript client (websocket gateways would be needed).

How about Zcash? You would need multisig (☑) and a Javascript client (☐)?

Yeah, I'd be happy to support Zcash if there was an in-browser JS wallet library (with multi-sig support) for it that could connect to lots of independent Zcash nodes via websockets.

What's the status of a in-browser JS SPV wallet for zcash?


Unclear text, please make it easy to understand or have some images

[Enter feedback here]
If the setting is Overridable and Value can be overridden is set to Environment and app the setting app value is returned.
This statement is so unclear and may be grammatically incorrect making it hard to understand. Please correct it and may be add images to make the point clear. Thanks

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

ID: f1feb676-9456-117a-1462-2fb0a6d1562c
Version Independent ID: f1feb676-9456-117a-1462-2fb0a6d1562c
Content: Get or update setting value using client API - Power Apps
Content Source: powerapps-docs/developer/model-driven-apps/clientapi/get-update-setting-value-using-code.md
Service: powerapps
Sub-service: dataverse-developer
GitHub Login: @HemantGaur
Microsoft Alias: hemantg

@zoh-akh
Thanks for your feedback.  That dense text packed together is hard to read.
I've split it out into nested bullet points and presented the values as bold text consistently.

OLD
NEW

I hope this helps.


X10

Description:
Adding X10 support
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#5469
Example entry for configuration.yaml (if applicable):
insteon_plm:
  port: /dev/insteon
  device_override:
    address: 44899f
    cat: 0x00
    subcat: 0x1b
  x10_all_units_off: a
  x10_all_lights_off: b
  x10_all_lights_on: c
  x10_devices:
   - housecode: c
     unitcode: 12
     platform: switch
   - housecode: b
     unitcode: 9
     platform: light
     dim_steps: 64
   - housecode: b
     unitcode: 3
     platform: binary_sensor

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[X] New dependencies have been added to the REQUIREMENTS variable (example).
[X] New dependencies are only imported inside functions that use them (example).
[X] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Want to make sure this PR is not lost in the process.

Having tested this personally on a live system I can say that it has been effective in adding the X10 function without impacting legacy Insteon function.

@balloob Sorry to bother you and I am trying to respect the process but this PR has been sitting for almost three weeks with no movement. I don't see any other PRs that have sat this long with no review at all.

Sorry for the delay, this PR looks great ! I'll tag it for the 0.72 release.

Thank you! This has been one of the biggest complaints from the Insteon community that OpenHAB has X10 support and HA did not so I think this is a very good improvement to help people who want to move from OpenHab.


support UE5.5

@yuokamoto,
This PR supports UE5.5. Tested via turtlebot3-UE project with following condition:

Ubutnu 24.04
UE5.5
ROS 2 jazzy(binary install)
Nav2 jazzy(source build)
rclUE(branch: UE5_devel_jazzy)

Thanks for your commitment always!


[tests-only]Skip litmus on docs-only title

Description
This PR skips litmus tests in docs-only.
Related Issue

litmus tests fail on docs-only PRs

How Has This Been Tested?

CI [https://drone.owncloud.com/owncloud/ocis/12464]

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[x] Tests only (no source changes)

Checklist:

[x] Code changes
[ ] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

I raised issue #3949 to further optimize when litmus runs in CI.

See #3951 for the next change to this logic.


While using allure-commandline via npm, an error getting displayed

C:\Users\anarwal\IdeaProjects\cm-ui-automation>allure help
events.js:154
throw er; // Unhandled 'error' event
^
Error: spawn C:\Users\anarwal\AppData\Roaming\npm\node_modules\allure-commandline\dist\bin\allure
ENOENT
at exports._errnoException (util.js:856:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
at onErrorNT (internal/child_process.js:344:16)
at nextTickCallbackWith2Args (node.js:474:9)
at process._tickCallback (node.js:388:17)
at Function.Module.runMain (module.js:449:11)
at startup (node.js:139:18)
at node.js:999:3

I think this might be the cause of an error I have just reported as an issue against mocha-allure-reporter. See https://github.com/allure-framework/mocha-allure-reporter/issues/16

@anarwal sorry for a long response. Didn't get a notification about it.
Since that, I released new version 1.4.23. It also has some fixes for Windows. Maybe it helps you.

closed due to no response


runtime: Require 'start' to validate the bundle

This spec places RFC-2119 requirements on both bundles (bundle.md,
config.md, ...)  and runtimes (runtime.md, runtime-linux.md).  While
it's possible to envision a system where bundle validation is
decoupled and the runtime is free to blindly stumble through as far as
it can, it's likely that users will expect the runtime to perform
basic bundle validatation for them.  With the requirement landing in
this commit, the runtime MUST at least validate bundles against this
spec.  The runtime MAY also validate the bundle against the host
system's capabilities, but is not required to do so.
With this change, all RFC-2119 requirements are things the runtime is
responsible for.
I'm personally ok with the decoupled-bundle-validation approach (and
we already link to ocitools and OCT for testing both runtimes and
bundles), but figured that will be an outlier position.  If we do
want to go that way (and leave runtime activity in the face of an
invalid bundle undefined), we probably want to explicitly call that
out in the ‘start’ docs to avoid surprising people.

-1
Every runtime author should not be expected to write validation logic for every field in the spec.  Lets go with the decoupled approach.

Closing since you opened the alternate approach.

On Mon, May 02, 2016 at 11:16:26AM -0700, Michael Crosby wrote:

Lets go with the decoupled approach.

Filed in #418 for folks to compare.  Once one of the PRs lands, we can
close the other.


Mark recents for deletion with hourly sweeper workers

classification deletes are cascading down to recents which is a very slow removal and is now erroring due the the pg statement timeouts
instead of dependent :destroy on the classification->recents relation, move to a mark and sweep system where we use a background worker on a schedule to remove the recents. The advantage of this technique is:

it's quick and will not impact the classifcation destroy
it allows us to have implement a simple capped collection for recents (max 50 or so) which will be updated when new classifications come in.

The removal worker will cleanup any marked recents and any old recents past 14 days by default.
The migration will remove recents older than 14 days, leave the rest and remove the bloated indexes and rebuild the only ones we use for the API.
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

@camallen , a few questions for context:

classification deletes are cascading down to recents which is a very slow removal

A curiosity: what is the typical scenario for a classification being deleted? I see in the specs that there are cases where an incomplete classification is saved, in which case that classification can be deleted, though I haven't figured out how to actually do that on the front-end.
Why is the removal so slow? Shouldn't there only be one 'recent' entry for each classification? (and if so, why would that make deletion so slow?) Perhaps my understanding of what a recents record represents is incomplete, I know that you're able to view your recent classifications for a project by clicking the RECENTS tab, and Ive taken a look at the specs associated with recents.

The migration will remove recents older than 14 days, leave the rest and remove the bloated indexes and rebuild the only ones we use for the API.

When you say 'remove bloated indexes', do you mean just narrow down which columns we have indexes set on? Also, what is the purpose of deleting an index only to rebuild it? Why not just omit them from the removal?

@camallen , a few questions for context:

classification deletes are cascading down to recents which is a very slow removal

A curiosity: what is the typical scenario for a classification being deleted? I see in the specs that there are cases where an incomplete classification is saved, in which case that classification can be deleted, though I haven't figured out how to actually do that on the front-end.

Transcription projects, i believe ASM allows users to save their work in incomplete classifications and then delete / save them as completed. https://app.honeybadger.io/projects/40595/faults/62245893
Only incomplete classifications can be deleted, https://github.com/zooniverse/Panoptes/blob/422cfe7cfdfe98e542a43d17958699ae43f76380/app/policies/classification_policy.rb#L38

Why is the removal so slow? Shouldn't there only be one 'recent' entry for each classification? (and if so, why would that make deletion so slow?)

Yep - we don't link a classification to a recent, rather a recent to a classification. So the search for a recent is on a FK index on a large table. The query is slow for some reason (see the honey badger link above and errors), these errors spurned this work which is linked to migration of db data as well.

Perhaps my understanding of what a recents record represents is incomplete, I know that you're able to view your recent classifications for a project by clicking the RECENTS tab, and Ive taken a look at the specs associated with recents.

FWIW - we only show the last 20 recents in the UI but we keep all of them and they serve no purpose.

The migration will remove recents older than 14 days, leave the rest and remove the bloated indexes and rebuild the only ones we use for the API.

When you say 'remove bloated indexes', do you mean just narrow down which columns we have indexes set on?

Once you delete a lot of indexed records the index generally needs to be cleaned up / rebuilt. https://wiki.postgresql.org/wiki/Index_Maintenance#Index_Bloat

Also, what is the purpose of deleting an index only to rebuild it? Why not just omit them from the removal?

This will rebuild a fresh index with no 'bloat'. We do this concurrently to avoid blocking read / write operations on the underlying table, REINDEX will lock the table (at least in our PG version), https://www.postgresql.org/docs/9.5/sql-reindex.html

An index build with the CONCURRENTLY option failed, leaving an "invalid" index. Such indexes are useless but it can be convenient to use REINDEX to rebuild them. Note that REINDEX will not perform a concurrent build. To build the index without interfering with production you should drop the index and reissue the CREATE INDEX CONCURRENTLY command.

I should have added more context to the reasons behind this work. The crux is:

we only use the last 20 recents but store them all (think every classification we receive).
Serving the last 20 recents is costly for user / project combos (indexes are large too - we currently serve these from the replica db)
classificaiton deletes for ASM were timing out and erroring (probably breaking UX)
we are migrating the dbs, so we don't want to pay the data transfer cost if we don't need the data
Keeping less data / smaller indexes is better for the db generally as the indexes use less RAM (more for others) and we shrink our storage space requirements as well.

These above is why i scheduled some time for this work before the db migration, it's been on my list for a long time but wasn't critical or at least folks weren't complaining about it.
Hope this helps, let me know if you want more info.

Thanks @camallen , this is very helpful :smiley:


no kernel image is available for execution on the device

My envioroment is :

Ubuntu 16.06
CUDA: 9.0
Pytorch: http://download.pytorch.org/whl/cu90/torch-0.3.1-cp35-cp35m-linux_x86_64.whl

I excute my program and meet trouble like this:
Here the subfolder module stores the implementation of your method.

Did you already compile the code with proper settings for your GPUs?

@pkontschieder  Yes, I meet no errors when build your code.

@PkuRainBow do you have the file inplace_abn/modules/_ext/__ext.so ? If so, can you provide us with the output of the command nm -gC __ext.so ?


Patreon Subscription Required?

Do I understand correctly that you require users to pay for a subscription to have access to latest binaries for cyberpunk camera tools?  This is not a criticism.  I'm seeking to understand if this is a requirement.  I don't have the resources to support subscribing to your patreon, so am concerned I will no longer be able to use this tool.  Thank you.

Yes this is a requirement now. I've moved all my binaries to my patreon. I gave away the Cyberpunk camera tools for free for more than a month, and maintenance starts to taking a lot of time hence I no longer give it away for free (normally cameras I make are paid from the start btw).
Subscribing also gets you 2 other things btw: Cyberlit, a paid custom light tool which allows you to create custom lights in a scene and a cheat table to control lookat camera (head, eyes) for V. You can sub for 1 month and download all cameras, they keep on working after the month, till CDPR decides to update the engine and break things of course ;)


ESCU Correlation Rules lose relative time settings

In some cases, editing ESCU correlation rules in ES after enabling them results in the latest time and earliest time values being reverted to absolute (Unix time) values.

This probably related to how the Splunk Analytic Story Execution (ASX) App updates the ESCU Analytics stories detections when using the "Execute Now" feature.

If that is the case, it would probably be worth explaining how ASX works in more details and the side-effect(s) it might have on an ES environment.  In other words, executing Stories (and their related detections) with ASX will change scheduling times (to absolute values) and also change existing searches to save the results in the "asx" summary index (and probably preventing the generation of Notables from that point on).

Thank you very much for this feedback. Splunk Analytic Story Execution (ASX) App was a POC.


Automated scheduled container images build and scan

Automated scheduled container images build and scan
Automated scheduled container images build and scan should be added to workflow.
Work tracked in:

KF-942
KF-949

Design
Main design points:

Github workflows are used to trigger scheduled build and scan actions.
Build and scan are reused from images definitions feature.
Kubeflow CI repo is used for common scan reporting functionality and provides integration with automated Jira ticket creation workflow

Implementation
Two PRs in two different repos:

https://github.com/canonical/notebook-operators/pull/196
https://github.com/canonical/kubeflow-ci/pull/46

Testing

Verify that nightly build and scan was triggered.
After integration with automate Jira ticket creation workflow, verify that Jira tickes are created for correct components.

Fix is merged. Closing.


[Technical Writing] : Getting started with MERN

Description
I want to add an article about "Getting started with MERN"
This article  would have the following contents:

What a Web Framework is?
Configuring a MongoDB Atlas Cluster
Building a API with Express.js
Creating a React App
Setting a Proxy from your Backend API server to the Frontend React App
Styling and making Requests from the frontend

Outcomes:

Will understand how to work with the MERN stack
Will have made a full MERN application project from scratch
Will be able to explore other node frameworks as well

Screenshots
No Response
Checklist

[x] I have checked the existing issues.
[x] I follow Contributing Guidelines of this project.
[x] I am a GSSoC'24 contributor.
[x] I want to work on this issue.

Code of Conduct

[x] I agree to follow this project's "Code of Conduct".

Hello @AMS003010 and @CSEdgeOff , I want to work on this task. Can you please assign me this.


hotfix: add use_ema condition for extracting ema_vae in train_step

There was a mistake in previous PR.
I added if condition when calling
ema_vae = self.ema_vae.module if self.is_distributed else self.ema_vae

so it is to be:
if self.use_ema:
    ema_vae = self.ema_vae.module if self.is_distributed else self.ema_vae

in train_step.

@bzantium oh got it Minho! thanks for sending the pull request!


merge branches of schema

just creating an issue for this so it doesn't get lost - hope that's ok!

I have merged the branches. You might need to close and reopen Oxygen to clear its temporary cache.
I have a few questions:

All but one of your schematron rules is set up to be specific to Medieval. But the @key attributes ones would be good for every catalogue that wants the corresponding indexes on their web sites. The supportDesc/@material requirement is universally adhered to in all but a single manuscript in all the catalogues. The requirement to have a textLang in every msContents is more debatable, I guess, but could certainly be a recommendation. So, would you have any objection to making them generic, but with a role of "warn"?
The .rng was build back in October, so includes the changes in version 3.2.0 of TEI P5. But there is a new version 3.3.0 which was released last week. Whose job is it to review the changes and rebuild? Or is that not considered necessary for this project?
Do you want to keep the medieval-schematron branch?

I think it would be our responsibility to steward upgrades to the TEI schema and make sure it doesn't break anything.

I don't have any objections to making the schematron rules generic (and I can think of others we might add...) but maybe check with the other catalogue owners first in case the sudden appearance of red squares alarms them?
I suppose that updating the ODD (if that is necessary) and rebuilding the .rng after TEI updates should be the responsibility of the "owner" of the consolidated-tei schema, whoever that may be (? @andrew-morrison ?)
No need to keep the medieval-schematron branch

The sudden appearance of red squares is why I suggested giving those schematron rules a role of "warn". Then they'd be displayed as yellow triangles (when validating in Oxygen) instead. It also helps triage to have more than one level (e.g. the lack of a @key is something you'd want to fix, but not before tackling invalid TEI.)
I'll review TEI releases from now on, for things that might suddenly become invalid. I don't have time to do so for 3.3.0 now, but maybe next month.

Thanks for clarifying. Sounds like we are good to go ahead with this then. Can I suggest an additional rule now which is that origdate should always have one or more of the relevant dating attributes?
Get Outlook for Androidhttps://aka.ms/ghei36

From: andrew-morrison<EMAIL_ADDRESS>Sent: Tuesday, February 13, 2018 11:14:32 AM
To: bodleian/consolidated-tei-schema
Cc: holfordm; Author
Subject: Re: [bodleian/consolidated-tei-schema] merge branches of schema (#10)
The sudden appearance of red squares is why I suggested giving those schematron rules a role of "warn". Then they'd be displayed as yellow triangles (when validating in Oxygen) instead. It also helps triage to have more than one level (e.g. the lack of a @key is something you'd want to fix, but not before tackling invalid TEI.)
I'll review TEI releases from now on, for things that might suddenly become invalid. I don't have time to do so for 3.3.0 now, but maybe next month.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/bodleian/consolidated-tei-schema/issues/10#issuecomment-365235689, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATThVIEZVTAf0pxdxqY4DEbgkKByrQ8gks5tUW6YgaJpZM4R4Rzb.


Decode fixes

Eventually hit a bug, but producing output for the 1st time.
['AND', 'THE', 'AND']
['AND', 'THEN']
['AND', 'THAT', 'THE', 'GROUND', 'AND', 'THE', 'WAS']
[]
['AND', 'THE']
['AND', 'THE', 'MEN', 'OF', 'WHICH', 'HAVE']
['BUT', 'THE', 'PASSION', 'OF', 'THE']
['AND', 'SEE', 'WHAT']
[]
['IT', 'WAS', 'ONE', 'OF', 'THE']
['SECOND', 'WHEN', 'THE']
[]
['AND', 'AND']
['AND', 'THEN']
['BUT', 'WITH']
['THAT', 'WAS', 'WITH']
['SINCE', 'ONE', 'OF', 'THE']
[]
[]
Traceback (most recent call last):
  File "decode.py", line 181, in <module>
    main()
  File "decode.py", line 155, in main
    results = decode(dataloader=test_dl,
  File "decode.py", line 93, in decode
    batch_idx, len(dataloader),
  File "/ceph-dan/.local/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 388, in __len__
    length = self._IterableDataset_len_called = len(self.dataset)  # type: ignore
TypeError: object of type 'K2SpeechRecognitionIterableDataset' has no len()
de-74279-k2-dev-0929153814-7686b86bc5-qbfjq:simple_v1:

IterableDatasets don't have len() specified due to their "dynamic" nature; you could count the number of cuts processed so far (variable in each batch) and report it with regard to len(dataset.cuts)


Remove wait cycle on node join

kubeadm now supports polling on join https://github.com/kubernetes/kubernetes/pull/34703. No longer need for: https://github.com/kubenow/KubeNow/blob/master/bootstrap/node.sh#L8.

 Remove wait cycle on node join

Fixed in #160


[WIP] Add official integration READMEs to docs

What kind of changes does this PR include?

New or updated content
Changes to the docs site code

Description

Closes #945
Add a script to fetch the official integration READMEs and generate a page for each one
Add a CI job to run the script nightly and open a PR with changes
Add links to the new pages from the existing integrations guide

To do

[ ] Think about what we want these pages to look like.

Are we really fans of <details>?
What’s missing on these auto-generated pages?
Is there anything we want to remove?

[ ] Do we want to make changes to the actual READMEs now we’re seeing them in this context?
[x] Make the integrations navigation component pretty à la deploy guide
[ ] Make an integration page layout to include the nav component in the footer like for deploy guides
[x] Add a remark plugin to map video URLs to video embeds (see https://github.com/withastro/docs/pull/954#issuecomment-1179374828)
[x] Fix absolute links when using the footnote/reference/whatever it's called format
[ ] Remove table of contents as we have that in “On this page”. Do we need to tag these specially in the integration READMEs? A hide-in-docs class or something?

Looking great, @delucis !  I know there's lots to think about here, so I'm sure there will be more comments to come...
But I'm initially thinking in particular about the note at the top of these pages re: autogeneration. I know I personally never remember exactly WHERE I have to go to make edits to the original files for our config reference page, and have to go looking each time. So maybe expanding the comment at the top to something like:
# NOTE: This file is auto-generated from 'scripts/generate-integration-pages.ts' and pulls content directly from the package README .
# Do not make edits to it directly, they will be overwritten. For corrections, please edit the individual package README in https://github.com/withastro/astro/tree/main/packages/integrations

I'm noticing in the tailwind page that the included .mp4 video is being rendered just like it is on npm's site... as the text of the url with a clickable link to the video instead of being playable inline. Do we have a way around this?

Are we fans of details?

We LOVE details, as a concept. 💜
I know we originally wondered, "Should INSTALL instructions be hidden behind details? Isn't that kind of a DON'T HIDE thing?"
At the time, it was possible to install these integrations through create-astro and I think it was common that you'd often know upfront if you wanted e.g. Tailwind. So, even astro add wasn't THAT big a thing to surface. Maybe now that everyone will have to astro add, it shold be plastered more prominently? Or, I could see the opposite argument. If ALL these things can be astro added, then it's gonna say that clearly on the main integrations page, a user may very well be astro adding a bunch of stuff, and the command will be a bit more common knowledge anyway.
I'm going to say loud +1 on detailing away at the very least manual install instructions. We shouldn't really need them soon (and at least in tailwind doc, astro add is still mentioned as "experimental" so that can change any time.) That's all I have a definite opinion about right now.

Adding a note to remind us to check on all these install instructions now that there have been changes to create-astro and astro-add. E.g. Is this still relevant?

I checked a random sample of these, and NONE of them show any information under Changelog (at the source).
Since the original is the package README, I'm assuming we'd need to add these in manually there to get them to update? That seems like a lot of maintanance. I'm wondering whether we:
(a) remove Changelog from those READMEs at the source, if they're not going to be updated and independently
(b) consider pulling this info in to the Astro file from the package somewhere else, if we decide we still want it? If not a full changelog, a version number or last updated date?

Similarly, the Contributing section makes sense as a package README, but I'm wondering whether we just not show that for docs? Presumably, anyone at the stage of wanting to contribute to the package will visit the package directly? We don't mention contributing to any other packages/features throughout the docs.

I checked a random sample of these, and NONE of them show any information under Changelog (at the source).

I did add this to the Preact README when I was updating it a few weeks back: https://deploy-preview-954--astro-docs-2.netlify.app/en/guides/integrations/preact/
I’d suggest copying that verbatim for all of these — I usually like having the CHANGELOG easy to reach for packages when I’m upgrading.

the Contributing section makes sense as a package README, but I'm wondering whether we just not show that for docs?

It is not super easy to delete specific sections — I can do something but it would likely end up being quite fragile. I’m going to try that for the ToCs now, but I’m a bit hesitant to go too much in that direction as it would likely break when content changes on GitHub.
We probably need to make our peace with some weirdness on these pages. But maybe it would help if I make it clearer somehow that this is a README? Like some design touches that hint at the fact that you’re reading a README rather than just another page on docs.

I did add this to the Preact README when I was updating it a few weeks back: deploy-preview-954--astro-docs-2.netlify.app/en/guides/integrations/preact
I’d suggest copying that verbatim for all of these — I usually like having the CHANGELOG easy to reach for packages when I’m upgrading.

I like that! Yes, let's do that.

It is not super easy to delete specific sections
That's fine! It was "just my initial thought!"  ;)

I can make peace with it!

@delucis This looks fantastic!
Now that we have all this, I think at a minimum, here are some quick changes to make to the main Integrations page in docs:

Remove the React tutorial entirely. Now that astro add is stable for all the official integrations, AND it links to every single set of READMEs with installation instructions there, I don't think this page needs to show an example of the long method.
Re the EXPERIMENTAL note:

Swap the order of the 2 paragraphs inside the note. It's really only 3rd party that are experimental, so let's highlight THAT, and make the follow up text that official integrations are fine and totally supported
Move the note down lower, maybe right before Using Integrations? But definitely lower.

The Automatic Integration Setup needs to be slightly redrafted to remove reference to:
1. being experimental
2. "instead of the manual install intstructions above"
3. I think we'll find this can be streamlined in genearl now, but at least those 2 things will stand out
Handling Peer depenencies: I almost don't even want this here anymore? I think it's big and it's distracting. Wild idea: this gets moved into troublshooting. Less wild idea: this text is streamlined, maybe even into a note.  I just don't think it's as big an issue anymore to take up so much real estate, especially before even getting to "Using Integrations." We could simply comment it out for now, and I can slowly rewrite and bring it back in in some form.


[Bug] [dev branch] Version 2.3.5 of dev packages and runs on the server with an error message

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
错误: 找不到或无法加载主类
SeaTunnel Version
dev 2.3.5
SeaTunnel Config
无

Running Command
bin/seatunnel-cluster.sh

Error Exception
错误: 找不到或无法加载主类

Zeta or Flink or Spark Version
No response
Java or Scala Version
1.8
Screenshots

Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

package with window?

package with windows?
yes

package with windows?
yes

you need change the starter shell command file line separator from windows (CRLF) to unix (LF)


private method should be set accessible before invoked

The declared methods contains private method.
mvel2 version: 2.4.0.Final

@jearton can you expand on what exactly is the issue? There is code to allow invocation of private methods:
https://github.com/mvel/mvel/blob/97071e83fbafb5b25360756f0f551837a648a07c/src/main/java/org/mvel2/PropertyAccessor.java#L601

Please note that invoking non-public methods may sometimes fail under high multi-thread load since "setAccessible(false)" is invoked immediately after invoking "setAccessible(false)" and making the call (In PropertyAccessor). The call to setAccessible(false) is probably not required since you get a new instance with its own accessibility state each time you retrieve the method.

@jearton can you expand on what exactly is the issue? There is code to allow invocation of private methods:
https://github.com/mvel/mvel/blob/97071e83fbafb5b25360756f0f551837a648a07c/src/main/java/org/mvel2/PropertyAccessor.java#L601

public class Service {
      private void hello() {System.out.println("hello world");}
}

@Test
public void test() {
      Map<String, Object> vars = new HashMap<>();
      vars.put("service", new Service());

     MVEL.eval("service.hello()", vars);
}

Thanks. I wasn't thinking about the direct mode (I generally use MVEL.compileExpression() - and these modes have completely different implementations).
I performed the test with compiled mode and it failed with a MVEL "unable to resolve" message, so I think the direct mode should do the same (instead of  throwing the "unable to invoke method" as it does now).
The code that I referred to before does not come into play, it appears to be invoked when the method is public but the class is not.
Bottom line: To be consistent this test should fail but with a different exception.


HTTPS

Is it possible to use https?

Same ask. Seems it only supports http now?
https://github.com/localtunnel/server/blob/master/server.js#L116
But why there is --secure then?


Update main.yml to add dependencies

This makes this role compatible with ansible 1.8 and ansible-galaxy.
Thanks for the great role!

Thank you!


Update deps, chokidar, replace some devDeps with smaller ones

Updates deps to compatible versions
Updates to chokidar v4

Many fewer deps, but no more globs. We didn't need that anyway.

Swaps chalk for picocolors, matching hereby

Moderately pointless; chalk is pulled in from transitive deps.

Swaps glob for tinyglobby.

Moderately pointless; c8 still uses glob v10, mocha uses glob v8 (which causes our npm warnings)

I'll probably revert picocolors and glob since they don't actually improve anything.


Click to Expand Tab on Split Screen Broken

Steps to Reproduce:

Open VSCode and view 2 files/tabs
Split one of the tabs right
Minimize/resize the right tab as much as possible by sliding the tab as far right as possible.
Try single & double clicking into the minimized tab to expand it

This used action used to expand the minimized tab to open at about 80%.

Does this issue occur when all extensions are disabled?: Yes

Duplicate of https://github.com/Microsoft/vscode/issues/51614


CUDA: Add support for CUDA 12.0 Windows conda packages

Windows CUDA 12.x conda packages place libraries in the Library subdir of the environment. This is an additional location to search, so no logic is removed, in order that libraries from 11.x packages will continue to be found.
Testing with the packages suggested in https://github.com/conda-forge/numba-feedstock/issues/130#issuecomment-1806595555:
conda install -c conda-forge cuda-version=12.0 cuda-nvcc-impl cuda-nvrtc

gives the following library test output for me on Windows:
(numba-issue-9278) C:\work\numbadev\numba [main ≡ +0 ~1 -0 !]> python -c "from numba.cuda.cudadrv.libs import test; test()"
Finding driver from candidates:
        nvcuda.dll
        \windows\system32\nvcuda.dll
Using loader <class 'ctypes.WinDLL'>
        Trying to load driver...        ok
                Loaded from nvcuda.dll
Finding nvvm from Conda environment (NVIDIA package)
        Located at C:\work\miniconda3\envs\numba-issue-9278\Library\nvvm\bin\nvvm64_40_0.dll
        Trying to open library...       ok
Finding nvrtc from Conda environment (NVIDIA package)
        Located at C:\work\miniconda3\envs\numba-issue-9278\Library\bin\nvrtc64_120_0.dll
        Trying to open library...       ok
Finding cudart from Conda environment (NVIDIA package)
        Located at C:\work\miniconda3\envs\numba-issue-9278\Library\bin\cudart64_12.dll
        Trying to open library...       ok
Finding cudadevrt from Conda environment (NVIDIA package)
        Located at C:\work\miniconda3\envs\numba-issue-9278\Library\lib\cudadevrt.lib
        Checking library...     ok
Finding libdevice from Conda environment (NVIDIA package)
        Located at C:\work\miniconda3\envs\numba-issue-9278\Library\nvvm\libdevice\libdevice.10.bc
        Checking library...     ok

This is without modifying my existing environment variables - I have:
(numba-issue-9278) C:\work\numbadev\numba [issue-9278]> echo $env:CUDA_PATH
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.4
(numba-issue-9278) C:\work\numbadev\numba [issue-9278]> echo $env:CUDA_HOME
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.4
(numba-issue-9278) C:\work\numbadev\numba [issue-9278]>

Fixes #9278.
cc @jakirkham

gpuci run tests

@esc Could this have a buildfarm run please? It should resolve the Windows CUDA 12 issues on the farm - if it does, then I think that would demonstrate that the code here fulfils its intended purpose.


Add and_ converter

Pull Request Check List
This is just a reminder about the most common mistakes.  Please make sure that you tick all appropriate boxes.  But please read our contribution guide at least once, it will save you unnecessary review cycles!
If an item doesn't apply to your pull request, check it anyway to make it apparent that there's nothing to do.

[V] Added tests for changed code.
[V] New features have been added to our Hypothesis testing strategy.
[V] Changes or additions to public APIs are reflected in our type stubs (files ending in .pyi).

[V] ...and used in the stub test file tests/typing_example.py.

[V] Updated documentation for changed code.

[V] New functions/classes have to be added to docs/api.rst by hand.
[V] Changes to the signature of @attr.s() have to be added by hand too.
[V] Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives.

[V] Documentation in .rst files is written using semantic newlines.
[V] Changes (and possible deprecations) have news fragments in changelog.d.

If you have any questions to any of the points above, just submit and ask!  This checklist is here to help you, not to deter you from contributing!

Looks good overall, please address what I've mentioned.
The answer to how to test a nested function: you find a way to exercise it. :) But I believe you do that now?

Well I did, but it was mentioned that I missed testing the nested function + the codecov check failed so I just wondering how can I pass it

@hynek it seems I still miss some..
What I'm I missing here :thinking:

Looks like either out-of-date branch or another codecov glitch.
I think we're done here, thank you for your patience!

@hynek Many thanks!


PageSpeed Insights flagging suboptimal image sizes

Web Stories AMP version: Page Speed insights flags image sizes.
Need image size option(thumbnail/medium/) & cropping option when insert.
Request is as plain as it is.

Hi there,
Could you perhaps share a URL to your story?

Hi there,
Could you perhaps share a URL to your story?

https://developers.google.com/speed/pagespeed/insights/?url=https://biggbossfans.in/web-stories/s14-ep19-next-captain/
Properly size images  :: 2.85 s

@swissspidy any further updates on this ?

Apologies, I seem to have missed your previous comment.
Thanks for sharing!
The Web Stories plugin already utilizes multiple image sizes to improve image loading. It looks though that we might be able to register some additional image sizes to further improve this under certain conditions.
In the meantime I suggest following the advice to compress your images or even automatically convert them to webp as that should be the first thing to improve.
Thanks again for your help.

What i'm saying is there is no option in web stories to select image size like thumbnail or medium etc.. by default it is linking & showing the original big size. Just for this plugin sake we cannot bring down the size/dimensions of original image. This plugin must adopt to the WordPress standards of providing option to insert the correct image size.
Please look from this perspective, im sure im making a valid point & which is also crucial too (especially mobile devices)

I see your point. Ideally the plugin should be making the correct choices and pick the image sizes. You as a user should not have to worry about it, which is why adding an option would put an unnecessary burden on your shoulders. So all I am saying is that we'll have to look into improving this where necessary


[LOG4J2-3319] Add support for log4j 1.2 API bundle in Eclipse IDE

This will add the "Eclipse-ExtensibleAPI" header to the manifest of "core" bundle, to allow any fragement (resp. the log4j 1.2 bridge) to extend the API of core bundle.

Should other modules include this type of change?

No, the change is made in log4j-core, only.
But have seen that several other libraries, like "log4j-appserver" or "log4j-cassandra" or ..., would benefit from this change, if developed within Eclipse IDE (resp. with their PDE tooling).

https://issues.apache.org/jira/browse/LOG4J2-3319

This looks like it should work. @garydgregory the fragments thing has to do with modules scanning for non-public bits for the most part. Generally, that means the 2.x plugin system needs the fragment hack to find and load plugins, but 3.x can rely on service definitions instead.

This was closed automatically by Github because we renamed the release-2.x branch to 2.x. Feel free to resubmit to the 2.x branch.


tour: Not many insights about best practices or tips

Context: https://go.dev/tour/methods/18
There could be  multiple ways of doing this exercise.
My solution is:
func (ip IPAddr) String() string {

	ipstr := fmt.Sprintf("%v", [4]byte(ip))

	ipstr = strings.ReplaceAll(strings.Trim(ipstr, "[]"), " ", ".")

	return ipstr
}

There should have any tip or best practice  explanation in terms of readability and efficiency.

I agree with this - the practice exercises are good but they should also have solutions so that it's easier for students to know that they wrote code the right way. Just because it ran and passed all the tests doesn't mean the code was using best practices.


Changes to CompactionDetails and CompactionLog to change APIs and fields

CompactionDetails no longer contains extra segment name and swap space count. This
will be determined by the BlobStoreCompactor at runtime. CompactionLog will provide
the ability to dynamically split a range of segments in CompactionDetails. The function
will be used to split the range when there aren't enough swaps to complete the compaction
at once.
Formatted and built on both OSx and Linux.
Primary reviewers: @xiahome, @cgtz
Unit testing

Class
Class, %
Method, %
Line, %
Test class

CompactionDetails
100% (1/ 1)
100% (5/ 5)
97.1% (34/ 35)
CompactionDetailsTest

CompactionLog
100% (3/ 3)
100% (24/ 24)
95.8% (137/ 143)
CompactionLogTest

Comments addressed.

Formatting and build confirmed.


[Components] Relayer + Robust reconnect

Implements and cleans-up the layering between MVC/Components.Server
Implements robust reconnect and prerender+reconnect

Enables components to be rendered on the server and then connect to them from the client.
Lifts the requirement to provide a selector when the component is being prerendered.
Retries sending missing batches and waits for the client to ack batches before discarding them.

Enables OnAfterRenderAsync to run when the rendered batch has been confirmed.

Notes on API changes

We've updated the APIs to be more clear:

RenderStaticComponentAsync is MVC basic support for rendering a static component without interaction.

`RenderComponentAsync is MVC integration with server-side blazor for rendering interactive components.
With this PRs we enable directly registering prerendered components from the call-site directly. We now don't require an element to prerender interactive components, we do this based on comments inserted on the document.
There are some API changes in the way we do prerendering to account for the need to know the componentId of the prerendered element. This API is not final and will evolve in the future towards a more performant API capable of writing the current prerendered content into the target output stream directly.

Scenarios
Interactive components prerendered from a Page/View
@(await Html.RenderComponentAsync<ComponentType>(args))
Startup
endpoints => {
  endpoints.MapComponentsHub()
  endpoints.MapFallbackToPage('/Host')
}

Interactive components not prerendered from a Page/View
@(await Html.ComponentAsync<ComponentType>(args)) // TBD This will emit a preregistered identifier
Startup
endpoints => {
  endpoints.MapComponentsHub()
  endpoints.MapFallbackToPage('/Host')
}

Static components from a Page/View
@(await Html.RenderStaticComponentAsync<ComponentType>(args))
Interactive components from a static page
endpoints => {
  // This scenario becomes way more niche now, so we might want to get rid
  // of all the overloads (and even this method) in favor of endpoints.MapHub<ComponentHub>(ComponentHub.DefaultPath);
  endpoints.MapComponentsHub().AddComponent<App>(selector: "app")
  endpoints.MapFallbackToFile('index.html') // making this up as i don't remember the exact syntax.
}

This PR covers scenarios 1, 3 and 4.

Don't see much for me to comment on as code owner. eng/ and *.csproj changes look fine.

@javiercn Thanks for your responsiveness to all this feedback. I think I've reviewed this as much as I can now. There are some remaining questions or requests for change among the 188 comments above (!), so please ping us when you think it's finalised.


Replaced feather with bcolz (Fixed)

The previous one dropped the indexes out of dataframe, which caused a few problems in use, but was still able to pass tests.

Lol, bcolz requires blaze which requires hdf5 which we got rid of because it was too difficult to manage. The humanity.

Well blaze isn't technically required but I have it in there for a plan I
have that I will tell you about to day, and it doesn't need the proprietary
backend since we aren't actually using it 😛
On Jan 4, 2017 10:13 AM, "Rob Schaefer"<EMAIL_ADDRESS>wrote:

Lol, bcolz requires blaze which requires hdf5 which we got rid of because
it was too difficult to manage. The humanity.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/schae234/Camoco/pull/48#issuecomment-270410775, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGw_Dux97ZcyjME78370yhpp6w-7gC_Zks5rO8TugaJpZM4LZXf3
.


Removed 2 instances of Concerto.

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


issuedjango

NOTE:

Please fill out the template below

Did you read the instructions in the README?
Y

Y/N

Have you read the instructions in CONTRIBUTING?
Y

Y/N

Have you written this article by yourself? Have you taken inspiration from anywhere and then written it in your words?
Yes,I took inspiration from various resources which includes youtube,quora,wikipedia and then wrote it in my words.

[Write here. Be specific.]

Thanks a lot ma'am!!


Questionnaire b

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Edited md file to complete assignment3
What did you learn from the changes you have made?
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
How were these changes tested?
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended

A3: Incomplete. Q1 - I was a bit confused by your answer, in particular "Because my target population is 30% of target population" - please clarify if you can, and think about other factors we learned about that can affect sample quality. Q2 - ok. Q3 - I think you're close, but can you rework your answer to better demonstrate your understanding of an observational study?

Will do.  Can I do the edits and re-submit later this week?  Thanks.

A3: Incomplete. Q1 - I was a bit confused by your answer, in particular "Because my target population is 30% of target population" - please clarify if you can, and think about other factors we learned about that can affect sample quality. Q2 - ok. Q3 - I think you're close, but can you rework your answer to better demonstrate your understanding of an observational study?

Hi there, I have edited my answers for Q1 and Q3.  Can you re-check please?  Thanks.


3xx HTTP status codes are counted as errors

The success of an HTTP response is defined incorrectly right now:
public static bool IsSuccessfulResponse(this HttpResponse httpResponse)
{
    return httpResponse.StatusCode >= StatusCodes.Status200OK && httpResponse.StatusCode < StatusCodes.Status300MultipleChoices;
}

3xx status codes are considered "unsuccessful", but they should not.
E.g. there is nothing unsuccessful about a 304 Not Modified response.
Maybe this was implemented to be consistent with HttpResponseMessage.IsSuccessStatusCode, but I think it does not have to be. On the client we may want to have a stricter check of the status code (200..299), e.g. to make sure we are safe to read the body, but on the server the notion of success should less strict, otherwise the metric OneMinErrorPercentageRate and the like give false alarms.
I propose to change the above method to
public static bool IsSuccessfulResponse(this HttpResponse httpResponse)
{
      return httpResponse.StatusCode < StatusCodes.Status400BadRequest;
}

Or you could just configure it...
.UseMetricsWebTracking(o =>                 {                     o.IgnoredHttpStatusCodes = new List<int>                     {                         101, 304                     };                 })

@franjom this is the workaround I'm currently using, but unfortunately it has a side effect of excluding the responses from the application_httprequests_transactions_per_endpoint metric, so the fix is still necessary, as I see it.


Update Security Hub Level 100 Lab

Description of changes
Much of the content for the Enable Security Hub lab was a bit dated. Worked through the lab and then updated much of the content to present-day.

Shortened the title for simplicity
Added configuration instructions for AWS Config, which is required for Security Hub
Updated many of the screenshots to display the new user experience.
Added tear-down page to explicitly describe what might incur charges and how to remove them.
Added additional reference documentation.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@cmd-not-found  your contribution is greatly appreciated, thank you!


Revert "Partial rollback of #10204"

Reverts flutter/flutter#10256
Issue is fixed on Fuchsia's end.

When checking in when the tree is red, please make sure to include a message explaining why you feel it is justified to do so (e.g. if the failure is flaky or if the checkin is intended to fix the redness).


The push-processor Lambda can notify an SNS topic

As discussed, only add a global sns_topic for the whole push-processor. Not specific topic for each output at the moment.

This change is

Review status: 0 of 2 files reviewed at latest revision, 3 unresolved discussions.

humilis_push_processor/meta.yaml.j2, line 47 at r1 (raw file):

        {% if sns_topic %}
        meta_sns_topic:

There is no need of having a meta_ prefix here. It was needed for the input/error/output ones, I can explain you why if you want to know. This would be simpler in my opinion:
sns_topic_name:
    description:
        The name of a SNS topic the lambda can use to send notifications
    value:
        # You can simply leave this empty meaning: by default there is no SNS topic

No need to have any conditional here. If the user does not provide the

humilis_push_processor/resources.yaml.j2, line 16 at r1 (raw file):

{% set meta_input = meta_input or {} %}
{% set meta_network = meta_network or {} %}
{% set meta_sns_topic = meta_sns_topic or {} %}

No need for this.

humilis_push_processor/resources.yaml.j2, line 186 at r1 (raw file):

                    - "ec2:DeleteNetworkInterface"
                  Resource: "*"
                  {% if meta_sns_topic %}

Simpler:
{% if sns_topic_name %}
...
{% endif %}

Comments from Reviewable

I have updated the PR and acknowledged all your comments but Reviewable doesn't allow me to Publish without writing an useless comment. That's why you are reading this atm...

Review status: 0 of 2 files reviewed at latest revision, 3 unresolved discussions.

Comments from Reviewable

Reviewed 2 of 2 files at r2.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

Comments from Reviewable

Review status: all files reviewed at latest revision, 3 unresolved discussions.

humilis_push_processor/meta.yaml.j2, line 47 at r1 (raw file):
Previously, germangh (German Gomez-Herrero) wrote…
> There is no need of having a `meta_` prefix here. It was needed for the `input/error/output` ones, I can explain you why if you want to know. This would be simpler in my opinion:
>
> ```
> sns_topic_name:
>     description:
>         The name of a SNS topic the lambda can use to send notifications
>     value:
>         # You can simply leave this empty meaning: by default there is no SNS topic
> ```
>
> No need to have any conditional here. If the user does not provide the

Done.

humilis_push_processor/resources.yaml.j2, line 16 at r1 (raw file):
Previously, germangh (German Gomez-Herrero) wrote…
> No need for this.

Done.

humilis_push_processor/resources.yaml.j2, line 186 at r1 (raw file):
Previously, germangh (German Gomez-Herrero) wrote…
> Simpler:
>
> ```
> {% if sns_topic_name %}
> ...
> {% endif %}
> ```

Done.

Comments from Reviewable


[flink] ContinuousFileSplitEnumerator.assignSplits should be thread safe

Purpose

Method should be synchronized because {@link #handleSplitRequest} and {@link #processDiscoveredSplits} have thread conflicts.

Tests

API and Format

Documentation

+1


chore(main): release 1.1.7

:robot: I have created a release beep boop
1.1.7 (2023-03-18)
Build System

deps: bump actions/setup-node from 1 to 3 (a2a5473)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/School-of-Website-Engineering/future-front-end/releases/tag/v1.1.7 :sunflower:


Can not found api

Hello, i used command yo meanjs:crud-module to create articles CRUD. But when i click to create post, meanjs can not found link POST http://localhost:3000/articles/api/articles 404 (Not Found)
And how to render html data with meanjs

@GinVlad you choose the wrong link to find the api.
as i can see here articles/server/routes
you need following url instead http://localhost:3000/api/articles/

@billyjov Is correct.
The MEANJS Generator is out of syc with the current master branch. We moved away from using a <base> tag in our Layout template. See https://github.com/meanjs/mean/pull/1544
@GinVlad In order to fix this issue you will need to prefix your API end-points from your client-side services with a /. See the articles service. There may be other instances where you need to add the "/" to. The above mentioned PR should be a good guide to reconcile the differences.
Unfortunately, the generator project isn't well maintained at this point. Any help in that regard would be much appreciated. As it stands the best way to create a new CRUD module would be to copy the modules/articles folder from a project that was cloned from master.

Thank you, it worked :)

I tried install angular-sanitize but can not work. Then i upgrade angular to 1.6.4 and when reload page, it render to blank page with error. How to install angular-sanitize to MEANJS ?


Voice detection detecting wrong phrases

Hi,
I got a problem with the voice detection. I'm using a USB sound adapter (Daffodil US01) with a normal headset. When I record something with "arecord -r 48000 -d 600 -f S16_LE test.wav" and then play it again with aplay test.wav, the recorded sound is perfectly fine & clear without any background noises.
When I run "python main.py", it also seems to get triggered when I say "Jasper", however the recognition always tells me that I'm saying "BUT", "BUT OF", "WHAT" and things like that and I never ever hear the beep... I tried it a hundred times now. Is there something wrong in my setup ?
Output:
===================
JASPER: OF OF
===================
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
INFO: cmn.c(175): CMN: 27.03 -0.24  0.11 -0.21 -0.21 -1.67  0.22 -0.29 -0.40 -0.16  0.48 -0.41  0.35
INFO: ngram_search_fwdtree.c(1549):     1359 words recognized (13/fr)
INFO: ngram_search_fwdtree.c(1551):    33927 senones evaluated (333/fr)
INFO: ngram_search_fwdtree.c(1553):    20976 channels searched (205/fr), 1764 1st, 17447 last
INFO: ngram_search_fwdtree.c(1557):     1752 words for which last channels evaluated (17/fr)
INFO: ngram_search_fwdtree.c(1560):     1581 candidate words for entering last phone (15/fr)
INFO: ngram_search_fwdtree.c(1562): fwdtree 0.20 CPU 0.196 xRT
INFO: ngram_search_fwdtree.c(1565): fwdtree 0.21 wall 0.204 xRT
INFO: ngram_search_fwdflat.c(302): Utterance vocabulary contains 19 words
INFO: ngram_search_fwdflat.c(937):      649 words recognized (6/fr)
INFO: ngram_search_fwdflat.c(939):    35160 senones evaluated (345/fr)
INFO: ngram_search_fwdflat.c(941):    31614 channels searched (309/fr)
INFO: ngram_search_fwdflat.c(943):     1567 words searched (15/fr)
INFO: ngram_search_fwdflat.c(945):     1001 word transitions (9/fr)
INFO: ngram_search_fwdflat.c(948): fwdflat 0.15 CPU 0.147 xRT
INFO: ngram_search_fwdflat.c(951): fwdflat 0.15 wall 0.150 xRT
INFO: ngram_search.c(1266): lattice start node <s>.0 end node </s>.87
INFO: ngram_search.c(1294): Eliminated 0 nodes before end node
INFO: ngram_search.c(1399): Lattice has 55 nodes, 124 links
INFO: ps_lattice.c(1365): Normalizer P(O) = alpha(</s>:87:100) = -739532
INFO: ps_lattice.c(1403): Joint P(O,S) = -752904 P(S|O) = -13372
INFO: ngram_search.c(888): bestpath 0.01 CPU 0.010 xRT
INFO: ngram_search.c(891): bestpath 0.01 wall 0.014 xRT
===================
JASPER: IS OF
===================

Is there anyone who has got a good voice recognition with Jasper? If not, why not close the issue? I also got the bad recognition result. If this issue has not been solved, why not put it on the top.


AzurePowerShellV4 does not prefer pwsh over powershell (despite code comment saying so) and there is no configuration option

Required Information
Type: Bug
Enter Task Name: AzurePowerShellV4
Environment
Azure Pipelines

Agent - Hosted or Private:

If using Hosted agent, provide agent queue name: windows-2019

Issue Description
When being run on an image that has PowerShell Core (pwsh) installed and on the path, the AzurePowerShellV4 task does not use it but uses Windows PowerShell (powershell).
The comment in the code says, that pwsh should be preferred
https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/AzurePowerShellV4/azurepowershell.ts#L91
However, when being run on the  windows-2019 image, it uses Windows PowerShell despite PowerShell Core being installed. It should either do what the comment states or similar to the PowerShellV2, there should be an optional parameter for it.
One can easily verify this by running where.exe pwsh first in the task to verify that pwsh is on the PATH and then $PSVersionTable will return a version number of 5.1.x, which is the version number of Windows PowerShell

@bergmeister
For now, the task AzurePowerShellV4 does not support powershell core in Windows. This support is recently added in this week. It will take at least 3-4 weeks to get deployed.

Thanks for the feedback. Sorry, I was not aware that this change was very recent and has not been deployed yet. :-)


Add support for managing labels

/draft
/triage
/assign
/label enhancement

/retitle Add support for managing labels

/restart-workflow

/restart-workflow


[AIRFLOW-3501] k8s executor - Support loading dags from image.

Jira

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

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

Description

[X] Here are some details about my PR, including screenshots of any UI changes:

This PR adds a new config property named use_container_dags to the kubernetes configuration section.
When this property is set to True, airflow will uses the dags packaged into the running docker container instead of loading them from a kubernetes volume mount or from a git init container.
Prior to this change airflow forced loading dags either from a volume claim or an init container.
The motivation for this change is to allow for an airflow image to be built and released via a CI/CD pipeline upon a new commit to a dag repository.  For example, given a new git commit to a dag repo, a CI/CD server can build an airflow docker image, run tests against the current dags, and finally push the entire bundle as a single, complete, well-known unit to kubernetes.
There's no need to worry that a git init container will fail, having to have a separate pipeline to update dags on a shared volume, etc.  And if issues arise from an update, the configuration can be easily rolled back to the prior version of the image.
Tests

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

Commits

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

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

Documentation

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

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

Code Quality

[X] Passes flake8

I believe this is already covered by [AIRFLOW-2770] kubernetes: add support for dag folder in the docker image?

Yup, this is a dupe of 2270.  I'll close this out and make a separate PR to include the tests from this PR.


Website down

@Efraa , the documentation website seems to be down since yesterday.

Moved to https://efrolic.github.io/css/

Thanks @Efraa !


release 1.0.3, fix a bug with the login and logout methods

@obdulia-losantos i will merge this in order to speed things up, but feel free to raise an hand in case there is something you don't like


Working through delete comment code

Doesn't correctly delete from server but does temporarily delete from page (until refresh)

The last 2 commits were merged from Map pull request - already approved.


WARNING: lavapipe is not a conformant vulkan implementation, testing use only.

I am getting this warning message everytime I turn on my discord.js bot. Any ideas?

I think you are in wrong place. This module should not cause a problem as big as that.

I think you are in wrong place. This module should not cause a problem as big as that.

But I think this warning message is there after I added this module.
If not, do you have any idea or solution?

It may came because of it's dependency on skia-canvas. Which OS you are using?

I will try something today and then I will text here.

I have tried to reinstall skia-canvas and it still gives me this warning message. How much is this important warning?

If you are using this for a personal use and a really small project then you can pretty much ignore it but if you are using it for some big projects I recommend you to consult your VPS provider regarding the upper limits and other details.

I tried to ask VPS support and nothing important.  Can you check my code please? @Shashank3736
`const { EmbedBuilder, AttachmentBuilder } = require("discord.js");
const verifyDB = require("../../Schemas/Verification");
const { Captcha } = require("captcha-canvas");
module.exports = {
name: 'guildMemberAdd',
once: false,
async execute(member, client) {
    const guildId = member.guild.id;

    const captcha = new Captcha(); //create a captcha canvas of 100x300.
    captcha.async = false
    captcha.addDecoy();
    captcha.drawTrace();
    captcha.drawCaptcha();

    let verifyData = await verifyDB.findOne({ Guild: guildId })

    if (!verifyData) { return; }
            let roleDB = verifyData.RoleID

    const captchaPicture = new AttachmentBuilder(await captcha.png, { name: 'captcha.png' });

    const verifyEmbed = new EmbedBuilder()
        .setTitle(`${member.guild.name} verification!`)
        .setDescription(`Reply with a message containing the correct characters (connected by a line) from the captcha image`)
        .setColor("Random")
        .setThumbnail(member.user.displayAvatarURL())
        .setFooter({ iconURL: client.user.displayAvatarURL(), text: client.user.tag })
        .setImage(`attachment://${captchaPicture.name}`)

    let msg;
    try {
        msg = await member.send({ embeds: [verifyEmbed], files: [captchaPicture] });
    } catch (err) { return console.log("Message failure: " + err) }

    const filter = (message) => {
        if (message.author.id !== member.id) return false;
        if (message.content === captcha.text) return true;
        else { member.send("Wrong!"); return false; }
    }

    try {
        let response = await msg.channel.awaitMessages({ filter, max: 1, time: 300000, errors: ['time'] });
        if (response) {
            let role = member.guild.roles.cache.find(role => role.id == roleDB);
            member.roles.add(role)
            return member.send({
                embeds: [new EmbedBuilder().setFooter({ iconURL: client.user.displayAvatarURL(), text: client.user.tag })
                    .setColor("Green")
                    .setTitle("You have been verified! ✅")
                    .setDescription(`Access to ${member.guild.name} has been granted. Enjoy 😄`)]
            })
        }

    } catch (e) { console.log("Verify" + e) }

}

}`
Thank you in advance for trying to help


egscomics.com – support HTTPS

Some pages that now work:

https://egscomics.com/comic/party-022
https://www.egscomics.com/comic/party-022

Some pages that already worked, for regression testing:

http://egscomics.com/comic/party-022
http://www.egscomics.com/comic/party-022

My changes to the code for EGS consist of the above support for the HTTPS pages plus the following minor changes:

Replaced @include with the safer, easier-to-use @match
Used tabs for indentation, for consistency with the majority of the file
Fixed grammar in a comment

For commit searching: the comic is named El Goonish Shive.

Many thanks!


Sidenav: remove sidenav button

This change removes the PharosSidenavButton and automatic sliding behavior of the sidenav. Before, the PharosSidenavButton and the PharosSidenav controlled its visibility automatically, making it difficult for consumers to control its state.
Now, users can control...

the visibility of the sidenav via the open property
the visibility of the close button via the hasCloseButton property
assign the data-sidenav-id attribute on trigger elements to open the sidenav when clicked

This change: (check at least one)

[x] Adds a new feature
[ ] Fixes a bug
[x] Improves maintainability
[x] Improves documentation
[ ] Is a release activity

Is this a breaking change? (check one)

[x] Yes
[ ] No

Is the: (complete all)

[x] Title of this pull request clear, concise, and indicative of the issue number it addresses, if any?
[ ] Test suite(s) passing?
[ ] Code coverage maximal?
[x] Changeset added?
[ ] Component status page up to date?

What does this change address?
Resolves #417
How does this change work?
Removes PharosSidenavButton and it's references. Previously the button was being used to maintain the state of the SideNav. This change moves that responsibility to the consumer where it can pass slide = [true/false] in order to control the visibility of the PharosSideNav.

🤔  not sure pharos-site is failing to build...
it's as if it's trying to build with pharos version 13 event though it's package.json lists 12.6.0

I think this one's good to go


[RFR] Fix ability to disable sort for a field

[x] Allow to disable sorting without having to specify a label
[x] Document the sortable option

Fix for #579


Adding simple temporary file and folder creation support

Added ability to create a uniquely named temporary file or subfolder to a folder.
Uses globallyUniqueString as per NSHipster for temporary generation
https://nshipster.com/temporary-files/
createTemporaryFile

Creates a temporary file within a folder with an optional prefix and extension
Filename is of the format [prefix_]random_guid[.extension]

createTemporarySubfolder

Creates a temporary subfolder within a folder with an optional prefix
Filename is of the format [prefix_]random_guid

Okey.

https://gist.github.com/dagronf/267514677f6a8849c4be90dd006f95c0


use alan compiler in repo to build anycloud cli

Do we want to edit .version.sh in this PR to make sure anycloud's version number is synced with Alan?

Do we want to edit .version.sh in this PR to make sure anycloud's version number is synced with Alan?

ah yes!


Leaderboard: Add ONNX and GGUF to frameworks to allow us to filter based on these

See #1579
I believe a way to do this automatically would be to consider Frameworks as a combined set from mteb and those derived from huggingface (we can create a whitelist of tags to look for)
e.g. Me5-large-instruct would have [sentence-transformers, Transformers, ONNX, safetensors].
We could potentially rename frameworks to "tags" or split it up into "frameworks" and "formats".
I am unsure if this is valid to fetch during the setup (if we run it once a day I believe it would be) - @x-tabdeveloping WDYT?

Great idea! We should inplement it after Christmas!


VsChromium lists too many processes as being the browser process

I am using Visual Studio 2015 to debug chromium, via attaching to chromium processors. I launched chromium (with only 1 tab), and then in VS2015, I clicked "Debug" in the toolbar on top, then clicked "Attach to chrome", then clicked "choose". The figure below is what I got. Basically, it recognizes more than one processor as browser processors. The reason of this is possibly VsChromium cannot tell what the other two "browser processors" are. But I am not sure.

In task manager of chromium browser, it seems that those processors are better recognized. The "Utility: V8 Proxy Resolver" processor was recognized as "browser processor" in VsChromium.

Fixed in a21a076e30960c79e77a5d424bad19d9f44c5f4a

(Oops, wrong bug)

I just checked this again and I see four processes listed as being the browser process. The other three are the crashpad-handler, utility, and watcher processes. I identified these by using procexp to get their command lines. They can also be identified by having a chrome process as their parent - only the browser process has a non chrome.exe parent.
One other identifying characteristic is that the browser process appears to be the only one with a window title.


Report feedback

Implemented @valmai 's feedback on the report

Adding some architecture stuff first

Looks good!

Nothing to comment, looks good.


Passing a styles prop to Presets.classic.Node results in "Invalid value for prop" error

As the title says, passing a styles prop to Presets.classic.Node results in the following warning:
styled-components: it looks like an unknown prop "styles" is being sent through to the DOM, which will likely trigger a React console error. If you would like automatic filtering of unknown props, you can opt-into that behavior via `<StyleSheetManager shouldForwardProp={...}>` (connect an API like `@emotion/is-prop-valid`) or consider using transient props (`$` prefix for automatic filtering.)

and the following error (which for some amusing reason chooses to call itself a "Warning":
Warning: Invalid value for prop `styles` on <div> tag. Either remove it from the element, or pass a string or number value to keep it in the DOM. For details, see https://reactjs.org/link/attribute-behavior

Example code which causes this:
const myStyle = css`
    background: red;
`;

export function StyledNode(props: {
    data: Schemes['Node'],
    emit: (props: ReactArea2D<Schemes>) => void;
}) {
    return <Presets.classic.Node styles={() => myStyle} {...props} />;
}

From what I've seen, the solution would be to use styled-components' transient props, by simply prefixing styles with $ in Node. I assume all the components under src/presets/classic/components that use the styles prop also suffer from this.

usually, a styled component can be styled like so
const  StyledNode  = styled(Presets.classic.Node)  background: red;
another solution is to just copy the file https://github.com/retejs/react-plugin/blob/ff40f62c065c84e66b47c4ed70424d19efd1f685/src/presets/classic/components/Node.tsx


Player unable to sell items adjusted via ragfair.config/itemPriceMultiplier

Ragfair not using itemPriceMultiplier from Ragfair.json to calculate sell chances.
currently its calculating sell chance based of handbook prices if item is missing from Prices.json.
Needs to be changed to handbook price * itemPriceMultiplier (if it has one)

Originally written by Kaeno

Fixed with: https://dev.sp-tarkov.com/SPT-AKI/Server/commit/872c6282ecda6ee3bb78eab31b5cf21ca1fd33c8

Originally written by chomp

Successfuly sold T-7 Thermals for proper price of handbook * itemPriceMultiplier
Also just verified by selling a 120 & 30 pcs box of 5.45x39MM BP for appropriate flea prices
(which I'm pretty sure are the only other 2 items using this multiplier?)
Fixed!

Originally written by acidphantasm


vscode-extensions: detect vsix sources and generate packages automatically

Looking at PR #348, I notice that we can improve how vscode-extensions handles generated vsix source in pkgs/sources.toml.
This PR aims to mkVscodeExtension with auto-generated meta attributes and passthru values such as meta.homepage, meta.downloadPage, meta.changelog, meta.license, meta.maintainers, meta.platforms, {drv}Phase, etc.
Therefore, the following code snippet can be simplified into:
[vscode-LiveServer]
src.openvsx = "ritwickdey.LiveServer"
fetch.openvsx = "ritwickdey.LiveServer"
passthru = { license = "mit", homepage = "https://github.com/ritwickdey/vscode-live-server", description = "Launch a development local Server with live reload feature for static & dynamic pages" }

The passthru can be generated through bud script, although I will need to test more of this later.

IMO, also bud complements can exquisitely live in a divnix/vsext.

Superseeded by https://github.com/divnix/devos-ext-lib


Threadsafe Handles

Two new Send + Sync features are introduced: EventQueue and Persistent. These features work together to allow multi-threaded modules to interact with the Javascript main thread.

EventQueue: Threadsafe handle that allows sending closures to be executed on the main thread.
Persistent<T>: Opaque handle that can be sent across threads, but only dereferenced on the main thread.

Finished my review! This is going to be a great addition to the core primitives of Neon. I'm psyched.

@dherman This is close to stabilization. One change I would like to make prior to merging is the addition of a return value. Two APIs to take inspiration from:

std::thread::spawn
tokio::spawn

In both of these APIs, a JoinHandle is returned. On a thread::spawn, a user can call join to block until the thread exits and get the return value. Similarly, in tokio, the handle can be awaited to get the resolved value.
I propose the following changes:
struct Channel
    pub fn send<T, F>(&self, f: F) -> JoinHandle<T>
    where
        T: Send + 'static,
        F: FnOnce(TaskContext) -> NeonResult<T>;

We don't need to initially do anything with the returned JoinHandle, but by adding it there, it allows extension without breaking changes to introduce JoinHandle::join and impl Future for JoinHandle.
Also, I'm still not feeling certain send is the right choice. Maybe it should be renamed spawn? If it is renamed spawn, Channel probably isn't the best name either.

This is a great idea @kjvalencik.
I think I do like send better than spawn, though, because we aren't spawning a thread (not even conceptually like a green thread), the user should be thinking of it as sending information back to an existing thread. As far as mixing traditions (channel / join) I think I'm comfortable with it: conceptually we're dealing with a channel because we're communicating between threads, and conceptually we're dealing with joining because we're blocking on another thread's computation.

Merged in https://github.com/neon-bindings/rfcs/commit/c6396817a56f323ae1d452d373c22513f6d7425b


Use sys.exc_info when catching all exceptions

In GitLab by @arisilon on Nov 7, 2019, 19:45
This is better than
except Exception as err:
followed by
except:

In GitLab by @arisilon on Nov 10, 2019, 21:38
removed milestone

In GitLab by @arisilon on Nov 10, 2019, 21:39
There were no instances of attempts to catch all exceptions.

In GitLab by @arisilon on Nov 10, 2019, 21:39
closed


Requirements to create NSG for corpnetsaw

Good day, I had the opportunity to engage MS support. I was asked to create the rule to allow RDP for corpnetsaw. I discovered that there is no option in the azure portal (GUI) to create the rule - Corpsaw does not appear in the list of service tags. It has to be created from command line. They provided me the following power shell. Which was the only way to specify the source address
Get-AzureRmNetworkSecurityGroup -Name "nsg-name" -ResourceGroupName "resource-group-name" | Add-AzureRmNetworkSecurityRuleConfig -Name "new-rule-name" -Access "Allow" -Protocol "TCP" -Direction "Inbound" -Priority "priority-number" -SourceAddressPrefix "CorpNetSaw" -SourcePortRange "" -DestinationPortRange "3389" -DestinationAddressPrefix "" | Set-AzureRmNetworkSecurityGroup
I think it would be a good note that it can't currently be created in the portal and it has to be done via command line.

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

ID: 7013d117-4c2e-1b3e-0b67-d3eec67dc490
Version Independent ID: c948be62-abef-57bb-232c-970ccfec504c
Content: Network planning and connections for Azure AD Domain Services
Content Source: articles/active-directory-domain-services/network-considerations.md
Service: active-directory
Sub-service: domain-services
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@mstb5150
Thanks for your feedback! We will investigate and update as appropriate.

Thanks @mstb5150 !
There is already a note about needing to use the command line for this, but I made a pull request to add an example. https://github.com/MicrosoftDocs/azure-docs-pr/pull/124660


Identify images from different receipts

Hi Team
I would like to know if there is a way to know if images sent to blink receipt sdk belongs to different receipts. So that we can notify user that they have shared receipts of a different shop.
We are using following method
public void recognize(@NonNull ScanOptions var1, @NonNull RecognizerCallback var2, @NonNull Bitmap... var3) {
       this.recognize(var1, var2, (CameraOrientation)null, var3);
   }

What happen now is that user is adding receipts of multiple stores and in the result we are getting a mix result of both the stores and that is not useful

@ErManishPatiyal  Yes But you need to handle that on your app end itself. The SDK returns the object that contains retailer's name and information

What if two images are of 2 different retails, which retail store will be picks, first receipts or second receipt. Is there any flag in the return data you can add to inform about multiple receipts

See @ErManishPatiyal comments :)


New Release?

Why are you releasing new versions with all of these PR's merged?

Sorry, don't totally understand your question. Can you please clarify?

There's lots of code on the HEAD of master that aren't published on NPM with a new version number.


Discrepancy between DMS level values and reported averages

Hello,
I have two question regarding the performances in the proteingym:

I opened https://github.com/OATML-Markslab/ProteinGym/blob/main/Detailed_performance_files/Substitutions/Spearman/all_models_substitutions_Spearman_DMS_level.csv. Then, I calculated average Spearman values for TranceptEVE_L and EVE_ensemble values using both pandas and a spreadsheet program. The average values I obtain do not agree with the values reported in Summary_performance_all_models_substitutions_Spearman.csv. I was wondering if you ignore some DMS experiments from the average when you report the values in the summary file.
I was wondering if all data points reported in the experiments (including multiple point measurements such as D170G:R187H in YAP1_HUMAN_Araya_2012.csv experiment) are calculated by the computational methods. I know that it may be difficult to answer that question for the other method reported in the ProteinGym but I am hoping that you have the answer for the methods developed in your lab (all tranception, tranceptEVE or EVE variants).
Thanks in advance,
Mustafa

Dear Mustafa,
Apologies for the delayed response. To answer your two questions:

As reported in the Tranception paper (Appendix E.1, last sentence) the computation approach at the time you asked the question was based on a 2-step process: 1) we were first aggregating all performance metrics at the Uniprot ID level and 2) we were then averaging the corresponding performance metrics across Uniprot IDs to obtain the final aggregate performance values reported everywhere. This was meant to remove potential biases stemming from having several assays for the same protein family. The exact logic for how things were computed back then is still available in the Tranception repo here (the former version of the ProteinGym codebase, now deprecated, was matching this code exactly).
Please note that in the new version we just released last week, we now also normalize by function grouping ("coarse_selection_type" in the updated reference files) when computing overall averages, to remove potential biases that would result from imbalances in the number of assays across function groupings. The exact computation approach is provided in the updated codebase here, and we recommend using this script to replicate all reported numbers in our paper / website.

All the data points corresponding to DMS scores that are provided in assay files (for instance here) are all directly based on experimental values measured in the corresponding assays, for both singles and multiples -- these are not computed by us. The predictions scores for the various baselines (for example here) are based on the official repo for each model. Generative models of full sequences, such as EVE or Tranception, handle multiple mutants directly. Pseudo-generative models, such as all ESM baselines, do not handle multiple mutants out-of-the-box and we resort to using the heuristics recommended by the authors to handle these (see Meier et al. for the ESM suite -- scores for multiple mutants are obtained by summing the scores for the corresponding individual single mutants).

Please let me know if that addresses your questions.
Kind regards,
Pascal

Dear Mustafa,
I'm closing this issue as I believe the above addressed it. Please feel free to re-open if you have any further questions on this.
Best,
Pascal

Hello Pascal,
Thanks a lot for the answers.
Best wishes,
Mustafa


Move oc sync path

@jupierce @tbielawa getting ready for https://jira.coreos.com/browse/ART-554

/lgtm


Any plans to rewrite on ES6?

Yes, as the models especially will benefit a lot from using ES6 features. Other than that, I see no large benefit. With this, I'd like to link this issue: https://github.com/Ivshti/linvodb3/issues/21, as both would probably happen at the same time

I've decided to reimplement almost all things of the project with better decomposition, promises, ES6 and code linting. Check my work in https://github.com/c58/marsdb
Maybe it would be useful for you. It does not work yet, i will continue working on it at free time. I'm planning to finish in next two weeks.

This seems like it has the potential to become the more elegant and lean version of linvodb, please keep us posted in this thread!

Hey, checkout my progress :) https://github.com/c58/marsdb
Indexes is removed, but should be implemented soon, after some storage implementations (just in-memory now)

@c58 I am keeping an eye on it, and I like the direction it's going in, especially under the hood. I was thinking of ways to do indexes better. Currently linvodb creates indexes for every key individually, on demand, and on queries makes an intersection of results from separate indexes.
I like that approach very much, but intersections can become expensive. The other option is to put results in a bitmap and XOR / XAND according to the required logic, but that will get ugly quickly when exceeding a million records. If there are clearly defined goals though, as with linvodb - "embedded DB engine for desktop apps" - then it's OK. But I'm still concerned about a possible desktop use case where there are a lot of records.
The other option is using compound indexes, but that can also get ugly quickly with many queries and etc. Maybe the DB can make compound indexes only in certain conditions and re-use them for several different queries, but I'm reluctant of trying to make a DB engine "smart". It's not a sustainable approach.
Thinking to other DB engines, embedded or not, relational or not, I cannot think of a solution to this problem. Maybe Postgres / some MySQL storage engines have the answer within them, but unfortunately I do not have enough knowledge on the matter.
Any ideas?

I think we need to get some ideas from the original, likely it's open sourced (I mean MongoDB, ofc) :)
Also I found some mongo-like databases, like TingoDB, whose supports indexes, but I don't think it uses some better solution, then intersecting/XORing. (need to be checked)
And some words about millions of records. It is not my case but I agree that using indexes with some simple query keys, like {a: 'test'}, is awesome, especially if it would work with simple regexp patterns, like "^test", just like meteor does.
So, I'm planing to make an algorithm of matching consisting of three stages:

Preprocess query for extracting simple indexable cases (no arrays, only numeric bounds and texts with simple regexes). Ensure indexes on demand and get list of ids.
Get objects from storage by given ids
If preprocessed query is still contains some query keys, match retrieved documents with minimingo algorithm

It would be enough for me. Also it should be benchmarked and compared with another solutions for discussing about performance.

20 окт. 2015 г., в 2:51, Ivo Georgiev<EMAIL_ADDRESS>написал(а):
@c58 I am keeping an eye on it, and I like the direction it's going in, especially under the hood. I was thinking of ways to do indexes better. Currently linvodb creates indexes for every key individually, on demand, and on queries makes an intersection of results from separate indexes.
I like that approach very much, but intersections can become expensive. The other option is to put results in a bitmap and XOR / XAND according to the required logic, but that will get ugly quickly when exceeding a million records. If there are clearly defined goals though, as with linvodb - "embedded DB engine for desktop apps" - then it's OK. But I'm still concerned about a possible desktop use case where there are a lot of records.
The other option is using compound indexes, but that can also get ugly quickly with many queries and etc. Maybe the DB can make compound indexes only in certain conditions and re-use them for several different queries, but I'm reluctant of trying to make a DB engine "smart". It's not a sustainable approach.
Thinking to other DB engines, embedded or not, relational or not, I cannot think of a solution to this problem. Maybe Postgres / some MySQL storage engines have the answer within them, but unfortunately I do not have enough knowledge on the matter.
Any ideas?
—
Reply to this email directly or view it on GitHub.

That's exactly the issue, the original doesn't solve the problem at all. It relies on you to make your own indexes, which is totally ok, but then it picks which indexes to use in a totally mindless way - if you have a lot of indexes. Which leads to having to use .hint(), which kind of removes the whole advantage of it's promised ease of use. You can optimize queries greatly with .hint(), but if you have a more dynamic query (e.g. not always on the same properties), then you have to be smart about hints.
MongoDB is also built to do one index lookup for a query. I'm not entirely sure if today it still follows that, but I'm sure it does a lot of scanning if you haven't optimized the queries.
That's why linvodb is entirely scan-less, except of course the first time when indexes are built.
Maybe some manual intervention should be allowed, but instead of building indexes prematurely, just give them as .hint()'s and then the DB first lookups this index, no matter if compound or not, and then applies XOR/XAND with the other matches for other properties if there are any.


Feedback on GH forks

In an organisation structure with private repositories, I face the following problem:
When an employee (lets say, Stefanius) forks a private repo and after developing I pushed my changes (PR) to the organisation-repo, the build on PHPCI will start.
But, after  that in my pull request the status is still 'yellow' (busy) for ever and it will not go red or green. So the only way to see of a build is correct, is to log on the PHPCI server.
Is this a bug or see I something over the head?

I think you talk about that, you need to run daemon for that, or cronjob:
https://github.com/Block8/PHPCI/wiki/Run-Builds-Using-a-Daemon

I'm assuming this is now working. Please feel free to reopen if this is not the case.