partially restructure the source tree

Restructure the Foundation modules into subdirectories for ease of discoverability.  This restructures the tree into the standard Apple framework-like layout with a subdirectory for each Swift "framework" module.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

Test with following PRs:
apple/swift#29634
@swift-ci please test Linux platform

Looks like there is a duplicate copy of Boxing.swift in ./Sources/FoundationNetworking/URLSession/Boxing.swift even though the ./Sources/FoundationNetworking/CMakeLists.txt refers to the one in ../Foundation/Boxing.swift

@swift-ci please test Linux platform

@spevans removed the duplicate copy, thanks for pointing that out

@swift-ci please test Linux platform

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test Linux platform

@swift-ci please test

What is the benefit of moving all of the files around? Doesnt it now require knowledge of which subdirectory a file is in? Im not sure this actually helps in anyway.

@spevans it actually helps quite a bit with discoverability.  It also makes it easier to grep within a single target (e.g. FoundationNetworking vs FoundationXML).

@swift-ci please test

@swift-ci please clean test

@swift-ci please clean test

@swift-ci please test

Please test with following PRs:
apple/swift#29804
@swift-ci please test Linux platform

Please test with following PRs:
apple/swift#29804
@swift-ci please test Linux platform

Please test with following PRs:
apple/swift#29804
@swift-ci please test Linux platform

Please test with following PRs:
apple/swift#29804
@swift-ci please test Linux platform

@swift-ci please test Linux platform

@swift-ci please test Linux platform

@swift-ci please test Linux platform

@swift-ci please test Linux platform

@swift-ci please test Linux platform

@swift-ci please test Linux platform

Please test with following PRs:
apple/swift-corelibs-xctest#298
@swift-ci please test Linux platform

Please test with following PRs:
apple/swift-corelibs-xctest#298
@swift-ci please test Linux platform

Please test with following PRs:
apple/swift-corelibs-xctest#298
@swift-ci please test Linux platform

Please test with following PRs:
apple/swift-corelibs-xctest#298
@swift-ci please test Linux platform


[PE-D][Tester B] Exit command will cause java.nio.file.AccessDeniedException

Labels: type.FunctionalityBug severity.Medium
original: ThomasHoooo/ped#1

Duplicate issue
This issue is a result of the jar file having insufficient permission to save data to a write-protected directory and not due to task select being not functional. This is the same as #75

Explanation is given in the FAQ section of the user guide.


build: remove Javadoc workaround

I haven't gone over the warnings in detail, but there were plenty of warnings before and the build no longer fails, so I consider that an improvement. Thanks for the review!


Bump Scala 3 to RC1

