Models that depend on external models do not automatically register their dependencies as views

Suppose we specify +materialization: external in our dbt_project.yml.
Initially we run all dbt computations using an in-memory db, materializing all the models as parquet files.
Subsequently we change one dbt model A, and want to recompute model A (and possibly downstream dependencies as well).
Now, if A depends on upstream models B and C, trying to run just A will result in a failure. Because, B and C are not registered as views yet (in-memory db!), despite all tables being specified as external. This forces the user to always recompute upstream dependencies just to trigger the registration logic https://github.com/jwills/dbt-duckdb/blob/master/dbt/include/duckdb/macros/materializations/external.sql#L51-L55
I'd like to propose putting in a check in the materialization macros to

loop through the parent nodes
for each parent_node, if load_cached_relation(parent_node) is None, call the registration logic.

Does this sound reasonable? Happy to send a PR.

The problem as you describe it makes sense, but I still don't totally grok the use case where folks are running stuff entirely in-memory over-and-over again without using a DuckDB database file, even if it's just to keep track of view definitions and how they map to external parquet files. Where does this sort of thing come up?

Suppose you have a dbt graph containing several hundred models. Different sets of sources are updated at different times (or one might update a few model definitions), and you spin off Kubernetes jobs that recompute the affected subsets of the graph.
With a centralized DuckDB database file, you would need some locking mechanism allowing only one job at a time to take ownership of the DuckDB file.
There is also the temporary instability of the DuckDB storage format, which makes sharing the db files across different jobs with possibly different DuckDB versions a bit annoying.

yes, got it-- thank you so much for taking the time to explain it! A PR would be most welcome!


pandoc build dependency, Data.Digest.Pure.SHA, is broken on i686-linux

Describe the bug
pandoc is not compiling because one of the build dependencies, namely Data.Digest.Pure.SHA (pname is simply SHA) is running out of memory.
Steps To Reproduce
Steps to reproduce the behavior:

nix build nixpkgs#legacyPackages.i686-linux.pandoc
Observe a build dependency failure

Please note that apparently GHC is a little-bit memory hungry as it is, so if you got less than 8 gigs of RAM you might be in trouble when building, like me.
Expected behavior
SHA builds and allows the pandoc build to proceed.
Screenshots

Build log of SHA

@nix { "action": "setPhase", "phase": "setupCompilerEnvironmentPhase" }
setupCompilerEnvironmentPhase
Build with /nix/store/n11yp7hqsl87wxmm5088vpb5bsicjysx-ghc-8.10.4.
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/ycp1zbir38w1vmpi5qj2gindib7l8kv0-SHA-<IP_ADDRESS>.tar.gz
source root is SHA-<IP_ADDRESS>
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file SHA-<IP_ADDRESS>/src/Test.hs
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
@nix { "action": "setPhase", "phase": "compileBuildDriverPhase" }
compileBuildDriverPhase
setupCompileFlags: -package-db=/build/setup-package.conf.d -j4 +RTS -A64M -RTS -threaded -rtsopts
[1 of 1] Compiling Main             ( Setup.hs, /build/Main.o )
Linking Setup ...
@nix { "action": "setPhase", "phase": "configurePhase" }
configuring
configureFlags: --verbose --prefix=/nix/store/l4j47i2ax9gd0dfarmigywy39iv5gl3b-SHA-<IP_ADDRESS> --libdir=$prefix/lib/$compiler --libsubdir=$abi/$libname --docdir=/nix/store/8vc02mfjqq0dnr1aim9bqkplb74x172v-SHA-<IP_ADDRESS>-doc/share/doc/SHA-<IP_ADDRESS> --with-gcc=gcc --package-db=/build/package.conf.d --ghc-options=-j4 +RTS -A64M -RTS --disable-split-objs --enable-library-profiling --profiling-detail=exported-functions --disable-profiling --enable-shared --disable-coverage --enable-static --disable-executable-dynamic --enable-tests --disable-benchmarks --enable-library-vanilla --disable-library-for-ghci --ghc-option=-split-sections --extra-lib-dirs=/nix/store/5wzqfqrdcsfqrmizmijr447and87jihd-ncurses-6.2/lib --extra-lib-dirs=/nix/store/029vwxq4yiqjz6c7vyrjlsi01x9kpnkk-libffi-3.3/lib --extra-lib-dirs=/nix/store/gzvqayajz9mybk594mvpw62pj1lv2fdj-gmp-6.2.1/lib
Using Parsec parser
Configuring SHA-<IP_ADDRESS>...
Flags chosen: exe=False
Dependency array >0 && <10000: using array-<IP_ADDRESS>
Dependency base >=4 && <6: using base-<IP_ADDRESS>
Dependency binary >=0.7 && <10000: using binary-<IP_ADDRESS>
Dependency bytestring >0.8 && <10000: using bytestring-<IP_ADDRESS>
Dependency QuickCheck >=2.5 && <3: using QuickCheck-2.14.2
Dependency array >0 && <10000: using array-<IP_ADDRESS>
Dependency base >4.3 && <7: using base-<IP_ADDRESS>
Dependency binary >=0.7 && <10000: using binary-<IP_ADDRESS>
Dependency bytestring >0.8 && <10000: using bytestring-<IP_ADDRESS>
Dependency test-framework >=<IP_ADDRESS> && <10000: using test-framework-<IP_ADDRESS>
Dependency test-framework-quickcheck2 >=<IP_ADDRESS> && <10000: using
test-framework-quickcheck2-<IP_ADDRESS>
Source component graph:
    component test:test-sha
    component lib
Configured component graph:
    component SHA-<IP_ADDRESS>-HSZ2egT8UYEJq9usxpdv1M-test-sha
        include QuickCheck-2.14.2-1nXrGtwtRp61bfajuQjq0X
        include array-<IP_ADDRESS>
        include base-<IP_ADDRESS>
        include binary-<IP_ADDRESS>
        include bytestring-<IP_ADDRESS>
        include test-framework-<IP_ADDRESS>-2vXDmDjWy8Q68guNZRkFo7
        include test-framework-quickcheck2-<IP_ADDRESS>-7dbPbVbJJ0nFK2uFcv0ZBV
    component SHA-<IP_ADDRESS>-Dz94o1VCJW37O5q6cnweGF
        include array-<IP_ADDRESS>
        include base-<IP_ADDRESS>
        include binary-<IP_ADDRESS>
        include bytestring-<IP_ADDRESS>
Linked component graph:
    unit SHA-<IP_ADDRESS>-HSZ2egT8UYEJq9usxpdv1M-test-sha
        include QuickCheck-2.14.2-1nXrGtwtRp61bfajuQjq0X
        include array-<IP_ADDRESS>
        include base-<IP_ADDRESS>
        include binary-<IP_ADDRESS>
        include bytestring-<IP_ADDRESS>
        include test-framework-<IP_ADDRESS>-2vXDmDjWy8Q68guNZRkFo7
        include test-framework-quickcheck2-<IP_ADDRESS>-7dbPbVbJJ0nFK2uFcv0ZBV
    unit SHA-<IP_ADDRESS>-Dz94o1VCJW37O5q6cnweGF
        include array-<IP_ADDRESS>
        include base-<IP_ADDRESS>
        include binary-<IP_ADDRESS>
        include bytestring-<IP_ADDRESS>
        Data.Digest.Pure.SHA=SHA-<IP_ADDRESS>-Dz94o1VCJW37O5q6cnweGF:Data.Digest.Pure.SHA
Ready component graph:
    definite SHA-<IP_ADDRESS>-HSZ2egT8UYEJq9usxpdv1M-test-sha
        depends QuickCheck-2.14.2-1nXrGtwtRp61bfajuQjq0X
        depends array-<IP_ADDRESS>
        depends base-<IP_ADDRESS>
        depends binary-<IP_ADDRESS>
        depends bytestring-<IP_ADDRESS>
        depends test-framework-<IP_ADDRESS>-2vXDmDjWy8Q68guNZRkFo7
        depends test-framework-quickcheck2-<IP_ADDRESS>-7dbPbVbJJ0nFK2uFcv0ZBV
    definite SHA-<IP_ADDRESS>-Dz94o1VCJW37O5q6cnweGF
        depends array-<IP_ADDRESS>
        depends base-<IP_ADDRESS>
        depends binary-<IP_ADDRESS>
        depends bytestring-<IP_ADDRESS>
Using Cabal-<IP_ADDRESS> compiled by ghc-8.10
Using compiler: ghc-8.10.4
Using install prefix: /nix/store/l4j47i2ax9gd0dfarmigywy39iv5gl3b-SHA-<IP_ADDRESS>
Executables installed in:
/nix/store/l4j47i2ax9gd0dfarmigywy39iv5gl3b-SHA-<IP_ADDRESS>/bin
Libraries installed in:
/nix/store/l4j47i2ax9gd0dfarmigywy39iv5gl3b-SHA-<IP_ADDRESS>/lib/ghc-8.10.4/i386-linux-ghc-8.10.4/SHA-<IP_ADDRESS>-Dz94o1VCJW37O5q6cnweGF
Dynamic Libraries installed in:
/nix/store/l4j47i2ax9gd0dfarmigywy39iv5gl3b-SHA-<IP_ADDRESS>/lib/ghc-8.10.4/i386-linux-ghc-8.10.4
Private executables installed in:
/nix/store/l4j47i2ax9gd0dfarmigywy39iv5gl3b-SHA-<IP_ADDRESS>/libexec/i386-linux-ghc-8.10.4/SHA-<IP_ADDRESS>
Data files installed in:
/nix/store/l4j47i2ax9gd0dfarmigywy39iv5gl3b-SHA-<IP_ADDRESS>/share/i386-linux-ghc-8.10.4/SHA-<IP_ADDRESS>
Documentation installed in:
/nix/store/8vc02mfjqq0dnr1aim9bqkplb74x172v-SHA-<IP_ADDRESS>-doc/share/doc/SHA-<IP_ADDRESS>
Configuration files installed in:
/nix/store/l4j47i2ax9gd0dfarmigywy39iv5gl3b-SHA-<IP_ADDRESS>/etc
No alex found
Using ar found on system at:
/nix/store/5c0w4vyxxg6zlxwajcssnknh12ps1dgk-binutils-2.35.1/bin/ar
No c2hs found
No cpphs found
No doctest found
Using gcc version 10.3.0 given by user at:
/nix/store/wjg50hjgmjxy76dikggxi6pbcyjss5za-gcc-wrapper-10.3.0/bin/gcc
Using ghc version 8.10.4 found on system at:
/nix/store/n11yp7hqsl87wxmm5088vpb5bsicjysx-ghc-8.10.4/bin/ghc
Using ghc-pkg version 8.10.4 found on system at:
/nix/store/n11yp7hqsl87wxmm5088vpb5bsicjysx-ghc-8.10.4/bin/ghc-pkg
No ghcjs found
No ghcjs-pkg found
No greencard found
Using haddock version 2.24.0 found on system at:
/nix/store/n11yp7hqsl87wxmm5088vpb5bsicjysx-ghc-8.10.4/bin/haddock
No happy found
Using haskell-suite found on system at: haskell-suite-dummy-location
Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
No hmake found
Using hpc version 0.68 found on system at:
/nix/store/n11yp7hqsl87wxmm5088vpb5bsicjysx-ghc-8.10.4/bin/hpc
Using hsc2hs version 0.68.7 found on system at:
/nix/store/n11yp7hqsl87wxmm5088vpb5bsicjysx-ghc-8.10.4/bin/hsc2hs
Using hscolour version 1.24 found on system at:
/nix/store/ai1c2wq5kg9n3mhbm9fvdj8c7mzvnjp7-hscolour-1.24.4/bin/HsColour
No jhc found
Using ld found on system at:
/nix/store/ddj4zljp77l59srl7vl4l2l5sq03qlxk-binutils-wrapper-2.35.1/bin/ld.gold
No pkg-config found
Using runghc version 8.10.4 found on system at:
/nix/store/n11yp7hqsl87wxmm5088vpb5bsicjysx-ghc-8.10.4/bin/runghc
Using strip version 2.35 found on system at:
/nix/store/5c0w4vyxxg6zlxwajcssnknh12ps1dgk-binutils-2.35.1/bin/strip
Using tar found on system at:
/nix/store/xnxwiby237risq8phndpvk4qlli0vgbn-gnutar-1.34/bin/tar
No uhc found
@nix { "action": "setPhase", "phase": "buildPhase" }
building
Preprocessing test suite 'test-sha' for SHA-<IP_ADDRESS>..
Building test suite 'test-sha' for SHA-<IP_ADDRESS>..
: warning: [-Wmissing-home-modules]
These modules are needed for compilation but not listed in your .cabal file's other-modules:
Data.Digest.Pure.SHA
[1 of 2] Compiling Data.Digest.Pure.SHA ( src/Data/Digest/Pure/SHA.hs, dist/build/test-sha/test-sha-tmp/Data/Digest/Pure/SHA.o )

