Implementing abstract class via quick fix yields compile errors

Steps to Reproduce:

create a new file storageMainService2.ts
type export class StorageMainService2 extends AbstractStorageService {}
use quick fix to implement abstract methods

=> 🐛 you see compile errors from the result

Missing return type for last method.

@bpasero I can't reproduce using those steps.
Starting with:
import { AbstractStorageService } from 'vs/platform/storage/common/storage';

export class StorageMainService2 extends AbstractStorageService { }

Implement abstract results in :
import { IStorage } from 'vs/base/parts/storage/common/storage';
import { AbstractStorageService, StorageScope } from 'vs/platform/storage/common/storage';
import { IWorkspaceInitializationPayload } from 'vs/platform/workspaces/common/workspaces';

export class StorageMainService2 extends AbstractStorageService {
	protected getStorage(scope: StorageScope): IStorage | undefined {
		throw new Error('Method not implemented.');
	}
	protected getLogDetails(scope: StorageScope): string | undefined {
		throw new Error('Method not implemented.');
	}
	migrate(toWorkspace: IWorkspaceInitializationPayload): Promise<void> {
		throw new Error('Method not implemented.');
	}
}

Can you test this again and make sure you are on the latest TS version: 4.2.0-insiders-20210210

@mjbvz steps:

git co 1.53.0
open src/vs/platform/storage/node/storageService.ts
type export class Foo extends AbstractStorageService {} at the top
use quick fix to implement methods

Thanks. Opened https://github.com/microsoft/TypeScript/issues/42833 to track upstream


Changelog?

I'd like to know what breaking changes are being introduced in 2.0.0.

https://github.com/kimmobrunfeldt/chokidar-cli/releases/tag/2.0.0
Requires node.js v8.0.0 or newer as chokidar requires that as well as of v3+

I'm sorry, sometimes I'm checking the top menu for the releases page.


fix: trim URL parameters from file paths in coverage

I think PR #1841 tries to do the same, but in a different way? @ChpShy

Hello, I've tried https://github.com/vitest-dev/vitest/pull/1841, the problem is that it will indead remove the error, but also remove the .ts file from the coverage result list, keeping only the .vue file in the result
This is only a draft ATM, but the following seems to allow to keep both ts and vue file in the coverage result, with the creation of the HTML file ine the html reporter

Yes, you are right. This is not v0.21.1's bug, to be precise, this is v0.16.x's bug.In v0.16.0, testing.ts is skipped. And I  misunderstood it.

Coverage is now implemented in different packages. @OrestHk do you think the fix is needed, or we can close this PR?

Tried with vitest 0.24.1 and @vitest/coverage-c8 the problem is still here
I'll close this PR and look into @vitest/coverage-c8 to see what can be done !

@sheremet-va I openned a new PR https://github.com/vitest-dev/vitest/pull/2181, as this one is a bit stale and I add a bit of trouble with the lock file


Add .git folder into list of ignored poms

When doing the release on Jenkins we clone the releaser into .git folder. The problem with that is that scan that repo to update poms (and we fail the build cause we're using snapshots).
19:28:38 Caused by: java.lang.IllegalStateException: The file [/opt/jenkins/data/workspace/spring-cloud-commons-releaser/.git/releaser/spring-cloud-release-tools-spring/src/test/resources/projects/spring-cloud-release/spring-cloud-starter-parent/pom.xml] contains a BUILD-SNAPSHOT version for a non snapshot release in line number [23]
19:28:38
19:28:38 		<spring-cloud.version>Dalston.BUILD-SNAPSHOT</spring-cloud.version>

That's why it broke your build @spencergibb

Seems odd to clone something into .git.

In our projects we need to clone the releaser. We can clone it to some temp directory but then we won't see the code in the workspace. We can't clone it to target cause it gets deleted. We can't clone it to any other dir in the root of the project cause we are commiting and pushing stuff so we would clone the releaser code. .git folder is by default excluded from any version control that's why I clone it there.

Why is a temp directory not an option? I don't understand.

It's an option but I'd have to modify the Jenkins scripts and if something goes wrong with the releaser build I won't be able to see the sources.

But if it's crucial for you so that the code gets cloned to tmp then I can do it, although I don't see a lot of benefit out of it.

Just trying to understand. The other option is to git ignore something else in each project, correct?

no no... Let's take a look at this. We're trying to release Sleuth. What we do first is that we clone Sleuth's code.

workspace

Sleuth's .git
Sleuth's code

Now we need to clone and build the releaser. We need to store it somewhere. Currently we do it like this

workspace

Sleuth's .git

releaser's code

Sleuth's code

I put it there cause I don't want it to be with Sleuth's code. We could .gitignore a releaser folder in each project but it's pointless and we will still have the same problem cause the releaser's logic is executed form the project's root. So all the releaser's poms will get updated since they lay in a subfolder of our project...
So there are 2 options.

Ignore .git from pom updating
Clone the releaser to tmp, build it there, call the releaser's JAR from the project's root. Then my fix will get ignored cause no releaser's code is anywhere near the project's path

Ok. Another question ;-) why are we cloning and building releaser?

Cause we need the jar and we're not publishing anything else but snapshots? At some point, you've asked me why I'm overriding the 1.0.0.M1 constantly. So the answer was that it's not a snapshot and I can download the latest version. So here, instead of rebuilding the releaser I could just download the jar but since we're not doing it I'm cloning and building it each time from scratch.


[Build] Upgrade dependencies and add shrinkwrap

Our dependencies were out of date which caused peer dependency conflicts
in the transitive dependency graph. These conflicts prevented npm from
generating a npm-shrinkwrap.json. By upgrading dependencies, we can
now generate the npm-shrinkwrap.json. The shrinkwrap should help with
reliable tests and deployments.
Closes #172

Alright, it seems like NPM refuses to generate a shrinkwrap that works across operating systems. I'm going to close this and give up.


[GUI] Device: actuator attribute

When creating an actuator attribute, you can assign a value to the parameter.

But in the attribute history, only the value of the effective actuation is stored.

flowbroker_1                  | <19:54:50 15/01/2019> -- DEBUG: Received message: { value: <Buffer 7b 22 6d 65 74 61 64 61 74 61 22 3a 7b 22 64 65 76 69 63 65 69
64 22 3a 22 33 61 36 34 35 64 22 2c 22 74 65 6e 61 6e 74 22 3a 22 61 64 6d 69 6e 22 2c ... >,
flowbroker_1                  |   size: 99,
flowbroker_1                  |   key: null,
flowbroker_1                  |   topic: '9b2d7e1d-28f1-4ca3-9b62-7ae72512ca54',
flowbroker_1                  |   offset: 0,
flowbroker_1                  |   partition: 0,
flowbroker_1                  |   timestamp:<PHONE_NUMBER>593 }
flowbroker_1                  | <19:54:50 15/01/2019> -- DEBUG: Emitting new event message for subject device-data@admin
flowbroker_1                  | <19:54:50 15/01/2019> -- DEBUG: Queued event {"metadata":{"deviceid":"3a645d","tenant":"admin","timestamp":1547582088593},"attrs"
:{"bool":true}}
flowbroker_1                  | <19:54:50 15/01/2019> -- DEBUG: Pre-processing event {"metadata":{"deviceid":"3a645d","tenant":"admin","timestamp":1547582088593}
,"attrs":{"bool":true}}
flowbroker_1                  | <19:54:50 15/01/2019> -- DEBUG: [ingestor] got new device event: { metadata: { deviceid: '3a645d', tenant: 'admin', timestamp: 15
47582088593 },
flowbroker_1                  |   attrs: { bool: true } }
flowbroker_1                  | [redis] storing device info on cache . . .
flowbroker_1                  | [redis] . . . device info stored successfully
flowbroker_1                  | [executor] will handle node switch
flowbroker_1                  | [executor] hop (switch) result: [{"payload":{"bool":true,"serialNumber":"undefined"}}]
flowbroker_1                  | debug: Executing switch node...
flowbroker_1                  | debug: ... switch node was successfully executed.
flowbroker_1                  | [executor] will handle node change
flowbroker_1                  | debug: Executing change node...
flowbroker_1                  | debug: ... change node was successfully executed.
flowbroker_1                  | [executor] hop (change) result: [{"payload":{"bool":true,"serialNumber":"undefined"},"saida":{"mensagem":"ATUE"}}]
flowbroker_1                  | [executor] will handle node actuate
flowbroker_1                  | debug: Executing actuate node...
flowbroker_1                  | debug: Sending message...
flowbroker_1                  | debug: Message is: { meta: { deviceid: '3a645d', service: 'admin' },
flowbroker_1                  |   metadata: { tenant: 'admin' },
flowbroker_1                  |   event: 'configure',
flowbroker_1                  |   data: { attrs: { mensagem: 'ATUE' }, id: '3a645d' } }
flowbroker_1                  | object
flowbroker_1                  | will produce [object Object] to dojot.device-manager.device:admin
flowbroker_1                  | <19:54:50 15/01/2019> -- DEBUG: Trying to publish someting. Current producer topics are { 'dojot.device-manager.device':
flowbroker_1                  |    { admin: 'd88f83e5-0493-4b68-ade1-6553b536e45e',
flowbroker_1                  |      teste: '2ad9ae2f-aee3-45a2-9d75-649de301b8c0' },
flowbroker_1                  |   'device-data':
flowbroker_1                  |    { admin: '9b2d7e1d-28f1-4ca3-9b62-7ae72512ca54',
flowbroker_1                  |      teste: '86facf58-d4cd-4f4a-a300-34154b1a71ba' } }
flowbroker_1                  | debug: ... message was sent.
flowbroker_1                  | debug: ... actuate node was successfully executed.
flowbroker_1                  | [executor] hop (actuate) result: undefined
flowbroker_1                  | debug: Executing switch node...
flowbroker_1                  | debug: ... switch node was successfully executed.
flowbroker_1                  | [executor] will handle node switch
flowbroker_1                  | [executor] hop (switch) result: [null]
flowbroker_1                  | debug: Checking memory.
flowbroker_1                  | <19:54:52 15/01/2019> -- DEBUG: Received message: { value: <Buffer 7b 22 6d 65 74 61 22 3a 7b 22 64 65 76 69 63 65 69 64 22 3a 22
33 61 36 34 35 64 22 2c 22 73 65 72 76 69 63 65 22 3a 22 61 64 6d 69 6e 22 7d 2c 22 6d ... >,
flowbroker_1                  |   size: 149,
flowbroker_1                  |   key: null,
flowbroker_1                  |   topic: 'd88f83e5-0493-4b68-ade1-6553b536e45e',
flowbroker_1                  |   offset: 20,
flowbroker_1                  |   partition: 0,
flowbroker_1                  |   timestamp:<PHONE_NUMBER>496 }
flowbroker_1                  | <19:54:52 15/01/2019> -- DEBUG: Emitting new event message for subject dojot.device-manager.device@admin

