timerecurrence not building

$ nixos-version
16.03pre73106.b1dca6c (Emu)
$ nix-shell --version
nix-shell (Nix) 1.10

Getting time-recurrence and building fails during the testing stage. I believe that tests are not expected to compile for timerecurrence because its test-suite flag is disabled by default. However, it is clearly getting enabled for the build.
Below is the full output:
$ nix-shell -p haskellPackages.time-recurrence
these derivations will be built:
  /nix/store/qr6n1g9x5819l56mq9cnxz46nzs517ny-time-recurrence-0.9.2.drv
building path(s) ‘/nix/store/g51wani86yafwydqadfapnayy7wzm6ax-time-recurrence-0.9.2’
setupCompilerEnvironmentPhase
Build with /nix/store/h0i71d1bi6a75rndb59yk3nas83yajd4-ghc-7.10.2.
unpacking sources
unpacking source archive /nix/store/ch14yd9f2q340bjdcynpw6q7s89s82zx-time-recurrence-0.9.2.tar.gz
source root is time-recurrence-0.9.2
patching sources
Replace Cabal file with edited version from http://hackage.haskell.org/package/time-recurrence-0.9.2/revision/1.cabal.
compileBuildDriverPhase
setupCompileFlags: -package-db=/tmp/nix-build-time-recurrence-0.9.2.drv-0/package.conf.d -j1 -threaded
[1 of 1] Compiling Main             ( Setup.hs, /tmp/nix-build-time-recurrence-0.9.2.drv-0/Main.o )
Linking Setup ...
configuring
configureFlags: --verbose --prefix=/nix/store/g51wani86yafwydqadfapnayy7wzm6ax-time-recurrence-0.9.2 --libdir=$prefix/lib/$compiler --libsubdir=$pkgid --with-gcc=gcc --package-db=/tmp/nix-build-time-recurrence-0.9.2.drv-0/package.conf.d --ghc-option=-optl=-Wl,-rpath=/nix/store/g51wani86yafwydqadfapnayy7wzm6ax-time-recurrence-0.9.2/lib/ghc-7.10.2/time-recurrence-0.9.2 --enable-split-objs --disable-library-profiling --disable-executable-profiling --enable-shared --enable-library-vanilla --enable-executable-dynamic --enable-tests
Configuring time-recurrence-0.9.2...
Flags chosen: test-suite=False
Dependency HUnit ==1.2.*: using HUnit-<IP_ADDRESS>
Dependency base ==4.*: using base-<IP_ADDRESS>
Dependency data-ordlist >=0.4.5: using data-ordlist-<IP_ADDRESS>
Dependency mtl >=2.0 && <2.3: using mtl-2.2.1
Dependency old-locale ==1.0.*: using old-locale-<IP_ADDRESS>
Dependency test-framework >=0.8: using test-framework-<IP_ADDRESS>
Dependency test-framework-hunit >=0.3.0: using test-framework-hunit-<IP_ADDRESS>
Dependency time >=1.4 && <2: using time-<IP_ADDRESS>
Using Cabal-<IP_ADDRESS> compiled by ghc-7.10
Using compiler: ghc-7.10.2
Using install prefix:
/nix/store/g51wani86yafwydqadfapnayy7wzm6ax-time-recurrence-0.9.2
Binaries installed in:
/nix/store/g51wani86yafwydqadfapnayy7wzm6ax-time-recurrence-0.9.2/bin
Libraries installed in:
/nix/store/g51wani86yafwydqadfapnayy7wzm6ax-time-recurrence-0.9.2/lib/ghc-7.10.2/time-recurrence-0.9.2
Private binaries installed in:
/nix/store/g51wani86yafwydqadfapnayy7wzm6ax-time-recurrence-0.9.2/libexec
Data files installed in:
/nix/store/g51wani86yafwydqadfapnayy7wzm6ax-time-recurrence-0.9.2/share/x86_64-linux-ghc-7.10.2/time-recurrence-0.9.2
Documentation installed in:
/nix/store/g51wani86yafwydqadfapnayy7wzm6ax-time-recurrence-0.9.2/share/doc/x86_64-linux-ghc-7.10.2/time-recurrence-0.9.2
Configuration files installed in:
/nix/store/g51wani86yafwydqadfapnayy7wzm6ax-time-recurrence-0.9.2/etc
No alex found
Using ar found on system at:
/nix/store/390z7i593kfnysfyx4sawlgxi8fvw074-binutils-2.23.1/bin/ar
No c2hs found
No cpphs found
Using gcc version 4.9.3 given by user at:
/nix/store/k495n2di6l9lq5blrxyi1m4a5pb6n7pa-gcc-wrapper-4.9.3/bin/gcc
Using ghc version 7.10.2 found on system at:
/nix/store/h0i71d1bi6a75rndb59yk3nas83yajd4-ghc-7.10.2/bin/ghc
Using ghc-pkg version 7.10.2 found on system at:
/nix/store/h0i71d1bi6a75rndb59yk3nas83yajd4-ghc-7.10.2/bin/ghc-pkg
No ghcjs found
No ghcjs-pkg found
No greencard found
Using haddock version 2.16.1 found on system at:
/nix/store/h0i71d1bi6a75rndb59yk3nas83yajd4-ghc-7.10.2/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.67 found on system at:
/nix/store/h0i71d1bi6a75rndb59yk3nas83yajd4-ghc-7.10.2/bin/hpc
Using hsc2hs version 0.67 found on system at:
/nix/store/h0i71d1bi6a75rndb59yk3nas83yajd4-ghc-7.10.2/bin/hsc2hs
Using hscolour version 1.22 found on system at:
/nix/store/sha1ywqd9q07yq5zrbxai2wy3sps6pm2-hscolour-1.23/bin/HsColour
No jhc found
Using ld found on system at:
/nix/store/k495n2di6l9lq5blrxyi1m4a5pb6n7pa-gcc-wrapper-4.9.3/bin/ld
No lhc found
No lhc-pkg found
No pkg-config found
Using strip version 2.23 found on system at:
/nix/store/390z7i593kfnysfyx4sawlgxi8fvw074-binutils-2.23.1/bin/strip
Using tar found on system at:
/nix/store/622ych28qrgjsn2mwiwhf7rf06hllp8b-gnutar-1.28/bin/tar
No uhc found
building
Building time-recurrence-0.9.2...
Preprocessing library time-recurrence-0.9.2...
[ 1 of 15] Compiling Data.Time.Recurrence.AndThen ( src/Data/Time/Recurrence/AndThen.hs, dist/build/Data/Time/Recurrence/AndThen.o )
[ 2 of 15] Compiling Data.Time.Calendar.WeekDay ( src/Data/Time/Calendar/WeekDay.hs, dist/build/Data/Time/Calendar/WeekDay.o )
[ 3 of 15] Compiling Data.Time.Moment.Private ( src/Data/Time/Moment/Private.hs, dist/build/Data/Time/Moment/Private.o )
[ 4 of 15] Compiling Data.Time.Moment.Interval ( src/Data/Time/Moment/Interval.hs, dist/build/Data/Time/Moment/Interval.o )
[ 5 of 15] Compiling Data.Time.Moment.StartOfWeek ( src/Data/Time/Moment/StartOfWeek.hs, dist/build/Data/Time/Moment/StartOfWeek.o )
[ 6 of 15] Compiling Data.Time.Calendar.Month ( src/Data/Time/Calendar/Month.hs, dist/build/Data/Time/Calendar/Month.o )

src/Data/Time/Calendar/Month.hs:29:16: Warning: Tab character

src/Data/Time/Calendar/Month.hs:30:16: Warning: Tab character
[ 7 of 15] Compiling Data.Time.CalendarTime.CalendarTime ( src/Data/Time/CalendarTime/CalendarTime.hs, dist/build/Data/Time/CalendarTime/CalendarTime.o )
[ 8 of 15] Compiling Data.Time.CalendarTime ( src/Data/Time/CalendarTime.hs, dist/build/Data/Time/CalendarTime.o )
[ 9 of 15] Compiling Data.Time.Moment.Moment ( src/Data/Time/Moment/Moment.hs, dist/build/Data/Time/Moment/Moment.o )
[10 of 15] Compiling Data.Time.Moment.FutureMoments ( src/Data/Time/Moment/FutureMoments.hs, dist/build/Data/Time/Moment/FutureMoments.o )
[11 of 15] Compiling Data.Time.Moment ( src/Data/Time/Moment.hs, dist/build/Data/Time/Moment.o )
[12 of 15] Compiling Data.Time.Moment.UTC ( src/Data/Time/Moment/UTC.hs, dist/build/Data/Time/Moment/UTC.o )
[13 of 15] Compiling Data.Time.Recurrence.ScheduleDetails ( src/Data/Time/Recurrence/ScheduleDetails.hs, dist/build/Data/Time/Recurrence/ScheduleDetails.o )
[14 of 15] Compiling Data.Time.Recurrence.Schedule ( src/Data/Time/Recurrence/Schedule.hs, dist/build/Data/Time/Recurrence/Schedule.o )
[15 of 15] Compiling Data.Time.Recurrence ( src/Data/Time/Recurrence.hs, dist/build/Data/Time/Recurrence.o )
In-place registering time-recurrence-0.9.2...
Preprocessing test suite 'test-time-recurrence' for time-recurrence-0.9.2...
[ 1 of 16] Compiling Data.Time.Recurrence.AndThen ( src/Data/Time/Recurrence/AndThen.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/Recurrence/AndThen.dyn_o )
[ 2 of 16] Compiling Data.Time.Calendar.WeekDay ( src/Data/Time/Calendar/WeekDay.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/Calendar/WeekDay.dyn_o )
[ 3 of 16] Compiling Data.Time.Moment.Private ( src/Data/Time/Moment/Private.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/Moment/Private.dyn_o )
[ 4 of 16] Compiling Data.Time.Moment.Interval ( src/Data/Time/Moment/Interval.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/Moment/Interval.dyn_o )
[ 5 of 16] Compiling Data.Time.Moment.StartOfWeek ( src/Data/Time/Moment/StartOfWeek.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/Moment/StartOfWeek.dyn_o )
[ 6 of 16] Compiling Data.Time.Calendar.Month ( src/Data/Time/Calendar/Month.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/Calendar/Month.dyn_o )