Additional context
The build is reproducible on latest nixos-unstable and breaking important stuff, such as the entirety of XFCE.
Notify maintainers

nix-repl> :p (builtins.getFlake "github:NixOS/nixpkgs/nixos-unstable").legacyPackages.${builtins.currentSystem}.haskellPackages.SHA.meta.maintainers or []
[]

cc @peti - was the last one who touched the lines (git blame) and happens to be the maintainer for Pandoc, so I guess they'll be the most competent person to investigate this
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.57, NixOS, 21.11 (Porcupine)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.4pre20210802_47e96bb`
 - channels(root): `""`
 - nixpkgs: `/nix/store/cykxhgky0kfgv37afd3xms9iscsnh0dh-source`

Please note: this is reproducible on the latest unstable version. Haven't tried master yet, but since my git changelog doesn't show updates to haskellPackages nor to Pandoc, I assume it'll be the same.
For the record: the latest unstable at the time of writing this is a51aa6523bd8ee985bc70987909eff235900197a.
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
 - pandoc
 - haskellPackages.SHA
# a list of nixos modules affected by the problem
module:

@kisik21 There are not many people testing Haskell-related stuff on i686-linux.
If you (or anyone else) want to figure out and send a fix for this, we would likely merge it.   But I imagine it is unlikely one of the Haskell maintainers here in Nixpkgs will look into this.


docs: redundant closing parenthesis in README.md

There is a redundant closing parenthesis in the Advanced usage section in the project README.md.

Thanks!


feat: add new property argsString

Fixes #138

I'm testing this way:

Hmm, I like this, since it takes parsing away from extension :)
Did you test the case where argsString is not set in launch.json?

I forgot to say, it is WIP. I should at least test it more extensively.

I'm using this to test:
https://github.com/felipecassiors/vscode-bash-debug-test

Hmm, I like this, since it takes parsing away from extension :)
Did you test the case where argsString is not set in launch.json?

Tested, and now it works. However, the solution is a bit clunky.

https://github.com/felipecassiors/vscode-bash-debug-test

@rogalmic what do you think now?

I would prefer to additionally handle empty argString in extension.ts -> resolveDebugConfiguration(), just to keep handling consistent. The changes in other files are fine.
See how args are handled:
		// Fill non-"required" attributes with default values to prevent bashdb (or other programs) from panic
		if (!config.args) {
			config.args = [];
		}
		else if (!Array.isArray(config.args)) {
			return vscode.window.showErrorMessage("Please specify `args` as array of strings in launch.json.").then(_ => { return undefined; });
		}

Fixed due to your comment, way better indeed.
I also used a new approach for your argument parsing. shell-quote already provides a method for transforming args array into a string, so why not use it instead? And also, I perform no parsing anymore at argsString. The value should be already properly escaped under JSON, and in case we use the input, it will also write the values accordingly in the JSON. This enabled a much cleaner usage, take a look at how do I pass environment variables and even expansive commands.

I think this is now ready for your testing/merging. I suggest merging this PR using squash.

OK, looks very good. I will merge this to master, then test a bit. Afterwards it will be released.
It will be available for manual install* under downloads@latest link in:
https://marketplace.visualstudio.com/items?itemName=rogalmic.bash-debug

This will have same version as current release, so manual uninstall + vscode restart is needed.

Awesome, I'm already using it! 👍


refactor timing code into the core

Currently the timing is implemented 3 times in different files (output handlers)
The code should be refactored such that the time measurements are in the core, and the results are exposed to the output handlers.

fixed by #483


Lazy load pretty library, used in the HTML block

@sneridagh long time wish of mine became true! Thank you!!! :)


Adding htmlUrl attribute to github-user

Looks like the build is failing, can you investigate?

@elwayman02 might be related to deprecation warning for _lookupFactory in beta.
I moved beta into allowed failures.
It's complaining that since this is used: https://github.com/alexander-alvarez/ember-data-github/blob/patch-1/addon/adapters/github.js#L9 you need to add needs: ['service:github-session'] to all the adapter tests, but I don't know why, so I didn't want to just treat the symptoms if there's something underlying that's needs to be updated, which will remove the need to do this.

Merging for now, but we should probably just add the needs and not allow beta failures in the future. Don't want to block this PR, though.


guacamole_connection_ssh -> terminal_type -> xterm-25color is bad value

Hi
I found a potential little mistake on a value checked for guacamole_connection_ssh -> terminal_type : xterm-25color

it should be xterm-256color

CLI htop is not working properly as it use $TERM env var

Terraform Version
Terraform v1.4.5
on linux_amd64

Guacamole provider version
techbeck03/guacamole v1.4.1

Affected Resource

guacamole_connection_ssh

Terraform Configuration Files
resource "guacamole_connection_ssh" "conn_ssh" {
  ...
  parameters {
    ..
    terminal_type = "xterm-25color"
  }
}

Expected Behavior
allow xterm-256color value instead of xterm-25color for terminal_type parameter
Actual Behavior
terraform apply is OK, but the $TERM is not correct for some linux CLI tools
arnault.michel@test-host:~$ htop
Error opening terminal: xterm-25color.
arnault.michel@test-host:~$ echo $TERM
xterm-25color

Steps to Reproduce
Please list the steps required to reproduce the issue, for example:

terraform apply
open the SSH connection to the linux VM
launch htop

References
please change the documentation

This is definitely a bug. Even in the Gucacamole UI, you can see it should be xterm-256color. Unfortunately, this bug means that xterm-256color cannot be set with this Terraform provider, since the incorrect value seems to be simply ignored by Guacamole (so terminal type ends up being set to nothing).

Opened #16 to fix this. It is really straightforward.

Thanks, I’ll work on applying the fix
On Fri, Nov 29, 2024 at 2:28 PM Thomas McKanna @.***>
wrote:

Opened #16
https://github.com/techBeck03/terraform-provider-guacamole/pull/16 to
fix this. It is really straightforward.
—
Reply to this email directly, view it on GitHub
https://github.com/techBeck03/terraform-provider-guacamole/issues/15#issuecomment-2508613526,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACXY3EZGXYESUJZ7O4LCEX32DDE77AVCNFSM6AAAAABSXWLTCWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBYGYYTGNJSGY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>


Source classes for MBE

Source 1: Effusion cell

type: single or dual filament cell
crucible

source_material
geometry

heater
thermometer

Source 2: Plasma sources

type: RF plasma source
RF generator
geometry (shared with other sources)
gas_flow

@hampusnasstrom we'll need to figure out some harmonization with the existing sources

The classes have been dropped in PDI plugin. They will be revised and dragged here later


Enable noImplicitAny TypeScript compiler option

What does this pull request do?
Enables the noImplicitAny TypeScript compiler option and fixes the resulting build failures.
What is the intent behind these changes?
To improve type safety and codebase understandability. See commit message for more details.

Closing this because Circle is refusing to build it, will reopen


AWS AppRunner setup w/postgres RDS

Resolves Notion ticket

[x] Depends on #265
[x] Depends on #266

Changes:

[x] Read only DB access for sql-explorer app. psql docs. Resolves Notion ticket.
[x] Add logging (resolves Notion ticket)
[x] Add apprunner.yml, biospecdb/settings/aws.py, and scripts/prd/deploy.sh for AWs app runner config.
[x] Add makesuperuser Django management command to wrap createsuperuser but not fail on existing user creation.
[x] Serve static files from gunicorn using whitenoise package.
[x] Add deployment script.
[x] Add django settings file for AWS deployment.
[x] Postgres

[x] Switch DB from sqlite to postgres.
[x] Fix sql view creation for postgres.

[x] Drop view even for postgres since column names can't be updated, only appended. This won't work if observables are deleted. See docs:

CREATE OR REPLACE VIEW is similar, but if a view of the same name already exists, it is replaced. The new query must generate the same columns that were generated by the existing view query (that is, the same column names in the same order and with the same data types), but it may add additional columns to the end of the list. The calculations giving rise to the output columns may be completely different.

[x] Refactor management command update_sql_views to not update all views. Due to psql's CASCADE view deletion, automatic view deletion requires that they get deleted and created in a specific order. To do this, the cmd would have to correctly graph the views and deps to correctly create this order - which just isn't worth it. Without this correct order, views created can be subsequently dropped and left non-existent if sub-views are created (and thus dropped) afterward.
[ ] ~MATERIALIZED vs normal views in postgres and vs those with sqlite?~ Simpler not to due to creation testing issues and errors thrown destroying transactions.

[x] Catch ProgrammingError when catchingOpertaionalError.
[x] Don't store app version as model field default as it causes migration issues with postgres (and isn't a good idea anyhow), instead use a callable.
[x] Fix issue with makemigrations in relation to observable access during ObservationInline.__init__.

[x] Don't serve static files from nginx for docker-compose.yml.
[x] S3

[x] Store and serve media files from S3, not local fs and nginx.
[x] Encryption at rest. S3's default see docs.
[x] Check file cleanup commands still work. Moved to #265
[x] Add cron job to deploy.sh. Depends on #266
[x] ~django-storage docs imply that files actually get deleted when DB entries are, check this and it would solve the above cleanup issue.~ Maybe, but doesn't matter as DB deletions happen from the admin forms using bulk deletions which are raw SQL and side step a model's delete method. Moved to #265
[x] Check exporters work with S3, e.g., zipping all data files together.
[x] Check bug in sqlexplorer app for full_patient. Looks like data isn't being loaded, resulting in an exception and charts not being loaded. ~Could just be an issue with the data as we're using the test data.~ This probably more like an S3 vs fs issue.

@amitschang Sorry for the lengthy PR 😬 . I really should have split this out into a few PRs but here we are. Cheers.

@amitschang FYI I just added another commit 6087f702d3b59b39dd36e399da500abf7f451024.


MH-13543 Rework workflow conditions, add string data type

This PR reworks the “execution conditions” (the if="…" attribute on workflow operations). In the following mostly backwards-compatible kind of way:
Switch the parser
After variable placeholders like ${foo} are replaced in the condition string, we are left with a string denoting a boolean expression, like true AND (1 < 2). This is currently parsed using the critically acclaimed functional library.
This PR removes the dependency on functional and instead adds a new, separate Opencast module which uses ANTLR to parse and interpret those strings. ANTLR generates Java code from a special grammar file, which looks very similar to the grammar given in the official Opencast developer documentation.
The code for replacing the variable placeholders was moved to this new module as well, as it seemed a bit more fitting.
Add strings as possible values
The original condition language only knew booleans and numbers, along with operators such as addition and comparison. This PR adds the ability to handle strings, using the same set of operators. String literals are enclosed in apostrophes, and variables that don’t “look like numbers or booleans” are replaced by these quoted literals. This way, a comparison like this is possible:
<operation if="${captureAgentVendor} == 'ACME Corporation'">
…
</operation>

Operations that mix strings and numbers are “mostly harmless”. For example, 3+'4' == '34' actually produces a value of true.
Note that “stringlike-looking” variables are only quoted inside if attributes. Variables in other places in the workflow XML are replaced as before, without quotes, so everything should be backwards-compatible.
Add default values for variable placeholders
Variable placeholders like ${foo} were previously replaced by false if the corresponding variable wasn’t found, which made no sense in relational contexts like ${foo} < 3 (frankly, I didn’t even check what happens in this case). This PR adds the ability to specify a default value after a colon (the syntax is borrowed from bash): ${foo:2}.
This is, of course, not backwards-compatible and was made under the assumption that people don’t define workflow variable names with a colon in them. If that’s not the case, please leave a comment here!
Misc
While working on the WorkflowServiceImpl, I removed some methods that weren't used and made minor style adjustments.
Attribution
This work is sponsored by SWITCH.

Hi, I just downloaded PR branch and I tried, but opencast crashes at startup.
org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=opencast-allinone; type=karaf.feature; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]"; filter:="(&(osgi.identity=opencast-allinone)(type=karaf.feature)(version>=8.0.0.SNAPSHOT)(version<=8.0.0.SNAPSHOT))" [caused by: Unable to resolve opencast-allinone/8.0.0.SNAPSHOT: missing requirement [opencast-allinone/8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-sox-impl; type=osgi.bundle; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve opencast-sox-impl/8.0.0.SNAPSHOT: missing requirement [opencast-sox-impl/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.opencastproject.workspace.api)(version>=8.0.0)(!(version>=9.0.0)))" [caused by: Unable to resolve opencast-workspace-api/8.0.0.SNAPSHOT: missing requirement [opencast-workspace-api/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.opencastproject.storage)(version>=8.0.0)(!(version>=9.0.0)))" [caused by: Unable to resolve opencast-common/8.0.0.SNAPSHOT: missing requirement [opencast-common/8.0.0.SNAPSHOT] osgi.identity; osgi.identity="root#opencast-core-8.0.0.SNAPSHOT"; type=karaf.subsystem; version="[0,0.0.0]"; resolution:=mandatory [caused by: Unable to resolve root#opencast-core-8.0.0.SNAPSHOT: missing requirement [root#opencast-core-8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-core; type=karaf.feature; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]" [caused by: Unable to resolve opencast-core/8.0.0.SNAPSHOT: missing requirement [opencast-core/8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-workflow-condition-parser; type=osgi.bundle; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve opencast-workflow-condition-parser/8.0.0.SNAPSHOT: missing requirement [opencast-workflow-condition-parser/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.antlr.v4.runtime)(version>=4.7.0)(!(version>=5.0.0)))"]]]]]]]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
	at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392)
	at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378)
	at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332)
	at org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
	at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:388)
	at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
	at org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve opencast-allinone/8.0.0.SNAPSHOT: missing requirement [opencast-allinone/8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-sox-impl; type=osgi.bundle; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve opencast-sox-impl/8.0.0.SNAPSHOT: missing requirement [opencast-sox-impl/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.opencastproject.workspace.api)(version>=8.0.0)(!(version>=9.0.0)))" [caused by: Unable to resolve opencast-workspace-api/8.0.0.SNAPSHOT: missing requirement [opencast-workspace-api/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.opencastproject.storage)(version>=8.0.0)(!(version>=9.0.0)))" [caused by: Unable to resolve opencast-common/8.0.0.SNAPSHOT: missing requirement [opencast-common/8.0.0.SNAPSHOT] osgi.identity; osgi.identity="root#opencast-core-8.0.0.SNAPSHOT"; type=karaf.subsystem; version="[0,0.0.0]"; resolution:=mandatory [caused by: Unable to resolve root#opencast-core-8.0.0.SNAPSHOT: missing requirement [root#opencast-core-8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-core; type=karaf.feature; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]" [caused by: Unable to resolve opencast-core/8.0.0.SNAPSHOT: missing requirement [opencast-core/8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-workflow-condition-parser; type=osgi.bundle; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve opencast-workflow-condition-parser/8.0.0.SNAPSHOT: missing requirement [opencast-workflow-condition-parser/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.antlr.v4.runtime)(version>=4.7.0)(!(version>=5.0.0)))"]]]]]]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
	... 12 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve opencast-sox-impl/8.0.0.SNAPSHOT: missing requirement [opencast-sox-impl/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.opencastproject.workspace.api)(version>=8.0.0)(!(version>=9.0.0)))" [caused by: Unable to resolve opencast-workspace-api/8.0.0.SNAPSHOT: missing requirement [opencast-workspace-api/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.opencastproject.storage)(version>=8.0.0)(!(version>=9.0.0)))" [caused by: Unable to resolve opencast-common/8.0.0.SNAPSHOT: missing requirement [opencast-common/8.0.0.SNAPSHOT] osgi.identity; osgi.identity="root#opencast-core-8.0.0.SNAPSHOT"; type=karaf.subsystem; version="[0,0.0.0]"; resolution:=mandatory [caused by: Unable to resolve root#opencast-core-8.0.0.SNAPSHOT: missing requirement [root#opencast-core-8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-core; type=karaf.feature; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]" [caused by: Unable to resolve opencast-core/8.0.0.SNAPSHOT: missing requirement [opencast-core/8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-workflow-condition-parser; type=osgi.bundle; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve opencast-workflow-condition-parser/8.0.0.SNAPSHOT: missing requirement [opencast-workflow-condition-parser/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.antlr.v4.runtime)(version>=4.7.0)(!(version>=5.0.0)))"]]]]]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
	... 13 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve opencast-workspace-api/8.0.0.SNAPSHOT: missing requirement [opencast-workspace-api/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.opencastproject.storage)(version>=8.0.0)(!(version>=9.0.0)))" [caused by: Unable to resolve opencast-common/8.0.0.SNAPSHOT: missing requirement [opencast-common/8.0.0.SNAPSHOT] osgi.identity; osgi.identity="root#opencast-core-8.0.0.SNAPSHOT"; type=karaf.subsystem; version="[0,0.0.0]"; resolution:=mandatory [caused by: Unable to resolve root#opencast-core-8.0.0.SNAPSHOT: missing requirement [root#opencast-core-8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-core; type=karaf.feature; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]" [caused by: Unable to resolve opencast-core/8.0.0.SNAPSHOT: missing requirement [opencast-core/8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-workflow-condition-parser; type=osgi.bundle; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve opencast-workflow-condition-parser/8.0.0.SNAPSHOT: missing requirement [opencast-workflow-condition-parser/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.antlr.v4.runtime)(version>=4.7.0)(!(version>=5.0.0)))"]]]]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
	... 14 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve opencast-common/8.0.0.SNAPSHOT: missing requirement [opencast-common/8.0.0.SNAPSHOT] osgi.identity; osgi.identity="root#opencast-core-8.0.0.SNAPSHOT"; type=karaf.subsystem; version="[0,0.0.0]"; resolution:=mandatory [caused by: Unable to resolve root#opencast-core-8.0.0.SNAPSHOT: missing requirement [root#opencast-core-8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-core; type=karaf.feature; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]" [caused by: Unable to resolve opencast-core/8.0.0.SNAPSHOT: missing requirement [opencast-core/8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-workflow-condition-parser; type=osgi.bundle; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve opencast-workflow-condition-parser/8.0.0.SNAPSHOT: missing requirement [opencast-workflow-condition-parser/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.antlr.v4.runtime)(version>=4.7.0)(!(version>=5.0.0)))"]]]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
	... 15 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve root#opencast-core-8.0.0.SNAPSHOT: missing requirement [root#opencast-core-8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-core; type=karaf.feature; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]" [caused by: Unable to resolve opencast-core/8.0.0.SNAPSHOT: missing requirement [opencast-core/8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-workflow-condition-parser; type=osgi.bundle; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve opencast-workflow-condition-parser/8.0.0.SNAPSHOT: missing requirement [opencast-workflow-condition-parser/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.antlr.v4.runtime)(version>=4.7.0)(!(version>=5.0.0)))"]]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
	... 16 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve opencast-core/8.0.0.SNAPSHOT: missing requirement [opencast-core/8.0.0.SNAPSHOT] osgi.identity; osgi.identity=opencast-workflow-condition-parser; type=osgi.bundle; version="[8.0.0.SNAPSHOT,8.0.0.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve opencast-workflow-condition-parser/8.0.0.SNAPSHOT: missing requirement [opencast-workflow-condition-parser/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.antlr.v4.runtime)(version>=4.7.0)(!(version>=5.0.0)))"]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
	... 17 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve opencast-workflow-condition-parser/8.0.0.SNAPSHOT: missing requirement [opencast-workflow-condition-parser/8.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.antlr.v4.runtime)(version>=4.7.0)(!(version>=5.0.0)))"
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
	... 18 more

After seeing this error I deleted and I downloaded the develop branch again and build it without this PR, worked without problems.

@pmiddend I could reproduce the problem described by @mliradelc and it is related to antlr.
I've found the following related output when doing a mvn clean install -Pdev:
[INFO] --- maven-bundle-plugin:3.5.0:bundle (default-bundle) @ opencast-workflow-condition-parser ---
[WARNING] Bundle org.opencastproject:opencast-workflow-condition-parser:bundle:8-SNAPSHOT : Export org.opencastproject.workflow.conditionparser,  has 1,  private references [org.opencastproject.workflow.conditionparser.antlr],

Could you please have a look at this?

Thanks for trying it out Maxi! Unfortunately, OSGi got in the way. I fixed that, it should work now.

Thanks for trying it out Maxi! Unfortunately, OSGi got in the way. I fixed that, it should work now.

No problem!, I just checked the last version and now works, also I made some tests and works very good.
Can you add the examples you give here in the PR description in the documentation like this and the other one with the addition?
<operation if="${captureAgentVendor} == 'ACME Corporation'">
…
</operation>

@mliradelc Thanks for the feedback, I added two more examples to the documentation.

For me its good, I backported to Version 7 without issues. Version 6 it was very difficult because the Workflow Service changed quite a lot between 6 to 7.
If there are no other issues, I will merge it at the end of this day.


BGP Session Edit view is too slow does not work consistently

NetBox version
2.11.2
Describe the bug
After a BGP Session is created, when I try to edit it by clicking on the Edit button (which tries to take me to https:///plugins/bgp/session//edit/) the edit BGP session page takes a very long time to load, and only loads sometimes. Most of the time, the page just hangs.
To Reproduce
Steps to reproduce the behavior:

Create a BGP session via the GUI
Click on the BGP session created, to view Details of the Session.
Click on the Edit button
Observe behavior: Does the Edit session page load quickly?

Expected behavior
The Edit BGP Session page loads as quickly as the Details view of the BGP session.
Screenshots
n/a
Additional context
The problem doesn't seem to be load/database size related. This behavior is observed both in our Production env as well as in Dev env. The total number of BGP sessions is only 5, so its not about number of entries in the BGP Session table. We do however have 2000 IP Address objects in Production, and 500 IP Address objects in Dev.

#66


Merge pull request #2985 from asuender/main

[German translation]: Remove 'Beitragsarten' and fix some minor stuff

[x] Have you followed the contributing guidelines?
[x] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

mona

Avs

CR = to be closed

SPAM, locked and reported.


Tabs not working. Notes delete after restarting the app.

Hello,
I'm facing an issue where every time I either restart the app or restart my mac. all the data in the notes are gone and the different tabs in the notepad don't work anymore.
This started happening after I logged out of my iCloud account and logged back in.
Would appreciate all the help.
Thanks.

Thank you for the report. I reproduced the issue and will fix it.

I should also follow up that a few friends of mine say that even downloading it the first time on a new machine has the same issue. It's probably a common issue on the latest version on the App Store.
Thanks again for the help and speedy reply :D

Hey bro o/
Any updates regarding this issue? I don't intend to rush you but your app is really important for me in every day use :D

@AlFaLaSi97 sorry for the delay. I will try to find time on this weekend and fix the issue.

Hi bro,
Hope everything is going well.
Any updates regarding the notes?

Hi @AlFaLaSi97. I released the fix yesterday.

Thank you for you support and response, I'm sorry I've missed your last comment and couldn't close the case sooner.
All the best bro :D


feat(rpc): basic engine api

This PR introduces the basic implementation of Paris specs for engine API

Codecov Report

Merging #551 (62235d0) into main (82cd84e) will decrease coverage by 0.43%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #551      +/-   ##
==========================================
- Coverage   72.70%   72.26%   -0.44%
==========================================
  Files         243      247       +4
  Lines       24701    24944     +243
==========================================
+ Hits        17959    18027      +68
- Misses       6742     6917     +175

Flag
Coverage Δ

unit-tests
72.26% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/consensus/src/engine/error.rs
0.00% <0.00%> (ø)

crates/consensus/src/engine/mod.rs
0.00% <0.00%> (ø)

crates/consensus/src/lib.rs
100.00% <ø> (ø)

crates/consensus/src/verification.rs
81.94% <0.00%> (-0.56%)
:arrow_down:

crates/net/rpc-types/src/eth/engine.rs
3.57% <0.00%> (-8.93%)
:arrow_down:

crates/net/rpc/src/engine/mod.rs
0.00% <0.00%> (ø)

crates/net/rpc/src/eth/api/mod.rs
0.00% <0.00%> (ø)

crates/net/rpc/src/eth/api/server.rs
0.00% <0.00%> (ø)

crates/net/rpc/src/lib.rs
100.00% <ø> (ø)

crates/storage/provider/src/block.rs
58.06% <ø> (ø)

... and 44 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Password field in the "Add item"-dialog has lost the mask

But maybe it looks better this way. We can also leave it like this.


Files shared with Anyone sometimes prompt users to login

I regularly share files using the "share with anyone, doesn't require sign-in"  option.
If I share to 10 users 3 of them get back to me saying its asking to sign in.
I have followed the methods mentioned in this page.
Not sure if this is a bug  or this page needs updating.
There is thread opened in 2019 with the same issue still not fixed so hopefully a onedrive issue.
https://techcommunity.microsoft.com/t5/onedrive-for-business/files-shared-with-anyone-sometimes-prompt-users-to-request/m-p/308153/page/3
https://www.reddit.com/r/sysadmin/comments/9spgsj/external_sharing_with_onedrive/

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

ID: d1b12dd3-e62d-a7ff-c597-9588cf6f1a23
Version Independent ID: 231efccb-cfad-cf42-bd45-48bbcb2958d9
Content: Best practices for unauthenticated sharing
Content Source: microsoft-365/solutions/best-practices-anonymous-sharing.md
Service: o365-solutions
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

@Jarajesh Thank you for your feedback. This looks like a bug in the tenant, I'd recommend you contacting support via the need help section on the admin center, so that the support engineer can fix this or raise a bug with the concerned team to fix it.
Hope this helps!
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @Jarajesh Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. You can contact Microsoft support via the need help section on the admin center. We proceed to close it as here we are limited to documentation fixes and improvements only.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Support Map types with itemType

It would be really useful to support Map types with itemType. Currently specifying an attribute as type Map results in "attribute.map is not a function" on attribute serialization. Is this something that could be added? If it's just a case of implementing a .map function for Map then that would be relatively trivial?
My use case is storing itemType's ID value as a key on Map.
Thanks!

This would be an excellent feature. We are currently working with DynamoDB and we often bump into cases where we want objects with dynamic property naming. This is an excelent use case for saving dictionaries and/or hashtables.
Both JavaScript and DynamoDB supports this use scenario and it would be a great addition to structure.

As discusses, we're gonna define the key and item type like this:
{
  permissions: {
    type: Map,
    itemType: { key: String, value: Permission }
  }
}

Where the value of key is a property on Permission? e.g.
  permissions: {
    type: Map,
    itemType: { key: 'permissionId', value: Permission }
  }


3.14.0 Rollup errors, preventing build or run

Environment

Operating System: Windows_NT
Node Version:     v20.12.2
Nuxt Version:     3.14.0
CLI Version:      3.15.0
Nitro Version:    2.10.3
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      default
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
A simple project using Nuxt ^3.13.2 updated to ^3.14.0 with bun update --save
Describe the bug
Project worked perfectly. Updated only Nuxt to ^3.14.0, getting lot of Rollup errors that are preventing the build.
RollupError: [plugin impound] This module cannot be imported in server runtime. [importing node_modules/nitropack/node_modules/unstorage/dist/index.mjs from node_modules/nitropack/dist/runtime/internal/storage.mjs]

And others related to external modules (that never gave these type of errors)
ERROR  RollupError: virtual:#nitro-internal-virtual/server-handlers-meta (29:7): Identifier "_BMjsRhMeta" has already been declared                                                                                nitro 22:26:03

27: import _rIuTp4Meta from "C:/Users/matteo/Documents/Progetti/Dev/saas/depthlog/node_modules/nuxt-og-image/dist/runtime...
28: import _BMjsRhMeta from "C:/Users/matteo/Documents/Progetti/Dev/saas/depthlog/node_modules/nuxt-og-image/dist/runtime...
29: import _BMjsRhMeta from "C:/Users/matteo/Documents/Progetti/Dev/saas/depthlog/node_modules/nuxt-og-image/dist/runtime...
           ^
30: import _pr69QkMeta from "C:/Users/matteo/Documents/Progetti/Dev/saas/depthlog/node_modules/nuxt-schema-org/dist/runti...
31: import _bHLnh6Meta from "C:/Users/matteo/Documents/Progetti/Dev/saas/depthlog/node_modules/nuxt-seo-experiments/dist/...

Additional context
No response
Logs
ERROR  RollupError: [plugin impound] This module cannot be imported in server runtime. [importing node_modules/nitropack/node_modules/unstorage/dist/index.mjs from node_modules/nitropack/dist/runtime/internal/storage.mjs]

this was resolved in https://github.com/nuxt/nuxt/pull/29780 and will be included in the next patch release (expect it shortly!)

this was resolved in #29780 and will be included in the next patch release (expect it shortly!)

Great! Are we talking hours or days here?

hours

any updates?

that is a different issue and likely related to adding the same nitro handler twice - it's likely an issue with your configuration or dependencies - feel free to open a new issue with a minimal reproduction

Hi, updated from 3.13.2 to 3.14.159 and got the same issue, has the feen already been released ?

Same for me after upgrading from 3.7.4 to 3.14.159. I will try ugrading progressively

Ditto seeing rollup errors in 3.14.159
 RollupError: virtual:#nitro-internal-virtual/server-handlers-meta (83:7): Identifier "_e32yxeMeta" has already been declared

I am still having a problem as well:
Nuxt 3.14.159 with Nitro 2.10.3
...
[nitro 08:42:15]  ERROR  RollupError: [plugin impound] This module cannot be imported in server runtime. [importing node_modules/nitropack/node_modules/defu/dist/defu.mjs from node_modules/nitropack/dist/runtime/internal/route-rules.mjs]

Same here
[nitro 08:50:42]  ERROR  RollupError: [plugin impound] This module cannot be imported in server runtime. [importing ../../node_modules/nuxt/node_modules/nitropack/node_modules/crossws/dist/adapters/node.mjs from ../../node_modules/nuxt/node_modules/nitropack/dist/presets/_nitro/runtime/nitro-dev.mjs]

Here as well
RollupError: [plugin impound] This module cannot be imported in server runtime. [importing node_modules/nitropack/node_modules/crossws/dist/adapters/node.mjs from node_modules/nitropack/dist/presets/_nitro/runtime/nitro-dev.mjs]

Same here Nuxt 3.14.159 with Nitro 2.10.3
RollupError: [plugin impound] This module cannot be imported in server runtime. [importing node_modules/nitropack/node_modules/ufo/dist/index.mjs from node_modules/nitropack/dist/runtime/internal/route-rules.mjs]

@danielroe here is an example:
A simple catch all file in /server/routes/api/[...].js (I do not put my url in here)
`import { useLogger } from '@nuxt/kit'
export default defineEventHandler((event) => {
const logger = useLogger()
return $fetch(url, {
onRequest: ({ request, options }) => {
logger.info('[fetch request]', request, options)
},
onRequestError: ({ error, request, options }) => {
logger.error('[fetch request error]', error, request, options)
},
onResponse: ({ response, request, options }) => {
logger.info('[fetch response]', response, request, options)
},
onResponseError: ({ error, response, request, options }) => {
logger.error('[fetch response error]', error, response, request, options)
}
})
})`
ERROR  RollupError: [plugin impound] This module cannot be imported in server runtime. [importing @nuxt/kit from server/routes/api/[...].js]

Okay, thanks!

I couldn't reproduce the error in a minimal example, so I suspected the issue might be with my local setup. Initially, I had simply updated the package.json to upgrade Nuxt and the Vite builder plugin. However, after running npx nuxi@latest upgrade --force, everything seems to be working as expected.
Lesson learned: always follow the documentation when upgrading! The documentation also notes that this command refreshes your lockfile, ensuring that updates from other dependencies in the Nuxt ecosystem are pulled in properly.

Thanks, @thorge.
I tried the suggested upgrade and had no luck; the same error persists.
Unfortunately I can't see from it what part of the code I'm having to maintain might be causing it, so if anyone has any suggestions of how to investigate it then they would be most welcome.

I couldn't reproduce the error in a minimal example, so I suspected the issue might be with my local setup. Initially, I had simply updated the package.json (running npm install afterwards) to upgrade Nuxt and the Vite builder plugin. However, after running npx nuxi@latest upgrade --force, everything seems to be working as expected.
Lesson learned: always follow the documentation when upgrading! The documentation also notes that this command refreshes your lockfile, ensuring that updates from other dependencies in the Nuxt ecosystem are pulled in properly.

works for me, thanks! I always used ncu- u -t minor and npm i afterwards. Seems I need to run npx nuxi upgrade -f first, to upgrade Nuxt and my ncu command to update other dependencies afterwards...

I'm getting the same issue, if it is of any help in looking into this, if I add
  nitro: {
    experimental: {
      // Enable Server API documentation within NuxtHub
      openAPI: true
    }
  },

to nuxt.config, it gives me the error
RollupError: virtual:#nitro-internal-virtual/server-handlers-meta (32:7): Identifier "_vtEFC3Meta" has already been declared

30: import _P2WQbkMeta from "/Users/pmcp/Documents/GitHub/kdm/node_modules/.pnpm/@nuxthub+core<EMAIL_ADDRESS>31: import _vtEFC3Meta from "/Users/pmcp/Documents/GitHub/kdm/node_modules/.pnpm/@nuxt+content<EMAIL_ADDRESS>32: import _vtEFC3Meta from "/Users/pmcp/Documents/GitHub/kdm/node_modules/.pnpm/@nuxt+content<EMAIL_ADDRESS>           ^
33: import _vtEFC3Meta from "/Users/pmcp/Documents/GitHub/kdm/node_modules/.pnpm/@nuxt+content<EMAIL_ADDRESS>34: import _qfWoImMeta from "/Users/pmcp/Documents/GitHub/kdm/node_modules/.pnpm/@nuxt+content<EMAIL_ADDRESS>

This experimental feature is included in the nuxthub starter, it seems to only break if nuxt content is added.
Combining Nuxt Content and openAPI: true seems to be the issue (for me).

Done (https://github.com/nuxt/content/issues/2839)

Having similar issue when updating to nuxt 3.14.159 with Nitro 2.10.4
RollupError: [plugin impound] This module cannot be imported in server runtime. [importing node_modules/nitropack/node_modules/db0/dist/index.mjs from node_modules/nitropack/dist/runtime/internal/database.mjs]

I faced a similar issue where using Yarn as the package manager caused a Rollup error, but everything worked fine with npm. The problem is likely due to how Yarn and npm handle dependencies differently. Yarn might have installed a conflicting or incompatible package version, causing the error during the build.
To fix it, I stuck with npm, as it resolved the dependencies correctly without any issues. You could try clearing the cache with yarn cache clean or regenerate the lockfiles by deleting yarn.lock and package-lock.json, but using npm, for now, is a simple workaround.

I'm getting the same issue, if it is of any help in looking into this, if I add
  nitro: {
    experimental: {
      // Enable Server API documentation within NuxtHub
      openAPI: true
    }
  },

to nuxt.config, it gives me the error
RollupError: virtual:#nitro-internal-virtual/server-handlers-meta (32:7): Identifier "_vtEFC3Meta" has already been declared

30: import _P2WQbkMeta from "/Users/pmcp/Documents/GitHub/kdm/node_modules/.pnpm/@nuxthub+core<EMAIL_ADDRESS>31: import _vtEFC3Meta from "/Users/pmcp/Documents/GitHub/kdm/node_modules/.pnpm/@nuxt+content<EMAIL_ADDRESS>32: import _vtEFC3Meta from "/Users/pmcp/Documents/GitHub/kdm/node_modules/.pnpm/@nuxt+content<EMAIL_ADDRESS>           ^
33: import _vtEFC3Meta from "/Users/pmcp/Documents/GitHub/kdm/node_modules/.pnpm/@nuxt+content<EMAIL_ADDRESS>34: import _qfWoImMeta from "/Users/pmcp/Documents/GitHub/kdm/node_modules/.pnpm/@nuxt+content<EMAIL_ADDRESS>
This experimental feature is included in the nuxthub starter, it seems to only break if nuxt content is added.
Combining Nuxt Content and openAPI: true seems to be the issue (for me).

Same here, setting the openAPI to false resolves the issue.

I couldn't reproduce the error in a minimal example, so I suspected the issue might be with my local setup. Initially, I had simply updated the package.json (running npm install afterwards) to upgrade Nuxt and the Vite builder plugin. However, after running npx nuxi@latest upgrade --force, everything seems to be working as expected.
Lesson learned: always follow the documentation when upgrading! The documentation also notes that this command refreshes your lockfile, ensuring that updates from other dependencies in the Nuxt ecosystem are pulled in properly.

thanks for the suggestion.
This worked for me

Same here, setting the openAPI to false resolves the issue.

Same here openAPI=true breaks latest 3.14.x for me.

I updated Nuxt to version 3.14.159 but I am still getting rollup errors:
ERROR  RollupError: virtual:#nitro-internal-virtual/server-handlers-meta (29:7): Identifier "_BMjsRhMeta" has already been declared                                                                                nitro 19:44:30

27: import _rIuTp4Meta from "C:/Users/matteo/Documents/Progetti/Dev/saas/depthlog/node_modules/nuxt-og-image/dist/runtime...
28: import _BMjsRhMeta from "C:/Users/matteo/Documents/Progetti/Dev/saas/depthlog/node_modules/nuxt-og-image/dist/runtime...
29: import _BMjsRhMeta from "C:/Users/matteo/Documents/Progetti/Dev/saas/depthlog/node_modules/nuxt-og-image/dist/runtime...
           ^
30: import _pr69QkMeta from "C:/Users/matteo/Documents/Progetti/Dev/saas/depthlog/node_modules/nuxt-schema-org/dist/runti...
31: import _bHLnh6Meta from "C:/Users/matteo/Documents/Progetti/Dev/saas/depthlog/node_modules/nuxt-seo-experiments/dist/...

I had the same error on upgrading and setting openAPI to false resolves the issue.

I had the same issue and thanks to comments in this issue I realize it was a wrong import that my IDE webstorm suggest it as it didn't recognize it (it was in red)  useNuxtApp() on the server side code. So by just removing the import below everything started it working again.
import { useNuxtApp } from "nuxt/app"


Add VP04 team and members to the SCS organization

This PR manages modifications related to VP04 within the SCS organization. It adds the VP04 tender section, introduces the Daiteap team section, updates the dNation team, and incorporates all newly assigned SCS organization members into the newly created sections.

@matofeder I went ahead and merged the change so it will run with my PAT.


cant run test_bcm8544

everytime i try to run the file test_bcm8544 i get the error:
-bash: test_bcm8544: command not found
i also tried to run the hello world example in the README.md, it gives this error:
-bash: test_bcm8544: command not found
am i doing something wrong?
please help

Did you compile it?
Did you add the ./ before the command. See in linux a command is searched for in the PATH but the PATH does not contain the current directory. So please try   ./test_bcm8544
Hope this helps

thanks for the response but i somehow figured it out myself so this thread
can be closed
Op zo 25 sep. 2022 07:34 schreef Michel Vos @.***>:

Did you compile it?
Did you add the ./ before the command. See in linux a command is searched
for in the PATH but the PATH does not contain the current directory. So
please try ./test_bcm8544
Hope this helps
—
Reply to this email directly, view it on GitHub
https://github.com/MichelVos/rpi_cpu_infoscreen/issues/3#issuecomment-1257125083,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AV4L5MT73INZSWZVHDYXEQDV77P75ANCNFSM5JHP227A
.
You are receiving this because you authored the thread.Message ID:
@.***>

thanks for the response but i somehow figured it out myself so this thread
can be closed


implement play/pause and skipforward media buttons

Issue #33  and #34 implemented,  needs clarification for #33 whether we use MEDIA_NEXT or SKIP_FORWARD @i315315 @stefanieschreiner

#33 clarified, pr can be reviewed and merged


Master

This introduces a new React component called Slider which contains History and SuggestedActions, thus separating concerns between those two. Slider owns all the CardAction handling for both.
Slider is a connected component, which is to say that it reacts to changes to app state and passes properties to History (which becomes strictly a rendering component) and SuggestedActions (which already was).
I also took the opportunity to clean up history.tsx a smidge by liberal use of the JSX object spread operator.
This paves the way to potentially moving the suggested actions state machine into Redux, but it is worthwhile just by itself.

This update is a better factoring of the same idea. Now SuggestedActions includes both the containing div and the actions bar itself, and renders History using props.children, which combines the clean separation of concerns of the previous approach with the efficiency of the original implementation. @danmarshall if you approve go ahead and merge, after which I will take on the Reduxification of SuggestedActions.


Fixing code to be able to use files.

*Part of issue #39 *
Description of changes:
Reverting changes to old code that worked with files. Code with new URL was breaking.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

To expand on this, I think the reason why the test was passing was that it was using '__dirname'. So the file that we were passing to new URL() was an absolute path. Therefore the path that was given to fs.readFileSync(path, 'utf-8') was also absolute and was able to find that file.
When we are passing our parameter-overrides filename we are not passing an absolute path and therefore it couldn't find the file. I've changed the test to reflect this also.


dnncommunity.org no verification email sent/received

I did not receive an activation email from DNNCommunity.org
Now that you have put up a site that runs CE which is AWESOME!!! you can now go through all the issues trying to get user growth on the site.
These are all major issues I have been trying to build awareness on since August 2017.
The registration system needs to get tweaked in.  Are you able to get the Facebook and other authentication systems working on this as well?
I have had no luck as something always keeps registrations from happening.  Especially if the portal uses "Email as Username".
"Cody" is my display name on the website if you could please activate me that would be great.
Most users wont know who or how to contact someone and will just forget about it and move on... if you are wondering why a lot of un-authenticated users this is why I have them.  Most people can register but I had to change from email as username to username and username in order to get things half way stable enough to call it good for now.
It would be nice to see that "resend email verification" link on the message and the message also centered as it is off ot the left when on a full screen.  I swear Ben created a pull request for it a few years ago.
I know there have been some discussions on updating the registration and login modules.
Also to shine a little light on the subject... I did receive emails letting me know I updated my profile.  So I know the email would get to me if it would have been sent to me.
No way to verify my account.  Maybe in the automated messages if any are sent to the user after registration if they are not yet verified there can be a verification link reminder.
For example in the message stating I updated my profile a reminder to verify my account along with a verification link.
Then if someone updates a profile or does anything such as a password reset they will get a verification link as well with the email.  Or if you change your password really that should be enough verification to show the email address is connected to that account.
Thank you.

@thabaum There are multiple issues in here, many of them duplicating issues that are already logged. Can you please divide this in multiple issues one for each thing and do a search for some keywords for each since some are already logged in here. And if you could also please log here only what can be reproduced on a new install and report the dnncommunity.org specifi things in the forums. Thanks.

please report issues specific for the dnncommunity.org site in forums at https://dnncommunity.org/forums/aff/13


What are kG and kCos?

Hi,
I was just checking out the tool when I noticed two new constants: kG and kCos. I was wondering if these are the voltage to angular velocity/acceleration constants meant to be passed into identifyDrivetrainSystem (for kVAngular and kAAngular respectively). Also, can the kS kV kA constants provided by the tool still be used for the standard SimpleMotorFeedforward calculations?

No, kG is for the elevator gravity feedforward term and kCos is for the single-jointed arm gravity feedforward. We had those since the 2019 offseason.
To obtain angular constants, there's a checkbox that flips the motor directions so the robot spins in place instead of driving forward. Everything else works the same way.

No, kG is for the elevator gravity feedforward term and kCos is for the single-jointed arm gravity feedforward. We had those since the 2019 offseason.
To obtain angular constants, there's a checkbox that flips the motor directions so the robot spins in place instead of driving forward. Everything else works the same way.

kG and kCos are for when you're analyzing an elevator or arm, respectively. The fields for those should be greyed out when you're analyzing a drivetrain.
To get angular constants for a drivetrain, you need to run the data logging routine twice. First run it normally, and then run it again but with the angular mode checkbox checked. You'll need to run both of the resulting data files through the analyzer.

kG and kCos are for when you're analyzing an elevator or arm, respectively. The fields for those should be greyed out when you're analyzing a drivetrain.
To get angular constants for a drivetrain, you need to run the data logging routine twice. First run it normally, and then run it again but with the angular mode checkbox checked. You'll need to run both of the resulting data files through the analyzer.

Got it, thank you so much. And just to clarify, you would use the linear KS KV KA wrapped in a SimpleMotorFeedforward to pass into the Ramsete controller (no state-space/LQR).

Got it, thank you so much. And just to clarify, you would use the linear KS KV KA wrapped in a SimpleMotorFeedforward to pass into the Ramsete controller (no state-space/LQR).

Yes, RamseteCommand takes a SimpleMotorFeedforward for each of your motors.
(Note that the RAMSETE control law doesn't actually have anything to do with computing feedforwards; RamseteCommand, however, handles all of the trajectory following, which includes computing feedforwards.)

Yes, RamseteCommand takes a SimpleMotorFeedforward for each of your motors.
(Note that the RAMSETE control law doesn't actually have anything to do with computing feedforwards; RamseteCommand, however, handles all of the trajectory following, which includes computing feedforwards.)

My apologies RamseteCommand was what I was referring to.

My apologies RamseteCommand was what I was referring to.


Table creation restriction blocks data import

Description
Data import can't be completed into existing table if structure edit id resricted
DBeaver Version
23.3.5
Operating System
Any
Database and driver
Any
Steps to reproduce

Open table type settings
Click edit permissions
Check only "restrict structure edit" box
Open import wizard for this connection
Ensure that table mapping is set to existing and no changes to table are needed
Start import

Expected: Data is imported
Actual: Error is shown, saying that table creation is restricted
Additional context

Open Defect in TestQuality


Exclude option, closes #435

Adds the option to use excludes as both a library argument and an API param, so that automatically included dependencies can be selectively excluded.
@callumlocke

LGTM 👍


Sync playbackRate between users

Hello, thank you for maintaining this extension.
I prefer to watch videos at higher speeds, It would be convenient if the current video speed was synchronized between users.
The speed is normally stored in "document.querySelector('video').playbackRate"
Implementing this features should be as easy as watching for a change and then setting the other client to the same speed.
Thank you for your time.

Appologies, I see you're setting the plackbackRate here: https://github.com/Semro/syncwatch/blob/master/plugin/js/content.js#L144-L148
This seems to work as long as the playback rate is set through the video player's ui, If an extension like Global Speed is used than the rate does not sync.
Idealy, one client would have global speed disabled, and the other would overide the speed.

Fixed in https://github.com/Semro/syncwatch/commit/597b158061f1736cac20a20e6c0660a4633bd56f


Add TestCaseFailureEvent and TestStepFailureEvent to LifeCycleListner…

… instead of TestCaseEvent and TestStepEvent

what the main purpose of this change? TestCaseEvent can be used to get (of fire) failure event without any problem

Yes but TestCaseEvent and TestStep are General event types. And it is not clear to listen TestFailure or TestStepFailure with TestStep and TestCase Events. For me - there can be false positives with this conception.

you can create own listener interface with custom events only and check correct type of event in common listener. It can't be false-positive because of every testcase (teststep) event knows own status.
 @Override
    public void fire(TestCaseEvent event) {
        if(TestCaseFailureEvent.class.isInstance(event)) {
             //your logic
        }
    }

Of course i can, but for my opinion: if you provide logic to listen events, why you don't provide logic to listen this kind of events in interface?. When i start writing integration, i spent time to look through code and find that TestCaseEvent is what i searched for. Anyway, i think it will be more clear to provide this events in interface. (Also you can just add comment to the TestCaseEvent in the interface.)

This part of allure api is experimental - thats why it has lack of documentation. The main listener class provides all functionality to do any kind of own listener. So it not need to expose all kind of events (its ridiculous to have 30 fire methods to any type of event). It's your choice to watch only for specific events. So it should be done in your code only and not in allure.

Ok then. Thanks for looking in to this.


Tour over two different pages

I am not able to make a vue tour over two components. As example when i start the tour on the landing page and then i want to show to users where the new feature is implemented i am not able to switch the pages and show the next step on the right place because the step is loading faster as the new page is rendering.

I think this is already discussed here https://github.com/pulsardev/vue-tour/issues/37

Hi @labionabazi,
Actually there even is an example here: https://github.com/pulsardev/vue-tour/issues/12.


Cannot Paste into same directory?

As a Data Platform developer I use Azure Storage Explorer to trigger new blob events which in turn execute event triggers in ADF.
Recently you took away the ability to copy and paste into the same directory.
Why?
Now I have to copy and paste into a completely different directory, then copy and paste back.
This is sometimes for 000s of files and is a very time intensive exercise.
Not to mention that in the process, the ACLs settings on the copied files often become corrupted in the process.
Can you please remove this restriction as I can see no purpose for this

I assume you mean copying blobs and pasting them into the directory they are in, right? The reason we removed it is because this will lead to data corruption on append or page blobs. If you attempt to overwrite an append/page blob by itself, it will accidentally erase the data of the blob.

@LukeMcCarthy-Versor this is by design. As @JasonYeMSFT explains, there were issues with allowing this behavior.


RDBMS cdc Hive (just only process insert data)

Only want to process INSERT data in real time, not DELETE and UPDATE data.
now ,How do I set it？

Hive doesn't have proper support for UPDATE and DELETE. It would be better to integrate with some data lake frameworks, such iceberg, which also support ingest Flink CDC data.


How to get user profile for code flow?

Hi! I try code flow https://manfredsteyer.github.io/angular-oauth2-oidc/docs/additional-documentation/code-flow-+-pcke.html.
How i can check user profile with oauthService.loadUserProfile()? I can't do this right now, the token is null.

Could you help us reproduce the issue? Perhaps create a StackBlitz.com example against one of the demo Identity Servers? It's a bit hard to follow why exactly you'd be getting into that situation...

I have already resolved the issue, my project was incorrectly configured redirect. Thanks for the help.


Feature Request: Automatically Assign Unset Iteration to Current Iteration

I am requesting an enhancement to the move-to-next-iteration library to include a feature that automatically assigns Issues and Pull Requests (PRs) with an unset Iteration to the current Iteration based on specific conditions. This automation would help streamline our workflow and ensure that all tasks and changes are properly tracked within the appropriate Iteration.
Use Case:
In our development process, it is common for Issues and PRs to be created without an assigned Iteration. Manually assigning these to the current Iteration can be time-consuming and prone to errors. Automating this process ensures that all relevant Issues and PRs are included in the current sprint or cycle, enhancing visibility and planning accuracy.
For example, during a sprint planning meeting, developers can create new Issues and PRs based on the discussed tasks. However, if these items do not have an Iteration assigned, they might be overlooked. With this feature, any newly created or existing Issues and PRs that meet the specified conditions will be automatically added to the current Iteration, ensuring they are part of the ongoing work without manual intervention.
This feature would greatly improve efficiency and accuracy in our project management process, reducing the administrative burden on our team.
Thank you for considering this request.

This feature addition deviates significantly from the main purpose of this Action, so I forked it and implemented the changes. If there is demand, I will submit a Pull Request.
https://github.com/tichise/move-to-next-iteration


BUILD FAILED

When i start android studio, i get this error during build up
Error:Execution failed for task ':buildSrc:plugins/edx-app-gradle-plugin:compileGroovy'.
ANY HELP ??

I was able to get the answer from the closed threads but after that i started getting a different error
ERROR
Error:Execution failed for task ':OpenEdXMobile:validateReleasekeySigning'.
Keystore file /home/arkangel/Documents/edx-app-android/OpenEdXMobile/edx-android-release-key.keystore not found for signing config 'releasekey'.

Where is your keystore file? and where is your gradle.properties pointing to for the keystore file?

@arkangel1611 This PR https://github.com/edx/edx-app-android/pull/938/ solves all the problems. Feel free to check out and comment if you find any improvements.

I just cloned the project and I seen below error:
Error:Execution failed for task ':buildSrc:plugins/edx-app-gradle-plugin:compileGroovy'.
Groovy version is set to 2.4.4 but the issue is not solved.

@saboori72 have you tried checking out this PR https://github.com/edx/edx-app-android/pull/938 ?

Closing this issue. Feel free to open if the issue persists.


make it works with ajax pages

someway to call plugin getLetters() dynamic.

@boynet I forked one and make the plugin can be called dynamic. https://github.com/nzbin/Framework7-Indexed-List-plugin


Update to new version of nodejs runtime (nodejs4.3)

The existing version of nodejs runtime has been depreciated and deployment was failing with current config. Was getting the following error:
[InvalidParameterValueException: The runtime parameter of nodejs is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs4.3) while creating or updating functions.]
message: 'The runtime parameter of nodejs is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs4.3) while creating or updating functions.',
code: 'InvalidParameterValueException'

Thanks for this :)


Replace reason.bsb.enabled with reason.diagnostics.tools

Companion PR of https://github.com/reasonml-editor/vscode-reasonml/pull/112.
There was some feedback on Discord about users wanting more control over which tool would be used for diagnostic. This PR changes bsb.enabled (boolean) with diagnostics.tools(array) so users can decide if they want merlin, bsb or both, or none :)
@freebroccolo @chenglou What do you think? cc @superherointj

So this is just for diagnosis right?
I think we can afford to be a little bit more opinionated about this, assuming the bsb feature is stable. For example, there's no occasion where for an overlapping merlin & bsb error, you'd choose the former.

For example, there's no occasion where for an overlapping merlin & bsb error, you'd choose the former.

Hmm... maybe this means the option is not very clear. I built it so when the user selects both, we would still be showing bsb errors first (if any) on save, and use merlin while the file is being changed.
So, to clarify:

diagnostics.tools
bsb.enabled

[]
New mode (no diagnostics)

["merlin"]
false

["merlin", "bsb"]
true (merlin while editing, bsb on save)

["bsb"]
New mode, only  bsb on save

Yeah. The third one is the opinionated part, and potentially confusing...

We could add a quick explanation on the setting description.

If you choose both "merlin" and "bsb", merlin will be used while editing and bsb when saving.

Sounds good.

@freebroccolo @chenglou This is ready.


Properties not getting updated

When I am inserting new entity, the Trackable propeteries Inserted & Updated is not getting the right value.
Please refer the app src at the below repository.
https://github.com/chetankhargone/Triggers-in-EF-COre.git
Can you please check & suggest ?
Thanking You.

Hi @chetankhargone
It looks like you are defining your own DbContextWithTriggers class, and also you aren't inheriting from it.
What you want to do is inherit your SampleAppContext from the DbContextWithTriggers class included in this library (so, delete your DbContextWithTriggers class). Like this...
class SampleAppContext : EntityFramework.Triggers.DbContextWithTriggers {

}


nvidiaConfigFail: NVIDIA GPU configuration failed unexpectedly

I am trying to run the python CNTK distributed GPU recipe. And the job is failing with the following error:
Job state: queued ExitCode: None
Cluster state: AllocationState.steady Target: 2; Allocated: 2; Idle: 0; Unusable: 2; Running: 0; Preparing: 0; Leaving: 0
Cluster error: nvidiaConfigFail: NVIDIA GPU configuration failed unexpectedly
Details:
Reason: Failed to install nvidia-docker
Any suggestion?

Having a similiar issue when creating a cluster. My nodes are unusable.
I checked the startup error logs in  /mnt/batch/tasks/startup/error.json and it says:
{"Code":"nvidiaConfigFail","Message":"NVIDIA GPU configuration failed unexpectedly","Category":"InternalError","ExitCode":1,"Details":[{"Key":"Reason","Value":"Failed to install nvidia-docker"}]}

Similarly, from /mnt/batch/tasks/startup/stderr.txt
(...)
018/04/03 00:40:50 install nvidia-docker
dpkg: dependency problems prevent configuration of nvidia-docker:
 nvidia-docker2 (2.0.2+docker17.12.0-1) breaks nvidia-docker and is installed.

dpkg: error processing package nvidia-docker (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 nvidia-docker

Sounds like the same issue. Still looking for suggestions.

Hi the issue was related with the new version of DSVM. We are rolling out a fix for this.

Can anyone confirm this is actually resolved?  If so what do I have to do to fix my cluster?

@CameronVetter Please recreate your Batch AI cluster to get the fix for this


Add polyfill, use isEmpty instead of Object.keys

isEmpty is better to check for empty objects
Add polyfill to combat IE11-issues
Image cropping not fixed for IE11

Codecov Report

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

@@           Coverage Diff           @@
##           master     #123   +/-   ##
=======================================
  Coverage   62.96%   62.96%
=======================================
  Files          20       20
  Lines         243      243
=======================================
  Hits          153      153
  Misses         90       90

Continue to review full report at Codecov.

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


Remove flash session data API

Unless someone is using it, even me I did not use it. It's too magical and I prefer to explicitly remove it when necessary.

:tada: This issue has been resolved in version 4.0.0 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


change card image to have radius on all corners and REM

.cards > ul > li img {
width: 100%;
height: auto;
border-radius: 0.5rem ;
}

I suppose this is something that doesn't need to scale like text so 8px may be more correct.

custom var 8px  standards (half gap quarter gap, radius all images etc)

duplicate of issue #167 that incudes various image style changes throughout the site


Fixes version variable overwrite

During testing, found that the VERSION variable used in the CP4I navigator instance creation gets overridden by the earlier change to download a default openshift oc client. This pull request fixes that by renaming the variable to OC_VERSION in the cli-download function.


Possible reflective cross site scripting in the io.dropwizard.validation.ConstraintViolations

We have come across a problem in when doing JSR-303 validation, due to dropwizard ConstraintViolations adding the InvalidValue back in the message.
The following request payload,
{
   "url": "/address/<script>alert(2)</script>"
}

will result in the following error
{
"errors": [
"url must be a valid URL (was /address/<script>alert(2)</script>)"
]
}

We don't want the "was" part.
Based on the investigation we found that it is being appended in the ConstraintViolations.format() method.
public static <T> String format(ConstraintViolation<T> v) {
    if (v.getConstraintDescriptor().getAnnotation() instanceof ValidationMethod) {
        final ImmutableList<Path.Node> nodes = ImmutableList.copyOf(v.getPropertyPath());
        final ImmutableList<Path.Node> usefulNodes = nodes.subList(0, nodes.size() - 1);
        final String msg = v.getMessage().startsWith(".") ? "%s%s" : "%s %s";
        return String.format(msg,
                             Joiner.on('.').join(usefulNodes),
                             v.getMessage()).trim();
    } else {
        return String.format("%s %s (was %s)",
                             v.getPropertyPath(),
                             v.getMessage(),
                             v.getInvalidValue());
    }
}

Is there any way that we can avoid the invalidValue from being attached to the message?
If not can we have a feature switch for that?

See also #892.

The issue I reported could be rectified if the invalidValue is not printed.
Is it something that could be considered?
I don't see a point in printing out the value that was sent in the request payload.

Funny, I was just about to prepare a patch that used that very function to log invalid messages on the server side. On the client, it probably is not as necessary, since the client might know what it just sent.

Please have a look at the pull request https://github.com/dropwizard/dropwizard/pull/1001/
and advice if it is okay.


Release Metafacture core 5.7.0

Follows up https://github.com/metafacture/metafacture-core/issues/487.
See https://github.com/metafacture/metafacture-core/issues/491.
Blocked by https://github.com/metafacture/metafacture-core/pull/507.

[x] update dependencies if these are promising to not break much(nothing this time)
[ ] test release candidate
[ ] release on maven central
[ ] release on github
[ ] update flux-commands
[ ] write blog post, see PR
[ ] toot
[ ] write to email list

Based on this PR is the sonatype SNAPSHOT release 5.7.0-rc2-SNAPSHOT and github packages 5.7.0-rc2 . See wiki/Maintainer-Guideline how to use it. Please test it and check mark:

[ ] lobid-resources
[ ] limetrans
[ ] fix
[ ] playground

fix:
MetafixMethodTest > shouldUriEncodePathSegment() FAILED
    org.mockito.exceptions.verification.VerificationInOrderFailure:
    Verification in order failure
    Wanted but not invoked:
    streamReceiver.literal(
        "id",
        "slash%2F990223521400206441%3ADE%2DA96%3A61%20TYD%2016%283%29%23%21"
    );
    -> at org.metafacture.metafix.MetafixMethodTest.lambda$shouldUriEncodePathSegment$318(MetafixMethodTest.java:4023)
    Wanted anywhere AFTER following interaction:
    streamReceiver.startRecord("1");
    -> at org.metafacture.metafix.Metafix.endRecord(Metafix.java:248)
        at org.metafacture.metafix.MetafixMethodTest.lambda$shouldUriEncodePathSegment$318(MetafixMethodTest.java:4023)
        at org.metafacture.metafix.MetafixTestHelpers.lambda$assertFix$0(MetafixTestHelpers.java:113)
        at org.metafacture.metafix.MetafixTestHelpers.assertFix(MetafixTestHelpers.java:138)
        at org.metafacture.metafix.MetafixTestHelpers.assertFix(MetafixTestHelpers.java:113)
        at org.metafacture.metafix.MetafixMethodTest.shouldUriEncodePathSegment(MetafixMethodTest.java:4013)

Re fix test error: There are two options:

we change the test to assert on slash%2F990223521400206441%3ADE-A96%3A61+TYD+16%283%29%23%21 (note the + for whitespace in comparison to %20 or
we set urlEncode.setPlusForSpace(false) as default in fix (in contradiction to the default in mf-core

I would vote for 1.

Note also the difference re  - . We discussed this. So it was expected to break things in metafacture-fix.
You can already setSafeChars in metafacture-core. We would have to add the feature to metafacture-fix`.

