Intel hd4600 graphics can not run tensorflow-directml programs，but hd530 works fine.

On hd4600 the console showing:
WARNING:tensorflow:
The TensorFlow contrib module will not be included in TensorFlow 2.0.
For more information, please see:

https://github.com/tensorflow/community/blob/master/rfcs/20180907-contrib-sunset.md
https://github.com/tensorflow/addons
https://github.com/tensorflow/io (for I/O related ops)
If you depend on functionality not listed there, please file an issue.

WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:50: The name tf.placeholder is deprecated. Please use tf.compat.v1.placeholder instead.
WARNING:tensorflow:From D:\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow_core\contrib\layers\python\layers\layers.py:1057: Layer.apply (from tensorflow.python.keras.engine.base_layer) is deprecated and will be removed in a future version.
Instructions for updating:
Please use layer.__call__ method instead.
WARNING:tensorflow:From D:\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow_core\contrib\layers\python\layers\layers.py:1066: batch_normalization (from tensorflow.python.layers.normalization) is deprecated and will be removed in a future version.
Instructions for updating:
Use keras.layers.BatchNormalization instead.  In particular, tf.control_dependencies(tf.GraphKeys.UPDATE_OPS) should not be used (consult the tf.keras.layers.batch_normalization documentation).
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:218: The name tf.losses.softmax_cross_entropy is deprecated. Please use tf.compat.v1.losses.softmax_cross_entropy instead.
WARNING:tensorflow:From D:\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow_core\python\ops\losses\losses_impl.py:121: where (from tensorflow.python.ops.array_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.where in 2.0, which has the same broadcast rule as np.where
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:219: The name tf.losses.get_total_loss is deprecated. Please use tf.compat.v1.losses.get_total_loss instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:220: The name tf.train.AdamOptimizer is deprecated. Please use tf.compat.v1.train.AdamOptimizer instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:223: The name tf.get_collection is deprecated. Please use tf.compat.v1.get_collection instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:223: The name tf.GraphKeys is deprecated. Please use tf.compat.v1.GraphKeys instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:234: The name tf.truncated_normal is deprecated. Please use tf.random.truncated_normal instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:238: calling dropout (from tensorflow.python.ops.nn_ops) with keep_prob is deprecated and will be removed in a future version.
Instructions for updating:
Please use rate instead of keep_prob. Rate should be set to rate = 1 - keep_prob.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:248: The name tf.nn.xw_plus_b is deprecated. Please use tf.compat.v1.nn.xw_plus_b instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:254: The name tf.losses.mean_squared_error is deprecated. Please use tf.compat.v1.losses.mean_squared_error instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:258: The name tf.trainable_variables is deprecated. Please use tf.compat.v1.trainable_variables instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:267: The name tf.Session is deprecated. Please use tf.compat.v1.Session instead.
2020-07-15 21:43:32.488885: I tensorflow/core/common_runtime/dml/dml_device_factory.cc:45] DirectML device enumeration: found 1 compatible adapters.
2020-07-15 21:43:32.501242: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
2020-07-15 21:43:32.503347: I tensorflow/core/common_runtime/dml/dml_device_factory.cc:32] DirectML: creating device on adapter 0 (Intel(R) HD Graphics 4600)
2020-07-15 21:43:32.621172: I tensorflow/stream_executor/platform/default/dso_loader.cc:60] Successfully opened dynamic library DirectMLba106a7c621ea741d2159d8708ee581c11918380.dll
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:269: The name tf.global_variables_initializer is deprecated. Please use tf.compat.v1.global_variables_initializer instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:271: The name tf.train.Saver is deprecated. Please use tf.compat.v1.train.Saver instead.
2020-07-15 21:44:13.976556: F tensorflow/core/common_runtime/dml/dml_command_recorder.cc:372] Check failed: (((HRESULT)((dml_device_->GetDeviceRemovedReason()))) >= 0) == true (0 vs. 1)
On hd530 the console showing:
WARNING:tensorflow:
The TensorFlow contrib module will not be included in TensorFlow 2.0.
For more information, please see:

https://github.com/tensorflow/community/blob/master/rfcs/20180907-contrib-sunset.md
https://github.com/tensorflow/addons
https://github.com/tensorflow/io (for I/O related ops)
If you depend on functionality not listed there, please file an issue.

WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:50: The name tf.placeholder is deprecated. Please use tf.compat.v1.placeholder instead.
WARNING:tensorflow:From D:\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow_core\contrib\layers\python\layers\layers.py:1057: Layer.apply (from tensorflow.python.keras.engine.base_layer) is deprecated and will be removed in a future version.
Instructions for updating:
Please use layer.__call__ method instead.
WARNING:tensorflow:From D:\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow_core\contrib\layers\python\layers\layers.py:1066: batch_normalization (from tensorflow.python.layers.normalization) is deprecated and will be removed in a future version.
Instructions for updating:
Use keras.layers.BatchNormalization instead.  In particular, tf.control_dependencies(tf.GraphKeys.UPDATE_OPS) should not be used (consult the tf.keras.layers.batch_normalization documentation).
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:218: The name tf.losses.softmax_cross_entropy is deprecated. Please use tf.compat.v1.losses.softmax_cross_entropy instead.
WARNING:tensorflow:From D:\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow_core\python\ops\losses\losses_impl.py:121: where (from tensorflow.python.ops.array_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.where in 2.0, which has the same broadcast rule as np.where
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:219: The name tf.losses.get_total_loss is deprecated. Please use tf.compat.v1.losses.get_total_loss instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:220: The name tf.train.AdamOptimizer is deprecated. Please use tf.compat.v1.train.AdamOptimizer instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:223: The name tf.get_collection is deprecated. Please use tf.compat.v1.get_collection instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:223: The name tf.GraphKeys is deprecated. Please use tf.compat.v1.GraphKeys instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:234: The name tf.truncated_normal is deprecated. Please use tf.random.truncated_normal instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:238: calling dropout (from tensorflow.python.ops.nn_ops) with keep_prob is deprecated and will be removed in a future version.
Instructions for updating:
Please use rate instead of keep_prob. Rate should be set to rate = 1 - keep_prob.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:248: The name tf.nn.xw_plus_b is deprecated. Please use tf.compat.v1.nn.xw_plus_b instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:254: The name tf.losses.mean_squared_error is deprecated. Please use tf.compat.v1.losses.mean_squared_error instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:258: The name tf.trainable_variables is deprecated. Please use tf.compat.v1.trainable_variables instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:267: The name tf.Session is deprecated. Please use tf.compat.v1.Session instead.
2020-07-15 21:48:28.272086: I tensorflow/core/common_runtime/dml/dml_device_factory.cc:45] DirectML device enumeration: found 2 compatible adapters.
2020-07-15 21:48:28.274903: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
2020-07-15 21:48:28.275889: I tensorflow/core/common_runtime/dml/dml_device_factory.cc:32] DirectML: creating device on adapter 0 (Intel(R) HD Graphics 530)
2020-07-15 21:48:28.346440: I tensorflow/stream_executor/platform/default/dso_loader.cc:60] Successfully opened dynamic library DirectMLba106a7c621ea741d2159d8708ee581c11918380.dll
2020-07-15 21:48:28.366793: I tensorflow/core/common_runtime/dml/dml_device_factory.cc:32] DirectML: creating device on adapter 1 (Intel(R) HD Graphics 530)
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:269: The name tf.global_variables_initializer is deprecated. Please use tf.compat.v1.global_variables_initializer instead.
WARNING:tensorflow:From D:\work\EkNiCuMine\train\tc7.py:271: The name tf.train.Saver is deprecated. Please use tf.compat.v1.train.Saver instead.
2020-07-15 21:49:10.806959 number iterations: 0
cost is: 2.8335354
accuracy is: 0.0

Hi, it appears that the HD4600 is running into a device removal error. Device removal can sometimes be triggered by driver errors, but more often are due to the GPU timing out. The GPU can time out if an extremely large workload is submitted all at once, causing the device to appear hung. Does the same error occur if you try a smaller or less complex model?
For example if you run the following simple example, does it still return the same error on the HD4600?
`>>> import tensorflow as tf

tf.debugging.set_log_device_placement(True)
tf.enable_eager_execution()
a = tf.constant([[1.0, 2.0, 3.0], [4.0, 5.0, 6.0]])
b = tf.constant([[1.0, 2.0], [3.0, 4.0], [5.0, 6.0]])
c = tf.matmul(a, b)`

Hi, it appears that the HD4600 is running into a device removal error. Device removal can sometimes be triggered by driver errors, but more often are due to the GPU timing out. The GPU can time out if an extremely large workload is submitted all at once, causing the device to appear hung. Does the same error occur if you try a smaller or less complex model?
For example if you run the following simple example, does it still return the same error on the HD4600?
import tensorflow as tf
tf.debugging.set_log_device_placement(True)
tf.enable_eager_execution()
a = tf.constant([[1.0, 2.0, 3.0], [4.0, 5.0, 6.0]])
b = tf.constant([[1.0, 2.0], [3.0, 4.0], [5.0, 6.0]])
c = tf.matmul(a, b)

works fine now:
WARNING:tensorflow:From D:\work\EkNiCuMine\train\t1.py:3: The name tf.enable_eager_execution is deprecated. Please use tf.compat.v1.enable_eager_execution instead.
2020-07-17 12:00:37.609541: I tensorflow/core/common_runtime/dml/dml_device_factory.cc:45] DirectML device enumeration: found 1 compatible adapters.
2020-07-17 12:00:37.610001: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
2020-07-17 12:00:37.611202: I tensorflow/core/common_runtime/dml/dml_device_factory.cc:32] DirectML: creating device on adapter 0 (Intel(R) HD Graphics 4600)
2020-07-17 12:00:37.619251: I tensorflow/stream_executor/platform/default/dso_loader.cc:60] Successfully opened dynamic library DirectMLba106a7c621ea741d2159d8708ee581c11918380.dll
2020-07-17 12:00:37.623759: I tensorflow/core/common_runtime/eager/execute.cc:571] Executing op MatMul in device /job:localhost/replica:0/task:0/device:DML:0
tf.Tensor(
[[22. 28.]
[49. 64.]], shape=(2, 2), dtype=float32)
But why?hd530 can works perfectly.