src/Data/Time/Calendar/Month.hs:29:16: Warning: Tab character

src/Data/Time/Calendar/Month.hs:30:16: Warning: Tab character
[ 7 of 16] Compiling Data.Time.CalendarTime.CalendarTime ( src/Data/Time/CalendarTime/CalendarTime.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/CalendarTime/CalendarTime.dyn_o )
[ 8 of 16] Compiling Data.Time.CalendarTime ( src/Data/Time/CalendarTime.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/CalendarTime.dyn_o )
[ 9 of 16] Compiling Data.Time.Moment.Moment ( src/Data/Time/Moment/Moment.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/Moment/Moment.dyn_o )
[10 of 16] Compiling Data.Time.Moment.UTC ( src/Data/Time/Moment/UTC.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/Moment/UTC.dyn_o )
[11 of 16] Compiling Data.Time.Moment.FutureMoments ( src/Data/Time/Moment/FutureMoments.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/Moment/FutureMoments.dyn_o )
[12 of 16] Compiling Data.Time.Moment ( src/Data/Time/Moment.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/Moment.dyn_o )
[13 of 16] Compiling Data.Time.Recurrence.ScheduleDetails ( src/Data/Time/Recurrence/ScheduleDetails.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/Recurrence/ScheduleDetails.dyn_o )
[14 of 16] Compiling Data.Time.Recurrence.Schedule ( src/Data/Time/Recurrence/Schedule.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/Recurrence/Schedule.dyn_o )
[15 of 16] Compiling Data.Time.Recurrence ( src/Data/Time/Recurrence.hs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Data/Time/Recurrence.dyn_o )
[16 of 16] Compiling Main             ( tests/Tests.lhs, dist/build/test-time-recurrence/test-time-recurrence-tmp/Main.dyn_o )

tests/Tests.lhs:30:28:
    Ambiguous occurrence ‘defaultTimeLocale’
    It could refer to either ‘System.Locale.defaultTimeLocale’,
                             imported from ‘System.Locale’ at tests/Tests.lhs:16:25-41
                          or ‘Data.Time.defaultTimeLocale’,
                             imported from ‘Data.Time’ at tests/Tests.lhs:17:3-18
                             (and originally defined in ‘time-<IP_ADDRESS>:Data.Time.Format.Locale’)

tests/Tests.lhs:30:46:
    Ambiguous occurrence ‘rfc822DateFormat’
    It could refer to either ‘System.Locale.rfc822DateFormat’,
                             imported from ‘System.Locale’ at tests/Tests.lhs:16:44-59
                          or ‘Data.Time.rfc822DateFormat’,
                             imported from ‘Data.Time’ at tests/Tests.lhs:17:3-18
                             (and originally defined in ‘time-<IP_ADDRESS>:Data.Time.Format.Locale’)
builder for ‘/nix/store/qr6n1g9x5819l56mq9cnxz46nzs517ny-time-recurrence-0.9.2.drv’ failed with exit code 1
error: build of ‘/nix/store/qr6n1g9x5819l56mq9cnxz46nzs517ny-time-recurrence-0.9.2.drv’ failed
/run/current-system/sw/bin/nix-shell: failed to build all dependencies

Since the tests are clearly not passing, is this considered a problem with the configure stage of nixpkgs not respecting the cabal flag, or with the upstream package?
Charles

cc @peti

@charles-cooper, these build errors are a bug in the package that should be reported upstream and fixed upstream. We configure (almost) all of our Haskell builds with --enable-tests, and IMHO it's quite reasonable to expect that test code shipped as part of the distribution succeeds.
Cc: @hellertime, who maintains time-recurrence.

It's still my responsibility but it's been a while :) I'll have a look at what's failing. Is there a specific build environment that I should be targeting here?
Sent from my iPhone

On Apr 4, 2016, at 6:06 AM, Peter Simons<EMAIL_ADDRESS>wrote:
@charles-cooper, these build errors are a bug in the package that should be reported upstream and fixed upstream. We configure (almost) all of our Haskell builds with --enable-tests, and IMHO it's quite reasonable to expect that test code shipped as part of the distribution succeeds.
Cc: @hellertime, who maintains time-recurrence.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@hellertime, this issue has all the information you'll need.

Thanks. I'll have a look.
Sent from my iPhone

On Apr 4, 2016, at 4:20 PM, Peter Simons<EMAIL_ADDRESS>wrote:
@hellertime, this issue has all the information you'll need.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

So it appears there was a breaking change in time between the version I was targeting and what is now in use. I just release 0.9.3 of time-recurrence that should address this, and have it building on GHC 7.10.2 in TravisCI. In addition the code is now building with stack.


Module 1.4 Assignment

Hello @jsueland , the exercise for 1.4 can be found here:
https://github.com/Campus-Advisors/campus-advisor-training-jsueland/blob/master/Module 1/Module 1.4 Assignment.md
Please complete this when you can.


@weave.op() does not work with Pydantic BaseModel functions or class variables

@weave.op() failure with BaseModel internal function
The code below fails the the error AttributeError: 'ObjectRecord' object has no attribute 'format'
import weave
from pydantic import BaseModel

class Book(BaseModel):
    title: str
    author: str

    def format(self) -> str:
        return f"{self.title} by {self.author}"

@weave.op()
def my_func(book: Book) -> str:
    return book.format()

weave.init("scratch-test")
book = Book(title="The Name of the Wind", author="Patrick Rothfuss")
print(my_func(book))

@weave.op() failure with BaseModel class variable
The code below fails with the error AttributeError: 'ObjectRecord' object has no attribute 'class_var'
from typing import ClassVar

import weave
from pydantic import BaseModel

class Book(BaseModel):
    title: str
    author: str

    class_var: ClassVar[str] = "class_var"

@weave.op()
def my_func(book: Book) -> str:
    return book.class_var

weave.init("scratch-test")
book = Book(title="The Name of the Wind", author="Patrick Rothfuss")
print(my_func(book))

Would you be open to a PR if I look into fixing this?
Any reference material I should look at before submitting one?

The culprit: https://github.com/wandb/weave/blob/41b5ad32303764585871da792f038510e40ac44e/weave/trace/object_record.py#L39
Looks like this only grabs model fields and doesn't grab any other information, which explains the missing functions and class variables.

Due to how pydantic BaseModel handling is implemented, @weave.op() removes everything except for the fields. This means built-in methods like model_dump are also no longer present.
I will try to update the code to handle porting over everything.

Fixed with #1390
Thanks!!


I can't see my containers in kinematic

Expected behavior
find my containers in Kinematic, like always when I open my Windows machine the first thing I do is going to Kinematic and I run my containers
Actual behavior
I can't find any of my containers in Kinematic.
Information about the Issue
I'm using the current Docker&kinematic version of Windows, normally when I open my computer I can see my containers in Kinematic, today I've found nothing, even when I "docker ps" or "docker images" I see nothing, like every thing is gone, I lost all my configs , all the data in my MongoDB, all the indexes in my Elasticsearch container, all the jobs in Jenkins, everything is gone. And i'm very sad now ..

if docker ps is showing no container, then Kitematic wont be showing anything either.
If this is with Docker for Windows, please open a thread in the Docker forums, as seen in the docs link you received, with your logs and steps to reproduce.


dtc,python.pkgs.libfdt: drop python buildInput

Motivation for this change
This doesn't seem to be necessary to build the library with
strictDeps = true, or when cross-compiling.
Would appreciate somebody who uses this with Python doing a sanity check for me.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

Result of nixpkgs-review pr 72744 1

1 package marked as broken and skipped:
- odroid-xu3-bootloader

7 packages built:
- diffoscope
- dtc
- fwts
- python27Packages.libfdt
- python37Packages.libfdt
- python38Packages.libfdt
- ubootTools


Support for nextjs v13

Is your feature request related to a problem? Please describe.
Actually I see that all the examples are based on nextjx v12 that used only the pages folder, but now in nextjs v13 they implemented the app page (https://nextjs.org/blog/next-13), so I wonder if there is a way to use it with nextjs v13 and if not, it would be great to implement it.
Describe the solution you'd like
Examples or compatibility with nextjs v13.
Describe alternatives you've considered
I do not know.

Hi @kaname-png and thanks for reaching out!
I'm exploring this currently in #144 (basic support) and #139 (integration with RSC). I'll close this issue as soon as I have found a good solution!


No initial transitions

Describe the solution you'd like
When loading the grid, every item is transitioning from the top left to its real position. It would be perfect if the elements appear in their final position.
Describe alternatives you've considered
I tried to hide all items until the transitions are finished but that is a horrible solution.
Any tips for me to implement that? I am new to vue and js development but I am trying my best :)

You can cancel the transitions by overriding these CSS rules:
.vue-grid-item {
  -webkit-transition: unset !important;
  transition: unset !important;;
  -webkit-transition-property: unset !important;
  transition-property: unset !important;
}


Add error validation for SIN

Uses a regex to remove spaces, dashes and underscores then checks that it's 9 characters and then checks that it's an int.

