v1beta1 and Tinkerbell changes

Issue #, if available:
Description of changes:
This branch is for testing all Tinkerbell related tasks. I will remove this branch once we have all the CAPI v1beta1 changes in the main branch.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold

@panktishah26 this PR  is merged with a few more changes

Closing this PR as CAPI v1beta1 changes are already merged in the main branch.


[BUG]: Can't share custom connector Office 365 Management API

Describe the bug
Can't share custom connector Office 365 Management API.  I'm not able to click on save button.
Is there anything that we did wrong when the custom connector was imported?
Thank you in advance
Component (please tell us which flow or app you are experiencing issues with):

Custom connector Office 365 Management API

To Reproduce
Steps to reproduce the behavior:
https://docs.microsoft.com/en-us/connectors/custom-connectors/share

Go to Data --> Custom connectors
Click on ellipsis button --> Invite another user
Scroll down to '....'
See error

Expected behavior
Be able to share the custom connector Office 365 Management API
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

@Bryand13 where the custom connector resides (environment), is that environment controlled by an O365 Group / Azure AD security group?

Hi @Daleyon ,
Thank you for comment.
Yes, the access to the environment where CoE is installed is controlled by a security group. But i don't know if that could be the reason, because we have the custom connector Office 365 Audit Logs also, and I'm able to share it with other users.
Thanks

Hello. I'm afraid this is outside of the scope of the CoE Toolkit. You'll need to contact customer support for assistance. I will also leave it open here for a few days to see if other users can offer advice.
Thanks for using CoE!

Hello @JeneferM-MSFT
What a pitty! I'll raise a ticket with MSFT support. Please don't close the issue, As you said maybe someone could help us with this matter.
Thanks in advance

Hello, from a colleague: Custom connectors shipped in a solution currently can't be shared, it's a product limitation.
The product team is continuing to shore up solutions, but for now you wont be able to do this.
Sorry about that, and thanks for using CoE

Closing as the product limitation will not surface a workaround. Thanks for using CoE!

Hello @JeneferM-MSFT ,
No problema at all. Thank you for letting me know.
Greetings


Concatenating files can generate same hash?

As far as I understand, this works by concatenating all of the files together and then hashing the result. Does this mean that we can get the same hash when hashing this:
File 1: 00 01 02
File 2: 03 04 05
As well as this?
File 1: 00 01 02 03
File 2: 04 05

That's true, thanks for uncovering this issue. I'll get this fixed soon.

Oh, just another thing to note, I'm not sure how important this is to you, but this hashing algorithm also doesn't seem to factor in the names of the files. So if a file got renamed from a.js to aa.js, the hash would still come out the same.

To solve both the issues at once, it would be enough to concatenate the full path of the file to the file data, and then hash.

To solve both the issues at once, it would be enough to concatenate the full path of the file to the file data, and then hash.

@monteiz No, because then you’d still get collisions like this:

file file1.txt with contents _foo_file2.txt_bar_ and file file2.txt with contents _baz_
file file1.txt with contents _foo_ and file file2.txt with contents _bar_file2.txt_baz_

which would both be smashed into file1.txt_foo_file2.txt_bar_file2.txt_baz_ and hashed to the same result.
To solve these issues, you need to encode the filenames and corresponding data into a stream from which they could be unambiguously recovered, for example, files.map((file) => file.name.length + " " + file.name + file.data.length + " " + file.data).join("").

@andersk good observation


Handle mixed cases of Platform generics

Description

Currently platform factory methods for KMP always use expect/actual and do not respect platform only cases.
Acceptance Critera:

Factories for generics are using the appropriate modifier according if they implement a meta source or not.

Done with release 0.2.0-rc01


move carina-grid into dedicated projcet and setup CI for that

carina-grid should be moved into new project, ideally with saving all history. It should be regular single maven repo where we are going to improve selenium hubs proxy logic to deliver one-click solution to integrate hub with

browserstack
zebrunner
local QPS-HUB

carina-grid moved outside: https://github.com/qaprosoft/carina-grid
also ci configured for new repo


Speed compared to opencv KCF?

Can anyone tell me if this method is faster than opencv KCF? How faster?

我在hisi3531dv200上测试的是opencv的fps是0.8帧左右
用这个有13帧左右

the opencv-contirb-python version is extremely fast(10 microseconds). Far more faster than the cpp version.


Duckduckgo privacy essential extension blocking twitter embedded code

With your DuckDuckGo Privacy Essentials Extension Enabled on Chrome twitter embedded code does not render on a website:
With the DuckDuckGo extension enabled:

With your DuckDuckGo extension disabled:

If you would like the embedded code I can provide it.
Here is where one can get the embedded code: https://publish.twitter.com/#

I'm curious why Twitter has been special cased. It appears that I can still view Instagram embeds, which use roughly the same technique? Is the plan to apply this across the board to other embeds from social media platforms, at least in principle?


RUMM-1488 Support US5 endpoints

What does this PR do?
Support US5 endpoints

Codecov Report

Merging #696 (735ae8c) into master (e64121f) will increase coverage by 0.20%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #696      +/-   ##
============================================
+ Coverage     88.63%   88.83%   +0.20%
- Complexity     1709     1711       +2
============================================
  Files           189      189
  Lines          5645     5648       +3
  Branches        695      695
============================================
+ Hits           5003     5017      +14
+ Misses          407      395      -12
- Partials        235      236       +1

Impacted Files
Coverage Δ

...main/kotlin/com/datadog/android/DatadogEndpoint.kt
0.00% <ø> (ø)

...src/main/kotlin/com/datadog/android/DatadogSite.kt
100.00% <100.00%> (ø)

...g/internal/domain/event/DdSpanToSpanEventMapper.kt
93.88% <0.00%> (-6.12%)
:arrow_down:

...m/internal/domain/scope/ExternalResourceTimings.kt
73.53% <0.00%> (-5.88%)
:arrow_down:

.../android/error/internal/DatadogExceptionHandler.kt
93.10% <0.00%> (-3.45%)
:arrow_down:

...droid/rum/internal/domain/scope/RumSessionScope.kt
97.78% <0.00%> (ø)

...l/net/info/BroadcastReceiverNetworkInfoProvider.kt
79.17% <0.00%> (ø)

.../android/rum/internal/domain/scope/RumViewScope.kt
96.01% <0.00%> (+0.85%)
:arrow_up:

...g/android/rum/internal/domain/scope/RumEventExt.kt
84.55% <0.00%> (+0.91%)
:arrow_up:

.../kotlin/com/datadog/android/rum/RumResourceKind.kt
85.71% <0.00%> (+4.76%)
:arrow_up:

... and 2 more


Feature/allow federated tables gdrive

Fixes #<issue_number_goes_here> (it's a good idea to open an issue first for discussion)

[ ] Tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Greetings, and thanks for the PR!  This looks to be written against a super old version of the codebase.  I kinda doubt rebase is even going to work here.  Would you mind updating to latest, and trying this again?

It looks like we already support passing in custom scopes, so I'm going to close this one out.


Desktop hangs after logging in with kernel >=5.10.76

Describe the bug
A few days ago, my GNOME desktop (tested on both Wayland and X11) started freezing after a few seconds whenever I boot kernel 5.10.76 or newer.
Steps To Reproduce
Steps to reproduce the behavior:

nixos-rebuild switch --upgrade-all to kernel 5.10.76
Reboot
Select the latest boot entry
Log into GNOME
Wait a few seconds (between 10 and 30 or so)

At this point I can still move the mouse pointer around, but the machine does not react to any other mouse/keyboard inputs (such as clicking, Ctrl-Alt-F1, Alt-Tab, etc.).
Expected behavior
The desktop should function as normal.
Logs
From journalctl --boot=-1:
kernel: BUG: unable to handle page fault for address:<PHONE_NUMBER>109530
kernel: #PF: supervisor instruction fetch in kernel mode
kernel: #PF: error_code(0x0010) - not-present page