It does look like the workload might just be a little too much for the HD4600 to handle. Because it's an older GPU, it might not have enough power to handle training a large model without timing out. I believe the HD530 is a newer chip with more compute power, which would explain why it works but the HD4600 doesn't. You can try reducing the complexity of your model to try to get it to run on the HD4600, but it may be simpler to stick to using the HD530 if you have it available.

@wangyuddd000 We've released a new version tensorflow-directml 1.15.3.dev200911 which should address this. The timeout behavior has been adjusted to allow for larger and more complex models to run on older GPUs without timing out.


[RFR] Responsive UI

Make the Mobile interface usable.

[x] Sidebar
[x] AppBar
[x] Datagrid (introducing <SimpleList> and <Responsive> components)
[x] Actions
[x] Pagination

Switching to RFR

I do not understand the "const isMobile = width === 1;" everywhere ?

@JulienDemangeon It's a material ui constant


Optimize simple exprs

Draft

asm_gen tests are currently failing. I just wanted to get the PR up so @mohammadfawaz could take a look at it

This PR optimizes BinaryOp exprs by folding any const exprs
Ex. var c = (1 + 2) - 3 + 4 - (2 - 5); becomes constraint (::c == 7);

@mohammadfawaz
The original goal of this PR was:
constraint x + 1 + 2 == 4;
should become
constraint x + 3 == 4

technically this is the case
constraint (::c == ((((1 + 2) - 3) + 4) - (2 - 5)));
becomes
constraint (::c == 7);

I don't think this was the spirit of the issue though. I think we wanted
Predicate Test {
    var x: int;
    constraint x + 1 + 2 == 4;
}

to result in

constraint ((::x + 3) == 4)

but unfortunately the flattened version of the constraint is constraint (((::x + 1) + 2) == 4); So when running over exprs() and evaluating immediates, there is nothing to simplify. (x + 1) would not be changed and then we're left with the original (x + 1) + 2 expr.
I spent a good while looking at how I could simplify consts that were next to each other but not in the same ast node, and didn't come up with a good solution.
Let me know if you have any ideas or if I'm overthinking this.

I spent a good while looking at how I could simplify consts that were next to each other but not in the same ast node, and didn't come up with a good solution.

This is actually not that simple.. don't worry about it for now. We'll open a separate issue to handle it.


Expo Version<EMAIL_ADDRESS>

Description
The current Expo Version in the SDK is ^49.0.16 within the script.
However, the latest Expo Version is<EMAIL_ADDRESS>Can we get this updated?
 ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/expo
npm ERR!   peer expo@"" from<EMAIL_ADDRESS>npm ERR!   node_modules/expo-application
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/expo-auth-session
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer expo@"*" from<EMAIL_ADDRESS>npm ERR!   node_modules/expo-asset
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   14 more (expo-camera, expo-constants, expo-contacts, expo-crypto, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@hashgraph/sdk
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/expo
npm ERR!   peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@hashgraph/sdk
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
Hedera network
other
Version
v2.47.0
Operating system
Windows

After some discussion with @rubixvi , we found out that bumping the expo version might not solve their issue. The following text and code is a followup from them.
Code snippets
import { AccountId, Client, TransferTransaction, Hbar } from '@hashgraph/sdk';

const client = Client.forTestnet().setOperator(
process.env.EXPO_PUBLIC_ACCOUNT_ID ?? '',
process.env.EXPO_PUBLIC_PRIVATE_KEY ?? ''
);

const confirmTransaction = async () => {
setModalVisible(false);
try {
const sanitizedRecipientId = sanitizeRecipientId(recipientId);
const sanitizedAmount = sanitizeAmount(amount);
const sanitizedMemo = sanitizeMemo(memo);
const hbarAmount = Number(sanitizedAmount);

  if (isNaN(hbarAmount) || hbarAmount <= 0) {
    setAlertType('error');
    setAlertMessage('Invalid amount. Please enter a valid number.');
    return;
  }

  if (sanitizedRecipientId === accountId) {
    setAlertType('error');
    setAlertMessage('Please check the payment address.');
    return;
  }

const transaction = await new TransferTransaction()
  .addHbarTransfer(accountId, Hbar.fromTinybars(-hbarAmount * 100000000))  // Convert HBAR to tinybars
  .addHbarTransfer(sanitizedRecipientId, Hbar.fromTinybars(hbarAmount * 100000000))
  .setTransactionMemo(sanitizedMemo)
  .execute(client);

const receipt = await transaction.getReceipt(client);
const status = receipt.status;

if (status.toString() === 'SUCCESS') {
  setAlertType('success');
  setAlertMessage('Sending Complete');
  setReceiptNumber(transaction.transactionId.toString());
  clearInputs();
} else {
  setAlertType('error');
  setAlertMessage('Sending Failed');
}
} catch (error) {
setAlertType('error');
setAlertMessage('Sending Failed');
console.error('Error during transaction:', error);
}
};

package.json:
"dependencies": {
"@ethersproject/shims": "^5.7.0",
"@expo/vector-icons": "^14.0.2",
"@hashgraph/sdk": "^2.26.0",
"@react-native-async-storage/async-storage": "^1.24.0",
"@react-native-picker/picker": "^2.7.7",
"@react-navigation/native": "^6.0.2",
"axios": "^1.7.2",
"expo": "~51.0.20",
"expo-camera": "^15.0.13",
"expo-clipboard": "~6.0.3",
"expo-crypto": "~13.0.2",
"expo-font": "~12.0.8",
"expo-local-authentication": "~14.0.1",
"expo-optimize": "^0.2.20",
"expo-print": "^13.0.1",
"expo-random": "^14.0.1",
"expo-router": "~3.5.18",
"expo-secure-store": "~13.0.2",
"expo-sharing": "^12.0.1",
"expo-splash-screen": "~0.27.5",
"expo-status-bar": "~1.12.1",
"expo-web-browser": "~13.0.3",
"long": "^5.2.3",
"react": "^18.3.1",
"react-dom": "^18.3.1",
"react-native": "^0.74.3",
"react-native-get-random-values": "^1.11.0",
"react-native-modal-datetime-picker": "^17.1.0",
"react-native-svg": "^15.4.0",
"react-native-web": "^0.19.12",
"react-qr-code": "^2.0.15"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"@types/react": "^18.3.3",
"@types/react-native": "^0.73.0",
"@types/react-test-renderer": "^18.0.7",
"eslint": "^9.7.0",
"eslint-config-expo": "^7.0.0",
"metro-minify-terser": "^0.80.9",
"postcss-loader": "^8.1.1",
"react-native-svg-transformer": "^1.4.0",
"react-test-renderer": "^18.3.1",
"ts-node": "^10.9.2",
"typescript": "^5.5.3"
},

Running a buffer:
import { Buffer } from "buffer";

globalThis.Buffer = Buffer;

Layout:
import "react-native-get-random-values"
import "./shims-buffer";
import '@ethersproject/shims';

Error

ERROR Error during transaction: [Error: Not a valid base64 encoded string length]

Hello @rubixvi,
Can I please have the code for sanitizeRecipientId, sanitizeAmount and sanitizeMemo as the current ongoing theory in the team is that your problem might be because of the stuff that's happening inside sanitizeMemo.

const sanitizeRecipientId = (input: string): string => {
return input.replace(/[^a-zA-Z0-9.]/g, '');
};
const sanitizeAmount = (input: string): string => {
return input.replace(/[^0-9.]/g, '');
};
const sanitizeMemo = (input: string): string => {
return input.replace(/[^a-zA-Z0-9\s-.]/g, '');
};
Just a simple script to prevent the wrong inputs.

Hello, @rubixvi.
We managed to reproduce your issue on Android using Android Studio's emulator. iOS was working fine. As you said the web version does not have this problem neither. After some investigation we found out that altho expo shows an error with atob's base64 length but the transaction still passes and the transaction receipt shows status code: 22. Which means the transaction was successful. This can be confirmed from hashscan too - https://hashscan.io/testnet/transaction/1721299020.763775003.
or by running this code:
      const response = await new AccountCreateTransaction()
        .setKey(privateKey)
        .execute(client);

      const receipt = await response.getReceipt(client);

Thank you for your code snippets for the sanitisation methods you useI asked you for the sanitisation methods because I wanted to be sure that there isn't some base64 encoding that you were doing to the memo. I tested that but this wasn't the issue as I tried running the script without any sanitisation and it was still throwing an error in Android environment.
We also tried to deserialise and serialise it back. For two reasons:

Wondering if there was some issue with Android converting the transaction to bytes as it uses base64 in some places but this was not the case.
Sending the transaction data to the RPC was the last place the code went in the SDK before the base64 error was thrown.

const response = await new AccountCreateTransaction()
        .setKey(privateKey)
        .toBytes();

      Transaction.fromBytes(response).execute(client);

The following code didn't throw an error and correctly deserialised the transaction with expected data.
Our current theory is that there is some issue with expo's newest version so we will be making an issue in their repository.
Thank you for raising this issue. Will keep you updated if there's some response from expo.

Thanks, glad that's all cleared up,
Looks like we'll just to wait for their response.
Atleast it wasn't my coding.


docs: whitelist api model classes

Pull Request
Changes
Keep only the relevant classes in the api_model.md.
Why this change?
Have the documentation not cluttered with classes that are of absolute no-use in mostlyai-client.
Testing
How was the change tested?
Additional Notes
Any additional information or context you want to provide?

It is possible to provide exclusion patterns via
::: mostlyai.client.model
    options:
      filters:
        - "!^Assistant.*"
        - "!^Share.*"
        - "!^LiteLlm.*"
        - "!^DataLlm.*"
        - "!.*PatchConfig.*"
        - "!.*CloneConfig.*"
        - "!.*CloneConfig.*"

we will leverage that as part of a separate PR


Offer to automatically send crash reports

There is a library somewhere on github to assist with this.

This seems very promising:
https://github.com/TheRealKerni/QuincyKit

That looks perfect.  Work it into the rewrite, I'll add it to version 1.
On Nov 8, 2011, at 5:56 PM, David Jennes wrote:

This seems very promising:
https://github.com/TheRealKerni/QuincyKit

Reply to this email directly or view it on GitHub:
https://github.com/dustinrue/ControlPlane/issues/78#issuecomment-2675639

Sure, but we'll need server support for the fancy stuff (see http://quincykit.net/)

Meh, wrangling servers is my day job :)
On Nov 8, 2011, at 5:58 PM, David Jennes wrote:

Sure, but we'll need server support for the fancy stuff (see http://quincykit.net/)

Reply to this email directly or view it on GitHub:
https://github.com/dustinrue/ControlPlane/issues/78#issuecomment-2675666

This is complete in v1 as well


[Backend API] Add internal auth

Auth between web app and API app

Pass pre-defined API key from web app to api app

Not relevant

Only for internal auth

#174
#175
#176
#177


Fix objc_bridging_test on non-osx platforms.

Fix objc_bridging_test on non-osx platforms.
rdar://problem/30559806

@swift-ci Please test and merge

@swift-ci Please test and merge

@swift-ci Please test and merge

Why do some architectures affirmatively check for [[BORROWED_FOO_OBJ]] and others simply allow {{%.*}}?

@gparker42 That is why the testing missed this.

@gparker42 That is why the OS X tests didn't catch the failure. I can normalize it. 1 sec.

@swift-ci Please test

@gparker42 Hows that look?

Still lax in CHECK-ios-i386-LABEL: sil hidden @_TF13objc_bridging6setZim and `CHECK-macosx-x86_64-LABEL: sil hidden @_TF13objc_bridging6setZim

@gparker42 Are you talking about matching the full name of the function? What is happening there is that the writer is trying to avoid adding the parameter type mangling to the name so that if the parameters change the value is still safe. That is common SILGen practice...
Or are you talking about something else?

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 1d9755c3188dc1410aeb0476a66d3fc84d052dda
Test requested by - @gottesmm

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 1d9755c3188dc1410aeb0476a66d3fc84d052dda
Test requested by - @gottesmm

@swift-ci Please test

@swift-ci Please test

@gparker42 I believe that I fixed what you asked me to fix.  Lets do any further feedback with post-commit review if necessary. I want to move on from this.


Independent Components

Hello,
It seems many binary masks generated by SAM2 are topological disconnected. Is there a way to get separate components using SAM2 or we have to write our own processing function?
Thans

Hi @shersoni610, if you need to further get independent components from the SAM 2 output masks, you can use either

the get_connected_components function, which directly works with GPU which requires building the SAM 2 CUDA extension (it's adapted from cc_torch)
external libraries like cv2.connectedComponentsWithStats or scipy.ndimage.label or skimage.measure.label


GooglePay 2 - Required member supportedMethods is undefined error on setup

General information

SDK version: 3.42
Environment: Sandbox
Browser and OS : Chrome Latest - Windows

Issue description
Ok - so this issue was several pages long a minute ago, but I narrowed everything down and it seems that the issue actually lies with GooglePay rather than Braintree.
I thought (very reasonably) that when updating to GooglePay version 2 that I was doing something wrong, but I don't believe that's the case.
Good news:

The GooglePay sheet opens up in Chrome and lets me select a payment.
I get a nonce back just fine.
I can mark this script as 'blackboxed' to avoid the error with Javascript console open. However based on the URL below it very much looks like it is subject to change.

So I am simply running this:
    const paymentsClient = new google.payments.api.PaymentsClient({environment: 'TEST'});

And here's the error I get:
TypeError: Failed to construct 'PaymentRequest': required member supportedMethods is undefined

"TypeError: Failed to construct 'PaymentRequest': required member supportedMethods is undefined.
at iF (https://www.gstatic.com//mss/boq-payments-consumer//js/k=boq-payments-consumer.InstantbuyFrontendBuyflowPayframeUi.en.B4YMOoaV5dY.O/ck=boq-payments-consumer.InstantbuyFrontendBuyflowPayframeUi.yeoIDllFnqE.L.W.O/rt=j/d=1/exm=_b,_tp,wmwg8b/excm=payframeview,_b,_tp/ed=1/rs=AMitfrhArRyDDDQ2l6GVoUbdibtA08eTig/m=Das5Le,IZT63,PrPYRd,Ru0Pgb,Y2UGcc,ZyYHPb,hc6Ubd,p8L0ob,wI7Sfc,ws9Tlc:232:89)

This error is coming from the following URL (modified a few random characters in case this represents my wallet!):
https://www.gstatic.com/_/mss/boq-payments-consumer/_/js/k=boq-payments-consumer.InstantbuyFrontendBuyflowPayframeUi.en.B5YMOpaV5dWY.O/rt=j/d=1/excm=payframeview,_b,_tp/ed=1/dg=0/rs=BPitfrhOz_WaLIWMcqt9C6ZEKFcXSk9SKh/m=_b,_tp
I am able to duplicate it error with the absolute minimal page here, and even when adding further code from Google's own sample code I still get the same error:

<!doctype html>
<html lang="en">
<head>

    <script src="https://pay.google.com/gp/p/js/pay.js"></script>

    <script>
        const paymentsClient = new google.payments.api.PaymentsClient({environment: 'TEST'});

    </script>
<body>

Run this page in javascript debugger mode

</body>
</html>

So I suspect this is a temporary Google bug - but if there's some way to pass in the 'missing' supportedMethods and avoid this error I'd love to know how.
In any case I wanted this to be here because others will likely be having this same issue whether temporary or not - and assuming it's BT and not Google at fault.

I can't reproduce the problem you are seeing (and like you said, there's absolutely no Braintree code involved in this). I'd try running it in incognito mode in case you have a browser extension that is causing issues. If you're still having issues after that, contact Google.


fix: adjust where grafana password is stored for kubeconfig deploys

Proposed changes
This minor change updates where the kubeconfig deployments store the prometheus/grafana password; it is now
stored in the secrets project, not the main project configuration.
Closes #204
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[X] I have written my commit messages in the Conventional Commits format.
[X] I have read the CONTRIBUTING doc
[X] I have added tests (when possible) that prove my fix is effective or that my feature works
[X] I have checked that all unit tests pass after adding my changes
[X] I have updated necessary documentation
[ X I have rebased my branch onto master
[X] I will ensure my PR is targeting the master branch and pulling from my branch from my own fork

I'm not sure why the runner tests are failing, as they are running fine for me on these platforms locally. Going to merge and move on to the next bug; will come back to this if it persists.


Running HA Rabbit in K8s causes duplicate or more emails

Describe the bug
When running RabbitMQ in HA in kubernetes (3 pods), emails are duplicated and maybe even more than duplicated
To Reproduce
Run RabbitMQ HA
Expected behaviour
Rabbit to be highly available in case one pod goes down Postal can still connect
Screenshots
Here's a screenshot of before/after me scaling down to only 1 Rabbit, note the messages per minute

Can someone explain this behavior?

as mentioned in https://github.com/postalserver/postal/discussions/2103, I'm not sure how you load balance amongst instances of RabbitMQ but I imagine your setup was somehow taking input from several queues simultaneously leading to the duplication. I don't know enough about RabbitMQ or Ruby on Rails to know how to fix off the top of my head but definitely something worth addressing in documentation if not in code.

I'm going to close this ticket because Rabbit will be removed in Postal v3 so any Rabbit related issues will be best resolved by upgrading once that version is stable.


{tor,mullvad}-browser: 13.0.9 -> 13.0.10

Description of changes
https://blog.torproject.org/new-release-tor-browser-13010/
https://github.com/mullvad/mullvad-browser/releases/tag/13.0.10

This version includes important security updates to Firefox.
This release updates Firefox to 115.8.0esr, OpenSSL to 3.0.13, zlib to 1.3.1, and Snowflake to 2.9.0. It also includes various bug fixes (see changelog for details).

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 290234 run on x86_64-linux 1

2 packages built:

mullvad-browser
tor-browser

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/1016/99

@marsam could you take a look at the backport PR as well?
https://github.com/NixOS/nixpkgs/pull/290241


Use context to pass down redux and use decorators on smart components

Love the ideas with redux.  I haven't been able to dig into the actually code, but the API was bothering me a little so I've been play with some ideas.  Think context and ES7 Decorators make for a better interface.  Here are some code snippets demonstrating it.
Smart component would look like:
import autobind from 'autobind-decorator'

@autobind
@Redux
export default class CounterApp extends React.Component {
  render() {
    return (
      ...
     )
  }

  decrement() {
    this.dispatchAction(CounterActions.decrement);
  }

  increment() {
    this.dispatchAction(CounterActions.decrement);
  }
}

Redux mixin would look like:
export function Redux(Component) {
  Component.contextTypes = {
    dispatch: React.PropTypes.func.isRequired
  }

  Component.prototype.dispatchAction = function(action) {
    this.context.dispatch(action)
  }

  return Component
}

Redux Component and loading CounterApp
import autobind from 'autobind-decorator'

@autobind
class Redux extends React.Component {
  constructor() {
    this.state = {}
  }

  getChildContext() {
    return {
      dispatch: this.dispatch
    }
  }

  dispatch(action) {
    ...
  }

  render() {
    return React.cloneElement(this.props.children, this.state);
  }
}

Redux.childContextTypes = {
  dispatch: React.PropTypes.func
}

// Only allow one element on children
Redux.propTypes = {
  children: React.PropTypes.element.isRequired
}

ReactDOM.render(<Redux><CounterApp /></Redux>, document.body);

I agree that the API is a little awkward as is. Evaluating only the API itself, this looks fantastic.

The current API is designed to encourage best React practices by forcing you to pass action creators down as props.  Following best practices, you should pass down this.decrement and this.increment as props to child dumb components so they can use them as event handlers. Once you've done that, you'll have written more lines of code that you would with the current API, which is optimized for the smart vs dumb component pattern.

I'm not too fond of the current <Provider> and <Connector> API.
If you have better ideas please chime in here: https://github.com/gaearon/react-redux/issues/1

@acdlite This is not meant to be a demo of "best practices", only a demo of a slightly different API for redux. My goals are to remove the need for Provider, Connector, and the "callback render".  Which is accomplished by using context.

@cgarvis If I'm not mistaken, you're proposing a new API to replace the current once. I'm telling you why this particular proposal isn't likely to be accepted :)
Let's move further discussion over to this thread https://github.com/gaearon/react-redux/issues/1


Duration fix breaks time

The duration fix:
ignore.append('_pytest')

seems to prevent freezegun from freezing time when a marker is set.
I've added some tests to demonstrate this here:
https://github.com/radiac/pytest-freezegun/commit/fec97f71716dd8042af2d53e61a311142b617d75

The fix should be in the 0.4.1 release.


When using array of hotkeys, it would be nice to show them all on the cheat sheet

Refs #15

If I had seen the list of PRs before I'd know that there are 3 pending PRs  (#98, #123, #126) for this same feature and wouldn't create this issue. Sorry.
Well, I'm using my solution for a personal project, but I hope you merge some of the PRs so we can use an official release.
Can you please close this issue?


If a feature is usable but missing additional options, could we call the feature Baseline?

(I was not sure where to post this question, please close this if it is not a fit for web-features repo)
I am looking at Conic Gradient which is available on cross browsers.
However, looking at MDN Browser compatibility table, Hue interpolation method and Interpolation color space are not yet supported on Firefox, this means the feature is usable but limited way to use them (than what is in spec).
In those case, could we call this a Baseline feature or should we wait until all implementation is complete with what is in speck??

I run into same thing (partially missing support within bigger "feature") in color-scheme (https://developer.mozilla.org/en-US/docs/Web/CSS/color-scheme)
This feature is very much cross browser supported to support dark mode (which is the main use case, I assume) but still missing cross browser support for only light keyword.

In BCD we would either have a note on the feature, or add a subfeature for the missing parts which are not supported. For web-features, I think the choice is similar. If the feature is useful on its own, then define "conic gradient without hue interpolation or interpolation color space" as the main feature, and add subfeatures for the remaining parts.
Unlike BCD, I think we should also sunset subfeatures like that when they're far enough in the past.
There are no obvious answers here, these are just my initial thoughts. cc @ddbeck


WIP

Codecov Report

Merging #165 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #165   +/-   ##
=======================================
  Coverage   66.94%   66.94%
=======================================
  Files          30       30
  Lines        2959     2959
=======================================
  Hits         1981     1981
  Misses        791      791
  Partials      187      187

Continue to review full report at Codecov.

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

:wave: @drewvanstone @br-lewis @makkes @bamarni @rgo3  Can you review, please?


Using mat-tabs with ngFor, Initializing component twice

Example -
https://stackblitz.com/edit/components-issue-otvvf6
html of main component have -
```
<mat-tab-group [(selectedIndex)]="selectedTabIndex" (selectedTabChange)="onTabSelect($event)">             <mat-tab [label]="tab.value.title" *ngFor="let tab of tabs | keyvalue">                 <ng-template matTabContent>                     <div *ngIf="(if user tab index selected show active users)">                         <active-users></active-users>                     </div>                 </ng-template>             </mat-tab>         </mat-tab-group>