All is done, closing.


DxChart zoomArgument(startValue, endValue) is missing

Hi,
in your chart zooming sample of DevExtreme
http://js.devexpress.com/Demos/WidgetsGallery/#demo/charts-advanced_features-zooming_and_scrolling
 there is a function
zoomArgument(startValue, endValue)
this seems not to be available via your Angular2 mappings

Hello,
You can get access to a DxChart instance by using the ViewChild decorator and the AfterViewInit lifecycle hook:
import {
    ViewChild
} from '@angular/core';

export class AppComponent implements AfterViewInit {
    @ViewChild(DxChart) DxChartComponent: DxChart;
    ngAfterViewInit(){
        this.DxChartComponent.instance.zoomArgument(800, 500);
    }
    ......
}


feat: default to navigatorLock on browsers

After having spent months of real-world testing on supabase.com, the navigatorLock is enabled on browsers that support the Navigator LocksManager API.
This makes sure that concurrent access to the storage in multiple tabs, windows or promises is no longer possible, thus removing issues such as:

Refreshing the session in parallel
Saving inconsistent state to storage

Wondering when can we expect to have this merged?

Right now.

Hi there,
this merge seems to be causing this issue now: https://github.com/supabase/supabase-js/issues/936
Can you please double check?
Thank you!
Paolo


