Can't compile project with Gradle 8.3.0 - com.likethesalad.android:stem-plugin:2.7.0

Hi. I want to report that I'm getting this error while trying to compile and run my Android app from Android Studio using Gradle 8.3.0 and with com.likethesalad.android:stem-plugin:2.7.0:
`A problem was found with the configuration of task ':app:resolveDebugPlaceholders' (type 'ResolvePlaceholdersTask').

Gradle detected a problem with the following location: '/Users/~/Desktop/~ - Android/app/build/generated/resolved/debug'.

Try:

Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.

Exception is:
org.gradle.internal.execution.WorkValidationException: A problem was found with the configuration of task ':app:resolveDebugPlaceholders' (type 'ResolvePlaceholdersTask').

Gradle detected a problem with the following location: '/Users/~/Desktop/~ - Android/app/build/generated/resolved/debug'.
Reason: Task ':app:generateDebugResources' uses this output of task ':app:resolveDebugPlaceholders' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':app:resolveDebugPlaceholders' as an input of ':app:generateDebugResources'.
Declare an explicit dependency on ':app:resolveDebugPlaceholders' from ':app:generateDebugResources' using Task#dependsOn.
Declare an explicit dependency on ':app:resolveDebugPlaceholders' from ':app:generateDebugResources' using Task#mustRunAfter.

For more information, please refer to https://docs.gradle.org/8.4/userguide/validation_problems.html#implicit_dependency in the Gradle documentation.
at org.gradle.internal.execution.WorkValidationException$BuilderWithSummary.build(WorkValidationException.java:137)
at org.gradle.internal.execution.WorkValidationException$BuilderWithSummary.get(WorkValidationException.java:119)
at org.gradle.internal.execution.steps.ValidateStep.throwValidationException(ValidateStep.java:178)
at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:100)
at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:55)
at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:71)
at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:45)
at org.gradle.internal.execution.steps.SkipEmptyWorkStep.executeWithNonEmptySources(SkipEmptyWorkStep.java:177)
at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:86)
at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:53)
at org.gradle.internal.execution.steps.RemoveUntrackedExecutionStateStep.execute(RemoveUntrackedExecutionStateStep.java:32)
at org.gradle.internal.execution.steps.RemoveUntrackedExecutionStateStep.execute(RemoveUntrackedExecutionStateStep.java:21)
at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:38)
at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:36)
at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:23)
at org.gradle.internal.execution.steps.CleanupStaleOutputsStep.execute(CleanupStaleOutputsStep.java:75)
at org.gradle.internal.execution.steps.CleanupStaleOutputsStep.execute(CleanupStaleOutputsStep.java:41)
at org.gradle.internal.execution.steps.ExecuteWorkBuildOperationFiringStep.lambda$execute$2(ExecuteWorkBuildOperationFiringStep.java:66)
at org.gradle.internal.execution.steps.ExecuteWorkBuildOperationFiringStep.execute(ExecuteWorkBuildOperationFiringStep.java:66)
at org.gradle.internal.execution.steps.ExecuteWorkBuildOperationFiringStep.execute(ExecuteWorkBuildOperationFiringStep.java:38)
at org.gradle.internal.execution.steps.AssignWorkspaceStep.lambda$execute$0(AssignWorkspaceStep.java:32)
at org.gradle.api.internal.tasks.execution.TaskExecution$4.withWorkspace(TaskExecution.java:293)
at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:30)
at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:21)
at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:37)
at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:27)
at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:47)
at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:34)
at org.gradle.internal.execution.impl.DefaultExecutionEngine$1.execute(DefaultExecutionEngine.java:64)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:145)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:134)
at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:74)
at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:78)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:42)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:331)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:318)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.lambda$execute$0(DefaultTaskExecutionGraph.java:314)
at org.gradle.internal.operations.CurrentBuildOperationRef.with(CurrentBuildOperationRef.java:80)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:314)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:303)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:463)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:380)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
at org.gradle.internal.concurrent.AbstractManagedExecutor$1.run(AbstractManagedExecutor.java:47)

BUILD FAILED in 1m 30s
34 actionable tasks: 3 executed, 31 up-to-date`
Thanks. I hope you can fix this soon! ;)

Hi @Megabyte94 - Thank you for letting me know about this issue, I'll take a look 👍

I've just released version 2.8.0 with a fix for this issue. Thank you for your feedback! Please feel free to reopen this issue if you still see the problem using the new version.


TLS support

Hi can you please add TLS support? :)

Hello @hmilkovi
Strictly speaking, TLS is already supported: foundationdb-explorer will use the TLS_* environment variables in its environment.  FDB_TLS_KEY_FILE=... FDB_TLS_CA_FILE=... FDB_TLS_VERIFY_PEERS=... foundationdb-explorer.
However, this is not particular user-friendly for people looking to a GUI based solution.
I suppose ideally there would be some way of configuring this via the front-end - with some mechanism to save the configuration, allow switching between different sets of configuration, etc. I'm not making any promises, though!


Make regression tests more strict, improve names

This will help allow us to customize comparisons, but make comparisons more strict by default.

bors r+


There is a problem with the layout Container

Problem a：
ScrollContainer
--VBoxContainer              <-  Vbox alignment center is invalid
----navbar

Problem b
ScrollContainer
--VBoxContainer
----CenterContainer        <- alignment center is invalid
------navbar

godot:  3.1.bate.calinou.623f7b6 (Daily compiled version)
OS:  win10 x64
The layout has no maximum or minimum size, the alignment of Vbox and hbox is invalid, CenterContainer has no left, right, top and bottom alignment options, and the layout constraint has no overflow options similar to CSS

Sorry, this issue barely explains what the problem you have or have found is. Unless you explain it in more depth or with pictures, I don't think anyone will understand what you are trying to say.

Yes, please explain a little bit more your issue.
But some answers to your comments:

VBoxContainers and HBoxContainer were never meant to align content vertically/horizontally. You need to put them into another container to do so.
"CenterContainer has no left, right, top and bottom alignment options,". Yes, it is a CENTERContainer.
You can put a CenterContainer in a HBoxContainer/VBoxContainer to align content top-center, center-left, center-right or bottom-center (with the appropriate alignment options in those containers).

The width of VBoxContainer should be 100%. CenterContainer should inherit the width of VBoxContainer. When the viewport size is larger than the minimum size of navbar_bg, navbar_bg should be displayed in the center. When the viewport size is smaller than the minimum size of navbar_bg, the alignment mode is left to right.

You can only use center constraints on the outside, but VBox can't use center constraints, so how can VBox constraints align controls, just like QT layout and html, with child controls center

Pictures don't work @crud-boy

@Zireael07 ok，Forget to be public

The width of VBoxContainer should be 100%

It is already the case, if you look at the selection rectangle you see it takes the full screen width.

CenterContainer should inherit the width of VBoxContainer

It already does, as the CenterContainer selection area suggests.

When the viewport size is larger than the minimum size of navbar_bg, navbar_bg should be displayed in the center.

No it should not, the HboxContainer pads its content to the left. If you want to achieve centering you probably need to use the anchor and margin system. And put your base node top the top-center.

You can only use center constraints on the outside, but VBox can't use center constraints, so how can VBox constraints align controls, just like QT layout and html, with child controls center

You need to put you logo in a center container I guess.
Ok, I am sorry but I that point I will assume that these issues results more in a misunderstanding on how the Container system works than real engine issues. Please use the other community channels for help. If you still have problems after that, please open an issue for each specific problem with a specific reproduction case.


I have made the site responsive

What is the change?
I have made the site responsive which includes navbar,team, projrcts, opportunities and contact-form.
Related issue?
closes: #49
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] I have followed the Code of Conduct.
[x] I have  checked there aren't other open Pull Requests for the same update/change.
[x] I have you tested the code before submission.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm Hacktoberfest'21 contributor.

Screenshots (if any)

@Mitushi-23 Can resolve the conflicts. We are facing issue while merging.

I have resolve the conflicts


Clean up doxygen documentation

Shogun uses doxygen for documentation purposes, the results are at
http://www.shogun-toolbox.org/doc/en/latest/index.html
The way this documentation is generated is via automatic doxygen, and a number of python scripts (that for example insert examples into the doxygen pages)
There are number of issues here:

Most things are horribly outdated (authors, implemented methods, install, etc)
The way code is put into documentation (for say the examples) is hacky: A python script just dumps all code into the doxygen page
This is really hard to maintain due to its complexity

Since this page is the portal for most people to start using Shogun, we should really do something about this.
High level suggestions:

Somehow merge all the Readmes, github wiki, and this documentation, to only have one ressource to maintain (which then can be displayed at multiple places). Preferable the README.md files which are already linked to the github wiki.
Handle example documentation and code in doxygen properly, see #2600

Action items:

Find a way to generate a MD (or doxygen) page from a source file - converting all comments to MD style content in the page. DONE ins #2600 2600
Make the doxygen pages include text from README's aka the github wiki, so that changes in the wiki directly are merged in our documentation page

Hi, is this still open ?

This has changed a lot due to the new cookbook.
Eventually we will remove the documentation part of doxygen (apart from maybe class docs), and move to something else. The current version is broken as well
Closing for now...


how to install mmcv and mmdet