Is the field required in the GUI?
Affected Version: 0.3.0-nightly_20181227

The actuator must have the same behavior as dynamic, it does not need a static value.
Is that correct, @raulnegreiros?

#966

Test OK.
The field for actuator data entry has been removed.

Note: This field may be required when the GUI allows action on a device.
Tested on Version: 62.3-20190603


fix(grammar): Handle quotes in multi-line strings

This doesn't fix ordian#128 but it makes it clearer where we are broken.
We might also get some batching string creation performance benefits.
This also makes it clear why ml_literal_string needs to allocate.  We
could possibly swap out a Cow so only \r\n users see a cost.

@ordian any combine tips to get the latest string grammar to work so we can pass all the string compliance tests?  It seems like its treating the first quote or two of delimiters as intermediate quotes, and then hitting end of input.  Instead it should attempt, fail, and fall back to the delimiter.  I tried sprinkling attempt around but it didn't seem to make a difference.

Oh, I haven't touched combine in a while, I would suggest asking a question here: https://gitter.im/Marwes/combine.

This PR started as attempting to fix the problem.  I've scaled that back to just mirroring the actual grammar.  This makes it clearer where the problem is and makes the scope for fixing this smaller


Remove vsphere provider dependency on api structs

Description of changes
It makes the code easier to follow, given the cluster spec is passed to most methods as an argument. This reduces api structs copies to one, removing ambiguity around which one contains the most updated data. It also avoids bugs where updates are only performed in one place but not the other.
If needed, a stateful version of the provider can be implemented by composing on top of this one.
This also fixes a bug where the controller rolled out new machines immediately after the cluster was created. It was detecting a change in machine configs due to a default not being applied in the cluster spec machine configs. I could have patched that alone and the change would have been smaller, but I decided to do this and avoid these kinds of bugs all together.
Testing

Unit tests
Upgrade e2e test run manually

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


check image os/arch on push

This change has the CLI checking image os and arch before pushing. If the os/arch is not linux/amd64, it warns the user there may be issues spawning and they should try rebuilding with the --platform=linux/amd64 flag. The user is then given the option to ignore the warning and push anyway.
Also, this PR fixes an issue where 404s were treated as AuthenticationErrors.
Screenshot:

Love it!


Remove TGI folder from Optimum Habana

What does this PR do?

TGI on Gaudi has been moved to https://github.com/huggingface/tgi-gaudi
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


"/create ponder " crashes multiplayer server when autocomplete attempts to return options

Describe the Bug
Just like #613, didn't know if I should reply to that or open another issue. Server crashes when trying to get the autocomplete options for the command /create ponder. Doesn't appear to occur in single player.
Reproduction Steps

On Multiplayer server, type /create ponder and hit space to get autocomplete's options
...

Expected Result
Command autocomplete returns a list of items to ponder, as in Single Player
Screenshots and Videos
No response
Crash Report or Log
https://pastebin.com/XRLgbwaB
https://pastebin.com/wevGJuHg
Operating System
Server on Linux, clients on Windows and macOS
Mod Version
0.5.0g
Minecraft Version
1.19.2
Other Mods
See crash log
Additional Context
No response

Happened on my server too

Same issue

fixed, but it doesn't actually suggest any completions. This matches forge.


Refactor spec/Spec.scala

convert map/flatMap into a for comprehension (c.f. https://stackoverflow.com/questions/12792595/how-to-convert-this-map-flatmap-into-a-for-comprehension-in-scala)
and fix indents

Codecov Report

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

@@          Coverage Diff           @@
##           master   #137    +/-   ##
======================================
  Coverage       0%     0%
======================================
  Files          27     27
  Lines        1783   1906   +123
  Branches        5      5
======================================
- Misses       1783   1906   +123

Impacted Files
Coverage Δ

core/src/main/scala/vegas/spec/Spec.scala
0% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@rgbkrk Thanks!


Error: Failed to install dependencies with npm. Please enter site directory and install dependencies with yarn or npm manually. Then run gridsome develop to start local development.

hi. i install gridsome, when i want to create project with below command:
gridsome create project
i recive this error:
Clone https://github.com/gridsome/gridsome-starter-default.git 1.74s
❯ Update project package.json 0.01s
❯ Install dependencies
• Installing dependencies with npm...
Error: Failed to install dependencies with npm. Please enter newf directory and install dependencies with yarn or npm manually. Then run gridsome develop to start local development.
Exit code 1
at ChildProcess.<anonymous> (/usr/local/lib/node_modules/@gridsome/cli/lib/commands/create.js:106:17)
at ChildProcess.emit (events.js:314:20)
at maybeClose (internal/child_process.js:1047:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)

arya@anonymous:~/tst$

what is problem?
ofcourse my OS is ubuntu!

solved it by my self.
use yarn instead npm.


Gradle updates

Aims to fix #265
Removes Retrolambda, updates Gradle, the plugin and the build tools, and updates the dependency management directives.
Also it has popped that there were some broken tests (my bet would be they weren't running before) so I fixed those, and had to add some dependencies here and there to address situations where modules would get dependencies transitively from other modules (this is no longer the case when using implementation from the 3.0 plugin).
Finally, a couple of the modules had a non-required dependency on the cache module only to reach the Preconditions class. I have removed this dependency as it is not really needed, but of course that means I have had to delete the couple of checks using the Preconditions class in those modules, so we should discuss how we want to address this.
PS: One more thing, I branched off of develop - was I supposed to do it from some other branch instead? (I'm thinking from develop this PR won't affect store-kotlin :disappointed:)

You can still use the java8 lambda feature when using
android {
  ...
  compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
  }
}

@digitalbuddha inline null checks with the same functionality as before cause PMD to complain. What approach would you like to solve that?
Also, what about the base branch?

Base it off rx2 Pls. Develop is Deprecated and needs to be deleted. As for the Pmd, suppress the violation. I'll find a cleaner fix later.

Thanks for the fantastic contribution!

A pleasure, looking forward to the next one :)


feat: Improve search bar suggestions

All subcategory are now displayed in the search bar suggestions. Also, we don't need to keep two lists of subcategories in different places anymore.

Fixes Issue
Closes #1746

Changes proposed

Screenshots

Note to reviewers
I had a hard time deciding if I should open this PR. While the commit message doesn't relate to the issue, I found out this is the solution while working on the issue. If you check the subcategories we have, you'll notice that some subcategories have & like Themes & Template while some have / like CI/CD. We even have C#😅.
So to avoid having a series of if statements while providing:

complete suggestions
correct URL

I thought it's better we derive the suggestions from the actual list(sidebarData) we have.
This helps:

to maintain one list
no need to think about what the URL should look like since we will be getting the URL from the suggestion itself.

Hi @Olaleye-Blessing! :) Can you post a screenshot of your proposed changes in the "Screenshot" section? It'll make it easier for the maintainers to review your contributions.

Hi @Olaleye-Blessing! :) Can you post a screenshot of your proposed changes in the "Screenshot" section? It'll make it easier for the maintainers to review your contributions.

Done.

@CBID2
You can see the issue here: https://jam.dev/c/05715bdb-fa75-4af0-a98f-fb020f3f643c
I will check this properly, in case there is bugs. It seems to be resolved from deployment.

@CBID2
You can see the issue here: https://jam.dev/c/05715bdb-fa75-4af0-a98f-fb020f3f643c
I will check this properly, in case there is bugs. It seems to be resolved from deployment.

Ahh thanks @Anmol-Baranwal

Congratulations @Olaleye-Blessing! You just made your first contribution! 🥳 It was wonderful working with you! 😄 If you want to stay updated on LinksHub, join our Discord community! :) We'd love to have you! :)


Implement or fix tuning of spatial smooting in spatialDGMM

As far as I remember, in older versions of spatialDGMM, the r parameter could be used to increase or decrease the amount of spatial smoothing (higher r values gave smoother segments). This was a very useful feature. In the current version, the segmentation is almost identical for different values of r.
An example to reproduce the issue:

set.seed(2020)
mse <- simulateImage(preset=3, dim=c(30,30), npeaks=9,
                     peakheight=c(3,6,9), centroided=TRUE, from=495, to=505)
peaks <- mz(metadata(mse)$design$featureData)
peak_IDs <- sapply(peaks, function(x) which.min(abs(x-mse@featureData$mz)))
for(r in c(1,2,5,10,15)) {
  gmm <- spatialDGMM(mse, r=r, k=4, weights="adaptive")
  show(image(gmm, i=peak_IDs))
}

The segments produced for these five values of r are nearly identical, only individual pixels change between them. In particular, even for r=15 many segments are very rugged.
My session info:
> sessionInfo()
R version 4.4.1 (2024-06-14)
Platform: x86_64-pc-linux-gnu
Running under: Ubuntu 22.04.5 LTS

Matrix products: default
BLAS:   /home/mciach/Programs/R/4.4.1/lib/libRblas.so
LAPACK: /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3.10.0

locale:
 [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C               LC_TIME=pl_PL.UTF-8
 [4] LC_COLLATE=en_US.UTF-8     LC_MONETARY=pl_PL.UTF-8    LC_MESSAGES=en_US.UTF-8
 [7] LC_PAPER=pl_PL.UTF-8       LC_NAME=C                  LC_ADDRESS=C
[10] LC_TELEPHONE=C             LC_MEASUREMENT=pl_PL.UTF-8 LC_IDENTIFICATION=C

time zone: Europe/Warsaw
tzcode source: system (glibc)

attached base packages:
[1] stats4    stats     graphics  grDevices utils     datasets  methods   base

other attached packages:
[1] Cardinal_3.6.5      S4Vectors_0.42.1    BiocParallel_1.38.0 BiocGenerics_0.50.0
[5] ProtGenerics_1.36.0

loaded via a namespace (and not attached):
 [1] nlme_3.1-166       cli_3.6.3          knitr_1.48         rlang_1.1.4
 [5] xfun_0.48          DBI_1.2.3          tiff_0.1-12        png_0.1-8
 [9] RCurl_1.98-1.16    htmltools_<IP_ADDRESS>  ontologyIndex_2.12 Biobase_2.64.0
[13] locfit_1.5-9.10    rmarkdown_2.28     grid_4.4.1         evaluate_1.0.1
[17] abind_1.4-8        bitops_1.0-9       fastmap_1.2.0      yaml_2.3.10
[21] compiler_4.4.1     codetools_0.2-20   CardinalIO_1.2.1   irlba_<IP_ADDRESS>
[25] htmlwidgets_1.6.4  fftwtools_0.9-11   EBImage_4.46.0     lattice_0.22-6
[29] digest_0.6.37      matter_2.6.3       parallel_4.4.1     Matrix_1.7-1
[33] tools_4.4.1        jpeg_0.1-10        biglm_0.9-3

The spatial smoothing itself has not changed. What has changed however, is the optimization process, which may be affecting what you're seeing.
Since Cardinal 3.6 (and matter 2.6), the underlying spatialDGMM algorithm exits early if the log-likelihood decreases during the optimization. In addition, the updated algorithm will more aggressively constrain parameters to valid values (e.g., make sure sigma, alpha, and beta are non-negative, and mu is within the range of the actual image intensities.
It's possible the early exiting from the algorithm is being too conservative. We can investigate this further.


+Viper instances for each profileBuilder command.

Fixes #1060

I assume everything works the same, this just cleans up some cruft yes?

@jhendrixMSFT says:
I assume everything works the same, this just cleans up some cruft yes?

Yep! There were actually some bugs I ran into the with the cruft that this fixes too.


Commands don't work via service principal

We should have a note on each command in this section to explain its not possible to run them via a service princiapl

Docs Build status updates of commit f3e203d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azureadps-2.0/AzureAD/Get-AzureADApplicationProxyApplication.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit f3e203d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azureadps-2.0/AzureAD/Get-AzureADApplicationProxyApplication.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@domooney
Per the read me file:
Please be aware that if you have any updates to automatically generated reference content, you should create an issue and not a PR. The issue will then be created into a bug and triaged accordingly. We do this because the reference content must mirror the *dll-help.xml file and subsequent updates to the reference content may overwrite any changes made through the repo. Capturing it in the source code ensures that this does not occur. Any PR with changes to automatically generated reference content will be closed.
Automatically generated reference content is any of the content under this Reference node, such as Get-AzureADUser
This only applies to reference content and not conceptual content. Pull requests for changes to conceptual content are accepted and encouraged. An example of the conceptual content is the Overview or a scenario such as importing data.
Thank you!
Bill

@domooney
Per the read me file:
Please be aware that if you have any updates to automatically generated reference content, you should create an issue and not a PR. The issue will then be created into a bug and triaged accordingly. We do this because the reference content must mirror the *dll-help.xml file and subsequent updates to the reference content may overwrite any changes made through the repo. Capturing it in the source code ensures that this does not occur. Any PR with changes to automatically generated reference content will be closed.
Automatically generated reference content is any of the content under this Reference node, such as Get-AzureADUser
This only applies to reference content and not conceptual content. Pull requests for changes to conceptual content are accepted and encouraged. An example of the conceptual content is the Overview or a scenario such as importing data.
Thank you!
Bill


Add dashboard to MyServices link

[ ] Make each of the numbers in the dashboard clickable - on mouse hover, it must clearly visible that they are clickable.
[ ] On click - the page must be directed to MyServices component and the URL must be updated to "serviceState=xxxx" with the corresponding state updated.
[ ] Table must be filtered and the filtered value must be selected in the drop down.

I‘ll take this


Support remove package version

This is a feature request.
Please add --remove flag.

This is not a feature I personally need, so I'm not stoked about the idea. If someone wants to work on it though, pull requests are welcome.
Instead of a --remove flag, I'd prefer a subcommand such as s3pypi remove {package} {version}.
In the meantime, if you want to remove a package, it would suffice to edit the index.html and remove the archive from S3.

I agree about the subcommand.
Editing the index.html is much more complex than having the subcommand...


Restore generation of XML documentation files

Types of changes

[x] Bugfix
[ ] Enhancement (new and/or improved behavior)
[ ] Refactoring (no functional changes)
[x] Code style update (no functional changes)
[x] Dependencies added, updated, or removed
[ ] Build related changes
[ ] Repository infrastructure changes (e.g. changes to issue / PR templates)
[ ] CI related changes
[ ] Documentation update
[ ] Other (please describe below)

Proposed changes / fixed issues
There is no Cecil.XmlDocNames.xml file in the NuGet package for version 1,2,1. This PR fixes it by:

re-enabling the generation of XML documentation;
updating Buildvana SDK to version 1.0.0-alpha.14, as alpha.12 had an issue that prevented the generation of XML documentation at all.

Checklist

[x] My contribution is my original work
[ ] My contribution, or part of it, comes from projects with an MIT-compatible license AND I have updated the THIRD-PARTY-NOTICES file accordingly
[ ] I have added and/or updated related documentation (if applicable)
[x] I have updated the "Unreleased changes" section in CHANGELOG.md according to the modifications I made

Codecov Report

Merging #39 (9075c30) into main (0678e91) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #39   +/-   ##
=======================================
  Coverage   65.42%   65.42%
=======================================
  Files           3        3
  Lines         107      107
  Branches       22       22
=======================================
  Hits           70       70
  Misses         26       26
  Partials       11       11

Impacted Files
Coverage Δ

src/Cecil.XmlDocNames/MemberReferenceExtensions.cs
0.00% <ø> (ø)

...Cecil.XmlDocNames/StringBuilderExtensions-Cecil.cs
69.23% <ø> (ø)

...ecil.XmlDocNames/StringBuilderExtensions-common.cs
53.84% <ø> (ø)

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 0678e91...9075c30. Read the comment docs.


⚠ ClamAV has degraded performance

In 7cc71dc, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 557 ms

Resolved: ClamAV performance has improved in 4da0d3f.


No delete options in system tray for stopped containers

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

The most common menu bar action for stopped containers is to start them. Moving their actions to a submenu would make it less convenient, so no plans to add more actions.


Kafka group.id to manage the number of workers Bytewax Docker

Bug Description
I am building a containerized application of Bytewax and Kafka.
I am expecting to manage the parallelism with the group.id, the topic has a partition of 10, so I can have 10 replicas of the worker.

from bytewax import operators as op
from bytewax.connectors.kafka import operators as kop
from bytewax.connectors.stdio import StdOutSink
from bytewax.dataflow import Dataflow

STREAM_BROKER = "kafka-bootstrap:9092"
TOPIC = "my-topic"
GROUP_ID = "A"

def get_flow():
    flow = Dataflow("processor-kafka")
    inp = kop.input("in", flow, brokers=[STREAM_BROKER], topics=[TOPIC], add_config={"group.id": GROUP_ID})
    op.output("out", inp.oks, StdOutSink())
    return flow

I was expecting to see different result by worker but all return the same value (meaning that they are not using consumer group
tracking the value I found this message:
%4|1705620172.932|CONFWARN|rdkafka#producer-1| [thrd:app]: Configuration property group.id is a consumer property and will be ignored by this producer instance

If I am setting up a input (consumer) Why I am receiving this messages. Is this the right approach to use bytewax with Kafka? Inst the kop.input a consumer?
Python version (python -V)
Python 3.11
Bytewax version (pip list | grep bytewax)
bytewax 18,1
Operating System version (uname -morp)
FROM bytewax/bytewax:0.18.1-python3.11
Relevant log output
%4|1705620172.932|CONFWARN|rdkafka#producer-1| [thrd:app]: Configuration property group.id is a consumer property and will be ignored by this producer instance

Steps to Reproduce

Create a kafka Cluster
Run docker-compose with Bytewax docker image --scale=3
lookup for the logs
(To reproduce exactly the problem we will have to setup the env)

Hi rafael.
The connector does not let kafka handle the offset with the group.id mechanism by default because we keep track of it in each partition internally. Bytewax does that to ensure that in the event of a restart, the dataflow can resume from the latest known checkpoint and ensure that all the messages will be processed at least once.
If you don't care about recovery, you can set group.id and enable auto.commit. But that means that when your dataflow restarts, you loose all the messages that were received but not processed, loosing the at-least-once semantics the operator normally offers.
The nice thing is that you don't need to use group.id to achieve the parallelization level you want, the connector already does that and creates a bytewax input partition for each partition in each topic in the broker, so if you have a single topic with 10 partitions, you can run the dataflow with 10 workers (or 10 processes), and each one will handle a single kafka partition.
The warning is related to the fact the we pass the same config used in the consumer to an AdminClient we use when bootstrapping the dataflow to retrieve the list of partitions for each topic (see here). That client is seen as a "producer", so you get the warning, but you can safely ignore that.

Thanks for the response. @Psykopear
If I understand correctly, I will have to modify the entrypoint.sh used by the Image bytewax/bytewax:0.18.1-python3.11
#!/bin/sh

cd $BYTEWAX_WORKDIR
. /venv/bin/activate
python -m bytewax.run -w$NUM_WORKERS $BYTEWAX_PYTHON_FILE_PATH

echo 'Process ended.'

if [ "$BYTEWAX_KEEP_CONTAINER_ALIVE" = true ]
then
    echo 'Keeping container alive...';
    while :; do sleep 1; done
fi

NUM_WORKERS is the known number of partitions of a given topic.
so In a given Dockerfile I will just need to
FROM bytewax/bytewax:0.18.1-python3.11
ENV NUM_WORKERS=10
COPY entrypoint.sh /bytewax/entrypoint.sh

Hey there, I have a question regarding this issue. Setting the number of workers for my dataflow when running the application, would mean that all the workers are running on the same pod , correct? For that my pod would have to be big enough to handle all the messages from the stream at once. This would also mean that the number of workers would be fixed , which does not allow me to have dynamic scaling of my app based on my current throughput. What i would like to do, is create additional replicas of my dataflow app when the data load is high and scale down automatically (reduce the number of replicas) when the data load is low. I thought using the same consumer group id for all the replicas would solve it, but it appears the messages are not distributed evenly across the replicas, but each replica sees all the messages. Any idea on how I can configure paralellism on my consumers based on group ids ?


Add columns necessary for gender analysis to the translation sheet

Currently the gender of a person is a column of the persons sheet. However, based on a request from the PhD students and to ease analysis in Excel, we should add columns in the translation sheet to indicate which translation had at least one female author or female translator.
We should add a script that computes the new columns femaleAuthor and femaleTranslator that can contain the values TRUE, FALSE or UNKNOWN (in case the gender information is unknown for at least one of the authors respectively translator)

I just added the newly computed columns via VLOOKUP also to the last corpus version of 2024-08-26.


vue-cli-service: command not found

Version
3.0.1
Node and OS info
nvm 0.33.1 / Node v8.11.4 / Ubuntu 16.04
Steps to reproduce
npm run build fails because vue-cli-service: command not found
What is expected?
npm run build succeeds
What is actually happening?
npm run build fails because vue-cli-service: command not found

Installed globally with npm install -g @vue/cli@latest

Please provide a valid reproduction when opening an issue.

@sodatea please explain how it would be possible to provide a reproduction for this issue.

Like, the project repository created by vue create.

Okay, here is a repository that I created with vue create:
https://github.com/DimaFromCanada/testrepoforvue.git

This works fine on my macOS. The issue is on Ubuntu 16.04 with NVM.
Yes, I have tried rm -rf node_modules and reinstall.

Still can't reproduce with a fresh install of nvm & node.
https://asciinema.org/a/hRDyrM5HcDHVieV3mPLEVlhdL
Maybe the $PATH variable is somehow messed up in your environment.

Please let me know what executables the $PATH should include.
Have you tested in Ubuntu 16.04?
On Thu, 30 Aug 2018 at 11:47 PM Haoqun Jiang<EMAIL_ADDRESS>wrote:

Still can't reproduce with a fresh install of nvm & node.
https://asciinema.org/a/hRDyrM5HcDHVieV3mPLEVlhdL
Maybe the $PATH variable is somehow messed up in your environment.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue-cli/issues/2404#issuecomment-417346214, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK5OkJWsFS1XqKD0gNGEUWqFB9OnB00Mks5uV_r1gaJpZM4WThwJ
.

This is most likely an npm issue (for not prepending ./node_modules/.bin to $PATH). So please also try updating  npm version.

Closing due to inactivity for more than 1 week. Please open a new issue with a reference to this one if you can follow up with more information.

Yeah, don't close this issue please. I'm getting this as well. vue-cli-service: not found

Hi, everyone, I've got the same error.
Apparently, I try to build the app locally, and it works fine.
But when I push the code to github, and the arrival of a new commit triggers travis-ci build job, and it gives me the error which is "/bin/sh: 1: vue-cli-service: not found".
https://github.com/whizjs/superjs/blob/master/.travis.yml
By the way, travis-ci has been working fine util this latest commit.

same issue here on ubuntu 18.04.. i just tried a complete reinstall of nodejs and npm and deleted all global node_modules

Hi,
I have exactly the same error for gitlab-ci:
yarn run v1.12.3 $ vue-cli-service build /bin/sh: 1: vue-cli-service: not found info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. error Command failed with exit code 127. ERROR: Job failed: exit code 1

Had similar issues as above and this worked
sudo npm cache clean -f

rm -rf node_modules package-lock.json && npm install worked for me

Tried all the options above nothing worked for me

on ubuntu I fixed this by:

uninstalled my old npm that was installed using apt install
apt-get remove npm
installed nvm
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.9/install.sh | bash
restarted terminal
installed latest npm using nvm
nvm install --latest-npm
reinstall packages as suggested by diachedelic
rm -rf node_modules package-lock.json && npm install

I got it working with npx vue-cli-service ...

Not sure if this is the correct solution, but deleting node_modules and npm install didn't solve it for me.  It looks like you need to install @vue/cli-service and any plugins you use globally.  Here's my solution:
Host: Windows 10
Dockerfile
FROM node:8.10-stretch

# update npm & install vue cli peer dependencies
RUN npm install -g npm
RUN npm install -g @vue/cli @vue/cli-service @vue/cli-plugin-babel @vue/cli-plugin-eslint

WORKDIR /app

COPY package*.json ./
RUN npm ci

VOLUME /app

CMD npm run serve

docker-compose.yml
version: "3.5"

services:
  ui:
    build:
      context: ui/
    ports:
      - 3000:80
    volumes:
      - ./ui/:/app
      - shadow-ui:/app/node_modules:delegated # see comment below
    stdin_open: true
    tty: true
    environment:
      CHOKIDAR_USEPOLLING: 'true'

volumes:
  shadow-ui: # see comment below

The shadow-ui volume prevents the node_modules directory on my host (windows) from being mounted into my container (debian), so npm ci will download the correct binaries for node-sass.  This error presents it's self as "Could not find package vue-template-compiler" or something similar.

if happened while building docker image, try to remove NODE_ENV=production before npm install or yarn install.

sudo yarn install fixed mine

I think this issue needs to be re-opened because I have got this error simply by deleting my node_modules and re-running npm install from inside the root directory of the application. Running $ vue create project-name allows for npm run serve to work correctly.

that fixs me:
edit package.json -> scripts, change vue-cli-service to node_modules/.bin/vue-cli-service

I also get it, will check if @microJ 's solution fixes it.

See...

Of course the last comment is the one that holds the answer for me. Resolved by prepending my command with ./node_modules/.bin/

This issue seems to be caused by several user environment related issues:

corrupted node_modules, which can be caused by bad installation of the project packages ➡ delete node_module and reinstall (deleting package-lock.json or yarn.lock too before reinstalling can also help)
using yarn to add a dependency in a npm project or using npm to add a dependency in a yarn project (don't do this)
: in the path, for example /Users/julien/programming:work/path/to/my-app (PATH separator is the : character)

https://stackoverflow.com/questions/40546231/sh-react-scripts-command-not-found-after-running-npm-start
https://stackoverflow.com/questions/47612580/react-scripts-command-not-found?rq=1
https://github.com/facebook/create-react-app/issues/3256#issuecomment-340259809
https://github.com/facebook/create-react-app/issues/3256#issuecomment-358406611
https://stackoverflow.com/questions/47842849/how-to-resolve-sh-react-scripts-command-not-found
https://npm.community/t/npm-script-cant-find-module-without-the-full-path/1344/15

rm -rf node_modules package-lock.json && npm install worked for me

this works for me

rm -rf node_modules package-lock.json && npm install 为我工作

thanks

I did npm install and that was enough for me.

Works if you run the "npm install" in "cmd", but not in powershell.

I'm using ubuntu inside windows 10.
In my case the problem WAS the Malwarebytes :( it was blocking some update in my npm install!

I got the same error in WSL ubuntu on Win 10.
My solution was to call ./node_modules/.bin/vue-cli-service; i.e. ./node_modules/.bin/vue-cli-service build --mode development.

Hey!
This is the correct solution: you need to install @vue/cli-service module.
Using NPM
$ npm i -S @vue/cli-service

Using Yarn
$ yarn add @vue/cli-service

Hey!
This is the correct solution: you need to install @vue/cli-service module.
Using NPM
$ npm i -S @vue/cli-service

Using Yarn
$ yarn add @vue/cli-service

Its Worked for me.

Hey!
This is the correct solution: you need to install @vue/cli-service module.
Using NPM
$ npm i -S @vue/cli-service

Using Yarn
$ yarn add @vue/cli-service

Its Worked for me.
If it doesent work, do this again, and call it like this ./node_modules/.bin/vue-cli-service

The only thing that worked for me was going to plugins menu and download '@vue/cli-service' from there

If you use NPM package manager you need move dependencies in package.json from "devDependencies" to "dependencies". Then NPM will install them and vue-cli-service can build your app.

npm install -g @vue/cli-service-global

npm install -g @vue/cli-service-global

This is the correct way... Always works for me.

I had an issue when I had NODE_ENV set to production, which was, quite for sure, incorrect for this script to execute.
Changed back to development, and everything is fine again.

That resolved it for me

Using npm
Install globally:
npm install -g @vue/cli-service-global
Add the directory where npm install globals to PATH and make it persistent in a new terminal by adding it to ~/.bashrc:
echo $'\nexport PATH="$(npm -g bin)":$PATH' >> ~/.bashrc

run it with npx e.g.
npx vue-cli-service build --mode development

in my case I think there was a conflict with yarn and npm.
I did

yarn remove global @vue/cli
npm cache -f clean
yarn add global @vue/cli

Which worked for me

I also was getting same issue: I resolved it by cleaning cache of npm npm cache clean -f and removing package-lock.json file rm -rf node-modules package-lock.json and start fresh install.

Got the same issue when deploy vue project in jenkins.
Here is what I did:
Add node's bin/ dir, to jenkins user's .bashrc file.
e.g
# node
NODE_HOME=/home/dev/.nvm/versions/node/default
PATH=$NODE_HOME/bin:$PATH

getting the same one too

In my case, the package @vue/cli-service is installed in my local node_modules environment, but not my global environment, so it cannot be used as a command. I type ./node_modules/.bin/vue-cli-service serve and it works.

In my case, I simply forgot to run yarn install before running the build script yarn build.

If you use NPM package manager you need move dependencies in package.json from "devDependencies" to "dependencies". Then NPM on Heroku will install them and vue-cli-service can build your app.

A potentiel issue of this could be that the production build gets heavier because of the additional dependency, which should not be needed in a production, especially if users want to install the app as a PWA.
I could fix this on Heroku by using the heroku build hooks as explained here
"heroku-prebuild": "npm install -g @vue/cli-service",

You can also customize the heroku-postbuild if you need additional configuration.

Similar to @COil's comment.  Simply got this error when cloning new repo and attempting to run yarn serve before yarn/yarn install.

My solution on Ubuntu 20.04:
npm i -g @vue/cli
rm -rf node_modules package-lock.json && npm install

Version
3.0.1
Node and OS info
nvm 0.33.1 / Node v8.11.4 / Ubuntu 16.04
Steps to reproduce
npm run build fails because vue-cli-service: command not found
What is expected?
npm run build succeeds
What is actually happening?
npm run build fails because vue-cli-service: command not found
Installed globally with npm install -g @vue/cli@latest
what's the fucking????

Hey!
This is the correct solution: you need to install @vue/cli-service module.
Using NPM
$ npm i -S @vue/cli-service

Using Yarn
$ yarn add @vue/cli-service

it's work for me too

I try all of them and now it's working)

rm -rf node_modules package-lock.json && npm install worked for me

This worked for me!

rm -rf node_modules package-lock.json && npm install worked for me

This worked for me!

If you use NPM package manager you need move dependencies in package.json from "devDependencies" to "dependencies". Then NPM on Heroku will install them and vue-cli-service can build your app.

A potentiel issue of this could be that the production build gets heavier because of the additional dependency, which should not be needed in a production, especially if users want to install the app as a PWA.
I could fix this on Heroku by using the heroku build hooks as explained here
"heroku-prebuild": "npm install -g @vue/cli-service",

You can also customize the heroku-postbuild if you need additional configuration.

First I update the npm to the lasted version, then I run it, This works for me!

rm -rf node_modules package-lock.json && npm install worked for me

This worked for me too. Ubuntu 18.04

Still an issue for me...
sudo npm install -g @vue/cli
...
$ vue
command "vue" not found

I had an issue when I had NODE_ENV set to production, which was, quite for sure, incorrect for this script to execute.
Changed back to development, and everything is fine again.

Yeah but then how do you deploy your actual production envoirnment then :D ?

Another solution
If you use yarn:

Install the vue cli globally if you didn't already:

yarn global add @vue/cli

Get the path where yarn stores global packages:

yarn -g bin

// Output: home/YOUR_USER_NAME/node_modules/.bin

Open file ~/.bashrc for editing in any text editor on directly in terminal using nano:

sudo nano ~/.bashrc

Add the following line on top. And replace YOUR_USER_NAME with your user name.:

export PATH=$PATH:/home/YOUR_USER_NAME/.yarn/bin

Save with Ctrl + S and exit Ctrl + X

Log out / Log in (or just restart the computer)

If you use npm:
Do the same thing but:

In the step 0 run npm install -g @vue/cli instead of yarn global add @vue/cli
In the step 1 run npm -g bin instead of yarn -g bin

The other solutions worked for me only temporarily until the terminal window is re-opened.
I don't use Linux as my primary OS, so I don't know if it's a good idea to add path variables to ~/.bashrc file.

I got the same issue on macOS.

I got the same issue on macOS.
Here is my solution.
Besides the error message above, there are other tips:
npm ERR!      /Users/xxx/.npm/_logs/2020-10-20T07_41_00_394Z-debug.log
Open the file of xxx-debug.log:
///
6 verbose cli   '/usr/local/Cellar/node/14.12.0/bin/node',
6 verbose cli   '/Users/xxx/node_modules/.bin/npm', <-------!!! wrong
6 verbose cli   'install',
6 verbose cli   '--loglevel',
6 verbose cli   'error',
6 verbose cli   '<EMAIL_ADDRESS>6 verbose cli   '<EMAIL_ADDRESS>6 verbose cli   '<EMAIL_ADDRESS>6 verbose cli   '--save-dev'
6 verbose cli ]
7 info using<EMAIL_ADDRESS>  <-------!!! wrong
8 info using<EMAIL_ADDRESS>///
I found the npm version and path are wrong.
I open the path of the npm of log file.
cd  /Users/xxx/node_modules/.bin/
then i run the command of ls -al.
///
lrwxr-xr-x    npm -> ../npm/bin/npm-cli.js
lrwxr-xr-x    npx -> ../npm/bin/npx-cli.js
///
The links above point to wrong paths.
The correct paths are :
lrwxr-xr-x    npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js
lrwxr-xr-x    npx -> /usr/local/lib/node_modules/npm/bin/npm-cli.js
After recorrecting these links. vue works well.

* I don't use Linux as my primary OS, so I don't know if it's a good idea to add path variables to `~/.bashrc` file.

for me it has to be in .bashrc vs .bash_profile for reason i cant remember.

Hi, I had the same issue for a while.
TL;DR
 npm install @vue/cli-service --save-dev

As the documentation specify it is a development dependency  https://cli.vuejs.org/guide/#cli-service

The CLI Service (@vue/cli-service) is a development dependency. It's an npm package installed locally into every project created by @vue/cli.

Origin
I had a fresh install of nodejs
And just did
>> sudo npm install -g @vue/cli@latest

>> vue --version
@vue/cli 4.5.8

The issue
The issue presented like this
>> npm run serve
yarn run v1.22.10
$ vue-cli-service build --mode development --watch
/bin/sh: 1: vue-cli-service: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

The fixes:
npm install @vue/cli-service --save-dev

Which led me straight to another error message
>> npm run serve
yarn run v1.22.10
$ vue-cli-service build --mode development --watch
ERROR  Error: Cannot find module 'vue-template-compiler/package.json'

Which I fixed the same way
npm i vue-template-compiler --save-dev

And now it is working fine.

Those facing this issue making a production build while deploying to Heroku or similar, remove @vue/cli-service and re-add it. Should do the job

Using github actions, the only way that worked for me was to set NODE_ENV to development just for install
- run: |
    NODE_ENV=development npm ci
    npm run build

Thanks @yoannes - I was missing the npm ci as part of my build.
- run: npm ci && npm run build
worked for me

Getting this issue.
How I got it:

created empty project via vue-cli-service, added it into backend code and deployed on heroku -- so frontend must be build on the server while deploy. The root folder contains ./client with the empty project, scripts.build in the ./package.json runs cd ./client && npm install && npm run build.
this error appears

What didn't help:

deleting package-lock.json
replacing vue-cli-service to either npx vue-cli-service or ./node_modules/.bind/vue-cli-service

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/vue-cli-service - Not found
npm ERR! 404
npm ERR! 404  'vue-cli-service@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)

adding @vue/cli-service to package.json - it's a vue-cli-generated project, it obviously contains @vue/cli-service in devDependencies
installing @vue/cli-service-global or vue globally

This fixed the issue for me:

Terminal Command:
./node_modules/.bin/vue-cli-service serve

finally this helped me, thank a lot.

@nguyentruongtansam Hi. I wrote like this ./node_modules/.bin/ in npm-sripts.
But on gitlab-ci it alwait fail with error.

./node_modules/.bin/vue-cli-service test:unit
sh: 1: ./node_modules/.bin/vue-cli-service: not found
How to fix this ob CI ?

rm -rf node_modules package-lock.json && npm install worked for me

This worked for me too. Ubuntu 18.04

This worked for me

 npm install @vue/cli-service --save-dev

this worked for me on MacOS 12.3.1

I found in docker service with NODE_ENV=production it's not compiling the node_modules/.bin dir when do npm i
so my workaround is to remove that var on the npm i become export NODE_ENV; npm i; export NODE_ENV=production
or backup it first to obtain whatever is the previous value

NAME="Ubuntu" VERSION="20.04.4 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.4 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal
Tried all, There's no way it works :(

Adding ./node_modules/.bin/ on the command path before the vue-cli-service as you can see in the screenshot below fixed the issue also for me!


Call Issue when logged in a same user in multiple devices

I've installed the the android-messenger-app in three device. and in two of the device i logged in with same user and with other one device i've logged in with other account and started the call.
devices: deviceA, deviceB, deviceC
users: X,Y
deviceA and deviceB is logged as X
deviceC is logged in as Y
when Y calls the user X, deviceA and deviceB receives the call and after i accepted the call from deviceA,
no event is triggered in deviceB that same user accepted call from another device.
and also when deviceB rejects the after deviceA accepted, call will disconnected from both deviceB, and deviceC
i've looked into the react-native-connectycube sdk too, there was a event callback i.e
Connectycube.videochat.onStopCallListener()
Is there any alternative event callback in react-native-android sdk.

In Android SDK we have similar callbacks:
/**
 * Called in case when opponent has rejected your call
 */
override fun onCallRejectByUser(session: RTCSession, userId: Int, userInfo: MutableMap<String, String>?) {}

and
/**
 * Called in case when opponent hung up
 */
override fun onReceiveHangUpFromUser(session: RTCSession, userId: Int, userInfo: MutableMap<String, String>?) {}

More info you can found in our documentation.

@TatankaConCube thanks for the info, but i've tried using these events. I works for the call initiator i.e. deviceC. But in my case deviceA and deviceB and are opponents with same user logged in, and none of the following events are invoked to the deviceB after deviceA accepted or rejected the call.
`/**

Called in case when opponent has rejected your call
*/
override fun onCallRejectByUser(session: RTCSession, userId: Int, userInfo: MutableMap<String, String>?) {}`

`/**

Called in case when opponent hung up
*/
override fun onReceiveHangUpFromUser(session: RTCSession, userId: Int, userInfo: MutableMap<String, String>?) {}`

`/**

Called in case when opponent accept the call
*/
override fun onCallAcceptByUser(session: RTCSession, userId: Int, userInfo: MutableMap<String, String>?) {}`

As a variant you can organise additional signalling via System messages feature. Oriented logic will be:

deviceA sends system message for himself (userX) with parameter self_action=accept (self_action=reject, self_action=hang_up for another actions) and type=self_signalling when does Accept call (or another) action;
deviceB receives this message and does needed actions (close call screen, etc.);

@TatankaConCube Thank you very much. I did implemented the purposed solution, it worked :)


Update README.md

Thank you! Just used it for a personal project of mine that was very helpful. I struggled initially to understand that our migration files needed to be in ./migrations based on the docker-compose.yaml example provided. I believe this change makes it more clear for docker novices like myself 👍

Glad you found this project helpful 😊


[Suggestion] Port for ReIndev?

Would it be possible to make a port for ReIndev?  It's another retrofork similar to BTA and NSSS.  It doesn't use the same package structure as vanilla b1.7.3

Indev doesn't even have multiplayer? Adding it would only affect the inventory screen and would basically involve rewriting the entire player renderer.

ReIndev isnt a mod for indev, thats just its name.  ReIndev is a mod for b1.7.3.  You can find videos of it on youtube

Thought I would add an update to this post; with the mixin based mod loader for ReIndev, "FoxLoader", a port of Ears is probably easier than ever now.


Current status of implementing space-delimited data

I was wondering what the current status is for implementing space-delimited data decoding. From what I can tell, the original discussion of this issue was at #14, then a pull request was made at #30, then a second pull request was made at #36. That was in October 2013, and as far as I can tell the issue just sort of died there. Is this still a planned / desired feature? If so, @Shimuuar are you still working on it?
If this is still a desired feature, but no one is working on it, I'd be happy to hack on this. Just let me know, and let me know what you think the interface should look like (there was some discussion of the interface in #30, but since that was a long time ago I'm assuming you might want something different now).

No I don't work on this. AFAIR adding parsing of space-delimited data introduced performance regressions. If you need to implement it please use PRs as you see fit


Docker image generates warning about psycopg2

The docker image for v0.63.1 generates this warning:
/usr/local/lib/python3.6/site-packages/psycopg2/init.py:144: UserWarning: The psycopg2 wheel package will be renamed from release 2.8; in order to keep installing from binary please use "pip install psycopg2-binary" instead. For details see: http://initd.org/psycopg/docs/install.html#binary-install-from-pypi.

Build a docker image on the top of your image, and add the following instructions :
FROM current-image:version
....
RUN pip3 unistall psycopg2
RUN pip3 install psycopg2-binary

I am running 0.70 and it still the warning is still there
 /usr/local/lib/python3.6/site-packages/psycopg2/__init__.py:144: UserWarning: The psycopg2 wheel package will be renamed from release 2.8; in order to keep installing from binary please use "pip install psycopg2-binary" instead. For details see: <http://initd.org/psycopg/docs/install.html#binary-install-from-pypi>.

Confirmed on version 0.72.1

Confirmed on version 0.80.3.
/usr/local/lib/python3.6/site-packages/psycopg2/__init__.py:144: UserWarning: The psycopg2 wheel package will be renamed from release 2.8; in order to keep installing from binary please use "pip install psycopg2-binary" instead. For details see: <http://initd.org/psycopg/docs/install.html#binary-install-from-pypi>.

The Docker image should make use of psycopg2-binary instead of psycopg2.
Starting from version 2.8 the psycopg2 package will not contain the binary anymore.
See http://initd.org/psycopg/docs/install.html#disabling-wheel-packages-for-psycopg-2-7


Error while fetching ratings for quote

2024-10-10T15:20:32.925201763Z app[web.1]: {"level":"debug","message":"[fTW3Ay9qPILaf7vRQMxHw] fetching quote for BA 2231","timestamp":"2024-10-10 15:20:32"}
2024-10-10T15:20:32.925423325Z app[web.1]: {"level":"debug","message":"proxy request ==> GET https://api.flightstats.com/flex/ratings/rest/v1/json/flight/BA/2231?appId=96875f77&appKey=dc097f38175fd39620c72b94fc79be05","reqId":"fTW3Ay9qPILaf7vRQMxHw","timestamp":"2024-10-10 15:20:32"}
2024-10-10T15:20:33.024279303Z app[web.1]: {"level":"debug","message":"proxy response <== 200","proxyRequestDuration":98,"reqId":"fTW3Ay9qPILaf7vRQMxHw","timestamp":"2024-10-10 15:20:33"}
2024-10-10T15:20:33.025270332Z app[web.1]:  ⨯ TypeError: Cannot read properties of undefined (reading 'ontime')
2024-10-10T15:20:33.025282595Z app[web.1]:     at x (/app/.next/server/app/api/quote/[carrier]/[flightNumber]/route.js:1:2262)
2024-10-10T15:20:33.025286713Z app[web.1]:     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2024-10-10T15:20:33.025289728Z app[web.1]:     at async g (/app/.next/server/app/api/quote/[carrier]/[flightNumber]/route.js:1:1251)
2024-10-10T15:20:33.025292253Z app[web.1]:     at async /app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:36957
2024-10-10T15:20:33.025294958Z app[web.1]:     at async eC.execute (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:27552)
2024-10-10T15:20:33.025297763Z app[web.1]:     at async eC.handle (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:38291)
2024-10-10T15:20:33.025300378Z app[web.1]:     at async doRender (/app/node_modules/next/dist/server/base-server.js:1345:42)
2024-10-10T15:20:33.025303274Z app[web.1]:     at async cacheEntry.responseCache.get.routeKind (/app/node_modules/next/dist/server/base-server.js:1567:28)
2024-10-10T15:20:33.025305869Z app[web.1]:     at async NextNodeServer.renderToResponseWithComponentsImpl (/app/node_modules/next/dist/server/base-server.js:1475:28)
2024-10-10T15:20:33.025308453Z app[web.1]:     at async NextNodeServer.renderPageComponent (/app/node_modules/next/dist/server/base-server.js:1901:24)
2024-10-10T15:20:33.102723502Z app[web.1]: {"level":"debug","message":"POST request to /api/client_error","timestamp":"2024-10-10 15:20:33"}
2024-10-10T15:20:33.103160857Z app[web.1]: {"level":"error","message":"client side error occured during action 'flightData/fetchQuote'\n======\nError fetching quote data: \n------\n{\"name\":\"Error\",\"message\":\"Error fetching quote data: \",\"stack\":\"Error: Error fetching quote data: \\n    at fetchQuote (https://flightdelay.integration.etherisc.com/_next/static/chunks/app/layout-39dfd358ed90bb54.js:1:15032)\\n    at async https://flightdelay.integration.etherisc.com/_next/static/chunks/app/layout-39dfd358ed90bb54.js:1:15430\\n    at async https://flightdelay.integration.etherisc.com/_next/static/chunks/836-137163563d9c5ff5.js:15:32086\"}\n------\n1728573632986 / 10/10/2024, 3:20:32 PM\n======\n","timestamp":"2024-10-10 15:20:33"}

flighstats response
{"request":{"airlineCode":{"requestedCode":"BA","fsCode":"BA"},"flightNumber":{"requested":"2231","interpreted":"2231"},"url":"https://api.flightstats.com/flex/ratings/rest/v1/json/flight/BA/2231"},"ratings":[],"appendix":{"airlines":[],"airports":[]}}


why does the function mess up the URL

the icon fadein function is a piece of garbage, rewrite in the morning.
it really messes up the URL of the background image for some reason
ugh

lol


Make order matching parallel in EndBlock

EDIT: going to break this down into smaller PRs
This PR includes the following changes:

Replace all maps used during order matching to sync.Map
Add a new numIncomingPaths field on ContractInfo that's automatically calculated upon contract registration. This field indicates the number of contracts that depend on the current contract
Add a ParallelRunner that takes in a runnable and a list of ContractInfo, and invoke runnable for ContractInfo according to their topological order while maximizing parallelism. Note that the runner implicitly performs topological sort so the list being passed in doesn't have to be topologically sorted already. (The old TopologicalSort utility is now only used for validation upon contract registration)
Use ParallelRunner for endBlockForContract in dex EndBlock

do we still need this PR?

@LCyson yes this is to actually add the core parallelization logic, using the data structure utilities merged in other PRs


[docs] Improve CollapsibleList demo in Joy UI List docs

[x] I have followed (at least) the PR section of the contributing guide.

Since we show pointer cursor, when clicked it should toggle the collapse like in Gatsby documentation.
Before: https://mui.com/joy-ui/react-list/#collapsible-list
After:

No need of this fix after changes in #34193 . Closing this PR.


OpenVPN loses connection, Authenticate/Decrypt packet error: missing payload

Hi, i have a problem with the vpnserver.
When I try to connect to the server via OpenVPN Clone function on port UDP443 (or TCP) with the OpenVPN Client (version 2.44-l601) using username/password authentification, I'm able to authenticate successfully.
After I got an address from the DHCP server the error "Authenticate/Decrypt packet error: missing payload" occurs on the client side and the client looses connection right after.
On the server side this message occurs in the logs:
"Connection "CID-46" terminated by the cause "The VPN session has been deleted. It is possible that either the administrator disconnected the session or the connection from the client to the VPN Server has been disconnected." (code 11).
2018-01-23 17:10:41.254 Connection "CID-46" has been terminated."
When I try to connect with the SoftEtherVPN client, there are no problems, but I need the server to work with both OpenVPN and SoftEther VPN Clients.
I use pretty much the default configuration of the server and I can't find any information about the missing payload error.
Does anyone have the same problem??
Let me know if you need any logs or files.
Versions:
OS: Debian 9.3 32-bit
Softether server version; 4.23 (build 9647) 32-bit (i cloned and compiled yesterday)
OpenVPN Client version: 2.44-l601

I resolved the issue by using libssl1.0.0-dev during build instead of the libssl1.1.0-dev (default in debian stretch).
I resolved the issue. Please close.

After some testing, I found out that the problem only happens with OpenSSL 1.1.0f.
Newer and older versions work fine, meaning that it's probably a regression introduced in 1.1.0f and then fixed in 1.1.0g.
Debian Stretch users should install libssl1.1 from the sid branch, as a temporary workaround.

Any chance of unit test for that))?