Additional context
Searching for similar error messages I've seen them pop up for video drivers. lspci lists my video card as "Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5)". I would expect this to be a video driver or kernel regression, but I've not found dupes of this issue after a quick search.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.75, NixOS, 21.05.3926.5ebb1dca9bb (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.16`
 - channels(root): `"nixos-21.05.4051.9e86f5f7a19, home-manager-21.05"`
 - channels(victor): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

I've experienced the same issue on 5.10.77. It was also reported on the amdgpu bug tracker: https://gitlab.freedesktop.org/drm/amd/-/issues/1778 (though that report claims 5.10.76 was still fine)
In any case it should be fixed in Linux 5.10.78 (#145358).

I can confirm having the same issue on 5.10.76 as well.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/crash-when-entering-suspend/16045/2

Thank you @FliegendeWurst; let's see if the next patch version (or nixpkgs 21.11, whichever comes first) fixes it.

Yep, looks like 5.10.78 fixed it!


Playground Zip File not saving images from CreateGroundFromHeightMap

Ref https://forum.babylonjs.com/t/tutorial-101-bugs/6633
PG https://www.babylonjs-playground.com/#CQNGRK
It may be something to do with lines 153 to 155 in https://github.com/BabylonJS/Babylon.js/blob/master/Playground/js/zipTool.js
where only one height map is added from those in textures, ie worldHeightMap.jpg even though there are others, eg heightMap.png, heightMapTriPlanar.png

Same ref there is an extra scene = createScene() in downloaded zip file.


Return the plaintext string, not the HiddenString object

Yup, I figure, the maintainer abandoned it, but at least maybe my patch can be useful to someone :)


What is your idea about managing RDP Session ? and VNC Session ?

No plans to include any remote desktop functionality.


Fixed #24677 -- made TextField to_python return a string

Small fix for #24677. There was no TextField specific test class to went ahead and added one.

Doh! Apologies. Have corrected.

buildbot, add to whitelist.

merged in 19e67c6cd13d6442abb2a6eba1b7fba80dcf5457, thanks!


pagination cache preventing reuse of previous datat

If you add keepUnusedDataFor: 0 to course queries, then the new pagination with useAppDispatch works. However using this approach means refetching previously fetched data ( the client sends new http requests ). I think the issue has to do with shallow copying the new new pagination request, so redux thinks the query got the same input, meaning it will subscribe to the previous query with the same input, therefore not rerendering the ui.


Each Request displays twice

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion

Question

What do you want to know?
Reason and how to fix it

Bug

Which version of SkyWalking, OS and JRE?
Skywalking 6.2.0
SpringBoot 1.5.9
undertow-core 2.0.9

Which company or project?

What happen?
like this, for each request, there are both two traces info
one is /apm/post/{mypath}
another one is /apm/post/1563774429 following
What's more there are some rules

traceId
trace Id of  /apm/post/{mypath} always ends with 000001
While trace Id of  /apm/post/1563774429 always ends auto increasingly from 0003 00005 0007 to 000017

component Type
/apm/post/{mypath} is http-SpringMVC
/apm/post/1563774429 is http-http

Requirement or improvement

Please describe about your requirements or improvement suggestions.

I think I have explained this multiple times. The Simple way, remove your Container plugin(Tomcat/Undertow), because you are using async mode between container and SpringMVC.

I think I have explained this multiple times. The Simple way, remove your Container plugin(Tomcat/Undertow), because you are using async mode between container and SpringMVC.

Thank U. :+1::+1::+1:
Sorry for that I didnt't understand your points before. I will try it later


refactor: include intent confidence score in conversations viewer

the conversations viewer shows confidence next to intent for a user utterance

The entities

Code looks good but there's a little bug: entities are not shown in the UtteranceViewer inside the conversation viewer. Can you take a look and see if it's related to this PR?

Hi, looks like this isn't related to this PR, it's happening in master as well.


HHH-12603 - Contributing using Eclipse Documentation out of Date

This is a continuation of this PR with clean commits and according to the contributing guidelines.
The changes presented firstly are the same as before closing the previous PR. Some changes based on the suggestions stated there will be uploaded ASAP.

@sebersole what do you think of this changes? (f7c7b19 and 6a14235) I left the idea plugin as it's not involved in this ticket.

Thanks @aepedraza ! Could you remove the commits which are not related to the specifics of importing into Eclipse?

Hi @Sanne, right away I'll be on it. In fact, the last commits are mistakenly pushed into this branch. I should do it in another branch related to another ticket. I'm terribly sorry

Done! @Sanne. Now please check if my changes for this ticket are good enough. Thank you so much for warning me about my commits

Thanks! I'll quickly check an import in both Idea and Eclipse then I'll merge it.

merged


Chat-API for WhatsApp

Have You Checked Chat-API?

Easy to Use
One of the best API for WhatsApp with WA2.0 Protocol.
Latest Android Environment
All Required Functions and Features
No More Blocking
Sample Bot
Well Documented

Try Now On
https://chat-api.net

Pretty bad, they won't refund you when you notice it actually doesn't work


SAMZA-2553: Fix NPE when one of the condition value is null

This PR is a Bug fix
Symptom: When one of the value for filter condition is null.
Cause:  Will lead to an NPE
Changes: Added handling for null case
Tests: Added more tests and run current tests end to end.

This change is

@b-slim Please update the description of the ticket following the guide-lines listed here: https://cwiki.apache.org/confluence/display/SAMZA/SEP-25%3A+PR+Title+And+Description+Guidelines . Post that change, I'll merge the PR

@santhoshvenkat1988 Thanks for the pointers.

Thanks for these changes. Merged the PR.


Error building pinpoint-web

Hello, I'm getting the following error when trying to build tag 1.8.5 of pinpoint.
[INFO] --- frontend-maven-plugin:1.5:npm (npm install) @ pinpoint-web ---
[INFO] Found proxies: [xxxxx!{protocol='http', host='xxxxx', port=8080}]
[INFO] Running 'npm install --https-proxy=http://xxxxx:8080 --proxy=http://xxxxx:8080' in C:\dev\git\pinpoint-cb\web\target
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>This module relies on Node.js's internals and will break at some point. Do not use it, and update to<EMAIL_ADDRESS>[WARNING] npm WARN deprecated<EMAIL_ADDRESS>CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
[ERROR] npm ERR! Windows_NT 6.1.7601
[ERROR] npm ERR! argv "C:\\dev\\git\\pinpoint-cb\\web\\target\\node\\node.exe" "C:\\dev\\git\\pinpoint-cb\\web\\target\\node\\node_modules\\npm\\bin\\npm-cli.js" "install" "--https-proxy=xxxxx:8080" "--proxy=xxxxx:8080"
[ERROR] npm ERR! node v5.11.1
[ERROR] npm ERR! npm  v3.9.6
[ERROR] npm ERR! code EMISSINGARG
[ERROR]
[ERROR] npm ERR! typeerror Error: Missing required argument #1
[ERROR] npm ERR! typeerror     at andLogAndFinish (C:\dev\git\pinpoint-cb\web\target\node\node_modules\npm\lib\fetch-package-metadata.js:31:3)
[ERROR] npm ERR! typeerror     at fetchPackageMetadata (C:\dev\git\pinpoint-cb\web\target\node\node_modules\npm\lib\fetch-package-metadata.js:51:22)
[ERROR] npm ERR! typeerror     at resolveWithNewModule (C:\dev\git\pinpoint-cb\web\target\node\node_modules\npm\lib\install\deps.js:490:12)
[ERROR] npm ERR! typeerror     at C:\dev\git\pinpoint-cb\web\target\node\node_modules\npm\lib\install\deps.js:491:7
[ERROR] npm ERR! typeerror     at C:\dev\git\pinpoint-cb\web\target\node\node_modules\npm\node_modules\iferr\index.js:13:50
[ERROR] npm ERR! typeerror     at C:\dev\git\pinpoint-cb\web\target\node\node_modules\npm\lib\fetch-package-metadata.js:37:12
[ERROR] npm ERR! typeerror     at addRequestedAndFinish (C:\dev\git\pinpoint-cb\web\target\node\node_modules\npm\lib\fetch-package-metadata.js:67:5)
[ERROR] npm ERR! typeerror     at returnAndAddMetadata (C:\dev\git\pinpoint-cb\web\target\node\node_modules\npm\lib\fetch-package-metadata.js:121:7)
[ERROR] npm ERR! typeerror     at pickVersionFromRegistryDocument (C:\dev\git\pinpoint-cb\web\target\node\node_modules\npm\lib\fetch-package-metadata.js:138:20)
[ERROR] npm ERR! typeerror     at C:\dev\git\pinpoint-cb\web\target\node\node_modules\npm\node_modules\iferr\index.js:13:50
[ERROR] npm ERR! typeerror This is an error with npm itself. Please report this error at:
[ERROR] npm ERR! typeerror     <http://github.com/npm/npm/issues>
[ERROR]
[ERROR] npm ERR! Please include the following file with any support request:
[ERROR] npm ERR!     C:\dev\git\pinpoint-cb\web\target\npm-debug.log

Build command line
mvn clean package -Dmaven.test.skip=true --projects :pinpoint-web --also-make`

Maven environment
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T20:33:14+02:00)
Maven home: C:\dev\apache-maven-3.5.4
Java version: 1.8.0_73, vendor: Oracle Corporation, runtime: C:\dev\jdk-8u73-windows-x64\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0

Forcing newer versions of node and npm in web/pom.xml seems to solve the issue.
                    <execution>
                        <id>install node and npm</id>
                        <phase>prepare-package</phase>
                        <goals>
                            <goal>install-node-and-npm</goal>
                        </goals>
                        <configuration>
<!--                             <nodeVersion>v5.11.1</nodeVersion> -->
<!--                             <npmVersion>3.9.6</npmVersion> -->
                            <nodeVersion>v10.6.0</nodeVersion>
                            <npmVersion>6.1.0</npmVersion>
                            <workingDirectory>${basedir}/target</workingDirectory>
                        </configuration>
                    </execution>

Is it ok to build with the newer versions of node and npm or is there a way to get it right without editing the pom?

@binDongKim
Please take a look at this issue.

@davide-parini
Thanks for reporting the version issue. The next version will work with the higher version.

What's the problem with that bug ? I encountered the same issue that I complied failed suddenly !

@geekMessi We used quite old(or I would say outdated) version of node and npm in 1.8.5 and there seems to be a compatibility issue with it.

@geekMessi We used quite old(or I would say outdated) version of node and npm in 1.8.5 and there seems to be a compatibility issue with it.

But the version of Pinpoint which I use is 1.7.X .


Renew opendata.scot domain by 3 Nov 2023

@JackGilmore assume this is done? Otherwise...

Yep. Not due again until 3/11/2024. Closing as done.


brew install dep installs go 1.11 even when another go exists

I already have go 1.10.1, and today installed dep by Homebrew.
But it installs another go, and now I have dep 0.5.0, and go 1.10.1 and 1.11.
$ go version
go version go1.10.1 darwin/amd64

$ brew install dep
==> Installing dependencies for dep: go
==> Installing dep dependency: go
==> Downloading https://homebrew.bintray.com/bottles/go-1.11.el_capitan.bottle.tar.gz
######################################################################## 100.0%
==> Pouring go-1.11.el_capitan.bottle.tar.gz
==> Caveats
A valid GOPATH is required to use the `go get` command.
If $GOPATH is not specified, $HOME/go will be used by default:
  https://golang.org/doc/code.html#GOPATH

You may wish to add the GOROOT-based install location to your PATH:
  export PATH=$PATH:/usr/local/opt/go/libexec/bin
==> Summary
🍺  /usr/local/Cellar/go/1.11: 9,273 files, 403.9MB
==> Installing dep
==> Downloading https://homebrew.bintray.com/bottles/dep-0.5.0.el_capitan.bottle.tar.gz
######################################################################## 100.0%
==> Pouring dep-0.5.0.el_capitan.bottle.tar.gz
🍺  /usr/local/Cellar/dep/0.5.0: 7 files, 9.1MB
==> Caveats
==> go
A valid GOPATH is required to use the `go get` command.
If $GOPATH is not specified, $HOME/go will be used by default:
  https://golang.org/doc/code.html#GOPATH

You may wish to add the GOROOT-based install location to your PATH:
  export PATH=$PATH:/usr/local/opt/go/libexec/bin

$ go version
go version go1.11 darwin/amd64

$ cd /usr/local/Cellar/go
1.10.1  1.11

And dep version command returns this:
dep:
 version     : v0.5.0
 build date  : 2018-07-26
 git hash    : 224a564
 go version  : go1.10.3
 go compiler : gc
 platform    : darwin/amd64
 features    : ImportDuringSolve=false

Readme says we can use dep with go 1.9 or newer, but Maybe go 1.10.3 is required for newest dep? If so, It should upgrade existing go or return some kind of error, not installing another one.

brew install --ignore-dependencies go should do the trick.

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!


RHBPMS-4021 - Not able to open BP without browser refresh

@jlindop to test you can follow this video: http://screencast.com/t/bv8luutHA1V
@jlindop I have also tested to make sure this does not affect https://bugzilla.redhat.com/show_bug.cgi?id=1269969 but since you made that change could you also test that one again? Thanks.

