[engSys] Client Libraries - package modernization

A mega-issue that tracks the ESM, vitest, and test-recorder migration for all track 2 high-level client libraries
Latest status:
Generated on: 10/8/2024
Migration report
Category: client

Total projects: 120
Total CJS: 95
Total ESM: 25
Total Mocha: 95
Total Vitest: 24
Converted to ESM percentage: 20.83%
Converted to vitest percentage: 20.00%

Package Name
Project Folder
Type
Migrated to ESM

@azure-rest/agrifood-farming
sdk/agrifood/agrifood-farming-rest
client
❌

@azure-rest/ai-anomaly-detector
sdk/anomalydetector/ai-anomaly-detector-rest
client
❌

@azure-rest/ai-content-safety
sdk/contentsafety/ai-content-safety-rest
client
❌

@azure-rest/ai-document-intelligence
sdk/documentintelligence/ai-document-intelligence-rest
client
✅

@azure-rest/ai-document-translator
sdk/documenttranslator/ai-document-translator-rest
client
❌

@azure-rest/ai-inference
sdk/ai/ai-inference-rest
client
✅

@azure-rest/ai-translation-document
sdk/translation/ai-translation-document-rest
client
❌

@azure-rest/ai-translation-text
sdk/translation/ai-translation-text-rest
client
❌

@azure-rest/ai-vision-face
sdk/face/ai-vision-face-rest
client
✅

@azure-rest/ai-vision-image-analysis
sdk/vision/ai-vision-image-analysis-rest
client
❌

@azure-rest/arm-appservice
sdk/appservice/arm-appservice-rest
client
❌

@azure-rest/arm-compute
sdk/compute/arm-compute-rest
client
❌

@azure-rest/arm-containerservice
sdk/containerservice/arm-containerservice-rest
client
❌

@azure-rest/arm-network
sdk/network/arm-network-rest
client
❌

@azure-rest/arm-servicefabric
sdk/servicefabric/arm-servicefabric-rest
client
❌

@azure-rest/batch
sdk/batch/batch-rest
client
✅

@azure-rest/communication-job-router
sdk/communication/communication-job-router-rest
client
❌

@azure-rest/communication-messages
sdk/communication/communication-messages-rest
client
❌

@azure-rest/confidential-ledger
sdk/confidentialledger/confidential-ledger-rest
client
❌

@azure-rest/defender-easm
sdk/easm/defender-easm-rest
client
❌

@azure-rest/developer-devcenter
sdk/devcenter/developer-devcenter-rest
client
✅

@azure-rest/health-deidentification
sdk/healthdataaiservices/azure-health-deidentification
client
✅

@azure-rest/health-insights-cancerprofiling
sdk/healthinsights/health-insights-cancerprofiling-rest
client
❌

@azure-rest/health-insights-clinicalmatching
sdk/healthinsights/health-insights-clinicalmatching-rest
client
❌

@azure-rest/health-insights-radiologyinsights
sdk/healthinsights/health-insights-radiologyinsights-rest
client
❌

@azure-rest/iot-device-update
sdk/deviceupdate/iot-device-update-rest
client
❌

@azure-rest/load-testing
sdk/loadtesting/load-testing-rest
client
❌

@azure-rest/maps-geolocation
sdk/maps/maps-geolocation-rest
client
❌

@azure-rest/maps-render
sdk/maps/maps-render-rest
client
❌

@azure-rest/maps-route
sdk/maps/maps-route-rest
client
❌

@azure-rest/maps-search
sdk/maps/maps-search-rest
client
❌

@azure-rest/purview-administration
sdk/purview/purview-administration-rest
client
❌

@azure-rest/purview-catalog
sdk/purview/purview-catalog-rest
client
❌

@azure-rest/purview-datamap
sdk/purview/purview-datamap-rest
client
❌

@azure-rest/purview-scanning
sdk/purview/purview-scanning-rest
client
❌

@azure-rest/purview-sharing
sdk/purview/purview-sharing-rest
client
❌

@azure-rest/purview-workflow
sdk/purview/purview-workflow-rest
client
❌

@azure-rest/synapse-access-control
sdk/synapse/synapse-access-control-rest
client
❌

@azure-tools/communication-alpha-ids
sdk/communication/communication-alpha-ids
client
❌

@azure-tools/communication-recipient-verification
sdk/communication/communication-recipient-verification
client
❌

@azure-tools/communication-short-codes
sdk/communication/communication-short-codes
client
❌

@azure-tools/communication-tiering
sdk/communication/communication-tiering
client
❌

@azure-tools/communication-toll-free-verification
sdk/communication/communication-toll-free-verification
client
❌

@azure/ai-form-recognizer
sdk/formrecognizer/ai-form-recognizer
client
❌

@azure/ai-language-conversations
sdk/cognitivelanguage/ai-language-conversations
client
❌

@azure/ai-language-text
sdk/cognitivelanguage/ai-language-text
client
❌

@azure/ai-language-textauthoring
sdk/cognitivelanguage/ai-language-textauthoring
client
❌

@azure/ai-metrics-advisor
sdk/metricsadvisor/ai-metrics-advisor
client
❌

@azure/ai-text-analytics
sdk/textanalytics/ai-text-analytics
client
❌

@azure/api-management-custom-widgets-scaffolder
sdk/apimanagement/api-management-custom-widgets-scaffolder
client
✅

@azure/api-management-custom-widgets-tools
sdk/apimanagement/api-management-custom-widgets-tools
client
✅

@azure/app-configuration
sdk/appconfiguration/app-configuration
client
❌

@azure/arm-computefleet
sdk/computefleet/arm-computefleet
client
✅

@azure/arm-healthdataaiservices
sdk/healthdataaiservices/arm-healthdataaiservices
client
✅

@azure/arm-informaticadatamanagement
sdk/informatica/arm-informaticadatamanagement
client
❌

@azure/attestation
sdk/attestation/attestation
client
❌

@azure/communication-call-automation
sdk/communication/communication-call-automation
client
❌

@azure/communication-chat
sdk/communication/communication-chat
client
❌

@azure/communication-common
sdk/communication/communication-common
client
❌

@azure/communication-email
sdk/communication/communication-email
client
❌

@azure/communication-identity
sdk/communication/communication-identity
client
❌

@azure/communication-job-router
sdk/communication/communication-job-router
client
❌

@azure/communication-phone-numbers
sdk/communication/communication-phone-numbers
client
❌

@azure/communication-rooms
sdk/communication/communication-rooms
client
❌

@azure/communication-sms
sdk/communication/communication-sms
client
❌

@azure/container-registry
sdk/containerregistry/container-registry
client
❌

@azure/cosmos
sdk/cosmosdb/cosmos
client
❌

@azure/create-microsoft-playwright-testing
sdk/playwrighttesting/create-microsoft-playwright-testing
client
✅

@azure/data-tables
sdk/tables/data-tables
client
❌

@azure/digital-twins-core
sdk/digitaltwins/digital-twins-core
client
❌

@azure/event-hubs
sdk/eventhub/event-hubs
client
✅

@azure/eventgrid
sdk/eventgrid/eventgrid
client
❌

@azure/eventgrid-namespaces
sdk/eventgrid/eventgrid-namespaces
client
❌

@azure/eventgrid-system-events
sdk/eventgrid/eventgrid-system-events
client
❌

@azure/eventhubs-checkpointstore-blob
sdk/eventhub/eventhubs-checkpointstore-blob
client
✅

@azure/eventhubs-checkpointstore-table
sdk/eventhub/eventhubs-checkpointstore-table
client
✅

@azure/functions-authentication-events
sdk/entra/functions-authentication-events
client
❌

@azure/identity
sdk/identity/identity
client
❌

@azure/identity-broker
sdk/identity/identity-broker
client
❌

@azure/identity-cache-persistence
sdk/identity/identity-cache-persistence
client
❌

@azure/identity-vscode
sdk/identity/identity-vscode
client
❌

@azure/iot-modelsrepository
sdk/iot/iot-modelsrepository
client
❌

@azure/keyvault-admin
sdk/keyvault/keyvault-admin
client
✅

@azure/keyvault-certificates
sdk/keyvault/keyvault-certificates
client
✅

@azure/keyvault-common
sdk/keyvault/keyvault-common
client
✅

@azure/keyvault-keys
sdk/keyvault/keyvault-keys
client
❌

@azure/keyvault-secrets
sdk/keyvault/keyvault-secrets
client
✅

@azure/maps-common
sdk/maps/maps-common
client
❌

@azure/microsoft-playwright-testing
sdk/playwrighttesting/microsoft-playwright-testing
client
❌

@azure/mixed-reality-authentication
sdk/mixedreality/mixed-reality-authentication
client
❌

@azure/mixed-reality-remote-rendering
sdk/remoterendering/mixed-reality-remote-rendering
client
❌

@azure/monitor-ingestion
sdk/monitor/monitor-ingestion
client
❌

@azure/monitor-opentelemetry
sdk/monitor/monitor-opentelemetry
client
❌

@azure/monitor-opentelemetry-exporter
sdk/monitor/monitor-opentelemetry-exporter
client
❌

@azure/monitor-query
sdk/monitor/monitor-query
client
❌

@azure/notification-hubs
sdk/notificationhubs/notification-hubs
client
✅

@azure/openai
sdk/openai/openai
client
✅

@azure/opentelemetry-instrumentation-azure-sdk
sdk/instrumentation/opentelemetry-instrumentation-azure-sdk
client
✅

@azure/quantum-jobs
sdk/quantum/quantum-jobs
client
❌

@azure/schema-registry
sdk/schemaregistry/schema-registry
client
❌

@azure/schema-registry-avro
sdk/schemaregistry/schema-registry-avro
client
❌

