[CARBONDATA-3783]Alter table drop column on main table is not dropping the eligible secondary index tables

Why is this PR needed?
Alter table drop column on main table when droping columns match to a secondary index table columns is actually not dropping secondary index table.
What changes were proposed in this PR?

Have corrected the dropApplicableSITables to check if the drop columns are matching the index table columns. If all columns of a index table match to drop columns, then drop the index table itself.
Index table refresh was missed in CarbonCreateSecondaryIndexCommand. It was missed in secondary index feature PR.

Does this PR introduce any user interface change?

No

Is any new testcase added?

Yes

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1113/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2826/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2827/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1114/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2829/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1116/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1143/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2856/

@VenuReddy2103 please fix the test cases

retest this please

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2864/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1150/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1152/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2867/

LGTM


Allow for comparisons of objects across heap snapshots and allocation traces

In order for users to get a better understanding of where and when memory is being consumed within their Dart applications, it is necessary to provide a way for tooling to compare objects in the heap at various points during runtime that makes it possible to determine which objects from different snapshots are the same. The current heap snapshot format does not allow for this capability as there is no concept of a stable object ID currently reported for each object.
The following functionality should be added to the heap snapshot format and the service protocol:

[x] Identity hash codes for non-core objects in the heap snapshot
[ ] Identity hash codes should be associated with each allocation of tracked types

First change landed in this CL.

Second changed landed in this CL.


Bring window to foreground

Activating a tab does activate it, but it will leave the window in the background if that's where it was.  While there might be a case for that, it seems more likely that the window should be brought to the foreground.  As an alternative, maybe this could be a separate command.
Bonus points if it can also switch desktop spaces on Mac OSX.

I'll second that.  Would also be nice to have an option to return to the terminal running the script that called chrome-cli, although one can fake that in a script with "open -a Terminal" following the chrome-cli call.
BTW, Thanks for this very useful and well-documented app!


Fix In Batch File

Getting PHP Warning: Declaration of Cassandra\Request\Batch::queryParameters($consistency, array $options = Array) should be compatible with Cassandra\Request\Request::queryParameters($consistency, array $values = Array, array $options = Array) in /var/www/html/php-cassandra/src/Request/Batch.php on line 122 for PHP7

Fix for the following error
FatalErrorException in Exception.php line 4:
Class Cassandra\Response\Exception cannot extend from interface Cassandra\Exception

@pincher2012 - Sorry i have reverted that implements to extends as it is the class and i have done one more fix now for the following error,
FatalErrorException in Exception.php line 4:
Class Cassandra\Response\Exception cannot extend from interface Cassandra\Exception

File - src\Response\Error.php
Line - 126
return new Exception($data['message'], $data['code']);
To
return new \Exception($data['message'], $data['code']);


API Documentation and simple example usage guide

this project is looks good but there is no api documentation so its hard to figure out everything , so it would be nice that we have documentation and simple usage guide both in swift and ios.
thanks you for  this awesome library.

Thanks! There is an example project which contains both obj-c and swift sample code. Is that helpful?


[DO-NOT-MERGE][SPARK-47047][SS] Add changes to support reading transformWithState value state variables

What changes were proposed in this pull request?
Add changes to support reading transformWithState value state variables
Why are the changes needed?
Adds support for reading state written by value state variables used within the transformWithState operator
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added unit tests
Was this patch authored or co-authored using generative AI tooling?
No

Will cover the changes as part of Jing's PR


docs_serve Makefile task limits jenkyll server to local access

When you use a container as your Jekyll server you might face some troubles reaching the application, since it denies any access other than local.
I've run a container with the following command:
sudo docker run -p 4000:4000 -v /home/fb/code/nbdev:/home -id -d ubuntu:20.04

Then I've run make:
make nbdev_build_docs

In the host machine I could not manage to browse the url http://localhost:4000
To solve this issue, I just change the line 15, adding host parameter like this:
 cd docs && bundle exec jekyll serve --host <IP_ADDRESS>

The makefile is meant for local debugging.  If you are trying to run a Docker application we have this docker compose file in this repo that configures the host as you mention.
I'm not sure there is something that should be changed?

Your concern makes sense to me, @hamelsmu! Let leave as it is.
Don't you think it deserves a mention in the troubleshooting section? I guess other devs might find it useful.
Thanks!


Scheduled cores Error ", all values of jobs will be affected"