@tsurdilo this change seems wrong to me. The parameter needs to be true (as it was before) and hence trigger a reload. If you open the designer and the asset is locked it will be in read-only mode. If the lock goes away (the other user is done editing) a refresh needs to happen to put the designer back in edit mode. This is also the original behaviour (before @jlindop's change).

-1 based on comment above until clarification. Just a reminder that when testing asset locking 2 different users in 2 different browsers need to be used.

@tsurdilo  This change does stop the asset locking working - if two users have a BP open and one of them edits the BP, when this user closes the BP without saving, the other user's editor remains readonly, whereas it should re-open in edit mode.

@tsurdilo When process C is opened, ORYX.READONLY is true at https://github.com/droolsjbpm/jbpm-designer/blob/6.4.x/jbpm-designer-client/src/main/resources/org/jbpm/designer/public/js/Core/main.js#L199
I suspect this is the cause of the problem.
Following the reproduction steps for RHBPMS-4021, if you close process B before opening C, there's no problem. This is because in this case ORYX.READONLY is false at the line above, as you'd expect.


Compiling a sqlite extension for wasm and ffi

I am trying to follow the readme for custom_wasm_build and it has a link that 404 for the setup:
https://github.com/simolus3/sqlite3.dart/tree/rust-wasm-build/sqlite3#compiling
What is the best way to run this on linux or macos? or even docker?
I want to take a custom sqlite-vec extension and compile it for wasm, and then compile it for ios,android,macos,window,linux.
The alternative would be to include the sqlite-vec extension into the build process itself like flutter_sqlite_libs but was also having a hard time getting that working.
Do you have any good docs to look at?

I have fixed the link, it should point to https://github.com/simolus3/sqlite3.dart/tree/main/sqlite3#compiling

What is the best way to run this on linux or macos? or even docker?

On Linux, I'm using
WASI_SYSROOT=/usr/share/wasi-sysroot/ CC=clang cargo build --target wasm32-wasi --release

I think the following should work on macOS once you have set up the dependencies:
WASI_SYSROOT=/opt/wasi-sysroot CC=/opt/homebrew/opt/llvm/bin/clang cargo build --target wasm32-wasi --release

Note that adding the sqlite-vec crate is not likely to work out of the box as the compilation process needs to be configured to explicitly target wasm, the default cc setup doesn't do that.
Given that sqlite-vec is a C library, it may be easier to adapt the existing CMakeLists we have for sqlite3 on the web by changing add_executable in the base_sqlite3_target macro to also include sqlite-vec.c.

and then compile it for ios,android,macos,window,linux.

Instead of customizing the sqlite3 build, it would probably be easier to compile sqlite3-vec as a loadable extension (make loadable in the sqlite-vec repository). Then you're responsible for opening the dynamic library in your app, but can load the extension (I'm doing this on Linux):
void main() {
  sqlite3.ensureExtensionLoaded(SqliteExtension.inLibrary(
      DynamicLibrary.open('/tmp/sqlite-vec/dist/vec0.so'), 'sqlite3_vec_init'));
  final db = sqlite3.openInMemory();
  print(db.select("select vec_f32('[.1, .2, .3, 4]');"));

Those flags are really helpful because I was thinking you needed the wasi sdk via cloning the repo and the version of clang was not working for me, but the LLVM might be the part I was missing for that in the path.
I was actually following the loadable extension route and got it working on MacOS as a DynamicLibrary and worked well. I was having issues including the DLL on windows but that is a separate flutter issue I am investigating.
sqlite-vec does support compiling to wasm but the docs differed and could not see how to include the custom dart helpers for vfs.
https://github.com/asg017/sqlite-vec/blob/main/examples/wasm/README.md
Maybe when I get this figured out we could add it as an example to take any c sqlite extension and compile it for all platforms including web.
Here is the current example I am trying to build:
https://github.com/rodydavis/flutter_sqlite_document_search/blob/main/lib/src/database/connection/native.dart
Works on MacOS with dynamic library but want to convert it to use and compile the c library for all platforms plus wasm.
There are not a lot of docs on this and really appreciate the reply.

I've tried compiling sqlite-vec to WebAssembly in 1ea51fef130a4782dd3486f6bc6cc2c57f6ab4ba (which already requires some hacks because sqlite-vec doesn't properly check for mutexes being omitted). When I've compiled it, the generated WebAssembly module required a WASI import (so probably something in sqlite-vec is using IO functions).

So does that mean it will only work for native platforms and not web?
I am assuming there is no way to use the sqlite-vec wasm module with sqlite3.dart

I've tried compiling sqlite-vec to WebAssembly in 1ea51fe (which already requires some hacks because sqlite-vec doesn't properly check for mutexes being omitted). When I've compiled it, the generated WebAssembly module required a WASI import (so probably something in sqlite-vec is using IO functions). That unfortunately means that it can't be loaded by package:sqlite3 without further modifications to remove the code that causes wasi imports to be added to the WASM module.

This isn't well documented but you can use -DSQLITE_VEC_OMIT_FS=1when compiling sqlite-vec to disable all the bits that use IO functions, which I put it when compiling it to WASM for a specific Go build. That should avoid all the WASI errors
Will also fix up the mutex compile errors

@simolus3 do you think you could try again with v0.1.2-alpha.5? I made some fixes with SQLITE_VEC_OMIT_FS that ensures stdio.h is never used when that compile time option is defined. I also fixed the mutex issues so you can remove those shims
I'd be very surprised to if had to do with strtod(). I also have a build of sqlite-vec that uses WASI for a custom WASM SQLite build in Go, so I'd be surprised if that WASI build works but this one fails
Happy to debug any linker error logs you come across, I'm having trouble running that branch myself

Thanks for all the help! Initially I had no luck with the 0.1.2-alpha.5 release, wasm-objdump -x -j Import sqlite3.wasm still includes the write/seek/close imports.
The link to the WASM build in Go was super helpful though, I realized that I was using some different compiler flags. In particular, -mexec-model=reactor removes the import requirements. I'll just change my build to reflect that build script as close as possible.

