Debug symbols not created on mac osx with the default options

Problem
I am on MacOS Mohave [10.14.6] and I am starting out with rust. The debugger does not identify any breakpoints.
Steps

Create a new cargo project in Mac OSX Mojave 10.14 [It may apply to other versions as well]
cargo new hello-rust
Run cargo build
cargo build -v
Put a breakpoint in line 2 using lldb
lldb target/debug/hello-rust
breakpoint set --file src/main.rs --line 2
You see the following error

error: hello-rust debug map object file '<workspace>/hello-rust/target/debug/deps/hello_rust.hello_rust.2vvlp69f-cgu.0.rcgu.o' has changed (actual time is 2021-06-24 21:15:36.000000000, debug map time is 1969-12-31 16:00:00.000000000) since this executable was linked, file will be ignored
error: hello-rust debug map object file '<workspace>/hello-rust/target/debug/deps/hello_rust.hello_rust.2vvlp69f-cgu.1.rcgu.o' has changed (actual time is 2021-06-24 21:15:36.000000000, debug map time is 1969-12-31 16:00:00.000000000) since this executable was linked, file will be ignored
error: hello-rust debug map object file '<workspace>/hello-rust/target/debug/deps/hello_rust.hello_rust.2vvlp69f-cgu.2.rcgu.o' has changed (actual time is 2021-06-24 21:15:36.000000000, debug map time is 1969-12-31 16:00:00.000000000) since this executable was linked, file will be ignored
error: hello-rust debug map object file '<workspace>/hello-rust/target/debug/deps/hello_rust.hello_rust.2vvlp69f-cgu.3.rcgu.o' has changed (actual time is 2021-06-24 21:15:36.000000000, debug map time is 1969-12-31 16:00:00.000000000) since this executable was linked, file will be ignored
error: hello-rust debug map object file '<workspace>/hello-rust/target/debug/deps/hello_rust.hello_rust.2vvlp69f-cgu.4.rcgu.o' has changed (actual time is 2021-06-24 21:15:36.000000000, debug map time is 1969-12-31 16:00:00.000000000) since this executable was linked, file will be ignored
error: hello-rust debug map object file '<workspace>/hello-rust/target/debug/deps/hello_rust.hello_rust.2vvlp69f-cgu.5.rcgu.o' has changed (actual time is 2021-06-24 21:15:36.000000000, debug map time is 1969-12-31 16:00:00.000000000) since this executable was linked, file will be ignored
error: hello-rust debug map object file '<workspace>/hello-rust/target/debug/deps/hello_rust.hello_rust.2vvlp69f-cgu.6.rcgu.o' has changed (actual time is 2021-06-24 21:15:36.000000000, debug map time is 1969-12-31 16:00:00.000000000) since this executable was linked, file will be ignored
error: hello-rust debug map object file '<workspace>/hello-rust/target/debug/deps/hello_rust.hello_rust.2vvlp69f-cgu.7.rcgu.o' has changed (actual time is 2021-06-24 21:15:36.000000000, debug map time is 1969-12-31 16:00:00.000000000) since this executable was linked, file will be ignored
Breakpoint 1: no locations (pending).
WARNING:  Unable to resolve breakpoint to any actual locations.

Possible Solution(s)

I changed the setting in Cargo.toml to the following so that the split-debuginfo is set to "packed" and now the breakpoint can be set correctly.

split-debuginfo = "packed"

Notes
Output of cargo version:
cargo 1.53.0 (4369396ce 2021-04-27)
Output of lldb version:
lldb-1<IP_ADDRESS>
  Swift-5.0

Output of rustc version
rustc 1.53.0 (53cb7b09b 2021-06-17)

The above steps work for me locally, and I don't see any issues. I'm using a more recent LLDB though (lldb-1<IP_ADDRESS>), so this is perhaps a bug fixed in LLDB? (or a feature added?)

I can reproduce this in older versions of Xcode.  The reason is that the object files have 0 timestamps (for deterministic builds).  This was fixed in later versions of Xcode via https://github.com/llvm-mirror/lldb/commit/f6ba8da08fdfbdb2ec190a5725729493a7ce5e51.  I have no idea how to determine which xcode that commit was first added, though.

Many thanks for quick confirmation. If this is not applicable to newer versions of LLDB then I probably ran into an edge case.  Feel free to close this out.


Refactor metallb-operator e2e tests

This PR is refactoring the e2e tests, made as part of resolving the issue of the e2etest cleanup. (#123)
The cleanup improvement itself is not being done yet, but here I make the groundwork for it.

looks good, left one comment.

LGTM


crossovers connecting same helix should "bow" up or down

Currently, a crossover between substrands in the same direction on the same helix are drawn as a straight line. This makes it difficult to see, since it typically runs over the top of other strands.
Detect if the crossover connects two substrands on the same helix, and have it bow slightly up or down to make it more visible.

More generally, they should probably bow in a direction orthogonal to the vector between the ends connected by the crossover.

See also #198.


groupwatch command title addition

for the gw command, make it be so we can put the title of the gw after "gw start" and have the file be titled as such so it is easier to refer back to previous logs
This suggestion was created by a user and sent by the bot:
jukebox-botto#8602

implemented


TrackDetailList: move delete all to Settings

Just removed delete all from TrackListActivity without adding it to settings.
This functionality should not be needed that often.


Hide the cables

Hello everyone, I would like to know how to hide the cables of the Refined storage I tried using the chisels & bits as I saw in some forums but I have experienced great difficulties I am putting 2 prints one of a video that I saw this being done and one of my map where I can not slip the cables.
https://imgur.com/a/z0o0r7k
...
Version (make sure you are on the latest version before reporting):
chiselsandbits-14.16
MCMultiPart-2.5.1
Minecraft 1.12.2 - MultiMC
refinedstorage-1.5.33
forge-1.12.2-<IP_ADDRESS>55-universal

What's the problem?

Hello I can not hide the cables using the chisels & bits covers as I showed in the screenshots.

Please head over to our Discord to ask your question there, this issue tracker is merely for bugs.


Unable to upload image succesfully after changing the "select backend" dropdown

Repro steps:

nav to https://microsoft.github.io/onnxruntime-web-demo/#/squeezenet and keep the default selected "GPU" backend selected
click upload image and upload a image of a dog
the result is a classification as expected
Toggle the dropdown "CPU"
click "upload image" and upload the image of the dog again
the result is blank, no classification or visible error warning is observed

thank you for the feedback! this issue is fixed in latest version.


fix(typescript): content-sensitive features are only allowed to return results in contiguous mapped ranges

Fixes https://github.com/vuejs/language-tools/issues/4811, closes https://github.com/vuejs/language-tools/pull/4906
In the past we mapped results in discrete mapping regions for all TS features, however for content-sensitive features (such as autocomplete/formatting), results should only be returned in continuous mapping regions.
Affected features:

getFormattingEditsForDocument
getFormattingEditsForRange
getFormattingEditsAfterKeystroke
getEditsForFileRename
getLinkedEditingRangeAtPosition
organizeImports
getDocumentHighlights
getEditsForRefactor
getCombinedCodeFix
getRenameInfo
getCodeFixesAtPosition
getEncodedSemanticClassifications
findRenameLocations
getCompletionsAtPosition
getCompletionEntryDetails

cc @piotrtomiak, @KazariEX

@johnsoncodehk - thanks for heads up! I already use continuous ranges everywhere, so nothing is affected.


Google OAuth Backend

The user can login using google.
The path is /auth/google/.
Issue number #24

Have you tested this? @shrirangpdeshmukh

Have you tested this? @shrirangpdeshmukh

Yes I have tested this

How are we maintaining a session here? Are we using check-session for a persistent session?

How are we maintaining a session here? Are we using check-session for a persistent session?

We are using cookies for a persistent session

@shrirangpdeshmukh, Right now if we are starting the server, It is throwing an error, because it is unable to find the configuration keys. What we want is that developers can start the server without any errors. Please, make the required changes so that no error gets thrown.

@arjungarg07,
I can comment out the current auth implementation.
The authentication won't be working in that case, the google strategy requires the client details
Either I have to share env file with the developers or currently turn off the google authnetication.


Add GraphQL code generation to actions-server

Move most of the GraphQL Code Generator configuration to the root directory
Add necessary dev dependencies to actions-server

closing in favor of https://github.com/avimoondra/fishbowl/pull/74, and a poor git form on my part... 🤦


Create misspell.yml

Currently it is set to push because I want to have the initial run right now.
Later I will change it to work once a day.

Related: https://github.com/lk-geimfari/mimesis/pull/823
But, I have to ignore .json files.

Actually, there are not typos here. So, we can ignore this check.


Feature: left click tray = quick actions

Please make sure that the feature you'd like to request is not already requested :)

Is your feature request related to a problem? Please describe.
NA
Describe the solution you'd like
An option to enable quick actions to be displayed when you left or right click the tray icon.
Describe alternatives you've considered
NA
Additional context
Currently there are options to modify the left and right clicks of the tray. I don't believe there is any action defined for a single left click of the tray icon. Mine doesn't do anything at least.  A double click opens the main window. To get to quick actions I have to right click, and then select quick actions. I thought it would be nice to streamline the work flow.
Thanks for all the work!

Hmm, when WebView is enabled the left click can be configured to show the normal "right click menu":

I could make it that when WebView is not enabled the left click will open the quick actions window - I understand that the quick actions hothey is not exactly working for your use-case?

You're correct about the existing options. I just thought it was interesting that there was no default for a single left click and perhaps this was a good option. And yes, I suppose it would have to be in the case that webview wasn't enabled.
That's correct about hotkeys. To be honest I forgot about hotkeys, although I didn't realize that the panel could be opened with one. I believe I programmed one for a quick action. That said, quick access to the panel one way or another is what I was thinking would be nice.


An error

An error occurred in Toolkit for YNAB (a browser extension you installed to enhance YNAB).

Same here today, no additional information on the error

Same here, been a few days. Had to disable. Found this in my developer console, seems relevant.

Same issue for me--has been happening for about a week and means I have to keep Toolkit turned off until it's resolved.

Duplicate of 2964


Add cegui

http://static.cegui.org.uk/docs/0.8.7/compiling.html
For activate Python support: "CEGUI_BUILD_PYTHON_MODULES"
Disable LUA , Direct3D
Enable OpenGL, OpenGL3
XML parser expat

Config from Belair
//Specifies whether to build the application templates.
CEGUI_BUILD_APPLICATION_TEMPLATES:BOOL=OFF

//Specifies whether to build the application template for GLFW3
CEGUI_BUILD_APPLICATION_TEMPLATE_GLFW3:BOOL=OFF

//Specifies whether to build the application template for SDL2
CEGUI_BUILD_APPLICATION_TEMPLATE_SDL2:BOOL=OFF

//Specifies whether to build the datafiles test.

CEGUI_BUILD_RENDERER_OPENGL3:BOOL=ON

//Specifies whether to build the OpenGL ES 1 renderer module
CEGUI_BUILD_RENDERER_OPENGLES:BOOL=OFF

//Specifies whether to build the Expat based XMLParser module
CEGUI_BUILD_XMLPARSER_EXPAT:BOOL=ON

//Specifies whether to build the libxml2 based XMLParser module
CEGUI_BUILD_XMLPARSER_LIBXML2:BOOL=OFF

//Specifies whether to build the RapidXML based XMLParser module
CEGUI_BUILD_XMLPARSER_RAPIDXML:BOOL=OFF

//Specifies whether to build the TinyXML based XMLParser module
CEGUI_BUILD_XMLPARSER_TINYXML:BOOL=OFF

//Specifies whether to build the Xerces-C++ based XMLParser module
CEGUI_BUILD_XMLPARSER_XERCES:BOOL=OFF

I get the intention to add cegui to the installer, but it's the wrong repository for the rest of the information and the cmake/build instructions. Because this installer repository bundles only already build stuff, for example the libfife-dependencies.
The correct location to build the cegui dependency is the superbuild project of fifengine.
You need to handle CeGui like Fifechan in the dependencies:

[ ] add option: https://github.com/fifengine/fifengine/blob/master/dependencies/CMakeLists.txt#L76
[ ] add conditional external project include (based on option): https://github.com/fifengine/fifengine/blob/master/dependencies/CMakeLists.txt#L125
[ ] create get-cegui.cmake (ExternalProject_Add)

add pre-build mingw, if available
add pre-build msvc, if available
or build from source with custom configuration

all the CEGUI_BUILD stuff would go here

After that, Fifengine itself searches for cegui, when cegui is enabled.
Once CeGui is build fifengine would be linked against it, either statically or dynamically.
That produces 3 more libfife artifacts of the fifengine repo: libfife-with-cegui-static + libfife-with-cegui-dynamic + the extra and optional libfife-cegui-dependency package.

Thanks for the info jakoch :-)