In mclapply(argsList, FUN, mc.preschedule = preschedule, mc.set.seed = set.seed,  :
scheduled cores 1, 2, 3, 4 did not deliver results, all values of the jobs will be affected
I got the above error at the end of runnning robyn_outputs() function , it returns all the one pager reports etc. however the error saying values will be effected is not nice, i am not sure if this refers to the actual values on my plots and they are actually affected.
I cant share my data but the code so far is down below ,i tried assigning only one core in robyn outputs function however it didnt work, still tries to use all the cores , is there a way to specify number of cores during robyn_outputs()
colnames(df_weekly)[25] = "OtelEndeks"
InputCollect <- robyn_inputs(
  dt_input = df_weekly,
  #dt_holidays = dt_prophet_holidays,
  date_var = "index", # date format must be "2020-01-01"
  dep_var = "sales_amount", # there should be only one dependent variable
  dep_var_type = "conversion", # "revenue" (ROI) or "conversion" (CPA)
  prophet_vars = c("season","trend"), # "trend","season", "weekday" & "holiday"
  prophet_country = "DE", # input one country. dt_prophet_holidays includes 59 countries by default
  context_vars = c("OtelEndeks"), # e.g. competitors, discount, unemployment etc
  paid_media_spends = c("tv_cost", "sm_cost", "gads_video_cost", "gads_display_cost", "gads_search_cost","dv360_video_cost","dv360_display_cost","cm360_video_cost","cm360_display_cost"), # mandatory input
  paid_media_vars = c("tv_impression", "sm_impression", "gads_video_impression", "gads_display_impression", "gads_search_impression","dv360_video_impression","dv360_display_impression","cm360_video_impression","cm360_display_impression"),
  adstock = "weibull_pdf", # geometric, weibull_cdf or weibull_pdf.
)
print(InputCollect)

plot_adstock(plot = FALSE)
plot_saturation(plot = FALSE)

hyperparameters <- list(
  gads_search_cost_alphas = c(0.5, 3),
  gads_search_cost_gammas = c(0.3, 1),
  gads_search_cost_shapes = c(0.0001, 10),
  gads_search_cost_scales = c(0, 0.1),
  sm_cost_alphas = c(0.5, 3),
  sm_cost_gammas = c(0.3, 1),
  sm_cost_shapes = c(0.0001, 10),
  sm_cost_scales = c(0, 0.1),
  tv_cost_alphas = c(0.5, 3),
  tv_cost_gammas = c(0.3, 1),
  tv_cost_shapes = c(0.0001, 10),
  tv_cost_scales = c(0, 0.1),
  #total_video_cost_alphas = c(0.5, 3),
  #total_video_cost_gammas = c(0.3, 1),
  #total_video_cost_shapes = c(0.0001, 10),
  #total_video_cost_scales = c(0, 0.1),
  #total_display_cost_alphas = c(0.5, 3),
  #total_display_cost_gammas = c(0.3, 1),
  #total_display_cost_shapes = c(0.0001, 10),
  #total_display_cost_scales = c(0, 0.1),
  gads_display_cost_alphas = c(0.5, 3),
  gads_display_cost_gammas = c(0.3, 1),
  gads_display_cost_shapes = c(0.0001, 10),
  gads_display_cost_scales = c(0, 0.1),
  gads_video_cost_alphas = c(0.5, 3),
  gads_video_cost_gammas = c(0.3, 1),
  gads_video_cost_shapes = c(0.0001, 10),
  gads_video_cost_scales = c(0, 0.1),
  dv360_display_cost_alphas = c(0.5, 3),
  dv360_display_cost_gammas = c(0.3, 1),
  dv360_display_cost_shapes = c(0.0001, 10),
  dv360_display_cost_scales = c(0, 0.1),
  dv360_video_cost_alphas = c(0.5, 3),
  dv360_video_cost_gammas = c(0.3, 1),
  dv360_video_cost_shapes = c(0.0001, 10),
  dv360_video_cost_scales = c(0, 0.1),
  cm360_display_cost_alphas = c(0.5, 3),
  cm360_display_cost_gammas = c(0.3, 1),
  cm360_display_cost_shapes = c(0.0001, 10),
  cm360_display_cost_scales = c(0, 0.1),
  cm360_video_cost_alphas = c(0.5, 3),
  cm360_video_cost_gammas = c(0.3, 1),
  cm360_video_cost_shapes = c(0.0001, 10),
  cm360_video_cost_scales = c(0, 0.1),
  train_size = c(0.5, 0.8)

)

OutputModels <- robyn_run(
  InputCollect = InputCollect, # feed in all model specification
  cores = 12, # NULL defaults to max available - 1
  ts_validation = TRUE,
  iterations = 6000, # 2000 recommended for the dummy dataset with no calibration
  trials = 8, # 5 recommended for the dummy dataset
  #add_penalty_factor = FALSE, # Experimental feature. Use with caution.
  outputs = FALSE # outputs = FALSE disables direct model output - robyn_outputs()
)

print(OutputModels)

OutputModels$convergence$moo_distrb_plot
OutputModels$convergence$moo_cloud_plot

OutputCollect <- robyn_outputs(
  InputCollect, OutputModels,
  csv_out = "pareto", # "pareto", "all", or NULL (for none)
  clusters = TRUE, # Set to TRUE to cluster similar models by ROAS. See ?robyn_clusters
  plot_pareto = TRUE, # Set to FALSE to deactivate plotting and saving model one-pagers
  plot_folder = robyn_object, # path for plots export
  ts_validation = TRUE
  #export = TRUE # this will create files locally
)
print(OutputCollect)

library(foreach)
doFuture::registerDoFuture()
library(doRNG)
with this lines of codes , the warning does not appear anymore

Hi @MustafaCelen thanks for sharing.

(...) is there a way to specify number of cores during robyn_outputs()?
Yes. You could change the cores value in OutputModels manually: OutputModels$cores <- X.

We are not using doFuture' 'registerDoFuture' but doParallel's registerDoParallel though, which is triggered here.

I am still getting the error when I am trying to get many one pager reports, I dont use clusters and try to get all of the pareto front results(usually between 100-200), i think it is better for me to analyse the output csv and decide which ones to create then i ll just use the robyn_onepagers func to create them. But I think there is a problem with the memory usage , even with 144gb and 72core cpu its taking so long for outputs.

Are you saying you're outputting 100-200 pareto_fronts? That's a lot. If you turn off clustering, try starting with few fronts, like 3 or so. If you have lots of iterations, 3 fronts will already give you quite some candidates and these are the best

No , but i dont cluster my pareto front results , to clarify you can see how i use it. I am trying 10k iterations with 10 trials, i have 150 weeks of data with 8 media and 2-3 context vars. Do you think I should increase my iterations or trials or is this enough?
OutputCollect <- robyn_outputs(
InputCollect, OutputModels,
#pareto_fronts = 1, # automatically pick how many pareto-fronts to fill min_candidates
min_candidates = 100, # top pareto models for clustering. Default to 100
#calibration_constraint = 0.1, # range c(0.01, 0.1) & default at 0.1
csv_out = "pareto", # "pareto", "all", or NULL (for none)
clusters = FALSE, # Set to TRUE to cluster similar models by ROAS. See ?robyn_clusters
plot_pareto = TRUE, # Set to FALSE to deactivate plotting and saving model one-pagers
plot_folder = robyn_object, # path for plots export
#ts_validation = TRUE
export = TRUE # this will create files locally
)

Old ticket. Please reopen if necessary.


I-19

Disclaimer
This pull request mainly focuses on the front-end dependencies and endpoint/file naming conventions of the ideas soffit. Some functionality still might not work when deployed to uPortal, but that will be caught in future testing with appropriate issues being made when bugs are caught.
Highlights
This pull request focuses on a few key things:

API names have been brought in-line with current UTS standards
Endpoint error handling / logging has been improved
MUI has been upgraded to version ^3

Main elements of the UI work without crashing, more thorough testing to come later

Closes #19

@amgoodfellow in IdeaEditor.js, the way that the cursor looks when you first enter the description box looks a bit confusing. It might be better to add an outline to the description box.

Also, in the pop up dialog, it might be nice to add a close button to avoid further confusing and imrpove ease of use.

Here is the list of things that I thought could be altered in the future:

Move the + button to the top so that individuals with smaller screens do not have to scroll down to see the button
Add a header explaining the process and how to add a new idea. You could also put the + button in the header
Fix the upvote/downvote logic so the difference is 2 and you do not have to click it twice
Add the option to remove your vote by reclicking the same button


Fixes highlight feature bugs

HTM-260: Remove highlight on layer deactivation & closing feature info
HTM-261: Disable simplification for feature info geometry
HTM-263: Reset current selected index when loading new feature info
HTM-264: Fixed height for feature info and scroll if there is more info

Codecov Report

Merging #64 (627e682) into main (7f43dae) will decrease coverage by 0.20%.
The diff coverage is 22.22%.

@@            Coverage Diff             @@
##             main      #64      +/-   ##
==========================================
- Coverage   62.01%   61.80%   -0.21%
==========================================
  Files         107      107
  Lines        1969     1982      +13
  Branches      260      266       +6
==========================================
+ Hits         1221     1225       +4
- Misses        685      690       +5
- Partials       63       67       +4

Flag
Coverage Δ

unittests
61.80% <22.22%> (-0.21%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ure-info-dialog/feature-info-dialog.component.html
100.00% <ø> (ø)

...ib/components/feature-info/feature-info.service.ts
92.00% <ø> (ø)

...eature-info/feature-info/feature-info.component.ts
94.28% <ø> (ø)

...ponents/feature-info/state/feature-info.reducer.ts
90.47% <ø> (ø)

...nents/feature-info/state/feature-info.selectors.ts
46.15% <0.00%> (-6.03%)
:arrow_down:

projects/map/src/lib/map-service/map.service.ts
23.80% <0.00%> (-1.20%)
:arrow_down:

...ature-info-dialog/feature-info-dialog.component.ts
89.36% <100.00%> (+0.98%)
:arrow_up:

Continue to review full report at Codecov.

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


Feather Falling

@Vapok I see this is a fork of the original. Would you have any interest in adding a new feather falling backpack?!

That's a fun idea!  I'm currently trying to rebuild the Unity project for this mod, as I don't seem to have the Unity project.  So, I'd expect that it's gonna be a bit.
That being said:  This mod + EpicLoot... gives you the ability to do just that... Add Feather Fall, Weightless, Waterproof... to a backpack, if you wanted to check it out.

Once I can get to a spot where I can achieve this, I want to add in a Mistlands Bag that includes a Feather Fall attribute.

Once I can get to a spot where I can achieve this, I want to add in a Mistlands Bag that includes a Feather Fall attribute.

https://github.com/sbtoonz/BackPacks_Remake/tree/master/BackPack_UnityProject
The assets at least are in my remake of the backpacks project feel free to grab them Cinnabun gave open reigns to the 2x models she made and the other model was gifted by a guy named Debarba (dylan)


Add user to impersonate when signing in with Admin user token

Summary
In the REST API is documented that you can impersonate a user using token authentication:

Request Type
New Feature
Type 1: support a REST API:
Yes, this is a supported feature in REST API:
Signing in with server administrator's personal access token(Link opens in a new window) (PAT) to impersonate a user (not available for Tableau Cloud): https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_ref_authentication.htm#sign_in

Description
Currently, impersonate user is only available for username and password in tableau_auth.py, however it could be needed in other cases where username and password is not available.

Would be fixed by #1219


Feature: Link element in component's data to Elements

I have a component what will have HTMLElement in it's data:

Will be useful if it will be linked to Elements tab in Devtools, co I can inspect what specific element was pessed there.

"Inspect DOM" button you see near component name does that already.
Doesn't it work for you?

No, because it sends me to this component's element, not to element what is in data variable.
Jan Pobořil
http://honza.poboril.cz/

2017 v 15:06, Kasparas Pochyla<EMAIL_ADDRESS>

"Inspect DOM" button you see near component name does that already.
Doesn't it work for you?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


[Bug] 查询hudi mor表报错

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
2.0.3
What's Wrong?
I1219 17:41:26.307972 1226839 internal_service.cpp:521] cancel fragment, fragment_instance_id=e229ab07404240b9-9ed80d41e7cb0232, reason: INTERNAL_ERROR
I1219 17:41:26.307994 1226839 runtime_state.h:172] task is cancelled, st = [CANCELLED]
W1219 17:41:26.308001 1226839 pipeline_fragment_context.cpp:162] PipelineFragmentContext Canceled. reason=
W1219 17:41:26.308058 1225639 fragment_mgr.cpp:482] report error status: [CANCELLED] to coordinator: TNetworkAddress(hostname=<IP_ADDRESS>, port=9020), query id: e229ab07404240b9-9ed80d41e7cb0230, instance id: e229ab07404240b9-9ed80d41e7cb0232
W1219 17:41:26.308364 1225640 fragment_mgr.cpp:482] report error status: [CANCELLED][INTERNAL_ERROR]InternalError: null
    0#  doris::JniUtil::GetJniExceptionMsg(JNIEnv_*, bool, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) at /root/src/doris-2.0/be/src/util/jni-util.h:110
    1#  doris::vectorized::JniConnector::get_nex_block(doris::vectorized::Block*, unsigned long*, bool*) at /root/src/doris-2.0/be/src/vec/exec/jni_connector.cpp:0
    2#  doris::vectorized::HudiJniReader::get_next_block(doris::vectorized::Block*, unsigned long*, bool*) at /root/src/doris-2.0/be/src/common/status.h:442
    3#  doris::vectorized::VFileScanner::_get_block_impl(doris::RuntimeState*, doris::vectorized::Block*, bool*) at /root/src/doris-2.0/be/src/common/status.h:442
    4#  doris::vectorized::VScanner::get_block(doris::RuntimeState*, doris::vectorized::Block*, bool*) at /root/src/doris-2.0/be/src/vec/exec/scan/vscanner.cpp:0
    5#  doris::vectorized::ScannerScheduler::_scanner_scan(doris::vectorized::ScannerScheduler*, doris::vectorized::ScannerContext*, std::shared_ptr<doris::vectorized::VScanner>) at /root/src/doris-2.0/be/src/common/status.h:354
    6#  std::_Function_handler<void (),

查询hudi mor表时报错doris::vectorized::ScannerScheduler::_schedule_scanners(doris::vectorized::ScannerContext*)::$_1::operator()() const::{lambda()#4}>::_M_invoke(std::_Any_data const&) at /var/local/ldb-toolchain/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/bits/shared_ptr_base.h:701
7#  doris::WorkThreadPool::work_thread(int) at /var/local/ldb-toolchain/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/bits/atomic_base.h:646
8#  execute_native_thread_routine at /data/gcc-11.1.0/build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/unique_ptr.h:85
9#  start_thread
10# __clone
What You Expected?
..
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Could you clarify the reason for closing this issue as completed, please? @lucienoz


Call docChanges method according to TS definition

TypeScript warned me this error when chaining forEach after docChanges
Property 'forEach' does not exist on type '(options?: SnapshotListenOptions |
undefined) => DocumentChange<DocumentData>[]'.ts(2339)

So I look at the doc and see it's an method and by calling it fixed the ts error

@googlebot I signed it!

Thank you for finding this bug @bodazhao !


ADVANCED_MODULE

Python Advanced May 2022
Lists as Stacks and Queues

[x] Video
[x] LAB
[x] Video
[x] EXERCISES

Tuples and Sets

[x] Video
[x] LAB
[x] Video
[x] EXERCISES

Stacks, Queues, Tuples and Sets

[x] Video
[x] EXERCISES

Multidimensional Lists

[x] Video
[x] LAB
[ ] Video
[x] EXERCISES
[ ] Video
[x] EXERCISES

Functions Advanced

[x] Video
[x] LAB
[ ] Video
[x] EXERCISES

Error Handling

[x] Video
[x] Video
[x] Homework !!!

File Handling

[x] Video
[ ] Video
[x] Homework !!!

Workshop

[ ] Video
[ ] Workshop
[ ] Video
[ ] Workshop

Modules

[x] Video
[ ] LAB
[ ] Video
[ ] Exercise

Exam Prep
...

Python Advanced May 2022
Lists as Stacks and Queues

[ ] Video
[ ] LAB
[ ] Video
[ ] EXERCISES

Tuples and Sets

[ ] Video
[ ] LAB
[ ] Video
[ ] EXERCISES

Exam passed


gltf ，material loss，why

gltf + bin ，material lose，why？

Can you please share more information about your issue? @atlas1119 what model file(s) have you tried? What is the error you are getting?


Fix Typos and add keywords for arduino IDE syntax highlighting.

Hi Wolfgang,
I was reading through your code and you did and amazing job. Thanks. First library that I found that have non-blocking methods for the adc reading.
I know it would be best it I had done 2 different pull requests for the following changes, but I'm starting to use git and I am still confused with some differences and workflow from svn. If you think it's better, you can reject this pull and I will try to make them apart.
I added keywords.txt, as suggested on Arduino Library Tutorial so that the arduino IDE is now able to highlight the library public methods, defines and enums:

I also fixed some typos. The only disadvantaged is that I had to rename the continous.ino example file and folder.
Since the typo was present in one enumeration, I kept both enum names with the same value, for backwards compatibility:
typedef enum ADS1115_MEASURE_MODE{
	ADS1115_CONTINOUS  = 0x0000, // keeping misspelled enum for backwards compatibility.
	ADS1115_CONTINUOUS = 0x0000,
	ADS1115_SINGLE     = 0x0100
} measureMode;

It is also present in the keywords file, so that it can be highlighted too.
I think this covers all modifications in the pull request. Let me know what you think.

Hi Martin, great contribution. Thanks. And good idea to keep the ADS1115_CONTINOUS for backwards compatibility.


Resource tab is always redirecting to list view instead of user default view

Describe the bug
When a user clicks on Resource tab from sidebar , it's always redirected to list view instead of changing based on user's default
To Reproduce
Steps to reproduce the behavior:

Click on Resource tab
Change the view to board view
Now move to another tab and click on Resource tab again
See error
Similar issue is present with Shifting Tab too

