Fix Ruby version dependencies

The original FROM ruby:2.3-slim line will automatically load the latest patch version of Ruby. At the moment it's 2.3.6, but the Gemfile specifies 2.3.3, so an error is thrown.
I just specified v2.3.6 both in the Gemfile and in the Dockerfile so any future updates shouldn't throw an error

Hey @joerodrig - thanks for the fix! I noticed Travis build broke, so fixed that on another PR https://github.com/jfroom/docker-compose-rails-selenium-example/pull/2. And then this bug reared its head there, so I fixed it there based on your edits. Closing this one. Cheers!


Create one test for fleeting-notes-obsidian code

Requirements:

Mock the API call (mock pulling a single note)
Test one-way sync and that file populates and has the correct title

See what templater uses!

For mocking the API call:
In tests, there shouldn't be any HTTP requests at all. What i suggest is you can mock the module utils.ts and the get_all_notes function within it.  See: https://www.chakshunyu.com/blog/how-to-mock-only-one-function-from-a-module-in-jest/#manual-mocking


Reduce Kp/Ki by 25% to eliminate steer oscillation on 2017+ CRV

seems like something changed from 0.7.6 to 0.7.7 that caused this, below is before/after back-to-back drives on same corner at same speed
0.7.6

0.7.7

Anything required to merge?


Update code coverage module

This resembles the CMake directives suggested by Codecov.

Hi,
the code coverage is for GNUfortran and Cland. Are there any plans to extend it for other compilers as well (like Intel) ?
Concerning failed test: test/test.py::test_boost_libs FAILED    This is OpenMPI,  does travis worker allow multiCPU processes ?

The test failure is unrelated to this PR. Merging. Thanks! About other compilers: PRs welcome but IMO free compilers are probably enough since they are always available.


Data: add useful language objects to data

This is useful because it will provide punctuation and orthography conventions, without the need for the user to create new ones every time.

[ ] English
[ ] Spanish
[ ] French

Don't worry about phoneme inventories for these, just orthographies.


Multi-lingual Helm text

Kubernetes, and a lot of other things, work in multi-lingual environments. Helm's output is currently English. Is it time to go multi-lingual? We could start with the tools and find people interested in translating.

there are now efforts being lead in helm-www to translate the documentation to multplie languages, including Korean and Chinese. Closing.


Add local loaded preferences

Codecov Report

Merging #510 (bbbde0f) into main (00b9dd1) will increase coverage by 0.66%.
The diff coverage is 86.17%.

@@            Coverage Diff             @@
##             main     #510      +/-   ##
==========================================
+ Coverage   70.60%   71.27%   +0.66%
==========================================
  Files          88       89       +1
  Lines        5014     4901     -113
  Branches     1038      987      -51
==========================================
- Hits         3540     3493      -47
+ Misses        746      729      -17
+ Partials      728      679      -49

Impacted Files
Coverage Δ

...lin/com/alexvanyo/composelife/ui/ComposeLifeApp.kt
61.76% <ø> (ø)

...o/composelife/ui/InteractiveCellUniverseOverlay.kt
84.27% <ø> (ø)

...yo/composelife/ui/action/CellUniverseActionCard.kt
77.77% <ø> (ø)

...ife/ui/action/settings/FullscreenSettingsScreen.kt
75.00% <ø> (ø)

...n/com/alexvanyo/composelife/ui/cells/CellWindow.kt
80.76% <ø> (-2.76%)
:arrow_down:

...vanyo/composelife/ui/cells/NonInteractableCells.kt
52.83% <33.33%> (-4.07%)
:arrow_down:

...mposelife/ui/action/settings/CellStatePreviewUi.kt
64.00% <72.72%> (-1.58%)
:arrow_down:

...omposelife/ui/action/settings/DarkThemeConfigUi.kt
62.79% <75.00%> (+5.89%)
:arrow_up:

...yo/composelife/ui/action/settings/DisableAGSLUi.kt
45.65% <75.00%> (-0.38%)
:arrow_down:

.../composelife/ui/action/settings/DisableOpenGLUi.kt
45.65% <75.00%> (-0.38%)
:arrow_down:

... and 27 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Inspired by the similar PR in the mobile app repository, which in turn was inspired by http://melix.github.io/blog/2022/05/gradle-laziness.html.

Review checklist (to be filled by reviewers)

[x] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[x] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[x] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #996 (5084d1e) into feature/sdkv2 (17cb5c7) will increase coverage by 0.05%.
The diff coverage is n/a.

@@                Coverage Diff                @@
##           feature/sdkv2     #996      +/-   ##
=================================================
+ Coverage          82.90%   82.95%   +0.05%
=================================================
  Files                296      296
  Lines               9841     9841
  Branches            1603     1603
=================================================
+ Hits                8158     8163       +5
+ Misses              1195     1193       -2
+ Partials             488      485       -3

Impacted Files
Coverage Δ

...android/rum/internal/ndk/DatadogNdkCrashHandler.kt
86.70% <0.00%> (-0.53%)
:arrow_down:

...rc/main/java/com/datadog/opentracing/DDTracer.java
55.65% <0.00%> (-0.42%)
:arrow_down:

...android/v2/core/internal/DatadogContextProvider.kt
81.03% <0.00%> (ø)

...rsistence/file/batch/PlainBatchFileReaderWriter.kt
91.18% <0.00%> (+5.88%)
:arrow_up:

...android/log/internal/logger/TelemetryLogHandler.kt
100.00% <0.00%> (+25.00%)
:arrow_up:


Error adding mask as alpha channel

Problem
Calling array_to_image using the array and mask returned from tile using a 4 band tiff returns an error:  WEBP driver doesn't support 5 bands. Must be 3 (RGB) or 4 (RGBA) bands.
Relevant code
# image at URL is 4 band geotiff
tile, mask = main.tile(url, int(tile_x), int(tile_y), int(tile_z), tilesize=256, nodata=None)
options = img_profiles["webp"]
buffer = utils.array_to_image(tile, mask=mask, img_format="webp", color_map=None, **options)

Possible Cause
It looks like utils:392 is just adding a band to the array without checking to see whether an alpha band already exists