This currently fails due to a reworked API of TASTy Reflect:
[error] -- [E006] Not Found Error: /Users/kmetiuk/Projects/scala3/tools/dotty-release-scripts/ecosystem_projects/foo/inspector/src/main/scala/inspector/Inspector.scala:11:24
[error] 11 |    val inspector = new TastyInspector {
[error]    |                        ^^^^^^^^^^^^^^
[error]    |                        Not found: type TastyInspector
[error] -- [E008] Not Found Error: /Users/kmetiuk/Projects/scala3/tools/dotty-release-scripts/ecosystem_projects/foo/inspector/src/main/scala/inspector/Inspector.scala:18:14
[error] 18 |    inspector.inspectTastyFiles(List(tastyFile))
[error]    |    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[error]    |    value inspectTastyFiles is not a member of Object

inspector project relies on the processCompilationUnit method which was removed. Using TastyInspector object directly without that method results in tests failures (read null instead of some meaningful content). @nicolasstucki any idea how to fix this?

The API changed. I will update it.

@anatoliykmetyuk branches should be created in dotty-staging, not in this repo just as we do for dotty.

Replaced with #12


Unit test issue

Hi
I tired to write unit tests using XUnit to test the libplctag class to check adding ,removing tags to the dictionary etc... I get an exception cannot load object with incorrect format.
Yet the same code in the test works in a console project.
Please help
Thanks

Post the code somewhere so I can have a look

Hi
Please find the code as you suggested the error I get is below and yet in a console project the code works . what is specific about a unit test that causes it to fail?
Thanks
		System.BadImageFormatException

An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
at LibplctagWrapper.PlcTagWrapper.plc_tag_create(String lpString, Int32 timeout)
at LibplctagWrapper.LibPlcTag.AddTag(Tag tag) in C:\Ref\OpenSource\libplctag-csharp-master\LibplctagWrapper\LibPlcTag.cs:line 43
at LibPlctagWrapper.Tests.PlcInterfaceTests.TestingAddTagCorrectlyAddsTag() in C:\Ref\OpenSource\libplctag-csharp-master\LibPlctagWrapper.Tests\PlcInterfaceTests.cs:line 24
        [Fact]
        public void TestingAddTagCorrectlyAddsTag()
        {
            // Arrange
            var client = new LibPlcTag();

            const string plcIp = "<IP_ADDRESS>";
            const string plcPath = "1, 1";
            const CpuType plcType = CpuType.LGX;

            var tagControlWord = new Tag(plcIp, plcPath, plcType, "CONTROL_WORD", DataType.Int32, 1);

            // Act
            client.AddTag(tagControlWord);

            // Arrange
        }

You probably have to force the build to be X86, and not AnyCPU for your unit test project.

Hi
Indeed x86 works , thanks for the help
Laz


Linux context match

Adds a talon context match to match on the window title to signify nvim
Wasn't clear if I should be merging this into beta or main. The main branch works fine for me locally and when we were testing it was fine, but I am realizing the readme says I should be using beta.

Indeed, main branch is fine. I'll delete the beta branch and mention in the readme.


Don't connect to setlist.fm if no API key

I don't have a setlist.fm key and for testing purposes don't need one. This minor change makes it easier to run locally without slowing things down by continuously getting 403s from setlist.fm because of a missing API key.

Not quite sure what Github is doing with this - it's saying changes need to be addressed but they have been - is it in the right state for you to approve?

Not quite sure what Github is doing with this - it's saying changes need to be addressed but they have been - is it in the right state for you to approve?

The last change is adding the braces for the if-statement in the suggested change I have above

Ah! Fixed now. I need to set up the formatter...

Ah! Fixed now. I need to set up the formatter...

Don't worry too much about it - I'll let most syntax stuff go, I just mentioned this one so you know my preference for the future. My formatter will fix anything up next time I touch the file so it's no big deal


[RUNTIME] Deprecate cupy and export nccl APIs from xla

Background
Currently, Alpa uses cupy as the python API binding for nccl. This causes two problems

We need to do conversion between cupy tensors and xla tensors. Although we can achieve zero-copy through dlpack, this part of code is error-prune and hacky.
There can be conflicts between the nccl used by cupy and the nccl used by XLA. cupy.nccl and xla/nccl_utils can initialize and call two different versions of nccl if we don't link or compile them correctly. This leads to unknown hanging issues.

To fix these problems, we can deprecate cupy.nccl and export NCCL apis from XLA. This makes sure we only use one version of nccl and avoids tensor conversion.
TODO

[ ] Export NCCL APIs from XLA

See also cupy/nccl.pyx, xla/nccl_utils.cc
Implement c++ functions in xla/nccl_utils.cc
Implement bind in xla.cc
Call c++ functions by xla_extension
Add nccl_utils to BUILD

[ ] Replace all usage of cupy.nccl in alpa with the NCCL APIs exported from XLA

xla uses stream_executor instead of the most original CUDA stream APIs
get rid of cupy, dlpack tensor types, and use XLA DeviceArray directly. Make sure the arrays are well synced since they are on GPUs
XLA DeviceArray is not indexable, so it might require some special handling, e.g., converted to JAX. All conversion needs to be zero-copy
How to handle the FREE instruction

@scv119 Are you interested in this issue? It's related to how alpa runtime deals with GPUs and should be helpful for you to explore how alpa runtime works.

@TarzanZhao

OK


Server placeholder

Is there a way to put a server as an placeholder?
Example:
[KITPVP] Snorgelo: Yo
So it's like [{SERVER}] {NAME}: {MESSAGE}

That's not possible currently, I can add it to the BungeeCord side when I get time.


infra: switch deployment image tag from latest to specific tag (0.7)

Pull Request
What changed?

Switches the deployment tag from latest to 0.7 which is the most current tag.
Updates configmap to match current .env (fix APP_URL, switch phpredis to redis)

Why did it change?
When new releases are tagged, deployment.yaml needs to be updated accordingly.  This will allow kubectl apply to push a change that the cluster can detect, without having to use imagePullPolicy: Always, not to mention the other benefits of tracking the deployed version in version control itself.
This PR is notable because of the bugfixes including the problem with using the latest tag.  Otherwise, release PRs should get their own template at some point, the standard one is kind of cumbersome.
Did you fix any specific issues?
none
CERTIFICATION
By opening this pull request, I do agree to abide by the Code of Conduct and be bound by the terms of the Contribution Guidelines in effect on the date and time of my contribution as proven by the revision information in GitHub.

I continue to look for alternatives to raw k8s deployments or to needing a PR for every release.  Some gitops actions on a new tag push using kustomize and/or helm might do the trick.  also looking into flux, but that might be a bit much for our tiny cluster.


MudRadio : Color apply when just ReadOnly, not disabled

Feature request type
Enhance component
Component name
MudRadio
Is your feature request related to a problem?
No response
Describe the solution you'd like
I use MudRadio for report screen with MudRadioGroup
I set ReadOnly property of MudRadioGroup to true.
I apply color  to one of MudRadio item which is correct answer.
But it does not apply color because of ReadOnly property. (https://github.com/MudBlazor/MudBlazor/blob/dev/src/MudBlazor/Components/Radio/MudRadio.razor.cs Line 29)
ReadOnly and Disabled states are looking same but they are different
MudRadio must apply color when it is just ReadOnly.
I suggest to remove  !GetReadOnly() condition when building ButtonClassname

Example
https://try.mudblazor.com/snippet/cEGoYjwVSnFfnKPO
Have you seen this feature anywhere else?
No response
Describe alternatives you've considered
No response
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

Would you be interested in creating a pull request? It might apply to MudSwitch and MudCheckBox as well, I haven't checked.


pandas-profiling not compatible with pandas v1.0

Describe the bug
pandas-profiling not compatible with pandas v1.0. The key method "ProfileReport" returns error "TypeError: concat() got an unexpected keyword argument 'join_axes'" as join_axes is deprecated starting from Pandas v1.0.
https://pandas.pydata.org/pandas-docs/stable/whatsnew/v1.0.0.html?highlight=concat
To Reproduce
import pandas as pd
import pandas_profiling
def test_issueXXX():
df = pd.read_csv(r'')
pf = pandas.profiling.ProfileReport(df)
TypeError: concat() got an unexpected keyword argument 'join_axes'
Version information:

Python version: 3.7.
Environment: Command Line and Pycharm
pandas-profiling: 1.4.1
pandas: 1.0

I"m getting the same error. was there a solution to this?

@neongreen13 to address this, I decided to downgrade pandas to before 1.0. To downgrade, I uninstalled Anaconda and reinstalled using the October 2019 installer from here: https://repo.anaconda.com/archive/

@penock Thank you! that worked for me too - using pandas 0.25.0 in a new environment. Cheers!

I do not want to downgrade. If any one can let me know that with the current version of Anaconda, when this or are this error going to be taken care, so that we can use Pandas profiling.
TypeError: concat() got an unexpected keyword argument 'join_axes'

@penock can we do this by not reinsatlling? Any other alternative?

Nope I haven't found a way. I would guess the pandas_profiling folks will
fix it in the next couple months, and until then I'm using pandas 0.25
installed via installing the old Anaconda 3 from last October.
On Sat, Apr 4, 2020 at 2:45 PM Himanshuaroraa<EMAIL_ADDRESS>wrote:

@penock https://github.com/penock can we do this by not reinstalling?
Any other alternative?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pandas-profiling/pandas-profiling/issues/376#issuecomment-609072260,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACQ74OFYOPVSUSO3YY2PVKDRK553NANCNFSM4KTN27OA
.

Many issues are related to pandas v1: #401, #409, #415, etc. Working on a solution.

Having this exact issue, hoping this is resolved soon
pandas = v1.0.1
pandas-profiling = v1.4.1

Nope I haven't found a way. I would guess the pandas_profiling folks will fix it in the next couple months, and until then I'm using pandas 0.25 installed via installing the old Anaconda 3 from last October.
…
On Sat, Apr 4, 2020 at 2:45 PM Himanshuaroraa @.***> wrote: @penock https://github.com/penock can we do this by not reinstalling? Any other alternative? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#376 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACQ74OFYOPVSUSO3YY2PVKDRK553NANCNFSM4KTN27OA .

@penock  I have upgraded the pandas profiling to 1.3/1.4 and it works for me.
you should all try that.

Hi All,
When we work and establish something -that's what we measure in the ongoing
process and make it as a practice to run the process in the enterprise.
If a product evolves it has a backward compatibility that makes it more
sustainable.
Its good to research and explore and improve the product. But adoption of a
product means its sustainable. So when a version changes it should have the
backward compatibility in the pipeline of change. This is not here in case
of pandas profiling so it fails in adopting  the feature that anybody like
to make it as industry standard.
I would rather prefer if there is a change in any product , its dependent
should be technically capable of not dropping that feature, as most cases
are not similar like this.
Thanks,
Debashis
On Sun, Apr 12, 2020 at 4:36 AM Himanshuaroraa<EMAIL_ADDRESS>wrote:

Nope I haven't found a way. I would guess the pandas_profiling folks will
fix it in the next couple months, and until then I'm using pandas 0.25
installed via installing the old Anaconda 3 from last October.
… <#m_5181534547951474040_>
On Sat, Apr 4, 2020 at 2:45 PM Himanshuaroraa @.***> wrote: @penock
https://github.com/penock https://github.com/penock can we do this by
not reinstalling? Any other alternative? — You are receiving this because
you were mentioned. Reply to this email directly, view it on GitHub <#376
(comment)
https://github.com/pandas-profiling/pandas-profiling/issues/376#issuecomment-609072260>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACQ74OFYOPVSUSO3YY2PVKDRK553NANCNFSM4KTN27OA
.
@penock https://github.com/penock I have upgraded the pandas profiling
to 1.3/1.4 and it works for me.
you should all try that.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pandas-profiling/pandas-profiling/issues/376#issuecomment-612588580,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKEORMEQSEENWZQZZYUQ743RMGDTXANCNFSM4KTN27OA
.

Pandas-profiling is now compatible with pandas 1+. For more information, please have a look at the v2.6.0 release notes.

The code has been changed and if you don't want to downgrade your program, try with this code instead of< join_axes>.
For example,
result = pd.concat([df1, df4], axis=1, join_axes=[df1.index])
--> result = pd.concat([df1, df4], axis=1).reindex(df1.index)
Good luck for everyone!

update to pandas-profiling to v2.4.0+

@penock I have upgraded the pandas profiling to 1.3/1.4 and it works for me.
you should all try that.

Didn't work for me

Pandas-profiling is now compatible with pandas 1+. For more information, please have a look at the v2.6.0 release notes.

v2.6 is not available in conda yet?

Pandas-profiling is now compatible with pandas 1+. For more information, please have a look at the v2.6.0 release notes.

v2.6 is not available in conda yet?

It is!

Pandas-profiling is now compatible with pandas 1+. For more information, please have a look at the v2.6.0 release notes.

v2.6 is not available in conda yet?

It is!

conda install -c conda-forge pandas-profiling installs v1.4.1 by default

@SiddhantSadangi Could you please provide some details (OS, Conda version etc.) on this issue: https://github.com/conda-forge/pandas-profiling-feedstock/issues/22. That way we can try to fix the issue.
Does fixing the version work for you?
conda install -c conda-forge pandas-profiling=2.6.0

yeah, I installed 2.6 via pip
adding details to the issue

I have installed latest version of pandas-profiling and its working for me.
conda install -c conda-forge/label/cf202003 pandas-profiling

Hi all,
I'm getting the same issue whilst trying to sample some data. I've tried to install 2.6 but I'm still getting the same error message?
"concat() got an unexpected keyword argument 'join_axes'"

Hi all,
I'm getting the same issue whilst trying to sample some data. I've tried to install 2.6 but I'm still getting the same error message?
"concat() got an unexpected keyword argument 'join_axes'"

Sounds like an incompatible version of pandas. Alternatively, you could set up a clean environment to see if the error persists.

Hi all,
I'm getting the same issue whilst trying to sample some data. I've tried to install 2.6 but I'm still getting the same error message?
"concat() got an unexpected keyword argument 'join_axes'"

Sounds like an incompatible version of pandas. Alternatively, you could set up a clean environment to see if the error persists.

I'm using Collabatory due to some issues with running Exoplanet code in Windows. It says that im running Pandas 1.0.3 and I've tried to update pandas-profiling which now says its running 2.6.0.
I've tried running it in a new notebook however the error still persists.

@hughesymendes Could you make a new issue with the following information:
Could you provide the minimal information to reproduce this error? This guide can help crafting a minimal bug report.

the minimal code you are using to generate the report

which environment you are using:

operating system (e.g. Windows, Linux, Mac)
Python version (e.g. 3.7)
jupyter notebook, console or IDE such as PyCharm
Package manager (e.g. pip, conda  conda info)
packages (pip freeze > packages.txt or conda list)

a sample or description of the dataset (df.head(), df.info())

i get an error as follows:
data=pd.DataFrame(np.array([[1,2,3,4],[5,6,7,8]]))
ppf.ProfileReport(data)

FileNotFoundError                         Traceback (most recent call last)
/usr/local/lib/python3.6/dist-packages/matplotlib/style/core.py in use(style)
113             try:
--> 114                 rc = rc_params_from_file(style, use_default_template=False)
115                 _apply_style(rc)
7 frames
FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/lib/python3.6/dist-packages/pandas_profiling/pandas_profiling.mplstyle'
During handling of the above exception, another exception occurred:
OSError                                   Traceback (most recent call last)
/usr/local/lib/python3.6/dist-packages/matplotlib/style/core.py in use(style)
118                     "{!r} not found in the style library and input is not a "
119                     "valid URL or path; see style.available for list of "
--> 120                     "available styles".format(style))
121
122
OSError: '/usr/local/lib/python3.6/dist-packages/pandas_profiling/pandas_profiling.mplstyle' not found in the style library and input is not a valid URL or path; see style.available for list of available styles

Pandas - Profiling not working out in Google Colab
Two ways have tried. (Both Screenshots Attached)
!pip install --user -q datascience
!pip install --user -q pandas-profiling
import pandas as pd
import pandas_profiling
profile=pandas_profiling.ProfileReport(ipl_india)
profile.to_file(outputfile  ="ipl_india_2017_preprocessing report.html")
Error: '/usr/local/lib/python3.6/dist-packages/pandas_profiling/pandas_profiling.mplstyle' not found in the style library and input is not a valid URL or path; see style.available for list of available st
!pip install --user -q datascience
!pip install --user -q pandas-profiling
import pandas_profiling
profile = pandas_profiling.ProfileReport(ipl_india)
profile
Error: OSError: '/usr/local/lib/python3.6/dist-packages/pandas_profiling/pandas_profiling.mplstyle' not found in the style library and input is not a valid URL or path; see style.available for list of available styles

I have the same issue with google colab described by TuringEmmy.

@TuringEmmy @belouali The issue you are reporting is different from the one in this issue, which doesn't help resolving it...
Please create a new issue with a minimal example.


移动端定时任务界面无法横向滚动

Qinglong version
2.15.6
Steps to reproduce
移动端chrome登录青龙，选择定时任务菜单
What is expected?
无法横向滚动查看定时任务列表
What is actually happening?
定时任务列表可以横向滚动
System Info
No response
Any additional comments?
No response

@kingsleygithub001 强制更新下

@kingsleygithub001强制更新下

好耶，更新后已修复


feature: reference graphs through API to remote system with token

Issue type
[X ] Feature request
[ ] Bug report
[ ] Documentation
Environment

Python version:  2.7
NetBox version:  2.1.3

Description
A number of monitoring and graphing systems make available device/port graphs through an API rather than a direct unauthed URL. It would be helpful to be able to reference these graphs using an API call with a token to improve on the graph integration.
Having said this, sometimes it is also necessary to to pull the graph information from multiple sources depending on the device being referenced. Based on the current implementation there isn't a way to set a specific graph template per customer/site.

This was discussed on the mailing list recently. Because the graphs are embedded using <img> tags, there is no mechanism available for sending an authorization header with the request. It might be possible with an AJAX request but you have to jump through some hoops to embed the retrieved image and I'm not interested in going down that path.

Having said this, sometimes it is also necessary to to pull the graph information from multiple sources depending on the device being referenced.

The embedded graphs were only ever meant to be a convenience feature. If you have a single NMS with no or basic authentication, great. If not, it won't fit your needs; #969 should provide a better solution in that case.


Intuition on VRAM requirements for various models + quantization recipes

What is the URL, file, or UI containing proposed doc change
README.md, or an addendum
What is the current content or situation in question
The naive understanding would be that llm-compressor requires roughly the VRAM of the unquantized model + some overhead, and that overhead is affected by the exact recipe and arguments (speed/memory tradeoff)
What is the proposed change
It could be very helpful to give a few examples, or a rough dimensional estimate of how much VRAM is needed relative to various base models and for various recipes
Additional context
This helps with ensuring users aren't over/under provisioning for the task. In my case I jumped to 2xH200 for a 123B model to avoid a run possibly failing mid run. Happy to seed this with my findings once the run is completed

Actually, found this under a secondary readme:

Note that running non-sequential GPTQ requires significant additional memory beyond the model size. As a rough rule of thumb, running GPTQModifier non-sequentially will take up 3x the model size for a 16-bit model and 2x the model size for a 32-bit model (these estimates include the memory required to store the model itself in GPU).

Hi @selalipop! This is indeed a good intuition. You can also check out some examples of quantizing large models using accelerate and the calculate_offload_device_map function.
Keep in mind, these requirements are likely to change slightly in the next release as more options for running forward calibration through models are introduced.
Please feel free to reopen if you have any specific questions about specific models or algorithms!


[SPARK-5707] [SQL] fix serialization of generated projection

Merged build triggered.

Merged build started.

Test build #36735 has started for   PR 7272 at commit 075ef76.

Test build #36735 has finished for   PR 7272 at commit 075ef76.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Thanks!  Merging to master.


fix: improved error handling

Purpose
Describe the problem or feature in addition to a link to the issue(s).
Resolves #57 and #58.
Approach
How does this change address the problem?

Checks the ./.git folder exists before attempting to delete it.
Catches errors during rollback and presents both to the user.

TODOs

[x] Documentation updated (if required)
[x] Build and tests successful

@satyarkar Another review please, missed some linting issues.


What should I do if the stepper motors are wired "incorrectly"?

I ordered six motors and all of them are wired in the "incorrect" configuration where the resistance pins are not adjacent to each other. Is there a way to resolve this issue in software or should I rewire the cables?

If you have some precision tweezers or maybe a needle, it's possible to pull the connecting pins out of the connector and rewire them like that. I would recommend trying that before chopping any wires or getting into soldering, though either one would work fine


More Qt tweaks

12439e9 - removes (ugly) rounded top and bottom
Before:

After:

492e810 - unify the look of elements and fix the (ugly) outline
Before:

After:

7bd524d - the background is just a huge white png now, this can be easily done via css instead (no visual changes)
14f1a8f - changed the inner part to be a transparent one (no visual changes)

looking at the first before and after image, why are a couple pixels missing on each corner?

@PastaPastaPasta good catch, I didn't notice this! It looks like the outer border is still rounded for some reason and I can't find a way to fix this. I wonder how things look like on other OSes... but thinking more about it - why do we have the black border at all here? There is no such thing for context menus for example (which are kind of similar to comboboxes in some sense). Pushed 3cd14a5f9 with the updated style and added new screenshot in the PR description.


Remove component Switch and replace with the PF4 component

Feature enhancement request:
Follow-up issue after #1396
Existing custom Switch does not bring much value and can be replaced by PatternFly Switch component.

The main functionality provided by the  custom Switch was translating the ON/OFF messages.
@sjd78 @sgratch
Do we want to stop translating ON/OFF labels? Or just inline the onText, offText props?
FIY the current functionality has 2 serious bugs:

OFF message is not translated due to typo (offTest  instead of offText)
widget is broken on VM Detail screen if translated label is longer then English  (caused by forcing handleWidth={30})

Example (the upper switch is not translated to show the difference):

@rszwajko, @sgratch - I vote that we just follow the current PF switch guidelines: https://www.patternfly.org/v4/components/switch
Basically always show the slider and enable/disable it based on the edit state.
I don't see a need for a text label driven by the state since we have decent field labels to begin with.  If we really want to drive an on/off message, that should customized the the field.


Update App.js

Q
A

Bug fix?
yes

New feature?
no

New sample?
no

Related issues?

Minor bug fixes

Called the correct jsom button
namespace fixed for constants

Hi @gautamdsheth, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Looks good, thanks!


minor: update nightly eval

Motivation

followup https://github.com/sgl-project/sglang/pull/1754
Modifications

Checklist

[ ] Format your code according to the Contributor Guide.
[ ] Add unit tests as outlined in the Contributor Guide.
[ ] Update documentation as needed, including docstrings or example tutorials.

ref https://github.com/sgl-project/sglang/actions/runs/11625976966


Arguments object properties should throw an error when non-configurable

function foo(a) {
  Object.defineProperty(arguments, "0", {configurable: false});

  var args = arguments;
  (function() { "use strict";
    delete args[0];
  })();
}
foo(1);

Expected: TypeError, deleting non-configurable property in strict mode
Actual: No error

Likewise, delete on a non-configurable property in sloppy mode returns true and should return false.

This inconsistency still exists.
V8, Spidermonkey and Javascriptcore throws the expected TypeError.


toltecctl: Fix typo in uninstall function

As pointed out by @isaacwisdom in #364, there is a typo in toltecctl’s uninstall function: it invokes uninstall_force but the function is actually called uninstall-force. This slipped through the testing in #356 since I changed the function name after doing the tests and forgot to re-test it afterwards.

 Maybe also point out that this path means everything in /opt as not everyone will have that technical knowledge and work primarily with /opt. Wouldn't mind approving this as well while on it.

Good suggestion, thanks! I changed the message to use $toltec_dest instead of $toltec_src. You will need to re-approve the PR before it can get merged.


Add files via upload

official website URL: https://www.st-etienne.org

@xunxiang012 Regrettably, this request has signs of fraud. I have to close it without merging.


Corrected path to application

C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\sqlserver should be C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\sqlservr (only 1 "e" in the app name)

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

@gbritton1 - thank you for the careful read and submission. #sign-off


BAMBK8S-47: Bamboo agent Helm chart

A chart for deploying bamboo agents. Agents are:

ephemeral in nature
short-lived
not public
only communicate with the pre-provisioned bamboo server.

As such:

they do not have a database
they do not have local-home
they do not have shared-home
they do not have an ingress
fluentd support is deliberately not provided - Log capture for ephemeral agents seems overkill. Happy to discuss this further though.

Additionally the chart does not support the following as the other product charts do:

additionalLibraries
additionalBundledPlugins
additionalVolumeMounts
additionalJvmArgs - image does not support JVM_SUPPORT_RECOMMENDED_ARGS

Notes about tests:
Due to the fact that many of these features are not supported some of the unit tests have been updated to skip testing the agent charts. This is done with the annotation:
@EnumSource(value = Product.class, names = {"bamboo_agent"}, mode = EnumSource.Mode.EXCLUDE)

Note this change also includes some minor updates to the bamboo server chart including additional tests

@errcode1202 nice work! I played a bit with a k8s Operator that launches agents this way based on Bamboo job queue state. It's just a fun project though.
Quick question about agent registration and scaling up/down. Since agent home isn't persisted, it'll be a new agent every time a new pod starts or restarts. Thus, we can have situations when a pod is killed if it exceeds mem cap, evicted, and so on. Also, if you scale up/down this deployment 10 times a day, you'll have 10 offline agents a day and potentially lots of them, if some kind of automation does the scaling like a cron job.
We have seen customers with 1000s of registered agents in the database which is caused by the usage pattern - creating and deleting agents on demand like this. This causes big issues with Bamboo performance since at times Bamboo needs to check all agent's capabilities.
Ideally, when such a stateless agent pod restarts, we need to "unregister" an agent (post shutdown hook). Or, maybe run a k8s job that does that every now and then - delete offline agents that have a particular naming pattern. In both cases though such a job/hook will need api token or username/pass. My lame attempts to do that
Maybe it's worth adding a note to docs and check with Bamboo team to confirm that such a usage pattern can lead to performance issues over time.

@errcode1202 nice work! I played a bit with a k8s Operator that launches agents this way based on Bamboo job queue state. It's just a fun project though.
Quick question about agent registration and scaling up/down. Since agent home isn't persisted, it'll be a new agent every time a new pod starts or restarts. Thus, we can have situations when a pod is killed if it exceeds mem cap, evicted, and so on. Also, if you scale up/down this deployment 10 times a day, you'll have 10 offline agents a day and potentially lots of them, if some kind of automation does the scaling like a cron job.
We have seen customers with 1000s of registered agents in the database which is caused by the usage pattern - creating and deleting agents on demand like this. This causes big issues with Bamboo performance since at times Bamboo needs to check all agent's capabilities.
Ideally, when such a stateless agent pod restarts, we need to "unregister" an agent (post shutdown hook). Or, maybe run a k8s job that does that every now and then - delete offline agents that have a particular naming pattern. In both cases though such a job/hook will need api token or username/pass. My lame attempts to do that
Maybe it's worth adding a note to docs and check with Bamboo team to confirm that such a usage pattern can lead to performance issues over time.

Hey @bianchi2 thanks for highlighting this behaviour. This is actually something I had noted, admittedly I assumed that Bamboo would clean out these "stale" agents (at some point) and remove them from its database. I have a demo tonight with the team on the current charts so I can definitely show case this as a potential issue. We have a dedicated engineer for this work so we may be able to add this to Bamboo server itself as an improvement. Failing, and depending on what the Bamboo folks think, we'll take our cues from you ;) and look at implementing a job, or shutdown hook, which I think would be a cleaner option. Very cool operator by the way!


Debugging crash in xrBeginFrame with SteamVR backend

Sometimes when my application calls xrBeginFrame, OpenXR crashes on xr_generated_loader.cpp:434 with message:
Exception thrown at 0x00007FFFB0A5665A (d3d12SDKLayers.dll) in RavEngineVR.exe: 0xC0000005:
Access violation reading location 0x0000000000000000.

Occasionally it also logs Unable to create draw lists in the console but not every time.
How should I debug this? I can't see very much through the dispatchtable or call stack:

So I think this is probably a SteamVR issue, or maybe a Windows or driver one. (Also it's strange to see the 11on12 layer in there, it almost certainly will not handle SteamVR d3d calls right) The loader is just the top thing in that call stack that you have source for. I'd suggest reaching out to any SteamVR dev rel contacts you might have. I'll ping some folks for you too.
Does this happen with hello-xr when running using d3d11 and otherwise similar setup?

My application is using Direct3D12, SteamVR version is 1.22.13
With the same computer and headset, I get a crash in hello_xr on D3D12 (same crash as #313, not in xrBeginFrame). hello-xr on D3D11 and OpenGL works correctly, the rest of the APIs are reported as unsupported.

Check the dxcpl and other dev settings, I'm guessing that the d3d11on12 layer is to blame here. Also you may wish to clean install SteamVR (and maybe update your GPU drivers and maybe manual install the Vulkan runtime?) because I was just testing it yesterday on Windows, and it reported all graphics apis as supported.

is this related to #313 I wonder? I have been doing a lot of steamvr d3d12 testing with the CTS, this may have been fixed.


[APIReview] Consider DeleteItemIfUnchanged

Convenience method - DeleteItemIfUnchanged(T item)

This is the normal flow, so will be skipping this.


Added reuse validation for integration test

Ref: https://issues.redhat.com/browse/OSD-7506

Codecov Report

Merging #639 (093c4f6) into master (cf42def) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #639   +/-   ##
=======================================
  Coverage   24.07%   24.07%
=======================================
  Files          46       46
  Lines        4478     4478
=======================================
  Hits         1078     1078
  Misses       3325     3325
  Partials       75       75


RFC: Change Version Scheme for baseimage-docker

I am proposing we change the version scheme for the tagging of baseimage-docker container images to match the version of LTS Ubuntu which it is built from and attach our semantic version.
Here is one idea:

phusion/baseimage-docker:18.04-1.0.0

Any additional feedback is welcomed! I would like to solidify this before we cut the next release.

I feel that we are well past "Version 1.0" of baseimage-docker and should graduate to a more mature versioning scheme, this is why I have proposed the above.

I think that semver is awesome, and there are some tools which do automation on semver that insist your tags must be rigidly semver without deviating.
18.04-1.0.0 does not parse in a semver context.  18.04 is also not semver.
I am not sure that it matters here, as the context I'm thinking of in particular is fluxcd, and you are not expected to run an unmodified baseimage-docker in any real environment.  So it might be more important for our tags to communicate something clearly, which 18.04-1.0.0 does nicely.

Thanks for the input!
On Tue, Oct 22, 2019, 11:29 AM Kingdon Barrett<EMAIL_ADDRESS>wrote:

I think that semver is awesome, and there are some tools which do
automation on semver that insist your tags must be rigidly semver without
deviating.
18.04-1.0.0 does not parse in a semver context. 18.04 is also not semver.
I am not sure that it matters here, as the context I'm thinking of in
particular is fluxcd, and you are not expected to run an unmodified
baseimage-docker in any real environment. So it might be more important for
our tags to communicate something clearly, which 18.04-1.0.0 does nicely.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/phusion/baseimage-docker/issues/543?email_source=notifications&email_token=AAAN5NLEISRK2GDCAKSS5J3QP5BBXA5CNFSM4JDFPIJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB6XS5Q#issuecomment-545094006,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAN5NNER3UV6UAZ4ZUISFTQP5BBXANCNFSM4JDFPIJQ
.

Maybe this adds more complexity, but an alternative is removing the 18.04 part from the tag, and add to the image name, like phusion/baseimage-docker-18.04:1.0.0 or phusion/baseimage-docker:20.04-1.0.0.

@rdeavila if we go based on standard Docker community established conventions (looking at common container images available on Docker Hub) we can see that the convention is to keep it in the tag.

I would suggest:

phusion/baseimage-docker:bionic-1.0.0
phusion/baseimage-docker:cosmic-1.0.0

Easier to read and more in line with the official ubuntu image tags.

Implementing new version strategy based on @brandonkal suggestion.

The official ubuntu image tags are:
18.04, bionic-20200403, bionic
19.10, eoan-20200410, eoan
20.04, focal-20200423, focal, latest, rolling
20.10, groovy-20200505, groovy, devel
14.04, trusty-20191217, trusty
16.04, xenial-20200326, xenial
So to be inline with official tags would mean to at least have the number and the name. Not one or the other.

@SuperSandro2000 I don't think it is necessary to go beyond bionic-1.0.0 as if you look at the Docker Hub for Ubuntu you will see that we can build from the bionic tag and we are not doing any regular/nightly builds.
I see your point regarding security updates though, it would be nice to know which image it was built from, but you can determine that from the date the image was built. It would in some sense be redundant, it would also make it so we cannot automate the build process as easily. and have super-long image tags.
Anyone else have input regarding this?

I did not mean that this image needs nightly builds or support every version of Ubuntu. I wanted to say that I would prefer two tags: bionic-1.0.0 and 18.04-1.0.0 for the same image.

@SuperSandro2000 that's certainly reasonable. I did not mean to imply that you had indicated nightly builds, I was stating that if we were to be doing nightly builds, we would include the 20200403 portion of the version in our tags. I will release two tags based on your input:

bionic-1.0.0
18.04-1.0.0

@SuperSandro2000 Just wanted to let you know I do appreciate your feedback and I agree entirely with you, I'v been super stressed at work lately and I should not allow it to affect my pragmatism. I hope to have the CI/CD pipeline working properly soon and have already made some recent changes to that effect. We use GitLab CI at work and I just haven't had the time to really take a deep dive into Travis CI, ironically enough it is named after me.
I just pushed up the new version.

@SuperSandro2000 CI pipeline is fixed, builds are fully automated now. 👍
Thank you for the inspiration and motivation! <3


fish 3.1: test_special_characters_double_quoted (test.test.TestFish) ... unexpected success

Since we have updated fish to 3.1 in Fedora, the package fails to build with:
test_special_characters_double_quoted (test.test.TestFish) ... unexpected success

I know how to fix this for us, by removing the test from:
https://github.com/kislyuk/argcomplete/blob/d2c12c3bfca2f1f11ad0737462360fba035fa71d/test/test.py#L1250-L1255
But I have no idea how to make it xfail only with fish 3.0.

How about this?
 class TestFish(_TestSh, unittest.TestCase):
     expected_failures = [
         'test_parse_special_characters',
         'test_comp_point',
     ]
    if get_fish_version_somehow() > (3, 1):
        expected_failures.extend([
            'test_special_characters_double_quoted',
        ])

Sure, do we have a rady get_fish_version_somehow? I am not familiar with fish at all.

Neither am I, but I would imagine it would be an environment variable like in bash: https://github.com/kislyuk/argcomplete/blob/d2c12c3bfca2f1f11ad0737462360fba035fa71d/test/test.py#L29. I don't have an environment handy at the moment to try the same for fish.

$ fish -c 'echo $FISH_VERSION'
3.1.0

>>> FISH_VERSION = subprocess.check_output(['fish', '-c', 'echo $FISH_VERSION']).decode().strip()
>>> FISH_VERSION_TUPLE = tuple(int(i) for i in FISH_VERSION.split('.'))
>>> FISH_VERSION_TUPLE >= (3, 1)
True

Looks good to me. Would you like to submit a pull request?

I won't get to it soon, sorry.

Should be fixed, let me know if you're still having issues.


Investigate possible slicing speed problem

It seems that in tests/unit/cube/test_Cube.py -v Test_slices_over many of the tests got much slower when introducing the new lazy data handling (#2364).
E.G. test_1d_slice_coord_given, taking 12sec instead of 1.7.
E.G. whole of Test_slices_over takes 75sec instead of 9.9sec.
This is decidedly peculiar, as the test data used is not lazy but a real numpy array ?

The data used in these tests are not lazy, but somewhere down the stack this happens:
cube.slices_over(stuff):
L.2718: return self.slices(stuff)
cube.slices(stuff):
L.2790: dims_index = list(self.shape)
cube.shape(stuff):
L.1594: shape = self.lazy_data.shape
I haven't worked out yet what takes so long, but this is the only place I can see that the original tests interact with the lazy array handling.

Spot on @corinnebosley !
Speed tests seem to indicate it is the lazy_data() call, and can be fixed by avoiding creating a lazy array if you don't need it, just by testing 'self.has_lazy_data()' first.
It seems like dask has a substantially higher overhead for creating a basic wrapper object than biggus.
A quick search shows there may be other places this could have an impact.
I'll think about that a bit longer + submit a PR to improve.

Now produced code to spit out test timings for all Iris tests.
See : #2372

This needs reassessing to see whether it is still an issue

No longer a problem.


Update build reports path for multi-project build

Update Saving arbitrary build outputs example to support multi-project Gradle builds

Thanks for your contribution @daniel-shuy


Cannot open database

public SQLite.Net.SQLiteConnection GetConnection()
{
var sqliteFilename = "earthplatdb.db3";
string documentsPath = Environment.GetFolderPath(Environment.SpecialFolder.Personal); // Documents folder
string libraryPath = Path.Combine(documentsPath, "..", "Library"); // Library folder
var path = Path.Combine(libraryPath, sqliteFilename);
		// This is where we copy in the prepopulated database
		//Console.WriteLine(path);
		//if (!File.Exists(path))
		//{
		//	File.Create(path);
		//}

		var plat = new SQLite.Net.Platform.XamarinIOS.SQLitePlatformIOS();
		var conn = new SQLite.Net.SQLiteConnection(plat, path); << EXCEPTION HERE

		// Return the database connection
		return conn;
	}

Could not open database file: /var/mobile/Containers/Data/Application/3238691B-A7DF-4D54-8568-0C78008B0DD1/Documents/../Library/earthplatdb.db3 (CannotOpen)
What am I doing wrong???

Closing this, issue is it won't open when trying to check a database value in the tabbed page:
override protected void OnCurrentPageChanged()
works if I take the code out of that override...


[bug]: Textual Inversions Produces Vastly Inferior Results to A1111

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
No response
What happened?
I used Automatic1111 to create a .pt embed.  The embed works as expected in Automatic1111.  When used in Invoke, the results are far inferior to what I get in A1111.  I would expect that with the same prompt, same size, same seed, same sampling steps, and same sampler, I would get comparable results.  Perhaps not identical, but comparable.  However this is not the case.  The results in Invoke are consistently worse - much worse - than A1111, indicating that something is happening in Invoke.  I have had similar results with other embeds, but having trained this one, I can say with confidence that it's not the embed.  It's Invoke.
Screenshots

Additional context
A related but different issue is that I can't call the embed by using the file name.  I can only call it by using the name that appears in the command line interface.  In A1111, I can call the embed simply by using the file name or the name that appears in the Command Line.
Here's the embed if you'd like to try  it.
memphis-style.zip
Contact Details
<EMAIL_ADDRESS>Steve Warner#1284 on Discord

About the filename, seems that this changed (filename != from prompt word) when the new embedding manager was implemented in 2.2.5. Now it gets the term from inside the embedding.... the issue is that when we use an intermediate file, if from auto1111 it includes the step (like myterm-20250) and then we have to use it in the prompts.
Would be good to have an option to revert using the filename

Just so I understand, the issue is not with training with the IAI text inversion script but with the same embed file not producing decent results in IAI. Have you compared results using HF concepts files?
Also are you taking advantage of AUTO1111 hypernetworks or other features that we don’t currently support?

Correct.   The issue is not with the training, but with the embed not producing comparable results in IAI.
This is not the only case where I've encountered embeds not performing well in Invoke.  Some came from HF.  Some came from Civit.  In most cases, they "work" meaning they produce some effect.  But the effect is either far less pronounced in Invoke than A1111 or it produces subpar results compared with A1111.
An embed should produce comparable results (not necessarily identical, but at least aesthetically comparable) in both apps.  Especially when the same Sampler, Steps, CFG, etc. are used.  However the screengrabs above show that this is not the case.  This means the issue is with Invoke, as the .pt file works as expected in A1111.

@realstevewarner are you sure you using same base model? In A1111 screenshot model is v1.5-pruned-emaonly, while on InvokeAI model is stable-diffusion-1.5

I'm sure.  Here's a screenshot:

In the image above, the Invoke command line shows the path that it's loading the .ckpt file from.  Below you can see a file explorer.  The left side of the explorer shows the file path and file name for the base 1.5 model install along with the file size and date.  On the right of the explorer, you can see the path to the A1111 install folder.  Same base model name, file size and date.
I'm not sure why Invoke calls it that when A1111 gives the full ckpt file name, but they're definitely the same.


Add new Cloud Storages

See How to add new Storages
Proposed ideas are:

[x] Mega

[ ] OneDrive

[ ] Dropbox

[ ] Amazon Cloud Drive

Other ideas are also welcome.

Hey Buddy can u add these cloud storages.
archive.org
filecorn.com

hey can you also add the feature to add url links and upload them to cloud

Its there since the start of the project(See README), please clarify if you're talking about something else.

Maybe he was referring to downloading files from direct links like www.jellyfish.com/sample.mp4
This would download sample.mp4 file and upload to cloud


RStudio doesn't build anymore

See https://hydra.nixos.org/build/176099719. Log tail:

qtPreHook
unpacking sources
unpacking source archive /nix/store/78kqfbj786m0yxj3sh5j2br0969prpr4-source
source root is source
patching sources
applying patch /nix/store/l04kvqr5gdlgh3imxpniq6r274c6q61w-r-location.patch
patching file src/cpp/core/r_util/REnvironmentPosix.cpp
applying patch /nix/store/a70nybb2ri1z3jv1c5i7x7g3383ji41z-clang-location.patch
patching file src/cpp/core/libclang/LibClang.cpp
applying patch /nix/store/vr4wcxlhlf2mz6dwl1cbchab14x5d0iv-system-node.patch
patching file src/gwt/build.xml
configuring
Warning: unknown option '-d'
* checking for file 'rsconnect/DESCRIPTION' ... OK
* preparing 'rsconnect':
* checking DESCRIPTION meta-information ... OK
* excluding invalid files
Subdirectory 'R' contains invalid file names:
  '.editorconfig'
* checking for LF line-endings in source and make files and shell scripts
* checking for empty or unneeded directories
Removed empty directory 'rsconnect/examples'
Removed empty directory 'rsconnect/pkgdown'
* building 'rsconnect_0.8.25.tar.gz'

fixing cmake files...
cmake flags: -DCMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_SKIP_BUILD_RPATH=ON -DBUILD_TESTING=OFF -DCMAKE_INSTALL_LOCALEDIR=/nix/store/ig99wwkh7ka6msd7fdhyl67yx4lz5q1n-RStudio-1.4.1717/share/locale -DCMAKE_INSTALL_LIBEXECDIR=/nix/store/ig99wwkh7ka6msd7fdhyl67yx4lz5q1n-RStudio-1.4.1717/libexec -DCMAKE_INSTALL_LIBDIR=/nix/store/ig99wwkh7ka6msd7fdhyl67yx4lz5q1n-RStudio-1.4.1717/lib -DCMAKE_INSTALL_DOCDIR=/nix/store/ig99wwkh7ka6msd7fdhyl67yx4lz5q1n-RStudio-1.4.1717/share/doc/RStudio -DCMAKE_INSTALL_INFODIR=/nix/store/ig99wwkh7ka6msd7fdhyl67yx4lz5q1n-RStudio-1.4.1717/share/info -DCMAKE_INSTALL_MANDIR=/nix/store/ig99wwkh7ka6msd7fdhyl67yx4lz5q1n-RStudio-1.4.1717/share/man -DCMAKE_INSTALL_OLDINCLUDEDIR=/nix/store/ig99wwkh7ka6msd7fdhyl67yx4lz5q1n-RStudio-1.4.1717/include -DCMAKE_INSTALL_INCLUDEDIR=/nix/store/ig99wwkh7ka6msd7fdhyl67yx4lz5q1n-RStudio-1.4.1717/include -DCMAKE_INSTALL_SBINDIR=/nix/store/ig99wwkh7ka6msd7fdhyl67yx4lz5q1n-RStudio-1.4.1717/sbin -DCMAKE_INSTALL_BINDIR=/nix/store/ig99wwkh7ka6msd7fdhyl67yx4lz5q1n-RStudio-1.4.1717/bin -DCMAKE_INSTALL_NAME_DIR=/nix/store/ig99wwkh7ka6msd7fdhyl67yx4lz5q1n-RStudio-1.4.1717/lib -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_OSX_SYSROOT= -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_STRIP=/nix/store/bg35nfwn6zd616facdywiysgpprfvsji-gcc-wrapper-11.3.0/bin/strip -DCMAKE_RANLIB=/nix/store/rs684lgm8k7akkgbisb49z4vpxxc2zns-binutils-2.38/bin/ranlib -DCMAKE_AR=/nix/store/rs684lgm8k7akkgbisb49z4vpxxc2zns-binutils-2.38/bin/ar -DCMAKE_C_COMPILER=gcc -DCMAKE_CXX_COMPILER=g++ -DCMAKE_INSTALL_PREFIX=/nix/store/ig99wwkh7ka6msd7fdhyl67yx4lz5q1n-RStudio-1.4.1717 -DRSTUDIO_TARGET=Desktop -DCMAKE_BUILD_TYPE=Release -DRSTUDIO_USE_SYSTEM_SOCI=ON -DRSTUDIO_USE_SYSTEM_BOOST=ON -DRSTUDIO_USE_SYSTEM_YAML_CPP=ON -DPANDOC_VERSION=<IP_ADDRESS> -DCMAKE_INSTALL_PREFIX=/nix/store/ig99wwkh7ka6msd7fdhyl67yx4lz5q1n-RStudio-1.4.1717/lib/rstudio -DQT_QMAKE_EXECUTABLE=/nix/store/jvkkwa0sfyca1wpyvrgvpbsa34l0w60l-hook/bin/qmake
-- The C compiler identification is GNU 11.3.0
-- The CXX compiler identification is GNU 11.3.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /nix/store/bg35nfwn6zd616facdywiysgpprfvsji-gcc-wrapper-11.3.0/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /nix/store/bg35nfwn6zd616facdywiysgpprfvsji-gcc-wrapper-11.3.0/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Machine architecture: x86_64
-- CMake build type: Release
-- Using RStudio tools root: /opt/rstudio-tools/x86_64
-- Configured to build GWT
-- Using ant: /nix/store/yl24cdsfxxm72m689kc1vsshb48lgc9z-ant-1.10.11/bin/ant
-- Configured to install GWT
-- Performing Test COMPILER_SUPPORTS_CXX11
-- Performing Test COMPILER_SUPPORTS_CXX11 - Success
-- Found Boost: /nix/store/1w5fsr9m28585fsbbppc8cc69x8cpi4v-boost-1.77.0-dev/lib/cmake/Boost-1.77.0/BoostConfig.cmake (found suitable version "1.77.0", minimum required is "1.69.0")
-- Found Boost: /nix/store/1w5fsr9m28585fsbbppc8cc69x8cpi4v-boost-1.77.0-dev/lib/cmake/Boost-1.77.0/BoostConfig.cmake (found suitable version "1.77.0", minimum required is "1.69.0") found components: atomic chrono date_time filesystem iostreams program_options random regex system thread
-- No Crashpad libraries found under /opt/rstudio-tools/x86_64/crashpad/crashpad/out/Default/obj. Crashpad integration disabled.
-- SOCI libraries found under /nix/store/287wpc41n1lxixfx8mrrfvq168qi58pq-soci-4.0.2/lib
-- Found OpenSSL: /nix/store/hkb5vrx22dbnpryalcl41240f83llvss-openssl-1.1.1o/lib/libcrypto.so (found version "1.1.1o")
-- Performing Test HAVE_SCANDIR_POSIX
-- Performing Test HAVE_SCANDIR_POSIX - Success
-- Looking for SA_NOCLDWAIT
-- Looking for SA_NOCLDWAIT - found
-- Looking for SO_PEERCRED
-- Looking for SO_PEERCRED - found
-- Looking for inotify_init1
-- Looking for inotify_init1 - found
-- Looking for getpeereid
-- Looking for getpeereid - not found
-- Looking for setresuid
-- Looking for setresuid - found
-- Configured to build DESKTOP
-- Found LibR: /nix/store/cs12xc2njghl2h3wnma9bmgv9pxpnqsa-R-4.1.3/lib/R
-- Found R: /nix/store/cs12xc2njghl2h3wnma9bmgv9pxpnqsa-R-4.1.3/lib/R
-- Found Qt: /nix/store/jvkkwa0sfyca1wpyvrgvpbsa34l0w60l-hook/bin/qmake
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

    BUILD_TESTING
    CMAKE_EXPORT_NO_PACKAGE_REGISTRY
    CMAKE_INSTALL_BINDIR
    CMAKE_INSTALL_DOCDIR
    CMAKE_INSTALL_INCLUDEDIR
    CMAKE_INSTALL_INFODIR
    CMAKE_INSTALL_LIBDIR
    CMAKE_INSTALL_LIBEXECDIR
    CMAKE_INSTALL_LOCALEDIR
    CMAKE_INSTALL_MANDIR
    CMAKE_INSTALL_OLDINCLUDEDIR
    CMAKE_INSTALL_SBINDIR
    CMAKE_POLICY_DEFAULT_CMP0025

-- Build files have been written to: /build/source/build
cmake: enabled parallel building
building
build flags: -j2 -l2 SHELL=/nix/store/07ln9bxp9k8nds669r24fsywf4d1jlly-bash-5.1-p16/bin/bash
Buildfile: /build/source/src/gwt/build.xml

ext:
   [jscomp] Compiling 62 file(s) with 93 extern(s)
   [jscomp] 0 error(s), 0 warning(s)

javac:
    [mkdir] Created dir: /build/source/src/gwt/bin
    [javac] Compiling 3 source files to /build/source/src/gwt/bin
    [javac] Note: Some input files use or override a deprecated API.
    [javac] Note: Recompile with -Xlint:deprecation for details.
    [javac] Compiling 2446 source files to /build/source/src/gwt/bin
     [copy] Copying 1594 files to /build/source/src/gwt/bin

gwtc:

panmirror:
    [mkdir] Created dir: /build/source/src/gwt/www/js/panmirror
     [exec] node:internal/modules/cjs/loader:936
     [exec]   throw err;
     [exec]   ^
     [exec]
     [exec] Error: Cannot find module 'fuse-box/sparky'
     [exec] Require stack:
     [exec] - /build/source/src/gwt/panmirror/src/editor/fuse.js
     [exec]     at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
     [exec]     at Function.Module._load (node:internal/modules/cjs/loader:778:27)
     [exec]     at Module.require (node:internal/modules/cjs/loader:1005:19)
     [exec]     at require (node:internal/modules/cjs/helpers:102:18)
     [exec]     at Object.<anonymous> (/build/source/src/gwt/panmirror/src/editor/fuse.js:16:27)
     [exec]     at Module._compile (node:internal/modules/cjs/loader:1105:14)
     [exec]     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
     [exec]     at Module.load (node:internal/modules/cjs/loader:981:32)
     [exec]     at Function.Module._load (node:internal/modules/cjs/loader:822:12)
     [exec]     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) {
     [exec]   code: 'MODULE_NOT_FOUND',
     [exec]   requireStack: [ '/build/source/src/gwt/panmirror/src/editor/fuse.js' ]
     [exec] }
     [exec] Result: 1
     [java] Compiling module org.rstudio.studio.RStudio

I'm currently bisecting on x86_64-linux.
Notify maintainers
@ciil @cfhammill

It seems mongodb has similar problem. https://github.com/NixOS/nixpkgs/issues/171928

I have investigated the same problem during the change the branch from 21.11 to 22.05.
I assume the error is related to the new compiler version (gcc 11 and later) will not compile the rstudio version. I've tried myself to fix this error, but the R version that is linked to rstudio is also too new, this will have some errors during changed headers of the new R version.
The only solution would be to raise to the current rstudio version. I have prepared the update here. But currently I am not able to start rstudio correctly:

TTY detected. Printing informational message about logging configuration. Logging configuration loaded from '/etc/xdg:/home/goetz/.nix-profile/etc/xdg:/etc/profiles/per-user/goetz/etc/xdg:/nix/var/nix/profiles/default/etc/xdg:/run/current-system/sw/etc/xdg:/nix/store/15fs19rshpzj57hw130n76w0fqhmxpsm-gnome-settings-daemon-42.2/etc/xdg/rstudio/logging.conf'. Logging to '/home/goetz/.local/share/rstudio/log/rdesktop.log'.
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
2022-06-08T12:12:40.894937Z [rdesktop] ERROR system error 2 (No such file or directory) [path: /nix/store/s1jjw29757y4ilsrkb0n1ylayfl9m52x-RStudio-2022.02.3+492/lib/rstudio/bin/resources/stylesheets/rstudio-gnome-light.qss]; OCCURRED AT rstudio::core::Error rstudio::core::FilePath::openForRead(std::shared_ptr<std::basic_istream >&) const src/cpp/shared_core/FilePath.cpp:1461; LOGGED FROM: void rstudio::desktop::applyDesktopTheme(QWidget*, bool) src/cpp/desktop/DesktopUtils.cpp:176
2022-06-08T12:12:41.358884Z [rdesktop] ERROR system error 2 (No such file or directory) [path: /nix/store/s1jjw29757y4ilsrkb0n1ylayfl9m52x-RStudio-2022.02.3+492/lib/rstudio/bin/resources/html/error.html]; OCCURRED AT rstudio::core::Error rstudio::core::FilePath::openForRead(std::shared_ptr<std::basic_istream >&) const src/cpp/shared_core/FilePath.cpp:1461; LOGGED FROM: void rstudio::desktop::SessionLauncher::showLaunchErrorPage() src/cpp/desktop/DesktopSessionLauncher.cpp:379
2022-06-08T12:12:41.359539Z [rdesktop] ERROR system error 2 (No such file or directory) [path: /nix/store/s1jjw29757y4ilsrkb0n1ylayfl9m52x-RStudio-2022.02.3+492/lib/rstudio/bin/resources/html/loading.html]; OCCURRED AT rstudio::core::Error rstudio::core::FilePath::openForRead(std::shared_ptr<std::basic_istream >&) const src/cpp/shared_core/FilePath.cpp:1461; LOGGED FROM: void rstudio::desktop::MainWindow::onLoadFinished(bool) src/cpp/desktop/DesktopMainWindow.cpp:714
"Uncaught TypeError: Cannot read property 'notifyRCrashed' of undefined"
2022-06-08T12:12:41.364791Z [rdesktop] ERROR system error 2 (No such file or directory) [path: /nix/store/s1jjw29757y4ilsrkb0n1ylayfl9m52x-RStudio-2022.02.3+492/lib/rstudio/bin/resources/html/loading.html]; OCCURRED AT rstudio::core::Error rstudio::core::FilePath::openForRead(std::shared_ptr<std::basic_istream >&) const src/cpp/shared_core/FilePath.cpp:1461; LOGGED FROM: void rstudio::desktop::MainWindow::onLoadFinished(bool) src/cpp/desktop/DesktopMainWindow.cpp:714
2022-06-08T12:12:41.574135Z [rdesktop] ERROR system error 2 (No such file or directory) [path: /nix/store/s1jjw29757y4ilsrkb0n1ylayfl9m52x-RStudio-2022.02.3+492/lib/rstudio/bin/resources/html/loading.html]; OCCURRED AT rstudio::core::Error rstudio::core::FilePath::openForRead(std::shared_ptr<std::basic_istream >&) const src/cpp/shared_core/FilePath.cpp:1461; LOGGED FROM: void rstudio::desktop::MainWindow::onLoadFinished(bool) src/cpp/desktop/DesktopMainWindow.cpp:714

Maybe the maintainer can help me?

Either way, feel free to open a pull request with your change, and we can discuss there.

Either way, feel free to open a pull request with your change, and we can discuss there.

I created already a pull request. But I'm not sure if I have understand the way of backporting the changes correctly. As I understand, it is mandatory to create a pull request for master and create another one for backporting the changes to the current release.

Ah, I think you mean this here: https://github.com/NixOS/nixpkgs/pull/177021 (Your link goes somewhere else) Great! Let's continue there.

This can be closed I think!


How to implement the Xtext-XMI cross reference for LSP based editor in Theia ?

Hi,
I am working on creating a LSP based editor in Theia for one of our DSL , from this DSL we need to cross reference model defined in separate XMI file on the basis of FullQualifiedName.
I am able to implement this for eclipse plugin but unable to implement it for theia based editor , kindly help. If there is any existing sample that is implementing this functionality in thiea then it would be great.

https://stackoverflow.com/questions/66968029/how-to-implement-the-xtext-xmi-cross-reference-for-lsp-based-editor-in-theia/66984117#66984117


flutter run:  I am facing issue to run the project. I have given log below .

exception
ProcessException: ProcessException: Process "E:\Kamlesh\flutter_project\first_flutter_app\android\gradlew.bat" exited abnormally:
Exception in thread "main" java.lang.NullPointerException
	at org.gradle.wrapper.BootstrapMainStarter.findLauncherJar(BootstrapMainStarter.java:34)
	at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:25)
	at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:129)
	at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
  Command: E:\Kamlesh\flutter_project\first_flutter_app\android\gradlew.bat -v

#0      runCheckedAsync (package:flutter_tools/src/base/process.dart:255:5)
<asynchronous suspension>
#1      _initializeGradle (package:flutter_tools/src/android/gradle.dart:225:9)
<asynchronous suspension>
#2      _ensureGradle (package:flutter_tools/src/android/gradle.dart:206:37)
<asynchronous suspension>
#3      _readGradleProject (package:flutter_tools/src/android/gradle.dart:134:31)
<asynchronous suspension>
#4      _gradleProject (package:flutter_tools/src/android/gradle.dart:111:34)
<asynchronous suspension>
#5      getGradleAppOut (package:flutter_tools/src/android/gradle.dart:105:29)
<asynchronous suspension>
#6      AndroidApk.fromAndroidProject (package:flutter_tools/src/application_package.dart:154:23)
<asynchronous suspension>
#7      ApplicationPackageFactory.getPackageForPlatform (package:flutter_tools/src/application_package.dart:46:32)
<asynchronous suspension>
#8      FlutterDevice.runHot (package:flutter_tools/src/resident_runner.dart:345:56)
<asynchronous suspension>
#9      HotRunner.run (package:flutter_tools/src/run_hot.dart:253:39)
<asynchronous suspension>
#10     RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:428:37)
<asynchronous suspension>
#11     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:559:18)
#12     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:77:64)
#13     _rootRunUnary (dart:async/zone.dart:1132:38)
#14     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#15     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#16     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#17     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#18     Future._complete (dart:async/future_impl.dart:473:7)
#19     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#20     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:28:18)
#21     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:294:13)
#22     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
#23     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:77:64)
#24     _rootRunUnary (dart:async/zone.dart:1132:38)
#25     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#26     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#27     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#28     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#29     Future._complete (dart:async/future_impl.dart:473:7)
#30     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#31     _AsyncAwaitCompleter.complete.<anonymous closure> (dart:async-patch/async_patch.dart:33:20)
#32     _rootRun (dart:async/zone.dart:1124:13)
#33     _CustomZone.run (dart:async/zone.dart:1021:19)
#34     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:947:23)
#35     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#36     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#37     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:115:13)
#38     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:5)

flutter doctor
[✓] Flutter (Channel stable, v1.5.4-hotfix.2, on Microsoft Windows [Version 6.3.9600], locale en-US)
    • Flutter version 1.5.4-hotfix.2 at E:\Kamlesh\flutter_project\flutter
    • Framework revision 7a4c33425d (10 weeks ago), 2019-04-29 11:05:24 -0700
    • Engine revision 52c7a1e849
    • Dart version 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\om\AppData\Local\Android\Sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = C:\Users\om\AppData\Local\Android\Sdk
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Android Studio (version 3.4)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 37.0.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] VS Code (version 1.36.0)
    • VS Code at C:\Users\om\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.2.0