Expected behavior
User default should change based on user latest preference
Screen Recording
https://github.com/user-attachments/assets/51a69fd4-a7e1-4967-9c5f-0d12a1f6a7f6
Desktop (please complete the following information):

OS: Windows
Browser : Chrome
Version : Latest

@Jacobjeevan @rithviknishad I'd like to work on this and raise an immediate PR


kpt pipeline run should check docker command is available on the system

kpt pipeline uses docker runtime for executing kpt functions. So we should ensure kpt is able to run docker command (may be run docker ps) before invoking kpt pipeline run command. If docker isn't available, we should present the user with a message saying docker is required to run this command and provide with links to docker installation page.

We should write this function in a way we can use this for kpt fn run as well.


Issue with LiveDemo when I logged in

Describe the bug
When I tried to log in to the live demo feature in the https://www.usememos.com/, it showed error "Cannot read properties of undefined (reading 'replace')".
Steps to reproduce

Go the https://www.usememos.com/
Use Live Demo Feature
Sign in with the default username and password that get populated.

The version of Memos you're using
Demo version
Screenshots or additional context

Thanks for your reporting. The demo site has been redeployed.


Error when using Webpack / Electron

I'm not really sure what's happening. It seems that there's something going on when Webpack tries to bundle my Electron app with the latest version of node-hue-api. Anyone have any ideas?
For context, I used the Electron React Boilerplate with Typescript.
https://github.com/electron-react-boilerplate/electron-react-boilerplate
> postinstall
> ts-node .erb/scripts/check-native-dep.js && electron-builder install-app-deps && cross-env NODE_ENV=development TS_NODE_TRANSPILE_ONLY=true webpack --config ./.erb/configs/webpack.config.renderer.dev.dll.ts && opencollective-postinstall

  • electron-builder  version=22.14.5
  • loaded configuration  file=package.json ("build" field)
  • installing production dependencies  platform=darwin arch=x64 appDir=/Users/chrisle/code/nowplaying2/release/app
ERROR in ./node_modules/node-hue-api/dist/esm/index.js 4:0-45
Module not found: Error: Can't resolve './api/discovery' in '/Users/chrisle/code/nowplaying2/node_modules/node-hue-api/dist/esm'
Did you mean 'index.js'?
BREAKING CHANGE: The request './api/discovery' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
 @ dll renderer renderer[26]

Well I at least tracked it down to the fact that the post-install was using webpack. My tsconfig modules was set to "commonjs" but for some reason, webpack was trying to use the ESM version in node-hue-api.
I don't know how to configure webpack to deal with TypeScript and CJS so my solution is to use the 4.x branch which is written in JavaScript instead of TypeScript.


When create jwt token inside loop getting same token

I am creating jwt tokens using jwt-go library. Later wrote a script to load test. I have noticed when I send the many concurrent request getting same token. To check more about this I created token inside for loop and result is same.
code as follows,
expirationTime := time.Now().Add(time.Duration(60) * time.Minute)

    for i := 1; i < 5; i++ {
        claims := &jwt.StandardClaims{
            ExpiresAt: expirationTime.Unix(),
            Issuer:"telescope",
        }
        _token := jwt.NewWithClaims(jwt.SigningMethodHS256, claims)
        var jwtKey = []byte("secret_key")
        auth_token, _ := _token.SignedString(jwtKey)
        fmt.Println(auth_token)
    }

I think you are using the same claims for tokens so you must get the same token. If you want to get different tokens, you can set IssueAt field in StandardClaims. However, consider waiting 1 second to generate a new token because Unix timestamp has 1-second accuracy.

yes that's why..


Fix lint error

Running vue server gave a lint error on this line

Can you show the error log? In the master branch, npm run lint shows no error to me Screenshot given below:

It's shown when the local server is started (yarn serve)

I had updated the dependencies and fixed the linting errors reported by latest version of formatters.
Now this patch is obsolele. Thanks


[el] Add sentences/test for homeassistant_HassGetState

This PR adds the missing el sentences and tests for homeassistant_HassGetState.
Btw I'm generally trying to be consistent with the current translations of state values. But I noticed that the on/off states for light entities are currently translated as:

on: Ενεργό
off: Ανενεργό

I don't think that anyone really says "το φως είναι ενεργό", the usual phrases are:

το φως είναι ανοικτό / κλειστό
το φως είναι αναμμένο / σβηστό

Maybe we can try to fix this? Should this change be done in lokalise?

Btw I'm generally trying to be consistent with the current translations of state values. But I noticed that the on/off states for light entities are currently translated as:

on: Ενεργό
off: Ανενεργό

I don't think that anyone really says "το φως είναι ενεργό", the usual phrases are:

το φως είναι ανοικτό / κλειστό
το φως είναι αναμμένο / σβηστό

Maybe we can try to fix this? Should this change be done in lokalise?

You are right. The "Ενεργό" and "Ανενεργό" states come from Lokalise, as the naming should be general enough to fit to other entities as well.  That is, the 'on' and 'off' states will be mapped to the your given 'ανοικτό / κλειστό' or 'αναμμένο / σβηστό' state examples, as the values (which are in English) -and not the keys- would be used in the backend for the intent actions.

You are right. The "Ενεργό" and "Ανενεργό" states come from Lokalise, as the naming should be general enough to fit to other entities as well.  That is, the 'on' and 'off' states will be mapped to the your given 'ανοικτό / κλειστό' or 'αναμμένο / σβηστό' state examples, as the values (which are in English) -and not the keys- would be used in the backend for the intent actions.

Indeed, I'm not worried about the intents, I just think that the translation for the state value of lights should probably be fixed.
I understand that "Ενεργό" is chosen as the generic term for arbitrary entities (makes sense), but there should be a way to specify that for light entities "on" should have a different translation, right?

I totally understand your point. Unfortunately, this is the way the translations of the words are published on Lokalise. That is, there is no way to have discrete entity-based status namings.

I totally understand your point. Unfortunately, this is the way the translations of the words are published on Lokalise. That is, there is currently no way to have discrete entity-based status namings.

