项目构建失败

已开始打包
autopacking.sh: line 166: 104: command not found
Print: Entry, "CFBundleVersion", Does Not Exist
autopacking.sh: line 168: 1.4#File: command not found
2019-05-17 13:35:22.053 xcodebuild[60630:936461] [MT] PluginLoading: Required plug-in compatibility UUID 72F7D751-F810-43B8-A53F-1F1DFD74FC54 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/xTransCodelation.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2019-05-17 13:35:22.053 xcodebuild[60630:936461] [MT] PluginLoading: Required plug-in compatibility UUID 72F7D751-F810-43B8-A53F-1F1DFD74FC54 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/ESTranslate.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2019-05-17 13:35:22.054 xcodebuild[60630:936461] [MT] PluginLoading: Required plug-in compatibility UUID 72F7D751-F810-43B8-A53F-1F1DFD74FC54 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Alcatraz.xcplugin' not present in DVTPlugInCompatibilityUUIDs
xcodebuild: error: Unknown build action 'Release'.
2019-05-17 13:35:22.882 xcodebuild[60631:936505] [MT] PluginLoading: Required plug-in compatibility UUID 72F7D751-F810-43B8-A53F-1F1DFD74FC54 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/xTransCodelation.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2019-05-17 13:35:22.882 xcodebuild[60631:936505] [MT] PluginLoading: Required plug-in compatibility UUID 72F7D751-F810-43B8-A53F-1F1DFD74FC54 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/ESTranslate.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2019-05-17 13:35:22.883 xcodebuild[60631:936505] [MT] PluginLoading: Required plug-in compatibility UUID 72F7D751-F810-43B8-A53F-1F1DFD74FC54 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Alcatraz.xcplugin' not present in DVTPlugInCompatibilityUUIDs
User defaults from command line:
    IDEArchivePathOverride = /Users/nathan/Documents/workspace/YY/LuckyBet/build/.xcarchive

Build settings from command line:
    CFBundleVersion =

xcodebuild: error: Unknown build action 'Release'.
项目构建失败 😢 😢 😢

我直接指定版本号貌似也不行，求解。

没有找到你的Info.plist, 说明Info.plist的路径不对，检查一下吧


documentation: fix build warning

Summary
Use correct highlight setting for block of assembly in nxflat.rst, which generated a warning.
Impact
Documentation
Testing
Builds with no warning

@v01d do you want me to merge this in now, or should we do it on top of my change?

We can wait. I'll rebase once the other PR finishes CI and I can merge it.

I just rebased and warning no longer appears.

@v01d I noticed another issue in the rendered docs
.. code-block:: asm

          ldr     r1, .L0         /* Fetch the offset to 'x' */
          ldr     r0, [r10, r1]   /* Load the value of 'x' with PIC offset */
          /* ... */
  .L0:    .word   x               /* Offset to 'x' */

this does not work correctly because the .L0 is on a different level than the start of the code block.  The rest of the page then is not quite rendered correctly.  I see in my text editor everything becomes italicised indicating a special mode.  You see this in the rendered docs as the second code block is not highlighted.
This renders correctly.
.. code-block:: asm

  .FOO
          ldr     r1, .L0         /* Fetch the offset to 'x' */
          ldr     r0, [r10, r1]   /* Load the value of 'x' with PIC offset */
          /* ... */
  .L0:    .word   x               /* Offset to 'x' */

I'm not sure what rendered docs you are referring to. I can see it correctly here: https://nuttx.apache.org/docs/latest/components/nxflat.html#appendix-a-no-got-operation
It also look OK locally.

The only strange thing I can see is that .word has a different color, but I'm not sure if that is OK or not. Also, #0 is indeed italicized but my guess is it does not like the #

I'm not sure what rendered docs you are referring to. I can see it correctly here: https://nuttx.apache.org/docs/latest/components/nxflat.html#appendix-a-no-got-operation
It also look OK locally.

Notice how the L1 in the next section is not highlighted.
And in my editor:

L1 appears highlighted:

BTW, shouldn't it be "L1:" (colon missing?)

The issue is the the code block is delimited by the indentation, if we add two empty spaces on the first line it is fine,  Perhaps a comment so editors do not strip it?

L1 appears highlighted:
Not in the rendered output.  Notice how the comments are also not highlighted.

BTW, shouldn't it be "L1:" (colon missing?)
Yes

This seems to be more about the editor correctly parsing RST or not. If I add the extra line, vim does not color correctly the block, it only works if it starts indented as you suggest. Starting with a label should take care of it. Do you want to make a PR?

Ahh. I take it back, I was seeing a cached version.  I do think my local editor is confused by the lack of proper indent on the start, but that is my editor not sphinx....

L1 appears highlighted:

Not in the rendered output. Notice how the comments are also not highlighted.

BTW, shouldn't it be "L1:" (colon missing?)

Yes

Where is that from? What is "rendered output" for you? I took a screenshot of documentation on the nuttx website.

@v01d the poor rendering of #0 bothered me so I opened a PR to fix it in pygments so hopefully the next release will fix this.  https://github.com/pygments/pygments/pull/1530
Sorry for all the noise on the other issue.  I thought I had forced my browser to clear its cache.


Remove hard failure for not getting global STS endpoint

Issue #, if available:
N/A
Description of changes:
We don't use global STS endpoint so in case global endpoint is not found, ignore and move ahead with regional STS provider
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

We don't use global STS endpoint so in case global endpoint is not found, ignore and move ahead with regional STS provider

This needs to be tested for other regions.
I think, we rely on global endpoint if the regional endpoint is not available. But post merge is fine.


Marking nscd mount as read only

For some volume mounts like nscd, it needs to be marked as read only for security reason. If it doesn't need to be kept read only then that can be set from property as well
azkaban.kubernetes.pod.nscd.mount.read.only=false

Pull Request Test Coverage Report for Build 6204

2 of 2 (100.0%)  changed or added relevant lines in 2 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 44.818%

Files with Coverage Reduction
New Missed Lines
%

azkaban-common/src/main/java/azkaban/jobExecutor/AbstractJob.java
2
37.93%

azkaban-common/src/main/java/azkaban/jobExecutor/AbstractProcessJob.java
3
52.58%

Totals

Change from base Build 6203:
-0.01%

Covered Lines:
17290

Relevant Lines:
38578

💛  - Coveralls


[WFLY-14049] Consolidate testsuite/integration/microprofile-tck confi…

…g boilerplate
https://issues.redhat.com/browse/WFLY-14049
Remove over 1500 net lines of pom xml by putting most of the mp tck config in the parent and using properties set by the children to set the per-TCK values.

@yersan We are using wildfly-preview-feature-pack for the other modules. Those ultimately use ${testsuite.ee.galleon.pack.artifactId} as the artifactId and in the ts.ee9 profile that is set to wildfly-preview-feature-pack. FT, JWT and OpenAPI do not use ${testsuite.ee.galleon.pack.artifactId} so they have to have the value explicitly set.
When we move all the MP specs out of wildfly-ee this will get reworked as none of them will use ${testsuite.ee.galleon.pack.artifactId} any more. That's part of the work to move them.

Thanks for the review, @yersan


feat: add oxc sourcemap crate

The sourcemap implement port from rust-sourcemap, but has some different with it.

Encode sourcemap at parallel, including quote sourceContent and encode token to vlq mappings.
Avoid Sourcemap some methods overhead, like SourceMap::tokens() caused extra overhead at common cases. Here using SourceViewToken to instead of it.

This is really hard to review, can you comment in the places where we should take a look?

Yeah. The code is larger to review, because the most code is port from rust-sourcemap. I only add some optimize to it. Maybe you can review ConcatSourcemapBuilder.rs or encode.rs at now, the changes of rust-sourcemap other files are small.


Standardise table.sql file

Description and Use case
The new datacheck for validating a db schema uses the table.sql file.
This is mostly consistent already, both within the file and between instances of the files in different repositories. But there are a few simple changes to terminology and formatting that would further standardise the files. These sorts of things can be handled in the datacheck code, but having fewer, and less complicated, exceptions makes the code more robust and easier to understand.
Benefits
Datacheck is simpler. Standardisation and consistency are generally good things to aim for.
Possible Drawbacks
None I can think of.
Testing
Unit tests not relevant.
I created databases before and after the changes, and the results were identical.

Coverage remained the same at 81.127% when pulling ce7ab63d197a3b95f998cab92bce7946fd5302c6 on james-monkeyshines:master into fdab1f12d8979de6596f806f8b82189d6e4ea9b1 on Ensembl:master.

I don't think I could write a patch file for these changes; ignoring the whitespace ones, they amount to replacing MySQL synonyms with the 'canonical' keywords. But when you load a database, that replacement happens automatically; so there is nothing to change in an existing database.

How do we update all the table.sql files living in modules/t/test-genome-DBs then? For example
https://github.com/Ensembl/ensembl/blob/release/94/modules/t/test-genome-DBs/homo_sapiens/core/table.sql

There's no need to update those files; they've already been through MySQL and out the other side, so the synonym mapping has already happened there. E.g. in the example you give, there are no BOOLEANs, just TINYINT(1)s. So those files are already consistent with my proposal.

Fair enough

I'm not making changes for the sake of brevity, but to use the standard terms rather than synonyms. I guess it's a matter of preference, but I do not like using BOOLEAN in MySQL; because that's not what it is, it's an integer in the range [-128, 127].
The "BOOLEAN" is lost as soon as you create a database, i.e. doing a 'show create table' or mysqldump will return "TINYINT(1)". So it would only be visible for people seeking to understand the schema by reading this file (or anything derived from this file), and the column names in these cases make the nature of the data clear, I think.
Note also that this is not just about standardising within this file; I've also been looking at funcgen, variation and production table.sql files, and they already all use TINYINT(1) in preference to BOOLEAN.

indeed mysql does not have a true boolean type and uses TINYINT(1) to hold that type of data, and defines the alias to use it. the alias exists only to make people's life easier, of course the engine does not care and uses the internal real data type.
But tables.sql is written by people, and I believe less people will know instantly what a TINYINT(1) means is than a BOOLEAN.
But I agree is just a matter of preference and not really important.


Object equivalency fails for Anonymous object Vs Private objects

type Employee object {
    int age;
};

public function main() {
    // semantic error
    object { int age; } p = new Employee();
}

Give the following semantic error:
incompatible types: expected '$anonType$0', found 'Employee'

Related issue: #14906

The above was fixed with PR #15180. Hence closing this.