[✓] Connected device (1 available)
    • Lenovo K8 Plus • HKE8323P • android-arm64 • Android 8.0.0 (API 26)

• No issues found!

I have the same problem

@kamleshgorasiya did you manage to solve it? Seems to be a duplicate of #34211. Please report if that will help.

Hello
It seems that it is compiled with some version of android and with not some
version of Android, It is not working with Android 2.1.
It shows OpenGL version issue,
Fluxstore code runs in my one device but not in another device. There are
also many lags, and App not responding issues. In-short it, not the code
that I can use for the production version.
It would good if you guys fix that error as soon as possible.
Thank you
Kamlesh
On Mon, Sep 30, 2019 at 9:36 PM Stanislav Bondarenko <
<EMAIL_ADDRESS>wrote:

@kamleshgorasiya https://github.com/kamleshgorasiya did you manage to
solve it? Seems to be a duplicate of #34211
https://github.com/flutter/flutter/issues/34211. Please report if that
will help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/35659?email_source=notifications&email_token=ABQ7FG72CW4TXRSJMYIQBRLQMIPXFA5CNFSM4H6SU3P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD76FSIY#issuecomment-536631587,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQ7FGYMTN2QSSQ7YE3T55LQMIPXFANCNFSM4H6SU3PQ
.

@kamleshgorasiya Can you provide your current flutter doctor -v output, and specify on which exactly device it doesn't work? Do you encounter it on any project or on the particular one?
What is the OpenGL version issue?
Please provide  a small self-contained app that demonstrates the problem. You can include small examples inline if they're enclosed by backticks, or just provide a public link to a github "gist" - https://gist.github.com/.