@azure/schema-registry-json
sdk/schemaregistry/schema-registry-json
client
❌

@azure/search-documents
sdk/search/search-documents
client
❌

@azure/service-bus
sdk/servicebus/service-bus
client
❌

@azure/storage-blob
sdk/storage/storage-blob
client
❌

@azure/storage-blob-changefeed
sdk/storage/storage-blob-changefeed
client
❌

@azure/storage-file-datalake
sdk/storage/storage-file-datalake
client
❌

@azure/storage-file-share
sdk/storage/storage-file-share
client
❌

@azure/storage-queue
sdk/storage/storage-queue
client
❌

@azure/synapse-access-control
sdk/synapse/synapse-access-control
client
❌

@azure/synapse-artifacts
sdk/synapse/synapse-artifacts
client
❌

@azure/synapse-managed-private-endpoints
sdk/synapse/synapse-managed-private-endpoints
client
❌

@azure/synapse-monitoring
sdk/synapse/synapse-monitoring
client
❌

@azure/synapse-spark
sdk/synapse/synapse-spark
client
❌

@azure/template
sdk/template/template
client
✅

@azure/template-dpg
sdk/template/template-dpg
client
✅

@azure/web-pubsub
sdk/web-pubsub/web-pubsub
client
❌

@azure/web-pubsub-client
sdk/web-pubsub/web-pubsub-client
client
❌

@azure/web-pubsub-client-protobuf
sdk/web-pubsub/web-pubsub-client-protobuf
client
✅

@azure/web-pubsub-express
sdk/web-pubsub/web-pubsub-express
client
✅

Work to be done

[x] Support ESM in samples (#29672)
[ ] Work with codegen folks to ensure new generated HLCs / RLCs / modular clients generate modern code
[ ] Migrate all HLCs
[ ] Regenerate all ARM packages using the new codegen
[ ] Migrate all RLCs

Cleanup, non-blocking work

[ ] Delete test-utils
[ ] Remove all traces of mocha and karma
[ ] Deprecate test-recorder-v3

Hi, does this also includes modernizing the codebase like in @azure/identity which depends on events that's irrelevant with modern JS engines?
I've found these issue but I don't see any progress:
https://github.com/Azure/azure-sdk-for-js/issues/27470
https://github.com/Azure/azure-sdk-for-js/issues/27468
https://github.com/Azure/azure-sdk-for-js/issues/27467


Public the child package @ckb-lumos/parser to work with custom molecule structures without manual binding

We've received feedback from the communication that Lumos now is not convenient to work with custom molecule files since we need to write many pieces of binding.
So we need to public the child package @ckb-lumos/molecule and create some toolkit to make the  package working better with TypeScript

Background
Recently, I received feedback suggesting that we generate codecs directly from .mol files instead of writing bindings manually to avoid potential errors.
While the binding may be effective when there are not many changes to the Molecule schemas, the new protocol cobuild will rely heavily on Molecule. This means that custom Molecule schema files will be subject to frequent changes. Therefore, a tool to generate codecs from schema files is beneficial for such scenarios
Idea
Currently, Lumos has a module @ckb-lumos/molecule that provides a parser to parse molecule schema files to a CodecMap
type Parser = {
  parse(schema: string): Record<string, BytesCodec>
}

It works, but

additional runtimes, such as nearley and moo, are required
the Record<string, BytesCodec> doesn't work well with code suggestion

Therefore, the codegen way would be a better solution than parsing in runtime.
Usage
array Byte32 [byte; 32];
vector Bytes <byte>;

table Script {
    code_hash:      Byte32,
    hash_type:      byte,
    args:           Bytes,
}

An expected generated schema should be
// an array or vector of bytes is better to decode in one step
declare const Byte32: FixedBytesCodec<HexString, BytesLike>;
declare const Bytes: BytesCodec<HexString, BytesLike>;

// custom byte codec is better for decoding to a human-readable target
declare const HashType: FixedBytesCodec<'type' | 'data' | 'data1' | 'data2', BytesLike>;

// the object keys could unify into camelcase
declare const Script: ObjectLayout<{
  codeHash: typeof Byte32,
  hashType: typeof HashType,
  args: typeof Bytes
}>

Therefore, customization features are required, such as

override generated codec by customized ones
override object keys
override the codec of byte, array [byte; n], and vector <byte>

Codegen CLI
The CLI could be something like this
lumos-molecule-codegen schema.mol \
  --config molecule-codegen.json # optional

{
  "prepend": "import { HashType } from './customized'",
  "objectKeyConvension": "camelcase", // or "keep"
  "overrides": {
    "Script.hash_type": "HashType", # to override the Script.hash_type with the customized `HashType` codec
  }
}


Prioritizing IDs over Names

Docker should prioritize IDs over Names in order to mitigate CVE-2014-5278:
https://groups.google.com/forum/m/#!topic/docker-user/jyf9_mYcMI8
In #8087, prioritizing Names over IDs was proposed and rejected (rightfully so).
However, in #9311 that behavior was proposed again and merged.
We must:

Revert that behavior
Add a test with a comment linking to the CVE in order to make sure it doesn't happen again

This is the offender: https://github.com/docker/docker/blob/master/daemon/daemon.go#L128
	// GetByName will match only an exact name provided; we ignore errors
	containerByName, _ := daemon.GetByName(prefixOrName)
	containerId, indexError := daemon.idIndex.Get(prefixOrName)

	if containerByName != nil {
		// prefix is an exact match to a full container Name
		return containerByName, nil
	}

ping @docker/core-maintainers @acbodine @ewindisch @thaJeztah @diogomonica

Hi!
If you are reporting a new issue, PLEASE make sure that does not have any duplicates already open.
We would like to take this time to remind you of the information we need to debug the problem you are seeing. This is an automated response so if this ticket is not about a bug, do not fret.
If you fail to provide this information within 7 days, we will close this because we cannot debug your issue. We can reopen whenever the information is provided.
Thank you.
Please see:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues
Description of problem:

`docker version`:

`docker info`:

`uname -a`:

Environment details (AWS, VirtualBox, physical, etc.):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual Results:

Expected Results:

Additional info:

#ENEEDMOREINFO

@aluzzardi why not error out when it's ambiguous?

I believe IDs (as in, full exact IDs) are used mostly by machines. If someone names a container after my ID, the machine won't be able to handle the conflict resolution (as in, if you "shadow" my ID then the only way to interact with the container is by name).
This could possibly break swarm, compose, and pretty much anything that uses the API and is not a human being :)

Thanks, @aluzzardi. For reference, this came up in https://github.com/docker/swarm/pull/803.
I don't think an ambiguous match (i.e. both an ID and name match) should error out, because that would still be a vulnerability; creating a container with a name that matches an ID, would block access to that container.
IMO the flow should basically be;
if exactMatchOnID {
    return match
}

// Fuzzy matching - do whatever is nice / useful / easy to use

Added this to the 1.7 milestone so that the behavior of Swarm and Docker match and this is a regression

+1;  Exact matches to the ID should supersede all.
Note that #8069 preferred fuzzy id matching over names. As a result, we had complaints that a container named 'db' would conflict with a container id named 'db00000...' and could not be referred to by name. A test should also exist for this and considerations made, otherwise someone might follow up with another wrong fix.

The first comment in this issue generates confusion as it misses a key difference between #8087 and #9705 (which is the PR that closes #9311; 9311 is only an issue).
8087 was closed because it "broke" the CVE fix; it disregarded IDs over names.  9705 was a rework based on @ewindisch feedback that full IDs had to be preferred over names always, so that is the way the code operates today.  A test was added for this behavior which will break if it is ever changed.
The only change introduced is the allowance for short IDs of any length < 64 to be superseded by names because of the hiding issue.. a container named "db" will be unreachable if and when any docker daemon has a container (or image for certain commands) which starts with the prefix "db".
If the test is not sufficient to maintain this behavior we can review, but I remember reviewing it during the 9705 PR review and it was testing all cases at the time.