From the proto3 Language Guide:

Note that creating custom options uses extensions, which are permitted only for custom options in proto3.

Thank you for reporting this, I also noticed that in some of protoc-s test files.
It will be fixed in the next release.


Add message for Save

Before it is possible to get an API key it is necessary to save the settings after input of IP and port.

Resolved by automatic save on loose focus of input fields for ip or port.


Daily sync from master to published

Proposed changes
Daily sync for November 12, 2019

Deploy preview for docsdocker ready!
Built with commit 24718c5e47eb85b7b219d34f13a4460df3616984
https://deploy-preview-9858--docsdocker.netlify.com


Add command set-bubble-transparent

I add a command to set the bubble transparent. This can be be mapped to a key. On the next keyup event the bubble is set opaque again.
'atom-text-editor:not(.mini)':
  'ctrl': 'linter:set-bubble-transparent'

This was discussed here: #608

Would you mind joining us in slack?
http://atom-slack.herokuapp.com

:+1: We should merge after the code is cleaned up.

LGTM after the changes.

I just noticed, when the editor looses focus the bubble stays transparent. So I need a way to handle this.

do this in the file require area
currentWindow = require('remote').getCurrentWindow()

and this in setTransparent
currentWindow.on 'blur', @setBubbleOpaque

and in setBubbleOpaque
currentWindow.off 'blue', @setBubbleOpaque