I am checking this on Nokia 2.1 having version Android P,
Any flutter project is not working on that device produce following error

@kamleshgorasiya Oh right, it's the #36130. Sorry to say, but so far I think using flutter master is the only solution:(


Feat/seven discard

Implements seven discard: throwing away a jack from the top of the deck when both cards are unplayable jacks
Issue number
Relevant issue number

Resolves #1112

Please check the following

[ ] Do the tests still pass? (see Run the Tests)
[ ] Is the code formatted properly? (see Linting (Formatting))
For New Features:

[ ] Have tests been added to cover any new features or fixes?
[ ] Has the documentation been updated accordingly?

Please describe additional details for testing this change

Nice, I think we need to update getLog as well since we added a movetype


Fix namespace in quick start page [doc]

Fix namespace in docs page docs/quick_start.md
In command created ns named test
kubectl create namespace test

But in apply command use ns test-clickhouse-operator
kubectl apply -n test-clickhouse-operator -f ...

Signed-off-by: orginux<EMAIL_ADDRESS>

Could you change target branch to 0.15.0, please. According to https://github.com/Altinity/clickhouse-operator/blob/master/CONTRIBUTING.md#how-to-make-pr

Looks like not all naming issues are fixed, it would be nice to update the doc to consistency

@sunsingerus you're right! In the next commit, I fixed namespace in all commands on the page.


