WebPart blanks on SPFx package update and can not be found on page

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details
SPFx 1.13.1 in SPO and its a tenant deployed app used across multiple sites.
package-solution
{
  "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/package-solution.schema.json",
  "solution": {
    "name": "Price Inquiries",
    "id": "13456fa2-5784-4d89-bc81-6b9fa1d22fa3",
    "version": "<IP_ADDRESS>",
    "iconPath": "img/ShareCloudAppIcon96x.png",
    "includeClientSideAssets": true,
    "isDomainIsolated": false,
    "developer": {
      "name": "ShareCloud OÜ",
      "websiteUrl": "https://sharecloud.ee",
      "privacyUrl": "",
      "termsOfUseUrl": "",
      "mpnId": "xxxx"
    },
    "webApiPermissionRequests": [
      {
        "resource": "Microsoft Graph",
        "scope": "Mail.Send"
      },
      {
        "resource": "Microsoft Graph",
        "scope": "Mail.ReadWrite"
      },
      {
        "resource": "Microsoft Graph",
        "scope": "User.ReadBasic.All"
      }
    ],
    "features": [
      {
        "title": "Application Extension - Deployment of custom action.",
        "description": "Deploys a custom action with ClientSideComponentId association",
        "id": "e8c7a393-b4a2-448d-8130-17e3e28b1e56",
        "version": "<IP_ADDRESS>",
        "assets": {
          "elementManifests": [
            "elements.xml",
            "ClientSideInstance.xml"
          ]
        }
      }
    ]
  },
  "paths": {
    "zippedPackage": "solution/price-inquiries.sppkg"
  }
}

Describe the bug / error
So I managed to blank one of the biggest WebParts for one of largest customers. Thankfully it happened when I was at ESPC22 and could find some sort of an explanation for our customer, but the issue I ran into basically stems from this one:
https://github.com/SharePoint/sp-dev-docs/issues/7929
Now the explanation that the kind MS expert gave me... just does not make sense, because the timeline does not match... but it was good enough for our client.
However, here is how I managed to blank our biggest customers largest WebParts.
Background:

SPFx 1.13.1 WebPart in production for a while and the client ordered a new major add-on before ESPC22, with was developed.

The update contained:

New WebPart
New Field Customizer
New Command Set Customizer

Blank Timeline:

The update was deployed on the last working day before ESPC22 and as far as we knew was working as expected.
At some point the client noticed that one feature in the product was not working it did before (minor bug, let me know if you think it could be relavent)
The bug was fixed and deployed on Wednesday
The package was working on the Pre-Live site (with its own app catalog)
Was deployed to tenant in the evening and I checked it one one of the Live sites (but not the problematic site)
Thursday, the subsidiary of the client who uses the problematic site discovers that the pages are blank after we told them that the minor bug was fixed... fun.

Fix:
So as the above issue says, the only way to fix this is to delete app from the app catalog and re-install it and yes... I did try everything else before trying something this extreme on the client live tenant on something this crucial.
Fix Notes:

In a live production site that is being used actively and has its own app catalog this does not work... simply because you can't de-facto you can't access the site's second level recycle bin. However if the explanation the MS expert gave me is even close to the truth, then this should happen only in a tenant deployed app. (I will open a second issue about this.)
IMPORTANT! - Once deleted and re-installed, make sure to update all the sites to the latest version of the app or they will not function as expected!

The issue as the MS Expert explained:
So as you can see in the package-solution.json I have the "features" filled. Namely he postulated that the SPFx version I had a bug that filled the array when it should not have when adding in a new WebPart and once deployed that will blank the package.
This explanation was good enough for our client, but I it just does not make sense it you look at the timeline. Namely the site that blanked was working with the minor bug version when ESPC22 started. The subsidiary who eventually blanked was the one that noticed the bug and reported it, but for them to report it they the package must have been deployed successfully before ESPC22.
Steps to reproduce
Sry I am not 100% on this ATM
Expected behavior
Update the package on SPO tenant app catalog and the WebPart should not blank

@IllimarAtShareCloud
The explanation you received during ESPC can be absolutely correct.
In your case you have added extensions to the existing projects.
When you add an extension (and starting with 1.14 - any type of the component) it will add a new feature to the features list in the package-solution.json file.
As this feature doesn't have componentIds property it will collect all the components in the solution to be part of the feature.
As a result,
before adding the extension you had auto-generated feature for each web part with ID === id of the web part.
after adding the extension you have a new single feature with new ID that contains all the components.
In that case on SharePoint side you have a mismatch as the same component was part of one feature and then - another.
In your case the solution probably is to add componentIds to the new generated features, and include only extensions in there.
In that case all web parts should still have their own features.
You can check the features after running gulp package-solution in sharepoint/debug folder.
Let me know if that helps.

Amm... I ran the command in the folder, but I do not get what I got.
However, if I understand correctly the issue should be fixed in the latest SPFx that is out already. We where planning to simply update all of our packages to the latest version so we would not run into it again.
Could you please tell me in with SPFx version is safe to use. We usually keep our packages 1-2 versions behind the latest just in case.

ty for the info, ATM we can't update to 1.16.1 anyway because when we tested it we ran into this yesterday:
https://github.com/SharePoint/sp-dev-docs/issues/8623
So we will simply stick with 1.13.1 and delete the tenant app before the update just to be safe.

@IllimarAtShareCloud - yes, there is an issue in 1.16.1.
That's why we rolled back to 1.16.0 and will get back to 1.16.1 next week.


Describe logged-in requirement in readme

Closes #126
Should probably add this to the Chrome Webstore too.

I added a note to the Chrome store page.


Jinja2 is sinle quoting while using the Template function + render

The issue tracker is a tool to address bugs in Jinja itself.
Please use the #pocoo IRC channel on freenode or Stack Overflow for general
questions about using Jinja or issues not related to Jinja.
If you'd like to report a bug in Jinja, fill out the template below and provide
any extra information that may be useful / related to your problem.
Ideally, you create an MCVE reproducing
the problem before opening an issue to ensure it's not caused by something in
your code.

Expected Behavior
Double quotining
Actual Behavior
Single quoting
Template Code
Paste the template code (ideally a minimal example) that causes the issue

Full Traceback
Paste the full traceback in case there is an exception

Your Environment

Python version: 3.7
Jinja version: 2.11.2

You need to show some actual code and explain what exactly is happening. With the amount of detail you provided so far I have no idea what your problem is...


Queuing incoming requests during fallback on replicas

currently, we require that clients resubmit requests after the fallback is over. but with the deduplication, we can have replicas queue requests and immediately start back on the fast path

not worth implementing? seems add more uncertainty, and we generally assume fallback happen rarely, the perf improve will be minor,