👋 @a2hill sorry for this bug
I don't see a fix directly to the array_to_image function but to me it seems you could pass indexes=(1,2,3) to the data function and then the mask return should be the alpha band.
Handling nodata/mask/alpha band is a tricky thing (I've worked on the matter all the week), maybe utils.tile_read could remove the alpha band from the data array directly ?

@a2hill where you able to have your code fixed ?
I'm going to close this issue, but feel free to re-open if you have more questions.
Note: I've added a note in #63 to add more documentation about nodata/alpha handling.

@vincentsarago Yes we implemented additional check's for 4 band images and handle them differently. I think the older version of array_to_img used a has_alpha check, was that specific to PIL support?

@a2hill I'll need to check but maybe this https://github.com/cogeotiff/rio-tiler/blob/9aa45d68b08b116740792441405bd3003f4a1bd8/rio_tiler/utils.py#L537
was taking care of it because it forced the data to be 3bands.
I'm kinda happy/not happy about the situation but I do believe that using the new gdal based function let's the user do more thing (e.g enable to save GeoTIFF). But maybe we still could add a test for data that have more than 3 bands and not saved as 'GTiff'.

I agree, I like the new gdal based image function as well. I think it is going to be a lot more helpful with single band images as well. Previously I was having to do linear scaling to convert my dem's from float to uint8 but it looks like I no longer will need to do that with the gdal based function?

@a2hill well I think GDAL will throw an error if your data is not in uint8, before we had a test to cast the data to uint8 but again we removed it to let the user decide in their own implementation (mostly to support other format).

Ah okay nevermind then! Related but kind of off topic, are you planning support to allow color_map files which use the GDAL color configuration syntax?

@a2hill when I started working on the new function I tried to use the internal gdal method (https://github.com/mapbox/rasterio/blob/master/docs/topics/color.rst#writing-colormaps) but I couldn't get it to work (If I remember well my problem was that I had to first write the file to the disk before being able to see the colormap applied data.
I could have a second look later, but if you ever want to start a PR to update array_to_image or add a new function, please feel free.
Also I'm also happy to see how people use rio-tiler 😄

@vincentsarago Thanks for pointing that out. I may have a look at that as I am currently looking into integrating support for colorbrewer2 palettes via palettable for DEM's. If I find a better way to apply the color maps I'll be sure to submit a PR.


Rounded statusbar style not applied for selected window

Is there an existing issue outlining your problem?

[X] I have searched the existing issues and they do not solve my problem.

Describe your problem.
Hi!
Rouded window-status-style is not applied to current selected window. Is this expected behavior?
Paste your configuration.
# Catppuccin theme config
set -g @catppuccin_flavor 'macchiato'
set -g @catppuccin_window_status_style "rounded"
set -g @catppuccin_window_default_text " #W"
set -g @catppuccin_window_current_text " #W"
set -g @catppuccin_window_current_background "#{@thm_mauve}"

Attach screenshots.

What tmux version are you seeing the issue on?
tmux 3.5
Any additional comments?
No response

I'm unable to replicate this. Have you completely restarted the tmux server after changing your configuration?

@kjnsn I don't know what exacty the problem was, but after tweaking my config , killing tmux server and restarting, it started to work. I also deleted tmux plugin folder and fetched everything from scratch. And the theme styling was correct now.
Thanks!
In case anybody has the same issue, here's my current config which is partially built on another user:
# Catppuccin theme config
set -g @catppuccin_flavor 'macchiato'
set -g @catppuccin_window_status_style "rounded"
# Config from https://github.com/omerxx/dotfiles/blob/a2e5406eeb1e7854dc4b1149b618c01ed13a6c53/tmux/tmux.conf
set -g @catppuccin_window_number_position "right"
set -g @catppuccin_window_default_fill "number"
set -g @catppuccin_window_default_text "#W "
set -g @catppuccin_window_current_fill "number"
set -g @catppuccin_window_current_text "#W#{?window_zoomed_flag,() , }"
set -g @catppuccin_status_left_separator " "
set -g @catppuccin_status_right_separator " "
set -g @catppuccin_status_right_separator_inverse "no"
set -g @catppuccin_status_fill "icon"
set -g @catppuccin_status_connect_separator "no"
set -g @catppuccin_directory_text "#{b:pane_current_path}"
set -g @catppuccin_date_time_text "%H:%M"
# Top status bar config
set -g status-left "#{E:@catppuccin_status_session}"
set -g status-right "#{E:@catppuccin_status_application}"
set -ag status-right "#{E:@catppuccin_status_directory}"
set -ag status-right "#{E:@catppuccin_status_date_time}"

Which basically looks like this:

I have the same issue in my config
Does this line should do the work?  set -g @catppuccin_window_status_style "rounded"


Discord.py 2.0

So, discussed, elsewhere but not here, the v6 and v7 API decommission was pushed back to 2023 from earlier this year means the current version of Seance will be running for a good while yet, however there is still that impending sunset to consider.
Additionally, the 2.0 version of the discord.py API includes new features like bots sending stickers, and slash based commands (these could useful for more elegant config/message editing), which are worth investigating.
I'd be more than happy to explore an API update and new features, but wanted to reach out here and ask if there were any existing plans that I could contribute to, or a joint effort might be, a thing? Basically wanted to open the topic for discussion!

Hi there, sorry for the late reply. We're absolutely planning on migrating Séance to modern Discord API and Discord.py versions. A bare migration should be happening shortly, but as for using the more advanced features, there are some things to work out. Interactions could provide an excellent way to implement message editing and such, but for any server with more than one Séance bot added, each bot would then add its own version of the commands, causing lots of visually-duplicate commands.
I'm not sure how to work around this besides implementing a some sort of standalone daemon bot that globally handles slash commands and then forwards them to the appropriate Séance bots, but that sounds incredibly messy. Suggestions are definitely welcome for a cleaner solution.

So, my thought here isn't strictly one solved on the Seance bot side, but server integration configuration now allows you to limit access to slash commands to given roles. This could be used similarly to the current --ref-user-id argument to limit access to the slash commands and prevent this command collision. Of course this could still lead to mess for anyone handling multiple instances themselves, but I would say it can remove some degree of mess.
The other part would be to simply return to the --prefix style solution and have the bots bind their slash commands with a prefix. It might not stop the overall clutter problem, but could mean in a few character you can filter down to the slash commands on the intended bot.
Both would probably need some practical testing however. On a more general note I will be trying to put some more time into code soon if stuff stops being added to my plate so if the opportunity to contribute arises I'd be interested.


Allow Json file to be located when not at root of package folder (Replacement PR)

This is the replacement PR for the previous one.
It should consists of two file changes to PsfRuntime to fully allow the config.json file to be found, even when not at the root folder of a package.

Hey Tim,
Thank you for closing and re-opening the PR.  It is much cleaner.
I've looked over and added comments.  Address them when you can.  if you have any questions please let me know.
BTW.  All tests pass, we are good in that department.

Requested changes are all complete.


An error pops up after clicking the icon of 'Property Pages'

Environment

Steps to Reproduce
1.Launch VS and create empty c++ project

2.Click the icon of 'Property Pages'
Actual behavior
An error pops up

I sent an e-mail to the VS Extensibility Discussions group, since I'm not sure where to reroute this to. Once we create a bug for the appropriate team, I'll close this out since it's not ours to fix.

This is already tracked at https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1666489. Closing this out.


Extend EpMethodModification with the current package of the class

Currently EpMethodModification does not correctly indicate the name of the old package containing the method. This appears when working with extension methods.
Below the method testA was moved to the package FooC. Before the method was in the package FooA, however the oldMethod attribute of the event incorrectly indicates FooC as the package before and after the modification.

A workaround to be able to know the name of the package is to extend the Epicea event with the name of the package containing the class.

We now add the name of the package containing the class to the event. This makes it possible to determine the initial package moving a method to another package.

Patched in https://github.com/feenkcom/gt4changes/commit/5ab737

Related: https://github.com/pharo-project/pharo/issues/12208


Fixing the AJAX search issue

Description
I have fixed the error while searching when nothing is there in input.
Checklist

[x] I am making a proper pull request, not spam.
[x] I've checked the issue list before deciding what to submit.

Related Issues or Pull Requests
#109
This PR is regarding Hacktoberfest

@wasimreja ??


Update Travis configuration to use Build Stages

Travis configuration change, PyPi deploy through Build Stages.

Codecov Report

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

@@           Coverage Diff           @@
##           master       #3   +/-   ##
=======================================
  Coverage   84.29%   84.29%
=======================================
  Files           3        3
  Lines         363      363
  Branches       78       78
=======================================
  Hits          306      306
  Misses         53       53
  Partials        4        4

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 dab1209...0433130. Read the comment docs.


Requirements for SciKeras v0.2.0

This issue tracks what's required for SciKeras v0.2.0. Here are some of the more significant changes (which are possibly in progress):

[ ] Documentation: #73 (MUST implement)
[ ] class_weights parameter: #52  (SHOULD implement)
[ ] classes param for partial_fit: #69 (SHOULD implement)

I think we should include re-writing docs right?
As far as features, I don't think there's anything else that is needed.

[ ]  #52, which would provide a class_weights parameter
[ ]  #51 provide an epochs parameter
[ ]  #69, classes param for partial_fit.

@stsievert I think we can probably leave these for a future release, which I think leaves us just with documentation, but do we want to also think about the data conversion interface for this release? It would probably require some type of API change (only to the "new" APIs, not the "TF" APIs). I made #83 to track this. I feel that it may heavily influence how we address the loose ends in #79.

I think we can probably leave these for a future release, which I think leaves us just with documentation

I think documentation is the most pressing issue right now (I'm inclined to think it's blocking release). I don't think #51 or #52 rise to that level, though they'd be nice to have.

Agreed. #51 and #52 are certainly features and not bugs/API problems, so I think it's okay to leave them out. I will work on the docs over the next week or so.
Do you think we need to clean up data conversion handling (#83) before a release? There is at least one bug (#78) related to this, and I think this API may cross over with the compile API (in terms of the loss function affecting data reshaping).
Should we address some/all of the tasks in #79, or can we ship the compiling feature as is after #66?

I'm going to edit the OP to reflect that we have these two + documentation as the only remaining issues before a release.

@adriangb could you put the original post to put those changes back in? I'd rather not lose them, and I think they'll make a good release note summary.

Sure, I'll re-organize them. We have largely the same info in the v0.2.0 project you created I think.

We have largely the same info in the v0.2.0 project you created I think.

Not quite. I quickly abandoned that project because keeping notes in an issue is easier. One recent example: I added a note on a specific piece of documentation to include in https://github.com/adriangb/scikeras/pull/88#discussion_r503518283. I remember adding some other notes in other issues or PRs too, and linking to other issues (e.g., I think I mentioned #100).
In the future, I would greatly appreciate asking permission before deleting content I create, whether it be deleted by comment editing (e.g, this issue) or removing commits (i.e force-pushing). To my knowledge, no content has been lost due to force-pushing but it makes it harder for my to collaborate with you (I think in #93 I had to delete my local branch and recreate it).

Hey I hear you. I try to avoid force pushing to a great extent, and typically ask for permission before making changes to someone else's work (eg. in https://github.com/adriangb/scikeras/pull/93#issuecomment-704460428) especially since there are there are now regular collaborators in this repository (namely you).
I was editing this issue as well as the project, I thought it was duplicate information to some extent and was trying to simplify tasks to make things clearer for posterity; I'm sorry if I muddled things and made them harder.
Regarding the specific content of this OP, I restored it from your last edit, I do not see any mention of #100 in the edit history, but I am glad to add it.
In the future, I will refrain from editing any of your posts, unless expressly discussed on an edit-by-edit basis.
Finally, should we close the v0.2.0 project if it is not useful?

I restored it from your last edit

Thanks! That's news to me; I wasn't aware GitHub had that feature. That significantly reduces my concern.

should we close the v0.2.0 project if it is not useful?

Yea, I think we should. I don't look at it and it's more useful to have this channel of conversation.

I try to avoid force pushing to a great extent

When do you need to force push? When the server rejects my commits, I run git pull, resolve any merge conflicts, then run git push.

Yea, I think we should.

👍

When do you need to force push? When the server rejects my commits, I run git pull, resolve any merge conflicts, then run git push.

Almost never. I generally only ever do it when I end up with diverging branches and would rather start from scratch based on a diff than rebase and resolve conflicts (as I suspect may happen with #104 and #103 after #88 gets merged). I suspect in all cases some git kong fu would solve the issue.

would rather start from scratch based on a diff than rebase and resolve conflicts

Yeah, rebasing is not fun. I used to do it rather frequently, but try to avoid it now. I try to resolve merge conflicts instead of rebasing.

I'll give it a shot again this time around. Maybe I'll learn some new tricks along the way.

Final release notes:
Completed as part of this release:

[X] Add Keras parameters to BaseWrapper.init (loss, optimizer, etc) (#47, #55).
[X] Remove needless checks/array creation (#63, #59)
[X] Make pre/post processing functions public (#42).
[X] Some stability around BaseWrapper.__call__ (#35).
[X] Cleanup around loss names (#38, #35).
[X] Parameter routing (#67)
[X] Rename build_fn to model (with deprecation cycle).
[X] Check to make sure model compiled correctly. (#86, #100 pending #88)
[X] Compile if uncompiled model is returned (#66).
[x] class_weights parameter: #52
[x] classes param for partial_fit: #69
[x] #51 provide an epochs parameter
[x] Documentation: #58, #73

[x] Add doc page describing "unknown target type" as in https://github.com/adriangb/scikeras/pull/88/files#r503418037

[x] Check to make sure model compiled correctly. (#86)

Scheduled for future work:

[ ] Add more tests using sklearn classifiers/regressors that check output shapes and dtypes for different types of target types and target dtypes. Similar to the current test_multilabel_classification test (#119)
[ ]  #66: globbing / param groups for routed params (#118)

Closing this issue since v0.2.0 is merged.


Issue with nested structure

Hey
Nice project!
I'm just attempting to deserialize a nested structure (2 levels). I'm not sure whether this is supported(?) but I'm doing something similar with the csv serde and it just flattens the nested structure. Not sure whether something similar would be possible here or are nested structures supported by arrow/parquet?
Currently I'm getting the following error Error: Cannot add_field with event StartMap
Thanks

Apologies for the delay...
I ended up just flattening the structure then writing to parquet. Works like a charm!
Thanks

Nested structures are natively supported on the arrow2 branch. Close once released

Released with 0.6.0-rc.0


Where are the "usSharedData.h" & "usSharedLibrary.h" files I cannot find them anymore.

Can someone provide the information about what happened to these files. I need it with another project to compile and I used the latest version of CppMicroServices and somehow the linking is good but the compiler cannot find the files.
The version of CppMicroServices which is used by the old project is version 2.9.9 : https://phabricator.mitk.org/source/mitk/browse/develop/Modules/CppMicroServices/
What I would like to do is to adapt these files: https://phabricator.mitk.org/source/mitk/browse/develop/Modules/Core/include/mitkEventConfig.h
https://phabricator.mitk.org/source/mitk/browse/develop/Modules/CppMicroServices/core/src/util/usAtomicInt_p.h
https://phabricator.mitk.org/source/mitk/browse/develop/Modules/CppMicroServices/core/include/usSharedData.h
https://phabricator.mitk.org/source/mitk/browse/develop/Modules/CppMicroServices/core/include/usSharedLibrary.h
https://phabricator.mitk.org/source/mitk/browse/develop/Modules/CppMicroServices/core/src/util/usSharedLibrary.cpp
https://phabricator.mitk.org/source/mitk/browse/develop/Modules/CppMicroServices/core/src/util/usThreads_p.h
So that it is properly running with the latest version of CppMicroServices which is 3.6.0.
What are the changes or things I have to be careful about?

I started by this let me know if this makes sense : https://github.com/al-sabr/CTK/commits/ctk-blueberry-port-from-mitk last commits from today.

it sounds like you have to update the mitk project to use cppms 3.6.0. This is most likely a non-trivial amount of work since there have been many breaking changes since version 2.9.9.
A listing of the changes can be found in the changelog
you should also read the migration guide which also provides a list of what has changed from the context of converting code from cppms 2.x to 3.x.

I cannot find any infos about what happened to usSharedData.h but I can see that usSharedLibrary.h was renamed to SharedLibrary.h.
I renamed all instance referring to https://github.com/jeffdiclemente/CppMicroServices/issues/1 and https://github.com/CppMicroServices/CppMicroServices/issues/46
I see also that ModuleSettings.h & Auto loading are not documented how to transition...
https://github.com/CppMicroServices/CppMicroServices/pull/30
https://github.com/CppMicroServices/CppMicroServices/issues/75
Or no documentation inside of the Migration concerning this : https://github.com/CppMicroServices/CppMicroServices/issues/39
Also us::InterfaceMap.h is not there also what is the purpose of this? Is it replaced by AnyMap.h
I will need some assistance to achieve my port thank you for your feedback.

I also have created a link on the MITK bug tracker : https://phabricator.mitk.org/T28454
Can we reopen this thread so that we can follow up?


VM crash in co19/src/Language/Statements/Continue/async_loops_t10.dart

test4 results in seg fault.
test5 and test6 fail the listEquals check.

test4() crashes because the VM has a bug in finally-block inlining with unresolved forward references of switch case labels.
The jump target of the 'continue L' statement is unresolved when parsed. The VM assumes it's a forward reference within the same switch statement, and thus does not inline the enclosing finally blocks. However, the forward reference is to a switch case outside the finally blocks (implicitly defined by await-for).

CL https://codereview.chromium.org/2030763002/ fixes this. The implicit finally clauses of the await-for statements were not inlined in front of the forward jump to the outer switch statement.

Fixed in 1859ce46c337e4e047e6543c561ff77af7910074


Some fields are not translated?

[v4]
It seems some fields are not translated, and the translation is not coming from iD presets? PT-BR in EveryDoor is 100% translated on Weblate (by me).
What I can see in English, that should be in PT-BR:

Room Number
Postcode
Elevation (Meters)
Levels
mobile

Is this an Every Door mistake or iD Preset? I remember seeing those fields translated on iD, but I might be wrong!

"Room Number" and "Postcode" are indeed not yet translatable. The other three come from presets, I guess.

In 4.1, I've changed Room Number to be taken from presets, and for Postcode, it's pretty hard to make it translatable, since there is no preset for this field alone.

Great! I just checked on Transifex, and it seems all of these fields are available on the iD Presets (although I'm not sure how it can be used on the fields). And I also checked PT-BR translations, those fields were already translated.

Update (which is probably known to you, Ilya, but just to make it easier for future fixes:
What I can see in English, that should be in PT-BR:
Postcode
Elevation (Meters)
Levels

Postcode is still untranslatable, but Levels and Elevation come from presets, there are no such strings in the code.

Don't know then what's the cause, because I checked the Presets translations and it's translated there for ages :(
(you can check in EveryDoor, in all languages have "Elevation" and "Levels")

Translated for me (the second and the third line). Are you looking at 5.1-beta2?

Actually here's pt-BR locale.

That's odd! iOS here, 5.1-beta2:

Oh! I see, this is related to references inside the fields files. And I guess this is a bug. I'll see what I can do.

Fixed in 5.1, including the postcode!


THRIFT-2925 CMake build does not work with OpenSSL nor anything installe...

...d in non-system location
This diff fixes them by correcting invalid CMake variable names:

OPENSSL_... rather than OpenSSL_...
LIBEVENT_... rather than Libevent_...
Boost_INCLUDE_DIRS rather than Boost_INCLUDE_DIR
LIBEVENT_INCLUDE_DIRS rather than LIBEVENT_INCLUDE_DIR
ZLIB_INCLUDE_DIRS rather than ZLIB_INCLUDE_DIR

Note:

OPENSSL_INCLUDE_DIR is correct (rather than ..._DIRS)
Boost_INCLUDE_DIR exists and actually works for most cases but
Boost_INCLUDE_DIRS is the one desinged to be included

Also, library headers are now included as SYSTEM headers.

Merged as c444fb581d2157c260f36db091a7cdd4511c6e32, thanks :)


Validation issue on scss / js

While validating scss and js we have to change few classes used on js and css and replace "__" with "--".
Can we have this updated so we can use script with npm and can validation using lint-sass
I can help and submit PR if needed

Sorry, I'm going to have to reject this ticket. Doing this would destroy any existing themes and would be a major backwards-incompatible change.
If sass-lint or lint-sass is claiming that the classes are invalid... well, they aren't. They're valid BEM using a less-commonly-used syntax of SASS to generate them. Add an exclusion for the Select2 files if you need to.


github action fails to find python entrypoint

Github action update seems not to work.

The log from sbomify backend ci-cd action
Run sbomify/github-action@master
/usr/bin/docker run --name a69ae2f9ca213944412290c39b1cf92cda67_879e8f --label 43a69a --workdir /github/workspace --rm -e "SBOMASM_VERSION" -e "TOKEN" -e "COMPONENT_ID" -e "SBOM_FILE" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_ENVIRONMENT" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e "ACTIONS_RESULTS_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/backend/backend":"/github/workspace" 43a69a:e2f9ca213944412290c39b1cf92cda67
Creating virtualenv sbomify-cDQ_M3T8-py3.12 in /github/home/.cache/pypoetry/virtualenvs
/github/home/.cache/pypoetry/virtualenvs/sbomify-cDQ_M3T8-py3.12/bin/python: can't open file '/github/workspace/entrypoint.py': [Errno 2] No such file or directory

Interesting. I need to add a check for that. Decided to all unit tests outside of docker for speed but maybe I should change that.


Move PostgreSQL storage implementation to grafeas-pgsql

Is your feature request related to a problem? Please describe.
For consistency with the Grafeas architecture, we'd like to move the PostgreSQL storage implementation to its own project, grafeas-pgsql.
Describe the solution you'd like

Move pgsqlstore.go to grafeas-pgsql.
Re-build the Grafeas server with the PostgreSQL storage.

Describe alternatives you've considered
For now, it's part of the Grafeas project, but going forward we'd like to keep the project scope limited to the API.

I can help with this issue

That'd be fantastic, thank you, @judavi!

I can resume the work on this issue based on the experience that I got working on Grafeas-oracle

That'd be great, thanks, @judavi!

Wondering if this has moved much more? I'm looking for a way to jump in and help with the codebase a bit more.


Adopt tox-travis

tox-travis is a plugin for tox that simplifies the setup between tox and Travis. For simpler projects, it makes it trivial to test against various Python versions. The django-nose configuration is more complex:

Test each Django release

Against each supported Python version

And each combo of SQLite, MySQL, and PostgreSQL

This may be possible with the Advanced Configuration.
The alternative, of a carefully constructed test matrix in .travis.yml, is repetitive, yet error prone when dropping or adding support, versus the tox notation for specifying variants:
https://github.com/jazzband/django-nose/blob/c48bd0e6b8e0f4c25af17feb83f1f06f3ce0254e/tox.ini#L1-L10

This is moot due to #317 which also used tox-gh-actions.


Add regions

The following regions are added:
us-west1
us-east1
asia-northeast1

Hi @mbrukman! Good to hear from you.
I pushed a change that hopefully works for you. I can't figure out github reviews so hopefully you see this note! :)
I plan on backporting this change, along with the two changes we put in yesterday, to the development-1.0 branch, since we're actively working on including them all in the upcoming Director release. Let me know if that poses any problems for you. Thanks!

Apologies for the delay and thanks for sorting the regions! Looks great.


Turn camel case + hyphen into CPAN release link

How is this?

Questhub is gone so I'm closing this.


GeoZarr Extension

Dear Community,
In the context of an European Space Agency (ESA) GSTP (General Support Technology Programme) we prepared a first draft for a geospatial extension to Zarr (GeoZarr).
This specification is an early draft (v0.1) and a prototype implementation of GeoZarr-based (and Cloud based) geospatial data store has been demonstrated to the Agency in the frame of the project. We are also developing a map viewer (based on OpenLayers) to demonstrate multiscaling and integration of the store in an Earth Observation catalogue.
If you have any interest in Space domain, we would be very interested to get your feedback and ideas to consolidate this extension. We mostly based the specification on what xarray already supports.
Here is the repository: https://github.com/christophenoel/geozarr-spec/blob/main/geozarr-spec.md
Kind regards,
Christophe Noël, Spacebel.

Have gone ahead and transferred this issue to zarr-specs since it seems like we are ok with that

@christophenoel, I've just added https://github.com/zarr-developers/zarr-specs/issues/125 which will be ramping up over the course of the next week or two. Hopefully this would help us to refactor any of the shared issues from the multiscale conventions into a shared document.

It would be great to align efforts. I will try to review your spec over the next week.
Hi Ryan, it tried to reach you by email unsuccessfully. I will be working on this by mid february.

Dear all,
I'm very happy to share with you a first bunch of resources (presentatins, demos) presenting the project, and showing the assets of GeoZarr.
We finally refined the multiscales support and recently introduced visual portrayals and symbology (see OGC WMS SLD) directly in the data to facilitate the display on map viewers.
I hope this helps !
Christophe.

Specification Document - Change Log
Demonstration Videos (Youtube channel):

Project Presentation (at WGISS-53) GeoZarr Data Store - Context of the ESA GSTP project
Project Presentation (at DAP) Hyperspectral Data Store and Access Project
Demo: GeoZarr Visual Portrayals and OpenLayers extension
Demo: GeoZarr Fast Time Series Plotting
Demo: GeoZarr Compute and plot NDWI index at runtime
Demo: GeoZarr Catalogue Integration
Demo: GeoZarr Serverless Visualisation and Pixel-Based Access
Comparison: GeoZarr vs COG Performances

OpenLayers extension prototype: https://github.com/spacebel/geozarr-openlayers

That's very interesting!

Thanks, @christophenoel. :+1: I've passed your comment on to the github.com/ome/ngff folks as well. You might be interested in further iterations to the OME-Zarr spec built on top of multiscales, e.g. Transformation types from @bogovicj. If you have any thoughts or just general interest in discussing ways of sharing updates to a base spec, let me/us know, here or possibly at a regular community call (which happens to be today).
All the best,
~Josh

@christophenoel: you might be interested in https://github.com/ome/ngff/pull/114 which resulted from discussion with various xarray-affine folks.
cc: @thewtex @malmans2 @TomNicholas @aurghs

Can this be closed in light of: https://github.com/zarr-developers/geozarr-spec


docs: fix incorrect hasOne example

I believe the very first example in relations documentation is incorrect. As Profile has a foreign key to User, the respective relation should be declared with belongsTo rather than hasOne?

Right, thanks for correcting!


Excluding all rules

Implement excluding all rules as dictated in section 6.3 of the standard.

Migrated from BitBucket.


[release-1.2] Allow modifications to VM spec during VM snapshot, except disks/volumes

Manual backport of pull request #13001
Relaxed check on modify VM spec during VM snapshot to only check disks/volumes

/test pull-kubevirt-e2e-k8s-1.29-sig-storage-1.2

/lgtm
/approve

/cherrypick release-1.1


Detailed control of auto exposure (application: low light motion capture)

Hi,
We are experiencing issues with the auto exposure on OAK-D in low-light situations with moderate motion. The resulting images are blurred. Would it be possible to modify the auto-exposure behavior to cap the exposure time? I've tried tweaking the exposure compensation integer, but haven't gotten the results I'd like. What does this compensation integer value do? I haven't been able to find any documentation for it.

(CC: @alex-luxonis)

Hi @oysstu,
You can find a good description of the AE compensation parameter, that matches our usage (-9 .. +9 range, 0.333 EV step, resulting -3 .. +3 EV range) here:
https://developer.android.com/reference/android/hardware/camera2/CaptureRequest#CONTROL_AE_EXPOSURE_COMPENSATION
We'll work on getting this better documented in our docs as well.
More details on how it adjusts the AE target exposure, depending on the value set:

positive → applied as post-gain in ISP, i.e the sensor exposure and gain (gain=iso/100) doesn't change, but digital gain is set in ISP processing;
negative → applied on sensor as exposure and/or gain change.

However, auto-exposure is currently implemented in the camera tuning database is by prioritizing the increase of exposure time  vs. increasing the gain, as in this graph:

So in low-light, first the exposure is applied until the max is reached (and this causes motion blur), then gain starts to increase.
This behavior is slightly affected by the anti-banding/anti-flicker config (default enabled for 50Hz mains), that sets an exposure in multiples of 1/2 of mains period. So for 50Hz, 1/2 * 20ms = 10ms, resulting in effective exposure times of:
fine-grained if < 10ms, 10ms, 20ms, 30ms.
For your use-case, either manual exposure can be used (but I understand this may not be desirable), or we could try to create a custom tuning where gain is preferred over exposure time.

Great, thanks for the detailed response, that explains why the auto exposure compensation did not give the expected results. Obviously, running the AE algorithm on the hardware would be best, both due to latency and offloading computations. I'm not sure what a custom tuning entails, but if it works it's definitely an option. I'm guessing this is part of some low level hardware/firmware blob, and not the open source components?

Upon further testing, it seems that the mono cameras are not able to push the exposure time low enough to avoid motion blur, without becoming excessively dark, even at ISO=1600. At exposure times below 20000us, even our brightly lit offices are almost pitch black. Do you have any final recommendations before closing this issue?

We actually have an active illumination version of OAK-D called OAK-D-Pro which may be of interest here:
https://shop.luxonis.com/collections/beta-store/products/oak-d-pro
Often for fast-moving objects it is necessary to have active illumination as otherwise yes motion blur will occur.  Global shutter hits all pixels at the same time, so there isn't tearing/jello - but the amount of motion during the exposure time still is what will dictate the amount of motion blur.


Upgrade aws-sdk-core for eager_autoload support

Looks like the only changes around SNS are https://github.com/aws/aws-sdk-ruby/blob/master/CHANGELOG.md#2031-2015-03-19 and https://github.com/aws/aws-sdk-ruby/blob/master/CHANGELOG.md#2034-2015-04-02 and they are minor / new features.
I think we are good with this upgrade. Tests are all :white_check_mark: for me, locally.


No results returned 1.6.14

Hi
I'm using 1.6.14.
Code:

googlenews = GoogleNews()

googlenews = GoogleNews(lang='en')
googlenews = GoogleNews(period='1h')
googlenews.get_news('PS4 PS5 PlayStation')

But there are no results returned.

googlenews = GoogleNews(lang='en',period='1h')
googlenews.get_news('PS4 PS5 PlayStation')
googlenews.results()


Won't install on angular 13

It seems like your angular 16 upgrades have now rendered v3 only compatible with 16.2.0.
Can you resolve this please.

Happy to do this! But the original package that I forked from still supports Angular v13 -- I'd suggest using that
I'll happily fix the versioning over the weekend though if you want to continue using this 👍

The original package also has issues within the dependancies, it incorrectly states bootstrap requirements using caret versioning instead of greater than (even though the documentation clearly states greater than). I've left comments on the original library but not sure how quick they will update.
If you can fix the versioning that would be super helpful, i've installed using force for now but would love to retain use long term without needing to do that.
Thanks!


Add generateURI option for customizing URIs

This allows generating custom URIs without having to add additional build steps. It could potentially replace the prepend option, but I feel they are complementary at this point in time. Since prepend is really about "where" the entries are coming from.

I'm unsure we wish to expose prepend to the user? It feels to me like generateURI should receive the asset after that path.join (which they don't have any control over) and then should get to munge it as they see fit.
Other things, I'm mildly uncomfortable that the function will capture a lot of things in its closure. I'd rather try to force it to be a pure transform without state, but that's against current option patterns, so /shrug.

I'm unsure we wish to expose prepend to the user? It feels to me like generateURI should receive the asset after that path.join (which they don't have any control over) and then should get to munge it as they see fit.

Makes sense. I literally just wrapped a function around what was happening before, but I think this approach makes more sense.
As for the closure issue, I don't see much way of avoiding that without jumping through a bunch of hoops.

So the only change then is to:
- uri: generateURI(prepend, entry),
+ uri: generateURI(path.join(prepend, entry)),

And tweak some docs.


Provide a way to run service code out of I/O event loops

Motivation:
When service devs are not very familiar with asynchronous programming, it is very easy to drive Armeria's core event loops into havoc by blocking them.
Framework devs may want to make sure Armeria at least handle I/O and function normally for a certain set of core services, such as PrometheusExpositionService or HealthCheckService, by isolating other non-core services from the I/O event loops.
Modifications:

Add the serviceWorkerGroup() builder methods to ServerBuilder and ServiceConfigSetters so a user can specify the service worker groups as shown in the above example.

If serviceWorkerGroup is not specified, the workerGroup is used by default.

Change how Armeria assigns an event loop to a ServiceRequestContext.

If the workerGroup is different from serviceWorkerGroup, then an event loop from serviceWorkerGroup is used.

Otherwise, the IO event loop is used for executing services

Modified the constructor of DefaultServiceRequestContext so it accepts an EventLoop.
Modified HttpServerHandler.handleRequest(), so that HttpService#serve is executed from the serviceWorkerGroup
Modified so that we can guarantee that pending RequestLogFutures are always scheduled from the context's event loop

Result:

Closes #4099.
Users can add per-service/virtual host/server serviceWorkerGroup property that makes a service use a different EventLoopGroup than ServerBuilder.workerGroup.

Thanks @kezhenxu94 for your initial effort. 🙇♂

With this new feature, does it make sense to allocate separate worker groups for error handling (i.e. Sentry), logging or tracing (Open Telemetry) related functionality? We use decorators to do those most of the time.

Decorators will share the same worker group with services which the decorators bind to.
Do you want to isolate some background jobs from service works?

Decorators will share the same worker group with services which the decorators bind to. Do you want to isolate some background jobs from service worker groups?

I wanted to separate where decorators run which are responsible for error reporting, logging tracing etc. Because I am afraid the underlying libraries we use are probably making unsafe calls. Prometheus service was an example that was a service rather than a decorator.
I think I have misunderstood what this PR achieves. This seem like per service (or vh) configuration rather than a decorator configuration.

This seem like per service (or vh) configuration rather than a decorator configuration.

Correct.
We don't have a plan to provide an option to bind a custom executor to a decorator at the moment. There was no request for that. If necessary, we need to change the way of decorator composition which is composed using Function. As a result, it is difficult to inject a scheduler to change the working thread.

Because I am afraid the underlying libraries we use are probably making unsafe calls.

Good point. In that case, the jobs have a separate executor to do the work. That said, most unsafe calls will caught in testing or development environments with the BlockHound agent.


Versioning

I was about to make a cut of Racer this morning and realized that we've changed a public API in an incompatible way. Specifically, we landed #498 which removed some unsafe code related to the FileCache. This was a very welcome patch of course, but it means we can't release from master without bumping the major version.
Options:

Revert the FileCache change. This is probably no longer easy to do since there's been quite a few changes to master.
Actually cut a 2.0. This isn't exactly great since there's a lot of other API work that could be done, but it would allow us to move forward with minimal effort.
Add a FileCache shim. This could expose an API matching the old FileCache, but it's pure technical debt. The shim would be thrown out when we actually

I'm inclined to just cut a version 2.0. This is the simplest option, there's just one type with breaking changes (so upgrading is easy), and there's really no limit to how many major versions we can have.
There's a bunch of fixes on master that really ought to be released, and there's more on the way. Assuming we release a 2.0 now, I would want to figure out what a minimal API we can commit to for 3.0 would look like and hold off on breaking changes until that's decided. Until then, the focus would be on backwards compatible changes like increasing stability and making racer work for more cases.
@phildawes, thoughts?

Hello! Does anything other than racerd use this api? I think the other plugins just use the command line interface. If that's true, then probably best to cut a 1.3 and not worry about it too much.
(I'm happy for a 2.0 release if you think it's warranted though)

Interesting thought! I think most integrations are using either the CLI, stdio pipe, or racerd. Thanks, Phil.
@nrc, does RLS use the FileCache API?

Not really. Our entry point to Racer is complete_from_file. We do create an empty FileCache, but only to make a Session which we pass to complete_from_file, we don't use any functionality beyond that.

@nrc thanks for the input
After thinking on this a bit (and reading comments in futures-rs#160), I think we should go for a 2.0 just to avoid any unexpected breakage. With that, I'd like to reduce the public API to a minimal set of things needed to make completions and etc; hopefully doing so will make this less likely to happen again.

I've got most of the 2.0 API worked out at this point, and I'll hopefully be submitting a patch for review tomorrow. The command line and daemon APIs will remain unchanged, and there are minor changes to how Rust code integrates with Racer (simpler). The main thing to look forward to in the patch will be a very narrow public API which will allow us to iterate quickly on Racer internals. There's also a number of fixes on master that will become available once we can publish to crates.io without inadvertently breaking anyone's code :).


Multiple resource-based authorization handlers in ASP.NET MVC 6

I want to have two resource-based authorization handlers like so.
public class FooAuthorizationHandler :
           AuthorizationHandler<OperationAuthorizationRequirement, Foo>
{
   protected override void	Handle(AuthorizationContext context,
                  OperationAuthorizationRequirement requirement, Foo foo)
   {
       // Do something here using context.User and foo
   }
}

public class BarAuthorizationHandler :
           AuthorizationHandler<OperationAuthorizationRequirement, Bar>
{
   protected override void	Handle(AuthorizationContext context,
                  OperationAuthorizationRequirement requirement, Bar bar)
   {
       // Do something here using context.User and bar
   }
}

I added the following lines in the ConfigureServices method of StartUp.
services.AddInstance<IAuthorizationHandler>(new FooAuthorizationHandler());
services.AddInstance<IAuthorizationHandler>(new BarAuthorizationHandler());

In my controller, I have the IAuthorizationService dependency like so and I call the AuthorizeAsyncmethod.
public class FooController
{
   IAuthorizationService authorizationService;

   public ValuesController(IAuthorizationService authorizationService)
   {
      this.authorizationService = authorizationService;
   }

   [ActionContext]
   public ActionContext ActionContext { get; set; }

   public async Task<string> SomeAction()
	{
	    var foo = new Foo();
	    bool result = await authorizationService.AuthorizeAsync(
                                ActionContext.HttpContext.User,
                                foo,
                                new OperationAuthorizationRequirement {
                                                   Name = "FooCheck" });

	    return "hello";
    }
}

With the AuthorizeAsync call, both the handlers run. I want to make sure only the FooHandler runs when I call AuthorizeAsync from FooController and BarHandler to run when I do the same from BarController. Basically I want to have more than one resource-based authorization handler. What is the right approach to accomplish what I want to? What am I doing wrong here?

I can re-produce that as well - I have to handlers (one for customer, one for product) - and the authorize call for product also triggers the Handle method of the customer handler.
My rep(r)o is here:
https://github.com/leastprivilege/AspNet5AuthorizationPlayground

This makes it pretty much un-usable. Any comment?

@HaoK we think this is a dup, can you find it and close this against that one?

Found it: Dup of https://github.com/aspnet/Security/issues/494


[Addon Action in v5]: The arguments are not longer decycled

Describe the bug
The arguments are not longer decycled in v5. The source code in v4 had a whole decycle function taking care of conficting arguments, this and is now gone in v5.
To Reproduce
Steps to reproduce the behavior:

Try to log an action with a cycled argument (with circular references).

Expected behavior
I would expect this change to have been documented and a workaround provided.
Additional context
I tried using some 3rd party decycle but they are not working as expected.

@ndelangen Did de-cycling break in telejson?

For the reference the errors I am getting are related to a non existing toJSON function in my argument objects. Which is actually not about circular references, but in v4 this was working fine.

I was able to reproduce this on a simpler configuration and so far I can only confirm is happening with the Vue version. Creating a simple story and trying to log the story vue instance would trigger the toJSON error. Ex
<template>
    <div>
        <button class="btn btn-primary" type="button" @click="trigger()">Action</button>
    </div>
</template>

<script>
import {action} from '@storybook/addon-actions';

export default {
    methods: {
        trigger(event, params) {
            action('test')([this]);
        }
    }
};
</script>

cc @ndelangen

Is this still an issue? cc @ndelangen

Is there any interest in solving this?

@miljan-aleksic Yes do you want to take a crack at it?

@shilman, our solution was to implement the SB 4.x decycle into SB5, I don't think that would be accepted. As for working on a real solution I would need to speak with the guy who made this change in the first place, or someone who knows the motivations behind.
Anyway, I would start by adding some more tests, this would not happen with them in place.

Thanks @miljan-aleksic. Hopefully @ndelangen sees these mentions and can help you get these changes in.

Sorry for the delay, @miljan-aleksic I'd be available to chat about the needed changes, join me on discord? https://discord.gg/sMFvFsG

@ndelangen, I did :)

I'm on it

After debugging this with @ndelangen it turns out to be a Vuejs specific issue when a Vue instance is attempted to be serialized. The Telejson library will attempt to use JSON.stringify on the Vue instance object which will expect the toJSON method to exist, as it does not Vue will warn about a undeclared method being referenced during render.
Serializing a Vue instance is not supported and most likely will never be, and as such it must be addressed by Storybook. Fairly enough is quite simple, and even though it looks like a hack is actually the suggested way of extending Vue:
Vue.prototype.toJSON = function () {
    return this;
};

This issue can be reproduced in the current Storybook Vue kitchen sink example, triggered by specifically this lines. I stay available for further help on this matter.


Hello, author

Does WhatsApp have an interface to synchronize contacts? I think IOS can use contacts to synchronize, but not on Android devices. I don't see the interface to synchronize contacts on your device

Yeah, it does. If you need any help to use it comment on this issue


Repeatable migrations

Opening to preserver changeset.

Adding to https://github.com/cakephp/phinx/wiki/Help-wanted for now


Fix Denial Of Service

📊 Metadata *
Please enter the direct URL for this bounty on huntr.dev. This is compulsory and will help us process your bounty submission quicker.
Bounty URL: https://www.huntr.dev/app/bounties/open/1-npm-metascraper-helpers
⚙ Description *
Affected versions of this package are vulnerable to Denial of Service. An attacker providing a very long string to isUrl function in packages/metascraper-helpers/index.js can cause a Denial of Service. The proposed will introduce a new package is-valid-http with a same functionalities but secure
💻 Technical Description *
I have found so many vulnerabilities that I have to introduce a new npm package with the same functionalities is-valid-http.
🐛 Proof of Concept (PoC) *
PoC
const { isUrl } = require('@metascraper/helpers')

const targetUrl = 'http://github.com.asdasdasd.asdsadasdsadsad.asdasdsad.asdsadasdsa.sadasdsadas.dasdasasdasd.432asdas3423.3423423423.234234243.234234234.23423423.24234.'

if (!isUrl(targetUrl)) {
      throw new Error('INVALID_URL')};

🔥 Proof of Fix (PoF) *
const { isUrl } = require('@metascraper/helpers')

const targetUrl = 'http://github.com.asdasdasd.asdsadasdsadsad.asdasdsad.asdsadasdsa.sadasdsadas.dasdasasdasd.432asdas3423.3423423423.234234243.234234234.23423423.24234.'

if (!isUrl(targetUrl)) {
      throw new Error('INVALID_URL')};

👍 User Acceptance Testing (UAT)
mocha test/index.js

The disclosure was not valid and therefore closing this pull request.
If you have any questions (@Hbkhan), please get in touch! 🍰

Sorry Hbkhan, we enjoyed reviewing your fix but it has not been selected this time. If this bounty has not been closed, please feel free to try again with a new pull request!
We appreciate your effort and look forward to reviewing more of your fixes in the future! 🔨😎


Allow product icon themes to override icons defined in contribute entries of an extension

Extensions can add contributes entries of which some accept custom icons. For example, take the vscode-bookmarks extensions, which defines a contribution endpoint for viewsContainers in its package.json:
"contributes": {
    "viewsContainers": {
        "activitybar": [
            {
                "id": "bookmarks",
                "title": "%bookmarks.activitybar.title%",
                "icon": "images/bookmark-activity-bar.svg"
            }
        ]
    },
}

This adds an entry to the activity bar with a provided custom icon to access the view. However, this icon cannot be overridden by a product icon theme.
Since product icon themes can provide new icons for the built-in codicons, of which icons are used for the 'standard' activity bar items, an extension's activity bar icon could be overridden to match the theme's style.
This use-case applies to all of the following, which allow an extension author to define custom icons:

contributes.commands
contributes.languages
contributes.views
contributes.viewsContainers

Food for thought is how to define the entrypoints for icons. I was thinking along the lines of adding a new key(s) to a product icon definition file "commands", "languages", "views", "viewsContainers". But then how would one reliably set the icons? Use extension ID in combination with the ID defined in one of those contribution entrypoints?
Would love to hear input from the VSCode team, and if if this use-case would be considered an in-scope issue,

If an extension want's that their icon(s) is/are themable, it should not use a SVG but a product icon:
        "activitybar": [
            {
                "id": "bookmarks",
                "title": "%bookmarks.activitybar.title%",
                "icon": "${bookmark-view-icon}"
            }
        ]

Extensions can define new product icons with the icon contribution point
"contributes": {
  "icons": {
        "bookmark-view-icon": {
            "description": "View icon for the bookmarks view",
            "default": {
                "fontPath": "./bookmark-icons.woff",
                "fontCharacter": "\\E001"
            }
        }
    }
}

With that, any product icon can define a customized bookmark icon by defining a new icon for bookmark-view-icon.
The crux is of course that a product icon theme would have to know and cares about the bookmark extension. But if the extension is very popular that might happen. Also, a user might file an issue against the product icon theme requesting a extension the be better supported.
I don't see any other way.
I hope I property understood your request.

I don't see any other way. I hope I property understood your request.

Yes, the request was understood perfectly, so we're on the same line.

The crux is of course that a product icon theme would have to know and cares about the bookmark extension. But if the extension is very popular that might happen. Also, a user might file an issue against the product icon theme requesting a extension the be better supported

Yes, this of course will always be the case so there's no problem here.
Indeed the solution proposed in your comment is (and should be) the solution to the described problem. I made the assumption that VSCode's contribution point API was not capable of this, so you've cleared that up.
From this point onwards it's clearly the responsibility of extension authors (or those who provide pull requests) to change the hardcoded icons to product icons.
I could probably argue to deprecate providing a hardcoded icon in the contribution API but I think nobody is waiting on that. Perhaps updating the documentation on the contribution point API page to show/encourage using newly defined product icons would be a good idea though.
I don't need any further information and an acceptable solution is already possible. If no further discussion is warranted, the issue can be closed.

Thanks for reply and feedback. You are right, it would be reasonable to deprecate SVG icons, they have other limitations too (e.g. we can't easily change the color). We haven't done that (yet) as contributing a icon is not that trivial as a font need to be created.
Closing the issue then


chore: update penumbra version to v0.77.3

Describe your changes
Refs #4648. Also, given #4562, CI should be fast on this PR.
Issue ticket number and link
Checklist before requesting a review

[x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

docs-only

Also, given https://github.com/penumbra-zone/penumbra/pull/4562, CI should be fast on this PR.

Noticed some trouble here:

but tacked on a fix commit to address. Will watch next time i changed the docs on main.


The resourceVersion defined as int make Python client code fail.

The resourceVersion is defined as int in swagger-spec which make Python client code to fail with TypeError('int' object is not iterable)

I will recommend filing a bug with swagger-codegen on this.
I dont see anything that we can do abut this in kubernetes.

resourceVersion is defined as string in v1beta3.

So I think  we need ot change this in v1beta1 also. RIght?

No, we can't change it in v1beta1 in order to preserve backward compatibility, though v1beta1 is also approaching its end of life.
More about our approach to API versioning can be found here:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/api.md
Sorry, I didn't mean to derail discussion of the problem that was reported.
resourceVersion in what object(s)?
The most recent version of our swagger output has:
     "resourceVersion": {
      "$ref": "uint64",
     },

which is definitely not right. This looks like a bug in the swagger-generation library we're using:
https://github.com/emicklei/go-restful/blob/master/swagger/model_builder.go#L250
Is that what it looks like in whatever version you're targeting? We've been making quite a few changes recently.
But I don't understand what the error you reported means.

Maybe because $ref is specified rather than type, the generated python is either trying to iterate over the value or over the type definition as if it were a map/list.
cc @brendandburns, since he said he might take a look at swagger-codegen.

I see:
"resourceVersion": {
      "type": "string",
      "description": "string that identifies the internal version of this object that can be used by clients to determine when objects have changed; populated by the system, read-only; value must be treated as opaque by clients and passed unmodified back to the server: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/api-conventions.md#concurrency-control-and-consistency"
     },

in https://github.com/GoogleCloudPlatform/kubernetes/blob/master/api/swagger-spec/v1beta3.json

Yes, uint64 is v1beta1.

Yes, bgrant is right. But I think this issue is fixed in master now.


What version of .NET Core does this repo build?

I just managed to run this successfully and took a look at the output:
$ git rev-parse HEAD
1b1fbed07487d0c864ee0fc4d34c47e5a9c56935

$ ls bin/x64/Release/*
bin/x64/Release/dotnet-sdk-2.0.0-preview3-006908-linux-x64.tar.gz
bin/x64/Release/dotnet-sdk-debug-2.0.0-preview3-006908-linux-x64.tar.gz
bin/x64/Release/dotnet-sdk-internal-2.0.0-preview3-006908-linux-x64.tar.gz
bin/x64/Release/dotnet-sdk-langpack-2.0.0-preview3-006908-linux-x64.tar.gz

The built binary says both preview3 and 2.0.0 (final):
$ ./dotnet --info
.NET Command Line Tools (2.0.0-preview3-006908)

Product Information:
 Version:            2.0.0-preview3-006908
 Commit SHA-1 hash:  38031f6e5c

Runtime Environment:
 OS Name:     fedora
 OS Version:  26
 OS Platform: Linux
 RID:         fedora.26-x64
 Base Path:   /home/omajid/devel/dotnet/source-build/dotnet/sdk/2.0.0-preview3-006908/

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0
  Build    : 82b22fa44e46d624ebeddf156f33e9cfb317bd57

Is this repository supposed to build 2.0.0? Or A pre-release version of the upcoming 2.0.x update? Or A pre-release version of 2.1?

Hey @omajid, I think you're talking about the master branch and the release monikers have not yet been updated. The intention is for source-build to track with the various master branches (coreclr, cli, etc). We'll get this updated.

Thanks. That clears things up. I thought master here was tracking the 2.0 release and I was really confused.


How do I change the navigation programmatically when using vue js?

I tried using
<BottomNavigation ref="bottomNav" ></BottomNavigation>
in my script
this.$refs.bottomNav.selectTab(1), but it doesn't work
Using it in my nativescript vue project

Hi,
What is the error message?

selectTab is not a function

sorry for the delay but you can access the methods doing this:
<BottomNavigation ref="bottomNav" ></BottomNavigation>

and in your javascript
const bottomNav = this.$refs.bottomNav.nativeView;
bottomNav.selectTab(1);

try above  code but it's not working it's throw  error
"TypeError: Cannot read property 'setCurrentItem' of undefined"
for more info check below code
<template>
  <BottomNavigation
    ref="bottomNav"
    activeColor="blue"
    inactiveColor="gray"
    backgroundColor="white"
    titleVisibility="always"
    @tabSelected="onBottomNavigationTabSelected"
  >
    <BottomNavigationTab title="Inbox" icon="ic_inbox"/>
    <BottomNavigationTab title="Favorite" icon="ic_heart"/>
    <BottomNavigationTab title="Message" icon="ic_mail"/>
    <BottomNavigationTab title="Settings" icon="ic_settings"/>
  </BottomNavigation>
</template>

<script>
export default {
  data() {
    return {};
  },
  mounted(){
       const bottomNav = this.$refs.bottomNav.nativeView;
    bottomNav.selectTab(1);
  },
}
</script>

you need to execute that method when the component (BottomNavigation) loads, you are executing that logic when the page is loaded that’s why you are having that error.
u should use the @loaded event in the component

try as you say but now it's goes in infinite
<template>
  <BottomNavigation
    ref="bottomNav"
    activeColor="blue"
    inactiveColor="gray"
    backgroundColor="white"
    titleVisibility="always"
    @tabSelected="onBottomNavigationTabSelected"
    @loaded="setActiveTab"
  >
    <BottomNavigationTab title="Inbox" icon="ic_inbox"/>
    <BottomNavigationTab title="Favorite" icon="ic_heart"/>
    <BottomNavigationTab title="Message" icon="ic_mail"/>
    <BottomNavigationTab title="Settings" icon="ic_settings"/>
  </BottomNavigation>
</template>

<script>
export default {
  data() {
    return {};
  },
 methods: {
    setActiveTab(){
      const bottomNav = this.$refs.bottomNav.nativeView;
      bottomNav.selectTab(this.activeIndex);
    },
 }
}
</script>


Efs

I have a question. And I don't know if this is the place to ask.
Following these directions. Is WordPress set up to run completely from the efs mount or only wp-content/uploads?

Only wp-content/uploads is stored on the EFS file system. This configuration file creates a simlink to map that folder to the mount folder:
.ebextensions/efs-mount.config
That leaves your wp-config.php file outside of EFS so you can keep it in source control, modify it locally, and deploy changes through Beanstalk.


CardFlight Errors

Alessandra reported a problem with credit card tokenization. It fails on production when registering for a new account or when using the admin CC testing screen.
Reproduced from last Hockey build; unable to reproduce when installing from Xcode. No keys have changed since the last build. Going to try to distribute a new version to see if that fixes the problem.

Alessandra and I have both confirmed that a new build submitted to Hockey fixed the problem. I'm not sure why it went wrong. My best guess is that the previous build used an older CardFlight API token. I don't know how it could've worked before, though.

Could we leave a SHA of the token in the app somewhere and do a test against it?

Yup – part of the unit tests? Deploy process? Any others?

deploy probably, can compare bundle exec pod keys get XXX - doing it in tests won't work without giving travis/circle our real secrets

Tests could check for the SHA comparison or a known stubbed key (the app currently defaults to stubbed behaviour only for one-character keys, for example).


cursor: col-resize for lt-column-resizer

Currently it seems to be getting a cursor: pointer; applied to it, which isn't as UX friendly as a proper resize cursor is.
I've applied my own style to .lt-column-resizer to add the cursor: col-resize and it seems fine. I might get a chance to do a PR for it this week before I go on holiday, but if someone else beats me to it that would be great ;)

In theory that should already be the case. :thinking:

Do you have ember-hammertime installed by any chance? I would assume that it accidentally adds these styles: Using Touch-action as a fastclick

Looks like I do! It was installed as a dependency for ember-toggle. Now to figure out how to make it work nicely with ELT... :)


mmdet.apis

ImportError: mmskeleton.utils.third_party attempted to use a functionality that requires module mmdet.apis, but it couldn't be loaded. Please install mmdet and retry.

ImportError: mmskeleton.utils.third_party attempted to use a functionality that requires module mmdet.apis, but it couldn't be loaded. Please install mmdet and retry.

Hello,I also met the same problem.Could you tell me how you finally solved it?Thanks!

ImportError: mmskeleton.utils.third_party attempted to use a functionality that requires module mmdet.apis, but it couldn't be loaded. Please install mmdet and retry.

Hello,I also met the same problem.Could you tell me how you finally solved it?Thanks!

Did you solve the problem? I also met it. Thanks!


React.isValidElement refinement is not working

import * as React from 'react';

function foo(a: React.Node) {
    if (React.isValidElement(a)) {
      return a.type; // An error here tells that "type" is not found in "Boolean"
    }
}

Try
Does React.isValidElement refine an argument type?
This may be connected with https://github.com/facebook/flow/issues/4775.

Can be fixed here: https://github.com/facebook/flow/blob/b76ad725177284681d483247e89739c292ed982b/lib/react.js#L222

Type refinement with React.isValidElement doesn't and can't work in general. Because react itself doesn't ship with flow. Its definitions are implemented in definition files from the flow project itself and as a result contains no logic so we cannot run static analysis to type refine anything.
The module that implements isValidElement isn't even flow typed, so that doesn't really help.
In my own project, I've written a little utility function that works for my use case, but a more barebones version that can handle type refinement is the following, although I still haven't figured out how to handle the $Iterable case. If anyone knows how to solve that part, it might be worth just publishing a seperate library to handle element validation.
const isReactElement = (obj): boolean %checks => (
  !!obj
  && typeof obj !== 'boolean'
  && typeof obj !== 'string'
  && typeof obj !== 'number'
  && typeof obj === 'object'
);


Add IJulia Error

I have Python 3.7.0 installed in Anaconda, and I have Julia 1.0.3 installed.
Then I tried to add IJulia, however, there seems to be something wrong with module jupyter-kernelspec.
I was aware of the issue #778, and I think this is a different problem.
Any help is appreciated!
julia> ENV["JUPYTER"]="D:\\Software\\Anaconda3\\Scripts\\jupyter"
"D:\\Software\\Anaconda3\\Scripts\\jupyter"

julia> using Pkg

julia> Pkg.add("IJulia")
   Cloning default registries into C:\Users\Mao\.julia\registries
   Cloning registry General from "https://github.com/JuliaRegistries/General.git"
 Resolving package versions...
 Installed SoftGlobalScope ─ v1.0.8
 Installed VersionParsing ── v1.1.3
 Installed Compat ────────── v1.4.0
 Installed BinaryProvider ── v0.5.3
 Installed ZMQ ───────────── v1.0.0
 Installed Conda ─────────── v1.1.1
 Installed MbedTLS ───────── v0.6.6
 Installed IJulia ────────── v1.14.1
 Installed JSON ──────────── v0.20.0
  Updating `C:\Users\Mao\.julia\environments\v1.0\Project.toml`
  [7073ff75] + IJulia v1.14.1
  Updating `C:\Users\Mao\.julia\environments\v1.0\Manifest.toml`
  [b99e7846] + BinaryProvider v0.5.3
  [34da2185] + Compat v1.4.0
  [8f4d0f93] + Conda v1.1.1
  [7073ff75] + IJulia v1.14.1
  [682c06a0] + JSON v0.20.0
  [739be429] + MbedTLS v0.6.6
  [b85f4697] + SoftGlobalScope v1.0.8
  [81def892] + VersionParsing v1.1.3
  [c2297ded] + ZMQ v1.0.0
  [2a0f44e3] + Base64
  [ade2ca70] + Dates
  [8bb1440f] + DelimitedFiles
  [8ba89e20] + Distributed
  [7b1f6079] + FileWatching
  [b77e0a4c] + InteractiveUtils
  [76f85450] + LibGit2
  [8f399da3] + Libdl
  [37e2e46d] + LinearAlgebra
  [56ddb016] + Logging
  [d6f4376e] + Markdown
  [a63ad114] + Mmap
  [44cfe95a] + Pkg
  [de0858da] + Printf
  [3fa0cd96] + REPL
  [9a3f8284] + Random
  [ea8e919c] + SHA
  [9e88b42a] + Serialization
  [1a1011a3] + SharedArrays
  [6462fe0b] + Sockets
  [2f01184e] + SparseArrays
  [10745b16] + Statistics
  [8dfed614] + Test
  [cf7118a7] + UUIDs
  [4ec0a83e] + Unicode
  Building Conda ──→ `C:\Users\Mao\.julia\packages\Conda\uQitS\deps\build.log`
  Building ZMQ ────→ `C:\Users\Mao\.julia\packages\ZMQ\ABGOx\deps\build.log`
  Building MbedTLS → `C:\Users\Mao\.julia\packages\MbedTLS\r1Ufc\deps\build.log`
  Building IJulia ─→ `C:\Users\Mao\.julia\packages\IJulia\DL02A\deps\build.log`
┌ Error: Error building `IJulia`:
│ Error executing Jupyter command 'kernelspec': [Errno 'jupyter-kernelspec' not found] 2
│ Traceback (most recent call last):
│   File "D:\Software\Anaconda3\Scripts\jupyter-kernelspec-script.py", line 6, in <module>
│     from jupyter_client.kernelspecapp import KernelSpecApp
│   File "D:\Software\Anaconda3\lib\site-packages\jupyter_client\__init__.py", line 4, in <module>
│     from .connect import *
│   File "D:\Software\Anaconda3\lib\site-packages\jupyter_client\connect.py", line 23, in <module>
│     import zmq
│   File "D:\Software\Anaconda3\lib\site-packages\zmq\__init__.py", line 47, in <module>
│     from zmq import backend
│   File "D:\Software\Anaconda3\lib\site-packages\zmq\backend\__init__.py", line 40, in <module>
│     reraise(*exc_info)
│   File "D:\Software\Anaconda3\lib\site-packages\zmq\utils\sixcerpt.py", line 34, in reraise
│     raise value
│   File "D:\Software\Anaconda3\lib\site-packages\zmq\backend\__init__.py", line 27, in <module>
│     _ns = select_backend(first)
│   File "D:\Software\Anaconda3\lib\site-packages\zmq\backend\select.py", line 27, in select_backend
│     mod = __import__(name, fromlist=public_api)
│   File "D:\Software\Anaconda3\lib\site-packages\zmq\backend\cython\__init__.py", line 6, in <module>
│     from . import (constants, error, message, context,
│ ImportError: DLL load failed: The specified module could not be found.
│ [ Info: Found Jupyter version 4.4.0: D:\Software\Anaconda3\Scripts\jupyter
│ [ Info: Installing Julia kernelspec julia-1.0
│ ERROR: LoadError: failed process: Process(`'D:\Software\Anaconda3\Scripts\jupyter-kernelspec.exe' install --replace --user 'C:\Users\Mao\AppData\Local\Temp\julia-1.0'`, ProcessExited(1)) [1]
│ Stacktrace:
│  [1] error(::String, ::Base.Process, ::String, ::Int64, ::String) at .\error.jl:42
│  [2] pipeline_error at .\process.jl:705 [inlined]
│  [3] #run#503(::Bool, ::Function, ::Cmd) at .\process.jl:663
│  [4] run at .\process.jl:661 [inlined]
│  [5] #installkernel#4(::String, ::Function, ::String) at C:\Users\Mao\.julia\packages\IJulia\DL02A\deps\kspec.jl:106
│  [6] installkernel(::String) at C:\Users\Mao\.julia\packages\IJulia\DL02A\deps\kspec.jl:36
│  [7] top-level scope at C:\Users\Mao\.julia\packages\IJulia\DL02A\deps\build.jl:92
│  [8] include at .\boot.jl:317 [inlined]
│  [9] include_relative(::Module, ::String) at .\loading.jl:1044
│  [10] include(::Module, ::String) at .\sysimg.jl:29
│  [11] include(::String) at .\client.jl:392
│  [12] top-level scope at none:0
│ in expression starting at C:\Users\Mao\.julia\packages\IJulia\DL02A\deps\build.jl:9
└ @ Pkg.Operations C:\cygwin\home\Administrator\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.0\Pkg\src\Operations.jl:1097

Looks like you are using your own Anaconda installation, and it is broken.
(Does jupyter kernelspec list work if you run it manually?)

@stevengj it works.
(base) C:\WINDOWS\system32>jupyter kernelspec list
Available kernels:
  python2    D:\Software\Anaconda3\share\jupyter\kernels\python2
  python3    D:\Software\Anaconda3\share\jupyter\kernels\python3

IJulia no longer uses the kernelspec command, so this issue should be moot now.


Proposal: More intelligent transpilation for Differential Loading

🚀 Feature request
Command (mark with an x)

- [ ] new
- [x] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Description
This proposal is inspired by the Chrome team's work on babel/preset-modules.
Currently, Angular CLI's mechanism for differential loading is simple; creating original bundles targetted in ES2015 and down-leveling it for ES5 compatible.
But today, modules-compatible browsers can accept more modern JavaScript than es2015 like async/await, Object Spread, Tagged Template, and more. So the Chrome team created a babel preset for getting more compact modern JavaScript.
Please see more https://github.com/babel/preset-modules#how-does-it-work.
I guess that idea can help also Angular CLI's build process. Generate original bundles for browsers that support ES Modules, and down-leveling it for legacy browsers.
I'm not sure how we can achieve it with TypeScript-based toolchain, but I hope it isn't impossible.

That is really a replacement for TypeScript's down-leveling (ESnext to ES2015) rather than a replacement or refinement of the differential loading down-leveling (ES2015 to ES5).  There are also concerns here with some of the ECMA features.  For instance, native async/await cannot be used with Zone.js so must always be down-leveled and as a result, a variety of plugins present within preset-env would then need to be also included.  Some initial work on usage-based polyfilling via preset-env has also been prototyped.  So the ideal scenario would be for this new preset to be incorporated within preset-env's esmodules option and from reading the documentation, this does appear to be the plan.

Just an idea for build process:

Type-checking with TypeScript (no emitimg)
Compiling source to modern JS with babel (typescript plugin)
Down-leveling bundles to ES5 with TypeScript (or babel?)

The AOT compiler necessitates TypeScript compilation.
The usage based polyfills prototype approach was for TS to target ESnext then use babel with preset-env as a post processor within the bundler to generate the module script variants.  However, the aforementioned preset is brand new and the babel configuration to ensure a functioning Angular application would be more complex than just adding this preset.  But this is definitely something to monitor and consider long-term.

https://www.npmjs.com/package/@alauda/custom-webpack

Is this currently being worked on?
This seems to be a major issue for Angular moving forward, as the zone.js issue with native async/await prevents developers from adopting anything newer then ES2015 (https://github.com/angular/angular/issues/31730) and also prevents other crucial libraries like rxjs from adopting newer targets (https://github.com/angular/angular/issues/38782).
Down-leveling only async/await seems to be the only working solution until other fixes are found - and seems a reasonable step towards supporting newer targets completely; reducing the current pain of developers running into this issue.
https://github.com/angular/angular-cli/issues/16996 has been opened as a request to support this solution, but has been closed in favour of this issue. So are there any plans moving forward?

Closing since async/await downlevelling has landed as part of https://github.com/angular/angular-cli/pull/19871.
It is also worth-mentioning the IE 11 support is deprecated and therefore differential loading.


Implement public sharing of comments on variants / genes

Is your feature request related to a problem? Please describe.
It would be beneficial if users could create public comments on variants.
Describe the solution you'd like
Allow users to share public comments on variants.
Describe alternatives you've considered
N/A
Additional context
N/A

Maybe we have to postpone this.


Idea: Documentation for negotiating larger MTU

If you think it's valuable, it might be good to add an example on MTU size negotiation. I found the default size of 23 to be a bit slow when performing reads on longer characteristics. This transformer will negotiate up the MTU size to the largest size supported by the phone and peripheral. I got it to 256 bytes between a Pixel 2 and a Sparklan chip
Defining a transformer
private val MtuNegotiationObservableTransformer = object : ObservableTransformer<RxBleConnection, RxBleConnection> {
    override fun apply(upstream: Observable<RxBleConnection>): ObservableSource<RxBleConnection> {

        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) {
            return upstream
                    .doOnNext {
                        Timber.e("Negotiating larger MTU")
                    }
                    .flatMap {
                        val connection = it
                        it.requestMtu(GATT_MTU_MAXIMUM)
                                .toObservable()
                                .map {
                                    connection
                                }
                    }
        } else {
            Timber.e("Larger MTU not supported")
            return upstream
                    .doOnNext {
                        Timber.e("Can't negotiate larger MTU on Android API ${Build.VERSION.SDK_INT}. Default is ${it.mtu}")
                    }
        }
    }

Using the transformer
device.establishConnection(false)
        .compose(MtuNegotiationObservableTransformer)
        .subscribe(
            {},
            {}
        )

Added a wiki page


Chip documentation/tas 303

[ ] changelog

I think I just forgot to push the last changes I had (at the __init__.py with most of the explanation for the chip module). Let me know if there are any classes with missing documentation


docs: Fix minor link formatting.

Some links weren't linkified or used a redundant structure ([URL](URL)). These have been properly formatted using <URL>.

By the way, I used the following regex to catch the [URL](URL) links:
\[(?P<addr>[^\]]+)\]\((?P=addr)\)

Maybe we want to add it to our Markdown linter?

Merged, thanks @YagoGG!  Yeah that seems worth adding to the markdown linter; want to add it?

Sure! Added it in #4172.


Update document to include support to msteams:// protocol for deep links.

Type of issue
Missing information
Feedback
We need to include information about the support of the msteams:// protocol for Deeplinks. T1 supported that and T2 not, but because of parity and customers escalations as a blocker to their business, a fix was released to make sure msteams:// is supported. Our article does not mention that and does not leave that clear, which can cause issues with customer escalations in the future without a reference to documentation saying that this is a supported usage. If there's desire to deprecate msteams:// in the future, that should still be mentioned in the article and information should be given for clarity. Announcement would need to be made to make sure customers are aware of future deprecation.
The fix is currently rolling out, reference work item:
Please reach out to Pulkit Sharma and Yuri Dogandjiev to discuss this and identify the PM responsible for helping in updating the documentation as I cannot provide all the details that are needed to make sure for correctness.
Page URL
https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/deep-link-workflow?tabs=teamsjs-v2#configure-deep-link-manually-to-start-audio-video-call-with-users
Content source URL
https://github.com/MicrosoftDocs/msteams-docs/blob/main/msteams-platform/concepts/build-and-test/deep-link-workflow.md
Author
@v-npaladugu
Document Id
98d88f26-f11f-4810-162a-40ca552be3e3

@cadasi -  Thanks for raising this. We will discuss internally and will take necessary action.


Implement a prompt section for Conda version (🅒)

Feature Request

Is your feature request related to a problem? Please describe.
This feature is intended to achieve feature parity with the following Spaceship section file: https://github.com/denysdovhan/spaceship-prompt/blob/master/sections/conda.zsh
Describe the solution you'd like
Porting over the existing zsh implementation of the Conda section file, showing the current Conda version when a Conda virtual environment is activated.

@matchai Taking up this one as well. 😸

Excellent! Glad to have you contributing! 😄

Why not add a section to show conda env verbose, I thought it would be much useful ...


Generating complex topology cloth type objects through unity for manipulation

Hi,
I am interested to generate complex topological garments for robotic manipulation and I was wondering if it possible to do this through the unity plug-in or by using the meshes from other simulators like blender for example.

In terms of what meshes are supported in MuJoCo, OBJ support was recently added (see the mug example here), and there's an ongoing discussion regarding MTL support.
Regarding cloth topology, and take this with a grain of salt because I'm not a deformable expert, maybe check out Composite objects and the following examples to see what sorts of things are currently model-able:

Flag flapping in the wind
Hammock


Adding m3tsz validation

Coverage decreased (-0.1%) to 78.146% when pulling 62d5142e95883267273c7d364c8ab9f4de47067d on martinm-encoder-protection into 6d33709833bd78a92fd801aa4e72dc1bbb013ddd on master.


Daily Task Indicator infoboxes

Implement infoboxes for daily task indicators. Add option to enable/disable infoboxes for daily tasks. Keep infoboxes disabled by default.

Need this!!

Added as a phub plugin

XD


[TEP-0100] Prepare for testing of minimal status implementation

Changes
This is for https://github.com/tektoncd/community/blob/main/teps/0100-embedded-taskruns-and-runs-status-in-pipelineruns.md
This change is to minimize the size of the actual implementation. We need to change a number of
tests in pkg/reconciler/pipelinerun/pipelinerun_test.go to be table-based, so that we can test
behavior under each possible value for the new embedded-status feature flag. Here, we just
modify the relevant tests to be table-based, with a test case for each value, but we don't actually
change any behavior. Right now, that means that these tests are purely duplicative - they're going
to run the same and check the same things for any value of embedded-status, but the implementation
PR will be much, much smaller, due to how many lines end up indented here.
/kind misc
/kind tep
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Docs included if any changes are user facing
[x] Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Release notes block below has been filled in or deleted (only if no user facing changes)

Release Notes
NONE

/assign @lbernick
/assign @jerop

Discussed offline with Andrew-- he is going to try reworking this to parameterize tests/use helpers for checking status
/hold
@abayer just remove the hold when ready for re-review!

Closing in favor of an alternative approach to modifying these tests - PR incoming.


[Feature Request] custom home page

What problem does the feature solve?
I would like to customize the home page.
Proposed solution
An index.md or README.md in the root directory, which is used if present.
Thank you so much
Hannes

found defaultPages.home: false. so it is solved. cheers.


Change header title and background color when in folders other than the main Inbox

When in the Inbox, the header title should display 'Inbox' and the background color should be #4285f4, same as it is now, probably.
Similarly,

Snoozed folder should change the header background color to #ef6c00 and title to 'Snoozed'
Done (All Mail) folder should change the header background color to #0f9d58 and title to 'All Mail'
All other folders should change the header background color to #898984 and title to the name of the folder/filter

Solved in PR #74


[Bug] "DetachAttach Force" with same Instance

We tried to transfer a database, but due to an error in the DNS (caused by renaming servers) source and destination IPs have been the same.
$source = 'sqlcsvr24win'              #-> [Same IP in DNS]
$destination = 'sqlcsvr24win_new'     #-> [Same IP in DNS]
Copy-DbaDatabase -Source $source -Destination $destination -Database db8 -DetachAttach -force
when we had used with the force parameter, the database files were completely deleted and then we got an error.

Errors Received

WARNING: [00:26:42][Dismount-SqlDatabase] Issue setting database to single-user. | User does not have permission to alter database 'db8'
, the database does not exist, or the database is not in a state that allows access checks.
ALTER DATABASE statement failed.
WARNING: [00:26:42][Dismount-SqlDatabase] Issue detaching database. | The database 'db8' does not exist. Supply a valid database name. T
o see available databases, use sys.databases.

Expected Behavior
Maybe it would make sense to verify if $source @@servername != $destination @@servername

It is unfortunate the use case you hit but I do not see this as a bug in the command.
We can't implement matching on the server name because that prevents use cases where databases are copied between named instances on the same server.

Yes, you're right but it's possible to compare the combination @@ServerName and @@InstanceName .
I think it's dangerous when a user due to an error in the DNS or name in code(e.g. parameter error), it's going to delete Databases files from Source.


RTD auctionDelay and waitForIt flag

A recent PR found a gap in the Real-Time Data documentation that this aims to close.

@bretg I added a few things to hopefully clarify a little. But I have a few of questions:

What happens if you set waitForIt to true but don't put in an auctionDelay value? How long will it wait?
What if you do the opposite, set an auctionDelay value without making any waitForIt true? Will the auctionDelay value be ignored?
Is the default for waitForIt false?

@bretg I added a few things to hopefully clarify a little. But I have a few of questions:

What happens if you set waitForIt to true but don't put in an auctionDelay value? How long will it wait?
What if you do the opposite, set an auctionDelay value without making any waitForIt true? Will the auctionDelay value be ignored?
Is the default for waitForIt false?

Thanks for the questions @jeanstemp -- added a "notes" section and the default values.

Thanks for the questions @jeanstemp -- added a "notes" section and the default values.


Fixed bug with $building.

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues

Need a unit test that tests for the behavior changed.

Thank you! Great catch.


Updated pdfjs-dist

Latest versions of pdfjs-dist caused worker loader errors either importing the package or when trying to set the workerSrc. Used a diff on this fork to come up with these fixes which puts pdfjs-dist at v2.4.456.
Pdfjs does have prerelease versions which include this fix which we think may resolve the issue in the future.

I've approved this, but I still think there's some CSS trickery here that might be causing our layer mis-alignment.  Let's check with @ThinkBrandonThink about if this what's causing the issue.

I've approved this, but I still think there's some CSS trickery here that might be causing our layer mis-alignment.  Let's check with @ThinkBrandonThink about if this what's causing the issue.

I've approved this, but I still think there's some CSS trickery here that might be causing our layer mis-alignment. Let's check with @ThinkBrandonThink about if this what's causing the issue.

I looked into the issue and found that the biggest issue causing the mis-alignment was do to the style sheet not being properly loaded into the iframe. The easiest solution was to copy the style sheet into the project in adhesion and make minor adjustments there.

I've approved this, but I still think there's some CSS trickery here that might be causing our layer mis-alignment. Let's check with @ThinkBrandonThink about if this what's causing the issue.

I looked into the issue and found that the biggest issue causing the mis-alignment was do to the style sheet not being properly loaded into the iframe. The easiest solution was to copy the style sheet into the project in adhesion and make minor adjustments there.

Do you have a code with implementation using the updated to PdfJs 2.4 version?
I have fork of 2019 but I tried update my code using your PdfAnnotate version but I'm with erros.
Example:
My version use:
annotationLayer = PDFJSAnnotate.UI.preparePage();
Your version doesn't work because:
caught TypeError: Cannot read properties of undefined (reading 'UI')


chore(install): Remove user/account NerdStorage writes

Summary
Removes writes to account- and user-scoped NerdStorage from the install status reporter.
Context
New Relic UI no longer depends on the openInstallLibrary collection, except for entity-scoped NerdStorage data.

It looks like the codecov check is failing because the coverage for mock_nerdstorage_client.go dropped by 37.50%. This an optional check I think?
Code coverage went down because the mock client's methods WriteDocumentWithUserScope and WriteDocumentWithAccountScope are no longer referenced in any tests. There's a possibility they might be useful in testing other parts of the code that deal with user/account storage, so I didn't remove them. Doesn't seem too worrisome to have some testing coverage gaps on a mock client 🤷

integration tests failing. looking into it 👀

I pushed a minor change and then reverted it. Now integration tests are passing again (I was pretty sure they were passing originally before I rebased on main). I think these tests might be a bit flakey for some reason.


stream_unpack tlast works incorrectly

axistream_unpack tlast is meant to be raised on the last unpacked output on an input with tlast raised, and otherwise remain low.
Tlast instead is raised for the entire split up packet.
The reg controlling tlast is also not reset properly.

fixed https://github.com/TripRichert/hdl_rosetta_stone/pull/6


Support adding tags for note.

I have two ideas to support tags in Evermonkey.

Markdown support: The tags is written directly into the text. You may have seen this in hexo, Story(小书匠). This will be a convention and if you don't follow this syntax correctly, you won't create tags correctly.
User Input: This may force you to make choice every time you publish(update & create) note to Evernote. An input box will show off and ask you whether add new tags or not.

Which one will you choose? Why?

Add completion support for metadata(tags, notebook).


Back of the PCB has a lot of stuff on it.

I understand wanting to attach info and a watermark, but seriously there's a LOT on the back of the case. Maybe make a variant without the Discord info and with a smaller watermark on there. I tried editing it again, since I modified the silkscreen when I ordered them but since I'm not good at designing PCBs (It's my first time) I ended up with this.

It's not aligned properly, and half of the text is the wrong way but you can still see what I was thinking of. Maybe have one without or with a smaller watermark that you can't use commercially. It would be easier if the KiCad (or other software) files were in the repo.

I will take a look at it. Which PCB service are you using? The silkscreen looked fine for JLCPCB and PCBWay. My newer PCBs are made with KiCAD. I have been working on a newer revision of this board for flush mounted components, so the case will be about 6-8mm shorter than the current one, but it is an edit of the original PCB on EasyEDA.

It's not an issue with your silkscreen, I think I accidentally moved mine.

Could be something like this instead

Oh yea, feel free to steal my design, I don't need credit but it would be nice to have in the README :)