[Snyk] Upgrade @docusaurus/core from 2.4.0 to 2.4.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @docusaurus/core from 2.4.0 to 2.4.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2023-05-15.

Release notes

Package name: @docusaurus/core

2.4.1 - 2023-05-152.4.1 (2023-05-15)
🐛 Bug Fix

docusaurus-theme-classic, docusaurus-theme-common

#8971 fix(theme): fix collapsible sidebar behavior when prefers-reduced-motion (@ slorber)

docusaurus-theme-translations

#8933 fix(theme-translations): fix Turkish translation for aria label "Enter key" (@ LiberaTeMetuMortis)

docusaurus

#8908 fix(core): Correct yarn upgrade command for yarn 2.x (@ andrewnicols)

docusaurus-plugin-content-blog, docusaurus-theme-common, docusaurus-utils-common, docusaurus

#8909 fix(theme): add __ prefix to technical anchors, search crawlers (Algolia) should ignore them (@ slorber)

docusaurus-theme-common

#8906 fix(theme-common): fix collapsible component with prefers-reduced-motion (@ slorber)
#8873 fix(theme-common): fix confusing theme error message: bad sidebar id suggestions (@ slorber)

docusaurus-utils

#8874 fix(utils): handle Markdown links with spaces to route correctly (@ morsko1)

docusaurus-theme-classic, docusaurus-theme-translations

#8842 fix(theme-translations): remove redundant navigation text in aria label (@ tarunrajput)

create-docusaurus

#8831 fix(create): add missing await (@ SACHINnANYAKKARA)

💅 Polish

docusaurus-theme-classic

#8862 refactor(theme): expose copy, success and word-wrap icons as standalone components (@ armano2)

Committers: 7

Aleksandr Vladykin (@ morsko1)
Andrew Lyons (@ andrewnicols)
Armano (@ armano2)
MetuMortis (@ LiberaTeMetuMortis)
Sachin Nanayakkara (@ SACHINnANYAKKARA)
Sébastien Lorber (@ slorber)
Tarun Chauhan (@ tarunrajput)

2.4.0 - 2023-03-232.4.0 (2023-03-23)
Blog post: https://docusaurus.io/blog/releases/2.4/
🚀 New Feature

docusaurus-plugin-content-docs, docusaurus-theme-classic

#8236 feat(content-docs): add support for sidebar item category/link descriptions in generated index page (@ ZarakiKanzaki)

docusaurus-theme-classic

#8708 feat(theme): allow to load a Docusaurus page with theme from query-string: ?docusaurus-theme=dark (@ slorber)
#8616 feat(theme): add ability to translate navbar+footer logo alt text (@ Mysterious-Dev)

docusaurus-remark-plugin-npm2yarn

#8690 feat(npm-to-yarn): add support for PnPm and custom converters (@ armano2)

docusaurus

#8677 feat(core): add script env variables: NODE_ENV + BABEL_ENV + DOCUSAURUS_CURRENT_LOCALE (temporary i18n workaround) (@ slorber)

docusaurus-theme-classic, docusaurus-theme-common

#8674 feat(theme-classic): respect prefers-reduced-motion: reduce mediaquery, bump Infima to alpha.43 (@ slorber)

docusaurus-theme-translations

#8668 feat(theme-translations): add Hungarian theme translations (@ trueqap)
#8631 feat(theme-translations): add Norwegian (Bokmål) theme translation (@ dr0nn1)

docusaurus-theme-common

#8656 feat(theme-common): allow passing a string for details summary (@ pReya)

docusaurus-plugin-google-gtag

#8620 feat(gtag-plugin): gtag should support multiple tracking ids, notably for the UA => GA4 transition (@ slorber)

🐛 Bug Fix

docusaurus-theme-classic

#8803 fix(theme): codeblock buttons should be kept on the right when using RTL locale (@ Vishruta-Patil)
#8615 fix(theme): improve color toggle when using dark navbar (@ dewanshDT)
#8699 fix(theme-classic): fix tab focus bug in dropdown (#8697) (@ kagankan)

docusaurus-theme-classic, docusaurus-theme-common

#8801 fix(theme): allow tabs children to be falsy (@ Josh-Cena)

docusaurus-theme-common, docusaurus-theme-search-algolia

#8757 fix(search): search page should react to querystring changes + cleanup/refactor (@ slorber)

docusaurus

#8746 fix(core): baseUrl error banner link anchor case (@ slorber)

docusaurus-theme-translations

#8744 fix(theme-translations): fix wrong arabic words (tip/next) (@ Anasqx)

💅 Polish

create-docusaurus

#8712 polish(create-docusaurus): the starter template should use a navbar item "docSidebar" instead of "doc" (less fragile on updates) (@ biplavmz)

docusaurus-theme-classic, docusaurus-theme-common, docusaurus-utils-common, docusaurus

#8735 polish(theme): better error messages on navbar item rendering failures + ErrorCauseBoundary API (@ tannerdolby)

docusaurus-theme-classic, docusaurus-theme-common, docusaurus

#8736 polish(core): better styling for error screens (@ tannerdolby)

Committers: 14

Anas (@ Anasqx)
Armano (@ armano2)
Davide Donadio (@ ZarakiKanzaki)
Dewansh Thakur (@ dewanshDT)
Joshua Chen (@ Josh-Cena)
Kagan (@ kagankan)
Moritz Stückler (@ pReya)
Mysterious_Dev (@ Mysterious-Dev)
Petter Drønnen (@ dr0nn1)
Sébastien Lorber (@ slorber)
Tanner Dolby (@ tannerdolby)
TrueQAP (@ trueqap)
Vishruta Patil (@ Vishruta-Patil)
@ biplavmz

    from @docusaurus/core GitHub release notes

Commit messages

Package name: @docusaurus/core