Thanks for the help! The SQLite build for Go was a good pointer, I can't reproduce the wasi imports with that build script. One difference is that I'm using a standard clang installation with a wasi sysroot instead of a full wasi SDK, that may also be related to this. I think the problem is most likely coming from something I'm doing wrong in my CMake build, so I've just switched that to custom targets directly invoking clang as a driver.
@rodydavis, you can apply this patch to the current main branch to build a WebAssembly module with sqlite-vec (note that the debug build still includes the wasi imports, but at least they're now removed by DCE in release builds):
diff --git a/sqlite3/assets/wasm/CMakeLists.txt b/sqlite3/assets/wasm/CMakeLists.txt
index c557d78..2b6e10f 100644
--- a/sqlite3/assets/wasm/CMakeLists.txt
+++ b/sqlite3/assets/wasm/CMakeLists.txt
@@ -15,8 +15,14 @@ FetchContent_Declare(
     URL https://sqlite.org/2024/sqlite-autoconf-3460000.tar.gz
     DOWNLOAD_EXTRACT_TIMESTAMP NEW
 )
+FetchContent_Declare(
+  sqlite_vec
+  URL https://github.com/asg017/sqlite-vec/releases/download/v0.1.2-alpha.5/sqlite-vec-0.1.2-alpha.5-amalgamation.tar.gz
+  DOWNLOAD_EXTRACT_TIMESTAMP NEW
+)

 FetchContent_MakeAvailable(sqlite3)
+FetchContent_MakeAvailable(sqlite_vec)

 file(DOWNLOAD https://raw.githubusercontent.com/sqlite/sqlite/master/src/test_vfstrace.c "${CMAKE_BINARY_DIR}/vfstrace.c")

@@ -39,6 +45,7 @@ macro(base_sqlite3_target name debug)
     ${CMAKE_CURRENT_SOURCE_DIR}/os_web.c
     ${CMAKE_CURRENT_SOURCE_DIR}/helpers.c
     ${sqlite3_SOURCE_DIR}/sqlite3.c
+    ${sqlite_vec_SOURCE_DIR}/sqlite-vec.c
   )
   set(flags -Wall -Wextra -Wno-unused-parameter -Wno-unused-function)

@@ -54,8 +61,9 @@ macro(base_sqlite3_target name debug)
     COMMAND ${clang} --target=${triple} -std=c23
       ${flags}
       -o ${clang_output}
-      -I ${PROJECT_SOURCE_DIR} -I ${sqlite3_SOURCE_DIR}
+      -I ${PROJECT_SOURCE_DIR} -I ${sqlite3_SOURCE_DIR} -I ${sqlite_vec_SOURCE_DIR}
       -D_HAVE_SQLITE_CONFIG_H
+      -DSQLITE_VEC_OMIT_FS=1
       -mcpu=generic
       -mexec-model=reactor
       -fno-stack-protector -fno-stack-clash-protection
diff --git a/sqlite3/assets/wasm/os_web.c b/sqlite3/assets/wasm/os_web.c
index 9800443..fc5e490 100644
--- a/sqlite3/assets/wasm/os_web.c
+++ b/sqlite3/assets/wasm/os_web.c
@@ -4,7 +4,11 @@

 #include "bridge.h"
 #include "sqlite3.h"
+#include "sqlite-vec.h"

-int sqlite3_os_init(void) { return SQLITE_OK; }
+int sqlite3_os_init(void) {
+    sqlite3_auto_extension((void (*)(void))sqlite3_vec_init);
+    return SQLITE_OK;
+}

 int sqlite3_os_end(void) { return SQLITE_OK; }
diff --git a/sqlite3/example/web/main.dart b/sqlite3/example/web/main.dart
index f7bf0bf..e97248f 100644
--- a/sqlite3/example/web/main.dart
+++ b/sqlite3/example/web/main.dart
@@ -9,8 +9,7 @@ Future<void> main() async {
   startIndexedDb.onClick.listen((_) async {
     startIndexedDb.remove();

-    final sqlite3 =
-        await WasmSqlite3.loadFromUrl(Uri.parse('sqlite3.debug.wasm'));
+    final sqlite3 = await WasmSqlite3.loadFromUrl(Uri.parse('sqlite3.wasm'));

     print(sqlite3.version);

@@ -19,6 +18,8 @@ Future<void> main() async {
       makeDefault: true,
     );

+    print(sqlite3.openInMemory().select('SELECT vec_debug()'));
+
     sqlite3.open('/database')
       ..execute('pragma user_version = 1')
       ..execute('CREATE TABLE foo (bar INTEGER NOT NULL);')

I've also uploaded a prebuilt module here: https://storage.googleapis.com/simon-public-euw3/assets/sqlite3/wasm/2.4.6/sqlite3_vec.wasm

Thank you so much both!!!

Flutter example updated and works really well!
https://github.com/rodydavis/flutter_sqlite_document_search/commit/631e7ed42e8f108a2551d9bab589f62ab36e30b6

Tried again with the ffi template and had better luck!
https://github.com/asg017/sqlite-vec/pull/119
Still WASM is not built yet, but open to options there


change variable names

address #31
Changes variable name new to newMachine and variable name old to oldMachine.

/test

/ok-to-test

/lgtm


Java: Move ExamplesApp to examples folder

Make sure to add error handling to the example

This will come in a follow-up PR.  This PR is just to move away from the client gradle project and allow users to download from Maven.


command 'slidev.preview-refresh' not found

Hi there :wave:
I've installed globally
npm i -g @slidev/cli

Then the extension but I got this error

Thanks a lot 🤗
Fra

Same here. Installed globally but no preview. I then install manually following this instruction, and it works, and it works in vs code.

This is because Slidev cannot make sure it is a "Slidev Markdown" or a common markdown when there is no package.json indicating this. A simpler workaround could be setting slidev.enabled to true in the workspace settings.

We've rewritten the VSCode extension for Slidev (https://github.com/slidevjs/slidev/pull/1557). Upgrading the VSCode extension to the latest (0.49.1) can fix this issue.


WRP-5951: Refine scrollContainerHandle of useScroll to be clearly understandable

Enact-DCO-1.0-Signed-off-by: Seungcheon Baek<EMAIL_ADDRESS>Checklist

[x] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
scrollContainerHandle has a initial object having several properties, but its current object is replaced by setScrollContainerHandle in the first rendering cycle. So, it looks better to make the initial object empty for better understanding in later visits.
Resolution
Make the initial object empty, then add comments about properties that should be inside scrollContainerHandle.
Additional Considerations
I found that scrollPos does not exist in the handle.
Links
WRP-5951
Comments

Would you please update your branch with the recent develop?


Support network metrics in helm chart

Added a preset property in values that would modify some defaults depending on its value "network" or "application".
For example, the easiest way to get a default network observability stack would be:
cd deployments/
helm install beyla --set preset=network ./helm

⚠ NOTE that the helm chart won't work by default, as network exporter in 1.4.1 does not support Prometheus.
Until we release Beyla 1.5.0, this is the way to give a try to this new helm chart:
cd deployments/
helm install beyla --set preset=network --set image.tag=main ./helm

A couple suggestions for missing configuration, I can do in a follow up PR but will note here. I'll link examples from the beyla-network chart I've been using in deployment_tools. Will migrate to this one when ready.

Add a checksum to the config so that the pods restart when only the config is updated. Example
Allow configuring podAnnotations (e.g. prometheus.io/scrape: true). Example
Allow configuring extra podLabels. Example


End_of_file_solution.java

Solution of a string problem
Issue Id you have worked upon -
#264
Briefly explain your program logic -
firstly don't think it as 3 different lines which required three different variables
think it as one string separated by next line "/n"
i used while loop and check with the help of  hasNextLine() method which returns true if and only if this scanner has another line of input. then print it with the print statement.
Screenshots(Attach 2 screenshots of your own input and output) -

Checklist:
Eg - If your code follow the below guidelines. Kindly change [] to [x]
All the conditions should be fulfilled for considering your code for merging -
[yes] I have mentioned the question as comment in my solution file.
[yes] My code follows the guidelines of this project.
[yes] I have performed a self-review of my own code.
[yes] I have commented my code.
[yes] My code gives the correct output.
[yes] I confirm that I have not copied the code from anywhere. In case its found that I have copied even after successful merge then I can be banned from the repository and hacktoberfest.
[yes] I affirm that I strictly follow contributing guidelines and code of conduct.

Here is the solution.
thank you

@Harsh-bartariya,
Kindly

Add question as first comment to the solution file
Add proper comments to your code
In the checklist replace all "yes" with "x"


Bump deps

@aetxebeste

Let's close this PR because it looks like it contains commits from other people. Also, we're updating this project to Symfony 6.3 (see #1415) so we're going to update all dependencies very soon.


Tree Greenhouse Controller MultiBlock is broken

i cant get the Tree greenhouse Controller to form at all the multiblock seems to be broken i gonna add botany pots (with tweaked Values) or a alterenative for the time being until it is fixed

if you could open a ticket here Discord and show some screenshots we could try to fix it. You are most likely doing something wrong, as there are no others who have reported this behaviour.

its been fixed it was a chunk border issue it was in 4 chunks at the same time


Update biFPN, Support COCO 2017, change Augmentation

Update biFPN
Support COCO 2017
Change Augmentation

Hello @toandaominh1997! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file datasets/__init__.py:

Line 4:32: W292 no newline at end of file

In the file datasets/augmentation.py:

Line 15:80: E501 line too long (80 > 79 characters)
Line 50:80: E501 line too long (108 > 79 characters)
Line 51:80: E501 line too long (130 > 79 characters)

In the file datasets/cocov2.py:

Line 19:11: W291 trailing whitespace
Line 21:1: E302 expected 2 blank lines, found 0
Line 35:18: E221 multiple spaces before operator
Line 35:80: E501 line too long (113 > 79 characters)
Line 45:21: E221 multiple spaces before operator
Line 46:25: E221 multiple spaces before operator
Line 75:1: W293 blank line contains whitespace
Line 76:69: W291 trailing whitespace
Line 79:5: E303 too many blank lines (2)
Line 81:13: E221 multiple spaces before operator
Line 81:80: E501 line too long (98 > 79 characters)
Line 90:80: E501 line too long (96 > 79 characters)
Line 91:20: E221 multiple spaces before operator
Line 105:23: E221 multiple spaces before operator
Line 107:29: E221 multiple spaces before operator
Line 108:24: E221 multiple spaces before operator
Line 120:5: E303 too many blank lines (2)
Line 130:1: E305 expected 2 blank lines after class or function definition, found 1
Line 130:12: E225 missing whitespace around operator
Line 132:35: E251 unexpected spaces around keyword / parameter equals
Line 132:37: E251 unexpected spaces around keyword / parameter equals
Line 132:80: E501 line too long (123 > 79 characters)

In the file datasets/visual_aug.py:

Line 4:32: W291 trailing whitespace
Line 24:70: W291 trailing whitespace
Line 25:80: E501 line too long (91 > 79 characters)
Line 31:80: E501 line too long (89 > 79 characters)
Line 34:80: E501 line too long (88 > 79 characters)
Line 36:80: E501 line too long (101 > 79 characters)
Line 36:102: W291 trailing whitespace
Line 37:80: E501 line too long (109 > 79 characters)
Line 38:80: E501 line too long (140 > 79 characters)
Line 45:80: E501 line too long (93 > 79 characters)
Line 49:1: E305 expected 2 blank lines after class or function definition, found 1
Line 52:80: E501 line too long (153 > 79 characters)
Line 53:1: E302 expected 2 blank lines, found 0
Line 57:80: E501 line too long (111 > 79 characters)
Line 58:29: E231 missing whitespace after ':'
Line 62:1: E305 expected 2 blank lines after class or function definition, found 0
Line 63:28: W292 no newline at end of file

In the file demo.py:

Line 56:22: E128 continuation line under-indented for visual indent
Line 57:22: E128 continuation line under-indented for visual indent
Line 58:22: E128 continuation line under-indented for visual indent
Line 59:22: E128 continuation line under-indented for visual indent
Line 60:22: E128 continuation line under-indented for visual indent
Line 61:22: E124 closing bracket does not match visual indentation

In the file models/bifpn.py:

Line 191:21: E225 missing whitespace around operator
Line 210:22: W292 no newline at end of file

In the file models/efficientdet.py:

Line 30:80: E501 line too long (82 > 79 characters)
Line 31:33: E127 continuation line over-indented for visual indent
Line 32:33: E127 continuation line over-indented for visual indent
Line 35:80: E501 line too long (88 > 79 characters)

In the file models/losses.py:

Line 27:80: E501 line too long (82 > 79 characters)
Line 51:80: E501 line too long (80 > 79 characters)

In the file train.py:

Line 13:80: E501 line too long (99 > 79 characters)
Line 63:80: E501 line too long (121 > 79 characters)
Line 93:80: E501 line too long (173 > 79 characters)
Line 96:80: E501 line too long (110 > 79 characters)
Line 97:80: E501 line too long (120 > 79 characters)
Line 99:80: E501 line too long (176 > 79 characters)
Line 142:80: E501 line too long (80 > 79 characters)
Line 184:80: E501 line too long (97 > 79 characters)

In the file utils/__init__.py:

Line 5:26: W292 no newline at end of file

In the file utils/config_eff.py:

Line 17:2: W292 no newline at end of file


Allow overlap and collide to work with multiple layers

added logic to allow an array of layer strings to be passed to overlap and collide to allow multiple layers to overlap and collide.
Changed a few function signatures so am very open to figuring out a cleaner method so that it's not as breaking of a change.

example of new signature would be:
// Global overlap
overlap('tag1', 'tag2', ['bg', 'game'], (tag1, tag2) => {
  // overlap code
});

// Entity overlap
const player = add([
  sprite('player', '/path/to/sprite.png'),
  layer('game')
]);

player.overlap('spike', ['bg', 'game'], (player, spikeTile) => {
  // overlap code
});

Hmm that'd be a breaking change, I'm thinking about just not checking for layers all together, right now there's no escape hatch except make stuff the same layer, people can always check layers themselves if they wish

Should this be closed as you're not going to go with this strategy?


We should replace the term "core team" in the process doc

As John mentioned, "core team" should be changed.
One option would be to use Eclipse approved committers:
https://projects.eclipse.org/projects/technology.microprofile/who

+1 for project committers
However, we should also count those who have been accepted as committers but have not completed the Eclipse paperwork or have any problems to join the committers' list. In that case, we would need to maitain a separate list of such people n top of the committer list.

In fact, it should be enough to define the term "Core team" in a prominent place and leave it in the document as is, without replacing it everywhere.

I'm fine with MicroProfile Core team. I think Core team should be similar to PMC.

closing as out of date with new process


Add ability to evict a container

Add ability to evict a container when it becomes unusable. This may
happen when the host setup changes after a container creation, making it
impossible for that container to be used or removed.

This may happen when you create a container with a specific runtime in libpod.conf, and later the runtime name is changed in the the conf, with outcome:
$ sudo podman run -d --runtime foo-runtime alpine sleep 12345
add950497c58b4004aee3a6077658615882f8487f9dca4a337fad14c01fb4077

$ sudo sed -i "s/foo-runtime/bar-runtime/" /etc/containers/libpod.conf

$ sudo podman ps -a
ERRO[0000] Error retrieving container add950497c58b4004aee3a6077658615882f8487f9dca4a337fad14c01fb4077 from the database: cannot find OCI runtime "foo-runtime" for container add950497c58b4004aee3a6077658615882f8487f9dca4a337fad14c01fb4077: runtime not available in the current configuration
CONTAINER ID  IMAGE                        COMMAND               CREATED      STATUS                     PORTS                                          NAMES
50c843e037fe  localhost/cups-epson:latest  cupsd -f              2 hours ago  Exited (0) 31 minutes ago  <IP_ADDRESS>:6631->631/tcp, <IP_ADDRESS>:3000->3000/tcp  suspicious_germain
c684f0d469f2  k8s.gcr.io/pause:3.1                               9 days ago   Exited (0) 31 minutes ago  <IP_ADDRESS>:6631->631/tcp, <IP_ADDRESS>:3000->3000/tcp  e812f6be094a-infra

$ sudo podman rm -ff ad
add950497c58b4004aee3a6077658615882f8487f9dca4a337fad14c01fb4077

@mheon I'd like your feedback on this, to see if it is going in the right direction.

@mheon  unrelated to this PR: here c is a pointer, and shadowing does not make sense:
https://github.com/containers/libpod/blob/6f3e7f7eccdfed03d3d617a9040d5e0b844ea637/pkg/adapter/containers.go#L212-L213

/ok-to-test

Thanks a lot @TomSweeneyRedHat, PR force pushed following your recommendations.

@marcov, CI isn't happy yet:
[+0001s] tree is dirty, please remove API.md, then "make varlink_api_generate" and commit changes.
[+0001s]
[+0001s]  M API.md

@marcov, could you squash the commits? In case some don't pass tests, it can make bisecting errors harder.

Just a few nits and the request to not change the existing varlink API. @marcov, can you elaborate a bit why we need new level of removal? I didn't follow previous discussions and will likely miss this information. I feel like just removing the containers with an invalid config by default (i.e., just extend the semantics of removal).

Hi @vrothberg.
Problem: containers as stored in the state DB with their config, containing among other things information about the OCI runtime name and paths. If the OCI runtime name changes in libpod.conf, of if the OCI runtime path does not point to the original runtime, then you can't do much with this container, apart from removing it.
What the evict API does is:

retrieve from the state a container ID (instead of a *Container).
remove from the state and from the storage that container ID with minimal checks.

Compared to the remove API, the evict does not try to terminate the processes associated with the container, since it's not possible to interact with the OCI runtime.

@marcov, thanks for the details!

Compared to the remove API, the evict does not try to terminate the processes associated with the container, since it's not possible to interact with the OCI runtime.

That's quite a difference. For the Varlink API, I suggest adding a EvictContainer(...) function. On the CLI, I prefer an podman rm --evict flag, rather than mixing that with force - especially since containers are not stopped.

@vrothberg thanks for the review. I squashed and applied the updates.

Compared to the remove API, the evict does not try to terminate the processes associated with the container, since it's not possible to interact with the OCI runtime.

That's quite a difference. For the Varlink API, I suggest adding a EvictContainer(...) function.

So you're suggesting to:

add in pkg/varlinkapi/containers.go a func (i *LibpodAPI) EvictContainer(...)
have that called from pkg/adapter/containers_remote.go:RemoveContainers(...) based on the passed flag?

On the CLI, I prefer an podman rm --evict flag, rather than mixing that with force - especially since containers are not stopped.

Got it, the -ff was suggested a @mheon, I am fine both ways. Using -ff has the advantage of having to remember one less flag :-)

So you're suggesting to:
1. add in `pkg/varlinkapi/containers.go` a `func (i *LibpodAPI) EvictContainer(...)`

2. have that called from `pkg/adapter/containers_remote.go:RemoveContainers(...)` based on the passed flag?

On the CLI, I prefer an podman rm --evict flag, rather than mixing that with force - especially since containers are not stopped.

Got it, the -ff was suggested a @mheon, I am fine both ways. Using -ff has the advantage of having to remember one less flag :-)

I would keep evict and remove separate on both, the API level and the CLI. The semantics seem too different to mix them together. My most important concern is to not break the existing API and I will leave the decision regarding -ff vs. --evict to @mheon.

Rebased to resolve conflicts and added varlink API EvictContainer.

Going to give this another look this afternoon or tomorrow - sorry for delays, been very busy over here

Overall direction looks solid. Would be nice to have some unit tests for the new State functions in state_test.go.

sorry for being late at the review.
Is the new flag useful only in the case a runtime is not available anymore or are there other cases?
I'd expect -f to behave like that by default.  It should try to cleanup as much as possible without the need of another flag.

Is the new flag useful only in the case a runtime is not available anymore or are there other cases?

@giuseppe as of now eviction would only be used if the container runtime is unavailable or has changed, while the -f flag is, according to the help, used to force stopping a container before remove.

@vrothberg, @jwhonce, @mheon: I addressed your latest comments with the last push.

@marcov, I'll take a look now. The CI errors seem legit as the linter isn't happy. You can run make validate locally to check.

@giuseppe as of now eviction would only be used if the container runtime is unavailable or has changed, while the -f flag is, according to the help, used to force stopping a container before remove.

can't we change the documentation and include this case as well?  It still seems like a very specific corner case to me, that can be handled with -f instead of another flag.

I don't think this new evict functionality should fall under --force; it's definitely a step beyond.
Whether we want -ff or --evict is still up for debate, but it seems like --evict is leading?

I would through my vote in for --force or --force --force.  I still see this as something that will just aggravate the user.  IE he tells podman to remove the container and it comes back and says,  I can't because it is in a weird state.  Then the user does a --force --force, and it removes it.  I as a user would react with WTF?

I would through my vote in for --force or --force --force. I still see this as something that will just aggravate the user. IE he tells podman to remove the container and it comes back and says, I can't because it is in a weird state. Then the user does a --force --force, and it removes it. I as a user would react with WTF?

And what if I changed the runtime crun and want to only clean up all old containers that ran with runc? The thing is that running -ff shows an inherently different behaviour, as it only removes containers with an invalid runtime and leaves the others untouched - no stopping etc. So it's not a functional or semantic extension to -f, in fact the sets of removed containers have zero overlap.
I wouldn't know how to explain the behaviour of -f vs -ff without starting the sentence with: "I know it sounds confusing ..." :^) All my confusion would disappear with a separate flag.

@vrothberg Not sure --evict does a better job of explaining this either.
Is the use case?
As a user I am switching from runc to crun, I have 2 containers which were created with runc and 3 created with crun.  I want to remove the runc containers, and I get an error.
podman rm RUNCCID1 RUNCCID2
Error: Runtime no longer exists
Now I say:
podman rm --force RUNCCID1 RUNCCID2
Error: Runtime no longer exists
So now I have to find and try:
podman rm --evict RUNCCID1 RUNCCID2
Success

@rhatdan, yes that's one use case. I think that --force should also --evict containers as invalid configs shouldn't be special cased. However, --evict is still a nice way of cleaning up those containers (and only those).

FWIW, I concur with @vrothberg's last note.  --force should do current functionality and also --evict.  It's our big sledge hammer.  --evict would handle just those particular containers.

@vrothberg @TomSweeneyRedHat  note however that as of now podman -a --evict would not work, as this would require a duplicate of GetContainersByContext returning a set of IDs instead of Containers.

I've tried these steps with Docker:

add a runtime to docker,
create a container $CTR_ID
remove the runtime.
docker rm -f $CTR_ID removes the container without complaining

Similarly, --force for 'rm has a similar meaning of attempting deleting as much as possible without bothering the user.
If we want to treat "containers without a working runtime" differently, I think we can add a new filter to ps so the user can do something like podman ps -q --filter runtime-status=not-existing | xargs podman rm -f

I tend  to agree with @giuseppe, the force word can refer both to running and not usable containers, and it's just easier for the users to use --force in both situations.

Pushed unit tests for the new functions in state.go

Put me in the camp for just using --force.

So, me, @giuseppe and @rhatdan likes --force
@vrothberg and @TomSweeneyRedHat wants --evict
@mheon is for --force --force
Can I go and update the code with the most voted option?

So, me, @giuseppe and @rhatdan likes --force
@vrothberg and @TomSweeneyRedHat wants --evict
@mheon is for --force --force
Can I go and update the code with the most voted option?

I think there's a misunderstanding. In https://github.com/containers/libpod/pull/3549#issuecomment-517660899 I actually meant to go with --force only :) However, if we want to have a dedicated --evict then --force should imply doing --evict.
I believe that @TomSweeneyRedHat is on board with that as well.

Thanks @vrothberg!

Just to be sure we're clear.  I'm good with the --evict option which would get rid of the unusable containers.  When the --force is used it should do the evict functionality too, regardless of the --evict option being present.

I have the impression that the added value of introducing an extra --evict flag is limited, --force can remove unusable containers, and I don't see any apparent disadvantage of using the flag for both use cases.

pushed a temp commit to use --force flag for eviction too. @TomSweeneyRedHat I'd appreciate your review for the text changes.

@marcov The doc part looks fine and I'm fine moving forward with this as is if you can get the uhappy tests to complete.
Personally, I'd like to have the --evict flag still to remove just unusable images.  Otherwise if the user wants to remove just the unusable ones, they'd have to do podman rm -f id1 id2 id3 ...  rather then podman rm --evict.  But that's probably a small use case.

An incredibly small use case.  Not worth worrying about.
Lets stick with --force and get this merged.

We should also remove all changes to the varlink API etc. since we go with --force.

@vrothberg: if I remove the varlink API, I end up not being able to call the EvictContainer method from  pkg/adapter/containers_remote.go : RemoveContainers. Is there a trick to have to solve this?

@vrothberg: if I remove the varlink API, I end up not being able to call the EvictContainer method from  pkg/adapter/containers_remote.go : RemoveContainers. Is there a trick to have to solve this?

Since we want rm --force to also evict a container, I assumed we don't need to expose EvictContainer anymore. Do still need that?

I tried to remove that from cmd/podman/varlink/io.podman.varlink and b/pkg/varlinkapi/containers.go, but then podman-remote fails to build because of a call to iopodman.EvictContainer in pkg/adapter/containers_remote.go : RemoveContainers. I'm not sure how to handle that.

I tried to remove that from cmd/podman/varlink/io.podman.varlink and b/pkg/varlinkapi/containers.go, but then podman-remote fails to build because of a call to iopodman.EvictContainer in pkg/adapter/containers_remote.go : RemoveContainers. I'm not sure how to handle that.

We need to revert the changes to cmd/podman/varlink/io.podman.varlink and the references to it in the code to get rid of the compilation error.

@vrothberg, if I do like you said, then how can I call iopodman.EvictContainer here?
https://github.com/containers/libpod/blob/128a1707f7d9e8df648a6ba353bfa16b9bef2431/pkg/adapter/containers_remote.go#L323-L339

Why are we trying to force the Varlink API to follow CLI conventions? These
are separate operations and the API should treat them as such, even if we
decide to conflate in the command line.
On Mon, Aug 19, 2019, 10:03 Marco Vedovati<EMAIL_ADDRESS>wrote:

@vrothberg https://github.com/vrothberg, if I do like you said, then
how can I call iopodman.EvictContainer here?
https://github.com/containers/libpod/blob/128a1707f7d9e8df648a6ba353bfa16b9bef2431/pkg/adapter/containers_remote.go#L323-L339
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containers/libpod/pull/3549?email_source=notifications&email_token=AB3AOCDU523ZRETR6U4OP33QFKR25A5CNFSM4H7RUQJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4TBKGI#issuecomment-522589465,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB3AOCG455MHJDMG2GUSW4DQFKR25ANCNFSM4H7RUQJQ
.

Any update on this PR?

I am still willing to have this merged, just let me know if there's something to change.

I think we're relatively close - I'll do another review pass on Monday.

@marcov could you please rebase this PR?

Rebased

Tests aren't happy yet. @marcov, once it's green we can merge it :)
@mheon, can you do another review?

Failures looked unrelated to a first glance. I've rebased and let's see...

@marcov, the error seems to be introduced with this PR. Running go test -v github.com/containers/libpod/libpod will report a breaking unit test.

Thank you @vrothberg, a mere glance was not enough :laughing:

Ok, tests now are better. I don't think the only test failing is related to this PR (hopefully I'm not wrong again)

Ok this needs a review by @mheon and then we can merge.

I think we have some unsettled debate about how and when to call this - but that can happen separately.
/lgtm

(still needs /approve)

Oops
/approve


Test dub with DMD 2.067 beta

@MartinNowak : http://downloads.dlang.org/releases/2.x/2.064/ , not 2.064.2 (I don't understand it either...)

I made a fix already, supposed to be deployed to Travis today.


fix: Do not clear state when answering 'no' in prompt

Closes https://github.com/meltano/meltano/issues/8114

My bad! :sweat_smile: :sweat_smile: :sweat_smile:

You probably noticed, but this actually affected set, copy and move too.


Encoding issue in blueprint.html

If you put accent in blueprint.html, the the encoding is not correct.

Thanks for reporting this issue. At the moment the serve command uses the HttpServer from Java's standard library. Fixing this shouldn't be too difficult, but I'm considering to use Armeria to serve the tiles. In the future, Armeria would allow to create additional web services (for localization, search, routing, etc.) with gRPC and to generate web and mobile SDKs. As for now, the release is about 28MB, and it gets to about 45MB with armeria. Would you consider this an issue?

Would you consider this an issue?

Not at all, I think Armeria is a great choice.

@fgravin Great, I added ne

The issue has been fixed in the latest release.


NerdTREE causing the cursor to disappear when used with Solarized Colors and GVim

Self-Diagnosis

[x] I have searched the issues for an answer to my question.
[x] I have reviewed the NERDTree documentation. :h NERDTree
[x] I have reviewed the Wiki.
[x] I have searched the web for an answer to my question.

Environment (for bug reports)

[x] Operating System: GNU/Linux (KDE neon
[x] Vim/Neovim version :echo v:version: 801
[x] NERDTree version, found on 1st line in NERDTree quickhelp ?: 6.9.10
[ ] vimrc settings

[ ] NERDTree variables

Other NERDTree-dependent Plugins

[ ] jistr/vim-nerdtree-tabs
[ ] ryanoasis/vim-devicons
[ ] tiagofumo/vim-nerdtree-syntax-highlight
[ ] Xuyuanp/nerdtree-git-plugin
[ ] Others (specify):

[x] I've verified the issue occurs with only NERDTree installed.

Steps to Reproduce the Issue

Install Solarized Colorscheme
Open GVim maximized
Start NerdTREE with :nerdtreetoggle
Exit NerdTree and try to move cursor on the editing window

Current Result (Include screenshots where appropriate.)
The cursor disappears but remains functional
Expected Result
The cursor should work and appear normally as it does when any other colorscheme (e.g. Gruvbox) is used
Edit
Same phenomenon started with GruvBox too

Can you provide a minimal .vimrc file that produces the issue? Make sure to identify where you obtained your plugins.

@PhilRunninger The only option related to NERDTree in my .vimrc file is:
nmap <C-l> :NERDTreeToggle<CR>
Some GVim options are there too like
set guioptions-=T
set guioptions-=R

Please let me know if you want to know any other options, or whether I should provide my full .vimrc file as it is only 22 lines

Go ahead and share your .vimrc, although, I'm not sure it will be all that helpful. I don't have access to a Linux box to test on, so I'd be just guessing.
I really think this is a bug in Vim. NERDTree doesn't do anything to change the cursor's appearance. I found this post - https://stackoverflow.com/questions/1025762/cursor-disappears-in-vim-when-switching-windows-between-vertical-and-horizontal - from a few years back. Some of the suggestions in it may still be relevant.
There also is an issue in the the Vim project with several contributors diagnosing the problem and offering suggestions: https://github.com/vim/vim/issues/480

Yes, this really seem like a Vim bug. I added set guioptions-=L (which removes the left scrollbar) in my .vimrc according to the StackOverflow thread which you shared. This might be as NERDTree also opens a window to display its content and I don't use many windows in my workflow, and that's why I didn't notice it happening with any other window.
I'll close this issue here then, as it doesn't belong to NERDTree. Thank you for reply.


[POC] add support to ubuntu 16

Description
This simple commit provide support to install Licode into ubuntu 16.
I simply modified openjdk to a newer version, supported both on ubuntu 14.04 and 16.04 and I made a patch to support the new libvpx library used by ubuntu 16 to compile libav 11.8.
Tested on both ubuntu 14.04 and 16.04 amazon EC2 and seems working with no problem
Add a short description here, please.
Add support to ubuntu 16.04
[] It needs and includes Unit Tests
[] It includes documentation for these changes in /doc.

yeah see: https://github.com/lynckia/licode/pull/1210 for an updated version


ARMv7 version

Hi.
Do you plan to provide an ARMv7 docker version of zeronsd ? I would be very interested.
Thank you.

Hi!
Yes, support is planned... I just got myself a PI to test it on.
Stay tuned =)
-s
On Tue, Jan 10, 2023 at 10:01 AM Gandulf78 @.***> wrote:

Hi.
Do you plan to provide an ARMv7 docker version of zeronsd ? I would be
very interested.
Thank you.
—
Reply to this email directly, view it on GitHub
https://github.com/zerotier/zeronsd/issues/202, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAQ3THKHRN4TFXFMV6KVY3WRUQOHANCNFSM6AAAAAATWOEYHA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi!
Yes, support is planned... I just got myself a PI to test it on.
Stay tuned =)