Found cegui on appveyor: https://ci.appveyor.com/project/cegui-ci/cegui/history

Something like this should work for building CEGUI for FIFE:
set cegui_deps_source_dir=??? (where cegui dependencies source package was extracted)
set cegui_deps_build_dir=??? (choose whatever)
set cegui_source_dir=??? (where cegui source package was extracted)
set cegui_build_dir=??? (choose whatever)

mkdir %cegui_deps_build_dir%
cd %cegui_deps_build_dir%
cmake -G "Visual Studio 14" %cegui_deps_source_dir%
cmake --build . --target ALL_BUILD --config Release

mkdir %cegui_source_dir%\dependencies
xcopy /Y /S %cegui_deps_build_dir%\dependencies %cegui_source_dir%\dependencies

mkdir %cegui_build_dir%
cd %cegui_build_dir%
cmake -G "Visual Studio 14" -D BOOST_ROOT:PATH=%boost_root% -D CEGUI_BUILD_APPLICATION_TEMPLATES:BOOL=OFF -D CEGUI_BUILD_PYTHON_MODULES:BOOL=ON -D CEGUI_SAMPLES_ENABLED:BOOL=OFF %cegui_source_dir%
cmake --build . --target ALL_BUILD --config Release

CEGUI download links are here: http://cegui.org.uk/download/cegui-087

Need to be done:
Find cmake scripts:
[ ] libexpat
[ ] glew
[ ] glfw
[ ] glm
[ ] pcre
[ ] libsilly
Get cmake scripts:
[ ] libexpat
[ ] glew
[ ] glfw
[ ] glm
[ ] pcre
[ ] libsilly

Branch for it: https://github.com/fifengine/fifengine/tree/cegui-sdk


Add the ASL license header on the source file

We need to add the License header on the script files, examples and some go files. and we could use Apache Rat to check the License information when doing the release.
I just ran a quick check with apache rat.
java -jar ~/bin/apache-rat-0.12/apache-rat-0.12.jar -a -d ./

I think we could skip the json files and *.adoc file as we cannot add the license header there.
Files with unapproved licenses:

  ./.dockerignore
  ./.gitignore
  ./.gitmodules
  ./.golangci.yml
  ./.pre-commit-config.yaml
  ./Gopkg.lock
  ./Gopkg.toml
  ./README.adoc
  ./contributing.adoc
  ./go.mod
  ./go.sum
  ./assets/json-schema/CamelCatalog.json
  ./assets/json-schema/Integration.json
  ./assets/json-schema/IntegrationContext.json
  ./assets/json-schema/IntegrationPlatform.json
  ./build/Dockerfile
  ./deploy/camel-catalog-2.23.0.yaml
  ./deploy/camel-catalog-2.23.1.yaml
  ./deploy/camel-catalog-2.23.2.yaml
  ./deploy/camel-catalog-2.24.0.yaml
  ./deploy/camel-catalog-3.0.0-M2.yaml
  ./deploy/cr-example.yaml
  ./deploy/crd-build.yaml
  ./deploy/crd-camel-catalog.yaml
  ./deploy/crd-integration-context.yaml
  ./deploy/crd-integration-platform.yaml
  ./deploy/crd-integration.yaml
  ./deploy/operator-deployment.yaml
  ./deploy/operator-role-binding-knative.yaml
  ./deploy/operator-role-binding.yaml
  ./deploy/operator-role-knative.yaml
  ./deploy/operator-role-kubernetes.yaml
  ./deploy/operator-role-openshift.yaml
  ./deploy/operator-service-account.yaml
  ./deploy/platform-cr.yaml
  ./deploy/platform-integration-context-groovy.yaml
  ./deploy/platform-integration-context-jvm.yaml
  ./deploy/platform-integration-context-knative.yaml
  ./deploy/platform-integration-context-kotlin.yaml
  ./deploy/user-cluster-role.yaml
  ./deploy/olm-catalog/camel-k.package.yaml
  ./deploy/olm-catalog/camel-k.v0.3.3.clusterserviceversion.yaml
  ./deploy/olm-catalog/csv-config.yaml
  ./docs/cluster-setup.adoc
  ./docs/gke-setup.adoc
  ./docs/languages.adoc
  ./docs/traits.adoc
  ./examples/CaffeineCacheSample.java
  ./examples/RestWithRestlet.java
  ./examples/Sample.java
  ./examples/camel-caffeine.groovy
  ./examples/dns.js
  ./examples/greetings-api.json
  ./examples/greetings.groovy
  ./examples/kotlin-routes.kts
  ./examples/props.js
  ./examples/resources-data.txt
  ./examples/resources-route.groovy
  ./examples/routes-rest.js
  ./examples/routes.flow
  ./examples/routes.groovy
  ./examples/routes.js
  ./examples/simple.groovy
  ./examples/simple.js
  ./examples/kafka/README.adoc
  ./examples/kafka/SampleKafkaConsumer.java
  ./examples/kafka/application.properties
  ./examples/knative/README.adoc
  ./examples/knative/feed.groovy
  ./examples/knative/messages-channel.yaml
  ./examples/knative/printer.groovy
  ./examples/knative/reader.groovy
  ./examples/knative/splitter.groovy
  ./examples/knative/words-channel.yaml
  ./examples/knative/writer.groovy
  ./pkg/apis/addtoscheme_camel_v1alpha1.go
  ./pkg/apis/addtoscheme_knative_eventing_v1alpha1.go
  ./pkg/apis/addtoscheme_knative_serving_v1alpha1.go
  ./pkg/apis/addtoscheme_monitoring.go
  ./pkg/apis/addtoscheme_openshift.go
  ./pkg/apis/apis.go
  ./pkg/apis/camel/v1alpha1/build_types.go
  ./pkg/apis/camel/v1alpha1/camelcatalog_types.go
  ./pkg/apis/camel/v1alpha1/doc.go
  ./pkg/apis/camel/v1alpha1/integration_types.go
  ./pkg/apis/camel/v1alpha1/integrationcontext_types.go
  ./pkg/apis/camel/v1alpha1/integrationplatform_types.go
  ./pkg/apis/camel/v1alpha1/register.go
  ./pkg/apis/camel/v1alpha1/zz_generated.deepcopy.go
  ./pkg/apis/camel/v1alpha1/zz_generated.defaults.go
  ./pkg/controller/add_build.go
  ./pkg/controller/add_integration.go
  ./pkg/controller/add_integrationcontext.go
  ./pkg/controller/add_integrationplatform.go
  ./pkg/controller/controller.go
  ./pkg/controller/build/build_controller.go
  ./pkg/controller/integration/integration_controller.go
  ./pkg/controller/integrationcontext/integrationcontext_controller.go
  ./pkg/controller/integrationplatform/integrationplatform_controller.go
  ./pkg/platform/operator.go
  ./pkg/util/defaults/defaults.go

The PR #712 was merged into master branch.


GPid and GPollFD ABI mismatch for Windows

https://github.com/gtk-rs/gir/pull/558 shows this problem:
ABI mismatch for GPid
Rust: ABI { size: 4, alignment: 4 }
C:    ABI { size: 8, alignment: 8 }
ABI mismatch for GPollFD
Rust: ABI { size: 8, alignment: 4 }
C:    ABI { size: 16, alignment: 8 }
GPid currently defined as pub type GPid = c_int;
In C it defined on linux as typedef int GPid;, on windows: typedef void * GPid.
GPollFD currently
pub struct GPollFD {
    pub fd: c_int,
    pub events: c_ushort,
    pub revents: c_ushort,
}

In C it different only on 64-bit Windows
struct _GPollFD
{
#if defined (G_OS_WIN32) && GLIB_SIZEOF_VOID_P == 8
#ifndef __GTK_DOC_IGNORE__
  gint64	fd;
#endif
#else
  gint		fd;
#endif
  gushort 	events;
  gushort 	revents;
};

Seems simpler way just add manual part to glib-sys that change definition.
IMHO we can use i64 for both types for #[cfg(all(windows,target_arch="x86_64"))]
@GuillaumeGomez, @sdroege, @tmiasko any comments?

We can totally use i64 for both even though it's not optimal.

Currently sys generation ignores object status for type generation and use it only for function,
I will try to fix it tomorrow.

Manual implementation seems like the best approach for this, yes

@sdroege GLib contains child_watch_add and child_watch_source_new that affected by this issue,
they used u32 as pid type (not sure about your reason to do that).
I tried done same as for sys in https://github.com/EPashkin/glib/commit/4e3100ed3f7da2c1648e2bae88623e30955ea62c, but it not looks good.
Maybe better do this:
define GPid as unsigned in sys in https://github.com/gtk-rs/sys/pull/81,
export it from glib as Pid,
and use in these functions directly?

Or define Pid as u64 or c_unt in glib and export it.

IMHO we should better define a correct type for pid instead of having configuration-dependant closure signatures. It's ugly otherwise.
That type could then be converted to the pid type of libstd with one of the conversion traits.

And I used u32 as pid type because that's what devhelp showed for the definition of GPid :)

GPid signed even on linux: https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html#GPid
If we go from https://doc.rust-lang.org/std/process/struct.Child.html#method.id then Windows
have different
in rust/src/libstd/sys/unix/process/process_unix.rs
    pub fn id(&self) -> u32 {
        self.pid as u32
    }

in rust/src/libstd/sys/unix/process/process_fuchsia.rs
    pub fn id(&self) -> u32 {
        self.handle.raw() as u32
    }

in rust/src/libstd/sys/windows/process.rs
    pub fn id(&self) -> u32 {
        unsafe {
            c::GetProcessId(self.handle.raw()) as u32
        }
    }