@estesp is completely right; as can be seen at these lines; https://github.com/docker/docker/blob/b2a43baf2e2cc68c83383a7524441f81bc4c4725/daemon/daemon.go#L125-L128
func (daemon *Daemon) Get(prefixOrName string) (*Container, error) {
	if containerByID := daemon.containers.Get(prefixOrName); containerByID != nil {
		// prefix is an exact match to a full container ID
		return containerByID, nil
	}

So looks like this is a non-issue after all.. (And NO idea why I didn't see this, I guess I didn't check the link to the actual code :blush:
I'm going to close this issue, because there isn't an issue here (as far as I can see).


Make chainlist page faster

PR-Codex overview
The focus of this PR is to implement a show more feature for search results in the Chainlist page.
Detailed summary

Added useShowMore custom hook to handle showing more items on scroll
Implemented show more functionality in SearchResults component
Added ListItem and UnorderedList components for better structure

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

📝 Changed routes:

/chainlist

(view full size)

Commit<PHONE_NUMBER>93d2e044c1de137af96bdaa14fa7cf (https://thirdweb-mgpzzvkca.thirdweb-preview.com).


Add clarification in docs of how to reference connections

This docs page mentions how a profiles.yml file is not required like in a typical dbt installation. The page mentions that the Airflow conn_id gets translated into a profiles.yml file under the hood. Love that, makes my life much easier!
I'm now trying to figure out how that conn_id or subsequently generated profiles.yml then get referenced in a dbt model. Do you just reference the conn_id string itself?:
with source as (

    select * from {{ ref('conn_id') }}

)

I'm more than happy to open up a PR to add this to the examples - just need some guidance first 😄

After doing some more reading, I think I've gotten myself closer but still need a bit of clarity.
So passing in a conn_id to a DbtTaskGroup or DbtDag means the tasks within are going to utilize that specified connection.
Can I then create a sources.yml that lists databases available within the connection created by conn_id?
For example:
If conn_id points to a snowflake account, would the following sources.yml be able to use that conn_id:
version: 2

sources:
  - name: pub
    database: raw
    schema: pub
    tables:
      - name: orders
      - name: customers

And then in my models can call
select
  ...

from {{ source('pub', 'orders') }}

I'm getting my environment set up so I will also test this out myself.

@patawan sorry for the lack of response to your question! So, for clarity are you trying to reference specific information about a connection parameter? For example, are you trying to reference the database, host, or user set on the Airflow connection in dbt?

@pohek321 yes at the time I thought I needed to reference the profiles.yml generated by cosmos somewhere in my dbt models. Didn't realize the DbtTaskGroup automagically passes the profile snowflake_profile  flag in the dbt run command. Admittedly I also didn't have a good grasp of how dbt actually functioned :sweat_smile:.
Got everything sorted out and feeling much better about it now. This precedence section also helped a ton. Thanks for getting back to me!


Moving Bug

The bug stops me from moving whenever there is a wall.
I have figured how to stop it but it's getting annoying.
I Expect the Issue to stop me from moving at a specific point and after that, I can't move anywhere else.
When the problem started I was using Google
Please fix this

Can you explain the bug in detail? Give us a repro.

When I put walls around my person and run my program it can move freely but after a few second it stops and I can move only pacing in a limited amount of space.

When I put walls around my person and run my program it can move freely but after a few second it stops and I can move only pacing in a limited amount of space.

No repro steps.


⚠ AGEG website (prod) has degraded performance

In c7889b0, AGEG website (prod) (https://www.ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 4374 ms

Resolved: AGEG website (prod) performance has improved in d8d9e96.


Dark edit recourse area in light color theme

Describe the bug
Dark edit recourse area in light color theme.
To Reproduce
Steps to reproduce the behavior:

Go to edit any recourse

Expected behavior
All elements of interface are equal.
Screenshots

Environment (please complete the following information):

Lens Version: 4.1.3 (in 4.1.0 - 4.1.2 same problem, in 4.0.8 work fine)
OS: Windows 10
Installation method: from installer

We had the terminal originally matching the theme but some found it unusable in light mode. We may add finer theme configuration in the future (theme extension perhaps).

Related to #1166


Symfony 3.0 compatibility

Hi,
Could you tag a release with this fix ?
Thanks !
De : Rafael Dohms<EMAIL_ADDRESS>Envoyé : samedi 2 avril 2016 12:22
À : rdohms/dms-twig-extension-bundle<EMAIL_ADDRESS>Cc : Simon DAIGRE<EMAIL_ADDRESS>Objet : Re: [rdohms/dms-twig-extension-bundle] Symfony 3.0 compatibility (#5)
Merged #5https://github.com/rdohms/dms-twig-extension-bundle/pull/5.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com/rdohms/dms-twig-extension-bundle/pull/5#event-612139520

@SDVI working on it

done! https://github.com/rdohms/dms-twig-extension-bundle/releases/tag/1.2.3


fix fix load cannot end when set exec_mem_limit

Proposed changes
When value of exec_mem_limit is too small(like 1 byte), the load cannot be completed.
int get_available_thread_slot_num() {
        int thread_slot_num = 0;
        thread_slot_num = (allowed_blocks_num() + _block_per_scanner - 1) / _block_per_scanner;
        thread_slot_num = std::min(thread_slot_num, _max_thread_num - _num_running_scanners);
        return thread_slot_num;
}

int32_t allowed_blocks_num() const {
        int32_t blocks_num = std::min(_free_blocks_capacity,
                                      int32_t((_max_bytes_in_queue + _estimated_block_bytes - 1) /
                                              _estimated_block_bytes));
        return blocks_num;
}

When exec_mem_limit = 1, _max_bytes_in_queue = 1/20 * num_parallel_instances = 0，and the value of get_available_thread_slot_num() is 0, which none thread will add block to queue and make sender in vtablet_sink endless loop.
Solving it by set minimum max_bytes_in_blocks_queue threshold to optimize get_available_thread_slot_num() logic.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall


Guest Agent automatic log collection

Can we update/rename this section to explain that this feature is also available on Linux (Since version 2.7, only Ubuntu so far) along with listing what files are collected analogous to what we already have here for Windows?
https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/agent-windows#windows-guest-agent-automatic-logs-collection

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

ID: ab75f449-661d-bd1e-3ebd-61e2384a911a
Version Independent ID: e7c93a31-6076-26b8-a53d-d36df01ec6bc
Content: Azure Virtual Machine Agent Overview - Azure Virtual Machines
Content Source: articles/virtual-machines/extensions/agent-windows.md
Service: virtual-machines
Sub-service: extensions
GitHub Login: @MsGabsta
Microsoft Alias: gabsta

@kegregoi, that would add an equivalent section to Linux VM Agent?
https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/agent-linux
We're assigning this to the document author for further review.

@kegregoi I am currently working on updating this information for WALA.

@kegregoi, I have updated the doc and it should be live in the next 24h.

@kobulloc-MSFT please close this issue.

@kegregoi We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Minor cleanup to rest api page

Focus was on changing the api link so that customers not logged in would see a notice of such rather than a page error. An admonition to this effect was added.
All links to the api were changed as otherwise they would need individual references.
Other minor clean done.
No related ticket, quick fix.
PR Template and Checklist
Please complete as much as possible to speed up the reviewing process.
Readiness and adding reviewers as appropriate is required.
All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.
Readiness

[x] Merge (pending reviews)
[ ] Merge after date or event
[ ] Draft

Overview
Follows up to discussion of issue.
Checklist

[x] Run spelling and grammar check, preferably with linter.
[x] Avoid changing any header associated with a link/reference.
[x] Review for wordiness
[x] Match tone and style of page/section.
[x] Run make linkcheck.
[x] View HTML in a browser to check rendering.
[x] Use semantic newlines.
[x] follow best practices for commits.

[x] Descriptive title written in the imperative.
[x] Include brief overview of QA steps taken.
[x] Mention any related issues numbers.
[x] End message with sign off/DCO line (-s, --signoff).
[x] Sign commit with your gpg key (-S, --gpg-sign).
[x] Squash commits if needed.

[x] Request PR review by a technical writer and at least one peer.

Docs for 1e6b5ce77331a842cfc7fb3c93132b5262444a6d are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2787/docs/artifacts/html/index.html

Docs for 534df188047db123149ecea6fcba25c381a69557 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2789/docs/artifacts/html/index.html


There is an extra action 'Pin to Quick Access' for one QA storage account

Storage Explorer Version: 1.29.0-dev
Build Number: 20230329.4
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Ventura 13.2.1 (Apple M1 Pro)
Architecture: ia32/x64
How Found: From running test cases
Regression From: Previous release (1.28.1)
Steps to Reproduce

Select one storage account -> Pin it to the 'Quick Access' node.
Right click the QA storage account -> Observe its context menu.
Check there is no extra action.

Expected Experience
There is no extra action.

Actual Experience
There is an extra action 'Pin to Quick Access'.

This should be fixed in most recent build on main. I confirmed it on my end, but if it's still appearing on your end please open up the issue again. Thanks!

Hi @richardMSFT Verified this issue on the main build 20230330.3. Reproduce.
We are going to re-open this issue.

Update: This issue also reproduces for '(Emulator - Default Ports) (Key)' node under the 'Quick Access' node.

Verified this issue on the build main 20230331.5. Fixed. We are going to close it.


Clarify "na" and "unknown" requirements for organism_*_ontology_term_id

Per https://github.com/chanzuckerberg/single-cell-curation/pull/1063#issuecomment-2436434173

Closed by #1065


Creation Example: -Name should be -RouteServerName

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

ID: a9051fe3-f785-0f9d-3915-8a08d842ab0a
Version Independent ID: b2ae1d2f-3d9d-8ec9-8112-722b315ce283
Content: Quickstart: Create and configure Route Server using Azure PowerShell
Content Source: articles/route-server/quickstart-configure-route-server-powershell.md
Service: route-server
GitHub Login: @duongau
Microsoft Alias: duau

@JustinGrote Thanks for bringing this to our attention. This has been fixed and the changes reflect in the doc in question.


Image on space button doesn't show up when using KeyboardAppearance

Hi!
I have a subclass of StandardKeyboardAppearance in which I override buttonImage(for:) and return an image for the .space action. However, this doesn't have an effect. It does work for other items. Setting a custom text via buttonText(for:) works everywhere, also on the space item.
override func buttonImage(for action: KeyboardAction) -> Image? {
    switch action {
    case .keyboardType(.emojis):
        return nil // this is necessary for the custom button text to show up
    case .space:
        return Image("icon_large") // this has no effect on the space button
    default:
        break
    }
    return super.buttonImage(for: action)
}

override func buttonText(for action: KeyboardAction) -> String? {
    switch action {
    case .keyboardType(.emojis):
        return "🔥" // this works as expected
    case .space:
        return nil // other custom text works, just making this explicit
    default:
        return super.buttonText(for: action)
    }
}

Workaround for the time being (thanks to @danielsaidi for this!):
Set your own button content when creating the keyboard and have a specific content for each type:
SystemKeyboard(controller: controller, autocompleteToolbarMode: .automatic) { item in
   systemKeyboardButton(for: item)
}

@ViewBuilder
func systemKeyboardButton(for item: KeyboardLayoutItem) -> some View {
   switch item.action {
   case .space: Image("icon_large")
   default: SystemKeyboardButtonContent(action: item.action,
                                        appearance: appearance,
                                        keyboardContext: keyboardContext)
   }
}

Hi @hiDominik
Great find, it must have got lost when I added more features to the space bar earlier :)
Since the bar will now fade between the current locale and the space text, it may not be an easy fix, but I will look into it.
Until then, I hope that the workaround works for you. I use it myself, which is why I haven't noticed this issue.

Sure - the workaround works perfectly, therefore no rush needed :)

@hiDominik I have adjusted the button behavior, so that an image returned from the style provider will override the standard space content, which is the locale to "space" animation that shows when you have multiple locales.
This will be available in 8.0 and can be tested in the v8 branch.


Enable inlining external resources

Respec has support for this through the data-include attribute.
I'm using it to include code samples of Web apps within the use case doc for the Generic Sensor API.

You only need local, right?  This should be pretty easy.

Okay, v1 of inclusions are in.  I"ll document it when I'm more finished, but for now just use an <include path='...'></include> element.  It assumes the target document is ordinary HTML at the moment (it doesn't do Markdown or data-block expansion), but that will change.  Recursive includes are allowed, and cycles are detected.
Replacement is done very early, immediately after the document is parsed as HTML, so all the other features of Bikeshed (besides data-blocks and Markdown) work as expected in the includes.

Thanks!
I'll port my use case doc to it and let you know how it goes.

And all done - markdown and datablocks are now processed.  And the bug that makes the top-level elements in an inclusion be inserted backwards is fixed. ^_^


Deprecate releasedCandidateVersions

As @ibuildthecloud accurately pointed out, there's no real reason for us to distinguish releaseCandidateVersions from packageVersions except for the fact that it is nice to have 1 packageVersion bump occur per release.
And from a user perspective, whether a chart bumps from 9.4.20401 to 9.4.20415 does not make a difference as long as one number is greater than the other.
Instead of trying to resolve issues like https://github.com/rancher/charts-build-scripts/issues/7 or adding logic for "Open" vs "Closed" packages as described in https://confluence.suse.com/display/EN/Multi-BranchSet+Release+Process+For+Feature+Charts, we should just deprecate releasedCandidateVersions in favor of always bumping the packageVersion in the pipeline.
As a result, a Package by definition will always be tied to its packageVersion and will be immutable (as opposed to temporarily mutable via multiple releasedCandidateVersions, as defined before).
We should also increase the size of the packageVersion to 4 digits to accommodate for up to 9999 changes to the same major.minor.patch of a chart. After that point, we might as well fork it 😄

Done in v0.2.0.


Create plugin "webhook"

The plugin sends HTTP requests to third-party endpoints to trigger further processing.
A user can define multiple endpoints.

Tests of the dependency checker plugin fail:
[INFO] Sauron Dependency Checker 0.0.64-SNAPSHOT .......... FAILURE [01:45 min]

That code is not touched by this pull request. Any idea how to fix that?

Checks have passed 🎉.
@sergioasantiago @ocristian Feel free to merge the change. I lack permission to do so.


Fix #6950: specify encoding when reading files for --source-code

Can one of the admins verify this patch? (see README)

@tombentley wdyt? Can this be merged?

Can someone please review this patch?

Pushed a new version that falls back to a default encoding in case of setEncoding(null), as suggested by @jvasileff.

Folks, can we merge this pull request or what?

No we can't, because if we have a null encoding, InputStreamReader will throw:
public More ...InputStreamReader(InputStream in, String charsetName)
95         throws UnsupportedEncodingException
96     {
97         super(in);
98         if (charsetName == null)
99             throw new NullPointerException("charsetName");
100        sd = StreamDecoder.forInputStreamReader(in, this, charsetName);
101    }

@lucaswerkmeister do you mind calling InputStreamReader(InputStream) (no charset) if we have a null charset as obtained by getEncoding() else the config value?

Updated, and I hope someone can mark this as “okay to test” :)

LGTM. OK to test.

So do we merge this ?

Absolutely, thanks.

Phew, thanks :)


function application concrete syntax

Reported by choeger on 1 Feb 2011 10:29 UTC
A function application might (according to the concrete syntax at page 224) be followed by
for for_indices
This is not mentioned in the function call syntax (12.4.1) and thus never explained. The exact semantics of that feature seem to be lost.
Maybe this feature might be removed at all. I have grepped through the MSL for " for .* )" but found no match.

Migrated-From: https://trac.modelica.org/Modelica/ticket/490

Comment by dietmarw on 1 Feb 2011 11:00 UTC
Duplicate of #491


Logging to file is not allowed

Hey there,
I'm using the traefik snap on Ubuntu 22.04.02 LTS using the file provider configuration.
The access log configuration in the static configuration file /etc/traefik/traefik.yml looks like that
accessLog:
  filePath: "/var/log/traefik.log"

When the snap is started, apparmor complains about opening/writing:
time="2023-05-02T23:14:41+02:00" level=error msg="Error while opening log file /var/log/traefik.log: open /var/log/traefik.log: permission denied"
audit: type=1400 audit(1683062081.508:102): apparmor="DENIED" operation="open" profile="snap.traefik.traefik" name="/var/log/traefik.log" pid=28937 comm="traefik" requested_mask="rac" denied_mask="rac" fsuid=0 ouid=0

Is there a way to allow the snap to write to logging files?

Snapcraft does not provide an interface to write logs. Instead you can use one of this paths:

/var/snap/traefik/current/traefik.log
/var/snap/traefik/common/traefik.log


Issues with cookie parameters being excluded from formatted document

Seems that components->parameters->cookies are not supported.  In fact, if you add a parameter with in: cookie, the parameter is not included in the output.  That is a bit of a head scratcher.
Supported in version 3.0.3
https://swagger.io/docs/specification/describing-parameters/#cookie-parameters
    "components": {     "parameters": {         "JSESSIONID": {           "name": "JSESSIONID",           "in": "cookie",           "required": false,           "schema": {               "type": "string"           }       }     } }

Looks to be an issue in this block just ignoring cookie based parameters.  Would be simple to add.
https://github.com/thim81/openapi-format/blob/8a2181bcb75126fa9e88692d7e42d03d885cba48/openapi-format.js#L616-L640

@bradworsfold-workday Thanks for reporting the issue.
I'll have a look and it should be rather straightforward to add the cookie parameters.
Did I understand your  use-case correct?
You want to format the OpenAPI document, including the cookie parameters, while instead of being nicely ordered, they are being removed from the formatted result?

Correct.  I have a solution for this.  I will fork and push it up for you to take a look at.

https://github.com/thim81/openapi-format/pull/62

@thim81 is it possible to review the PR and get this in?  Thanks. 🙇

Hi @bradworsfold-workday
I m this week not near a laptop or pc, but my plan was to review the PR next week and potentially release it next week.

hi @bradworsfold-workday
I had the time to review and merge your PR.
Thanks for taking the time to also update the readme and extend the test.
I'm going to close this issue, since openapi-format version 1.11.0 was just released, which contains your PR for adding support for parameters in Cookies ( #62).


Support of L4T R32.5.1 ?

Dear,
I use the latest version of rootOnUSB and follow the README and Videos but after I reboot the system to start from USB drive, the starts fail because no /dev/sda was found.
I use an SSD installed in a Geekworm Jetson Nano T300 expansion adapter with Jetson L4T R32.5.1 .
Any suggestions or hints?
Thanks in advance, Andreas

Yes, I also runing L4TR32.5.1. After reboot, the nano device seems even locked at the BIG NVIDIA LOGO, and then exit and LOGO again until for ever.
since this Repo alardy two years ago, may be need updated.
Just want to know if I install L4T R32.2.4  get this external SSD work first , then upgrade to L4T R32.5.1.
Is this a eay way or not ?
Thanks
Dan

Hi there
I just find a solution on the net, and I already successfully got the job done  yesterday!!
you can following the detail instruction there!
https://robroyce.dev/2021/02/11/how-to-boot-jetson-nano-from-usb-3-0-natively-with-jetpack-4-5/
Dan


protocol compatible

The meaning of the parameter is changed, which can be used or not available depending on the version of the protocol.
Whether to divide classes by version

Solving compatibility problems with 0.1


iommi.js fixed/improved

fixed select2 reset in filter form
improved IommiSelect2
added missing semicolons

this fixes #442

oh, I might also try to add pagination via ajax here


Add private for shopify

Proposed changes
add private so this can't be found
Merge timing
asap

@tcgilbert So the private flag here doesn't necessarily hide the page (it looks like it's already hidden, actually).  If we add private, it means it's in private beta.  Is that the goal?