[ISSUE #6236]Optimize ThreadLocalIndex replace Integer with AtomicInteger

Make sure set the target branch to develop
What is the purpose of the change

fix #6236
Brief changelog

Optimize ThreadLocalIndex replace Integer with AtomicInteger

Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

public class ThreadLocalIndexOptimize {
    private final ThreadLocal<AtomicInteger> threadLocalIndex = new ThreadLocal<>();
    private final Random random = new Random();
    private final static int POSITIVE_MASK = 0x7FFFFFFF;

    public int incrementAndGet() {
        AtomicInteger index = this.threadLocalIndex.get();
        if (null == index) {
            index = new AtomicInteger(random.nextInt());
            threadLocalIndex.set(index);
        }
        return Math.abs(index.incrementAndGet() & POSITIVE_MASK);
    }

    @Override
    public String toString() {
        return "ThreadLocalIndex{" +
            "threadLocalIndex=" + threadLocalIndex.get() +
            '}';
    }
}

benchmark
@BenchmarkMode(Mode.Throughput)
@Warmup(iterations = 3, time = 1)
@Measurement(iterations = 5, time = 5)
@Fork(1)
@State(value = Scope.Benchmark)
@OutputTimeUnit(TimeUnit.SECONDS)
public class ThreadLocalIndexBenchmark {

    private ThreadLocalIndex index = new ThreadLocalIndex();

    private ThreadLocalIndexOptimize optimize = new ThreadLocalIndexOptimize();

    @Benchmark
    @Threads(1)
    public void threadLocalIndex_1() {
        index.incrementAndGet();
    }

    @Benchmark
    @Threads(1)
    public void threadLocalIndexOptimize_1() {
        optimize.incrementAndGet();
    }

    @Benchmark
    @Threads(8)
    public void threadLocalIndex_8() {
        index.incrementAndGet();
    }

    @Benchmark
    @Threads(8)
    public void threadLocalIndexOptimize_8() {
        optimize.incrementAndGet();
    }

    public static void main(String[] args) throws RunnerException {
        Options opt = new OptionsBuilder()
            .include(ThreadLocalIndexBenchmark.class.getSimpleName())
            .result("result.json")
            .resultFormat(ResultFormatType.JSON).build();
        new Runner(opt).run();
    }
}

result:
REMEMBER: The numbers below are just data. To gain reusable insights, you need to follow up on
why the numbers are the way they are. Use profilers (see -prof, -lprof), design factorial
experiments, perform baseline and negative tests that provide experimental control, make sure
the benchmarking environment is safe on JVM/OS/HW level, ask for reviews from the domain experts.
Do not assume the numbers tell you what you want them to tell.

Benchmark                                              Mode  Cnt           Score          Error  Units
ThreadLocalIndexBenchmark.threadLocalIndexOptimize_1  thrpt    5   170159993.824 ±  1318284.420  ops/s
ThreadLocalIndexBenchmark.threadLocalIndexOptimize_8  thrpt    5<PHONE_NUMBER>.108 ± 23152204.877  ops/s
ThreadLocalIndexBenchmark.threadLocalIndex_1          thrpt    5   234089647.698 ± 16986301.995  ops/s
ThreadLocalIndexBenchmark.threadLocalIndex_8          thrpt    5   776787743.442 ± 50277549.179  ops/s

@RongtongJin  PTAL~


Contributors Documentation

Hi,
I would like to add better support for Typescript in the plugin however I have been unable to get the plugin to compile in IntelliJ (missing classes, etc...).
Could you please add some instruction details on how to set-up the dev environment in IntelliJ starting from the GitHub repo ?
Also, maybe you could commit the . idea directory with the exception of workspace.xml  file as a help ?
Thanks

I've updated the docs and hopefully you will be able to compile.
It's not recommended to push .idea to git so I hope you could do it without it.
Tell me if you need help.

I had a couple of issues to get going on 14.0.3:
1- IntelliJ does not import plugins well: I had to manually hack the react-templates-plugin.iml file to tell that it is not a java module but a plugin.
My current content is

Maybe you should consider committing this file at leat
2- I had to add jars to the IDEA JDK from my Utlimate installation at plugins/JavascriptLanguage/lib. I picked all of them but resources_en.jar. Maybe I do not need all of these
Since this is a plugin that can run in IntelliJ idea only, a few files from .idea may help
3- I had to comment out the completion.contributor in plugin.xml because the class com.wix.rt.codeInsight.PropertyCompletionContributor is not available in the sources. Could you please check ?
<completion.contributor language="HTML" implementationClass="com.wix.rt.codeInsight.PropertyCompletionContributor"/>
Thanks.
b.

On 12 Mar 2015, at 17:09, Ido<EMAIL_ADDRESS>wrote:
I've updated the docs and hopefully you will be able to compile.
It's not recommended to push .idea to git so I hope you could do it without it.
Tell me if you need help.
—
Reply to this email directly or view it on GitHub https://github.com/idok/react-templates-plugin/issues/5#issuecomment-78512184.


document and recommend try TiKV with TiUP

Update README to document and recommend try TiKV with TiUP, both start a release version or binary version built from source.
I'll try to take care of it this week.

Using TiUP to deploy standalone TiKV cluster is easy. Here is an example:

Ensure ssh connectivity between tiup's machine and several target nodes
topo.yaml:

global:
user: "ubuntu"
ssh_port: 22
deploy_dir: "whatever"
data_dir: "whatever"
pd_servers:

host: x.x.x.x
host: y.y.y.y
host: z.z.z.z

tikv_servers:

host: x.x.x.x
host: y.y.y.y
host: z.z.z.z

monitoring_servers:

host: a.a.a.a

grafana_servers:

host: b.b.b.b

alertmanager_servers:

host: c.c.c.c

$ tiup cluster deploy foobar v4.0.0 ./topo.yaml --user ubuntu -i ~/.ssh/id_rsa
$ tiup cluster start foobar
You're all set!

Thanks for your input @c4pt0r ! I think it can be a paragraph on setting up cluster deployment. However, for the beginner journey a local setup is more appreciated. It seems tiup itself doesn't support well yet and here is the improvement ticket.
I will create a pull request this week rephrase the "Try TiKV" paragraph and link it to your input above while putting your into doc folder. It is somewhat advanced topic, anyway.


Add Josh Hillmann to Contributors List

could you please add your name in Contributing.md rather than CONTRIBUTORS.md?

@hillmannj, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.


ADBDEV-1877 5.28.13 sync

Here are some reminders before you submit the pull request

[ ] Add tests for the change
[ ] Document changes
[ ] Communicate in the mailing list if needed
[ ] Pass make installcheck
[ ] Review a PR in return to support the community

Postgres planner tests failed with:

! DETAIL:  Could not write to file "pg_subtrans/0180" at offset 557056: No space left on device.

Tests were finished. Only known issues were detected.


Error when deploying using command line but no error when deploying from Application

Hello,
I'm having the following issue when deploying from command line:
##[error]Deployment failed! Column 'SalesRepNum' in Table 'Sales Rep' contains a duplicate value '91000033' and this is not allowed for columns on the one side of a many-to-one relationship or for columns that are used as the primary key of a table.
2023-01-12T08:05:51.7453150Z
##[error]Cmd.exe exited with code '1'.
But deploying the same model from TE2 application I'm not having any errors
Already checked Column 'SalesRepNum' in Table 'Sales Rep':
is not a key in the model
is not referenced in any relationships
Could you please help me figuring out this issue?
Thanks in advance,
Ben

Hi @BenT13
Could you share the command line that you are using to deploy with?
Thank you

Hi @mlonsk
Please find here below the command:
echo (Model.DataSources["BI SQL"] as ProviderDataSource).ConnectionString = Environment.GetEnvironmentVariable("BISQLConnectionString"); > SetConnectionStringFromEnv.cs "C:\Program Files (x86)\Tabular Editor\TabularEditor.exe" "$(System.ArtifactsDirectory)\$(Build.DefinitionName)\drop\Model.bim" -S SetConnectionStringFromEnv.cs -D "$(ASConnectionString)" "$(ASDatabase)" -O -C -V -E -W -R -P
Regards,
Ben

Thank you Ben,
Just to confirm. When you are deploying from within Tabular Editor where it works, you deploy to the same instance (Database and model) as when using the CLI

Yes indeed

If you have some availabilities as can have a screen sharing session and I can show you what I'm doing, maybe I'm missing some steps or not doing the rights things with TE2?

Hi Ben
I have a few more questions, but we can set up a meeting. :) Shoot me an email on<EMAIL_ADDRESS>Have you tried deploying from the CLI from your local laptop and does that work?
Which version of TE2 are you using in Devops?
Have you tried to "Process Clear" your SalesRep table and then running the deployment? Does it work then

Hi Morten,
I didn't try yet deploying from CLI from my local laptop.
Version of TE2 on my tfs server is 2.17.2, the same installed on my local laptop.
After a "Process Clear" deployment is successful, I'll know it for next time :)
Thanks a lot for your support,
Best regards,
Ben


TDR-1965 Rewording of error page and add reference to the email subject

I am wondering whether I should reword it similarly to the judgment error like  "One or more files you uploaded have failed our checks. Please try again. If this continues, contact us at<EMAIL_ADDRESS>to resolve the issue"? Because as it is now, it sounds like they should contact us straight away if they see this error rather than try again.

After discussion with Kirsten we have decided to word the error as such "One or more files you uploaded have failed our checks. Contact us at<EMAIL_ADDRESS>if the problem persists."


Feature Request: Display Last Edited Position in Preview for LeaderFBuffer

vim or neovim?

[x] vim
[ ] neovim

Output of vim --version or nvim --version: VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Nov 13 2024 20:39:13) Included patches: 1-842
Output of :echo has("python"): 0
Output of :echo has("python3"): 1
Output of :echo &pythondll(only vim, not neovim): libpython2.7.so.1.0
Output of :echo &pythonthreedll(only vim, not neovim): libpython3.8.so.1.0
Output of :py print(sys.version):
Output of :py3 print(sys.version): 3.8.10 (default, Jul 29 2024, 17:02:10) [GCC 9.4.0]
Output of :echo g:Lf_Debug_Cmd:
Output of :echo g:Lf_FilesFromCache:
Operating system:

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Configurations related to LeaderF in vimrc:

 let g:Lf_WindowHeight = 0.30
 let g:Lf_HideHelp = 1
 let g:Lf_UseCache = 0
 let g:Lf_UseVersionControlTool = 0
 let g:Lf_IgnoreCurrentBufferName = 1
 let g:Lf_StlColorscheme = 'Powerline'
 let g:Lf_MruEnableFrecency = 1
let g:Lf_PreviewCode = 1
let g:Lf_PreviewResult = {
        \ 'File': 1,
        \ 'Buffer': 1,
        \ 'Mru': 1,
        \ 'Tag': 1,
        \ 'BufTag': 1,
        \ 'Function': 1,
        \ 'Line': 1,
        \ 'Colorscheme': 0,
        \ 'Rg': 1,
        \ 'Gtags': 0
        \}
let g:Lf_WildIgnore = {
    \ 'dir': ['.git', '.hg', '.svn'],
    \ 'file': ['*.o', '*.a', '*.d', '*.i', '*.s', '*.bc', '*.so', '*.pyc', '*.swp', '*.class']
    \ }
let g:Lf_MruWildIgnore = {
    \ 'dir': ['.git', '.hg', '.svn'],
    \ 'file': ['*.o', '*.a', '*.d', '*.i', '*.s', '*.bc', '*.so', '*.pyc', '*.swp', '*.class']
    \}