where Windows handle.raw() is your GPid and GetProcessId is WinApi function https://msdn.microsoft.com/ru-ru/library/windows/desktop/ms683215(v=vs.85).aspx and it not exported from std,
also it seems don't have good inverse function: https://stackoverflow.com/questions/2221103/how-to-get-process-handle-from-process-id
So using u32 as rust variant for GPid seems not good for Windows and maybe Fuchsia too.

Nobody ported GLib to Fuchsia yet :)
So a process ID on Windows is a u32 but the handle for the process is a HANDLE like everything, so basically a pointer. And GPid is basically a *mut c_void then on Windows.

So let's define GPid in -sys like that, and in glib as pub struct Pid(pub ffi::GPid) and ignore the problem for now.

This fixed by #81


how to generate texts based on videos？

I want to know how to generate texts based on videos？And i only look a chat.

The chat demo generates texts based on videos under the hood, so they're not fundamentally different. Do you have more specific questions?


Fix latent assertion output bug

Turned out the successful return path for assert_success and assert_failure when no arguments were given wasn't routed through __return_from_bats_assertion, which meant set -o functrace was not going back into effect.
Noticed this while writing tests for the upcoming lib/log module, whereby the custom assert_log_equals assertion was not showing up in error stack traces despite not scrubbing the Bats stack trace arrays. Figured out this was because assert_success was called before assert_log_equals, and eventually found the bug.
Then I thought things over and decided that __return_from_bats_assertion was a fragile means of resetting set -o functrace, and came up with the bats_assertion_return_trap method. When used as described in the comments, it works very well (though there are still some mysteries about how RETURN traps play with DEBUG traps, ERR traps, and set -o functrace that I'll be exploring for some time to come).
Update: I reverted the trap-based solution, as it added O(20s) to the test suite.

Coverage increased (+0.01%) to 96.221% when pulling f4a0f85b662297778bae6216ca1727ce648cd7c7 on assertions into 52bc541014249e36ebd268a98085d8f6bcc52b6e on master.

Coverage increased (+0.01%) to 96.221% when pulling 0d94845ec460bc90d58ff288ed89dcc21309aecf on assertions into 52bc541014249e36ebd268a98085d8f6bcc52b6e on master.


[question] snap refresh fails

Hello,
The package is not upgrading and throws up an error
# snap list
Name          Version   Rev    Tracking       Publisher       Notes
core20        20220512  1498   latest/stable  canonical✓      base
snapd         2.55.5    15909  latest/stable  canonical✓      snapd
zwavejs2mqtt  v6.9.1    379    latest/stable  giaever-online  -

# snap refresh
error: cannot perform the following tasks:
- Mount snap "zwavejs2mqtt" (383) (cannot undo partial setup snap "zwavejs2mqtt": umount: /snap/zwavejs2mqtt/383: not mounted.)
- Mount snap "zwavejs2mqtt" (383) (cannot proceed, expected snap "zwavejs2mqtt" revision 383 to be mounted but is not)

Any idea how to fix this?

Can you try to restart snapd with
sudo systemctl restart snapd.servcice

and then try to do the refresh
sudo snap refresh


csharp: integration tests (ClientTests/DriverTests) can cause concurrency issues creating/updating table.

What happened?
When running the (integration) tests, the ClientTests.CanExecuteUpdate and DriverTests.CanExecuteUpdate can concurrently try to create and update the same test table. This can lead to flakey test failures and in the worst case leave the Databricks server in an inconsistent state (resource leaks).
Stack Trace
Message:
  System.AggregateException : One or more errors occurred. (Error running query: io.delta.exceptions.ConcurrentAppendException: Files were added to the root of the table by a concurrent update. Please try the operation again.
  Conflicting commit: {"timestamp":1730135866536,"operation":"WRITE","operationParameters":{"mode":Append,"statsOnLoad":false,"partitionBy":[]},"readVersion":34,"isolationLevel":"WriteSerializable","isBlindAppend":true,"operationMetrics":{"numFiles":"1","numOutputRows":"1","numOutputBytes":"6118"},"tags":{"restoresDeletedRows":"false"},"engineInfo":"Databricks-Runtime/13.3.x-scala2.12","txnId":"70495e06-e88b-446b-8dd3-9e216cdbf0c6"}
  Refer to https://docs.microsoft.com/azure/databricks/delta/concurrency-control for more details.)
  ---- Apache.Arrow.Adbc.Drivers.Apache.Hive2.HiveServer2Exception : Error running query: io.delta.exceptions.ConcurrentAppendException: Files were added to the root of the table by a concurrent update. Please try the operation again.
  Conflicting commit: {"timestamp":1730135866536,"operation":"WRITE","operationParameters":{"mode":Append,"statsOnLoad":false,"partitionBy":[]},"readVersion":34,"isolationLevel":"WriteSerializable","isBlindAppend":true,"operationMetrics":{"numFiles":"1","numOutputRows":"1","numOutputBytes":"6118"},"tags":{"restoresDeletedRows":"false"},"engineInfo":"Databricks-Runtime/13.3.x-scala2.12","txnId":"70495e06-e88b-446b-8dd3-9e216cdbf0c6"}
  Refer to https://docs.microsoft.com/azure/databricks/delta/concurrency-control for more details.

Stack Trace:
  Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
  Task`1.get_Result()
  HiveServer2Statement.ExecuteUpdate() line 39
  AdbcCommand.ExecuteNonQuery() line 149
  ClientTests.CanClientExecuteUpdate(AdbcConnection adbcConnection, TestConfiguration testConfiguration, String[] queries, List`1 expectedResults) line 64
  ClientTests.CanClientExecuteUpdate() line 73
  RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
  MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
  ----- Inner Stack Trace -----
  HiveServer2Statement.ExecuteStatementAsync() line 119
  HiveServer2Statement.ExecuteQueryAsync() line 43
  HiveServer2Statement.ExecuteUpdateAsync() line 61

How can we reproduce the bug?
Using VS, invoke the tests for Apache.Arrow.Adbc.Tests.Drivers.Apache.Spark level.
Environment/Setup
No response

Fixed in https://github.com/apache/arrow-adbc/pull/2282


Please support ---@version, ---@author, ---@license, ---@created and ---@lastmod.

As, shown here.
Also, being really greedy here! Can you also support ---@version, ---@author, ---@license, ---@created and ---@lastmod.
Which means version number, last author name, license name/summary, creation time and last-modified time. Maybe similar to this.
Thank you!

---@tag and ---@brief are already supported. Please read the docs.
As for the other tags, it's not a matter of adding them, we also need to take care of how they look and whether they will interfere with lua-language-server.

Oh! I thought it was just a general guide to write emmylua docs. Reading it right now. Should I swap the title of this issue with those other tags then?

Also, I do not know if it has something to do with my settings but writing those tags did not result in any warnings from the language server.

I would suggest you to share how you intend to write those tags on the lua side and how you want your docs to look like. So that we can work with sketches before getting into the implementation.

Alright! I already have some of my files using those tags. I'll get back to you with a minimal example in a bit.

Docs metadata specification sample.
This is a rough specification file for preferences and features that the following
tags should support.

The ---@license tag.
The ---@lastmod tag.
The ---@version tag.
The ---@created tag.
The ---@author tag.

The ---@license tag.
This is also a top level tag like ---@brief.
This should support taking in one parameter if possible.

Linking the complete license.

---@license [[
--- GNU GENERAL PUBLIC LICENSE
--- Version 3, 29 June 2007
---
--- Permissions of this strong copyleft license are conditioned on
--- making available complete source code of licensed works and
--- modifications, which include larger works using a licensed work,
--- under the same license. Copyright and license notices must be
--- preserved. Contributors provide an express grant of patent rights.
--@license ]]

This should result in the following.
*plugin.txt*

GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007

Permissions of this strong copyleft license are conditioned on
making available complete source code of licensed works and
modifications, which include larger works using a licensed work,
under the same license. Copyright and license notices must be
preserved. Contributors provide an express grant of patent rights.

Now, with the link parameter.
---@license "https://github.com/numToStr/lemmy-help/blob/master/LICENSE" [[
--- GNU GENERAL PUBLIC LICENSE
--- Version 3, 29 June 2007
---
--- Permissions of this strong copyleft license are conditioned on
--- making available complete source code of licensed works and
--- modifications, which include larger works using a licensed work,
--- under the same license. Copyright and license notices must be
--- preserved. Contributors provide an express grant of patent rights.
--@license ]]

This should result in the following.
*plugin.txt*

Licensed under:
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007

Permissions of this strong copyleft license are conditioned on
making available complete source code of licensed works and
modifications, which include larger works using a licensed work,
under the same license. Copyright and license notices must be
preserved. Contributors provide an express grant of patent rights.

Read the complete license here:
https://github.com/numToStr/lemmy-help/blob/master/LICENSE

Also note that this should have a higher priority than ---@brief.
The ---@author tag.
This is also another top level tag like ---@brief and ---@mod i.e.
only allow this at the very top of the file.
This should be ranked above the ---@license tag.
Now, look at the following demo.
---@author dharmx |<EMAIL_ADDRESS>
---@mod sample THIS IS A SAMPLE

---@brief [[
---A very, very short overview of this module.
---@brief ]]

This should be rendered to the following.
Authored by: dharmx |<EMAIL_ADDRESS>
==============================================================================
THIS IS A SAMPLE                                                           *sample*

A very, very short overview of this module.

Additional Note
It would be nice if we could disable the horizontal line that comes with ---@mod and
a way to align *sample* to the very left if <name> is empty. Hence, see the
following.
---@mod false noalign sample.txt

---@author dharmx |<EMAIL_ADDRESS>
Here, false should indicate if the horizontal line should be added and noalign should
press to the very left. See the following.
*sample.txt*
Authored by: dharmx |<EMAIL_ADDRESS>
This way we can have the ranking of ---@mod higher than that of ---@author. Well, perhaps
we could have a different tag for this.
The ---@lastmod, ---@created and ---@version tags.
These should have the same ranking and should be lower than ---@author. Now, see the following
sample.
---@author dharmx |<EMAIL_ADDRESS>---@created 2022-11-18
---@lastmod 2022-11-19
---@version 0.1.0

This should be rendered into the following.
Authored by: dharmx |<EMAIL_ADDRESS>Creation date: 2022 November 18
Last modified: 2022 November 19
Version: 0.1.0

A full sample.
-- vim:filetype=lua

---@author dharmx
---@created 2022-11-18
---@lastmod 2022-11-19
---@version 0.1.0

---@mod sample A SAMPLE MODULE

---@license "https://github.com/numToStr/lemmy-help/blob/master/LICENSE" [[
--- GNU GENERAL PUBLIC LICENSE
--- Version 3, 29 June 2007
---
--- Permissions of this strong copyleft license are conditioned on
--- making available complete source code of licensed works and
--- modifications, which include larger works using a licensed work,
--- under the same license. Copyright and license notices must be
--- preserved. Contributors provide an express grant of patent rights.
--@license ]]

---@brief [[
---Lorem ipsum dolor sit amet, officia excepteur ex fugiat reprehenderit enim
---labore culpa sint ad nisi Lorem pariatur mollit ex esse exercitation amet.
---Nisi anim cupidatat excepteur officia. Reprehenderit nostrud nostrud ipsum
---Lorem est aliquip amet voluptate voluptate dolor minim nulla est proident.
---@brief ]]

---@mod config THE SAMPLE CONFIG

---@class SampleConfig This a configuration table for a sample plugin.
---@field setup boolean The setup function.
---@field load string[] Modules to load.
---@field condition fun(path:string):string|nil A function.

---@type SampleConfig
local Config = {
  ---A Sample option.
  setup = true,
  load = { "core", "plug", "theme" },
  ---This is a condition function.
  ---@param path string
  ---@return string|nil
  condition = function(path) return path:match("load") end,
}

---Setup function.
---@see nvim-dharmx-config
---@usage `require("sample").startup()`
function Config.startup()
  if Config._done then return end
  Config._done = true
end

return Config

For Neovim version 0.7.0
Creation date: 2022 November 18
Last modified: 2022 November 19
Version: 0.1.0

Licensed under:
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007

Permissions of this strong copyleft license are conditioned on
making available complete source code of licensed works and
modifications, which include larger works using a licensed work,
under the same license. Copyright and license notices must be
preserved. Contributors provide an express grant of patent rights.

Read the complete license here:
https://github.com/numToStr/lemmy-help/blob/master/LICENSE

==============================================================================
A SAMPLE MODULE                                                         *sample*

Lorem ipsum dolor sit amet, officia excepteur ex fugiat reprehenderit enim
labore culpa sint ad nisi Lorem pariatur mollit ex esse exercitation amet.
Nisi anim cupidatat excepteur officia. Reprehenderit nostrud nostrud ipsum
Lorem est aliquip amet voluptate voluptate dolor minim nulla est proident.

==============================================================================
THE SAMPLE CONFIG                                                       *config*

SampleConfig                                               *config.SampleConfig*

Config.startup()                                                *config.startup*
    Setup function.

    See: ~
        |nvim-dharmx-config|

    Usage: ~
>lua
        require("sample").startup()
<

vim:tw=78:ts=8:noet:ft=help:norl:

Let me know what you think!

Thanks for the detailed explanation. Even though these looks useful, they certainly don't provide any real benefit and can be easily covered by ---@brief. That's what I am also using in Comment.nvim. Also, there is no concept of priority. Everything is parsed and rendered from top to bottom. If you go by these rules, your file might look like this.
-- vim:filetype=lua

---@brief [[
---Authored by: dharmx |<EMAIL_ADDRESS>---Creation date: 2022 November 18
---Last modified: 2022 November 19
---Version: 0.1.0
---
---Licensed under:
---GNU GENERAL PUBLIC LICENSE
---Version 3, 29 June 2007
---
---Permissions of this strong copyleft license are conditioned on
---making available complete source code of licensed works and
---modifications, which include larger works using a licensed work,
---under the same license. Copyright and license notices must be
---preserved. Contributors provide an express grant of patent rights.
---
---Read the complete license here:
---https://github.com/numToStr/lemmy-help/blob/master/LICENSE
---@brief ]]

---@mod sample A SAMPLE MODULE

---@brief [[
---Lorem ipsum dolor sit amet, officia excepteur ex fugiat reprehenderit enim
---labore culpa sint ad nisi Lorem pariatur mollit ex esse exercitation amet.
---Nisi anim cupidatat excepteur officia. Reprehenderit nostrud nostrud ipsum
---Lorem est aliquip amet voluptate voluptate dolor minim nulla est proident.
---@brief ]]

...

One thing that might somewhat related your request is the first line (IDK what this is really called) of the help file. If you have any idea on this, I'll be happy to hear it :)

That seems really neat. I did not know you could use ---@brief twice! Rather, I did not try using it that way. As, for the first line thing, I think a doctag with two parameters would be great, like ---@headmod <tag-name> <version> <lastmod> to ---@headmod comment-nvim.txt 0.7 2021-07-11. And, if you do want to support spaces.. I think enclosing them around "" would be great.
Also, my issues have been solved! This can be closed if you want.

Thanks for the idea! I'll track the doctag in another issue. Closing this now.


Add pyproject.toml for Custom Node Registry

We are working with dr.lt.data and comfyanon to build a global registry for custom nodes (similar to PyPI). Eventually, the registry will be used as a backend for the UI-manager. All nodes go through a verification process before being published to users.
The main benefits are that authors can

publish nodes by version and users can safely update nodes knowing ahead of time if their workflows will break or not
automate testing against new commits in the comfy repo and existing workflows through our CI/CD dashboard

Action Required:

[ ] Go to the registry. Login and create a publisher id. Add the publisher id into the pyproject.toml file.
[ ] Write a short description.
[ ] Merge the separate Github Actions PR and run the workflow.

If you want to publish the node manually, install the cli and run comfy node publish
Check out our docs if you want to know more about the registry. Otherwise, feel free to message me on discord at haohao_81202 or join our server if you have any questions!

hey @wwwins, wanted to send a small nudge and ask if you had any questions!

@wwwins, wondering if there's any way we can support you on this PR!


[INLONG-496][tubemanager] clean offset in consumer group

clean offset in consumer group
JIRA link - [INLONG-496] created by stingpeng

This issue was created a long time ago. Close it first


[WIP] Semantic markdown comparison and pretty diffs

There are two commits here, both towards the same aim: Improving markdown tests.
There is a change from using both Python's and Node.js's native assert diffing capabilities to using one unified diffing tool based on a javascript port of Python's difflib library.  Oftentimes, the diffs that were automatically produced in Python (the node tests didn't even produce true diffs) were nearly unreadable, partially since many markdown test fixtures consist of extremely ( hundreds of characters ) long lines, that don't play well with the default diff tool, forcing you to copy and paste into an external tool. Now both the frontend (node) and backend (python) markdown fixture tests use the same colorful and much easier to read diff tool!
Another change here, is that the node frontend tests no longer do naive string comparisons.  Rather, using the jsdom library, we compare instead the DOM elements produced by these strings.  This means that a difference such as " over \" will no longer trip up the tests.  Nor will a change in attribute orders in tags, so woof and woof will no longer trip up the tests, either.  Also, in case of differences, instead of diffing the original HTML, we diff HTML generated from these DOM elements, so that only real changes show up in the diff, and it isn't cluttered with the previously mentioned differences that, in fact, aren't actually relevant at all.
The change to semantic comparisons of HTML as opposed to the naive string approach has already removed six frontend-only fixtures from markdown_test_cases.json, unifying them with the expected values for the backend markdown test.  And, with the improved error messages, it's a lot easier to see where the other tests in which the frontend/backend disagree diverge.
Here's a simple example of the changes in both the node and python markdown fixture tests.  Red indicates removal, green (looks yellowish here) indicates an addition, and yellow changes.