How to define REALLOC in OPLIST?

How to define REALLOC in OPLIST?
There is error in following code:
static data_node * data_node_realloc(data_node * obj, size_t size);
ARRAY_DEF(/* the array prefix / array_data_node,
/ the object type / data_node,
/ the object oplist */ (INIT(API_2(data_node_init)),
SET(API_6(data_node_set)),	 REALLOC(API(data_node_realloc,ARGPTR1,ARGPTR2,ARG3)),
INIT_SET(API_6(data_node_init_set)),
CLEAR(API_2(data_node_clear))))

Hi,
You need to define it like this:
ARRAY_DEF(/* the array prefix */ array_data_node,
	  /* the object type */ data_node,
	  /* the object oplist */ (INIT(API_2(data_node_init)),
				   SET(API_6(data_node_set)),
				   REALLOC(API(data_node_realloc,NONE, ARG2, ARG3)),
				   INIT_SET(API_6(data_node_init_set)),
				   CLEAR(API_2(data_node_clear))))

More information:

ARG1 is the type itself, which is useless for your already strongly type function.
It already expects the argument to be pointer to object, so no need to add an additional pointer.
Since the prototype of the operator expects a pointer as return value, there is no transformation to perform to match your prototype.

Additional notes on this code which may be bugs:

there is no INIT_SET operator (copy constructor), which is likely to be problematic for your object
you over-define the REALLOC operator but not the FREE operator, which means standard C "free" function will be used. I am not sure it is want you want.


