trufflehog: 3.28.5 -> 3.28.6

Changelog: https://github.com/trufflesecurity/trufflehog/releases/tag/v3.28.6
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.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

[ ] Fits CONTRIBUTING.md.

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

1 package built:

trufflehog


Multiple dataset training Web Support

Fixes #391
NOTE - Need the latest kitware/viame:gpu-algorithms-latest for the input_list  to work properly.

Enabled Training menu button when one or more items are selected in a folder
Changes the input type for training to an array of folderIds and updates the API in the relevant locations.
Server now takes in the JSON data for the folderIds and does a preprocess check on each dataset to ensure there is some groundtruth csv files there.
Updated the training to remove the labels.txt and use the new -il input_folder_list.txt and the -it input_groundtruth_list.txt for specifiying the data.
Since it still requires a folder structure for orangization I kept the organize_folder_for_training but removed the labels.txt stuff.
--no-query is added to the groundtruth command so it will use all types that would be in the labels.txt by default and prevent the user from being prompted to accept.

I've tested by taking to small datasets with different track types in it and training on them.  Then I would run the trained model on another small dataset and ensure that it is using types from both datasets.
Additionally I trained across different folders by using the /viame/train endpoint and manually specifying folderIds across different root folders and different public users.  It trained successfully and the resulting pipeline incorporated types across the different folders.

Since it still requires a folder structure for orangization

Could you explain this part?  I didn't expect that anything would need to move.  You could just do a simple download of each dataset from Girder, then point to the data in-place without moving anything.
Also, I expect you'd like to merge this before #487.  I'm fine with that.  Just to confirm, this will work with arbitrary dataset ids right?  They don't have to be siblings?

Could you explain this part? I didn't expect that anything would need to move. You could just do a simple download of each dataset from Girder, then point to the data in-place without moving anything.

besides my massive spelling mistake there (orangization).  Bad choice of words for the explanation.  I had the assumption that the testing of the ground_truth to see if it is a directory was in there because of some legacy items where the meta.detection might provide a directory instead of a csv so that test needed to remain in there.  Really all organize_folder_for_training does right now is check if the ground_truth is a directory, if it is it will copy the first .csv out of it into the training data directory associated with that groundtruth and then deletes the folder.  If it is a file it just renames it to ground_truth.csv which is unnecessary but cleaner.   I could keep all ground truth at the root level, but if I'm doing the test and possibly moving it why not keep it a bit more organized.  I should probably clean up the description and what it is called.

Also, I expect you'd like to merge this before #487. I'm fine with that. Just to confirm, this will work with arbitrary dataset ids right? They don't have to be siblings?

Yeah that was the second part of my testing, I was training across different user's public folders, just required that I manually create the array of dataset ids and call the endpoint because there is no UI  for it currently.

Really all organize_folder_for_training does right now is check if the ground_truth is a directory, if it is it will copy the first .csv out of it into the training data directory associated with that groundtruth and then deletes the folder. If it is a file it just renames it to ground_truth.csv which is unnecessary but cleaner.

For the record, the reason this is done is in case the girder item has multiple files. If it does, it's a folder when downloaded. Otherwise it's just a file. Since we still use the csv_detection_file method to ensure a csv file on the item, this is likely always the case.


docs: Add node/python lambda examples

I haven't had a chance to document Python yet. I'll look at this when I get to it.

I haven't had a chance to document Python yet. I'll look at this when I get to it.

A big reason I chose sst was the ability to integrate with AWS using whatever best tech I can use. Having an example is nice, but I'll also look into integrating them more tighly via the SDK, maybe allowing me to call resources like the python lambda from a nodejs app (given there is a VPC/public network between them). This could be a real game changer.


stereocilia terms lack part_of relationships

These need better part-of links eg to CL

GO:0002139 ! stereocilia coupling link [subclass: "GO:0044464"] [subclass: "cell part"]
GO:0032421 ! stereocilium bundle [subclass: "GO:0043232"] [subclass: "intracellular non-membrane-bounded organelle"]

See diagram

Mmmm, spaghetti .... (dreams of a glorious future where clean partonomies and local axioms on terms are sufficient).
That path through stereocillium bundle to non-membrane-bound organelle is wrong too.

Cleared up lots here:

neuromast cells have stereocillia too.  I've made CL po link to mechanosensory hair cell
This is classified in CL as a neuron.  Perhaps should also be epithelial?
Added missing terms and partonomy links under stereocillium and stereocillium bundle
Made new classification 'actin-based cell projection' that covers this, microvillus and fillpodium
Added in missing details of biology of  'actin-based cell projection' s
stereocillium bundle and micovillus are now grouped under 'cluster of actin-based cell projections' - link to intracelullar non-membrane bound organelle dropped.

Chasing up a few loose ends on this.  One of these - stereocillium seems to be used for projections in male reproductive system, but these are probably more like microvilli.


history mode for using anchors and TOC

I modified the project a bit to use markdown-it and its plugins. one of it is anchor. However since this projects router uses hash mode it misunderstands the link and puts the anchor right at the root of url. If I change the path of build.js to /build.js and change the mode to history, it works.
Therefore want to ask it is more preferable to make the change? I can make a PR for that.

#10

Thank you IniZio,
I've tried the HTML5 History Mode but failed in just few months ago.
To use this mode, you have to do some serve configurations (URL Rewrite) but unfortunately GitHub Pages doesn't support any server side configuration. That is why I am still using hash mode.  Deeply regret and I am looking for other methods to solve this problem.

Some discussion:  https://github.com/isaacs/github/issues/408
Vue-router documentation:  http://router.vuejs.org/en/essentials/history-mode.html

I tried to use the method on my blog, and it seems to be working to my expectation. Would you mind reviewing my code at the develop branch of the repo to see if the method is simply not feasible?

Access from List is work. (Because our browser support HTML5 pushState API )
But if you refresh, it will request from GitHub Pages server and get the 404 response 🙈.
eg. http://inizio.github.io/post/b4ed1f5e7939732e07e7ad35b9af18588a509297

In addition, what's the meaning of TOC 🤔 ?

Hmm ok understood, will close the PR then. TOC means Table Of Contents, just want to make it pair with anchors.

I will add it into TODO #1  and keep exploring the solution.
Thank you for your contribution. @IniZio


Add music interest to onboarding

Source data has been added, this is just the translation.

yep yep!


"Range too large for use with labels" error when using --no-board-labels

For SZ > 99 we throw this error, which makes sense if we are trying to draw board labels (which are limited by space to two characters), but doesn't make sense with --no-board-labels.
echo '(;GM[1]FF[4]SZ[255];B[bb]W[Bc])' | sgf-render --format text --no-board-labels
Failed to write output: Range too large for use with labels

On the other hand, there is literally no way in the SGF spec to reference a point outside a 52x52 board, so maybe the real issue here is that if either coordinate is larger than 52 we should be returning a more on point error.

Fixed in 5f38b73. I decided to throw an error for board sizes > 52. I can't come up with a scenario where drawing a larger board than you can place stones on is actually useful, and I think this is probably the best user experience.


Feature/d2.1 database scripts

I think this is done. I agree that it makes more sense to include the 1.6.3->1.7 DDL upgrade script into D1.4.

All latest scripts tested and working


Temporarily shifted to tests working on all machines

@josevalim to at least have tests on master that work for everybody without fail while the problems with the original are being diagnosed, I have condensed the functionality of the tests by grouping similar things together and by having only 5 different tests.
I tested these by running a shell script for around 50 times on a friend's machine and there is no failure.
This is only temporary and once the problem with the original tests are figured out, we will revert back to them.

Sorry, I don't believe we should merge this, as it does not fix the problem, it only hides it. It is better to keep the tests failing until we come with the proper fix.

Sorry I merged it immediately @josevalim I was going to submit a PR for the new matrix functionalities and didn't want a conflict.
I can put the original tests back if you think so, but then I was thinking if people who use Tensorflex come across the tests failing they might think that the code doesn't work at all, while in fact the same stuff in the test code actually runs outside the tests in IEx.
Would it not be better to have the problematic expanded original tests in another branch while we figure out the fix? Because these condensed tests prove that the tests run fine when lumped together, so the functionality is not the problem, something else is.
What do you think? I'll put in the original tests back if you think that is better.

I can put the original tests back if you think so, but then I was thinking if people who use Tensorflex come across the tests failing they might think that the code doesn't work at all,

Before fixing the tests, we actually do not have a guarantee that the code works. Since the test fails from time to time, we know there are specific scenarios that will make the system fail, and at the moment we have not guaranteed that those scenarios cannot happen in production.
Hopefully more people looking at the tests means we can find the root cause sooner.

@josevalim I see your point. I have reverted the tests back to the way they were in the next PR #35 containing new matrix functions.
Sorry for not directly removing the commit made here and then adding the new PR.


Added options for bodyParser.json() and bodyParser.urlencoded()

By default bodyParser has a limit of 100kb which in some cases needs to be increased. I have added two options, one for both bodyParser.json and bodyParser.urlencoded.
I have tested the implementation in a project where I do file upload and and everything passes. Scenarios:

with default options
with limit set and file uploaded is below limit
with limit set and file uploaded is above limit

Oh awesome thank you! Merging now and will try and push out in a new version at the weekend.
(I need to update the docs as not options like this that have been added are not yet documented).


Make some packages more descriptive

Having more content make each eye-catching in my opinion, So I have done just that.
+1 Package

Thanks for those description. It makes it more clearer.


[Bitcoin Op_Return/ThorSwap] Proper handling for len 76-80 bytes in two chunks

Description
Proper handling for BTX OP_RETURN with data > 75 bytes, relevant for THORChainSwap.
Data of length 76-80 bytes is split into two data pushes:
<script_len> OP_RETURN <data1_len> <data1> <data2_len> <data2>
Fixes #2752.
How to test
ThorSwap swap from Btc, with memo >75 bytes.
Unit tests *Bitcoin* and *THOR*.
Validated with tx (80-byte OP_RETURN):
https://blockchair.com/bitcoin/transaction/42f6bb73720b502f4480a49e8878ab88b52143dc97f4b6ea365dc2b0be7039ec
Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist

[x] Create pull request as draft initially, unless its complete.
[x] Add tests to cover changes as needed.
[x] Update documentation as needed.
[x] If there is a related Issue, mention it in the description.

If you're adding a new blockchain

[ ] I have read the guidelines for adding a new blockchain.

Note: 80-byte OP_RETURN is encoded as:
53 6a 4b
3d3a424e422e425553442d4244313a626e6231796b757265776375337564367568737a6367377039667a3833376b72617165766b66373937743a31303030303a7468726e6d3a31303a3132
05<PHONE_NUMBER>