A second example of the same for good measure:

An example of what the new diffs let you do that the previous do not;  The longest fixture in which the javascript frontend and python backend disagree is kind of impenetrable with normal diffs, the lines are too long to navigate without color and there's a lot of irrelevant differences such as changes in attribute order.  But, now it's not very difficult to see that the only real difference is that the marked output simply lacks
 tags around  (which happens to be the case a lot of the time; would be really difficult to tell this is the only problem without these changes).
![image](https://user-images.githubusercontent.com/6401828/34027196-2351516e-e129-11e7-9a36-8e4dd2c9fd66.

png)

It isn't perfect yet, and there are some things to iron out, namely the use of absolute imports instead of relative ones when require()ing the code in markdown.js, but I'd appreciate feedback nonetheless!

Is this ready for final review now?  If so, go ahead and remove "wip" from the title and indicate in the comments that you've addressed your own to-dos (like the relative import thing).
I just read what you have now, and it looks great.

@PentaHiggs Pinging on this.  The build's failing for some reason now and you still have "wip" in the title.  Other than that, I'm eager to merge this when you feel it's ready.

@showell I apologize for the delays, I was rather preoccupied for the last few days.  I've made some changes, and I'm ready for a final review.

merged,thanks @PentaHiggs


Name for the 'predicate' in Therapeutic Response annotations

We need to think about what to call the predicate describing the variant-treatment relationship, as some felt that the proposed predicts_sensitivity_to makes perhaps too strong a statement. Below is a list of possible predicate names to consider/debate:

predicts_sensitivity_to - perhaps too strong?
associated_with_sensitivity_to - perhaps too weak?
confers_sensitivity_to
causes_sensitivity_to
correlates_with_sensitivity_to

Please share other ideas and thoughts/preferences about the proposals above.

I think that these annotations are making an assertion that there is some causal/contributing relationship between the variant and a response to a treatment, or at least a strong statistical correlation that suggests causality, and that the predicate should reflect this.  I'm not too worried about using stronger language here, as any 'predicted sensitivity' statements should be considered in the context of what evidence supports it (and we could even allow for some qualifier that explicitly states the degree of confidence in the statement).
I don't have particularly strong feelings about the choices above, but agree that 'predicts' is perhaps not right, and 'associated with' is perhaps too weak.  So might lean toward one of the others.

+1 to the predicates listed here
(I guess that the 'no_association_with_response_to' means negative evidence, i.e. something that would make sense that could work but it has been demonstrated that it does not (e.g. BRAFV600E inhibtor in colorectal cancer)   (If it does not mean that, we need to include that predicate))
regarding the terms themselves, i m fine with almost all of them, but if i need to vote a couple, I d say 'confers' sounds nice and 'is associated with' is loose enough to be fair even for those statements with lower levels of evidence (note that i would not employ different terms depending on the level of evidence)

On the March 20 VA call there was general agreement that 'predicts' is fine to use in predicate labels (e.g. predicts_sensitivity_to), for the reasons laid out in above.

My only concern is with the definition of predicts_reduced_sensitivity_to. Of the 4,291 predictive evidence statements in CIViC, only 20 use this. It is a value that is used to change the type of statement being made, which is partially captured above.
However, an important clarification of the above definition (strikeout added, new text emphasized):

predicts_reduced_sensitivity_to (the treatment has reduced efficacy in patients when they have the variant - ~i.e. some efficacy but less then when compared to a WT state, or a different variation state~ used to state reduced efficacy when compared to another non-reference state - e.g. BCR-ABL vs BCR-ABL + M351T)

I bring this up because the implicit model of predictive evidence in CIViC is that every variant is with respect to the reference state unless otherwise specified, and there is no way (outside of free text) to assert an alternative comparator to the subject variant. This additional term was added to convey this complex meaning as described in the documentation, but in essence is a predicts_resistance_to relationship between the subject and an alternate non-reference states. This is important clinically, because variant callers (and the common notion of a "variant") are founded upon a "wild type" reference, and there was a valid concern that putting predicts_resistance_to as the value for such evidence may be misinterpreted as a comparison to the wild type state and adversely impact clinical care.
We should have a discussion about whether or not we intend to model this complexity (non-reference comparator) in therapeutic response statements, and the answer to that may inform the inclusion/exclusion of predicts_reduced_sensitivity_to in the value set.

Perhaps in initial release we can recommend to provide in free text comment field additional clarifications if predicts_reduced_sensitivity_to term is used.