Hi. Would you have an ETA by any chance?
Thanks.


Form field validation scroll with fixed nav

How can implementation be modified to ensure the invalid field does not hide behind a fixed nav?  See here:  https://getbootstrap.com/docs/4.0/components/forms/#browser-defaults
Scroll down so that the form input are behind the nav, and click submit.  The invalid field is then behind nav.
Also, when using novalidate, scrolling to the invalid field is also removed/disabled, so the end user has no notification of what went wrong, in the case of the form field being out of view.
Think of a long form, and the user has scrolled down to click submit.  If there is an invalid field, the form scrolls to the input (as long as not using novalidate), but it's behind the fixed nav.  I would think by default that bootstrap would scroll to a viewable area, not behind some other layer.
Any ideas?

Only way to adjust this is to try to style those alerts in Chrome (not cross browser friendly) or to change the z-index of the navbar. Not much we can do about it I'm afraid though given it's the native browser validation tooltip.


Remove version from soroban-cli install instruction

What
Remove version from soroban-cli install instruction.
Why
Most of the time people should install the latest version.
We're failing to keep this updated which is harming developer experience.
Now that we're releasing stable versions, it's very unlikely someone would have a problem installing a newer soroban-cli.
There will be a window for new protocol releases where the cli could support features that work on a local or test network, but not on the pubnet network, but I think we'd be introducing them in a way that the CLI would work for both protocol versions.
We used to need to specify a version because we were releasing pre-releases that can't be selected automatically. That's no longer the case.