More info here and here.

@steelbrain thx

@steelbrain Actually in this case, since it is in a view you access the window directly and use window.addEventListener and window.removeEventListener.

I think it should be working as expected now.

Confirmed

Do you want me to squash the commites?

Squashing commits is not really necessary :)

LGTM

@josa42 Thanks again. :clap:

@steelbrain My pleasure!

People, I feel like we should add a default keybinding for this. 'cause not all of users are gonna want to modify the keymap.

@steelbrain I'm with you!


Fix player sprite flickering

Because the player sprite is drawn in the mainline code it is not tied to VBLANK and as such flickers.
The original code drew the player sprite in an interrupt routine interentry(), which was controlled by dontupdatedizzy flag.
When dontupdatedizzy was 0 (enable), it would call updatedizzy().

In my implementation of the updatedizzy() function I did have a waitvsync() call, however this doesn't have the desired effect.


attempt to index local 'heading' (a nil value)

when exec h fold-manual it failed
Error executing lua callback: ...site/pack/lazy/opt/helpview.nvim/lua/helpview/parser.lua:68: attempt to index local 'heading' (a nil value)
stack traceback:
        ...site/pack/lazy/opt/helpview.nvim/lua/helpview/parser.lua:68: in function 'vimdoc'
        ...site/pack/lazy/opt/helpview.nvim/lua/helpview/parser.lua:359: in function 'fn'
        ...6/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:473: in function 'for_each_tree'
        ...site/pack/lazy/opt/helpview.nvim/lua/helpview/parser.lua:355: in function 'init'
        ...arvim/site/pack/lazy/opt/helpview.nvim/ftplugin/help.lua:75: in function <...arvim/site/pack/lazy/opt/helpview.nvim/ftplugin/help.lua:32>