Also, something @nmakuch and I were doing before was putting in screenshots or gifs if there was a new page or some new behaviour. (like this one: https://github.com/cds-snc/cra-claim-tax-benefits/pull/16)
It's maybe less needed now that we have the github PRs, but it's still kind of nice if you have an easy way to snap a photo.


Support GemFire 8.2

Are there any plans to continue this library and support newer versions of Gemfire, or is this project effectively dead?

@jmpresso I am not aware of any current plans to make enhancements to this library. That doesn't mean it's not gonna happen though.
There is some work being done on a ProtoBuf based API. That should make it easier in the future to interact with GemFire from any language. Would that be helpful for you?

@pivotal-amurmann - Thanks for the response. I'm honestly not very familiar with ProtoBuf- I'll have to do some research there to understand how complex it would be, compared to a seemingly simpler interface for Node like this looked to have previously provided.


Incorrect frame rate sending

I am streaming using rtmp. I setup 30fps on app but its sending incorrect fps.
Can you help me why its behaving like that?

I disabled fpslimiter because this produce audio sync problems in stream. For this reason this number is not relevant if you are using a mode that render with surface. Anyway I will check this because that fps is not real because your display can't render more than 60fps. So it is imposible in display mode.


No compatible version found<EMAIL_ADDRESS>

This problem occurs durring installing NPM dependencies:
# meteor npm install
npm ERR! Linux 4.4.39-moby
npm ERR! argv "/root/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/node" "/root/.meteor/packages/meteor-tool/1.4.2_3/mt-os.linux.x86_64/dev_bundle/bin/npm" "install"
npm ERR! node v4.6.2
npm ERR! npm  v3.10.9
npm ERR! code ETARGET

npm ERR! notarget No compatible version found<EMAIL_ADDRESS>npm ERR! notarget Valid install targets:
npm ERR! notarget 1.10.13, 1.10.12, 1.10.11, 1.10.10, 1.10.9
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'mongoclient'
npm ERR! notarget

npm ERR! Please include the following file with any support request:
npm ERR!     /mongoclient/npm-debug.log

Hello there,
I never encountered this issue either in any OS, would you please share the OS details you're trying to execute this ?

Hello there,
I never encountered this issue either in any OS, would you please share the OS details you're trying to execute this ?


Support webpack-dev-server v5

Command
build
Description
Unable to resolve dependency peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular-devkit/build-webpack
npm ERR!   dev<EMAIL_ADDRESS>from the root project
Describe the solution you'd like
Add support for webpack-dev-server v5
Describe alternatives you've considered
No response

Support for Webpack-dev-server version 5 will be available in version 18. See: https://github.com/angular/angular-cli/pull/27250


3.0.0: Broken in LinuxEditor

BeaconConnectorFactory is missing
case RuntimePlatform.LinuxEditor:
and thus always fails initialization.
This will also fail for Closed Source Platforms (Consoles, mostly), which should be addressed in the future with a dedicated Exception ideally.

This has been resolved in the develop branch and will be included in the upcoming release. We will also improve how the exception is handled. Thank you for bringing this to our attention, your assistance is greatly appreciated!


fix CI cache

The CI cache seems to complain about a missing "path" argument or something similar.
Started happening after we moved to the new buildjet runners.

sir i want try this


Value of type 'InstagramEngine' has no member 'receivedValidAccessTokenFromURL '

Hello,
I'm trying to use InstagramKit in Swift but I think there is a problem with the framework in Swift for the receivedValidAccessTokenFromURL function. I checked this function in InstagramEngine.h and .m but Xcode itself doesn't recognize function and always shows error :
Value of type 'InstagramEngine' has no member 'receivedValidAccessTokenFromURL '
I use the last version of instagramKit (3.8) from Cocoapods.
Thank you

I believe that method was deprecated, and should now be receivedValidAccessToken.


[Bug] shell script about the var wrong

Code of Conduct

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

Search before asking

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

Describe the bug
description: I'm trying to solve the issue about #2062 , the job is to add shell style check util to the GitHub action, I try to add that in my fork project, when test the shellcheck, I found some script syntax errors

it's about /bin/stop-application.sh , the reason is $# is a int type, if we want compare, we should us -lt-gt, but the script us < or >
it's about /bin/kyuubi, we use exit -1, I know if we not use the code 0, it always report failed, but in shell, the right number is 0-255
it's about bin/docker-image-tool.sh, we should use #* replace #@

In bin/docker-image-tool.sh line 230:
if [[ "$@" = *--help ]] || [[ "$@" = *-h ]]; then
      ^--^ SC2199: Arrays implicitly concatenate in [[ ]]. Use a loop (or explicit * instead of @).
                              ^--^ SC2199: Arrays implicitly concatenate in [[ ]]. Use a loop (or explicit * instead of @).

In bin/kyuubi line 33:
if [[ "$@" = *--help ]] || [[ "$@" = *-h ]]; then
      ^--^ SC2199: Arrays implicitly concatenate in [[ ]]. Use a loop (or explicit * instead of @).
                              ^--^ SC2199: Arrays implicitly concatenate in [[ ]]. Use a loop (or explicit * instead of @)
In bin/kyuubi line 51:
    exit -1
         ^-- SC2242: Can only exit with status 0-255. Other data should be written to stdout/stderr.

In bin/stop-application.sh line 19:
if [[ $# < 1 ]] ; then
         ^-- SC2071: < is for string comparisons. Use -lt instead.

I think we should fix the bug in fix #206
Affects Version(s)
master
Kyuubi Server Log Output
No response
Kyuubi Engine Log Output
No response
Kyuubi Server Configurations
No response
Kyuubi Engine Configurations
No response
Additional context
No response
Are you willing to submit PR?

[X] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to fix.
[ ] No. I cannot submit a PR at this time.

I don't know the issue is right or wrong, should I fix that?

@pan3793 hi, i fix some file bug, could you assign the issue to me? there are some modify info
fix-#4057 info: modify the shellcheck errors file in ./bin

"$@" is a array, we want use string to compare. so modify "$@" => "$*"
tty mean execute the command, we can use $(tty) replace it
param $# is a number, compare number should use -gt/-lt,not >/<
not sure the /bin/kyuubi line 63 'exit -1' need modify? so the directory bin only have a shellcheck note in /bin/kyuubi


Option to add borders and/or drop shadows to fonts

On bright background images white font is hard or impossible to read. This could be mitigated by an option to activate font borders and/or drop shadows. I also think that drop shadows would look pretty cool, regardless of legibility issues 💯
PS: Thanks for making and maintaining this theme. It's an absolute joy to use.

Drop shadows cause performance issues if used a lot. When you say white font what doe you mean specifically? Would you want all text to have drop shadows everywhere or just certain text?

Mainly the text in the library overview. Especially the game title and the title of the current filter.

This option will be available in v1.2.3, no ETA on release


python311Packages.aioridwell: 2023.01.0 -> 2023.07.0

Diff: https://github.com/bachya/aioridwell/compare/refs/tags/2023.01.0...2023.07.0
Changelog: https://github.com/bachya/aioridwell/releases/tag/2023.07.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 242893 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.ridwell
python310Packages.aioridwell
python310Packages.aioridwell.dist
python311Packages.aioridwell
python311Packages.aioridwell.dist


Vulnerability roundup 101: nettle-3.6: 1 advisory [8.1]

search, files

[ ] CVE-2021-20305 CVSSv3=8.1 (nixos-unstable)

Scanned versions: nixos-unstable: f5e8bdd07d1.

Fixed in f688168abb7724c9cff22aa764786e444c8f5573.


add GetRandBytes() as wrapper for RAND_bytes()

add a small wrapper in util around RAND_bytes() and replace with GetRandBytes() in the code to log errors from calling RAND_bytes()
remove OpenSSL header rand.h where no longer needed
move rand functions from util to new random.h/.cpp

Works for me


Example not working -> TypeError: SimpleSchema is not a constructor

I always get a TypeError: SimpleSchema is not a constructor
The provided solutions like "remove your node_modules folder and run npm i again" are not working for me. I provided a simple Runkit sample, more or less copied over from the examples.
https://runkit.com/embed/y2txqblvkles

What bundler are you using? and are you using ES Module syntax or CommonJS (require)?
It looks like an ES Module compat problem, because SimpleSchema is the default export as an ES Module, if you are using require, you need to access the default export by name:
var SimpleSchema = require("simpl-schema").default

https://runkit.com/coagmano/5c86ead3d16d480012306954
Some bundlers, like Meteor, will attempt to automatically grab the default export when using require to save you the boilerplate, but does make it slightly less predictable

Important:
In my package.json i remove simpl-schema from devDependencies, and add to dependencies


User should be able to filter pins/trips by type/cost

Ref fridayideas/daytomato#66.

This is done!


Integrate the Student class into the User class and delete the Student class

Changes can be seen in commit b7e579401fdc423ae6e4ab1e97b67a77e54bc447


New guides (testing docs preview)

Confirmed that the preview is correctly working!
Closing for now since we're already using the new-guides branch deploy link.


Trim down java/multiproject snippet to contain only what's needed for the relevant guide sections

Remove all the cross-configuration and source code, leave only the minimum needed for the use cases demonstrated.

This one has quite an elaborate test setup - perhaps it is useful as a smoke test. I will update it to use convention plugins instead.


Fix unstake

I think this is the new variable name in the state https://github.com/OlympusDAO/olympusdao/blob/f3f0bc8e2c338912f84fa79ba87ea22705ab21af/src/actions/Stake.actions.js#L50

Is this right? Looks like it sets unstake allowance to the new unstake. In migrate need to approve unstake of oldsohm

True, the problem is fetchMigrationData is never being called

Works fine when you access the migration tab manually but not when you use the URL http://localhost:3000/#/stake/migrate


Updates tsec and rewrites sinks assignement

The latest tsec commit fixes a bug where tsec was no building properly postinstall, this PR updates tsec to the latest commit and pins it to that commit in package.json.
This PR also rewrites policy usages to all be of the same shape (i.e. policy?.createHTML(html) ?? html) and moves all the casts to the sinks assignment expressions directly as this is the only way tsec can recognize them.
This PR fixes #111289
Related issues are #108400 #103699 & https://github.com/googleinterns/tsec/issues/18

@koto & @uraj for visibility

Thanks @engelsdamien!


Dropdown for account link icon on a left side menu

If the user has multiple banks or validators linked to the account, we will display a dropdown of all the servers (in the same order as the side menu)
This is not happening right because network does not have accounts linked to multiple banks/validators

Outdated


[github] support jobs.<job_id>.steps[*].continue-on-error

Prevents a job from failing when a step fails. Set to true to allow a job to pass when this step fails.
See

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error

Adding v1 yaml support in #74


Sawyer Bot Motor Direction Fix

The front right and right elevation has been reversed in this update.

Merged. This is worrying as the changes are inconsistent with the anomaly patches for Lem's configuration: you reversed the signal to port 2 but not to port 3, whereas for Lem's bot both ports needed their signals to be reversed.


[Bug]: Cmd/Ctrl-c works intermittently on Anvil base DP

Is there an existing issue for this?

[X] I have searched the existing issues

Description
conversation
Steps To Reproduce
https://theappsmith.slack.com/archives/C025SE88KNE/p1709729652471759
Public Sample App
No response
Environment
Deploy Preview
Severity
High (Blocker to building)
Issue video log
No response
Version
Cloud

Moving it to blocked until we get usability results of Editor vs Widegt interactions POC. The POC fixes this issue.
cc: @ramsaptami @somangshu

Will fix this here #32138


Multi-task settings

Hi @nreimers
For the multi-task framework, does it always have to be pos and chunking? or it could be any sequence labelling tasks?

Hi. You can use it of course for any sequence tagging task. The POS and chunking code is just an example, which you can modify to be used for your use case.

I am really confused about the architecture of multi task framework as there is no diagram in the original paper. Could you please explain as to which layers are being shared? In the example that you have given pos is at the lower level because it appears first in the constructor? Each task has its own Bi-LSTM-CRF task specific network, which of the layers are being shared? Can you show this graphically?

In the Train_MultiTask.py example, the POS and chunking network both share the embedding layer and one LSTM layer. If you change params like this
params = {'classifier': ['CRF'], 'LSTM-Size': [100, 50], 'dropout': (0.25, 0.25)}

Both networks would share 2 stacked LSTM layers, the first with 100 recurrent units, the second with 50.
In that file, only the CRF is task specific.
If you run the code, the model architecture is also printed. Shared layers have the name shared_..., while task specific layers have the name POS_... and chunking_....
The order in the datasets dict doesn't matter.
In Train_MultiTask_Different_Levels.py, the POS layer uses the output from the first LSTM layer, while chunking has a task specific LSTM layer:
params = {'classifier': ['CRF'], 'LSTM-Size': [100], 'dropout': (0.25, 0.25),
          'customClassifier': {'unidep_pos': ['Softmax'], 'conll2000_chunking': [('LSTM', 50), 'CRF']}}

Both networks have one shared LSTM (LSTM-Size), then pos uses 'Softmax' on top of that shared LSTM layer. Chunking in contrast uses an LSTM with 50 units and then a CRF.

OK thanks for the detailed answer. Could also explain the difference between "Train_Multitask" and Train_Multitask_different_levels"?

Have a look at this paper:
https://www.aclweb.org/anthology/P16-2038
Train_Multitask_different_levels implements the ideas from that paper.

Thanks for the link.


Build customizations run before VCPKG

Describe the bug
When using the CUDA insight tool, the tool attempts to build files before vcpkg run.
Environment

OS: Windows
Compiler: VS 2019

To Reproduce
CUDA 11.2 build configuration enabled
Enable CUDA on a source file
Run in manifest mode and rebuild solution
Expected behavior
VCPKG installs all dependencies prior to the build starting
Failure logs
Logs.txt
Additional context
Add any other context about the problem here.

The work around was to add this command to the pre-build options:
$(VcpkgRoot)/vcpkg.exe install --triplet=$(VcpkgTriplet)
Seems uber hacky but it works.

Could you please provide a simple project?

ConsoleApplication6.zip

That should build using vcpkg manifest but with CUDA 11.2 installed it tries to run the build customization before vcpkg. Shouldn't vcpkg be run before any part of the build starts? I could add any number of build customizations and I would hope vcpkg systematically works with all of them unless they directly interfere with vcpkg.

@Adela0814

Sorry, currently the running mechanism of manifest mode in msbuild project is only triggered by build command, it cannot be started before build command.

Close this issue, this is not a bug.


some strange problem

when i use pprof display a heap profile, some strange info puzzles me ,
like that:
addr2line: invalid option -- i
Usage: addr2line [option(s)] [addr(s)]
Convert addresses into line number/file name pairs.
If no addresses are specified on the command line, they will be read from stdin
The options are:
-b --target=  Set the binary file format
-e --exe=  Set the input file name (default is a.out)
-s --basenames         Strip directory names
-f --functions         Show function names
-C --demangle[={none,auto,gnu,lucid,arm,hp,edg,gnu-v3,java,gnat,compaq}]
Demangle function names
--demangler=dso:function
Set dso and demangler function
-h --help              Display this information
-v --version           Display the program's version

i see https://google-perftools.googlecode.com/svn/trunk/doc/heapprofile.html,
i use pprof --base=/tmp/profile.0004.heap gfs_master /tmp/profile.0100.heap
but it doesn't work

pls help,thx

You're likely using super-old version of addr2line. What kind of OS you're using ? And what addr2line --version says?

yes, it's too old to run, now no errors when i use pprof,
the second question, could you tell me why?
thx

Why what ? Can you please elaborate ?

ah, i found why, some problem caused by myself
thx anyway ^_^

I have the same problem.
What did you do to fix this?
And yes, I'm using an old linux too.


Use Cesium sun as lightsource for material

When converting Collada models to glTF via the web service you provide and then displaying the model in Cesium makes the model unaffected by the lighting direction of the sun. I saw that the obj2gltf library added a --cesium flag to address this issue. Would it be possible for the web service to provide a similar feature?
As a side note, it is not possible for us to use obj2gltf because of limitations in storing model hierarchies in the obj format, which are needed for rotating parts of the models we use.

@laurensdijkstra I moved this to https://github.com/AnalyticalGraphicsInc/cesium/issues/4207 since this repo is just example code, not the actual model converter used on cesiumjs.org.

Thanks! I was already wondering if this was the right repo because I didn't see any updates since a long time yet online al kinds of new features were added.


NR89185: Vertica - new quickstart

Ticket: https://issues.newrelic.com/browse/NR-89185
Dashboard: https://onenr.io/07j9YYqDVjO
Summary
A concise description of the changes being introduced. Please review the pre-merge checklist section to validate this pull request is ready for review and merge. If it is not ready, please mark the pull request as a draft.
The owners of this repo are not experts in the subject matter of the quickstarts. We review for the quickstart to be functional and for security risks. If you are seeking feedback on the content of the quickstart, please seek out a subject matter expert. If you are not an internal NR contributor, we can do our best to connect you with a content reviewer.

Pre merge checklist

[ ] Did you check you NRQL syntax? - Does it work?
[ ] Did you include a Data source and Documentation reference?
[ ] Are all documentation links publicly accessible?
[ ] Did you check your descriptive content for voice and tone?
[ ] Did you check your descriptive content for spelling and grammar errors?
[ ] Did you review your content with a subject matter expert? (e.g. a Browser agent quickstart is reviewed with a member of the Browser Agent team)

Dashboards

[ ] Does the PR contain a screenshot for each of your dashboards?
[ ] Do your screenshots show data?
[ ] Has the sanitization script been run on each dashboard?

Alerts

[ ] Did you check that your alerts actually work?

closing this PR as we have created another PR: https://github.com/newrelic/newrelic-quickstarts/pull/2065


Support for unit testing workflows

Closed in https://github.com/cschleiden/go-workflows/commit/3d39a280f78d2064d485161c418a9edb9cb40ad8


feat: allow ImageField form override

create wagtail.image.models.ImageField with formfield method that can be extended and overwritten.

remove the branch in formfield_for_dbfield  that hard coded the formfield to WagtailImageField

Please check the following:

[X] Do the tests still pass?[^1]
They seem to be passing except one and I think it's because of FS related issues on windows. the runtests.py output is too noisy to really tell what is happening. CI will tell.

[X] Does the code comply with the style guide?

[X] Run make lint from the Wagtail root.

[X] For Python changes: Have you added tests to cover the new/fixed behaviour?
Existing behavior shouldn't change.  The behavior is Django behavior, so we shouldn't need to re-test it.I'm assuming existing tests already verify forms for models with models.ImageField have the correct form fields.

[X] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]
There are no front-end changes.

[X] For new features: Has the documentation been updated accordingly?
This isn't a new feature. From a developer's perspective, it is an upstream Django feature that refactoring has unmasked.

this is a proposed fix to https://github.com/wagtail/wagtail/issues/9088

Would it be possible to also add a unit test that covers the override/extend scenario so that it doesn't break in the future.

It'll be a week or two before I can come back around to it and this is a low priority for me. I've wrapped my current project implementation for this using monkey patching and https://github.com/wagtail/wagtail/pull/8974 is a higher priority for me since it will solve this problem that required this in the first place

I still have hopes of getting back around to these tests, but it is likely going to be at least a month before I can get back around to this.


Fixes #602: user configurable listener backlog

Codecov Report

Merging #721 (ca4e707) into main (4c51748) will increase coverage by 0.01%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main     #721      +/-   ##
==========================================
+ Coverage   27.00%   27.01%   +0.01%
==========================================
  Files         131      131
  Lines       31285    31288       +3
  Branches     4989     4989
==========================================
+ Hits         8448     8453       +5
+ Misses      21746    21745       -1
+ Partials     1091     1090       -1

Flag
Coverage Δ

unittests
27.01% <50.00%> (+0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

src/adaptors/adaptor_listener.c
36.41% <25.00%> (+0.39%)
:arrow_up:

src/adaptors/adaptor_common.c
14.38% <100.00%> (+1.18%)
:arrow_up:

src/entity.c
41.95% <0.00%> (+1.39%)
:arrow_up:

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


Error: list[torch.nn.Module]

Hi I'm running
I'm not sure if this is just my python version but it seems there are case-typos all over the place with use of typing classes
for example
https://github.com/anguyen8/gScoreCAM/blob/0dea5d5ced338673fb97be45e7f5a8015efe4b0e/tools/cam.py#L249
https://github.com/anguyen8/gScoreCAM/blob/0dea5d5ced338673fb97be45e7f5a8015efe4b0e/tools/heatmap2bb.py#L26
should  be List[torch.nn.Module] ?
and
https://github.com/anguyen8/gScoreCAM/blob/0dea5d5ced338673fb97be45e7f5a8015efe4b0e/visualize_cam.py#L183
should be tuple[str, float]
with from typing import List, Tuple
My interpeter also complains about
https://github.com/anguyen8/gScoreCAM/blob/0dea5d5ced338673fb97be45e7f5a8015efe4b0e/visualize_cam.py#L199
TypeError: Too many parameters for typing.List; actual 4, expected 1

If you are using python < 3.9, yes, we will need from typing import List, Tuple and change list to List and change tuple as well.
Another workaround is to install python > 3.9 which supports the typing in the repo.


Labels on status screen graphs.

It took me a while to know which graph was insulin and which was carbs.  Our school nurse has expressed confusion about it as well as my parents.  In my experience, it's a nearly universal response.
The consistent color coding is a step in the right direction, but maybe not sufficient.

Thanks for re-filing this. It's on my list, and mentioned it here but needed the bump back up.

I had done a label overlay on each graph at the upper left when I started using Loop to help me remember.  I am sure there is a much better way to accomplish the same thing using the the chartkit.

Those look pretty good! One thought is to push them to the upper right. Glucose should be trending towards the target range, there will be no doses in the future, and both IOB and COB will taper to zero, meaning that the label shouldn't interfere with data.

Chris Hannemann
<EMAIL_ADDRESS>
On Sep 23, 2016, at 10:48 AM, Jeremy M Lucas<EMAIL_ADDRESS>wrote:
I had done a label overlay on each graph at the upper left when I started using Loop to help me remember. I am sure there is a much better way to accomplish the same thing using the the chartkit.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I tried the upper right initially, but my typical use case always led to the labels being obscured by the data readout.  I also used verbose labels to get the concepts to stick in my head instead of Acronyms so this may be part of my issue.  Longer text may be useful for the "school nurse" use case.


custom_profile_fields: Make "Name" and "Hint" field of default "External account" type profile fields editable.

Name and hint fields of default "External account" type profile fields
can be updated, as the "external account type(subtype)" field of this
type profile field is still cannot be updated.
Disable "External account type" select field from External account type
profile field edit form, doing it because this select field is not
editable and it is incorrectly looks like editable.
Fixes: #22290

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

I tested this briefly, and it looks good to me!
I don't recall if we have a separate issue/PR for this, but we should also allow editing the "Name" and "Hint" fields when a new "External account" custom profile field is being created.

I ran out of time for cleaning this up, but pushed a partial commit intended to be squashed into the backend changes to make the logic correct; the implementation isn't done but the tests should verify the right things now.

If we ignore the field_data parameter then what we should return if someone tries to change field_data, code will just change the updatable data but what about the interface?

Finally, we should check the API documentation for this endpoint and make sure it correctly discusses this detail correctly.

I didn't find about updating custom profile fields in the API documentation.

For now, I squashed the changes from [squash] work commit and fixed the test error.

If we ignore the field_data parameter then what we should return if someone tries to change field_data, code will just change the updatable data but what about the interface?

I think it'd be a fine option to return an error if the passed field_data is nonempty and different from the existing field_data.
The current implementation, which allows changing the field_data in the API but not the UI, is just wrong.

The other thing that I don't understand with this PR is how we expect the DEFAULT_EXTERNAL_ACCOUNTS to interact with the name/hint metadata being saved with this PR.
Perhaps you can post in the api design thread on chat.zulip.org about this, because it's something we'll need to discuss with mobile clients as well.

The current implementation, which allows changing the field_data in the API but not the UI, is just wrong.

I don't understand how field_data is changeable from API, there will two fields in field_data subtype and url_pattern if this changes somehow validation function will return an error, if the value of subtype changes this new function changing_field_data_of_default_external_account will handle this, and if the value of url_pattern changes this function validate_external_account_field_data will return error

The current implementation, which allows changing the field_data in the API but not the UI, is just wrong.

Sorry, but I don't understand how field_data is changeable from API, there will two fields in field_data in case of external_account profile field subtype and url_pattern if this changes somehow validation function will return an error, if the value of subtype changes this new function changing_field_data_of_default_external_account will handle this, and if the value of url_pattern changes this function validate_external_account_field_data will return error

Merged, thanks @yogesh-sirsat!
I'll post about follow-ups in the chat.zulip.org thread.


Subject: Urgent: Issue with Token Swapping and Move to Razor in M1 Devnet & M2 Devnet

Dear Tech Team,
I hope this message finds you well. I am writing to bring to your attention an issue I've encountered while attempting to swap tokens on both M1 Devnet and M2 Devnet environments.
Specifically, I am experiencing the following problems:
Token Swapping Error: When attempting to swap tokens, I am encountering an error where the process hangs indefinitely at "Fetching best price...". This delay significantly impacts usability.

Move to Razor Failure: Additionally, during the token swapping process, I intermittently encounter failures when attempting to proceed with "Move to Razor".
These issues are occurring consistently across both development networks and are impacting my workflow significantly.
Could you please investigate and resolve these issues at your earliest convenience? If further information or access to logs is needed, please let me know, and I will provide them promptly.
Thank you for your prompt attention to this matter.
Best regards,
Mohd Irfan
0x044ea1c74ae0b4a3e4f498bcf8820ddee645bd6f42542ef203ffa2c942ba37cd

Hi, I would raise this with Razor wallet, thanks.


[rebranch] Merge main -> rebranch

Conflicts:

lib/AST/TypeCheckRequests.cpp renamed isMoveOnly which requires
a static_cast on rebranch because Optional is now a std::optional

Also fixed IsEscapableRequest::getCachedResult which needs a similar static_cast.

@swift-ci please smoke test


ISPN-9701 TransactionTable does not shutdown gracefully

https://issues.jboss.org/browse/ISPN-9701
@danberindei Please review.
Needs backporting to 9.4.x, 9.3.x, and 8.2.x.

Integrated directly in master and 9.4.x, created #6477 for 9.3.x and #6478 for 8.2.x


Could you provide an example about how to use this library

Could you please build a example about how to use you libray in the java code?
Thanks!

Agreed!

example

So.. somebody have some example shows how to use this library?
Thanks in advance.

I'm considering to use this lib as well... But I would appreciate some examples and a way to get versioned artefacts from somewhere.
Thanks in advance.

@fcabestre take a look in maven, you will find version 1.0.1 of this library.
I too would like a simple example just to get me started. Any chance of that @shevek please.

Thank you @philbaxter. I have found the artefacts meanwhile :).

no provide example？

How to use this library? Any examples, unit tests would be helpful.

It has been a while, but, if anybody is interested, we have just published our ipmi library, it has been built with scala, but any contribution of java bindings would be appreciated. You can find it at https://github.com/CycloneTechnology/ChaMP you will find examples of use with scala in the project directories.

how to use it？Who can provide a example？3ks.


[Pager] Issues with Hilt enableAggregatingTask feature

Describe the bug
This is a compilation bug with Hilt version 2.37 and accompanist 1.12.0.
In my app.gradle file I enabled
hilt {
    enableAggregatingTask = true
}

To Reproduce
Steps to reproduce the behavior:

Use hilt version 2.37
Add accompanist "com.google.accompanist:accompanist-pager:0.12.0"
Sync Gradle
Try to launch the app

Expected behavior
Everything would build and the app would launch normally
Screenshots?
If applicable, add screenshots to help explain your problem.
Environment:

Android OS version: [Android 11.0]
Device: [Emulator Google Pixel 5]
Accompanist version: [0.12.0]

Additional context
Stacktrace:
Execution failed for task ':app:hiltAggregateDepsDevDebug'.
> Could not resolve all files for configuration ':app:hiltCompileOnlyDevDebug'.
   > Could not resolve io.github.aakira:napier:1.4.1.
     Required by:
         project :app > com.google.accompanist:accompanist-pager:0.12.0
      > The consumer was configured to find attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug', attribute 'version' with value 'dev'. However we cannot choose between the following variants of io.github.aakira:napier:1.4.1:
          - commonMainMetadataElements-published
          - debugApiElements-published
          - debugRuntimeElements-published
          - iosArm64ApiElements-published
          - iosArm64MetadataElements-published
          - iosX64ApiElements-published
          - iosX64MetadataElements-published
          - jsApiElements-published
          - jsRuntimeElements-published
          - jvmApiElements-published
          - jvmRuntimeElements-published
          - metadataApiElements-published
        All of them match the consumer attributes:
          - Variant 'commonMainMetadataElements-published' capability io.github.aakira:napier:1.4.1:
              - Unmatched attributes:
                  - Doesn't say anything about com.android.build.api.attributes.BuildTypeAttr (required 'debug')
                  - Provides org.gradle.status 'release' but the consumer didn't ask for it
                  - Provides org.gradle.usage 'kotlin-api' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.platform.type 'common' but the consumer didn't ask for it
                  - Doesn't say anything about version (required 'dev')
          - Variant 'debugApiElements-published' capability io.github.aakira:napier:1.4.1 declares attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug':
              - Unmatched attributes:
                  - Provides com.android.build.api.attributes.VariantAttr 'debug' but the consumer didn't ask for it
                  - Provides org.gradle.status 'release' but the consumer didn't ask for it
                  - Provides org.gradle.usage 'java-api' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.platform.type 'androidJvm' but the consumer didn't ask for it
                  - Doesn't say anything about version (required 'dev')
          - Variant 'debugRuntimeElements-published' capability io.github.aakira:napier:1.4.1 declares attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug':
              - Unmatched attributes:
                  - Provides com.android.build.api.attributes.VariantAttr 'debug' but the consumer didn't ask for it
                  - Provides org.gradle.status 'release' but the consumer didn't ask for it
                  - Provides org.gradle.usage 'java-runtime' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.platform.type 'androidJvm' but the consumer didn't ask for it
                  - Doesn't say anything about version (required 'dev')
          - Variant 'iosArm64ApiElements-published' capability io.github.aakira:napier:1.4.1:
              - Unmatched attributes:
                  - Provides artifactType 'org.jetbrains.kotlin.klib' but the consumer didn't ask for it
                  - Doesn't say anything about com.android.build.api.attributes.BuildTypeAttr (required 'debug')
                  - Provides org.gradle.status 'release' but the consumer didn't ask for it
                  - Provides org.gradle.usage 'kotlin-api' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.native.target 'ios_arm64' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.platform.type 'native' but the consumer didn't ask for it
                  - Doesn't say anything about version (required 'dev')
          - Variant 'iosArm64MetadataElements-published' capability io.github.aakira:napier:1.4.1:
              - Unmatched attributes:
                  - Provides artifactType 'org.jetbrains.kotlin.klib' but the consumer didn't ask for it
                  - Doesn't say anything about com.android.build.api.attributes.BuildTypeAttr (required 'debug')
                  - Provides org.gradle.status 'release' but the consumer didn't ask for it
                  - Provides org.gradle.usage 'kotlin-metadata' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.native.target 'ios_arm64' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.platform.type 'native' but the consumer didn't ask for it
                  - Doesn't say anything about version (required 'dev')
          - Variant 'iosX64ApiElements-published' capability io.github.aakira:napier:1.4.1:
              - Unmatched attributes:
                  - Provides artifactType 'org.jetbrains.kotlin.klib' but the consumer didn't ask for it
                  - Doesn't say anything about com.android.build.api.attributes.BuildTypeAttr (required 'debug')
                  - Provides org.gradle.status 'release' but the consumer didn't ask for it
                  - Provides org.gradle.usage 'kotlin-api' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.native.target 'ios_x64' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.platform.type 'native' but the consumer didn't ask for it
                  - Doesn't say anything about version (required 'dev')
          - Variant 'iosX64MetadataElements-published' capability io.github.aakira:napier:1.4.1:
              - Unmatched attributes:
                  - Provides artifactType 'org.jetbrains.kotlin.klib' but the consumer didn't ask for it
                  - Doesn't say anything about com.android.build.api.attributes.BuildTypeAttr (required 'debug')
                  - Provides org.gradle.status 'release' but the consumer didn't ask for it
                  - Provides org.gradle.usage 'kotlin-metadata' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.native.target 'ios_x64' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.platform.type 'native' but the consumer didn't ask for it
                  - Doesn't say anything about version (required 'dev')
          - Variant 'jsApiElements-published' capability io.github.aakira:napier:1.4.1:
              - Unmatched attributes:
                  - Doesn't say anything about com.android.build.api.attributes.BuildTypeAttr (required 'debug')
                  - Provides org.gradle.status 'release' but the consumer didn't ask for it
                  - Provides org.gradle.usage 'kotlin-api' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.js.compiler 'legacy' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.platform.type 'js' but the consumer didn't ask for it
                  - Doesn't say anything about version (required 'dev')
          - Variant 'jsRuntimeElements-published' capability io.github.aakira:napier:1.4.1:
              - Unmatched attributes:
                  - Doesn't say anything about com.android.build.api.attributes.BuildTypeAttr (required 'debug')
                  - Provides org.gradle.status 'release' but the consumer didn't ask for it
                  - Provides org.gradle.usage 'kotlin-runtime' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.js.compiler 'legacy' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.platform.type 'js' but the consumer didn't ask for it
                  - Doesn't say anything about version (required 'dev')
          - Variant 'jvmApiElements-published' capability io.github.aakira:napier:1.4.1:
              - Unmatched attributes:
                  - Doesn't say anything about com.android.build.api.attributes.BuildTypeAttr (required 'debug')
                  - Provides org.gradle.libraryelements 'jar' but the consumer didn't ask for it
                  - Provides org.gradle.status 'release' but the consumer didn't ask for it
                  - Provides org.gradle.usage 'java-api' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.platform.type 'jvm' but the consumer didn't ask for it
                  - Doesn't say anything about version (required 'dev')
          - Variant 'jvmRuntimeElements-published' capability io.github.aakira:napier:1.4.1:
              - Unmatched attributes:
                  - Doesn't say anything about com.android.build.api.attributes.BuildTypeAttr (required 'debug')
                  - Provides org.gradle.libraryelements 'jar' but the consumer didn't ask for it
                  - Provides org.gradle.status 'release' but the consumer didn't ask for it
                  - Provides org.gradle.usage 'java-runtime' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.platform.type 'jvm' but the consumer didn't ask for it
                  - Doesn't say anything about version (required 'dev')
          - Variant 'metadataApiElements-published' capability io.github.aakira:napier:1.4.1:
              - Unmatched attributes:
                  - Doesn't say anything about com.android.build.api.attributes.BuildTypeAttr (required 'debug')
                  - Provides org.gradle.status 'release' but the consumer didn't ask for it
                  - Provides org.gradle.usage 'kotlin-metadata' but the consumer didn't ask for it
                  - Provides org.jetbrains.kotlin.platform.type 'common' but the consumer didn't ask for it
                  - Doesn't say anything about version (required 'dev')
        The following variants were also considered but didn't match the requested attributes:
          - Variant 'releaseApiElements-published' capability io.github.aakira:napier:1.4.1:
              - Incompatible because this component declares attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug'
              - Other compatible attribute:
                  - Doesn't say anything about version (required 'dev')
          - Variant 'releaseRuntimeElements-published' capability io.github.aakira:napier:1.4.1:
              - Incompatible because this component declares attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug'
              - Other compatible attribute:
                  - Doesn't say anything about version (required 'dev')`

Looks like Hilt's plug-in doesn't support handling KMP dependencies. (Napier is KMP). Please raise a bug over on the Dagger tracker.


fix: allow leveldb storage to start twice

We are hitting a problem in Ahau tests where we start two of our peers, each trues to start  an agent (in a different path) but this global variable says "oh, there's already another db there!" and then it crashes the tests.
The change in here is more a map-pin than actual solution. I think it's fine to let levelDB handle it's own lockfile stuff?

oh no, it needs to be an instance variable, not a global variable I think

oh no, it needs to be an instance variable, not a global variable I think

I remember seeing some code in DexieEncrypted plugin to make it multi instance support. we can check that no worries

@mixmix I've pushed a very very small change to just simplify.
Can you try creating the storage by passing level db instance and not dbPath?
createLevelDBStorage({
    level: [[your LEVEL instance]]
  })

That should potentially let you have multiple different instances. Need to test though.

I have pushed one more change improving pluto for levelDB by using a MAP when needed.
Have also added 1 test scenario validating that I can create and work with 2 instances in the same thread without issues and checked the data is completely independent.
All working!!

:tada: This PR is included in version 1.0.23 :tada:
The release is available on<EMAIL_ADDRESS>Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.8 :tada:
The release is available on<EMAIL_ADDRESS>Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on<EMAIL_ADDRESS>Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.0 :tada:
The release is available on<EMAIL_ADDRESS>Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.0 :tada:
The release is available on<EMAIL_ADDRESS>Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on<EMAIL_ADDRESS>Your semantic-release bot :package::rocket:


Chore: Update Play store and F-Droid links in README.md

Fixes #1349
Checklist:

[x] I have checked for PMD and check-style issues
[x] I have read the Contribution & Best practices Guide and my PR follows them.
[x] My branch is up-to-date with the Upstream development branch.

@iamareebjamal  pls review

Please use lower case tags like chore from now on

Oops 😅


[CHALLENGE SUBMISSION]

Please provide the following information for your submission:
What is your name (First, Last):
Wesley Cabus
Where is your GitHub Repo (with your challenge solution):
https://github.com/wcabus/ColdStart-Challenge-2021
What Challenge is this for (challenge number between 1 and 6): 5
(Optional) Anything else we should know? e.g., language used, location, blog post?
The swagger json and REST endpoint can be found here: http://0a4d4593-130e-41da-ab8c-cec8631457d8.westeurope.azurecontainer.io/swagger.json

Thanks for participating in our coding challenges Wesley ❤! To claim your Raspberry PI device, please DM me on Twitter to get the link for providing your shipping details. https://twitter.com/nicktrog


Update assertRevert to support buidler dev tool

Note that the current test setup is not using the buidlerevm yet because a few tests broke when we assert with our own assertRevert helper as explained here: https://github.com/aragon/contract-helpers/pull/53#discussion_r467152817.

Thanks for the review, I'll add the changes into a new PR. You are right the solidity-coverage condition is no longer relevant.


aspirate generate --output-format compose  error

When I use “aspirate generate --output-format compose“, the following error occurs
Error executing action 'GenerateDockerComposeManifestAction':
System.NullReferenceException: Object reference not set to an instance of an object.
at void Aspirate.Commands.Actions.Manifests.GenerateDockerComposeManifestAction.ProcessIndividualComponent(KeyValuePair<string, Resource> resource, List services) in
/home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Commands/Actions/Manifests/GenerateDockerComposeManifestAction.cs:109
at Task Aspirate.Commands.Actions.Manifests.GenerateDockerComposeManifestAction.ExecuteAsync() in /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Commands/Actions/Manifests/
GenerateDockerComposeManifestAction.cs:30
at async Task Aspirate.Commands.Actions.ActionExecutor.ExecuteCommandsAsync() in /home/runner/work/aspirational-manifests/aspirational-manifests/src/Aspirate.Commands/Actions/ActionExecutor.cs:65

I'm using Dapr in my project and it works fine if it doesn't include it


15/chat ui and functional interaction

[x] Remove old POC UI and codes
[x] Structure a bit of webpack and framework file structure for better coding experience :)
[x] Integrate bunch of libraries (slider, bootstrap, resource, localstorage etc.)
[x] Create basic UI for chat component without any fancy layout since our UI mockup is not yet ready
[x] Create logic for the chat component
[x] Integrate with backend service with rest calls, and handle/bind all the data on frontend
[ ] Test the functionality and integration
[ ] Create unit test

Can you post screenshots whenever there is a UI change? It is easier to code review

There is no theme just a functional component. By the time the UI/theme is ready we are need to do is assemble them on the page and css it.

Initial UI on PC

Initial UI on iPad

Initial UI on IPhone


[Question] on iOS should getToken or getAPNSToken be used?

if we are using FCM for iOS, should getToken or getAPNSToken be used?

getToken works for me. Seems you don’t need APNSToken, But you have to remember to make sure in your info.plist this is there set to no:

On 02 Jun 2020, at 08:03, Gaurav Chandra<EMAIL_ADDRESS>wrote:
if we are using FCM for iOS, should getToken or getAPNSToken be used?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/andrehtissot/cordova-plugin-fcm-with-dependecy-updated/issues/87, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2GQA6U542MS7GCWWJBXPTRUSI3ZANCNFSM4NQNCQNQ.

@RichardBoyder what is the setting which needs to be set to no?

FirebaseAppDelegateProxyEnabled.  Boolean.    No
That’s in your info.plist .
The plugin actually should do that for you automatically so if installed in Xcode you should see that.

On 02 Jun 2020, at 08:38, Gaurav Chandra<EMAIL_ADDRESS>wrote:
@RichardBoyder https://github.com/RichardBoyder what is the setting which needs to be set to no?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/andrehtissot/cordova-plugin-fcm-with-dependecy-updated/issues/87#issuecomment-637311022, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2GQA7CIHIFSGAAV2U7XZTRUSM7FANCNFSM4NQNCQNQ.

getToken() retrieves the Firebase Token. getAPNSToken() retrieves the Apple Push Notification Service token. Depending on your 3rd party integrations you might need one or the the other.
FirebaseAppDelegateProxyEnabled should be disabled as default. Since the app itself is handling the firebase setup itself, as proxying was too unreliable.
This plugin should set FirebaseAppDelegateProxyEnabled as False on install, hence the log message.


Use 'latest' as VERSION on master.

The build information of the binary file will be accurate when anyone
builds from master.
Also guide user to release page on GitHub as source of truth.

This PR will resolve #128.

@jkohen Please take a look on the latest change. VERSION is not mentioned in the Makefile, so I added the documentation in the release script on why we update VERSION file.


Add email template

Here's a working version that needed a little polishing.


[music3] Load -> Temporary Import

Will be rebased with the other music3 PR.
Source PR https://github.com/Inria-Asclepios/medInria-public/pull/428
Commit https://github.com/medInria/medInria-public/commit/bfd6c2ab24d1dc9158aeda3d20d76e4b59f775ea
The Load button/action in the File System tab in Browser are not comprehensible for users, so:

"Load" button becomes "Temporary Import" button
"View" button has a better explanation tooltip

:m:

Je valide mais attentions il faut que la PR des log files soit merger et surtout corriger (Attention utf8/utf16).

PR rebased @Florent2305


Barback should eagerly report that an asset isn't found if all transformers are declaring

 Issue by nex3
Originally opened as dart-lang/sdk#18226

If it can use declaring transformers' output to prove that no transformers will emit a given output, barback shouldn't block [getAssetNode] on waiting for all transformers to finish.

 Comment by nex3

Fixed in dart-lang/sdk@602dbd59c639a1467f88fc48c944b7a44d07c6aa.

Added Fixed label.

 Comment by nex3

Added Started label.


[Addition]: [Request MOC investigation] Kerlink self-witnessing only clusters

Hotspot b58 Addresses
11pDVihnDjmxVVigsZD6rtaSgPdweVepenR9kc4j4Sv5NxjhHjs
112WT8JgyUiixgwvEmgAFZgr5ssag9v3NzgC6fa8feHqCKoJuA8U
112ACYcFDyjU6TmczSkwa6LwDXdft4d4yftWsBCs7CCGfp9p7tzT
11cNCTrh4pwGHWucsg4foXbphe72WwiFzid2bnJLswuKaSqjFHy
1133PuoKLurwxDfn4rFsMPARSwiWTGgKyfm6GtyKEjTSyMFzf4z
11QcsMvfu4M7ZDYNL3aXDiT2S7PdS1CQuSdMuvViDNRZugfbjga
112J4PXfZ4wA4qYWKVG9V7HAtoPbhA6M5QLQdg3bnKWaxXCuZLk6
112QXsXERfPBq5WN1zauAndYhAk8mxr1ifETddcaQbGhLMDtMn1E
112bHH5jHoTL94ABtgJsqc7viQ3QcsQoweCwsWGHVjiVd8Yo7iFJ
11VRFhECgQzxYN2cAmsEXdjs2o4az12kbb3P5FiiH9EGLMLuJ68
112PGRXG9i3nN76X9wkzyK9tYU3FVLexBE6eb2PtMp1J1d5CE29t
Discord Handle
No response
Reason(s)
too good signal
Half witnessing are invalid (signal is too good)
Hotspots only witnessing each other

Theses hotspot does not witnessing each others only :
Extract from personnal tool:

Maker
Number of witnessed

Kerlink
10

Nebra Ltd
6

RAKwireless
8

SenseCAP
3

RisingHF
1

None
1

PantherX
1

Browan/MerryIoT
1

Bobcat
2

Hotspots are placed at 10/20/30m height, seems to be ISP operator (pic from the first )!
![image](https://user-images.githubusercontent.com/343732/163980045-2f214ca4-a38b-40ac-8515-5915b7ba1f7c.png)
Did an analysis must be done on all of them ?


Add Function functionality is missing in Azure functions extension of VS Code

This is from the StackOverflow user and after reproducing from our end we faced the same issue after installing the latest update.
https://stackoverflow.com/questions/73271028/not-able-to-add-new-azure-function-in-vscode
Steps:

Install/Update the latest VS Code release July 2022 (version 1.70).
Navigate to Azure Extension.
Hover to Workspace.

We cannot able find the Add new function (+ icon) after installing or updating to the latest July 2022 (version 1.70) in VS Code.

Hi @SwethaKandikonda-MT
Thanks for filing this issue. We have the same issue filed here: https://github.com/microsoft/vscode-azureresourcegroups/issues/330
Unfortunately, the only current workarounds is to downgrade VS Code or uninstall either the Azure App Service or Functions extension as having both is what is causing this issue.

Having the same issue on my side, uninstalling Azure App Service did the trick as work around for now.
It's acceptable since I don't need that now but I hope they can fix this bug soon and release an general update for vscode.

Fixed in https://github.com/microsoft/vscode/releases/tag/1.70.2


BUG: onyo mving an asset into a non-existent dir results in incorrect message

The source file exists and the destination dir doesn't. Yet the error message says that the source is not an inventory directory.
(onyo) aqw@hrududu in /tmp/yope on git:master
❱ onyo mv dp/Alex\ Waite/keyboard_wasd_cool.faux does_not_exist/
ERROR: Not an inventory directory: /tmp/yope/dp/Alex Waite/keyboard_wasd_cool.faux

I found an issue that I think is related:
When doing: onyo mv <asset A> <non-existing-dir> it gives a different error message compared to
onyo mv <asset A> <asset A> <non-existing-dir> or onyo mv <asset A> <asset B> <non-existing-dir>:
(onyo) tkadelka@bnbmac73 in ~/none-existing-folder on git:master
❱ onyo mv ethics/Achilles\ Book/laptop_microsoft_surface.oq782j asdf                       1 !
ERROR: Not an inventory directory: /Users/tkadelka/none-existing-folder/ethics/Achilles Book/laptop_microsoft_surface.oq782j

(onyo) tkadelka@bnbmac73 in ~/none-existing-folder on git:master
❱ onyo mv ethics/Achilles\ Book/laptop_microsoft_surface.oq782j ethics/Achilles\ Book/laptop_microsoft_surface.oq782j asdf
ERROR: Cannot rename multiple sources.

(onyo) tkadelka@bnbmac73 in ~/none-existing-folder on git:master
❱ onyo mv ethics/Achilles\ Book/laptop_microsoft_surface.oq782j ethics/Theo\ Turtle/laptop_lenovo_thinkpad.owh8e2 asdf
ERROR: Cannot rename multiple sources.

There are multiple other issues related to onyo mv and its messages (e.g. #442); but I think my examples are closest connected to this one.


Added ipynb as example for shake generation.

June 11, 2023 ape

@Lucky-Armin I don't see any notebook.

I have overlooked the .ipynb file in the commit due to the .gitignore settings....

@Lucky-Armin would you be so kind an clear the output of the notebook.

@97gamjak I see, we have an error in the Pylint action.

@galjos @Lucky-Armin
Please note for the next time this shouldn't be a merge to main... should be included in dev - this is not worth a new tag - therefore, merging to dev

@97gamjak I see we have an error in the Pylint action.

Yes, I know this error. It only appears on pullnrequests from forked branches. Probaboy because the bot has nonwrite permissions on such repos.

closes #94


Support Empty{SVector}

Codecov Report

Merging #72 into master will decrease coverage by 0.23%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #72      +/-   ##
==========================================
- Coverage    92.9%   92.66%   -0.24%
==========================================
  Files          19       19
  Lines         296      300       +4
==========================================
+ Hits          275      278       +3
- Misses         21       22       +1

Impacted Files
Coverage Δ

src/NoBang/emptycontainers.jl
100% <ø> (ø)
:arrow_up:

src/NoBang/singletonof.jl
100% <ø> (ø)
:arrow_up:

src/NoBang/staticarrays.jl
100% <100%> (ø)
:arrow_up:

src/NoBang/base.jl
94.44% <0%> (-1.39%)
:arrow_down:

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 ac190bc...674c613. Read the comment docs.


Executing example with master=yarn gives CUDA_ERROR_NO_DEVICE error

I am trying to submit an example from edge node which doesn't have GPU against yarn cluster with datanodes having GPUS like this:
spark-submit --master=yarn --jars gpu-enabler/target/gpu-enabler_2.11-1.0.0.jar --class com.ibm.gpuenabler.GpuEnablerCodegen examples/target/gpu-enabler-examples_2.11-1.0.0.jar
I am getting this error:
Caused by: org.apache.spark.SparkException: Could not initialize CUDA because of unknown reason
	at com.ibm.gpuenabler.CUDAManager.<init>(CUDAManager.scala:53)
	at com.ibm.gpuenabler.GPUSparkEnv.<init>(GPUSparkEnv.scala:42)
	at com.ibm.gpuenabler.GPUSparkEnv$.initalize(GPUSparkEnv.scala:58)
	at com.ibm.gpuenabler.GPUSparkEnv$.get(GPUSparkEnv.scala:66)
	at com.ibm.gpuenabler.CUDACodeGenerator$.<init>(CUDACodeGenerator.scala:207)
	at com.ibm.gpuenabler.CUDACodeGenerator$.<clinit>(CUDACodeGenerator.scala)
	... 12 more
Caused by: jcuda.CudaException: CUDA_ERROR_NO_DEVICE
	at jcuda.driver.JCudaDriver.checkResult(JCudaDriver.java:312)
	at jcuda.driver.JCudaDriver.cuInit(JCudaDriver.java:439)
	at com.ibm.gpuenabler.CUDAManager.<init>(CUDAManager.scala:43)

I understand the error is because there no GPU on the edge node. So my questions are:

Does GPUEnabler support submitting jobs with MASTER=yarn to run on GPU enabled cluster nodes? Or it only supports submission against one local node with GPU?
What should be the workflow to submit jobs in my configuration: edge node w.o GPU and cluster nodes with GPUs?
What jCuda library I have to use in Spark (I see many after successful build of GPUEnabler):

./mavenized-jcuda/repo/jcuda/jcuda/0.6.0/jcuda-0.6.0.jar
./mavenized-jcuda/repo/jcuda/jcuda/0.6.0RC/jcuda-0.6.0RC.jar
./mavenized-jcuda/repo/jcuda/jcuda/0.7.5/jcuda-0.7.5.jar
./mavenized-jcuda/repo/jcuda/jcuda/0.7.0a/jcuda-0.7.0a.jar
./mavenized-jcuda/repo/jcuda/jcuda/0.5.5/jcuda-0.5.5.jar
./mavenized-jcuda/repo/jcuda/jcuda/0.6.5/jcuda-0.6.5.jar
./mavenized-jcuda/repo/jcuda/jcuda/0.7.5b/jcuda-0.7.5b.jar
./mavenized-jcuda/repo/jcuda/jcuda/0.5.0/jcuda-0.5.0.jar
./mavenized-jcuda/target/mavenized-jcuda-0.1.2.jar

Thanks!

About your problems:
Does GPUEnabler support submitting jobs with MASTER=yarn to run on GPU enabled cluster nodes? Or it only supports submission against one local node with GPU?
What should be the workflow to submit jobs in my configuration: edge node w.o GPU and cluster nodes with GPUs?
I'm having the same issue , did you find any answer?
thanks

I couldn not find solution for this. At some point gpu support will be implemented in spark anyway.
Sent from my T-Mobile 4G LTE Device
-------- Original message --------From: IslandGod<EMAIL_ADDRESS>Date: 4/5/17  4:12 AM  (GMT-05:00) To: IBMSparkGPU/GPUEnabler<EMAIL_ADDRESS>Cc: dimon777<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [IBMSparkGPU/GPUEnabler] Executing example with master=yarn gives
  CUDA_ERROR_NO_DEVICE error (#40)
About your problems:
Does GPUEnabler support submitting jobs with MASTER=yarn to run on GPU enabled cluster nodes? Or it only supports submission against one local node with GPU?
What should be the workflow to submit jobs in my configuration: edge node w.o GPU and cluster nodes with GPUs?
I'm having the same issue , did you find any answer?
thanks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/IBMSparkGPU/GPUEnabler","title":"IBMSparkGPU/GPUEnabler","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/IBMSparkGPU/GPUEnabler"}},"updates":{"snippets":[{"icon":"PERSON","message":"@IslandGod in #40: About your problems:\r\nDoes GPUEnabler support submitting jobs with MASTER=yarn to run on GPU enabled cluster nodes? Or it only supports submission against one local node with GPU?\r\nWhat should be the workflow to submit jobs in my configuration: edge node w.o GPU and cluster nodes with GPUs?\r\n\r\nI'm having the same issue , did you find any answer? \r\nthanks\r\n"}],"action":{"name":"View Issue","url":"https://github.com/IBMSparkGPU/GPUEnabler/issues/40#issuecomment-291787193"}}}

Whatever I use ./sbin/start-all.sh to active my clusters or not,  I can use the same cmd like:
spark-submit --master=spark://<IP_ADDRESS>:7077 --jars gpu-enabler/target/gpu-enabler_2.11-1.0.0.jar --class com.ibm.gpuenabler.GpuEnablerCodegen examples/target/gpu-enabler-examples_2.11-1.0.0.jar
to get the some correct answer.
So I wonder, does GPUEnabler really submit to clusters, or it just run locally?
all info will help, thanks

It should work with local or standalone-cluster. However, we have not tested with yarn.

"Whatever I use ./sbin/start-all.sh to active my clusters or not, I can use the same cmd like:"
start-all.sh simply starts hdfs and yarn stack in Hadoop, and Spark is decoupled from them. You can start standalone cluster and observe GPU status via nvidia-smi tool to judge if they use multi node GPUs or not. This can be evident from GPU memory consumption and temperature values.


component suggestion {mini-toast}

The toast component in the Shadcn UI is generally satisfactory, but on certain occasions, it might feel excessive for minor actions. It would be beneficial to have a mini toast component specifically designed for smaller tasks, such as indicating when a product has been added or deleted. These types of actions don't warrant the full-scale toast, and a more compact alternative would be appropriate.

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.

A minimalistic toast in the same vein of react-hot-toast would indeed be helpful.

@Suksham-sharma @PieterT2000 does sonner work?

Yes , it's good . It wasn't there earlier when i was exploring . So I thought I could add it . Thanks for letting me know .


Ability to make certain headers optional

Hey first of all, thanks for creating this library! It works very well so far in my testing and saves a ton of time!
To explain the title further, for context, I have an openapi json (not controlled by me) which specifies some required headers for every request. Each request requires a custom header to be specified and its the same value across all requests. To make things easier I decided I would set the header globally in the requestFn much like you do for the 'Authorization' header in this docs page:
https://openapi-qraft.github.io/openapi-qraft/docs/hooks/qraft-context
The issue is, since the header is specified as required in the parameters of the operation in the openapi json the generated types for the hooks also require this header.
I am wondering if its possible to somehow add an option when generating the client hook typings to make a certain header optional?
As a work around I am aware I could pre-process the schema to change the header from required to optional but I believe this may be useful if theres an accepted way to handle this situation for users of this library.
Thanks,

Ah nice, I think I understand now how the library expects you to handle this.
On the cli it appears we can set the --operation-generics-import-path option to import from our own ServiceOperationMutation / ServiceOperationQuery types allowing developers to perform any required modifications to the types.
Am I correct in this being the accepted way to achieve what I want to achieve?

@TomCaserta, you're right about wanting to set certain parameters in advance. However, redefining ServiceOperationQuery won't help here.
The problem is that the parameters will still reside in schema.d.ts, which is generated by openapi-typescript, and they will constantly get in the way.
For this reason, I decided to generate schema.d.ts using @openapi-qraft/openapi-typescript-plugin as a thin wrapper over openapi-typescript.
This allows to add functionality like support for the --operation-predefined-parameter  option 🆕
This feature is now available in<EMAIL_ADDRESS>If you can't wait, you can try<EMAIL_ADDRESS>(next betas break support for Next.js Server Actions temporary). Use the -h option to display the help.
An example of using --operation-predefined-parameter is here. This option allows you to make the specified parameters optional. For example,
--operation-predefined-parameters `/**:header.Authorization`

makes the Authorization header optional for all requests:
// schema.d.ts
parameters: {
  query?: never;
  header?: {
    Authorization?: string;
  };
  path: {
    approval_request_id: string;
  };
};

This automatically simplifies working with parameter types in the code, and consequently, Qraft won't require them to be passed in the request.
You've already figured out how to add headers, but I would also recommend implementing a check to ensure they are needed for the request, like here.
A crucial point: if even one endpoint does not contain header.Authorization in its parameters, such as /public-profile, you must specify it as an exception:
--operation-predefined-parameters `/**,!/public-profile:header.Authorization`

In future versions, there will be automatic resolution of which predefined parameter is needed for which request, so you won't need to write regular expressions or worry about headers ending up where they shouldn't be.


DatePickerInput not styled

What package has an issue
@mantine/core
Describe the bug
The DatePickerInput popout isn't (or is only minimally) styled.
I'm using NextJs, and I recreated the issue in the next-app-min-template to check that it wasn't anything else I'd done. I used the DatePickerInput code from the manual page.

What version of @mantine/* page do you have in package.json? (Note that all @mantine/* packages must have the same version in order to work correctly)
7.0.0-beta.0
If possible, please include a link to a codesandbox with the reproduced problem
No response
Do you know how to fix the issue
No
Are you willing to participate in fixing this issue and create a pull request with the fix
No
Possible fix
No response

You did not import @mantine/dates/styles.css

Thanks a lot, how dumb of me!


Add support for IntesisHome controllable air conditioners

Description:
Added support for IntesisHome controlled air conditioners.
Work in progress, first time submitting a component so please let me know if anything needs changing.
This platform has been in use by a number of testers on https://community.home-assistant.io/t/add-support-for-intesishome-wifi-ac-control/5172 - initially was added as an IntesisHome platform and climate component however combined it into the one climate component.
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
TBC
Example entry for configuration.yaml (if applicable):
climate:
  - platform: intesishome
    username: 'user'
    password: 'pass'

Checklist:
If user exposed functionality or configuration variables are added/changed:

[Y] Documentation added/updated in home-assistant.github.io PR#2925

If the code communicates with devices, web services, or third-party tools:

[Y] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[Y] New dependencies have been added to the REQUIREMENTS variable (example).
[?] New dependencies are only imported inside functions that use them (example).
[Y] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[Y] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Hi @jnimmo,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Hi @jnimmo,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

I'm not sure how to resolve the following issues from Travis - is someone able to kindly advise?
The intesishome variable is designed to be a singleton i.e. one interface back to the IntesisHome API, and then the IntesisAC objects maintain their state from that one intesishome object.
C: 55, 0: Invalid constant name "intesishome" (invalid-name)
C: 61, 4: Invalid constant name "intesishome" (invalid-name)
R:251, 4: Method could be a function (no-self-use)
W: 48, 4: Unused ensure_future imported from asyncio (unused-import)

Suggest you update the description file to include your .io PR.
https://github.com/home-assistant/home-assistant.github.io/pull/2925

@jnimmo any updates on this PR?

Waiting on this PR as well.
@jnimmo Just put in a comment in intesishome.py line 277, lots of deprecation warning

Can be reopen if all comments are addressed


Alert on deprecated controls in Winforms

Fixes
#782
#783

@RussKie FYI, this is the change to alert on deprecated controls, could you review the accuracy of categorizations?

/azp run

/azp run

@sunandabalu Until the maui stuff is worked out, why don't you just skip those tests and @Sweekriti91 can handle that separately so this can get merged it