After some tests I found that there are some languages for which light entities have different translation for "on" than generic entities. For instance, changing my language to danish (which I don't speak :smile: ), I get

"on" for lights: "Tændt"
"on" for several other entities: "Til"

So I started digging in Lokalise and found the following:

There is a key common::state::on which in english is translated as "On".

There are also lots of per-entity keys, for instance:

component::light::entity_component::_::state::on
component::switch::entity_component::_::state::on
component::fan::entity_component::_::state::on

In both english and greek (and many other languages), these keys have value [%key:common::state::on%], which I guess means that they link to the generic work for "on". This is why "on" for all entities is the same.

However in some languages the per-entity keys have a different translation! For instance in danish you have

common::state::on: "Til"
component::light::entity_component::_::state::on: "Tændt"

Explaining what I observed in my tests.

So I guess we can simply change the greek translation of component::light::entity_component::_::state::on to have lights shown as "Ανοικτό", right?
Should I try to change this in lokalise? I have no experience with it, are you also maintaining the greek translations there?

There is no Maintainer per Language in Lokalise, like here. Although, I am an active contributor there. Of course, your contribution will be really helpful there as well. In case I have some free time I will verify that and change it accordingly (if you have not done that by then).

Seems correct 👍


[zh] sync expose-external-ip-address.md

This is the 2nd file found via #37919
content/zh-cn/docs/tutorials/stateless-application/expose-external-ip-address.md

Preview: https://deploy-preview-37932--kubernetes-io-main-staging.netlify.app/zh-cn/docs/tutorials/stateless-application/expose-external-ip-address/

lgtm

/lgtm
/approve


feat: respect env variables

Overview
Resolves:
AI-1455
Checklist

[ ] I have run this code and it appears to resolve the stated issue
[ ] README.md updated and added information about my change

The migration is missing from the parameter to the env var. Can you try to implement that as well?


chore(*): remove kotlin-stdlib-jdk7 dependency

Starting in Kotlin 1.4.0, the kotlin-stdlib is added by default. So we no longer need it on our build.gradle files.

@rosariopfernandes nice!  CI passes to LGTM


Media element CORS error

Target Platforms
NodeJS
SDK Version
latest
Application Name
Adaptive Card designer & js viewer
Problem Description
I have a Media element with an mp3 for example from http://open.live.bbc.co.uk/mediaselector/6/redir/version/2.0/mediaset/audio-nondrm-download-rss/proto/http/vpid/p0k5xlhh.mp3
The file plays when using a plain <audio src="..."
When using it in a Media element it does not play and CORS error is showing in console. That is probably caused by the crossorigin attribute added by the Adaptive Card runtime.
How do I disable the unwanted attribute and/or play mp3 files hosted on servers which I do not control?
Screenshots
No response
Card JSON
.

Sample Code Language
No response
Sample Code
No response

Bug is caused by https://github.com/microsoft/AdaptiveCards/blame/main/source/nodejs/adaptivecards/src/card-elements.ts#L2901 where the crossorigin attribute is set unconditionally


Release 2.6.0 for jakartaEE

Does this support versions above Jakarta EE 9 and Servlet 5.0?

Not yet but that is the plan.
Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: jaxhsu @.>
Sent: Wednesday, May 3, 2023 11:20:08 PM
To: hazendaz/sitemesh2 @.>
Cc: Jeremy Landis @.>; Assign @.>
Subject: Re: [hazendaz/sitemesh2] Release 2.6.0 for jakartaEE (Issue #5)
Does this support versions above Jakarta EE 9 and Servlet 5.0?
—
Reply to this email directly, view it on GitHubhttps://github.com/hazendaz/sitemesh2/issues/5#issuecomment-1534035254, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAHODI5HKAL6BT2RJW5UDSDXEMN6RANCNFSM6AAAAAAXQLHCOM.
You are receiving this because you were assigned.Message ID: @.***>

@jaxhsu I've released milestone 1 for jakarta.  To get there the following had to go

Dropped support for freemarker as it doesn't support jakarta
Dropped support for velocity as it doesn't support jakarta
Dropped support for tapestry as it doesn't support jakarta and we are too out of date.

Those are all optional usages here and my personal usage doesn't use any of those.

@hazendaz Thank you for sharing. Currently, the version 2.6.0-M1 is running smoothly on my project.

Nice! Thanks for sharing your results.
Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: jaxhsu @.>
Sent: Monday, May 15, 2023 11:28:09 PM
To: hazendaz/sitemesh2 @.>
Cc: Jeremy Landis @.>; Mention @.>
Subject: Re: [hazendaz/sitemesh2] Release 2.6.0 for jakartaEE (Issue #5)
@hazendazhttps://github.com/hazendaz Thank you for sharing. Currently, the version 2.6.0-M1 is running smoothly on my project.
—
Reply to this email directly, view it on GitHubhttps://github.com/hazendaz/sitemesh2/issues/5#issuecomment-1548923334, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAHODI77YKKK5SEKWTFIEPTXGLX4TANCNFSM6AAAAAAXQLHCOM.
You are receiving this because you were mentioned.Message ID: @.***>

closing as completed.  Items that do not exist are listed separately for adding back when jakarta support is released for each of the three.


Automated backlog grooming

The dotnet/docs repo has more than 1500 open issues in our backlog. That's not manageable for us to track work. We're building a plan to bulk close stale issues based on five variables. That will trim the active backlog to a set of issues that we intend to address.
This plan is not intended to avoid the tasks identified in the issues being closed. Rather, it is to organize our backlog so we can effectively manage it. Many of the issues are stale. Many reflect plans that have changed. Others reflect work that has become unnecessary because of other completed tasks. Our intent is to run this process once, with a commitment to stay current on our backlog grooming.
Process
We are building a query script to do the following:

Find all issues matching any of the criteria listed below.
Add a "won't fix" label to each of those issues. That will help us find any of these later to understand why they were closed.
Add a comment that points to this issue clarifying that the issue author may re-open the issue if they feel it should not have been closed.
Close the issue.

Variables
There are five variables we will use to close issues:

"P?" priority labels (P0, P1, P2, P3): These have been added by people examining the issue in the past. When none have been set, the script will behave as though "P2" was set.
"Pri?" Automated labels (Pri1, Pri2, Pri3) set by our label bot: These are added based on the traffic to an article. When none have been set, the script will behave as though "Pri2" was set for any article that has the "document details" codeblock. (Any issue without that codeblock should have "Pri3" assigned, unless assigned a different priority manually):
Author: We create different criteria for those issues opened by our team and partners, and customers.
Age: Different criteria are applied to issues based on when it was opened.

Criteria
The following table has our first pass at the criteria.  Headers are:

P: "P?" priority label
Pri: "Pri?" priority label
CodeBlock: The presence or absence of a "Document details" block. Its presence indicates an issue filed from the live article.
Author: Indicates if the author is a team member, or a partner.
Age: This column indicates how old an issue must be for it to be automatically closed.

The rows with a strikethrough should never occur. The labeling bot should always assign "Pri3" to any issue that does not contain the document details block when no other priority label has been set. The script will process any rows that do occur.

The ? in the priority column indicates an issue where no priority label has been applied.

To make suggested changes to the criteria, copy the table below, and make a comment changing the values in the Age column. Add Bold to any you change to help us spot your edits.

P
Pri
Author
CodeBlock
Age

0
1
External
Yes
No

0
1
External
No
No

0
1
Internal
Yes
No

0
1
Internal
No
No

0
2
External
Yes
No

0
2
External
No
No

0
2
Internal
Yes
No

0
2
Internal
No
No

0
3
External
Yes
No

0
3
External
No
No

0
3
Internal
Yes
No

0
3
Internal
No
No

0
?
External
Yes
No

0
?
External
No
No

0
?
Internal
Yes
No

0
?
Internal
No
No

1
1
External
Yes
24m

1
1
External
No
No

1
1
Internal
Yes
No

1
1
Internal
No
24m

1
2
External
Yes
18m

1
2
External
No
12m

1
2
Internal
Yes
12m

1
2
Internal
No
18m

1
3
External
Yes
12m

1
3
External
No
12m

1
3
Internal
Yes
12m

1
3
Internal
No
12m

1
?
External
Yes
18m

1
?
External
No
12m

1
?
Internal
Yes
12m

1
?
Internal
No
18m

2
1
External
Yes
18m

2
1
External
No
12m

2
1
Internal
Yes
12m

2
1
Internal
No
18m

2
2
External
Yes
12m

2
2
External
No
9m

2
2
Internal
Yes
9m

2
2
Internal
No
12m

2
3
External
Yes
9m

2
3
External
No
9m

2
3
Internal
Yes
9m

2
3
Internal
No
9m

2
?
External
Yes
12m

2
?
External
No
9m

2
?
Internal
Yes
9m

2
?
Internal
No
12m

3
1
External
Yes
9m

3
1
External
No
9m

3
1
Internal
Yes
9m

3
1
Internal
No
12m

3
2
External
Yes
9m

3
2
External
No
6m

3
2
Internal
Yes
6m

3
2
Internal
No
9m

3
3
External
Yes
6m

3
3
External
No
6m

3
3
Internal
Yes
3m

3
3
Internal
No
6m

3
?
External
Yes
9m

3
?
External
No
6m

3
?
Internal
Yes
6m

3
?
Internal
No
9m

2
1
External
Yes
18m

?
1
External
No
12m

?
1
Internal
Yes
12m

?
1
Internal
No
18m

?
2
External
Yes
12m

?
2
External
No
9m

2
2
Internal
Yes
9m

?
2
Internal
No
12m

?
3
External
Yes
9m

?
3
External
No
9m

?
3
Internal
Yes
6m

?
3
Internal
No
9m

?
?
External
Yes
12m

?
?
External
No
9m

?
?
Internal
Yes
9m

?
?
Internal
No
12m

The first run of the tool that queries for issues found the following results:
Closing 884 of 1539

CloseCriteria { PLabel = P1, PriLabel = Missing, HasDocIssue = True, IsInternal = True }:

Total issues: 22, Closing 0 older than -1 months

CloseCriteria { PLabel = P1, PriLabel = Missing, HasDocIssue = True, IsInternal = False }:

Total issues: 96, Closing 50 older than 18 months

CloseCriteria { PLabel = P1, PriLabel = Pri2, HasDocIssue = True, IsInternal = True }:

Total issues: 4, Closing 0 older than 12 months

CloseCriteria { PLabel = P1, PriLabel = Pri2, HasDocIssue = True, IsInternal = False }:

Total issues: 19, Closing 0 older than 12 months

CloseCriteria { PLabel = P1, PriLabel = Pri3, HasDocIssue = False, IsInternal = True }:

Total issues: 71, Closing 50 older than 12 months

CloseCriteria { PLabel = P1, PriLabel = Pri3, HasDocIssue = False, IsInternal = False }:

Total issues: 18, Closing 11 older than 18 months

CloseCriteria { PLabel = P2, PriLabel = Missing, HasDocIssue = True, IsInternal = True }:

Total issues: 66, Closing 38 older than 18 months

CloseCriteria { PLabel = P2, PriLabel = Missing, HasDocIssue = True, IsInternal = False }:

Total issues: 376, Closing 305 older than 12 months

CloseCriteria { PLabel = P2, PriLabel = Missing, HasDocIssue = False, IsInternal = True }:

Total issues: 1, Closing 1 older than 12 months

CloseCriteria { PLabel = P2, PriLabel = Pri1, HasDocIssue = True, IsInternal = True }:

Total issues: 1, Closing 0 older than 12 months

CloseCriteria { PLabel = P2, PriLabel = Pri1, HasDocIssue = True, IsInternal = False }:

Total issues: 1, Closing 0 older than 9 months

CloseCriteria { PLabel = P2, PriLabel = Pri2, HasDocIssue = True, IsInternal = True }:

Total issues: 8, Closing 0 older than 9 months

CloseCriteria { PLabel = P2, PriLabel = Pri2, HasDocIssue = True, IsInternal = False }:

Total issues: 26, Closing 6 older than 9 months

CloseCriteria { PLabel = P2, PriLabel = Pri3, HasDocIssue = False, IsInternal = True }:

Total issues: 90, Closing 85 older than 9 months

CloseCriteria { PLabel = P2, PriLabel = Pri3, HasDocIssue = False, IsInternal = False }:

Total issues: 45, Closing 38 older than 12 months

CloseCriteria { PLabel = P3, PriLabel = Missing, HasDocIssue = True, IsInternal = True }:

Total issues: 1, Closing 1 older than 9 months

CloseCriteria { PLabel = P3, PriLabel = Missing, HasDocIssue = True, IsInternal = False }:

Total issues: 30, Closing 8 older than 9 months

CloseCriteria { PLabel = P3, PriLabel = Pri2, HasDocIssue = True, IsInternal = False }:

Total issues: 3, Closing 0 older than 6 months

CloseCriteria { PLabel = P3, PriLabel = Pri3, HasDocIssue = False, IsInternal = True }:

Total issues: 11, Closing 11 older than 6 months

CloseCriteria { PLabel = P3, PriLabel = Pri3, HasDocIssue = False, IsInternal = False }:

Total issues: 9, Closing 4 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Missing, HasDocIssue = True, IsInternal = True }:

Total issues: 60, Closing 12 older than 18 months

CloseCriteria { PLabel = Missing, PriLabel = Missing, HasDocIssue = True, IsInternal = False }:

Total issues: 296, Closing 199 older than 12 months

CloseCriteria { PLabel = Missing, PriLabel = Missing, HasDocIssue = False, IsInternal = False }:

Total issues: 1, Closing 0 older than 18 months

CloseCriteria { PLabel = Missing, PriLabel = Pri1, HasDocIssue = True, IsInternal = True }:

Total issues: 7, Closing 0 older than 12 months

CloseCriteria { PLabel = Missing, PriLabel = Pri1, HasDocIssue = True, IsInternal = False }:

Total issues: 10, Closing 0 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Pri1, HasDocIssue = False, IsInternal = True }:

Total issues: 1, Closing 0 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Pri1, HasDocIssue = False, IsInternal = False }:

Total issues: 1, Closing 1 older than 12 months

CloseCriteria { PLabel = Missing, PriLabel = Pri2, HasDocIssue = True, IsInternal = True }:

Total issues: 20, Closing 4 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Pri2, HasDocIssue = True, IsInternal = False }:

Total issues: 105, Closing 7 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Pri2, HasDocIssue = False, IsInternal = True }:

Total issues: 3, Closing 0 older than 6 months

CloseCriteria { PLabel = Missing, PriLabel = Pri2, HasDocIssue = False, IsInternal = False }:

Total issues: 1, Closing 0 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Pri3, HasDocIssue = True, IsInternal = True }:

Total issues: 2, Closing 0 older than 12 months

CloseCriteria { PLabel = Missing, PriLabel = Pri3, HasDocIssue = True, IsInternal = False }:

Total issues: 8, Closing 0 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Pri3, HasDocIssue = False, IsInternal = True }:

Total issues: 73, Closing 31 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Pri3, HasDocIssue = False, IsInternal = False }:

Total issues: 53, Closing 22 older than 12 months

The first run of the tool that queries for issues found the following results:
Closing 884 of 1539

CloseCriteria { PLabel = P1, PriLabel = Missing, HasDocIssue = True, IsInternal = True }:

Total issues: 22, Closing 0 older than -1 months

CloseCriteria { PLabel = P1, PriLabel = Missing, HasDocIssue = True, IsInternal = False }:

Total issues: 96, Closing 50 older than 18 months

CloseCriteria { PLabel = P1, PriLabel = Pri2, HasDocIssue = True, IsInternal = True }:

Total issues: 4, Closing 0 older than 12 months

CloseCriteria { PLabel = P1, PriLabel = Pri2, HasDocIssue = True, IsInternal = False }:

Total issues: 19, Closing 0 older than 12 months

CloseCriteria { PLabel = P1, PriLabel = Pri3, HasDocIssue = False, IsInternal = True }:

Total issues: 71, Closing 50 older than 12 months

CloseCriteria { PLabel = P1, PriLabel = Pri3, HasDocIssue = False, IsInternal = False }:

Total issues: 18, Closing 11 older than 18 months

CloseCriteria { PLabel = P2, PriLabel = Missing, HasDocIssue = True, IsInternal = True }:

Total issues: 66, Closing 38 older than 18 months

CloseCriteria { PLabel = P2, PriLabel = Missing, HasDocIssue = True, IsInternal = False }:

Total issues: 376, Closing 305 older than 12 months

CloseCriteria { PLabel = P2, PriLabel = Missing, HasDocIssue = False, IsInternal = True }:

Total issues: 1, Closing 1 older than 12 months