I am not getting any errors though?
Can you send a screenshot?

Here is my (debugging) init.lua with the error that occurs when I do :h (or any other help command). I'm not using any particular plugin manager, just using Nix/Home Manager to place the plugin downloads the vim path.

However using a modified version of the minimal init.lua provided by noice, I am able to open help files without any issues and helpview is active.

Are you sure you don't have some other plugin that works on help files?

Are you sure you don't have some other plugin that works on help files?

It doesn't appear to be that - running nvim with the following init.lua still generates the same error, and presumably no other plugins are being loaded (using nvim -u helpview-init-nolazy.lua)
require('helpview').setup()

It only happens on :h fold-manual, right?

It only happens on :h fold-manual, right?

Any help command will cause the error for me.

That is so strange. Even with the minimal init.lua I still can't reproduce the issue.
What neovim version are you using?

What neovim version are you using?

Also did you update the plugin?

I'm using commit 336d731
I don't have any lua experience so apologies if I can't provide much assistance here.

Can you manually add vim.print(row_start) before this line and see what gets printed?

Which help file did you open?

I need it to check what is on that line.

Which help file did you open?
In the above screenshot, I was doing :h so it gives 40, 43, 60
:h nvim gives the rows 21, 72
:h fold-manual gives the rows 13, 273, 463, 576, 617