@tcgilbert So the private flag here doesn't necessarily hide the page (it looks like it's already hidden, actually). If we add private, it means it's in private beta. Is that the goal?

Ah I see. Thanks for clarifying. I'll close this.


[packaging] Bump package versions in requirements.txt

Codecov Report

Merging #1946 (f95ccc8) into master (45fbacb) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1946      +/-   ##
==========================================
+ Coverage   87.90%   87.91%   +0.01%
==========================================
  Files          50       50
  Lines        8620     8637      +17
==========================================
+ Hits         7577     7593      +16
- Misses       1043     1044       +1

Impacted Files
Coverage Δ

reframe/core/runtime.py
88.95% <0.00%> (-0.21%)
:arrow_down:

reframe/frontend/cli.py
76.51% <0.00%> (+0.53%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 45fbacb...f95ccc8. Read the comment docs.


[labs/react] more generic interface with react module

This PR adds a more generic type with a smaller scope in lieu of typeof React.
The entire react "module" is passed as the first argument to createComponent.
However we don't need to use the entire API of the react module. It is more portable to only require what we use:
Component
createComponent
forwardRef

All other instances of react are for types, so the three properties above would have to fit into the expected types from react anyways

this isn't as beneficial as I thought

actually might be beneficial to support preact / react

I tried another take of this here https://github.com/lit/lit/pull/4143 too but ultimately don't feel this is worth pursuing at the moment. It's not going to change anything in terms of types for preact users using preact/compat, and it would make changing any React API usage be breaking.


Add missing datasource to certificate dashboards

This PR adds the missing datasource so the dashboard can be checked on mimir and also fixes the tag ownership because certificate related dashboards should not belong to honeybadger.
Checklist

[x] Update changelog in CHANGELOG.md in an end-user friendly language.

cert-manager is owned by @giantswarm/team-bigmac :)