Preview is available here:http://soroban-docs-pr758.previews.kube001.services.stellar-ops.com/


deep_clone has issues with acts_as_tenant gem how we can make it work ?

deep_clone has issues with acts_as_tenant gem how we can make it work ?

I don't think that deep_cloneable is the root cause of your issue. But there's really nothing for me to work with here. Closing due to lack of information.


Python extension keeps requiring Reload

Issue Type: Bug
OS : Linux Ubuntu 14.04.5 LTS through remote login from Windows 10
Extension : Python [2020.5.86806 (10 June 2020)]
Symptoms : Suddenly started requiring Reload and kept requiring it
Fix : Uninstall and Install the extension
When I remote logged in Ubuntu from Windows PC, the Python extension required Reload. This extention had been working without issue, at least for a couple of weeks.
Though I clicked Reload and VSCode remote-logged in Ubuntu back again, the extension was still saying "Reload required." I repeated reloads a few times, but, it kept requiring Reload.
I just Uninstalled the extension and Installed it by myself. Then, the extension stopped asking reload.
Extension version: 2020.5.86806
VS Code version: Code 1.43.0 (78a4c91400152c0f27ba4d363eb56d2835f9903a, 2020-03-09T19:47:57.235Z)
OS version: Windows_NT x64 10.0.17134
Remote OS version: Linux x64 3.11.0-12-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4910MQ CPU @ 2.90GHz (8 x 2893)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.91GB (24.28GB free)

Process Argv
-n

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: pttools

OS
Linux x64 3.11.0-12-generic

CPUs
Intel(R) Core(TM) i7 CPU         975  @ 3.33GHz (8 x 1600)

Memory (System)
19.60GB (16.72GB free)

VM
0%

I am realizing that this happens when I switch Windows 10 PCs to remote-ssh into the same Ubuntu system.
I mean, when I exit from the remote-ssh session with the Ubuntu on one Windows 10 and then I remote-ssh into the same Ubuntu from another Windows 10, this Python extension reload loop seems happening.
Is this expected behavior?

@vjou The extension may require reload after an update. But this is controlled entirely by VS Code or vscode server (for remote). The extension itself does not control this behavior. The scenario you mentioned is possible if VSCode server has the extension loaded and not all versions were removed for some reason. Try this, uninstall the extension, go to either ~/.vscode/extensions/ or ~/.vscode-server/extensions/ (it should be something like ~/.vscode*/extensions). Check if there are any instances of ms-python.python, delete all of them. Then install the python extension again. This should resolve the issue.

I think I figured. The issue seemed the old version VS Code had an issue with its update processing. After I manually updated the older VS Code (ver. 1.43.0) to 1.47.1, the extension reload loop was gone on both of the Windows PCs.
Here is a little bit of detail about my troubleshooting:

I noticed there were two Python extensions displayed in EXTENSIONS on one VS Code (ver. 1.43.0).
"LOCAL-INSTALLED" was version "ms-python.python-2020.5.86806" and
"SSH:***-INSTALLED" was "ms-python.python-2020.6.91350".
I repeated to uninstall and install the LOCAL-INSTALLED Python extension. But, every time when I reloaded VS Code, the old version "ms-python.python-2020.5.86806" kept coming back.
I tried to use "Install Another Version..." option on the extension a few times, but, it just gave me a message something like "server 404".
Then, I noticed the version of VS Code itself was 1.43.0 and much older than one on another Windows PC. Somehow, the old VS Code stopped automatic update checking.
I did Check for Updates and the VS Code found an update.
Though it failed to update a few times, the VS Code finally made updated to 1.47.1.
And then, new VS Code updated the Python extension to the latest one by itself.

So, I guess my VS Code version 1.43.0 had an issue with its update processing.

Thanks for the detailed trouble shooting steps. In case you run into "server 404" when switching versions, you can do this manually by downloading the package from this location https://github.com/microsoft/vscode-python/releases and install using the "Install from VSIX..." option.

@vjou The extension may require reload after an update. But this is controlled entirely by VS Code or vscode server (for remote). The extension itself does not control this behavior. The scenario you mentioned is possible if VSCode server has the extension loaded and not all versions were removed for some reason. Try this, uninstall the extension, go to either ~/.vscode/extensions/ or ~/.vscode-server/extensions/ (it should be something like ~/.vscode*/extensions). Check if there are any instances of ms-python.python, delete all of them. Then install the python extension again. This should resolve the issue.

surely is the solution, Thanks


Kube UI not working

I get this when I spin up a new cluster.
Internal Server Error (500)
Get https://<IP_ADDRESS>:443/api/v1/replicationcontrollers: dial tcp <IP_ADDRESS>:443: getsockopt: connection refused

Ansible version (1.9.4):
Python version (2.79):
Git commit hash or branch: a86bf60487183a05692a534f66da990e325717c1
Cloud Environment:  Vagrant
Terraform version (<IP_ADDRESS>):

I am also having a problem with the UI on AWS. But, instead of the 500 error, I am getting a 504 Gateway Time-out error from the nginx proxy.

@ryane I also get that, I think it's something to do with the kubeworker. Sometimes it comes up other times not really.

This appears to be the source of the problem (at least on AWS):
[Service]
ExecStart=/usr/bin/kubelet \
  --api-servers=http://localhost:8085 \
  --register-schedulable=false \
  --hostname-override={{ ansible_hostname }} \
  ...

On AWS, ansible_hostname ends up being something like ip-10-1-1-31. But, this is not resolvable within the cluster:
$ cat /etc/hostname
ip-10-1-1-31.ec2.internal

$ host ip-10-1-1-31.ec2.internal
ip-10-1-1-31.ec2.internal has address <IP_ADDRESS>

$ host ip-10-1-1-31
Host ip-10-1-1-31 not found: 3(NXDOMAIN)

Open questions:

Do we need the hostname-override option? What hostname is used without it? If it is needed, is there a safer variable (inventory_hostname, maybe?) that we can use instead of ansible_hostname?

Why isn't ip-10-1-1-31 resolvable in DNS?
$ sudo yum list installed mantl-dns -q
Installed Packages
mantl-dns.x86_64                                                                                1.1.0-1.centos                                                                                @asteris-mantl-rpm

$ cat /etc/resolv.conf.mantl-dns
# this config installed by mantl-dns