" If needs
set ambiwidth=double
let g:Lf_StlSeparator = { 'left': "\ue0b0", 'right': "\ue0b2", 'font': "DejaVu Sans Mono for Powerline" }

" LeaderfFile
let g:Lf_ShortcutF = '<C-P>'
noremap <leader>p :LeaderfFile<CR>

noremap <C-L> :LeaderfMru<CR>
noremap <leader>l :LeaderfMru<CR>

"LeaderfBuffer
let g:Lf_ShortcutB = '<C-B>'

let g:Lf_CommandMap = {'<C-K>': ['<Up>'],
                     \ '<C-J>': ['<Down>']}

"noremap <leader>fs :<C-U><C-R>=printf("Leaderf file %s", "")<CR><CR>
"" preview all Line
nnoremap <leader>fl :<C-U><C-R>=printf("Leaderf line %s", "")<CR><CR>
"" preview all tag, such as function
nnoremap <leader>ft :<C-U><C-R>=printf("Leaderf bufTag %s", "")<CR><CR>
"" preview all tag, such as function, more detail
nnoremap <leader>ff :<C-U><C-R>=printf("Leaderf function %s", "")<CR><CR>
noremap <leader>fb :<C-U><C-R>=printf("Leaderf buffer %s", "")<CR><CR>
"noremap <leader>fm :<C-U><C-R>=printf("Leaderf mru %s", "")<CR><CR>

let g:Lf_RgConfig = [
    \ "--glob=!git/*",
    \ "--glob=!cscope.*",
    \ "--glob=!tags*",
    \ "--hidden"
    \ ]
" search word under cursor, the pattern is treated as regex, and enter
" normal mode directly
nnoremap <C-F> :<C-U><C-R>=printf("Leaderf! rg -e %s ", expand("<cword>"))<CR>

" search word under cursor literally in all listed buffers
nnoremap <C-D> :<C-U><C-R>=printf("Leaderf! rg --all-buffers -e %s ", expand("<cword>"))<CR>

" search word under cursor literally only in current buffer
nnoremap <leader>gc :<C-U><C-R>=printf("Leaderf! rg --current-buffer -e %s ", expand("<cword>"))<CR>

" search visually selected text literally
xnoremap <leader>gf :<C-U><C-R>=printf("Leaderf! rg -F -e %s ", leaderf#Rg#visual())<CR>

" recall last search. If the result window is closed, reopen it.
nnoremap <leader>gr :<C-U>Leaderf! rg --recall<CR>

Describe your question, feature request, or bug.
When I trigger :LeaderfBuffer or , the LeaderF buffer window appears. I would like the preview to display the last edited position of the file instead of starting from the first line. How can I configure this behavior?
Steps to reproduce

:LeaderfBuffer
 or ,  Preview show Edited locate。such as："chose file ，, :300 "

I would like the preview to display the last edited position of the file in the center of the preview window instead of starting from the first line.

Actual behaviour
Expected behaviour

Done. But it is displaying the last cursor position instead of last changed position.

Done. But it is displaying the last cursor position instead of last changed position.

How to set it so that the cursor is at the last position? With my current settings, the result always starts displaying from line 0.

no need extra settings.

It's weird, it doesn't work on my another machine either.

In vim 9.1.16 it does not work. It works in vim9.1.602.

In vim 9.1.842 it does not work.

It should work after 9.1.0500.

When I use git pull to get the latest LeaderF code, LeaderFBuffer works well.

[擦汗]


Implement redirecting to landing url after login

Adds a redirect query parameter to the login route if an unauthenticated user lands on an authenticated route.
Also fixes an issue I was having with safeAsync when writing tests for this new functionality.
Closes #188.

I solved this problem of returning to the pre-auth URL after auth in PrairieLearn with another cookie. It was much cleaner than query parameter parsing and was surprisingly easy to add (only 3-4 lines of code in the right place in the auth code).


Bumped version of the components and dropped old versions.

PHP 7.3 should probably be dropped from our supported versions

This PR is greatly appreciated and badly needed!

The problem with that I don't know what to do with doctrine/doctrine-mongo-odm-module - this is the dependency that is preventing from update now, if @Ocramius can tell what to do...

Not sure how to proceed either: practically, supporting version ranges that are not tested by our CI is not feasible, as it's just a lie towards end-users.
Only version ranges touched by CI should be part of our dependency range.
If doctrine/doctrine-mongo-odm-module is a problem, perhaps we should really just yeet it out.

Not sure how to proceed either: practically, supporting version ranges that are not tested by our CI is not feasible, as it's just a lie towards end-users.
Only version ranges touched by CI should be part of our dependency range.
If doctrine/doctrine-mongo-odm-module is a problem, perhaps we should really just yeet it out.

As I see it it is, I will do not PR without it and we will see how tests will go through. Maybe we can drop support for ODM for now? If someone will eventually update doctrine/doctrine-mongo-odm-module it will come back in a future.

Maybe we can drop support for ODM for now?

Would require a major version, if any of our API is affected.

Would require a major version, if any of our API is affected.

Should I do something except updating this PR to make it happen?

Just push to this branch: practically, all we want is to try bumping dependencies up, so we can try until we get to a dependency range that is fully tested by CI.

Okey, I'll try to do it and we will see =)

@Ocramius I had to fix few things in tests, as newer versions of doctrine libraries does not have some models, that were used. Please, write me if I have to do something else. I think tests should be passing now.

Not sure how to proceed either: practically, supporting version ranges that are not tested by our CI is not feasible, as it's just a lie towards end-users.
Only version ranges touched by CI should be part of our dependency range.
If doctrine/doctrine-mongo-odm-module is a problem, perhaps we should really just yeet it out.

I would vote towards yeeting it out. There are several other ODM providers and I think a module solely for mongoDB is the wrong approach. If we remove support on the next major version, a more generic ODM adapter could be introduced into the major version as a patch/minor version update.

Lots to be checked here :D

@tasselchof Do you need help getting this across the finish line? I could help out with the requested changes if needed.

@javabudd changes are done, just @Ocramius wrote, that there are a lot to be reviewed here - so we wait for review now.

@Ocramius psalm is reporting a lots of issues with config/admin.config.php file, what I should do about it?
Mostly this is a
ERROR: MixedArrayOffset - config/admin.config.php:193:40 - Cannot create mixed offset – expecting array-key (see https://psalm.dev/031)     'validator_metadata'            => [         Server\Validator\ObjectExists::class   => [             'entity_class' => 'string',             'fields'       => 'string',         ],         Server\Validator\NoObjectExists::class => [             'entity_class' => 'string',             'fields'       => 'string',         ],     ],

I wonder if it can't find Server\Validator\ObjectExists::class, therefore evaluating it to mixed?

I wonder if it can't find Server\Validator\ObjectExists::class, therefore evaluating it to mixed?

Exactly.

Are we missing a require then? These should be visible/located by vimeo/psalm.
Alternatively, replace their ::class version with a string version, if the design really requires them to not be existing classes (for BC purposes)

Are we missing a require then? These should be visible/located by vimeo/psalm.
Alternatively, replace their ::class version with a string version, if the design really requires them to not be existing classes (for BC purposes)

Can we just drop them I wonder - they are marked as ZF Legacy aliases:
https://github.com/laminas-api-tools/api-tools-doctrine/blob/2.5.x/config/admin.config.php#L81

If they are old ZF legacy aliases, then the right move is to:

mark them as deprecated (could be a comment - deprecation warning could be added later, perhaps)
use the string version, without ::class

If they are old ZF legacy aliases, then the right move is to:

mark them as deprecated (could be a comment - deprecation warning could be added later, perhaps)
use the string version, without ::class

The thing is that I can't find DoctrineAutodiscovery class at all, which was there:
use ZF\Apigility\Doctrine\Admin\Controller\DoctrineAutodiscovery;
So when I changed ZF\Apigility to Laminas/ApiTools everything went find besides this class.

I changed

That's another BC break though :thinking:
Overall, I'm fine with BC breaks, if we decide that this goes to 4.0.x, but everything should be weighed against the pain that the end-user will experience :D

That's another BC break though 🤔

I am not sure this issue could be done without BC breaks and this namespaces and things should be fixed sooner or later...

Yes, it's about calibrating how many BC breaks land in each major version.
The BC break here would be for people referencing these classes by string name: our mitigation could be to declare aliases for these services.

Here is the report from Roave/BackwardCompatibilityCheck: report.txt.

That report seems broken 😁

Sorry about that =)
report.txt

@tasselchof This one is so close to the finish line! I don't mind helping with the rest of the changes if you need.

@tasselchof This one is so close to the finish line! I don't mind helping with the rest of the changes if you need.

I am all in to finish it myself, but it depends on @Ocramius and reviewers.

TBH, I would say that we:

fix the broken bits I commented on
merge this against 3.0.x (I'll do it after approval)

@tasselchof I've applied the review changes on this PR into your branch: https://github.com/orderadmin/api-tools-doctrine/pull/1

@javabudd merged. @Ocramius what’s next? :)

It's all red? :P

It's all red? :P

We need bump of one module for hydration from API-Skeletons: https://github.com/laminas-api-tools/api-tools-doctrine/runs/7590699927?check_suite_focus=true#step:4:160
@TomHAnderson would you be so kind to do it?

@Ocramius is it ok to use my fork of this module? It works perfect and pull request there is taking too long time. I am speaking about https://github.com/API-Skeletons/doctrine-orm-hydration-module package.

@tasselchof not in the official package (here), but you can certainly use your fork locally.
See https://naderman.de/slippy/src/?file=2012-11-22-You-Thought-Composer-Couldnt-Do-That.html#30

@tasselchof not in the official package (here), but you can certainly use your fork locally.
See https://naderman.de/slippy/src/?file=2012-11-22-You-Thought-Composer-Couldnt-Do-That.html#30

Thanks for the reference - I am using it in our project though satis =)) Just I want to bump officials package.

OSS requires lots of patience: you aren't just trying to fix coding bugs, but also fighting for time allocation with people's free time :-)
Some of my own packages aren't compatible with PHP 8.1 yet, for example.

OSS requires lots of patience: you aren't just trying to fix coding bugs, but also fighting for time allocation with people's free time :-)
Some of my own packages aren't compatible with PHP 8.1 yet, for example.

Yeah, I understand this =)) Will be patient and contribute where I can. Thank you for your time, that you committing to this.

OSS requires lots of patience: you aren't just trying to fix coding bugs, but also fighting for time allocation with people's free time :-)
Some of my own packages aren't compatible with PHP 8.1 yet, for example.

I totally get this reasoning, however, PHP 7.4 reaches EOL on the 28th of November. This is one of the few Laminas libraries that still has yet to support even PHP 8.0 and I think prioritizing this merge/version update is very important.

What need to be fixed to merge it? I am using my fork in my projects, although I think somebody might need this one.


Fix: Don't throw on compression error

Use Promise.allSettled instead of Promise.all, to allow the build to go to completion even if any one of the files fails to be compressed.
And to give users visibility into the failed files, print them out at the end