Question: Dynamic Features & Data Binding  & MinifyEnabled

Hi! I noticed about the app crash in runtime related to shrinking enabled minifyEnabled true, Any update about this issue?
// There's a Dex Splitter issue when enabling DataBinding & proguard in dynamic features
 // The temporary workaround is to disable shrinking

https://github.com/android/plaid/blob/master/app/build.gradle#L57

It seems as long as you don't obfuscaste the binding mapper, you can still have minifyEnabled true without the runtime crash.
-keep class com.example.module1.DataBinderMapperImpl { *; }
-keep class com.example.module2.DataBinderMapperImpl { *; }

https://stackoverflow.com/questions/54404492/proguard-with-appbundle-and-data-binding-illegalstateexception

thanks, of course, I tried this solution and doesn't seem it works. (maybe I missing something)


How to configure a the Java webapp behind a Proxy in Apache

Dear,
I'm trying to configure the example webapp Java application (https://docs.microsoft.com/azure/active-directory/develop/quickstart-v2-java-webapp) to work behind a ProxyPass and ProxyPassReverse in Apache, but I can't get it work.
In Apache I have the following configuracion:
ProxyPass               /testazure              http://localhost:8080
ProxyPassReverse        /testazure              http://localhost:8080

And I made some changes in the templates of the example to redirect the auth_page.html and index.html forms to /testazure/msal4jsample/XXX.
Also I changed the application.properties file to redirect to my Apache, that works in https:
aad.redirectUriSignin=https://localhost/testazure/msal4jsample/secure/aad
aad.redirectUriGraph=https://localhost/testazure/msal4jsample/graph/me