#### Expected Behavior
It should initialize the user component on the selection of user tab only once.

#### Actual Behavior
But when I select user tab it initialize its component twice.

#### Environment
- Angular: 7
- CDK/Material: 8.0.1
- Browser(s): Chrome v75
- Operating System (e.g. Windows, macOS, Ubuntu): Windows/Ubuntu

Please create stackblitz for that, it’s hard to help you without an example.

https://stackblitz.com/edit/components-issue-otvvf6

Please create stackblitz for that, it’s hard to help you without an example.

https://stackblitz.com/edit/components-issue-otvvf6

You can see a solution on this stackblitz example.
Basically only difference with your example is that I’m using tab index value that is calculated in ngFor, instead of fixed value like you are doing.


255 GitHub actions migration

Description:
Migrate to github actions
Related issue(s):
Fixes #255
Notes for reviewer:
Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

You should add the SonarCloud GitHub app to the project so that it can comment in PRs with its report.

@steven-sheehy I think I need an admin of the org level to update settings on either github or sonarqube to do that - https://docs.sonarqube.org/latest/analysis/github-integration/
I added the needed stuff to the pipeline and it doesn't seem to be connecting.

Can reach out to Mark in IT for that.

I think this is ready for merge.


Argument of type 'Repository' is not assignable to parameter of type 'Repository & Repository<ProductReview

While building the project I am getting errors regarding the product review services.
                                                                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

src/services/product-review.ts:23:72 - error TS2345: Argument of type 'Repository<ProductReview>' is not assignable to parameter of type 'Repository<any> & Repository<ProductReview | { product_id?: string; product?: DeepPartial<Product>; customer_id?: string; customer?: DeepPartial<Customer>; ... 6 more ...; updated_at?: DeepPartial<...>; }>'.

every line which this.productReviewRepository_ is used in the file src/services/product-review.ts is throwing this error

If you are building yourself, are you familiar with the build procedures for medusa plugins?  You have to yarn link the peer dependencies.
If you need to make customizations, you will probably find it easier to copy the code from src into your medusa project src folder rather than rebuilding the plugin.


Estelle/Arb Math Portfolio

Closes #231. This is still a work in progress but contains an abstraction of the pool parameterization so we have less hard coding instances, and currently stands at just the arb amount calculation for the x reserve. Working on the y reserve next.

lmao i forgot to put this as a draft. Not sure how to convert from here tbh

Converted to draft for you.

How are things going on this front? Do you need any help? I see you cruising :)


Ingest MONDO

Name of the dataset
MONDO disease ontology
Mapping or relevant fields
Probably should ingest this obojson:
http://purl.obolibrary.org/obo/mondo.json
We need disease IDs and also axioms that link to HPO phenotypes
Similar ingest to #48

@justaddcoffee I am going to take this one since I am already in the realm of ontologies with GO.

I think we might need equivalence axioms to other disease ontologies, since drug indications might reference these instead of MONDO

@justaddcoffee I am going to take this one since I am already in the realm of ontologies with GO.

Great, go for it @deepakunni3

closed by #100


add rez-maintainers as codeowners

Signed-off-by: Stephen Mackenzie<EMAIL_ADDRESS>

I'm leaving @nerdvegas on the list separately as a backup to see how marking the group rather than individuals works, in case something is wrong with that (though the docs indicate it should work)

@maxnbk could we simplify the file and just make the whole TSC the owner of all files?

@maxnbk could we simplify the file and just make the whole TSC the owner of all files?

Maybe? But the separation may become useful later if we decide that not everyone wants to see every kind of PR, or that maybe a specific team is in charge of, say, the solver. I'll keep the update to a group ownership update for now, and check to see if we can collapse it as a separate one, because my main concern here is that each TSC member approves being added to every PR by default, and then moving on from there if there is an objection.

Alright, make sense. I approved and merged since everybody approved.
Thanks @maxnbk !


Ability to specify cordova plugin versions

Hi, I haven't found a way to pin down a specific plugin version with $ ionic state save or $ ionic plugin add
I believe this is a real necessity in order to have reproducible builds on different machines at different times. Any plans to support this? Is it already implemented, but not documented?
Thanks.

if you add do ionic plugin add com.myplugin.www it will save the plugin to the confix.xml file

Greetings @fabiosussetto!
I've closed this issue because my sensors indicated it was old and inactive, and may have already been fixed in recent versions of Ionic. However, if you are still experiencing this issue, please feel free to reopen this issue by creating a new one, and include any examples and other necessary information, so that we can look into it further.
Thank you for allowing me to assist you.


Green ffplay window instead of the camera's feed

Describe the bug
Using ffplay to show the video on the webcam, the video feed is green.
To Reproduce
Steps to reproduce the behavior:
Executing the command ffplay rtsp://<IP_ADDRESS>:8554/unicast  to start the RTSP server on the webcam
./v4l2rtspserver
log level:500

[NOTICE] /home/hil/git/v4l2rtspserver/main.cpp:269
	Version: 0.3.8 live555 version:2023.11.30
[NOTICE] /home/hil/git/v4l2rtspserver/src/V4l2RTSPServer.cpp:37
	Create V4L2 Source.../dev/video0
[NOTICE] /home/hil/git/v4l2rtspserver/libv4l2cpp/src/V4l2Device.cpp:133
	driver:uvcvideo capabilities:84a00001 mandatory:4000001
[NOTICE] /home/hil/git/v4l2rtspserver/libv4l2cpp/src/V4l2Device.cpp:136
	/dev/video0 support capture
[NOTICE] /home/hil/git/v4l2rtspserver/libv4l2cpp/src/V4l2Device.cpp:139
	/dev/video0 support streaming
[ERROR] /home/hil/git/v4l2rtspserver/libv4l2cpp/src/V4l2Device.cpp:212
	/dev/video0: Cannot set pixelformat to:H264 format is:MJPG
[NOTICE] /home/hil/git/v4l2rtspserver/libv4l2cpp/src/V4l2Device.cpp:225
	/dev/video0:MJPG size:1920x1080 bufferSize:4177920
[NOTICE] /home/hil/git/v4l2rtspserver/libv4l2cpp/src/V4l2Device.cpp:246
	fps:1/30
[NOTICE] /home/hil/git/v4l2rtspserver/libv4l2cpp/src/V4l2Device.cpp:247
	nbBuffer:0
[NOTICE] /home/hil/git/v4l2rtspserver/libv4l2cpp/src/V4l2MmapDevice.cpp:49
	Device /dev/video0
[NOTICE] /home/hil/git/v4l2rtspserver/libv4l2cpp/src/V4l2MmapDevice.cpp:73
	Device /dev/video0 nb buffer:10
[NOTICE] /home/hil/git/v4l2rtspserver/src/V4l2RTSPServer.cpp:62
	Create Source .../dev/video0
[NOTICE] /home/hil/git/v4l2rtspserver/inc/BaseServerMediaSubsession.h:49
	format:video/JPEG
[NOTICE] /home/hil/git/v4l2rtspserver/inc/V4l2RTSPServer.h:240
	Play this stream using the URL "rtsp://<IP_ADDRESS>:8554/unicast"
[NOTICE] /home/hil/git/v4l2rtspserver/src/V4L2DeviceSource.cpp:96
handleCmd_SETUP:SETUP rtsp://<IP_ADDRESS>:8554/unicast/track1 RTSP/1.0
Transport: RTP/AVP/UDP;unicast;client_port=12660-12661
CSeq: 3
User-Agent: Lavf60.3.100

^C	begin threadSIGINT

[NOTICE] /home/hil/git/v4l2rtspserver/main.cpp:357

observe the video feed window:

Expected behavior
Normal video feed shows on Logitech, Inc. Logitech Webcam C925e on a different PC using the same method to build and execute.
Desktop (please complete the following information):

Ubuntu 23.10 running on AMD Ryzen 7700x.

Hi,
Maybe increasing log level will help you to get more information.
Best Regards,
Michel.

