CompleterCmp - caused by: this.text.toLowerCase is not a function

I wonder if this due to my text being non English.
Would appreciate some help here

@rannaot can you provide an example?

Will try to send something while at home but in general my data is typed... this could also be the reason.
Class FoodName{ id:number; name::string; }
My search data is an Array
something like
'
let serachData=new Array();
searchData.push(new FoodName(1,'לחם');
searchData.push(new FoodName(2,'מיים');
'
Eventually this the data I am sending to the local completer (not directly like this, but this is the data).
this.dataService = completerService.local(this.searchData, 'name');

I see the problem is with the typed data, not with the language.
It can be a nice feature since this is a type lang :)

Hi,
Haven't tried it with an array of classes if you make it an interface it should work:
interface FoodName{ id:number; name:string; }

let serachData=new Array<FoodName>();
searchData.push({ id: 1, name: 'לחם` } as FoodName);
searchData.push({ id: 2, name: 'מים` } as FoodName);


[HOLD for payment 2024-10-31][$250] [Search v2.3] Add Onyx optimistic and failure data

See https://github.com/Expensify/App/pull/48566#issuecomment-2348617805
You should also optimistically display the saved search.
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021836663116286679327
Upwork Job ID:<PHONE_NUMBER>286679327
Last Price Increase: 2024-09-19
Automatic offers:

nkdengineer | Contributor | 104037632

Issue OwnerCurrent Issue Owner: @hoangzinh

Proposal
Please re-state the problem that we are trying to solve in this issue.
Add Onyx optimistic and failure data
What is the root cause of that problem?

The Save search button is not greyed out when offline, but instead takes you to the You appear to be offline page which is probably fine for now, but blocking the button tap would be the standard thing to do here I think!

The save search button is not disabled when we offline
https://github.com/Expensify/App/blob/f7a4aa13979ae71631df79a6ac181c2e9b08f17f/src/pages/Search/AdvancedSearchFilters.tsx#L320

Deleting a saved search has no offline feedback (I'd expect the deleted search to show up greyed out)

https://github.com/Expensify/App/blob/f7a4aa13979ae71631df79a6ac181c2e9b08f17f/src/libs/actions/Search.ts#L61
What changes do you think we should make in order to solve the problem?

The Save search button is not greyed out when offline, but instead takes you to the You appear to be offline page which is probably fine for now, but blocking the button tap would be the standard thing to do here I think!

We can add disabled={isOffline} for the save search button. Or if we want to create optimistic data and failure data for ONYXKEYS.SAVED_SEARCHES with pendingAction as add here with key is queryJSON.hash, name is queryJSON.saveSearchName and query is queryJSON.inputQuery. Then we can also add an error infailureData to display the error
https://github.com/Expensify/App/blob/f7a4aa13979ae71631df79a6ac181c2e9b08f17f/src/pages/Search/AdvancedSearchFilters.tsx#L320

When we delete the saved search here, we can add pendingAction in optimistic data of this saved search as delete and reset it in failureData and we can also add an error if the API fails

https://github.com/Expensify/App/blob/f7a4aa13979ae71631df79a6ac181c2e9b08f17f/src/libs/actions/Search.ts#L61
Then we can add pendingAction field as item.pendingAction here. We can also add error field to display the error and onPendingActionDismiss to clear the error if we want
https://github.com/Expensify/App/blob/f7a4aa13979ae71631df79a6ac181c2e9b08f17f/src/pages/Search/SearchTypeMenu.tsx#L109
What alternative solutions did you explore? (Optional)
NA

Added @allroundexperts experts as the C+ since he's available now to review, to move this forward.

@nkdengineer's proposal looks good enough to me. I think we want to go with the optimistic data creation in this case. @lakchote can confirm this.
🎀 👀 🎀 C+ reviewed

Let's go with optimistic data creation, yes.
@nkdengineer's proposal LGTM.

@lakchote This issue is ready for payment.

friendly bump @johncschuster, please process payment for @nkdengineer thanks!

Thanks for the bump! My bookmark for outstanding payments seems to not include the Awaiting for payment label. I'll take care of this now.

@johncschuster Can we please have a payment summary for this? Thanks!


 If you click the link for it to show up again, you will also notice that it's blank.
Expected:  HostIP should show up on edit/upgrade.

Version - master 2.0 (8/2)
Verified fixed

@tfiduccia is it going to be fixed in 1.x?

I would really appreciate if this could get fixed in the latest stable version and not only in the unreleased 2.0, as the documentation also suggests that Rancher 1.6 will receive full maintenance support til Dec 1, 2018.
Thanks in advance.

Well it's been three months since it's "Verified fixed" and it does not appear working in the latest 1.x May be @vincent99 can comment if @tfiduccia is not available?

In v2 it's not fixed if you use workload instead of load balancer. HostIP in workload settings ignored/
screen

@nosovk This is a different issue then. This is about container binding, the issue here is about the lb, which is a totally different thing. And the ingress in v2 works way better than the lb from rancher 1.6 though.


Install OpenSSL lib from edge in various KEB components

Description
Recently we updated only OpenSSL client but not the library, which was still installed from the stable repo.
$ docker run kyma-environment-subaccount-cleanup-job openssl version
OpenSSL 1.1.1m  14 Dec 2021 (Library: OpenSSL 1.1.1l  24 Aug 2021)

this ensures the library is also the latest available from edge and not vulnerable to https://github.com/advisories/GHSA-ph2x-8239-7xc7
$ docker run kyma-environment-subaccount-cleanup-job openssl version
OpenSSL 1.1.1m  14 Dec 2021

Related issue(s)

https://github.com/kyma-project/control-plane/pull/1343, https://github.com/kyma-project/control-plane/pull/1339

/retest


Strip '://' suffix from remote_write scheme

Issue
Users could mistakenly pass "http://" with a "://" suffix,
            endpoint_schema="http://",  # should have been just "http"

and the generate reldata will be invalid:
    related-units:
      mimir/0:
        in-scope: true
        data:
          remote_write: '{"url": "http://://mimir-0.mimir-endpoints.test-alert-propagation-nxl2.svc.cluster.local:9009/api/v1/push"}'

Solution
Eliminate the problem by always stripping the :// suffix.
Cannot use Literal["http", "https"] because it will reject arbitrary strings such as:
src/charm.py:130: error: Argument "endpoint_schema" to "PrometheusRemoteWriteProvider" has incompatible type "str"; expected "Literal['http', 'https']"  [arg-type]
                endpoint_schema=external_url.scheme,

Context
NTA.
Testing Instructions
Relate mimir to avalanche and juju show-unit avalanche/0.
Release Notes
Strip '://' suffix from remote_write scheme.

Closing due to mixed views.


DevOpsInfrastructure - .Net files for GA stable version

No changes to the API, just generating .net files off stable version spec for GA launch.
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

@microsoft-github-policy-service agree company="Microsoft"

API change check
API changes are not detected in this pull request.


docs: Consider "latest" as the latest version

Description
After the #2345 change we also have to consider "latest" as the latest version, so that we don't show a warning box for that.
Checklist

[x] I have followed the Contributor Guide when preparing my PR.
[x] I have updated/added tests for ALL new/updated/fixed functionality.
[x] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[x] I have updated/added relevant examples in examples or docs.

Breaking Change?

[x] No, this PR is not a breaking change.

Related Issues

I missed this! 😅 didn't think it would give an issue as the versions were as it is in versions.txt
I am not sure if we added the 'latest' in special versions would work. Anyway, this seems good enough.


Implement well-known types for Rust

We want to use custom types (e.g. this) for well-known messages.
These include:

[x] google.protobuf.Timestamp
[x] google.protobuf.Duration
[x] google.protobuf.Any
[x] google.protobuf.FieldMask.
[ ] google.protobuf.Struct
[ ] google.protobuf.*Value (from wrappers.proto)

We have enough well-known types to generate the majority of the Google Cloud APIs.  We can add the remaining ones as time allows.


Warm start an encoder-decoder transformer with a language model

Description
Is it possible to train the language model using a single column text data, and then use this to warm start a transformer encoder-decoder (Translation) model which has labeled pairs?
...
Environment information
OS:  Ubuntu

$ pip freeze | grep tensor
mesh-tensorflow==0.0.5
tensor2tensor==1.12.0
tensorboard==1.13.1
tensorflow==1.13.1
tensorflow-estimator==1.13.0
tensorflow-metadata==0.13.0
tensorflow-probability==0.6.0
tensorflow-serving-api==1.10.1

$ python -V
Python 3.5.2

Have a look at this: https://github.com/tensorflow/tensor2tensor/issues/1469#issuecomment-468576095

Thank you. Will give it a try.


Setup basic infrastructure for template model

Motivation:
Create public template repository so custom models can be created on the top of it.
https://github.com/Green-Software-Foundation/if-model-template

redundant, see #242


FR: support global  HTTP idleTimeout config

(This is used to request new product features, please visit https://discuss.istio.io for questions on using Istio)
Describe the feature request
The default idleTimeout is 1 hour, with the default keep-alive value of many other languages or web frameworks, it is relatively large. This may cause some connection termination problems. I need to modify the idleTimeout values of many services to avoid this.
Can we provide a global configuration, such as adding to meshConfig
Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[X] Virtual Machine
[ ] Multi Control Plane
Additional context

@zxh326 did you mean idle_timeout on tcp_proxy

@zxh326 did you mean idle_timeout on tcp_proxy

https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/core/v3/protocol.proto#envoy-v3-api-field-config-core-v3-httpprotocoloptions-idle-timeout

@zxh326 did you mean idle_timeout on tcp_proxy

https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/core/v3/protocol.proto#envoy-v3-api-field-config-core-v3-httpprotocoloptions-idle-timeout

right now you can config this via destination-rule
what your need is an global IdleTimeout config override this maybe default value keep 1h?

@zxh326 did you mean idle_timeout on tcp_proxy

https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/core/v3/protocol.proto#envoy-v3-api-field-config-core-v3-httpprotocoloptions-idle-timeout

please take a look at this PR https://github.com/istio/api/pull/879


[FCM-81] Sleep for 30 seconds to ensure Kafka is stable

Sleep for 60 seconds to ensure Kafka is stable

Thank you for this PR!
We are already waiting for the port to appear:
- name: Wait for Kafka port
  wait_for:
    host: "{{ sansible_kafka_listen_address }}"

What does waiting 30s before that add to this?

@dennisconrad it's for cases when Kafka does starts up, and port 9092 is available, but then due to config error Kafka dies

That still doesn't explain why we're waiting for 30s before we're even checking for the port :-)  I would understand the other way round, but not like this.
Also, is there another way to ensure Kafka is ready?  Can we check a log file instead, something like...
- name: Wait until Kafka is ready
  wait_for:
    path: /var/log/kafka/startup.log
    search_regex: "^Ready\.$"

?

ok, what about
- name: Wait for Kafka port
  wait_for:
    host: "{{ sansible_kafka_listen_address }}"
    port: "{{ sansible_kafka_port }}"
    state: started
    timeout: "{{ sansible_kafka_wait_for_kafka_port }}"

- name: "Check again after {{ sansible_kafka_waitfor_delay }} seconds to ensure Kafka is stable"
  wait_for:
    delay: "{{ sansible_kafka_waitfor_delay }}"
    host: "{{ sansible_kafka_listen_address }}"
    port: "{{ sansible_kafka_port }}"
    state: started
    timeout: "{{ sansible_kafka_wait_for_kafka_port }}"

How about...
- name: Wait for Kafka port
  wait_for:
    delay: "{{ sansible_kafka_waitfor_delay }}"
    host: "{{ sansible_kafka_listen_address }}"
    port: "{{ sansible_kafka_port }}"
    state: started
    timeout: "{{ sansible_kafka_wait_for_kafka_port }}"
  with_items: [1, 2, 3]

Wait 30 seconds
Wait for port
Wait 30 seconds
Wait for port
Wait 30 seconds
Wait for port

If either of 2, 4, 6 times out, the task fails.

  TASK [kafka : Wait for Kafka port] *********************************************
    ok: [sansible_kafka-xenial] => (item=Initial check)
    ok: [sansible_kafka-bionic] => (item=Initial check)
    ok: [sansible_kafka-xenial] => (item=Second check)
    ok: [sansible_kafka-bionic] => (item=Second check)


How to run TF learn (skflow) Kmeans clustering in multi-machine multi-gpu environment?

Is there any example / guide which shows how to implement skflow(tf.contrib.learn) in distributed GPUs? For example :- I want to implement KMeansClustring using skflow(tf.contrib.learn) in a distributed GPU environment. How should I proceed?
Stackoverflow questions :- here  and here

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!


Question regarding NodeRefs

Hi!
As there is no discussion/Q&A section activated for this repo, I'll ask here.
I am trying to understand how to apply the knowledge of overflowdb's README regarding NodeRefs.

That's why you should never hold a (strong) reference onto them in your main application: it would inhibit the overflow mechanism.

If I understand correctly, one should only hold onto NodeRefs, instead of the "full" nodes. How do I do this when using the cpg?
Let's say I have this example code:
val nodes = cpg.call("name")

How do I get the NodeRefs belonging to these nodes? Should I cast them? (NodeRefs seems to take type parameters?)

On a different note:
cpg.all returns StoredNodes. Are they related to NodeRefs or sth. different altogether? I couldn't find documentation about them, or source code for that matter.
Thanks in advance!

The public api is designed so you'll do the right thing by default. In other words, you'll get NodeRefs, because a Call is a NodeRef:
joern> val call = cpg.call.head
call: Call = Call(
  id -><PHONE_NUMBER>11902973L,
  argumentIndex -> 7,
  argumentName -> None,
  code -> "pat == null",
  columnNumber -> None,
  dispatchType -> "STATIC_DISPATCH",
  dynamicTypeHintFullName -> ArraySeq(),
  lineNumber -> None,
  methodFullName -> "<operator>.equals",
  name -> "<operator>.equals",
  order -> 7,
  signature -> "",
  typeFullName -> "<empty>"
)

joern> call.isInstanceOf[NodeRef[_]]
res6: Boolean = true

joern> call.isInstanceOf[NodeDb]
res7: Boolean = false

You can pass them around and store them in your maps/lists/whereever, they are just a thin reference to the actual data. What you should not do is hold onto the NodeDb instance, which you can get via call.get. On low memory, overflowdb drops the on-heap instance to clear some space, and will use the id from the NodeRef instance to load it back from disk if required.
The domain specific nodes and edges are generated based on the schema. To see the sources, simply run sbt compile and have a look in schema/target/scala-3.1.0/src_managed/main/overflowdb-codegen/io/shiftleft/codepropertygraph/generated

That makes sense, thank you very much!


[BUG] Typo in Iskcon feature name on the home page

Description
Describe the bug:
Typo in Iskcon feature name on the home page
Expected behavior:
Iskcon
Actual behavior:
Iskon

Reproduction Steps
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected result:
A clear and concise description of what you expected to happen at each step.
Actual result:
A clear and concise description of what actually happened at each step.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional Information
Device (please complete the following information):

OS: [e.g., Windows, macOS, Linux]
Browser [e.g., Chrome, Safari, Firefox]
Version [e.g., 22]

Additional context:
Add any other context about the problem here.

Go for it!

CAN YOU PLEASE ASSIGN ME THIS ISSUE?

hey @akshitagupta15june please assign me this task under iwoc'24.


Deprecated packages

npm WARN deprecated<EMAIL_ADDRESS>WARNING: This package has been renamed to react-router-redux. See https://github.com/rackt/react-router-redux/issues/80
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated<EMAIL_ADDRESS>Deprecated, use jstransformer
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated<EMAIL_ADDRESS>react-tools is deprecated. For more information, visit https://fb.me/react-tools-deprecated
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g

#3 close


remove __get_candid_interface_tmp_hack endpoint

Now that candid are in the canister metadata for quite a while, tmp_hack is redundant. It also cannot be set to private like we do in metadata.

@ggreif Why does it cause gas change at all?

@ggreif Why does it cause gas change at all?

I think this is due to the static heap being different which can affect deserialization of bignums due to @Gabor's speculative decoding of compact bignums. @luc-blaeser look familiar to you?
I kicked off the mac build again since it failed due to drun non-determinism.

Hmm, I'm not sure why the perf changed, tbh. I think my original hunch was wrong, actually.

The benchmark may contain deserialization, but I don't know why the perf changed.

We are still using it in our Java Agent so we need to fix it and replace with metadata. Any example how to get idl from running canister using metadata?

If you already have an agent library, you can fetch the state tree with path /canister/<canister_id>/metadata/candid:service. See the spec: https://internetcomputer.org/docs/current/references/ic-interface-spec/#state-tree-canister-information.
Concretely, here is the code in Rust: https://github.com/dfinity/agent-rs/blob/main/ic-agent/src/agent/mod.rs#L994 and code in agent-js: https://github.com/dfinity/agent-js/blob/main/packages/agent/src/canisterStatus/index.ts#L144

If you already have an agent library, you can fetch the state tree, e.g., read_state, with path /canister/<canister_id>/metadata/candid:service. See the spec: https://internetcomputer.org/docs/current/references/ic-interface-spec/#state-tree-canister-information.
Concretely, here is the code in Rust: https://github.com/dfinity/agent-rs/blob/main/ic-agent/src/agent/mod.rs#L994 and code in agent-js: https://github.com/dfinity/agent-js/blob/main/packages/agent/src/canisterStatus/index.ts#L144

Thank you, I will fix our Java code.

Worked. Fixed our Java Agent. We will publish fixed library ASAP. Thanks for help.


[gce-staging-1] Increase size of subnets to match what we are going for in production

This has been applied to staging.

Would it be good to use the same ranges as in production? <IP_ADDRESS>/22 for .org and <IP_ADDRESS>/22 for .com?

can do, what should we do with the public and workers subnets?

<IP_ADDRESS>/22 and <IP_ADDRESS>/22?

done!

also applied now.


add events, use enzyme tests

cc/ @coopy this PR adds events to victory-label and switches to enzyme testing. Depends on FormidableLabs/builder-victory-component#38

Damn, that was silly of me. I'll open another PR for that missed test


remove makemigration from setup script

Since you 0001_initial.py is saved, running makemigration while the file in migration directory, will
https://github.com/beyond-io/ultimatejob/blob/main/setup.sh#L14
generate autofiles.. and cause a mess,
you can use migrate only when 0001_initial is saved,
This file should be modified in git,  whenever model.py is changing.
https://github.com/beyond-io/ultimatejob/blob/main/ultimatejobweb/migrations/0001_initial.py

Working well now


SSL on iOS9

Hello.
I'm using Xamarin.Auth to add "Login with Facebook" functionality to my app.
When running in iOS 9, immediately after presenting the GetUI() View Controller, I get an SSL error alert dialog. The application log is reporting "NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9802)".

Documentation here:
https://developer.apple.com/library/mac/documentation/CoreFoundation/Reference/CFStreamConstants/#//apple_ref/doc/constant_group/CFStream_Error_Domain_Constants_CFHost_
Says the StreamErrorDomainSSL error codes are defined in:
Security/SecureTransport.h
That you can find in XCode or here:
http://www.opensource.apple.com/source/libsecurity_ssl/libsecurity_ssl-36800/lib/SecureTransport.h
-9802 would be errSSLFatalAlert, which doesn't help much I guess.

Hi,
I saw that codes, and it looks like some https call is complaining about invalid ssl certificates.
However I cannot pinpoint which call is failing.
I should debug using the source code rather than the compiled assembly.
Strange enough, the very same app is working in ios 8 (both simulator and real device),
but fails under ios 9.
[cid:566BD339-1A17-483F-ADC0-ECC106D6CA47]http://www.msoft.it/
Supporto Tecnico
supporto<EMAIL_ADDRESS>B-Press S.r.l.
Piazzale Lombardia, 4 - 28100 Novara (NO)
T. +39 0321 499508 - F.+39 0321 492974
Da: Thibault Durand
Risposta: "xamarin/Xamarin.Auth"
Data: lunedì 21 settembre 2015 09:04
A: "xamarin/Xamarin.Auth"
Cc: Supporto MSoft
Oggetto: Re: [Xamarin.Auth] SSL on iOS9 (#95)
Documentation here:
https://developer.apple.com/library/mac/documentation/CoreFoundation/Reference/CFStreamConstants/#//apple_ref/doc/constant_group/CFStream_Error_Domain_Constants_CFHost_
Says the StreamErrorDomainSSL error codes are defined in:
Security/SecureTransport.h
That you can find in XCode or here:
http://www.opensource.apple.com/source/libsecurity_ssl/libsecurity_ssl-36800/lib/SecureTransport.h
-9802 would be errSSLFatalAlert, which doesn't help much I guess.
—
Reply to this email directly or view it on GitHubhttps://github.com/xamarin/Xamarin.Auth/issues/95#issuecomment-141895330.

Hi.
I've tried to debug the source code, and it looks like the error is thrown by the UIWebView inside the WebAuthenticationController, while trying to load this url:
https://m.facebook.com/dialog/oauth/?client_id=1658202597727497&redirect_uri=http%3A%2F%2Fwww.facebook.com%2Fconnect%2Flogin_success.html&response_type=token&scope=email&state=jyeybgpamkrsaodc
I've tried to completely disable ATS by adding the following keys to Info.plist, but with no success at all:
<key>NSAppTransportSecurity</key> <dict> 	<key>NSAllowArbitraryLoads</key> 	<true/> </dict>
Again, this occurs only in iOS 9

Add this to your plist
<key>NSAppTransportSecurity</key>
<dict>
  <key>NSExceptionDomains</key>
  <dict>
    <key>facebook.com</key>
    <dict>
      <key>NSIncludesSubdomains</key> <true/>
      <key>NSThirdPartyExceptionRequiresForwardSecrecy</key> <false/>
    </dict>
    <key>fbcdn.net</key>
    <dict>
      <key>NSIncludesSubdomains</key> <true/>
      <key>NSThirdPartyExceptionRequiresForwardSecrecy</key>  <false/>
    </dict>
    <key>akamaihd.net</key>
    <dict>
      <key>NSIncludesSubdomains</key> <true/>
      <key>NSThirdPartyExceptionRequiresForwardSecrecy</key> <false/>
    </dict>
  </dict>
</dict>

I made the info.plist changes and now I get
"Given URL is not allowed bt the Application configuration.  One or more given URLs is not allowed by Apps settings.

Opt out with until you figure out all the urls.
NSAppTransportSecurity

NSAllowsArbitraryLoads

Opting out using the keys above still gives me the error

this is a issue for ios apps with ATS no xamarin.auth


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/139 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit 11d8065:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 11d8065:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-10-08-08-52-17 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-10-08-08-52-17

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add missing examples for fix functions and additional some old workshop examples as use cases

For the old workshop examples see: #175

Test are failing. From the logs one problem seemed to be to_base64, and indeed if I try to run that that example it fails. Same on test, which uses a newer metafix version. It seems the examples use functionality that's not in main (yet?). Do you have a local Playground running to test this?

I've updated test-PG. See the mentioned to_base64 now ok.

Looks good on deployed Playground, but this PR is failing.
If I understand it correctly what's missing here is the update to current fix & core.

@fsteeg could you have another look!

When good, need to update the documentation.


Linear server

Description
Adds a new Linear MCP server for issue tracking and project management. The server enables LLMs to interact with Linear issues through a standardized MCP interface, supporting core functionality like creating, updating, searching issues and adding comments.
Server Details

Server: Linear
Changes to: created the MCP server - added tools, resources, and prompt

Motivation and Context
Linear is a popular project management tool, and this MCP server enables AI assistants to directly interact with Linear data and workflows. This allows for automated issue management, automated chat-based search for issues, status updates, and team coordination through natural language. It gives Claude context from Linear, and can allow Claude to help you complete your Linear issues and then update them when they're completed.
How Has This Been Tested?
During development, tested resources, prompts, and tools extensively with the MCP Inspector to confirm functionality is working as expected.
After development completed, tested with Claude Desktop client across multiple scenarios, including:

Issue creation with various priorities and statuses
Issue updates and modifications
Complex search queries with multiple filters, or only a single filter
Finding all issues for a team and analyzing those issues
Adding a comment to an issue with markdown formatting

Breaking Changes
None.
Types of changes

[X] New MCP Server
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update

Checklist

[X] I have read the MCP Protocol Documentation
[X] My server follows MCP security best practices
[X] I have updated the server's README accordingly
[X] I have tested this with an LLM client
[X] My code follows the repository's style guidelines
[X] New and existing tests pass locally
[X] I have added appropriate error handling
[X] I have documented all environment variables and configuration options

Additional context

Built using Linear SDK for reliable API interaction: https://developers.linear.app/docs/sdk/getting-started
Structured around core Linear concepts (issues, teams, users, organization), focused on common Linear operations for issue discovery and management for now
Comprehensive resource templates for navigation
Detailed server prompt to help the LLM client understand how to user the server

@jspahrsummers thanks for the heads up - ngl that is disappointing because I worked on this PR before the announcement was shared, and it seems easier for users to integrate MCP servers from the official repo than from community repos (which I think require them to clone the repo locally and then add the appropriate config file to their, rather than using the npx -y) command.
but sounds good, I'll make this a repo and then submit the PR. do you have specific recommendations for how these repos should be structured?

I understand the disappointment—sorry about that! I think there's simply no way for us to scalably manage that many integrations in one place.
However, you can definitely still make your server installable with npx, just by publishing it to npm. 🙂
It's easiest to use npx @modelcontextprotocol/create-server to set up the project with everything you need. Please do open an issue on https://github.com/modelcontextprotocol/create-typescript-server if you run into any problems, and I'd be happy to help.

@jspahrsummers Totally, makes sense. Thanks for the help! Set my server up on npm and submitted a PR to add it here: https://github.com/modelcontextprotocol/servers/pull/229


Why there is a need for 2 (Playwright and NUnit) Adapters in dependencies

Please do not submit this issue.

[x] I understand

Hi,
I am trying to work with Playwright and I am just exploring different things that are needed for working with Playwright.

I came across 2 adapter dependencies when I installed Microsoft.Playwright.NUnit package. Isn't NUnit adapter enough to work? NUnit adapter will be used for both test discovery and test execution. I am confused what is this additional adapter doing here. Does it modify default execution of NUnit Adapter or it completely overrides it somehow?
Does this need node JS runtime to run the tests. I came across this this architecture which says that this language dependencies are very just libraries which provide programming interface to in different languages and there will be WebSocket connection to the Playwright Server where the execution of browser steps happens? So, with this I see it now working without Node JS runtime. Also seeing port of Playwright in README confused me more?
Also wondering about if I can use different tools that I see in nodejs like test reports UI etc. One doubt is NUnit does not support test steps, and in UI I saw has test steps, So I wounder if there will be 2 test reports that will come one in .trx format specific to .NET and one in Playwright format. Playwright format report will be used for that UI (probably without steps I guess as there is no steps anyway in .NET)?
Keeping steps in mind I wounder if you guys have plans to support Reqroll (Formally SpecFlow) framework based NuGet package?

It would be great if this questions are answered to get started with Playwright with great clarity.

It takes care of reading the values from the runsettings file / parameters.

@mxschmitt Thanks for super fast reply. But I was not yet written my questions 😁. It would be really kind of you if you can address my questions.

https://github.com/microsoft/playwright-dotnet/issues/2988
I guess Reqroll (Formally SpecFlow) framework based NuGet package would resolve my 4 point quite easily.

Its not enough, since we have a custom logic to parse the runsettings file with the Playwright properties. This is what our TestAdapter takes care of. It does not modify default execution of NUnit or MSTest.
Internally yes, but this is an implementation detail. Internally we are communicating over stdin/stdout with it. With port we mean the .NET version of Playwright aka. a client.
There is no trx integration with Playwright test steps. Playwright for .NET is just a library. No additional integrations as of today. Tools like VSCode integration, UI Mode or HTML Reporter are Node.js only.
There are no plans for that as of today.


Hyper-parameter tuning

I think this is an important part in most machine learning projects. Any thought on adding it to current pipeline?

Closing since this is out of scope for a project template. Not all DS projects even involve fitting an ML model (some may be simply analysis) so this is likely useful in more specific domain templates.


Fix patching for promise subclasses + strengthen native promise checks

/cc @hayes @watson @Qard @ofrobots

0.12 through 5.x seem to fail on Travis. Not sure why. On mobile at the moment, so can't dig in right now.

Everything should be green now (except for the known failures on 7.x).

Would be cool to add tests that instanceof checks work as expected on promises returned by then, and maybe ensure that if the subclass defines a Symbol.species property that that is also respected. I don't think there are issues with either of these cases, but tests are cheap

@hayes I'm not sure which instanceof checks you are referring to. Are you asking for checks that the result of Promise.then has a natively implemented toString?

On mobile, so not sure if this will be exactly right, but basically was thinking something like:
const p = new Promises class(resolve => resolve(123)).then(() => 456)

p instanceof PromiseSubclass
p instanceof OriginalPromise
p instanceof WrappedPromise

And if Promise.prototype[Symbol.species] is defined, some of those might be false.

To clarify, not a requirement to merge this change, and not testing this change specifically, but would be good for ensuring proper subclassing going forward. It would be easy to write a version of the wrapper around then that doesn't properly handle this

I've added the tests you've described to check the new ES6 class based promise wrappers.

@hayes Could you take a look at the newly added tests?

I think it's good to go, I can merge it, but I don't think I have publish access

@Qard Are you able to publish and update cls?

Ping, when do you think this could be published?

Published. Sorry for the delay.


Reimplement transform

#18 - if I understand correctly, the normal transform is like transformChildren plus transform(this).
If #21 is accepted, this will have to be updated. There will be transform and transformInPlace

I seem to misunderstand transformChildren: does it only affect the direct children of the node? If so, where is the function that affects all descendants?

Yes, it seems to affect only the direct children.
I think there is note an operation to transform all descendants. I think one could build it using transformChildren in the operation, making it recursive

I think the initial use case was replacing a child in an AST which may be immutable

Well, I made #23.
So, what exactly should transform do?

Perhaps we should wait and merge the others PRs, as they would affect this one, correct?

Okay, only this one left. If you had to Javadoc this function, what would it say?

My Javadoc would say this:
Transform can be used to operate on a whole AST, transforming single nodes as desired.
Depending on the AST being modifiable or not the transformation can happen in place or not. In the former case the existing AST is modified directly, otherwise a new AST is generated to replace the previous one.
``

@matozoid I need to finish this :-)

Okay, naming is now in order :-)


Roll engine 5aff31194809..0ad54c210659 (7 commits)

https://github.com/flutter/engine/compare/5aff31194809...0ad54c210659
git log 5aff31194809..0ad54c210659 --first-parent --oneline
2020-03-06<EMAIL_ADDRESS>[web] Fixes IE11 crash due to missing canvas ellipse support and font polyfill failure (flutter/engine#16965)
2020-03-06<EMAIL_ADDRESS>Fix issue viewdidload call while init FlutterViewController (flutter/engine#16672)
2020-03-06<EMAIL_ADDRESS>[fuchsia] fix broken flows when under high load (flutter/engine#16834)
2020-03-06<EMAIL_ADDRESS>Roll src/third_party/skia 93a2a6b8badb..74055566bd14 (2 commits) (flutter/engine#16981)
2020-03-06<EMAIL_ADDRESS>Roll src/third_party/skia 012f8497802e..93a2a6b8badb (4 commits) (flutter/engine#16974)
2020-03-06<EMAIL_ADDRESS>fix shadows and mask filter blurs (flutter/engine#16963)
2020-03-06<EMAIL_ADDRESS>Roll fuchsia/sdk/core/linux-amd64 from cXgMr... to cTw2C... (flutter/engine#16970)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Gold has detected one or more untriaged digests on patchset 7.
Please triage them at https://flutter-gold.skia.org/search?issue=52131.

Commit queue failed; closing this roll.


The pointer isn't threadsafe

If one thread expects the pointer to remain set, while another thread sets it to a different value, undefined behavior may occur. The pointer needs to be thread-local.

You're right, and it's by intention because thread-localizing the pointer degrades performance slightly. The bigger issue is it's still not safe unless everything is thread-localized. Need to come up with some solution for this.

2.0.0 no longer uses pointer variable


Upgrade Jackson 2.17.0 -> 2.17.1

This PR contains the following updates:

Package
Type
Update
Change

Jackson
import
patch
2.17.0 -> 2.17.1

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

Suggested commit message:
Upgrade Jackson 2.17.0 -> 2.17.1

See https://github.com/FasterXML/jackson-bom/compare/jackson-bom-2.17.0...jackson-bom-2.17.1


Add support for Reverso Context

First, thanks for this great tool!
Then, subject says it all: add support for https://context.reverso.net/ as, at least in French, it gives excellent results.
Thanks in advance for considering this request and again for sharing your hard work.
TY
J

Do you know if they have an API?
Would you like to work on it?

Do you know if they have an API?

Looks like they do :)
https://github.com/s0ftik3/reverso-api/blob/master/src/reverso.js
Sadly Python projects seem to only be scrapers
https://github.com/topics/reverso-context-api?l=python
https://github.com/demian-wolf/pyreverso

Would you like to work on it?

I'm afraid I haven't the skills to 😢

Thanks for the helpful links. I will check it out when I have the time


Ability to add metadata to all log event created by logger

Some use cases it would be very beneficial to be able to attach metadata to logger created in some class.
There is MDC and NDC but those are global for thread and are not very good option in async application where some code maybe shared by same thread, for example application which uses workers and each job what workers does have own context and in that context there is logger which is used to log event specific for that job/context.  In that case it would be way more better to attach needed metadata directly to logger.
Some example by pseudo code:
class App {

  void startWorkAtWorker() {
    Context context;

    context.logger = LogManager.getLogger("whatever");
    context.logger.addMetadata("key", "value");

    Worker WorkerInstance;
    WorkerInstance.queue(context)
  }
}

class Worker {
 void runTask() {
  // pick context from queue....

  // run task
   context.logger.info("starting work, this event has metadata, pushed when context created");
 }
}

I certainly recognize the problem. It is a pretty common in reactive applications. The arrival of Loom and scoped values adds extra dimensions to it. Delivering a solution that only fixes the issue for one might jeopardize delivering a good fix for the others. I doubt if there is any one-size-fits-all answer to this. I personally expect MDC/NDC to be populated from scoped values in the future.
Coming back to your proposal of enriching the Logger with an extra field... Let's say we have implemented that. How will the downstream use it? We need to adapt all layouts to take this new field into account too. Hence, "a new field to Logger" has far reaching implications.
Using MapMessage
An approach you can carry yourself out is to use MapMessages instead:
context.addMetadata("githubUserId", "vy");
logger.info(new MapMessage(Map.of(
    "message", "comment submitted",
    "metadata", context.getMetadata())));

This is an area where Log4j shines compared to other logging solutions in the market: You can log anything that implements the Message interface, you are not limited to Strings.
Injecting a dynamic MDC entry
You can try injecting into MDC an Object whose toString() will return (or StringBuilderFormattable#formatTo(StringBuilder) will render) the metadata stored in the TaskContext. Something like this might work:
private volatile TaskContext taskContext;

private void initMdc() {
    ObjectThreadContextMap map = (ObjectThreadContextMap) ThreadContext.getThreadContextMap();
    map.put("taskMetadata", (StringBuilderFormattable) (buffer -> buffer.append(taskContext.getMetadata())));
}

private void performTask() {
    taskContext.addMetadata("foo", "bar");
    logger.info("buzz");
}


Сompatibility with another extension

Hello! I won't describe the problem again, it has already been described here.  Is it possible to fix this from your side or should the author of that extension fix it directly? Thanks!

From beirfly looking through the code, this can probably be fixed by removing this line and this line, therefore the InputAccordion is at the top level within the Extension, instead of being nested 1 layer deep.
I can probably support it. But this will be low priority for me.

Yes, it is correct, I hope the author will make the necessary changes. Thanks!


Updated Cosmos Hub 2 information to fix typos

Fixes #14 and #23

👍
At the moment you still need to run npm run parse after making changes to update the lists that are checked in.
Also please use two separarte "Fixes" lines in description in order to auto-close and reference both tickets.

@webmaster128 Thanks for the tips! Updated everything

@RiccardoM as the dotted line indicates, only the first issue will be closed:

If you drop the "and" word, a second "fixes" command is found and both ticket will be closed and referenced

@RiccardoM as the dotted line indicates, only the first issue will be closed:

If you drop the "and" word, a second "fixes" command is found and both ticket will be closed and referenced

Sorry, used to Gitlab which is smarter and allows for single liners. The additional "and" was a refuse of the correction


Support Docker Compose environments?

I have all my environments in docker machines, and I'd like to configure phpsab.executablePathCS and phpsab.executablePathCBF` to run in the container. Something like
docker-compose exec php vendor/bin/phpcs path/to/files/to/lint
I'd rather not run phpcs from my host operating systems.
I was hoping to do something like this, but I cannot get it working. Is this possible?
-mike

Any update?

Yeah, this would be great to have!
SanderRonde/phpstan-vscode has a great implementation of this with their phpstan.binCommand config option. Would be great to have something similar here.

This fork of this repo appears to work well actually https://github.com/mtbdata711/vscode-phpsab-docker. Probably just a matter of somebody opening a pull request to merge the changes into here.

Yeah, I don't have time to actively work on this project these days and I work in .net now. I will always field PRs though.

@valeryan perhaps it would make sense to update the readme to include details on the fork that works with docker, and then you could close this ticket?
Happy to submit a pr to update the readme.

Information about how to find the docker fork was added to the readme. Closing this. If the developer of that fork wants to look at a way to add docker support to the main extension through PR I will check it out.


System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (in v3.0.476)

Describe the bug
I'm having issues opening my PS4 save data in the editor. Every time I attempt to open the file, I receive an error.
To Reproduce
Steps to reproduce the behavior:

Go to 'Save editor
Click on open file
Scroll down to a save for the PS4
See error

System Information

OS: [e.g. Windows 10 2004]
Game version [e.g. Stream, GOG and please include the CS]
Version of the editor: [e.g. 3.0.476]

Additional context
Please also attach a save file that exhibits the issue.

Can you fill out the form, and or attach the save file?

I was able to figure it out. I had to export the file through the advance mode on Save Wizard.


Add support for composer.json when using truncate_with_package_name

It would be nice to be able to truncate directory names with the name of a composer/PHP project. The strategy should use the name present in either package.json or composer.json depending on which one is present. When both are present, allow the user to choose which one has precedence.
Any suggestions?

I'm not a JS developer myself, so I don't think I have good enough of an understanding of normal workflows to weigh in, here.
A sane default will need to be chosen, though, which users can override - I'm thinking package.json since

@ettoredn Interesting idea! I actually use composer a lot. I'll see what I can do here, once I have some time (might be after #344 is done).
Btw. a quick idea regarding having a composer.json and a package.json in the same folder: I think that could be separate segments. Here somebody implemented truncation with a stopfile. We could use that in combination with a separate composer/package.json segment. By joining (and some icon-tricks) it could look like one segment..

@ettoredn Have a look at #412 . There I implemented truncate via composer.json ;)

Another feature request knocked out by @dritter!
#412 has been merged into next!


Witherspoon: Unable to boot Ubuntu on w37

[ 9.021567] Unable to handle kernel paging request for data at address 0x00002260
[ 9.021567] Unable to handle kernel paging request for data at address 0x00002260
[ 9.022501] Faulting instruction address: 0xc0000000006c7770
[ 9.022501] Faulting instruction address: 0xc0000000006c7770
[ 9.023105] Oops: Kernel access of bad area, sig: 11 [#1]
[ 9.023105] Oops: Kernel access of bad area, sig: 11 [#1]
[ 9.023674] SMP NR_CPUS=2048
[ 9.023674] SMP NR_CPUS=2048
[ 9.023676] NUMA
[ 9.023676] NUMA
[ 9.023970] PowerNV
[ 9.023970] PowerNV
[ 9.024372] Modules linked in: ofpart cmdlinepart ipmi_powernv powernv_flash ipmi_devintf mtd ipmi_msghandler ibmpowernv opal_prd uio_pdrv_genirq uio vmx_crypto ip_tables x_tables autofs4 ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt crc32c_vpmsum fb_sys_fops drm ahci libahci tg3
[ 9.024372] Modules linked in: ofpart cmdlinepart ipmi_powernv powernv_flash ipmi_devintf mtd ipmi_msghandler ibmpowernv opal_prd uio_pdrv_genirq uio vmx_crypto ip_tables x_tables autofs4 ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt crc32c_vpmsum fb_sys_fops drm ahci libahci tg3
[ 9.027146] CPU: 15 PID: 354 Comm: kworker/u64:2 Not tainted 4.10.0-8-generic #10-Ubuntu
[ 9.027146] CPU: 15 PID: 354 Comm: kworker/u64:2 Not tainted 4.10.0-8-generic #10-Ubuntu
[ 9.027978] Workqueue: events_unbound flush_to_ldisc
[ 9.027978] Workqueue: events_unbound flush_to_ldisc
[ 9.028468] task: c0000016a7758c00 task.stack: c0000000fd084000
[ 9.028468] task: c0000016a7758c00 task.stack: c0000000fd084000
[ 9.029055] NIP: c0000000006c7770 LR: c0000000006c7758 CTR: c0000000006c84b0
[ 9.029055] NIP: c0000000006c7770 LR: c0000000006c7758 CTR: c0000000006c84b0
[ 9.029767] REGS: c0000000fd0878c0 TRAP: 0300 Not tainted (4.10.0-8-generic)
[ 9.029767] REGS: c0000000fd0878c0 TRAP: 0300 Not tainted (4.10.0-8-generic)
[ 9.030520] MSR:<PHONE_NUMBER>80b033 <SF,HV,VEC,VSX,EE,FP,ME,IR,DR,RI,LE>
[ 9.030520] MSR:<PHONE_NUMBER>80b033 <SF,HV,VEC,VSX,EE,FP,ME,IR,DR,RI,LE>
[ 9.030537] CR: 28002888 XER: 00000000
[ 9.030537] CR: 28002888 XER: 00000000
[ 9.031579] CFAR: c000000000b3e20c DAR:<PHONE_NUMBER>002260 DSISR: 40000000 SOFTE: 1
[ 9.031579] GPR00: c0000000006c7758 c0000000fd087b40 c00000000143c900<PHONE_NUMBER>000000
[ 9.031579] GPR04: c000000002ac8c20 c000000002ac8d20<PHONE_NUMBER>000100<PHONE_NUMBER>000001
[ 9.031579] GPR08: c0000016ae0ebcc0<PHONE_NUMBER>000001 c00000000139a5a0 c0000016a7758ca8
[ 9.031579] GPR12:<PHONE_NUMBER>002888 c00000000fb88700 c0000000000f6668 c0000016b4b7e3c0
[ 9.031579] GPR16: c0000016c90322d8 c0000016c9032090 c0000016c9032020<PHONE_NUMBER>000001
[ 9.031579] GPR20:<PHONE_NUMBER>000000<PHONE_NUMBER>000000 c000000001335ce9<PHONE_NUMBER>000000
[ 9.031579] GPR24:<PHONE_NUMBER>000000<PHONE_NUMBER>000000 c000000002ac8c20 c0000016b4f932a0
[ 9.031579] GPR28: c000000002ac8d20<PHONE_NUMBER>000100 c0000016a8dca608 c0000016ae0ebc00
[ 9.031579] CFAR: c000000000b3e20c DAR:<PHONE_NUMBER>002260 DSISR: 40000000 SOFTE: 1
[ 9.031579] GPR00: c0000000006c7758 c0000000fd087b40 c00000000143c900<PHONE_NUMBER>000000
[ 9.031579] GPR04: c000000002ac8c20 c000000002ac8d20<PHONE_NUMBER>000100<PHONE_NUMBER>000001
[ 9.031579] GPR08: c0000016ae0ebcc0<PHONE_NUMBER>000001 c00000000139a5a0 c0000016a7758ca8
[ 9.031579] GPR12:<PHONE_NUMBER>002888 c00000000fb88700 c0000000000f6668 c0000016b4b7e3c0
[ 9.031579] GPR16: c0000016c90322d8 c0000016c9032090 c0000016c9032020<PHONE_NUMBER>000001
[ 9.031579] GPR20:<PHONE_NUMBER>000000<PHONE_NUMBER>000000 c000000001335ce9<PHONE_NUMBER>000000
[ 9.031579] GPR24:<PHONE_NUMBER>000000<PHONE_NUMBER>000000 c000000002ac8c20 c0000016b4f932a0
[ 9.031579] GPR28: c000000002ac8d20<PHONE_NUMBER>000100 c0000016a8dca608 c0000016ae0ebc00
[ 9.038511] NIP [c0000000006c7770] n_tty_receive_buf_common+0xb0/0xdf0
[ 9.038511] NIP [c0000000006c7770] n_tty_receive_buf_common+0xb0/0xdf0
[ 9.039139] LR [c0000000006c7758] n_tty_receive_buf_common+0x98/0xdf0
[ 9.039139] LR [c0000000006c7758] n_tty_receive_buf_common+0x98/0xdf0
[ 9.039766] Call Trace:
[ 9.039766] Call Trace:
[ 9.040009] [c0000000fd087b40] [c0000000006c7758] n_tty_receive_buf_common+0x98/0xdf0 (unreliable)
[ 9.040009] [c0000000fd087b40] [c0000000006c7758] n_tty_receive_buf_common+0x98/0xdf0 (unreliable)
[ 9.040868] [c0000000fd087c10] [c0000000006cc524] tty_ldisc_receive_buf+0x44/0xe0
[ 9.040868] [c0000000fd087c10] [c0000000006cc524] tty_ldisc_receive_buf+0x44/0xe0
[ 9.041595] [c0000000fd087c40] [c0000000006ccd9c] flush_to_ldisc+0x13c/0x160
[ 9.041595] [c0000000fd087c40] [c0000000006ccd9c] flush_to_ldisc+0x13c/0x160
[ 9.042265] [c0000000fd087c90] [c0000000000ed8c0] process_one_work+0x2b0/0x5a0
[ 9.042265] [c0000000fd087c90] [c0000000000ed8c0] process_one_work+0x2b0/0x5a0
[ 9.042955] [c0000000fd087d20] [c0000000000edc58] worker_thread+0xa8/0x650
[ 9.042955] [c0000000fd087d20] [c0000000000edc58] worker_thread+0xa8/0x650
[ 9.043625] [c0000000fd087dc0] [c0000000000f67b4] kthread+0x154/0x1a0
[ 9.043625] [c0000000fd087dc0] [c0000000000f67b4] kthread+0x154/0x1a0
[ 9.044245] [c0000000fd087e30] [c00000000000b4e8] ret_from_kernel_thread+0x5c/0x74
[ 9.044245] [c0000000fd087e30] [c00000000000b4e8] ret_from_kernel_thread+0x5c/0x74
[ 9.044964] Instruction dump:
[ 9.044964] Instruction dump:
[ 9.045281] eb3f0260 7c9a2378 7cbc2b78 7cdd3378 f8e10030 48476a55 60000000 3b000000
[ 9.045281] eb3f0260 7c9a2378 7cbc2b78 7cdd3378 f8e10030 48476a55 60000000 3b000000
[ 9.046128] 7af783e4 60000000 60000000 60420000 7c2004ac e8d90000 80ff0110
[ 9.046128] 7af783e4 60000000 60000000 60420000 7c2004ac e8d90000 80ff0110
[ 9.047044] ---[ end trace 6b3bf4b72485f95c ]---
[ 9.047044] ---[ end trace 6b3bf4b72485f95c ]---
[ 9.047485]
[ 9.047485]
I used to see this once in a while. But. on w37 it fails every IPL.

This is a linux kernel bug, not skiboot.

@yadlapati - please open an issue against open-power/linux

Actually, the Linux repository has issues turned off. @mikey @shenki where should these be reported?

https://github.com/open-power/op-build

It's a ubuntu bug.  Should be opening in launchpad https://launchpad.net/ubuntu
FWIW, I think the fix is https://patchwork.kernel.org/patch/9106291/ I'll try to get it upstream.

I can take care of submitting it to Canonical once we narrow down to the missing patch.

FWIW gregkh too the fix for me here  https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next&id=71472fa9c52b1da27663c275d416d8654b905f05


RTMP Live stream issue

when publishing live streams from OBS the RTMP server keeps repeating the video and the audio forever. (Infinite loop).

The same here, I'm using the relay feature and the video keeps repeating.
Any news?

I've decided to move on and I'm currently using Icecast media server, which
is way better.
Check out Icecast here in this link https://icecast.org/download/, and
let me know if you need help to run it.
Best,
Jo
On Sun, Jul 5, 2020, 8:46 PM Sandro Simas<EMAIL_ADDRESS>wrote:

The same here, I'm using the relay feature and the video keeps repeating.
Any news?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/illuspas/Node-Media-Server/issues/333#issuecomment-653917885,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYYLDJEMOS4WBVJCPWHVKLR2C36RANCNFSM4MSO6DOA
.

I've decided to move on and I'm currently using Icecast media server, which is way better.

Icecast features set if not comparable with Node-Media-Server, if you need audio stream icecast is fine if you need video streaming over HLS and Websocket support then Icecast is not going to provide such features.


Cannot download v7.0.3

I have an issue when yarning the package. The error message is as below
error An unexpected error occurred: "xxx/cross-spawn/-/cross-spawn-7.0.3.tgz: Request failed \"500 Internal Server Error\"".

Does anyone have the same issue?

Which command did you run? Was it yarn add<EMAIL_ADDRESS>If so, I couldn't reproduce it here

I think that is an internal issue with verdaccio. Thanks for taking a look!

I think that is an internal issue with verdaccio. Thanks for taking a look!


no progress with honggfuzz on file

I'm attempting to use honggfuzz in the current Rode0day competition and I'm having a problem with the file target.  I compiled file with hfuzz-clang to run in the instrumented mode.  The seed file is a simple ascii text file.
Unfortunately, even after running for hours, honggfuzz seems to never generate new inputs.  It generates one new input, but then gets stuck.  Do you have any idea why this might be the case?
Here is my command line:
honggfuzz -i inputs --output outputs/fileS4_hf/queue -n 4 -W outputs/fileS4_hf/crashes -w dict/consts.txt -- hf/bin/file -m built/share/misc/magic.mgc ___FILE___

And the lack of progress:
------------------------[  0 days 02 hrs 32 mins 57 secs ]----------------------
  Iterations : 1,693,114 [1.69M]
  Mode [3/3] : Feedback Driven Mode
      Target : hf/bin/file -m built/share/misc/magic.mgc ___FILE___
     Threads : 4, CPUs: 16, CPU%: 401% [25%/CPU]
       Speed : 200/sec [avg: 184]
     Crashes : 0 [unique: 0, blacklist: 0, verified: 0]
    Timeouts : 0 [10 sec]
 Corpus Size : 2, max: 8,192 bytes, init: 1 files
  Cov Update : 0 days 02 hrs 32 mins 57 secs ago
    Coverage : edge: 182/5,218 [3%] pc: 4 cmp: 6,572
---------------------------------- [ LOGS ] ------------------/ honggfuzz 1.9 /-

Feel free try this

Feel free to try this:

Works well for me:
------------------------[  0 days 00 hrs 00 mins 27 secs ]----------------------
Iterations : 37,793 [37.79k]
Mode [3/3] : Feedback Driven Mode
Target : ./persistent-file
Threads : 8, CPUs: 16, CPU%: 836% [52%/CPU]
Speed : 1,807/sec [avg: 1,399]
Crashes : 0 [unique: 0, blacklist: 0, verified: 0]
Timeouts : 0 [10 sec]
Corpus Size : 220, max: 8,192 bytes, init: 438 files
Cov Update : 0 days 00 hrs 00 mins 08 secs ago
Coverage : edge: 860/3,946 [21%] pc: 0 cmp: 25,690
---------------------------------- [ LOGS ] ------------------/ honggfuzz 1.9 /-

Also, are you sure you compiled the whole libmagic with hfuzz-cc?
Btw, to compile the static *.a version (to use my example), please compile libmagic with
CC="honggfuzz/hfuzz_cc/hfuzz-clang" ./configure --enable-static --disable-shared

Thanks!

I'm not sure why honggfuzz was getting stalled with the native invocation, but it works fine with the persistent-file.c driver.

------------------------[  0 days 00 hrs 06 mins 09 secs ]----------------------
  Iterations : 82,587 [82.59k]
  Mode [3/3] : Feedback Driven Mode
      Target : hf/bin/file built/share/misc/magic.mgc
     Threads : 4, CPUs: 16, CPU%: 401% [25%/CPU]
       Speed : 155/sec [avg: 223]
     Crashes : 26 [unique: 26, blacklist: 0, verified: 0]
    Timeouts : 0 [10 sec]
 Corpus Size : 613, max: 8,192 bytes, init: 1 files
  Cov Update : 0 days 00 hrs 00 mins 01 secs ago
    Coverage : edge: 1,091/5,079 [21%] pc: 6 cmp: 31,948
---------------------------------- [ LOGS ] ------------------/ honggfuzz 1.9 /-

Ah.. with your original example, please add -L after file, otherwise file will not follow symlinks, and honggfuzz provides it with /dev/fd/1021 which technically is a symlink.
     -L, --dereference
             option causes symlinks to be followed, as the like-named option in ls(1) (on systems that support symbolic links).  This is the default if the environment variable POSIXLY_CORRECT
             is defined.

Great catch.  I didn't think of that.  AFL first tries to hard link the input file locally and falls back to symlinks so I've never come across this issue before.  I had seen the dev/fd references in the process list, but I didn't think about those being symlinks.


Error archivebox init

E:\ArchiveBox>archivebox init
←[01;30m[i] [2021-03-27 03:50:10] ArchiveBox v0.5.4: archivebox init←[00;00m
←[01;30m    > E:\ArchiveBox←[00;00m

←[01;32m[*] Updating existing ArchiveBox collection in this folder...←[00;00m
    E:\ArchiveBox
←[01;32m------------------------------------------------------------------←[00;00m

←[01;32m[*] Verifying archive folder structure...←[00;00m
    √ E:\ArchiveBox\sources
    √ E:\ArchiveBox\archive
    √ E:\ArchiveBox\logs
    √ E:\ArchiveBox\ArchiveBox.conf

←[01;32m[*] Verifying main SQL index and running migrations...←[00;00m
    √ E:\ArchiveBox\index.sqlite3

Traceback (most recent call last):
  File "d:\python\lib\site-packages\django\db\backends\utils.py", line 82, in _execute
    return self.cursor.execute(sql)
  File "d:\python\lib\site-packages\django\db\backends\sqlite3\base.py", line 411, in execute
    return Database.Cursor.execute(self, query)
sqlite3.OperationalError: no such function: JSON_VALID

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "d:\python\lib\runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "d:\python\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "D:\Python\Scripts\archivebox.exe\__main__.py", line 7, in <module>
    from .cli import main
  File "d:\python\lib\site-packages\archivebox\cli\__init__.py", line 129, in main
    run_subcommand(
  File "d:\python\lib\site-packages\archivebox\cli\__init__.py", line 69, in run_subcommand
    module.main(args=subcommand_args, stdin=stdin, pwd=pwd)    # type: ignore
  File "d:\python\lib\site-packages\archivebox\cli\archivebox_init.py", line 33, in main
    init(
  File "d:\python\lib\site-packages\archivebox\util.py", line 112, in typechecked_function
    return func(*args, **kwargs)
  File "d:\python\lib\site-packages\archivebox\main.py", line 323, in init
    for migration_line in apply_migrations(out_dir):
  File "d:\python\lib\site-packages\archivebox\util.py", line 112, in typechecked_function
    return func(*args, **kwargs)
  File "d:\python\lib\site-packages\archivebox\index\sql.py", line 98, in apply_migrations
    call_command("migrate", interactive=False, stdout=out)
  File "d:\python\lib\site-packages\django\core\management\__init__.py", line 168, in call_command
    return command.execute(*args, **defaults)
  File "d:\python\lib\site-packages\django\core\management\base.py", line 371, in execute
    output = self.handle(*args, **options)
  File "d:\python\lib\site-packages\django\core\management\base.py", line 85, in wrapped
    res = handle_func(*args, **kwargs)
  File "d:\python\lib\site-packages\django\core\management\commands\migrate.py", line 243, in handle
    post_migrate_state = executor.migrate(
  File "d:\python\lib\site-packages\django\db\migrations\executor.py", line 117, in migrate
    state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
  File "d:\python\lib\site-packages\django\db\migrations\executor.py", line 147, in _migrate_all_forwards
    state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
  File "d:\python\lib\site-packages\django\db\migrations\executor.py", line 227, in apply_migration
    state = migration.apply(state, schema_editor)
  File "d:\python\lib\site-packages\django\db\migrations\migration.py", line 124, in apply
    operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
  File "d:\python\lib\site-packages\django\db\migrations\operations\models.py", line 92, in database_forwards
    schema_editor.create_model(model)
  File "d:\python\lib\site-packages\django\db\backends\base\schema.py", line 324, in create_model
    self.execute(sql, params or None)
  File "d:\python\lib\site-packages\django\db\backends\base\schema.py", line 142, in execute
    cursor.execute(sql, params)
  File "d:\python\lib\site-packages\django\db\backends\utils.py", line 66, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "d:\python\lib\site-packages\django\db\backends\utils.py", line 75, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "d:\python\lib\site-packages\django\db\backends\utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "d:\python\lib\site-packages\django\db\utils.py", line 90, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "d:\python\lib\site-packages\django\db\backends\utils.py", line 82, in _execute
    return self.cursor.execute(sql)
  File "d:\python\lib\site-packages\django\db\backends\sqlite3\base.py", line 411, in execute
    return Database.Cursor.execute(self, query)
django.db.utils.OperationalError: no such function: JSON_VALID

Your SQLite3 install needs to have the JSON extension enabled: https://www.sqlite.org/json1.html
You should either install Python 3.9, or enable the JSON extension manually by following the instructions here: https://code.djangoproject.com/wiki/JSON1Extension#windows


Test breaking locally, travis passed

@barberboy
Referencing #4
Running node fizzbuzz.js, output looks correct. Though travis test passed, running test on desktop breaks with:

assert.js:89
throw new assert.AssertionError({
^
' on line 1.ror: Expected '1' to be '1
at C:\Users\James\Documents\GitHub\fizzbuzz\test\index.js:21:20
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)

I had the same issue with the local tests.


TSX navigate to definition

This may be a duplicate, but I could not find it between issues.
It is a feature request, to have the possibility to use "CMD+R" just like in ".ts" files to navigate to definition / symbol.
Thanks! Keep up the great work!

released https://github.com/TypeStrong/atom-typescript/releases/tag/v7.14.1 :rose:

Awesome! Works! :tulip:

Hi, this is not working again ;(

Actually .. sorry .. this is working, but pressing "CMD + SHIFT + R" in tsx files gets nothing. Should I open a new issue?

If you feel like there is a bug go for it 🌹


Provide way to open the merge editor even if the "source control" pane doesn't load

Type: Feature Request
I'm fixing up old PRs; merging main leads to far too many changes for the Source Control pane to load. But, now I can't click on a conflicted file to be open it in the new merge editor. The only option I get are the inline buttons to accept specific changes, when I just really want the option that will let me accept the combination (the best merge editor feature).
VS Code version: Code - Insiders 1.91.0-insider (aea213b7fcc7de5c24ad797ac1af209b159d451f, 2024-06-28T05:56:20.804Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

For reference, I see:

No merge editor button, none of the palette buttons do the thing I'm looking for.

Glad to hear you like the merge editor! ❤
I think you can configure VS Code as merge tool in git (there are CLI options to pass base/input1/input2/result paths to VS Code).
Then git merge tool (or a similar command) will open the merge editor of VS Code.
@lszomoru Can we do something here?

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

@jakebailey, thanks for the screenshot. The "Source Control" view is being rendered by running git status and then parsing the output. Given the screenshot, what I am suspecting is that your are in a state in which running git status returns more than 10,000 entries hence we show a warning. Could you confirm that? Could you try setting the git.statusLimit setting to 0 in order to remove this limit. Did that help? Thanks!
Adding @chrmarti as well since he owns the merge conflict codelenses.

Setting "git.statusLimit": 0 allowed the source control page to load:

When opening a file manually in the editor, I now get the button bottom right:

And clicking on the conflicted file in the source control pane also works to open the merge editor.
Verifying without the setting, the source control page never loads and the button never appears, so my test case is at least good.
If you want to test this yourselves, I've pushed https://github.com/jakebailey/TypeScript/tree/merge-testing up; doing git merge main creates the 20000 file merge.

It sounds like I can leave this setting on; even when I set it to zero, the UI was responsive and working fine.
One thing I'm wondering here is whether or not it would be worth it for VS Code to instead use something like git diff --name-only --diff-filter=U or git diff --check to get a list of conflicting files, in the case where it can't parse out the status. But if setting the status limit to 0 to allow unlimited parsing works fine, that's also good and I'll keep using it in the meantime!
Offering the button on files with merge conflict markers would also be pretty helpful; that doesn't require any additional git parsing as VS Code already sees those markers and handles them for other UI...


Does this project have a CHANGELOG.md or similar?

If you are NOT on macOS and have come here to file an issue about compatibility problems,
please stop and go to #115 for your answer.
You can look through many other similar closed issues as well if you're interested:
https://github.com/strongloop/fsevents/search?utf8=✓&q="notsup"+OR+"EBADPLATFORM"&type=Issues.
If you are here to report an issue observed while using this module on OS X, please delete
all this pre-filled text then go ahead and submit your report.

https://github.com/fsevents/fsevents/commit/10512a2aec64751af391e662407210193ec32607

https://github.com/fsevents/fsevents/commit/10512a2aec64751af391e662407210193ec32607

The intent is to be as stable as possible. If a bug has been fixed or a change has been made we try to mention it in the release notes (github release).
At this point there are no actual major changes. Any change that would usually be mentioned in a changelog would trigger a major version release.
So TL;DR: sort of (github-release notes) but not really

The intent is to be as stable as possible. If a bug has been fixed or a change has been made we try to mention it in the release notes (github release).
At this point there are no actual major changes. Any change that would usually be mentioned in a changelog would trigger a major version release.
So TL;DR: sort of (github-release notes) but not really


Update 'internals.md' with the latest build changes

PR Summary
Fix #7057
Update internals.md to reflect the latest build changes.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[ ] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[ ] Not Applicable
OR
[x] User-facing Documentation needed

[x] Issue filed - Issue link:

Testing - New and feature

[x] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

@daxian-dbw Please fix a spelling error.

@iSazonov Sorry that I missed it :)


[protobuf] Well-known types should be full models

For example, if I use the well-known LatLng type in a REST API, it should work. Presently the type has no fields so I can't leverage that type's shape outside of proto contexts.

I don't think all of them should be full models. Maybe LatLng is special in this respect, because Any is what we map tsp unknown to. We may need a bit more robust of a mechanism for the REST/Protobuf hybrid-context use-case.

Ah sure, I guess to be more specific, well-known object types should be models, and well-known scalars should extend appropriate scalars.


Move iOS 12 CI build to GitHub Actions

Travis CI no longer has free macOS builds, so it's time to migrate away. This moves our iOS 12 snapshot CI build over to GitHub Actions.

Had to pin SnapshotTesting to 1.7 in the sample app because 1.8 dropped support for Xcode 10. Really wish that had been considered a breaking change. 😞  Unfortunately GitHub Actions doesn't have an easy way to run iOS 12 tests on Xcode 11, so we need to keep up Xcode 10 support.

Had to pin SnapshotTesting to 1.7 in the sample app because 1.8 dropped support for Xcode 10. Really wish that had been considered a breaking change. 😞  Unfortunately GitHub Actions doesn't have an easy way to run iOS 12 tests on Xcode 11, so we need to keep up Xcode 10 support.

I already marked the Travis CI build as a non-required check since it isn't working properly. Once this is merged I'll mark the new iOS 12 build as required.

[ ] Add Xcode Build (iOS_12) as required PR check

I already marked the Travis CI build as a non-required check since it isn't working properly. Once this is merged I'll mark the new iOS 12 build as required.

[ ] Add Xcode Build (iOS_12) as required PR check

We've added the SwiftUI tests on master since this PR was opened. The CI build rebases before building, so it was pulling in the SwiftUI changes which don't compile on Xcode 10. I added some Swift version checks to only compile those on Xcode 11+. This shouldn't affect anything since those tests are marked as iOS 13+ anyway.

We've added the SwiftUI tests on master since this PR was opened. The CI build rebases before building, so it was pulling in the SwiftUI changes which don't compile on Xcode 10. I added some Swift version checks to only compile those on Xcode 11+. This shouldn't affect anything since those tests are marked as iOS 13+ anyway.

Sorry for the issues with this because of the SwiftUI views. I took a look at it and I could get the tests run locally (Xcode 10.3, 11.3.1 and 12.2) with the following changes:

Remove the -weak_framework for SwiftUI in the "Other Linker Flags" for the Example Project again
Add another #if swift(>=5.1) flag around both SwiftUI Tests
Update all #if swift(>=5.1) flags to #if swift(>=5.1) && canImport(SwiftUI)

Sorry for the issues with this because of the SwiftUI views. I took a look at it and I could get the tests run locally (Xcode 10.3, 11.3.1 and 12.2) with the following changes:

Remove the -weak_framework for SwiftUI in the "Other Linker Flags" for the Example Project again
Add another #if swift(>=5.1) flag around both SwiftUI Tests
Update all #if swift(>=5.1) flags to #if swift(>=5.1) && canImport(SwiftUI)

Oh awesome, that's a super clean fix. Thanks @fbernutz! No worries about the issues, the required Xcode version support was kind of vague.

Oh awesome, that's a super clean fix. Thanks @fbernutz! No worries about the issues, the required Xcode version support was kind of vague.


Can't import Bestiary 4 - Dodo (Familiar)

Can't import statblock:
Dodo (Familiar)      CR 1/4
XP 100
Dodo (Pathfinder RPG Bestiary 4 96)
N Small animal
Init +0; Senses low-light vision; Perception +3
Defense
AC 11, touch 11, flat-footed 11 (+1 size)
hp 6 (1d8+2)
Fort +4, Ref +2, Will -1
Offense
Speed 20 ft.
Melee bite +1 (1d3-4)
Statistics
Str 3, Dex 11, Con 14, Int 2, Wis 9, Cha 6
Base Atk +0; CMB -5; CMD 5
Feats Weapon Finesse
Skills Acrobatics +0 (-4 to jump), Perception +3
Ecology
Environment temperate or warm islands
Organization solitary, pair, or huddle (3-6)
Treasure none
Special Abilities
Low-Light Vision See twice as far as a human in dim light, distinguishing color and detail.

Used your latest module that was available as of about 10:30 am. I used Hero Lab to produce this statblock. For greater accuracy, you might want to use one of the online resources. Hero Lab can truncate some of the text -- or inject errors due to a lack of data. All the other statblocks from Bestiary 4 imported -- a total of more than 85% imported!


Or filters with warnings

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Should be merged after or-queries PR. Adds warnings when .filter is not used correctly and modifies tests to react to warnings correctly.

also, please rename PR with conventional commit prefix


[Bug] timeout argument not working correctly

UNFLoader.exe -r "E:\Games\N64\EverDrive 64\1 US - A-M\Lode Runner 3-D (USA).z64" -c 6102 -t 3 -h 12

Running this command instantly closes the process after it reaches 100%. No timeout occurs. Same with -t 3000, so it doesn't seem to be milliseconds either.
This is with commit e8c9501, built by myself.

Timeout is for debug mode specifically, which I know isn't very clear...
The intended purpose for it was for unit tests or similar purposes, where a ROM is executed with debug logging for a specific period of time and then closed soon after. I can patch it to work outside of debug mode as well :slightly_smiling_face:

The main use I have for it is using it in automated scripts. Leaving the window open with a "pause" at the end is kind of redundant. :P

The timeout should (supposedly) remove that pause at the end. I'll check this code later today or tomorrow since my exams are over.

Sounds good. And yes, the timeout does remove the pause at the end. It just ends instantly without any delay, regardless of the seconds given.

Latest commit (ca7408e) should now have timeout for non debug mode usage. Please check if everything is working!

 Pushed a backup that I made before I pulled the changes from Korgeaux's PR's. The correct commit it (3d4b413) :sweat_smile:

I'll give it a try asap. :)

Timeout still doesn't seem to work. I tried this command in a command prompt:
UNFLoader.exe -r "007 - GoldenEye (USA).z64" -c 6102 -t 3 -h 12

That's weird. CLOCKS_PER_SEC must differ between Linux and Windows...

Yeah after doing a bit of reading, the return value clock(), and by extension CLOCKS_PER_SEC seems to differ in a varying amount of ways for all sorts of reasons.
tl;dr, there is no one singular function for both Windows and Linux which'll return the same value. Even on different machines running the same OS, the values of clock() can differ plenty.
I'm moving this to low priority, since the code is working, just not with a consistent time between devices... The workaround is to just change the value of the -t to something that works best for the user.

https://stackoverflow.com/questions/12244153/behaviour-of-clocks-per-sec-in-different-operating-systems

Yeah, there's a bunch of other intricacies as well with clock(), like how it's based on how long the program is running for, so sleep() screws with that.

I edited my post. The example uses gettimeofday, not sleep().

Ugh, for some reason I was thinking that clock_gettime() and gettimeofday() weren't part of standard libs like time.h... I'll give it a try in a bit.
Also I was referring to how my code uses sleep() (particularly in debug mode), and how that messes with the return value of clock() (because clock() returns CPU time, and sleep() doesn't consume any of that)

Ah. I see. Well, there's no rush on this. I was just noting my findings.

I switched to using time() instead of clock(). Can you please test 00e85a9?

Well, I started it with a timer of 3 seconds. 20 minutes later it's still staying up with "Press any key to continue, or wait for timeout."

I missed a spot... Try ad4f5b3.

It now goes back to its old method of just immediately ending and not having a timeout at all.

Perhaps this might help? https://www.pluralsight.com/blog/software-development/how-to-measure-execution-time-intervals-in-c--

You've been building these yourself, right? Can you try grabbing one of the Azure builds instead and seeing if that works?
I already tested this with both debug mode on and off on:

Windows 10
Windows 7
Windows XP
Linux

And I have been unable to replicate the timeout issue. It's working perfectly on the devices I've tested...

Yes I've been using Visual Studio 2019 to build. I'll give it a try later. Really strange.

Lol. Apologies. Weekends typically keep me busy. I'll take a look tomorrow during work. Heading to bed now and I've been busy all day. Haha.

I tried the Azure build and it also doesn't work properly.

Does it usually take that long to upload on your 64Drive? For instance, a 32MB ROM uploads in 2 and a half seconds on mine...
The timeout value starts counting down as soon as the application opens, so it might simply be that, by the time the upload has finished, the timeout value is long past.

It is probably due to me running USB over ethernet. No data is lost, but the transmission is probably slower. I haven't had any issues. I would figure the timeout would start after it completes, as that is what I'm used to for timeout options. lol.

That is a fair assumption, lol...
 I guess I won't take the lazy way out and do it properly :sweat_smile:

Hopefully, the conclusive commit. 4dc1ffd

That fixed it! Tested with a couple various commands. :)

:partying_face:


Maximum subset XOR

Problem: Given an array of N positive integers. Find an integer denoting the maximum XOR subset value in the given array.
Asked in Microsoft
Concept: Bit manipulation
Contributor: DevIncept
Please assign this to me. Will solve in C++

Hello, I can solve this in CPP and Even I can work with Python. Can I contribute over here?

Sure @ishikasinha-d, you can go ahead !

@shubhdholakiya, please create a new issue, if you want to solve this in Python.

@smv1999 Should I put it in the bit manipulation folder? Or create another folder for questions asked in  Interview?

Yes put it in Bit Manipulation folder @ishikasinha-d


Provide Relay Modern integration in docs.

Suggestion: With the release of Relay Modern yesterday, it would be cool to have a Relay integration included within the documentation for ReactQL.
I'm not saying a Relay version of ReactQL needs to be spun up at this point in time but instead providing guidelines in the docs for how-to/best practices on Relay integration would satisfy most use-cases.
Realise this adds extra complexity but it could also benefit the adoption of ReactQL by opening it up to a wider audience - and by keeping Relay-related info in the documentation rather than adding it to the codebase there will be less confusion.
Thoughts?

Sure, makes sense. Tracked in https://github.com/reactql/docs/issues/7

***Tracked in https://github.com/reactql/old_docs/issues/7


support ipv6_cidr_block in network acls

Description
Add support for ipv6_cidr_block in *_{in|out}bound_acl_rules.  As a
conseqeunce, the (ipv4) cidr_block is made optional.
The other options have been reindented but are otherwise unchanged.
After this patch, you can use ipv6-ACLs like this:
module "vpc" {
  source = "terraform-aws-modules/vpc/aws"

  name = "Test"
  cidr = "<IP_ADDRESS>/16"
  enable_ipv6 = true
  public_subnet_assign_ipv6_address_on_creation = true

  azs              = ["us-east-1a","us-east-1b"]
  public_subnets   = ["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]
  private_subnets  = ["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]
  public_subnet_ipv6_prefixes = [ 1, 2 ]

  enable_nat_gateway = true

  public_dedicated_network_acl = true
  public_inbound_acl_rules =  [
    { rule_number = 600, rule_action = "allow", from_port =    80, to_port =    80, protocol = "tcp", cidr_block       = "<IP_ADDRESS>/0"        },
    { rule_number = 601, rule_action = "allow", from_port =   443, to_port =   443, protocol = "tcp", cidr_block       = "<IP_ADDRESS>/0"        },
    { rule_number = 610, rule_action = "allow", from_port =    80, to_port =    80, protocol = "tcp", ipv6_cidr_block  = "::/0"             },
    { rule_number = 611, rule_action = "allow", from_port =   443, to_port =   443, protocol = "tcp", ipv6_cidr_block  = "::/0"             },
    { rule_number = 698, rule_action = "allow", from_port = 32768, to_port = 61000, protocol = "tcp", cidr_block       = "<IP_ADDRESS>/0"        },
    { rule_number = 699, rule_action = "allow", from_port = 32768, to_port = 61000, protocol = "tcp", ipv6_cidr_block  = "::/0"             },
  ]

  public_outbound_acl_rules = [
    { rule_number = 601, rule_action = "allow", from_port =    80, to_port =    80, protocol = "tcp", cidr_block       = "<IP_ADDRESS>/0"        },
    { rule_number = 602, rule_action = "allow", from_port =   443, to_port =   443, protocol = "tcp", cidr_block       = "<IP_ADDRESS>/0"        },
    { rule_number = 611, rule_action = "allow", from_port =    80, to_port =    80, protocol = "tcp", ipv6_cidr_block  = "::/0"             },
    { rule_number = 612, rule_action = "allow", from_port =   443, to_port =   443, protocol = "tcp", ipv6_cidr_block  = "::/0"             },
    { rule_number = 698, rule_action = "allow", from_port =  1024, to_port = 65535, protocol = "tcp", cidr_block       = "<IP_ADDRESS>/0"        },
    { rule_number = 699, rule_action = "allow", from_port =  1024, to_port = 65535, protocol = "tcp", ipv6_cidr_block  = "::/0"             },
  ]

  private_dedicated_network_acl = true
  private_inbound_acl_rules =  [
    { rule_number = 699, rule_action = "allow", from_port = 32768, to_port = 61000, protocol = "tcp", cidr_block       = "<IP_ADDRESS>/0"        },
  ]
  private_outbound_acl_rules = [
    { rule_number = 601, rule_action = "allow", from_port =    80, to_port =    80, protocol = "tcp", cidr_block       = "<IP_ADDRESS>/0"        },
    { rule_number = 602, rule_action = "allow", from_port =   443, to_port =   443, protocol = "tcp", cidr_block       = "<IP_ADDRESS>/0"        },
  ]
}

Without this patch, this config results in the following error:
Error: Invalid index

  on .terraform/modules/vpc/terraform-aws-modules-terraform-aws-vpc-13fc020/main.tf line 574, in resource "aws_network_acl_rule" "public_outbound":
 574:   cidr_block  = var.public_outbound_acl_rules[count.index]["cidr_block"]
    |----------------
    | count.index is 7
    | var.public_outbound_acl_rules is list of map of string with 10 elements

The given key does not identify an element in this collection value.

Thanks, Bas! We are 1 step closer to IPv6 now :)
v2.17.0 has been just released.


Gas price unit on offline transactions at MEW

If I want to make an Offline transaction at MEW, I would like to be sure on which unit the software is calculating the gas price. I'm only able to see this message: "This was displayed in Step 1 on your online computer".
Is it in Gwei or in Wei?  A link to http://ethgasstation.info would be perfect to know how much are we paying.
In the other hand, how it's calculated the gas price of a normal MEW transaction?
Congratulations for the work on MEW.

Hi jmiehau,
The gas is in Wei. We manually set the gas price at this time and the gas price on the offline tab is the same price as the online tab. We have only changed the gas price once when it was recommended during the network attacks. At that time we increased the price to<PHONE_NUMBER>0.
The transaction fee is the gas price * gas limit. A default transaction has a gas limit of 21000. The current gas price we are using is<PHONE_NUMBER>0 (or	0.00000002 ETH).
21000 * 0.00000002 Ether = 0.00042 Ether ($0.02)
You can typically see this by clicking on a recent transaction to our donation account (as those are almost always sent via MyEtherWallet: https://etherscan.io/tx/0x876b563ef7f45875df681fe1cbb97a7f713d3ece81648bd1323a27827dcfc56e


No unbound variable reported for variable self assignment inside function

Environment data

Language Server version: 2023.7.30
OS and version: Windows 10 21H2
Python version (& distribution if applicable, e.g. Anaconda): 3.10 mambaforge

Code Snippet

y = y

def test():
    x = x
    z

def test2():
    x.next()

Expected behavior
The line x = x inside test() should show a ~"x" is not defined~ local variable 'x' referenced before assignment error.
Edit: I realize after running the snippet that the error should be for an unbound local variable, not undefined variable.
Looking at the docs I would assume this case should be properly identified
Actual behavior
In all cases except x = x, Pylance shows the correct error. But in this case, it is treated as a valid assignment.

Sorry for all the noise on this issue tracker. After investigating further, I see there is a discrepancy between the reportUnboundVariable docs and reality:
Docs:

The default value for this setting is "error".

Vscode default config is "information":

Closing since it appears pylance indeed identifies this case, just doesn't show it in the editor without adjusting the default settings.

@ntjess, the default value of reportUnboundVariable depends on your python.analysis.typeCheckingMode setting. If typeCheckingMode is off, most of our diagnostics rules (including reportUnboundVariable) will be set to none by default. However, if you change typeCheckingMode to basic or strict, more diagnostics are enabled by default, and reportUnboundVariable for example will default to error.
I believe that the config setting UI always shows the same default values for our diagnostic rules regardless of your typeCheckingMode setting. That's unfortunate, but regardless the default for reportUnboundVariable doesn't make sense. I would expect it to be either none (the off default) or error (the basic default), but not information.
Seems like we should review these default and make sure they are up-to-date. So I'm reactivating this issue to track that.

The reportUndefinedVariable check is performed based entirely on binding information — i.e. information about which symbols are in the symbol table for each scope in a program. The reportUnboundVariable check requires code flow analysis and is done as part of type evaluation. That's why it's disabled when type checking is disabled. At least that's the logic behind the current defaults. I think there's an argument that could be made in favor of making reportUnboundVariable a "warning" by default when type checking is "off".

@debonte I can go through all the settings and make sure the default values match with our docs.

Thanks @StellaHuang95. It's possible that the docs are out of date as well. I believe the source of truth is the off/basic/strict lists in packages\pyright\packages\pyright-internal\src\common\configOptions.ts plus the overrides in _applyPylanceDiagnosticOverrides.

This issue has been fixed in prerelease version 2023.7.43, which we've just released. You can find the changelog here: CHANGELOG.md


windows server 2019 do not respond for any nvm commands during remote session or when execute over azure devops pipeline task

Operating system and version: Windows Server 2019 Std
nvm debug output:

Windows PowerShell
Windows Version: 10.0 (Build 17763)
Windows Developer Mode: UNKNOWN (user cannot read registry)
NVM4W Version:      1.1.12
NVM4W Path:         C:\ProgramData\nvm\nvm.exe
NVM4W Settings:     C:\ProgramData\nvm\settings.txt
NVM_HOME:           C:\ProgramData\nvm
NVM_SYMLINK:        C:\Program Files\nodejs
Node Installations: C:\ProgramData\nvm
Total Node.js Versions: 1
Active Node.js Version: v20.11.1
No problems detected.
Find help at https://github.com/coreybutler/nvm-windows/wiki/Common-Issues

nvm ls output:

 * 21.6.2 (Currently using 64-bit executable)

How did you install nvm? using nvm-windows (nvm-setup.exe) version 1.1.12

What steps did you perform? Double click install, then npm install latest
What happened? Installed and configured nvm and can use locally from server using powershell and cmd
What did you expect to happen? nvm commands to work from azure devops pipeline or PSSession remote but it doesn't respond for ever
Azure DevOps Version and Agent used:

Azure DevOps Server 2019
Agent version used: 2.200.0
NVM version: 1.1.12

Everything works with:

Azure DevOps Server 2019
![Uploading Log-PS-NVM_Timeout.png…]()
Agent version used: 2.200.0
NVM version: 1.1.11

You’re using nvm-windows, which is an entirely different project.


gRPC and proto3 beta!

Alain, does it pass locally?
I aggressively cache the outout of the python build process. Cached directories are currently:

$HOME/gopath/dist/grpc/.build_finished
$HOME/gopath/dist/grpc/grpc/python2.7_virtual_environment
$HOME/gopath/dist/grpc/lib/python2.7/site-packages

We probably have to adjust these paths in .travis.yml?
In any case, we need to delete the cache for the "master" branch and this pull request to make the test pass: https://travis-ci.org/youtube/vitess/caches
Otherwise, Travis will just always skip the build of gRPC and protobuf.

@michael-berlin : Only the grpc python versions should be affected, and we don't test these in travis yet, so I think with the fixed typos, it will just work. gRPC / python is much better now, I think it's close to production quality already.

Nice! I left a few small comments, LGTM after those are fixed (and Travis passes)

@alainjobart grpc python is used by the Travis tests as well. Tests are currently failing due to a Python import.
I've deleted all caches and restarted the failing test shards. For now, Travis should pass without the cache.
To make it pass with the cache, we need to update the cached Python output directories.

@michael-berlin the python import was my bad, leftover from a debug session. It will work without it, no grpc python involved in travis tests for now.
The caches, once rebuilt, will work. We're getting closer to adding grpc python tests into travis I think.

(and thanks for the review guys, was waiting for travis to pass to ask for it explicitly :) )


ECS Task Definition: Updating network mode should force replacement

What happened?
pulumi version: v3.45.0
aws-native plugin: 0.43.0
sdk: "github.com/pulumi/pulumi-aws-native/sdk/go/aws/ecs"

ECS Task definition was deployed without a network mode specified.
Updated ECS Task definition network mode to awsvpc and resulted in the following error when pulumi attempted to update the task definition:
preview:
    ~ aws-native:ecs:TaskDefinition: (update)
        [id=arn:aws:ecs:us-west-2:<redacted>:task-definition/LJWk46EDDqfqcJOMut5ZQB2iU-aWZI8HIi0OLT:1]
        [urn=urn:pulumi:cloudsec-vulnerability-management-infra.vuln-management.rpo::findings-generator::aws-native:ecs:TaskDefinition::vuln-mgmt-infra-relay]
      + networkMode: "awsvpc"

error
  aws-native:ecs:TaskDefinition (vuln-mgmt-infra-relay):
    error: operation error CloudControl: UpdateResource, https response error StatusCode: 400, RequestID: 476719c2-544a-4e79-acfa-a66dfad4cde6, NotUpdatableException: Invalid patch update: createOnlyProperties [/properties/NetworkMode] cannot be updated

Steps to reproduce

create a task definition with a service without a network mode specified
update network mode to awsvpc

Expected Behavior

recreate the task definition with the AWSVPC mode

Actual Behavior

pulumi attempted to update the task definition rather than replace it

Output of pulumi about
No response
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

reopening this under the aws-native repo


use correct framework

the undocumented names (without period in dotnet 5+) can drop their support when move to double-digit (to avoid potential conflicts) learn.microsoft.com/en-us/dotnet/standard/frameworks#supported-target-frameworks

@kasperk81 so what's your end goal?
You hide your activity but you obviously use a bot to open this exact same PR in 100+ projects that you found by searching those non-standard TargetFrameworks monikers.
How do you then profit when you own an account that had 100s of meaningless PR merged?


Add a type transformer for whylogs dataset profiles

TL;DR
This adds a type plugin that enables whylog's dataset profiles to participate in the flytekit task framework.
Type

[ ] Bug Fix
[ ] Feature
[x] Plugin

Are all requirements met?

[ ] Code completed
[x] Smoke tested
[x] Unit tests added
[x] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
This is the first step to enabling whylogs dataset profile visualization in flytedeck and enabling constraints. Viz will be hooked up through flytedeck and it will allow users to visualize the data in that workflow. Constraints are a way to specify properties that should hold in the data and conditionally fail the workflow otherwise.
Tracking Issue

Follow-up issue
We're in the process of releasing our 1.0.0 right now and some features (constraints in particular) are missing from our release candidate. I need that to exist before I can add the right example. I'll also have to update the dependency in setup.py.

Superseded by https://github.com/flyteorg/flytekit/pull/1100.