When I access to https://localhost/testazure, it shows me the website:

When I try to login, it ask me about the user, but when I choose my user, the server throws this exception:
2021-03-25 15:06:09.018 ERROR 77186 --- [onPool-worker-2] c.m.a.m.ConfidentialClientApplication    : [Correlation ID: a3857c1b-8c7f-4aaf-9df3-7d0092a9d900] Execution of class com.microsoft.aad.msal4j.AcquireTokenByAuthorizationGrantSupplier failed.

com.microsoft.aad.msal4j.MsalServiceException: AADSTS500112: The reply address 'http://localhost:8080/msal4jsample/secure/aad' does not match the reply address 'https://localhost/testazure/msal4jsample/secure/aad' provided when requesting Authorization code.
Trace ID: 7b151e82-b7c1-46c8-a237-e9875a079500
Correlation ID: a3857c1b-8c7f-4aaf-9df3-7d0092a9d900
Timestamp: 2021-03-25 14:06:08Z
	at com.microsoft.aad.msal4j.MsalServiceExceptionFactory.fromHttpResponse(MsalServiceExceptionFactory.java:43) ~[msal4j-1.6.1.jar:1.6.1]
	at com.microsoft.aad.msal4j.TokenRequestExecutor.createAuthenticationResultFromOauthHttpResponse(TokenRequestExecutor.java:90) ~[msal4j-1.6.1.jar:1.6.1]
	at com.microsoft.aad.msal4j.TokenRequestExecutor.executeTokenRequest(TokenRequestExecutor.java:38) ~[msal4j-1.6.1.jar:1.6.1]
	at com.microsoft.aad.msal4j.AbstractClientApplicationBase.acquireTokenCommon(AbstractClientApplicationBase.java:117) ~[msal4j-1.6.1.jar:1.6.1]
	at com.microsoft.aad.msal4j.AcquireTokenByAuthorizationGrantSupplier.execute(AcquireTokenByAuthorizationGrantSupplier.java:63) ~[msal4j-1.6.1.jar:1.6.1]
	at com.microsoft.aad.msal4j.AuthenticationResultSupplier.get(AuthenticationResultSupplier.java:59) [msal4j-1.6.1.jar:1.6.1]
	at com.microsoft.aad.msal4j.AuthenticationResultSupplier.get(AuthenticationResultSupplier.java:17) [msal4j-1.6.1.jar:1.6.1]
	at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1604) [na:1.8.0_281]
	at java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1596) [na:1.8.0_281]
	at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) [na:1.8.0_281]
	at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1067) [na:1.8.0_281]
	at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1703) [na:1.8.0_281]
	at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:172) [na:1.8.0_281]