@whai362
After I installed mmcv and mmdet with pip which the commands were:
pip install mmcv-full==latest+torch1.6.0+cu102 -f https://download.openmmlab.com/mmcv/dist/index.html
pip install mmdet
I ran the command: bash tools/rects_dist_train.sh local_configs/rects_ae_textspotter_r50_1x.py 8
but it reported the following error:
Traceback (most recent call last):
File "tools/rects_train.py", line 9, in
from mmdet.apis import (get_root_logger, init_dist, set_random_seed,
ImportError: cannot import name 'init_dist' from 'mmdet.apis' (/home/garone/anaconda3/lib/python3.8/site-packages/mmdet/apis/init.py)
Traceback (most recent call last):
File "tools/rects_train.py", line 9, in
from mmdet.apis import (get_root_logger, init_dist, set_random_seed,
ImportError: cannot import name 'init_dist' from 'mmdet.apis' (/home/garone/anaconda3/lib/python3.8/site-packages/mmdet/apis/init.py)
Traceback (most recent call last):
File "tools/rects_train.py", line 9, in
from mmdet.apis import (get_root_logger, init_dist, set_random_seed,
ImportError: cannot import name 'init_dist' from 'mmdet.apis' (/home/garone/anaconda3/lib/python3.8/site-packages/mmdet/apis/init.py)
Traceback (most recent call last):
File "tools/rects_train.py", line 9, in
from mmdet.apis import (get_root_logger, init_dist, set_random_seed,
ImportError: cannot import name 'init_dist' from 'mmdet.apis' (/home/garone/anaconda3/lib/python3.8/site-packages/mmdet/apis/init.py)
Traceback (most recent call last):
File "tools/rects_train.py", line 9, in
from mmdet.apis import (get_root_logger, init_dist, set_random_seed,
ImportError: cannot import name 'init_dist' from 'mmdet.apis' (/home/garone/anaconda3/lib/python3.8/site-packages/mmdet/apis/init.py)
Traceback (most recent call last):
File "tools/rects_train.py", line 9, in
from mmdet.apis import (get_root_logger, init_dist, set_random_seed,
ImportError: cannot import name 'init_dist' from 'mmdet.apis' (/home/garone/anaconda3/lib/python3.8/site-packages/mmdet/apis/init.py)
Traceback (most recent call last):
File "tools/rects_train.py", line 9, in
from mmdet.apis import (get_root_logger, init_dist, set_random_seed,
ImportError: cannot import name 'init_dist' from 'mmdet.apis' (/home/garone/anaconda3/lib/python3.8/site-packages/mmdet/apis/init.py)
Traceback (most recent call last):
File "tools/rects_train.py", line 9, in
from mmdet.apis import (get_root_logger, init_dist, set_random_seed,
ImportError: cannot import name 'init_dist' from 'mmdet.apis' (/home/garone/anaconda3/lib/python3.8/site-packages/mmdet/apis/init.py)
Traceback (most recent call last):
File "/home/garone/anaconda3/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/home/garone/anaconda3/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/garone/anaconda3/lib/python3.8/site-packages/torch/distributed/launch.py", line 261, in
main()
File "/home/garone/anaconda3/lib/python3.8/site-packages/torch/distributed/launch.py", line 256, in main
raise subprocess.CalledProcessError(returncode=process.returncode,
subprocess.CalledProcessError: Command '['/home/garone/anaconda3/bin/python', '-u', 'tools/rects_train.py', '--local_rank=7', 'local_configs/rects_ae_textspotter_r50_1x.py', '--launcher', 'pytorch']' returned non-zero exit status 1.
I want to know how to install mmcv and mmdet correctly so that I can run it. Thanks!

https://github.com/open-mmlab/mmdetection/blob/v1.0rc0/INSTALL.md

pip install mmcv==0.2.13 --user

It can't install mmcv with this method
ERROR: Command errored out with exit status 1:
 command: /home/garone/anaconda3/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-rszl7l43/mmcv/setup.py'"'"'; __file__='"'"'/tmp/pip-install-rszl7l43/mmcv/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-u6vi5a39
     cwd: /tmp/pip-install-rszl7l43/mmcv/
Complete output (33 lines):
WARNING: The repository located at mirrors.aliyun.com is not a trusted or secure host and is being ignored. If this repository is available via HTTPS we recommend you use HTTPS instead, otherwise you may silence this warning and allow it anyway with '--trusted-host mirrors.aliyun.com'.
ERROR: Could not find a version that satisfies the requirement pytest-runner (from versions: none)
ERROR: No matching distribution found for pytest-runner
Traceback (most recent call last):
  File "/home/garone/anaconda3/lib/python3.8/site-packages/setuptools/installer.py", line 128, in fetch_build_egg
    subprocess.check_call(cmd)
  File "/home/garone/anaconda3/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/home/garone/anaconda3/bin/python', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmp20h4pvq2', '--quiet', 'pytest-runner']' returned non-zero exit status 1.

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

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/tmp/pip-install-rszl7l43/mmcv/setup.py", line 55, in <module>
    setup(
  File "/home/garone/anaconda3/lib/python3.8/site-packages/setuptools/__init__.py", line 164, in setup
    _install_setup_requires(attrs)
  File "/home/garone/anaconda3/lib/python3.8/site-packages/setuptools/__init__.py", line 159, in _install_setup_requires
    dist.fetch_build_eggs(dist.setup_requires)
  File "/home/garone/anaconda3/lib/python3.8/site-packages/setuptools/dist.py", line 699, in fetch_build_eggs
    resolved_dists = pkg_resources.working_set.resolve(
  File "/home/garone/anaconda3/lib/python3.8/site-packages/pkg_resources/__init__.py", line 779, in resolve
    dist = best[req.key] = env.best_match(
  File "/home/garone/anaconda3/lib/python3.8/site-packages/pkg_resources/__init__.py", line 1064, in best_match
    return self.obtain(req, installer)
  File "/home/garone/anaconda3/lib/python3.8/site-packages/pkg_resources/__init__.py", line 1076, in obtain
    return installer(requirement)
  File "/home/garone/anaconda3/lib/python3.8/site-packages/setuptools/dist.py", line 758, in fetch_build_egg
    return fetch_build_egg(self, req)
  File "/home/garone/anaconda3/lib/python3.8/site-packages/setuptools/installer.py", line 130, in fetch_build_egg
    raise DistutilsError(str(e)) from e
distutils.errors.DistutilsError: Command '['/home/garone/anaconda3/bin/python', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmp20h4pvq2', '--quiet', 'pytest-runner']' returned non-zero exit status 1.
----------------------------------------

ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.


Proposal: Figma tokens (colors and dimensions) including different themes are added to tailwind directly

Summary

This PR includes the CSS files (for Harness Open Source, Harness Theme, and UI Core theme) and tailwind files (color, dimensions) which is exported from Figma

Background
Starting from Figma...

Our Figma tokens are orgamized as such: A core collection and its theme collections.
The theme collections contains base tokens for that specific theme. At this point since there are 3 themes, there are 3 collections. The tokens in this theme have two modes: Light, Dark. The variables within this collection is not used by the designers directly in Figma. Instead, these are only used as reference by the core collection.
The core collection contains both semantic and component tokens for the 3 themes. The tokens here reference the base tokens from the respective theme collections meaning that the tokens in the core collection has access to to Light/Dark values in the theme collections. The designers will be using these tokens in their Figma UIs.
In summary, think of the core collection as an interface that allows the designers access to semantic and component tokens that can be used irregardless of theme.

Through the token pipeline...

Given the explanation above, we only need to export the Figma tokens from the core collection (remember the interface?). Meaning the exported tokens that will be built to CSS and Tailwind inlcudes semantic and component tokens but not base tokens.
With this method, we can ensure that for the different themes in the generated CSS files, they all have the same set of CSS variables. Same goes for Tailwind. This provides confidence for the developers that they can use the semantic and component level tokens within their code irregardless of the theme

To Tailwind file in this codebase

Previously we discussed that we will be following shadcn method of theming. Meaning we have a CSS file that contains the mapping between the semantic and component level tokens to the CSS variables.
However, given that we are only exporting semantic and component level tokens, this CSS file that includes the shadcn mapping is not generated.
With that same reason, we can actually add the semantic and component level tokens (color and dimensions) to tailwind directly, which is then picked up by the Tailwind intellisense. With this method, the developer has that confidence that what they see in Figma is what they can use in Tailwind. Ensuring design consistency
On a side note, we added a prefix to the tailwind tokens from Figma, so that the likelihood of the tokens from Figma clashing with tokens used directly in Tailwind is mitigated

Tailwind intellisense

What devs see in Figma is what they can use in Tailwind

TL;DR

Implementation is only exporting semantic and component tokens from Figma into CSS and tailwind files.
These same semantic and component tokens are used by the designers in the Figma UI
Adding these tokens directly to Tailwind ensures that the developers can easily reference the tokens from Figma and use them in tailwind. What they see in Figma is what they can use in code.

Other items

At the point of this writing, I realized that we will need to flesh out the dimensiosn tokens better because currently we are dumping the dimension Tailwind tokens into "Spacing" in Talwind. But other config in Tailwind also requiers the same dimension Tailwind tokens e.g. "borderRadius"

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This pull request has been automatically closed due to 30 days of inactivity. If you believe this was done in error, please feel free to reopen the PR or reach out to the BT team for further assistance. Thank you for your contributions!


RFE: missing TANDBERG LTO drives

( TANDBERG is using the HP fork:
https://www.overlandtandberg.com/products/neo-tape/lto-software/lto-ltfs/#LTO-56
ftp://ftp1.overlandtandberg.com/neo/LTFS/LTO-5,6/Red Hat/ltfs-3_4_2-source-rhel_x86_64.tar.gz )
From the HP fork: https://github.com/nix-community/hpe-ltfs/blob/f909474d71deb0e6a7abc71fd47c16a78b9c1eb0/ltfs/src/tape_drivers/osx/ltotape/ltotape_supdevs.h#L46-L47
TANDBERG LTO-5 HH and LTO-6 HH:
   { "LTO-5 HH        ", drivefamily_lto,     "TANDBERG DATA LTO5",  drive_lto5         },
   { "LTO-6 HH        ", drivefamily_lto,     "TANDBERG DATA LTO6",  drive_lto6         },

@ia2115
Patch to add Tandberg LTO 5 and 6 HH tape drives to HP back-end : https://paste.debian.net/plain/1198176
Based on #283 info and tests.


Run dropdown arrow disappear when multiple extension contributes to it

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

Version: 1.59.0 (user setup)
Commit: 379476f0e13988d90fab105c5c19e7abc8b1dea8
Date: 2021-08-04T23:13:12.822Z
Electron: 13.1.7
Chrome: 91.0.4472.124
Node.js: 14.16.0
V8: 9.1.269.36-electron.0
OS: Windows_NT x64 10.0.19043
Steps to Reproduce:

Install at least two extensions which contribute to editor/title/run". For example, Java Debugger & Code Runner
The dropdown arrow in editor run button disappear

When only one extension contributes to it

When multiple

// cc @weinand

/duplicate #129599
@jdneo Code Runner does not use theme icons but SVGs and we were not covering that case in the new split button dropdown item in VS Code 1.59 and automatically fall back to the previous version (just a dropmenu). The fall back is used whenever a contributed command uses an an SVG.
This has been fixed in Insiders.

Thank you for the information @weinand


feat: hide appbar button

Shouldn't the button hide the appbar only when the user is typing
__
  Summary: :hammer_and_wrench: This code needs a fix

Shouldn't the button hide the appbar only when the user is typing. Also the state doesn't persist across challenges.

Hey it should be fixed now, I do not think it is necessary to keep the state across challenges. It is a simple button press.


OSError: [Errno 1] Operation not permitted:

Hi there, I tried both command on my mac with the same error. i used sudo, but it is still operation not permitted. Any idea? thanks your help !
sudo pip install aws-shell --upgrade --ignore-installed six
sudo pip install aws-shell

Are you on El Capitan?  This is a known issue on El Capitan, but I'm surprised you're still getting this error even when you run --ignore-installed six.  Can you confirm a few things for me?

What version of Mac OS X are you running?
Can you share the whole output of sudo pip install aws-shell --upgrade --ignore-installed six?


Feat/archive

Changes

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] spec PR link included
[x] Follows the commit message standard
[x] Meets the contributing guidelines (including
functionality, content, code)
[x] Test cases with documentation and functionality works as expected using current and related github repos (MUST deploy and check)
[x] Release notes block below has been filled in or deleted (only if no user facing changes)

Release Notes

覆盖率不够，稍后补充


Conflicting return type in declaration of 'new'

We are getting the static analyzer warning
Branch/Branch-SDK/Branch-SDK/Networking/BNCNetworkService.h:36:1: Conflicting return type in declaration of 'new': 'instancetype' (aka 'id') vs 'id'
https://github.com/BranchMetrics/ios-branch-deep-linking/blob/02394ce83dc419bac02c9877d9f0ce9a3c7515f3/Branch-SDK/Branch-SDK/Networking/BNCNetworkService.h#L36

Fixed in #792 .

Updated in version 0.23.4.


How to use large batch_size?

Thanks to this great work.
I want to use large batch_size to train the model.  In config_v1.py, I set both batch_size and im_batch to be 2. However, the shape(N, H, W, C) of the image still keeps to be N=1.
So how can I use large batch_size?

This is not implemented yet, as stated in the Readme, that training > 2 is NOT implemented yet.


proposal: x/debug: make the core and gocore packages public

Authors: @mknyszek @prattmic @aclements
Purpose
The purpose of this proposal is to help fill in an important gap in Go debugging by providing a foundation for Go heap analysis. The primary use-cases for heap analysis (vs. heap profiles) are to pinpoint memory leak issues and debug out-of-memory errors by providing an in-depth look at the memory graph. Other use-cases exist as well, mostly related to the large amount of detail available in typical heap analysis software.
Go currently has two heap analysis options: analyzing core files for Go processes (via golang.org/x/debug/cmd/viewcore) or analyzing heap dumps (produced by runtime/debug.WriteHeapDump). As of today, both of these options are not easily available to users. The former has bit-rotted, while the latter lacks working tooling (and so may not actually work either).
Some companies using Go have expressed interest in building their own heap analysis tooling, while members of the Go community have contributed time and effort to updating viewcore. The utility of such functionality is lauded in the Java world, especially when it's available for servers over a connection (e.g. net/http/pprof).
Plan
We propose the following plan for improving the state of Go heap analysis, with the core API change here being to make the golang.org/x/debug/internal/core and golang.org/x/debug/internal/gocore packages public.
Before that can happen, however, we also need to fix them and prevent them from breaking again by:

[ ] Updating gocore and core to work with Go at tip.
[ ] Ensure that gocore and core are well-tested, and tested at tip.

[ ] Running the full test suite for a core dump created from a Go binary built at tip.
[ ] Setting up the golang.org/x/debug builder to run against the main Go repository.

After that, I propose making gocore and core externally-visible APIs, allowing Go developers to build on top of it with some fairly minor changes to the API that I would like to hash out. To begin with, I would like to also propose to make these APIs not Go 1 compatible (more on this below).
Some proposed changes to the API include:

Consider exporting gocore.region (very useful API for type-casting memory regions).
Consider moving gocore.region into core.
Iterator-style interfaces for some functions/methods.
Write go.dev documentation on how to do heap analysis with viewcore.

These small steps would bring back heap analysis to the Go ecosystem and will ensure it continues to work.
We feel that the existing gocore library is sufficiently abstract such that it likely will not break between Go releases, but marking it as not Go 1 compatible allows us to be more flexible with the API as the runtime itself changes (whose details it intimately relies upon). We may also choose to make it Go 1 compatible if we can ensure users have enough escape hatches to discover additional details (though not necessarily in a backwards-compatible way) while minimizing the API to what we're comfortable with assuming about a Go process. The difference between these options is admittedly small; the existing API is already unlikely to change much over time.
viewcore, though minimalistic, provides a proof-of-concept for the gocore library that we hope will motivate Go developers to build fancier tooling for heap analysis. Documentation will be critical to making this tooling more widely known ("how to debug a memory leak with viewcore").
Potential future work
I want to also mention some ideas for future work to gauge interest, even though they're not relevant to the proposal directly.

Stub out runtime/debug.WriteHeapDump to reduce eliminate some technical debt.
Provide a way to construct a core file at runtime and expose it through net/http (perhaps via WriteHeapDump).
Reduce dependence on DWARF information for type-casting regions.

The goal of (1) and (2) is to replace WriteHeapDump with a way to produce a process snapshot that works with existing tooling (i.e. gocore and viewcore). Constructing our own core file isn't terribly difficult, provides us with a stable binary format specification so we don't have to go through the trouble of defining our own, and is a format already automatically generated by Linux, so we have fewer formats to support.
The goal of (3) would be to improve the debugging experience with core dumps from stripped binaries. This might not need any additional API, but should be considered up-front.

This would be an incredible help to the ecosystem! viewcore is an absolutely key tool for developers of CockroachDB, and it's been challenging to be able to contribute to viewcore because of its position as an internal package.
I created some basic viewcore documentation for CockroachDB developers, in case this prior art is useful at all. It also contains a pointer to the branch I've been maintaining with some extra tools that allow dumping the viewcore output into something that can be consumed by pprof to create a very primitive object graph viewer.
https://cockroachlabs.atlassian.net/wiki/spaces/CRDB/pages/1931018299/Using+viewcore+to+analyze+core+dumps

I think the main thing missing here is actually what the final API itself will look like. After an offline discussion today with @aclements and @prattmic, I think we've decided the right next step is to fork these x/debug-internal libraries into x/exp where we can iterate on them freely. The API is far too large to try to summarize for a proposal and have everyone comment on it. Meanwhile, x/exp will allow us to put it out there in a way that will allow for experimentation and trial.
The reason we chose x/exp over x/debug is because x/exp has clear expectations with respect to backwards compatibility (i.e. there is none). Meanwhile, x/debug contains only one exported package with zero imports in the Go ecosystem and a handful in the main Go repository (for testing). Although x/debug has a disclaimer on it with respect to compatibility, it is less clearly experimental in its import path and long-term we do want it to maintain backwards compatibility, at least at compile time. By experimenting directly in x/debug, we risk tarnishing its reputation, so-to-speak.
To keep viewcore working as a tool, I think our plan is to temporarily have x/debug import x/exp, so it can take advantage of improvements we make.
Frankly, I don't expect the API to change all that much, but simultaneously it's hard to get a sense of the API in totality without first using it and iterating on it.

I updated the proposal to reflect these changes, and also updated the proposal's compatibility story based on our current thinking.

@mknyszek @jordanlewis is there any update now about viewcore in golang.org/x/debug or golang.org/x/exp, please? do we plan to add one tool to parse the dump file from debug.WriteHeapDump()？

Hey @superajun-wsj, unfortunately the focus on diagnostics lately has been on execution tracing. We still plan to come back to this in the near future and there's been a little bit of progress in June by @prattmic, but this is still a little ways off.
Thanks for your interest, and stay tuned.

Hi, thought you might like to know I got viewcore to work with binaries compiled by Go 1.20 and 1.21.
It's somewhat empirical, definitely not complete, and I haven't tried to make it compatible with multiple versions, but my branch it's at https://github.com/golang/debug/compare/master...bboreham:go-debug:go-1-20

I'm running into this issue with the latest version of go-debug and a dump generated by go 1.21: https://github.com/golang/go/issues/33661

Hi, @mknyszek , I've been trying to use viewcore recently, and I've found some strange errors. I'm also trying to fix some of them.
Friendly ping, is there any latest update or specific milestone for viewcore? For example, go1.23 go1.24
By the way, Are there any plans or reference implementations for supporting variable types on the goroutine stack?   Thank you !

@WangLeonard The current problem with viewcore is that the packages that back the implementation (mainly gocore) have not been updated for the Go 1.22 heap layout, which will probably require some refactoring to make work. Unfortunately, there is no specific milestone for viewcore and the core analysis packages at the moment.

Hi all, I recently implemented a heap reference analysis tool for dwarf type retrieval based on delve. It might be relevant to the problem mentioned in this issue. Welcome to discuss and exchange ideas with us.
repo: https://github.com/cloudwego/goref

There are feature requests on debug/gosym, such as #58474, which would be folded into the new x/debug packages. Though the title is about the gocore package, we envision having an API that operates only on a binary (without a core file). These APIs would be similar, with the core version obviously able to provide more complete information using data from the heap, etc. In some ways, these x/debug packages are a v2 of debug/gosym.
vulncheck (cc @zpavlinovic) is particularly interested in this work, as they have custom forks of debug/gosym and rsc.io/goversion/version to provide the extra functionality they need. These are a maintenance burden outside, so they'd like to move to supported packages ASAP, even while the API may not yet be finalized. If we start work in x/exp/debug (or x/debug/exp?) I think it would not be too much trouble to update vulncheck as needed as the API evolves since it is a first-party use.


Cannot run APIM On windows as a Service with Java 17

Description
Cannot run APIM On windows as a Service with Java 17 and yajsw-stable-13.08
Steps to Reproduce
follow https://apim.docs.wso2.com/en/4.2.0/install-and-setup/install/installing-the-product/installing-api-m-as-a-windows-service/

setup yajsw-stable-13.08 (this support java 17)
follow documentation and configure "wrapper.conf"
start the wrapper

Actual result : getting below error and terminated
NFO|wrapper|WSO2 Carbon|23-02-22 14:14:57|stopping process with pid/timeout 10428 45000
INFO|wrapper|WSO2 Carbon|23-02-22 14:14:58|process exit code: 1
system.env 58
INFO|wrapper|WSO2 Carbon|23-02-22 14:15:03|started process with pid 5480
INFO|wrapper|WSO2 Carbon|23-02-22 14:15:03|too many restarts: 5
INFO|wrapper|WSO2 Carbon|23-02-22 14:15:03|too many restarts: 5
INFO|wrapper|WSO2 Carbon|23-02-22 14:15:03|Shutting down Wrapper
NOTE:
same APIM pack is working with
java 11 and yajsw-stable-12.14"
Affected Component
APIM
Version
4.2.0
Environment Details (with versions)
beta pack
Relevant Log Output
INFO|wrapper|WSO2 Carbon|23-02-22 14:14:57|stopping process with pid/timeout 10428 45000
INFO|wrapper|WSO2 Carbon|23-02-22 14:14:58|process exit code: 1
system.env 58
INFO|wrapper|WSO2 Carbon|23-02-22 14:15:03|started process with pid 5480
INFO|wrapper|WSO2 Carbon|23-02-22 14:15:03|too many restarts: 5
INFO|wrapper|WSO2 Carbon|23-02-22 14:15:03|too many restarts: 5
INFO|wrapper|WSO2 Carbon|23-02-22 14:15:03|Shutting down Wrapper

Related Issues
No response
Suggested Labels
No response

@BathiyaL @rmsamitha
The issue can be resolved by following the below steps.

Download the latest version (13.05) of YAJSW from here.
Extract the content of yajsw-stable-13.05.zip to <YAJSW_HOME>
Copy the wrapper.conf file found in the <APIM_HOME>/bin/yajsw/ directory and paste it in the <YAJSW_HOME>/conf/ directory.
Delete the wrapper.java.additional.4 = -XX:MaxPermSize=256m line in wrapper.conf file
Rename the subsequent wrapper.java.additional variables to be in consecutive order.
i.e. Rename wrapper.java.additional.5 to wrapper.java.additional.4. Rename wrapper.java.additional.6 to wrapper.java.additional.5 and so on.
Additionally wrapper.conf can be overwritten by wrapper.conf in [1] .

[1] wrapper.zip

Tested the functionality on both JAVA11 and JAVA17 with YAJSW 13.05 on windows 11.


Interactive list PR

Hello,
I added required change to the project.
Thanks.


codeunit 90 "Purch.-Post" - events supporting Sales Tax calculations

Hello,
We have two events to request in the Purchase Post codeunit to support some addition sales tax processing that we have.  The first event shown we have internal varaibles to process, so we don't require any parameters, but logically you may want to add the PurcahseHeader variable.  The second is sort of a mirror of the same type of event in the PostSalesTaxToGL procedure (with some modifications of variables that your code does not need to access for the Prov. tax calculdation).  Thanks!
codeunit 90 "Purch.-Post"
......
    local procedure CalcProvincialSalesTax(PurchHeader: Record "Purchase Header")
    var
        TempPurchLineForProvSalesTax: Record "Purchase Line" temporary;
        TaxAreaLine: Record "Tax Area Line";
        TaxJurisdiction: Record "Tax Jurisdiction";
    begin
        OnBeforeCalcProvincialSalesTax();  // new event

        if (TaxOption <> TaxOption::SalesTax) or (SalesTaxCountry <> SalesTaxCountry::CA) then
            exit;

        TempPurchLineForProvSalesTax.DeleteAll();

....

    local procedure PostProvincialSalesTaxToGL(PurchHeader: Record "Purchase Header"; var TotalUseTaxAmount: Decimal)
    var
        TaxJurisdiction: Record "Tax Jurisdiction";
        GenJnlLine: Record "Gen. Journal Line";
        RemSalesTaxAmt: Decimal;
        RemSalesTaxSrcAmt: Decimal;
        IsHandled: Boolean;  // new event var
    begin
        // new event begin
        OnBeforePostProvincialSalesTaxToGLostSalesTaxToGL(PurchHeader, TotalUseTaxAmount, TempSalesTaxAmtLine, SalesTaxCountry,
            TaxOption, GenJnlLineDocNo, GenJnlLineExtDocNo, GenJnlLineDocType, SrcCode, Currency, GenJnlPostLine, IsHandled);
        if IsHandled = true then
            exit;
        // new event end

        if (TaxOption <> TaxOption::SalesTax) or (SalesTaxCountry <> SalesTaxCountry::CA) then
            exit;

        RemSalesTaxAmt := 0;

.....

    [IntegrationEvent(false, false)]
    local procedure OnBeforeCalcProvincialSalesTax()
    begin
    end;

    [IntegrationEvent(false, false)]
    local procedure OnBeforePostProvincialSalesTaxToGLostSalesTaxToGL(var PurchHeader: Record "Purchase Header"; var TotalUseTaxAmount: Decimal; var TempSalesTaxAmtLine: Record "Sales Tax Amount Line" temporary;  var SalesTaxCountry: Option US,CA,,,,,,,,,,,,NoTax;  TaxOption: Option ,VAT,SalesTax; var GenJnlLineDocNo: Code[20];  var GenJnlLineExtDocNo: Code[35];  var GenJnlLineDocType: Enum "Gen. Journal Document Type"; var SrcCode: Code[10];  var Currency: Record Currency; var GenJnlPostLine: Codeunit "Gen. Jnl.-Post Line"; var IsHandled: Boolean)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 13321.


Add support for XML type in stored procedure

Discussed in https://github.com/Azure/data-api-builder/discussions/1813

Originally posted by meareal October 14, 2023
Would be really nice to be able to use XML type in stored procedures
Stored procedure sample

dab-config.json file

DAB CLI

DAB Version

Thank you DAB team. It looks like all we would need to do is to add [SqlDbType.Xml] = typeof(string) in .Core.Services -> TypeHelper.cs -> _sqlDbTypeToType

Thank you Sean for the follow up.
We use XML in the request. Both on sprocs that query data and especially the ones that update data. This is how we do bulk updates. It is very performant.
JSON response works fine.


Could you provide some simple instructions on how to build from source

Hi I pulled the repo using git clone:
git clone --recurse-submodules -j8 git@github.com:shalzuth/AutoGunfireReborn.git
I them set IL2CPPDumper as the default project and dumped the dlls into a DummyDLL folder but I am a bit confused where to go from here
Thanks in advance

GunfireRebornDumper generates the DLL's using Il2cpp dumper, set GunfireRebornDumper as the default project. It will dump the dummy dlls, then create the proxy dlls.

Thanks


ZTF Matchfiles ingestion: track failures

We ran into several issues while ingestion DR16 on melman recently. DR17 was released yesterday, and we need to make sure the existing script allows for easy reruns.
After reading the current script carefully, we can see that the _id of every mongo document ingested is unique, and made of a baseid (unique, made of field, readout and filter) + matchid unique to each entries of the matchfiles.
Thanks to that, we do not need to flush the database before reingesting, as the behavior of MongoDB should be to ignore existing documents.
Therefore, we just need some extra tools to keep track of which files failed ingesting, so that we can retry ingesting only these files. If one uses rm then anyway only failed files will be left. However this allows reingestion when not using this argument, as well as keeping track of the error messages for each failed ingestion. Essential to figure out if anything needs to be modified to get around that failure.
Also, we add some extra arguments to the fetching script, which allow us to only download missing (useful if the download was interrupted), or to only fetch the csv without also downloading the files (useful for debug or when we want to decouple that process. That might be needed if we want to remove some already ingested files from the csv to only redownload the ones we need).
TODO: add a method to verify the download of files. If a file is corrupted, we delete it. That way, we can restart the script using the argument to only download missing files. Unclear how this will be done, as a checksum isn't provided. pytables format can contain some sort of checksum, and I believe that I've seen failures in production mentioning that the file didn't end as expected. If that's how it works, we could simply open and close the file. If opening it failed, then we can remove the corrupted file and retry the download.

NOTE: Tests are failing, working on it right now.


.setSrc() on IE8

.setSrc() returns error on IE8

Object doesn't support this property or method.

I used something like this.
var meplayer = new MediaElementPlayer('#meplayer',{type:'video/mp4'});
meplayer.setSrc('video.mp4'); meplayer.load(); meplayer.play();
Actually other methods too: .play(), .load()...
I noticed I can access other than setSrc() via $('video')[0].player.play();
use: v2.13.1

Tried the code above by copy/pasting it, but it seems that the success event is never triggered on IE8. Any insight on that @sebass ? I'm using the latest version of mejs.

Make sure to set the filetype. It's essential. But you probably did, since you did a copy paste. :-)
Furthermore: there is a small error in my script. The initial value of mediaElementInitialized should be false, not true.


Show Broken Jscookie

This one is a bit weird.
The actual bundle is at node_modules/js-cookie/src/js.cookie.js which is stated in the package.json
Closure tries to find it at js-cookie/index
ERRORS:
java -jar node_modules/google-closure-compiler/compiler.jar --flagfile closure.conf
built/basic.js:3: ERROR - required "module$js_cookie$index" namespace never provided
import * as jsCookie from 'js-cookie/index';
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

1 error(s), 0 warning(s)

This might be fixed by https://github.com/angular/tsickle/pull/462

Oh crap. That tsickle fix does not work. The reason is that tsickle re-writes imports to match the actual path that was resolved, which in this case is
<EMAIL_ADDRESS>rather than
node_modules/js-cookie/src/js.cookie.js
So you end up with basic.js containing
import * as jsCookie from '@types/js-cookie/index';
Needs more design thought.

FYI I have a new place for us to experiment with third-party library compatibility that doesn't bloat the hello-world example, see prototype: https://github.com/alexeagle/angular-closure-compatibility
We're still deciding where is the right place to put that.

Sorry we didn't get to finish this @FrozenPandaz - the Bazel stuff took over my life. I think next quarter we can revive this.
https://github.com/angular/closure-demo is the new location for the barebones closure demo and
things like this belong on
https://github.com/alexeagle/angular-closure-compatibility


   The "<about" back button was lost.  why? should be needed!!!!!!!!

#6875.  There's no I want to answer
i use the version is v1.3.1
could you tell me the problem still exists on  the future version

Hello, thanks for opening an issue with us! I will be closing this issue as a duplicate of #6875 . Unfortunately I do not have a good answer at the moment for when this will be fixed. Thanks for using Ionic!


This commit removes the /go implementation.
Signed-off-by: David Enyeart<EMAIL_ADDRESS>

@salimbene @mbwhite I noticed the erc-721 was moved to /chaincode-go but the original /go implementation was left behind.


16 Similar Error Definitions with Same & Different Names in Swagger Specs

16 Similar Error Definitions with Same & Different Names in Swagger Specs
There are several similar error definitions across Azure Swagger specs with same & different names.
In languages like Java and C#, similar error definitions with same & different names generate similar, multiple exception class definitions with same & different names in different name spaces.
Azure libraries for Java and other such languages carry a large surface area. A major part of API ergonomics is consistent naming themes, uniform definition of errors, uniform error handling, etc. Consistency makes it easier to use and memorize and also enables portability of learning. Having learnt a part of the library, developers can apply that learning across other parts of the libraries.
In Swagger specifications, designers should avoid duplicate definition of errors with same or different names. This, in turn, helps language-specific client library generators to choose an already existing exception class for each kind of abnormal condition that may cause an operation to thrown an error; define new exception classes, if needed.
The table below describes the current state - 16 similar error definitions with different names. These definitions can be represented with a single base error definition that comprises of {code, message, source-of-error, description, details} and Swagger specs MAY extend the definition to differentiate or pack additional info.

 The only commonality the type ItemError has with the others is an error message. Why would we change it to inherit from a type that has far more properties? That seems to go against the goal of making the Swagger spec accurately model the REST API.
FYI @chaosrealm @devigned

@brjohnstmsft BTW, there are two common items - message and description. Regardless, ItemError is different from other error definitions. So, removed it off the list

@Azure/adx-autorest-contributors and @Azure/openapi-advisors any thoughts on this issue?

@selvasingh @devigned
I work on the Batch team, so addressing some of the error types which were listed above from the Azure Batch service swagger specification.
The Errors you listed are almost all errors in the body of entities rather than errors which generate exception types.  For example, the following errors do not map onto exceptions:

DeleteCertificateError
JobSchedulingError
TaskSchedulingError
AutoScaleRunError
ResizeError
ComputeNodeError

These types are used because our service performs many operations asynchronously on behalf of the user and because the operation is not being performed in the context of a particular user API call, it doesn't make sense to propagate errors which occur as part of an asyncronous workflow as an exception. Thus they follow the FooError naming, but are not exceptions but are rather just properties.
The one that does map onto an exception is: BatchError
I believe that the topic of a common Exception or Error base class for use across libraries has been discussed, and if such a thing were to exist (for example in the client runtimes of each language with a code and message field), then BatchError ought to inherit from that (or maybe just use the base if it matches exactly).

Closing this since we are tracking it here - https://github.com/Azure/autorest/issues/1523


fix: UI: Added 'Delete Mappings' and 'Delete Documents and Mappings'

Fixes: #3865, #3866

Can you make these invoke backend service as I described in #3865 and #3866?

I thought I'd use existing infrastructure rather than write more core UI code.

The purpose is to centralize the logic to the backend, then UI only asks backend to manipulate the mappings/documents/libraries. It eventually removes the logic from UI code, even if it adds the REST invocations in short term.

Actually #3866 might be better to wait for #3750 and #1476 as it involves removing all persisted resources (inspection seed, inspection result, and from data source catalog) correlated to the Document.

Ok - so we only want Remove Mappings - I'll leave the UI side infrastructure in place but not visible.  The remove mappings core will DELETE /v2/atlas/project/{mappingDefinitionId}/mapping - correct?

yep and it's already here
https://github.com/atlasmap/atlasmap/blob/main/lib/service/src/main/java/io/atlasmap/service/MappingService.java#L106
Not sure if this works OOTB, it removes the mapping definition file at file level. But instead, it might need to remove Mapping entries from MappingDefinition instead, to keep DataSource, Constants and Properties. LookupTable would be removed as it's tightly coupled with mappings.


[v1alpha2] Modify image name for capbm for quay.io

Friday evenings... :tired_face: I forgot to change the name of the image from jbrette's repository.

/cc kashifest
/cc jan-est

/lgtm


ServiceMessageProcessingEvent for BasicMessage not triggering

Hi,
I have a Xamarin Edge Agent. I have subscribed to ServiceMessageProcessingEvent and am able to get the events such as OfferCredential, RequestPresentation, etc.
I want to receive an update when the Edge Agent gets a BasicMessage. However, I'm unable to receive any such event with the ServiceMessageProcessingEvent subscription.
Can anyone help me with this, please?

This is resolved by publishing an event in the DefaultBasicMessageHandler.cs.


Make invalid callback in call queue error more verbose

Closes https://github.com/godotengine/godot-proposals/issues/7408
This transformed an opaque:

Trying to execute a deferred call/notification/set on a previously freed instance. Consider using queue_free() instead of free()."

Into a sufficiently useful:

Trying to execute a deferred set (disabled) on a previously freed instance. Consider using queue_free() instead of free().

As this allowed me to search for set_deferred where the property being set was "disabled", which allowed to identify which objects were being freed, and from there debug the issue.

What IF the deferred thing is NOT a set but indeed a call?

What IF the deferred thing is NOT a set but indeed a call?

Instead of saying set (member name) it would say call (member name)

The change in question is getting reverted (https://github.com/godotengine/godot/pull/80081), so I'm closing this PR and the corresponding proposal. Thanks for your contribution nevertheless.


Corrupted output with llama prototype model

I understand the llama model is still a 'prototype', so it is expected to have some issues when running it.
I am nevertheless creating this issue hoping that my tests will help fixing them.
I am using openlm-research/open_llama_3b for a simple text-generation.
I am using the transformers-neuronx main branch.
The neuronx-cc compiler version is <IP_ADDRESS>+a3ad0f342.
The model is compiled with batch_size = 1, amp = 'f16', tp_degree = 2.
I use transformers.set_seed(42) to get reproducible results, using the same "One of my fondest memory is" prompt.
If I generate only 128 tokens, I get something that looks ok:
'<s> One of my fondest memory is my school time. Before I went to college, I was studying at Kofu Municipal Technical
 School in the north part of Yamanashi. It was a small school (about 300 students) but it was very cozy. Not just the school
 building, but the area where the school was situated was very calm and I was very happy living in that area.\nMy father
 was the principal of the school. I was a senior high school student and I got married when I was 19 years old. My father
 died when I was 35 years old. I stayed in'

But if I increase the number of generated tokens, the output tokens are duplicated or corrupted (here starting from token 133):
'<s> One of my fondest memory is my school time. Before I went to college, I was studying at Kofu Municipal Technical
 School in the north part of Yamanashi. It was a small school (about 300 students) but it was very cozy. Not just the school
 building, but the area where the school was situated was very calm and I was very happy living in that area.\nMy father
 was the principal of the school. I was a senior high school student and I got married when I was 19 years old. My father
 died when I was 35 years old. I stayed in that area until Iw at his office from 39 at least 568833 years later on this blog,
 I I’ The school'

The more tokens I generate, the worse it gets.

Hi @dacorvo:
Thank you for reporting this issue. We are looking into this, and we expect to have a fix in an upcoming release. We will update this ticket when this issue has been resolved.

Thanks @dacorvo . Looks like you are able to get batch 1 and 2 working with latest release 2.13 version of transformers-neuronx. We will track the batch size > 2 issue with https://github.com/aws-neuron/transformers-neuronx/issues/34 . In the meantime, I will close this ticket.


Add floors to locations.

Adds floors to all locations
Refactored closest location calculation to take in the entire location list rather than just the values
Heatmap weight now cannot go lower than 0.1 so it is always visible for all locations

Closes #116

Looks good to me


Unrecognized Windows Sockets error: 11: connect

I've got,
.nuget/packages/ikvm.maven.sdk/1.0.1/buildTransitive/netstandard2.0/IKVM.Maven.Sdk.targets(93,9): error : ArtifactTransferException: Could not transfer artifact (mvn_package:pom:version) from/to central (https://repo1.maven.org/maven2/): Unrecognized Windows Sockets error: 11: connect [(path_to_csproject)]
in docker container debian:bullseye-20220801-slim.
And everything works fine on Windows 10/11.

This is blocked on IKVM issue 89.

Issue 89: Socket Redesign for Linux

Should be solved in 1.2, which depends on IKVM 8.4.


Accept Widgets instead of only Text

Thanks a lot @gliden for this small updates but with huge impact I will update the published version


Test with autobahn.ws/testsuite ?

Not really an "issue," but I'm looking into WebSocket servers and was wondering how well websocketd handled against things like invalid UTF-8 messages, the client lying about its payload size, etc.
Have you ever run the Autobahn test suite against websocketd?  If so, can we see the results?  "The test suite will check an implementation by doing basic WebSocket conversations, extensive protocol compliance verification and performance and limits testing."
Example report for a bunch of WebSocket servers:
http://autobahn.ws/testsuite/reports/servers/index.html

I tried it today. Well there is lots of tests and some of them are not quite worth to implement unless people ask (as with compression in #174 )
I wonder what anyone here might think of importance of following to be fixed:

ping/pongs (we somewhat ignoring those because it's not something you can tell bash script)
fragmentation (same thing, if we support it we may only spend resources on server side)
tricky UTF8 cases (not many of them pass but I doubt much would as you rely on external tool like bash script to echo your data without much idea about input encoding)
couple tricky close test cases (somewhat important but we also did not leak anything)
websocket compression

I'm thinking there is not much we will do to specifically address test. I'll close it for now.
"Invalid headers or data will not break the websocketd" is my answer to the original question.


Simplify goroutine setup for async task requests

This change works, but I see that the total execution time jumps from ~500ms to ~2s though (both FULL TURBO). I can share the test I'm using (in front).
The execution time shouldn't change by much, because execution is closed off before the wg.Wait(), so I don't think this diff is the best either

Not quite what I meant. You're seeing a slowdown because the channel is unbuffered: writers must wait for an available reader. While the first request is pending, no one can write to the channel. So, the goal is to read from the channel as fast as possible and not block reading on IO. Pseudocode of one way to do it:
func start() {
  firstRequestDone := make(chan interface{})
	go func() {
		pending := []*request{}
		startedFirstRequest := false
	FirstRequest:
		for {
			select {
			case <-firstRequestDone:
				for _, req := range pending {
					go doReq(req)
				}
				break FirstRequest
			case req <- requestsChannel:
				if startedFirstRequest {
					pending = append(pending, req)
				} else {
					startedFirstRequest = true
					doFirstReq(req)
				}
			}
		}
		for _, req := range requestsChannel {
			go doReq(req)
		}
	}()
}

In this case, you have a single reader that never blocks. When it gets the first request, it starts it. While the first request is in flight, it buffers subsequent requests. When the first request completes, it fires off the buffered requests and switches to reading and immediately firing off requests

@gsoltis thanks! this mostly worked. Only thing I don't understand he requests channel receives a ton of nil messages and not sure where they're coming from.
I also don't quite get the for+select combo pattern, but I see it's a common way to listen for messages, so I'll read up on that.

Going to merge this into the base PR for a holistic look and put in any questions there.


Use custom resource in advanced config

close https://github.com/GoogleContainerTools/kpt/issues/1498

I wonder if we can do something like below to have clearer interfaces. Other function developers in golang can follow this pattern when they need config in ConfigMap and CRD.
Let me know if this makes sense to you.
type SetAnnotationConfig interface {
	Transform([]*kyaml.RNode) error
}

type CRDForSetAnnotationConfig struct {
	metav1.TypeMeta   `json:",inline" yaml:",inline"`
	metav1.ObjectMeta `json:"metadata,omitempty" yaml:"metadata,omitempty"`

	Annotations map[string]string `json:"annotations,omitempty" yaml:"annotations,omitempty"`
	FieldSpecs  []types.FieldSpec `json:"fieldSpecs,omitempty" yaml:"fieldSpecs,omitempty"`
}

func (c *CRDForSetAnnotationConfig) Transform([]*kyaml.RNode) error { return nil }

type ConfigMapForSetAnnotationConfig struct {
	corev1.ConfigMap `json:",inline" yaml:",inline"`
}

func (c *ConfigMapForSetAnnotationConfig) Transform([]*kyaml.RNode) error { return nil }

func decode(in []byte) (SetAnnotationConfig, error) {
	type k8sObject struct {
		metav1.TypeMeta `json:",inline" yaml:",inline"`
	}
	var obj k8sObject
	if err := yaml.Unmarshal(in, &obj); err != nil { /*do something*/ }
	switch {
	case obj.APIVersion == "v1" && obj.Kind == "ConfigMap":
		var cmCfg ConfigMapForSetAnnotationConfig
		if err := yaml.Unmarshal(in, &cmCfg); err != nil { /*do something*/ }
		return &cmCfg, nil
	case obj.APIVersion == fnCRDConfigAPIVersion && obj.Kind == fnCRDConfigKind:
		var crdCfg CRDForSetAnnotationConfig
		if err := yaml.Unmarshal(in, &crdCfg); err != nil { /*do something*/ }
		return &crdCfg, nil
	}
	return nil, nil
}

func run(resourceList *framework.ResourceList) error {
	...
	fnConfigBytes := convertToBytes(resourceList.FunctionConfig)
	cfg, err := decode(fnConfigBytes)
	err = cfg.Transform(resourceList.Items)
	...
}

This LGTM, will do it.

@mengqiy @Shell32-Natsu Why should we accept configMap as an input ? Isn't that confusing for the users as to when to use what ? Instead, if each function has it's own crd for input config, it is more uniform and clear IMO.

@phanimarupaka Because in the pipeline, if user specifies the parameters via 'configMap', it will be converted to a ConfigMap. We have to support this case.

@mengqiy Please review again.

@phanimarupaka Because in the pipeline, if user specifies the parameters via 'configMap', it will be converted to a ConfigMap. We have to support this case.

Why should we allow users to pass parameters via configMap. I commented on the pipeline definition doc as well. It would be nice if there is single way to pass inputs to function. WDYT ?

@phanimarupaka Because in the pipeline, if user specifies the parameters via 'configMap', it will be converted to a ConfigMap. We have to support this case.

Why should we allow users to pass parameters via configMap. I commented on the pipeline definition doc as well. It would be nice if there is single way to pass inputs to function. WDYT ?

I think the reason is we want to provide a convenient way for uses to provide simple configs instead of forcing them to write a CRD for every function even when they don't want additional configs.

@Shell32-Natsu @phanimarupaka We need a broader discussion with @droot about if it should be a best practice for a function to support both ConfigMap and CRD. The decision is affected by the hydration design. We can discuss it offline if needed.
Supporting CRD in the functions in this PR is anyway needed.


values set in launchSettings.json override values set in the system

Fixes #17763

@serpent5  please review
To review the doc build

download https://www.dropbox.com/sh/yy994551cje0kap/AAB0tRnm7gze2kYrSYPSFHIda?dl=0
unzip
view HTML file in FF (Fire Fox). It best to view the doc with the widest window that has no left or right TOC (Table  of contents)

@serpent5  thanks for the review.


Fix ambiguous comment

Found this quite confusing and it seems this is the correct way around

Thanks @jaymeyerowitz . FYI, since 6.0.0 release --rbac is default on.

Awesome @tamalsaha. Will keep that in mind


Issuer validation failed. Issuer did not match: visit external storage account resources

Hi, I am trying to visit an external user's storage resources by letting them login the AzureAD app, store their Bearer token to session, and send get request to https://<external user's storage account>.blob.core.windows.net/?comp=list.
But it always return error '<?xml version="1.0" encoding="utf-8"?><Error>AuthenticationFailed<Message>Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.\nRequestId:xxxxxxx0-00xx-00xx-xxxx-20xxxx000000\nTime:2019-06-11T20:52:26.2516628Z</Message><AuthenticationErrorDetail>Issuer validation failed. Issuer did not match.</AuthenticationErrorDetail></Error>'.
The tutorial on this page definitely works fine if it's same user has storage account and AzureAD App, but how about authorizing visiting to another user's blobstorage?

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

ID: d02de0bf-09d7-a7fc-1b4a-213426e96b2d
Version Independent ID: 36f6c8fe-6bc1-6643-4b66-2c38bcd2e5f0
Content: Authenticate with Azure Active Directory to access blob and queue data from your client application
Content Source: articles/storage/common/storage-auth-aad-app.md
Service: storage
Sub-service: common
GitHub Login: @tamram
Microsoft Alias: tamram

@yixue-at-symantec Thanks for posting, Issuer validation failed. Issuer did not match.'. most likely means that the possible token used is generated for a specific service different than the one you're trying to access. For example, tokens can be generated based on services: Blobs, or Files, or Queues, etc... if you use one that's for another service, you may receive the error message. My best advice is to check the Expiration date on the token that has been generated as well as the service for which it was generated for. Let me know if this works.

Hi Adam,
I am pretty sure that the access-token is not expired and the sevice(probably i should call it resource) is https://storage.azure.com/, and I am using https://login.microsoftonline.com/common/oauth2/authorize to get the token.
My findings:

if I set the external User's source be "External Azure Active Directory", then it works well, but if the external user's source be "Microsoft Account", then I always get the "Issuer ddi not match" error.
If I set the external user's source remains "Microsoft Account", and I create a new account under the domain of the original external user, and login AzureAD with the new account, i don't have the error and can get the storage resources.

Thanks.

@yixue-at-symantec The documentation seems to be correct, but doesn't mention your specific case, I'll triage it as a doc-enhancement. If it's an issue, that's blocking you, I'd recommend posting in either MSDN or StackOverflow forums for help, or opening a support case(I can help you if you don't have a support plan), let me know which option you'd like me to follow up on

We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Is it necessary to unsubscribe before subscribing with new parameters?

For a location-based application, we have to update the subscriptions frequently, i.e. every time a user moves significantly. Is it necessary to unsubscribe in this case before subscribing to the same publication, but with other parameters? Or is it sufficient to just re-subscribe, as it is done in a regular Meteor client?
In the latter case: what happens to event handlers that have been registered on the previous subscription? Will they be automatically purged?

This library is doing nothing more than implementing a communication protocol.
I might be wrong, but your question seems to be related to Meteor's usage and strategy, I think it should be asked on the Meteor forum instead.


standardize on env vars for py libs

details to come. just clearing out todos from notes

Not sure if this is related to your intention for this issue, but here's a case that's frustrating when working with arguments and inline python:
Consider this example:
Name: Text inline python args
Args: foo: an argument

#!python3
print(os.environ['foo'])

I would expect I can call it this way but it fails because the arguments are not populated in the environment. However, this same script would work if it were call as a tool from another gptscript:
gptscript testpy.gpt --foo bar
15:57:28 started  [main] [input=--foo bar]
15:57:28 sent     [main]
Traceback (most recent call last):
  File "/tmp/gptscript1115266740", line 1, in <module>
    print(os.environ['foo'])
          ^^
NameError: name 'os' is not defined. Did you forget to import 'os'?
15:57:28 failed to run tool [text inline python args] cmd [/usr/local/bin/python3 /tmp/gptscript1115266740]: exit status 1
2024/03/28 15:57:28 ERROR: Traceback (most recent call last):
  File "/tmp/gptscript1115266740", line 1, in <module>
    print(os.environ['foo'])
          ^^
NameError: name 'os' is not defined. Did you forget to import 'os'?
: exit status 1

Calling the same script works all the time this way:
$ foo=bar gptscript testpy.gpt
16:01:39 started  [main]
16:01:39 sent     [main]
16:01:39 ended    [main]

OUTPUT:

bar


Allow the adapter to fetch objects out of a collection.

Helpful for when we want to pick out a specific collection object, using a combination of default adapter and this adapter.

This is necessary for fetching a model out of a collection by id.

@Jmeyering thanks for PR and sorry for the late response.

<EMAIL_ADDRESS>


createCustomEnvironment not documented

What does createCustomEnvironment do?

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

ID: fa498d54-1576-498a-b8b5-189f2859a884
Version Independent ID: 0642e827-92b5-5f30-e162-c7220de4089f
Content: Conda Environment
Content Source: docs/pipelines/tasks/package/conda-environment.md
Product: devops
GitHub Login: @erickson-doug
Microsoft Alias: brcrista

conda is both a package manager and environment manager. createCustomEnvironment set to True tells this task that you want to create an environment instead of using the default one.

Docs have been updated to clarify this and other arguments.  Thank you!

create an environment link does not exists. Please update the doc with correct link.

@DavidStaheli
In the Azure pipeline conda step, can we specify conda.yaml file path, such that it creates env from the yaml file?

@brcrista can you please advise?

@praneetmsft we've learned that the task can't cover every scenario.  We're in the process of deprecating the task and recommend you just use script for working with Anaconda environments.
We have a new guide just for using Anaconda in Pipelines, you can see it here: https://docs.microsoft.com/azure/devops/pipelines/languages/anaconda#from-yaml
Thanks for pointing out the broken link, I'll fix that.

@brcrista In principle I'm very much in favour of exposing functionality with CLI tools. I see two problems with the new approach though:

Activating an environment has to be done for each subsequent task that needs to use it. That is quite cumbersome. Any way to work around that and make it persist?
Having to change PATH just to use conda is a bit awkward, for one thing because of the syntax ##vso[.. syntax) and also because it's different per operating system. What about a UseConda task that does this automatically?

Agreed on both counts.  The way each step runs in a fresh system environment / process has been feedback we've heard before, especially with conda.  That was a fundamental decision made a long time ago in what it means to be a "step."  The original Conda Environment task was an attempt to address this, but Anaconda environments end up having a lot of customization options that the task just can't cover.  @vtbassmatt and I have kicked around some new ideas on how to address this in a script-first way for the YAML world.
Yeah, putting every tool in PATH does get hard to scale for reasons like this.
@vtbassmatt , being able to say use: conda and go look for an install location might be a good solution here too.


Wrong realease date on website?

Hi there thank you for creating this awesome library!
I just noticed that if you go to the project website and scroll all the way down to the release notes, it reads 2021 in all the two releases, I guess it should be 2022 according to the GitHub release?

https://github.com/DioxusLabs/docsite

Missed that repo, thanks!
Seems to be fixed now...

Thanks for the report - I fixed it but forgot to update this issue :)

Haha all good! Thanks again and keep up the good work! :rocket:


[Nightly] It makes you scroll too far to close the keyboard

it should hide almost instantly when you start scrolling up
on ios theme i just scrolled an entire 5000+ message convo without it hiding
after scrolling to bottom, the scrollController goes completely insane
and it never hides the keyboard again
¯_(ツ)_/¯
gesture detector implementation just worked better

My branch


Assign a volume to persist orders on restart

Assign a volume to backend so that orders are persisted across restarts.
Document a production ready database.
Database currently lives inside the container in the working directory as database.sqlite. To make a copy of the database run:
docker cp <container id>:/usr/src/app/database.sqlite .

This is now possible and an answer has been added to the FAQ.


Additional scripts for test cases.

Team,
Please review and approve.
Thank you.

A newer version is available.


Calendar Formatting documentation is incomplete

What type of issue is this?
Documentation issue / typo
What SharePoint development model, framework, SDK or API is this about?
Declarative list formatting
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested

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

Additional environment details

browser version
SPFx version
Node.js version
etc

Issue description
As a first-time user of calendar view formatting, I attempted to recreate the steps outlined in the article https://learn.microsoft.com/en-us/sharepoint/dev/declarative-customization/view-calendar-formatting but was unsuccessful implementing the steps as written.
Problem
When a new calendar view is created on a list, fields that are not available to be edited using the Modern Calendar view editor control are not included in the view definition (i.e. any fields other than title, start and end date are not added).  When a user who is new to modern view configuration tries to add the JSON to the advanced formatting of the view, the formatting interpreter cannot find the field name "PROJECT" in the view definition and defaults to the "no matching value found" use case.
** Solution **
Provide instructions in this article that tell the user to edit the new Calendar view through the List Settings page and add the "PROJECT" field to the list of fields to be displayed.  This will add the field to the view definition and make it available for the custom formatting interpreter to find the appropriate field to use in the formula.

Happy to write this up if an admin wants to assign this issue to me.

Hi @calebmil, I tried to improve the article. Let me know if further changes are needed.
Alternatively, feel free to fork the sp-dev-docs repository and submit a change to be merged.
See you!

@andrewconnell I took a look at the note about making sure that the PROJECT column already exists before creating the calendar view.  My experience was that the PROJECT column is consistently NOT added to the Calendar view whether it exists at the time of view creation or not.  The pointer to go to List Settings and add the column to the view through the Classic view editing interface is what solved my problems.

@calebmil If there's an error with the docs, please create a new issue (feel free to reference this one).


⚠ Bofrost.at has degraded performance

In 6fedc86, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2180 ms

Resolved: Bofrost.at performance has improved in 1f54040.


allow-spec-url-load and allow-spec-file-load toggles not working in 9.1.2

Was testing out the new release and noticed that these toggles are not working properly for me - they have no effect on the resulting html that is generated. I verified that I am using the 9.1.2 dist.
allow-spec-url-load="false"
allow-spec-file-load="false"

thanks for reporting , I will investigate it further

we have the patch window open till first week of sept if we fix it by then will get released

just had a quick check , it works as expected for me
allow-spec-url-load show/hide the url bar on the header
allow-spec-file-load show/hide the button on the header to load a JSON
to see the effect of these attributes you should have show-header = "true"
<rapi-doc
  spec-url = "./specs/petstore.yaml"
  show-header = "true"
  allow-spec-url-load = "false"
  allow-spec-file-load = "false"
></rapi-doc>

Hm I tried this and it doesn't work for me. Just to be clear, these are the buttons that I am wanting to hide. Are these buttons not the ones that those two attributes control?

no they aren't, for now we dont have a specific attribute to control those.
To hide it it needs show-info="false" which will hide the entire overview section.
We checked with other renderers, who would also provide a way to download the spec. would you like to hide them specifically ?

Yes I would like to specifically hide those if that wouldn't be too hard to implement. None of our clients need to see those buttons so at the moment they are sitting there taking up space.

okay, have similar request from our internal users will add allow-spec-file-download attribute which will be defaulted to true
should find it soon in next patch release

we set the default value allow-spec-file-download = false.
But I recommend always specify the desired value for attributes and do not depend on defaults. As we have changed defaults in the past in different releases.


XBox Series S/X Support

What is currently missing for supporting the new protocol version and therefore the new XBoxes? Is there a specific part where I could help with?

Implementation of Nano v3 is missing entirely. Is that something you want to help with?

Yes, but I have no idea where to start.

The Xbox One X is very similar to the Series X|S, therefore if you have an Xbox One/X/S then you should be capable of running those games

The Xbox One X is very similar to the Series X|S, therefore if you have an Xbox One/X/S then you should be capable of running those games

I have an Xbox series X, which only has remote game function in the latest system.
Remote games can make the client directly connect to the game controller through the Internet
In addition, the network of the controller can be in NAT, and there is no need to disclose the accessible ports.
At least it looks like it's penetrated through the intranet

I have an Xbox series X, which only has remote game function in the latest system.
Remote games can make the client directly connect to the game controller through the Internet
In addition, the network of the controller can be in NAT, and there is no need to disclose the accessible ports.
At least it looks like it's penetrated through the intranet

I guess Microsoft provides a server to support FRP
But I'm in China, China's Xbox network is terrible
But the function of remote game can provide me with high-speed game experience
It's really amazing

I guess Microsoft provides a server to support FRP
But I'm in China, China's Xbox network is terrible
But the function of remote game can provide me with high-speed game experience
It's really amazing

I just got to know UPnP, please forgive my stupidity.
So it looks like Xbox app is directly connected to the controller.
Maybe xbox live has the ability of service discovery?

I just got to know UPnP, please forgive my stupidity.
So it looks like Xbox app is directly connected to the controller.
Maybe xbox live has the ability of service discovery?

So there is a gamecontroller that directly connects to the cloud and TV wirelessly to let you gamestream? wow.
If thats not what you are saying, I dont understand your posts at all.

So there is a gamecontroller that directly connects to the cloud and TV wirelessly to let you gamestream? wow.
If thats not what you are saying, I dont understand your posts at all.

Maybe it's a Plug-n'-play android device, i'm not entirely sure...

Maybe it's a Plug-n'-play android device, i'm not entirely sure...

Hi, my Xbox Series X arrives tomorrow and i would like to support you with the Implementation of Nano v3. Do you have any information about the protocol yet? or do we have to reverse engineer it? Did you already run some tests to verify if the crypto / salting part is still the same?

Hi, my Xbox Series X arrives tomorrow and i would like to support you with the Implementation of Nano v3. Do you have any information about the protocol yet? or do we have to reverse engineer it? Did you already run some tests to verify if the crypto / salting part is still the same?

As the devs said before, nano v3 is not openly available to the public, so they can't implement series x|s support. When it does eventually, it will be supported, but until then, you'd have to stick to your phone.

Just checking to see if there has been any updates on nano v3 for XBox Series X.  If you have any additional information I could possibly try to help with implementation or testing of the feature.


php希望添加 composer支持

rt
希望加入 php的 composer

It would be very nice if there was some way to utilize composer within codeapp. this would make it possible to use laravel and many other open source code from the php community.


Create Mainhub View

According to figma,
Use Material Ui components.
Its important that the profile Button is accessible.

closed as of 581c5dc


This app attempts to access privacy-sensitive data without

When submitting the app with Xcode 8 i get an error requesting me to add keys to the .plist. Not sure what the best course of action is here. I could work around it for now by deleting the files I didn't need as adding all the keys seems like a ground for rejection. M aybe there's an option to separate them into different modules?

Dear developer,
We have discovered one or more issues with your recent delivery for "app-name". To process your ? delivery, the following issues must be corrected:
This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSContactsUsageDescription key with a string value explaining to the user how the app uses this data.
This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSCalendarsUsageDescription key with a string value explaining to the user how the app uses this data.
This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSBluetoothPeripheralUsageDescription key with a string value explaining to the user how the app uses this data.
This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSMicrophoneUsageDescription key with a string value explaining to the user how the app uses this data.
This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSMotionUsageDescription key with a string value explaining to the user how the app uses this data.
Once these issues have been corrected, you can then redeliver the corrected binary.
Regards,
The App Store team

Yeah that new policy kind of breaks this library. You could split it up in different modules, but that would be quite the hassle to integrate into projects.

😞 This is really sad. Apple is trying to make things harder.

PermissionScope also has this problem.  I was looking for a project that addressed it.  Sadly, Apple comes up with lots of restrictions and yet has no API to address it.  Since nearly every app requires some sort of permission, they should provide a better API as well as a better user interface for permissions.  What the have now is inadequate.

@timlehr I don't think it would be such a hassle. Simply pod 'Permission/Notification' and all other modules you require. I wouldn't mind helping out on the migration.

@hartbit @delba would also be happy to help in the migration if there is a plan to modularize things.

Would love some sort of update on this. I literally use the library to manage Notification permissions via Carthage, and just received this email on my latest app submission. I'm thinking the workaround is to come up with defaults, but seeing as I don't request them, I'm afraid of further rejection.

We addressed the issue in our library by hiding all permissions behind build flags, so code that is not used will never ship. It does require users of the library to place an xcconfig file in a pre-defined location. CocoaPods users can just specify the sub specs they need without any further configuration:
https://github.com/iosphere/ISHPermissionKit

@shagedorn do you know if it's possible to do that with Carthage?

@AndrewSB Carthage just builds the shared schemes in your project. I think if there was a scheme to load from a configuration similarly to CocoaPods uses configurations, it could be done.

That sounds doable @justinmakalia.
I'm (not) looking forward to splitting my permission library into 9 (or is it more?) framework targets 😔
Happy to help with the migration as well, though

@AndrewSB Not really sure how best to handle the enumerations if we're hiding them behind flags, using
open var status: PermissionStatus {
  switch type {
    #ifdef CONTACTS_PERMISSION_ENABLED
      case .contacts:          return statusContacts
    #endif
    ...
  }
}

is the best way to go about it

@justinmakaila not sure I understand what you said. Are you saying that ⬆ is or isn't the best way to go about the migration?

Started work on https://github.com/delba/Permission/pull/75.
Lemme know what you guys think

The Swift 3.0 is finally out for Carthage:
github "delba/Permission" >= 2.0

There still is some work to do for CocoaPods (creating the subpod etc.) :/
If someone feels like submitting a PR for that, it would be wonderful 😃
Thanks to all the contributors 🎉

I create a PR for this #78. @delba can you have a look and tell me what you think

Hey everyone, the Permission pods are here:
use_frameworks!

pod 'Permission/Camera'
pod 'Permission/Notifications'

Again, to all the contributors, thank you.
I guess it's time to close this issue now 😅


pins are offset

Hi,
It looks like pins are slightly offset compared to where they should point. In the attached screenshot, the four pins should point directly to the road, at the crossing.

It seems, in my usage, that they're centred to the centre of the circular part (the head of the pin), whereas expected & common (elsewhere) behaviour is for the tip / point of the pin to be at the coördinates with the remainder above that position (exactly like a physical pin in a paper map).
This difference is most pronounced the further zoomed-out I'm viewing map+pins.


Initial SS4 upgrade work

Needed this for a site upgrade, so I’ve quickly thrown it together (hence no test coverage/doc updates!). The button now lives in the popup menu:

tagged as 0.2.0 - a shame tests aren't passing, but that can be looked into later. thanks @kinglozzer


Don't show D&D target cursor for original text selection

Testing #21012:

select some text
start D&D operation
move the mouse pointer (which marks the drop target location) over the original text

Observe: the dotted cursor is shown but if you end the D&D operation by releasing the mouse button, nothing happens.
Since the original selected text is not a valid drop target, no dotted cursor should be shown.

This behavior is aimed to be backwards compatible. Without Drag and Drop, clicking on a selection will move the cursor to the place your click. So right now with Drag and Drop, if you click on a selection, move it around and drop it inside the selection, we still shrink the selection to the place where the target is.

So IMHO, we can either

Stick with current behavior, or
Do not show dotted cursor if the target is inside the selection, and when users release the mouse, keep the selection instead of shrinking it.

Let me know if my explanation makes sense.

I suggest to use the second option:

It gives the correct feedback that there is no target
it is the same behaviour that you find in other text editors.

Right now as we can't distinguish a pure mouse down event and a drag event in DND contribution, we always shrink the selection if the dnd target or the mosuedown target is inside the selection.
I'll make enhancement to this part together with https://github.com/Microsoft/vscode/issues/21320 .


Add Login with Github feature

Task

[ ] Add the ability to login and authenticate with github

So that we can then use the oauth tokens to fetch the commit status

@haroon-sheikh in order to request access_token from GitHub we would need the server to call GitHub API since its payload requires client_secret which we cannot expose from the client side. What do you think about it?

@asadkhalid305 We would need to create an oauth and set the client_id and client_secret as environment variables. Look at this for example https://levelup.gitconnected.com/how-to-implement-login-with-github-in-a-react-app-bd3d704c64fc
Please create an oauth app under your fork but leave it pickup these client_id and client_secret from env variables. Make sure you dont commit your details ;)

@haroon-sheikh I am glad for the article you shared. With some modifications I have made this feature more clear and precise. Now all you have to do is use access_token which is stored in localStorage to work further on the application.
Please review PR

@haroon-sheikh I am hoping you review and merge the PR before Hacktoberfest ends.

Fixed in #78