Thanks @ubergesundheit I then changed the tags


Not compatible with latest version of Gutenberg

Hi,
If you have the latest version of the Gutenberg plugin installed with the latest version of kirki. The CSS is not loading properly. See image below

Thank You

Hello and thank you for reporting this issue.
We are closing most open GitHub issues with the release of Kirki 4 to start fresh with this major release.
If you are still running into issues after you have tested your theme with Kirki 4, please let us know so we can reopen the issue.
Please note that Kirki 3 is no longer actively supported. Moving forward, we will only provide support the very latest version of Kirki.
Thank you for your understanding.
Best,
David


Add "Line Direction" to Graphics2D

This was my first time editing an extension using Scratch.Translate, apologies if I broke anything

What is scratch.translate

What is scratch.translate

An API that allows extensions to have different translations for block text depending on the language you have selected.

What is scratch.translate

An API that allows extensions to have different translations for block text depending on the language you have selected.

Ok

这是我第一次使用Scratch.Translate编辑扩展，如果我破坏了任何东西，请道歉

The correct translation of ray_direction is“（[x1],[y1]）到（[x2],[y2]）的方向”
After adding ray_direction, the translation of “line_section” should be changed to “（[x1],[y1]）到（[x2],[y2]）的距离”（zh）

这是我第一次使用Scratch.Translate编辑扩展，如果我破坏了任何东西，请道歉

The correct translation of ray_direction is“（[x1],[y1]）到（[x2],[y2]）的方向” After adding ray_direction, the translation of “line_section” should be changed to “（[x1],[y1]）到（[x2],[y2]）的距离”（zh）

Went ahead and fixed ray_direction line_section translations

这是我第一次使用Scratch.Translate编辑扩展，如果我破坏了任何东西，请道歉

The correct translation of ray_direction is“（[x1],[y1]）到（[x2],[y2]）的方向” After adding ray_direction, the translation of “line_section” should be changed to “（[x1],[y1]）到（[x2],[y2]）的距离”（zh）

Went ahead and fixed ray_direction line_section translations

By the way, what is your native language?

这是我第一次使用Scratch.Translate编辑扩展，如果我破坏了任何东西，请道歉

The correct translation of ray_direction is“（[x1],[y1]）到（[x2],[y2]）的方向” After adding ray_direction, the translation of “line_section” should be changed to “（[x1],[y1]）到（[x2],[y2]）的距离”（zh）

Went ahead and fixed ray_direction line_section translations

By the way, what is your native language?

I only speak english, I was using google translate to add the translations in the extension.

Any opinions on what this should return?


Implement completion GA event

Could be implemented based on scroll depth, slide progress or something else

N/A

See songMaxIndex event for a similar metric instead of completion.


Strongly typed css variable api

Is your feature request related to a problem? Please describe.
I think many of us have a lot of css variables thrown all around our code in the style strings. This can easily break with the new versions (renames, breaking changes etc.). I think it would be awesome to have an API for this. A simple enum-based dictionary or class of constant strings would do. Naturally, everybody can just use constants, but maybe it's something that can be included in the base. It can also benefit the codebase here in the Mud.

This issue is now organized in our feature requests project
Note: the issue is closed but that doesn't mean that this won't be implemented. Check the project to see how it is scheduled. If enough users vote for a different scheduling it can be changed. Also, if you want to PR this feature you may do so any time.
You can still discuss this feature here!

Duplicate? see my comment in your other issue.

The other issue is #1379


Investigate Blazer support for chameleon cloud use