60e657d v2.4.1
941f717 fix(theme): fix collapsible sidebar behavior when prefers-reduced-motion (#8971)
2a16f63 fix(theme-translations): fix Turkish translation for aria label "Enter key" (#8933)
704841f fix(core): Correct yarn upgrade command for yarn 2.x (#8908)
b345e9b fix(theme): add __ prefix to technical anchors, search crawlers (Algolia) should ignore them (#8909)
8346c23 fix(theme-common): fix collapsible component with prefers-reduced-motion (#8906)
aa49226 fix(theme-common): fix confusing theme error message: bad sidebar id suggestions (#8873)
6fae23b fix(utils): handle Markdown links with spaces to route correctly (#8874)
d20e9c4 refactor(theme): expose copy, success and word-wrap icons as standalone components (#8862)
74781b0 fix(theme-translations): remove redundant navigation text in aria label (#8842)
b6d5262 fix(create): add missing await (#8831)
4fb67ef chore: backport retro compatible commits for the Docusaurus v2.4 release (#8809)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

No longer needed.


Example in README doesn't type-check

Repro
import { createReducer } from 'typeful-redux'

interface TodoItem {
  task: string
  completed: boolean
}

// Create a new reducer with initial state [], then add three actions
const TodoReducer = createReducer([] as TodoItem[])('clear', s => [])('add', (s, newItem: TodoItem) => [...s, newItem])(
//                                                                            ^ error here: Parameter 's' implicitly has an 'any' type
  'toggle',
  (s: TodoItem[], index: number) => [...s.slice(0, i), { ...s[i], completed: !s[i].completed }, ...s.slice(i + 1)]
)

tsconfig
{
  "compilerOptions": {
    "module": "commonjs",
    "moduleResolution": "node",
    "strict": true,
    "noImplicitReturns": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "noFallthroughCasesInSwitch": true,
    "target": "es5",
    "forceConsistentCasingInFileNames": true
  }
}

Also in the last action there's a typo: index instead of i

There's another example which doesn't type-check (createReducer section)
const TodoReducer = createReducer([] as TodoItem[])
  .addSetter('clear', s => []) // error: Property 'addSetter' does not exist on type 'Reducer<TodoItem[], {}, {}>'
  .addHandler('add', (s, newItem: TodoItem) => [...s, newItem])
  .addHandler('toggle', (s, index: number) => [ // <= index instead of i?
    ...s.slice(0, i),
    { ...s[i], completed: !s[i].completed },
    ...s.slice(i + 1)
  ])

Thanks for the report - indeed I was a bit careless here. I'll fix these up.

I've updated the README, the issues should be fixed now. Thanks again for reporting them.
(if you have a good way to have the typechecker run over these files (a la literate Haskell) I'd be very interested).


Replacing DP Mosaic design language to Salt DS

As part of moving DP Mosaic design language to Salt DS, I'm categorising components that currently being used on DP Mosaic into 3parts.
1. Using Salt component : The component replaced to Salt component. Ex) Button, layout, icon, link, Tooltip
2. Mosaic specific component: The component designed for DP Mosaic using Salt DS.(Currently based on Mosaic Design language but will update it to Salt DS) Ex) Audio, video player, Accordion, callout, card, feature.. and so on
3. To be replaced to salt component: The component building in progress in Salt team. Currently using Mosaic component on the site, to be replaced to Salt component once it’s built. Ex) App header, Nav item, Tabs, List…
Our goal would be replace the DP Mosaic components to Salt DS components and keep Salt DS foundation styles include typography, color, and shadow.
 For the components that designed only specific for DP Mosaic, also will be based on Salt DS, there won’t be DP Mosaic specific styles or specs.

All the related information will be documented on this Figma file
Currently Type ramp update and component categorising in progress.

As part of this work, can we look at Link styles too please?

@joshwooding There is Link color style analysis on the Figma file. I'll tag you to the board. Currently this project is pending that fimga file hasn't update for a while but this Link style analysis could be helpful.


Support the "release" configuration when using dotnet

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

In the CLI with the dotnet sdk, when running pulumi up or another command, a dotnet build command is executed.
It’s always being built in debug mode (the default configuration).
It would be preferred to be able to run the dotnet build with the release configuration.
Affected area/feature

I would expect debug (or rather, default!) builds to be faster, and as Pulumi is rarely limited by the performance of the language executed, this might be an anti-pattern.
Were we to implement this, I'd recommend we benchmark using some of our large SDKs. My prior is that this would make deployments substantially slower with azure-native.

Hello, in my case providing support for the release configuration would be helpful in two aspects

If the #if DEBUG directive is present in our codebase, running Pulumi CLI will cause unexpected behaviors because often times when I am doing a new deployment on the production environment, I would expect the release configuration to be used for compilation and not the debug one. It doesn't feel right to give up on those directives just because the Pulumi CLI doesn't support release configuration.
If in the code we are referencing specific binaries in the Release folder, they will not get updated as expected during dotnet build and we might reference an outdated version of them. For instance, one way to deploy Azure Functions is to upload its binaries with the FileAsset class. We are currently taking the files in the Debug folder but it would have been preferable to take it in the Release folder as the compilation is more optimized.

Bonus : Code compiled in release mode runs faster than debug mode as the compilation makes a lot of optimizations

It’s always being built in debug mode (the default configuration).

Specifically it builds in the default configuration because we just don't pass any /c option.

It would be preferred to be able to run the dotnet build with the release configuration.

I'm fine with adding an option for this. Most sensible place I think would be the runtime options so you could write in your Pulumi.yaml:
runtime:
  name: dotnet
  options:
    configuration: Release

And we would simply pass the value given there to the /configuration flag of msbuild.

Hi @SineLung - have you measured this? Our .NET SDKs can be quite large, and the "extra compilation" options can actually make programs very slow.
We find that the most time consuming steps of the execution time of Pulumi programs are:

Downloading and installing dependencies (nuget for .NET, or setting up a venv, npm install, etc.)
Building or setting up the runtime
Provider execution time - that is, the time the Pulumi Engine and Provider plugins (pre-compiled) spend running, or typically, waiting for cloud service API calls to complete.

If these factors are removed, the language and whether it's compiled or interpreted, optimized or not, rarely make a difference. In fact, compiled languages can take much longer to start (step 2) in some circumstances.

If in the code we are referencing specific binaries in the Release folder, they will not get updated as expected during the execution of dotnet build by the Pulumi CLI and we might reference an outdated version of them. For instance, one way to deploy Azure Functions is to upload its binaries with the FileAsset class. I don't want to manually build in release mode from Visual Studio every time before running Pulumi CLI.

@Frassle should weigh in here, as I don't think I understand this. If you're building binaries manually, I don't think Pulumi is using them, that's not part of the deployment method that Pulumi expects.

I would go a step further - if we could run .NET programs directly without a build step (dotnet run --no-build), that might be even faster. @Frassle do we support that?

It’s always being built in debug mode (the default configuration).

Specifically it builds in the default configuration because we just don't pass any /c option.

It would be preferred to be able to run the dotnet build with the release configuration.

I'm fine with adding an option for this. Most sensible place I think would be the runtime options so you could write in your Pulumi.yaml:
runtime:
  name: dotnet
  options:
    configuration: Release

And we would simply pass the value given there to the /configuration flag of msbuild.

It would be perfect to have that option here !

Hi @SineLung - have you measured this? Our .NET SDKs can be quite large, and any steps to optimize the program can actually make Pulumi much slower.
For one of our Pulumi projects, a full rebuild in debug mode took 15 seconds.
In release mode it took 9.9 seconds.

I would go a step further - if we could run .NET programs directly without a build step (dotnet run --no-build), that might be even faster. @Frassle do we support that?

Not directly like that, but we do support the "binary" option to tell the plugin to directly run an executable rather than working through project files. You could use that to ensure you always ran the release binary but it would then be on the user to remember to rebuild when needed.


Is Bluetooth required?

Hi,
I'd love to use my Nimbus on Windows 10, and I followed all the instructions and at the end the Feeder says "Successfully initialized gamepad", but I can't get the vJoy monitor or any games to recognize the controller. I'm not using it via bluetooth, but instead plugged-in to my PC via lightning-to-USB. Is this the issue? Does it require bluetooth to work?
Thanks!
Jeff

Unfortunately this software will work only via bluetooth


[Bug] Uninformative TypeError using tsfeatures when series_length < 12

I'm trying to run this on a test series of length 11 and freq='D', and getting TypeError: 'float' object is not subscriptable.
Is this expected/unavoidable? Ideally it could be fixed even if some features must return NaN or similar. Otherwise there could be a more informative error, or just check if the series_length is too small and raise an exception. Here is some code that breaks when the series_length is 11, but works when it's 12.
import numpy as np
import pandas as pd
from tsfeatures import tsfeatures

periods = 11
ind = pd.date_range(start='2000-01-01', periods=periods, freq='D')
vals = np.random.rand(periods)

df = pd.DataFrame({'ds':ind, 'y':vals, 'unique_id':1})
print(f'Inferred freq: {pd.infer_freq(df.ds)}')
print(df.head())

tsfeatures(df)

Output >
Inferred freq: D
          ds         y  unique_id
0 2000-01-01  0.576768          1
1 2000-01-02  0.482616          1
2 2000-01-03  0.848193          1
3 2000-01-04  0.180783          1
4 2000-01-05  0.060860          1

---------------------------------------------------------------------------
RemoteTraceback                           Traceback (most recent call last)
RemoteTraceback:
"""
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 125, in worker
    result = (True, func(*args, **kwds))
  File<EMAIL_ADDRESS>line 51, in starmapstar
    return list(itertools.starmap(args[0], args[1]))
  File "/Users/loganduffy/Code/ts/notebooks/tsdl/lib/python3.9/site-packages/tsfeatures/tsfeatures.py", line 871, in _get_feats
    c_map = ChainMap(*[dict_feat for dict_feat in [func(ts, freq) for func in features]])
  File "/Users/loganduffy/Code/ts/notebooks/tsdl/lib/python3.9/site-packages/tsfeatures/tsfeatures.py", line 871, in <listcomp>
    c_map = ChainMap(*[dict_feat for dict_feat in [func(ts, freq) for func in features]])
  File "/Users/loganduffy/Code/ts/notebooks/tsdl/lib/python3.9/site-packages/tsfeatures/tsfeatures.py", line 539, in pacf_features
    pacf_5 = np.sum(pacfx[1:6] ** 2)
TypeError: 'float' object is not subscriptable
"""

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

TypeError                                 Traceback (most recent call last)
Input In [239], in <cell line: 13>()
     10 print(f'Inferred freq: {pd.infer_freq(df.ds)}')
     11 print(df.head())
---> 13 tsfeatures(df)

File ~/Code/ts/notebooks/tsdl/lib/python3.9/site-packages/tsfeatures/tsfeatures.py:916, in tsfeatures(ts, freq, features, dict_freqs, scale, threads)
    912 partial_get_feats = partial(_get_feats, freq=freq, scale=scale,
    913                             features=features, dict_freqs=dict_freqs)
    915 with Pool(threads) as pool:
--> 916     ts_features = pool.starmap(partial_get_feats, ts.groupby('unique_id'))
    918 ts_features = pd.concat(ts_features).rename_axis('unique_id')
    919 ts_features = ts_features.reset_index()

File /usr/local/Cellar/python@3.9/3.9.4/Frameworks/Python.framework/Versions/3.9/lib/python3.9/multiprocessing/pool.py:372, in Pool.starmap(self, func, iterable, chunksize)
    366 def starmap(self, func, iterable, chunksize=None):
    367     '''
    368     Like `map()` method but the elements of the `iterable` are expected to
    369     be iterables as well and will be unpacked as arguments. Hence
    370     `func` and (a, b) becomes func(a, b).
    371     '''
--> 372     return self._map_async(func, iterable, starmapstar, chunksize).get()

File /usr/local/Cellar/python@3.9/3.9.4/Frameworks/Python.framework/Versions/3.9/lib/python3.9/multiprocessing/pool.py:771, in ApplyResult.get(self, timeout)
    769     return self._value
    770 else:
--> 771     raise self._value

TypeError: 'float' object is not subscriptable

Hey @chillerobscuro! Thank you for reporting this.
I was able to reproduce the error. Let me dig into it.

Hey @FedericoGarza I know these things take time but any luck finding the root issue? If it's a straightforward fix I could open a PR

hey @chillerobscuro! We release a new version (0.4.0) that fixes the issue 🙌


[Service Bus] Remove the use of InternalReceiveMode

In the Service Bus package, the receive mode is represented via string literals "peekLock" and "receiveAndDelete".
Internally, these get mapped to enum InternalReceiveMode which does not add much value at the moment and can be refactored out in favor of the string literals themselves.
PRs are welcome to make this change.
Code pointers:

Set up dev env and run rush build
Open the sdk/servicebus/service-bus folder in your editor and start with the refactoring
Use rushx build in this folder to ensure the code builds successfully

Fixed with #11755
Thanks @mohsin-mehmood!


Use custom template to generate server code

I'm using graphql-maven-plugin to generate graphQL server code and I'm planning to do some changes to GraphQLDataFetchers. But to provide a custom template for DATA_FETCHER, the templated file should be in the classpath and so I have to implement another jar to add them.
Is there a better way to apply a custom template than implementing another jar?

There is currently no better way.
But I committed last week an enhancement about this. In the next release, you'll be able to put the custom template in the project that uses it (instead of another project or module, that produces a jar that your project will use).
I'm working on a last issue, before doing this release. So I think this next release will come next week-end.
Etienne

So, if you're in a hury, you can checkout and build the current code. The release version would then be local-SNAPSHOT.
Otherwise, just wait some days, and it will be ok.

@etienne-sf thanks for the update. I can test this locally and wait for the release.
This is really a great news 👍

@ruks
what are those changes.
You know, that you can have custom wiring and datafetchers now?
`@Component
@Primary
public class CustomGraphQLDataFetchers extends GraphQLDataFetchers {
@Autowired
protected AreaBDF batchloaderDataFetcherArea;
public DataFetcher<CompletableFuture> dataFetchersDelegateLocationMMAreaWithDataLoader() {
return dataFetchingEnvironment -> batchloaderDataFetcherArea.get(dataFetchingEnvironment);
}
`
and
`@Component
@Primary
public class CustomGraphQLWiring extends GraphQLWiring {
@Autowired
CustomGraphQLDataFetchers graphQLDataFetchers;
@Override
protected TypeRuntimeWiring.Builder addWiringForLocationMM(TypeRuntimeWiring.Builder typeWiring) {
typeWiring = super.addWiringForLocationMM(typeWiring);
  typeWiring.dataFetcher("area", graphQLDataFetchers.dataFetchersDelegateLocationMMAreaWithDataLoader());
   return typeWiring;

}
`

@mheidt I'm still on version 1.11. In my graphQL schema, all the operations are query type and I need to execute all of them async on the server-side. So I tried to return CompletableFuture<Item> DataFetcher. So I changed the template and was able to achieve my requirements.
I also noticed that this check #if (${dataFetcher.completableFuture}) in the velocity template. But when I check the code this was derived automatically based on the operation and there wasn't any global config to make all the operations async.
Do you have any suggestions?
Thanks in advance.

If it concerns all of your datafetcher, changing the template is a good idea.
In my case I needed aliasable batchloader oder batchloader that return a Long or String and not an object.
That's when I use CompletableFuture and the method I described above.

@mheidt thanks, yes I also thought the same, will use a custom template.
When I use the master, I got this error. Does anyone have an idea?
***************************
APPLICATION FAILED TO START
***************************

Description:

Field executor in com.graphql_java_generator.client.GraphQLConfiguration required a bean of type 'com.graphql_java_generator.client.QueryExecutor' that could not be found.

The injection point has the following annotations:
	- @org.springframework.beans.factory.annotation.Autowired(required=true)

The following candidates were found but could not be injected:
	- Bean method 'queryExecutor' in 'GraphQLAutoConfiguration' not loaded because auto-configuration 'GraphQLAutoConfiguration' was excluded

Action:

Consider revisiting the entries above or defining a bean of type 'com.graphql_java_generator.client.QueryExecutor' in your configuration.

Process finished with exit code 1

Note that i'm using the default generated GraphQLServerMain.

The above issue is sorted and tested with the customized template and it working perfectly. I will be waiting for the next release.

You can now check the 1.13 release

You can now check the 1.13 release

Upgraded to 1.13 and work as expected. Hence i'm closing this issue.
Thanks all for the help 👍


Devstudio info load from metainfo

test this

Codecov Report

Merging #658 into master will decrease coverage by 1.16%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #658      +/-   ##
==========================================
- Coverage   97.19%   96.02%   -1.17%
==========================================
  Files          29       28       -1
  Lines        2529     2544      +15
  Branches      215      204      -11
==========================================
- Hits         2458     2443      -15
- Misses         71      101      +30

Impacted Files
Coverage Δ

browser/pages/account/controller.js
82.55% <0%> (-13.88%)
:arrow_down:

browser/services/platform.js
90.16% <0%> (-9.84%)
:arrow_down:

browser/model/virtualbox.js
87.44% <0%> (-4.58%)
:arrow_down:

browser/model/helpers/util.js
98% <0%> (-2%)
:arrow_down:

browser/model/helpers/downloader.js
97.7% <0%> (-0.76%)
:arrow_down:

browser/model/cdk.js
99% <0%> (-0.05%)
:arrow_down:

browser/main.js
100% <0%> (ø)
:arrow_up:

browser/model/hyperv.js
100% <0%> (ø)
:arrow_up:

browser/pages/start/controller.js
100% <0%> (ø)
:arrow_up:

browser/directives/pathValidator.js
100% <0%> (ø)
:arrow_up:

... and 16 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 d6b8770...1c9390d. Read the comment docs.


after upgrade from vue2 to vue3, breakpoint in VSCode stops working if typescript is used in SFC

Version
3.2.19
Reproduction link
github.com
Steps to reproduce
You can bypass step 1 to 3 if you open project vue3-proj-02 from https://github.com/lydev/public-demo.git.

vue create .  Enable typescript and choose vue3 in the wizard.
Enable source map by creating vue.config.js:

module.exports = {
configureWebpack() {
return {
devtool: "source-map",
};
},
};

Create .vscode/launch.json:

{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"type": "chrome",
"request": "launch",
"name": "vuejs: chrome",
"url": "http://localhost:8080",
"webRoot": "${workspaceFolder}",
"breakOnLoad": true,
"sourceMapPathOverrides": {
"webpack:///./": "${webRoot}/"
},
"skipFiles": ["${workspaceFolder}/node_modules/**/*"]
}
]
}

Yarn serve;
Open project in VSCode. Open "src/components/HelloWorld.vue" and set a breakpoint at line "export default class HelloWorld extends Vue".
F5 start debugging.

What is expected?
Chrome launches, line 42 is hit in VSCode.
What is actually happening?
Line 9 is hit. That's incorrect.

This only happens in Vue3, but Vue2.
This only happens if you have "lang=ts" enabled in SFC.
I think the problem is when compiler moves the TS script to a new file, it simplely put the script at line 1. It doesn't respect the fact that

Someone wrote an article on this that offers a solution, albeit a very intricate one:
https://ckhconsulting.com/vue-typescript-debuggers/#correct-source-map
Note that it only works for Vue CLI 4, and it needs to be altered for Vue CLI 5. However, the altered version doesn't work when using <script setup lang="ts"> either.

To add to my previous comment, it seems using the script setup syntax also has a line offset issue. However, unlike the normal TS compilation problems, the offset seems to vary from component to component, making it unpredictable such that the solution I linked doesn't work. Even when I set the offset to test a single component, however, it still seems to jump to random spots after the initial setup() script has run (e.g. I had an onMounted() hook and a watch(), but each time the watch() was triggered it would jump to the onMounted() function a few lines down instead).

Struggling with the same thing. I have followed the above article and have succeeded for the most part, but when it comes to script setup, it behaves strangely.
If I create a new Vue CLI 5 + TS project and define the following template/script in my vue file:
<template>
<button @click="updatecount">{{ count }}</button>
</template>
<script setup lang="ts">
import { ref } from "vue";
let count = ref(0);

function updatecount() {
	count.value++;
	console.log("updated");
}
</script>

and place breakpoint on count.value++ line, the breakpoint gets hit as soon as I refresh the page, but not on actual click, even when the count is updated.


UTF-8 decode issue when crawling

I installed diskover to hopefully get some insight into a large-ish dataset on an old NetApp filer.
A short way into the crawl diskover stops with a traceback about failing to decode UTF-8:
2018-01-19 10:46:11,547 [INFO][diskover] Creating ES index
2018-01-19 10:46:11,796 [INFO][diskover] Adding disk space info to ES index
2018-01-19 10:46:11,804 [INFO][diskover] Starting crawl using 8 threads
Crawling: 100%|████████████████████| 5630/5643 [0h:00m:00s, 36.7 dir/s]Traceback (most recent call last):
  File "diskover.py", line 2699, in <module>
    worker_setup_crawl(path)
  File "diskover.py", line 1147, in worker_setup_crawl
    start_crawl(path, crawlbot)
  File "diskover.py", line 1083, in start_crawl
    for root, dirs, files in walk(path):
  File "/home/AD/johnb/diskover-venv/lib/python2.7/site-packages/scandir.py", line 654, in _walk
    for entry in walk(new_path, topdown, onerror, followlinks):
  File "/home/AD/johnb/diskover-venv/lib/python2.7/site-packages/scandir.py", line 654, in _walk
    for entry in walk(new_path, topdown, onerror, followlinks):
  File "/home/AD/johnb/diskover-venv/lib/python2.7/site-packages/scandir.py", line 654, in _walk
    for entry in walk(new_path, topdown, onerror, followlinks):
  File "/home/AD/johnb/diskover-venv/lib/python2.7/site-packages/scandir.py", line 654, in _walk
    for entry in walk(new_path, topdown, onerror, followlinks):
  File "/home/AD/johnb/diskover-venv/lib/python2.7/site-packages/scandir.py", line 654, in _walk
    for entry in walk(new_path, topdown, onerror, followlinks):
  File "/home/AD/johnb/diskover-venv/lib/python2.7/site-packages/scandir.py", line 654, in _walk
    for entry in walk(new_path, topdown, onerror, followlinks):
  File "/home/AD/johnb/diskover-venv/lib/python2.7/site-packages/scandir.py", line 603, in _walk
    entry = next(scandir_it)
  File "/home/AD/johnb/diskover-venv/lib64/python2.7/encodings/utf_8.py", line 16, in decode
    return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: 'utf8' codec can't decode byte 0x8a in position 69: invalid start byte

I'm guessing there are some filenames with some Latin-1 encoding, or maybe just errant bytes input by a user accidentally.

Duplicate of #21


Compositor does not support the input inhibitor protocol

Hyprland Version
hyprland 0.33.1-2  / hyprland-git 0.31.0.r7.a0b675ec-1
Bug or Regression?
Bug
Description
Hi, the input inhibitor protocol is not supported anymore now i cant use a lockscreen like swaylock it just will not work.
How to reproduce
just open a terminal type in swaylock you will see the following message :  swaylock
2023-12-08 14:41:24 - [main.c:1824] Compositor does not support the input inhibitor protocol, refusing to run insecurely
Crash reports, logs, images, videos
No response

Thanks did not no that !


[WIP] ENH: Allow asv continuous to use a branch not in JSON branches

Background / Motivation
For some projects it would be useful to be able to run asv continuous between a (commit hash on) standard master branch that can be listed in the JSON branches parameter (i.e., the branch the project mainly uses on github) and a (commit hash on) new feature branch from a given developer (in i.e., a github PR) from their new branch that is not included in the branches parameter of the JSON file.
If I'm not mistaken, this isn't currently possible if you want to check the performance between i.e., the tip of master and the most recent commit hash of the new feature branch not listed in the JSON file.
It might be possible to manually edit the JSON file for each new feature branch (add its name), but that seems rather awkward, right?
Implementation in this PR
I've just hacked something together to support the above functionality based on a few hours of looking at the asv source code, so there is almost certainly a far better way to do this, if there's even general interest in doing this at all.
If there might be interest in supporting this, I'm hoping that I can at least catalyze some criticism / feedback on doing this more appropriately based on this initial hack that seems to work in my early / crude tests.
I currently run a command as below using this 'new feature:'
asv continuous --bench GROReadBench 175aba4b 3e16993 -e --extrabranch 3e16993
Where the new extrabranch provides a commit hash from the new feature branch that is not listed in the JSON file (ok, even if you like this feature / idea, the API is almost certainly going to need to change).
Suggestions? Even if asv itself doesn't want to support this, one project I work on will likely want to maintain a fork that does because of the development workflow, so any suggestions are most welcome.

"asv continuous" can take two commit arguments, so if you know the
commit hashes --- or even branch names -- you should be able to compare
them. These commits do not need to be on any branch --- indeed the
branches listed in the JSON config should not play any role here. So
before commenting on your suggested change, can you clarify what goes
wrong? Why are changes necessary?

From the code changes, it appears you want to control the version
installed when benchmark discovery is run. This should not matter for
a correctly structured benchmark suite, as the no benchmark will be run
using this version.
.
However, the assumption in asv is that the benchmark suite must be
importable for any version you wish to benchmark against. This
requirement is largely not negotiable, so imports need be protected with
try-except blocks.

The main branch of the project (the only one the JSON file knows about) has two issues: setup.py is in the wrong place and it has no benchmark suite yet. The feature branch has a few commits -- one moves setup.py to the place asv expects and another adds the asv benchmark suite (JSON file, a simple benchmark to run, etc.) to the repo.
If I run asv continuous on two commits in the feature branch, asv will still apparently use a commit hash that precedes the feature branch even though I've only specified comparison of commit hashes in the feature branch; so asv continuous is perhaps discovering the benchmarks to run from a parent of the commit hashes (apparently the tip of the branch specified in the JSON file). I was trying to get benchmark discovery to happen from the first chronological commit hash provided to asv continuous because the 'master' branch is not compatible with asv yet.
However, if the JSON file is edited to contain the name of the feature branch instead of the master branch, it will use the feature branch that is compatible with asv and that contains the newly-included suite / benchmarks & everything works as expected. It doesn't seem to have complete isolation to the commit hashes that are provided to asv continuous (discovery happens beyond those provided commit hashes and 'master' was never intended for use with asv).
So while introduction of the asv suite to a project might seem like an extreme example, doesn't this issue also exist if you write a new benchmark that doesn't exist in master on a new feature branch? Can you discover a benchmark test that doesn't exist in master (introduced in feature branch with new name that is not listed in the JSON file), and run that?
So:
master branch commit hash a57381 -- doesn't have the new benchmark test
new feature branch commit hash a57382 -- has the new benchmark test written in
new feature branch commit hash a57383 -- makes a potential performance improvement to code being benchmarked
Then run asv continuous with JSON file only knowing about the master branch -- it seems master gets checked out for discovery and you can't run the benchmark introduced in the feature branch, right?
If my assumptions / descriptions above sound consistent with your expectations, perhaps this can simply be summarized as:

Changes (i.e., new tests) to the benchmarking suite should be merged to the 'discovery' / master branch (listed in JSON file) first.
After a new benchmark test has been merged to the 'discovery' / master branch, it is then safe to open a new feature branch that attempts to alter the target benchmark code and check performance there, because the discovery can safely happen from (the tip of) the JSON-listed master.

Perhaps supporting flexible test discovery (from i.e., a feature branch not listed in JSON file) is more confusing than it is worth & the above workflow is the intended approach anyway? If so, I guess this should be closed and I can perhaps focus more on the issue of retroactive testing when the repo had setup.py in the wrong place for years worth of commits (which has more to do with supporting a custom build / make process for asv as I understand it).

The issue does not affect adding new benchmarks --- asv always uses the
benchmark suite is present when running "asv continuous" etc.
.
To avoid confusion --- asv installs different versions of the project.
It checks out the specified repository to a temporary directory and
builds it, installing to a virtualenv. It never changes anything in the
current working tree.
.
The benchmark suite is completely separate object, and its versioning is
not managed by asv. The benchmark suite does not need to be in the
same repository as the project. It also does not even need to be version
controlled.
.
If you are working on a feature branch, you can check out the version of
the benchmark suite you want to use.
.
It is correct that the benchmark discovery will not work if the branches
defined in the JSON file are not installable. However, I'm not so sure
if this is a common occurrence that needs a workaround.

More flexible project installation would be welcome addition, e.g.
finding setup.py in subdirectory or using a non-Python build system.
.
The problem with this is how to do it so that it does not bring in a
large amount of complexity. One simple alternative could be to add
"shell_install", "shell_uninstall", and "shell_setup_env" options
containing command lines to execute, to be run instead of "pip install
.", "pip uninstall $PROJECT", and "python -mvirtualenv ..." for
installing/uninstalling/setting up the project. This then would be an
additional setup target in addition to Virtualenv and Conda.

Thanks for the clarifications.

It is correct that the benchmark discovery will not work if the branches defined in the JSON file are not installable.

Since the branch defined in the JSON has nothing to do with the commit hashes I'm feeding in to asv continuous, I guess I'm just not understanding why asv is even using it--why is asv trying to install a commit hash of the project that I don't want to benchmark during the "discovery" process?
If you can put the benchmarks outside of the project, why can't asv just read those & only touch the commit hashes that are specified?

asv wants to make sure some version of the project is installed in the virtualenv, when it imports the benchmark suite to crawl through the available tests. It should not matter what version gets installed, so it just picks something --- the versions specified in the branches are usually available, so it uses them by default.
It could be better design to make it so that the benchmark suite must be importable without the project being installed in the environment --- but this would be a backward compatibility break.

@pv Thanks, closing now that I understand what is going on with the third commit hash.


Add build tooling to ensure that we don't check in more hardcoded paths

We've fixed a number of hardcoded path related issues in the past, and we're still seeing them get checked in. This adds a verifier to ensure that we don't add new ones, while still having a way to have exceptions in cases where they are actually legitimate.
This has exceptions for the existing custom profile generator and test code, along with the scene system .unity files that are breaking arbitrary folder moves.

/azp run

/azp run

/azp run


dependency name is incorrect

implementation("com.mohamedrejeb.richeditor:richeditor-compose:1.0.0-beta03") mentioned in readme
and
https://mvnrepository.com/artifact/com.mohamedrejeb.richeditor/richeditor-compose-desktop
have different names.

It's correct, that one if just for desktop target. That howa kotlin multiplatform works, there's also richeditor-compose-android and same for other targets.
Check these
https://mvnrepository.com/artifact/com.mohamedrejeb.richeditor/richeditor-compose
https://mvnrepository.com/artifact/com.mohamedrejeb.richeditor

In Gradle you only need the one mentioned in readme richeditor-compose


MINOR: update kafka-topics.sh line command tool upgrade notes with removed option

As the title.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

related to #10457 . Please take a look. @showuon @ijuma


Fix duplicate minus one from RINGTOP

I think we already minus one in the macro definition,
so we dont't need to minus again in function fresh

If you remove the -1, the function creates wrong partitions for even sized numbers. If you leave the -1 there, it will create wrong partitions for uneven sized numbers. Thank you for finding a related bug! (see #89 ).


macOS installation error

pip install firepit failed with macOS 10.15 and Python 3.9. Lower Python version works.
Testing script: https://github.com/subbyte/github-action-test/blob/main/.github/workflows/firepit-install.yml
Error with Python 3.9: https://github.com/subbyte/github-action-test/runs/3078492170?check_suite_focus=true
Run python -m pip install --upgrade pip
Requirement already satisfied: pip in /Users/runner/hostedtoolcache/Python/3.9.6/x64/lib/python3.9/site-packages (21.1.3)
Requirement already satisfied: setuptools in /Users/runner/hostedtoolcache/Python/3.9.6/x64/lib/python3.9/site-packages (56.0.0)
Collecting setuptools
  Downloading setuptools-57.2.0-py3-none-any.whl (818 kB)
Installing collected packages: setuptools
  Attempting uninstall: setuptools
    Found existing installation: setuptools 56.0.0
    Uninstalling setuptools-56.0.0:
      Successfully uninstalled setuptools-56.0.0
Successfully installed setuptools-57.2.0
Collecting firepit
  Downloading firepit-1.0.14-py2.py3-none-any.whl (33 kB)
Collecting lark-parser
  Downloading lark-parser-0.11.3.tar.gz (229 kB)
Collecting ijson
  Downloading ijson-3.1.4-cp39-cp39-macosx_10_9_x86_64.whl (52 kB)
Collecting orjson==3.3.1
  Downloading orjson-3.3.1.tar.gz (655 kB)
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'done'
    Preparing wheel metadata: started
    Preparing wheel metadata: finished with status 'error'
    ERROR: Command errored out with exit status 1:
     command: /Users/runner/hostedtoolcache/Python/3.9.6/x64/bin/python /Users/runner/hostedtoolcache/Python/3.9.6/x64/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py prepare_metadata_for_build_wheel /var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/tmpoj1meudm
         cwd: /private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pip-install-b17aksbl/orjson_8be9df0c073140d4bd3b219ebd07017a
    Complete output (13 lines):
    💥 maturin failed
      Caused by: Cargo metadata failed. Do you have cargo in your PATH?
      Caused by: Error during execution of `cargo metadata`: error: failed to run `rustc` to learn about target-specific information

    Caused by:
      process didn't exit successfully: `rustc - --crate-name ___ --print=file-names -Z mutable-noalias --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg` (exit status: 1)
      --- stderr
      error: the option `Z` is only accepted on the nightly compiler

    Checking for Rust toolchain....
    Running `maturin pep517 write-dist-info --metadata-directory /private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pip-modern-metadata-3baxp3mn --interpreter /Users/runner/hostedtoolcache/Python/3.9.6/x64/bin/python --manylinux=off --strip=on`
    Error: Command '['maturin', 'pep517', 'write-dist-info', '--metadata-directory', '/private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pip-modern-metadata-3baxp3mn', '--interpreter', '/Users/runner/hostedtoolcache/Python/3.9.6/x64/bin/python', '--manylinux=off', '--strip=on']' returned non-zero exit status 1.
    ----------------------------------------
WARNING: Discarding https://files.pythonhosted.org/packages/23/c9/d4db467d5b5c91f5ff3ff3be5c731eb7fcc2b8b2c31540d5faeca794bf4d/orjson-3.3.1.tar.gz#sha256=149d6a2bc71514826979b9d053f3df0c2397a99e2b87213ba71605a1626d662c (from https://pypi.org/simple/orjson/) (requires-python:>=3.6). Command errored out with exit status 1: /Users/runner/hostedtoolcache/Python/3.9.6/x64/bin/python /Users/runner/hostedtoolcache/Python/3.9.6/x64/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py prepare_metadata_for_build_wheel /var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/tmpoj1meudm Check the logs for full command output.
Collecting firepit
  Downloading firepit-1.0.13-py2.py3-none-any.whl (33 kB)
  Downloading firepit-1.0.12-py2.py3-none-any.whl (33 kB)
  Downloading firepit-1.0.11-py2.py3-none-any.whl (33 kB)
  Downloading firepit-1.0.10-py2.py3-none-any.whl (33 kB)
  Downloading firepit-1.0.9-py2.py3-none-any.whl (33 kB)
  Downloading firepit-1.0.8-py2.py3-none-any.whl (32 kB)
  Downloading firepit-1.0.7-py2.py3-none-any.whl (32 kB)
  Downloading firepit-1.0.6-py2.py3-none-any.whl (32 kB)
  Downloading firepit-1.0.4-py2.py3-none-any.whl (30 kB)
  Downloading firepit-1.0.3-py2.py3-none-any.whl (30 kB)
  Downloading firepit-1.0.2-py2.py3-none-any.whl (30 kB)
  Downloading firepit-1.0.1-py2.py3-none-any.whl (30 kB)
  Downloading firepit-1.0.0-py2.py3-none-any.whl (30 kB)
ERROR: Cannot install firepit==1.0.0, firepit==1.0.1, firepit==1.0.10, firepit==1.0.11, firepit==1.0.12, firepit==1.0.13, firepit==1.0.14, firepit==1.0.2, firepit==1.0.3, firepit==1.0.4, firepit==1.0.6, firepit==1.0.7, firepit==1.0.8 and firepit==1.0.9 because these package versions have conflicting dependencies.

The conflict is caused by:
    firepit 1.0.14 depends on orjson==3.3.1
    firepit 1.0.13 depends on orjson==3.3.1
    firepit 1.0.12 depends on orjson==3.3.1
    firepit 1.0.11 depends on orjson==3.3.1
    firepit 1.0.10 depends on orjson==3.3.1
    firepit 1.0.9 depends on orjson==3.3.1
    firepit 1.0.8 depends on orjson==3.3.1
    firepit 1.0.7 depends on orjson==3.3.1
    firepit 1.0.6 depends on orjson==3.3.1
    firepit 1.0.4 depends on orjson==3.3.1
    firepit 1.0.3 depends on orjson==3.3.1
    firepit 1.0.2 depends on orjson==3.3.1
    firepit 1.0.1 depends on orjson==3.3.1
    firepit 1.0.0 depends on orjson==3.3.1

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies
Error: Process completed with exit code 1.

I am experiencing the same issue with OSX, tried python 3.7.8 and 3.9.4

Firepit seems to require orjson 3.3.1, which for some reason pip isn't able to install for me, but it will install 3.6.0 without issue.
pip install orjson
pip install --no-deps firepit

confirmed fix: https://github.com/subbyte/github-action-test/actions/runs/1090834139


Watch mode testing

Describe the feature you'd like:
Really happy to find this library. I am looking around for a user centric of testing a CLI of a test runner. I have read documentation a couple of times. It seems like most of the patterns covered look like this: user must see this prompt, be able to interact with it, and the library has assertions to check the output after interaction.
That’s all very useful. What I try to understand is the following: a test runner is watching the file system, user is changing files, and the runner is responding to that. In this case there are no prompts, but user still sees the output which was triggered by some activity not directly related with the CLI app.
Suggested implementation:
I wonder if the cli-testing-library is interested to cover this use case? What would be the best practises in this case?
Describe alternatives you've considered:
Own code. Own approach.
Teachability, Documentation, Adoption, Migration Strategy:
Users will be able to use the cli-testing-library to test watch mode of their apps.

I guess, that is not planned. Feel free to reopen.


Error with path attribute in IonItem

Hello,
Just found that specifying a path attribute for the ionItem component triggers the following error client-side:
Exception in template helper: TypeError: Cannot read property 'call' of undefined

Here is my code:
{{#ionItem path="iTrackStores" buttonRight=true class="item-icon-right"}}
  iTrack {{>ionIcon icon="ios-arrow-forward" class="assertive"}}
{{/ionItem}}

And the route definition:
Router.route 'iTrackStores',
  path: '/itrack/stores'

I've followed this example though.

Yeah, that should work.
@benstr any thoughts on this?

Yeah that should. I will look into this. In the meantime try calling route=, you do not need path since you are not including additional route params.
{{#ionItem route="iTrackStores" buttonRight=true class="item-icon-right"}}
  iTrack {{>ionIcon icon="ios-arrow-forward" class="assertive"}}
{{/ionItem}}

more info under Guide.md

Yes, I also tried url but I still have the same error. What I did for the moment is to use a simple href but that's not dynamic. :/
{{#ionItem href="/itrack/stores" buttonRight=true class="item-icon-right"}}
  iTrack {{>ionIcon icon="ios-arrow-forward" class="assertive"}}
{{/ionItem}}

It works fine for me. Can you verify the package version is version: "0.1.12"?
We were having this issue in version: "0.1.10" and since has been fixed.

Thank you, I don't know why but it was using 0.1.10.


Make CLI more graceful on handling environments with IPv6 disabled

Currently, for many of the CLI commands, if you run them in an environment where IPv6 is disabled, they will complain to stderr:
# cilium bpf nat list 1>/dev/null
Unable to open /sys/fs/bpf/tc/globals/cilium_snat_v6_external: Unable to get object /sys/fs/bpf/tc/globals/cilium_snat_v6_external: no such file or directory. Skipping.

This happens even if IPv6 is administratively disabled.
Ideally the commandline implementations like cilium bpf nat ... would detect this and silently ignore the missing IPv6 map.
Note that cilium bpf ... CLI tools in particular should be able to succeed if cilium-agent is unavailable. Regardless of the method for detecting that IPv6 is disabled, it should either be done reliably from state on the filesystem, or optionally by consulting the daemon (but if the daemon is unavailable, continue executing the command anyway).

@pchaigno I would like to take this up

All configuration parameters are defined in the Config.Map and map file is store at the location "tmp/cilium/config-map".
and the state of all the parameters can fetched from that directory files.
The state of IPv6 can be read from filesystem at "tmp/cilium/config-map/enable-ipv6",
Now we can check IPV6 status and NAT map, if IPv6 is disabled then we ignore the error msg from NAT map also.
If IPv6 enabled and NAT map not found then we should display the error msg.
Pls correct us if we are missing anything.

All configuration parameters are defined in the Config.Map and map file is store at the location "tmp/cilium/config-map".
and the state of all the parameters can fetched from that directory files.

I don't think we can assume the file will always be there. You can check the code of other cilium subcommands to see how to get that information from the cilium-agent daemon.

As per the issue description we want to do even if cilium-agent not running it should done reliably from the filesystem state,
Can you pls suggest any specific Cilium command to browse?

As per the issue description we want to do even if cilium-agent not running it should done reliably from the filesystem state,

Yes, it should try to reach the daemon and fallback to the filesystem otherwise.

Can you pls suggest any specific Cilium command to browse?

cilium status reaches the daemon for example.

Hi @pchaigno,
Can you assign this issue to me?
I want to work on this.
-Thanks

@pchaigno
As am looking into this issue for some time.
Can you assign this to me?
-Thanks


Error when building demo project with AOT

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

OS and Version?

Mac os Sierra (10.12.6)
Windows 7

Node / Npm or Yarn Version

» node --version
v7.7.1

» yo --version
2.0.0

» yarn --version
0.22.0

Targeted Angular version

Tested with both 2.x.x and 4.x.x
Repro steps.

» yo ngx-library

     _-----_     ╭──────────────────────────╮
    |       |    │  Welcome to the wondrous │
    |--(o)--|    │<EMAIL_ADDRESS>  │
   `---------´   │        generator!        │
    ( _´U`_ )    ╰──────────────────────────╯
    /___A___\   /
     |  ~  |
   __'.___.'__
 ´   `  |° ´ Y `

? (1/12) What is your name? You name
? (2/12) What is your email address<EMAIL_ADDRESS>? (3/12) What is your Github username? username
? (4/12) What is the name of your project? ngx-lib
? (5/12) What is the version of your project? 0.0.1
? (6/12) What is the description of your project? Angular library built with ❤ u
sing ngx-library yeoman generator.
? (7/12) What keywords best describe your project (comma-separated)? ng,angular,
library
? (8/12) What minimal version of Angular do you want to base your library upon?
4.X.X
? (9/12) What prefix would you like to use to name your components, directives,.
..? ngx-lib
? (10/12) What Angular modules will your library use? core, common, http, compil
er, platform-browser-dynamic, platform-browser
? (11/12) Do You want to use Greenkeepeer (to automatically keep your dependenci
es up-to-date)? No
? (12/12) Do You want to use Compodoc (to generate your Angular project document
ation)? No

[...]

» gulp build:demo

The log given by the failure.

[17:39:29] Using gulpfile /private/tmp/ngx-test/gulpfile.js
[17:39:29] Starting 'build:demo'...
[17:39:29] No 'node_modules' found in 'demo/'. Installing dependencies for you..
yarn install v0.22.0
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.84s.
yarn install v0.22.0
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
$ npm link ngx-lib
/private/tmp/ngx-test/demo/node_modules/ngx-lib -> /usr/local/lib/node_modules/ngx-lib -> /private/tmp/ngx-test/dist
Done in 288.09s.
Date: 2017-08-28T15:44:42.052Z                                                y Hash: ef70c651342119cfd414
Time: 19218ms
chunk {0} polyfills.b59a8422e26e64d12be4.bundle.js (polyfills) 63.9 kB {3} [initial] [rendered]
chunk {1} main.f4fab8807a794a7599a3.bundle.js (main) 61.7 kB {3} [initial] [rendered]
chunk {2} styles.8d8889034cdf8cb01f46.bundle.css (styles) 166 kB {3} [initial] [rendered]
chunk {3} inline.f80d2f9e96d89d576d7c.bundle.js (inline) 1.45 kB [entry] [rendered]

ERROR in Error encountered resolving symbol values statically. Could not resolve ngx-lib relative to /private/tmp/ngx-test/demo/src/app/app.module.ts., resolving symbol AppModule in /private/tmp/ngx-test/demo/src/app/app.module.ts, resolving symbol AppModule in /private/tmp/ngx-test/demo/src/app/app.module.ts, resolving symbol AppModule in /private/tmp/ngx-test/demo/src/app/app.module.ts
ERROR in ./src/main.ts
Module not found: Error: Can't resolve './$$_gendir/app/app.module.ngfactory' in '/private/tmp/ngx-test/demo/src'
resolve './$$_gendir/app/app.module.ngfactory' in '/private/tmp/ngx-test/demo/src'
  using description file: /private/tmp/ngx-test/demo/package.json (relative path: ./src)
    Field 'browser' doesn't contain a valid alias configuration
  after using description file: /private/tmp/ngx-test/demo/package.json (relative path: ./src)
    using description file: /private/tmp/ngx-test/demo/package.json (relative path: ./src/$$_gendir/app/app.module.ngfactory)
      no extension
        Field 'browser' doesn't contain a valid alias configuration
        /private/tmp/ngx-test/demo/src/$$_gendir/app/app.module.ngfactory doesn't exist
      .ts
        Field 'browser' doesn't contain a valid alias configuration
        /private/tmp/ngx-test/demo/src/$$_gendir/app/app.module.ngfactory.ts doesn't exist
      .js
        Field 'browser' doesn't contain a valid alias configuration
        /private/tmp/ngx-test/demo/src/$$_gendir/app/app.module.ngfactory.js doesn't exist
      as directory
        /private/tmp/ngx-test/demo/src/$$_gendir/app/app.module.ngfactory doesn't exist
[/private/tmp/ngx-test/demo/src/$$_gendir/app/app.module.ngfactory]
[/private/tmp/ngx-test/demo/src/$$_gendir/app/app.module.ngfactory.ts]
[/private/tmp/ngx-test/demo/src/$$_gendir/app/app.module.ngfactory.js]
[/private/tmp/ngx-test/demo/src/$$_gendir/app/app.module.ngfactory]
 @ ./src/main.ts 3:0-74
 @ multi ./src/main.ts
[17:44:42] ng command failed. See below for errors.

Desired functionality.

Be able to use library within project using AOT
Mention any other details that might be useful.

I have tested with both target version 2.X and 4.X and I have tested under Windows and Macos and I have the same error each time.

Tried to force to add js files and associted sourcemap and it worked.
I have created the PR #73 for that reason. Don't know if this solution is the good one but at least it is working :smiley:

Hi @sichida ,
Thank you for your time in reporting this and for the proposed  PR.
Unfortunately i can not accept the PR, as the issue you're having is due to the fact that
you didn't initially build your library (gulp build) before you tried to build the demo app (gulp build:demo).
The missing files you are adding in the PR, are already generated during the sub-task gulp rollup-bundle, included in gulp build.
To sum-up, the workflow to build the demo app (in standalone) should be:

yo ngx-library
make your changes in src/
gulp build
gulp build:demo

I will update docs to make that more clear.
So I'm closing this for now, feel free to re-open if you face the issue again.
Cheers!

Hi @sichida
My apologies, 'cause you were right about the bug in the generated gulpfile.js( only present when targeting angular 2.x.x though). The *.js files were indeed missing from distributed files...
I'll merge your PR after you update the code based on my review.
Also, please update the commit message of #73 as follow:
fix(demo): add js and associated sourcemap when targeting angular 2.x.x

Closes #72

This way, the commit will be integrated in the CHANGELOG file automagically!
Once done, you can force push on the same branch
Thanks!

Hi thank you for looking deeper into this.
I've just updated my pull-request with your instructions.
Regards,
Shoun

any plans for a release date for this issue?
not able to gulp build:demo

...
Field 'browser' doesn't contain a valid alias configuration
after using description file: C:\Projekte\Git\LotesCore\node-packages\lotes-datepicker\demo\package.json (relative path: ./src)
using description file: C:\Projekte\Git\LotesCore\node-packages\lotes-datepicker\demo\package.json (relative path: ./src/datepicker)
no extension
Field 'browser' doesn't contain a valid alias configuration
C:\Projekte\Git\LotesCore\node-packages\lotes-datepicker\demo\src\datepicker doesn't exist
.ts
Field 'browser' doesn't contain a valid alias configuration
C:\Projekte\Git\LotesCore\node-packages\lotes-datepicker\demo\src\datepicker.ts doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
C:\Projekte\Git\LotesCore\node-packages\lotes-datepicker\demo\src\datepicker.js doesn't exist
as directory


Failed to resolve: io.github.udhayarajan:VidSnapKit:4.0.3

Failed to resolve: io.github.udhayarajan:VidSnapKit:4.0.3
what can I do?

Make sure you have included
repositories {
    mavenCentral()
}

https://vimeo.com/783455041
I get a error
failed to get stream info: ERROR: [vimeo] 22439234: Unable to download webpage:  (caused by URLError(timeout('_ssl.c:1091: The handshake operation timed out')))
Thanks

@NewMacPro is your Failed to resolve: io.github.udhayarajan:VidSnapKit:4.0.3 resolved? Kindly post other issues in a separate issue thread.

I first just use your vidsnap.apk to try. https://github.com/Udhayarajan/VidSnap/releases
VidSnap.6.0.0.apk
I get an error

I'm marking it as closed because if you get the error io.github.udhayarajan: VidSnapKit:4.0.3 in VidSnap. It might be a gradle problem in that repo not in this.


Bug: Currently it is not possible to delete or update content with user progress data

Description
It needs to be possible to delete or update content with user progress data.
Acceptance criteria

[ ] bug fixed

@LG1401 Die Karte nehm ich noch in Angriff

I just wasted four hours on this, still don't understand why it happens. Every workaround other way of doing failed so for now I just gave up.

@LG1401 I will probably move it back to the backlog


[Util] pd.date_range implementation

date_rangereturns an index, and because we're not planing yet to have a distributed index object, I'm going to close this issue. There's nothing to implement for now.


Support file protocol

Support file protocol
example: file:///C:/xxx/yyy/zzz.html

Firefox don't allow file protocol for security reasons.
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/tabs/create


Fancy non-whitespace indentation

Now indentation can be an arbitrary string instead of just a number of spaces. This will allow comment nodes to place comment syntax in front of all of the lines they contain. We also now store doc node ids and marks for each individual level of indentation, which will allow for better cursor region highlighting.

Reviewed. See the changes I pushed. And three suggestions:

The Oracle's complicated append method isn't needed. It can just have append_text and append_newline, and they'll both be much simpler.
struct Line { segments: Vec<Segment> } should probably just be struct Line(Vec<Segment>)?
Block::new() should take an &IndentNode for effiency. Maybe? Though it isn't cloning, maybe it's already walking the Rcs without modifying their counts?

Each of these suggestions has a TODO, that should be deleted when it's done or wontfix-ed.


Linter panel doesn't hide when it's empty and "line" tab is selected

This is a minor UI nit.
If you're using the new "line" tab to show only current-line issues in the linter-panel, and you're on a line with no issues, but there are issues in the file, the panel doesn't hide.  It's just at its minimum height while empty.  The panel should hide in this case for consistent UI behavior.

Screenshot please?

Found it, working on a fix.


refactor: sdk improvements

This should probably have been squash-merged, or its history been cleaned up before a merge.


${vsInstallDir} or ${env.vsInstallDir}?

section "Build-in macros" lists 3 built-in macros for use in CppProperties.json, after test i find use ${vsInstallDir} in known keys such as includePath in CppProperties.json results in a warning text printed in vs' output window:
failed to evaluate environment variable "${vsInstallDir}"
if i use ${env.vsInstallDir} it works.
"includePath": [ "${env.vsInstallDir}" ]
so is it ${vsInstallDir} or ${env.vsInstallDir}?

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

ID: fed0104b-8ba3-0b4d-5765-29f20e842b5c
Version Independent ID: 7d5cc7af-86de-89cd-c86f-61f050ce7d1b
Content: CppProperties.json schema reference
Content Source: docs/build/cppproperties-schema-reference.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @corob-msft
Microsoft Alias: corob

after some consideration i believe despite the above fact that ${env.vsInstallDir} seems defined, it really should be ${vsInstallDir}, not ${env.vsInstallDir}, that is, defined in current ide rather than in system env. because under side by side installation, the environment variable vsInstallDir, even if set as array, is almost useless and in fact is not set. since there's no vsInstallDir env var, the item shouldn't be accessed through ${env.xxx}.
ps. the warning message given by output window is
failed to evaluate environment variable "${vsInstallDir}"
does this suggesting that it only evaluates ${env.xxx}?

@wangzimei in cppproperties.json the correct value is ${env.vsInstallDir}. Thanks for the feedback and the doc will be fixed soon.

thanks. i prefer ${vsInstallDir} though. unless some bin files already rely on the environment variable vsInstallDir, it's no point to add it to some exe's environment (when called by vs), being a macro in vs is sufficient.


Enable pedantic warnings

Good finds 👍

This is now ready for review.  I have tested also tested this with IBM and Intel compilers.


Add details on new suppression rule capabilities

It would be good to add documenation or the file name, hash and file path suppression rules that were added to the portal.
It's covered inthis blog post:
https://techcommunity.microsoft.com/t5/Windows-Defender-ATP/What-s-new-in-the-WDATP-Portal-June-6th-2017/ba-p/104099

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

ID: 578a2a0c-d8ec-de9f-0a2a-450d1087ecf7
Version Independent ID: 14b80f24-ed8e-9b63-d3f6-85852467b679
Content: Manage Windows Defender Advanced Threat Protection alerts
Content Source: windows/security/threat-protection/windows-defender-atp/manage-alerts-windows-defender-advanced-threat-protection.md
Product: w10
GitHub Login: @mjcaparas
Microsoft Alias: macapara

@officedocsbot assign @mypil

@markwoMSFT - From our understanding, the issue has been resolved but it may take a few days for the merged content to appear in the article. If you feel it hasn't been resolved, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

@officedocsbot close


New standard that mandates that parties redact any "confidential information"

E.g.:

Minor children names
Domestic violence survivor names

See: https://mobar.org/site/Lawyer_Resources/Remote_Public_Access_Redaction_Center/site/content/Lawyer-Resources/Remote_Public_Access_Redaction_Center.aspx
and https://casetext.com/rule/missouri-court-rules/missouri-rules-of-civil-procedure/rules-governing-civil-procedure-in-the-circuit-courts/rule-55-pleading-motions-and-hearings/rule-55025-redaction-requirements-effective-july-1-2023

Add information screen for this
Tell people not to include names of minors from case caption
Any of the describe the problem questions should include text for this

Do you have to redact parties if they are protected by a restraining order?

Here is the official redaction certificate: https://www.courts.mo.gov/file.jsp?id=195253


[Fix-8696][server]add comments for the repeated record on granting project

添加注释：在2.0.5中，授权项目时，重复记录BUG

Purpose of the pull request

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Is this nessessary?

Is this nessessary?

I think it is. The Bug has been fixed in dev branch. But it is not a UI BUG.

I think it is. The Bug has been fixed in dev branch. But it is not a UI BUG.

Since it has been fixed in dev branch. I think this comment is redundant.

Hi @yanmushi I agree with @SbloodyS, If this is already fix in dev, we should not add any comment on it

I think it is. The Bug has been fixed in dev branch. But it is not a UI BUG.

Since it has been fixed in dev branch. I think this comment is redundant.

Agree with @SbloodyS , and I will close this pr.
@yanmushi Thanks for your submitting and looking forward to your next pr.


✨ Mobile | Add SSW YouTube channel link to flyout

Hi team
As per Adam's email, we should include a link to SSW's YouTube channel in the flyout menu on the left.
Tasks

[ ] Investigate and discuss design
[ ] Add link to SSW's YouTube channel in the flyout

Thanks!

Should we also add links to other social media or just YouTube? 🤔


[11.x] Use config value for property default

Based on https://github.com/laravel/framework/pull/53734#issuecomment-2518193734

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions!


New business - changed mind

@Sheeri please write a description

To reproduce:

On the Vessel Information page of a boarding, under "Last Delivery Date", click "Business"
Then click "+ New Business"
You can then select "Business" again, and instead of getting the menu of businesses, you can type in a new business.
This is for the use case where a user realizes their choice WAS in the menu. Is there a way they can "reset" so they can see the menu? Maybe by clicking another field and coming back, or going to another page and coming back?

@Sheeri when you clicked on the "Business" edit view, it always opens the page in which we have existing businesses.
You can check by pulling the "development" branch :)

Yes, this works now, thanks!


Add support for bernard queue

Would you accept a PR for that?

I'd be interested, especially once multi-bus support is finished soon and provided Bernard has reached a stable enough state that it can be relied on going forward everywhere (I know it was still in flux a lot last year but haven't looked much since :smile: )

I am trying to put effort in bernard as well. As far as I can see some generic project decisions need to be made (code organization, some changes in the abstraction, etc), but hopefully we will get there soon.

Sounds good to me. I'm swamped right now because DomCode is this Friday ( :sweat_smile: ) but having had a year more experience now with this now, maybe it would be good to sit down on Hangouts or something in November and plot a course together, including the plugin as well. :smile:

Closing this one due to inactivity and maybe something to think about on a more fundamental level with Tactician2. :)

Yeah, nothing really happened during this one year on this front.
Is Tactician 2 coming?

I have some ideas in my notebook for it but I'm not sure there's a lot of demand.
My current idea is to mainly drop some features (get_class everywhere, no more ClassNameExtractors) and add a Router object to core. Bring PSR-11 container support to core. Stuff like that.
After a couple years of maintaining the different packages, I feel like there's way too many moving parts in all the packages for something that should be so darn simple. I want to see how the changes in this bundle are received and then look at bringing Tactician back to something really really tight.


sprintfix: 修复部分灰度问题

Codecov Report

Merging #1536 (db9e980) into _v2.3.x/feature_issue_1174 (5ae18e4) will decrease coverage by 0.05%.
The diff coverage is 37.20%.

@@                      Coverage Diff                       @@
##           _v2.3.x/feature_issue_1174    #1536      +/-   ##
==============================================================
- Coverage                       73.51%   73.46%   -0.05%
==============================================================
  Files                             385      385
  Lines                           25860    25893      +33
==============================================================
+ Hits                            19011    19023      +12
- Misses                           6849     6870      +21

Impacted Files
Coverage Δ

...eps/agent_adapter/config_context/context_helper.py
33.33% <ø> (ø)

apps/node_man/constants.py
96.33% <ø> (ø)

apps/node_man/serializers/job.py
77.18% <28.57%> (-8.78%)
:arrow_down:

apps/core/gray/handlers.py
44.85% <41.66%> (-0.19%)
:arrow_down:

...nents/collections/agent_new/choose_access_point.py
92.30% <100.00%> (+0.42%)
:arrow_up:

apps/node_man/handlers/validator.py
81.92% <100.00%> (ø)

... and 1 file with indirect coverage changes


impl causes RA to crash repeatedly overflowing stack

rust-analyzer version: rust-analyzer version: 5a6918f1c 2022-04-05 nightly
rustc version: rustc 1.60.0-beta.6 (7bccde197 2022-03-22)
relevant settings:
VS Codium 1.66.0 (using VS Code marketplace)
Preferences:
{
  "rust-analyzer.checkOnSave.command": "clippy",
  "rust-analyzer.highlighting.strings": true,
  "rust-analyzer.lens.methodReferences": true,
  "rust-analyzer.lens.references": true,
  "rust-analyzer.procMacro.enable": true,
  "rust-analyzer.server.extraEnv": {
    "CHALK_OVERFLOW_DEPTH": "3000",
    "CHALK_SOLVER_MAX_SIZE": "1500"
  },
  "rust-analyzer.cache.warmup": false,
  "rust-analyzer.experimental.procAttrMacros": false,
  "rust-analyzer.diagnostics.enableExperimental": false,
  "rust-analyzer.inlayHints.reborrowHints": true,
  "rust-analyzer.inlayHints.closureReturnTypeHints": true,
  "rust-analyzer.inlayHints.lifetimeElisionHints.useParameterNames": true,
  "rust-analyzer.inlayHints.lifetimeElisionHints": "always",
  "rust-analyzer.inlayHints.hideNamedConstructorHints": true,
  "rust-analyzer.checkOnSave.extraArgs": ["--no-deps"],
  "rust-analyzer.inlayHints.lifetimeElisionHints.enable": "skip_trivial"
}

This small code fragment causes RA to repeatedly crash until it disables itself:
[package]
name = "testaes"
version = "0.1.0"
edition = "2021"

[dependencies]
aes = "=0.8.1"

use aes::cipher::{generic_array::GenericArray, BlockCipher, KeySizeUser};

struct Testy<CI>(CI);

impl<CI: BlockCipher + KeySizeUser> Testy<CI> {
    pub fn new(_key: GenericArray<u8, <CI as KeySizeUser>::KeySize>) {}
}

fn main() {}

Example output from a crash:
thread '<unknown>' has overflowed its stack
fatal runtime error: stack overflow
[Error - 2:44:59 AM] The Rust Analyzer Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
[Error - 2:44:59 AM] Request textDocument/semanticTokens/full failed.
Error: Connection got disposed.
	at Object.dispose (/home/some_user/.vscode-oss/extensions/matklad.rust-analyzer-0.3.1003-linux-x64/out/main.js:32:4437)
	at Object.dispose (/home/some_user/.vscode-oss/extensions/matklad.rust-analyzer-0.3.1003-linux-x64/out/main.js:37:12019)
	at Rg.handleConnectionClosed (/home/some_user/.vscode-oss/extensions/matklad.rust-analyzer-0.3.1003-linux-x64/out/main.js:39:9883)
	at Rg.handleConnectionClosed (/home/some_user/.vscode-oss/extensions/matklad.rust-analyzer-0.3.1003-linux-x64/out/main.js:39:80621)
	at t (/home/some_user/.vscode-oss/extensions/matklad.rust-analyzer-0.3.1003-linux-x64/out/main.js:39:9591)
	at zd.invoke (/home/some_user/.vscode-oss/extensions/matklad.rust-analyzer-0.3.1003-linux-x64/out/main.js:5:14370)
	at Ri.fire (/home/some_user/.vscode-oss/extensions/matklad.rust-analyzer-0.3.1003-linux-x64/out/main.js:5:15139)
	at qt (/home/some_user/.vscode-oss/extensions/matklad.rust-analyzer-0.3.1003-linux-x64/out/main.js:6:6354)
	at zd.invoke (/home/some_user/.vscode-oss/extensions/matklad.rust-analyzer-0.3.1003-linux-x64/out/main.js:5:14370)
	at Ri.fire (/home/some_user/.vscode-oss/extensions/matklad.rust-analyzer-0.3.1003-linux-x64/out/main.js:5:15139)
	at ca.fireClose (/home/some_user/.vscode-oss/extensions/matklad.rust-analyzer-0.3.1003-linux-x64/out/main.js:5:17394)
	at Socket.<anonymous> (/home/some_user/.vscode-oss/extensions/matklad.rust-analyzer-0.3.1003-linux-x64/out/main.js:5:18924)
	at Socket.emit (node:events:402:35)
	at Pipe.<anonymous> (node:net:687:12)

Please let me know if any further details would be helpful.

This would usually be a Chalk overflow; it's probably not helpful to set CHALK_OVERFLOW_DEPTH that high.

Presumably a duplicate of #11370.

Thanks for the response. I disabled setting those environment variables and it just panics due to hitting the maximum depth.
Is there any other information that would be helpful?
Output (note - some repetition elided):
Panic context:
>
version: 134dbc610 2022-04-07 nightly
request: textDocument/semanticTokens/full/delta SemanticTokensDeltaParams {
    work_done_progress_params: WorkDoneProgressParams {
        work_done_token: None,
    },
    partial_result_params: PartialResultParams {
        partial_result_token: None,
    },
    text_document: TextDocumentIdentifier {
        uri: Url {
            scheme: "file",
            cannot_be_a_base: false,
            username: "",
            password: None,
            host: None,
            port: None,
            path: "/home/some_user/personal/testaes/src/main.rs",
            query: None,
            fragment: None,
        },
    },
    previous_result_id: "1",
}

thread '<unnamed>' panicked at 'overflow depth reached', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/chalk-recursive-0.81.0/src/fixed_point/stack.rs:51:13
stack backtrace:
   0: std::panicking::begin_panic
   1: chalk_recursive::fixed_point::RecursiveContext<K,V>::solve_goal
   2: chalk_recursive::fulfill::Fulfill<I,Solver>::prove
   3: chalk_recursive::fulfill::Fulfill<I,Solver>::solve
   4: chalk_recursive::solve::SolveIteration::solve_iteration
   5: chalk_recursive::fixed_point::RecursiveContext<K,V>::solve_goal
   6: chalk_recursive::fulfill::Fulfill<I,Solver>::prove
   7: chalk_recursive::fulfill::Fulfill<I,Solver>::solve
   8: chalk_recursive::solve::SolveIteration::solve_iteration
   9: chalk_recursive::fixed_point::RecursiveContext<K,V>::solve_goal
[...]
  88: chalk_recursive::solve::SolveIteration::solve_iteration
  89: chalk_recursive::fixed_point::RecursiveContext<K,V>::solve_goal
  90: chalk_recursive::fulfill::Fulfill<I,Solver>::prove
  91: chalk_recursive::fulfill::Fulfill<I,Solver>::solve
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[Error - 4:38:57 AM] Request textDocument/semanticTokens/full/delta failed.
  Message: server panicked: overflow depth reached
  Code: -32603
Panic context:
>
version: 134dbc610 2022-04-07 nightly
request: experimental/inlayHints InlayHintsParams {
    text_document: TextDocumentIdentifier {
        uri: Url {
            scheme: "file",
            cannot_be_a_base: false,
            username: "",
            password: None,
            host: None,
            port: None,
            path: "/home/some_user/personal/testaes/src/main.rs",
            query: None,
            fragment: None,
        },
    },
    range: Some(
        Range {
            start: Position {
                line: 0,
                character: 0,
            },
            end: Position {
                line: 9,
                character: 0,
            },
        },
    ),
}

Regarding #11370, setting CHALK_SOLVER_MAX_SIZE to 100 does seem to fix the problem. I guess I don't understand how those settings work, I'd think increasing the maximum size would make it more likely to work instead of less!

Having a lower max size makes it short-circuit the calculation earlier, so it doesn't get as deep. It still means the result might be wrong though.

This works for me with CHALK_OVERFLOW_DEPTH set to 350 or above. #12281 will probably bump it slightly, but at this point we probably can't avoid the need to tweak these at times.


Sample App improvements to showcase local Fhir resources

[ ] Show search results for Observations referred by a given Patient
[x] When no objects available from sync, import json bundle as local Fhir resources [Removed]
[ ] Use the sync button in the toolbar to actually sync results from external Fhir Resources
[x] Remove dependence on CqlLoader for firing the sync.
[x] Remove SamplePatients.kt if it's no longer needed.

Hi @jingtang10 please assign me this issue, I would like to work on it ASAP..

@jingtang10 I would like to work on this issue, can you please assign it to me?

@Anshul-9923 thanks for your interest. Will you be able to take a look at: https://github.com/google/android-fhir/issues/218
This issue is obsolete. I'm going to close this.

If you leave a comment in 218 I'll assign it to you. Thanks @Anshul-9923


Optimize docker registry response code

Use UNSUPPORTED response code instead of InternalServerError response code.
Ref: https://github.com/distribution/distribution/blob/main/docs/content/spec/api.md#errors-2

I do not think it is right, it seems to be an abuse of "UNSUPPORTED"

InternalServerError

Currently I think UNSUPPORTED will have detailed errors, at least better than InternalServerError

I do not think it is right, it seems to be an abuse of "UNSUPPORTED"

Currently I think UNSUPPORTED will have detailed errors, at least better than InternalServerError.

These errors shouldn't happen in daily usage, if it happens, end users still could do nothing.
 If you'd like to show errors to end users, it's better to clearly define what end users would see.

Even you do not care about server-side sensitive information, always returning "unsupported' is definitely an abuse to the docker status code.

you are reporting internal errors, it doesn't mean it is not supported
if you read docker's document, you could see that "unsupported" is not defined for every API response, if you'd like to strictly follow docker's document, many API should not respond "unsupported".

So I'd like to suggest do not spend more time on this, unless you have a clear plan to use it in some real cases.

I do not think it is right, it seems to be an abuse of "UNSUPPORTED"

Currently I think UNSUPPORTED will have detailed errors, at least better than InternalServerError.

These errors shouldn't happen in daily usage, if it happens, end users still could do nothing.
 If you'd like to show errors to end users, it's better to clearly define what end users would see.

But there was an error message returned before.

Maybe we should desensitize misinformation.

But there was an error message returned before.

No, they don't.

So I'd like to suggest do not spend more time on this, unless you have a clear plan to use it in some real cases.

Again, do not spend time on it unless you have a clear picture about it.


⚠ Bofrost.be has degraded performance

In b423886, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2702 ms

Resolved: Bofrost.be performance has improved in 56b35b2.


Transaction isolations for sql modules

Quill currently doesn't provide a way to define the isolation level of sql database transactions.

Is this still valid? Is there some workaround about this?
It looks like in my case I have the following scenario:

Begin transaction
Insert into table A
Insert into table B, where is used FK on table A
End transaction

@likern can you use ctx.transaction with the default isolation level for that or do you need a custom isolation level for the transaction?

I think, according to Postgres specification, transaction requires to have DEFERRABLE property. I'm not sure how transaction DEFERRABLE relates to DEFERRABLE in create table. I think they are the same.
My problem was solved by changing column constraints manually when creating table
model_id WITH OPTIONS
    REFERENCES models(id)
    DEFERRABLE
    INITIALLY DEFERRED

after that I'm able to use ctx.transaction.
But if these DEFERRABLE's have the same meaning it would be advisable to be able to change isolation level and other transaction characteristics without changing table options (for me I looks like the different options  to do the same)

I think I have a need for this. My use case is only making a reservation if there is still a space available. So within one transaction, I need to do some queries and run a bunch of logic on their results to determine availability, then if the checks pass, create the reservation (which may cause availability to change). With the default isolation level, each subsequent query can be affected by updates committed outside the transaction, so I don't think this is possible (although, perhaps restructuring the application or storing more data in the database could help). I think it's solvable either with serializable isolation level, so that if conditions change it would automatically fail (requiring me to retry), or else with repeatable read what I could do is, after creating the reservation check if it's overbooked (which could not be due to a concurrent transaction since I wouldn't see its effects) and if so fail.
In both modes I think the transaction can fail with specific errors that would be reason to retry, which means it has to be possible to check the error. I don't know if there's any way other than string matching.

Why not use ctx.run(infix"SET TRANSACTION ISOLATION LEVEL SERIALIZABLE".as[ctx.Action[_]]) ?

Are "per query" transaction isolation levels not coming at all in the foreseeable future? 😞
Should I use what scf37 suggested?


dns/dyndns: Implementend a basic PoC for Gandi LiveDNS

As requested in #1743  - this is a working version of the Gandi LiveDNS for OPNsense.
Works for me. Personally, I can not provide an API key for testing at the moment, but have tested it succesfully with my own Gandi API key.

Merged with godaddy changes...

LGTM! 👍

Hi @fichtner could you please clarify whats missing? I think its about the log log_error("DAN: ". $server);, isn`t it?  - it can be removed as it was a helper for me to understand some mechanics. I am removing it.

Sorry, for that. I have found the comments.

yep, please remove log_error() additions and add a last test date for the gandi livedns implementation in the header

yep, please remove log_error() additions and add a last test date for the gandi livedns implementation in the header

Done.

Merged, thank you ❤

❤


UX improvements.

Affects #22, #34.

Platform descriptions are now always displayed next to checkboxes rather than in a tooltip.

Descriptions were shortened to support this change.

Platforms are now sorted manually rather than alphabetically.

Core platforms are displayed at the top.
Secondary platforms are separated and displayed at the bottom.
Legacy Desktop platform was renamed to Lwjgl2 in code.

Removed the majority of application's tooltips (where permanent descriptions are now displayed instead). #34
Increased paddings in most tabs to improve readability.
Increased contrast in scroll panes, as the background color clashed with buttons and made it more difficult to read text.
READMEs are now generated by default. As they contain a lot of useful info for beginners, this should be something that users can opt-out of rather than the opposite.

Project templates README descriptions were slightly cleaned up and improved.
Templates of gdx-lml libraries now correctly link to @crashinvaders fork.

Project README was simplified. It had too much info for the beginners, and focused on advanced tool usage rather than what it can offer for the users.

The usage guide was moved to Guide.md.
Application screenshot is now pulled from the repo rather than Imgur.

I know I've said I'm done, but it kept bugging me. :)

By the way, I'm not sure if it's related to the viewport change, or if the UI skin was modified, but the UI of the old gdx-setup looks cleaner. Almost as if antialiasing is missing. Did you change the font?

Yes, the font changed as part of the HDPI changes -- this one is a larger image that is scaled down to fit the desired text size for the current window size (which could be quite large on a > 4K screen). The typeface is the same, but the rendering is different, and this does seem to change antialiasing.

I think also preferred subtler error highlights with a red border - the current red background is distracting and makes it more difficult to read the text.

I actually didn't intentionally change this -- this may have been a VisUI-related style setting that is different here than in the original gdx-setup. If you want to change it back to gdx-setup's theme in this PR, feel free; I don't really know how this part of the style works.
As for the palette, I haven't gotten any particular complaints about it, so presumably it's easy enough to read currently. I should maybe mention that @raeleus had started prototyping some "fancy UI" parts with transitions between storyboard-like parts of setup; I think if that ends up being possible to integrate into Liftoff (we might just keep the current tabs and have nicer transitions between them), then most palette changes could be done then.
The rest of the changes seem good, except I'm not sure if the Desktop to Lwjgl2 change affects the projects' Gradle commands, or the names of the modules. If it does, we need to update a bunch of docs, though the older "legacy" Desktop wasn't used very much in the first place.

Yes, the font changed as part of the HDPI changes -- this one is a larger image that is scaled down to fit the desired text size for the current window size (which could be quite large on a > 4K screen).

I see, that could cause the font to look worse with smaller resolutions. It does look better when scaled up.

I should maybe mention that @raeleus had started prototyping some "fancy UI" parts with transitions between storyboard-like parts of setup; I think if that ends up being possible to integrate into Liftoff (we might just keep the current tabs and have nicer transitions between them), then most palette changes could be done then.

I'll hold off with the interface changes then.

As for the palette, I haven't gotten any particular complaints about it, so presumably it's easy enough to read currently.

Just because users don't comment on it, doesn't mean there's nothing wrong. :) I don't think it's a good practice to use completely black backgrounds - original application is also guilty of this.

I'm not sure if the Desktop to Lwjgl2 change affects the projects' Gradle commands, or the names of the modules. If it does, we need to update a bunch of docs, though the older "legacy" Desktop wasn't used very much in the first place.

Yes, I've updated the documentation to reflect this. The legacy platform will now export as lwjgl2 to avoid confusion.


Modifying ETS table to a :set?

Hi,
Here https://github.com/ExHammer/hammer/blob/master/lib/hammer/backend/ets.ex#L138 we can see that the ETS table is an ordered_set. It seems to me that ordered_set are slower than set in most cases, except when doing traversal on some close keys. I can't see, however, where this property of ordered_set could be used. Is there a rational for using it?
Regards

Yup, good catch.
I'll try changing it and see how it goes, thanks for the input :)


fix(RHINENG-8314): Rename action buttons

Fixes https://issues.redhat.com/browse/RHINENG-8314.
A quick PR to slightly rename the button names. On the tasks list page, "Run tasks" -> "Select systems", in the select systems modal, "Execute task" -> "Run task".

Setting to draft to also clarify if we want to rename "Run task again"

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.57%.  Consider uploading reports for the commit 5db2999 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #169   +/-   ##
=======================================
  Coverage   81.57%   81.57%
=======================================
  Files          73       73
  Lines        1547     1547
  Branches      483      483
=======================================
  Hits         1262     1262
  Misses        248      248
  Partials       37       37

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix tox.ini lint target

tox fails due to being unable to reference the script module when
trying to run script/gen_requirements_all.py. Instead it needs to be
run as a module.
This was found while I was debugging #20197
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

@MartinHjelmare FYI

Thanks!


POSTFIX_RAW_CONFIG_ is only appending to main.cf the value of setting, but not the name

E.g., if I set the following: POSTFIX_RAW_CONFIG_MYNETWORKS=<IP_ADDRESS>/8 <IP_ADDRESS>/12
This is what's appended to end of main.cf:
## POSTFIX_RAW_CONFIG ##

<IP_ADDRESS>/8 <IP_ADDRESS>/12

Instead, I expected the following:
## POSTFIX_RAW_CONFIG ##

mynetworks = <IP_ADDRESS>/8 <IP_ADDRESS>/12

PR merged.


Use stages for travis builds

Codecov Report

Merging #424 (4b69326) into master (7ea8875) will decrease coverage by 0.15%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #424      +/-   ##
==========================================
- Coverage   96.39%   96.23%   -0.16%
==========================================
  Files          17       17
  Lines        1165     1117      -48
  Branches      132      132
==========================================
- Hits         1123     1075      -48
  Misses         18       18
  Partials       24       24

Impacted Files
Coverage Δ

pylxd/models/cluster.py
94.59% <0.00%> (-0.65%)
:arrow_down:

pylxd/models/profile.py
94.59% <0.00%> (-0.53%)
:arrow_down:

pylxd/models/instance.py
89.26% <0.00%> (-0.25%)
:arrow_down:

pylxd/models/operation.py
97.36% <0.00%> (-0.20%)
:arrow_down:

pylxd/models/image.py
99.08% <0.00%> (-0.04%)
:arrow_down:

pylxd/client.py
98.87% <0.00%> (-0.04%)
:arrow_down:

pylxd/managers.py
100.00% <0.00%> (ø)

pylxd/models/_model.py
100.00% <0.00%> (ø)

pylxd/models/network.py
100.00% <0.00%> (ø)

pylxd/models/certificate.py
100.00% <0.00%> (ø)

... and 1 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 7ea8875...4b69326. Read the comment docs.


Database locked

I'm getting an error about the database, it makes my server very laggy

Its literally describes what is the issue. Database is locked, check your sql file permissions or ask your host why resources can't write/read database files.


CAN support with bxcan crate

Ready to review
Example code not working yet.
https://github.com/stm32-rs/stm32f1xx-hal/pull/215#issuecomment-629356701 might be related

CI is read because https://github.com/embassy-rs/stm32-data/pull/74 is required

Merged! Could you bump the submodule to get green? Thanks :)


Support single array input for metric

Description
Fix #9865 by reshaping both label and pred.
Checklist
Essentials

[ ] Passed code style checking (make lint)
[X] Changes are complete (i.e. I finished coding on this PR)
[X] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

when labels and preds are NDArray instead of list NDArray, the for loop is superfluous

@piiswrong The for loop is fixed.

Hi, the community has passed to vote about associating the code changes with JIRA<EMAIL_ADDRESS>We have updated the guidelines for contributors in https://cwiki.apache.org/confluence/display/MXNET/Development+Process, please ensure that you have created a JIRA at https://issues.apache.org/jira/projects/MXNET/issues/ to describe your work in this pull request and include the JIRA title in your PR as [MXNET-xxxx] your title where MXNET-xxxx is the JIRA id
Thanks!


Remove apply constants from module build.gradle

This is a really small change, but I got burned by it while working on a different project. apply from: "../constants.gradle" doesn't work for some reason and is unused. Instead, the constants are applied in the root build.gradle.

LGTM.  There was a time when this worked (or appeared to work) but don't need it anymore.