Fix example to support correct Transformer version (#3556)

Fix requested to be part of the <IP_ADDRESS> release

Looks to be a tensorflow version, not transformer


datalib has no module: datalib.pgvgraph , no pygraphvis

if you are working in anaconda, the best solution is to go to the enviroment section and install pygraph in it.


Allow short aliases to refer to application/* as well as text/* for json types

This is the rest of my fix - a few extra tests, but also removes the need for lang to always start with text/. Often json types use application/

🎉


Fix clippy by avoiding deprecated functions in chrono

Which issue does this PR close?

Closes #3097.
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

cc @tustvold @alamb

Thanks @viirya


fix Issue 14949 - Non-descriptive "Enforcement failed" when attemptin…

…g to write to closed file
https://issues.dlang.org/show_bug.cgi?id=14949

LGTM

Auto-merge toggled on


app.py not working

Hi Team,
Thanks for the great work!
After installation, I tried python app.py. The website is launched with message: Welcome to chat with me. But when I started chatting, it keeps coming back with only: There is something wrong, please query again. The model was :
model_name_or_path = '../output_models/gpt_neo2.7B_inst_tuning/'
Below are logging infos:
/home/t3080/anaconda3/envs/lmflow/bin/python /home/t3080/workspace_AI/LMFlow/service/app.py
[2023-04-05 18:39:51,605] [INFO] [comm.py:570:init_distributed] Not using the DeepSpeed or dist launchers, attempting to detect MPI environment...
[2023-04-05 18:39:51,714] [INFO] [comm.py:620:mpi_discovery] Discovered MPI settings of world_rank=0, local_rank=0, world_size=1, master_addr=<IP_ADDRESS>, master_port=29500
[2023-04-05 18:39:51,714] [INFO] [comm.py:586:init_distributed] Initializing TorchBackend in DeepSpeed with backend nccl
[2023-04-05 18:39:51,715] [INFO] [logging.py:96:log_dist] [Rank 0] DeepSpeed info: version=0.8.3+e73de8ce, git-hash=e73de8ce, git-branch=master
[2023-04-05 18:39:51,808] [INFO] [logging.py:96:log_dist] [Rank 0] DeepSpeed Flops Profiler Enabled: False
[2023-04-05 18:39:51,809] [INFO] [logging.py:96:log_dist] [Rank 0] Creating BF16 optimizer
[2023-04-05 18:39:51,880] [INFO] [utils.py:780:see_memory_usage] begin bf16_optimizer
[2023-04-05 18:39:51,881] [INFO] [utils.py:781:see_memory_usage] MA 5.13 GB         Max_MA 10.37 GB         CA 10.38 GB         Max_CA 10 GB
[2023-04-05 18:39:51,881] [INFO] [utils.py:788:see_memory_usage] CPU Virtual Memory:  used = 12.91 GB, percent = 20.8%
Using /home/t3080/.cache/torch_extensions/py39_cu117 as PyTorch extensions root...
Emitting ninja build file /home/t3080/.cache/torch_extensions/py39_cu117/utils/build.ninja...
Building extension module utils...
Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
Loading extension module utils...
ninja: no work to do.
Time to load utils op: 0.26142168045043945 seconds
[2023-04-05 18:39:52,485] [INFO] [utils.py:780:see_memory_usage] end bf16_optimizer
[2023-04-05 18:39:52,486] [INFO] [utils.py:781:see_memory_usage] MA 5.13 GB         Max_MA 5.13 GB         CA 10.38 GB         Max_CA 10 GB
[2023-04-05 18:39:52,486] [INFO] [utils.py:788:see_memory_usage] CPU Virtual Memory:  used = 12.94 GB, percent = 20.9%
[2023-04-05 18:39:52,486] [INFO] [config.py:935:print] DeepSpeedEngine configuration:
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   activation_checkpointing_config  {
"partition_activations": false,
"contiguous_memory_optimization": false,
"cpu_checkpointing": false,
"number_checkpoints": null,
"synchronize_checkpoint_boundary": false,
"profile": false
}
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   aio_config ................... {'block_size': 1048576, 'queue_depth': 8, 'thread_count': 1, 'single_submit': False, 'overlap_events': True}
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   amp_enabled .................. False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   amp_params ................... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   autotuning_config ............ {
"enabled": false,
"start_step": null,
"end_step": null,
"metric_path": null,
"arg_mappings": null,
"metric": "throughput",
"model_info": null,
"results_dir": "autotuning_results",
"exps_dir": "autotuning_exps",
"overwrite": true,
"fast": true,
"start_profile_step": 3,
"end_profile_step": 5,
"tuner_type": "gridsearch",
"tuner_early_stopping": 5,
"tuner_num_trials": 50,
"model_info_path": null,
"mp_size": 1,
"max_train_batch_size": null,
"min_train_batch_size": 1,
"max_train_micro_batch_size_per_gpu": 1.024000e+03,
"min_train_micro_batch_size_per_gpu": 1,
"num_tuning_micro_batch_sizes": 3
}
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   bfloat16_enabled ............. True
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   checkpoint_parallel_write_pipeline  False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   checkpoint_tag_validation_enabled  True
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   checkpoint_tag_validation_fail  False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   comms_config ................. <deepspeed.comm.config.DeepSpeedCommsConfig object at 0x7f435772cd90>
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   communication_data_type ......  False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   curriculum_params_legacy ..... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   data_efficiency_config ....... {'enabled': False, 'seed': 1234, 'data_sampling': {'enabled': False, 'num_epochs': 1000, 'num_workers': 0, 'curriculum_learning': {'enabled': False}}, 'data_routing': {'enabled': False, 'random_ltd': {'enabled': False, 'layer_token_lr_schedule': {'enabled': False}}}}
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   data_efficiency_enabled ...... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   dataloader_drop_last ......... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   disable_allgather ............ False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   dump_state ................... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   dynamic_loss_scale_args ...... None
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   eigenvalue_enabled ........... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   eigenvalue_gas_boundary_resolution  1
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   eigenvalue_layer_name ........ bert.encoder.layer
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   eigenvalue_layer_num ......... 0
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   eigenvalue_max_iter .......... 100
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   eigenvalue_stability ......... 1e-06
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   eigenvalue_tol ............... 0.01
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   eigenvalue_verbose ........... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   elasticity_enabled ........... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   flops_profiler_config ........ {
"enabled": false,
"profile_step": 1,
"module_depth": -1,
"top_modules": 1,
"detailed": true,
"output_file": null
}
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   fp16_auto_cast ............... None
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   fp16_enabled ................. False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   fp16_master_weights_and_gradients  False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   global_rank .................. 0
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   grad_accum_dtype ............. None
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   gradient_accumulation_steps .. 1
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   gradient_clipping ............ 0.0
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   gradient_predivide_factor .... 1.0
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   initial_dynamic_scale ........ 1
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   load_universal_checkpoint .... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   loss_scale ................... 1.0
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   memory_breakdown ............. False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   monitor_config ............... tensorboard=TensorBoardConfig(enabled=False, output_path='', job_name='DeepSpeedJobName') wandb=WandbConfig(enabled=False, group=None, team=None, project='deepspeed') csv_monitor=CSVConfig(enabled=False, output_path='', job_name='DeepSpeedJobName') enabled=False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   nebula_config ................ {
"enabled": false,
"persistent_storage_path": null,
"persistent_time_interval": 100,
"num_of_version_in_retention": 2,
"enable_nebula_load": true,
"load_path": null
}
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   optimizer_legacy_fusion ...... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   optimizer_name ............... None
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   optimizer_params ............. None
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   pipeline ..................... {'stages': 'auto', 'partition': 'best', 'seed_layers': False, 'activation_checkpoint_interval': 0}
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   pld_enabled .................. False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   pld_params ................... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   prescale_gradients ........... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   scheduler_name ............... None
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   scheduler_params ............. None
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   sparse_attention ............. None
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   sparse_gradients_enabled ..... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   steps_per_print .............. 2000
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   train_batch_size ............. 1
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   train_micro_batch_size_per_gpu  1
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   use_node_local_storage ....... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   wall_clock_breakdown ......... False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   world_size ................... 1
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   zero_allow_untested_optimizer  False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   zero_config .................. stage=0 contiguous_gradients=True reduce_scatter=True reduce_bucket_size=500,000,000 allgather_partitions=True allgather_bucket_size=500,000,000 overlap_comm=False load_from_fp32_weights=True elastic_checkpoint=False offload_param=None offload_optimizer=None sub_group_size=1,000,000,000 cpu_offload_param=None cpu_offload_use_pin_memory=None cpu_offload=None prefetch_bucket_size=50,000,000 param_persistence_threshold=100,000 model_persistence_threshold=sys.maxsize max_live_parameters=1,000,000,000 max_reuse_distance=1,000,000,000 gather_16bit_weights_on_model_save=False stage3_gather_fp16_weights_on_model_save=False ignore_unused_parameters=True legacy_stage1=False round_robin_gradients=False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   zero_enabled ................. False
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   zero_force_ds_cpu_optimizer .. True
[2023-04-05 18:39:52,487] [INFO] [config.py:939:print]   zero_optimization_stage ...... 0
[2023-04-05 18:39:52,487] [INFO] [config.py:925:print_user_config]   json = {
"fp16": {
"enabled": false
},
"bf16": {
"enabled": true
},
"steps_per_print": 2.000000e+03,
"train_micro_batch_size_per_gpu": 1,
"wall_clock_breakdown": false
}
Time to load utils op: 0.00018405914306640625 seconds

Serving Flask app 'app'
Debug mode: off
Using /home/t3080/.cache/torch_extensions/py39_cu117 as PyTorch extensions root...
No modifications detected for re-loaded extension module utils, skipping build step...
Loading extension module utils...
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
Running on http://<IP_ADDRESS>:5000
Press CTRL+C to quit

Could you please help to check out what could be wrong?
Lots of thanks
George

Hi George,
Could you have a check which config you are using? Is it the one under ‘examples/‘ ?

Yes, examples/ds_config.json

ds_config_path = "../examples/ds_config.json"
Original code not changed...

I have the same problem by using the docker image

I have the same problem by using the docker image

Thanks your interest in LMFlow! I am not sure about the original issue, but for docker to work, you may need to map docker container's port to the host's port in the docker run ... command. I am not sure but I conjecture the original issue is also caused by port problem.
Could you please check if running
python -m http.server 5000

successfully opens a HTTP service in your server? (To get the IP of your server, you may run ifconfig, then access the website in your browser via http://{your-ip}:5000, a page with some folders on your server should appear. For localhost, like local Mac OSX PC computers, you may access http://<IP_ADDRESS>:5000)
Hope that can help you. Thanks!

I have the same problem by using the docker image

Thanks for your interest in LMFlow! I am not sure about the original issue, but for docker to work, you may need to map docker container's port to the host's port in the docker run ... command. I am not sure but I conjecture the original issue is also caused by port problem.
Could you please check if running
python -m http.server 5000

successfully opens a HTTP service in your server? (To get the IP of your server, you may run ifconfig, then access the website in your browser via http://{your-ip}:5000, a page with some folders on your server should appear. For localhost, like local Mac OSX PC computers, you may access http://<IP_ADDRESS>:5000)
Hope that can help you. Thanks!

Thanks ~ but i already map the container's port to the host's port，and the web page looks ok, i can send message, but always reply'There is something wrong, please query again'. my machine is 4*A4000 16G

I am wondering if run_chatbot.sh works? If not, we may try to make run_chatbot.sh work first. If run_chatbot.sh works fine, it may be caused by app.py only. In that case, one of my guesses is that it was caused by multi-GPU inference. You may try to turn on export CUDA_VISIBLE_DEVICES=0 and see if the problem occurs again. Thanks 😄

I tried run_chatbot.sh. The result seems ok except the answers from the bot quite weird. See below infos
User >>> hi
Bot: , a former member of the U.S. House of Representatives, said the bill would "make it easier for the government to spy on Americans."
User >>> what's your name?
Bot:
User >>> how old are you?

As for the app.py, even export CUDA_VISIBLE_DEVICES=0 is done, the result is still the same. It keeps exporting: There is something wrong, please query again. I am running on my local machine and using the local browser to  access http://<IP_ADDRESS>:5000

Thanks! Looks like the problem is in app.py, not the chatbot itself. @SHUMKASHUN We will look into it and get back to you as soon as we locate the problem. Thanks for your understanding 🙏
As for the chatbot's weird output, it is as expected since gpt-neo-2.7b is a rather weak model, hence sometimes it outputs strange words or repeats. You may try stronger models or further finetune the model, and those problems will be less severe. Thanks 😄

OK. Stay tuned.
Thanks!

Hi team,

Some more information. I tried python app.py on another machine with 4 RTX3090. It's still not working. My machine has 512G ram and 32 CPU cores.

Thanks
George

@SHUMKASHUN Could you please check this problem? Looks like an issue related service.

Hi @george66s ,
I am sorry for the late reply. Could you please try using single gpu by deepspeed --num_gpus=1 app.py. Because of some reason, flask with multi-gpus will lead to vert low inference speed, so current app.py is only designed for single gpu.


MockHandler - Add support to reset internal queue

Q
A

Bug?
no

New Feature?
yes

Version
6.3.3

Actual Behavior
MockHandler doesn't offer a way of resetting the internal queue. There are testing scenarios where the handler has been initialized in the setUp() method of a test suite, to avoid duplication, and some specific responses are queued up as the default behavior but then you have tests which need to queue up something different (i.e a request error).
In this cases, it is not possible to reuse the handler defined in setUp(), and instad, it is required to re-instantiate and re-wire a handler and the dependencies all over again.
Expected Behavior
To avoid having to wire and set up the handler all over again, it would be great to expose a way to reset the internal queue in the MockHandler instance, and then just queue the new response(s).
This PR adds a method to MockHandler to reset the internal queue. Calling $handler->reset();  would reset the internal array and allow the tester to queue up new responses.

@sagikazarmark @Nyholm Please let me know what do you think about this little feature, and whether this is the correct way of doing this or if there is a better way that maybe I'm not aware of.

rebased with latest from master

Thank you for reviewing/merging! 🎉


Highlight string escape /

Right now we don't really see if something is escaped or not.  Related https://github.com/Azure/typespec-azure/issues/3399
Example in typescript

I believe this is actually a downgrade from using the semantic highlighting


Use thread-safe cache in thread_local_caching_allocator

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each------InfoPropertyBeforeAfterHPX Datetime2024-03-18T14:00:30+00:002024-09-07T00:47:36+00:00HPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477fe972af2a5b4ee1afbcd4ac398814f6c3cec30cb6ClusternamerostamrostamDatetime2024-03-18T09:18:04.949759-05:002024-09-06T19:55:11.519858-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Datetime2024-03-18T14:00:30+00:002024-09-07T00:47:36+00:00HPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477fe972af2a5b4ee1afbcd4ac398814f6c3cec30cb6ClusternamerostamrostamDatetime2024-03-18T09:19:53.062988-05:002024-09-06T19:57:01.633845-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add------Stream Benchmark - Scale-------Stream Benchmark - Triad------Stream Benchmark - Copy------InfoPropertyBeforeAfterHPX Datetime2024-03-18T14:00:30+00:002024-09-07T00:47:36+00:00HPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477fe972af2a5b4ee1afbcd4ac398814f6c3cec30cb6ClusternamerostamrostamDatetime2024-03-18T09:20:13.002391-05:002024-09-06T19:57:19.484829-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each------InfoPropertyBeforeAfterHPX Datetime2024-03-18T14:00:30+00:002024-09-07T22:36:42+00:00HPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477fb751e7222b8a81dc3f249ebed4c5ff450c3ea88cClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5EnvfileDatetime2024-03-18T09:18:04.949759-05:002024-09-07T17:45:10.927119-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Datetime2024-03-18T14:00:30+00:002024-09-07T22:36:42+00:00HPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477fb751e7222b8a81dc3f249ebed4c5ff450c3ea88cClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5EnvfileDatetime2024-03-18T09:19:53.062988-05:002024-09-07T17:47:00.957806-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add------Stream Benchmark - Scale-------Stream Benchmark - Triad------Stream Benchmark - Copy------InfoPropertyBeforeAfterHPX Datetime2024-03-18T14:00:30+00:002024-09-07T22:36:42+00:00HPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477fb751e7222b8a81dc3f249ebed4c5ff450c3ea88cClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5EnvfileDatetime2024-03-18T09:20:13.002391-05:002024-09-07T17:47:18.556829-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each------InfoPropertyBeforeAfterHPX Datetime2024-03-18T14:00:30+00:002024-09-09T17:15:16+00:00HPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477fed89bf1eb08064ae1ffe977a90813110c6c85091Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamEnvfileDatetime2024-03-18T09:18:04.949759-05:002024-09-09T12:25:01.395820-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Datetime2024-03-18T14:00:30+00:002024-09-09T17:15:16+00:00HPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477fed89bf1eb08064ae1ffe977a90813110c6c85091Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamEnvfileDatetime2024-03-18T09:19:53.062988-05:002024-09-09T12:26:52.095834-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add------Stream Benchmark - Scale-------Stream Benchmark - Triad------Stream Benchmark - Copy------InfoPropertyBeforeAfterHPX Datetime2024-03-18T14:00:30+00:002024-09-09T17:15:16+00:00HPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477fed89bf1eb08064ae1ffe977a90813110c6c85091Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamEnvfileDatetime2024-03-18T09:20:13.002391-05:002024-09-09T12:27:09.764152-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

@Pansysk75 we still have the circular dependency between the concurrency and allocator modules. Also, some of the header tests are failing (most likely caused by the circular dependency issue)

@Pansysk75 we still have the circular dependency between the concurrency and allocator modules. Also, some of the header tests are failing (most likely caused by the circular dependency issue)

Hmm I suppose that means the allocator_support module is higher in the module hierarchy than the concurrency module?
I'm not exactly sure what fixing this would involve.

@Pansysk75 we still have the circular dependency between the concurrency and allocator modules. Also, some of the header tests are failing (most likely caused by the circular dependency issue)

Hmm I suppose that means the allocator_support module is higher in the module hierarchy than the concurrency module? I'm not exactly sure what fixing this would involve.

Yes, see: https://hpx-docs.stellar-group.org/latest/report/v1.10.0/core/allocator_support.html

Oh, also, we should probably make all accesses to members of allocated_cache thread safe... Not sure why I ignored that. Also, this now makes me dislike this solution even more.

Yes, the deallocated and allocated members should be atomic. But we should combine both variables into one counter for that.

I opened an issue #6540 to document this.

Thanks!

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each------InfoPropertyBeforeAfterHPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477f3c74e4bad47aa0960477a99bddf8e8c395b258ddHPX Datetime2024-03-18T14:00:30+00:002024-09-11T23:01:22+00:00EnvfileDatetime2024-03-18T09:18:04.949759-05:002024-09-11T18:42:36.321504-05:00ClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477f3c74e4bad47aa0960477a99bddf8e8c395b258ddHPX Datetime2024-03-18T14:00:30+00:002024-09-11T23:01:22+00:00EnvfileDatetime2024-03-18T09:19:53.062988-05:002024-09-11T18:44:26.972373-05:00ClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add------Stream Benchmark - Scale------Stream Benchmark - Triad------Stream Benchmark - Copy-------InfoPropertyBeforeAfterHPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477f3c74e4bad47aa0960477a99bddf8e8c395b258ddHPX Datetime2024-03-18T14:00:30+00:002024-09-11T23:01:22+00:00EnvfileDatetime2024-03-18T09:20:13.002391-05:002024-09-11T18:44:44.719698-05:00ClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each------InfoPropertyBeforeAfterHPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477f1bb079662f04637aa7084809d24fded673df2d30HPX Datetime2024-03-18T14:00:30+00:002024-09-12T16:43:09+00:00ClusternamerostamrostamEnvfileDatetime2024-03-18T09:18:04.949759-05:002024-09-12T11:50:01.583868-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477f1bb079662f04637aa7084809d24fded673df2d30HPX Datetime2024-03-18T14:00:30+00:002024-09-12T16:43:09+00:00ClusternamerostamrostamEnvfileDatetime2024-03-18T09:19:53.062988-05:002024-09-12T11:51:51.740992-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add------Stream Benchmark - Scale-----Stream Benchmark - Triad------Stream Benchmark - Copy------InfoPropertyBeforeAfterHPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477f1bb079662f04637aa7084809d24fded673df2d30HPX Datetime2024-03-18T14:00:30+00:002024-09-12T16:43:09+00:00ClusternamerostamrostamEnvfileDatetime2024-03-18T09:20:13.002391-05:002024-09-12T11:52:09.519499-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

@Pansysk75 I think this is good to go as a stop-gap measure circumventing the underlying problem from happening. What do you think?

@Pansysk75 I think this is good to go as a stop-gap measure circumventing the underlying problem from happening. What do you think?

Sure, one last thing, what is this check supposed to do? Our underlying data structure has a .size() member function, is it any different to use that?

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each------InfoPropertyBeforeAfterHPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477f36162bef56888b301b9a9a582191b8fe3d0a8d82HPX Datetime2024-03-18T14:00:30+00:002024-10-17T16:31:14+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5Datetime2024-03-18T09:18:04.949759-05:002024-10-17T11:40:01.944161-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamEnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477f36162bef56888b301b9a9a582191b8fe3d0a8d82HPX Datetime2024-03-18T14:00:30+00:002024-10-17T16:31:14+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5Datetime2024-03-18T09:19:53.062988-05:002024-10-17T11:41:51.944113-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamEnvfileComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add------Stream Benchmark - Scale------Stream Benchmark - Triad------Stream Benchmark - Copy------InfoPropertyBeforeAfterHPX Commitd27ac2efb17ed7a61d0417a1926ba8991f4f477f36162bef56888b301b9a9a582191b8fe3d0a8d82HPX Datetime2024-03-18T14:00:30+00:002024-10-17T16:31:14+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/18.1.5/bin/clang++ 18.1.5Datetime2024-03-18T09:20:13.002391-05:002024-10-17T11:42:12.510962-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamEnvfileExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

@Pansysk75 the original issues are resolved here. Let's merge it now.


exp/services/soroban-rpc: support version parameter on command line

What problem does your feature solve?
find out the build version of soroban-rpc
What would you like to see?
soroban-rpc version returns the build version or git commit hash if available.
What alternatives are there?

Could this version also include:

Version of XDR
Version of embedded Env


NullPointerException on ND4j.create after running the ENCDECLSTM example

We are taking this example as reference to develop a seq2seq predicter, by running this project we fixed the data to fit with our expectations.
Here is the code > https://github.com/samuelchapas/LSTMEncDecDL4J
After running it, we got this issue placed on the CorpusIterator
https://gist.github.com/samuelchapas/50300c608f3235704c59861f29a31abf
This is the section of code where the issue is placed.
https://gist.github.com/samuelchapas/140cef4fb5cde297ac470422c24c57f3
Thanks for your help.

well the problem was fixed by taking only the lines of the custom data with words.


Add browser APIs that need to be supported to the README

What
In the README, adds references and statistics about the browser APIs that the polyfill needs to function.
Why
As a consumer of this polyfill, it's not obvious whether a given browser will support it or not. Knowing what the underlying APIs are enables consumers to determine this by, for example, looking them up on https://caniuse.com/

Addresses https://github.com/speechly/speech-recognition-polyfill/issues/28


[CM-1013] Logout User from device when password gets changed from das…

…hboard (#20)

Logout User incase of password change

Added logoutLocally function

optimised logout flow

Co-authored-by: Sathyan Elangovan<EMAIL_ADDRESS>

testing notification for slack channel


Hand Flipped Upside-down for block TSR

Now that the hand and FT sensor are mounted correctly (plan to home config works correctly), it seems the TSR is flipped, so the extended finger points down and hits the table.

@ClintLiddick Is this still an issue?

I believe we decided the issue was that the hand itself was physically
flipped.
On Monday, February 8, 2016, Michael Koval<EMAIL_ADDRESS>wrote:

@ClintLiddick https://github.com/ClintLiddick Is this still an issue?
—
Reply to this email directly or view it on GitHub
https://github.com/personalrobotics/herbpy/issues/64#issuecomment-181603990
.

--
Jen King


[WIP] Try xcode9.3 as claimed to use java 1.8 by default (https://docs.trav…

…is-ci.com/user/reference/osx/#OS-X-Version)
Fixes issue #<issue_number>
Brief summary of changes
Testing I've completed
CHANGELOG.md (choose one)

no need to update because...
updated...

@chrisdembia Per the travis page here https://docs.travis-ci.com/user/reference/osx using xcode9.3 would get java 1.8 by default, however the build fails due to trying to use open-jdk 13, any idea what we're doing wrong here? Thanks

Well, it looks like Travis-CI is failing because it can't find Ant, and GitHub Actions is failing because brew install ant is not working (probably temporarily).

@chrisdembia True but not finding ant is a downstream effect of not finding the right java, per the page I linked to above their osx, xcode combination defaults to xcode 9.4.1 which is java 13.  Check log of last successful build shows Java 1.8 installed first

Hmmm...maybe we could try specifying the jdk key.
https://docs.travis-ci.com/user/languages/java/#testing-against-multiple-jdks


Test Flake: TestContainerHostname

Flake during Linux Integration (io.containerd.runc.v2, crun) in "Integration 2"
=== Failed
=== FAIL: . TestContainerHostname (0.13s)
    log_hook.go:47: time="2023-02-10T06:30:03.283804919Z" level=debug msg="remote introspection plugin filters" func="introspection.(*introspectionRemote).Plugins" file="/home/runner/work/containerd/containerd/services/introspection/introspection.go:46" filters="[type==io.containerd.snapshotter.v1, id==overlayfs]" testcase=TestContainerHostname
    container_test.go:1178: expected output "myhostname" but received ""

DONE 153 tests, 7 skipped, 1 failure in 174.161s
make: *** [Makefile:215: integration] Error 1
Error: Process completed with exit code 2.

After the job is re-run, a message is displayed that the job succeeded


Use 1ES pools for all internal jobs

We need to change this:
https://github.com/microsoft/go/blob/9b40a19bd6840ed5c2818e1896d9868603a2a120/eng/pipeline/jobs/run-job.yml#L16-L30
to be more like this:
https://github.com/microsoft/go/blob/9b40a19bd6840ed5c2818e1896d9868603a2a120/eng/pipeline/jobs/sign-job.yml#L19-L22
Note that release branches use a different pool:
https://github.com/microsoft/go/blob/86be7f0711e77709c0629899f75b9b6268e7481b/eng/pipeline/jobs/sign-job.yml#L19-L22
(We should change the hard-coded internal/public pool into a condition, so we don't need to keep track of that when forking new release branches.)
As of writing, we have no specific deadline for this. It depends on https://github.com/dotnet/core-eng/issues/15256.

On the Docker side, the .NET Docker infrastructure made these changes to use 1ES pools: https://github.com/dotnet/docker-tools/pull/954/files.

I tested out the replacement pool in https://github.com/dotnet/core-eng/issues/15256, and it worked, and I've just been told it's now live. This work should be unblocked now. 🎉

Done (but different targets) by 1ES PT migration.


feat(op): Ecotone hardfork

Overview
Adds definitions and support for the upcoming Ecotone hardfork on Optimism.
Details
The Ecotone hardfork is activated alongside Cancun, with few execution layer modifications of our own. The rollup will now be using 4844 DA, which involves some changes to the L1 fee calculation.

Ecotone L1 fee specifications: https://github.com/ethereum-optimism/specs/blob/main/specs/exec-engine.md#ecotone-l1-cost-fee-changes-eip-4844-da
Ecotone L1 fee reference implementation: https://github.com/ethereum-optimism/op-geth/blob/a4e85ec465e2de3f962d757d8f9b561b5461f861/core/types/rollup_cost.go

@rakita Yep! The idea was to have runtime configuration for the optimism features, if revm is compiled with the optimism feature flag enabled. This was for tools like foundry to be able to swap between optimism and default ethereum execution at runtime, for example in fork tests.
This can be abstracted into the handler instead as well, but the ability to switch between the optimism and default execution at runtime is still desired.

@rakita Yep! The idea was to have runtime configuration for the optimism features, if revm is compiled with the optimism feature flag enabled. This was for tools like foundry to be able to swap between optimism and default ethereum execution at runtime, for example in fork tests.
This can be abstracted into the handler instead as well, but the ability to switch between the optimism and default execution at runtime is still desired.

Yeah, this can be abstracted with handler register! Good to know, will remove the flag.
Optimism feature is still needed for additional field (l1block) and for additional SpecIds. But will see to make those generic in future.


Triton docker container failed to start due to unknown error

The inference task was successfully created after launching the serving services (clearml-serving launch --queue default).
However, it seems that the nvdia container failed to start with the following error:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: driver error: failed to process request: unknown.

Using a local worker without GPU attached to the public hosting clearml server.

Hi @janesenaj,
From a quick look online, it seems this error is related to the NVIDIA driver you have installed - can you try to upgrade to a newer driver?

Closing this issue as inactive, feel free to open a new issue and link to this one.


Local setup + SSH pipe + NFS

Hi,
I'm basically using this:
ssh USER@HOST "tail -f LOG_LOCATION/access.log" | goaccess --log-format=COMBINED -o /data/goaccess/goaccess.html --real-time-html -
That /data/goaccess/goaccess.html is exported using NFS to another server in the same network. The destination goaccess.html file gets written ok but subsequent updates don't get written and the html report does not get updated with new data.
If I use the same command but displaying the data in CLI, I see the data updating every second.
Am I missing something? Do you know of any issues with NFS?

The server that runs the goaccess command and thus, creates the html report, does not have a public IP, only a local one.
The server that has a public IP now has an NFS share with dest folder to /data/goaccess/goaccess.html on the private goaccess server above.
So, the goaccess server writes the html report to the NFS share and I'm access the goaccess.html on the public server through a web url.
This should work, right?

The front facing, public website is reporting:
WebSocket connection to 'wss://DOMAIN:7890/' failed: Error in connection establishment: net::ERR_CONNECTION_RESET

I've opened port 7890 like it says here https://github.com/allinurl/goaccess/issues/1100 but still nothing.

hm... from reading other issues in this queue, I see I need to supply SSL keys.

I had no idea making goaccess work with SSL and behind a Varnish cache would be so hard!

Still struggling with WebSocket connection to 'wss://DOMAIN:7890/' failed: Error in connection establishment: net::ERR_CONNECTION_RESET.
I now have goaccess on the same domain as the frontend, I feed it the SSL key and cert and still nothing.
Initial changes in Varnish for websocket don't seem to work.

I ended up using Goaccess on a standalone server with Apache. I now get this error:
goaccess: unrecognized option '--ssl-key
although I installed libssl-dev on Ubuntu and configured '--with-openssl'.
Funny thing is when I run the command directly in the CLI it works but if I set it as a service in /etc/systemd/system it throws the above error.

It seems there is a lingering goaccess v1.0.2 somewhere. That's the version being called from systemd, although I installed 1.4, confirmed by goaccess -V.
I can't find where it comes from.

How did you find out that it's running v1.0.2?

From /var/log/syslog

When I run the following command from CLI, everything works and I can access the URL with the realtime report:
ssh USER@HOST "tail -f /var/log/sites/joccom/logs/web-2917/access.log" | /usr/local/bin/goaccess --log-format=COMBINED --ssl-cert /SSLPATH/cert.pem --ssl-key /SSLPATH/privkey.pem -o /var/www/html/goaccess.html --keep-last=90 --with-output-resolver --geoip-database=/root/geolite2-city/GeoLite2-City.mmdb --real-time-html -
When I use the exact same command in goaccess.service in ExecStart, it says:
/etc/systemd/system/goaccess.service:11: Executable path is not absolute: ssh...
I go in and fix that by changing 'ssh' to '/usr/bin/ssh' and now it complains about SSL:
goaccess: unrecognized option '--ssl-cert'

How on earth can '--ssl-cert' be unrecognized?

I finally used sshfs and all works now!

This should be fixed. Please update to v1.4.2. Should work with:
ssh -n root@server 'tail -f /var/log/apache2/access.log' | goaccess - --log-format=COMBINED

Note, SSH requires -n so GoAccess can read from stdin.
Closing this. Feel free to reopen it if needed.


Mostly cleanup, adding focus outline

Mostly cleaning up CSS.
Adding a focus outline like so:
*:focus{
    outline: 2px dotted black !important;
    z-index: 1000;
}

TODO:

[ ] Need to make sure the blocklySVG doesn't capture focus
[ ] Need to make sure the search field doesn't capture tabs

@veler this should help resolve some of these button focus bugs.

The current changes looks good to me. But in the TODO, why do you want to make sure the search field doesn't capture tabs ?


permissions: not working on not logged users

I've added several tests for invenio-access, particularly for actions with arguments, and for not logged users.
Globally, we should have the following:
parameterized actions
Imagine you have 2 users: user1 and user2, and 2 actions: action1 and action2.
You have the following actions users table:

id
user
action
parameter

1

action1

2
user1
action1
p1

3
user1
action2

4
user2
action2
p1

The action1 and all its children (action1 with any parameters) will be accessible by anybody because of the first rule.
The second rule says that only user1 can access to the action1, but it is useless because of the rule 1.
The third rule says that only user1 can access to action2.
Finally, the last rule says that user2 can access to action2 with p1 parameter.

To summarize, user1 can access everything.
user2 can only action1 and action1 with any parameters. He can also access to action2 but only with parameter p1
Finally, a not-logged user will be able to access action1, but that's all.
The problem I actually have is the overriden rules explained in rules 1 and 2. Actually the test fails at line 131 (the only assert that fails), while this should pass.
See the comments for more details.

Is there a command to rerun Travis ?

You should be able to re-run the travis build since you have write access. Or simply close/open the PR. However, this branch has conflicts that must be resolved.

the tests will never pass on this branch as it is its purpose: to show a problem in the current invenio-access module. See it as a test case. This PR doesn't provide any solution to fix the issue.
I can rebase though, I'll do it when I'll have a bit of time

I've updated to the last version, it still crashes at the same point ;)

New version, fixes the main problem with no users:

it is now impossible to create an action with no users. THUS, it is no longer possible to allow or deny all users from an action.
in the future, we may have to create new explicit groups like "anyusers"

Merged in https://github.com/inveniosoftware/invenio-access/tree/feature-refactor


Uncaught TypeError: Cannot read property '2' of undefined

[Enter steps to reproduce:]

...
...

Atom: 1.19.2 x64
Electron: 1.6.9
OS: Microsoft Windows 7 Enterprise
Thrown From: autocomplete-wordpress-hooks package 0.2.2
Stack Trace
Uncaught TypeError: Cannot read property '2' of undefined
At C:\Users\a636861\.atom\packages\autocomplete-wordpress-hooks\lib\provider.js:111

TypeError: Cannot read property '2' of undefined
    at Object.isInFilter (/packages/autocomplete-wordpress-hooks/lib/provider.js:111:41)
    at Object.getSuggestions (/packages/autocomplete-wordpress-hooks/lib/provider.js:37:13)
    at C:/Atom Windows/Atom x64/resources/app/node_modules/autocomplete-plus/lib/autocomplete-manager.js:337:60
    at Array.forEach (native)
    at AutocompleteManager.getSuggestionsFromProviders (C:/Atom Windows/Atom x64/resources/app/node_modules/autocomplete-plus/lib/autocomplete-manager.js:313:23)
    at AutocompleteManager.findSuggestions (C:/Atom Windows/Atom x64/resources/app/node_modules/autocomplete-plus/lib/autocomplete-manager.js:302:25)

Commands

Non-Core Packages
atom-wordpress 0.3.0
autocomplete-wordpress-hooks 0.2.2

Fixed in v0.2.3


pull request for e2e test at 11/10/2016 15:15:09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

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


SetUserAgent Support

Allow user to set custom User-Agent

@MikeYeager to tracking visitor informations. and use injected functions from web pages when open from inner webview.

Great. Thank you @kinosang. This is something we can probably do, but will have to do for each of the 3 browser controls used on the 3 OSs. It would be great if someone from the community could help us out with this.

@kinosang This can be set with the new SetUserAgent() method during PhotinoWindow startup in v2.5.0:
        PhotinoWindow window = new PhotinoWindow()
            .SetTitle("Photino Testing")
            .SetUserAgent("Photino Testing")
            /// more options ...
            .LoadRawString("Hello World!");


Update test-file-05.md

@adunndevster : Thanks for your contribution! The author, @davidmu1, has been notified to review your proposed change.


translate to japanese

PR into Azure/azureml-cheatsheets
Checklist
I have:

[ ] read and followed the contributing guidelines

Changes

fixes #

@konabuta lgtm


RNGoogleSignin.configure error

Im getting this error undefined is not an object (evaluating 'RNGoogleSignin.configure'), anyone here encountered this error?

I am seeing this same thing. Have yet to get passed it.

Did you run react-native link?

@Kerumen I already link react-native-vector-icons

What is your platform?

@Kerumen right now IOS

Yes, I did use react-native link. Also on IOS

react-native run-android/IOS  and then
react-native link

@ahmadahmadi14 Tried that, still the same thing. Even tried unlinking and linking again while ios sim was running. Maybe this is a different error now, but still seeing:

Any update on this? Is there a way that I can check for RNGoogleSignin within my project? Or place it there manually?

Stupid question maybe but did you restart the packager and the simulator after react-native link ?

Yes, I have.
Also, as a note, I receive the following when trying to link again:

I have also tried deleting the build folder and re-running and linking.

What's your React Native version?

react-native: 0.42.0
react-native-cli: 2.0.1

I don't understand..
Did you drag & drop the GoogleSdk folder in your project?
Try to install it with CocoaPods?

I just saw the other install setup/guide stuff (thought install included just the first steps there). Its seems like that is it.
Although, when I try to follow instructions and run pod 'Google/SignIn', I see:

Trying the manual copy right now.

I just clarified this part. You have to add pod 'Google/SignIn' in your Podfile and then run pod install.
But wait, you didn't follow the installation guide before?

I did. I just followed the manual section again to be sure I didn't miss something there.
Adding a podfile now and trying that, but to confirm, redoing manual setup did not change anything.

I added the podfile with pod 'Google/SignIn and tried deleting build folder, re-running and re-linking. No change.

I'm out of ideas. Can you try to run the example project in the repo? It's based on RN 0.42 and the latest library version and it's working on my computer.

Yeah, the example project runs fine for me. I will just start from there, not sure what the difference is.
Thanks for the help.

@prescottprue if your problem solved? please let me know, i am having same issue

@noumanDev we updated our example up please check it out and see if it solves your problem.
Feel free to open a new issue if this problem persists.

@AndreiCalazans thanks alot, finally someone came to solve this issue, library was dead, will try it soon.

i am having the same issue i installed the pod through cocoa pod followed the guide correctly but i ma still getting this error can anybody help?

Hi Everybody I was having the same issue which just got resolved.
My react-native version is 0.50.4
react-natve-google-sign-in version is 0.12.0
I followed this link only automatic linking not mannual
https://github.com/react-native-community/react-native-google-signin/blob/master/ios-guide.md
and one more change in
node_modules/react-native-google-signin/src/
replace the below constants
GoogleSigninButton.Size = {
Icon: RNGoogleSignin.BUTTON_SIZE_ICON,
Standard: RNGoogleSignin.BUTTON_SIZE_STANDARD,
Wide: RNGoogleSignin.BUTTON_SIZE_WIDE
};
GoogleSigninButton.Color = {
Auto: RNGoogleSignin.BUTTON_COLOR_AUTO,
Light: RNGoogleSignin.BUTTON_COLOR_LIGHT,
Dark: RNGoogleSignin.BUTTON_COLOR_DARK
};
with
GoogleSigninButton.Size = {
Icon: '48 x 48',
Standard: '230 x 48',
Wide: '312 x 48'
};
GoogleSigninButton.Color = {
Auto: 'white',
Light: 'blue',
Dark: 'grey'
};

I solved with pod install but when I wrote pod install I got error about versions and I wrote pod update RNGooglesignin (check yourself I might have written wrong ) and then I wrote pod install and solve.  thanks @Kerumen

GoogleSignin.hasPlayServices({ autoResolve: true, showPlayServicesUpdateDialog: true  })


⚠ PrivateHD has degraded performance

In 59e7cd6, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2314 ms

Resolved: PrivateHD performance has improved in fd4bb63 after 6 minutes.


Using quick tiles doesn't work and crashes app

Good morning, if I try to add any of the quick tiles, the app crashes. If I try to tap on any of the quick tiles, either nothing happens or the app crashes. If I click and hold, the app crashes. I'm using the google pixel 6 pro and I'm on the latest Android update. Thank you

Hi,
I'm sorry to hear that. To dive further into why that happens, could you please copy the device info and paste it here? (You can find it inside the app by clicking on the info icon at the top right and clicking "Copy device info".
Furthermore please tell me if you are running the stock pixel Android or if you are using a custom OS.

App Version: 2.3.3 (25)
App Build Type: release
App Installer: org.fdroid.fdroid
Software: Android 14 (34)
Light Levels: 45
Manufacturer: Google
Brand: google
Model: Pixel 6 Pro
Device: raven
Board: google
Supported ABIs: arm64-v8a,armeabi-v7a,armeabi
I'm using the stock pixel Android

That's weird.
Have you tried reinstalling the app?
That solved problems for some users.

Yes, I have tried reinstalling. I have tried installing from playstore and
github but they both have the same bug. The app itself works fine except
for when it comes to using quick tiles.
On Tue, Apr 30, 2024, 4:33 AM Niko Diamadis @.***>
wrote:

That's weird.
Have you tried reinstalling the app?
That solved problems for some users.
—
Reply to this email directly, view it on GitHub
https://github.com/cyb3rko/flashdim/issues/66#issuecomment-2084830738,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2S2ICTU26JSZESKPKQHW53Y75QPPAVCNFSM6AAAAABG66QH7WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBUHAZTANZTHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


[test] Fix test broken by collision of recent changes

Two interacting changes were accidentally tested independently instead
of together and this got missed.

@swift-ci please test


Add shortening strategy based on package.json name

Finally got around to re-implementing #140 without using the jq tool, and against the current next branch so it can be pulled in easily.
I'm happy to pull the comments out if you'd prefer; I just left them in now because they were in my original implementation.

Unrelated: it seems like the prompt loads a bit more slowly than the version I was using before (which you can find here).  Have you noticed this too?

Cool thing!
About the speed issues:
The theme got a lot more complex since then. We split it up into several files, added the joining segments mechanism, etc.. Another reason could be the rework of the rbenv segment (it now invokes rbenv instead of checking an environment variable).

Ahh, I see. I did have to change to the rbenv segment instead of the more-generic ruby_version one.  I'll see if disabling that makes a considerable difference.

Yep. Unfortunately, rbenv does quite a bit on discovering the ruby version (like going up all directories to search for special files, etc.). See #216 for more infos about that.

Thanks :) Any feedback on the PR?

Looks good and works fine :+1: . I tested this under plain ZSH, Antigen and on OSX.
Only thing is, that the structure of the whole dir segment isn't the best at the moment, and I think we should do a cleanup-PR in the future for that. What I mean by this is that a user has to set POWERLEVEL9K_SHORTEN_STRATEGY (whyever this variable does not contain the segments name) and POWERLEVEL9K_SHORTEN_DIR_LENGTH even though this variable is never used by the new truncate_with_package_name. But as said, I think this is something for a future PR..
Or on second thought:
Wouldn't it be nice to use the POWERLEVEL9K_SHORTEN_DIR_LENGTH to do the same as truncate_from_right? So the segment would always show the package name and a path (if variable is set to zero, then show full path)..
In this case, it wouldn't be so confusing that you are required to set an unused variable..

Thanks for testing it out!

Wouldn't it be nice to use the POWERLEVEL9K_SHORTEN_DIR_LENGTH to do the same as truncate_from_right?

I'm not sure what you mean, but that's probably because I'm just not 100% up-to-date on how the configuration works right now.

Okay. I'll try to explain more thoroughly.
The dir segment offers different ways of truncate long directory names. One shortens from the right side, one from left, and one from the middle (they are not very consistent in how the do that, but that's another story).
You added truncate_with_package_name, which is kind of truncation. Kind of, because it replaces the first part of the path, but does nothing if you are in a deep subfolder. So you don't use the mandatory variable POWERLEVEL9K_SHORTEN_DIR_LENGTH, wich makes it necessary to either refactor the segment, or to make use of that variable..
This is what I suggest: truncate the right part (subfolder part) like the truncate_from_right strategy. If  POWERLEVEL9K_SHORTEN_DIR_LENGTH is not set, do no truncation.
This way we get a path like this (assuming we are in ~/test/1/12/123/1234/12345/123456, and SHORTEN_DIR_LENGTH is set to 2, and there is a package.json in ~/test with name "XX"): XX/1/12/12…/12…/12…/123456.
I hope that made it clearer what I meant. :wink:

Ahh, okay! I can do that. I wrote this change a long time ago -- originally for Agnoster, ported it to Powerlevel before I even knew about shortening strategies (maybe before the were implemented?) and eventually ported that to a real strategy, as seen in this PR.
Your recommendation makes perfect sense, I'll update this PR!

Alright, so I factored the sed operation to shorten the path out into a function, and apply that to the path after the package.json name.  If POWERLEVEL9K_SHORTEN_DIR_LENGTH is true then it keeps the same behavior as before; if it is a number, it will shorten each segment in the path to that amount of characters plus the ....

@alexlafroscia - Thanks so much for coming back to this! It looks like a really cool feature.
Do we need to make any adjustments to the README regarding the settings for truncation as part of this merge?
@dritter - Do the CI tests for this test the three different truncation strategies? Might be good to make sure we are doing that, at this point, since this code is fairly complex.

Oh, I totally forgot to update the README.  I'll add that in.

@alexlafroscia - Sorry it's taken me a while to get back to this - I've been traveling for the last few weeks, and am just now catching up.
Your update to the README looks good, and the change overall is a fantastic contribution. Thanks so much for taking the time to put this together. I'm excited it's going upstream =)

I am too!


Update package dependencies, deprecate --package-root.

package-root specification has been removed in the upstream coverage package, deprecate it here as well.

Note that I have also prepared a migration for null safety which I will send in a separate PR, which builds on top of this change.


Continual wake word detection

Make sure you have read the documentation, and have put forth a reasonable effort to find an existing answer.
Expected behaviour
i expected it to detect the wake word when audio input corresponding to the wake word was recorded
Actual behaviour
it continually detects the wake word even in silence
Steps to reproduce the behaviour
setup basic demo python script on raspberry pi running ubntu, usb mic works and records fine, audio files recorded in response to wake word detection play fine and sound fine.
`def wake_word_detected():
print("Wake word detected. Recording audio...")
audio_data = record_audio(10)
save_audio(audio_data, "audio.wav")
transcribe_audio("audio.wav")
time.sleep(5)
if name == "main":
porcupine = pvporcupine.create(access_key="+egBfj3x6kVryxbMrFIPNF0BC1bNFbkGLnYzRAVE/ppqGx7kW5aoBQ==",keywords=['porcupine'], )
samplerate = porcupine.sample_rate
num_channels = 1
print("Listening for wake word 'Porcupine'...")

with sd.InputStream(samplerate=samplerate, channels=num_channels) as stream:
    while True:
        audio_chunk, overflowed = stream.read(porcupine.frame_length)
        audio_chunk = (audio_chunk * 32767).astype(np.int16).flatten()
        if porcupine.process(audio_chunk):
            wake_word_detected()

`
my output looks like this:
Recording complete. Wake word detected. Recording audio... Recording... Recording complete. Wake word detected. Recording audio... Recording... Recording complete. Wake word detected. Recording audio... Recording... Recording complete. Wake word detected. Recording audio... Recording... Recording complete. Wake word detected. Recording audio... Recording... Recording complete. Wake word detected. Recording audio... Recording... Recording complete. Wake word detected. Recording audio... Recording... Recording complete. Wake word detected. Recording audio... Recording... Recording complete. Wake word detected. Recording audio... Recording... Recording complete. Wake word detected. Recording audio... Recording... Recording complete. Wake word detected. Recording audio... Recording... Recording complete. Wake word detected. Recording audio... Recording... Recording complete.
this occurs regardless of which wake word i try to use or whether i lower the sensitivity

Double-check your loop. This forum is only for issues with Picovoice's SDK and Picovoice's official demo.


Homebrew: does zsh completions work?

I have installed kubectx with brew install kubectx but I can't see any completion suggestions.
How to check if it was installed correctly?
Thank you.

It doesn't work for me either.

Works for me just fine on my oh-my-zsh.
Does adding this to your .zshrc solve the problem:
autoload -U compinit && compinit

Thanks @ahmetb this worked for me.

adding
autoload -U compinit && compinit
after source $ZSH/oh-my-zsh.sh
solve this issue also for me.
thanks


Simplify installation instructions.

No longer suggest virtualenv --system-site-packages as default,
but let NeuroM install all dependencies into clean virtualenv.
Mention --system-site-packages as an alternative, allowing to use
system-wide packages.

Increase version to 1.1.1.

@liesbethvanherpe FYI.


Handle validations for numeric variables with ranges and missing codes

New validation system in place is not currently handling this case.

This was fixed in commit 03d6a4d24a4c8f17d0215621b1602fafb25f0f9d


Documentation of supported marker APIs/extensions would be great

Description
In https://www.elopezr.com/a-macro-view-of-nanite/ I noticed the author's renderdoc screenshot contained some really cool annotations that I didn't realize renderdoc was even capable of capturing. I dug around in the documentation (in-application API, etc) and couldn't find any clues to how I would feed the relevant data through:

It would be great if the docs had a brief section listing which APIs/extensions are supported for the various backends so that an app developer can then read the docs for the relevant APIs/extensions and integrate them into their renderer. I could always go through and read UE5's direct3d renderer, I guess :-)
Environment
Not applicable

These markers are available through API standard marker methods, which are documented in those particular APIs. I should support all available marker methods (some APIs have more variants than others but I think all of them have more than one).
There's also a section calling them out in RenderDoc's documentation.
FYI in future please fill out the environment section for all issues including feature requests, as it gives context that can be useful such as the OS and graphics API that you're using.

Would you accept a PR to add a link or call-out for that section under "how do i" or "in application API"? I checked a bunch of places, so making it visible somewhere other than the event window docs could be good, and a "see here" hyperlink would do the trick
On June 1, 2021 1:43:04 AM PDT, Baldur Karlsson @.***> wrote:

Closed #2285.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/baldurk/renderdoc/issues/2285#event-4823954330

kg (mobile)

I wouldn't want it to be listed/linked from the in-application API page, because that's describing RenderDoc 's API and I think it's important to keep a distinction there. Maybe it could be linked from a "how do I" page but I'm not sure which one you'd want to link it from? I'm not opposed to making changes but I just want to make sure links are only added where they make sense and there's sufficient value, to avoid adding lots of intra-links everywhere which I find makes it hard to navigate.
FYI it's the first result for searching "annotations" currently.

I guess it's user error then, i only read that "how do i" entry and didn't use the search box. Thanks
On June 1, 2021 3:24:47 AM PDT, Baldur Karlsson @.***> wrote:

I wouldn't want it to be listed/linked from the in-application API
page, because that's describing RenderDoc 's API and I think it's
important to keep a distinction there. Maybe it could be linked from a
"how do I" page but I'm not sure which one you'd want to link it from?
I'm not opposed to making changes but I just want to make sure links
are only added where they make sense and there's sufficient value, to
avoid adding lots of intra-links everywhere which I find makes it hard
to navigate.
FYI it's the first result for searching
"annotations"
currently.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/baldurk/renderdoc/issues/2285#issuecomment-852012134

kg (mobile)

Which "how do I" did you read? Those are intended to be sort of user stories/worked examples of high level tasks rather than feature reference, which is why my mind didn't go to them necessarily. Though in principle almost anything could fit that template.
I'll still look at this and see if it could be made clearer, but indeed I'm not sure yet that anything needs to change.

Which "how do I" did you read? Those are intended to be sort of user stories/worked examples of high level tasks rather than feature reference, which is why my mind didn't go to them necessarily. Though in principle almost anything could fit that template.
I'll still look at this and see if it could be made clearer, but indeed I'm not sure yet that anything needs to change.

I read "How do I annotate a capture?", which you can see is result #2 in the search. I would have expected it to also mention the supported APIs (a hyperlink to the relevant page would be sufficient) since that's the other way to annotate a capture. Knowing about the search, it's not unreasonable to expect someone to use it, but I started by looking at the "how do I" and then figured that was all there was.
I'm already using glStringMarker and some of the D3DPERF APIs, so I figured I was perhaps expected to just figure it out (I knew vulkan had an API for this).
FWIW I omitted environment because I support all backends, so I need to know about all of them - not necessarily looking for platform-focused guidance or a 'here's how you do it' so much as just 'these are the extensions or APIs renderdoc supports', since some tracing tools only support a subset of them. I assume renderdoc supports most or all of them, though :-)

Oh yeh now that I look at it with fresh eyes that is definitely ambiguous :/. It was supposed to be about the ways that you could annotate a capture after making it, which is why I didn't mention the markers an application can emit or the ways of setting resource names from your code. Annotation is kind of an overload term (overloaded terms in graphics? who'd have thought).
And yeh indeed if there's a marker method I don't support then that's a bug :). Since as much as possible I want things to Just Work:tm:. The reason I asked for the environment to always be listed in feature requests is because it's better to list it up front even if it doesn't end up being useful, rather than omitting it and then having to ask. It's totally fine to list multiple APIs or OSs for a case like this.

That commit moves the capture-time annotation (marker regions and object names via graphics API calls) out of the other pages and into the "how do I annotate a capture" page so that it's all together. That was definitely a bit of an unintentional trap since I added the replay time annotation in much later, and didn't go back and adjust the other docs :/.


Build errors

laptop:/tmp/dmonitord$ ./mk.sh
Build for bin/dmonitord
src/whois.go:8:2: cannot find package "github.com/domainr/whois" in any of:
	/usr/lib/go-1.7/src/github.com/domainr/whois (from $GOROOT)
	/opt/dmonitord/src/github.com/domainr/whois (from $GOPATH)
	/tmp/dmonitord/src/github.com/domainr/whois
src/database.go:4:2: cannot find package "github.com/forease/ebase" in any of:
	/usr/lib/go-1.7/src/github.com/forease/ebase (from $GOROOT)
	/opt/dmonitord/src/github.com/forease/ebase (from $GOPATH)
	/tmp/dmonitord/src/github.com/forease/ebase

you need run below command:
go get github.com/domainr/whois
go get github.com/forease/ebase


[Mutant Year Zero] Dark mode adjustment

Adjustment of font colors to accommodate for dark mode.

@NicholasR77 This PR was merged 7 days ago but still does not show up in the games. This version is 0.1.12 but the latest in API Scripts is the previous version, 0.1.11.
Although the script still works, the dark mode changes has made the text quite difficult to read, especially on smaller screens.


[tests] tweaking some unit test to speed up local tests/ci

to: @jacknagz, @mime-frame
cc: @airbnb/streamalert-maintainers
size: small
resolves N/A
Background
Unit tests are getting very slow and take 86+ seconds to run
Changes

Patching the amount of retries for backoff for firehose and sending max_tries=1 to athena get_messages.
These changes bring unit test runs down from 86+ seconds to 3.2 seconds

Testing
Unit tests pass.

Coverage decreased (-0.05%) to 95.109% when pulling d8ca5dbcba9dff0863b3f4833ee5085f07cfe461 on ryandeivert-unit-test-improvements into 0f013daf4d7972bd6ab48df1a7a5c62b84148cc8 on master.

Coverage decreased (-0.05%) to 95.109% when pulling 7f51de86b440d79da384bdb64cdd6495d3fabad8 on ryandeivert-unit-test-improvements into 0f013daf4d7972bd6ab48df1a7a5c62b84148cc8 on master.


Handle Refund event

Hi, thanks for this package!
Just want to know how to handle when user make a refund.
 StreamSubscription _purchaseUpdatedSubscription = FlutterInappPurchase.purchaseUpdated.listen((productItem) {
    removeAds = true;
   Pref.saveData();
  });

When users have succesfully buy the product, It save in preferences local data. But when they refund, all money is back and they got removeAds to true already! I want also make removeAds to false when they refunded. Can anyone explain please?

Try this solution in react-native-iap.

Hi @mliitfall ,
for checking that if a user has refunded an in app purchase, you could set a function to be called upon app startup once in a day, that verifies that of the purchase for you. Moreover, if your app connects with your own server while using the app, you could set up real time developer notifications in your server via the play apis which will report your server when a user refunds a purchase or cancels a subscription.
if you have a consumable product, you could verify details like consumption details, purchase state after querying previous purchases from the following statement.
List<PurchasedItem> items =
          await FlutterInappPurchase.instance.getAvailablePurchases();

more reference here - https://developer.android.com/google/play/billing/realtime_developer_notifications
https://developers.google.com/android-publisher/api-ref/purchases/products
https://developers.google.com/android-publisher/api-ref/purchases/subscriptions


feat: add ensure-custom-hooks-using-other-hooks

fix #1
This is my first time trying to write custom eslint rules and I'm not quite sure if the way to go about it is appropriate. If you find some tests that don't pass, you can add them and I'll try to fix them.

Glad to see you're trying to implement this, but I need to be sure of the proper way to do it first, and when I'm done with debug/hooks, I'll see if we should use.

I will check and learn from that PR first.

I will check and learn from that PR first.

Minor updates, see https://github.com/eslint-react/eslint-react/commit/8cd3f526503f1f9bf8b86a615dc74b20a5810f7c

I've updated the hooks-collector implementation to support more complex cases, such as nested hooks.


lots of errors with gstreamer repo

Getting lots of error when opening the gstreamer mono-repo. I've been told by @xclaesse it's related to the new language server feature.

Changing this setting removes those errors:

cc @JCWasmx86

Given what you said, I don't really see a reason to change anything. Sounds like gstreamer might need to update some subprojects.

@JCWasmx86 not sure if you noticed the typo in the errors above: No method has found

Oh, guess I read that message wrong.

Yeah that looks like a gstreamer bug again.

Closing this. Thanks @JCWasmx86


Implemented custom scrollToHandler.

Haven't got a test for this. Had a bit of trouble testing the scroll position. Any thoughts on the best way to do this?

@craigsketchley I think you should be able to check scrollTop to find the scroll position. What have you tried so far?

@craigsketchley want me to give testing a go?

Hey, yeah, happy for you to have a go. I think I'm close but I'm having trouble finding a way to set the viewport size for testing. Checking if the window has scrolled to the current step element requires that some of the page is out of view. Currently when running the tests the window height and document height are the same so no scrolling occurs :(

Just pushed where I'm at so you can see my thought process.

I did see that you can specify the viewport size in PhantomJS. Any idea if we can use that?

@craigsketchley There is currently a bug that makes Phantom not work. I'll see if I can get it working with Chrome this weekend.

@craigsketchley I think the problem here is document and window and such are not necessarily just the app, they include the qunit container page, and the real container is #ember-testing-container. I just changed the tests to check that scroll is initially 0 and then > 0 after the scrollTo, which means scrolling worked. Are you good with that test? I committed it to your PR branch.

Yeah nice work. That makes sense. Your commit looks good to me.

@craigsketchley got it all merged in, published version 2.0.5. Is there anything we need to document in README.md?

@rwwagner90 I don't think we need to document anything. Just a fix.