Clouds using OpenStack Blazer(https://wiki.openstack.org/wiki/Blazar#Introduction) may force having a reservation to boot VMs. Right now will probably have to create reservation manually and there may be some new behvarior in dealing with failing to boot due to no active reservation. Can begin testing once account approved.

looks like will need to use a reservation_id flag when creating VM. and way to fetch the reservations

Blazer requires using keystone v3 endpoint


MINOR: Adding system test for named repartition topics

This is a system test for doing a rolling upgrade of a topology with a named repartition topic.

An initial Kafka Streams application is started on 3 nodes.  The topology has one operation forcing a repartition and the repartition topic is explicitly named.
Each node is started and processing of data is validated
Then one node is stopped (full stop is verified)
A property is set signaling the node to add operations to the topology before the repartition node which forces a renumbering of all operators (except repartition node)
Restart the node and confirm processing records
Repeat the steps for the other 2 nodes completing the rolling upgrade

I ran two runs of the system test with 25 repeats in each run for a total of 50 test runs.
All test runs passed
First 25 test runs
Second 25 test runs
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

ping @guozhangwang, @mjsax, and @vvcephei for reviews

Call for second review @guozhangwang @vvcephei

updated this and rebased from trunk

kicked off new system test https://jenkins.confluent.io/job/system-test-kafka-branch-builder/2105/

Retest this please.


0.13 - 0.14 upgrade breaks when calling memoized_methods from a child class

After upgrading from 0.13 to 0.14 on Rails <IP_ADDRESS> app I get those errors from a child class of:
class AbstractService
  extend Memoist

module:
undefined method 'memoized_methods' for AbstractService:Class
adding require 'memoist' at the top of the file does not resolve the issue.

@januszm can you explain what happens?
The basics definitely work for me.

Funny, on Rails <IP_ADDRESS> it doesn't even know the Memois module and I can't use require 'memoist' because it says no such file.
Anyway, on Rails <IP_ADDRESS> I get this in a call to flush_cache method.
class AbstractService
  extend Memoist

  def run
    flush_cache if respond_to?(:flush_cache)

I think something else must be at play.
Can you try turning off backtrace silencers
# /config/initializers/backtrace_silencers.rb
Rails.backtrace_cleaner.remove_silencers!

And see where the actual error comes from

Now it shows line 102 in lib/memoist.rb
# an ancestor method.
ancestors.grep(Memoist).each do |ancestor|
  ancestor.memoized_methods.each do |m|
    structs << m unless structs.any? {|am| am.memoized_method == m.memoized_method }
  end
end

hmm, yeah this piece of code was added between v0.13.0 and v0.14.0, how about this dirty quick fix?
ancestor.memoized_methods.each do |m|
  structs << m unless structs.any? {|am| am.memoized_method == m.memoized_method }
end if ancestor.respond_to?(:memoized_methods)

@matthewrudy just to be clear, I ommitted this before. I get this error from a child class that inherits from the AbstractService. Maybe this is happening:

Parent class extends Memoist module but doesn't make a call to memoize
Child class calls memoize_methods on its ancestor (which is Parent class)

And here we get the undefined method error because this portion of code wasn't executed:
def memoize(*method_names)
  ...
  Memoist.memoist_eval(self) do
    def self.memoized_methods

because there's no call to #memoize in the Parent, AbstractService class in my case.
Anyway, the current implementation makes using inheritance harder.

@januszm that makes sense.
So I guess we can reproduce with a test.

I tried adding this test
and its passes
def test_memoization_where_superclass_doesnt_call_memoize
    a = Class.new
    a.extend Memoist
    b = Class.new(a) do
      def foo
        @foo_count ||= 0
        @foo_count += 1
        "foo #{@foo_count}"
      end
      memoize :foo
    end

    obj = b.new
    2.times do
      assert_equal "foo 1", obj.foo
    end
  end

Here's my example that fails:
class Abb
  extend Memoist

  def run(*args)
    flush_cache if respond_to?(:flush_cache)
    execute
  end

  protected

  def execute
    # Override this
  end
end

class Bbb < Abb
  protected

  def execute
    some_method
  end

  def some_method
    'FooBar'
  end
  memoize :some_method
end

x = Bbb.new
x.run

NoMethodError: undefined method `memoized_methods' for Abb:Class

It works if I remove the call to flush_cache so this is the place where problems arise

@januszm I get it.
Actually I guess it's enough to say
class Foo
  extend Memoist
end

Foo.new.flush_cache

Let me work out why we don't define memoized_methods when we extend

@matthewrudy - any progress?  I have several class methods on a Device model that I memoize then use Device.flush_cache in an RSpec config.before block.  Not why we do that -- it's legacy code.

I got the same issue too

Submitted a fix in #68


[Announcement] Changing port prefix of iCub model in Gazebo from icubGazeboSim to icubSim

Hi @robotology/all-robotology-developers ,
to simplify the management of shared configuration files between the iCub_SIM simulator and the iCub model in Gazebo, we are thinking about changing the port prefix of the ports opened by the iCub model in Gazebo from icubGazeboSim to icubSim.
By changing your applications and configurations files, this modification should be frictionless, however the possibility of getting something wrong (for example if you have some local and non-versioned configuration/application) is rather high, and for this reason we are making this announcement before the change is made on the master branch of the icub-gazebo repository.
For more information and discussing the issue, please see https://github.com/robotology/icub-gazebo/issues/8 . Please reply on that issue, and not on this one that is just an announcement, thanks.

The change as today have been fully implemented in icub-gazebo master branch and all related repositories.


[BUG] delete link from wash doesn't work the same way as delete from washboard

Describe the bug
Seen while developing an event app.
wash ctl link del
didn't seem to remove link from provider's list of links, because a subsequent link put resulted in error from provider "ignoring duplicate link"
May need some experimentation to reproduce.

Not a bug - was using wrong params for link del. (provider id instead of contract id)

This should be noted for #192, if you supply a 56 character uppercase contract ID we should warn the user


fix dialog fonts on Windows

When encoding=utf-8, dialog font size is incorrect on Windows.
Current

Fixed

Also tearoff dialog
Current

Fixed

The font name is treated as UTF-8 eventhough it's ANSI.

Codecov Report

Merging #2160 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2160      +/-   ##
==========================================
+ Coverage   73.94%   73.94%   +<.01%
==========================================
  Files          90       90
  Lines      131915   131914       -1
  Branches    28967    28968       +1
==========================================
+ Hits        97540    97544       +4
+ Misses      34356    34347       -9
- Partials       19       23       +4

Impacted Files
Coverage Δ

src/if_py_both.h
76.09% <0%> (-0.15%)
:arrow_down:

src/undo.c
81.69% <0%> (-0.07%)
:arrow_down:

src/window.c
81.12% <0%> (+0.03%)
:arrow_up:

src/terminal.c
61.79% <0%> (+0.62%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 22ab547...b25fd7b. Read the comment docs.


[Breaking] Use sign.detached instead of sign to get just the signature

PULL REQUEST
Overview
Previously, the returned signature was longer than SIGNATURE_LENGTH. This is
because sign returns the signed message (including the original message) which
was not necessary -- we only need it to return the signature.
In addition to being unnecessary, it was also confusing to have a signature that
was longer than expected.
Solution
We are now using sign.detached. We already use verify.detached.
This doesn't break the test suite because the extra bytes from sign
were being just ignored. The return value for signature is now different though so we label it
a breaking change.

Two tests failing due to network timeouts. I think it's safe to merge this.


Rework DeviceLink to allow for one input having multiple outputs

This will help with #18. See this comment

Requires #12 to be implemented first


Fix NSString exception in NSError+Git

git_lasterror() may return NULL, which causes an exception in [NSString stringWithUTF8String:]
i.e. if GTRepository - (id)initWithURL:(NSURL *)localFileURL error:(NSError **)error is called with a file:// URL that doesn't exist, the git_repository_open(...) call will fail with code GIT_EOSERR, which indicates that the operating system error codes should be checked.
We fix this case by using the result of strerror(errno) if:

git_lasterror() returned NULL  AND
The error code is GIT_EOSERR

This returns "No such file or directory" in the case given.

Awesome, good catch!


Feature Request: UMI Join

Some tools that work with extracted UMIs expect a specific delimiter between umi1 and umi2 (assuming each read has its own UMI). E.g. fgbio CopyUmiFromReadName (https://fulcrumgenomics.github.io/fgbio/tools/latest/CopyUmiFromReadName.html) expects something like $read_name:ACTG-CCGA .
Currently it seems like fastp can only output $read_name:ACTG_CCGA type formats. This can be shifted after the fastp run, but this shifting gets complex if multiple compressed parts are being written.
Request is a for a now CLI arg --umi_join that will define the character placed between the UMIs in read1 and read2. The default value would remain '_' but could be adjusted to '-'  or '+' for better downstream compatibility.

+1 . Can you add this feature？@sfchen


Sunset px4_fmu-v2_default

Due to a silicon errata on STM32F427VIT6 we can only use 1 MB flash instead of 2 MBs that would be available on the chip.
The target fmu-v2 was used for Pixhawks with the silicon errata while the target fmu-v3 can be used for newer Pixhawks without the errata.
For several years we have maintained the px4_fmu-v2_default target by optimizing flash space and removing debug helpers as well as drivers for less common peripherals and sensors.
Now that the release v1.10 is forked off, it's sensible to sunset the px4_fmu-v2_default target in order to make development easier.
This only removes the _default target which contains multicopter, fixedwing, and VTOL modules but keeps the separate _multirotor, _fixedwing, _rover modules.

Given _fixedwing and _multicopter are also overflowing flash now, we might think about deprecating all v2 targets.

@julianoes - let's add this to the agenda for the dev call and see if we get consensus on it.  FYI @mrpollo

Can you capture the result of the developer call discussion here. It has fairly significant product and documentation implications.
I'm presuming that we'd mark v1.10 as the last supported version for fmu_v2.

@dagar mentioned in the call a couple of reasons why we can't/shouldn't do this:

We will hit the flash limit on other platforms anyway, so it's an ongoing problem that we need to tackle.
Most downloads are fmu-v2_default, so it should probably stay.


Undo Button

Addition of an Undo Button
It will help the user to get back to their previous drawing.
In case of any error the user can go back to the previous work. It will help the user preventing from starting it from the scratch, which will save the time of the user.

please assign the issue to me under gssoc..i can contribute to make it responsive


Did not find movement strategies implemented in the code

Thank you for sharing such an amazing work and truely one of the clearest instructions in using the codes!
I read your paper that the Full Movement strategy gave the best results, where there is a "sequential"relationship between the movement and box branch (bounding boxes on current frames are regressed on centers predicted by the movement branch).
However, I could not find relevant implementation in your code (e.g., box branch depending on movement branch).  Could you guide me where you implemented the movement strategy?
Thank you again!

Training: from L127 to L132
https://github.com/MCG-NJU/MOC-Detector/blob/45c3fd0c5e4ca455e7e739f3ad80b2c91813df35/src/datasets/sample/sampler.py#L127
Inference: from L56 to L 72
https://github.com/MCG-NJU/MOC-Detector/blob/45c3fd0c5e4ca455e7e739f3ad80b2c91813df35/src/detector/decode.py#L56

I see. Thank you for your prmpt response!


Add synopsys include path generation

Creates a target to create a synthesis friendly variable of include paths

Thanks for your contribution. Can you briefly show the type of file that is generated from this and how you use it in your flow?
Otherwise looks good to me. Since its orthogonal to the other code I don't mind merging it.

Use case is to create a .tcl file to construct a aggregate list of include paths which end up being fed to the Genus init_hdl_search_path setting for resolving `includes.
Thank you.

If you say it is for genus then you should name the functions appropriately.

We use genus in our flow but I assume that it would be more usefully named
as synopsys is more common for front end synthesis.
On Tue, May 5, 2020 at 3:42 PM bluew<EMAIL_ADDRESS>wrote:

If you say it is for genus then you should name the functions
appropriately.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pulp-platform/IPApproX/pull/16#issuecomment-624344745,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN7DQY2HDIMXIDJPIET42DRQCI63ANCNFSM4MXIFXNA
.

Thanks its merged


close dialogue when the escape button is pressed

feature request
Dialogue should be close when the escape button is pressed
What is the use-case or motivation for changing an existing behavior?
It is useful for the small dialogue like messages. and its improves the accessibility of the application.

This should be the case already. Do you have an example where it doesn't work?

Are you using an older version of Material? In beta.3, the escape key should close the dialog. It seems to be working on our docs demo.
If you still think this isn't the case for you, please open a new issue with a plunker repro. As it stands, there's not enough for us to look into this.


babel-preset-es2015-rollup

I got this error while compiling:
Module build failed: Error: Couldn't find preset "es2015-rollup" relative to directory "/Users/piaaaac/code/dd-mag/node_modules/jump.js"
Adding babel-preset-es2015-rollup led to successful compiling but now I'm getting:
Uncaught ReferenceError: babelHelpers is not defined
    at jump.min.js:7
    at Object.defineProperty.value (jump.min.js:7)
    at __webpack_require__ (bootstrap 910dd27f6e55ce09ccba:54)
    at Object.defineProperty.value (Manager.js:9)
    at __webpack_require__ (bootstrap 910dd27f6e55ce09ccba:54)
    at Object.<anonymous> (ScrollableAnchor.js:21)
    at __webpack_require__ (bootstrap 910dd27f6e55ce09ccba:54)
    at Object.defineProperty.value (index.js:23)
    at __webpack_require__ (bootstrap 910dd27f6e55ce09ccba:54)
    at Object.<anonymous> (helpers.js:78)

Could anyone help me out? thx

+1, i'm also have the same error

As the error states, it's the jump.js package that wrongfully includes a .babelrc. Remove ./node_modules/jump.js/.babelrc and the app will compile, though you probably don't want to manually tamper with node_modules.


setup.py install fails on Ubuntu vivid: SyntaxError: mismatched input 'as' expecting COLON

After installing jython 2.5.3-3 on Ubuntu 15.04:
jip-0.9.4$ jython setup.py install
"my" variable $jythonHome masks earlier declaration in same scope at /usr/bin/jython line 15.
Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar
Traceback (most recent call last):
  File "setup.py", line 29, in <module>
    from jip import JIP_VERSION as version
  File ".../jip-0.9.4/jip/__init__.py", line 33, in <module>
    from jip.repository import repos_manager
  File ".../jip/repository.py", line 43, in <module>
    from jip.util import DownloadException, download, download_string, get_virtual_home
  File ".../jip-0.9.4/jip/util.py", line 65
    except requests.exceptions.RequestException as e:
                                               ^
SyntaxError: mismatched input 'as' expecting COLON

This feels like it might be an upstream problem with jython, but I am very green at jython.
Also as I am following the typical newbie approach of install jython and then jip, this might be useful to add a helpful error message.

Seems the as keyword is not supported by python 2.5:
http://stackoverflow.com/questions/11285313/try-except-as-error-in-python-2-5-python-3-x

Please update to jip 0.9.5 and test again. jip isn't well tested under python 2.5 so I suggest you to upgrade your jython to latest 2.7.

With 0.9.5:
$ jython setup.py install
"my" variable $jythonHome masks earlier declaration in same scope at /usr/bin/jython line 15.
Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar
/usr/share/jython/Lib/distutils/dist.py:263: UserWarning: Unknown distribution option: 'install_requires'
  warnings.warn(msg)
/usr/share/jython/Lib/distutils/dist.py:263: UserWarning: Unknown distribution option: 'entry_points'
  warnings.warn(msg)
running install
running build
running build_py
creating build
creating build/lib
creating build/lib/jip
copying jip/embed.py -> build/lib/jip
copying jip/search.py -> build/lib/jip
copying jip/index.py -> build/lib/jip
copying jip/dist.py -> build/lib/jip
copying jip/repository.py -> build/lib/jip
copying jip/commands.py -> build/lib/jip
copying jip/cache.py -> build/lib/jip
copying jip/main.py -> build/lib/jip
copying jip/maven.py -> build/lib/jip
copying jip/util.py -> build/lib/jip
copying jip/__init__.py -> build/lib/jip
running build_scripts
creating build/scripts-2.5
copying scripts/jython-all -> build/scripts-2.5
error: build/scripts-2.5/jython-all: Unknown error: 20000

I'm happy to test changes from git so you dont need to do a release.
If you're interested in jip working with the Ubuntu distributed jython, it would be a good idea to add 2.5 to .travis.yml

Supporting python 2.5 would make it harder to implement python 3 support.

Just googled and find this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752357
It's a bug of jython on Debian/Ubuntu.

Closing... Old issue.


Deploy fails for Kubernetes >= 1.22

Deployment is failing for Kubernetes 1.22 and 1.23, here's the output extract from CI:
79	+ bats -t katalog/tests/istio-operator/istio-minimal-install.sh
1s
80	1..2
1s
81	1: Install istio minimal profile
1s
82	Warning: spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].key: beta.kubernetes.io/arch is deprecated since v1.14; use "kubernetes.io/arch" instead
4s
83	Warning: spec.template.spec.affinity.nodeAffinity.preferredDuringSchedulingIgnoredDuringExecution[0].preference.matchExpressions[0].key: beta.kubernetes.io/arch is deprecated since v1.14; use "kubernetes.io/arch" instead
4s
84	Warning: spec.template.spec.affinity.nodeAffinity.preferredDuringSchedulingIgnoredDuringExecution[1].preference.matchExpressions[0].key: beta.kubernetes.io/arch is deprecated since v1.14; use "kubernetes.io/arch" instead
4s
85	Warning: spec.template.spec.affinity.nodeAffinity.preferredDuringSchedulingIgnoredDuringExecution[2].preference.matchExpressions[0].key: beta.kubernetes.io/arch is deprecated since v1.14; use "kubernetes.io/arch" instead
4s
86	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
4s
87	unable to recognize "STDIN": no matches for kind "IstioOperator" in version "install.istio.io/v1alpha1"
4s
88	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
4s
89	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
4s
90	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
4s
91	# waiting... 0
6s
92	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
9s
93	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
9s
94	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
9s
95	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
9s
96	# waiting... 1
11s
97	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
14s
98	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
14s
99	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
14s
100	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
14s
101	# waiting... 2
16s
102	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
19s
103	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
19s
104	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
19s
105	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
19s
106	# waiting... 3
21s
107	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
24s
108	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
24s
109	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
24s
110	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
24s
111	# waiting... 4
26s
112	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
28s
113	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
28s
114	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
28s
115	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
28s
116	# waiting... 5
31s
117	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
33s
118	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
33s
119	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
33s
120	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
33s
121	# waiting... 6
35s
122	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
38s
123	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
38s
124	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
38s
125	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
38s
126	# waiting... 7
40s
127	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
43s
128	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
43s
129	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
43s
130	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
43s
131	# waiting... 8
45s
132	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
48s
133	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
48s
134	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
48s
135	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
48s
136	# waiting... 9
50s
137	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
53s
138	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
53s
139	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
53s
140	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
53s
141	# waiting... 10
55s
142	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
57s
143	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
57s
144	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
57s
145	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
57s
146	# waiting... 11
59s
147	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
62s
148	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
62s
149	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
62s
150	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
62s
151	# waiting... 12
64s
152	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
67s
153	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
67s
154	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
67s
155	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
67s
156	# waiting... 13
69s
157	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
72s
158	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
72s
159	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
72s
160	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
72s
161	# waiting... 14
74s
162	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
76s
163	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
76s
164	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
76s
165	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
76s
166	# waiting... 15
79s
167	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
81s
168	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
81s
169	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
81s
170	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
81s
171	# waiting... 16
83s
172	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
86s
173	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
86s
174	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
86s
175	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
86s
176	# waiting... 17
88s
177	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
91s
178	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
91s
179	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
91s
180	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
91s
181	# waiting... 18
93s
182	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
95s
183	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
95s
184	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
95s
185	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
95s
186	# waiting... 19
97s
187	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
100s
188	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
100s
189	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
100s
190	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
100s
191	# waiting... 20
102s
192	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
105s
193	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
105s
194	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
105s
195	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
105s
196	# waiting... 21
107s
197	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
110s
198	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
110s
199	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
110s
200	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
110s
201	# waiting... 22
112s
202	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
114s
203	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
114s
204	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
114s
205	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
114s
206	# waiting... 23
116s
207	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
119s
208	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
119s
209	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
119s
210	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
119s
211	# waiting... 24
121s
212	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
124s
213	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
124s
214	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
124s
215	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
124s
216	# waiting... 25
126s
217	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
129s
218	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
129s
219	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
129s
220	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
129s
221	# waiting... 26
131s
222	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
134s
223	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
134s
224	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
134s
225	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
134s
226	# waiting... 27
136s
227	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
138s
228	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
138s
229	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
138s
230	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
138s
231	# waiting... 28
140s
232	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
143s
233	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
143s
234	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
143s
235	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
143s
236	# waiting... 29
145s
237	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
148s
238	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
148s
239	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
148s
240	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
148s
241	not ok 1 Install istio minimal profile
148s
242	# (from function `loop_it' in file katalog/tests/istio-operator/./../helper.bash, line 28,
148s
243	#  in test file katalog/tests/istio-operator/istio-minimal-install.sh, line 15)
148s
244	#   `loop_it test 30 2' failed
148s
245	# Timeout waiting a condition