@JuroOravec Thanks for the PR - however, as I don't really use this plugin anymore (most platforms already handle compressing files for you), I intend to deprecate it in favour of https://github.com/agaengel/gridsome-plugin-precompress


Add Adobe Substance 3D logos

Name with link
Adobe Substance 3D Collection
https://www.adobe.com/products/substance3d/3d-augmented-reality.html
Description
Newly added products into Adobe collection.
I would personally need it to my Tech Stack portfolio section.
Adobe Substance 3D Assets
https://www.adobe.com/content/dam/cc/icons/sb_assets_appicon_256.svg
Adobe Substance 3D  Designer
https://www.adobe.com/content/dam/cc/icons/ds_appicon_256.svg
Adobe Substance 3D  Sampler
https://www.adobe.com/content/dam/cc/icons/sa_appicon_256.svg
Adobe Substance 3D  Painter
https://www.adobe.com/content/dam/cc/icons/pt_appicon_256.svg
Adobe Substance 3D  Stager
https://www.adobe.com/content/dam/cc/icons/sg_appicon_256.svg

Cleaning


[BUG] Anchoring doesn't properly works in pages with tabs

Describe the bug
We can't get an anchor links to "titles" inside tabs other than the default one
To Reproduce

Go to some section inside a tab that isn't the default one, such as "React Native > 0.60" inside Components Getting Started,  and click its anchor:

Result url: https://gympass.github.io/yoga/components/getting-started#react-native--060

You'll be redirected to the main tab, since each tab is by itself already an anchor (such as #native)

Expected behavior
We should be able to "inherit" a tab inside our anchor in order to copy a direct link to a section rather to just the tab itself. We can open a page with a default tab, such as components/getting-started#native, but we can't link any other anchor inside this tab to be opened in.
Additional context
Other sites such as React Native's documentation for instance support an anchor direct to its title and it will infer the correct tab to be opened. In case of "conflicting" anchors, such as Adding Gympass font in your project that we have in both Android and iOS, they send you to the default one (Android)
See here for instance an example that will send you to the React Native CLI tab instead of the default one (Expo)

Hey @coelhucas,
Hope you're doing well! 🌟
Just wanted to give you a heads-up that it seems like this issue has taken a bit of a nap and gone MIA. 😴 Since we're doing some cleanup, we're going to close it for now.
No worries though! If you think there's still life in it or if you've got more info to share, feel free to wake it up by reopening. Your input is always appreciated!


allow Kepler to run if no Pods info exist

Is your feature request related to a problem? Please describe.
Currently, kepler aggregates metrics at Pods level when the cgroup is resolved and container ID can be retrieved from kubelet. In environment without kubelet, kepler should still export metrics, just not to aggregate them at pods level.
Describe the solution you'd like
Some env var to enable/disable kubelet query and allow kepler to export metrics without pod level aggregation

In environment without kubelet, kepler should still export metrics, just not to aggregate them at pods level.

so this is for something like docker-componse that not in k8s ecosystem but still containerized workload?

um... checked the code
https://github.com/sustainable-computing-io/kepler/blob/main/pkg/cgroup/resolve_container.go#L142
https://github.com/sustainable-computing-io/kepler/blob/main/pkg/cgroup/resolve_container.go#L326
seems we highly rely on above logic (get pods from kubelet) then resolve the containerID from pod info such as init/ephemeral/normal pod's each container info , if we remove the kubelet query, where should we obtain such info? so it's not only the pod info , but also the container info ?

@rootfs and @jichenjc since we have the process metrics can we close this issue?


Fix crash by adding Resources folder to output directory

Some projects did not run, resource not found. This fixes that by adding the resources to the output directory.

Thanks so much for this PR! Always a pleasure to see new contributors.
If you're in the discord, mention @varon there to get your name in blue!


Add change directory to bosh-lite

It is necessary to cd into the bosh lite directory for the the rest of the commands to work.

Added.


Appstudio update test-component-pac-vwid

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-vwid-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
18 seconds
clone-repository

✅ Succeeded
22 seconds
build-container

✅ Succeeded
31 seconds
clamav-scan

✅ Succeeded
8 seconds
clair-scan

✅ Succeeded
16 seconds
inspect-image

✅ Succeeded
15 seconds
deprecated-base-image-check

✅ Succeeded
8 seconds
sbom-json-check

✅ Succeeded
5 seconds
optional-label-check

✅ Succeeded
5 seconds
label-check

✅ Succeeded
5 seconds
show-sbom

✅ Succeeded
5 seconds
show-summary


Use the total # of processors instead of # online.

Use the total number of processors in the system since the number online can change from time to time.
When running this on a Jetson TX-2 which can bring processors online and offline and running a program under valgrind, these errors are reported:
==4895== Invalid read of size 8
==4895==    at 0x13BA8BC: grpc_completion_queue_create_internal(grpc_cq_completion_type, grpc_cq_polling_type) (completion_queue.cc:440)
==4895==    by 0x13B9B53: grpc_completion_queue_create (completion_queue_factory.cc:76)
==4895==    by 0x1203993: CompletionQueue (completion_queue.h:240)
==4895==    by 0x1203993: ServerCompletionQueue (completion_queue.h:378)
==4895==    by 0x1203993: grpc::ServerBuilder::BuildAndStart() (server_builder.cc:258)
==4895==  Address 0x269c9490 is 16 bytes after a block of size 29,952 alloc'd
==4895==    at 0x7900C3C: calloc (vg_replace_malloc.c:711)
==4895==    by 0x13E50DB: gpr_zalloc (alloc.cc:67)
==4895==    by 0x13CB1D3: grpc_stats_init() (stats.cc:36)
==4895==    by 0x1374C07: grpc_init (init.cc:127)
==4895==    by 0x1203947: GrpcLibraryCodegen (grpc_library.h:45)
==4895==    by 0x1203947: CompletionQueue (completion_queue.h:236)
==4895==    by 0x1203947: ServerCompletionQueue (completion_queue.h:378)
==4895==    by 0x1203947: grpc::ServerBuilder::BuildAndStart() (server_builder.cc:258)
==4895==
==4895== Invalid write of size 8
==4895==    at 0x13BA8C4: grpc_completion_queue_create_internal(grpc_cq_completion_type, grpc_cq_polling_type) (completion_queue.cc:440)
==4895==    by 0x13B9B53: grpc_completion_queue_create (completion_queue_factory.cc:76)
==4895==    by 0x1203993: CompletionQueue (completion_queue.h:240)
==4895==    by 0x1203993: ServerCompletionQueue (completion_queue.h:378)
==4895==    by 0x1203993: grpc::ServerBuilder::BuildAndStart() (server_builder.cc:258)
==4895==  Address 0x269c9490 is 16 bytes after a block of size 29,952 alloc'd
==4895==    at 0x7900C3C: calloc (vg_replace_malloc.c:711)
==4895==    by 0x13E50DB: gpr_zalloc (alloc.cc:67)
==4895==    by 0x13CB1D3: grpc_stats_init() (stats.cc:36)
==4895==    by 0x1374C07: grpc_init (init.cc:127)
==4895==    by 0x1203947: GrpcLibraryCodegen (grpc_library.h:45)
==4895==    by 0x1203947: CompletionQueue (completion_queue.h:236)
==4895==    by 0x1203947: ServerCompletionQueue (completion_queue.h:378)
==4895==    by 0x1203947: grpc::ServerBuilder::BuildAndStart() (server_builder.cc:258)
After this change, the errors are gone.  We also had many crashes on startup that was likely caused by this problem.
The Jetson has a user-level program that allows a user to changes CPUs to online or offline.  So using the max # possible should reduce potentials for errors like these and at worse over-allocate just a few extra bytes.

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @nnorwitz isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
CLA GitHub bot

The CLA was completed AFAIK.  Let me know if there's anything else to do to merge this.

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[microbenchmarks] No significant performance differences


Improve CI/CD

Description

Changelog Description

TODO

[ ] Test on multiple OS - Resolves #72
[ ] Deploy to Test PyPI

Questions

Status

[ ] I have read the guidelines in
CONTRIBUTING.md.
[ ] I have formatted my code using yapf
[ ] I have tested my code by running pytest (tox is run in CI/CD)
[ ] I have linted my code with pylint
[ ] This PR is ready to go

A possible issue here is that mac and windows are in higher demand and thus take longer to start jobs on.


Nuke frameworks if Podfile.lock has changed

This PR makes Rome nuke the built frameworks if the Podfile.lock file has changed.
This way caches won't have to be cleared manually, which is especially useful for CI.

I have committed the requested changes.


add kzu school

http://kzu.ch/
same type of school as "kzo" just another location.

@jsauvain Pull request merged. Please notice that free educational license for JetBrains tools is for high and higher schools students, i.e. those who are over 13 of age. Thank you!


fix: brief appended to intro by mistake

brief has been appended to the end of intro by mistake
this pr fixes this
bug screenshot (see the selected part):

Good catch thanks! Just need to wait for CI pass.
FYI the Julia version of Ion has been abandoned see also https://discourse.julialang.org/t/ann-the-ion-command-line-for-julia-developers-written-in-rust/94495/1

FYI the Julia version of Ion has been abandoned ...

Thanks for pointing this out.
I was checking Ion.jl mostly to make sure what I saw in my own CLI project with Comonicon was really bug (that also appears in another CLI project) but not something I did wrong.

is the failed CI related to my PR?
i tested it locally with the main branch and see the same error in CI.

Indeed seems due to #244 not updating the printing tests, I'll merge this one first


[Accordion] Fix invalid HTML inside heading

Fixes #44153
This PR resolves a regression introduced in #42914 by making the following changes to ensure valid HTML structure for the Accordion component:

Changed the Accordion summary element to button.
Updated the Accordion summary content and icon wrapper elements to span.

Additionally, typography has been removed from the demos since the p element rendered by Typography is invalid inside a span. Typography styles are now applied directly to the summary button using theme.typography.body1, making the extra Typography component unnecessary.
Breaking Change

The structure of the Accordion summary has been updated:

The root element is now a button.
Summary content and the icon wrapper are rendered as span.

Developers using the previous div element for styling in the AccordionSummary should update their styling. Additionally, those using Typography, which defaults to rendering a p tag, should replace it with a span or remove it for valid HTML, as shown in the updated demos.

These changes are critical to fix the regression but introduce a breaking change. IMO, this should be released in a minor version (v6.x) and documented in the migration guide. I know this is not ideal but the fix is also important.

If approved, I’ll include a note in the migration guide detailing these changes.

Any review even though it'a a breaking change?

@ZeeshanTamboli should there be any visual changes? I see one regression test changing due to typographic styles: https://app.argos-ci.com/mui/material-ui/builds/34147/123626742. I wonder if it should look the same given this PR is supposed to fix only the HTML structure and I wonder how many users will be affected by this change. Just asking in case we can avoid any visual change.

I just added the v7.x.

@ZeeshanTamboli should there be any visual changes? I see one regression test changing due to typographic styles: https://app.argos-ci.com/mui/material-ui/builds/34147/123626742. I wonder if it should look the same given this PR is supposed to fix only the HTML structure and I wonder how many users will be affected by this change. Just asking in case we can avoid any visual change.

