[iOS] Disallow user to enter spaces in TextInput.

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
React Native Environment Info:
System:
OS: macOS High Sierra 10.13.6
CPU: x64 Intel(R) Core(TM) i5-4308U CPU @ 2.80GHz
Memory: 102.42 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 8.11.4 - ~/.nvm/versions/node/v8.11.4/bin/node
Yarn: 1.9.4 - /opt/local/bin/yarn
npm: 5.6.0 - ~/.nvm/versions/node/v8.11.4/bin/npm
SDKs:
iOS SDK:
Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
Android SDK:
Build Tools: 23.0.1, 25.0.2, 26.0.2, 27.0.3, 28.0.2
API Levels: 23, 24, 25, 26, 28
IDEs:
Android Studio: 3.1 AI-173.4907809
Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
npmPackages:
@types/react: ^16.4.6 => 16.4.6
@types/react-native: ^0.56.3 => 0.56.4
react: 16.4.1 => 16.4.1
react-native: 0.56.0 => 0.56.0
Description
I'm trying to trim user input in TextInput field. I've tried to just use JS trim function from String.prototype but had to replace it with .replace(/\s/g, ''). The reason is that when I open my application on iOS simulator I'm experiencing behaviour when user input is gets trimmed, but it's not reflected on UI. I'm still able to type as mush spaces as I want.
Reproducible Demo
Code looks something like the following:
<TextInput
  ...
  value={this.state.myString}
  onChangeText={this.updateInput.bind(this)}
/>

And updateInput is represented as:
updateInput(newString) {
  this.setState({ myString: newString.trim() });
}

I've recorded short video of described behaviour. It's not quite good as I expected but it's possible to get the idea of the issue. I'm sorry for that. If needed I'll try to set more examples and record better frames.
Link: https://streamable.com/dzl3c

Thank you! @zibs