Deploy fails because istio-operator manifests use CustomResourceDefinition in version apiextensions.k8s.io/v1beta1 that is not supported anymore since Kubernetes >= 1.22.
unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
unable to recognize "STDIN": no matches for kind "PodMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"

I'm disabling the e2e checks in the meanwhile.


Selectively disable the datadog agent. This can be useful for some heroku run invocations.

An alternative approach would be to check if the DYNO env var matched run.[0-9]+ and then bail but this is a much lower impact change.

Nice, thanks! Can you elaborate a bit on why someone might not want to start the agent, but have the it installed anyhow?

heroku run is the primary use case, since a slug for an app is used by all dynos you can't really prevent the agent from being installed in the one-off dynos used by heroku run.

:+1: Thanks!

@dreid I tried this today:
$ heroku run --env DISABLE_DATADOG_AGENT=true bash
Running bash on $DYNONAME... up, run.5324
DISABLE_DATADOG_AGENT environment variable is set, not starting the agent.
$

I get immediately disconnected, and cannot use bash in the environment. Have you had success with this?

It appears to not work because of the early exit (I guess all the scripts run in the same shell)
I will try to find time to work on a patch next week.


Update EPA Logo

Definition of Ready

[ ] Does this meet the INVEST criteria?
[ ] Does this have a clearly defined user?
[ ] Does this have an estimate?
[ ] Does this have acceptance criteria?
[ ] Does this have sufficient context for the specific functionality being developed (design, business rules, etc.)
[ ] Does this have a dev link been provided in the design?
[ ] Is this traceable to a feature, epic, or PI?

User Story
As a CAMPD User
I want accurate navigation
So that I cna understand that CAMPD is an EPA Service
Acceptance Criteria
Given a User Accesses CAMPD
When the Homepage Loads
Then The proper EPA logo is displayed
Development Notes
Link to photo
Does this Story require 508 Testing?

[ ] Implementing a new authoring tool that will produce code / content for the application
[ ] Implementing a 3rd party widget that will be part of the application
[ ] Adding new / updating custom functionality
[ ] Adding new / updating a page template
[ ] Adding new / replacing existing functionality (unless the replacement has already passed 508 testing)
[ ] Full Site Review prior to a scheduled EPA 508 review
[ ] Planning a video that will appear on the application
[ ] Producing a video that will appear on the application
[ ] Producing Training materials
[ ] Producing documents

Context
(User journeys, design mockups, architectural diagrams, business rules, data element definitions)
Testing
Test Case:
Tester:
Definition of Done

[ ] Have all Acceptance Criteria been agreed to and validated by the scrum team?
[ ] Has the code been unit tested and peer reviewed?
[ ] Have the functional tests been executed?
[ ] Have all defects been reviewed and dispositioned, resolved, or deferred?
[ ] Is the user story ready to be deployed to the test/staging environments?

ticket no longer needed per Epa Style team


[Improve][e2e][Flink] Execute extra commands on task manager container

Purpose of this pull request
Execute extra commands on task manager container

Check list

[x] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs

@ashulin  PTAL


Feature autocomplete

I will merge this PR, but donwload buttom in dashbord/index.html is removed  (because this index file is no longer used)


(question) Also retrieve content outside shortcodes when parsing

Hello,
I discovered this library while searching for a solution to parse content with Wordpress shortcodes. It is fantastic, thank you for all the efforts you put into this project :)
I'm trying to make sure I'm using it the right way. What I need to achieve is transforming this initial content:
Block of regular text
[my-shortcode id="1"]Shortcode content[/my-shortcode]
Other block of regular text