If I change in AuthFilter.java file the currentUri attribute to the following value, it works:
currentUri = "https://localhost/testazure" + httpRequest.getRequestURI();

Does exist any way to configure it to work without doing that?

Hello @marcgise : You set the redirect URIs in applications.properties, but did you also set them in the app registration in Azure?
Check the 'authentication' tab of your app in Azure (like in the below image), it may still have the default redirect URIs which are missing the /testazure part needed by your client application. I haven't used ProxyPass before, but if all that's needed is for requests to have that /testazure path in it then having the correct redirect URLs should be enough.
If it's still not working or if the redirect URLs are already correct, then you may have to use your own HTTPClient class to handle any extra HTTP steps (see here for more info on overriding the library's default HTTP stuff)


Merged Klocwork Plugins

I have updated the Klocwork Jenkins plugin to accept xml reports generated by v9.5. Originally the xml parsing failed as the "owner" of an issue is now reported in the xml reports.
Other functionality added include: link to Klocwork Review, link to build.log and parse_errors.log files, and per-build pie chart showing issues by state.
Updated the trend graph so that maximum number of builds can be specified and the interval. Stops the graph getting over-crowded.

Thanks for your updates.
I'll do some tests tomorrow and I'll merge it if no problem appears.

Brilliant, glad I could help.
Thanks,
Jacob