I think the webcam is not supported. I tried https://kaustavmukherjee-66179.medium.com/convert-any-webcam-into-ipcam-in-2-minutes-using-rtsp-server-and-ffmpeg-a27414f08af5 and had similar failures.

Hi,
This may depends on q field and quantification tables (see https://www.rfc-editor.org/rfc/rfc2435#appendix-A). q field is not decoded, code suppose quantification table are sent.
Best Regards,
Michel.


No JupyterLab 3.x support

As of v0.20.0, this library supports JupyterLab 2.x releases, but many users have moved to version 3 of JupyterLab and others will move soon. Additionally, JupyterLab 3 has a much easier model for supporting extensions (without requiring the jupyter lab build step).

v0.22.0 is now released with JupyterLab 3.x support.


confirmations field in Transaction struct.

Possible to add confirmations field that comes from getrawtransaction rpc call in the Transaction struct.
It doesn't have it currently, I can raise a PR for this.

No, because the confirmations field is a property of the entire blockchain, not of a single transaction. There is no way to serialize or unserialize it.

For interacting with bitcoincore RPC, you can use rust-bitcoincore-rpc crate. For example, this field has GetRawTransactionResult that you need.


fix(nexus/io): set nvmf subsystem as frozen

Multiple children may be retired at "the same time". In case the first retires "wins" and pauses the subsystem, if we simply leave it paused at the end, the other retires will remain stuck in the pause.
Instead, introduce a new state of Frozen, which allows other pauses to execute their paused code and at the end the subsystem remains frozen.

bors merge


The fltk::dialog::message window has no title

The fltk::dialog::message window has no title, nor does the API allow the user to set a title.
Ideally the user should be able to specify a title as well as the message text.
https://docs.rs/fltk/1.2.17/fltk/dialog/fn.message.html

These just call fl_message(…) which doesn’t have a title field. FLTK allows customizing the dialog’s title via another function, fl_message_title which isn’t currently exposed in fltk-rs, but I’ll add it this evening. The api should look like:
dialog::message_title("some title");
dialog::message(args…); // works for alert, choice etc.

There’s also an fl_message_default_title(), which allows setting the title only once.
Ideally though, especially for apps with their own styling, a user defined dialog window should be preferable. Something like:
https://gist.github.com/MoAlyousef/ce50902cb7929760b89af60b3702fc1d

I tried the example on gist that you gave.

When I run it on Linux, if I click "Click" and enter the text say, "aaa" and then after clicking "Ok" the "aaa" shows up correctly in the frame. However, if I then repeat the process but with new text, say "WWW", the frame shows the new text on top of the old text! This is even more apparent if you do it a third time with longer text.

Usually when I show a modal dialog like this I like to delete it after use, but this one is only hidden. Is it possible to delete when ok is clicked? I tried changing the ok.set_callback() to use win.delete(), win::.delete() and app::delete_widget(win), but all of them produced errors.

Thanks for your help.

I've added dialog::message_title() and message_title_default().
1- I've also fixed the gist, it was because of the frame's FrameType (which I've changed, another option was to call redraw in the button's callback).
2- Closing an FLTK window destroys it and its children. When you call show_dialog() (in the gist) again on it, it respawns a new window and new children.

I've now switched to using the lastest rust-rs using git in my Cargo.toml so I've tried dialog::message_title_default() and it works great. (I'll also try message_title().)
I applied your changes to my version of your dialog example and now it all works fine.
For modal dialogs I like to create/pop-up/retrieve OK/Cancel and any data/delete.
But unfortunately I cannot find a way to delete. The delete must be done in the callback to allow for the retrieval of data before deletion, but I can't get it to work:
    btn.set_callback(move |_| {
        let dlg = show_dialog();
        frame.set_label(&dlg.value());
        //app::delete_widget(dlg);
        //window::Window::delete(dlg);
    });

The first commented out line if uncommented produces:
the trait fltk::prelude::WidgetBaseis not implemented forMyDialog, and the second produces: `expected struct `DoubleWindow`, found struct `MyDialog
Thanks for your help!

You can expose the window as a field of the MyDialog:
pub struct MyDialog {
    win: window::Window,
    inp: input::Input,
}

Then you can call either window::Window::delete(dlg.win); or app::delete_widget(dlg.win);
Another option is to implement the Drop trait on the MyDialog, and call the deleter there.

I followed your advice adding the window to the MyDialog struct and I used app::delete_widget(dlg.win) in the callback. Thank you.
I think you've now changed fltk-rs's behavior. The dialog now seems to have the parent window's title (label) "My Dialog". However neither dialog::message_title() nor dialog::message_title_default() seem to be able to override it.
I've attached my edited main.rs which I had to gzip to make it work on github
main.rs.gz
.

This is a custom dialog, so it wouldn't respond to dialog::message_title(). You can specify whatever you want in the constructor and show_dialog function:
use fltk::{
    app, button,
    enums::{Color, Font, FrameType},
    frame, group, input,
    prelude::*,
    window,
};

fn style_button(btn: &mut button::Button) {
    btn.set_color(Color::Cyan);
    btn.set_frame(FrameType::RFlatBox);
    btn.clear_visible_focus();
}

pub fn show_dialog(title: &str) -> MyDialog {
    MyDialog::new(title)
}

pub struct MyDialog {
    window: window::Window,
    input: input::Input,
}

impl MyDialog {
    pub fn new(title: &str) -> Self {
        let mut win = window::Window::default()
            .with_size(400, 100)
            .with_label(title);
        win.set_color(Color::from_rgb(240, 240, 240));
        let mut pack = group::Pack::default()
            .with_size(300, 30)
            .center_of_parent()
            .with_type(group::PackType::Horizontal);
        pack.set_spacing(20);
        frame::Frame::default()
            .with_size(80, 0)
            .with_label("Enter name:");
        let mut input = input::Input::default().with_size(100, 0);
        input.set_frame(FrameType::FlatBox);
        let mut ok =
            button::Button::default().with_size(80, 0).with_label("Ok");
        style_button(&mut ok);
        pack.end();
        win.end();
        win.make_modal(true);
        win.show();
        ok.set_callback({
            let mut win = win.clone();
            move |_| {
                win.hide();
            }
        });
        while win.shown() {
            app::wait();
        }
        Self { window: win, input }
    }
    pub fn value(&self) -> String {
        self.input.value()
    }
}

fn main() {
    let a = app::App::default();
    app::set_font(Font::Times);
    app::set_screen_scale(0, 1.2);
    let mut win = window::Window::default()
        .with_size(600, 400)
        .with_label("My App");
    win.set_color(Color::from_rgb(240, 240, 240));
    let mut btn = button::Button::default()
        .with_size(80, 30)
        .with_label("Click")
        .center_of_parent();
    style_button(&mut btn);
    let mut frame = frame::Frame::new(
        btn.x() - 40,
        btn.y() - 100,
        btn.w() + 80,
        30,
        None,
    );
    frame.set_frame(FrameType::BorderBox);
    frame.set_color(Color::Red.inactive());
    win.end();
    win.show();
    btn.set_callback(move |_| {
        let dlg = show_dialog("Whatever title!");
        frame.set_label(&dlg.value());
        app::delete_widget(dlg.window);
    });
    a.run().unwrap();
}

Here it just takes the title of the dialog

I'm very sorry for that silly mistake!
Here's possibly another one. Out of interest and because I think it would be cleaner I tried implementing the Drop trait (and of course remove the delete_widget() call from the callback):
impl Drop for MyDialog {
    fn drop(&mut self) {
        println!("### Dropping MyDialog");
        //app::delete_widget(self.window);
        window::Window::delete(self.window);
    }
}

Neither of these works. I also tried &self.window and &mut self.window but without success.
I'm also reading through and trying out the rest of your examples, so may encounter a solution in the process.

You can use self.window.clone()
This doens't actually clone the window

Ah, I hadn't realised about clone() not cloning! Here's the code I ended up using:
impl Drop for MyDialog {
    fn drop(&mut self) {
        app::delete_widget(self.window.clone());
    }
}

It is much nicer than needing to explicitly delete (& I tested it with a println!() first).
Oh, and I tried out dialog::message_title() and dialog::message_title_default() and they both worked fine.
PS My rust is a bit rusty and this is the first time I've used FLTK (I've used Qt, wxWidgets, Tk, and others, so am used to GUI toolkits). I really like how I can build with the same source on Windows & Linux and how small the executables are.


CB-11772 Security vulnerability: Bind 8080, 8443 to localhost only

CB-11772 Security vulnerability: Bind 8080, 8443 to localhost only

This pullrequest is draft only, because I would like to test the Freeipa HA scenario and the Freeipa repair flows.


Bluetooth: audio: has: Fix client context allocation

The client context shall be allocated once paired i.e. encryption is
enabled. This fixes issue that client context was allocated only for
bonded devices and as a result the ATT Unlikely Error was replied to
Control Point operation that paired remote requested.
Signed-off-by: Mariusz Skamra<EMAIL_ADDRESS>

Hi @MariuszSkamra, your PR will need a linked bug report for me to merge it during the stabilization phase of 3.3. File and let me or @\ stephanosio know if that is the case ^_^


[request] Translatable messages

There are some hardcoded strings, such as:

Settings successfully updated
No settings fields have been defined.
Error

It would be nice to be able to translate them via .js files in resources/lang. I think there is some way to get __ as Vue helper, if not, you can easily reimplement it:
let __ = function (original) {
    let translated = window.config.translations[original];
    if (translated !== undefined) return translated;
    return original;
}

Added translations support in version 2.3.0. Good luck!


feat: init codeartifact repository

tried to rip off the existing codeartifact functionality from the related pulumi project, while extending fields to be more reusable.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Improve type checking across codebase

Adds the following TS configuration, in order to improve the libraries portability into other TS projects:

--noImplicitAny: Raise error on expressions and declarations with an implied any type.
--noImplicitReturns: Report error when not all code paths in function return a value.
--noImplicitThis: Raise error on this expressions with an implied any type.
--strictNullChecks: In strict null checking mode, the nulland undefined values are not in the domain of every type and are only assignable to themselves and any (the one exception being that undefined is also assignable to void).

NOTE: in a few q-related cases, explicit type casting was necessary. I haven't been able to dig far enough into why the code works but types are incorrect - either there is an issue with the code, or the types aren't quite correct (in particular, a q.Resolve(...) is not compatible with the PromiseLike interface).
Fixes #55.

Any thoughts @mboudreau or should we merge this in (no API compatibility changes).

@mefellows Ah, right, I'll look at this today.


Android artifacts. Get rid of publication of two artifacts ("debug" and "release")

Now we have two android artifacts:
org.jetbrains.compose.animation:animation-android:0.2.0-build124
org.jetbrains.compose.animation:animation-android-debug:0.2.0-build124
The need of "debug" artifact seems strange.
Figure out how to change MPP publication configuration so we can only publish "org.jetbrains.compose.animation:animation-android".

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


webhook is no work

Describe the bug
webhook is no work
To Reproduce
my docker-compose file
version: "3"
services:
ciao:
image: brotandgames/ciao
container_name: status_ciao
ports:
- '8090:3000'
environment:
- SECRET_KEY_BASE=seth
- TIME_ZONE=PRC
- BASIC_AUTH_USERNAME=xxxx
- BASIC_AUTH_PASSWORD=xxxxx
- CIAO_WEBHOOK_ENDPOINT_1=http://<IP_ADDRESS>:9000/wecomchan
- CIAO_WEBHOOK_PAYLOAD_1={"sendkey":"5660bcd256ba0012c41d3d6f22c17472","msg_type":"text","msg":"name{check_url} Status changed from (status_before) to (status_after)"}
- CIAO_LOG_LEVEL=DEBUG
volumes:
- ./data:/app/db/sqlite/

after do no work, fail site status, no WEBHOOK request send

Are you still having this problem? If so, could you please add logs from ciao?


[Suggestion] Move this repo to the PolyMC organization repos

If this happens, more people will be able to notice it

Ill do this soon but for now the project is still very early

bruh :skull:


Increase testing matrix.

Add 32-bit x86-Linux builds.
Add building with the nightly LLVM releases.  There are some regressions
since LLVM 8 that would have been caught by this that we can hopefully
fix in time for the LLVM 12 release.

This is great. With the LLVM nightlies changing independently of this, would it make sense / be possible to set up an automated build to be run e.g. weekly to test the latest releases?

Yes, I'd like to make this do a weekly run.

A fix for the failing case is under review:
https://reviews.llvm.org/D91874
Once this is merged and the LLVM nightly build is updated, I'll merge this.

I saw that Azure Pipelines recently added support for Linux ARM64 - would that make it easy to build and run the test for ARM 32 and 64 as well?
https://azure.microsoft.com/en-gb/updates/azure-devops-pipelines-introduces-support-for-linuxarm64/

Looks as if they've added Linux support for the pipelines agent (which basically means Arm Linux is now a supported platform for .NET Core), they haven't added hosted pipelines, so someone would need to stand up some Linux VMs to do that.  Using qemu user mode on x86 is probably easier.

New version is rebased on top of @ngrewe's changes, so tests every combination of:

32 / 64-bit
Debug / Release
libstdc++ / libc++ (this tests libsupc++ / lib++abi, the FreeBSD runners test the released and trunk versions of libcxxrt)
Clang 8 / Clang nightly build

Each of these runs takes about 1.5 minutes.  We get 10 runners for free with Azure Pipelines and are building 20 configurations (16 Linux, 4 Windows).  The longest Windows runs take almost 6 minutes and so the 16 Linux builds on the 6 other runners don't take much longer.  It looks as if the Azure jobs still complete faster than the Cirrus CI ones, so this isn't adding anything to our total time.
I'd like to add Arm builds with the tests in qemu user mode at some point.  That will definitely slow things down, but given the commit rate in this repo even a 15-30 minute delay for the last tests in a PR is probably fine.


fix: bug in late message handling for sliding window

fixes #1468

@yhl25 - we need to get this fixed before v1.2.0 release.


i can't contact quantopian.com web site, do you have some problems with server?

i can't contact quantopian.com web site, do you have some problems with server?
**
Dear Zipline Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment

Operating System: (Windows Version or $ uname --all)
Python Version: $ python --version
Python Bitness: $ python -c 'import math, sys;print(int(math.log(sys.maxsize + 1, 2) + 1))'
How did you install Zipline: (pip, conda, or other (please explain))
Python packages: $ pip freeze or $ conda list

Now that you know a little about me, let me tell you about the issue I am
having:
Description of Issue

What did you expect to happen?
What happened instead?

Here is how you can reproduce this issue on your machine:
Reproduction Steps

...
What steps have you taken to resolve this already?
...
Anything else?
...
Sincerely,
$ whoami

Hi, Quantopian shut down a month ago, so the website no longer works. The open-source libraries will live on in GitHub.


Fix: allow executing CopyCommand operations in parallel when it is set

Description
This PR fixes the CopyCommand execute in sequence issue observed in #5925
Fixes: #5925
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@blueorangutan package

@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 2501

@blueorangutan test matrix

Trillian test result (tid-3217)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 33816 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr5960-t3217-kvm-centos7.zip
Smoke tests completed. 92 look OK, 0 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

Trillian test result (tid-3216)
Environment: xenserver-71 (x2), Advanced Networking with Mgmt server 7
Total time taken: 36491 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr5960-t3216-xenserver-71.zip
Smoke tests completed. 91 look OK, 1 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_01_sys_vm_start
Failure
0.13
test_secondary_storage.py

Trillian test result (tid-3218)
Environment: vmware-65u2 (x2), Advanced Networking with Mgmt server 7
Total time taken: 37451 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr5960-t3218-vmware-65u2.zip
Smoke tests completed. 90 look OK, 2 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_01_offline_migrate_VM_and_root_volume
Error
91.06
test_vm_life_cycle.py

test_03_live_migrate_VM_with_two_data_disks
Error
61.44
test_vm_life_cycle.py

ContextSuite context=TestMigrateVMwithVolume>:teardown
Error
166.35
test_vm_life_cycle.py

test_06_disk_offering_strictness_false
Error
145.65
test_service_offerings.py

Thanks @DaanHoogland - refactored
@blueorangutan package

@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_multiplication_x: el7 :heavy_multiplication_x: el8 :heavy_multiplication_x: debian :heavy_multiplication_x: suse15. SL-JID 2542

@blueorangutan package

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 2543

Trillian test result (tid-3271)
Environment: vmware-65u2 (x2), Advanced Networking with Mgmt server 7
Total time taken: 36202 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr5960-t3271-vmware-65u2.zip
Smoke tests completed. 90 look OK, 2 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_01_offline_migrate_VM_and_root_volume
Error
98.12
test_vm_life_cycle.py

test_03_live_migrate_VM_with_two_data_disks
Error
59.33
test_vm_life_cycle.py

test_06_disk_offering_strictness_false
Error
147.85
test_service_offerings.py

Trillian test result (tid-3269)
Environment: xenserver-71 (x2), Advanced Networking with Mgmt server 7
Total time taken: 36509 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr5960-t3269-xenserver-71.zip
Smoke tests completed. 90 look OK, 2 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_01_sys_vm_start
Failure
0.10
test_secondary_storage.py

test_01_nic
Error
210.81
test_nic.py

Trillian test result (tid-3270)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 37340 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr5960-t3270-kvm-centos7.zip
Smoke tests completed. 92 look OK, 0 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

@blueorangutan package

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 2575

@blueorangutan test centos7 vmware-67u3

@nvazquez a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests

Trillian test result (tid-3297)
Environment: vmware-67u3 (x2), Advanced Networking with Mgmt server 7
Total time taken: 35982 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr5960-t3297-vmware-67u3.zip
Smoke tests completed. 90 look OK, 2 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_01_offline_migrate_VM_and_root_volume
Error
123.11
test_vm_life_cycle.py

test_03_live_migrate_VM_with_two_data_disks
Error
64.63
test_vm_life_cycle.py

test_06_disk_offering_strictness_false
Error
144.14
test_service_offerings.py


[Security] Add a file extension validation whitelist mapped to an allowed mimetype

Supersed #262.

Thank you!
We should still update the documentation on this feature.
And it can't go into 1.x because it's breaking BC in configuration.

missing docs!
oneup_uploader:     mappings:         gallery:             max_size: 9999990             allowed_mimetypes:                 image/jpeg: ['jpg', 'jpeg', 'jpe']


[ ] WSL 2
[x] WSL 1

Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
wsl --install --from-file distro.tar --version 1
wsl -d distroName

Expected Behavior
Run the OOBE
Actual Behavior
Logs directly with root:

Diagnostic Logs
No response

The guide at https://learn.microsoft.com/en-us/windows/wsl/build-custom-distro states that This guide only applies to WSL release 2.4.4 and higher, so is WSL1 aware of the  [oobe] section in etc/wsl-distribution.conf?


[ls-qpack] Add new port port

[x] Changes comply with the maintainer guide.
[x] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
[x] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx.
[x] The versioning scheme in vcpkg.json matches what upstream says.
[x] The license declaration in vcpkg.json matches what upstream says.
[x] The installed as the "copyright" file matches what upstream says.
[x] The source code of the component installed comes from an authoritative source.
[x] The generated "usage text" is accurate. See adding-usage for context.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is in the new port's versions file.
[x] Only one version is added to each modified port's versions file.

Windows build is fail on my local. It not create the lib file, and I am not sure why.

Windows build is fail on my local. It compile without errors, but it not create the lib file, and I am not sure why.

If there is no __declspec(dllexport) and no .def file and no  WINDOWS_EXPORT_ALL_SYMBOLS, then MSVC will not produce an import lib for the DLL.

Windows build is fail on my local. It compile without errors, but it not create the lib file, and I am not sure why.

If there is no __declspec(dllexport) and no .def file and no WINDOWS_EXPORT_ALL_SYMBOLS, then MSVC will not produce an import lib for the DLL.

Then it mean I should create .def file as I saw in other ports.

WINDOWS_EXPORT_ALL_SYMBOLS

Adding
-DCMAKE_WINDOWS_EXPORT_ALL_SYMBOLS=ON
solved the problem! thank you! :)
We should also apply that on nettle port. and not edit manually the .def file.