@aarongarciah This regression test fails because it did not render Typography since the beginning, but typographic styles are now applied via theme.typography.body1. The issue is that keeping the Typography component in the rest of the demos results in invalid HTML because a <p> (Typography's default element) cannot be inside a <span>. Removing Typography causes significant visual regressions. To address this, I applied theme.typography.body1 directly to the Accordion Summary.
Options:

Remove theme.typography.body1 from accordion summary and Typography from demos, accept the visual regressions, and leave styling to the developer without enforcing typographic body1 style.
Remove theme.typography.body1 and keep Typography in the demos but use <Typography component="span" /> for valid HTML. However, this feels like a workaround.

Apologies for not flagging this earlier.

I just added the v7.x label

I think this should be released in v6. This can be considered a fix. The breaking change was already done in #42914 with the introduction of heading. We shouldn't have a breaking change which is wrong. What do you think?

@ZeeshanTamboli option 1 sounds like a breaking change, so I think this option shouldn't be introduced in v6. Option 2 sounds safer. Why using <Typography component="span" /> feels like a workaround? Changing the HTML tag is something Typography support so I'm curious why you feel that way.
cc @DiegoAndai in case you have some thoughts.

 However, after reconsidering, it doesn’t seem like a workaround anymore.
So I tried option 2: removing theme.typography.body1 and keeping Typography in the demos with <Typography component="span" /> for valid HTML.
But the issue is that removing theme.typography.body1 causes default HTML button styles to apply (see screenshot below). This forces the user to always use a Typography component for styling. IMO, the current approach what we have right now is better.

I agree with @aarongarciah that the changes proposed are breaking and cannot be released in 6.x, and we should try to find a workaround in the meantime

But the issue is that removing theme.typography.body1 causes default HTML button styles to apply (see screenshot below). This forces the user to always use a Typography component for styling the summary text.

What about removing the button styles?

What about removing the button styles?

How to do that?

I'm a bit lost.
This is the option I think we should go for:

Option 2: Remove theme.typography.body1 and keep Typography in the demos but use  for valid HTML. However, this feels like a workaround.

Why, then, are the typography styles not applied if we're still using the Typography component?

I'm a bit lost.
This is the option I think we should go for:

Option 2: Remove theme.typography.body1 and keep Typography in the demos but use  for valid HTML. However, this feels like a workaround.

Why, then, are the typography styles not applied if we're still using the Typography component?

@DiegoAndai See this sentence: This forces the user to always use a Typography component for styling the summary text.

Maybe we could:

Change the Accordion summary element to button.
Update the Accordion summary content and icon wrapper elements to span.
Keep Typography on the demos as before, but with component='span'

And release that as a minor.

I've made the changes. The first demo no longer uses Typography, so Argos CI flagged the change (aside from the flaky progress component test). I wasn't aware the first demo differed between CodeSandbox and the docs, but now they're the same. The docs theme isn't applied—is that okay? I think it is because the HTML button styles are applied, as shown in the screenshot:

This PR: https://deploy-preview-44408--material-ui.netlify.app/material-ui/react-accordion/#introduction
Production: https://mui.com/material-ui/react-accordion/#introduction)](https://mui.com/material-ui/react-accordion/#introduction

@ZeeshanTamboli can you update the first demo to include the Typography component so it looks the same as the other demos?

@ZeeshanTamboli can you update the first demo to include the Typography component so it looks the same as the other demos?

@aarongarciah Updated.

@aarongarciah

Add an entry in the migration guide explaining the change.

Added. https://deploy-preview-44408--material-ui.netlify.app/material-ui/migration/upgrade-to-v6/#accordion-starting-from-v6-3-0

Update the PR description to reflect the latest changes in the PR.

Updated

CC: @mnajdova for next week's release: this required a minor bump and a mention on the CHANGELOG.

I argue this can be considered as a fix (of previously invalid HTML) more than a breaking change so I'm removing the "breaking" label and instead labeling as "minor version change".


v2 parsing

First half of support for version 2 of Docker Compose. All v2 files should now be parsed, although no actions are taken for the new volumes and networks keys yet (the part you're likely interested in :smile: )
This is essentially a refactoring that makes projects store service configs in v2 format internally, rather than in the existing format. When parsing v1 files, they are first converted to v2 format. Processing is the same for both after this point. All existing v1 functionality should remain exactly the same.
What's left:

Implementing volumes and networks
Validating v2 files (although the schema is added by this PR)
A suite of integration tests for v2 files

Signed-off-by: Josh Curl<EMAIL_ADDRESS>

@joshwget yay :tada: It looks good ! It doesn't seem to break anything (build is green :green_heart:), so I'm more than willing to merge it early and iterate over it (that way we can parallelize the work, for example on the config command, and taking care of network and such \o/).
Big LGTM :+1:


Rebaseline JavaIncrementalExecutionPerformanceTest

To accept a <1% regression

@bot-gradle test and merge

No milestone for this PR. Please set a milestone and retry.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Compilation failure when building on 32-bit windows

..\..\elastic\gosigar\sigar_windows.go:491: cannot use &availableBytes (type *C.ULARGE_INTEGER) as type *[8]byte in argument to _Cfunc_GetDiskFreeSpaceEx

This should be fixed in master. Please re-open if you find any other issues on 32-bit Windows. Thanks


121 | Best Time to Buy and Sell Stock | C++

Best Time to Buy and Sell Stock -
What will change -
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language
Please add/delete options that are not relevant.

[x] C++

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

Assign me to this issue! Thanks...


[FLINK-33313][table] fix RexNodeExtractor#extractConjunctiveConditions throws an Exception when handle binary literal

What is the purpose of the change
Fix a bug that RexNodeExtractor#extractConjunctiveConditions throws an Exception when handle binary literal
Brief change log
cast ByteString to byte[] in RexNodeToExpressionConverter#visitLiteral
Verifying this change
This change added tests and can be verified as follows:

Added a new test testExtractCnfCondition in RexNodeExtractorTest

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

@flinkbot run azure

@flinkbot run azure


Request for Feedback: V1.0.7 release

Hi,
After some final testing I would release the current version 1.0.7. Think this should be the last version supporting old Visual Studio and Boost versions.
With next 1.0.8 I would then:

support VS2015+ only / remove support of older VS versions
support Boost 1.60+  only / remove support of older Boost versions
remove parsing the source code

Regards,
Günter

Moved remaining issues to v1.0.8.

Release Notes: https://github.com/etas/vs-boost-unit-test-adapter/releases/tag/buta-1.0.7

Hi everyone,
Like to ask you to test v1.0.7. If everything is working we will distribute it in the Visual Studio Gallery:
https://github.com/etas/vs-boost-unit-test-adapter/releases/tag/buta-1.0.7
Regards,

Hi,
tested today Buta 1.0.7. using Microsoft Visual Studio Ultimate 2013, Version 12.0.40629.00 Update 5 and my existing tests. Unfortunatly I cannot see let alone execute my data driven tests via the test adapter. As by your discussion on this topic, issue #23 Support BOOST_DATA_TEST_CASE should have been solved in 1.0.7. Any feedback on how to use this feature is greatly appreciated, since this (beside supporting DISABLED tests) is the one I was looking forward for a rather long time.
However, at least I detected no breaking changes with my tests so far :)
Regards

@foobar303 thanks for your feedback and just for completeness: which boost version are you using?

Boost 1.60.0.

Additional note: Test output yields the following message "Could not locate debug symbols for 'C:\workspaces.build\bin\Debug\MyApp.exe'. To make use of '--list_content' discovery, ensure that debug symbols are available or make use of '' via a .runsettings file."

Hi @foobar303 and thank you for the feedback.
Could you kindly look into issue #120 and see if your issue is similar? In brief, list content discovery is not being used due to missing debug symbols which was caused by certain compilation properties.

Which compiler options are known to cause failing the list content discovery? My test projects use the following settings:

Linker/Debugging/Generate Debug Info: "Yes (/DEBUG)"
C/C++/General/Debug Information Format: "Program Database (/Zi)". I tried /Z7 and  /ZI instead (while the latter will be changed back automatically since I'm compiling for 64 bit), anyway, none of these changed the described behavior.

Eventually, when using a .runsettings file
<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
  <BoostTest>
    <ForceListContent>true</ForceListContent>
  </BoostTest>
</RunSettings>

the warning mentioned in my previous post disappeared. Although in this case my data driven tests do not show up in Test Explorer either (am I wrong to expect this?), the VS Test Output showed messages like the following when running all tests from Test Explorer:
Executing:   -> [UnitTests_DbUtils/ScanMode_WithinBounds_DoesNotThrow]
Executing:   -> [UnitTests_DbUtils/ScanMode_OutOfBounds_Throws]
Test adapter sent back a result for an unknown test case. Ignoring result for 'ScanMode_WithinBounds_DoesNotThrow'.
Test adapter sent back a result for an unknown test case. Ignoring result for 'ScanMode_OutOfBounds_Throws'.

Guess this indicates that at least test have been being executed but for some reason test adapter can't handle the results properly. Note that test do not fail when executing via the .exe.

@foobar303 Could you kindly open a new issue(s) in this regard please? It seems that there are 2 issues: debug symbols not being located properly and possibly something wrong with test registration for BOOST_DATA_TEST_CASE.
Providing log files (log file path should be listed in output window) should be helpful for debugging. A test sample which can be used to reproduce the issue also helps. Please note that these may contain sensitive data (path information, test names, source code) so be wary before posting such material.

Hi netspiri,
just opened new issu #130.

Team 1: Visual Studio 2015, Boost 1.60 ==> everything working

Team 2: Visual Studio 2015, Boost 1.59 ==> Breaking change #71, #99
With 1.0.6 the "current directory" was the directory of the boost EXE. Starting with 1.0.7 it's the Config / Debugging / Working Directory setting which is per default $(ProjectDir) and not $(OutDir) as before.
Don't know where VS is storing this setting? Seems to be not in the project file .vcxproj

@guwirth
VS by default stores the Working Directory setting in the ProjectName.vcxproj.user file that is placed next to the project file. The relevant XML node is named LocalDebuggerWorkingDirectory.
Answering the main question — 1.0.7 changes that detect working directory and environment work great for me. Thanks! :-)

@foobar303 Unfortunately, that is a known issue. The Boost test framework (1.59) returns that kind of data as the line number (see example output below). I do not know if this has been fixed in recent Boost Test versions. Regarding the use of .runsettings, it can be avoided if you include the test framework within your module instead of dynamically linking to Boost Test. By omitting the #define BOOST_TEST_DYN_LINK and providing debug symbols, the test adapter should be able to use --list_content=DOT automatically.
tu65581[shape=Mrecord,fontname=Helvetica,color=yellow,label="DataLost|d:\boostunittest\test_a.cpp(1047)"];
tu22 -> tu65581;
tu65590[shape=Mrecord,fontname=Helvetica,color=yellow,label="ChangeEvent|(3435973836)"];
tu22 -> tu65590;

@guwirth As @mwu-tow correctly mentioned, the property can also be set from here:

The reason for this 'breaking' change in behaviour is to ensure that running the test program from Visual Studio (via Debug - Start Debugging/Start Without Debugging) and from the test explorer should react in an equivalent manner. We have had issues in the past were tests running via the test explorer passed but running them from the executable directly from Visual Studio failed due to assumptions made about relative paths.
As a general note, I would like to thank all for the helpful feedback and for supporting this project.

... The relevant XML node is named LocalDebuggerWorkingDirectory. ...

@guwirth As @mwu-tow correctly mentioned, the property can also be set from here:

Think current behaviour is ok but surprising for some users because their unit test are red now. Setting can be changed per project but only in .user file which is currently not part of our repository.
Main issue is that behaviour from command line and within VS is different now.:

run tests from command line: test files are expected in parallel to EXE
run test from VS: test files are expected in $(ProjectDir) per default

... but at the end I think we should release it as it is.

VERSION <IP_ADDRESS> is ready to download from the Visual Studio Gallery.
Also from my side thanks to all contributors!


SO-4751: support nested object and array/collection property auto merging

This PR introduces automatic merging of non-conflicting nested objects, arrays, and collections during rebase/merge operations.

Codecov Report

Merging #790 (28b7430) into 7.x (1f5fbbd) will increase coverage by 0.03%.
The diff coverage is 80.54%.

@@             Coverage Diff              @@
##                7.x     #790      +/-   ##
============================================
+ Coverage     58.91%   58.94%   +0.03%
- Complexity    12884    12909      +25
============================================
  Files          1777     1779       +2
  Lines         65628    65776     +148
  Branches       6475     6512      +37
============================================
+ Hits          38665    38774     +109
- Misses        23948    23969      +21
- Partials       3015     3033      +18

Impacted Files
Coverage Δ
Complexity Δ

...core/merge/ComponentRevisionConflictProcessor.java
88.88% <50.00%> (-11.12%)
4.00 <1.00> (ø)

...b2international/index/mapping/DocumentMapping.java
73.38% <61.11%> (-1.62%)
55.00 <13.00> (+10.00)
:arrow_down:

...m/b2international/index/es/admin/EsIndexAdmin.java
83.19% <66.66%> (+0.08%)
87.00 <2.00> (ø)

...x/src/com/b2international/index/util/JsonDiff.java
75.30% <75.30%> (ø)
18.00 <18.00> (?)

...onal/index/revision/RevisionConflictProcessor.java
83.05% <80.76%> (-16.95%)
3.00 <0.00> (ø)

.../src/com/b2international/index/util/ArrayDiff.java
94.11% <94.11%> (ø)
4.00 <4.00> (?)

...om/b2international/index/revision/StagingArea.java
93.44% <95.45%> (-0.27%)
189.00 <3.00> (-7.00)

...erge/SnomedComponentRevisionConflictProcessor.java
90.09% <100.00%> (ø)
37.00 <0.00> (ø)

...wl/fhir/core/model/conceptmap/TranslateResult.java
77.41% <0.00%> (-6.46%)
6.00% <0.00%> (-1.00%)

.../snomed/core/ecl/SnomedEclRefinementEvaluator.java
87.16% <0.00%> (-0.30%)
108.00% <0.00%> (ø%)

... and 3 more

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 1f5fbbd...28b7430. Read the comment docs.


Update Storybook to reflect the use of carbon-icons

Detailed description
It's not an issue related to the components per se, more to the Storybook documentation. In Storybook, the example using icons are not truthful.
Using Storybook code leads to mistake when you're not familiar with the codebase. If we look at Structured List as an example we can see that when copy and pasting code the icon property is actually a JS object, which is not correct, it should be an object imported from carbon-icons.
Code examples and solution below.
Steps to reproduce the issue

Go to the Storybook for Structured List
Copy and paste code in your own app.

Test Case in Sandbox:
https://codesandbox.io/s/k24o7pomm5
Solution in Sandbox:
https://codesandbox.io/s/q8580y7jww

Hi 👋 thank you for reporting! Storybook's "Story Source" feature seems to have a limitation showing prop with complex object, where it shows some inner-properties with "...", which seems to have caused a confusion. The actual Storybook code can be found at https://github.com/IBM/carbon-components-react/blob/v6.39.0/src/components/StructuredList/StructuredList-story.js#L85, whose icon is actually coming from carbon-icons. Hope this helps!

Hey,
It does help, thanks! Could we keep this issue open? I'd like to find a way to fix that but I don't have any ETA to provide at the moment.
Cheers

Sure @carvallegro! Looking forward to hearing from you - It may end up with a fix to Storybook or its add-on.

@carvallegro Just wanted to ping to see if you are still interested in this area. Thanks!

Hey! I'm currently without any computer so literally not able to touch
code. Not sure when I'll be able to have a look
On 2:03PM, Mon, 04/02/2019 Akira Sudoh<EMAIL_ADDRESS>wrote:

@carvallegro https://github.com/carvallegro Just wanted to ping to see
if you are still interested in this area. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IBM/carbon-components-react/issues/1491#issuecomment-460118943,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUjYi9hOBmcrfsaoycxLB8hKfIzNprks5vJ6MZgaJpZM4X9V2H
.

Thanks @carvallegro for the response - Closing for now, can reopen if anybody else has an interest!


List of available methods is incomplete, covers only SysQueryRangeUtil

There are many more methods, which are supported by other classes then SysQueryRangeUtil with many useful methods. The listing here should be extended to cover as much as possible of these interfaces. For example HcmWorkerLookup::currentWorker().

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

ID: f307ed75-4498-8c54-13ed-a9c25d8a286b
Version Independent ID: 8f4e1122-fa74-4e64-8a5d-80d6ddd58201
Content: Advanced filtering and query syntax - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/fin-and-ops/get-started/advanced-filtering-query-options.md
Service: dynamics-ax-applications
GitHub Login: @jasongre
Microsoft Alias: jasongre

Thanks for taking the time to provide feedback. Your comment has been noted as a future enhancement to the documentation.


Cannot compile Windows C reverse shell

By compiling with cl, I get payload.c(23): error C2198: 'strcpy_s': too few arguments for call

By compiling with cl, I get payload.c(23): error C2198: 'strcpy_s': too few arguments for call

The strcpy_s function takes three arguments: the destination string, the size of the destination string, and the source string. You are likely only providing two of these arguments. To fix this error, you need to make sure that you are providing all three of the required arguments. For example, if you are trying to copy the string "Hello, world!" to a buffer of size 20, you would call strcpy_s like this:
char dest[20];
strcpy_s(dest, sizeof(dest), "Hello, world!");

ChatGPT detected ⚠

Will be closed with #148


0043 - Multiply Strings

Description of the Problem
Given two non-negative integers num1 and num2 represented as strings, return the product of num1 and num2, also represented as a string.
Example 1:
Input: num1 = "2", num2 = "3"
Output: "6"

Example 2:
Input: num1 = "123", num2 = "456"
Output: "56088"

Note:

The length of both num1 and num2 is < 110.
Both num1 and num2 contain only digits 0-9.
Both num1 and num2 do not contain any leading zero, except the number 0 itself.
You must not use any built-in BigInteger library or convert the inputs to integer directly.

Link To The LeetCode Problem
LeetCode Problem 43

Hey can you assign me this issue?
I have good experience with competitive programming as well [ rated 1900+ on codechef ]


UserList definition missing in README?

I think possibly your HTMY templating example in the README for this repo needs the definition of UserList from your htmy repo

htmy is cool btw thanks for making it and fasthx

Hi,
First of thank you!
You're totally right. I was deliberating whether to include everything in examples or not. In the end I decided that since the Jinja example doesn't include the Jinja template itself, I'll also skip the component implementation for HTMY in the readme and only show how to use a component in the decorators. It may be a bad idea.
Actually the full, working example is both in the docs and in the examples folder. Maybe the best solution would be to add a line to each example in the readme with a link to the full, working code.
What do you think? Would you maybe prepare a PR for this change?
I hope you'll like these tools. Feel free to report problems you may bump into, or even better PRs with improvements (there's a lot of room for it especially with htmy).