Hi Jacob,
It seems that some files are missing : when I tried to compile the project, I got this message :
symbol  : class KloBuildReviewLink
location: package com.thalesgroup.hudson.plugins.klocwork.util
import com.thalesgroup.hudson.plugins.klocwork.util.KloBuildReviewLink;
^
symbol  : class KloProjectReviewLink
location: package com.thalesgroup.hudson.plugins.klocwork.util
import com.thalesgroup.hudson.plugins.klocwork.util.KloProjectReviewLink;
^
symbol  : class KloBuildReviewLink
location: package com.thalesgroup.hudson.plugins.klocwork.util
import com.thalesgroup.hudson.plugins.klocwork.util.KloBuildReviewLink;
^
symbol  : class KloProjectReviewLink
location: package com.thalesgroup.hudson.plugins.klocwork.util
import com.thalesgroup.hudson.plugins.klocwork.util.KloProjectReviewLink;
^
symbol  : class KloProjectReviewLink
location: class com.thalesgroup.hudson.plugins.klocwork.KloPublisher
actions.add(new KloProjectReviewLink(project));
^
symbol  : class KloBuildReviewLink
location: class com.thalesgroup.hudson.plugins.klocwork.KloPublisher
build.addAction(new KloBuildReviewLink(build));
Can you add them please ? Thank you.
Aravindan