# search is added here so that the system can address nodes by their simplest
# name (x.node.consul becomes x.node or simply x.) This will work for service
# addressing as well, so you can use y.service instead of y.service.consul
options ndots:2
search node.consul consul
nameserver <IP_ADDRESS>

$ cat /etc/resolv.conf.masq
; generated by /usr/sbin/dhclient-script
search ec2.internal
nameserver <IP_ADDRESS>

#1374 resolves the problem without any other changes. And, perhaps might fix other things (#1195). Is setting the hostname this way a good option? Will it cause other problems?

ping @BrianHicks @zogg @stevendborrelli

The Kubernetes integration brings in some older code that the core team didn't write. It's entirely possible that I missed something when upgrading it. #1374 seems like the best solution, it does need to be resolvable.

I'm thinking we should also change the service file to use inventory_hostname also so that it is consistent.
Any idea why DNS is not working for the internal AWS hostname?

Yes, sorry, that was my intention: we should mirror the behavior of the
other PR.
As for the DNS failure, that’s bizarre. Have you tried putting DNSMasq
into debug mode and watching as you try to resolve? It’s got pretty
good logging for dealing with these kinds of issues.

$ sudo /usr/sbin/dnsmasq -d
dnsmasq: started, version 2.66 cachesize 150
dnsmasq: compile time options: IPv6 GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth
dnsmasq: using nameserver <IP_ADDRESS>#153 for domain cluster.local
dnsmasq: using nameserver <IP_ADDRESS>#8600 for domain consul
dnsmasq: reading /etc/resolv.conf.masq
dnsmasq: using nameserver <IP_ADDRESS>#53
dnsmasq: using nameserver <IP_ADDRESS>#153 for domain cluster.local
dnsmasq: using nameserver <IP_ADDRESS>#8600 for domain consul
dnsmasq: read /etc/hosts - 12 addresses
dnsmasq: read /etc/hosts - 12 addresses
dnsmasq: read /etc/hosts - 12 addresses
dnsmasq: time<PHONE_NUMBER>
dnsmasq: cache size 150, 0/0 cache insertions re-used unexpired cache entries.
dnsmasq: queries forwarded 2, queries answered locally 1
dnsmasq: server <IP_ADDRESS>#8600: queries sent 2, retried or failed 0
dnsmasq: server <IP_ADDRESS>#153: queries sent 0, retried or failed 0
dnsmasq: server <IP_ADDRESS>#53: queries sent 0, retried or failed 0

Is it that queries are not getting forwarded to the internal dns servers (only consul) for some reason?
On GCE, I see something like this in the logs:
dnsmasq: server <IP_ADDRESS>#8600: queries sent 3, retried or failed 0
dnsmasq: server <IP_ADDRESS>#153: queries sent 0, retried or failed 0
dnsmasq: server <IP_ADDRESS>#53: queries sent 12, retried or failed 0

Is that when you try and resolve {ip}.ec2.internal? IIRC debugging mode logs every query, the results, and where they came from. Did you try that?

RE: https://github.com/CiscoCloud/mantl/issues/1346#issuecomment-213456944
ah! My cluster is down now but I'll try that in a bit.

$ sudo /usr/sbin/dnsmasq -d -q
dnsmasq: started, version 2.66 cachesize 150
dnsmasq: compile time options: IPv6 GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth
dnsmasq: using nameserver <IP_ADDRESS>#153 for domain cluster.local
dnsmasq: using nameserver <IP_ADDRESS>#8600 for domain consul
dnsmasq: reading /etc/resolv.conf.masq
dnsmasq: using nameserver <IP_ADDRESS>#53
dnsmasq: using nameserver <IP_ADDRESS>#153 for domain cluster.local
dnsmasq: using nameserver <IP_ADDRESS>#8600 for domain consul
dnsmasq: read /etc/hosts - 12 addresses
dnsmasq: read /etc/hosts - 12 addresses
dnsmasq: read /etc/hosts - 12 addresses
dnsmasq: query[A] ip-10-1-1-125.node.consul from <IP_ADDRESS>
dnsmasq: forwarded ip-10-1-1-125.node.consul to <IP_ADDRESS>
dnsmasq: query[A] ip-10-1-1-125.consul from <IP_ADDRESS>
dnsmasq: forwarded ip-10-1-1-125.consul to <IP_ADDRESS>
dnsmasq: query[A] ip-10-1-1-125 from <IP_ADDRESS>
dnsmasq: config ip-10-1-1-125 is NODATA-IPv4
dnsmasq: query[AAAA] ip-10-1-1-125 from <IP_ADDRESS>
dnsmasq: config ip-10-1-1-125 is NODATA-IPv6
dnsmasq: query[MX] ip-10-1-1-125 from <IP_ADDRESS>
dnsmasq: forwarded ip-10-1-1-125 to <IP_ADDRESS>
dnsmasq: time<PHONE_NUMBER>
dnsmasq: cache size 150, 0/0 cache insertions re-used unexpired cache entries.
dnsmasq: queries forwarded 3, queries answered locally 2
dnsmasq: server <IP_ADDRESS>#8600: queries sent 2, retried or failed 0
dnsmasq: server <IP_ADDRESS>#153: queries sent 0, retried or failed 0
dnsmasq: server <IP_ADDRESS>#53: queries sent 1, retried or failed 0
dnsmasq: Host                                     Address                        Flags     Expires
dnsmasq: localhost.localdomain                    ::1                            6F I   H
dnsmasq: localhost.localdomain                    <IP_ADDRESS>                      4F I   H
dnsmasq: resching-aws-control-03                  <IP_ADDRESS>                     4FRI   H
dnsmasq: resching-aws-kubeworker-001              <IP_ADDRESS>                     4FRI   H
dnsmasq: resching-aws-control-02                  <IP_ADDRESS>                     4FRI   H
dnsmasq: resching-aws-control-01                  <IP_ADDRESS>                     4FRI   H
dnsmasq: resching-aws-worker-002                  <IP_ADDRESS>                     4FRI   H
dnsmasq: resching-aws-worker-003                  <IP_ADDRESS>                     4FRI   H
dnsmasq: resching-aws-worker-001                  <IP_ADDRESS>                     4FRI   H
dnsmasq: resching-aws-worker-004                  <IP_ADDRESS>                      4FRI   H
dnsmasq: localhost6.localdomain6                  ::1                            6F I   H
dnsmasq: localhost4                               <IP_ADDRESS>                      4F I   H
dnsmasq: localhost                                ::1                            6FRI   H
dnsmasq: localhost                                <IP_ADDRESS>                      4FRI   H
dnsmasq: resching-aws-edge-01                     <IP_ADDRESS>                     4FRI   H
dnsmasq: localhost6                               ::1                            6F I   H
dnsmasq: localhost4.localdomain4                  <IP_ADDRESS>                      4F I   H
dnsmasq: resching-aws-kubeworker-002              <IP_ADDRESS>                     4FRI   H

$ dig ip-10-1-1-125 @<IP_ADDRESS>

; <<>> DiG 9.9.4-RedHat-9.9.4-29.el7_2.3 <<>> ip-10-1-1-125 @<IP_ADDRESS>
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21487
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ip-10-1-1-125.                     IN      A

;; ANSWER SECTION:
ip-10-1-1-125.ec2.internal. 20  IN      A       <IP_ADDRESS>

;; Query time: 1 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Fri Apr 22 16:00:33 UTC 2016
;; MSG SIZE  rcvd: 71

I guess the internal aws nameservers just don't resolve the short ip-10-1-1-125 hostnames. Do you interpret that the same way?

The nameservers don't resolve it because dig doesn't respect search paths. And in this case, even with +search dig would be reading from /etc/resolv.conf instead of /etc/resolv.conf.masq so it's not a fair test.
I do see that dnsmasq forwarded the IP to the upstream nameserver in the log:
dnsmasq: forwarded ip-10-1-1-125 to <IP_ADDRESS>

But it doesn't have any information about how it applied the search paths, which are clearly not being applied if the query is failing.
This is turning into two different issues at this point. We need to change the Kubelet hostname to the inventory name instead of the IP, but we also need to fix this search config in dnsmasq.

ah, makes sense.
We already have #1376 for the kubelet hostname which can hopefully close out this issue (although the AWS problem looks to be slightly different than the problem @andreimc is experiencing on Vagrant) . I opened #1377 for the dnsmasq issue.

@ryane I am happy if you close this issue I think if the search configuration is updated it will also work in Vagrant

After applying 1374, I can bring up that endpoint.

aws problem resolved in #1374. DNS fix is tracked in #1377. Kubernetes on Vagrant issues are being tracked in #1365. going to close this one


Imrpove code for App.

Code for the App is pretty organized now after migrating to Vue and implementing the state management for the app. I don't think we need this anymore.


Support for definining which files to copy

Currently plugin copies all files that are referred as relative links (starting with ./ or ../). For images this works nicely and images are at the generated documentation. For other files like MDs or code examples coped files are not necessarily most user friendly.
README states that only images are copied, so I think it should be default action. If something else is needed, user could provide own filter. So default filtering value would be "all image extensions" (or normal ones), and if user would also want to get e.g. ts-files filter need to contain md and also those image extensions. So user given filter would fully override default one, not append to it.

Hi @Hi-Fi,
Thanks for the feature request.
It was added to version 1.0.5.
For complete functionality, please see the readme file.
In short, the default is to copy image references ![label](./path/image.png). But you can enable all references with setting the onlyImages option. To fine tune what to include/exclude you can set regexes in the options.
{
  "copyAssets": {
    "onlyImages": false,
    "include": [".(png|md)\\)$"],
    "exclude": ["\\(.*?exclude/.*?\\)$"]
  }
}

If you have any issues with this solution, please reopen the ticket.

For some reason I get error when trying to configure that copyAssets:
npx typedoc --logLevel Verbose
Loaded plugin @droppedcode/typedoc-plugin-copy-assets
[@knodes/typedoc-plugin-pages] ⇒ Using plugin version 0.23.1
Loaded plugin @knodes/typedoc-plugin-pages
Loaded plugin typedoc-plugin-replace-text
error Tried to set an option (copyAssets) that was not declared.

Can you check that npm installed the 1.0.5 version of the plugin?

I'm quite sure it was, that's why I was puzzled. Have to try with other project, too

> npm i -D @droppedcode/typedoc-plugin-copy-assets@latest

changed 2 packages, and audited 14 packages in 4s

found 0 vulnerabilities
npm notice
npm notice New minor version of npm available! 8.5.5 -> 8.19.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.19.2
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
> npm run typedoc

> typedoc
> typedoc

Loaded plugin @droppedcode/typedoc-plugin-copy-assets
Loaded plugin typedoc-plugin-replace-text
error Tried to set an option (copyAssets) that was not declared.

I fixed the issue with 1.0.6

Thank you, now config doesn't complain at least anymore.


Creating rooms CRUD endpoints

Task description

Implement the /room endpoint that deals with POST requests to create a new room in the database.
Implement the /room/{room_id} endpoint that deals with GET requests to retrieve the room record from the database.
Implement the /room/{room_id} endpoint that deals with PUT requests to update the room record from the database.
Implement the room/{room_id} endpoint that deals with DELETE requests to delete a specific room from the database.

Points to consider.

All 4 endpoints must be annotated with @token_required from the authentication module.
The proposed object for the room document will be available before this task is assigned.

Done ✅


add LaMa library (SLAM)

LaMa - A Localization and Mapping library.

