DF Chat Archive - Unable to access Archive.

Module
DF Chat Enhancements 4.1.0 - Archive feature
**Describe the Issue **
Hi! This module is really useful, but the chat archive feature doesn't seem to work for me.
What steps did you take before experiencing the problem?
Steps to reproduce the behavior:

Click on "Archive Chat log" in the chat window
Create a chatlog (any amount of chat selected)
Go to "Manage Chat Archives" in settings
Click any archive in there, including the one just created.

What did you expect to happen?
A chatlog to appear that I could access through Foundry.
What happened instead?
I recieved an "Unexpected character" error and several other errors, all reproduced below.
Screenshots
The Error I got when attempting to open the chatlog originally.
The current error.
Error with all modules except DF chat disabled.
Unsure if this is related but dumping it anyway.
Foundry Versions

Version of this module: 4.1.0
Foundry Version: V10 Build 287
System Name and Version: Oracle Cloud host, accessed via windows 10.
Browser Name and Version: Firefox and Chrome both tested.

What other modules did you have active when experiencing this issue (include both names and versions)?
Full list of active modules as of most recent test.
Without all modules I get a slightly different error.
Additional context
I've tested this on a fresh foundry install and it seems to function, so I'm not quite sure what's causing the incompatability or if it's something in my old chat archives.
Full list of active modules as of most recent test.
I used ViNo in V9 but have since disabled and uninstalled it.
I've tested by posting several messages in the recent chat and ONLY archiving those, and it seems to display fine. I can provide the JSON archives creating the errors but would rather not upload publicly, as they contain NSFW content and I don't quite know what github's policy is.

I am experiencing this on a new install with foundry v10, although my error messages are different.

The archive in question is a single chat message, although I do have a lot of other modules enabled.

Followup comment, mostly to @Lukasrygh23 - if you make a chat archive with no spaces in the name, you can rename it in foundry to something with spaces, using the chat archive rename feature even, and the file on disk will still have no spaces and load fine.

I can create new logs without spaces and they work fine, but I couldn't salvage the old ones even by renaming them to space-less names. Thanks, Darloth!

This seems to be the main issue, given that the first JSON error only appears once.

As a note, you can do the following in the console.
game.settings.get("df-chat-enhance", "logs") gets you all of the archives data in the module.
You can then modify this array of archive objects, and use await game.settings.set("df-chat-enhance", "logs") to apply it.
Done properly, it can fix your archives. Will investigate further.

Please note I am not responsible if this breaks your archives.
A step by step solution to making your archives work:

Go to your archives folder and create a copy of your archives. Rename the copies to just the number at the front.
Copy paste this into the console.

let originalSettings = game.settings.get("df-chat-enhance", "logs")
console.log("These are the original settings", originalSettings)
originalSettings.map(x => { x.filepath = `${game.settings.get("df-chat-enhance", "archiveFolder")}/${x.id}.json`})
console.log("Modifying the settings to...", originalSettings)
await game.settings.set("df-chat-enhance", "logs", originalSettings)

Open your archives!

This issue is still occurring... Also happens with newly created archives.
At the very least, the ability to name a new archive using spaces should be disabled or prevented in some way so that new archives can't be created like this.

The modules are unmaintained for a while now, and the fix is already made. It's just a matter of updating the module unfortunately.

Please note I am not responsible if this breaks your archives. A step by step solution to making your archives work:
1. Copy paste this into the console.

let originalSettings = game.settings.get("df-chat-enhance", "logs")
console.log("These are the original settings", originalSettings)
originalSettings.map(x => { x.filepath = x.filepath.replaceAll("%20", "%2520").replaceAll("%25%25", "%25"); return x})
console.log("Modifying the settings to...", originalSettings)
await game.settings.set("df-chat-enhance", "logs", originalSettings)

2. Open your archives!

NOTE THAT THIS APPLIES TO ALL ARCHIVES, WORKING OR NOT. WHILE IT SHOULD NOT BREAK ANY ALREADY-WORKING ARCHIVES, IF YOU WANT TO ONLY FIX A SPECIFIC ARCHIVE, YOU NEED TO MODIFY ONLY THAT ARCHIVES originalSettings
You can also use this method to change other attributes, such as names or visibility options, just edit originalSettings and to apply the changes, await game.settings.set("df-chat-enhance", "logs", originalSettings)

Unfortunately none of these seemed to work in Foundry VTT v11.307 which is unfortunate because this looks like a great module.

Please note I am not responsible if this breaks your archives. A step by step solution to making your archives work:

Copy paste this into the console.

let originalSettings = game.settings.get("df-chat-enhance", "logs")
console.log("These are the original settings", originalSettings)
originalSettings.map(x => { x.filepath = x.filepath.replaceAll("%20", "%2520").replaceAll("%25%25", "%25"); return x})
console.log("Modifying the settings to...", originalSettings)
await game.settings.set("df-chat-enhance", "logs", originalSettings)

Open your archives!

NOTE THAT THIS APPLIES TO ALL ARCHIVES, WORKING OR NOT. WHILE IT SHOULD NOT BREAK ANY ALREADY-WORKING ARCHIVES, IF YOU WANT TO ONLY FIX A SPECIFIC ARCHIVE, YOU NEED TO MODIFY ONLY THAT ARCHIVES originalSettings
You can also use this method to change other attributes, such as names or visibility options, just edit originalSettings and to apply the changes, await game.settings.set("df-chat-enhance", "logs", originalSettings)

Thanks so much for this! I had a mild panic attack last night when I did a fresh archive/delete and didn't know not to use spaces. I can now get into the archive 😅❤

@MrVauxs sorry to disturb but you're probably the only one able to answer this. I have some old chat archives that are in the archive folder but aren't showing up in the UI. Is there a way I can 'relink' them so they show up in the UI? This is an old world that's been through some migrations, not sure at what point they disappeared.
Thanks again for the above btw.

Yes. You'd have to update the settings to include a new entry linking to the filepath of the archive, or modify an existing one to instead link to that file.

Thanks! Makes sense. The JS to do so is beyond me... but I might try making new archives with the same name and then doing a ninja swap of the archive file.


MB-13179-create-update-movingExpense-handler

Jira ticket for this change
Summary
This PR enables users to create and update a moving expense
Files that were added or updated:

internal.yaml
MovingExpense.yaml
handlers/internalapi/moving_expense.go
handlers/internalapi/moving_expense_test.go
handlers/internalapi/internalapi/payload_to_model
handlers/internalapi/internalapi/model_to_payload

Setup to Run Your Code

### To Run Tests:
##### Terminal 1
Run Create tests
go test ./pkg/handlers/internalapi --testify.m TestCreateMovingExpenseHandler  -v

Terminal 2
Run Update Tests:
go test ./pkg/handlers/internalapi --testify.m TestUpdateMovingExpenseHandler  -v

Messages

:book:
:link: MB-13179

  Generated by :no_entry_sign: dangerJS against a2d758e42d1e303616e733f181893ba87f5d5063

@NamibiaTorres I think something went wrong with the latest commit. I'm seeing 1233 files changed, and it looks like a bunch of gen files were deleted:

@NamibiaTorres I think something went wrong with the latest commit. I'm seeing 1233 files changed, and it looks like a bunch of gen files were deleted:

Fixed!

I updated with PR with suggestions from Duncan, after it was approved. The tests pass and it looks like nothing is breaking after implementing changes.


Dataset format

May in know the format for dataset?

https://www.cityscapes-dataset.com/file-handling/?packageID=3

In fact, I did not understand exactly what you were asking. I will write some more information.
We were able to parse the dataset into numpy to create the .h5 file, and in .h5, we could get the data at about 10 times faster than opencv imread.
When creating the data (256, 512, 3), the image was resized and limited to three classes.