We should have a discussion about whether or not we intend to model this complexity (non-reference comparator) in therapeutic response statements, and the answer to that may inform the inclusion/exclusion of predicts_reduced_sensitivity_to in the value set.

@rrfreimuth's post-doctoral fellow Yiqing is working with us on a project to more comprehensively evaluate and model different categories of TR statements found cross many KBs, using the VA Statement model.  I think her work will shed light on this issue.
I propose to table it for now - keep v0 TR statement as originally proposed, and refine later based on the more comprehensive requirements and examples provided by Yiqing's work.


Custom TitleBar Randomly Becomes Unclickable (fix #52522)

Refs #52522
Please test on macOS against regression before approving. (Don't have mine on me right now)
This is to address the issue where the mouse events are trapped in the draggable region of the titlebar even when we draw a non-draggable menu underneath. The hack forces a mouse out and in event to get cursor events back allowing the menubar to function properly. The repro is inconsistent, but I could not repro with this fix so I hope it works.

I feel like we could look into this for July, I would first like to understand the issue better and reproduce it (it does not reproduce in my VM).

@sbatten are you still planning to make changes here or should I review?

@bpasero we were holding off on this to see if the alt-toggle behavior change would resolve the issue. It doesn't seem to fix it, so I think this fix/a fix are still necessary

@sbatten yeah I am now hitting this also all the time

@bpasero the only way I can repro this now is by taking advantage of bad alt behavior that will be fixed tomorrow. it is probably still reproducible another way but more rare. further, showing and hiding the drag region in testing didn't work when I initially opened the PR which is we went with modifying the height (to trigger a mouse event). However, using builder.hide() is working right now. If we see errors in the future, we can make the change then. For now, I'll keep it simple as is.


Drush error when deploying DVM to prod w/DVM as a Composer dependency

Issue Type

Bug Report / Support Request

Your Environment

Vagrant 1.9.1
VirtualBox 5.1.12r112440
ansible <IP_ADDRESS>
  config file =
  configured module search path = Default w/o overrides

Your OS

macOS (version)
Linux (version)

Full console output
Refer to summary below for context.
DRUPALVM_ENV=prod ansible-playbook -i deploy/inventory vendor/geerlingguy/drupal-vm/provisioning/playbook.yml -e "config_dir=$(pwd)/config" --sudo --ask-sudo-pass

TASK [Install Drupal with drush.] **********************************************
fatal: [redacted]: FAILED! => {"changed": true, "cmd": ["/var/www/drupalvm/vendor/drush/drush/drush", "site-install", "standard", "-y", "--site-name=Drupal", "--account-name=admin", "--account-pass=redacted", "--db-url=mysql://redacted:redacted@localhost/redacted"], "delta": "0:00:00.117899", "end": "2017-01-09 19:51:12.269741", "failed": true, "rc": 1, "start": "2017-01-09 19:51:12.151842", "stderr": "Command site-install needs a higher bootstrap level to run - you will\u001b[31;40m\u001b[1m[error]\u001b[0m\nneed to invoke drush from a more functional Drupal environment to run\nthis command.\nThe drush command 'site-install standard' could not be executed.     \u001b[31;40m\u001b[1m[error]\u001b[0m", "stdout": "", "stdout_lines": [], "warnings": []}

Summary
I am working through the docs on deploying Drupal VM to a production environment with Drupal VM as a composer dependency. I have everything working as expected, up to a point. The local Vagrant instances spins out without any issues but I'm getting an error on the production side.
Local directories look like this:
config/config.yml (default)
config/local.config.yml #contains overrides for local Vagrant
config/prod.config.yml #contains overrides for remote server
config/Vagrantfile.local

prod.config.yml looks like this:
build_composer_project: false
build_composer: true
drupal_composer_path: false
drupal_composer_install_dir: "/var/www/drupalvm"
drupal_core_path: "{{ drupal_composer_install_dir }}/docroot"
drupal_composer_dependencies: []

Ansible roles successfully build the LAMP stack and Composer builds Drupal at docroot as expected, i.e.:
TASK [Run composer install.] ***************************************************
changed: [x.x.x.x]

So far, so good....but I'm getting hung up here:
TASK [Install Drupal with drush.] **********************************************

which throws the error pasted above. I can't tell why it's attempting to execute a Drupal install w/Drush.
build_makefile is set to false. So I'm not sure if I missed another override somewhere or there's some other variable I'm missing. I'm pretty sure I had this working correctly over the weekend....{grumble}

To skip the installation step you need to set install_site: false https://github.com/geerlingguy/drupal-vm/blob/master/default.config.yml#L70

FYI local.config.yml is loaded for both production and vagrant.  There's vagrant.config.yml if you need it.

Thanks for the tip @oxyc. I changed local.config.yml to vagrant.config.yml and everything now works as designed. As you described, the task runner was trying to load both local and prod. Still, I don't instructions for installing via drush in any of my configs.
build_composer_project: false
build_composer: true
drupal_composer_path: false
drupal_composer_install_dir: "/var/www/drupalvm"
drupal_core_path: "{{ drupal_composer_install_dir }}/docroot"
drupal_composer_dependencies: []

On another note, I've seen some discussion on further developing DVM for production use cases. Is there a coordinated effort on that front? To move it from "experimental" to "supported"? DVM is truly an incredibly useful development tool and, speaking for myself, I'd like to see it also regarded as a useful deployment tool. For frontend developers and designers, It's in a really nice sweet spot between cutting and pasting shell commands and full-blown devops deployment strategies.  Thanks again.

Hehe, same here. At least not for production. Not yet.

On another note, I've seen some discussion on further developing DVM for production use cases. Is there a coordinated effort on that front? To move it from "experimental" to "supported"?

It's mostly just my laziness. I don't have any automated testing set up on the prod side of things, so I can't guarantee changes won't break people's prod configurations. I think we could get around that by making a major caveat like always run updates in --check mode before deploying to production...

It's mostly just my laziness. I don't have any automated testing set up on the prod side of things

Travis tests this quite well no? Any additional features we should test? Saying that Drupal VM supports production use is a bit scary though...

Saying that Drupal VM supports production use is a bit scary though...

Yeah, that's the gist of it—I'd want to have my own servers running through Drupal VM for more assurance that I won't break things :)
A few of my servers have something I call 'Drupal VM lite' (basically a fork with almost nothing besides LAMP and a firewall), but nothing is running Drupal VM proper at this time.

I'd like a canary server, at least. Maybe I could toss my non-monetarily-important sites on a Drupal-VM-powered droplet?

A few of my servers have something I call 'Drupal VM lite' (basically a fork with almost nothing besides LAMP and a firewall), but nothing is running Drupal VM proper at this time.

We're currently running a basic intranet and a shared wildcard staging environment for 10+ small sites on Drupal VM–works great!

@oxyc - One thing I would like to add to make things even spiffier for prod is certbot/LE integration. I use it for most of my sites now and have mostly automated things, but my certbot role is still in need of a little extra TLC in terms of automating initial setup further.
Also, backup is another area that I have through a private role that I should really open source and make public (it backs up to another server over SSH, and grabs databases, files, etc. with configurable paths).

One thing I would like to add to make things even spiffier for prod is certbot/LE integration. I use it for most of my sites now and have mostly automated things, but my certbot role is still in need of a little extra TLC in terms of automating initial setup further.

Awesome, I was actually thinking about opening up an issue for this.

Also, backup is another area that I have through a private role that I should really open source and make public (it backs up to another server over SSH, and grabs databases, files, etc. with configurable paths).

I'm pretty sure we would use this if you release it.

I agree it is a pretty monumental shift in the declared intention of the project. (Think of it as bonus functionality!) I just can't think of another solution that works as well, short of writing my own fleet of ansible projects.
I guess my own use case is pretty constrained: small-ish 2-tier applications hosted on AWS (public facing www, db on a private subnet). I launch the EC2 instances with Terraform and let DVM do the rest. This works well for independent freelancer and small agency work, as most client requirements are satisfied by this approach.
I plan on documenting my approach and providing it to our community of users. It's a good exercise for me and would be useful to gauge interest.
If you're interested in taking input on incrementally adding support for additional features in production, I think ngnix and (very definitely) backups would be appreciated.

Do we want to change the title of this issue to something relevant in case others want to chime in?

@minorscience - How about we start a new issue, as this one has served its course :)

:thumbsup:

Just wanted to tack one quick question on to this thread. It looks like ansible isn't loading my local composer.json into the production environment.
TASK [Copy drush makefile into place.] *****************************************
skipping: [<IP_ADDRESS>]

TASK [Ensure drupal_core_path directory exists.] *******************************
skipping: [<IP_ADDRESS>]

TASK [Generate Drupal site with drush makefile.] *******************************
skipping: [<IP_ADDRESS>]

TASK [Check if a composer.json file is present.] *******************************
skipping: [<IP_ADDRESS>]

TASK [Run composer install if composer.json is present.] ***********************
skipping: [<IP_ADDRESS>]

TASK [Ensure drupal_composer_install_dir directory exists.] ********************
skipping: [<IP_ADDRESS>]

TASK [Copy composer.json into temporary location.] *****************************
skipping: [<IP_ADDRESS>]

TASK [Move composer.json into place.] ******************************************
skipping: [<IP_ADDRESS>]

TASK [Run composer install.] ***************************************************
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": true, "cmd": ["composer", "install"], "delta": "0:00:00.082901", "end": "2017-01-15 21:18:16.406508", "failed": true, "rc": 1, "start": "2017-01-15 21:18:16.323607", "stderr": "Composer could not find a composer.json file in /var/www/drupalvm\nTo initialize a project, please create a composer.json file as described in the https://getcomposer.org/ \"Getting Started\" section", "stdout": "", "stdout_lines": [], "warnings": []}

If I manually copy my composer.json file to /var/www/drupalvm and retry the playbook, all is well.
Looking at build-composer.yml task, it looks pretty straightforward, copying composer.json into /tmp, then moving it to the configured Drupal install directory.
Am I missing something?

Earlier you mentioned that you had:
drupal_composer_path: false

By doing this you're telling Drupal VM not to move a composer.json file into place. Combining this setting with:
build_composer: true

Requires you to have a composer.json already in place (the drupal_composer_install_dir directory).

The file set in drupal_composer_path (which defaults to drupal.composer.json) will be copied from your host computer into the VM's drupal_composer_install_dir and renamed composer.json. If you already have a composer.json within that directory, set drupal_composer_path: false.

http://docs.drupalvm.com/en/latest/deployment/composer/#using-composerjson

Right. My settings correspond to those stipulated here: http://docs.drupalvm.com/en/latest/deployment/composer/#using-composer-when-drupal-vm-is-a-composer-dependency-itself
and also referenced here:
http://docs.drupalvm.com/en/latest/other/production/#provision-drupal-vm-on-the-droplet
build_composer_project: false
build_composer: true
drupal_composer_path: false
drupal_composer_install_dir: "/var/www/drupalvm"
drupal_core_path: "{{ drupal_composer_install_dir }}/docroot"

So what's missing is a mechanism to upload the local composer.json to the remote host directory specified at drupal_composer_install_dir, correct?

Ah, yes you need to set the drupal_composer_path as there's no NFS/rsync to upload it to a remote environment otherwise.
Do you have your config.yml in the same directory as you composer.json, or did you set a config subdirectory with DRUPALVM_CONFIG_DIR?
If your composer.json file is in the same directory as your config.yml use:
drupal_composer_path: "{{ config_dir }}/composer.json"

If the configurations are in a subdirectory as shown in the example here, use:
drupal_composer_path: "{{ config_dir }}/../composer.json"

@minorscience any updates on this?

I'll close this as I assume you got it working. If not, please re-open and we can discuss it further.


add thai name to max and mark

cool, thanks!
megred

Seems to be conflicted. Could you please resolve it?

nvm, megred! #33


⚠ ClamAV has degraded performance

In 26700b5, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 76 ms

Resolved: ClamAV performance has improved in 5709962.


mbtiles

It would be great to also preview mbtiles
don't need to make mbtiles but load an mbtiles with tile_data with PNG or JPG tiles
separately, it would also be great to preview vector tiles mbtiles with PBF in tile_data

I am currently working on the MBTiles to GeoPackage converter.  I will keep this thread updated with progress.

Would like to also just view mbtiles just like geopackage tiles.  Without nodejs dependency. Just client side Javascript


Too much notitifications on low battery

It happened on sunday when my battery dropped under 15% and system activated a battery saver. When the screen was locked I was receiving new notification to stop the battery saver every few minutes.
Android 9, Nokia 8

Same for me. (same mobile, same OS version). And one more thing I can't remove notification with warning that app is inactive, even when I charged battery, activate / deactivate app. The notification is still here and can't be removed.

This issue is not happening in v2 version of the app, closing.


Migrating from ASB to DBaaS issues

When performing a migration from the ansible service broker in openshift, to the mariadb consumer resource for the dbaas-operator, there are some issues encountered that could cause a lot of issues.
Manually creating the mariadbconsumer resource works fine. But at the first deployment lagoon in openshift does an oc process, then oc apply of a template, and this overwrites what was manually created, and the dbaas attempts to provision a new database (and is successful) so the original database remains stale, and the new one is provisioned. So 2 databases/users now exist for that environment
Subsequent deployments result in an unchanged mariadbconsumer though, so I'm not sure what is happening here.
Here is where we do the oc process https://github.com/amazeeio/lagoon/blob/master/images/oc-build-deploy-dind/build-deploy-docker-compose.sh#L591-L604 then we oc apply it here https://github.com/amazeeio/lagoon/blob/master/images/oc-build-deploy-dind/build-deploy-docker-compose.sh#L895 with a bunch of other resources.
I'm not sure why this remains unchanged after the initial creation, but i think we should only oc process this resource if it doesn't exist.

Subsequent deployments result in an unchanged mariadbconsumer though, so I'm not sure what is happening here.

how do we create the mariadbconsumer resource during the migration? I could imagine that it is not created via kubectl apply and therefore the kubectl.kubernetes.io/last-applied-configuration is not existing, so the next time that lagoon adds the mariadbconsumer resource via kubectl apply the kubectl has no idea which fields have been added before and which not, so it overwrites the complete object.

I tried to do it the following ways, and both result in the resource being overwritten by lagoon and the dbaas attempting to provision a new database for the namespace.

straight up oc apply the full crd with all the information required

oc apply -f tmp.yml

doing it a similar way to how lagoon does it using oc process of a template

oc process -o yaml \
                -n ${1} \
                -f tmp.yml \
                -p SERVICE_NAME="${2}" \
                -p SAFE_BRANCH="${GIT_SAFE_BRANCH}" \
                -p SAFE_PROJECT="${PROJECT}" \
                -p ENVIRONMENT="${ENVIRONMENT_TYPE}"

I still think #2502 should be merged, because there isn't really any reason to apply or generate the consumer crd if it already exists?

Openshift doesn't exist anymore


Purplet depends on @discordjs/rest's cdn object which we didn't implement

We didn't implement this feature because it's not rest related, it's just url generating. We can create some utilities at some point. Will probably be closed during dev of purplet structures

Feels like something that should be put into buncord

@Clembs this would likely go into @purplet/structures directly when needed, or maybe do you think having a separate set of url formatter functions like getEmojiURL(emojiId, imageOpts) in a package like @purplet/utils (a package i've already wanted to make for some discord-specific utility functions we have).
all i know is the rest client seems like the wrong place for this logic since it's not the usual thing to be fetching these resources, and even if that was the case, they are not json results (obviously) and other implications.

I'm 100% on board with coding a @purplet/utils package, which I also thought of a while back.

closed with commit ce4f3fe


Update granulate-utils submodule to master

Related Issue
https://github.com/Granulate/gprofiler/issues/503

I think it will fail because https://github.com/Granulate/gprofiler/pull/483 wasn't merged yet and it has some fixes after updating granulate-utils. We will get to this PR after that one is merged

https://github.com/Granulate/gprofiler/pull/483 ended up updating granulate-utils to a newer commit, which includes your changes from https://github.com/Granulate/granulate-utils/pull/87, so we don't need it anymore :) Closing this one.


Shall we switch to GitFlow after (or before) v7 release?

Right now people are opening PR's against master instead of rxui7-master which makes their first experience with contributing not the smoothest. @kentcb is working on the v7 release and it is also causing him a bunch of pain, not to mention wasted effort on his and the communities part.

master is where stable nuget packages are produced from.
develop is where -pre nuget packages are produced from when CI is up and running.
maintainers/contributors submit PR's to the develop branch.

When a release is in the oven, you branch a release branch, make any necessary tweaks based on testing, then merge that to master (with a tag for that release).
https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow/
Also related to #1006 but we can start doing this practice before CI comes in.

I've switched the default branch to rxui7-master, we don't need git flow (and imho, neither does anyone else)

I'm not a huge fan of git flow, personally. IMHO, It's one of those things that developers do because they like, neat, ordered processes, but it's not a good idea in practice.

:thumbsup: to changing the default branch
I'm neutral to the Git Flow proposal - beyond "long lived branches are the devil" I don't have any strong opinions on branching flows...


Update UBI8 dockerfile with most recent CRIU artifactory binaries

fyi @tajila

@AdamBrousseau could you please review and merge this PR? We will need it for aarch64 testing. Thanks


SSO - turn off direct access grant for all Registry clients

Describe the issue
SSO team has reached out asking to turn off direct access grant for Registry clients in the realm.
Definition of done

[ ] discuss changes, update SSO team on timeline
[ ] test out in lower environment
[ ] push in changes

Shelly asked Oamar to create this ticket. For more information we can reach out to Shelly.


JavaScript parameter hints for local variable picking up signatures from @types

From https://github.com/Microsoft/vscode/issues/29269
TypeScript Version:  2.4.1
Code
For a javascript project with @types/jquery installed. In the file:
function foo() {
    const $ = 1
    $(
}

Trigger parameter hints on $(
Expected behavior:
No suggestion is shown or $(): void is shown. The latter is what happens if you use another variable name such as a instead of $
Actual behavior:
Suggestions for jquery are shown. Suggestions on $. do not show the jquery suggestions

the local const $ shadows the jquery $. that is what is gonna happen at runtime as well.

misunderstood the issue. in a .js file the signature help behavior is rather probabilistic. so it will search for some function that has this name, and will show that to you. in this case, it is the $. but that is how we can do things like:
function f(a) {
    a.forEach( | )
}

and get help for forEach.


Gather update methods to try to update faster

This may not be worth it though since it will likely result in more http connections to the device as well as asyncio.Task overhead. Needs testing

It actually seems to save quite a bit of time since the syno api startup overhead is what is inefficient and not the asyncio.Task overhead or connection overhead

Thanks


Picture Problems

I am trying to make a custom menu page and i have watched videos rechecked my config and i keep getting purple and black pictures witch meas the texture is not found.
Here are my resources,
In this example i am trying to load two separate pictures
mianmenu.jason - http://pastebin.com/eE9HRbd1
Minecraft Client - https://i.gyazo.com/5a4f9c24e35ef719e37bdfc8654f807a.png
Mods Folder - https://i.gyazo.com/52b5d646ccd090bf38f0882163417a03.png
Inside Resources Folder - https://i.gyazo.com/8f1e250de2aab5cf4e2af6de3dc0ee5f.png
Inside Resources/Modpack Folder - https://i.gyazo.com/c308780f17611d742c6641d5504f255c.png
It out I added the pictures after the fact and and did not restart my client. REMEBER TO RESTART YOUR CLIENT.
NOT REALLY AN ISSUE. A STATEMENT. EXCELLENT MOD

I might have lied... I went and moved the overlay not the background and the single player button. . I went in to full screen and the overlay and button did not go over to its respective spot is there a reason or how it works.

What do you mean "respective spot"? Did your config changes not have any effect?

I moved the picture to the left and when i went to full screen it stayed in the middle of the screen. So i moved it all the way to the left and after i moved it i minimized the screen and didn't see it anymore.

That's what alignments are for. They move the x:0,y:0 position for an element to a position that's relative to the screen size.

i think so...
As seen in this video https://www.youtube.com/watch?v=fwqKJRJBwQY
The creator has it in small screen 37;45 and when he flicks the full screen his layout stays the same mine gets hidden or stays small

"background":
{
        "image" : "",
        "slideshow":
        {
          "images": [ "modpack:textures/thisone.jpg", "modpack:textures/tester.jpg", "modpack:textures/ice.jpg", "modpack:textures/wond.jpg", "modpack:textures/land.jpg", "modpack:textures/north.jpg" ],
            "displayDuration" : 100,
            "fadeDuration" : 20
			"sync" : true


startup-scripts don't seem to work for Ubuntu 16.04 image

Version: ubuntu-1604-xenial-v20160922
Tried using the startup-script option as well as via Google Storage.

/cc @OddBloke
Thanks for the report - this appears to be an issue with the latest image release. As we work with Canonical to fix the issue, I'd suggest using the ubuntu-1604-xenial-v20160921 image.

The problematic image is rolled back so the issue should be (mostly) resolved.

Hey there,
Unfortunately this doesn't seem to be resolved (or I'm experiencing a similar issue). Here's my bug report on the old / other bug tracker: https://code.google.com/p/google-compute-engine/issues/detail?id=426
PS: I was able to reproduce the problem today. @illfelder

Oh I see, the Cloud Console says "amd64 xenial image built on 2016-09-21" so that obviously does not include the fix you mentioned above. When are images expected to be updated in Cloud Console?

/cc @gaughen

The existing image that you are running should work out of the box, however the issue presents after updating packages. Canonical is pushing package updates to close off the issue (followed by new images).

Any update on this issue? One and a half year passed and it's still not working for me.

Hi @Kamforka, could you give us an example gcloud command line that reproduces the problem you are seeing?

Hi @OddBloke this is my way of doing things:
I've set up a metadata for my Ubuntu 16.04 LTS compute engine instance as:
key: startup-script
value:
#! /bin/bash
su my_user -c gcsfuse my-storage /home/Storage/

I restarted the VM, did ssh into in through the web console. And noted that  the mount command specified in the startup wasn't executed.
Also tried to execute the startup-script manually like:
sudo google_metadata_script_runner --script-type startup
But nothing happened.

@OddBloke
Well it was my mistake, I used a different image that is not Ubuntu 16.04, but Debian stretch.
On the Ubuntu image it works fine, although I still don't understand why it does not on Debian?

@Kamforka I'd suggest opening a separate issue for that. :-)
@illfelder I think we can close this out now?

When running manually, add the debug flag to your command so you can see the script output:
sudo google_metadata_script_runner --script-type=startup --debug

We are facing the same problem. We upgraded from Ubuntu 14.04 to Ubuntu 16.04 (with apt-get dist-upgrade command) and startup scripts stopped working after the upgrade.
When we run manually the 14.04 version: sudo /usr/share/google/run-startup-scripts  it works
When we run manually the 16.04 version: sudo google_metadata_script_runner --script-type=startup --debug it returns sudo: google_metadata_script_runner: command not found
How to solve this?

@flaviokr Could you run dpkg -l | grep '\(gce\|goog\)' and paste the output here, please?

ii  gce-cloud-config                      1.2.2-0ubuntu2~14.10.0                      amd64        Configuration for Ubuntu on Google Compute Engine
ii  gce-daemon                            1.2.2-0ubuntu2~14.10.0                      amd64        Google daemon for configuring instances
ii  gce-imagebundle                       1.2.2-0ubuntu2~14.10.0                      amd64        Bundle image for use on Google Compute Engine
ii  gce-startup-scripts                   1.2.2-0ubuntu2~14.10.0                      amd64        Google Compute Engine Start-up scripts
ii  google-cloud-sdk                      0.9.37-20141125060859+dsf1-0ubuntu1~14.10.0 all          Google Cloud SDK for interacting with Google Cloud services.
ii  google-compute-engine-oslogin         20171129+dfsg1-0ubuntu1~16.04.0             amd64        Google Compute Engine OS Login

We installed google-compute-engine-oslogin recently while trying to fix this issue.

It looks like your VM is running a very old version of the guest environment. It's possible you're running into an issue we fixed in a guest environment change that you haven't yet updated to. We have instructions on how to update here: https://cloud.google.com/compute/docs/instances/linux-guest-environment. Let me know if you run into any problems.

problem exists with ubuntu18
dpkg -l | grep '\(gce\|goog\)'
ii  google-compute-engine              20210629.00-0ubuntu1~18.04.0              all          Google Compute Engine guest environment.
ii  google-compute-engine-oslogin      20210728.00-0ubuntu1~18.04.0              amd64        Google Compute Engine OS Login
ii  google-guest-agent                 20210629.00-0ubuntu1~18.04.1              amd64        Google Compute Engine Guest Agent
ii  google-osconfig-agent              20210608.1-0ubuntu1~18.04.1               amd64        Google OS Config Agent


revert Tables api to version 2020-08

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[v] SDK of .NET (need service team to ensure code readiness)
[v] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[v] PowerShell
[v] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@msyyc this PR is to revert Tables api versoin.

Hi @msyyc , @kairu-ms
can we merge this? I have to publish both Python and .NET SDK and this config block me

/azp run


LSTM with the new version of FINN

Hi,
I'm currently trying to implement an LSTM on FPGA using the "old" version (0.1) of FINN. I'm happy to see that the new version is on its way but I was wondering if the newer version will support LSTM networks. Having looked at brevitas and the finn-hlslib, there do not seem to be any references to LSTM or RNN networks in general.
Do you plan to support RNN / LSTM networks in the future?
Thank you for your time,
Phillip Geier

Hi Philip, LSTM are going to be supported on the Brevitas side at some point. They were in the original version (back when it was pytorch-quantization), but that was Pytorch 0.3.1 and everything has changed since then. The new implementation is going to be entirely JIT based (something like this). On the FINN side, @giuliogamba is more suited to answer.

Thank you very much for your quick reply, glad to hear that LSTM are going to be supported on Brevitas !

Hi Phillip ,
Supporting LSTMs for FINN-style compilation is not on the development roadmap at the moment as we're just working on bringing up the infrastructure for regular feedforward nets. Conceptually it's possible to support them, but this isn't high priority for the FINN team at the moment.
Is this something you are interested in? You may want to have a look at https://github.com/Xilinx/LSTM-PYNQ and check out this paper.

Yes I am interested in this. I had looked at the lstm-pynq repo and tried it out, and had a look at the paper but was curious about the new version of FINN :)
I understand that it is not a priority right now but I am still looking forward to this new version of FINN.
Than you for your work !


UI Refactoring list

Inputs

Single Line
Multi line
[ ] Font Styles
[ ] Buttons
[ ] Icons
[ ] Errors

https://zpl.io/2p4PP1M
Cells

Single Line
Multi line
[ ] Font Styles
[ ] Icons
[ ] Accessories
[ ] Dividers

https://zpl.io/2p4PP1M
Header / Footer

[ ] Light/Dark

Nav Bars

App Bar
Tab / Amount / Hash bar
Botton bar
[ ] Font Styles
[ ] Icons
[ ] Dividers

zpl.io/VqWnxj7
Controllers

Confirm
Receive
Send
Send Confirm
[ ] Font Style
[ ] Icons
[ ] New cells

https://zpl.io/aw4Pr8g

Most is done. Left part separated to issue #563


[FEAT] QD base code additions

query decomposition initial code
only notebooks included

Thanks for adding all this previous work! Could you provide explanations for each file?

File Breakdown

langchain_ms.ipynb - using LangChain to breakdown subqueries
MS_finetuning.ipynb - fine-tuning the query decomposition
rest - multi step query decomp examples


APPS-1328 Add operation error to log

added operation error processing

Codecov Report
Attention: Patch coverage is 57.14286% with 9 lines in your changes missing coverage. Please review.

Project coverage is 80.28%. Comparing base (cc6f134) to head (b6d1574).

Files with missing lines
Patch %
Lines

io/aerospike/record_batch_writer.go
57.14%
9 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #169      +/-   ##
==========================================
- Coverage   80.36%   80.28%   -0.08%
==========================================
  Files          96       96
  Lines        7211     7229      +18
==========================================
+ Hits         5795     5804       +9
- Misses       1056     1065       +9
  Partials      360      360

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


Modify existing azure pipelines credential test to see if invalid system access token test fails as expected

Investigating a similar test to https://github.com/Azure/azure-sdk-for-cpp/pull/5875

/azp run js - identity


Split Uint::mul_mod and Uint::mul_mod_vartime

The previous mul_mod was variable-time with respect to the modulus.
This adds a proper constant-time version.

An updated version of mul_mod_vartime would not require an odd modulus, but I think requiring a NonZero modulus would make sense.


Make all button width consistent in desktop mode

What

How it looks before:

After:

Also tested under mobile mode - it is still working great!

Why

How Tested

Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

I love the PR desc videos, super informative 👌❤


(fix) error when launching on macOS with disabled show unread badge

@JohnnyBui feel free to merge and release new version.

@denysdovhan I cannot pumb new version to master (package.json)

@JohnnyBui use this release checklist:

Draft a new release at Releases page
Pull all changes locally
Run npm version patch, npm version minor or npm version major to bump a version and create a tag
Push all changes with git push --follow-tags
Publish a release created at step 1

After passing a CI, all compiled binaries will be attached to the drafted release.
You can also check Recommended GitHub Releases Workflow

Cool. Thanks

When I do step 4, it says ! [remote rejected] master -> master (protected branch hook declined)

@JohnnyBui strange. master branch is protected. The rejection might happen because of force push.

@denysdovhan Do I need additional permission to push changes to master this case?


config/routes.rb:83:in `block in <top (required)>': uninitialized constant Subdomain (NameError)

Rails 3.1rc6
Problem solved by adding :
config.autoload_paths += Dir["#{config.root}/lib/**/"]
in config/application.rb

Adding
require 'subdomain'

before the routes block fixes this
Another alternative is to use lambda expression in your route so you have the logic in the routes constraint, like this
constraints: lambda {|request| request.subdomain.present? && request.subdomain != "www" }


Add locket client keepalive time and timeout to jobs

Follow up to this PR: https://github.com/cloudfoundry/diego-release/pull/675. I deleted that fork by mistake. Anyhow I have added template tests for the rep, auctioneer and bbs. We only test the new introduced props to the locket client. I imagine that these tests can be filled with all the needed cases in the future.

I have added another file called run-template-tests-in-docker which we execute in the docker shell script, right before we start the standard docker image. In this file we start a docker container with the ruby:3.0 image. I did this since we cannot execute the test in the other container, since there is not ruby on those images. @ameowlia Please let me know if this way is appropriate.

https://github.com/cloudfoundry/diego-release/pull/722


Identical image filenames are combined incorrectly

In Arknights for whatever reason, some enemies have the same filenames for their spine images such as enemy_1027_mob and enemy_1027_mob_2. For your project, these images appear separately in the unpacked folder. But when the transparency is applied, the project seems to only use the first one. Could you make it so all the images are processed?
I cant read Python or Chinese very well, but my first guess would be that it's because the alpha image is named "enemy_1027_mob[alpha]_#0" instead of "enemy_1027_mob_#0[alpha]".
Example:
Unpacked folder (red shirt guy is here)

Combined folder (red shirt guy is missing)

I just realized that if you are able to save files based on their actual enemy ID instead of the image filenames, so enemy_1027_mob and enemy_1027_mob_2 are in separate folders, then that would resolve this issue better.

Thank you for your investigation. It is confirm that these enemies can cause this bug :

1027_mob & 1027_mob_2
1036_amraoe & 1036_amraoe_2
1046_agent & 1046_agent_2
1047_sagent & 1047_sagent_2
1049_eagent & 1049_eagent_2
1286_dumcy & 1286_dumcy_2

In these cases, the "_2" model was named without the suffix "_2", so that they are recognized as the "non-2" models by our program. So, the suffix "#0" was automatically added to these different image files in the unpacking stage. However, the skel/atlas files of "_2" and "non-_2" have the same content, so they are not unpacked because of the same-file-conflict.
This circumstance we talking about is a historical problem of Arknights. Your advice is a helpful approach to solve this bug. To temporarily solve this bug, you can manually rename the conflicted files after the unpacking stage.
Internationalization of our Unpacker tool will be carried out in the next versions.


Good Great 👍 Parojakt

This issue tracker is only for technical issues related to AXE Core.
General AXE questions and/or support requests and are best directed to the Reddit or Slack.
To report critical security issues, email<EMAIL_ADDRESS>instead of creating Github issues.
Describe the issue
Can you reliably reproduce the issue?
If so, please list the steps to reproduce below:

Expected behaviour
Tell us what should happen
Actual behaviour
Tell us what happens instead
Screenshots.
If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.
What version of AXE Core are you using?
List the version number/commit ID, and if it is an official binary, self compiled or a distribution package such as PPA.
Machine specs:

OS:
CPU:
RAM:
Disk size:
Disk Type (HD/SDD):

Any extra information that might be useful in the debugging process.
This is normally the contents of a debug.log or config.log file. Raw text or a link to a pastebin type site are preferred.

🤔


Fix failing tests on Linux.

TrivialModelTests.testXOR has been failing on the Linux CI machine. It does not fail on macOS. This also seems related to the case where -O is enabled on the TensorFlow module in https://github.com/apple/swift/pull/25166.
Test Case 'TrivialModelTests.testXOR' started at 2019-05-31 07:16:34.843
931
Exited with signal code 11
932
The command '/bin/sh -c /swift-tensorflow-toolchain/usr/bin/swift test' returned a non-zero code: 1

cc @bgogul

Here is the stack trace of the crash:
* thread #1, name = 'TensorFlowPacka', stop reason = signal SIGSEGV: invalid address (fault address: 0x0)
  * frame #0: 0x00007ffff7c64a9b libswiftCore.so`swift_getAssociatedTypeWitnessSlowImpl(swift::MetadataRequest, swift::TargetWitnessTable<swift::InProcess>*, swift::TargetMetadata<swift::InProcess> const*, swift::TargetProtocolRequirement<swift::InProcess> const*, swift::TargetProtocolRequirement<swift::InProcess> const*) + 203
    frame #1: 0x00007ffff7c62f2e libswiftCore.so`swift_getAssociatedTypeWitness + 142
    frame #2: TensorFlowPackageTests.xctest`$s10TensorFlow20_ShapedArrayProtocolPA2aB7ElementRpzAD_ADQZAERSrlE11description33_DBF849D2A9DA24E23B4FF3FA4D3704F0LL11indentLevel04edgeF5Count15maxScalarLength0vwU7PerLine11summarizingSSSi_S3iSbtF at <compiler-generated>:0
    frame #3: TensorFlowPackageTests.xctest`$s10TensorFlow20_ShapedArrayProtocolPA2aB7ElementRpzAD_ADQZAERSrlE11description33_DBF849D2A9DA24E23B4FF3FA4D3704F0LL11indentLevel04edgeF5Count15maxScalarLength0vwU7PerLine11summarizingSSSi_S3iSbtF18elementDescriptionL_ySSAeaBRzAabERQAfERSlF at ShapedArray.swift:356
    frame #4: TensorFlowPackageTests.xctest`$s10TensorFlow20_ShapedArrayProtocolPA2aB7ElementRpzAD_ADQZAERSrlE11description33_DBF849D2A9DA24E23B4FF3FA4D3704F0LL11indentLevel04edgeF5Count15maxScalarLength0vwU7PerLine11summarizingSSSi_S3iSbtF18elementDescriptionL_ySSAeaBRzAabERQAfERSlFTA at <compiler-generated>:0
    frame #5: TensorFlowPackageTests.xctest`$s7ElementQzSSs5Error_pIgnozo_ABSSsAC_pIegnrzo_10TensorFlow20_ShapedArrayProtocolRzAdeBRQAA_AAQZABRSlTR at <compiler-generated>:0
    frame #6: TensorFlowPackageTests.xctest`$s7ElementQzSSs5Error_pIgnozo_ABSSsAC_pIegnrzo_10TensorFlow20_ShapedArrayProtocolRzAdeBRQAA_AAQZABRSlTRTA.29 at <compiler-generated>:0
    frame #7: 0x00007ffff79a7d0f libswiftCore.so`$sSlsE3mapySayqd__Gqd__7ElementQzKXEKlF + 751
    frame #8: TensorFlowPackageTests.xctest`$s10TensorFlow20_ShapedArrayProtocolPA2aB7ElementRpzAD_ADQZAERSrlE11description33_DBF849D2A9DA24E23B4FF3FA4D3704F0LL11indentLevel04edgeF5Count15maxScalarLength0vwU7PerLine11summarizingSSSi_S3iSbtF at ShapedArray.swift:370
    frame #9: TensorFlowPackageTests.xctest`$s10TensorFlow20_ShapedArrayProtocolPA2aB7ElementRpzAD_ADQZAERSrlE11description9lineWidth04edgeF5Count11summarizingSSSi_SiSbtF at ShapedArray.swift:405
    frame #10: TensorFlowPackageTests.xctest`$s10TensorFlow11ShapedArrayV11descriptionSSvg at ShapedArray.swift:733
    frame #11: TensorFlowPackageTests.xctest`$s10TensorFlow0A0V11descriptionSSvg at Tensor.swift:419
    frame #12: TensorFlowPackageTests.xctest`$s10TensorFlow0A0VyxGs23CustomStringConvertibleAAsAEP11descriptionSSvgTW at <compiler-generated>:0
    frame #13: 0x00007ffff7a0833d libswiftCore.so`$ss15_print_unlockedyyx_q_zts16TextOutputStreamR_r0_lF + 765
    frame #14: 0x00007ffff7f07f43 libXCTest.so`$s6XCTest14XCTAssertEqual___4file4lineyxyKXK_xyKXKSSyXKs12StaticStringVSutSQRzlFAA19_XCTAssertionResult33_F1DE58039960C6E2C9E25CD38F016B36LLOyKXEfU_Tm + 275
    frame #15: 0x00007ffff7f07bed libXCTest.so`$s6XCTest14XCTAssertEqual___4file4lineyxyKXK_xyKXKSSyXKs12StaticStringVSutSQRzlFTm + 61
    frame #16: 0x00007ffff7f06cab libXCTest.so`$s6XCTest14XCTAssertEqual___4file4lineyxyKXK_xyKXKSSyXKs12StaticStringVSutSQRzlF + 91
    frame #17: TensorFlowPackageTests.xctest`$s15TensorFlowTests012TrivialModelC0C7testXORyyF at TrivialModelTests.swift:56
    frame #18: TensorFlowPackageTests.xctest`$s15TensorFlowTests012TrivialModelC0C7testXORyyFTA at <compiler-generated>:0
    frame #19: TensorFlowPackageTests.xctest`$sIeg_ytIegr_TR at <compiler-generated>:0
    frame #20: TensorFlowPackageTests.xctest`$sIeg_ytIegr_TRTA at <compiler-generated>:0
    frame #21: 0x00007ffff7eff201 libXCTest.so`$sytIegr_Ieg_TRTA + 17
    frame #22: 0x00007ffff7eff25e libXCTest.so`$s6XCTest4test33_3BE257A46ADB477C7BF2D39968B39F9DLLyyAA0A4CaseCKcyyKcxcAERbzlFyAEKcfU_TA + 78
    frame #23: 0x00007ffff7eff1d4 libXCTest.so`$s6XCTest0A4CaseCs5Error_pIeggzo_ACytsAD_pIegnrzo_TRTA + 20
    frame #24: 0x00007ffff7ef2da7 libXCTest.so`$s6XCTest0A4CaseCyts5Error_pIegnrzo_ACsAD_pIeggzo_TRTA + 39
    frame #25: 0x00007ffff7efe849 libXCTest.so`$s6XCTest0A4CaseC10invokeTestyyF + 73
    frame #26: 0x00007ffff7efe50c libXCTest.so`$s6XCTest0A4CaseC7performyyAA0A3RunCF + 172
    frame #27: 0x00007ffff7f023df libXCTest.so`$s6XCTestAAC3runyyF + 191
    frame #28: 0x00007ffff7f00068 libXCTest.so`$s6XCTest0A5SuiteC7performyyAA0A3RunCF + 232
    frame #29: 0x00007ffff7f023df libXCTest.so`$s6XCTestAAC3runyyF + 191
    frame #30: 0x00007ffff7f00068 libXCTest.so`$s6XCTest0A5SuiteC7performyyAA0A3RunCF + 232
    frame #31: 0x00007ffff7f023df libXCTest.so`$s6XCTestAAC3runyyF + 191
    frame #32: 0x00007ffff7efd4b3 libXCTest.so`$s6XCTest7XCTMainys5NeverOSayAA0A4CaseCm04testD5Class_SaySS_yAFKctG8allTeststGF + 1091
    frame #33: TensorFlowPackageTests.xctest`main at LinuxMain.swift:7
    frame #34: 0x00007fffebeef2b1 libc.so.6`__libc_start_main + 241
    frame #35: 0x000055555561d21a TensorFlowPackageTests.xctest`_start + 42

Could be related to https://github.com/apple/swift/pull/23837.

@rxwei, I think you are right. It looks like the assertion in that test fails and xctest is trying to print a message with the tensor.

If it takes too long to fix, it’s fine to revert it to get a green build status first. The tensor pretty printing implementation is known to have other bugs as well.

@bgogul @rxwei also dataset tests fail.

I think I found the problem and it has to do with the code for the TensorFlow library multiple times: once during the compilation of stdlib and once during the compilation of tests. I removed the code from TensorFlow/CMakeLists.txt, rebuilt the whole toolchain and the tests pass.
Here is a possible plan forward:

on apple/swift:tensorflow, remove the code from TensorFlow/CMakeLists.txt and disable all the TensorFlow tests
get CI to green
migrate all the tests from apple/swift:tensorflow to swift-apis

@bgogul what do you mean when you say "code"? Is it just the tests code being duplicate? Or do you also refer to the sources of the TensorFlow module itself? If it is the sources of the TensorFlow module, I'm not sure how we can remove them but keep it part of the standard library.
I wonder what @testable import TensorFlow does. Does it prioritize the local TensorFlow module or does it also import stuff from the stdlib? I generally don't understand how name collisions like that are handled in Swift.

I wonder what @testable import TensorFlow does. Does it prioritize the local TensorFlow module or does it also import stuff from the stdlib? I generally don't understand how name collisions like that are handled in Swift.

@testable import imports a module that has been compiled for testing. If a module is compiled for testing, all internal symbols will be accessible to whoever imports it using @testable import.
I don't see any way @testable import TensorFlow can import the TensorFlow module that's part of the Swift for TensorFlow toolchain, because the one in the toolchain has not been compiled for testing and thus cannot be imported this way.

@bgogul what do you mean when you say "code"? Is it just the tests code being duplicate? Or do you also refer to the sources of the TensorFlow module itself? If it is the sources of the TensorFlow module, I'm not sure how we can remove them but keep it part of the standard library.

I meant the TensorFlow module. For the time being, I am building a toolchain with the tensorflow-swift-apis so that we can use it to run tests in swift-apis repository.
For testing things locally on your machine, just rename tensorflow-swift-apis to something else and rebuild the toolchain.

@bgogul does #163 solve these issues?

Yes, Pawan. Let us close this issue then?
On Sat, Jun 1, 2019, 9:25 AM Pawan Sasanka Ammanamanchi <
<EMAIL_ADDRESS>wrote:

@bgogul https://github.com/bgogul does #163
https://github.com/tensorflow/swift-apis/pull/163 solve these issues?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/swift-apis/issues/161?email_source=notifications&email_token=ABTJAKYOJFZOPQLYZU6VLHLPYKPH5A5CNFSM4HRV67A2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXD26I#issuecomment-497958265,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABTJAK6ADRRJDGLUZZWSF7TPYKPH5ANCNFSM4HRV67AQ
.

@bgogul Yeah, We should.


Data set

Thank you very much for the code you provided. As a novice of SR task, I want to ask how to design my own dataset. Will it have a better effect on SRGAN and other networks

@kill4nia11x @
Duplicate of #13


⚠ Orpheus has degraded performance

In 0df9a04, Orpheus ($OPS) experienced degraded performance:

HTTP code: 504
Response time: 20871 ms

Resolved: Orpheus performance has improved in c6e919b.