Add Special Number Calculator

DESCRIPTION
To check if the given number is a special number or not.
For example, 1729 is a special number since, when its digits are added together, produces a sum that, when multiplied by its reversal, yields the original number:
1 + 7 + 2 + 9 = 19
19 × 91 = 1729
CHECKLIST

[x] I have checked the existing issues.
[x] I am a GSSOC'24 contributor.

SCREENSHOT

@Sravyasaka Check your points. Let me know


Option to set python.analysis.packageIndexDepths  depth globally.

MacOS 13.0
VSCode Version: 1.73.1
Pylance v2022.11.30
Pylance language server 2022.11.30
For now if you want to fully index (deeper than 2 directories deep) installed libraries to get auto import working you have to do something like this in your settings.json for each library:
 ],
  "python.analysis.packageIndexDepths": [
    {
      "name": "rest_framework",
      "depth": 10,
      "includeAllSymbols": true
    },
    {
      "name": "django",
      "depth": 10,
      "includeAllSymbols": true
    },
    {
      "name": "factory",
      "depth": 10,
      "includeAllSymbols": true
    }
  ]

I would like to have an option to index everything globally, taking the performance hit

to change the default set name to ""

@bschnurr If I do
"python.analysis.packageIndexDepths": [
    {
      "name": "",
      "depth": 10,
      "includeAllSymbols": true
    }
  ]

my library competitions doesn't work at all

Repro:

No setting set or one below:

"python.analysis.packageIndexDepths": [
    {
      "name": "",
      "depth": 10,
      "includeAllSymbols": true
    }
  ]