WINDOWS_EXPORT_ALL_SYMBOLS

Adding -DCMAKE_WINDOWS_EXPORT_ALL_SYMBOLS=ON
solved the problem! thank you! :)

No! I made a different proposal.

WINDOWS_EXPORT_ALL_SYMBOLS

Adding -DCMAKE_WINDOWS_EXPORT_ALL_SYMBOLS=ON
solved the problem! thank you! :)

No! I made a different proposal.

I didn't understand that. I will change your suggestion. Thank you!

@WangWeiLin-MV Ready for review.


feat(fake-tcp) add TCP keep-alive support to client

This adds TCP KeepAlive support to client. Close #30, also related to #87. Three arguments are added: keepalive-time, keepalive-interval, keepalive-retries.
Let's say keepalive-time=300s, keepalive-interval=10s, keepalive-retries=3. This feature works like this: when the client detects that no TCP packet has arrived within 300 seconds, it will send a TCP Keep-alive packet to server. If server doesn't respond in time, the client will retry in 10 seconds. After 3 retries, the client will give up this connection. When server received the Keep-alive packet, it will immediately respond with an ACK.
While the user application may have its own keep-alive mechanism, this feature can detect broken connections, so it is still useful to turn it on. For example, if the NAT mapping table on the router is somehow reset, packets are no longer be able to go through. Without keep alive detection, the client will not mark the connection as expired because the UDP client keeps sending packets, so the UDP client may never be able to communicate. With keep alive detection, after the client detected that the connection is not receiving data, it will actively send keep-alive packets. It knows that the connection is broken when maximum retries are reached, and it will remove the connection from its memory, so a new connection can be established. This feature will not add any extra overhead on working connections, because keep-alive packets from the user application will keep the keepalive-time timer from being triggered.