This test does too many things.

In an attempt to reduce duplication, this one test checks that:

A decoded packfile can be encoded to be equal to the input.
A decoded re-encoded packfile is equal to a decoded packfile.
The CRCs of an encoded packfile match the CRCs provided in the pack index.
A list of objects resolved with reference to the index matches the list of objects resolved without reference to the index.
The hashes of the resolved objects match the ones found in the pack index.
The resolved objects can be written to disk (writeObject works correctly).
We can generate a list of pack index entries that matches our input.

This is absurd. It would be better to split this test into many smaller tests and test writeObject separately so that it is explicit that the rest of the tests depend on the presence of the correct loose objects.

The test has been split into smaller tests.


Don't decrypt the deployment key where we don't need it

Without this, PRs are hanging looking for a passphrase.  We should only try to get the deploy key where we intend to deploy.

@rossabaker This should probably be cherry-picked into release-0.15.x and we'll want to merge into cats soonish too.  Bit me on the #984 PR against release-0.15.x.  Oh the fun of long-lived branches.


nixos/mautrix-whatsapp: various fixes

Description of changes
Some fixes and improvements to the NixOS module, see the commit messages for the details.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested on my homeserver by backporting to NixOS 23.05.
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/setting-up-the-as-token-for-mautrix-telegram-matrix-bridge/34025/3