There was a bug (#18874) in RN 0.56 that prevent controlled TextInput to work properly. It was fixed in RN 0.57.
It was:


Changed the color of the message button on hover

Color of the message button looks better no hover

Share the screenshot of the card after the change you have made. And contribution of new template is preferred.

New stats card component


All tests fail when -DOQS_KEM_ENCODERS=ON

Describe the bug
All tests fail when I add -DOQS_KEM_ENCODERS=ON to the CMake params.
To Reproduce
Steps to reproduce the behavior:

Clone the repo.
Configure with cmake -DCMAKE_BUILD_TYPE=Debug -DOQS_KEM_ENCODERS=ON -DOPENSSL_ROOT_DIR="/opt/local/libexec/openssl3" -DCMAKE_C_FLAGS="$CFLAGS -g -I/opt/local/include -L/opt/local/lib" -DCMAKE_VERBOSE_MAKEFILE:BOOL=True -S . -B _build 2>&1 | tee -a build-out.txt
cmake build
scripts/runtests.sh
See error

External interop tests commencing
Using Web proxy "xxxxxxxxxxxxxxx"
 Google:
  x25519_kyber768 @ oqsprovider
  X25519MLKEM768 @ oqsprovider
Test project /Users/ur20980/src/oqs-provider/_build
    Start 1: oqs_signatures
1/6 Test #1: oqs_signatures ...................Subprocess aborted***Exception:   0.01 sec
    Start 2: oqs_kems
2/6 Test #2: oqs_kems .........................Subprocess aborted***Exception:   0.01 sec
    Start 3: oqs_groups
3/6 Test #3: oqs_groups .......................Subprocess aborted***Exception:   0.01 sec
    Start 4: oqs_tlssig
4/6 Test #4: oqs_tlssig .......................Subprocess aborted***Exception:   0.01 sec
    Start 5: oqs_endecode
5/6 Test #5: oqs_endecode .....................Subprocess aborted***Exception:   0.01 sec
    Start 6: oqs_evp_pkey_params
6/6 Test #6: oqs_evp_pkey_params ..............Subprocess aborted***Exception:   0.01 sec

0% tests passed, 6 tests failed out of 6

Expected behavior
External interop tests commencing
Using Web proxy "xxxxxxxxxxxxxxx"
 Google:
  x25519_kyber768 @ oqsprovider
  X25519MLKEM768 @ oqsprovider
Test project /Users/ur20980/src/oqs-provider/_build
    Start 1: oqs_signatures
1/6 Test #1: oqs_signatures ...................   Passed    3.61 sec
    Start 2: oqs_kems
2/6 Test #2: oqs_kems .........................   Passed    0.25 sec
    Start 3: oqs_groups
3/6 Test #3: oqs_groups .......................   Passed    0.37 sec
    Start 4: oqs_tlssig
4/6 Test #4: oqs_tlssig .......................   Passed  120.36 sec
    Start 5: oqs_endecode
5/6 Test #5: oqs_endecode .....................   Passed    9.03 sec
    Start 6: oqs_evp_pkey_params
6/6 Test #6: oqs_evp_pkey_params ..............   Passed    0.70 sec

100% tests passed, 0 tests failed out of 6

Total Test time (real) = 136.54 sec

Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS: MacOS Sonoma 14.7.1
OpenSSL version 3.4.0 22 Oct 2024 (Library: OpenSSL 3.4.0 22 Oct 2024)
oqsprovider 0.7.1-dev

Additional context
Crashes are:
Process:               oqs_test_endecode [26776]
Path:                  /Users/USER/*/oqs_test_endecode
Identifier:            oqs_test_endecode
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ctest [26771]
Responsible:           Terminal [4859]
User ID:               0

Date/Time:             2024-12-10 10:52:17.4068 -0500
OS Version:            macOS 14.7.1 (23H222)
Report Version:        12
Bridge OS Version:     9.1 (22P1072)
Anonymous UUID:        BD844EB9-9C6F-867E-78EB-1ACDA55970A0

Time Awake Since Boot: 390000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process:   oqs_test_endecode [26776]

Application Specific Information:
abort() called

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	    0x7ff812ee7d96 __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff812f20ebd pthread_kill + 262
2   libsystem_c.dylib             	    0x7ff812e46a79 abort + 126
3   libcrypto.3.dylib             	       0x1072ab81a OPENSSL_die + 26 (cryptlib.c:260)
4   oqs_test_endecode             	       0x10655cafb load_oqs_provider + 123 (test_common.c:55)
5   oqs_test_endecode             	       0x10655c06d main + 77 (oqs_test_endecode.c:255)
6   dyld                          	    0x7ff812b95345 start + 1909

and
Process:               oqs_test_kems [26773]
Path:                  /Users/USER/*/oqs_test_kems
Identifier:            oqs_test_kems
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ctest [26771]
Responsible:           Terminal [4859]
User ID:               0

Date/Time:             2024-12-10 10:52:17.3092 -0500
OS Version:            macOS 14.7.1 (23H222)
Report Version:        12
Bridge OS Version:     9.1 (22P1072)
Anonymous UUID:        BD844EB9-9C6F-867E-78EB-1ACDA55970A0

Time Awake Since Boot: 390000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process:   oqs_test_kems [26773]

Application Specific Information:
abort() called

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	    0x7ff812ee7d96 __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff812f20ebd pthread_kill + 262
2   libsystem_c.dylib             	    0x7ff812e46a79 abort + 126
3   libcrypto.3.dylib             	       0x1078ab81a OPENSSL_die + 26 (cryptlib.c:260)
4   oqs_test_kems                 	       0x106b58cfb load_oqs_provider + 123 (test_common.c:55)
5   oqs_test_kems                 	       0x106b583f4 main + 84 (oqs_test_kems.c:89)
6   dyld                          	    0x7ff812b95345 start + 1909

Without -DOQS_KEM_ENCODERS=ON all the tests execute and complete successfully.
Update
Switching from Xcode-16.1 Clang to Macports-installed Clang seemed to provide a workaround:
Test project /Users/ur20980/src/oqs-provider/_build
    Start 1: oqs_signatures
1/6 Test #1: oqs_signatures ...................   Passed    3.71 sec
    Start 2: oqs_kems
2/6 Test #2: oqs_kems .........................   Passed    0.31 sec
    Start 3: oqs_groups
3/6 Test #3: oqs_groups .......................   Passed    0.44 sec
    Start 4: oqs_tlssig
4/6 Test #4: oqs_tlssig .......................   Passed  218.33 sec
    Start 5: oqs_endecode
5/6 Test #5: oqs_endecode .....................   Passed   10.22 sec
    Start 6: oqs_evp_pkey_params
6/6 Test #6: oqs_evp_pkey_params ..............   Passed    1.25 sec

100% tests passed, 0 tests failed out of 6

Total Test time (real) = 235.79 sec

Hmm, we have a test for OQS_KEM_ENCODERS=ON in CI and it passes.

Switching from Xcode-16.1 Clang to Macports-installed Clang seemed to provide a workaround:

That seems to imply the choice of Clang origin on MacOS triggers this problem and you have found a sensible workaround. IMO that does not warrant (make appear prudent?) a change to oqsprovider.
Reminder: oqsprovider has no "guaranteed supported platforms" (no community activity on https://github.com/open-quantum-safe/oqs-provider/issues/293), so this does not look like a bug in my eyes and I'll move this to discussion for others to find this workaround as/if needed (unless someone is willing to work on/for supporting MacOS-origin Xcode-16.1 Clang and (documenting that in) https://github.com/open-quantum-safe/oqs-provider/issues/293 (?)).


ROX-20236: Set release Dockerfile label to some dummy value

Description
Per title.
Checklist

[ ] Investigated and inspected CI test results

These won't be done:

[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change

[ ] Pulled all 6 images and checked release label is there and set to 1.

Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/retest


Autocomplete, tabIndex is not passed on input

NextUI Version
lastest
Describe the bug
Hello everyone !
I love using this lib, thank you for the work !
I 'm facing an (probable) issue on autocomplete :
The tabIndex props seems to not be passed on the input item :
<Autocomplete
      size="sm"
      {...value}
     ... other props
      inputProps={{
        classNames: {
          inputWrapper: "border ....",
          innerWrapper: "justify-b....",
          input: "text-neutra...."
        },

        tabindex: tabIndex.  <---- here the tabIndex, tryed with tabIndex, and passing number or string
      }}
      listboxProps={{
          ....
      }}
      >
      {(item) => <AutocompleteItem aria-label='brand auto-complete item' key={item.id}>{item.name}</AutocompleteItem>}

        </Autocomplete>

I tried to pass the tabIndex props to autocomplete node but not working too.
The tabIndex props is not passed when i inspect the DOM. but this attribute work on Select and Inputs ...
Am I doing something wrong ? or bug ?
Thanks in advance for your help
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
create an autocomplete and pass tabIndex to inputProps
Expected behavior
expected to see tabIndex in input node
Screenshots or Videos
No response
Operating System Version
macOS
Browser
Chrome

@Fjohn666 Thanks for reporting the issue! Yes, I also could create the same bug with your clear instructions! I'll take a look at this issue 👍


Use options builder pattern for command constructors

Can we follow up and replace this kind of stuff (here and elsewhere) with the options builder pattern? The default should be used if the option isn't explicitly set. You shouldn't have to explicitly set it if it's a default 😄
e.g.
NewWriteAuthorizationModelCommand(datastore, WithLogger(logger), WithAuthorizationModelSizeInBytes(2048)) // if non-defaults are desired, otherwise

NewWriteAuthorizationModelCommand(datastore)

Originally posted by @jon-whit in https://github.com/openfga/openfga/pull/1036#discussion_r1344851323

Hey, I would be happy to contribute to this enhancement.
May I work on it?

@ilaleksin sure!


Connection stucks in second phase of a connect request

Ever since I started using OpenDTU, I have been troubled by a annoying reconnect problem, that I found described on several forums.
I've analyzed and corrected it in my temp branch of async-mqtt-client in the module MqttClient.cpp used by OpenDTU.
Regarding the cause:
OpenDTU initiates a connect request via an external mqtt client software to the MQTT server (e.g., ioBroker). It expects either a successful response via onMqttConnect-Callback (_onConnectCallback) or, through onMqttDisconnect-Callback (_onDisconnectCallback), an indication that the connection was interrupted or the connection attempt failed. In the case of an onMqttDisconnect call, a new attempt to connect is initiated by OpenDTU via mqtt client. If the call to onMqttDisconnect is absent, no reconnect occurs.
The problem now, however, is that the mqtt client code seems to has a bug in the connection setup. Under certain circumstances, the method MqttClient::loop() may stuck in the second phase of the connection setup if the mqtt server e.g. ioBroker allows a socket connect but unfortunately does not send back a connect-acknowledge packet in situation like server shutdown or restart.
The faulty code in MqttClient.cpp:
void MqttClient::loop() {
  switch (_state) {
    case State::connectingTcp1:
      ...
      ...
      if (_useIp ? _transport->connect(_ip, _port) : _transport->connect(_host, _port)) {
        _setState(State::connectingTcp2);   <---- connection successful; set _state to connectingTcp2
      } else {
        _setState(State::disconnectingTcp1);
        _disconnectReason = DisconnectReason::TCP_DISCONNECTED;
        break;
      }
      // Falling through to speed up connecting on blocking transport 'connect' implementations
      [[fallthrough]];
    case State::connectingTcp2:
      if (_transport->connected()) {    <---- connected is false until the ioBroker sends a connect-acknowledge-packet
        _parser.reset();
        _setState(State::connectingMqtt);  <---- ioBroker does not send an acknowledge, the _state will never set to next step connectingMqtt
      }
      break;

Here are my modifications:

void MqttClient::loop() {
  switch (_state) {
    case State::disconnected:
      #if defined(ARDUINO_ARCH_ESP32)
      if (_useInternalTask == espMqttClientTypes::UseInternalTask::YES) {
        vTaskSuspend(_taskHandle);
      }
      #endif
      break;
    case State::connectingTcp1:
      if (_useIp ? _transport->connect(_ip, _port) : _transport->connect(_host, _port)) {
        _setState(State::connectingTcp2);
        _lastClientActivity = millis();           // <---- set connect time
      } else {
        _setState(State::disconnectingTcp1);
        _disconnectReason = DisconnectReason::TCP_DISCONNECTED;
        break;
      }
      // Falling through to speed up connecting on blocking transport 'connect' implementations
      [[fallthrough]];
    case State::connectingTcp2:
      if (_transport->connected()) {
        _parser.reset();
        _lastClientActivity = _lastServerActivity = millis();
        _setState(State::connectingMqtt);
      }  else if (millis() - _lastClientActivity > _keepAlive) {  //  <---- new else block; use _keepAlive 15 seconds as timeout here
        _setState(State::disconnectingTcp1);                         // <---- force an disconnect sequence that calls onMqttDisconnect which starts a new connect request
        _disconnectReason = DisconnectReason::TCP_DISCONNECTED;
      }
      break;

Regards!

if (_transport->connected()) {    <---- connected is false until the ioBroker sends a connect-acknowledge-packet
This checks the TCP connection status, not the MQTT connection. Since you're falling through from State::connectingTcp1 this check should be redundant in case of the non-async version. The async version keeps checking until it can move on.
You are using the async version?
Do you happen to have a debug log?
PS AsyncTCP has a nasty limitation. It it not possible to set the connection timeout. So if the broker is not responding, you will have to sit out the hardcoded timeout which is quite long.

Yes, I know it does not depend on the MQTT connection. It is the connected status of the specific implementation of the communication channel (espMqttClientInternals::Transport* _transport).
The issue is independent of the case statement's fall-through. As long as the method _transport->connected() returns FALSE, the case State::connectingTcp1 is repeatedly called over the loop() method, and it cannot exit the state since connected() continuously returns FALSE.
Example for the code of ARDUINO_ARCH_ESP32 (WiFi), _transport->connected():
arduinoespresif32 - WiFiClient.cpp:
uint8_t WiFiClient::connected()
{
if (_connected) {
uint8_t dummy;
int res = recv(fd(), &dummy, 0, MSG_DONTWAIT);
// avoid unused var warning by gcc
(void)res;
// recv only sets errno if res is <= 0
if (res <= 0){
switch (errno) {
case EWOULDBLOCK:
case ENOENT: //caused by vfs
_connected = true;
break;
case ENOTCONN:
case EPIPE:
case ECONNRESET:
case ECONNREFUSED:
case ECONNABORTED:
_connected = false;
log_d("Disconnected: RES: %d, ERR: %d", res, errno);
break;
default:
log_i("Unexpected: RES: %d, ERR: %d", res, errno);
_connected = true;
break;
}
} else {
_connected = true;
}
}
return _connected;
}
If the socket-connection runs into problems between the socket connect and the subsequent call to connected(), the call to recv() will always call the cases where _connected is set to false.
That means MqttClient::loop() keeps “looping” over the case State::connectingTcp1.
Regards!

yes, I am using the regular version.

yes, I am using the regular version.

But please keep in mind, that OpenDTU uses the AsyncTCP approach

Maybe this works too: (brainstorming here, completely untested)
    case State::connectingTcp2:
      if (_transport->connected()) {
        _parser.reset();
        _lastClientActivity = _lastServerActivity = millis();
        _setState(State::connectingMqtt);
      }  else if (_client->disconnected()) {  // sync: implemented as "not connected"; async: depending on state of pcb in underlying lib
        _setState(State::disconnectingTcp1);
        _disconnectReason = DisconnectReason::TCP_DISCONNECTED;
      }
      break;

There is no point in having a timeout here. For the sync version, the timeout is already in the connect function. Timeout for async is handled in the underlying lib.

Hi! I guess you mean _transport->disconnected() instead of _client->disconnected()

For a swift response, I've integrated your code changes into my OpenDTU setup and have started and killed my ioBroker Docker many times. So far, your solution seems to be working as well. I'll monitor the solution for a while.
However, a combination of both approaches, disconnected() plus a timeout query, could also be a solution to ensure safety.
    case State::connectingTcp1:       if (_useIp ? _transport->connect(_ip, _port) : _transport->connect(_host, _port)) {         _setState(State::connectingTcp2);         _lastClientActivity = millis();       } else {         _setState(State::disconnectingTcp1);         _disconnectReason = DisconnectReason::TCP_DISCONNECTED;         break;       }       // Falling through to speed up connecting on blocking transport 'connect' implementations       [[fallthrough]];     case State::connectingTcp2:       if (_transport->connected()) {         _parser.reset();         _lastClientActivity = _lastServerActivity = millis();         _setState(State::connectingMqtt);       } else if ((millis() - _lastClientActivity > _keepAlive) && (_transport->disconnected())) {         _setState(State::disconnectingTcp1);         _disconnectReason = DisconnectReason::TCP_DISCONNECTED;       }       break;

"Mind that in the Transport implementation client.disconnected() is implemented as !client.connected(). simple as that."
I hope I’m not misunderstanding your concerns. Indeed, that’s why I suggested adding an extra time period before disconnected() is triggered. There’s an AND operation in the else-if clause, meaning the time must elapse before disconnected() is called/relevant. In other words, both conditions must be true before the disconnection process starts. This approach makes it safer with such straightforward connected/disconnected implementations.
Regards!

It will work, but the extra timeout is not needed. It will just take longer to move on in case of a failed connection.
sync version:
transport->connect is a blocking call with a timeout. If the result is true, the transport->connected() is true so we fall through. all is well.
If in between these states connected() would become false, disconnected() will return true. There is no automatic reconnect so once the connection is down, it stays down. Also, in case of a half-open connection, it will get detected in the next state.
async version:
no blocking calls and anything can happen between calls. we rely on the callbacks of the async lib to update the state of the FSM. The transport can be "not connected" and "not disconnecting" at the same time (eg. "busy connecting"). Adding a timeout here might cause strange behaviour and is a nightmare to test thouroughly.

The behavior heavily depends on the implementation of the Transport interface class. In the Async version, future code changes could lead to a situation where connected() is equivalent to !disconnected(), and the case statement, through fall-through, might immediately proceed to disconnect. Even if it’s a brief moment that stabilizes in a few milliseconds, a timeout would be beneficial. The timeout isn't problematic, especially since we now face a situation where it could loop indefinitely.
From my personal experience, I’ve learned that one should not rely on the behavior of interface methods unless they are explicitly described.
But I don't mean to interfere. It’s entirely up to you whether and how you want to address this issue.
By the way, OpenDTU runs stable with the current modifications until now.

Hello,
For your information, OpenDTU runs stable with the current modifications until now. It always reconnects to ioBroker without any problem.
Regards!


[Backend] Allow layout propagation through TransOp.

[NVGPU] Allow layout propagation through TransOp.
This is a revival of https://github.com/openai/triton/pull/3097, which I now
realize I need for some int4 matmul work I'm doing.
Previously this caused performance problems / running out of shmem on A100, but
it seems that https://github.com/openai/triton/pull/3261 (or perhaps something
else) fixed it.  This now has no performance delta on our internal performance
tests on A100 or H100.
PR chain

👉 #3316 👈 YOU ARE HERE

can we add a simple lit test that does forward propagation:
 %c = convert...
  %t = trans
  tt.return %tt

that should move the convert after

Absolutely, I intended to add a test but wanted to check that the tests were passing first.  Looks like they are, so yay.  :)

Added a test; phal, Thomas.

Thanks, Thomas.  PHAL.


binary available?

I'm on a slow connection in peru, so installing Xcode just so I can build this is tricky. is there a binary that can be shared, downloaded?

Here you go https://github.com/0xbb/gpu-switch/releases/tag/macos-binaries


ATS 8.0.3 traffic_top crashed when traffic_server is not running

[root@localhost ats]# bin/traffic_top
Error getting stat: proxy.process.http.100_responses when calling TSRecordGetInt() failed: file "traffic_top/stats.h", line 302
Aborted
OS: CentOS 7.4
GCC: devtoolset-7-gcc-c++-7.3.1-5.15.el7.x86_64
./configure --prefix=/opt/ats --enable-debug --disable-tests --enable-experimental-plugins --enable-example-plugins --with-ncurses

#0  0x00007f2a23aab2c7 in raise () from /lib64/libc.so.6
#1  0x00007f2a23aac9b8 in abort () from /lib64/libc.so.6
#2  0x00000000004295a7 in Stats::getStats (this=0x7fff6cbd5ab0) at traffic_top/stats.h:303
#3  0x00000000004256e6 in main (argc=1, argv=0x7fff6cbd62f8) at traffic_top/traffic_top.cc:441
(gdb)

is trafficserver fully started? I can reproduce this situation when I try to run traffic_top before traffic_server is accepting traffic.

@randall Yes，you are right，traffic_server can not start. Thanks a lot.
The traffic_server was built with user root. This is not allowed.
[root@node1 ts]# ps -ef |grep traffic
root     25683     1  0 10:37 pts/1    00:00:00 /opt/ts/bin/traffic_manager --bind_stdout /opt/ts/var/log/trafficserver/traffic.out --bind_stderr /opt/ts/var/log/trafficserver/traffic.out
root     25866 13932  0 10:37 pts/1    00:00:00 grep --color=auto traffic

Since traffic_cop is EOLifed, unless this is a common problem (which I don't think it is), we shouldn't spend time fixing this. Closing for now, but if you have a fix, please make a PR against the 8.0.x branch.

you can check if the fd  of the trafficserver process leaked,  that is the reason why all the process can't connect the trafficserver process to get stat


Adding .babelrc by-passes Babel entirely

What I did:

npm i -D @rescripts/cli @rescripts/rescript-env
Update package.json's scripts to use rescripts instead of react-scripts
Add .rescriptsrc (containing: module.exports = [ "env"];)
Add my own custom .babelrc

This is happening to me with<EMAIL_ADDRESS>as well as<EMAIL_ADDRESS>A look at my package.json reveals:
"devDependencies": {
    "@rescripts/cli": "0.0.10",
    "@rescripts/rescript-env": "0.0.10"
  }

Expected:
Things to go as smoothly as they sometimes go in the occasional dream... ⭐⭐⭐⭐
Currently:
It appears that Babel has been entirely bypassed; It does not recognize jsx anymore...
The contents of the .babelrc file do not matter at all. No matter if my own customized version, if empty or if you copy some basic templates from the web, the result is always the same: babel gets bypassed entirely, like so:

Failed to compile.
./src/index.js
SyntaxError: /my-code/src/index.js: Unexpected token (18:16)
16 |
17 |
18 | ReactDOM.render(<Loading centered />, document.getElementById('root'));
     |                                 ^

The Twist
Things are working fine (except for legacy decorators, i.e. the CRA default babel config kicks in) if I remove my .babelrc file.

Not sure what is causing it, but after getting rid of rescripts and ejecting, I still get the same problem - so probably not related to rescripts. Closing this. - Sorry for wasting your time!

Hey @Domiii, I am having the same problem. Did you ever figure out a solution?

@Domiii @mariaines that's because Rescripts doesn't merge with the pre-existing Babel config (the CRA preset). If you want this config (which includes the JSX transpilation), you'll need to specify the config manually:
.babelrc
{
  "presets": [
    "react-app"
  ]
}

Ah, great, thank you for the quick help @harrysolovay !


How to use database connection pool or redis connection pool in custom middleware

I want to get the DbConn of sea_orm in the custom middleware, how to deal with it

https://docs.rs/axum/latest/axum/middleware/index.html#accessing-state-in-middleware
As long as you can access state from the middleware, you can get the registered component through state.app.getComponent::<C>().
In spring-web, AppState is a reference to an App.

If you want to get AppState, it seems that you can only get it by implementing a plug-in？ I am still learning and don’t understand it very well.


Lançando versao 1.4.14

Atualizando dependencias
Corrigindo modelo de Mercado
Removendo Sphinx

Coverage increased (+1.7%) to 95.484% when pulling b22c933f97016260632cb5288e80dffa3ed28802 on dev into c2f60ed9d3aeeb868e56e12dd1ef3cb36d93a6ba on master.

Coverage increased (+1.7%) to 95.484% when pulling b22c933f97016260632cb5288e80dffa3ed28802 on dev into c2f60ed9d3aeeb868e56e12dd1ef3cb36d93a6ba on master.

Coverage increased (+1.7%) to 95.484% when pulling b22c933f97016260632cb5288e80dffa3ed28802 on dev into c2f60ed9d3aeeb868e56e12dd1ef3cb36d93a6ba on master.

Coverage increased (+1.7%) to 95.484% when pulling b22c933f97016260632cb5288e80dffa3ed28802 on dev into c2f60ed9d3aeeb868e56e12dd1ef3cb36d93a6ba on master.


Oracle visitor needs two more add_bind argument fix

Refer https://github.com/rails/arel/commit/53521a9e39b9d8af4165d7703c36dc905f1f8f67
This pull request addresses this failure at Oracle enhanced unit test.
$ bundle exec rspec ./spec/active_record/connection_adapters/oracle_enhanced_adapter_spec.rb:628
==> Loading config from ENV or use default
==> Running specs with MRI version 2.5.0
/home/yahonda/git/rails/activesupport/lib/active_support/core_ext/hash/keys.rb:14: warning: method redefined; discarding old transform_keys
/home/yahonda/git/rails/activesupport/lib/active_support/core_ext/hash/keys.rb:25: warning: method redefined; discarding old transform_keys!
==> Effective ActiveRecord version 5.2.0.alpha
Run options: include {:locations=>{"./spec/active_record/connection_adapters/oracle_enhanced_adapter_spec.rb"=>[628]}}
F

Failures:

  1) OracleEnhancedAdapter using offset and limit should return the records starting from offset n with offset(n)
     Failure/Error: type_casted_binds = type_casted_binds(binds)

     NoMethodError:
       undefined method `value_for_database' for #<Arel::Nodes::BindParam:0x000055852a3e64d0>
     # /home/yahonda/git/rails/activerecord/lib/active_record/connection_adapters/abstract/quoting.rb:161:in `block in type_casted_binds'
     # /home/yahonda/git/rails/activerecord/lib/active_record/connection_adapters/abstract/quoting.rb:161:in `map'
     # /home/yahonda/git/rails/activerecord/lib/active_record/connection_adapters/abstract/quoting.rb:161:in `type_casted_binds'
     # ./lib/active_record/connection_adapters/oracle_enhanced/database_statements.rb:22:in `exec_query'
     # /home/yahonda/git/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:427:in `select_prepared'
     # /home/yahonda/git/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:49:in `select_all'
     # /home/yahonda/git/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:99:in `select_all'
     # /home/yahonda/git/rails/activerecord/lib/active_record/querying.rb:41:in `find_by_sql'
     # /home/yahonda/git/rails/activerecord/lib/active_record/relation.rb:664:in `block in exec_queries'
     # /home/yahonda/git/rails/activerecord/lib/active_record/relation.rb:687:in `skip_query_cache_if_necessary'
     # /home/yahonda/git/rails/activerecord/lib/active_record/relation.rb:663:in `exec_queries'
     # /home/yahonda/git/rails/activerecord/lib/active_record/relation.rb:542:in `load'
     # /home/yahonda/git/rails/activerecord/lib/active_record/relation.rb:251:in `records'
     # /home/yahonda/git/rails/activerecord/lib/active_record/relation.rb:247:in `to_a'
     # /home/yahonda/git/rails/activerecord/lib/active_record/relation/finder_methods.rb:541:in `find_nth_with_limit'
     # /home/yahonda/git/rails/activerecord/lib/active_record/relation/finder_methods.rb:530:in `find_nth'
     # /home/yahonda/git/rails/activerecord/lib/active_record/relation/finder_methods.rb:124:in `first'
     # ./spec/active_record/connection_adapters/oracle_enhanced_adapter_spec.rb:630:in `block (3 levels) in <top (required)>'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/example.rb:254:in `instance_exec'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/example.rb:254:in `block in run'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/example.rb:500:in `block in with_around_and_singleton_context_hooks'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/example.rb:457:in `block in with_around_example_hooks'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/hooks.rb:464:in `block in run'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/hooks.rb:602:in `run_around_example_hooks_for'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/hooks.rb:464:in `run'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/example.rb:457:in `with_around_example_hooks'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/example.rb:500:in `with_around_and_singleton_context_hooks'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/example.rb:251:in `run'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/example_group.rb:627:in `block in run_examples'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/example_group.rb:623:in `map'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/example_group.rb:623:in `run_examples'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/example_group.rb:589:in `run'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/example_group.rb:590:in `block in run'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/example_group.rb:590:in `map'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/example_group.rb:590:in `run'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/runner.rb:118:in `block (3 levels) in run_specs'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/runner.rb:118:in `map'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/runner.rb:118:in `block (2 levels) in run_specs'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/configuration.rb:1894:in `with_suite_hooks'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/runner.rb:113:in `block in run_specs'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/reporter.rb:79:in `report'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/runner.rb:112:in `run_specs'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/runner.rb:87:in `run'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/runner.rb:71:in `run'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/lib/rspec/core/runner.rb:45:in `invoke'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/rspec-core-3.6.0/exe/rspec:4:in `<top (required)>'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/bin/rspec:23:in `load'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/bin/rspec:23:in `<top (required)>'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/bundler-1.15.3/lib/bundler/cli/exec.rb:74:in `load'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/bundler-1.15.3/lib/bundler/cli/exec.rb:74:in `kernel_load'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/bundler-1.15.3/lib/bundler/cli/exec.rb:27:in `run'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/bundler-1.15.3/lib/bundler/cli.rb:365:in `exec'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/bundler-1.15.3/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/bundler-1.15.3/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/bundler-1.15.3/lib/bundler/vendor/thor/lib/thor.rb:369:in `dispatch'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/bundler-1.15.3/lib/bundler/cli.rb:22:in `dispatch'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/bundler-1.15.3/lib/bundler/vendor/thor/lib/thor/base.rb:444:in `start'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/bundler-1.15.3/lib/bundler/cli.rb:13:in `start'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/bundler-1.15.3/exe/bundle:30:in `block in <top (required)>'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/bundler-1.15.3/lib/bundler/friendly_errors.rb:121:in `with_friendly_errors'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/lib/ruby/gems/2.5.0/gems/bundler-1.15.3/exe/bundle:22:in `<top (required)>'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/bin/bundle:23:in `load'
     # /home/yahonda/.rbenv/versions/2.5.0-dev/bin/bundle:23:in `<main>'

Finished in 0.42775 seconds (files took 0.77656 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spec/active_record/connection_adapters/oracle_enhanced_adapter_spec.rb:628 # OracleEnhancedAdapter using offset and limit should return the records starting from offset n with offset(n)

Coverage report generated for RSpec to /home/yahonda/git/oracle-enhanced/coverage. 1027 / 2229 LOC (46.07%) covered.
$

Updated pull request to reflect reviews.
Note: this method needs to bind offset value twice. The bind value name for the second offset changed from :b1 to :b3 by using visitor pattern here and confirmed the first offset :b1 and the second offset :b3 have the same value.

Current behavior with this pull request

D, [2017-07-25T22:16:51.986248 #27602] DEBUG -- :    Load (4.1ms)
              SELECT * FROM (
                SELECT raw_sql_.*, rownum raw_rnum_
                FROM (SELECT  "TEST_EMPLOYEES".* FROM "TEST_EMPLOYEES" ORDER BY "TEST_EMPLOYEES"."SORT_ORDER" ASC ) raw_sql_ WHERE rownum <= (:a1 + :a2) ) WHERE raw_rnum_ > :a3  [["OFFSET", 0], ["LIMIT", 1], ["OFFSET", 0]]
D, [2017-07-25T22:16:51.989567 #27602] DEBUG -- :    Load (1.0ms)
              SELECT * FROM (
                SELECT raw_sql_.*, rownum raw_rnum_
                FROM (SELECT  "TEST_EMPLOYEES".* FROM "TEST_EMPLOYEES" ORDER BY "TEST_EMPLOYEES"."SORT_ORDER" ASC ) raw_sql_ WHERE rownum <= (:a1 + :a2) ) WHERE raw_rnum_ > :a3  [["OFFSET", 1], ["LIMIT", 1], ["OFFSET", 1]]
D, [2017-07-25T22:16:51.991870 #27602] DEBUG -- :    Load (0.6ms)
              SELECT * FROM (
                SELECT raw_sql_.*, rownum raw_rnum_
                FROM (SELECT  "TEST_EMPLOYEES".* FROM "TEST_EMPLOYEES" ORDER BY "TEST_EMPLOYEES"."SORT_ORDER" ASC ) raw_sql_ WHERE rownum <= (:a1 + :a2) ) WHERE raw_rnum_ > :a3  [["OFFSET", 4], ["LIMIT", 1], ["OFFSET", 4]]

Previous behavior

D, [2017-07-25T22:18:01.061554 #27751] DEBUG -- :    Load (4.8ms)
              SELECT * FROM (
                SELECT raw_sql_.*, rownum raw_rnum_
                FROM (SELECT  "TEST_EMPLOYEES".* FROM "TEST_EMPLOYEES" ORDER BY "TEST_EMPLOYEES"."SORT_ORDER" ASC ) raw_sql_ WHERE rownum <= (:a1 + :a2) ) WHERE raw_rnum_ > :a1  [["OFFSET", 0], ["LIMIT", 1]]
D, [2017-07-25T22:18:01.065624 #27751] DEBUG -- :    Load (1.1ms)
              SELECT * FROM (
                SELECT raw_sql_.*, rownum raw_rnum_
                FROM (SELECT  "TEST_EMPLOYEES".* FROM "TEST_EMPLOYEES" ORDER BY "TEST_EMPLOYEES"."SORT_ORDER" ASC ) raw_sql_ WHERE rownum <= (:a1 + :a2) ) WHERE raw_rnum_ > :a1  [["OFFSET", 1], ["LIMIT", 1]]
D, [2017-07-25T22:18:01.068899 #27751] DEBUG -- :    Load (1.0ms)
              SELECT * FROM (
                SELECT raw_sql_.*, rownum raw_rnum_
                FROM (SELECT  "TEST_EMPLOYEES".* FROM "TEST_EMPLOYEES" ORDER BY "TEST_EMPLOYEES"."SORT_ORDER" ASC ) raw_sql_ WHERE rownum <= (:a1 + :a2) ) WHERE raw_rnum_ > :a1  [["OFFSET", 4], ["LIMIT", 1]]

Ah I see. In that case your original fix was the right thing to do.

Pushed the original fix again.

I've found the original fix did not resolve this error when tested with JRuby and JDBC driver
since bind value naming convention differences between OCI(for CRuby) and JDBC(for JRuby).
       Java::JavaSql::SQLException: Missing IN or OUT parameter at index:: 3:

https://travis-ci.org/rsim/oracle-enhanced/jobs/257787629
Going back to visitor pattern again and it works with both CRuby and JRuby.

r? @sgrif


Problems shown in Problems pane for files in excluded folders

In user settings:
"files.exclude": {
	"**/.git": true,
	"**/.svn": true,
	"**/.hg": true,
	"**/CVS": true,
	"**/.DS_Store": true,
}

Make a javascript file in the .git folder of a workspace. Write some javascript and introduce a problem.
Expected: The problem doesn't show up in the Problems pane.
Actual: The problem is in the problems pane even though the .git folder is excluded.
Version 1.29.0-insiders commit 2b06dd1ca31 on Windows.
Found while testing: #62063

@alexr00 Did you enable exclude option in filter box?

Works great with that. Thanks!


Nuxt Bridge + vueuse/head - Cannot start nuxt:  Cannot find module 'nuxt'

Environment

Operating System: Linux
Node Version:     v16.16.0
Nuxt Version:     2.16.0-27616340.013f051b
Package Manager<EMAIL_ADDRESS>Builder:          webpack
User Config:      target, head, css, components, buildModules, build, bridge, serverHandlers, devServerHandlers
Runtime Modules:  -
Build Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>
Reproduction
Install https://github.com/piniajs/example-nuxt-bridge
Install npm install --save @vueuse/head
Set   bridge: { meta: true }
Describe the bug
Cannot start nuxt:  Cannot find module 'nuxt'
Additional context
After reinstall
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/vue
npm ERR!   peerOptional<EMAIL_ADDRESS>|| ^3.2.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/@vueuse/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer vue@">=3" from<EMAIL_ADDRESS>npm ERR!   node_modules/@vueuse/head
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR<EMAIL_ADDRESS>from the root project

Logs
No response

These are package management issues and can probably be addressed by using yarn or npm overrides. In general, however, I would advise against using the (experimental) @vueuse/head implementation on Bridge.

This reproduction uses 3.0.0-27621666.ee600b4 Can you try with a newer version of bridge? 3.0.0-27639120.e7a7f9b

These are package management issues and can probably be addressed by using yarn or npm overrides. In general, however, I would advise against using the (experimental) @vueuse/head implementation on Bridge.

notably that useAsyncData and useFetch composables are not available
with bridge no Directly calling an API Endpoint ?

This reproduction uses 3.0.0-27621666.ee600b4 version of nuxt-bridge. Can you try with a newer version of bridge? 3.0.0-27639120.e7a7f9b

how to do that?
in package.json is @nuxt/bridge": "npm:@nuxt/bridge-edge

This reproduction uses 3.0.0-27621666.ee600b4 version of nuxt-bridge. Can you try with a newer version of bridge? 3.0.0-27639120.e7a7f9b

how to do that? in package.json is @nuxt/bridge": "npm:@nuxt/bridge-edge

You can remove yarn.lock and run yarn install.

This reproduction uses 3.0.0-27621666.ee600b4 version of nuxt-bridge. Can you try with a newer version of bridge? 3.0.0-27639120.e7a7f9b

how to do that? in package.json is @nuxt/bridge": "npm:@nuxt/bridge-edge

You can remove yarn.lock and run yarn install.

I think i always do so. i use npm

This reproduction uses 3.0.0-27621666.ee600b4 version of nuxt-bridge. Can you try with a newer version of bridge? 3.0.0-27639120.e7a7f9b

how to do that? in package.json is @nuxt/bridge": "npm:@nuxt/bridge-edge

You can remove yarn.lock and run yarn install.

I think i always do so. i use npm

in that case you should remove package.lock and run npm install.

This reproduction uses 3.0.0-27621666.ee600b4 version of nuxt-bridge. Can you try with a newer version of bridge? 3.0.0-27639120.e7a7f9b

how to do that? in package.json is @nuxt/bridge": "npm:@nuxt/bridge-edge

You can remove yarn.lock and run yarn install.

I think i always do so. i use npm

in that case you should remove package.lock and run npm install.

i understand, and do that yesterday and today but that not help
{
  "name": "pinia-example-nuxt",
  "version": "1.0.0",
  "private": true,
  "license": "MIT",
  "scripts": {
    "dev": "nuxi dev",
    "build": "nuxi build",
    "start": "node .output/server/index.mjs",
    "generate": "nuxi generate"
  },
  "dependencies": {
    "@pinia/nuxt": "^0.3.1",
    "@vueuse/core": "^9.0.0",
     "@vueuse/head": "^0.7.7",
    "nuxt-edge": "latest",
    "pinia": "^2.0.17"
  },
  "devDependencies": {
    "@nuxt/bridge": "npm:@nuxt/bridge-edge",
    "@nuxt/types": "^2.15.8",
    "prettier": "^2.7.1"
  }
}

This reproduction uses 3.0.0-27621666.ee600b4 version of nuxt-bridge. Can you try with a newer version of bridge? 3.0.0-27639120.e7a7f9b

how to do that? in package.json is @nuxt/bridge": "npm:@nuxt/bridge-edge

You can remove yarn.lock and run yarn install.

with yarn work well

These are package management issues and can probably be addressed by using yarn or npm overrides. In general, however, I would advise against using the (experimental) @vueuse/head implementation on Bridge.

hmm interesting, the documentation gives useHead as an option. guess I'll stick with useNuxt2Meta then.

These are package management issues and can probably be addressed by using yarn or npm overrides. In general, however, I would advise against using the (experimental) @vueuse/head implementation on Bridge.

From what package to import useMeta?
Can you in example to indicate which function from which package are imported, and not  reley on auto import.
import { useMeta } from '@vueuse/head'

You import useHead from #head or #imports.

You import useHead from #head or #imports.

i not import it because after install it not start

I managed to get it to work by putting
  bridge: {
    meta: true,
  },

in my defineNuxtConfig and then installing @vueuse/head.
If I didn't install @vueuse/head then I was getting This dependency was not found:  * @vueuse/head in and @danielroe suggestion did not work. Maybe his suggestion was for nuxt3 rather than bridge, because doing his suggestion does work there.


WIP: MAID-1429

https://maidsafe.atlassian.net/browse/MAID-1429

r? @vinipsmaker
(maidsafe_highfive has picked a reviewer for you, use r? to override)


Add isort to CI

Motivation

Description

Add isort to CONTRIBUTING.md and add to CI tests
Alternatives (optional)

Leave as is. This may be useful if some of our examples are replicated to other repositories, such as Chainer, to keep both versions identical
Additional context (optional)

It looks like this was added in https://github.com/optuna/optuna-examples/pull/25. It's probably safe to close this issue

@jrbourbeau Thank you for letting us know about it!


Storing the row index inside the ReadCellValueResult struct

I think it would be good to have this value stored, so it's possible to work with the column index and row index inside the WithConverter extension method, giving the possibility to point it out the position of where the convertion failed inside the excel.

Hey buddy thanks for this!
I like this quite a lot as an idea actually.
I also think actually we should move the Sheet property into ReadCellValueResult as well.
Since I’m making breaking changes and bumping up the major version in #62, we could think about renaming ReadCellValueResult to ReadCellValueContext as that more accurately represents the meaning of the struct. We could also remove the ExcelSheet sheet and int columnIndex parameters from ICellValueReader. What do you think?
Also take a look at that PR. It’s aim to make it a lot easier to detect errors, handle them and know where they occurred.
it’s good to see that there’s demand for better exception handling. This will be something ima work on during lockdown 3 in U.K. :))

Hey buddy thanks for this!
I like this quite a lot as an idea actually.
I also think actually we should move the Sheet property into ReadCellValueResult as well.
Since I’m making breaking changes and bumping up the major version in #62, we could think about renaming ReadCellValueResult to ReadCellValueContext as that more accurately represents the meaning of the struct. We could also remove the ExcelSheet sheet and int columnIndex parameters from ICellValueReader. What do you think?
Also take a look at that PR. It’s aim to make it a lot easier to detect errors, handle them and know where they occurred.
it’s good to see that there’s demand for better exception handling. This will be something ima work on during lockdown 3 in U.K. :))

Also please let me know any problems/bugs/weird things you’ve encountered with the library and any feature requests - can work it out

Also please let me know any problems/bugs/weird things you’ve encountered with the library and any feature requests - can work it out

Looking at https://github.com/hughbe/excel-mapper/pull/62 it's just the thing I need. I can implement my own FallbackItem and getting the exception thrown, so it's possible to show the user the exact error and point it out the row and column index.
I don't thing these changes is necessary anymore.

Looking at https://github.com/hughbe/excel-mapper/pull/62 it's just the thing I need. I can implement my own FallbackItem and getting the exception thrown, so it's possible to show the user the exact error and point it out the row and column index.
I don't thing these changes is necessary anymore.

I've published https://www.nuget.org/packages/ExcelDataReader.Mapping/2.2.0
Do close this PR if you think it is no longer necessary!

I've published https://www.nuget.org/packages/ExcelDataReader.Mapping/2.2.0
Do close this PR if you think it is no longer necessary!

I'll close this now

I'll close this now


[BUG] ESCU - Prohibited Software On Endpoint - Rule

Rule ESCU - Prohibited Software On Endpoint - Rule fails to run with the following error:

Since this rule is deprecated, maybe we should remove it?

Thanks for opening this issue. We're already tracking this issue. Unfortunately, removing a detection is not possible at this time.

Noted Lou, thanks!


Retry Action for failed downloads.

The snackbars for "Download failed/couldn't refresh" or similar events should contain a "retry" action so user can retry easily and get improved experience.

@the-dagger, could you assign this to me? I'd like to contribute.

Hey @gogeta95 you can go ahead and work on this if you like.
Only the people belonging to an organization can be assigned to an issue. :)


Running c++ on vs code

c_cpp_properties.json
This issue is happening when i enter a input and try to run it is kept on running but not showing the output. It only runs hello world program. I even uninstalled, restarted but issue is not solved. Also, there is problem in the .vscode folder of c++.
Hope u help me resolve.

launch.json
settings.json
tasks.json
Above are generated automatically.
Below are something i added with the help of vscode tutorial..
c_cpp_properties.json
launch.json
settings.json

c_cpp_properties.json

I've also met this problem in my computer :(

Then did you solve this problem?
On Fri, 29 Mar, 2024, 7:51 am polaritus9801, @.***>
wrote:

I've also met this problem in my computer :(
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/208975#issuecomment-2026488940,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3F4PX6XZEWPLCX36DGP74TY2TFZRAVCNFSM6AAAAABFMG2ET2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRWGQ4DQOJUGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Please file this on the C++ debug extension

Sorry, I didn't understand
On Tue, 9 Apr, 2024, 3:34 am Rob Lourens, @.***> wrote:

Closed #208975 https://github.com/microsoft/vscode/issues/208975 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/208975#event-12398921506, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A3F4PX2F6RPPFMF6LZD6EXTY4MIARAVCNFSM6AAAAABFMG2ET2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGM4TQOJSGE2TANQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


models/slim download_and_convert_data.py, unicodeDecodeError

Windows 10 x64 build 1703
Anaconda 4.3.1 with Python 3.6.1 x64
Geforce GTX1080
Tensorflow-gpu 1.1.0

@mrry Did you run into UnicodeDecodeError problems when working on the Windows port? If so, this might be an easy question for you.

My guess is that the tf.gfile.FastGFile(filenames[i], "r") in the stack trace should really be tf.gfile.FastGFile(filenames[i], "rb"), because it seems to be barfing on a binary file, and Windows handles text and binary files differently.

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


[LOC] Back-Translation "regsvr32.exe 行います" → regsvr32.exe msxml.dll

https://docs.microsoft.com/ja-jp/windows/deployment/update/windows-update-resources

ドキュメントの詳細
⚠ このセクションを編集しないでください。 docs.microsoft.com で必須です ➟ GitHub の問題のリンク。

ID: 886426b5-8548-1cfc-ccd2-fd03e549c967
Version Independent ID: 599aea76-47e4-dccc-799c-2d8acf549546
Content: Windows Update - その他のリソース
Content Source: windows/deployment/update/windows-update-resources.md
Product: w10
Technology: windows
GitHub Login: @kaushika-msft
Microsoft Alias: elizapo

@officedocsbot assign @e0i
@officedocsbot assign @dongmicro
@officedocsbot add label localization

3567

@officedocsbot assign @MollyMalone

@officedocsbot unassign @MollyMalone
@officedocsbot assign @TinaMcN

@officedocsbot unassign @dongmicro

@hyoshioka0128 Good bug!  It seems to be an issue with the machine translation tool.  I logged a bug for the tool owners to investigate.

Hi, @TinaMcN. It has been updated, but not fixed.

Thank you.

After the merge of my PR on 2019-09-05 (September 5, 2019), commit https://github.com/MicrosoftDocs/windows-itpro-docs/commit/00ff5b9219391031ac3240c7eb0f806ee38c952e, this issue should be OK to close now that the entire list of regsvr32.exe commands are now part of the translated pages:
regsvr32.exe atl.dll
regsvr32.exe urlmon.dll
regsvr32.exe mshtml.dll
regsvr32.exe shdocvw.dll
regsvr32.exe browseui.dll
regsvr32.exe jscript.dll
regsvr32.exe vbscript.dll
regsvr32.exe scrrun.dll
regsvr32.exe msxml.dll
regsvr32.exe msxml3.dll
regsvr32.exe msxml6.dll
regsvr32.exe actxprxy.dll
regsvr32.exe softpub.dll
regsvr32.exe wintrust.dll
regsvr32.exe dssenh.dll
regsvr32.exe rsaenh.dll
regsvr32.exe gpkcsp.dll
regsvr32.exe sccbase.dll
regsvr32.exe slbcsp.dll
regsvr32.exe cryptdlg.dll
regsvr32.exe oleaut32.dll
regsvr32.exe ole32.dll
regsvr32.exe shell32.dll
regsvr32.exe initpki.dll
regsvr32.exe wuapi.dll
regsvr32.exe wuaueng.dll
regsvr32.exe wuaueng1.dll
regsvr32.exe wucltui.dll
regsvr32.exe wups.dll
regsvr32.exe wups2.dll
regsvr32.exe wuweb.dll
regsvr32.exe qmgr.dll
regsvr32.exe qmgrprxy.dll
regsvr32.exe wucltux.dll
regsvr32.exe muweb.dll
regsvr32.exe wuwebv.dll

This list is now clearly visible as a code block, both in the originating en-us page and the translated pages.

@illfated - Fixed.
Closed #3569
Thanks.


sdnoverlay + flannel should have extra EndpointPolicy in config

In order for flannel + sdnoverlay to work in overlay mode this extra endpoint policy should be added:
{
            "Name":"EndpointPolicy",
            "Value":{
               "Type":"ProviderAddress",
               "Settings":{
                  "ProviderAddress":"host ip"
               }
            }
         }

https://github.com/microsoft/windows-container-networking/pull/39

thanks


Running Flask server using run_simple instead of app.run

I know that it has been brought up before that attempting to run a server in newer versions of Flask using app.run in places like the Selenium test case and in the flask profile command results in a warning that app.run will be silently ignored.
What has worked for me is to instead use Werkzeug's run_simple function to start the server as indicated here and here in the documentation.
Here is what I have in flasky.py:
# ...
from werkzeug.serving import run_simple
# ...
@app.cli.command()
@click.option('-h', '--host', default='<IP_ADDRESS>',
              help='The interface to bind to.')
@click.option('-p', '--port', default=5000,
              help='The port to bind to.')
@click.option('--length', default=25,
              help='Number of functions to include in the profiler report.')
@click.option('--profile-dir', default=None,
              help='Directory where profiler data files are saved.')
def profile(host, port, length, profile_dir):
    """
    Start the application under the code profiler.
    """
    from werkzeug.contrib.profiler import ProfilerMiddleware
    app.wsgi_app = ProfilerMiddleware(app.wsgi_app, restrictions=[length],
                                      profile_dir=profile_dir)
    run_simple(host, port, app, use_debugger=False)  # use run_simple instead of app.run()

Thanks, this is a good workaround. There is a bug logged with Flask regarding this problem that I hope one day will be fixed.

werkzeug locks my console after 10 loops, it is a virus


Update logback-classic, logback-core to 1.5.9

About this PR
📦 Updates

ch.qos.logback:logback-classic
ch.qos.logback:logback-core

from 1.5.8 to 1.5.9
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "ch.qos.logback" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "ch.qos.logback" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #3018.


use scala schema dsl (instead of json schema)

depends on https://github.com/ShiftLeftSecurity/overflowdb-codegen/pull/42/

remaining tasks before this can be merged:

fix cpgvalidator
fix downstream projects (codescience, ocular, joern, ...)


Feature Request: Antialiasing mode options

Summary of the new feature/enhancement
Support for different text rendering modes, current mode at least for me causes eye strain making new terminal unusable.
Example between terminal (left) and conemu (right):

Proposed technical implementation details
Adding options to profiles.json:
{
...
"TextAntialiasMode": "D2D1_TEXT_ANTIALIAS_MODE_CLEARTYPE",
...
}

I think this is a really good idea, and one that @miniksa and I have definitely discussed before.
I'd probably want to make the settings values a little clearer than "D2D1_TEXT_ANTIALIAS_MODE_CLEARTYPE", but that we could hash out in a PR I think :)

https://docs.microsoft.com/en-us/windows/desktop/api/d2d1/ne-d2d1-d2d1_text_antialias_mode

If the render target has an alpha channel and is not set to D2D1_ALPHA_MODE_IGNORE, then the default text antialiasing mode is grayscale.

Maybe that's the issue here.
It would be nice if we could set the DWRITE_RENDERING_MODE/DWRITE_MEASURING_MODE too.
For example, look at text rendering in Firefox and Chrome, both using DirectWrite, even in cases when they both enable ClearType : Firefox uses the "GDI classic" mode in some cases :

gfx.font_rendering.cleartype_params.force_gdi_classic_for_families = Arial,Consolas,Courier New,Microsoft Sans Serif,Segoe UI,Tahoma,Trebuchet MS,Verdana
gfx.font_rendering.cleartype_params.force_gdi_classic_max_size = 15

My heart sank the moment I first opened Windows Terminal and witnessed this awful text rendering method that's prevalent in Chromium based applications. (notably Electron based apps) Glad to hear it might get fixed.
Is there a scenario in which the blurry rendering is required, or why is it used? Is the clear text not objectively better looking?

Grayscale rendering is significantly faster than ClearType. You also cannot mix ClearType with alpha blending of the background.
This should be offered as a user preference for sure because everyone has their own tastes when it comes to text rendering.

You also cannot mix ClearType with alpha blending of the background.

But IHMO it makes sense to use "GDI classic" rendering mode to disable subpixel positioning (and perhaps a stronger hinting) in this case, especially for a monospace font.

You also cannot mix ClearType with alpha blending of the background.

But IHMO it makes sense to use "GDI classic" rendering mode to disable subpixel positioning (and perhaps a stronger hinting) in this case, especially for a monospace font.

That might also be a user preference. Maybe someone likes subpixel positioning. Maybe the default should be GDI Classic. To be honest, I haven't thought that hard about this specific topic while standing up the renderer, so it hasn't been addressed.
If someone has strong reasons one way or another, I'd love to hear them. Or I'd love to see someone try them out and prove why one beats the other handily. Or offer both as choices.

Please also consider adding an option to completely disable antialiasing. Not everyone likes soapy text.

call me crazy, but i think it should first of all obey the system-wide settings and if they want to do something different, obey the user's choice

Is this why my Windows Terminal fonts look vertically stretched? I use Hack, size 10. In Windows Terminal the lowercase "e" is 8 pixels high. In all other apps (Emacs, WSL terminal etc.), lowercase "e" is 7 pixels high (and is ClearType-antialiased rather than monochrome). Sample of Windows Terminal (0.6.2951.0):

Sample of WSL terminal (different theme but same text):

As you can see, the same font is significantly taller in Windows Terminal. (The prompt line is also rendered in bold in WSL, but look at the echoed text -- that's not bold in both samples, so should be comparable.)

that could very well be a different font size.
the fact that you ask for a size "10" font doesn't mean anything.
yes, theoretically it does mean something and they will claim it refers
to, again, something, but if you get an answer to the question "why does
every program render a size 10 font to different sizes, then?", i will
shave my scrotum with a rusty spoon and some tabasco.
On Thu, Nov 21, 2019, 23:31 GaryO<EMAIL_ADDRESS>wrote:

Is this why my Windows Terminal fonts look vertically stretched? I use
Hack, size 10. In Windows Terminal the lowercase "e" is 8 pixels high. In
all other apps (Emacs, WSL terminal etc.), lowercase "e" is 7 pixels high
(and is ClearType-antialiased rather than monochrome). Sample of Windows
Terminal (0.6.2951.0):
[image: image]
https://user-images.githubusercontent.com/139975/69378273-18d03e00-0c7c-11ea-846c-9dee6cd647e2.png
Sample of WSL terminal (different theme but same text):
[image: image]
https://user-images.githubusercontent.com/139975/69378307-24236980-0c7c-11ea-9695-9fa48c226c2b.png
As you can see, the same font is significantly taller in Windows Terminal.
(The prompt line is also rendered in bold in WSL, but look at the echoed
text -- that's not bold in both samples, so should be comparable.)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/1298?email_source=notifications&email_token=AM77DI462LU4ZXLRVUUUYSTQU343XA5CNFSM4HYWYCC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE3W6DQ#issuecomment-557281038,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM77DI3JVXGTAQV7C3WZWI3QU343XANCNFSM4HYWYCCQ
.

the fact that you ask for a size "10" font doesn't mean anything.

Well yes, it's possible of course. I do understand in some detail how Windows TrueType font creation/selection works though; and the fact that these samples have (almost) the same width but different heights suggests to me that something else is at work here. And in every other Windows program I use that font in (OneNote, Word and some web apps, as well as the examples I gave above), it does not come out vertically stretched like that.

Opened Windows Terminal for the first time today. My first impression was that something is very wrong. Then I realized the text looked awful, as if I need to wear glasses because the text is out of focus. Tried changing font to no avail. :-/
I don't understand the comments abovem. Did you say that this antialiasing/blur is necessary to allow acrylic backgrounds to work?
I hope the text can be made sharp with a better anti aliasing algorithm. Like in notepad.exe, which is rendering crisply antialiased text. I don't think Terminal is supposed to be so ugly in comparison, right?

Did you say that this antialiasing/blur is necessary to allow acrylic backgrounds to work?

No -- ClearType works fine on the acrylic background. The alpha blending only comes into play in the titlebar IIRC (when drawing over the standard titlebar), but I think that should be fine, too, since any area where text is drawn into the titlebar is entirely covered by an opaque background color.
You can build the terminal yourself, replace the single use of D2D1_TEXT_ANTIALIAS_MODE_GRAYSCALE with D2D1_TEXT_ANTIALIAS_MODE_CLEARTYPE, and see this result:

In the titlebar, it still uses grayscale AA. I haven't looked enough to be able to say if this is because of alpha blending problems, or if that text is drawn differently and doesn't use this AA mode because of that.

I wonder if rendering without antialiasing at all, a la mintty, would be possible at all:

I'm still seeing this when running the very latest terminal 1.0.1401.0 when using "antialiasingMode": "cleartype" on every profile in my settings.json.
Every single profile in profiles.list has "antialiasingMode": "cleartype" set, and it's set in profiles.defaults.
I tried:

Updating - I was seeing this last version as well (0.11.x?) - and that made no difference.
Reinstalling and editing cleartype into the settings before opening Terminal in the first place. No difference.
Nearly an hour on Google - this and related threads primarily - with no result.

I'm a little stuck.

@Legorooj if you have acrylic on, it won't use cleartype, see #5277

@melak47
"defaults":
{
    // Put settings here that you want to apply to all profiles.
    "antialiasingMode": "cleartype",
    "useAcrylic": false
},

The error still occurs (several relaunches. I also tried setting it individually for each profile):

@melak47
"defaults":
{
    // Put settings here that you want to apply to all profiles.
    "antialiasingMode": "cleartype",
    "useAcrylic": false
},

The error still occurs (several relaunches. I also tried setting it individually for each profile):

@Legorooj, that's not a cleartype error. That screenshot is of the problem in #5759.
You can try the rendering settings documented behind https://docs.microsoft.com/en-us/windows/terminal/troubleshooting#the-text-is-blurry to set either full repaints or software rendering to mitigate that until we can fully understand what is causing some graphics drivers to blur out the previous frames of our rendering.

@miniksa thanks for that - somehow I didn't come across that issue or the settings page. Using forced software rendering seems to have fixed the problem. Thanks!

pixel center offset, texture resize, texturemin/mag filter, texture
compression, glViewport, data type when packing/unpacking pixels, dpi
settings, are some of the things that come to mind. On amd hardware there
is an option in their control panel, "morphological filtering" that may
interfere
i've spent unhealthy amounts of effort and time rendering text as sharp as
possible.
i've concluded that unless you plan on running behind the gpu vendors every
time they change something, the only feasible method is software rendering
with simd, blitting, raster fonts, and dirty rects. In short, the oldest
methods known.
On Fri, May 29, 2020, 18:51 Michael Niksa<EMAIL_ADDRESS>wrote:

@melak47 https://github.com/melak47
"defaults":
{
// Put settings here that you want to apply to all profiles.
"antialiasingMode": "cleartype",
"useAcrylic": false
},
The error still occurs (several relaunches. I also tried setting it
individually for each profile):
[image: PowerShell 21_05_2020 5_34_34 PM]
https://user-images.githubusercontent.com/50370070/82629398-f7eca380-9c32-11ea-9c24-6f207a350b26.png
@Legorooj https://github.com/Legorooj, that's not a cleartype error.
That screenshot is of the problem in #5759
https://github.com/microsoft/terminal/issues/5759.
You can try the rendering settings documented behind
https://docs.microsoft.com/en-us/windows/terminal/troubleshooting#the-text-is-blurry
to set either full repaints or software rendering to mitigate that until we
can fully understand what is causing some graphics drivers to blur out the
previous frames of our rendering.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/1298#issuecomment-636047233,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM77DIZXIOTKYPT33DCYWVTRT7KYVANCNFSM4HYWYCCQ
.

Question -- some people turn off the "smooth edge of screen fonts" option available on the "Performance Options", so the fonts look pixeleted but crystal sharp. From what I saw the fonts stay the same with this option turned on or off. Can you please check if this is causing the fonts to look smudge?
Take care and awesome terminal you've got there 👍
Mic.

if you have acrylic on, it won't use cleartype, see https://github.com/microsoft/terminal/pull/5277

is that still the case?

not sure if this old issue got closed because of a fix or not just inactivity, but the issue is happening to me as well

That doesn't look like antialiasing to me, that looks like you've got a custom scaling factor set, see #4591

oooh thanks for the quick response, this indeed looks like my issue


[test-triage] chip_sw_spi_device_pass_through_collision

Hierarchy of regression failure
Chip Level
Failure Description
UVM_ERROR @ * us: (sw_logger_if.sv:523) [spi_passthrough_test_prog_sim_dv(sw/device/tests/sim_dv/spi_passthrough_test.c:400)] CHECK-fail: status & kSpiFlashStatusBitWip has 1 failures:
Test chip_sw_spi_device_pass_through_collision has 1 failures.
0.chip_sw_spi_device_pass_through_collision.2017016022
Line 1064, in log /container/opentitan-public/scratch/os_regression/chip_earlgrey_asic-sim-vcs/0.chip_sw_spi_device_pass_through_collision/latest/run.log
UVM_ERROR @ 3248.195940 us: (sw_logger_if.sv:523) [spi_passthrough_test_prog_sim_dv(sw/device/tests/sim_dv/spi_passthrough_test.c:400)] CHECK-fail: status & kSpiFlashStatusBitWip
UVM_INFO @ 3248.195940 us: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
--- UVM Report catcher Summary ---
Steps to Reproduce

GitHub Revision: HASH_VALUE
dvsim invocation command to reproduce the failure, inclusive of build and run seeds:
./util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_sw_spi_device_pass_through_collision --build-seed<PHONE_NUMBER> --fixed-seed<PHONE_NUMBER>

Tests with similar or related failures

[ ] chip_sw_spi_device_pass_through_collision

Triaged for spi_device. Assigning to M2.5 with https://github.com/lowRISC/opentitan/labels/Priority%3AP2. This test passes 3/3 in today's nightlies but only 2/3 in yesterday's nightlies, so it still appears to be flaky. We need to check this to ensure there's no bug lurking here.

estimate 4
remaining 2023-03-22 4

Triaged with @engdoreis - test is failing every now and again (mostly passing).
Decided to lower this to P2 for now.

In the original failing hash, we have a PageProgram command that hasn't even finished signaling yet, but software is already checking the busy bit? There may be a bug in the software.

Ah, we're touching on one of the ways that spi_device is not very ergonomic, and I made an error with this test:
https://github.com/lowRISC/opentitan/blob/adecb1646aa293f069a73e3637b9cb68632ad585/sw/device/tests/sim_dv/spi_passthrough_test.c#L450-L458
This only checks when the command FIFO is not empty, and that commit occurs on bit 8, before the transaction is complete. We're not actually ready to begin processing the command until CSB is de-asserted. The related cmdfifo_not_empty interrupt doesn't fire until the command is complete, but the software doesn't currently check that it has occurred.
The reporting of partial transactions makes for a rather awkward interface. However, with the hardware design as it is, software should check for the cmdfifo_not_empty interrupt before processing the command.


AttributeError: 'module' object has no attribute 'patch_all'

Hi,
I am getting the error below when I execute, please help.
This is on Linux Mint
my@machine ~ $ pyportify
Traceback (most recent call last):
File "/usr/local/bin/pyportify", line 9, in
load_entry_point('pyportify==0.2.7', 'console_scripts', 'pyportify')()
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 351, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2363, in load_entry_point
return ep.load()
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2088, in load
entry = import(self.module_name, globals(),globals(), ['name'])
File "/usr/local/lib/python2.7/dist-packages/pyportify/server.py", line 5, in
from pyportify.views import app as application
File "/usr/local/lib/python2.7/dist-packages/pyportify/views.py", line 7, in
monkey.patch_all()
AttributeError: 'module' object has no attribute 'patch_all'

Never mind, sorted. Don't know what I did to fix it.


Release scoped package?

@feross do you prefer a GitHub dependency, or scoped: @webtorrent/airplay-protocol?
Branch release is prepared for a scoped publication.
Related: https://github.com/webtorrent/airplayer/pull/1#issuecomment-529186869

I would rather just depend on this with a git dependency since this should hopefully just be temporary. If we publish to npm, then we'll need to do deprecations later.


figure out if we can take in a single sparse dictionary, and convert it to the same structure dataframe as we used for training

say we train on 600 features. then we pass in a single dictionary that only has 300 features. this will not result in the same DF as what we trained on.

we'll take care of this with our own custom DataFrameVectorizer.
Ideally, that vectorizer will be able to take in either a df or a single dictionary (so use bracket notation, not dot notation), and perform the same vectorizing regardless.
this means we'll also have to try to keep our transform functions as flexible as possible, to take in either a df or a single dictionary. but that's a future optimization.

done.


Pico board config improvements

Splits the big if/else chain in 32blit-pico's CMakeLists into separate config files and the "drivers" into multiple files instead of a giant pile of #ifdefs.
Also includes some of the configs from the "all-the-boards" branch (the ones that don't need much extra code).

Oh, and removes the pico-extras requirement for devices that don't use it. (PicoSystem most importantly)

Ooooh, veeerryy nice!
I guess this is a huge step toward making this project a little less opinionated about target platforms and a touch more extensible. I think @ali1234 had some thoughts in that direction, but I can't remember where they were mentioned.

At least for anything RP2040-based... 32blit-stm32 remains a bit of a mess. But uh, there's not a huge amount of hardware to target there.
Currently working through the "everything" branch attempting to not make things too messy. I think finishing VGA board support might be next...

Le rebase fail? :eyes:

Nope, just forgot to rebase entirely.
(Pressed the resolve button to see what it would do...)

Oh yeah, I'm floored at just how incredibly bad GitHub's integrated conflict resolution is.

Borrowed a little idea from this for Galactic (Blunicorn) Bluetooth Audio. Thanks :laughing:


[Migration] DB schema migration for improvements in FIDO2

Related issues:
- https://github.com/wso2/product-is/issues/6970
- https://github.com/wso2/product-is/issues/7151
Related PR: https://github.com/wso2/carbon-identity-framework/pull/2644
With this PR it introduces the following new columns to FIDO2_DEVICE_STORE table. This is done for a requirement for improvements in the UI.

DISPLAY_NAME VARCHAR(255)
IS_USERNAMELESS_SUPPORTED CHAR(1) DEFAULT '0'

Done with https://github.com/wso2-extensions/identity-migration-resources/pull/39


[RELEASE] Update copyright message, change notice, remove cma kernel mod

The cma kernel module are created to run the CMA on top of linux distributions. The license of the code is MIT. Unfortunately due to the license policy of linux and the module macro indicate the MODULE_LICENSES("GPL"), it is best to act caution and not release the code as part of the Apache release
This PR removes the kernel module parts for now. We could host a separate repo that we can point to and move the code there.
cc @liangfu

cc @yzhliu


application.systemAppearance() failing for iOS

Environment

CLI: 6.5.0
Cross-platform modules: 6.5.1
Android Runtime: 6.5.0
iOS Runtime: 6.5.0
Plugin(s<EMAIL_ADDRESS>NativeScript-Angular: 8.21.0
Angular: 8.2.14

Describe the bug
application.systemAppearance() is failing for iOS with the following error and stack trace
CONSOLE ERROR file: node_modules/@angular/core/fesm5/core.js:4002:0: ERROR Error: Uncaught (in promise): TypeError: null is not an object (evaluating 'this.rootController.traitCollection')
get(file: node_modules/@nativescript/core/application/application.ios.js:100:0)
at systemAppearance(file: node_modules/@nativescript/core/application/application.ios.js:419:0)
at ItemsComponent(file: src/app/item/items.component.ts:17:72)
at createClass(file: node_modules/@angular/core/fesm5/core.js:21148:0)
at createDirectiveInstance(file: node_modules/@angular/core/fesm5/core.js:21027:0)
at createViewNodes(file: node_modules/@angular/core/fesm5/core.js:29387:0)
at createRootView(file: node_modules/@angular/core/fesm5/core.js:29301:0)
at callWithDebugContext(file: node_modules/@angular/core/fesm5/core.js:30309:0)
at file: node_modules/@angular/core/fesm5/core.js:20506:0
at file: node_modules/@angular/core/fesm5/core.js:20617:0
at file: node_modules/@nativescript/angular/common/detached-loader.js:38:0
at file: node_modules/@nativescript/angular/router/page-router-outlet.js:300:0
at file: node_modules/@nativescript/angular/router/page-router-outlet.js:270:0
at file: node_modules/@angular/router/fesm5/router.js:2310:0
at file: node_modules/@angular/router/fesm5/router.js:2261:0
at forEach([native code])
at file: node_modules/@angular/router/fesm5/router.js:2260:0
at file: node_modules/@angular/router/fesm5/router.js:2185:0
at file: node_modules/@angular/router/fesm5/router.js:2169:0
at file: node_modules/rxjs/_esm5/internal/operators/map.js:35:0
at file: node_modules/rxjs/_esm5/internal/Subscriber.js:53:0
at file:///ap<…>

To Reproduce
Setup new Angular based project:
tns create testSystemAppearanceNg --ng
cd testSystemAppearanceNg

Change the content of src/app/item/items.component.ts to:
import { Component, OnInit } from "@angular/core";

import * as application from "@nativescript/core/application";

import { Item } from "./item";
import { ItemService } from "./item.service";

@Component({
    selector: "ns-items",
    templateUrl: "./items.component.html"
})
export class ItemsComponent implements OnInit {
    items: Array<Item>;

    constructor(private itemService: ItemService) {

        // check for current systemAppearance (dark or light):
        console.log('systemAppearance >>>', application.systemAppearance());
    }

    ngOnInit(): void {
        this.items = this.itemService.getItems();
    }
}

Run for iOS:
tns run ios
Expected behavior
No error.
Additional context
This is only failing for iOS, Android is working fine.

I can confirm that this is a problem on iOS.
Any news on this?

Having the same Issue. Found a workaround yet?

Having the same Issue. Any workaround yet?

How am I supposed to check the system appearance on iOS? Any input? The issue exists still with latest NS7.

I've got a service that makes it easy to use in TypeScript.
import { Injectable } from '@angular/core';
import { on as applicationOn, systemAppearanceChangedEvent, SystemAppearanceChangedEventData } from '@nativescript/core/application';
import { Observable, Subject } from 'rxjs';
import { map } from 'rxjs/operators';

const EVENT_STREAM: Subject<SystemAppearanceChangedEventData> = new Subject<SystemAppearanceChangedEventData>();

@Injectable()
export class DarkModeService {
    readonly changedAppearance$: Observable<'dark' | 'light'>;
    constructor() {
        this.changedAppearance$ = EVENT_STREAM.pipe(map((event: SystemAppearanceChangedEventData) => {
            return event.newValue;
        }));
    }
}

applicationOn(systemAppearanceChangedEvent, (event: SystemAppearanceChangedEventData) => {
    EVENT_STREAM.next(event);
});

In your templates, you can use the CSS classes:
.ns-root.ns-light :host .my-class {
  ...
}

.ns-root.ns-dark :host .my-class {
  ...
}

I suspect it might also be an implementation issue on your side. You've called that function in the constructor of an injectable service. It's possible that you may be constructing that before your application has a root view controller assigned, which is what's causing the error you see.
Move it into an observable or function such that it's queried when needed, and not at application start.

Thanks @facetious for your input. It helped me a lot finding a working solution for my use case.
It is just so irritating that some stuff is working just fine in Android and not iOS or the other way round.

I've got a service that makes it easy to use in Angular.
import { Injectable } from '@angular/core';
import { on as applicationOn, systemAppearanceChangedEvent, SystemAppearanceChangedEventData } from '@nativescript/core/application';
import { Observable, Subject } from 'rxjs';
import { map } from 'rxjs/operators';

const EVENT_STREAM: Subject<SystemAppearanceChangedEventData> = new Subject<SystemAppearanceChangedEventData>();

@Injectable()
export class DarkModeService {
    readonly changedAppearance$: Observable<'dark' | 'light'>;
    constructor() {
        this.changedAppearance$ = EVENT_STREAM.pipe(map((event: SystemAppearanceChangedEventData) => {
            return event.newValue;
        }));
    }
}

applicationOn(systemAppearanceChangedEvent, (event: SystemAppearanceChangedEventData) => {
    EVENT_STREAM.next(event);
});

In your templates, you can use the CSS classes:
.ns-root.ns-light :host .my-class {
  ...
}

.ns-root.ns-dark :host .my-class {
  ...
}

@facetious : I just tried the service code you provided. Unfortunately, it seems that the systemAppearanceChangedEvent is only called when a change is happening. However, I need to get the dark or light mode state already on app startup, Hence in case the app was started before a change happened. Do you have an idea how I can read out the currrently set state?


root_key_ids keep getting added to lnd even when I delete an LND Account

root_key_ids keep getting added to lnd even when I delete an LND Account
Expected behavior
When deleting an LND Account, lnd should forget about the root_key_id.
Actual behavior
After deleting an account with litcli, lnd stills has a root_key_id for it.
To reproduce

Run lncli listmacaroonids and see the initial list of root_key_ids.
Run litcli accounts create 150 to create a new LND Account.
Run lncli listmacaroonids again to see the new list of root_key_ids.
Run litcli accounts remove id to remove the account that was just created.
Run lncli listmacaroonids again to see the list of root_key_ids has not shrunk.

System information
Standalone install on ubuntu
Remote lnd
v0.10.1-alpha, self compiled

Hey Andy, thanks for the feedback. Chatting with the team on this one a bit. We have some folks out of office this week who have the most context on this feature so it might take til next week to get a substantive response here, but wanted to let you know that we are looking at it :)

There may be some actual purpose to not delete the root_key_ids forever, but I can't currently think of why. Would like to hear what your team says for sure.

Yep, I dont see why we cant just delete it 👍 just want to get a second opinion from @guggero  here though to make sure there isnt a security issue with re-using root keys for different macaroons.

There is a "one-to-many" relationship between a macaroon root key and an account (and also between account and LNC session, so this is related to https://github.com/lightninglabs/lightning-terminal/issues/578), so root_key_id  <--- n : 1 --->  account  <--- n : 1 ---> lnc_session. That's why when deleting/expiring a session we don't automatically remove the account and when removing an account we don't remove the root key. I agree that this is probably quite confusing as there is currently no way in the RPC to specify the root_key_id to use when creating an account, so it's only "one-to-many" under the hood.
Given that we can identify the root key IDs created by litd and can find out if there are multiple accounts using the same, we should be able to clean up.
Maybe adding the ability to specify the root key ID to use for an account and also showing that info in the RPC would make the relationship more clear (and that would also allow you to revoke access to multiple accounts/sessions with a single command if you group multiple accounts to the same root key ID).

The way it appears to me, you are creating a new root_key_id for each account. In what scenario are you sharing a root_key_id between multiple accounts?
I would think that deleting a session shouldn't necessarily remove the account because you may want to create a new session for the same account, but deleting an account should delete the account and all sessions (if it does not already do so).

In what scenario are you sharing a root_key_id between multiple accounts?

This is not currently done internally and there is no way to do it over the CLI/RPC either (yet), but I can imagine this being useful as a feature in general. You could create a single root key ID for a specific group of users, create an account for each user but still have the ability to revoke all permissions of the whole user group with a single command.

but deleting an account should delete the account and all sessions (if it does not already do so).

I agree, we should do that (I'm pretty sure we currently don't, as accounts and sessions are mostly independent data structures and only linked through a single attribute).

For now, I'd recommend automatically removing the root_key_ids when removing an account if you don't have a way to link them to anything else. If you ever do add functionality to apply multiple users to the same root_key_id, then consider adding the option to remove root_key_ids when removing the last user from the group.


Add 3.14-rc variants

Python 3.14 is still in development. This release, 3.14.0a1 is the first of seven planned alpha releases.
https://www.python.org/downloads/release/python-3140a1/

I'll update the PR with the correct GPG key in a bit...

https://peps.python.org/pep-0761/ seems to confirm that Python is indeed moving from PGP to Sigstore. For >= 3.11 this seems to be in place, so a full migration would not be possible yet; so probably this would require distinguishing versions and implementing two different ways to verify artefacts.

https://github.com/docker-library/python/issues/977#issuecomment-2403109432
So, I think we'll have to just remove the gpg verification for 3.14 and above and solely rely on the sha256 check (https://github.com/docker-library/python/pull/978) until there is a secure/verifiable way (like an apt package in Debian) to get a sigstore client to check the sigstore signature.

Updated with an appropriate conditional to remove the PGP logic for 3.14+ :eyes:


[CT-2024] 1.4.0 migration tracker for partner- and community-developed adapters

Using this as a status tracker on migration of adapter ecosystem to dbt-core.1.4.0. See #6624 for the main upgrade guide.
### Tasks
- [ ] https://github.com/ClickHouse/dbt-clickhouse/issues/135
- [ ] https://github.com/databricks/dbt-databricks/issues/267
- [ ] https://github.com/jwills/dbt-duckdb/issues/88
- [ ] https://github.com/tglunde/dbt-exasol/issues/57
- [ ] https://github.com/firebolt-db/dbt-firebolt/issues/93
- [ ] https://github.com/aws-samples/dbt-glue/issues/143
- [ ] https://github.com/markporoshin/dbt-greenplum/issues/14
- [ ] https://github.com/cloudera/dbt-hive/issues/94
- [ ] https://github.com/aurany/dbt-ibmdb2/issues/30
- [ ] https://github.com/cloudera/dbt-impala/issues/142
- [ ] https://github.com/iomete/dbt-iomete/issues/5
- [ ] https://github.com/MaterializeInc/materialize/issues/17500
- [ ] https://github.com/mindsdb/dbt-mindsdb/issues/18
- [ ] https://github.com/dbeatty10/dbt-mysql/issues/122
- [ ] https://github.com/chop-analytics/dbt-netezza/issues/18
- [ ] https://github.com/oracle/dbt-oracle/issues/70
- [ ] https://github.com/rockset/dbt-rockset/issues/28
- [ ] https://github.com/memsql/dbt-singlestore/issues/18
- [ ] https://github.com/dbt-labs/dbt-spark/issues/631
- [ ] https://github.com/dbt-msft/dbt-sqlserver/issues/333
- [ ] https://github.com/dbt-athena/dbt-athena/issues/136
- [ ] https://github.com/splitgraph/sgr/issues/773
- [ ] https://github.com/codeforkjeff/dbt-sqlite/issues/40
- [ ] https://github.com/StarRocks/dbt-starrocks/issues/15
- [ ] https://github.com/microsoft/dbt-synapse/issues/147
- [ ] https://github.com/Teradata/dbt-teradata/issues/63
- [ ] https://github.com/pingcap/dbt-tidb/issues/49
- [ ] https://github.com/starburstdata/dbt-trino/issues/223
- [ ] https://github.com/vertica/dbt-vertica/issues/67
- [ ] https://github.com/dremio/dbt-dremio/issues/117
- [ ] https://github.com/fal-ai/fal/issues/740
- [ ] https://github.com/databendcloud/dbt-databend/issues/1
- [ ] https://github.com/inferlabs/dbt-infer/issues/5

closing in favor of a comment in the discussion
https://github.com/dbt-labs/dbt-core/discussions/6624#discussioncomment-5663823


Fixed other samples link

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

Looks good; thanks @javierdlg.


can't import tensorflow.keras properly

I,m writing my code in vscode edit with tensorflow=1.13.1 version and anaconda virtual environment. But when I write 'from tensorflow.keras import layers',it give me a warning:
"unresolved import 'tensorflow.keras'(unresolved import)".
The code can run as I expected,no errors. But because tensorflow.keras can't be imported properly,the auto-completion and intelligent hint function can't work,I need to search the function's usage everytime. I have thought it's the problem of vscode, but the problem came as well when I use pycharm IDE. Have anyone has the same problem? Is there anyone can help me?

The problem is present also in 2.0. Apparently, Jedi (or Pyls) cannot resolve Keras import.

Works fine for me, with both ways of importing
"from tensorflow.python.keras import layers"
and
"from tensorflow.keras import layers"
Can you give us a little more info about your configuration?

In my case I am using the 2.0 Nightly, the issue is related to autocomplete either using Jedi or Pyls (Python Language Server) with either Vim/Neovim/Pycharm or VS Code.
The issue is present also if linting with pylint as it cannot see Keras marking it as an erroneous import. The problem is common to all 4 machines we use in our lab. The only peculiar thing is that we run Arch Linux but Tensorflow is installed in a separate virtualenv. Every other module seems to work fine, Keras is the only problematic one.

Works fine for me, with both ways of importing
"from tensorflow.python.keras import layers"
and
"from tensorflow.keras import layers"
Can you give us a little more info about your configuration?

I works on windows10 platform, and I use the python plugin for vscode. It seems that just tensorflow's keras module can't be imported properly, i.e. vscode's automatic completion function didn't work but other modules works fine.

If the issue is related to autocomplete related to your IDEs, then maybe this isn't a tensorflow issue.
Can you import from a python interpreter that does NOT use any autocomplete method? If you already tried that, does the problem persist?

Importing keras in an interpreter works but all linters and autocomplete providers cannot resolve it. Unless it's something shared by all of them I would guess it's TF

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

The automatic completion never worked for me either. I'm using PyCharm (professional edition).

You can use the v1 api like so:

from tensorflow._api.v1.keras import Sequential
from tensorflow._api.v1.keras.layers import Dense

or the tensorflow.python api like so:
from tensorflow.python.keras import Sequential
from tensorflow.python.keras.layers import Dense

Closing this issue since it is IDE related. Feel free to reopen if have any questions. Thanks!

It solved my problem, thank you!
At 2019-04-17 18:00:06, "Raphael Neumann"<EMAIL_ADDRESS>wrote:
You can use the v1 api like so:
from tensorflow._api.v1.keras import Sequential
from tensorflow._api.v1.keras.layers import Dense
or the tensorflow.python api like so:
from tensorflow.python.keras import Sequential
from tensorflow.python.keras.layers import Dense
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

It seems because auto-complete won't scan the whole code of a library. I open __init__.py file whose path is /usr/local/lib/python3.6/dist-packages/tensorflow/__init__.py in my computer, and add one line from tensorflow.python import keras. It works for me. And you can find the path of the file by using finding definition of your IDE. I think it's a temporary way.

@kong13661 so it is a tf issue.

this is still a problem for me, it cann't auto-complete the code.

Using tensorflow 2.1.0 in VScode.
I'm having the same issue.

Having the same issue. Please reopen this

Having the same issue. Please reopen this

same issue with VScode 1.42.1 & tensorflow 2.0.1

Same issue TensorFlow 2.0 in PyCharm.

If you upgrade pycharm to 2019.3 version, this issue may can be solved.
Soheila Zangeneh<EMAIL_ADDRESS>周四上午10:25写道：

Same issue TensorFlow 2.0 in PyCharm.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/26813?email_source=notifications&email_token=ALBFLYHYG7P7W7JRZOJDBETRDXLXFA5CNFSM4G7DFINKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMKL5IQ#issuecomment-588562082,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALBFLYDITBG5QDCR5A67EMLRDXLXFANCNFSM4G7DFINA
.

Same issue here. All other packages work fine.

If you upgrade pycharm to 2019.3 version, this issue may can be solved. Soheila Zangeneh<EMAIL_ADDRESS>周四上午10:25写道：
…

Worked for me! Thanks!

Try removing the prefix "tensorflow".
Eg: from keras import layers

When I switched to use flake8 instead of pylint, all error message related to importing keras has gone. If you try, open VScode setting page and serach Linting Enabled, and

Uncheck Python › Linting: Pylint Enabled
Check Python › Linting: Flake8 Enabled

I opened an issue for this on the vscode-python page: https://github.com/microsoft/vscode-python/issues/10598

When I switched to use flake8 instead of pylint, all error message related to importing keras has gone. If you try, open VScode setting page and serach Linting Enabled, and
1. Uncheck `Python › Linting: Pylint Enabled`

2. Check `Python › Linting: Flake8 Enabled`

Other solution?
#15736 (comment)

That finally worked for me! Thanks a lot for that hint!

Working with the 2.1.0. The problem persists only with the TensorFlow modules.

uninstall extension Visual Studio IntelliCode works fine for me

Locking conversation to drive people encountering new issues with newer code to open new issue reports (filling in template) and to help people encountering the same issue find the solution here


Embedded subtitles not shown in Chromecast

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
The latest one available for Chromecast (2.5.8)
Can you reproduce the issue with our latest release version?
Yes, I changed the player version in the cast receiver script and the issue was still observable.
Can you reproduce the issue with the latest code from master?
N/A
Are you using the demo app or your own custom app?
Custom receiver app
What browser and OS are you using?
Version 80.0.3987.132 (Official Build) (64-bit)
What are the manifest and license server URIs?
https://ngtoslvideolive.solocoo.tv/ngtcleardash/discovery/manifest.mpd?text=wvtt
No DRM
What did you do?
Loaded the stream into Chromecast Receiver App and tried to load subtitles
What did you expect to happen?
I was expecting to see the subtitles on the screen
What actually happened?
The stream is being played correctly but instead of subtitles, I see an empty black rectangle in a place where subtitles should be.

What did you do?
Loaded the stream into Chromecast Receiver App and tried to load subtitles

Is this:

our Chromecast Receiver App, using Shaka Player directly?  https://github.com/google/shaka-player/tree/master/demo/cast_receiver
your own receiver app using Shaka Player directly?
some default receiver provided by CAF?

Thanks!

@joeyparrish It's our own custom app built using CAF.

We don't control CAF, so unfortunately, this is the wrong forum for CAF support.  Please refer to https://developers.google.com/cast/support#report_issues
Sorry we can't help with that!  Hopefully the Cast team will be able to offer a solution.  As an alternative, you can always try using Shaka Player directly in a custom receiver as we do in our demo.