I'd love this feature. In a very common IPv6 setup, the LAN client probably gets its IP address by SLAAC from router's RA. Suppose the ISP delegates a new prefix to the router, the client would have a new IP but still keep the old (not-yet-expired-but-unusable-already) IP - while the phantun connection still last - which means conntrack isn't going to MASQUERADE to a new address.
Currently the workaround is to simply restart the phantun, but there should be a more elegant way.

@sakamoto-poteko Could you please test if this works?

@andreadaoud I've been running with -k 10 with https://github.com/sakamoto-poteko/phantun/tree/andreadaoud-keepalive for a few days. So far so good.


cannot seem to fully enable monitoring diagnostic via az cli

Describe the bug
Trying to programmatically (via az cli) enable monitoring diagnostic settings for Azure VM.  The script seems to run successfully.  However, when I look at the portal UI, it shows the setting as pending a save.  Not clear why it is in this state.
To Reproduce

az login -u $AZURE_AD_USER -p $AZURE_PASSWORD --subscription $AZURE_SUBSCRIPTION_ID
az account set -s $AZURE_SUBSCRIPTION_ID

my_resource_group=rg-westus2
my_win_vm=winvm
my_diagnostic_storage_account=stoacctwestus2
my_vm_resource_id=$(az vm show -g $my_resource_group -n $my_win_vm --query "id" -o tsv)
protected_settings="{'storageAccountName': '${my_diagnostic_storage_account}',
'storageAccountSasToken': '${storage_sastoken}'}"
default_config=$(az vm diagnostics get-default-config --is-windows-os
| sed "s#DIAGNOSTIC_STORAGE_ACCOUNT#$my_diagnostic_storage_account#g"
| sed "s#VM_OR_VMSS_RESOURCE_ID#$my_vm_resource_id#g")
storage_sastoken=$(az storage account generate-sas
--account-name $my_diagnostic_storage_account --expiry 2037-12-31T23:59:00Z
--permissions wlacu --resource-types co --services bt -o tsv)
az vm diagnostics set --settings "${default_config}"
--protected-settings "${protected_settings}"
--resource-group $my_resource_group --vm-name $my_win_vm
az logout --username $AZURE_AD_USER
Expected behavior
Diagnostic setting for wimvm should be enabled and saved as enabled.
Environment summary
Linux mine.local 3.10.0-862.9.1.el7.x86_64 #1 SMP Mon Jul 16 16:29:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
azure-cli (2.0.50)
Python location '/usr/lib64/az/bin/python'
Extensions directory '/home/getreal/.azure/cliextensions'
Python (Linux) 2.7.5 (default, Jul 13 2018, 13:06:57)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-28)]
Additional context
Add any other context about the problem here.

@jagan-at-vi, sorry for the trouble you have run into. There are some invalid help/examples for Windows VM, which I am submitting the fix.
But we have one service end issue which I am chatting with windows diagnostics extension for fix, particularly the error below. I will post updates when that issue gets resolved. Stay tuned.
(env) D:\sdk\azure-cli>az vm diagnostics set --settings d:\temp\pub.json --protected-settings d:\temp\pri.json -g yg --vm-name yg-1 --no-auto-upgrade
Deployment failed. Correlation ID: d293ca3f-41d0-4a3e-98cb-2e78ac2361f9. VM has reported a failure when processing extension 'IaaSDiagnostics'. Error message: "Monitoring Agent not reporting success after launch".

dupe to #8108 which has more discussions/comments. The WAD extension does have issues which we are working with service team to resolve it. At the same time pr #8117 does fix invalid templates.

Tried the template for default config per 8117 – did not help – tables are not being created in the storage account
"adewaleo" <notifications<EMAIL_ADDRESS>wrote on 1/2/19, 2:12 PM :
dupe to #8108https://github.com/Azure/azure-cli/issues/8108 which has more discussions/comments. The WAD extension does have issues which we are working with service team to resolve it. At the same time pr #8117https://github.com/Azure/azure-cli/pull/8117 does fix invalid templates.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-cli/issues/7809#issuecomment-451001518, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Amli8YIV3q7Tfa-Nj7f-JjRGljN7p_sRks5u_S7RgaJpZM4YXvFa.
--

The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please contact the sender immediately and permanently delete or destroy the material/information.


[11.x] Update detachUsingCustomClass to trigger delete event with full model record

TLDR: This update allows the any listener to the delete event on a pivot model record to receive the full set of columns (including the PK) instead of just the foreign keys.
Fully compatible with 10.x branch as well.
Long Description: I am working on a feature to audit pivot column changes. Attach and detach work fine to create audits. However, detach (the delete event) failed to create an audit record because my audits table does not allow null values for auditable primary key value. The issue is that the detach section was creating a new pivot record only with the foreign keys leaving out all other columns from the delete event.
While debugging I dug into the history of Laravel supporting pivot records triggering events and this change brings the framework more in line with how the updateExistingPivot method works when using a pivot model in the updateExistingPivotUsingCustomClass method.

I also made the delete null safe in case the record has already been deleted by another process it doesn't throw a "call to member function delete() on null"  as was fixed on this pull request for the pivot update section -> https://github.com/laravel/framework/pull/29362
Relevant links to other PRs or commits related to this change:

Original PR for pivot model events -> https://github.com/laravel/framework/pull/27571
Commit to use getCurrentlyAttachedPivots method in updateExistingPivotUsingCustomClass -> https://github.com/laravel/framework/commit/e31d13111da02fed6bd2ce7a6393431a4b34f924

Happy to add necessary test but generally speaking this change should match all existing tests.
Thank you for your consideration!
Abraham

I don't think we can change this on a patch release.

@taylorotwell This change wasn't breaking any functionality but I can make a PR to target the master branch if that's a better route for this change.


Adjust speed of playing track

Hi
is it possible to change speed of playing track?

Apparently there is a way to do that with HTML audio, but it is not implemented by the plugin.
You could fork the plugin and add the method if you wish, it should be easy.
This seems to be method that needs to be implemented: https://developer.mozilla.org/en-US/Apps/Fundamentals/Audio_and_video_delivery/WebAudio_playbackRate_explained

@arielfaur
Could you tell me in which file of your plugin should I add this method?


"Mine current subtitle and open Anki dialog" No longer works in fullscreen (Mac Google Chrome)

After using the Mine current subtitle and open Anki dialog shortcut, the dialog only shows up until fullscreen is exited. The updated card notification after mining also only appears when exiting full screen.

@zuckyyyy I deployed a fix for this, let me know if it works for you.

Works now thanks


Remove the ability to mutate the timestamp of a CompatibilityResult

Next time can you make sure you're even with the upstream/master branch before making new changes? The change is small in this case so it's ok, but having old commit histories in the PR makes it confusing to review.


Translate quick-start-gke-dm into Chinese

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: fuxu
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rootsongjc
If they are not already assigned, you can assign the PR to them by writing /assign @rootsongjc in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content_zh/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @fuxu. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

CI failed with the following errors:
- ./public/docs/setup/kubernetes/quick-start/index.html
  *  External link https://archive.istio.io/v0.2/docs/setup/kubernetes/quick-start#uninstalling failed: got a time out (response code 0)
htmlproofer 3.9.1 | Error:  HTML-Proofer found 1 failure!

Please fix it.

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fuxu, rootsongjc
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content_zh/OWNERS [rootsongjc]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add more tags to make the plugin easier to find in hub and config

Done as a result of https://github.com/runelite/runelite/discussions/16594


[SMALLFIX]replace anonymous type with lambda in alluxio.client.file.RetryHandlingFileSystemMasterClient#delete #146

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17484/
Test PASSed.

@GIFTED-BOY Please sign the contribution license agreement when you have a chance

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17542/
Test PASSed.

Merged build finished. Test PASSed.


link openssl statically for Windows

Problem
a refined version of the timeline for future reference:

we applied the vendored feature on openssl for all platforms.
it looks like we had some perl issues so we did Unvendor OpenSSL for Windows to avoid CI troubles with perl.exehttps://github.com/anza-xyz/agave/commit/c9bfc99c720ed091c326c1cce58fcd8197306235
we planed to vendor Windows binaries #73.
the pipeline failed recently https://github.com/anza-xyz/agave/actions/runs/11163589550/job/31030913975 and I have this PR

Summary of Changes