pip install django-rest-framework
Type ListAPIView, no completition
3.Change setting to one below

 "python.analysis.packageIndexDepths": [
    {
      "name": "rest_framework",
      "depth": 10,
      "includeAllSymbols": true
    }

4.Type ListAPIView ->

This issue has been fixed in prerelease version 2022.11.42, which we've just released. You can find the changelog here: CHANGELOG.md

I can confirm, that now
"python.analysis.packageIndexDepths": [
    {
      "name": "",
      "depth": 10,
      "includeAllSymbols": true
    }
  ]

works correctly, thanks a lot!

@diego351 I just checked, and it worked as expected. since you are searching for depth 10 for every module installed, it will take long time to index, make sure you wait for it to finish.
once indexing is finished, you will be able to see Indexing finished in Python Language Server in output tab.
For me, with only a few packages installed, enabling depth 10 for all modules took almost 1 min on my dev machine.


Franz fails to load completely

Describe the bug
Franz will not load.  The 2 Franz.exe processes show in the task manager, but the application itself does not.
To Reproduce
Had Windows crash at some point, which began the trouble.
Have tried uninstalling & reinstalling several times, cleaning the registry and updating to the latest beta.  When I go to uninstall, it does claim that Franz is running, but it will never appear in the tray icon nor in the application tab of the task manager.
Desktop (please complete the following information):

OS: Win 7 Pro 64bit
Browser: use both Mozilla and Chrome
Version: 5.0.1-beta1 (previously 5.0.0 with same issue)

Solved own problem.  Had to go to C:\Users%user%\AppData\Roaming and delete the Franz folder, then reinstall again.
Would suggest that either the uninstall or install script have the option of a complete cleanup or fresh install.


feat(sidecar): gross tip revenue metric

I've not seen the metric added anywhere in the sidecar code, is this PR still draft?

Yes mb, converted


ospdo adoption makefile tests

Add Director Operator test execution scripts for adoption
Related CI patch and background:
https://gitlab.cee.redhat.com/ci-framework/ci-framework-jobs/-/merge_requests/966
PRs submitted together :
related PR list
Jiras:
https://issues.redhat.com/browse/OSPRH-1891
https://issues.redhat.com/browse/OSPRH-2984

recheck

recheck

recheck

recheck

Approved since last week, merging.


Extra the hard code to a constants file

Why you need it?
Is your feature request related to a problem? Please describe in details
Extra the hard code to a constants file.
If you want to support it, please comment "Please assign it to me" is this issue.
How it could be?
A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.
Other related information
Add any other context or screenshots about the feature request here.

Please assign it to me


Ignore compaction group with only 1 block

Signed-off-by: Ben Ye<EMAIL_ADDRESS>

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

If the compaction group only contains 1 block metadata, then there is nothing to plan and compact. In this case, we can safely ignore the group.
Changes

Verification

Oops, sorry, brain fart. I meant that I thought the planners were taking care of this - they check whether there is any work to perform. So, this won't bring any visible change to users, right? Except for those metrics and not creating/removing dirs unnecessarily

So, this won't bring any visible change to users, right? Except for those metrics and not creating/removing dirs unnecessarily

Yeah, that's correct. There is no difference except the metrics I would say. Maybe some CPU time can be saved because we omit the planning phase.
But overall it is a tiny thing so this pr is mainly a cleanup.

So, this won't bring any visible change to users, right? Except for those metrics and not creating/removing dirs unnecessarily

Yeah, that's correct. There is no difference except the metrics I would say. Maybe some CPU time can be saved because we skip the planning phase. But overall it is a tiny thing so this pr is mainly a cleanup.

:+1: let's remove those old comments in the test and merge this


update deployment diagram for cdk app

closed by https://github.com/josefaidt/amplify-discord-bots/commit/743d6281b4c5a134464b41c8c5deb07355083cc9


Allow rate limiting per URL rather than per service

This change allows rate limiting per path on a service. So user would get limited only if he repeatedly accessed the same path on a service, however calling various endpoints in a row wouldn't be an issue.
Feedback welcome!
Michal

Thanks for this PR @msvab could you update the README.md file with this new option?

@msvab Thanks for the updates I'll try to generate a new version with your stuff in couple hours

@msvab I just released the version 1.0.5.RELEASE to the maven central.
Thanks a lot.

Great, thanks for such a fast turnaround!

If you find any issue let me know


@go.restore_stubbed_core_modules, lib/kcov-ubuntu, and test tweaks

This is a collection of three small changes I want to merge before a more substantial change to extract lib/bats-main in the next PR:

Previously, if no modules had been stubbed, @go.restore_stubbed_core_modules would
try to remove the glob pattern itself, resulting in an error message. Now it's a no-op if nothing's been stubbed.
Updated lib/kcov-ubuntu to use the new @go get git-repo from #114.
Replaced run env VAR=foo with VAR=foo run everywhere. Don't notice much of a performance impact on macOS, but it's more consistent with my more recent style and should save a process, which might make more of an impact on Windows.

Coverage increased (+0.004%) to 95.299% when pulling c38fb1fb81cdf7819f2758adfae8335bcd58877d on tweaks into 2c4f9c0c9a9378cfa6338f8859737625a352243d on master.

Coverage increased (+0.004%) to 95.299% when pulling 00925fe505b9b4100a42e79de6be2adaac31a1d0 on tweaks into 2c4f9c0c9a9378cfa6338f8859737625a352243d on master.


Support .NET Core tool installation

Thought an easy way to get the NetSparkle.Tools installed and available for me to use might be using dotnet tool install but it looks like it's not a compatible package type to do so. Wondering if this might be a useful thing to do, to make it that type of package?
Trying gets this which troubleshooting says it's a regular nuget package instead of a Core Tool package:
NU1212: Invalid project-package combination for <ToolName>. DotnetToolReference project style can only contain references of the DotnetTool type.

This is a great idea. Thank you for the suggestion.
Note to self/whomever: https://docs.microsoft.com/en-us/dotnet/core/tools/global-tools-how-to-create is a tutorial on how to do this. Will need to figure out how to update the current NuGet and/or the CI/CD to do all this.

I downloaded source then just added below 3 lines to project xml
<PackAsTool>true</PackAsTool>
<ToolCommandName>appcast</ToolCommandName>
 <PackageOutputPath>./nupkg</PackageOutputPath>
then it was a simple as dotnet tool install --global --add-source ./nupkg generate_appcast
Im not sure  if this would let you install without unpacking nuget from web before trying to install or not.  I think user would need to download, unpack then install using above dotnet command

first time center, but I've been lurking a while.
what would it require to have the generator tool made available as a NuGet package as part of the normal release?
I'm adding something like tests, a release process of some kind and then something like github actions to bring this together.
I'm willing to help agent this available (I've just put NetSparkle into an app i ported from mac), and having the tool available on whatever I'm using to rebuild the appcast would be very helpful.
if it's already been done and I've not seen it - apologies in advance.

@johncclayton Thanks for your question. Does https://www.nuget.org/packages/NetSparkleUpdater.Tools/ help? It should have the app cast generator in it.

Absolutely - I checked the code out to work out what I was doing wrong on the command line.  I've got a lot of experience in IT (over 20 years), but am really new to the whole .net / CLI part - so while the tools worked, I didn't know how to get the generator .exe tool installed reliably at a path location I could use for the build.
But if it's just something like: dotnet install that I have to do - it sounds done already :-)
When I installed the package the exe ended up in C:\Users\john.nuget\packages\netsparkleupdater.tools\2.0.0-preview20210131001 - and of course this isn't on a standard build path.  If there's a way to get that tool available in a GitHub action more easily - I'd love to know about it.
Thanks for the fast answer.

I tried the changes as outlined by @aelmendorf - that worked really great - thank you.  It probably wants to be called something different than appcast, likely generate_appcast.exe right?  I can create a PR from my own forked version of the repo if that'd help.

Hi, sorry, not wanting to ignore you. Just very busy.
I have two pending questions/things to research in my mind about this that need to be figured out:

How do I properly publish this to NuGet? I probably have to have 1 tool per 1 NuGet package, I'd assume, rather than the current setup of all tools in 1 package?
Is everything setup properly for the tool to list things on all 3 platforms such that dotnet tool install will work right? I have no clue if I've set up the NuGet package properly.

As far as a name: netsparkle-generate-appcast is what I would prefer, personally, to differentiate it with the macOS Sparkle library.
tl;dr: I have research to do to understand how all of this works and if the CI/CD and NuGet need restructuring. I won't have time to do this for a while. If someone else knows how this works, it'd be greatly appreciated.

I get busy, no problem at all.  I am more than happy to start looking for answers to these questions - as part of my learning journey into .net.
I believe at a minimum, having the generate-app-cast tool in a separate NuGet package makes a TON of sense.  I like the cross platform aspect of that a LOT, and I have the gear here to test it on all 3 platforms if that helps.   I don't have an M1 thing, but I know someone who does.
Got any good links to help me get up to speed on NuGet packaging / building them / best practises?  I'm totally willing to learn this to help out.

Ok, tomorrow I'll read the following properly:
1. https://docs.microsoft.com/en-us/dotnet/core/tools/global-tools-how-to-create
2. https://docs.microsoft.com/en-us/dotnet/core/tools/local-tools-how-to-use

I think I'll play around with using a manifest file and see if I can get it to a stage where I'm able to change my build process to simply do:
$ dotnet tool run netsparkle-generate-appcast <arguments>

Please forgive me ahead of time if I'm spouting utter rubbish, the tooling and how it all hangs together (and what its possibilities and limitations are) is still really new to me.
Sleep calls.
(2am).

Hi
I spend a couple of hours learning / experimenting with the nuget tool & packaging.  I learned the ropes by creating a simple tool project, and published this locally.  I then proceeded to install it from my NAS on Mac, Windows and Linux systems.
The installation works like a charm in both global and local.  The tool .exe/command can be called whatever you like (and dotnet tool upgrade takes care of tool name changes across versions - which is a nice touch).
I tested the behaviour on Windows, Linux (via VM) and Mac - all of them seem to work exactly the same way.  No surprise there really; hats off to the dotnet 5.0 dev work that was done to bring the same codebase to each of those platforms!
In my case I'm interested in having this tool available without having to mess with the PATH; doubly so when it comes to cross platform builds.  For this use case I would choose a local install as it allows me to run the command via dotnet tool run <name-of-tool>, so I can use the same command across all platforms.  I find that valuable as its less stuff that I need to keep in my head "just because I'm on Mac and not Windows etc etc".  Additionally if I switch branches and require some other version of the tool this local install can be changed without breaking other projects.
Here's what I'd suggest as next steps:

update the documentation for newbies (like me); such that it describes explicitly how to set up a working build environment & the right way to install the tool - this is important; because there is a "wrong" way as well (by trying to use the .Tools package as a dependency - I'll explain that below).
I'd like to write up the stuff I would have loved to have the first time I saw the docs - I came into NetSparkle with no nuget tool knowledge, and didn't know about local vs global - having a bit of background will certainly help other devs reach success and also help NetSparkle gain even more traction.
Change the csproj XML tags for the tool as suggested by @aelmendorf - additionally using the ToolCommandName tag as you wanted the thing to have a very specific name.

     <PackAsTool>true</PackAsTool>
     <ToolCommandName>netsparkle-generate-appcast</ToolCommandName>

BTW: I don't see a need to separate out the tools into a separate NuGet package, that just seems like more work for no benefit.

Doing this allows the tools to be used something like this - anywhere - e.g. GitHub Actions etc - note the use of a local tool to make it possible to run it without having to know the path name:
$ dotnet new tool-manifest
$ dotnet install tool NetSparkle.Tools (a local install - not global)
$ dotnet tool run netsparkle-generate-appcast <args>

After 3 hours of learning and playing around - I like that this patch appears to be simply two lines of XML configuration.  My goodness; if that's actually TRUE I'll be a happy man.
Let me know what you think; I'd be happy to adjust the outstanding PR to include documentation changes as well.
Thank you!

@johncclayton Thank you SO MUCH for your contributions, here. That's very helpful to confirm that the csproj changes are really all that is needed!
I have done the following:

Merged your PR with those changes
Published two NEW packages: NetSparkleUpdater.Tools.AppCastGenerator and NetSparkleUpdater.Tools.DSAHelper. Two new packages keeps things separate (versions, etc.) and also makes it possible to allow BOTH of these tools to work as .NET global tools.

dotnet tool install --global NetSparkleUpdater.Tools.AppCastGenerator -> netsparkle-generate-appcast
dotnet tool install --global NetSparkleUpdater.Tools.DSAHelper -> netsparkle-dsa

Bumped tool versions to .NET 5 instead of .NET Core 3.1
Deprecated NetSparkleUpdater.Tools in lieu of the two new packages (plus some issues with having that as one package when there is PackAsTool set -- see this GitHub issue in dotnet)

update the documentation for newbies (like me); such that it describes explicitly how to set up a working build environment & the right way to install the tool - this is important; because there is a "wrong" way as well (by trying to use the .Tools package as a dependency - I'll explain that below).

Please feel free to submit a PR! You can make a new section in the README for this.

I'd like to write up the stuff I would have loved to have the first time I saw the docs - I came into NetSparkle with no nuget tool knowledge, and didn't know about local vs global - having a bit of background will certainly help other devs reach success and also help NetSparkle gain even more traction.

Again, please feel free to submit a PR!
I'm going to go ahead and close this issue as "finished" -- for doc update requests, please comment on #61 or create a new issue for that specific documentation.
Thank you for your patience and for everyone's help!


[BUG] Using vmimage.status.storageClassName to fill volumeClaimTemplates

Describe the bug
When changing storage class name format (https://github.com/harvester/harvester/pull/5459), I cannot create a VM with new format. It looks like dashboard uses longhorn-<vmimage-name> as storage class name. It's better to get storage class name from vmimage.status.storageClassName.
To Reproduce
Steps to reproduce the behavior:

Install a new harvester cluster with https://github.com/harvester/harvester/pull/5459.
Create a VMImage and VM.
VM PVC can't be provisioned cause of storage class not found.

Expected behavior
VM can run.

Verified this bug has been fixed.
Test Information

Environment: qemu/KVM 2 nodes + 1 witness
Harvester Version: v1.4.0-dev-20240918
ui-source Option: Auto

Verify Steps

same as https://github.com/harvester/harvester/issues/5584#issuecomment-2092604751


Column order and visibility

Still in progress.
Done

Better context menu on the + button in the right corner of the table
Short cut to only show small table or all columns

TODO

[ ] Fixed order for columns (ID, RT, MZ, Height, Area, .... Shape, Feature: State, RT, MZ, Height, Area, .... )
[ ] Control visibility for all columns and sub columns (Spectral match:Compound, RTRange:min ...)

The stuff noone likes to do, thanks Robin!


Evdi 12.0.1 dosen’t work with kernel 5.18.14

ArchLinux
5.18.14
Cinnamon

Network and USB works but no display signal and can’t choose resulotion with evdi 11.0 works but can’t choose resolution over FullHD. It’s was possible before.

Same with me with the version 1.12.0 and kernel 5.18.14-arch1-1
Rollback to 1.11.0 fixes the issue.

@fs-evooq Hello, I have the same issue, how did you roll-back ? Did you compile and install from sources ? Thanks

git clone https://aur.archlinux.git/evdi.git
cd evdi
vim PKGBUILD
#edit version number 11.0.0 and hash sum ti ‘SKIP’
makepkg -si

@julian-poidevin To rollback the aur package installed with paru:
cd ~/.cache/paru/clone/evdi
git log
git checkout 4bcc74e6f3dd59fda2abd07fea1d990858fcaa55
makepkg -cirs
sudo rmmod evdi
sudo modprobe evdi

Thanks a lot guys !

Hi, recently released Evdi 1.12.0 is incompatible with the Displaylink driver 5.6, because of an API change. Hm, AUR maintainers should be more careful and wait for the binary driver.

Same problem here, also Arch Linux. Kernel 5.18.14, GNOME.

displaylink 5.6-1
evdi 1.12.0-1

Same problem on Kernel v5.10.131, rollback to v1.11.0 was needed.

git clone https://aur.archlinux.git/evdi.git

This address does not exist. The correct command would be: git clone https://aur.archlinux.org/evdi.git

I can confirm a rollback from evdi 1.12.0-1 to evdi 1.11.0-1 using the method described by @fs-evooq in their comment got my external monitor working again. Really appreciate the advice!

As details.md says, major version number should be increased when incompatible API changes occur, yet only minor version was increased. This means that v1.12 should have been released as v2.0 instead.

I'm experiencing graphical artifacts at the mouse position on both the screens
evdi 1.11.0-1
displaylink 5.6-1

I'm experiencing graphical artifacts at the mouse position on both the screens evdi 1.11.0-1 displaylink 5.6-1

@palexdev This is a known issue. See also https://www.youtube.com/watch?v=3ZGX-3dATW4&ab_channel=FixitKB!
The solution for me is to logout then login again and it resolves the issue.

I'm experiencing graphical artifacts at the mouse position on both the screens evdi 1.11.0-1 displaylink 5.6-1

@palexdev This is a known issue. See also https://www.youtube.com/watch?v=3ZGX-3dATW4&ab_channel=FixitKB!
The solution for me is to logout then login again and it resolves the issue.

Thank you very much, that solves the issue for me too
This is a temporary workaround, right? Every time I disconnect/connect the display I will have to do it again?

I'm experiencing graphical artifacts at the mouse position on both the screens evdi 1.11.0-1 displaylink 5.6-1

@palexdev This is a known issue. See also https://www.youtube.com/watch?v=3ZGX-3dATW4&ab_channel=FixitKB!
The solution for me is to logout then login again and it resolves the issue.

Thank you very much, that solves the issue for me too This is a temporary workaround, right? Every time I disconnect/connect the display I will have to do it again?

Yes I think. At least, that the case for me.

git clone https://aur.archlinux.git/evdi.git cd evdi vim PKGBUILD
#edit version number 11.0.0 and hash sum to ‘SKIP’ makepkg -si

Worked for me with following changes, HTH:

git clone https://aur.archlinux.org/evdi.git (note the archlinux.org part)
change version number to 1.11.0 (not 11.0.0)
change hash sum line to sha256sums=('SKIP') (attention, I don't know if this could be a security issue)

DisplayLink 5.6.1 has been released, and it's compatible with evdi 1.12.0. Source: changelog.
The DisplayLink AUR package is still at 5.6 at the time of writing. A self-bumped version works with evdi 1.12.0, for me at least.

Hi, Just upgraded to 5.19.3-arch1-1 and the displaylink service fails to load...
I am running evdi 1.12.0 from AUR and displaylink 5.6.1

For me evdi 1.11.0 and displaylink 5.6 still works

Hi am running 5.19.3-arch1-1 and fail when evdi is uploaded from 1.11.0 to 1.12.0, I needed to do a rollback

rollback to 1.11.0? What version of displaylink are you running?

Yes, you have to rollback to 1.11.0 (as described by https://github.com/DisplayLink/evdi/issues/373#issuecomment-1193698810) (just replace cd ~/.cache/paru/clone/evdi accordingly to your package manager) until the AUR package of displaylink is updated to the new 5.6.1 version (see https://github.com/DisplayLink/evdi/issues/373#issuecomment-1219468570)

rollback to 1.11.0? What version of displaylink are you running?

Yes, if you rollback evdi to 1.11.0 displaylink will works again

No, I think there is a pb with evdi. I can't add the module:
modprobe evdi
modprobe: ERROR: could not insert 'evdi': Invalid argument

dmesg | grep evdi
[ 6033.780665] failed to validate module [evdi] BTF: -22
[ 6035.177502] failed to validate module [evdi] BTF: -22
[ 6039.029240] failed to validate module [evdi] BTF: -22
[ 6044.290658] failed to validate module [evdi] BTF: -22
[ 6049.530255] failed to validate module [evdi] BTF: -22
[ 6054.789138] failed to validate module [evdi] BTF: -22
[ 6060.041652] failed to validate module [evdi] BTF: -22

No, I think there is a pb with evdi. I can't add the module:
modprobe evdi
modprobe: ERROR: could not insert 'evdi': Invalid argument

dmesg | grep evdi
[ 6033.780665] failed to validate module [evdi] BTF: -22
[ 6035.177502] failed to validate module [evdi] BTF: -22
[ 6039.029240] failed to validate module [evdi] BTF: -22
[ 6044.290658] failed to validate module [evdi] BTF: -22
[ 6049.530255] failed to validate module [evdi] BTF: -22
[ 6054.789138] failed to validate module [evdi] BTF: -22
[ 6060.041652] failed to validate module [evdi] BTF: -22

I only follow this procedure;
I uninstalled evdi
I uninstalled DisplayLink (I think maybe this is not necessary to do, but I did it)
I clone the git repository for evdi from aur page and once I got the PKG file I edited the pkgver to pkgver=1.11.0 and sha256sums to sha256sums=('SKIP'). Once I did that, I did makepkg -si procedure and reinstalled DisplayLink again and my docking worked again. I have a pluggable USB3.0, so that is working fine now
I based this procedure in the answer of @5472qaywsx and my displaylink version is displaylink 5.6-1

Yes thanks, I did try that but no luck.

@rbeucher I have the same issue as you, created a new issue: https://github.com/DisplayLink/evdi/issues/377

Thanks @Grisu118 . I hope we are gonna sort this out.

After a recent system upgrade, my external monitor yet again stayed black. I noticed that evdi was again on the incompatible 1.12 version - this despite me using displaylink 5.6-1.
After reverting back to the old 1.11 evdi version again, I adjusted my pacman config as to avoid evdi from being upgraded.
https://wiki.archlinux.org/title/Pacman#Skip_package_from_being_upgraded

@olof-nord Evdi 1.12 doesn't work with displaylink 5.6. The dependencies go like this (using Arch versioning):

displaylink 5.6-1 <--> evdi 1.11.0-1
displaylink 5.6.1-1 <--> evdi 1.12.0-1

As this ticket was pretty much Arch specific, and displaylink 5.6.1 and evdi 1.12.0 are out, I think this ticket can be closed.

It now works with 5.19.4.arch

I can install evdi 1.12.0 and displaylink 5.6.1 and is running but doesn’t recognise second screen. Evdi 1.11.0 with 5.6 still works

Hi, my system upgraded the kernel to the 6.0.2 version, then any of the solutions posted here helped me. I try to downgrade the kernel to the 5.19.3 version, but that produces an issue in my system and the graphical interface doesn't work. Then, I returned to the 6.0.2 kernel but the available version of evdi and displaylink don't work anymore to detect may docking to my second monitor.
I tried these step:

Downgrade the kernel to 5.19.3
uninstall evdi and displaylink
reboot my system. But the issues with the graphical interface happened, however, I was available to install evdi 1.11.0 and displaylink 5.6-1
Then I returned to 6.0.2 kernel, but to recover the graphical interface but evdi and displayllink don't work.

Does anybody know how to solve the issue using the kernel 6.0.2 version?

I am currently using the main git branch and it works fine for me

I am currently using the main git branch and it works fine for me

what kernel version are you using?

6.0.2