CloseCriteria { PLabel = P2, PriLabel = Pri1, HasDocIssue = True, IsInternal = True }:

Total issues: 1, Closing 0 older than 12 months

CloseCriteria { PLabel = P2, PriLabel = Pri1, HasDocIssue = True, IsInternal = False }:

Total issues: 1, Closing 0 older than 9 months

CloseCriteria { PLabel = P2, PriLabel = Pri2, HasDocIssue = True, IsInternal = True }:

Total issues: 8, Closing 0 older than 9 months

CloseCriteria { PLabel = P2, PriLabel = Pri2, HasDocIssue = True, IsInternal = False }:

Total issues: 26, Closing 6 older than 9 months

CloseCriteria { PLabel = P2, PriLabel = Pri3, HasDocIssue = False, IsInternal = True }:

Total issues: 90, Closing 85 older than 9 months

CloseCriteria { PLabel = P2, PriLabel = Pri3, HasDocIssue = False, IsInternal = False }:

Total issues: 45, Closing 38 older than 12 months

CloseCriteria { PLabel = P3, PriLabel = Missing, HasDocIssue = True, IsInternal = True }:

Total issues: 1, Closing 1 older than 9 months

CloseCriteria { PLabel = P3, PriLabel = Missing, HasDocIssue = True, IsInternal = False }:

Total issues: 30, Closing 8 older than 9 months

CloseCriteria { PLabel = P3, PriLabel = Pri2, HasDocIssue = True, IsInternal = False }:

Total issues: 3, Closing 0 older than 6 months

CloseCriteria { PLabel = P3, PriLabel = Pri3, HasDocIssue = False, IsInternal = True }:

Total issues: 11, Closing 11 older than 6 months

CloseCriteria { PLabel = P3, PriLabel = Pri3, HasDocIssue = False, IsInternal = False }:

Total issues: 9, Closing 4 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Missing, HasDocIssue = True, IsInternal = True }:

Total issues: 60, Closing 12 older than 18 months

CloseCriteria { PLabel = Missing, PriLabel = Missing, HasDocIssue = True, IsInternal = False }:

Total issues: 296, Closing 199 older than 12 months

CloseCriteria { PLabel = Missing, PriLabel = Missing, HasDocIssue = False, IsInternal = False }:

Total issues: 1, Closing 0 older than 18 months

CloseCriteria { PLabel = Missing, PriLabel = Pri1, HasDocIssue = True, IsInternal = True }:

Total issues: 7, Closing 0 older than 12 months

CloseCriteria { PLabel = Missing, PriLabel = Pri1, HasDocIssue = True, IsInternal = False }:

Total issues: 10, Closing 0 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Pri1, HasDocIssue = False, IsInternal = True }:

Total issues: 1, Closing 0 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Pri1, HasDocIssue = False, IsInternal = False }:

Total issues: 1, Closing 1 older than 12 months

CloseCriteria { PLabel = Missing, PriLabel = Pri2, HasDocIssue = True, IsInternal = True }:

Total issues: 20, Closing 4 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Pri2, HasDocIssue = True, IsInternal = False }:

Total issues: 105, Closing 7 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Pri2, HasDocIssue = False, IsInternal = True }:

Total issues: 3, Closing 0 older than 6 months

CloseCriteria { PLabel = Missing, PriLabel = Pri2, HasDocIssue = False, IsInternal = False }:

Total issues: 1, Closing 0 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Pri3, HasDocIssue = True, IsInternal = True }:

Total issues: 2, Closing 0 older than 12 months

CloseCriteria { PLabel = Missing, PriLabel = Pri3, HasDocIssue = True, IsInternal = False }:

Total issues: 8, Closing 0 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Pri3, HasDocIssue = False, IsInternal = True }:

Total issues: 73, Closing 31 older than 9 months

CloseCriteria { PLabel = Missing, PriLabel = Pri3, HasDocIssue = False, IsInternal = False }:

Total issues: 53, Closing 22 older than 12 months

@BillWagner How do I “tag @dotnet/docs ”? It doesn’t seem like it actually works…

@BillWagner How do I “tag @dotnet/docs ”? It doesn’t seem like it actually works…

Frustrated to see Microsoft do this. https://news.ycombinator.com/item?id=25821092 is a discussion from 12 days ago, where a large portion of users agreed stale bots were frustrating and anti-user in nature, especially in the case of repos where maintainers were the slower party to respond.

Frustrated to see Microsoft do this. https://news.ycombinator.com/item?id=25821092 is a discussion from 12 days ago, where a large portion of users agreed stale bots were frustrating and anti-user in nature, especially in the case of repos where maintainers were the slower party to respond.

Cross-posting from https://github.com/dotnet/docs/issues/6773#issuecomment-76687149: since only repo collaborators can reopen a closed issue I assume you really mean "open a new one"?

Cross-posting from https://github.com/dotnet/docs/issues/6773#issuecomment-76687149: since only repo collaborators can reopen a closed issue I assume you really mean "open a new one"?

@akoeplinger

Cross-posting from #6773 (comment): since only repo collaborators can reopen a closed issue I assume you really mean "open a new one"?