That is very strange.

What does :InspectTree show on these lines? Does NixOs get a different version of tree-sitter?
Anyway, you can just do :h, 40j & run :InspectTree and see if it looks any different than my screenshot.

:TSUpdate says all parsers are up to date
Here's a screen recording of running that set of commands and it does land on an h1 element, though I have no idea why unless we're somehow looking at different help files.
https://github.com/user-attachments/assets/1e36683d-a619-4572-98f4-6a7d06290539

What does :InspectTree show on those lines?

Just do :h, 40j & run :InspectTree and see if it looks any different than my screenshot.

I have found the issue.
You treesitter shows (word) (word). It should be showing (delimiter) (heading).

There's definitely something wrong with the parser you are using (headings should be highlighted even without the plugin, which isn't the case in the video).

You most likely don't have this PR in your parser.

Yup, nixpkgs has nvim-treesitter rev 8012b55, which pulls vimdoc b711df (as per their lockfile.json), one commit before that PR is merged. So looks like myself and anyone else having issues with this need to be on at least nvim-treesitter rev 69341a2.


Scss: ignore leading combinator

Hi, I just updated grunt-csscomb to version 4.0.0 from 3.11. It comes with csscomb 4.2. Unfortunately after running it, it moved all my leading combinators. This behavior was fixed a while ago here: https://github.com/csscomb/csscomb.js/pull/599 But seems to be back in 4.2?
Even if I install version 4.3 and run grunt, I get the same behavior. When I downgrade again to 3.1.1 of grunt-csscomb it works.