Add analysis notebooks

Collect analysis notebooks in separate branch
Use sun as common data storage

Added branch analyses

We ended up using validation, and the relevant notebooks made it to main.


ENH: update package version

Hi! This is the friendly automated conda-forge-webservice.
I've started a version update as instructed in #16.
I'm currently searching for new versions and will update this PR shortly if I find one! Thank you for waiting!
Fixes #16

@jorisvandenbossche it seems that we now have hard dependency on dask-expr which does not come with dask? I am not entirely familiar with the structure of dask and its dependencies so I'm slightly confused here. We certainly don't mention dask-expr in pyproject.toml.

We don't have a hard dependency on dask-expr because this is only a depedency for more recent dask (and I don't think we can make a dependency dependent on the version of dask ..). And it also does not come directly with dask, because it is only a dependency of dask.dataframe (and we depend on dask-core).
It's a bit annoying for the tests, but I assume we can add an additional test dependency in the recipe?

Although looking at the warning message 'Dask dataframe query planning is disabled because dask-expr is not installed", it's actually still possible to run recent dask without dask-expr as well. And that is maybe something we don't allow anymore (and we could).

It's a bit annoying for the tests, but I assume we can add an additional test dependency in the recipe?

I don't think it is a question of tests as it fails on import.
I think that we either need to add dask-expr as a dependency here on top of dask-core + probably to pyproject.toml or ensure that we can import and use dask-geopandas without it.

It's still a question of the tests (although the same issue annoyingly applies to all users), because we cannot express "dask-expr is needed if dask >= 2024.3" in the dependencies section of the recipe or of pyproject.toml AFAIK.
This is quite annoying, but not sure how to deal with that ..