If you want to train your own dataset,,,,, Sorry but its not supported. We`ll make methods later(maybe after several months - maybe after we make various sota models)

I recommend to use original cityscape dataset structure thuogh we use hdf5 format.
cityscpae dataset sturcture
The folder structure of the Cityscapes dataset is as follows:
{root}/{type}{video}/{split}/{city}/{city}_{seq:0>6}_{frame:0>6}_{type}{ext}

The meaning of the individual elements is:

root  the root folder of the Cityscapes dataset. Many of our scripts check if an environment variable CITYSCAPES_DATASET pointing to this folder exists and use this as the default choice.
type  the type/modality of data, e.g. gtFine for fine ground truth, or leftImg8bit for left 8-bit images.
split the split, i.e. train/val/test/train_extra/demoVideo. Note that not all kinds of data exist for all splits. Thus, do not be surprised to occasionally find empty folders.
city  the city in which this part of the dataset was recorded.
seq   the sequence number using 6 digits.
frame the frame number using 6 digits. Note that in some cities very few, albeit very long sequences were recorded, while in some cities many short sequences were recorded, of which only the 19th frame is annotated.
ext   the extension of the file and optionally a suffix, e.g. _polygons.json for ground truth files

Possible values of type

gtFine       the fine annotations, 2975 training, 500 validation, and 1525 testing. This type of annotations is used for validation, testing, and optionally for training. Annotations are encoded using json files containing the individual polygons. Additionally, we provide png images, where pixel values encode labels. Please refer to helpers/labels.py and the scripts in preparation for details.
gtCoarse     the coarse annotations, available for all training and validation images and for another set of 19998 training images (train_extra). These annotations can be used for training, either together with gtFine or alone in a weakly supervised setup.
leftImg8bit  the left images in 8-bit LDR format. These are the standard annotated images.
leftImg16bit the left images in 16-bit HDR format. These images offer 16 bits per pixel of color depth and contain more information, especially in very dark or bright parts of the scene. Warning: The images are stored as 16-bit pngs, which is non-standard and not supported by all libraries.
rightImg8bit  the right stereo views in 8-bit LDR format.
rightImg16bit the right stereo views in 16-bit HDR format.
timestamp     the time of recording in ns. The first frame of each sequence always has a timestamp of 0.
disparity     precomputed disparity depth maps. To obtain the disparity values, compute for each pixel p with p > 0: d = ( float(p) - 1. ) / 256., while a value p = 0 is an invalid measurement. Warning: the images are stored as 16-bit pngs, which is non-standard and not supported by all libraries.
camera        internal and external camera calibration. For details, please refer to csCalibration.pdf
vehicle       vehicle odometry, GPS coordinates, and outside temperature. For details, please refer to csCalibration.pdf


update connectionStateListenerMetrics

In PR https://github.com/Azure/azure-sdk-for-java/pull/27242, I added the connectionStateListener metrics  This PR is to make a slight change when there is no connectionStateListener related events triggered.
before:
"serviceEndpointStatistics": {
"availableChannels": 1,
"acquiredChannels": 0,
"executorTaskQueueSize": 0,
"inflightRequests": 1,
"lastSuccessfulRequestTime": "2022-02-20T20:30:13.507Z",
"lastRequestTime": "2022-02-20T20:30:13.481Z",
"createdTime": "2022-02-20T20:30:11.920759Z",
"isClosed": false,
"**cerMetrics**": {
"lastCallTimestamp": "N/A"
}
}

After:
"serviceEndpointStatistics": {
"availableChannels": 1,
"acquiredChannels": 0,
"executorTaskQueueSize": 0,
"inflightRequests": 1,
"lastSuccessfulRequestTime": "2022-02-20T20:30:13.507Z",
"lastRequestTime": "2022-02-20T20:30:13.481Z",
"createdTime": "2022-02-20T20:30:11.920759Z",
"isClosed": false,
"**cerMetrics**": {}
}

API change check for com.azure:azure-cosmos
API changes are not detected in this pull request for com.azure:azure-cosmos

/azp run java - cosmos - tests


List of topics for articles

[ ] Application Case Study: Spee.ch
[ ] What are Claims, how they work
[ ] URLs, Name Resolution
[ ] DHT?
[ ] How to run wallet server/reflector/search server/chainquery
[ ] Design / branding
[ ] using lbrynet as a library in your code
[ ] Validating signatures on claims

@tzarebczan let's get these split out into individuals tickets and assigned to the actual responsible team member.

These were broken out into separate issues.


On revert, old links could still be available

Assume this scenerio where the current files are
index.html
page2.html
page3.html
950e80e70eb0/index.html
950e80e70eb0/page2.html
950e80e70eb0/page3.html
c7ff515816e5/index.html
c7ff515816e5/page2.html

if we were to revert to c7ff515816e5 from 950e80e70eb0, page3.html would remain visible on the website. This is happening because in the source the contents of the version is being copied to the root with replace but not checking for already existing files.

One way to fix this could be finding out the latest deploy, removing the files that don't exist anymore in the new version after deploying the new version.
[After deploy, list all html files, remove files that was not part of that deploy]


QuantifiedCode will be shutting down

QuantifiedCode will be shutting down on October 1st.
Properly remove it from the workflow. (Disabling integrations and so on.)

The service will run at least till end of year. So this is fixed for now.


favicon: Remove event listeners from old container on change

previously the event listeners were removed off the new container which has no effect

Coverage decreased (-0.07%) to 71.641% when pulling a5faf11327a2590d198af2cd9866dcae08435a4f on tjenkinson-patch-2 into 3140ce09b5279f180d688c25447ef9220f74d9aa on master.

Great job, thanks @tjenkinson!


Fixing Cache References

Changed cache dict definition in Simulation Sequence https://github.com/NREL/PowerSimulations.jl/blob/b8e2e70843c79f8e8bb30f2adf394740dbe0c7b9/src/core/simulation_sequence.jl#L169
This will allow multiple stages to modify information in cache

The tuple keys are really ugly. I'm approving this, but this implementation reinforces that we need to provide nice user interfaces so that they don't have to interact with these.

Agreed, we need to come up with a better interface for the cache. For now, it is important to enabling #370


Window unmaximize not working

Works if u drag the window to a different position after the failed maximize attempt

Seems to work for me in https://github.com/Limit-Theory-Redux/ltheory/pull/290 - either I fixed it by accident or it was fixed a while ago.


TMP file location

Hi,
I was unable to find it in the code myself, this may not be an issue/possible.
I'm running this on a device that has a slow SD card but has /tmp in RAM.
It "looked" like the download test was happening on the SDcard. Is there a way to control this/change the tmp location?

This application does not perform any disk access.


No documentation for running neuralmonkey

If I run
./bin/neuralmonkey-run ./examples/translation.ini ./examples/data/val.en
I get the following error. Also, python becomes defunct, and I need to reboot -f to get back into my machine. What am I doing wrong? It looks like an .ini file is expected as input file
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcublas.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcudnn.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcufft.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcuda.so.1 locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcurand.so locally
2016-09-19 17:14:21: Loading INI file: './examples/translation.ini'
2016-09-19 17:14:21: INI file is parsed.
DEBUG (configBuild):Building value on depth 0: ['object:bleu1', 'object:bleu4']
DEBUG (configBuild):Building value on depth 1: object:bleu1
DEBUG (configBuild):Building value on depth 2: 1
DEBUG (configBuild):Instantiating class <class 'neuralmonkey.evaluators.bleu.BLEUEvaluator'> with arguments {'n': 1}
DEBUG (configBuild):Class <class 'neuralmonkey.evaluators.bleu.BLEUEvaluator'> initialized into object <neuralmonkey.evaluators.bleu.BLEUEvaluator object at 0x7f2086e1d3c8>
DEBUG (configBuild):Building value on depth 1: object:bleu4
DEBUG (configBuild):Building value on depth 2: 4
DEBUG (configBuild):Instantiating class <class 'neuralmonkey.evaluators.bleu.BLEUEvaluator'> with arguments {'n': 4}
DEBUG (configBuild):Class <class 'neuralmonkey.evaluators.bleu.BLEUEvaluator'> initialized into object <neuralmonkey.evaluators.bleu.BLEUEvaluator object at 0x7f20c70f6be0>
DEBUG (configBuild):Building value on depth 0: out-example-translation
DEBUG (configBuild):Building value on depth 0: object:bpe_postprocess
DEBUG (configBuild):Instantiating class <class 'neuralmonkey.processors.bpe.BPEPostprocessor'> with arguments {}
DEBUG (configBuild):Class <class 'neuralmonkey.processors.bpe.BPEPostprocessor'> initialized into object <neuralmonkey.processors.bpe.BPEPostprocessor object at 0x7f20c70eabe0>
DEBUG (configBuild):Building value on depth 0: 4
DEBUG (configBuild):Building value on depth 0: object:runner
DEBUG (configBuild):Building value on depth 1: object:decoder
DEBUG (configBuild):Building value on depth 2: 256
DEBUG (configBuild):Building value on depth 2: 0.8
DEBUG (configBuild):Building value on depth 2: 50
DEBUG (configBuild):Building value on depth 2: target
DEBUG (configBuild):Building value on depth 2: True
DEBUG (configBuild):Building value on depth 2: 300
DEBUG (configBuild):Building value on depth 2: object:target_vocabulary
DEBUG (configBuild):Building value on depth 3: 50000
DEBUG (configBuild):Building value on depth 3: ['object:train_data']
DEBUG (configBuild):Building value on depth 4: object:train_data
DEBUG (configBuild):Building value on depth 5: examples/data/train.en
DEBUG (configBuild):Building value on depth 5: object:bpe_preprocess
DEBUG (configBuild):Building value on depth 6: examples/data/bpe_merges
DEBUG (configBuild):Instantiating class <class 'neuralmonkey.processors.bpe.BPEPreprocessor'> with arguments {'merge_file': 'examples/data/bpe_merges'}
2016-09-19 17:14:21: Initializing BPE preprocessor
DEBUG (configBuild):Class <class 'neuralmonkey.processors.bpe.BPEPreprocessor'> initialized into object <neuralmonkey.processors.bpe.BPEPreprocessor object at 0x7f20b745c7b8>
DEBUG (configBuild):Building value on depth 5: examples/data/train.de
DEBUG (configBuild):Instantiating class <function load_dataset_from_files at 0x7f20b7426488> with arguments {'s_source': 'examples/data/train.en', 'preprocessor': <neuralmonkey.processors.bpe.BPEPreprocessor object at 0x7f20b745c7b8>, 's_target': 'examples/data/train.de'}
2016-09-19 17:14:21: Initializing dataset with: source, target
2016-09-19 17:14:21: Loading examples/data/train.en
2016-09-19 17:14:38: Loading examples/data/train.de
2016-09-19 17:15:13: Dataset length: 500000
DEBUG (configBuild):Class <function load_dataset_from_files at 0x7f20b7426488> initialized into object <neuralmonkey.dataset.Dataset object at 0x7f20792da898>
DEBUG (configBuild):Building value on depth 3: ['target']
DEBUG (configBuild):Building value on depth 4: target
DEBUG (configBuild):Building value on depth 3: tmp-decoder-vocabulary
DEBUG (configBuild):Building value on depth 3: decoder_vocabulary
DEBUG (configBuild):Instantiating class <function initialize_vocabulary at 0x7f20b7433d90> with arguments {'max_size': 50000, 'directory': 'tmp-decoder-vocabulary', 'name': 'decoder_vocabulary', 'datasets': [<neuralmonkey.dataset.Dataset object at 0x7f20792da898>], 'series_ids': ['target']}
2016-09-19 17:15:13: Warning! Use of deprecated initialize_vocabulary method. Did you think this through?
2016-09-19 17:15:13: Pickled vocabulary loaded. Size: 39041 words
2016-09-19 17:15:13: Sample of the vocabulary: ['loose', 'aufs@@', 'bewusstsein', 'corporate', 'Verstän@@']
DEBUG (configBuild):Class <function initialize_vocabulary at 0x7f20b7433d90> initialized into object <neuralmonkey.vocabulary.Vocabulary object at 0x7f20b745c748>
DEBUG (configBuild):Building value on depth 2: ['object:encoder']
DEBUG (configBuild):Building value on depth 3: object:encoder
DEBUG (configBuild):Building value on depth 4: 300
DEBUG (configBuild):Building value on depth 4: 50
DEBUG (configBuild):Building value on depth 4: 0.8
DEBUG (configBuild):Building value on depth 4: source
DEBUG (configBuild):Building value on depth 4: 300
DEBUG (configBuild):Building value on depth 4: <class 'neuralmonkey.decoding_function.Attention'>
DEBUG (configBuild):Building value on depth 4: object:source_vocabulary
DEBUG (configBuild):Building value on depth 5: 50000
DEBUG (configBuild):Building value on depth 5: ['object:train_data']
DEBUG (configBuild):Building value on depth 6: object:train_data
DEBUG (configBuild):Skipping already initialized value: object:train_data
DEBUG (configBuild):Building value on depth 5: ['source']
DEBUG (configBuild):Building value on depth 6: source
DEBUG (configBuild):Building value on depth 5: tmp-encoder-vocabulary
DEBUG (configBuild):Building value on depth 5: encoder_vocabulary
DEBUG (configBuild):Instantiating class <function initialize_vocabulary at 0x7f20b7433d90> with arguments {'max_size': 50000, 'directory': 'tmp-encoder-vocabulary', 'name': 'encoder_vocabulary', 'datasets': [<neuralmonkey.dataset.Dataset object at 0x7f20792da898>], 'series_ids': ['source']}
2016-09-19 17:15:13: Warning! Use of deprecated initialize_vocabulary method. Did you think this through?
2016-09-19 17:15:13: Pickled vocabulary loaded. Size: 23792 words
2016-09-19 17:15:13: Sample of the vocabulary: ['feu@@', 'C-@@', 'fu@@', 'gs', 'bes@@']
DEBUG (configBuild):Class <function initialize_vocabulary at 0x7f20b7433d90> initialized into object <neuralmonkey.vocabulary.Vocabulary object at 0x7f2078feedd8>
DEBUG (configBuild):Instantiating class <class 'neuralmonkey.encoders.sentence_encoder.SentenceEncoder'> with arguments {'rnn_size': 300, 'max_input_len': 50, 'dropout_keep_p': 0.8, 'data_id': 'source', 'embedding_size': 300, 'attention_type': <class 'neuralmonkey.decoding_function.Attention'>, 'vocabulary': <neuralmonkey.vocabulary.Vocabulary object at 0x7f2078feedd8>}
2016-09-19 17:15:13: Initializing sentence encoder, name: "sentence_encoder"
2016-09-19 17:15:18: Sentence encoder initialized
DEBUG (configBuild):Class <class 'neuralmonkey.encoders.sentence_encoder.SentenceEncoder'> initialized into object <neuralmonkey.encoders.sentence_encoder.SentenceEncoder object at 0x7f2078feeda0>
DEBUG (configBuild):Instantiating class <class 'neuralmonkey.decoders.decoder.Decoder'> with arguments {'rnn_size': 256, 'dropout_keep_p': 0.8, 'max_output_len': 50, 'data_id': 'target', 'use_attention': True, 'embedding_size': 300, 'vocabulary': <neuralmonkey.vocabulary.Vocabulary object at 0x7f20b745c748>, 'encoders': [<neuralmonkey.encoders.sentence_encoder.SentenceEncoder object at 0x7f2078feeda0>]}
2016-09-19 17:15:18: Initializing decoder, name: 'decoder'
2016-09-19 17:15:20: Decoder initialized.
DEBUG (configBuild):Class <class 'neuralmonkey.decoders.decoder.Decoder'> initialized into object <neuralmonkey.decoders.decoder.Decoder object at 0x7f20b745c7f0>
DEBUG (configBuild):Building value on depth 1: 256
DEBUG (configBuild):Instantiating class <class 'neuralmonkey.runners.runner.GreedyRunner'> with arguments {'decoder': <neuralmonkey.decoders.decoder.Decoder object at 0x7f20b745c7f0>, 'batch_size': 256}
DEBUG (configBuild):Class <class 'neuralmonkey.runners.runner.GreedyRunner'> initialized into object <neuralmonkey.runners.runner.GreedyRunner object at 0x7f20c517f630>
DEBUG (configBuild):Building value on depth 0: object:decoder
DEBUG (configBuild):Skipping already initialized value: object:decoder
DEBUG (configBuild):Building value on depth 0: ['object:encoder']
DEBUG (configBuild):Building value on depth 1: object:encoder
DEBUG (configBuild):Skipping already initialized value: object:encoder
2016-09-19 17:15:20: INI file loaded.

2016-09-19 17:15:20: Initializing the TensorFlow session.
I tensorflow/core/common_runtime/gpu/gpu_init.cc:102] Found device 0 with properties:
name: GeForce GTX TITAN X
major: 5 minor: 2 memoryClockRate (GHz) 1.076
pciBusID 0000:0b:00.0
Total memory: 12.00GiB
Free memory: 11.87GiB
W tensorflow/stream_executor/cuda/cuda_driver.cc:572] creating context when one is currently active; existing: 0x168659f0
I tensorflow/core/common_runtime/gpu/gpu_init.cc:102] Found device 1 with properties:
name: GeForce GTX TITAN X
major: 5 minor: 2 memoryClockRate (GHz) 1.076
pciBusID 0000:06:00.0
Total memory: 12.00GiB
Free memory: 11.87GiB
I tensorflow/core/common_runtime/gpu/gpu_init.cc:126] DMA: 0 1
I tensorflow/core/common_runtime/gpu/gpu_init.cc:136] 0:   Y Y
I tensorflow/core/common_runtime/gpu/gpu_init.cc:136] 1:   Y Y
I tensorflow/core/common_runtime/gpu/gpu_device.cc:838] Creating TensorFlow device (/gpu:0) -> (device: 0, name: GeForce GTX TITAN X, pci bus id: 0000:0b:00.0)
I tensorflow/core/common_runtime/gpu/gpu_device.cc:838] Creating TensorFlow device (/gpu:1) -> (device: 1, name: GeForce GTX TITAN X, pci bus id: 0000:06:00.0)
2016-09-19 17:15:26: Loading variables from out-example-translation/variables.data.best
2016-09-19 17:15:27: Session initialization done.

2016-09-19 17:15:27: Loading INI file: './examples/data/val.en'
2016-09-19 17:15:27: Failed to load INI file: File contains no section headers.
file: '', line: 1
'in the resolution , we recommend frontloading subject to cautious conditions . 1'
Traceback (most recent call last):
  File "/home/joachim/repositories/neuralmonkey/bin/neuralmonkey/config/configuration.py", line 44, in load_file
    config_dict = load_config_file(config_f, self.ignored)
  File "/home/joachim/repositories/neuralmonkey/bin/neuralmonkey/config/config_loader.py", line 122, in load_config_file
    config_dicts = parsing.parse_file(config_file)
  File "/home/joachim/repositories/neuralmonkey/bin/neuralmonkey/config/parsing.py", line 173, in parse_file
    config = parse_config(config_file)
  File "/home/joachim/repositories/neuralmonkey/bin/neuralmonkey/config/parsing.py", line 157, in parse_config
    config.read_file(line_numbers, source=filename)
  File "/home/joachim/anaconda2/envs/tensorflow_python_3_5/lib/python3.5/configparser.py", line 715, in read_file
    self._read(f, source)
  File "/home/joachim/anaconda2/envs/tensorflow_python_3_5/lib/python3.5/configparser.py", line 1077, in _read
    raise MissingSectionHeaderError(fpname, lineno, line)
configparser.MissingSectionHeaderError: File contains no section headers.
file: '', line: 1
'in the resolution , we recommend frontloading subject to cautious conditions . 1'

the correct way to run neuralmonkey is to supply two .ini files. The first file is the file with the model description and the second one is the file with dataset description. I will add the proper documentation tomorrow. Meanwhile, you can look inside the run.py script to figure out what is needed in the second ini file.

This is how the second ini should look like:
[main]
test_datasets=[<news>]

[bpe_preprocess]
class=processors.bpe.BPEPreprocessor
merge_file=/home/user/experiments/merges.bpe

[news]
class=config.utils.dataset_from_files
s_source=/home/user/data/newstest/news.de
s_target_out=/home/user/experiments/news/news.out.en
preprocess=<bpe_preprocess>

Note that you can specify more datasets at once. Also note that for each dataset, you must provide the source data series and the target_out data series. These names should match the encoder and decoder data series names provided in the model configuration file.

Thanks, it seems to work now.  The crashes I experienced seem to stem from ubuntu 14, as described in https://github.com/tensorflow/tensorflow/issues/1203.

I am preparing a tutorial here: http://neural-monkey.readthedocs.io/en/latest/tutorial.html if you want to check it out..

The tutorial now contains the description of how to prepare the test dataset file and how to run it.


Remove block producer's Store trait

The Store trait abstracts over the gRPC server, the main utility of this trait is to implement tests. However, this is not necessary, since tonic already has a strategy to mock the servers for testing, here is an example:
https://github.com/hyperium/tonic/blob/master/examples/src/mock/mock.rs

Would we basically just replace Store trait with the current DefaultStore struct? (i.e., Store trait goes away and DefaultStore struct becomes Store struct).
If we can do this while still mocking store for test purposes, I'm in favor or that (upon a quick look at the example, I didn't quite understand how it would work, but I also didn't look too long).

Implementation wise it would something like this:

Store trait is removed

This issue is not about ApplyBlock, that would stay there as far as this issue is concerned

The existing impl Store for DefaultStore would become just an impl DefaultStore, as this code is doing some extra object translation.
The MockStoreSuccess and MockStoreFailure would be rewritten, and implemented in terms of trait for the gRPC store interface

The linked example shows how this can be used. Basically the test spawns a task to run the test server, and uses a stream instead of a socket to do the communication.

And if you want, the DefaultStore struct can be renamed to Store

Makes sense. Yes, I think this works. @plafer what do you think?

The one downside is that it makes it harder to move away from gRPC in the future. But if that's not much of a concern, then yes this approach is simpler and thus better.

I'm just remembering previous conversations we had about how when all components are running in the same process (including the database and rpc), we shouldn't need to use gRPC. This change would force us to keep using gRPC in that situation.

The one downside is that it makes it harder to move away from gRPC in the future. But if that's not much of a concern, then yes this approach is simpler and thus better.

This is a far point. But I think changes like this happen once or twice in a project's lifetime. So personally I would optimize for easy of readability here.

I'm just remembering previous conversations we had about how when all components are running in the same process (including the database and rpc), we shouldn't need to use gRPC. This change would force us to keep using gRPC in that situation.

This is true, we probably don't need the socket api, but we would need to do something similar to what is done in the tests, and communicate over a channel.

Closed in #571


Adds WORKFLOW.md file

I'm basing this document heavily off of the document that Kurt has been writing up in our service repositories. The biggest differences are that I've added references (where appropriate) to ReadTheDocs, removed the release script, made references to when and where to create PRs during the release process, and filled in the Deploying to production section with a reference to a currently non-existent Github Action.
The end goal is to have a workflow here that is very similar to our service repos. This process is what I had in mind when making my comments on PR-251 in Flows. I'm hoping we can compare and make updates to both PRs so that we're happy with the workflow.

@urimandujano I'm waiting to review this until after I've merged the work elsewhere on this doc. In particular, I'm working on making a GitHub action that can perform checks when attempting to merge to production.

Shall we get the globusonline/flows#251 settled first and then take another pass on this one? Or, is the stuff pulled from there good enough and we should review separately at this point?

@jimPruyne If we get the Flows PR settled then I'd like for us to hop back over here and make sure the process in this doc is consistent with what we have there. And if not then at least understanding that it'll be inconsistent (:

@jimPruyne @kurtmckee @rudyardrichter I just came back here to update based on edits that were made into WORKFLOW.md in the Flows repo. A few of us have gone through this process already so please let me know if you read something and it looks unfamiliar. I'd like to get this doc settled and copied into action-provider-tools by the end of this sprint.


Support sessionid as a build property

as an ISV, I would like to be able to pass a sessionid directly as a build property, instead of a username/password pair.
this allows me to not require username/passwords for developers who are primarily working via an environment hub and single sign on.
the signuprequest api also allows calling it with a connected app key, and it will return an active auth code when the org is provisioned. By supporting sessionid in build props, it would be easier to automate the signuprequest -> full org process

closed in #168


Jsdoc tips don't work with react Functional Component with TypeScript

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.82.0
OS Version: Windows 11 Home 10.0.22621 build 22621

Steps to Reproduce:

Create one simple function with type and one simple functional component, also with type but with different notation
In first simple function we can see jsdoc notation for even params, in FC - nothing

Please share example code (as text) that demonstrates the problem

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Fix package casing issue breaking build on Linux

Building this repo was failing for me on Linux due to nunit vs NUnit casing.
Fixed by normalizing to NUnit, matching https://www.nuget.org/packages/NUnit/

@nguerrera: Any idea why this is failing for you on Linux, but it seems to work for other people, it works on our Linux build agents, etc?  Is there something special about you Linux distro or config?

@mikeharder Great question and I have no idea.
This is what I have:
.NET Core SDK (reflecting any global.json):
 Version:   3.1.403
 Commit:    9e895200cd

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  20.04
 OS Platform: Linux
 RID:         ubuntu.20.04-x64
 Base Path:   /usr/share/dotnet/sdk/3.1.403/

Host (useful for support):
  Version: 3.1.9
  Commit:  774fc3d6a9

.NET Core SDKs installed:
  3.1.403 [/usr/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.23 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.23 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.9 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.23 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.9 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

Maybe something broke in a newer SDK?

These are the errors without this patch:
/home/nicholg/src/azure-sdk-for-net/sdk/core/Microsoft.Azure.Core.NewtonsoftJson/tests/Microsoft.Azure.Core.NewtonsoftJson.Tests.csproj : error : The package reference 'NUnit' must have a version defined in '/home/nicholg/src/azure-sdk-for-net/eng/Packages.Data.props'.
/home/nicholg/src/azure-sdk-for-net/sdk/digitaltwins/Azure.DigitalTwins.Core/tests/Azure.DigitalTwins.Core.Tests.csproj : error : The package reference 'NUnit' must have a version defined in '/home/nicholg/src/azure-sdk-for-net/eng/Packages.Data.props'.
/home/nicholg/src/azure-sdk-for-net/sdk/eventhub/Azure.Messaging.EventHubs.Processor/tests/Azure.Messaging.EventHubs.Processor.Tests.csproj : error : The package reference 'NUnit' must have a version defined in '/home/nicholg/src/azure-sdk-for-net/eng/Packages.Data.props'.
/home/nicholg/src/azure-sdk-for-net/sdk/eventhub/Azure.Messaging.EventHubs.Shared/tests/Azure.Messaging.EventHubs.Shared.Tests.csproj : error : The package reference 'NUnit' must have a version defined in '/home/nicholg/src/azure-sdk-for-net/eng/Packages.Data.props'.
/home/nicholg/src/azure-sdk-for-net/sdk/eventhub/Azure.Messaging.EventHubs/tests/Azure.Messaging.EventHubs.Tests.csproj : error : The package reference 'NUnit' must have a version defined in '/home/nicholg/src/azure-sdk-for-net/eng/Packages.Data.props'.
/home/nicholg/src/azure-sdk-for-net/sdk/eventgrid/Azure.Messaging.EventGrid/tests/Azure.Messaging.EventGrid.Tests.csproj : error : The package reference 'NUnit' must have a version defined in '/home/nicholg/src/azure-sdk-for-net/eng/Packages.Data.props'.
/home/nicholg/src/azure-sdk-for-net/sdk/extensions/Microsoft.Extensions.Azure/tests/Microsoft.Extensions.Azure.Tests.csproj : error : The package reference 'NUnit' must have a version defined in '/home/nicholg/src/azure-sdk-for-net/eng/Packages.Data.props'.
/home/nicholg/src/azure-sdk-for-net/sdk/digitaltwins/Azure.ResourceManager.DigitalTwins/tests/Azure.ResourceManager.DigitalTwins.Tests.csproj : error : The package reference 'NUnit' must have a version defined in '/home/nicholg/src/azure-sdk-for-net/eng/Packages.Data.props'.
/home/nicholg/src/azure-sdk-for-net/sdk/servicebus/Azure.Messaging.ServiceBus/tests/Azure.Messaging.ServiceBus.Tests.csproj : error : The package reference 'NUnit' must have a version defined in '/home/nicholg/src/azure-sdk-for-net/eng/Packages.Data.props'.

Hmmm... I know we haven't moved our agents to ubuntu 20.04 yet and I know we had some interesting string comparison issues come on there so I suspect this might be related to that somehow.

@nguerrera: Before you merge this, let me create a quick PR to bump our build agent to Ubuntu 20 and see if it fails there.

Draft PR testing Ubuntu 20: https://github.com/Azure/azure-sdk-for-net/pull/16016

@mikeharder Hmm that passed? Which SDK version is being used?

https://github.com/Azure/azure-sdk-for-net/blob/master/global.json#L6 we are using 3.1.301

@mikeharder Hmm that passed? Which SDK version is being used?

Yes, it did pass but I'm not sure what is different.  Let me try on a clean Ubuntu 20.04 VM.
This might be a bug in some of our custom build logic -- maybe we are comparing case-sensitive when it should be case-insensitive?  This is the source of the error message but I'm not very familiar with this code:
https://github.com/Azure/azure-sdk-for-net/blob/4a7444beedb6423b4dd70fd9c93fa03e241c5e74/eng/Microsoft.Build.CentralPackageVersions/2.0.46/Sdk/Sdk.targets#L170-L173

I will also update my test PR to use SDK 3.1.403 (matching the original repro).

This does look like a regression in the .NET SDK:
https://dev.azure.com/azure-sdk/public/_build/results?buildId=578706&view=logs&j=b08a78d6-c9ce-53c1-53b1-9a5d436f78f6&t=756e146f-7609-5d03-4e3a-e5bd2f3174ad&l=31
The build passes on Ubuntu 20.04 with SDK 3.1.301, but fails on Ubuntu 20.04 with SDK 3.1.402.  I'll run a few more tests to find exactly which OS/SDK versions trigger the issue.

Also fails on Ubuntu 18.04 with SDK 3.1.402.  So the Ubuntu version is not relevant.  This appears to be a regression in the .NET SDK on all Ubuntu versions.

cc @dsplaisted @nkolev92 Does this ring a bell?

Looks like the error is coming from the CentralPackageVersions SDK. @jeffkl
Also FYI @cristinamanum @adgrv

I'm surprised, the condition that generates the error is in MSBuild and is not file system dependent.  The Microsoft.Build.CentralPackageVersions SDK relies on <PackageReference Update="NUnit" Version="1.0" /> syntax, which should be case insensitive.
FYI @rainersigwald

Hi @nguerrera.  There hasn't been recent engagement on this PR.  Would you please be so kind as to let us know if this is still an active work stream or if the PR should be closed out?

This change is part of https://github.com/Azure/azure-sdk-for-net/pull/16947
Closing.


prevent KeyError in build_track_add

Certain tracks (like Tp3e52picsj55ozzmjtxwb5xpwa) are lacking keys like
artistId. Make sure a key exists before trying to scrub it.

Nice; thanks!


Service Account Access

Hello! I've been working on getting an instance of Library running locally prior to deploying in a test environment and think I have it mostly working except for one part. At the bottom of this page when attempting to share the folder with the service account address, I don't have that option. Instead, "Share" is disabled and grayed out.
After reading a bit, I found this Google support answer which says Note: You may not share folders stored in Team Drives.
We attempted to give the service account read only access to the team drive even though we're using a sub-folder, but no luck.
Here's the log output when attempting to load localhost:3000:
app_1  | debug: searching for files > 0
app_1  | debug: Current file count in drive: 0
app_1  | debug: tree updated.
app_1  | error: Serving an error page for /
app_1  | { message: 'Cannot convert undefined or null to object',
app_1  |   stack:
app_1  |    'TypeError: Cannot convert undefined or null to object\n    at Function.keys (<anonymous>)\n    at buildDisplayCategories (/usr/src/app/server/routes/pages.js:56:29)\n    at handlePage (/usr/src/app/server/routes/pages.js:47:24)' }

It may be unrelated since we aren't customizing any of the behavior, but I see the following debug errors during boot:

debug: Failed pulling in custom file cache/store @ /usr/src/app/custom/cache/store
debug: Failed pulling in custom file userAuth @ /usr/src/app/custom/userAuth
debug: Failed pulling in custom file csp @ /usr/src/app/custom/csp

Maybe we need to specify these? Is there a different way to give the service account access to a subfolder of our team drive that we might be missing? Thanks in advance!

Hey @cookrn,
As you mentioned, it's not possible to share subfolder within team drives. Instead, you need to share access on the entire team drive or use a folder outside the team drive to share that content as a blanket rule.
The first several debug log lines above indicate that the service account didn't find any Google Docs within your shared folder to display in Library. That's likely the cause of the error on the following lines Cannot convert undefined or null to object.
So far as the debug lines about failing to pull in customization options for those files go, they should not affect your ability to run the app. Are there documents within the subfolder you tried to share with Library? If so, it may indicate that Library doesn't work yet pointed at a subfolder of a Team Drive.
We've never tested that configuration before, but it sounds like a valid use case to me and we could open a new issue to support that if it's not possible currently.

Due to the topic of this issue, it is being converted into a discussion! This issue will be closed, but discussion can continue in the newly created discussion.


Switch util.GeneratePassword to password.Generate

Description of your changes

The former has been replaced by the latter.
Checklist

I have:

[ ] Run make reviewable to ensure this PR is ready for review.
[x] Ensured this PR contains a neat, self documenting set of commits.
[ ] Updated any relevant documentation, examples, or release notes.
[ ] Updated the dependencies in app.yaml to include any new role permissions.

This is super weird; this commit seems to break golangci-lint somehow in that it reports there are no Go files to analyse. 🤔

This is super weird

Ah - I missed a few uses of pkg/util. Fixed in a separate commit.


Update BuildMetricsReporter.js

↪ Pull Request

💻 Examples

🚨 Test instructions

✔ PR Todo

[ ] Added/updated unit tests for this change
[ ] Filled out test instructions (In case there aren't any unit tests)
[ ] Included links to related issues/PRs

Benchmark Results
packages/benchmarks/kitchen-sink
Timings

Description
Time
Difference

Cold
10.80s
-348.50ms 🚀

Cached
7.75s
+86.00ms

Bundles

Bundle
Size
Difference
Time
Difference

index.js
794.00b
-0.00b
415.50ms
+8.50ms

index.js
252.00b
-0.00b
417.00ms
+9.00ms

index.css
29.00b
-0.00b
1.41s
+14.50ms

index.css
29.00b
-0.00b
1.41s
+14.50ms

parcel.e91de340.webp
0.00b
-0.00b
165.50ms
-6.00ms

parcel.3cc6ed39.webp
0.00b
-0.00b
69.50ms
+21.00ms


Fix: ViewPropTypes will be removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch<EMAIL_ADDRESS>for the project I'm working on.
replace the code to solve my problem in React Native 0.69.6 to import the 'deprecated-react-native-prop-types'
Here is the diff that solved my problem:
diff --git a/node_modules/react-native-snap-carousel/src/carousel/Carousel.js b/node_modules/react-native-snap-carousel/src/carousel/Carousel.js
index dae71a3..8056cd4 100644
--- a/node_modules/react-native-snap-carousel/src/carousel/Carousel.js
+++ b/node_modules/react-native-snap-carousel/src/carousel/Carousel.js
@@ -1,5 +1,6 @@
 import React, { Component } from 'react';
-import { Animated, Easing, FlatList, I18nManager, Platform, ScrollView, View, ViewPropTypes } from 'react-native';
+import { Animated, Easing, FlatList, I18nManager, Platform, ScrollView, View } from 'react-native';
+import { ViewPropTypes } from 'deprecated-react-native-prop-types'
 import PropTypes from 'prop-types';
 import shallowCompare from 'react-addons-shallow-compare';
 import {
diff --git a/node_modules/react-native-snap-carousel/src/pagination/Pagination.js b/node_modules/react-native-snap-carousel/src/pagination/Pagination.js
index 5c021cf..4741489 100644
--- a/node_modules/react-native-snap-carousel/src/pagination/Pagination.js
+++ b/node_modules/react-native-snap-carousel/src/pagination/Pagination.js
@@ -1,5 +1,6 @@
 import React, { PureComponent } from 'react';
-import { I18nManager, Platform, View, ViewPropTypes } from 'react-native';
+import { I18nManager, Platform, View } from 'react-native';
+import { ViewPropTypes } from 'deprecated-react-native-prop-types'
 import PropTypes from 'prop-types';
 import PaginationDot from './PaginationDot';
 import styles from './Pagination.style';
diff --git a/node_modules/react-native-snap-carousel/src/pagination/PaginationDot.js b/node_modules/react-native-snap-carousel/src/pagination/PaginationDot.js
index e59d196..84821b5 100644
--- a/node_modules/react-native-snap-carousel/src/pagination/PaginationDot.js
+++ b/node_modules/react-native-snap-carousel/src/pagination/PaginationDot.js
@@ -1,5 +1,6 @@
 import React, { PureComponent } from 'react';
-import { View, Animated, Easing, TouchableOpacity, ViewPropTypes } from 'react-native';
+import { View, Animated, Easing, TouchableOpacity } from 'react-native';
+import { ViewPropTypes } from 'deprecated-react-native-prop-types'
 import PropTypes from 'prop-types';
 import styles from './Pagination.style';

diff --git a/node_modules/react-native-snap-carousel/src/parallaximage/ParallaxImage.js b/node_modules/react-native-snap-carousel/src/parallaximage/ParallaxImage.js
index 8bc774a..8fc99b7 100644
--- a/node_modules/react-native-snap-carousel/src/parallaximage/ParallaxImage.js
+++ b/node_modules/react-native-snap-carousel/src/parallaximage/ParallaxImage.js
@@ -1,7 +1,8 @@
 // Parallax effect inspired by https://github.com/oblador/react-native-parallax/

 import React, { Component } from 'react';
-import { View, ViewPropTypes, Image, Animated, Easing, ActivityIndicator, findNodeHandle } from 'react-native';
+import { View, Image, Animated, Easing, ActivityIndicator, findNodeHandle } from 'react-native';
+import { ViewPropTypes } from 'deprecated-react-native-prop-types'
 import PropTypes from 'prop-types';
 import styles from './ParallaxImage.style';

This issue body was partially generated by patch-package.

is anyone actively working on this repo ? this issue is becoming a real problem with newest versions of react native

up

Perhaps we'd be better off with someone just forking the project if there's no one around to build a new version anymore?

Have a fork here and when installing from this it works fine for me

Have a fork here and when installing from this it works fine for me

Hi @paulsjohnson91 , will you maintain and/or add features ?
I also noticed there's this https://github.com/dohooo/react-native-reanimated-carousel#readme  that looks promising.
👋

https://github.com/meliorence/react-native-snap-carousel/pull/955

https://github.com/meliorence/react-native-snap-carousel/pull/955 I sent PR for this error.

This package is abandoned

Well, they can use this: https://github.com/lfabl/react-native-snap-carousel

There is working beta for newest version of react native:
https://www.npmjs.com/package/react-native-snap-carousel/v/4.0.0-beta.6
npm i<EMAIL_ADDRESS>

There is working beta for newest version of react native: https://www.npmjs.com/package/react-native-snap-carousel/v/4.0.0-beta.6
npm i<EMAIL_ADDRESS>
@michal-pusz  but why no answer from the maintainer ? it's a bit risky to use this in a production software

react-native-reanimated-carousel seems to be the way to go as it's actively maintained

react-native-reanimated-carousel seems to be the way to go as it's actively maintained

looks good

There is working beta for newest version of react native: https://www.npmjs.com/package/react-native-snap-carousel/v/4.0.0-beta.6
npm i<EMAIL_ADDRESS>
@michal-pusz but why no answer from the maintainer ? it's a bit risky to use this in a production software

i was thinking the same!
why not comment if something exists
i did try it and works fine for me

Can anyone confirm that version<EMAIL_ADDRESS>works on RN 0.69+ ?

@danidaryaweesh I tried it and seems to be working fine, but please be careful if you want to use it in production environment since it seems to be a beta version only.

Thanks for the feedback @Guille47! I was already using this library in production with no issues. But I'm upgrading my RN from version 0.64.2 to 0.69.6, so I'm checking all libraries before doing that

Guys i already create a fork, because i think something happened with the maintainer of this repo ... try using my solution on
https://www.npmjs.com/package/react-native-new-snap-carousel
hope this help

Guys i already create a fork, because i think something happened with the maintainer of this repo ... try using my solution on
https://www.npmjs.com/package/react-native-new-snap-carousel
hope this help

i tried your one but 404 not found error is coming please share solution for that


[AppRewrite] Part 6: Loaders in the telestion-services module

Stacked Pull Request
This is a stacked pull request. Please wait on pending pull requests that reference on this branch before merging this branch.
Take a look at https://www.michaelagreiler.com/stacked-pull-requests/ for more information.
Summary
This PR adds ready-to-use Loaders to the telestion-services module for the most common use cases.
Details
The Debug Loader
The Debug Loader implements every possible event hook and logs a debug message.
This Loader is only useful to debug and test different Loader Launcher implementations.
It doesn't accept any configuration.
You can use it via its classname:
conf/telestion.json
{
  "loaders": [
    "de.wuespace.telestion.services.loader.DebugLoader"
  ]
}

The Abstract Verticle Loader

Note: This Loader is not usable in the telestion.json. Please use the Verticle Loader or the Config Loader instead.

This Loader extends the functionality of the TelestionLoader and provides methods to deploy verticles from a Verticle Configuration.
The Abstract Verticle Loader accepts one configuration property verticlesProperty which specifies the key the Loader should use to access the Verticle Configurations from the given configuration.
It provides the onConfiguration method that extending Loaders should use to deploy Verticle Configurations from a main configuration.
An example could look like:
public class MyVerticleLoader extends AbstractVerticleLoader<MyVerticleLoader.Configuration> {
	public record Configuration(
			@JsonProperty String verticlesProperty
	) implements VerticleLoaderConfiguration {
	}

	@Override
	public void onAfterVertxStartup(Promise<Void> startPromise) throws Exception {
		// load the main configuration from a specific place
		var mainConfiguration = load(/* ... */);
		onConfiguration(mainConfiguration).onComplete(startPromise);
	}
}

The Verticle Loader
The Verticle Loader reads the Verticle Configurations from the main configuration of the associated Launcher.
It has the same configuration as the Abstract Verticle Loader and use it as basis.
You can import the Loader via its classname:
conf/telestion.json
{
  "loaders": [
    "de.wuespace.telestion.services.loader.VerticleLoader"
  ],
  "verticles": [
    {
      "name": "Message Logger",
      "verticle": "de.wuespace.telestion.services.monitoring.MessageLogger",
      "magnitude": 1,
      "config": {}
    }
  ]
}

The Config Loader

Note: This Loader covers a rather advanced use case. If you want to load Verticle Configurations from the main configuration please see the Verticle Loader.

The Config Loader uses the Vert.x Config Retriever to load and merge the configuration from multiple stores (like the good old conf/config.json).
This Loader accepts beside the verticlesProperty a configuration object which maps to the ConfigRetrieverOptions.
You can use it via its classname and additional configuration:
conf/telestion.json
{
  "loaders": [
    {
      "className": "de.telestion.wuespace.services.loader.ConfigLoader",
      "config": {
        "includeDefaultStores": true,
        "stores": []
      }
    }
  ]
}

conf/config.json
{
  "verticles": [
    {
      "name": "Message Logger",
      "verticle": "de.wuespace.telestion.services.monitoring.MessageLogger",
      "magnitude": 1,
      "config": {}
    }
  ]
}

Sample project
You can find a sample project that uses the new application structure here:
https://github.com/wuespace/telestion-project-playground/tree/fussel178/feat/application-rewrite/application
Next steps
This PR belongs to a series of changes which updates the application structure in Telestion.
Read previous: https://github.com/wuespace/telestion-core/pull/504
CLA

[x] I have signed the individual contributor's license agreement and sent it to the board of the WüSpace e. V. organization.

I'll close this pull request due to inactivity and re-create one pull request with a simpler implementation.
In this new pull request the RFC: $ (dollar sign) operators in Application Configuration will also be addressed.


Add support for annotation opacity via constantOpacity

With this change PdfBox-Android now renders annotations that have constantOpacity set with the correct opacity.
You need to make a judgement on whether this can affect other parts of drawing, as I am not yet properly familiar with all the workings of PdfBox/PdfBox-Android.
Got it working for the example document attached in issue #402

@TomRoush Any chance this will be considered for an upcoming release? Let me know if there's any adjustments you'd like that I can help with.

Hi @jaranflaath, this looks good, thanks for the work. If you can rebase this PR on the latest changes in master, we can get it merged. Then it would be out in the next release

@TomRoush Done 👍


ENH: Interactive Volatility Control Charts

Fixes #79 (well, all but zooming, will open a new issue for that)
Fixes #75 ~(need to double-check this, I think the mouseover only works for the mean lines ATM)~
Fixes #82
Fixes #83

This PR is a bit large, so I broke it up into sequential commits that build on each other, and will hopefully make review a bit more digestible. Whenever it gets merged, lets squash it all down into one commit. Thanks!

If this vega business works out, we should move a lot of this boilerplate over to q2templates. Lets open an issue (if necessary) when this PR is merged.

cc @ElDeveloper

Here is a sample QZV, based on the code in this PR present as of the time of this comment. The viz is based on the q2-longitudinal tutorial  from the docs.

Oh I forgot this one — #83  is a feature that I would like to add in when we release this, if possible
In an interactive context, I suppose there should just be a "NA" option so that the means are averaged across all samples instead of splitting by group.
if it is more than a trivial task, we can save that for another day...

Thanks @nbokulich! I implemented the changes requested above in this commit. Please see the commit message for an itemized list of what was changed. Thanks!
PS - I took a stab at addressing #83 by including the sample ids in the "group" dropdown. Let me know what you think!

@thermokarst, I was testing these plots this morning and noticed that the mouseovers can be a little deceiving. See these screenshots.
Here's the overall plot I'm looking at - the mean presented in the mouseover seems reasonable:

If I hover near the last time point, but not on the last time point, it looks like the mean is the week 0 mean - this is confusing b/c it's very different than what the line suggests.

If my hover actually hits that last time point, it shows what I would expect:

Could the mouseover show the mean of the closest (before or after) time point, or of the last time point before the location of the mouse? (either of those is fine by me)

Thanks @gregcaporaso - were you using Chrome? I noticed the tooltips freak out a bit in Chrome, but not in Firefox. Will take a look - but not sure what I can do - there isn't much we can do to customize this vega plugin. If that is the case, I will need to strip the plugin and implement manually.

Just to clarify - "this vega plugin" == https://github.com/vega/vega-tooltip

Thanks @nbokulich! https://github.com/qiime2/q2-longitudinal/pull/86/commits/0ae8ab899c4de0f183fed721185a66def65ad862

We discussed out-of-band, but for posterity, will record here. This has to do with framework-level metadata merging and missing sample IDs - we won't worry about that here.
Replaced the individual samples with the individual_id_column
After much blood, sweat, and tears, I think we came up with a solution here. The diff is remarkably trivial.
Will follow up with another commit or two for addressing @gregcaporaso's mouse-over/tooltip concerns. Stay tuned! 📺

@gregcaporaso & @nbokulich - I updated the Vega libraries to use the latest and greatest, which includes a handful of improvements w.r.t. tooltips. I also found that by adding in some explicit widgets for controlling the scatterplot symbols (that were previously invisible), it makes it a bit easier to interactively interrogate discrete points.  @gregcaporaso, the reason you were seeing that weird time-point-zero tooltip was because you were first hovering over one of the invisible symbols (good), and then you were hovering over the line, which shouldn't have been displaying a tooltip at all, but was for some reason (bad). This looks like it is fixed now with the latest vega.
Check out this sample viz for an example, and please let me know how it goes. Thanks!

Thanks @thermokarst ! These are beautiful!
Everything LGTM. I have failed to break these with my tests. Ready to merge once @gregcaporaso gives his approval.

Looks great @thermokarst, thanks for figuring that issue out! I think that'll save us some support questions on the forum. I'm happy with this version, merge away @nbokulich !


Export Plugin

Would this be the way to write additional network export plugins or should they be structured/placed elsewhere?
これは追加のネットワーク エクスポート プラグインを作成する方法ですか、それとも他の場所に構造化/配置する必要がありますか?

Thank you for your interest.
I think you would like to add new plugin to export created model.
I think plugins/_Post_Process directory is suitable for this purpose, but you can put your python script under neural network console > plugins > _xxx (any ascii characters start with _).
After that, the plugin information will be updated automatically by launching neural network console application.
Some writing rules are available, please check this document (written in Japanese) : https://support.dl.sony.com/docs-ja/how_to_develop_a_plugin
I hope this information help you, but please let me know if this is not what you want to know.

I am grateful for the guidance. There is so much untapped potential in NN-Console through the use of plugins is this manner.


Fix a bug giving wrong birth times in dimension 0

When computing the persistence pairs in dimension 0, and using a filtration such as sum of vertex weights, sometimes the birth time was wrong.
The reason for this is that dset.link(u, v) was being called to late. On line 539 a test is done to see if u has been merged into v or if v has been merged into u. However, it always finds that dset.find(u)==u as the function dset.link(u, v) has not yet been called.
So I have moved dset.link(u, v) to line 531, which I think fixes the problem.

You're right it'd better for it to be inside the if branch, that was what I had originally intend but moved it to the wrong place. Fixed now.

Perfect, thanks!


Fix Workflows Credentials from Authentication options API

Fix Authentication.build_credential_types which is used by OPTIONS /api/authentications to list the API_OPTIONS used by the UI.
The other automation managers have a base credential class which is only a parent to other credential types, the workflows credential class wasn't returned by the Authentication.build_credential_types method due to this.


Add support for project isolation

Is your feature request related to a problem? Please describe.
I would like to use project isolation in our build and use the dependency analysis gradle plugin
Project isolation is described here:
https://docs.gradle.org/current/userguide/isolated_projects.html
Describe the solution you'd like
Make the necessary changes to make this plugin compliant.
Describe alternatives you've considered
None available
Additional context
Here is the first problem encountered when I tried to use project isolation:
- [error] Project `:buildSrc` cannot access `Project.plugins` functionality on another project `:`
    - plugin 'com.autonomousapps.dependency-analysis'
        - Exception at `com.autonomousapps.services.InMemoryCache$Companion.serviceHoldingBuild(InMemoryCache.kt:76)`
org.gradle.api.InvalidUserCodeException: Project ':buildSrc' cannot access 'Project.plugins' functionality on another project ':'
	at org.gradle.internal.cc.impl.ProblemReportingCrossProjectModelAccess$ProblemReportingProject_Decorated.getPlugins(Unknown Source)
	at com.autonomousapps.services.InMemoryCache$Companion.serviceHoldingBuild(InMemoryCache.kt:76)
	at com.autonomousapps.services.InMemoryCache$Companion.register$dependency_analysis_gradle_plugin(InMemoryCache.kt:90)
	at com.autonomousapps.internal.analyzer.JvmAnalyzer$registerFindDeclaredProcsTask$1.invoke(JvmProjectAnalyzer.kt:72)
	at com.autonomousapps.internal.analyzer.JvmAnalyzer$registerFindDeclaredProcsTask$1.invoke(JvmProjectAnalyzer.kt:71)
	at com.autonomousapps.internal.analyzer.JvmAnalyzer$inlined$sam$i$org_gradle_api_Action$0.execute(TaskContainerExtensions.kt)
	at java.base/java.lang.Iterable.forEach(Iterable.java:74)
	at com.intellij.gradle.toolingExtension.impl.model.warmUp.GradleTaskWarmUpService.lambda$buildAll$2(GradleTaskWarmUpService.java:34)
	at com.intellij.gradle.toolingExtension.impl.util.GradleResultUtil.lambda$runOrRetryOnce$0(GradleResultUtil.java:34)
	at com.intellij.gradle.toolingExtension.impl.util.GradleResultUtil.runOrRetryOnce(GradleResultUtil.java:16)
	at com.intellij.gradle.toolingExtension.impl.util.GradleResultUtil.runOrRetryOnce(GradleResultUtil.java:33)
	at com.intellij.gradle.toolingExtension.impl.model.warmUp.GradleTaskWarmUpService.buildAll(GradleTaskWarmUpService.java:33)
	at com.intellij.gradle.toolingExtension.impl.modelBuilder.ExtraModelBuilder.buildServiceModel(ExtraModelBuilder.java:87)
	at com.intellij.gradle.toolingExtension.impl.modelBuilder.ExtraModelBuilder.buildAll(ExtraModelBuilder.java:67)
	at com.intellij.gradle.toolingExtension.impl.modelBuilder.ExtraModelBuilder.buildAll(ExtraModelBuilder.java:47)

This plugin does already support Isolated Projects (Gradle itself has confirmed this, as they use the plugin in their own builds). Do you have a minimal reproducer?

Ok. this bug is really strange. It only reproduces in Idea. If you run gradle on its own everything is fine.  I have attached a project that when you open in Idea should fail.
deps-bug.zip


Reset background color in fullscreen Safari

Safari sets background color of fullscreen elements to white via user
agent styles. This can be seen on before/after pages when switching to
fullscreen mode.
REDMINE-16802

Coverage remained the same at 99.299% when pulling b17f0ec49c86bc88ad38ad6ed1bf1bd2d37545d2 on tf:safari-fullscreen-bg into 7af228dd19c5439180a5d2db2e617cbf44e1cef9 on codevise:master.


How to unistall apt2

How i can uninstall apt2 if it was installed using: python setup.py install. There arent options like uninstall/remove.

Honestly, I am not entirely sure.  Someone else wrote that code and personally I rarely if ever use it.  the setup.py is included for those who wish to use it.
personally, I simply run it from the github clone directory   "python apt2.py"
I will look to see what is needed to remove it if it is installed via the setup.py script.


Example/kernel oligo string

This is where there seems to be some error causing it to timeout. What can be done about this?

This is where there seems to be some error causing it to timeout. What can be done about this?

nothing, sometimes the examples overrun the timeout, but it seems like everything ran successfully :)

LGTM

thx @Hephaestus12
@gf712 do we still need to prioritize string kernel examples?
Otherwise I would say let's do kernel/distance examples last from now on and focus on other ones ....

yup, other examples would be better now (and more interesting/challenging). The only one that would be good to merge asap is #5078