Thanks, I thought that was already included. So many SLAMs...


Upgrade controller-runtime to v0.7.0

Ref: https://github.com/fluxcd/flux2/issues/613
This PR upgrades the controller-runtime dependency to v0.7.0,
including all changes required to make all wiring work again.

Loggers have been removed from the reconcilers and are now retrieved
from the context.Context passed to the Reconcile method and
downwards functions.
Logger configuration flags are now bound to the flag set using
BindFlags from runtime/logger, ensuring the same contract across
GitOps Toolkit controllers, and the --log-json flag has been
deprecated in favour of the --log-encoding=json default.
The ChangePredicate from runtime has changed to a
ReconcilateAtChangedPredicate, and is now chained with the
GenerationChangedPredicate from controller-runtime using
predicate.Or.
Signatures that made use of runtime.Object have changed to
client.Object, removing the requirement to e.g. call
runtime.Object#Object.
The client.MatchingField function was deprecated, and has been
replaced with client.MatchingFields{}.
The leader-election-role was changed, as leader election now works
via the coordination/v1 API.

Other notable changes:

util.ObjectKey was added to easily construct a client.ObjectKey /
types.NamespacedName from a metav1.Object.
The SourceIndexKey constant has been split out into
{GitRepository,HelmRepository,Bucket}IndexKey constants.

Looks like the current test failure has to do with leader election defaulting to configmap lock type. I think the LeaderElectionResourceLock controller option needs to be set to leases. See the notes here.

Putting this on hold till the new year, but glad it has been prepared.


Support for Tasks Syntax

Hello,
I justed installed Perlite on my Raspy and hooked it up with syncthing so it has my notes.
But I run into a problem where my Task and and footnotes aren't convertet like they should in Obsidian.

As one can see in the image the footnotes and task aren't convertet.
Is this normal?

Yes, these both features are not implemented yet. for the footnotes there exists already a issue #9 and back then I hoped for some update of the parsedown library which Im using. But it seems this will never happen as there are no updates since years. At least for the Tasks I will try to implement this by myself.
So I will use this issue as tracker for the Task implementation

implemented in release 1.5.9


Could you kindly share the training code?

Thanks for you attention and waiting. We have published our training code and trainning config.


Debug output visible in releases

This code is hidden behind #if debug, which suggests to me it's not supposed to show up in marketplace releases. However, it looks like marketplace releases are debug builds, as build.hxml has -debug and package.json has haxe build.hxml as its prebublish command.

Thanks.  I forgot all about that.


initial WebRTC connections unreliable

Requires multiple refreshes (sometimes restarting server) for clients to successfully pair in a room. Can't tell what's going on yet, but this is a blocker for v0.5.0.

I will also look into this and see if I can find the cause.


slow typing experience

This happens when I found myself editing a .pl file, comments are not affected.

I think this is because of the linting. You can disable it with the following setting: "prolog.linter.run": "never".
And because I'm on Windows, I deactivated formatting too (the README says it's Linux only).

I think this is because of the linting. You can disable it with the following setting: "prolog.linter.run": "never".
And because I'm on Windows, I deactivated formatting too (the README says it's Linux only).


Package Initialization Error

Diagnostics
Request: GET https://api.teletype.atom.io/protocol-version

Versions
Teletype version: v0.13.3
Atom version: 1.35.1
Platform: darwin

Thanks for the report! I'm going to go ahead and close as a duplicate of #372 so you can subscribe there for updates if you'd like. If you can, please let us know if you're consistently seeing this error or if you saw it just once. It would also be useful to know if you access the internet via a proxy.


Get Node object from APIServer cache

The risk is pretty low given the returned Node object isn't actually used anywhere - two places invoking GetNode()

k8s_exporter calls it to check if readiness but the returned node object is discarded right away
GetConditions, which is not referenced anywhere

Thanks @linxiulei!
/lgtm

/cc @wangzhen127

/test all

/lgtm
/approve

/retest


GEOMESA-1902 Fixing secondary upper ranges in attribute index

Signed-off-by: Emilio Lahr-Vivaz<EMAIL_ADDRESS>

Uhmm...  by chance, is there a unit test that could cover this change?  I only ask since this is a tad subtle (at least for my vacation recovering brain).

that would be a good idea :)


Discord link is invalid

Cannot use the discord link to channel. Please update the latest one.

sorry, updated now.


Network interface

create an interface for the network so it could be mocked
expose GetKeys() in the interace

build


Add previewer bundle

Coverage remained the same at 89.109% when pulling 246bc5438cfa79fbfaceeec1fe37976eb0afe71c on zzacharo:add-previewer-bundle into 2f264c691cfaf37451763a72122be82112120565 on inveniosoftware:master.


paginated issue index

It would be good to be able to see every available issue in the index page.  Support for an offset query parameter to index.html, and some pagination navigation links, would enable at least basic support for this.

:star2: Thank you!!!


[Bug] Flink ui can not access

Code of Conduct

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

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the bug
Flink ui can not access
Affects Version(s)
master
Kyuubi Server Log Output
No response
Kyuubi Engine Log Output
No response
Kyuubi Server Configurations
No response
Kyuubi Engine Configurations
No response
Additional context
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

cc @yanghua @deadwind4

Can't you access Flink Web UI? Either standalone or yarn-session?
In my opinion,  Flink Web UI has nothing to do with Kyuubi.

@deadwind4 Can you show me the config?

@cutiechi You can run ${FLINK_HOME}/bin/start-cluster.sh and access Flink UI in localhosts:8081

@deadwind4 but when i execute sql there is no job on flink ui

It's does not like an issue but a question, please go ahead in discussion channel


Search Function did not work in "Select prior knowledge"

No matter what "title" I searched, it showed the same article as result.
I used EndnoteX9 ris. file.
This is my ris. file without LB field.
TY  - JOUR
AB  - OBJECTIVE: To assess the sex difference in the prevalence of COVID-19 confirmed cases. DESIGN: Systematic review and meta-analysis. SETTING: PubMed, Cochrane Library and Google Scholar were searched for related information. The authors developed a data extraction form on an Excel sheet and the following data from eligible studies were extracted: author, country, sample size, number of female patients and number of male patients. Using STATA V.14 for analysis, the authors pooled the overall prevalence of men and/or women using a random-effect meta-analysis model. The authors examined the heterogeneity in effect size using Q statistics and I2 statistics. Subgroup and sensitivity analyses were performed. Publication bias was also checked. PARTICIPANTS: Studies on COVID-19 confirmed cases were included. INTERVENTION: Sex (male/female) of COVID-19 confirmed cases was considered. PRIMARY AND SECONDARY OUTCOME MEASURES: The primary outcome was prevalence of COVID-19 among men and women. RESULT(S): A total of 57 studies with 221 195 participants were used in the analysis. The pooled prevalence of COVID-19 among men was found to be 55.00 (51.43-56.58, I2=99.5%, p<0.001). Sensitivity analysis showed the findings were not dependent on a single study. Moreover, a funnel plot showed symmetrical distribution. Egger's regression test p value was not significant, which indicates absence of publication bias in both outcomes. CONCLUSION(S): The prevalence of symptomatic COVID-19 was found to be higher in men than in women. The high prevalence of smoking and alcohol consumption contributed to the high prevalence of COVID-19 among men. Additional studies on the discrepancies in severity and mortality rate due to COVID-19 among men and women and the associated factors are recommended. Copyright © Author(s) (or their employer(s)) 2020. Re-use permitted under CC BY-NC. No commercial re-use. See rights and permissions. Published by BMJ.
AD  - (Abate) Nursing, Woldia University, Amhara, Ethiopia (Kassie, Kassaw, Aragie) Nursing, Woldia University, Amhara, Ethiopia (Masresha) College of Health Sciences, Department of Public Health, Woldia University, Amhara, Ethiopia
AN  - 633136599
AU  - Abate, B. B.
AU  - Kassie, A. M.
AU  - Kassaw, M. W.
AU  - Aragie, T. G.
AU  - Masresha, S. A.
C2  - 061120 Updated search Ovid Medline, Embase, PsychInfo
DA  - 06 Oct
DB  - Embase
DO  - http://dx.doi.org/10.1136/bmjopen-2020-040129
DP  - Ovid Technologies
IS  - 10
KW  - epidemiology
immunology
infectious diseases
adult
alcohol consumption
article
Cochrane Library
communicable disease
coronavirus disease 2019
data extraction
effect size
female
human
male
Medline
meta analysis
mortality rate
outcome assessment
prevalence
publication bias
sample size
sensitivity analysis
sex difference
smoking
systematic review
LA  - English
PY  - 2020
SN  - 2044-6055 (electronic)
2044-6055
SP  - e040129
ST  - Sex difference in coronavirus disease (COVID-19): a systematic review and meta-analysis
T2  - BMJ open
TI  - Sex difference in coronavirus disease (COVID-19): a systematic review and meta-analysis
UR  - http://ezproxy.library.usyd.edu.au/login?url=http://ovidsp.ovid.com/ovidweb.cgi?T=JS&CSC=Y&NEWS=N&PAGE=fulltext&D=emexb&AN=633136599
https://sydney.alma.exlibrisgroup.com/openurl/61USYD_INST/61USYD_INST:sydney?sid=OVID:embase&id=pmid:33028563&id=doi:10.1136%2Fbmjopen-2020-040129&issn=2044-6055&isbn=&volume=10&issue=10&spage=e040129&pages=e040129&date=2020&title=BMJ+open&atitle=Sex+difference+in+coronavirus+disease+(COVID-19)%3A+a+systematic+review+and+meta-analysis&aulast=Abate
VL  - 10
ID  - 1108
ER  -

Hi there @Sitong22 ,
Just noticed that you mentioned that this is your .ris file. As you can see there is only one record present in this .ris file, meaning that something might have gone wrong in the export-step from EndNote (see my comment in #754).
Please do let us know whether retrying the export step, while selecting all the records in EndNote, solved (hopefully both of) your issue(s)!
All the best,
Sofie

I am closing this issue because it has been solved with the suggestion of @SagevdBrand .
@Sitong22 feel free to post a question in our discussion feed if you need additional assistance with exporting a .ris file from Endnote.


fix(gen-doc-assist): remove lifetimes in description of new

From wrong behavior:
/// Creates a new [`MyGenericStruct<'a, T>`].

to correct behavior:
/// Creates a new [`MyGenericStruct<T>`].

But I feel like there is a better way to implement it. Do you know if there is an existing function that could do the work of lifetimes_removed() below?

Converted to draft because I just realized this implementation is obviously not correct: I think it would transform Foo<'a> to Foo<> but the expected text here is Foo.
It seems easy to fix, but actually, I really feel like I am re-inventing the wheel with this lifetimes_removed() function…

I don't think we have code that wants to discard lifetimes yet. But a better approach you could do here is to maybe use one of the SyntaxNode::preorder, SyntaxNode::descendants or ``SyntaxNode::descendants_with_tokenson theast::Typenode and construct your output that way by formatting everything into your string but the lifetimes(and the< >` brackets if empty).

I finally cast the type to a PathType and dive in it to get a PathSegment from which I extract what I need.


zopen upgrade should upgrade only for it's release line (dev or stable)

A global switch for dev/stable may be preferable, although some tools don't have a dev or stable release, in this case we should fallback to latest.

Latest PR & merge should implement this capability