If we add a dependency here on dask-expr, that means you cannot longer install dask-geopandas with an older version of dask because dask-expr pins to a recent version of dask (https://github.com/conda-forge/dask-expr-feedstock/blob/main/recipe/meta.yaml)
In theory we could depend on dask here for conda-forge instead of dask-core, which will ensure to include dask-expr (https://github.com/conda-forge/dask-feedstock/blob/main/recipe/meta.yaml), but then you also get bokeh/pyarrow/distributed, and then there is no way to install a minimal dask-geopandas (unless we would also add a dask-geopandas-base ..)

For pip / pyproject.toml, we can probably depend on dask[dataframe] instead of dask, as dask[dataframe] only additionally depends on pandas and dask-expr (and pandas we already have as a dependency anyway)

So updated this to directly package 0.4.1. For the pip side we will now include dask-expr through dask[dataframe], but for the conda-forge side here I am still not sure how to best deal with this (it is somewhat annoying to have users ensure this themselves, although if they rely additionally on the dask conda-forge package themselves as well, they will also get dask-expr, which is probably good enough?)


make global jest object compatible with vi/vitest

https://jestjs.io/docs/27.2/jest-object#jestisolatemodulesfn

Closing, since it is compatible as it can get for now. New features should be discussed in new issues.


document.getWordRangeAtPosition(position) not working properly in XML files.

Example:
<content>
    <function>PostChangeLog</function>
    <Value3>1644336660000</Value3>
    <DeviceID>FA954A84D674FAE</DeviceID>
    <EntryGUID>793FCA-50B-76D-FDB-3BC93E512</EntryGUID>
</content>

Some particular observations:

When putting the position of any character of the word PostChangeLog in the function I get the Word Range of the word PostChangeLog which is correct.
But when putting the position of any character of the word<PHONE_NUMBER>000 in the function I get the Word Range of the whole document. (This is the issue that I am concerned with).
Furthermore, I tried some more combinations, so that I can get why is it happening:
-- Any character of the word FA954A84D674FAE; Result - Word Range of the word FA954A84D674FAE
-- Any character of the word 793FCA-50B-76D-FDB-3BC93E512; Result - Word Range of the word 793FCA-50B-76D-FDB-3BC93E512

I think this might be a problem with the XML word pattern, which came in via https://github.com/microsoft/vscode/pull/127334


Add support for multiple schemas

Fixes #1766

We also need a test for schemas and patterns together.

To me this looks good.

I tried this change in a project that I'm working on and the maven configuration got smaller :) Does this takes into account the typeMapping in case of having different tables with the same name across schemas?

@natros Could you provide a configuration example?

It seems there is a schema inheritance, RFID has a parent schema GAL.
Once you tell it to export just RFID, a foreign key can't be generated it seems.

When using  <schemaToPackage>true</schemaToPackage> the beans are correctly generated. Only one User classe instead of two.
https://github.com/natros/querydsl-test/tree/schema-to-package


Add a replace section so the original xmlseclibs will never installed

Q
A

Bug fix?
yes

New feature?
no

BC breaks?
no

Deprecations?
no

Fixed tickets
partially #81

Related issues/PRs
robrichards/xmlseclibs#104

License
MIT

What's in this PR?
This adds a replace section to the composer.json which says this library replaces the xmlseclibs. Thus the the xmlseclibs will no longer get installed via composer as you need your modified ones.
After xmlseclibs finally has a release (note robrichards/xmlseclibs#104) this must be reverted. Maybe this will be only a shortly living bugfix release, but we would happy if we can get a release of php-saml after merging this :grinning:
Why?
This gets finally rid of the ambigious class resolution warnings:
Generating autoload files
Warning: Ambiguous class resolution, "XMLSecEnc" was found in both "/vagrant/vendor/onelogin/php-saml/extlib/xmlseclibs/xmlseclibs.php" and "/vagrant/vendor/rob
richards/xmlseclibs/src/XMLSecEnc.php", the first will be used.
Warning: Ambiguous class resolution, "XMLSecurityDSig" was found in both "/vagrant/vendor/onelogin/php-saml/extlib/xmlseclibs/xmlseclibs.php" and "/vagrant/vend
or/robrichards/xmlseclibs/src/XMLSecurityDSig.php", the first will be used.
Warning: Ambiguous class resolution, "XMLSecurityKey" was found in both "/vagrant/vendor/onelogin/php-saml/extlib/xmlseclibs/xmlseclibs.php" and "/vagrant/vendo
r/robrichards/xmlseclibs/src/XMLSecurityKey.php", the first will be used.

Having this in mind, it is rather coincidence that your supplied and modified version of xmlseclib gets chosen first and not the ones installed via composer. If it would be otherwise, php-saml would crash, as said in #81 you've backported stuff from master of xmlseclibs

robrichards said that a release is planed for next week, so let's wait.

No short living release then? :grin:

xmlseclibs has a 2.* release https://github.com/robrichards/xmlseclibs/issues/104#issuecomment-245638629

Yes I saw, but need to commit first some improvements.


Other alternatives to Pololu 38 kHz IR Proximity Sensor

Are there any other alternatives to the Pololu 38 kHz IR Proximity Sensor?
The sensor is hard to get and very expensive to sende to Europe.

https://www.ebay.com/itm/KY-032-4pin-IR-Infrared-Obstacle-Avoidance-Sensor-Module-/383563635806


Add support for relay subscriptions

As a developer, I want to be able to specify my applications subscription requirements through relay subscription model.
From #27

You already can specify your subscriptions through the graphql api (see here) and there's already graphene support. I have some thoughts on ways to tie the requested subscription to amqp routes, which lets us "whitelist" backend events and pass them onto the subscriptions that need them. If we do things correctly (ie, conforming to the "relay way"), this should give us realtime for free in react clients. Extending this to a general socket.io connection should be really easy - and probably the job for a standalone service, not the api gateway.

I will provide a more detailed description of the whitelist when I have some time to collect my thoughts

Closing this since it will probably come with updates to the apollostack


AR Mode - No Camera Feed

Description
Trying to view a 3d model in augmented reality using model viewer
I am able to see the model but the camera feed doenst open it stays black
Live Demo
http://testzone.pt/
Browser Affected

[X] Chrome
[ ] Edge
[x] Firefox
[ ] Helios
[ ] IE
[ ] Safari

OS

[X] Android
[ ] iOS
[ ] Linux
[ ] MacOS
[ ] Windows

Versions

model-viewer: latest version using cdn
three.js: rXX

@cdata any tip about what can be causing this ?
I am using a Samsung S8 with Android 9

@ghus86 sorry for the delayed response; I'm happy to help if I can.
Can you confirm if you are using WebXR for AR, or Scene Viewer? Scene Viewer is a native app, so you will see a different panel in your task switcher when it launches.

@cdata no problem about delay
I am just using the tag model viewer and adding this
<script type="module"<EMAIL_ADDRESS><script nomodule<EMAIL_ADDRESS>

@ghus86 there may be other problems, but the first one I noticed is that your site is not being served over SSL, and going to the https:// version results in an error suggesting that you do not have a valid certificate. In order for Scene Viewer to work, you need to serve your content over SSL (https:// with a valid certificate).

@cdata ok thanks
didnt know that was required

After syncing up with the Scene Viewer team, I'm told that the https:// requirement will go away when we fix #1097

@cdata Thanks for your time
configuring the ssl fixed my problem.


feat(workflows): npm vesrion and test workflows added

Hello there,
enjoy!
add you email in the npm-version workflow and add NPM_TOKEN to the repo secrets and consider using Conventional Commits from now on and the workflow will version your package automatically

wow, thanks! This is some very useful PR :)


Add IsFinite to C# Variants

Follow up to https://github.com/godotengine/godot/pull/64268

Thanks!


drop-down menu for API and HELP is broken

Version - master
Steps to Reproduce:

Move mouse over API or Help menu

Results: Showing APPLICATIONS submenu
Expected: Since there are no submenus for this and if I click on them, the submenu bar is empty, I say it should be blank.

Version - master 3/4
Verified fixed


Preliminary Prototype

Not even really a prototype as there are some fundamental missing features (see the many TODO's), but hopefully something to work off.  In particular it doesn't explode on drugs/genes/phenotypes, and does not do any mapping to EFO/CHEBI identifiers or functional consequence prediction.
However it does provide a reproducible way to generate pseudo-evidence strings, which we can use to continue to develop the schema and requirements with Open Targets.
Test run here.

@M-casado Regarding the separate repo, I was thinking that it was providing an entirely different datasource to OT so would be more organised to separate it, especially given we're preparing to publish the ClinVar stuff.  There will be some code reuse via libraries and executables but I think it's manageable, though it's a bit hard to predict as we haven't fully fleshed out the PGKB processing.
We can always move the code back to the eva-opentargets repo at a later date if that makes more sense.


OAuth2AuthorizationCodeBearer: use id_token instead access_token

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
app: FastAPI = FastAPI(title="pyauth", debug=True,
                       swagger_ui_init_oauth={"clientId": "eN2PZiKgIwt3UZEDHtttivsUJdNV6W8y",
                                              "clientSecret": "hvo_secret_5OYAbYzfYi9Oh9dKvPqiBjwI4jT5lT4AhZwezm0Gi7HFYCMPpqoladkAWRcDG2Ci",
                                              "appName": "pyauth",
                                              "scopes": "openid",
                                              "useBasicAuthenticationWithAccessCodeGrant": True,
                                              },
                       )

oauth = OAuth2AuthorizationCodeBearer("http://<IP_ADDRESS>:8200/ui/vault/identity/oidc/provider/test/authorize",
                                      "http://<IP_ADDRESS>:8200/v1/identity/oidc/provider/test/token",
                                      scopes={"admins": "asda", "user": "users"},
                                      scheme_name="Vault"
                                      )

Description
I use OAuth2AuthorizationCodeBearer with external Oidc provider (Vault OIDC Provider).  Identity server receive acess_token and id_token. When calling my api it send access_token, but I need id_token. is it possible to send id_token instead?
In swagger issue I found info about x-tokenName, but I can't understand how I can use it in FastApi.
Operating System
macOS
Operating System Details
No response
FastAPI Version
0.71
Python Version
3.9
Additional Context
No response

What the API returns is not defined by the OAuth2AuthorizationCodeBearer, but by the endpoint. Check line 38: https://github.com/tiangolo/full-stack-fastapi-postgresql/blob/master/{{cookiecutter.project_slug}}/backend/app/app/api/api_v1/endpoints/login.py

You can extend the OpenAPI schema in FastAPI to specify x-tokenName and set it as id_token.
from fastapi import FastAPI
from fastapi.openapi.utils import get_openapi

app = FastAPI()

def custom_openapi():
    if app.openapi_schema:
        return app.openapi_schema
    openapi_schema = get_openapi(
        title="OIDC Authenticated API",
        version="1.0.0",
        description="An API that uses OIDC id_token to authenticate",
        routes=app.routes,
    )
    openapi_schema["components"]["securitySchemes"][f'{SCHEMA_NAME}']["x-tokenName"] = "id_token"
    app.openapi_schema = openapi_schema
    return app.openapi_schema

app.openapi = custom_openapi

It would be great if this was supported through the OAuth2 modules thoughs.


Doc generation CleanUp

[x] Clean up eng\pipelines\templates\steps\archetype-sdk-docs.yml to get all the steps into single powershell script so to can easily be reproduced locally.
[x] Track exit codes to ensure runs are correct.
[ ] Convert management and client steps into a single step
[x] Map service names to a friendly name on doc index
[ ] Figure our how to build doc index without losing docs for renamed packages
[x] I also like the doc generation stuff under the doc\ root folder similar to python.

The renamed package item was tracked by a different issue (https://github.com/azure/azure-sdk/issues/761) and is cut.


add border by default for code editors

requested by the UX team

Codecov Report

Merging #701 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #701      +/-   ##
==========================================
+ Coverage   99.72%   99.72%   +<.01%
==========================================
  Files         264      264
  Lines        6801     6802       +1
  Branches     1588     1588
==========================================
+ Hits         6782     6783       +1
  Misses         19       19

Impacted Files
Coverage Δ

src/components/editor/CodeEditor.tsx
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


CLI to get vm IP

like what docker-machine ip <machine> does

dscacheutil -q host -a name local.docker

@arnested Or grep local.docker /etc/hosts but both are only convenient until the hostname will change as a newly introduced parameter to dlite install --hostname X. Then the daemon basically knows the IP and a simple dlite ip is again convenient.

Yes, your are probably right.

i can add a command for this


Add and use utility for generating 'empty' narrative text for resources

Is your feature request related to a problem? Please describe.
We get a lot of validation warnings due to our examples not having narrative text.
Describe the solution you'd like
Ideally we could generate narrative text from the structured data (#645), but until we get to that I think we could just add empty narrative like this:
  "text" : {
    "status": "empty",
    "div": "
Narrative text intensionally left empty
"
  },

Some alternate placeholder text I considered was "This resource contains only structured data, no narrative text".  We could make it shorter, but I wanted to make it clear the text was empty and not necessarilly the resource.

team decision:  introduce a constant Narrative.EMPTY with the follow content:
  "text" : {
    "status": "empty",
    "div": "
Narrative text intensionally left empty
"
  },


CX-16047 Create reusable components for AI Assistant in Momentum UI l…

…ibrary
Description
Created various UI components for all possible AI Assistant delegates.
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots:

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Could you add a CardAi storybook file

Could you add a CardAi storybook file

So I wasn't sure whether these were still things which worked because when I tried to preview these in the browser I couldn't get anything to render out of the box (for any component!).

You should update the package.json minor version number


Go parallel getImage handler, better errors, and fix DB

To match what Rust did in #258 (making save-image parallel) do something similar for Go. Also, insert a transaction such that the DB will never be updated unless the S3 upload succeeds by having a DB transaction wrap the whole process.
Fixed up error code with a helper to clean-up some returns, as well as standardize wrapping errors.
Finally, fix a bug that broke the DB submit code in PR #256 when it used the wrong quoting style for postgres databases. Although I am having trouble configuring Minio properly to do a full test, I was able to see this failure and test that my change worked (when S3 errors were ignored).

@cookieo9 you can use docker compose to run it locally, postgres and monio
---
services:
  minio:
    image: minio/minio:RELEASE.2024-09-13T20-26-02Z
    command: server /data --console-address ":9001"
    ports:
      - 9000:9000
      - 9001:9001
    networks:
      - private
    volumes:
      - minio-data:/data

  postgres:
    image: postgres:16.4
    ports:
      - 5432:5432
    environment:
      POSTGRES_USER: myuser
      POSTGRES_PASSWORD: devops123
      POSTGRES_DB: mydb
    volumes:
      - postgres-data:/var/lib/postgresql/data
    networks:
      - private

volumes:
  minio-data:
  postgres-data:

networks:
  private:


Updated the support matrix to show the minor versions of TensorFlow. …

…(#191)

LGTM, to match the Install TensorFlow page. Compatibility Matrix needs to be updated too.

Opened a separate issue for that.


Upgrade ring to 0.3.0

ring has been upgraded to 0.3.0 and has yanked all previous versions, causing jsonwebtoken to fail to resolve dependencies:
> cargo build
    Updating registry `https://github.com/rust-lang/crates.io-index`
error: no matching package named `ring` found (required by `jsonwebtoken`)
location searched: registry https://github.com/rust-lang/crates.io-index
version required: ^0.2
versions found: 0.3.0

I can create a PR for this shortly.

It's ok, i'm pushing a new version as we speak :)

Pushed as 1.1.5, thanks for the report!


Add conversion table to guide

Closes #374
Tried to keep it clear and short, but cover all relevant detail. Happy to edit any terms, wording or other suggestions you have.

Thank you!
Generally, I think we should note both class name and mypy type.
E.g., object and Any, dict and Dict[K, V], ...
In addition, it would be great if we have a review from someone with expertise in Python(e.g., @birkenfeld).

Thank you!
Generally, I think we should note both class name and mypy type.
E.g., object and Any, dict and Dict[K, V], ...

In the interest of not duplicating things I'm going to switch to use object, dict[K, V] etc. as that's the syntax that will be official from Python 3.9 (as per PEP 585)
Thanks for the review @birkenfeld - I've pushed some changes based on your feedback 👍

@birkenfeld Thank you for your review :slightly_smiling_face:

Thanks, have addressed the final points of feedback.


Yjs simple provider

Adds a yjs provider that persists to crsqlite and syncs through crsqlite.

can't merge this yet -- it changes the rx interface which breaks other example apps.

going to shelve this for now.
crsqlite shouldn't concern itself with application layer integrations at this point in time.