use vendored in openssl for all platforms (it should work. I verified by this pipeline https://github.com/yihau/solana/actions/runs/11241556386/job/31253379456#step:7:8654)

> ldd solana-test-validator
  	ntdll.dll => /c/Windows/SYSTEM32/ntdll.dll (0x7ffe8ccc0000)
  	KERNEL32.DLL => /c/Windows/System32/KERNEL32.DLL (0x7ffe8b580000)
  	KERNELBASE.dll => /c/Windows/System32/KERNELBASE.dll (0x7ffe8a240000)
  	apphelp.dll => /c/Windows/SYSTEM32/apphelp.dll (0x7ffe88280000)
  	bcryptprimitives.dll => /c/Windows/System32/bcryptprimitives.dll (0x7ffe8ab70000)
  	USER32.dll => /c/Windows/System32/USER32.dll (0x7ffe8b3d0000)
  	win32u.dll => /c/Windows/System32/win32u.dll (0x7ffe8ab40000)
  	POWRPROF.dll => /c/Windows/SYSTEM32/POWRPROF.dll (0x7ffe8a120000)
  	GDI32.dll => /c/Windows/System32/GDI32.dll (0x7ffe8c610000)
  	ucrtbase.dll => /c/Windows/System32/ucrtbase.dll (0x7ffe8a800000)
  	gdi32full.dll => /c/Windows/System32/gdi32full.dll (0x7ffe8a6e0000)
  	RPCRT4.dll => /c/Windows/System32/RPCRT4.dll (0x7ffe8c1f0000)
  	msvcp_win.dll => /c/Windows/System32/msvcp_win.dll (0x7ffe8aaa0000)
  	CRYPT32.dll => /c/Windows/System32/CRYPT32.dll (0x7ffe8a910000)
  	WS2_32.dll => /c/Windows/System32/WS2_32.dll (0x7ffe8b7d0000)
  	ADVAPI32.dll => /c/Windows/System32/ADVAPI32.dll (0x7ffe8b710000)
  	msvcrt.dll => /c/Windows/System32/msvcrt.dll (0x7ffe8b320000)
  	sechost.dll => /c/Windows/System32/sechost.dll (0x7ffe8c640000)
  	bcrypt.dll => /c/Windows/System32/bcrypt.dll (0x7ffe8aa70000)
  	SHLWAPI.dll => /c/Windows/System32/SHLWAPI.dll (0x7ffe8c5b0000)
  	shell32.dll => /c/Windows/System32/shell32.dll (0x7ffe8b8d0000)
  	secur32.dll => /c/Windows/SYSTEM32/secur32.dll (0x7ffe7db70000)
  	ole32.dll => /c/Windows/System32/ole32.dll (0x7ffe8b1e0000)
  	combase.dll => /c/Windows/System32/combase.dll (0x7ffe8c910000)
  	VCRUNTIME140.dll => /c/Windows/SYSTEM32/VCRUNTIME140.dll (0x7ffe7e9a0000)
  	MSVCP140.dll => /c/Windows/SYSTEM32/MSVCP140.dll (0x7ffe7e9c0000)
  	VCRUNTIME140_1.dll => /c/Windows/SYSTEM32/VCRUNTIME140_1.dll (0x7ffe7f450000)
  	CRYPTBASE.DLL => /c/Windows/SYSTEM32/CRYPTBASE.DLL (0x7ffe899b0000)
  	SSPICLI.DLL => /c/Windows/SYSTEM32/SSPICLI.DLL (0x7ffe89bf0000)

fixed openssl version to 3.3.2
update ci

(will re-enable those 2 pipelines when this one is ready to merge)


Cleanup

Only print logrus if in debug mode
Validate options
If an string option is passed in, and it is not followed by a value,
then error out with a message saying the option requires a value.
For example
buildah from --creds --pull dan
option --creds requires a value
Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

Fixes https://trello.com/c/NLJtPsvv/607-1-validate-and-fix-buildah-params-that-take-values?menu=filter&filter=targeted-rh

Probably want the same patches for kpod.

@mheon @nalind PTAL

@umohnani8 PTAL

LGTM

@mheon PTAL

I'm slightly concerned we might someday have someone try and pass a legitimate argument that begins with a hyphen. But I can't think of any cases where this would actually be something people do. I suppose we can handle it if someone actually files a bug report about it.
LGTM.

LGTM, ship it!

@rh-atomic-bot rTomSweeneyRedHat cdc5b95

@rh-atomic-bot r+ cdc5b95


Add epoch based temporal extraction functions

Currently we have functions like e.g. hour that extract the hour part of a temporal value i.e. produces 3 for the interval 2 days 3 hours. Oftentimes it is necessary to extract the full hours i.e. 51 which can be done by extracting the epoch and then dividing it to the desired unit. Some DBMS might not have efficient epoch extraction functions so letting the user do the calculation based on the epoch might not be very nice.
I propose we add the following functions, analogous to the part extract function, with pluralized names

microseconds
milliseconds
seconds (alias for epoch)
minutes
hours
days
weeks
months
quarters
years

Related to #380


Change naming.  Fixes #9

cose.COSE_Mac -> cose.mac
moved code into /lib
Updated package version to 1.0 (breaking API change)
Fixed tests
Added myself to contributors

Coverage remained the same at 95.455% when pulling e3233b7789a43bbff4fc34ad1a868e01ec7ef292 on hildjj:naming into 25dccaa2a4d0f4b4df3b0c09c972a54f4cc956cc on erdtman:master.

Coverage remained the same at 95.455% when pulling 8dc5b9349be08c5f58cc33c1b1c73f9c01620866 on hildjj:naming into 25dccaa2a4d0f4b4df3b0c09c972a54f4cc956cc on erdtman:master.


java.lang.NoSuchFieldError: MATERIALS Crash

I'm seeing the following crash when launching the game.
https://pastebin.com/Nsbk26LM
Thank you

Another crash that I can't replicate in my development environment...
Fix coming out shortly.

Should be fixed in 1.1.2.
Get it here, update will be up on Curse soon.

Thank you!

Sorry, not it's changed to the following crash.
java.lang.NoSuchFieldError: MISC
https://pastebin.com/PJqZWfqV

No idea why this is happening. Might be an issue with the latest Forge version.

 Version 1.1.3 will fix everything properly.

ALL FIXED IN 1.1.3, FINALLY.
Grab it here, now being uploaded to Curse.


Enable Nullable Reference Type(only warnings)

Nullable Reference Type

set LangVersion to 8.0

not to latest because C# 7.x Compiler interprets it as 7.x.

set Nullable to warnings
fix warnings caused by NRT

CS8600
CS8602

Nullable annotations are not set because of breaking change for programs used this library.
Other Fixes

accept some suggested code by IDE (excludes /sandbox folder)

IDE0017: dotnet_style_object_initializer
IDE0018: csharp_style_inlined_variable_declaration
IDE0034: csharp_prefer_simple_default_expression
IDE0044: dotnet_style_readonly_field
IDE0052: Remove unread private members
IDE0059: csharp_style_unused_value_assignment_preference
IDE0063: csharp_prefer_simple_using_statement
IDE0066: csharp_style_prefer_switch_expression

remove and sort using directive
add scope private explicitly

Thanks!
I want to accept it.
But IDE**** fix is not needed.

Okay, I'll reverted it.

And, do you think to need Nullable annotations?
I can help you add them.

thanks, merge it.
Annotation, I will think later.


An OPTIONS request to the TUS URL does not contain the Tus-Version header

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
When I send an OPTIONS request to the TUS endpoint then I don't get a Tus-Version header in the response.
The TUS protocol states that "a successful response ... MUST contain the Tus-Version header".
To Reproduce

Run a Supabase stack locally with Supabase Storage. Set up Kong on port 8000
Run this command line command:

curl -D - --request OPTIONS --url http://localhost:8000/storage/v1/upload/resumable

Expected behavior
A Tus-Version header should be in the response headers.
I see this:
HTTP/1.1 204 No Content
Connection: keep-alive
Tus-Resumable: 1.0.0
Access-Control-Expose-Headers: Authorization, Content-Type, Location, Tus-Extension, Tus-Max-Size, Tus-Resumable, Tus-Version, Upload-Concat, Upload-Defer-Length, Upload-Length, Upload-Metadata, Upload-Offset, X-HTTP-Method-Override, X-Requested-With, X-Forwarded-Host, X-Forwarded-Proto, Forwarded, Upload-Expires
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST, HEAD, PATCH, OPTIONS, DELETE
Access-Control-Allow-Headers: Authorization, Content-Type, Location, Tus-Extension, Tus-Max-Size, Tus-Resumable, Tus-Version, Upload-Concat, Upload-Defer-Length, Upload-Length, Upload-Metadata, Upload-Offset, X-HTTP-Method-Override, X-Requested-With, X-Forwarded-Host, X-Forwarded-Proto, Forwarded, Upload-Expires, X-Upsert, Upload-Expires, ApiKey
Access-Control-Max-Age: 86400
Tus-Extension: creation,creation-with-upload,creation-defer-length,termination,expiration
Tus-Max-Size:<PHONE_NUMBER>776
Date: Thu, 14 Nov 2024 16:25:52 GMT
X-Kong-Upstream-Latency: 29
X-Kong-Proxy-Latency: 36
Via: kong/2.8.1

Docker image: supabase/studio:20230926-3e441e4

Hi @jfeaver thanks for reporting this.
I just checked this on the tus-node-server repo, and yes the Tus-Version seems to be missing from the OPTIONS request
Will follow up, upstream https://github.com/tus/tus-node-server/issues/674


Describe the kinds of cloud infrastructure we can provide

The main brochure page won't go into a ton of detail about the kinds of environments and infrastructure that we can provide. But we may want a page that goes into more information, provides more options, etc.

I think that this is now in existence: https://2i2c.org/infrastructure/


Backend: Add support for local logging

Currently logs only go to Azure Insights. Support for local logs might be desirable for some users.

Obsolete task. Closing


Removes shared methdispatch implementation

There is a subtle bug in the existing implementation where if multiple (>=2) ActionProviderBlueprints are created and attached to a Flask app, the implementation of methdispatch would only ever record one Blueprint's status, cancel and release endpoints. For example, this meant that all requests to a status operation on the app would get routed to one of the ActionProviderBlueprint's routes (typically the last Blueprint to get registered on the app). What should happen is that calls to a Blueprint's endpoint should get routed to that Blueprint's routes.
This PR fixes the issue by removing the methdispatch implementation. Aside from the buggy implementation, it was hard to understand and hard to maintain. It's purpose was to transparently call the correct route depending on if the route was called with a str or ActionStatus argument. Without it, it's a bit more digestable to decribe the behavior as "if an action_loader is registered, your endpoint routes should expect an ActionStatus type value as the first argument".
Also pdates type annotations to keep mypy happy while also providing useful feedback to devs.

I'm not entirely sure myself how to bug in the faulty implementation worked. I think it has to do with how python marries decorators to class methods - it ended up being that all instances shared the same methdispatch reference. Removing it is one less thing to keep track of.