into an array of blocks
[
  0 => [
    'type' => 'text',
    'content' => 'Block of regular text'
  ],
  1 => [
    'type' => 'my-shortcode',
    'id' => 1,
    'content' => 'Shortcode content'
  ],
  2 => [
    'type' => 'text',
    'content' => 'Other block of regular text'
  ]
]

So everything is working great to parse and extract content from shortcodes, but I am wondering whether there is a way to also extract the content from outside the shortcodes?

Hi @thdebay, thanks for the kind words! I still have an idea in my mind for a shortcode "AST" (Abstract Syntax Tree) where instead of returning shortcodes you would get a kind of tree with all metadata about elements' positions, structure, etc. In your case, I think what you need are shortcode offsets by which you can split the text after parsing. Look at the example below, the final variable $parts contains a list of arrays with type (text or shortcode) and text properties. You can tweak this to have the shortcode instance. As for the "ID", you can use the offset value as it will be unique in the whole text. Also note that RegularParser (unlike WordPress or any other regex-based parser) properly handles nesting, so you need to repeat the process for nested shortcodes. Hope that helps!
<?php
declare(strict_types=1);
namespace X;

use Thunder\Shortcode\Parser\RegularParser;
use Thunder\Shortcode\Shortcode\ParsedShortcodeInterface;
use Thunder\Shortcode\Syntax\CommonSyntax;

require_once __DIR__.'/vendor/autoload.php';

$text = <<<EOF
Block of regular text
[first /][my-shortcode id="1"]Shortócode❤ content[/my-shortcode][last /]
Other block of [inner] regular text
EOF;

$parser = new RegularParser(new CommonSyntax());
/** @var ParsedShortcodeInterface[] $shortcodes */
$shortcodes = $parser->parse($text);
$parts = [];
$offsets = [];
if($shortcodes && $shortcodes[0]->getOffset() !== 0) {
    $offsets[] = 0;
}
$shortcodeOffsets = [];
foreach ($shortcodes as $shortcode) {
    $shortcodeOffsets[] = $shortcode->getOffset();
    $offsets[] = $shortcode->getOffset();
    $offsets[] = $shortcode->getOffset() + mb_strlen($shortcode->getText());
}
$offsets[] = strlen($text);
for($i = 0; $i < count($offsets) - 1; $i++) {
    if($offsets[$i] === $offsets[$i + 1]) {
        continue; // one shortcode right after the other
    }
    $parts[] = [
        'type' => in_array($offsets[$i], $shortcodeOffsets, true) ? 'shortcode' : 'text',
        'text' => mb_substr($text, $offsets[$i], $offsets[$i + 1] - $offsets[$i]),
    ];
}

var_dump($parts); // your actual logic here

Result, compressed a bit, but don't worry - actual result properly handles newlines:
[
    0 => ['type' => 'text', 'text' => 'Block of regular text'],
    1 => ['type' => 'shortcode', 'text' => '[first /]'],
    2 => ['type' => 'shortcode', 'text' => '[my-shortcode id="1"]Shortócode❤ content[/my-shortcode]'],
    3 => ['type' => 'shortcode', 'text' => '[last /]'],
    4 => ['type' => 'text', 'text' => 'Other block of ',],
    5 => ['type' => 'shortcode', 'text' => '[inner]'],
    6 => ['type' => 'text', 'text' => ' regular text'],
]

Thanks a lot @thunderer, this is exactly what I needed. I had thought of another solution based on str_replace() but yours is much better and more efficient with mb_substr() and getOffset(). Again, thank you, I really appreciate your help! I'll implement your solution in my project, and I'd be glad to help with the testing if this feature makes it to the code of the library some day.


Images are broken on Volunteer page

The images are present on t3. When was the last sync done?

Fixed


Distributed Laradock environments

First i have to say laradock is a really really nice solution for moving php applications to containers because it's the only solution which has a really wide support for different modules.
But laradock is clearly oriented more towards development (#143) because it's separating the webserver and php-fpm process which each have to mount the source files by shared folders.
The problem with distributed environments like docker swarm, kubernetes, openshift or any other solution is the management of these source files. You no longer have the ability to update the sourcefiles on every server that your laradock containers will see the new sourcecode.
You could try to solve the problem by "burning" the sourcecode into the nginx/apache/caddy and php-fpm container and no longer use the folder mounting technique. But this solution is tricky in production because container rollout may need a few minutes in geographically distributed environments with hundreds of containers on every continent. It would be much simpler and efficient to roll-out a combined webserver + php-fpm container because they have to share some files. Think of the webserver checking first if a php file is existing to call php-fpm.
I'll propose a new container/solution which simply allows combining the webserver and php-fpm into one container.

@tpetry let's combine them. Will you be willing to submit a PR with that change.
Whoever gonna do this, should make sure we have the least amount of duplicated code, since we currently support 3 PHP versions in the php-fpm container. And we have 3 servers as you named them.

Excellent idea, in my opinion. There is, as you've pointed out, a lot of duplicate code. Fixing that would make it more maintainable as well.

Yes agree... that's sound great...

@Mahmoudz To be honest i will have not time for a PR for several weeks because i will now have to the building of docker containers by my own as laradock was not feasible and there are a few more languages that need to be containerised.
Does anybody have an idea how this could be generally done without duplicating all the code? The docker devs states that they will not extend the Dockerfile language anymore, like adding include statements. And solutions like Ansible/Chef/Puppet would drastically change the orientation of the project.

Just a thought, could we make something like bash script / batch file which will generate the Dockerfile and then we build the image of that generated Dockerfile?

@tpetry kinda the same situation. Hopefully after 6 weeks I'll have more free time..
Let's keep this open, to see if anyone would like to give it a shot.
@a-h-abid that's pretty much the concept of the CLI which I don't think anyone is working on right now. If we gonna do it this way (scripts to generate dockerfiles), we need to have some discussions first, as the tool should be capable of doing other useful stuff.. checkout this video it's a demo from this repo, it's a nice CLI tool, similar to what I had in mind for Laradock a long time ago.
@laradock/admins you might also be interested in checking this repo.

@tpetry Take a look at rocker
I have a question for laradock maintainers relevant to it being oriented towards development. I noticed the project is built where the application code is assumed to be on the host machine, not as a container/volume container, is there an intent to give some focus on production environments?

@calnation yes there's intent to support production as much as we do support development. Obviously, there are some major changes that needs to be done for that purpose, like stop running the workspace by default, merging php-fpm in the servers (nginx)......
If you are willing start that "or anyone else reading this", we'll be more than happy to support you. Just let us know, to make an experimental branch, to test the new changes and help you fix the problems you might face...

Well, what I admire most about Laradock is how it takes into consideration many scenarios out there (at least in development env for now) and simplifies adapting to them. So I'd say you can start by planning things out here for the production env and getting others input, scenarios and ideas for the best way possible to approach this.

@calnation that would be cool.
Also note the PHP version problem is fixed now.

As a quick bit of feedback for you guys on this, you shouldn't need to add both a Webserver and FPM into one container, in fact running multiple processes is taboo. Whilst I don't run laradock in production I run something very close to it, heres a quick break down:
Get rid of the workspace container, it will cause more trouble than its worth. No more mounting to the host OS, this is fine in dev but destroys portability in production.
Copy your laravel public folder into the webserver container.
Copy your laravel project into php fpm container. Also install cron on this container but don't run it.
These two new images will serve all the features of laravel you need.
Create three services from the fpm image, one for the actual fpm process, one for the laravel scheduler (just start the container with the cron start command), one for the laravel queue (Just start the container with the  artisan queue command )
Voila

So... how would I run npm tasks without the workspace container? or composer install/update??

What tasks are you looking to run?

@CharlieTapSonin We are building React-powered websites using Create React App so we need to run npm tasks like: npm start (The page will reload if you make edits), npm run build, npm test, etc.

(off topic) For the react app, #553 could be interesting as well.
(on topic) I really like this discussion. We should implement it sooner rather than later, I think. Would mean a lot less maintenance, as well. However, we should not lose the aspect that makes Laradock pretty cool right now, the workspace functionality. We can still merge it into the php-fpm container and make it args, prefixed with WORKSPACE_ or DEV_ or something.

I'm not particularly familiar with react so I'm not sure if these tasks need to be called for pre production packaging or they are actual tasks that get called in production?
If its the former then it's straight forward enough, just run them prior to copying the files into the images using the existing workspace container.
If its the latter then you would just have to install npm and any other dependencies in the php fpm container.
The key thing really is just ensuring that tools for Dev and build stay in those phases of development, it will mean that your containers stay lighter and have less surface area for attack. That being said @winfried-van-loon you guys should look into using the alpine images for most of the containers, I'm running alpine nginx alongside alpine fpm and it's saved me hundreds of mb.

@CharlieTapSonin Those npm tasks are used during development so not called in production

@cr101 Then yeah just use the workspace container to prep the application files ready for copying into the production container, I actually do this on my CI/CD server as it saves a ton of time.

I've been scouring the documentation and source to find a way to essentially reverse engineer laradock to package these containers for portability so I can run laradock in production on kubernetes.
@CharlieTapSonin you seem knowledgable, may I ask for advice? I believe I have a simple use-case for Laravel: I want to use laravel in our CI/CD pipeline with Gitlab, which will re-create the Nginx & FPM containers via web hook. The problem is that Laradock doesn't seem production ready for anything other than docker-compose. Is it worth trying to make this work for my use-case or should I just start from scratch?
Also, for things like composer, is it best practice to run 'composer install' at build time or deployment time? Seems to be a trade-off of either larger containers or slower deployments.