config:
    "exclude": [
        ".git/**",
        "._*",
        "node_modules/**"
    ],
    "always-semicolon": true,
    "block-indent": 2,
    "tab-size": 2,
    "color-case": "lower",
    "color-shorthand": true,
    "element-case": "lower",
    "leading-zero": false,
    "quotes": "double",
    "remove-empty-rulesets": false,
    "space-before-colon": "",
    "space-after-colon": " ",
    "space-before-combinator": " ",
    "space-after-combinator": " ",
    "space-between-declarations": "\n",
    "space-before-opening-brace": " ",
    "space-after-opening-brace": "\n",
    "space-before-closing-brace": "\n",
    "space-after-selector-delimiter": "\n",
    "unitless-zero": true,
    "vendor-prefix-align": false,
    "sort-order": [

I have a new insight. I just update my node version to 8.16.1. It looks like it is not happening then. I was running 6.4.0 before and that looks like it's insight all requirements but maybe somewhere node 8 was needed.


Solder cables on ESP32 CAM

https://github.com/gramaziokohler/clamp_electronics/blob/master/10_ESP32CAMAdapter/10_ESP32CAMAdapter.md

Solder cables to save space.

The header pins are pushed to the other side of the ESP 32.
2 Cables soldered to GND and 5V. Wireless antenna also will go out of the same hole in the camera mount.


Limitations pywinauto

So I tried quite hard to get some CustomLists (I think they are) of applications and failed, so I wondered about the limitations of what could be achieved. The content of these lists dont show up on inspect.exe (msaa and uia mode),  spyxx, pyinspect and similar tools. If that is the case, are we already out of luck or not necessarily? Would would be the most native approach to get information out of the application.
So in that context I wondered what would be an attempt to an extremely extensive search of an application and all its elements and print out every text rich_text legacyproperties and so and to see if a "text" is in principle reachable.
Sorry about the broad question, its not really an issue but about what is in principle possible. The lib is superb and I am a huge fan!

Is there some info about which GUI framework was used for the app development? If it's .NET, technically it's possible to inject managed DLL to reach internal properties of every control (Squish and TestComplete use that way). We have just long term plans to research in this direction. The proof of concept is here: https://github.com/vperevalov/WPFA but we haven't tried to touch it yet.
If it's not .NET, it's more likely you're out of luck. But some info would be helpful anyway. I can't recommend you give up if I have incomplete info. If there is something private, no problem to contact me by gmail (just .replace("-", ".") for my GitHub nickname). I can sign NDA (non-disclosure agreement) if necessary.

@blaaaaaaa I've found that the "Snoop" tool also provided much more information than others for .NET applications, by injecting code into applications - you might want to give it a try to investigate the issue.


Duplicate issue (#1602): [SDImageCache storeImage:forKey:toDisk:completion:]: unrecognized selector sent to instance

New Issue Checklist

[x] I have read and understood the CONTRIBUTING guide
[x] I have read the Documentation
[x] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
e.g. ios

Platform Version
e.g. 10.3.2

SDWebImage Version
e.g. 4.0

Integration Method
e.g. cocoapods

Xcode Version
e.g. Xcode 8.3.3

Repro rate
e.g. all the time (100%)

Repro with our demo prj
e.g. does it happen with our demo project? NA

Demo project link
e.g. link to a demo project that highlights the issue NA

Issue Description and Steps
Please fill in the detailed description of the issue (full output of any stack trace, compiler error, ...) and the steps to reproduce the issue.
Hello! This is the same issue at #1602, where I'm getting the unrecognized selector when calling storeImage:forKey:toDisk:completion:, after migrating to SDWebImage 4.0. The reason I'm posting is that the person who opened the original issue did not clarify how to resolve it. I have been using this framework for awhile on the various 3.x versions in the same app and it worked flawlessly. However, after upgrading to 4.0, I'm not getting the below error...
-[SDImageCache storeImage:forKey:toDisk:completion:]: unrecognized selector sent to instance 0x174282e90
Here is the code...
@property (strong, nonatomic) SDImageCache *imageCache;
// lazy instantiate imageCache
- (SDImageCache *)imageCache {

    if (!_imageCache) {
        _imageCache = [[SDImageCache alloc] initWithNamespace:NAME_SPACE_IMAGE_CACHE];
        // BELOW LINE NO LONGER WORKS WITH 4.0.0
        //[_imageCache setMaxCacheAge:ONE_HOUR_IN_SECONDS * 3]; // cache age limit set to 3 hours (in seconds)
    }

    return _imageCache;
}
**/* This is the line that throws the error */**
[[SDImageCache sharedImageCache] storeImage:[UIImage imageWithContentsOfFile:coffeeImageData.imageURL.path] forKey:coffeeImageData.imageURL.absoluteString toDisk:YES completion:^{
                                    NSLog(@"INFO: CID Image cached successfully!");
                                }];

Also, I'm on the latest version of OS X and XCode. Please help me resolve this! A working app is now completely broken after migrating to 4.0. Thank you!

clean your derived data folder and then try to rebuild

I'm not sure which folder is the derived data. I did do a clean, then build and that did not make any difference.

~/Library/Developer/Xcode/DerivedData

Thanks!

if this solved your issue let me know so i can close the ticket

Yep, that worked...thanks!