Hi Aravindan,
Sorry about that. Seems that commit -a hadn't picked these files up so have added them manually.
Let me know if there is anything else.
Thanks,
Jacob

I've added them, no more compilation problems. Thanks.
Aravindan

Brilliant. Thanks for your help.
Jacob

Hi Aravindan,
Have pushed the help files and also some of the resource files which I saw were missing to the repo. All should be there now! I was under the impression that "commit -a" even adds new files, but according to the manual it only checks for changes in files which Git knows about. So sorry for all this.
Thanks,
Jacob

Thanks, can you do a new pull request please ?
Aravindan

Sure, submitted a new pull request.
Thanks,
Jacob

The merge has been successfully completed. Thank you.
Aravindan

Thanks Aravindan.


Missing support for Spring Data REST

I'm trying to implement JWT authentication in a Spring Data REST project, but I noticed that spring-webmvc-pac4j library is working only with regular controllers and not for the endpoints generated by Spring Data REST framework.
Is there a way to enable this, or is this feature missing?
Thanks,
David

To apply security in Spring MVC, pac4j has a SecurityInterceptor which is defined on URL patterns. So it should work for any controller or REST API.
Example:
registry.addInterceptor(new SecurityInterceptor(config, "jwt")).addPathPatterns("/api/*");

Thank you @leleuj , I have already configured a SecurityInterceptor in my project, but it's not working...
Some additional detail:
In my project I'm using Spring Data REST to dynamically generate endpoints for the REST API.  All these endpoints match this pattern: /api/*
Then I manually created a test rest controller, like this:
@RestController
public class TestController {
    @GetMapping("/test")
    public Item testMethod(){
        return new Test();
    }
}

As you suggested I added a SecurityInterceptor in my configuration:
registry.addInterceptor(new SecurityInterceptor(config, "HeaderClient")).addPathPatterns("/*");
and ran my project.
As checked before. The /test endpoint is secured, while all the /api/* path are still accessible...
Is there something wrong in the way I am configuring path pattern?

Can you try that: https://stackoverflow.com/questions/46953039/spring-interceptor-not-working-in-spring-data-rest-urls? Thanks

Closed due to inactivity


iTerm2 says This session's triggersare pretty slow. Disable them in interactive app?

ref: https://gitlab.com/gnachman/iterm2/-/wikis/Slow-Triggers

I guess this cause is https://github.com/sensuikan1973/dotfiles/blob/10f39f455775804ebeaa4c7fd94bf57ac4511020/iterm2/com.googlecode.iterm2.plist#L834-L860


Enhancement/enable serverless

resolves #248

Description
Add serverless Dataproc submission method and re-enable python model tests

Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have run changie new to create a changelog entry

Don't forget to take the branch out of dev-requirements.txt :)

@gshank Yea, I am gonna make sure the tests all pass then update and merge in sequence

It looks like dev-requirements.txt got merged on accident?
https://github.com/dbt-labs/dbt-bigquery/blob/84c20fcef86d9777b6ce6a4745b6415ec288ed93/dev-requirements.txt#L3-L4

Yes, fixing now


Can't reach sites with hostname from OCP

Install OCP on PowerVM using wildcard domain name.
Perform the workaround provided by<EMAIL_ADDRESS>to avoid the certificate issue

_=============Workaround==================
here is the workaround.
option domain-name              "nip.io";
option domain-search            "nip.io";
option domain-name              "yus-1ae<IP_ADDRESS>.145.nip.io";
option domain-search            "yus-1ae<IP_ADDRESS>.145.nip.io", "<IP_ADDRESS>.nip.io";
update /etc/dhcp/dhcpd.conf on bastion and restart service dhcpd restart
reboot all masters and workers nodes
=============Issue=======================
[root@iocp-5 ~]# oc import-image recreate-issue --from=registry.redhat.io/redhat-openjdk-18/openjdk18-openshift
error: tag latest failed: Internal error occurred: registry.redhat.io/redhat-openjdk-18/openjdk18-openshift:latest: Get “https://registry.redhat.io/v2/”: x509: certificate is valid for *.apps.ocp-b10b.<IP_ADDRESS>.xip.io, not registry.redhat.io
imagestream.image.openshift.io/recreate-issue imported with errors
Name:			recreate-issue
Namespace:		try-nightly
Created:		22 seconds ago
Labels:
Annotations:		openshift.io/image.dockerRepositoryCheck=2021-04-22T06:56:25Z
Image Repository:	default-route-openshift-image-registry.apps.ocp-b10b.<IP_ADDRESS>.xip.io/try-nightly/recreate-issue
Image Lookup:		local=false
Unique Images:		0
Tags:			1
latest
tagged from registry.redhat.io/redhat-openjdk-18/openjdk18-openshift
! error: Import failed (InternalError): Internal error occurred: registry.redhat.io/redhat-openjdk-18/openjdk18-openshift:latest: Get “https://registry.redhat.io/v2/”: x509: certificate is valid for *.apps.ocp-b10b.<IP_ADDRESS>.xip.io, not registry.redhat.io
================================_

However, still failed to connect to another system with host name from cluster. Seems the DNS is still not configured properly.
[core@worker-1 ~]$ ssh p8adt05.rch.stglabs.ibm.com
ssh: Could not resolve hostname p8adt05.rch.stglabs.ibm.com: Name or service not known

/assign

Fix it by updating dns setting. Thanks,


2FA Support

I have figured out what needs to be done for the 2FA changes that are coming into effect in July 22nd '24.
Here is the section of code I modified for the login to allow the passing of the 2FA token:
def _login(self):
        self.log.debug("login() as %s", self.username)
        self.session = requests.Session()
        self.session.verify = self.ssl_verify

        response = self.session.post(
            self.auth_url,
            data=json.dumps({"username": self.username, "password": self.password, "ubic_2fa_token": self.token}),
            headers=self.headers,
        )

        print(response.content)

        if response.headers.get("X-CSRF-Token"):
            self.headers = {"X-CSRF-Token": response.headers["X-CSRF-Token"]}
        if response.status_code == 400:
            raise APIError(
                "Login failed - status code: %i, msg: %s" % (response.status_code, response.json()["meta"]["msg"])
                )

        if response.status_code != 200:
            raise APIError(
                "Login failed - status code: %i, msg: %s" % (response.status_code, response.text)
                )

I pass this to the controller using this:
mfa_token = input("Enter your 2FA Token: ")

c = Controller('-Unifi Controller-', '-username-', '-password-', mfa_token)

You also need to add token=0 to the start of the init definition, I put this after the password entry, then you'll need to define the self variable down further using self.token = token
Passing json in the session.post command was not sending in the correct format for this. it needs to be sent as data, and decoded from JSON. I have checked that this still does work with accounts without the 2FA enabled on it, you can either just not pass the 2FA argument, or send any value you like - it will be ignored.
Hope this helps those looking for an answer for this!

Hi thanks for this - one of my controllers (UDM SE) does not ask for a MFA code each time I run the unmodified script, but my other controller (Unifi Express) fails to log in and I get the pop up on my unifi MFA app asking to approve login - which I do, but it obviously doesn't work.
I updated the file as you have above and installed it, but do not understand how to not put in the MFA code each time the script is run. Can you post an example? I'm just trying to run something basic like printing the connected client's IPs.
Thanks

Hi jhavens12,
The following bit of code prompts you for your 6 digit code that gets generated by your authentication app:
mfa_token = input("Enter your 2FA Token: ")
Once you type in your code, the script will continue. This is how its setup from what I have written, as I do not have my accounts prompting for authentication prompts via the app - only though an authenticator app.


Is it possible to put masks over multiview?

question in title

Hi, of course you can. But I haven't updated code yet, maybe we will support it in the future.

你好，当然可以。但我还没有更新代码，也许我们将来会支持它。

你好，多视角的数据应该怎么处理，希望得到你的帮助