53 is script length = 83
6a is OP_RETURN
4b is 75 data length
<75 bytes>
05 is data length
<05 bytes>
Assembled payload is 3d3a424e422e425553442d4244313a626e6231796b757265776375337564367568737a6367377039667a3833376b72617165766b66373937743a31303030303a7468726e6d3a31303a31323334353637
that is =:BNB.BUSD-BD1:bnb1ykurewcu3ud6uhszcg7p9fz837kraqevkf797t:10000:thrnm:10:1234567.
It is shown correctly in Blockchair explorer:

https://blockchair.com/bitcoin/transaction/42f6bb73720b502f4480a49e8878ab88b52143dc97f4b6ea365dc2b0be7039ec


ImportError: No module named 'torch_ext'

Hi, I was running the "quickstart" code on my win10. I used torch = 1.8.0 and python = 3.7 with cuda = 10.2.
The problems happened when I tried training the model in Jupyter:
optimizer = torch.optim.Adam(task.parameters(), lr=1e-3)
solver = core.Engine(task, train_set, valid_set, test_set, optimizer, gpus=[0],
                     batch_size=512) solver.train(num_epoch=100)

And this turned to:
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
~\AppData\Local\Temp/ipykernel_19744/1406504193.py in <module>
----> 1 solver.train(num_epoch=100)

d:\conda\envs\torchdrug\lib\site-packages\torchdrug-0.1.0-py3.7.egg\torchdrug\core\engine.py in train(self, num_epoch, batch_per_epoch)
    141                     batch = utils.cuda(batch, device=self.device)
    142
--> 143                 loss, metric = model(batch)
    144                 if not loss.requires_grad:
    145                     raise RuntimeError("Loss doesn't require grad. Did you define any loss in the task?")

d:\conda\envs\torchdrug\lib\site-packages\torch\nn\modules\module.py in _call_impl(self, *input, **kwargs)
    887             result = self._slow_forward(*input, **kwargs)
    888         else:
--> 889             result = self.forward(*input, **kwargs)
    890         for hook in itertools.chain(
    891                 _global_forward_hooks.values(),

d:\conda\envs\torchdrug\lib\site-packages\torchdrug-0.1.0-py3.7.egg\torchdrug\tasks\property_prediction.py in forward(self, batch)
     72         metric = {}
     73
---> 74         pred = self.predict(batch, all_loss, metric)
     75
     76         if all([t not in batch for t in self.task]):

d:\conda\envs\torchdrug\lib\site-packages\torchdrug-0.1.0-py3.7.egg\torchdrug\tasks\property_prediction.py in predict(self, batch, all_loss, metric)
    103     def predict(self, batch, all_loss=None, metric=None):
    104         graph = batch["graph"]
--> 105         output = self.model(graph, graph.node_feature.float(), all_loss=all_loss, metric=metric)
    106         pred = self.linear(output["graph_feature"])
    107         return pred

d:\conda\envs\torchdrug\lib\site-packages\torch\nn\modules\module.py in _call_impl(self, *input, **kwargs)
    887             result = self._slow_forward(*input, **kwargs)
    888         else:
--> 889             result = self.forward(*input, **kwargs)
    890         for hook in itertools.chain(
    891                 _global_forward_hooks.values(),

d:\conda\envs\torchdrug\lib\site-packages\torchdrug-0.1.0-py3.7.egg\torchdrug\models\gin.py in forward(self, graph, input, all_loss, metric)
     74
     75         for layer in self.layers:
---> 76             hidden = layer(graph, layer_input)
     77             if self.short_cut and hidden.shape == layer_input.shape:
     78                 hidden = hidden + layer_input

d:\conda\envs\torchdrug\lib\site-packages\torch\nn\modules\module.py in _call_impl(self, *input, **kwargs)
    887             result = self._slow_forward(*input, **kwargs)
    888         else:
--> 889             result = self.forward(*input, **kwargs)
    890         for hook in itertools.chain(
    891                 _global_forward_hooks.values(),

d:\conda\envs\torchdrug\lib\site-packages\torchdrug-0.1.0-py3.7.egg\torchdrug\layers\conv.py in forward(self, graph, input)
     89             update = checkpoint.checkpoint(self._message_and_aggregate, *graph.to_tensors(), input)
     90         else:
---> 91             update = self.message_and_aggregate(graph, input)
     92         output = self.combine(input, update)
     93         return output

d:\conda\envs\torchdrug\lib\site-packages\torchdrug-0.1.0-py3.7.egg\torchdrug\layers\conv.py in message_and_aggregate(self, graph, input)
    339     def message_and_aggregate(self, graph, input):
    340         adjacency = utils.sparse_coo_tensor(graph.edge_list.t()[:2], graph.edge_weight,
--> 341                                             (graph.num_node, graph.num_node))
    342         update = torch.sparse.mm(adjacency.t(), input)
    343         if self.edge_linear:

d:\conda\envs\torchdrug\lib\site-packages\torchdrug-0.1.0-py3.7.egg\torchdrug\utils\torch.py in sparse_coo_tensor(indices, values, size)
    160         size (list): size of the tensor
    161     """
--> 162     return torch_ext.sparse_coo_tensor_unsafe(indices, values, size)
    163
    164

d:\conda\envs\torchdrug\lib\site-packages\torchdrug-0.1.0-py3.7.egg\torchdrug\utils\torch.py in __getattr__(self, key)
     28             self.module = cpp_extension.load(self.name, self.sources, self.extra_cflags, self.extra_cuda_cflags,
     29                                              self.extra_ldflags, self.extra_include_paths, self.build_directory,
---> 30                                              self.verbose, **self.kwargs)
     31         return getattr(self.module, key)
     32

d:\conda\envs\torchdrug\lib\site-packages\torch\utils\cpp_extension.py in load(name, sources, extra_cflags, extra_cuda_cflags, extra_ldflags, extra_include_paths, build_directory, verbose, with_cuda, is_python_module, is_standalone, keep_intermediates)
   1089         is_python_module,
   1090         is_standalone,
-> 1091         keep_intermediates=keep_intermediates)
   1092
   1093

d:\conda\envs\torchdrug\lib\site-packages\torch\utils\cpp_extension.py in _jit_compile(name, sources, extra_cflags, extra_cuda_cflags, extra_ldflags, extra_include_paths, build_directory, verbose, with_cuda, is_python_module, is_standalone, keep_intermediates)
   1315         return _get_exec_path(name, build_directory)
   1316
-> 1317     return _import_module_from_library(name, build_directory, is_python_module)
   1318
   1319

d:\conda\envs\torchdrug\lib\site-packages\torch\utils\cpp_extension.py in _import_module_from_library(module_name, path, is_python_module)
   1697 def _import_module_from_library(module_name, path, is_python_module):
   1698     # https://stackoverflow.com/questions/67631/how-to-import-a-module-given-the-full-path
-> 1699     file, path, description = imp.find_module(module_name, [path])
   1700     # Close the .so file after load.
   1701     with file:

d:\conda\envs\torchdrug\lib\imp.py in find_module(name, path)
    294         break  # Break out of outer loop when breaking out of inner loop.
    295     else:
--> 296         raise ImportError(_ERR_MSG.format(name), name=name)
    297
    298     encoding = None

ImportError: No module named 'torch_ext'

The same code works well in Colab and I suspect this is because I couldn't install rdkit-pypi and installed rdkit on conda instead.

Thanks for the observation. TorchDrug is mainly developed and tested on Linux, and should work with Colab. Currently there is no guarantee for installing TorchDrug on Windows, but we will come up with Windows support soon.

Got same problem on CentOS8, with PyTorch 1.8.0, CUDA 11.0 and python 3.7

Do you guys install from conda or from source? I just checked the conda package and torch_ext.cpp lies correctly under torchdrug/utils/extension. torch_ext should be automatically imported and JIT compiled by PyTorch when it is used.
One issue I've encountered with PyTorch JIT is that if you kill the process during the compilation of JIT, it sometimes causes a broken compiled binary and JIT can neither load it or recompile it. You need to manually delete the folder torch_extensions, which may lies under either /home/your_user_name/.cache or /tmp by default.

Had the same issue, and was able to fix it by:
rm -rf /home/your_user_name/.cache/torch_extensions

Had the same issue, and was able to fix it by:
rm -rf /home/your_user_name/.cache/torch_extensions

If this can solve, I believe it's caused by the broken cache in JIT. This is typically caused by Ctrl-C break during compilation or compiling multiple instances of the same extension at the same time.
If you want to import torchdrug in several processes on the same machine, a safe solution is to manually specify a separate extension directory for each process like
TORCH_EXTENSIONS_DIR=/path/to/your/extensions python script.py

I'm using anaconda on windows and install torchdrug and other required packages in specific environment.
I've got the message : "ImportError: DLL load failed while importing torch_ext: The specified module could not be found."
I dont know if it is the same problem as mention above. If yes, there is no solution fo now until windows compatible version release right?
Does it compatible with conda in linux windows subsystem WSL?

@natchanon-me Hi! I am not sure if they are the same problem, but it must be caused by JIT. We didn't test torchdrug on Windows. I think TorchDrug might be compatible with Windows if the JIT utilities (e.g. g++ on Linux. on Windows I guess it's MSVC) from PyTorch work well, since the library doesn't rely on any pre-compiled binaries.

I am running into a similar issue, CentOS7, python 3.8, pytorch 1.8, cuda 10.1.
14:20:53   >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
14:20:53   Epoch 0 begin
/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/utils/cpp_extension.py:283: UserWarning:

                               !! WARNING !!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Your compiler (c++) is not compatible with the compiler Pytorch was
built with for this platform, which is g++ on linux. Please
use g++ to to compile your extension. Alternatively, you may
compile PyTorch from source using c++, and then you can also use
c++ to compile your extension.

See https://github.com/pytorch/pytorch/blob/master/CONTRIBUTING.md for help
with compiling PyTorch from source.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

                              !! WARNING !!

  warnings.warn(WRONG_COMPILER_WARNING.format(
Traceback (most recent call last):
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1667, in _run_ninja_build
    subprocess.run(
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/subprocess.py", line 516, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

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

Traceback (most recent call last):
  File "pretrain_chem.py", line 82, in <module>
    sys.exit(main())
  File "pretrain_chem.py", line 78, in main
    process(args)
  File "pretrain_chem.py", line 43, in process
    solver.train(num_epoch=5)
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torchdrug/core/engine.py", line 143, in train
    loss, metric = model(batch)
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torchdrug/tasks/pretrain.py", line 139, in forward
    pred, target = self.predict_and_target(batch, all_loss, metric)
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torchdrug/tasks/pretrain.py", line 118, in predict_and_target
    output = self.model(graph, node_feature.float(), all_loss, metric)
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torchdrug/models/gin.py", line 76, in forward
    hidden = layer(graph, layer_input)
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torchdrug/layers/conv.py", line 91, in forward
    update = self.message_and_aggregate(graph, input)
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torchdrug/layers/conv.py", line 340, in message_and_aggregate
    adjacency = utils.sparse_coo_tensor(graph.edge_list.t()[:2], graph.edge_weight,
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torchdrug/utils/torch.py", line 182, in sparse_coo_tensor
    return torch_ext.sparse_coo_tensor_unsafe(indices, values, size)
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torchdrug/utils/torch.py", line 27, in __getattr__
    return getattr(self.module, key)
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torchdrug/utils/decorator.py", line 21, in __get__
    result = self.func(obj)
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torchdrug/utils/torch.py", line 31, in module
    return cpp_extension.load(self.name, self.sources, self.extra_cflags, self.extra_cuda_cflags,
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1079, in load
    return _jit_compile(
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1292, in _jit_compile
    _write_ninja_file_and_build_library(
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1404, in _write_ninja_file_and_build_library
    _run_ninja_build(
  File "/srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1683, in _run_ninja_build
    raise RuntimeError(message) from e
RuntimeError: Error building extension 'torch_ext': [1/2] c++ -MMD -MF torch_ext.o.d -DTORCH_EXTENSION_NAME=torch_ext -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE=\"_gcc\" -DPYBIND11_STDLIB=\"_libstdcpp\" -DPYBIND11_BUILD_ABI=\"_cxxabi1011\" -isystem /srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/include -isystem /srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -isystem /srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/include/TH -isystem /srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/include/THC -isystem /srv/home/wconnell/anaconda3/envs/10-torchdrug/include/python3.8 -D_GLIBCXX_USE_CXX11_ABI=0 -fPIC -std=c++14 -Ofast -fopenmp -DAT_PARALLEL_OPENMP -DCUDA_OP -c /srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torchdrug/utils/extension/torch_ext.cpp -o torch_ext.o
FAILED: torch_ext.o
c++ -MMD -MF torch_ext.o.d -DTORCH_EXTENSION_NAME=torch_ext -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE=\"_gcc\" -DPYBIND11_STDLIB=\"_libstdcpp\" -DPYBIND11_BUILD_ABI=\"_cxxabi1011\" -isystem /srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/include -isystem /srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -isystem /srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/include/TH -isystem /srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torch/include/THC -isystem /srv/home/wconnell/anaconda3/envs/10-torchdrug/include/python3.8 -D_GLIBCXX_USE_CXX11_ABI=0 -fPIC -std=c++14 -Ofast -fopenmp -DAT_PARALLEL_OPENMP -DCUDA_OP -c /srv/home/wconnell/anaconda3/envs/10-torchdrug/lib/python3.8/site-packages/torchdrug/utils/extension/torch_ext.cpp -o torch_ext.o
c++: error: unrecognized command line option ‘-std=c++14’
ninja: build stopped: subcommand failed.

I met the same problems, could you tell me how do you solve it?

same error.. anyone has any ideas for solving this?
I installed with py 3.8 using conda install torchdrug -c milagraph -c conda-forge -c pytorch -c pyg

@natchanon-me Windows is now supported! Please check https://torchdrug.ai/docs/installation.html#windows-powershell

What if I am running VSCode and my project is in a conda environment. Which steps are required to get it up and running? I run Python 3.8 rather than the specified 3.7.


ListItemCheckboxMixin causes ARIA attribute cannot be used: aria-labelledby

Basically, axe-core 4.2.0 code states that

// aria-label and aria-labelledy are not allowed on elements
// without roles, but if the element has text content then
// we will return undefined as a screen reader will read
// the text content

It seems that _renderCheckboxAction function renders a label that does not have an ARIA role according to getRoles of axe-core.
JFYI @bemailloux @johngwilkinson

The issue can be reproduced using this test https://github.com/Brightspace/insights-engagement-dashboard/blob/0b276d36217ba7cd52f3e0e093125a73d3dd46b2/test/components/card-selection-list.test.js#L15


Github Codespaces: Show specific documents after startup

It would be great to show specific documentation after codespaces starts up. There's ways to open files after startup, but you cannot open them in markdown preview mode.
Perhaps we could change the vscode settings to automatically open md as preview (like this)?

In fact, even just leaving the README and opening keys.cfg in addition would be good. But if I start using openFiles, the main README would also disappear (and I can't open it in preview mode).


Two-way binding

I think it would be nice if the directive updated scope.from and scope.to when the slider's internal model changes.
Something like this:
onChange: function (a) {     $scope.from = a.from;     $scope.to = a.to;     $scope.onChange && $scope.onChange({         a: a     }); },

It has been done in #6 as far as I know.


oreg_url work

@pweil- @mjudeikis @kargakis @kwoodson as things stand if/when this gets merged you'll need to change DEPLOY_VERSION=v3.10 (additional v).  Should have done that all along.

Lgtm
On Mon, Jul 23, 2018, 19:04 Jim Minter<EMAIL_ADDRESS>wrote:

Merged #98 https://github.com/jim-minter/azure-helm/pull/98.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jim-minter/azure-helm/pull/98#event-1748237120, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADuFf_rWrMsVsVIjaNtvzQXzqdBHVZysks5uJgIkgaJpZM4VXMH6
.


GCC 8 warns about catching polymorphic types by value

Catching a const reference to the exception is preferred.
Here's the warnings:
libtests/qutil.cc:250:17: warning: catching polymorphic type ‘class std::exception’ by value [-Wcatch-value=]
     catch (std::exception)
                 ^~~~~~~~~
libtests/qutil.cc:29:5: warning: catching polymorphic type ‘class std::runtime_error’ by value [-Wcatch-value=]
     catch (std::runtime_error)
     ^~~~~
libtests/qutil.cc:29:5: warning: catching polymorphic type ‘class std::runtime_error’ by value [-Wcatch-value=]
qpdf/qpdf.cc: In function ‘std::vector<int> parse_numrange(const char*, int, bool)’:
qpdf/qpdf.cc:776:31: warning: catching polymorphic type ‘class std::runtime_error’ by value [-Wcatch-value=]
     catch (std::runtime_error e)
                               ^
qpdf/qpdf.cc: In function ‘void parse_rotation_parameter(Options&, const string&)’:
qpdf/qpdf.cc:1375:17: warning: catching polymorphic type ‘class std::runtime_error’ by value [-Wcatch-value=]
     catch (std::runtime_error)
                 ^~~~~~~~~~~~~
qpdf/test_driver.cc: In function ‘void runtest(int, const char*, const char*)’:
qpdf/test_driver.cc:720:14: warning: catching polymorphic type ‘class std::logic_error’ by value [-Wcatch-value=]
  catch (std::logic_error)
              ^~~~~~~~~~~
qpdf/test_driver.cc:1006:33: warning: catching polymorphic type ‘class std::logic_error’ by value [-Wcatch-value=]
         catch (std::logic_error e)
                                 ^
qpdf/test_driver.cc:1015:33: warning: catching polymorphic type ‘class std::logic_error’ by value [-Wcatch-value=]
         catch (std::logic_error e)
                                 ^
qpdf/test_driver.cc:1112:33: warning: catching polymorphic type ‘class std::logic_error’ by value [-Wcatch-value=]
         catch (std::logic_error e)
                                 ^
qpdf/test_driver.cc:1121:33: warning: catching polymorphic type ‘class std::logic_error’ by value [-Wcatch-value=]
         catch (std::logic_error e)
                                 ^
qpdf/test_driver.cc:1142:33: warning: catching polymorphic type ‘class std::logic_error’ by value [-Wcatch-value=]
         catch (std::logic_error e)
                                 ^
qpdf/test_driver.cc:1188:33: warning: catching polymorphic type ‘class std::logic_error’ by value [-Wcatch-value=]
         catch (std::logic_error e)
                                 ^
qpdf/test_driver.cc:1198:35: warning: catching polymorphic type ‘class std::runtime_error’ by value [-Wcatch-value=]
         catch (std::runtime_error e)
                                   ^
examples/pdf-split-pages.cc: In function ‘int main(int, char**)’:
examples/pdf-split-pages.cc:80:27: warning: catching polymorphic type ‘class std::exception’ by value [-Wcatch-value=]
     catch (std::exception e)
                           ^

thanks

Good timing. I just happen to be tying up some loose ends in preparation for 8.2.0.


Delete messages

Is there a way to delete all messages (or all messages  since )?

There is no way to delete messages, no. But they are only cached for 12h so they go away pretty quickly.


JavaDistributionPluginTests no longer produces infinite loop process

Coverage remained the same at 99.408% when pulling 0dfe1026b9e2165c36decca8aa16c54740635d27 on rfink/infinite-test-loop into 07df6a9dc84e9a1ad9ff0a52528adf1ffd12d9b1 on develop.


Update service-gateway-sso-kerberos-sap-bw-commoncryptolib.md

Adding additional troubleshooting step, remove reference to admin requirement. The admin requirement was a workaround for a more targeted permissions-based fix.

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

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

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

#sign-off

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


Cannot connect my local websocket server

Like this picture above, the connect button is disable.

@WafeiBaBa Thanks for reporting the issue. Will fix it ASAP. Meanwhile you can access your local WebSocket endpoints from wss://<IP_ADDRESS>:8080/ws

@liyasthomas any progress ? else I will pick it up.

@AndrewBastin sorry for the delay. I caught up with some personal stuffs. The issue is regarding the newly implemented regex for WSS url validation. Port number on localhost isn't passing. Think you can add that to regex.


GUI Item display not working with log variants

What is your Quests version / build number (do not say "latest")?
quests 3.7.8      minecraft 1.12.2
Describe the problem and how to replicate it. Any console errors to post using Pastebin.com?  if you make a gui item display a birch log itll show up as an oak log when youre done with the quest. no console errors
If applicable, can you provide an example quest from quests.yml using Pastebin.com?
yeah sure hold up, https://pastebin.com/SHkd90FU

Thanks for your report. Use the following development build or wait until the next Spigot release:
https://ci.codemc.org/job/PikaMug/job/Quests/33/


Cannot annotate a const generic function with a contract

This issue was reported in https://github.com/model-checking/verify-rust-std/discussions/143.
I tried this code:

#[kani::requires(true)]
const fn bar<T>(_v: T)
where T: Sized
{
}

using the following command line invocation:
kani s.rs -Zfunction-contracts

with Kani version: 1fe80f9c5b2

$ kani s.rs -Zfunction-contracts
Kani Rust Verifier 0.56.0 (standalone)
error[E0493]: destructor of `T` cannot be evaluated at compile-time
 --> s.rs:2:17
  |
1 | #[kani::requires(true)]
  |                       - value is dropped here
2 | const fn bar<T>(_v: T)
  |                 ^^ the destructor for this type cannot be evaluated in constant functions

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0493`.
error: /home/ubuntu/git/kani/target/kani/bin/kani-compiler exited with status exit status: 101

This is not a Kani issue though. If you remove the contract and try to run it with rustc, the same error occurs:
// dummy.rs
pub const fn bar<T>(_v: T)
where T: Sized
{
}

Running:
rustc dummy.rs

Returns
error[E0493]: destructor of `T` cannot be evaluated at compile-time
 --> dummy.rs:1:21
  |
1 | pub const fn bar<T>(_v: T)
  |                     ^^ the destructor for this type cannot be evaluated in constant functions
...
4 | }
  | - value is dropped here

error: aborting due to 1 previous error

The problem here is that the function has a local parameter that may implement Drop, and that will be marked as dead by the end of the functions. But constant functions cannot call drop.
Note that if the function does not drop the value, that is OK:
pub struct WithDrop;
pub struct Wrap<T>(T);

impl Drop for WithDrop {
    fn drop(&mut self) {}
}

pub const fn will_not_drop(v: WithDrop) -> Wrap<WithDrop>
{
    Wrap(v)
}

pub const fn will_drop(_v: WithDrop)
{
}

Note that the function will_not_drop is OK, but the will_drop has a compilation error:
error[E0493]: destructor of `WithDrop` cannot be evaluated at compile-time
  --> dummy.rs:13:24
   |
13 | pub const fn will_drop(_v: WithDrop)
   |                        ^^ the destructor for this type cannot be evaluated in constant functions
14 | {
15 | }
   | - value is dropped here

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0493`.
I'm going to close this for now, but please let me know if you have another example in mind.

@celinval Thanks for clarifying. In the original issue (https://github.com/model-checking/verify-rust-std/discussions/143), the error only appears when the function is annotated with a requires clause.

Here is a small example of the issue in https://github.com/model-checking/verify-rust-std/discussions/143:
#![feature(const_ptr_write)]

struct Foo<T> {
    ptr: *const T,
}

impl<T: Sized> Foo<T> {
    #[cfg_attr(kani, kani::requires(true))]
    const unsafe fn bar(self, v: T)
    where
        T: Sized,
    {
        unsafe { core::ptr::write(self.ptr as *mut T, v) };
    }

}

fn main() {}

rustc succeeds:
$ rustc w.rs
warning: struct `Foo` is never constructed
 --> w.rs:3:8
  |
3 | struct Foo<T> {
  |        ^^^
  |
  = note: `#[warn(dead_code)]` on by default

warning: method `bar` is never used
 --> w.rs:9:21
  |
7 | impl<T: Sized> Foo<T> {
  | --------------------- method in this implementation
8 |     #[cfg_attr(kani, kani::requires(true))]
9 |     const unsafe fn bar(self, v: T)
  |                     ^^^

warning: 2 warnings emitted

but Kani fails:
$ kani w.rs
Kani Rust Verifier 0.56.0 (standalone)
warning: the feature `const_ptr_write` has been stable since 1.83.0 and no longer requires an attribute to enable
 --> w.rs:1:12
  |
1 | #![feature(const_ptr_write)]
  |            ^^^^^^^^^^^^^^^
  |
  = note: `#[warn(stable_features)]` on by default

error[E0493]: destructor of `T` cannot be evaluated at compile-time
 --> w.rs:9:31
  |
8 |     #[cfg_attr(kani, kani::requires(true))]
  |                                         - value is dropped here
9 |     const unsafe fn bar(self, v: T)
  |                               ^ the destructor for this type cannot be evaluated in constant functions

Thank you for the new example @zhassan-aws. I was able to reproduce it on my side. The problem here seems to be coming from the logic Kani encodes to stub the function.
During stubbing, Kani assign a new value to the return value instead of using the value passed as an argument like the other modes. Thus, the function could potentially drop the value, and the compilation fails.
One potential fix that comes to mind would be to change Kani to do a dummy assignment of the input variables to local variables inside the generated closure. Since the closure doesn't get called in the constant context, the compiler will no longer complain about the drop.


Works Intermittently

This seems to only work intermittently. It rarely works on the first attempt. Sometimes if I choose to continue trying after the first ping fail, it works after several minutes. Sometimes it never ends up coming on. I've tried a couple of other WOL scripts and had similar results so I imagine it's something to do with the XB1 rather than your script. Do you have any ideas why this is happening or at least, have you seen similar issues?

Sorry, just read through your closed issues and saw that this is indeed common behavior. Closing this issue.


#1591 #1726

#1591 Peek/Goto definition for library functions should work like View(func)
#1726 Xaml binding error in variable explorer

tests

Will move around and use interactive workflow provider as discussed offline


Fixing more const qual drop warnings

Same old errors, and this fixes the warnings in tpp-mlir. Errors will be fixed in #23.


No apparent way to unload a Nuget package after #r, to support reloading an earlier package

Is your feature request related to a problem? Please describe.
Before I came across issue #50 I wanted to try using Google charts, so I added the following:
#r "nuget:XPlot.GoogleCharts,3.0.1"

Then, when I try the following:
var geoPlot = XPlot.GoogleCharts.Chart.Geo(
    byDensity.Select(i => i.Item3),
    byDensity.Select(i => i.Item1)
);
display(geoPlot);

...I get the following error:
(1,15): error CS1705: Assembly 'XPlot.GoogleCharts' with identity 'XPlot.GoogleCharts, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' uses 'FSharp.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' which has a higher version than referenced assembly 'FSharp.Core' with identity 'FSharp.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

OK, so let's go change that #r to try an earlier version of the package with dependencies on an earlier version of FSharp.Core:
#r "nuget:XPlot.GoogleCharts,3.0.0"

But that yields:
XPlot.GoogleCharts version 3.0.0 cannot be added because version 3.0.1 was added previously.

Spent hours now looking at the source code here, reading about CSX scripting and the commands available there, to no avail. It looks like (on Linux Mint) the library is installed at ~/.nuget/packages/xplot.googlecharts, but I don't want to just delete that directory, since I am worried that isn't the right way to do it.
Describe the solution you'd like
Some way, either through the notebook menu or with something like an #unload or magic command to remove a nuget package to then allow replacing it.
Describe alternatives you've considered

Deleting the above .nuget/packages subdirectory, but I fear breaking something.

Looked at the raw .ipynb file for my notebook, but didn't see anything leap out at me there.

This is by design in .NET Interactive. The solution, for now, is to restart the kernel and install the version you need.
Picture this sequence of submissions:
#r "nuget:DinosaursLib,1.0.0"
var brontosaurus = new Brontosaurus();
var dinosaurs = new List<Dinosaur>
{
  brontosaurus
};

...and then, assuming we allowed referencing a second version (which, it's worth pointing out, C# scripting does allow for .dll references):
#r "nuget:DinosaursLib,2.0.0" // new version of DinosaursLib, where Brontosaurus is obsolete
var dinosaurs.Add(new Apatosaurus());

The second submission gives a compile error because we've loaded two versions of DinosaursLib and we have two different Dinosaur types, but our dinosaurs list references Dinosoaur from version 1.0.0.
This kind of error is pretty confusing and hard to reason about, especially when it crops up (as it usually will) in transient references. It's also hard to recover from because you already have a bunch of compiled code from earlier in the session referencing the older version. It still can't really be solved without restarting the kernel.
We did consider just loading these into separate AssemblyLoadContext instances. While it might address some special cases, it's still very hard to reason about.
Hope that makes sense. Thoughts?

This is by design in .NET Interactive. The solution, for now, is to restart the kernel and install the version you need.

Doh! So simple! I thought it must be a permanent part of the notebook.

Hope that makes sense. Thoughts?

That does make sense. Thanks for the quick turnaround. And I learned a lot just playing around on a Saturday morning along the way.
Closing the ticket.


🐞 - documentRef.createRange is not a function at new TuiLineClampDirective on server side (SSR)

Which @taiga-ui/* package(s) are the source of the bug?
kit
Please provide a link to a minimal reproduction of the bug
No response
Description
When rendering a <tui-line-clamp> on server side, I get the following error: documentRef.createRange is not a function.
Angular version
13.2.0
Taiga UI version
2.35.0
Which browsers have you used?

[X] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[X] macOS
[ ] Windows
[ ] Linux
[ ] iOS
[ ] Android

(Note that I do use @ng-web-apis/universal, I tried both your version, 1.9.5, and the latest, 2.0.0)

@VictorienTardif thank you for the report. We will patch this on our side but the issue is coming from DOCUMENT token from Angular so if you want this to be fixed at the root cause, it's best to file an issue with Angular as well.

https://github.com/angular/angular/issues/45163


Remove lifecycle manager deps

Description
Changes proposed in this pull request:

Remove lifecycle manager dependencies
Update k8s deps to 1.26
Update Istio library to version complaint with k8s 1.26

Related issue(s)

https://github.com/kyma-project/istio/issues/109

/test all

/test all

/retest


Merge/05 24

Merge from blockly develop
@rachel-fenichel a few things I noticed that should be checked a bit more closely:

[ ] The targetBlock/startBlock change in gesture.js
[ ] The way the variable blocks are generated using the new variableModel. We have different variable blocks from blockly, as well as generating them in a different way. I believe I converted it over correctly, but that would be one area where it would be easy to make a mistake.
[ ] Some of the other dropdown div hide vs. widget hide seems to have changed, not sure if that is right?

Variable sanity check complete.

@rachel-fenichel and @marisaleung thank you both for the quick review! The last few commits address your comments.

Looks awesome! lgtm after nit.

LGTM

@marisaleung thanks fixed the spacing.


Supported Versions

Please add what versions of S4/HANA are supported by Microsoft Purview. If all, please state that explicitly.
Thank you

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

ID: 4966409a-b58e-8892-b99f-f7673b9841bf
Version Independent ID: afdc938f-ac77-6614-bd82-67eb6673b4da
Content: Connect to and manage SAP HANA - Microsoft Purview
Content Source: articles/purview/register-scan-sap-hana.md
Service: purview
Sub-service: purview-data-map
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@Edcorcor  Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@Edcorcor - thanks for reaching out! I am confirming the available versions with engineering and then I'll add it to the documentation. I expect to have this updated by early next week at the latest.

I have submitted an update to the documentation as well! You should see it reflected later this afternoon.

#please-close


Example with code

Hi @AndreiMisiukevich
could you translate your XAML example in CSHARP?
Thanks
Alessandro

Hi.
Sure, I will do it and let you know
Thanks for feedback

wow, you are fast. Thanks!

Readme is updated =)

Thanks I take a look


TextEditingController gets triggered twice when deleting characters from TextField

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Just use the official example for controlled text input on the latest stable release:
https://docs.flutter.dev/cookbook/forms/text-field-changes
Expected results
The characters should not show up twice in the console when deleting them:

Actual results
The last character gets printed twice to the console when deleting it:

Code sample
Code sample
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      title: 'Retrieve Text Input',
      home: MyCustomForm(),
    );
  }
}

// Define a custom Form widget.
class MyCustomForm extends StatefulWidget {
  const MyCustomForm({super.key});

  @override
  State<MyCustomForm> createState() => _MyCustomFormState();
}

// Define a corresponding State class.
// This class holds data related to the Form.
class _MyCustomFormState extends State<MyCustomForm> {
  // Create a text controller and use it to retrieve the current value
  // of the TextField.
  final myController = TextEditingController();

  @override
  void initState() {
    super.initState();

    // Start listening to changes.
    myController.addListener(_printLatestValue);
  }

  @override
  void dispose() {
    // Clean up the controller when the widget is removed from the widget tree.
    // This also removes the _printLatestValue listener.
    myController.dispose();
    super.dispose();
  }

  void _printLatestValue() {
    print('Second text field: ${myController.text}');
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('Retrieve Text Input'),
      ),
      body: Padding(
        padding: const EdgeInsets.all(16.0),
        child: Column(
          children: [
            TextField(
              onChanged: (text) {
                print('First text field: $text');
              },
            ),
            TextField(
              controller: myController,
            ),
          ],
        ),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.1, on macOS 13.3.1 22E261 darwin-arm64, locale de-DE)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
[✓] Android Studio (version 2020.3)
[✓] VS Code (version 1.78.1)
[✓] Connected device (2 available)
[✓] Network resources

same problem...

This breaks my search completely... Did you find any workaround so far?

Thanks for filing this issue @kamami. This https://github.com/flutter/flutter/issues/45804#issuecomment-1234656811 is similar to this issue. Closing this as there is a similar issue currently open #45804, kindly follow up on the issue for further updates.
Thank you!


updating python scripts to fix install failures with python2.7 lambda…

… requirements

minor update to python version


add a chapter on enum representation

This is a proposed summary chapter on enum representation. I made a best effort to represent what seemed to be the consensus from #10 but I would definitely appreciate review, as I confess I kind of wrote this in a hurry and could easily have missed some details or objections. 😛
Here are the important details:

Uninhabited enums (no variants) are guaranteed to share layout with !
C-like enums are
I copied the definition of the layout of #[repr] enums from RFC #2195
I coined the term "discriminant elision" to describe the "Option optimization"
I adopted what seemed like a fairly restrictive definition of "option-like enums"; these are the enums for which we guarantee "discriminant elision".

It does permit enums with more than one unit variant. only one unit variant now
The unit variant must have no fields, like None, and hence this definition excludes Result<T, ()>
I was thinking this would be better for now, so as to sidestep the problem of defining zero-sized structs and so forth, but I would be happy for us to revisit it.

I left a few (non-normative, caveated) notes about niche values. mostly removed

Here are a few questions:

Is my definition of "option-like enums" acceptable? I think it is crucial to include Option<&T> as having a guaranteed optimization, but am somewhat flexible beyond that
We never settled on a term for "niche values". I simply used "niche values" here but I was thinking after writing that perhaps "illegal" or "undefined values" would be better?
In writing this summary, I realize I did not specify anything about variants with uninhabited types and so forth. Perhaps I should leave this as "future work"?

Fixes #10
cc @eddyb in particular for technical review

Comments added, mostly nits. The big one is that it would be nice to have the defn of "niche value" in this section rather than hidden away in another "representation invariant" section. This would make the "representation" section self-contained, and get rid of the need for "bitstring validity".

Comments added, mostly nits. The big one is that it would be nice to have the defn of "niche value" in this section rather than hidden away in another "representation invariant" section. This would make the "representation" section self-contained, and get rid of the need for "bitstring validity".

OK, pushed a few updates to resolve comments so far.

Addressed outstanding feedback I believe. =)

I'm marking this with FINAL COMMENT PERIOD, it's been idle for quite a while.

Still LGTM.
My only nits are that Rust code in the wild already relies on many enum optimizations that are not guaranteed, and that makes the unsafe code guidelines less useful and more complicated than what they could be.
For example, the answer to the question: "Can I use Option<&T> on C FFI where pointers are expected?" is not "Yes.", but rather, "That relies on an optimization that is not guaranteed to happen, but in practice, yes, you can rely on that.". The same applies to data-carrying enums with ZST variants, fieldless enums with one variant, etc.
We don't have to provide better answers to these questions right now, but we should strive to do so in 2019, e.g., via an RFC about guaranteed enum optimizations or something like that.

That relies on an optimization that is not guaranteed to happen

Doesn't this guarantee the optimization?

Option-like enums where the payload defines at least one niche value
are guaranteed to be represented using the same memory layout as their
payload.

Doesn't this guarantee the optimization?

If it were normative, it would, but a couple of lines above the document states that everything that follows isn't normative :/
We discussed this briefly in the meeting, and @nikomatsakis wanted to open an issue to track all non-normative things that we'd like to RFC at some point and why.

but a couple of lines above the document states that everything that follows isn't normative :/

I agree it should be made normative through an RFC, but you made it sound like a change in this document could make you happy ("my only nits are ...").  I don't understand how that can be the case.  Nothing we write here can change the fact that this is not normative.

Ah no, sorry! I didn't meant to say that, only that we should fill some issues about this and once we do that hyperlink them here, but that can be done as a follow up PR, once this is merged and those issues are filled.


Missing \toolsrc\Release\vcpkg.exe and 460 more error after run bat file

Missing \toolsrc\Release\vcpkg.exe and 460 more error after run bat file.
Repositry isn't full? A lot of missing files.

Could you try re-cloning the repository?
If none of that provides any useful information, could you send us the full error log at<EMAIL_ADDRESS>Thanks for reporting this issue!

My latest Windows SDK 10.0.15063.0 don't have shlobj.h, so it failed

I'm successful when I manually changed bootstrap.ps1
$windowsSDK = '10.0.14393.0'

Please open a new issue if this is still a problem for you.


[BUG] disableTelemetry option does not work

Adding 'disableTelemetry' configuration option to Application Insights Configuration - cfg  disables telemetry regardless of the value of the option.

What version of the SDK do you observe this behavior in?

This is Javascript and it is the latest one I got from AI page.

@Tilldawnbreak
Do you mind sharing your cfg? I tested the latest snippet and it seems working.

cfg: { // Application Insights Configuration
connectionString: "InstrumentationKey=[omitted]"
,disableTelemetry : "true" ,loggingLevelTelemetry : "2"
/* ...Other Configuration Options... */
}
telemetry is disabled regardless of the value of the 'disableTelemetry'.

@Tilldawnbreak
do you mind try disableTelemetry : false (Note: it is Boolean, NOT String)

That worked,  thank you for looking into this, closing the bug as user error.


Proper poet challenge submit timeout

Motivation
Currently, there is a hardcoded 10s timeout for all requests to the Poet service. It's limiting, we might want to wait longer or shorter depending on the situation. The user should set the timeout.
Changes
Removed the context factory from the HTTP Poet client. The user of the client decides about the timeout on a per-request basis.
Test Plan

added unit tests verifying if a hanged challenge submit times out properly.

bors try

bors merge

bors merge


Couldn't catch exception from Rails controller

Description of the bug
If rails controller has error, then there is no exception_event from span.
For example, below is a sample rails controller, and create_error is not defined from User, so it should create error
class UsersController < ApplicationController
  # curl http://<IP_ADDRESS>:8002/users/new
  def new
    @user = User.new
    @user.create_error
  end
end

The sample span from above call
span_data: #<struct OpenTelemetry::SDK::Trace::SpanData name="UsersController#new",
kind=:server, status=#<OpenTelemetry::Trace::Status:0x0000ffffa17e7588 @code=2, @description="">,
parent_span_id="\x00\x00\x00\x00\x00\x00\x00\x00", total_recorded_attributes=12, total_recorded_events=0,
total_recorded_links=0, start_timestamp=1693241683805542134, end_timestamp=1693241684087133009,
attributes={"http.method"=>"GET", "http.host"=>"<IP_ADDRESS>:8002", "http.scheme"=>"http", "http.target"=>"/users/new",
 "http.user_agent"=>"curl/7.74.0", "code.namespace"=>"UsersController", "code.function"=>"new",
"http.status_code"=>500}, links=nil, events=nil, resource=#<OpenTelemetry::SDK::Resources::Resource:0x0000ffffa4c8bf50
@attributes={"service.name"=>"unknown_service", "process.pid"=>151, "process.command"=>"bin/rails",
"process.runtime.name"=>"ruby", "process.runtime.version"=>"3.1.0", "process.runtime.description"=>"ruby 3.1.0p0 (2021-12-25 revision fb4df44d16) [aarch64-linux]",
"telemetry.sdk.name"=>"opentelemetry", "telemetry.sdk.language"=>"ruby", "telemetry.sdk.version"=>"1.2.0"}>,
instrumentation_scope=#<struct OpenTelemetry::SDK::InstrumentationScope
name="OpenTelemetry::Instrumentation::Rack", version="0.22.1">, span_id="F\x7F#\xA7\x80D\e%",
trace_id="\x83\x14\n\x9D\xB68M\x9B\x00\xD3x\xFE\xDF\xE0)0", trace_flags=#<OpenTelemetry::Trace::TraceFlags:0x0000ffffa5c08bb8 @flags=1>,
tracestate=#<OpenTelemetry::Trace::Tracestate:0x0000ffffa4bd91c0 @hash={"sw"=>"0000000000000000-01"}>>

Even though the status_code is 500, but there is no exception.
I checked the opentelemetry-instrumentation-rack between L81-L82, there is no record_exception even the status is 500.  I added request_span.record_exception(Exception.new) if status == 500 between 81 and 82, and rack span can create exception_event.
I tried to produce error from action_view, and the exception was caught in span.
I am wondering is there particular reason or the error should be handled in somewhere else?
Similar issue I found is https://github.com/open-telemetry/opentelemetry-ruby-contrib/issues/56
Share details about your runtime
Operating system details: Debian GNU/Linux aarch64 GNU/Linux
RUBY_ENGINE: "ruby"
RUBY_VERSION: "3.1.0"
RUBY_DESCRIPTION: "ruby 3.1.0p0 (2021-12-25 revision fb4df44d16) [aarch64-linux]"
Share a simplified reproduction if possible
opentelemetry-version
opentelemetry-api (1.2.2)
opentelemetry-common (0.19.6)
opentelemetry-instrumentation-action_pack (0.5.0)
opentelemetry-instrumentation-action_view (0.4.0)
opentelemetry-instrumentation-active_job (0.4.0)
opentelemetry-instrumentation-active_model_serializers (0.19.1)
opentelemetry-instrumentation-active_record (0.5.0)
opentelemetry-instrumentation-active_support (0.3.0)
opentelemetry-instrumentation-all (0.31.0)
opentelemetry-instrumentation-rack (0.22.1)
opentelemetry-instrumentation-rails (0.25.0)
opentelemetry-registry (0.3.0)
opentelemetry-sdk (1.2.0)
opentelemetry-semantic_conventions (1.10.0)

move to contrib


export Condition

We can use this with the TemplateEngineManager to add Conditions to custom blocks (as we do in the AdvancedBlock)
Another option is to export generateAdvancedBlock. WDYT?

Discord is not working, can you please check

We can use this with the TemplateEngineManager to add Conditions to custom blocks (as we do in the AdvancedBlock)
Another option is to export generateAdvancedBlock. WDYT?

I think it would be more appropriate to cover TemplateEngineManager.


Feature/norm assoc type

Note: This subsumes #118
This is part of a greater effort to remove old_impl_check from nphysics
Discussion - which other traits are going to be similarly transformed?

I’ve made some work a few weeks ago on using associated types for most trait that may be transformed. You'll find it on the associated_types branch. Naming needs to be discussed (currently I kind of followed a common pattern for all names with the name of the trait followed by Type). Also all the implementations are commented out at the moment.
I stopped working on it because it ICEd (and still does with the last nightly)...

Yep, still ICE

Opened https://github.com/rust-lang/rust/issues/24179


SIGABRT being caused when disposing resources?

Describe the bug
I'm getting SIGABRT crashes when Filament resources are being disposed.
On my home screen, I'm using ModelViewer to display a model I created in Blender. It's just a simple cube that has one of the sides painted blue.

When I tap the cube icon on the bottom left corner of the screen, we show another screen that is using another ModelViewer to display a more complex cube.

When I navigate to the 2nd screen from the 1st one, I usually get SIGABRT crashes (attached below) and I can't figure out how to fix it.
Here's how I'm creating the models
val buffer = assets.open("models/cube1x1_1.glb").use { input ->
	val bytes = ByteArray(input.available())
	input.read(bytes)
	ByteBuffer.wrap(bytes)
}

modelViewer.loadModelGlb(buffer)
modelViewer.transformToUnitCube()

I'm not disposing anything manually, I'm leaving it all for ModelViewer to dispose
Logs
Crash from Crashlytics: https://gist.github.com/victorbrndls/cd93f8ec4a2679956c64e32bfd719446
Crash from Logcat: https://gist.github.com/victorbrndls/82fe62f846a7c70fff876fe7b6129e87
I also noticed that most crashes show that the user had little RAM free. It usually ranges from 30mb to 130mb on Crashlytics.
Smartphone (please complete the following information):

Device: Redmi Note 7
OS: Android 10

Do you have the lines right before https://gist.github.com/victorbrndls/82fe62f846a7c70fff876fe7b6129e87 ?

https://gist.github.com/victorbrndls/9e7c3acd6e09465d1fd7878be3379352

This is the memory usage if I open the 2nd screen right after the 1st one is created. It crashes

This is the memory usage if I open the 2nd screen a few seconds after the 1st one is created. It doesn't crash

We really don't have enough to go on here. This seems like a problem specific to this application or devices. Something is calling abort() it might be the runtime because its running out of heap space, or something else.
I think this is more appropriate for discussions than issues. You could try to attach a debugger and see what happens, you could also use a debug version of filament.


Run some tests weekly instead of on every PR.

Overview
Move some test to run weekly, rather than on every PR.
EDIT: This is based on the feat/openstack-integration branch. Merge that PR first.
Rationale
Development will shift to OpenStack integration runners. Focus will be on juju 3+.
The local LXD runners and juju 2.9 tests will not need to be ran every PR.
Checklist

[x] The charm style guide was applied
[x] The contributing guide was applied
[x] The changes are compliant with ISD054 - Managing Charm Complexity
[x] The documentation is generated using src-docs
[x] The documentation for charmhub is updated.
[x] The PR is tagged with appropriate label (urgent, trivial, complex)

Close when the other PR merges


Visual Studio Test task silently passes while exception was thrown during the test

Hi folks,
Seems like the VS Test task is not able to report the exception. Not sure if there is anything missing from my side. Thanks in advance!
Environment

Server - VSTS

If using VSTS, provide the account name, team project name, build definition name/build number:

account name: msasg
project name: Bing_and_IPG
build definition name: EKG Rolling Build
build number: 1.0.1809.19020

Agent - Hosted:

If using Hosted agent, provide agent queue name:
Hosted VS2017

Issue Description
If you check the task named "Unit Integration Tests", exception was thrown, while the task was still marked as successful.
Task logs
NUnit Adapter <IP_ADDRESS>: Test execution started
2018-09-19T18:44:57.9516585Z Exception System.IO.FileNotFoundException, Exception thrown executing tests
2018-09-19T18:44:57.9517615Z Could not load file or assembly 'System.Xml.XPath.XmlDocument, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
2018-09-19T18:44:57.9519261Z    at NUnit.VisualStudio.TestAdapter.NUnit3TestExecutor.RunAssembly(String assemblyPath, TestFilter filter)
2018-09-19T18:44:57.9520853Z    at NUnit.VisualStudio.TestAdapter.NUnit3TestExecutor.RunTests(IEnumerable`1 sources, IRunContext runContext, IFrameworkHandle frameworkHandle) in D:\repos\nunit\nunit3-vs-adapter\src\NUnitTestAdapter\NUnit3TestExecutor.cs:line 97

@hengjiaqi the issues template clearly asks for the entire logs zip with system.debug set to true in the build definition.
Please provide those. Also verify if when running locally with vstest.console.exe and the same error occurs whether the test run is marked as failed or not.

@ShreyasRmsft , thanks for the response, please refer to the log with system.debug set to true. I don't see the same error when running locally.
log_15_3360757.zip

@hengjiaqi please provide the complete zip file you get when you click download all logs. There are additional files we upload apart from the task logs that help with diagnosing issues on the testplatform side and these are present in the complete zip.

log_9_3367396.zip
@ShreyasRmsft  Please refer to the entire log of the build definition.

@ShreyasRmsft Any updates?


Fix UwpList parsing

This fixes the issue with UwpList and line endings reported in ticket #2
It just changes the parser instead of changing the gitattributes and having to recommit every file in the repository 👍
There was a recent commit that also broke the parser and deleted the caps.txt (2a6dc2bcd93a1d75fc3837bae6cb827d49b0217a) this PR also fixes those issues too 😄

Pavel can you please make a new release that has these fixes? Right now both releases are broken.

Will do

Fixed (I think) and pushed


[ldd-geom] Add incidence and heliocentric range for surface geometry

Two related items:

Okay so this one I'd like your opinion on.
We have three keywords:
PHASE ANGLE
SOLAR_INCIDENCE_TARGET_ANG
SOLAR_INCIDENCE_TARGET_ANG_NAME
The first is measured at the boresight of the camera and fits nicely in Derived_Geometry.phase_angle.
The second could fit in Derived_Geometry.incidence_angle.  However, there's that pesky name, which identifies where the incidence angle is measured.  In this case, it's the SuperCam cal target.  So we need to identify that.
This looks like a good use of Illumination_Specific, a child of Illumination_Geometry, except for two things:

Illuminatation_Geometry is only available under Geometry_Orbiter (not surface)
it doesn't allow for an arbitrary target name (requires having an entry in Geometry_Target_Identification which requires some SPICE stuff that are not applicable on the ground).

So there are two possible solutions here (well, many possible, but two that I've thought of that make sense):

Add Illumination_Geometry as a child of Geometry_Lander, add Named Target as a valid for reference_location, add reference_name as an additional child of Illumination_Geometry, and set maxOccurs="any" for Illumination_Specific.

simply add target_name as an optional child of Derived_Geometry.

Of the two, #2 is simpler and more in keeping with the surface paradigm, but #1 helps bridge the gap between lander and orbiter, if that is at all desired (it may not be, dunno).
For #1 it would look like:
<geom:Geometry_Lander>
  ... stuff
  <geom:Illumination_Geometry>
    <geom:Illumination_Specific>
      <geom:reference_pixel_location>Center</>
      <geom:phase_angle unit="deg">40</>
    </>
    <geom:Illumination_Specific>
      <geom:reference_location>Named Target</>
      <geom:reference_name>Supercam Calibration Target</>
      <geom:incidence_angle unit="deg">20</>
    </>
  </>
</>

For #2 I'd have additional DG groups for these, e.g.
<geom:Derived_Geometry>
  ... the normal Site geometry stuff
</>
<geom:Derived_Geometry>
  ... the normal Rover geometry stuff
</>
<geom:Derived_Geometry>
  <geom:target_name>Boresight</>
  <geom:phase_angle unit="deg">40</>
</>
<geom:Derived_Geometry>
  <geom:target_name>Supercam Calibration Target</>
  <geom:incidence_angle unit="deg">20</>
</>

Looking at these I tend to like #2 better, but would like your opinion.
P.S.  for target_name, definition: Specifies the name of the target location for items in this class.

MARS_HELIOCENTRIC_RANGE
Again there's an existing class (Distances_Specific) but it's only allowed as a child of Geometry_Orbiter.
But there's a problem with it: it has target_geoctric_distance, target_heliocentric_distance, and target_ssb_distance... but nothing I can find that identifies what the "target" is!  This would seem to be a problem generally, if you wanted to use this in orbital.
So again there's a choice:

Add Distances as a child of Geometry_Lander, and add "target_name" as an optional child of Distances_Specific.  (for good measure also make maxOccurs=any for Distances_Specific, although I don't need it right now).

Add heliocentric_range as a child of Derived_Geometry

These would look like for #1:
<geom:Geometry_Lander>
  ... stuff
  <geom:Distances>
    <geom:Distances_Specific>
      <geom:target_name>Mars</>
      <geom:target_heliocentric_range unit="km">2.07e8</>
    </>
  </>
</>

or for #2:
<geom:Derived_Geometry>
  <geom:target_name>Mars</>
  <geom:heliocentric_range unit="km">2.07e8</>
</>

Again I kind of lean toward #2 but #1 feels less bad here than with the illumination angles, for some reason.

After email discussion, here's the current proposal, stripped of all the options:
First, here's the suggested end state for the labels:
<geom:Derived_Geometry>
  ... the normal, existing Site geometry stuff
</>
<geom:Derived_Geometry>
  ... the normal, existing Rover geometry stuff
</>
<geom:Derived_Geometry>
  <geom:target_name>Boresight</>
  <geom:phase_angle unit="deg">40</>
</>
<geom:Derived_Geometry>
  <geom:target_name>SuperCam Calibration Target</>
  <geom:incidence_angle unit="deg">20</>
</>
<geom:Derived_Geometry>
  <geom:target_name>Mars</>
  <geom:target_heliocentric_distance unit="km">2.07355e8</>
</>

Changes needed to get there:

Add an instance of geom:target_heliocentric_distance to geom:Derived_Geometry.  Reusing the existing keyword. Goes inside the existing xs:choice block (along with incidence_angle, etc).

Move Vector_Solar_Direction

Add a new keyword, geom:target_name to geom:Derived_Geometry.  This would go outside the xs:choice block, with a cardinality 0-1.

New keyword definition:
target_name: Specifies the name of the target location for items in this class.
Valid list for target_name would be unspecified at the geom: dictionary level, mission-specific dictionaries can specify values for validation purposes if desired.
Additional changes that came up in discussion:

Modify definition of Vector_Solar_Direction to say:  Unit vector pointing in the direction of the Sun at the time of the observation, from the point of view of the instrument making the observation (unless specified otherwise by target_name).

Move the Vector_Solar_Direction inside the xs:choice block in Derived_Geometry.


fastly: 8.1.0 -> 8.1.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/fastly/cli/releases.
meta.description for fastly is: Command line tool for interacting with the Fastly API
meta.homepage for fastly is: https://github.com/fastly/cli
meta.changelog for fastly is: https://github.com/fastly/cli/blob/v8.1.2/CHANGELOG.md
Updates performed

Golang update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 8.1.2 with grep in /nix/store/4zn1061rhmnw4lbdrwjjkn5b5i5l63pw-fastly-8.1.2
found 8.1.2 in filename of file in /nix/store/4zn1061rhmnw4lbdrwjjkn5b5i5l63pw-fastly-8.1.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
fastly

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4zn1061rhmnw4lbdrwjjkn5b5i5l63pw-fastly-8.1.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A fastly https://github.com/r-ryantm/nixpkgs/archive/f0940dac89fcd5b0e12b517161cc46b4772ca318.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4zn1061rhmnw4lbdrwjjkn5b5i5l63pw-fastly-8.1.2
ls -la /nix/store/4zn1061rhmnw4lbdrwjjkn5b5i5l63pw-fastly-8.1.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

fastly

Maintainer pings
cc @ereslibre @shyim for testing.

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

1 package built:

fastly

Result of nixpkgs-review pr 223686 run on aarch64-darwin 1

1 package built:

fastly


Shakyground: 'Canvas tainted' when WMS is displayed

When a shakyground-wms result is displayed in the frontend, no popups work anymore. The reason is that the browser refuses to interact with the canvas, because it has been 'tainted' by 3rd party content.
https://gis.stackexchange.com/questions/199540/avoiding-cors-error-with-openlayers-3 suggests that this can be resolved serverside with correct headers and clientside with the 'crossOrigin' attribute.

I have implemented testing solution for this on the server. But the CORS headers are set only if there is the "Origin" header send in the request.
For the demonstrator I can see that RetrieveResultServlet request has this header is set to http://riesgos.dlr.de/ but not for the WMS requests to the GeoServer, like http://rz-vm140.gfz-potsdam.de/geoserver/wms
Is it possible that you can somehow add the "Origin" header to the request made to the WMS endpoint?

Done! Works like a charm :) App is building right now, should be online in a minute...

Spiffy! That was awesome work! Closing happily :)


3.11 memory missing import

Owing to my yahoo image restoration process, these didn't make it in for sunday the 17th.

I took a look at our scripts and they grab the past weeks data from the 3.11 memories source. This means that the January 17th upload actually made it in on the next day. A look at the database confirms this!


Detect Changes

Hi Dear;
I was looking at your code, I found this part Detect Changes
I need help to understand what does it mean 0.3 , 0.01, et?. what is the standard of 300 and how it is obtained to be as change_threshold?.
May anyone help me in clarification this part, please?.
I'd appreciate your cooperation
`if 'prev_color_img' in locals():
    # Detect changes
    depth_diff = abs(depth_heightmap - prev_depth_heightmap)
    depth_diff[np.isnan(depth_diff)] = 0
    depth_diff[depth_diff > 0.3] = 0
    depth_diff[depth_diff < 0.01] = 0
    depth_diff[depth_diff > 0] = 1
    change_threshold = 300
    change_value = np.sum(depth_diff)
    change_detected = change_value > change_threshold or prev_grasp_success
    print('Change detected: %r (value: %d)' % (change_detected, change_value))`

Sincerely

Can your camera capture real scene images? My camera D415 failed to capture images. I don’t know what’s wrong. I can see from the camera software that it works normally, but the program does not generate the corresponding image, and the program has been stuck in the while loop of the camera.py. Could you help me?


Floating misalignment

The floating element is initially misaligned under certain conditions:

A wrapper div with position: relative; display: flex; justify-content: flex-end;.
An intermediate div wrapping the reference and the floating elements.
The floating element without a defined width using the absolute strategy.
The floating element is positioned using transform: translate() instead of top and left.

Repro: https://codesandbox.io/s/floating-ui-dom-template-forked-btknl4?file=/src/index.js
Related: https://github.com/ariakit/ariakit/issues/1657

Add top: 0 and left: 0 in the initial CSS (or prior to the call). The layout of the element prior to being positioned needs to have the final dimensions ready.

Setting top and left to '0' initially minimizes layout interference with the dimensions of the element, so that its final dimensions are ready before being positioned.

More info: https://github.com/floating-ui/floating-ui/issues/1736

Thanks, @atomiks! I suggest updating the issue template with a CodeSandbox with those styles applied.


"Unrecognized car" Mazda CX-5 2024 PP

Describe the bug
I'm testing a newly purchased C3x on my 2024 CX-5 PP and encountered the "car unrecognized, dashcam mode only" exception.
Which car does this affect?
Mazda CX-5 2024 Premium Plus
Provide a route where the issue occurs
b830dd79ab37754c/2024-03-29--16-37-40
openpilot version
0.9.6
Additional info
dongle_id	      serial	    device_type	alias	sim_id	    prime	   prime_type	    last_ping
b830dd79ab37754c	ddfe2c1f	threex	None<PHONE_NUMBER>3020025713	False	0	2024-03-29 17:08:00	uploads accepted`

Your fingerprints were added in https://github.com/commaai/openpilot/pull/30882


API URLs in published docs don't match source

It looks like something went wrong with the URLs in the published tutorial at: https://enyojs.com/docs/latest/developer-guide/getting-started/moonstone-app-tutorial.html
Several URLs that should read api.flickr.com are shown as api.com
However the github source still shows the correct flickr URLs:
https://github.com/enyojs/enyo-docs/blob/master/developer-guide/getting-started/moonstone-app-tutorial.md
See:
http://forums.enyojs.com/discussion/2637/error-on-tutorial-building-a-moonstone-app

The 2.6+ docs are build from this branch:
https://github.com/enyojs/enyo-docs/blob/2.6.0-dev/developer-guide/getting-started/moonstone-app-tutorial.md
The error exists on those pages.  Pull requests welcomed!

I just pushed an update to the docs thanks to your PR!  Should be good now.


Add new currencies

Add new currencies from the API's.

Added 6 new currencies in pull request #4

PS: Could you put a CONTRIBUTE file or make a contribution guide, it's better for contributors :)

Added all currencies available on the API in pull request #5

@Norech I am creating new issue :)


Cycling dependancy in Hiera-based config

ruby 1.9.3p194
puppet 3.7.3

Yaml-based hiera setup, applied in order (merge deeper @ hiera):
Main config shared everywhere (init style = false because we have a local .deb repo where init is already taken care of when installing consul):
consul::config_dir: '/etc/consul.d'
consul::install_method: 'package'
consul::init_style: false
consul::ui_package_name: 'consul-web-ui'
consul::package_name: 'consul'
consul::config_hash:
  datacenter: 'datacentername'
  data_dir: '/var/lib/consul'
  domain: 'dcs.consul'
  retry_join:
    - '<IP_ADDRESS>'
    - '<IP_ADDRESS>'
    - '<IP_ADDRESS>'

Consul-master config:
consul::config_hash:
  log_level: 'INFO'
  server: true
  bootstrap_expect: 3
  ui_dir: '/usr/share/consul/web-ui'
  client_addr: '<IP_ADDRESS>'

consul::services:
  'zookeeper':
    tags: [ 'mesos' , 'master' ]
    port: 2181

Apply results in:
Error: Could not apply complete catalog: Found 1 dependency cycle:
(File[/etc/consul.d/service_zookeeper.json] => Class[Consul::Run_service] => Service[consul] => Class[Consul::Run_service] => Class[Consul] => Consul::Service[zookeeper] => File[/etc/consul.d/service_zookeeper.json])

Unless I'm doing something wrong in Hiera of course...

Hm, merging config like that appears (which is very handy for a multiple datacenter setup etc.) was also only working for me after a local edit....
-  $config_hash_real = merge($config_defaults, $config_hash)
+  $config_hash_real = merge($config_defaults, hiera_hash('consul::config_hash'),$config_hash)

... which apparently had something to do with https://github.com/solarkennedy/puppet-consul/commit/76bc1effe92daa55d2ab9350c0b64d145067a857 ... but beside that little tidbit change, I would be running v0.4.6 now.

This surprises me because we have a test for this:
https://github.com/solarkennedy/puppet-consul/blob/master/spec/classes/init_spec.rb#L247
If there was a dependency loop when settings consul::services then that test would fail to compile?

Im hitting this as well -
 DEBUG [9817a86d]
 DEBUG [9817a86d] 	(File[/etc/consul/service_haproxy.json] => Class[Consul::Run_service] => Service[consul] => Class[Consul::Run_service] => Class[Consul] => Consul::Service[haproxy] => File[/etc/consul/service_haproxy.json])
 DEBUG [9817a86d] ```

It could be it's about an incomplete consul definition which causes it. Once I hiera_merge it like mentioned, the problem disappears, but without merging (which granted, would result in an incomplete / faulty consul config), this dependency cycle happens, so with just:
consul::config_hash:
  log_level: 'INFO'
  server: true
  bootstrap_expect: 3
  ui_dir: '/usr/share/consul/web-ui'
  client_addr: '<IP_ADDRESS>'

consul::services:
  'zookeeper':
    tags: [ 'mesos' , 'master' ]
    port: 2181

Arguable, this is incomplete, but probably it gives more clear error messages when:

either defaults for the missing data which causes the loop are provided
or missing data which causes the loop is checked and the code is aborted there & then

Changing the merge() function as you describe above makes no difference for me, I am still receiving the same error. Having a look into it now...


feat: docker demo

Hello,
I took some time to create a demo of retronas in docker.
This is more or less a proof of concept, many things may require fixes and/or tuning to be considered stable.
Docker
Using docker with this project can be a little bit tricky and may not work with every usecase.
It may be a good idea to create one docker image per utility, for example one for samba, one for netatalk, one for ftp...
Containers
Base image
The base image is a simple container running ansible and waiting infinitely.

NOTE:  Ansible part of the project may require modifications to ensure the same behaviour between docker and baremetal installation

File browser
The included example is using filebrowser to manage files in the docker environment, the default user/password is admin/admin. It may be possible to change the user/pass with a configuration file.
Samba
Simple Samba sharing with a random but working docker image found on the internet.
The configuration will require tuning but "works on my machine".
People using actual nas don't require an additional samba container, I only included this for the demo.
TODO and ideas
Ansible playbook vs roles
for the moment, the ansible tasks are in the playbook, while this is not an issue, it may be better to create roles and apply roles to the localhost, we can also use molecule to test each role before sending to "production" (i can help for this part)
Docker image publishing
Github provides a hosting of docker image, the build can be automated using github actions.

Converted to draft since this is a demo

I have added an example with a piforce implementation that tests on device image building from an ansible generated Dockerfile,
https://github.com/danmons/retronas/tree/docker-example
A couple of notes on the example:

PiForce was chosen because it currently can't be integrated into RetroNAS due to python2.x requirements
On device image building on an RPI4 is unacceptable at ~15m for the initial build process
The size of piforce increases from ~300k to 900mb using the python2 official image (silly, probably unofficial alternatives)
No docker-compose is required at the moment
Integrated as a systemd service
Generic (basic) Dockerfile jinja template populated by ansible

Hello,
You seems very commited to this project, and I don't want to hurt your feelings, but I think your approach is far too complicated.
We do not want the user to build his own docker image, we (or the CI) build the image, then send it to the registry.
The end user only has to download the registry image to use it.
Also, if the demo uses ansible, it's mainly because the work was already done and also because I was a bit lazy, but in the future, ansible should not be used in docker images, because it's a bad practice. (the official ansible documentation mention usage with docker, which is great for the demo, but this is mainly a sponsored/political move from some investors/marketers). It's unrealistic to run ansible on each container restart.
Regarding the size increment of the docker image, this is because of your layers, docker images are build by adding the data from the current layer into the previous. In your dockerfile, you leave the temporary files of the installation at the end of your layer, so these files add to the total size of the image, so you have to delete the temporary files before finishing the layer.
Here is an example using apt:
RUN apt-get update && apt-get install -y ansible && rm -rf /var/lib/apt/lists/*
Since i remove the files during the layer (at the end of the RUN command), the files were not added to the layer, saving disk space.
If you want, I can take some time to show you how to build a docker image for piforce.

Thanks, appreciate the input,
This approach was expected to demonstrate two key items (although some additional items came from it as per above.)

a method of integration with the existing project (no re-writes, taking the path of least resistance)
external registry was going to be a very real dependency

It is only one of many approaches we could take i.e. it is not intended to green field the existing project nor be a final solution. I am not particularly interested in ansible's politics, this is my own solution to demonstrate integration with our existing methods.
I do entirely agree there are a number of steps that could have been taken to clean up the final image in this example and reduce the space requirements although even applying good practice will not make a significant impact in regards to the comparison against the initial size of the core application. The whole docker solution in and of itself is a trade of between space vs convenience.
We have discussed if we would need/want to manage a registry (account) as per accepted ci practice or if we could have an on device build integration. This demo was expected to prove that the dependency on an external registry was going to be a very real requirement (and has achieved that based on rpi4 build times). The demo is published to the repo for transparency, and for continuity is linked here to spur conversation, just as this pull request remains open.
You are welcome to revisit the demo and refine it, ignoring as you like for now the ci/registry publishing as I understand how that will impact user experience vs on device build

hrrrm, I'd like to commit this into the docker-example branch but I can't see a way to do that from this end, I mean I could muck around locally with it and commit it myself but I think your work deserves to be recognised here.
Is this something you can look at, i.e. resubmit against the docker-example branch? I would like to have all docker proposals in that branch so we can play with it.
Please note before its committed into the docker-example branch I'd like the ansible to be updated to the current MiSTer spec using retronas_systems.yml

This has sat around long enough, thanks for the example but it wont be merged with main, if you want to resubmit againt the docker-example branch while we have i'd be happy to merger it there


Update RoleManager and UserManager to use Protected Internal rather than Private

Problem
When extending RoleManager or UserManager, we are unable to call the following methods in a derived class:
RoleManager

ValidateRoleInternal
UpdateRoleAsync

UserManager

ValidateUserInternal
UpdateUserAsync
UpdateSecurityStampInternal

These are useful and have repeated in the base class to continue the same pattern of functionality.
Solution
Change these methods to use protected internal rather than private so they will be accessible in a derived class.

@ajcvickers seems safe to move this to 2.1, no breaking changes here


Remove bare except clauses (E722)

A recent release of flake8 adds a rule check for this, which broke CI.
For safety, I've sticked to Exception when there is at least a nested function call in the try block.

run all integration tests

@bamarni I am blocked by this. If everything is good to go, please merge this :)

I'll close this as you included it in your PR


Support for "properties" language for ".conf" file extensions

Looks like VS Code has support for ".cfg", ".conf" files as part of the ini language module:
https://github.com/microsoft/vscode/blob/a8c3c47555ec693a4ab9dee76a20c18e054bf50f/extensions/ini/package.json#L20
Which seems to be missing from monaco.

Is there any update on this?

Unfortunately, we don't have the resources to address this right now, but we're more than happy to accept a PR for this!
Closing due to inactivity.


Revert "Merge pull request #319 from nhsuk/frontend/logo-button"

This reverts commit 4d9620b6ddd9a00841923db93e60430e1e9779d1, reversing
changes made to 377b2cc68b6c5da1f4e6d4f6997291665afe28ec.

:rocket: deployment of connecting-to-services succeeded (http://connecting-to-services-pr-323.dev.beta.nhschoices.net)


psql client pod does not include database admin name environment variable.

Added to github.com/IBM version.


Burn Book: Data manipulation guide

Introduce every dataset transform and their uses
Introduce the batcher

Addressed in PR #1183 . Closing


debian: Fix incorrect use of link-time optimizer.

Current version of debian/rules simply uses the default lto GCC optimization settings during the linkage process.
The main problem with this approach is that GCC on OS like Debian Jammy, for example, can enable the -flto=auto option during the openvswitch building and linking process. In this case, the linked dynamic libraries would need to be builded based on the same lto optimization options, at the risk of not working, according to documentation [1].
I'm not sure of the real benefits of using this link-time optimization option, and since when it is enabled it causes problems with shared libs link libjemalloc, for example, it seems safer overwritten compiler decision by passing -fno-lto command.
[1] https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-flto
Reported-at: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2015748

Hi,
Thanks for your contribution.
I am closing this PR as it appears to have gone stale.
If you believe this change is still relevant then please do feel welcome to resubmit it using the preferred mechanism of the Open vSwitch project, the email workflow described in Submitting Patches.


docs(readme): changed completion engine plugin example

https://github.com/nvim-lua/completion-nvim has become deprecated. changed it to https://github.com/hrsh7th/nvim-cmp.

@budswa Thanks for the contribution 🥇


bootstrap-slider

I used this in a project and liked it. You may consider adding it.
Demo: http://www.eyecon.ro/bootstrap-slider/
Github: https://github.com/brownieboy/react-bootstrap-slider

it have too much decencies which we don't want to use.
https://github.com/brownieboy/react-bootstrap-slider/blob/master/package.json#L36


Alert Details unavailyble / not an entity there / since 5.7.0

Checklist

[x] I have updated to the latest available of the Indego component version.
[x] I have updated to the latest available Home Assistant version.
[x] I have read the README https://github.com/jm-73/Indego/blob/master/README.md) and especially read the part about the KNOWN ISSUES (https://github.com/jm-73/Indego/blob/master/README.md#known-issues).
[x] I have checked for other open or recently closed issues for similar bugs/issues.

The problem
The Alert Details are no longer available. There used to be entities for it, but there are no longer. Only an 'there is an alert' entity is available, a binary sensor. I have also set the third checkmark in the configuration to have the alerts stored, however, there are no alert details or entities besides the binary sensor.
Expected behavior
Seeing alert details / corresponding entities, at least after setting the third checkmark in the integration config.
Steps to reproduce
For me: Delete Indego integration, reinstall, set up with the chrome auth helper plugin. Set it as mower and also check the alerts checkmark.
Environment

Indego component version: 5.7.0, current.

HomeAssistant version: 2024.6.3

Indego component release with the issue: 5.7.0

Last working Indego component release (if known): 5.6.3

Home Assistant release with the issue: N/A

Last working Home Assistant release (if known): N/A

Operating system: N/A

Logs
switched on debug logging on integration page, reloaded integration, switched off debug logging.  I have switched that on but still can not see the alert details.
Hope, I got that right. Thank you so much for your great work!!!

The Alert entities were deleted but they were added as attributes to the alert entity (the binary sensor). Are there also no attributes ?

Unfortunately not, in my case at least. The entity "binary_sensor.indego_serial_alert" only has the number of alerts as attributes:
device_class: problem
friendly_name: Radio alert
alerts_count: 0

Ok but do you have an active alert in your bosch app ? Because in the actual setting an alert is only added to the attributes when the alert count is > 0. When it is 0 then it looks like you have posted (only friendly name, device class and alert_count)

No, I did not, as you said ;) Thanks for pointing this out, I was not aware of that. And yes, when there is an active alert, the attributes are there.
=> User error, works as designed. Sorry and thank a lot!

No problem, you're welcome 😉