Thanks for noting this. I'm watching notifications and I'll reopen issues based on author comments. (I think the original author can also reopen issues, but I'll watch to make sure).

@akoeplinger

Cross-posting from #6773 (comment): since only repo collaborators can reopen a closed issue I assume you really mean "open a new one"?

Thanks for noting this. I'm watching notifications and I'll reopen issues based on author comments. (I think the original author can also reopen issues, but I'll watch to make sure).

@BillWagner I wasn't able to re-open issues for which I was the original author. GitHub allows me to reopen only if I'm who closed it.
Also tagging @dotnet/docs doesn't work for external contributors.
I've tagged you on a few issues that I think needs to be re-opened.

@BillWagner I wasn't able to re-open issues for which I was the original author. GitHub allows me to reopen only if I'm who closed it.
Also tagging @dotnet/docs doesn't work for external contributors.
I've tagged you on a few issues that I think needs to be re-opened.

Project maintainers can reopen closed issues regardless of who closed them. External users can only reopen an issue if they themselves closed it.

Project maintainers can reopen closed issues regardless of who closed them. External users can only reopen an issue if they themselves closed it.

@BillWagner

@akoeplinger

Cross-posting from #6773 (comment): since only repo collaborators can reopen a closed issue I assume you really mean "open a new one"?

Thanks for noting this. I'm watching notifications and I'll reopen issues based on author comments. (I think the original author can also reopen issues, but I'll watch to make sure).

Original author cannot reopen issues.
I still am awaiting instructions on how to “tag @dotnet/docs teams”. How does one do this with GitHub?

@BillWagner

@akoeplinger

Cross-posting from #6773 (comment): since only repo collaborators can reopen a closed issue I assume you really mean "open a new one"?

Thanks for noting this. I'm watching notifications and I'll reopen issues based on author comments. (I think the original author can also reopen issues, but I'll watch to make sure).

Original author cannot reopen issues.
I still am awaiting instructions on how to “tag @dotnet/docs teams”. How does one do this with GitHub?

@ocdtrekkie
We understand your frustration. We discussed this internally for some time before coming to this conclusion. The reality is that we just couldn't manage the backlog by hand. Also, note that we tailored the age of issues based on several variables. While we know that an automated system will never be perfect, we tried to minimize the number of valid issues to close while maximizing closing those that no longer applied. I'm watching comments to see which we will reopen.
Our commitment going forward is to stay on top of new issues better and not have this happen again. Furthermore, as we update or rework articles, we can find issues that were closed with the "won't fix" label and make sure the root cause is fixed.

@ocdtrekkie
We understand your frustration. We discussed this internally for some time before coming to this conclusion. The reality is that we just couldn't manage the backlog by hand. Also, note that we tailored the age of issues based on several variables. While we know that an automated system will never be perfect, we tried to minimize the number of valid issues to close while maximizing closing those that no longer applied. I'm watching comments to see which we will reopen.
Our commitment going forward is to stay on top of new issues better and not have this happen again. Furthermore, as we update or rework articles, we can find issues that were closed with the "won't fix" label and make sure the root cause is fixed.

I still am awaiting instructions on how to “tag @dotnet/docs teams”. How does one do this with GitHub?

Only members of the dotnet org can mention @dotnet/docs. It's either automatic or not possible, depending on the user. However, even without the group mention we one of the triage members should see the reply.

I still am awaiting instructions on how to “tag @dotnet/docs teams”. How does one do this with GitHub?

Only members of the dotnet org can mention @dotnet/docs. It's either automatic or not possible, depending on the user. However, even without the group mention we one of the triage members should see the reply.

One alternative would've been to use a system like https://probot.github.io/apps/stale/ which first posts a comment on stale issues and only if nobody replies within some time frame closes the issue.

One alternative would've been to use a system like https://probot.github.io/apps/stale/ which first posts a comment on stale issues and only if nobody replies within some time frame closes the issue.

@akoeplinger We looked at that. We wanted to have better control over which old issues were closed. (We looked at page views, whether it was targeting an article, or a general concern, whether it was an internal work item, or a customer concern, and its age).

@akoeplinger We looked at that. We wanted to have better control over which old issues were closed. (We looked at page views, whether it was targeting an article, or a general concern, whether it was an internal work item, or a customer concern, and its age).

Tagging the @dotnet/docs team only works for members of the dotnet org.
You can add a comment, and any of us on the triage team are watching for them.
Thanks for your patience.

Tagging the @dotnet/docs team only works for members of the dotnet org.
You can add a comment, and any of us on the triage team are watching for them.
Thanks for your patience.

@akoeplinger  - pls no stale bot. That thing and its ilk are community deadly as they dont inspect for a contributor, member, owner, etc.  to have done anything on an issue before slamming it closed.   There are very few customer (or even generally personal) interactions that create more negative feelings (spanning disappoint, upset, hostility, rage, etc) than crassly ignoring someone asking you for help.  Do that to your userbase enough and it becomes a reputation that is very hard to reverse.
@BillWagner - This kind of system/response is similar to the developer community's "Sorry we know the thing you bought is having a problem thats crippling your productivity, but we are too busy with something else for the last three months to even read what you wrote, so it will now be closed (and locked so you cant even respond to this in protest)".
You should probably update the message in that to not say "Tag @dotnet/docs" since it wont work for most of us.

@akoeplinger  - pls no stale bot. That thing and its ilk are community deadly as they dont inspect for a contributor, member, owner, etc.  to have done anything on an issue before slamming it closed.   There are very few customer (or even generally personal) interactions that create more negative feelings (spanning disappoint, upset, hostility, rage, etc) than crassly ignoring someone asking you for help.  Do that to your userbase enough and it becomes a reputation that is very hard to reverse.
@BillWagner - This kind of system/response is similar to the developer community's "Sorry we know the thing you bought is having a problem thats crippling your productivity, but we are too busy with something else for the last three months to even read what you wrote, so it will now be closed (and locked so you cant even respond to this in protest)".
You should probably update the message in that to not say "Tag @dotnet/docs" since it wont work for most of us.

Cannot re-open
https://github.com/dotnet/docs/issues/7489
If you reviewed it and tagged in the backlog with a priority, it would seem like the need was acknowledged.  I'm not sure why you would auto close it.

Cannot re-open
https://github.com/dotnet/docs/issues/7489
If you reviewed it and tagged in the backlog with a priority, it would seem like the need was acknowledged.  I'm not sure why you would auto close it.

Adding a new on #7489: We agreed to keep that closed based on another article that addresses the questions.

Adding a new on #7489: We agreed to keep that closed based on another article that addresses the questions.

@StingyJack I don't think it's quite the same. The team here has a large backlog and is putting to the side those issues that aren't burningly important to someone. If you indicate that your issue is important (by tagging @dotnet/docs) the team is willing to consider reopening (that's been my experience so far).
On the flip side, if the author can't even be bothered to respond with said tag, I would think it shows a certain level of uninterest.
(It's not like Developer Community, where filing issues often/usually feels like a directed path to the circular file.)

@StingyJack I don't think it's quite the same. The team here has a large backlog and is putting to the side those issues that aren't burningly important to someone. If you indicate that your issue is important (by tagging @dotnet/docs) the team is willing to consider reopening (that's been my experience so far).
On the flip side, if the author can't even be bothered to respond with said tag, I would think it shows a certain level of uninterest.
(It's not like Developer Community, where filing issues often/usually feels like a directed path to the circular file.)

@zspitz - the action taken here is fine so long as nobody starts showing symptoms of the MCLA fever ("must close/lock/archive"). User abandonment is one thing, using the stalebot is another.
( The ~600 issues I've reported on devcomm unquestionably tell the story that the circular file is both real and very likely and not just a feeling. )

@zspitz - the action taken here is fine so long as nobody starts showing symptoms of the MCLA fever ("must close/lock/archive"). User abandonment is one thing, using the stalebot is another.
( The ~600 issues I've reported on devcomm unquestionably tell the story that the circular file is both real and very likely and not just a feeling. )

Closing, as all issues we planned to close have been closed. (We'll still respond to requests to reopen issues).
Thanks for the comments, discussion, and request where our tool caught issues that should be reopened.

Closing, as all issues we planned to close have been closed. (We'll still respond to requests to reopen issues).
Thanks for the comments, discussion, and request where our tool caught issues that should be reopened.


[FEAT]: Add Bitbucket / Git repo connector

What would you like to see?
Why limit only to github ?

We support GitHub and GitLab, we will have loadable data connectors and you can build the ones you explicitly use. The GitHub and GitLab connectors were highly requested, that is why.


MHR crashes instantly upon startup, potentially DirectX 12 related?

As described, MHR crashes within 1 to 2 seconds on the initial loading screen. Tried loading with no mods in the \reframework subfolders, fresh REFramework install, fresh game install, Nightly release install, ect. It's also not the HDR in-game, my setup doesn't support that.
As far as I can tell it's unrelated to similar issues already posted... I am a dummy when it comes to programming though. Any help would be greatly appreciated.
re2_framework_log(3).txt

I also have the same problem, which started from base rise. This almost makes it impossible to use any mod.Thanks in advance for the help
re2_framework_log.txt
.


portico: Features table fixes.

This PR corrects a whole bunch of different edge cases, largely at smaller screen sizes, where sticky headers spilled over the top of the header row or fell out of nice alignment with the plans labels.
It also provides a fix for overscrolling on the features table's All view, which can be viewed in viewports as narrow as 374px (previously, it needed a viewport of at least 406px to not begin to scroll).
Screenshots and screen captures:
Firefox does not capture blur effects, so disregard the lack of blur behind the menus here.

Cloud view, before
Cloud view, after

All view sticky header, before
All view, after

iPhone Overscroll, before
iPhone Overscroll, after (none)

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @karlstolley!


Implement LLama-2

Feature request
We would like to request access to LLama-2 and implement it as a provided ML model, i.e openadapt.provider.LLAMA2 or similar.
Motivation
No response

I've already requested access just now, waiting on Meta's reply 😄

Nouse-Hermes-Llama2-13b: https://huggingface.co/NousResearch/Nous-Hermes-Llama2-13b?text=My+name+is+Lewis+and+I+like+to
LLama-2 GGML model: https://huggingface.co/TheBloke/Llama-2-7B-GGML,
LLama-2-Chat GGML model: https://huggingface.co/TheBloke/Llama-2-7B-Chat-GGML
Seems like The Bloke wastes no time in GGML'ing models! CPU supported llama-2 models above.
@abrichr With the amount of models coming in, I'm wondering what the strategy to choose the most 'worthwhile' ones would be.

@FFFiend as discussed, we would like to implement a high level API that the rest of the system uses, and have models implement that API as necessary.

https://huggingface.co/chat/
LLAMA2-70b chat model hosted by huggingface.
Issue with LLama-2 specifically is that you have to sign in to your huggingface account through the CLI since only accounts that are granted access can download the model..so that is currently a blocker with Modal.
TODO: figure out how to authenticate on Cloud based services and run inference with LLama-2


[iOS] Create Setting Screen (UI)

Kind (Required)

Improvement

Overview (Required)

This issue can work after #443 merged.
Please implement Setting Screen UI.
No needed to implement  logic (Changing Language, Toggle theme).

Links

Figma

I would like to try this task✋

Thanks! I will assign this issue to you 👍🏼


[DNM] CI: Disable debug symbols on desktop (test)

Do not merge!
This is a CI test to get the sizes of desktop builds without debug symbols, to compare with #42826.

Superseded by #42997.


chore: reset selection color in editor

Fixes #279

So much better, thank you!

(I notice the PR is still in draft, are you planning to fix dark mode in this PR as well?)

I notice the PR is still in draft, are you planning to fix dark mode in this PR as well?

I've done it. Sorry for the wait.

this looks fantastic, thanks so much!


Bump github.com/imroc/req/v3 to version that builds with latest golang

The test seem to fail due to the CI not due to any tests :(

Yes, I'll fix it. (There is no osx binary in latest mage release)


Manual issuing of (unlimited) access tokens

I'm working on a CMS like application that uses fosite to implement OAuth2 for all authentication and authorization purposes. The app uses the "implicit grant" for user authentication and the "client credentials grant" to authenticate applications that access data from the system (non web).
Now I would like to implement a feature that a SPA can directly access data and images from the CMS over an API. For that I would like to generate a long-lived access token that the application can directly use to access the data without having to authenticate and authorize itself. This is also important for caching images properly, etc.
As far as I can tell is the Access Token Lifespan configured on a global level (not per access token) this means that supporting unlimited access token would currently require to set the global token lifespan to infinite (very bad for security) or always returning an up to date RequestedAt time when loading the token from storage.
Is there a proper way implemented to handle this?
Following that I was also thinking about what would be the proper way to manually issue access tokens without talking to the database directly?

Hey, awesome that you ask this! I am working on a proposal to implement API keys which are bound to clients and basically long living OAuth2 access tokens in hydra: https://github.com/ory-am/hydra/issues/234
I am completely open to have this proprietairy flow included in fosite if it suits your purposes.
The second option is to use a session struct that implements HMACSessionContainer where you can set the expiry time on a per-token or per-code basis. Unfortunately, this isn't currently implemented for JWT sessions.

Ok, cool :)
So, all the OAuth2 handling is part of a framework that I extracted out of this CMS project.
The following function authorizes the request:
https://github.com/gonfire/fire/blob/master/oauth2/authenticator.go#L140
And the authorization will at some point fetch the access token here:
https://github.com/gonfire/fire/blob/master/oauth2/storage.go#L110
As far as I can tell, one would need to configure the HMACSessionContainer and the token lifespan in the first function, yet the information that this token is in fact a long-lived token would be only available by the end of the second function. Is the proper way to reconfigure the session from within the second function on the storage?

The most natural way would be to set the expiry on the Requester returned by the lookup function:
https://github.com/gonfire/fire/blob/master/oauth2/storage.go#L141
At that point I'm asking myself: Why is the RequestedAt saved of a token and not the expiry date?

Sorry, I'm not enough in the mindset of your code, but if you don't know that the token will be long living when fosite is storing it in the database, you probably must override the database entry yourself :/

At that point I'm asking myself: Why is the RequestedAt saved of a token and not the expiry date?

The original idea behind this was to prevent people from issuing long living access tokens, as they are an anti pattern and one should use refresh tokens to achieve the same effect. However, after some time I was convinced by someone that this is a key feature so I introduced it as part of the session without breaking backwards compatibility and without compromising the way things usually work. Another part of the reasoning was that some (additional or proprietairy) requests might not have an expiry time at all.
However I agree that this is a quirky part of the library.

One of the reasons for trying to prevent this is that people tend to use the implicit flow, then realize that it doesn't issue refresh tokens and then just say: oh ok, let's create access tokens that are valid for 30 days. But being mandatory isn't always the right path for a library :/

Ok, I see the reasoning behind the RequestedAt and expiry time.
I'm still not sure where I need to configure/modify the HMACSession. The following storage method is called by fosite upon validating a newly received access token:
func (s *storage) GetAccessTokenSession(ctx context.Context, signature string, session interface{}) (fosite.Requester, error) {
  // ...
  session.(*oauth2.HMACSession).AccessTokenExpiry = time.Now().Add(1 * time.Hour)
  // ...
}

Would that be the right approach?

That looks good, sorry for the delayed response!


Error: Field name duplication not allowed with modifiers

After migrating from the Meteor package to this one, I've started getting Field name duplication not allowed with modifiers errors. I'm not really sure where they're coming from, because I don't see any duplicate field names in my modifiers… Any thoughts?

Also I should mention that I'm only seeing this issue on my production instance, which uses a Compose db running Mongo 3.4.0 (vs 3.2.12 locally). I don't know if that has anything to do with it…


PHPDoc tag @extends contains generic type Illuminate\Http\Resources\Json\JsonResource but class Illuminate\Http\Resources\Json\JsonResource is not generic.

Larastan Version: 2.5.1
Laravel Version: 10.5.1
--level used: 5
Description
The upgrade guide states:
Upgrading To 0.5.3 From 0.5.2
Eloquent Resources
In order to perform proper analysis on your Eloquent resources, you must typehint the underlying Eloquent model class. This will >inform PHPStan that this resource uses User model. So calls to $this with model property or methods will be inferred correctly.
/**
 * @extends JsonResource<User>
 */
class UserResource extends JsonResource
{
...
}

However, doing this, causes Larastan to report:
PHPDoc tag @extends contains generic type Illuminate\Http\Resources\Json\JsonResource<App\Models\WorkProfile> but class Illuminate\Http\Resources\Json\JsonResource is not generic.
Am I confused or should this be working as described?
Example of one of my JsonResource's
<?php

namespace App\Http\Resources;

use App\Models\WatchProfileChecklistItem;
use Illuminate\Http\Request;
use Illuminate\Http\Resources\Json\JsonResource;

/**
 * @extends JsonResource<WatchProfileChecklistItem>
 * @mixin WatchProfileChecklistItem
 */
class WatchProfileChecklistItemResource extends JsonResource
{
    /**
     * @param  Request  $request
     * @return array
     */
    public function toArray($request)
    {
        return [
            'id'                         => $this->id,
            'name'                       => $this->name,
            'watch_profile_checklist_id' => $this->watch_profile_checklist_id,
            'created_at'                 => $this->created_at,
            'updated_at'                 => $this->updated_at,

            'checklist' => new WatchProfileChecklistResource($this->whenLoaded('checklist')),
        ];
    }
}

Reopening of 1614 as it's also occurring in larastan 2.5.1

I have noted the same upgrade steps were provided for Factory.
The Illuminate\Database\Eloquent\Factories\Factory class does indeed have a generic defined: @template TModel of \Illuminate\Database\Eloquent\Model
It appears JsonResource does not.

Thank you for your report!
Please try removing @extends JsonResource<WatchProfileChecklistItem>


Support for dnx test (coreclr only)

Run tests with the new runner on CoreCLR. Run with dnx on desktop.
Please review: @BrennanConroy @anurse
FYI @piotrpMSFT

Merging because I need the package. Feel free to leave comments and I'll address them


Android Manifest Error After adding this dependency.

Manifest merger failed : Attribute application@appComponentFactory value=(android.support.v4.app.CoreComponentFactory) from [com.android.support:support-compat:28.0.0] AndroidManifest.xml:22:18-91
	is also present at [androidx.core:core:1.0.1] AndroidManifest.xml:22:18-86 value=(androidx.core.app.CoreComponentFactory).
	Suggestion: add 'tools:replace="android:appComponentFactory"' to <application> element at AndroidManifest.xml:5:5-30:19 to override.

@santalu any updates with this issue?

@doilio how did you fix that issue?


Make Go To Definition work for symbols in project

The implementation for Go To Defintiion was using a tempfile for the current buffer. This made it so that Go To Definition wasn't working for symbols defined in the current source tree.
I switched the command to use the full file path of the file the user is invoking Go To Definition in, and now it works for the current project.

Hmm, is there no better way? Like running racer.exe on the temp file but working directory of the original file?
We can't run racer.exe on the on-the-disk file. This will break down for the unsaved files. It's better to not have definitions shown in some predictable cases instead of showing totally wrong definitions in some random and hard to predict cases.


[secrets-service] Use platform secrets store for shared secret

Currently, secrets-service stores the symmetric encryption key on
disk. Now, it uses the platform secrets code.
Right now the platform secrets store is also an insecure on-disk sore.
However, this makes it a bit easier for us to make sure we can export
all of the known shared secrets in the system.
To mitigate the very confusing naming, I've moved lib/secrets to
lib/platform/secrets.
Signed-off-by: Steven Danna<EMAIL_ADDRESS>

I didn't know we had a pattern for this.

@phiggins That was a bit purposeful.  When we put this in it was really just to support some legacy bits in chef-server.  To be frank, I'm a bit nervous about spreading its use because as I said it just uses insecure on-disk storage; but, perhaps gives us some leverage to improve it more easily in the future.

There's other places in secrets-service and nodemanager-service where we store keys on disk that could probably use the same treatment.

If you have a minute and want to point these out to me, I can include them in this PR or in a follow up.

If you have a minute and want to point these out to me, I can include them in this PR or in a follow up.

The ones I was thinking of are where we fetch a node's credential information and hydrate any SSH keys it has by calling this function: https://github.com/chef/automate/blob/master/components/nodemanager-service/api/nodes/node.secrets.go

https://github.com/chef/automate/blob/master/components/compliance-service/inspec-agent/resolver/resolver.go#L719
https://github.com/chef/automate/blob/master/components/nodemanager-service/api/nodes/server/server.go#L150

We've gone a different way for now.


Where is the transcribed result

Hello , please where can  I get the result of a transcribed conversation the tutorial on https://learn.microsoft.com/en-us/azure/cognitive-services/speech-service/how-to-use-conversation-transcription?pivots=programming-language-python does n't print results.

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

ID: f1d88ac1-d269-5f91-fb1f-8901589c6b02
Version Independent ID: 3fa3ffe6-277a-547a-a434-7002c056b3b9
Content: Real-time Conversation Transcription quickstart - Speech service - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/how-to-use-conversation-transcription.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @eric-urban
Microsoft Alias: eur

Thank you @Naveenommi-MSFT . I mean the transcription result is not printed on the terminal.

but when I  translate I get result on terminal like this.

Hence I am asking, Please where can see the result of my transcription ? No thing in the docs mentions how to get the transcribed result/file.

I mean please where can I get the spoken words with time stamps (Transcribed results) ☺?

@Forchapeatl - There are multiple code blocks in this article. Are you running the sample under Transcribe conversations? Please see transcriber.transcribed.connect.

#please-close


React to namespace changes in Razor.

Note this is only test changes.

aspnet/Razor#779
/cc @dougbu @pranavkm

:shipit:


Tests folder outside Python package?

Hello. I am probably doing something wrong, but I have been battling with this for a while... So far, when using the MolSSI cookiecutter I always moved the tests folder outside the Python package folder just after creating the repository and I never encountered any problems. However, in a recent project I decided to keep the MolSSI cookiecutter structure (tests folder inside the Python package folder) and while at first things seemed to work well, I encountered a problem when I started defining custom command line arguments in conftest.py.
The problem is the following. When I defined a custom command line option in conftest.py using pytest_addoption (to be used in a fixture with "sessioon" scope by passing pytestconfig as argument of the fixture, also defined in the same conftest.py file), the pytest command started failing because the custom option could not be found.
If I run pytest <PACKAGE>/tests, everything works as expected, but running pytest fails. This happens despite having the following pytest.ini file:
[pytest]
minversion = 6.0
testpaths =
    <PACKAGE>/tests/

Everything seems to work as expected if I either move the conftest.py file in the root directory (which I don't think is clean) or if I move the tests directory outside of the Python package and change the pytest.ini file as follows:
[pytest]
minversion = 6.0
testpaths =
    tests/

(as I used to do for other projects).
Am I doing something wrong or the way the cookiecutter is set up does not fully work with a conftest.py file in <PACKAGE>/tests/?

Related to https://github.com/MolSSI/cookiecutter-cms/issues/140
I've ran into the same issues


Cargo build Errors

Hi,
Am i missing some pre-requisites to build on Debian 12 (bookworm) as i get these errors;
~#cargo build

   Compiling windows_x86_64_gnu v0.52.6
   Compiling libc v0.2.162
   Compiling windows-targets v0.52.6
   Compiling windows-sys v0.59.0
   Compiling bitflags v2.6.0
   Compiling once_cell v1.20.2
   Compiling pkts-common v0.1.0
   Compiling rscap v0.2.2

warning: constant `PACKET_HOST` is never used
  --> rscap/src/linux.rs:40:18
   |
40 | pub(crate) const PACKET_HOST: libc::c_uchar = 0;
   |                  ^^^^^^^^^^^
   |
   = note: `#[warn(dead_code)]` on by default

warning: constant `PACKET_BROADCAST` is never used
  --> rscap/src/linux.rs:41:18
   |
41 | pub(crate) const PACKET_BROADCAST: libc::c_uchar = 1;
   |                  ^^^^^^^^^^^^^^^^

warning: constant `PACKET_MULTICAST` is never used
  --> rscap/src/linux.rs:42:18
   |
42 | pub(crate) const PACKET_MULTICAST: libc::c_uchar = 2;
   |                  ^^^^^^^^^^^^^^^^

warning: constant `PACKET_OTHERHOST` is never used
  --> rscap/src/linux.rs:43:18
   |
43 | pub(crate) const PACKET_OTHERHOST: libc::c_uchar = 3;
   |                  ^^^^^^^^^^^^^^^^

warning: constant `PACKET_OUTGOING` is never used
  --> rscap/src/linux.rs:44:18
   |
44 | pub(crate) const PACKET_OUTGOING: libc::c_uchar = 4;
   |                  ^^^^^^^^^^^^^^^

warning: constant `PACKET_LOOPBACK` is never used
  --> rscap/src/linux.rs:45:18
   |
45 | pub(crate) const PACKET_LOOPBACK: libc::c_uchar = 5;
   |                  ^^^^^^^^^^^^^^^

warning: constant `PACKET_USER` is never used
  --> rscap/src/linux.rs:46:18
   |
46 | pub(crate) const PACKET_USER: libc::c_uchar = 6;
   |                  ^^^^^^^^^^^

warning: constant `PACKET_KERNEL` is never used
  --> rscap/src/linux.rs:47:18
   |
47 | pub(crate) const PACKET_KERNEL: libc::c_uchar = 7;
   |                  ^^^^^^^^^^^^^

warning: constant `PACKET_AUXDATA` is never used
  --> rscap/src/linux.rs:51:18
   |
51 | pub(crate) const PACKET_AUXDATA: libc::c_int = 8;
   |                  ^^^^^^^^^^^^^^

warning: constant `PACKET_LOSS` is never used
  --> rscap/src/linux.rs:55:18
   |
55 | pub(crate) const PACKET_LOSS: libc::c_int = 14;
   |                  ^^^^^^^^^^^

warning: constant `PACKET_FANOUT_CBPF` is never used
  --> rscap/src/linux.rs:66:18
   |
66 | pub(crate) const PACKET_FANOUT_CBPF: libc::c_uint = 6;
   |                  ^^^^^^^^^^^^^^^^^^

warning: constant `PACKET_FANOUT_EBPF` is never used
  --> rscap/src/linux.rs:67:18
   |
67 | pub(crate) const PACKET_FANOUT_EBPF: libc::c_uint = 7;
   |                  ^^^^^^^^^^^^^^^^^^

warning: constant `PACKET_FANOUT_FLAG_UNIQUEID` is never used
  --> rscap/src/linux.rs:69:18
   |
69 | pub(crate) const PACKET_FANOUT_FLAG_UNIQUEID: libc::c_uint = 0x2000;
   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^

warning: constant `TP_STATUS_KERNEL` is never used
  --> rscap/src/linux.rs:72:18
   |
72 | pub(crate) const TP_STATUS_KERNEL: u32 = 0;
   |                  ^^^^^^^^^^^^^^^^

warning: constant `TP_STATUS_BLK_TMO` is never used
  --> rscap/src/linux.rs:78:18
   |
78 | pub(crate) const TP_STATUS_BLK_TMO: u32 = 1 << 5;
   |                  ^^^^^^^^^^^^^^^^^

warning: constant `TP_STATUS_TS_SOFTWARE` is never used
  --> rscap/src/linux.rs:87:18
   |
87 | pub(crate) const TP_STATUS_TS_SOFTWARE: u32 = 1 << 29;
   |                  ^^^^^^^^^^^^^^^^^^^^^

warning: constant `TP_STATUS_TS_SYS_HARDWARE` is never used
  --> rscap/src/linux.rs:88:18
   |
88 | pub(crate) const TP_STATUS_TS_SYS_HARDWARE: u32 = 1 << 30;
   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^

warning: constant `TP_STATUS_TS_RAW_HARDWARE` is never used
  --> rscap/src/linux.rs:89:18
   |
89 | pub(crate) const TP_STATUS_TS_RAW_HARDWARE: u32 = 1 << 31;
   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^

warning: constant `TP_FT_REQ_FILL_RXHASH` is never used
  --> rscap/src/linux.rs:91:18
   |
91 | pub(crate) const TP_FT_REQ_FILL_RXHASH: u32 = 1;
   |                  ^^^^^^^^^^^^^^^^^^^^^

warning: struct `tpacket_rollover_stats` is never constructed
  --> rscap/src/linux.rs:98:19
   |
98 | pub(crate) struct tpacket_rollover_stats {
   |                   ^^^^^^^^^^^^^^^^^^^^^^

warning: variants `TPACKET_V1` and `TPACKET_V2` are never constructed
   --> rscap/src/linux.rs:121:5
    |
120 | pub(crate) enum tpacket_versions {
    |                 ---------------- variants in this enum
121 |     TPACKET_V1,
    |     ^^^^^^^^^^
122 |     TPACKET_V2,
    |     ^^^^^^^^^^

warning: struct `fanout_args` is never constructed
   --> rscap/src/linux.rs:128:19
    |
128 | pub(crate) struct fanout_args {
    |                   ^^^^^^^^^^^

warning: struct `sockaddr_pkt` is never constructed
   --> rscap/src/linux.rs:139:19
    |
139 | pub(crate) struct sockaddr_pkt {
    |                   ^^^^^^^^^^^^

warning: struct `tpacket_auxdata` is never constructed
   --> rscap/src/linux.rs:147:19
    |
147 | pub(crate) struct tpacket_auxdata {
    |                   ^^^^^^^^^^^^^^^

warning: struct `tpacket_hdr` is never constructed
   --> rscap/src/linux.rs:159:19
    |
159 | pub(crate) struct tpacket_hdr {
    |                   ^^^^^^^^^^^

warning: struct `tpacket2_hdr` is never constructed
   --> rscap/src/linux.rs:180:19
    |
180 | pub(crate) struct tpacket2_hdr {
    |                   ^^^^^^^^^^^^

warning: struct `tpacket_stats_v3` is never constructed
   --> rscap/src/linux.rs:225:19
    |
225 | pub(crate) struct tpacket_stats_v3 {
    |                   ^^^^^^^^^^^^^^^^

warning: union `tpacket_req_u` is never used
   --> rscap/src/linux.rs:256:18
    |
256 | pub(crate) union tpacket_req_u {
    |                  ^^^^^^^^^^^^^

warning: field `iface` is never read
   --> rscap/src/linux/addr.rs:262:5
    |
261 | pub struct L2AddrAll {
    |            --------- field in this struct
262 |     iface: Interface,
    |     ^^^^^

warning: `rscap` (lib) generated 29 warnings
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.02s

Hey @daNutzzzzz, it looks like I have some warnings to clean up in the project--I'll fix those as appropriate. In general though, the library should work just fine despite these--they're mostly just unused code issues.


No module named spatial_correlation_Sampler

Hi @z-x-yang ,
It was mentioned in the readme that demo script will run even without spatial correlation sampler.But, in the attention.py ,it was being imported and the error is as follows:
Build AOT model.
Traceback (most recent call last):
File "/home/ubuntu/sam_track/DeAOT/aot-benchmark/tools/demo.py", line 286, in
main()
File "/home/ubuntu/sam_track/DeAOT/aot-benchmark/tools/demo.py", line 282, in main
demo(cfg)
File "/home/ubuntu/sam_track/DeAOT/aot-benchmark/tools/demo.py", line 107, in demo
model = build_vos_model(cfg.MODEL_VOS, cfg).cuda(gpu_id)
File "/home/ubuntu/sam_track/DeAOT/aot-benchmark/./networks/models/init.py", line 7, in build_vos_model
return AOT(cfg, encoder=cfg.MODEL_ENCODER, **kwargs)
File "/home/ubuntu/sam_track/DeAOT/aot-benchmark/./networks/models/aot.py", line 23, in init
self.LSTT = LongShortTermTransformer(
File "/home/ubuntu/sam_track/DeAOT/aot-benchmark/./networks/layers/transformer.py", line 75, in init
block(d_model, self_nhead, att_nhead, dim_feedforward,
File "/home/ubuntu/sam_track/DeAOT/aot-benchmark/./networks/layers/transformer.py", line 279, in init
self.short_term_attn = MultiheadLocalAttention(d_model,
File "/home/ubuntu/sam_track/DeAOT/aot-benchmark/./networks/layers/attention.py", line 282, in init
from spatial_correlation_sampler import SpatialCorrelationSampler
ModuleNotFoundError: No module named 'spatial_correlation_sampler

What is the perf gap without spatial correlation sampler?


How to pass metadata_context into requests to the ext_authz service?

Hi Envoy authors. I have been trying for hours to pass metadata from the Envoy instance to the gRPC external authorization service (both network and http) using the Check() method request argument which contains metadata_context as shown in th docs. I've tried to inject the metadata into the listener.metadata field from the envoy instance but it never works and the metadata is always empty inside the ext_authz service request. What am I doing wrong?

Hi @erir910
If your use case is to add static configuration to listener.metadata and then use that from within the external authorization service, I think you may want to look at context_extensions in https://www.envoyproxy.io/docs/envoy/latest/api-v3/service/auth/v3/attribute_context.proto.html#service-auth-v3-attributecontext
You can then set per-route config similar to how the Emissary Ingress (formerly Ambassador) does it https://www.envoyproxy.io/docs/envoy/latest/api-v3/service/auth/v3/attribute_context.proto.html#service-auth-v3-attributecontext
Let me know if that doesn't make sense or fit the use case you're describing.


Loading Custom Package's routes can only be done in one Service Provider

Laravel Version: 7.16.1
PHP Version: 7.4.7
Database Driver & Version: 10.4.13-MariaDB Homebrew

Description:
I opened this discussion in Laracasts. It refers to a problem when creating a custom package that uses "child" service providers that are registered by the Package's main service provider like this:
<?php

namespace Vendor\Package\Providers;

use Illuminate\Support\ServiceProvider;

class MainServiceProvider extends ServiceProvider
{
    /**
     * Register services.
     *
     * @return void
     */
    public function register()
    {
        // Register all the Package's Service Providers
        $this->app->register(
            FirstServiceProvider::class,
            SecondServiceProvider::class,
            ThirdServiceProvider::class,
        );
    }

    /**
     * Bootstrap services.
     *
     * @return void
     */
    public function boot()
    {
        // Load routes
        $this->loadRoutesFrom(__DIR__.'/../First/Routes/web.php');
        $this->loadRoutesFrom(__DIR__.'/../Second/Routes/web.php');
        $this->loadRoutesFrom(__DIR__.'/../Third/Routes/web.php');
    }
}

Each of these child service providers, namely First, Second and Third, have Routes, Traits, Commands, Models, Facades, etc, of their own and they all load without a hitch except for routes.
Steps To Reproduce:
In a folder structure like this:
src/
    First/
        Routes/
            web.php
    Second/
        Routes/
            web.php
    Third/
        Routes/
            web.php
    Providers/
        FirstServiceProvider.php
        SecondServiceProvider.php
        ThirdServiceProvider.php
        MainServiceProvider.php

Register only the MainServiceProvider.php in the package's composer.json:
"extra": {
    "laravel": {
        "providers": [
            "Vendor\\Package\\Providers\\MainServiceProvider"
        ],
    }
}

Load all routes from MainServiceProvider.php in the boot() method, as demonstrated in the code above, and run php artisan route:list to verify that the routes have been loaded correctly.
They should be.
Now comment out all three loadRoutesFrom() methods from MainServiceProvider and copy them to their respective provider's boot() method. When running php artisan route:list again, only the routes from the first registered service provider will be loaded. In this example, that would be the routes from FirstServiceProvider.php.
This is strange to me, since I can load and bind other things to Laravel's Service Container in each child provider, such as loading migrations and binding singletons; but not routes.

You can't call $this->app->register() with multiple (provider) arguments. The register method accepts the $provider and a $force flag. Now you are only registering the first provider, and only the first routes from the first provider are registered.
You need to register each provider explicitly:
$this->app->register(FirstServiceProvider::class);
$this->app->register(SecondServiceProvider::class);
$this->app->register(ThirdServiceProvider::class);

@sebdesign Thank you, that fixed it. I found the code to register multiple provider arguments in the same method in some tutorial and thought it worked fine. But registering them individually worked perfectly, thanks a lot


I am testing the Fabric Version of the Mod.

For some reason, only version 0.0.0 is being shown in the CurseForge Launcher. When I manually install the 0.0.1 update, it shows an error icon saying it isn't supported. The 0.0.1 version also requires the Architectury API for some reason now.
Another issue I have noticed, when holding down the RIGHT CLICK button, the sword continuously swings really fast. It is somewhat game-breaking.
Also, when holding a sword in the off-hand in creative mode and attempting to interact/place blocks, nothing works.
I love this mod a lot, but I am going to wait for the bugs to be fixed before I add it to the Fabric Version of my Modpack. I will do further testing with the Forge Version later!

Thancc


Do not depend on host to host transfers for Ceph MV action

Description
Do not depend on host to host transfers for Ceph MV action
Use case
In some circumstances, when using VM HA, VMs cannot be rescheduled because SSH becomes non accessible and you can see an error like this one:
ERROR: mv: Command "set -e -o pipefail tar -C /var/lib/one//datastores/<DS_ID> --sparse -cf - 0 | ssh <HOST> 'tar -C /var/lib/one//datastores/<DS_ID> --sparse -xf Error copying disk directory to target hostailed: ssh: connect to host <HOST> port 22: No route to host".

Interface Changes
Ceph driver

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

Hello, any information when this fix will be get to community version?

It is in 6.4 beta and will be released in 6.4 this month
However the patch is straightforward, just need to replace the ceph/mv action. This can be safely applied to any 6.2 installation


feat: support for ServerlessFunctionConfig and EdgeFunctionConfig

Adding support for :

memory, maxDuration and regions for Serverless Functions
envVarsInUse and regions for Edge Functions

I tried to keep the types structure defined here: https://vercel.com/docs/build-output-api/v3 without breaking the current API.
Limitation: settings cannot be defined on a by function basis when using split = true, they are applied globaly.
Maybe there is a nicer API for this, but for now:

import vercel from '@sveltejs/adapter-vercel';

export default {
  kit: {
    adapter: vercel({
      serverlessFunctionConfig: {
          memory: 1024,
          maxDuration: 10,
          regions: ['cdg1']
      },
    })
  }
};

and on the edge:

import vercel from '@sveltejs/adapter-vercel';

export default {
  kit: {
    adapter: vercel({
      edge: true,
      edgeFunctionConfig: {
          envVarsInUse: ['ENV1'],
          regions: ['cdg1']
      }
    })
  }
};

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[X] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[X] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[X] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Thanks for the PR. Our current plan is to expose this sort of configuration within the routes themselves — #8383 — so we don't want to add adapter-level configuration for this stuff in the meantime (though there probably will be some default config for +server.js files).
Until we implement that — hopefully soon — you can achieve the same outcome by modifying the contents of .vercel/output. Slightly hacky, but totally within the scope of what the Build Output API is designed to facilitate!

That would be awesome @Rich-Harris! I'm currently maintaining a custom vercel adapter that fits my needs: I have taken the more simpler route of defining each route config in svelte.config.js in a vercel.json fashion:
const config = {
  kit: {
    adapter: vercel({
      default: {
        runtime: "node",
        regions: ['fra1'],
        memory: 2048,
        maxDuration: 30
      },
      functions: {
        '/(landing)/.*': {
          runtime: 'edge',
          regions: ['cdg', 'fra']
        },
        '/api/.*': {
          runtime: 'node', // not necessary
          memory: 1024,
          maxDuration: 60,
        },
        '/(app)/.*': {
          maxDuration: 10,
        }
      }
    })
  }
};

A bit less hacky than modifying the contents of .vercel/output 🙂