Profile branch

This PR replaces and addresses the issues with the previous Profile Pr (#68 )
Changes in this PR:

changes occurrences of 'delete profile' to 'delete account' @phreid
Modals close after the information is submitted @phreid
items show up on 'my items' page @imogenem
reset button clears form input @imogenem

Thanks for your help guys!

In this branch, the edit profile form isn't pre-filled with the user's data.
profileUpdate branch:
EditUserForm.jsx

const [username, setUsername] = useState(currentUser.username)
const [password, setPassword] = useState(currentUser.password)
const [bio, setBio] = useState(currentUser.bio)
const [email, setEmail] = useState(currentUser.email)
const [location, setLocation] = useState(currentUser.location)

profileBranch branch:
ProfilePage.jsx

const [username, setUsername] = useState('')
const [password, setPassword] = useState('')
const [bio, setBio] = useState('')
const [email, setEmail] = useState('')
const [location, setLocation] = useState('')

And if the form is submitted with an empty field, it overwrites what's in the database with an empty field.

@phreid I updated the edit user form to not accept any blank value so that the DB isn't overwritten. I also made sure that the Edit User form is pre-filled with the user's data.
To make my code cleaner, I abstracted out both the Edit User and Delete Account forms into different components. The downside of this is that the EditUserForm will close only if:

the cross is clicked at the top right
the user clicks outside the modal
I don't think this is a major issue, and I can take it up in the next sprint.

Also cleaned up the appearance of the profile page and respective modals.
This PR doesn't have any conflicts with dev, and it seems good to go. Waiting on approval to merge.

@imogenem  yep, that's what I mentioned (I'll edit my comment to make it clear). As of now, the profile modal will not close when the submit button is clicked. It will only close when the cross is clicked (on the top right) or when you click outside the modal. Because the modal show logic is on the profile component and the actual submit form logic in the edit user component, the submit button is giving me a hard time tying in with the close modal logic. I will fix this in the next sprint.

Not sure what the issue is exactly with closing on submit, but there are working examples in EditCardModal and EditRatingModal in case you haven't seen them.

Yup, I have seen those examples. I was working through them and trying to pass the show and hide parameters accordingly, but because of the way my logic for modals is abstracted right now, it wasn't working as expected. I'll fix this up in the upcoming sprint.


Additional preference: on login, automatically open workspace on file

I would like to be able to automatically open workspaces from files, on login.
My original thought was how annoying it is that I can't keep the console workspace contents alive from session to session.  But opening a separate workspace is probably more useful.

Should be able to open a workspace on a file or not in 3.0.82.

I can't get this to work in 3.0.82.
This is my prefs file:
autocommitEnabled: false
autocompleteEnabled: false
transcriptEnabled: false

openWorkspace: C:\GS\Oscar\testws.gs
openBrowserOnPackage: RowanSample1-Tests

the file exists:

But on login, it opens the PB, but not the workspace.

Very odd. Full paths work for me. There are no spaces in your path (which I realize probably won't work as currently implemented).  If you move testws.gs to the working directory (where the .exe is) does it open?  Does a nil open a blank workspace ok?

This file is in the same dir as the exe, so presumably working directory; and no, nil does not open a blank workspace either.

Very odd.  Are you sure that the preferences file that opens the workspace is called Jadeite.prefs and is in the same directory as the .exe?

Same file it's always been - and it does opens the Project Browser, and set other options. You can look at it in person tomorrow...

Think the problem is that the openWorkspace: method in JadeitePreferences was getting stripped out of the runtime. Fixed in 3.0.83.

working nicely in 3.0.83


Run only on electron

maybe good to look this later
https://github.com/arturadib/node-qt
https://github.com/arturadib/node-five

:/
Maybe we nee to go to electron:
https://github.com/arturadib/node-qt/issues/39#issuecomment-241583056

https://github.com/panther-js/toskeiraspace#how-to-run


FYPO:0005188

I selected
FYPO:0000712
and FYPO:0005188 was suggested as a child term

fixed the logical def for FYPO:0000712
edit file: 347065c800c0106d0a95ea0cd89fcd3609c72a57
release: 3414f9f3492b36c76acc37fb2192e78938dc2f17


factorio-updater isn't updating old server version

I have a local isntallation of the factorio headless server 0.13.20 in /home/jan/factorio/bin/x64/factorio
Thatfor I run python3 update_factorio.py -a /home/jan/factorio/bin/x64/factorio
But that gives a return of
No updates available for version 0.13.20 (latest stable is 0.14.23). Did you want `--experimental`?

It doesn't update the server and it doesn't even seem to recognize that there is a newer version, even though it displays just that. What's the problem here?

The problem is that 0.13.19 and 0.13.20 are dead-ends for headless servers* (no updates exist to go from them to the 0.14 series). If you look at https://updater.factorio.com/get-available-versions?apiVersion=2, you will see there is no "from": "0.13.20" to anything, and that the only "from": "0.13.19" has "to": "0.13.20". From 0.13.18 you can go to 0.13.19 or to 0.14.0.
I'm sorry to say, you're going to have to download the whole thing**. Try:

wget -O factorio-headless-0.14.23.tar.gz 'https://www.factorio.com/get-download/0.14.23/headless/linux64' for stable, or
wget -O factorio-headless-0.15.30.tar.gz 'https://www.factorio.com/get-download/0.15.30/headless/linux64' for experimental.

Or try other versions from https://www.factorio.com/download-headless, of course.

* For regular (i.e., non-headless), there are updates from 0.13.20 to 0.14.5. This, of course, doesn't help us.
** Actually, since you're going so many versions forward, you're saving bandwidth -- the entire set of 0.14.0 to .23 is 223 MB, whereas the 0.14.23 headless download is only 22 MB.

Hmm. Maybe I could detect this case and change the error to say something like "can't reach latest stable, which is 0.14.23".

Would my command auto-update it afterwards? I mean would it download newer version and automatically apply them?

It certainly should. You may want to add -D for "delete after apply" and -x for "experimental"; my update command is python3 ~/src/factorio-updater/update_factorio.py -xDa ./bin/x64/factorio (while in the factorio root folder, obviously).

alright, thanks


ci: add v3 release (#53)

Cherry pick the commit from https://github.com/amplitude/amplitude-js-gtm/pull/53 as Github doesn't show actions from branches other than main.

Should we remove it from the feature branch? Does the github action ever show on the sub branch?

@yuhao900914 let's remove publish-v3.yml in another PR as it should merge into v3.x.

Does the github action ever show on the sub branch?
https://stackoverflow.com/a/77161850/24248957


Fix a typo for version at example.

As the version is up, the version of example also should be updated.

Current coverage is 88.25%

Merging #58 into master will not affect coverage as of a738283

@@            master     #58   diff @@
======================================
  Files           12      12
  Stmts          613     613
  Branches        82      82
  Methods          0       0
======================================
  Hit            541     541
  Partial          0       0
  Missed          72      72

Review entire Coverage Diff as of a738283

Powered by Codecov. Updated on successful CI builds.

Merged.


Update rust

This PR contains the following updates:

Package
Type
Update
Change

regex
dependencies
minor
1.9 -> 1.10

tokio (source)
dependencies
minor
1.32 -> 1.33

tokio (source)
dev-dependencies
minor
1.32 -> 1.33

Release Notes

rust-lang/regex (regex)
v1.10.1
Compare Source
===================
This is a new patch release with a minor increase in the number of valid
patterns and a broadening of some literal optimizations.
New features:

FEATURE 04f5d7be:
Loosen ASCII-compatible rules such that regexes like (?-u::snowman_with_snow:) are now allowed.

Performance improvements:

PERF 8a8d599f:
Broader the reverse suffix optimization to apply in more cases.

v1.10.0
Compare Source
===================
This is a new minor release of regex that adds support for start and end
word boundary assertions. That is, \< and \>. The minimum supported Rust
version has also been raised to 1.65, which was released about one year ago.
The new word boundary assertions are:

\< or \b{start}: a Unicode start-of-word boundary (\W|\A on the left,
\w on the right).
\> or \b{end}: a Unicode end-of-word boundary (\w on the left, \W|\z
on the right)).
\b{start-half}: half of a Unicode start-of-word boundary (\W|\A on the
left).
\b{end-half}: half of a Unicode end-of-word boundary (\W|\z on the
right).

The \< and \> are GNU extensions to POSIX regexes. They have been added
to the regex crate because they enjoy somewhat broad support in other regex
engines as well (for example, vim). The \b{start} and \b{end} assertions
are aliases for \< and \>, respectively.
The \b{start-half} and \b{end-half} assertions are not found in any
other regex engine (although regex engines with general look-around support
can certainly express them). They were added principally to support the
implementation of word matching in grep programs, where one generally wants to
be a bit more flexible in what is considered a word boundary.
New features:

FEATURE #469:
Add support for \< and \> word boundary assertions.
FEATURE(regex-automata) #1031:
DFAs now have a start_state method that doesn't use an Input.

Performance improvements:

PERF #1051:
Unicode character class operations have been optimized in regex-syntax.
PERF #1090:
Make patterns containing lots of literal characters use less memory.

Bug fixes:

BUG #1046:
Fix a bug that could result in incorrect match spans when using a Unicode word
boundary and searching non-ASCII strings.
BUG(regex-syntax) #1047:
Fix panics that can occur in Ast->Hir translation (not reachable from regex
crate).
BUG(regex-syntax) #1088:
Remove guarantees in the API that connect the u flag with a specific HIR
representation.

regex-automata breaking change release:
This release includes a regex-automata 0.4.0 breaking change release, which
was necessary in order to support the new word boundary assertions. For
example, the Look enum has new variants and the LookSet type now uses u32
instead of u16 to represent a bitset of look-around assertions. These are
overall very minor changes, and most users of regex-automata should be able
to move to 0.4 from 0.3 without any changes at all.
regex-syntax breaking change release:
This release also includes a regex-syntax 0.8.0 breaking change release,
which, like regex-automata, was necessary in order to support the new word
boundary assertions. This release also includes some changes to the Ast
type to reduce heap usage in some cases. If you are using the Ast type
directly, your code may require some minor modifications. Otherwise, users of
regex-syntax 0.7 should be able to migrate to 0.8 without any code changes.
regex-lite release:
The regex-lite 0.1.1 release contains support for the new word boundary
assertions. There are no breaking changes.
v1.9.6
Compare Source
==================
This is a patch release that fixes a panic that can occur when the default
regex size limit is increased to a large number.

BUG aa4e4c71:
Fix a bug where computing the maximum haystack length for the bounded
backtracker could result underflow and thus provoke a panic later in a search
due to a broken invariant.

v1.9.5
Compare Source
==================
This is a patch release that hopefully mostly fixes a performance bug that
occurs when sharing a regex across multiple threads.
Issue #934
explains this in more detail. It is also noted in the crate
documentation.
The bug can appear when sharing a regex across multiple threads simultaneously,
as might be the case when using a regex from a OnceLock, lazy_static or
similar primitive. Usually high contention only results when using many threads
to execute searches on small haystacks.
One can avoid the contention problem entirely through one of two methods.
The first is to use lower level APIs from regex-automata that require passing
state explicitly, such as meta::Regex::search_with.
The second is to clone a regex and send it to other threads explicitly. This
will not use any additional memory usage compared to sharing the regex. The
only downside of this approach is that it may be less convenient, for example,
it won't work with things like OnceLock or lazy_static or once_cell.
With that said, as of this release, the contention performance problems have
been greatly reduced. This was achieved by changing the free-list so that it
was sharded across threads, and that ensuring each sharded mutex occupies a
single cache line to mitigate false sharing. So while contention may still
impact performance in some cases, it should be a lot better now.
Because of the changes to how the free-list works, please report any issues you
find with this release. That not only includes search time regressions but also
significant regressions in memory usage. Reporting improvements is also welcome
as well! If possible, provide a reproduction.
Bug fixes:

BUG #934:
Fix a performance bug where high contention on a single regex led to massive
slow downs.

v1.9.4
Compare Source
==================
This is a patch release that fixes a bug where RegexSet::is_match(..) could
incorrectly return false (even when RegexSet::matches(..).matched_any()
returns true).
Bug fixes:

BUG #1070:
Fix a bug where a prefilter was incorrectly configured for a RegexSet.

v1.9.3
Compare Source
==================
This is a patch release that fixes a bug where some searches could result in
incorrect match offsets being reported. It is difficult to characterize the
types of regexes susceptible to this bug. They generally involve patterns
that contain no prefix or suffix literals, but have an inner literal along with
a regex prefix that can conditionally match.
Bug fixes:

BUG #1060:
Fix a bug with the reverse inner literal optimization reporting incorrect match
offsets.

v1.9.2
Compare Source
==================
This is a patch release that fixes another memory usage regression. This
particular regression occurred only when using a RegexSet. In some cases,
much more heap memory (by one or two orders of magnitude) was allocated than in
versions prior to 1.9.0.
Bug fixes:

BUG #1059:
Fix a memory usage regression when using a RegexSet.

v1.9.1
Compare Source
==================
This is a patch release which fixes a memory usage regression. In the regex
1.9 release, one of the internal engines used a more aggressive allocation
strategy than what was done previously. This patch release reverts to the
prior on-demand strategy.
Bug fixes:

BUG #1027:
Change the allocation strategy for the backtracker to be less aggressive.

tokio-rs/tokio (tokio)
v1.33.0: Tokio v1.33.0
Compare Source
1.33.0 (October 9, 2023)
Fixed

io: mark Interest::add with #[must_use] (#6037)
runtime: fix cache line size for RISC-V (#5994)
sync: prevent lock poisoning in watch::Receiver::wait_for (#6021)
task: fix spawn_local source location (#5984)

Changed

sync: use Acquire/Release orderings instead of SeqCst in watch (#6018)

Added

fs: add vectored writes to tokio::fs::File (#5958)
io: add Interest::remove method (#5906)
io: add vectored writes to DuplexStream (#5985)
net: add Apple tvOS support (#6045)
sync: add ?Sized bound to {MutexGuard,OwnedMutexGuard}::map (#5997)
sync: add watch::Receiver::mark_unseen (#5962, #6014, #6017)
sync: add watch::Sender::new (#5998)
sync: add const fn OnceCell::from_value (#5903)

Removed

remove unused stats feature (#5952)

Documented

add missing backticks in code examples (#5938, #6056)
fix typos (#5988, #6030)
process: document that Child::wait is cancel safe (#5977)
sync: add examples for Semaphore (#5939, #5956, #5978, #6031, #6032, #6050)
sync: document that broadcast capacity is a lower bound (#6042)
sync: document that const_new is not instrumented (#6002)
sync: improve cancel-safety documentation for mpsc::Sender::send (#5947)
sync: improve docs for watch channel (#5954)
taskdump: render taskdump documentation on docs.rs (#5972)

Unstable

taskdump: fix potential deadlock (#6036)

Configuration
:date: Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
:warning: Warning: custom changes will be lost.


AssemblyInformationalVersion does not produce a build warning

Summary
The documentation says that if you use a version for <AssemblyInformationalVersion> which does not follow the format Major.Minor.Build.Revision a build warning is produced, but this is not correct.
The build warning is produced for the <FileVersion>. If its version does not follow the format above then we see the following warning:
The specified version string does not conform to the recommended format - major.minor.build.revision
This PR moves the "Note" about the build warning under the "Assembly file version" section.  See the demo project I created to exemplify this: https://github.com/joaopgrassi/fileversion-buildwarning

Awesome! Super excited that it got merged/accepted that fast! Thanks for the good work you all put up for us at docs.microsoft.com!


Implementation of support for new PHP7 typing features

Corresponding to issue #3

Enabling code generation with type hints;
Options to adapt the generated code to PSR 1, 2 and 12;
Option to choose PHPDoc notation type for typing non-empty arrays

model-example.zip

Thank you, this is quite the big pull request
I will have a look at it tomorrow, but on the first viewing everything looks great.

It's ok. I hope the implementation will help the project


Using rich as a visual library

Hello there,
I've seen that there have been some attempts to improve colcon via adding more colors to the output
https://github.com/colcon/colcon-core/pull/195
https://github.com/colcon/colcon-core/pull/487
I was thinking lately we could go further with utilization of Python's rich library.
I did some initial experiments and with minimal effort I've been able to get some results:

This is just an experiment, but I'm happy to make a PR for this.

@Serafadam, do you mind sharing your code for this?

maybe @Serafadam uses from rich import print and keeps other code as is @rhaschke ?


Failing build on Arch Linux

The current develop branch fails to build on Arch Linux:
[856/1238] Linking CUDA executable cuda/test/base/array
FAILED: cuda/test/base/array
: && /opt/cuda/bin/g++ -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now     -Wl,-rpath -Wl,/usr/lib -Wl,--enable-new-dtags cuda/test/base/CMakeFiles/cuda_test_base_array.dir/array.cu.o -o cuda/test/base/array  -Wl,-rpath,/build/ginkgo-hpc-git/src/build/lib  lib/libginkgo.so.1.7.0  lib/libginkgo_omp.so.1.7.0  lib/libginkgo_cuda.so.1.7.0  -ldl  lib/libginkgo_reference.so.1.7.0  lib/libginkgo_hip.so.1.7.0  lib/libginkgo_dpcpp.so.1.7.0  lib/libginkgo_device.so.1.7.0  /usr/lib/libhwloc.so  /usr/lib/libhwloc.so  /usr/lib/libmpi_cxx.so  /usr/lib/libmpi.so  /usr/lib/libgtest_main.so.1.13.0  /usr/lib/libgtest.so.1.13.0  -lcudadevrt  -lcudart_static  -lrt  -lpthread  -ldl -L"/opt/cuda/targets/x86_64-linux/lib/stubs" -L"/opt/cuda/targets/x86_64-linux/lib" && :
/usr/bin/ld: lib/libginkgo.so.1.7.0: undefined reference to<EMAIL_ADDRESS>/usr/bin/ld: lib/libginkgo_cuda.so.1.7.0: undefined reference to `std::ios_base_library_init()'
collect2: error: ld returned 1 exit status

There are many more linking errors like this.

Could you provide us your used compiler and cuda versions? Maybe that has some incompatibilities. (I think detailed.log in the build directory should have the necessary information)

Could you use the host compiler for compiling all of ginkgo?

After some comments from CMake developers, we recently moved away from setting the CMAKE_CUDA_HOST_COMPILER inside ginkgo, since providing a compatible environment cannot be our responsibility.

Sounds like the default compiler Arch uses is incompatible with the CUDA version available: https://forums.developer.nvidia.com/t/identifier-float32-is-undefined-etc-cuda-12-2-0-gcc-13-1/258930
Building everything with the CUDA package-provided gcc 12 seems to work on Arch.

Sounds like the default compiler Arch uses is incompatible with the CUDA version available: https://forums.developer.nvidia.com/t/identifier-float32-is-undefined-etc-cuda-12-2-0-gcc-13-1/258930

That's exactly why Arch Linux provides the /opt/cuda/bin/g++ -> /usr/bin/g++-12 symlink.

Building everything with the CUDA package-provided gcc 12 seems to work on Arch.

Passing -DCMAKE_C_COMPILER=gcc-12 -DCMAKE_CXX_COMPILER=g++-12 to cmake results in error due to cmake not finding MPI:
-- Could NOT find VTune (missing: VTune_EXECUTABLE VTune_LIBRARY VTune_INCLUDE_DIR)
-- Could NOT find METIS (missing: METIS_LIBRARY METIS_INCLUDE_DIR)
-- Could NOT find MPI_CXX (missing: MPI_CXX_WORKS) (Required is at least version "3.1")
CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find MPI (missing: MPI_CXX_FOUND CXX) (Required is at least
  version "3.1")
Call Stack (most recent call first):
  /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake/Modules/FindMPI.cmake:1837 (find_package_handle_standard_args)
  CMakeLists.txt:239 (find_package)

Same thing happens when I set the compilers via the CC and CXX environment variables. Of course the openmpi package is installed and the configure step actually passed before I started setting the compilers.

That's the same issue:
    kind: "try_compile-v1"
    backtrace:
      - "/usr/share/cmake/Modules/FindMPI.cmake:1278 (try_compile)"
      - "/usr/share/cmake/Modules/FindMPI.cmake:1322 (_MPI_try_staged_settings)"
      - "/usr/share/cmake/Modules/FindMPI.cmake:1645 (_MPI_check_lang_works)"
      - "CMakeLists.txt:2 (find_package)"
    description: "The MPI test test_mpi for CXX in mode normal"
    directories:
      source: "/test/build/CMakeFiles/CMakeScratch/TryCompile-BvetGK"
      binary: "/test/build/CMakeFiles/CMakeScratch/TryCompile-BvetGK"
    cmakeVariables:
      CMAKE_CXX_FLAGS: ""
    buildResult:
      variable: "MPI_RESULT_CXX_test_mpi_normal"
      cached: true
      stdout: |
        Change Dir: '/test/build/CMakeFiles/CMakeScratch/TryCompile-BvetGK'

        Run Build Command(s): /usr/sbin/ninja -v cmTC_33b4e
        [1/2] /opt/cuda/bin/g++    -o CMakeFiles/cmTC_33b4e.dir/test_mpi.cpp.o -c /test/build/CMakeFiles/CMakeScratch/TryCompile-BvetGK/test_mpi.cpp
        [2/2] : && /opt/cuda/bin/g++  -rdynamic  -Wl,-rpath -Wl,/usr/lib -Wl,--enable-new-dtags CMakeFiles/cmTC_33b4e.dir/test_mpi.cpp.o -o cmTC_33b4e  /usr/lib/libmpi_cxx.so  /usr/lib/libmpi.so && :
        FAILED: cmTC_33b4e
        : && /opt/cuda/bin/g++  -rdynamic  -Wl,-rpath -Wl,/usr/lib -Wl,--enable-new-dtags CMakeFiles/cmTC_33b4e.dir/test_mpi.cpp.o -o cmTC_33b4e  /usr/lib/libmpi_cxx.so  /usr/lib/libmpi.so && :
        /usr/sbin/ld: /usr/lib/libmpi_cxx.so: undefined reference to<EMAIL_ADDRESS>        collect2: error: ld returned 1 exit status
        ninja: build stopped: subcommand failed.

For this to work, libmpi_cxx.so needs to be compiled for the right standard library.

@lahwaacz do you want to keep this open for CUDA/HIP support?

@upsj This was already fixed...?

@upsj Well the asserts are a different issue :shrug:


postgresql flex parameter accessible

would it be possible to make all parameters of postgresql flex accessible for the terraform provider. specifically i am interested in:
database
uri
https://docs.api.stackit.cloud/documentation/postgres-flex-service/version/v1#tag/users/paths/~1v1~1projects~1{projectId}~1instances~1{instanceId}~1users/post

Hi @fapo85,
Thanks for the request, we are clarifying and issue with the equivalent for fields for MongoDB Flex and will work add both together then.

Hi @fapo85,
the release v0.30.0 contains the URI support for the postgresflex user resource.
We will also address soon the changes for the database field.


Error: Cannot find module '../../../private.json'

Hi there. Just installed your app on fedora with npm. Trying to run it and it gives me
`
module.js:471
throw err;
^
Error: Cannot find module '../../../private.json'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/usr/lib/node_modules/cli-weather/lib/weather/Data/Weather.js:15:9)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
`

Seems to be a recurring issue with my install, but doesn't come up in my tests. Looking into it.

some isue

The missing file includes the API key, and I just didn't want it to be available with git, so I .gitignored it. Just added a blank .npmignore so it doesn't end up on git, but is still distributable through npm.
Sorry this took so long to fix.


improve reduce default load stream per node to 2 for stream load

Proposed changes
The previous default value 20 is too large, reduce it to 2.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


Change code style

The current naming style is rather horrible to work with. I'd like to switch to a more common camel-cased one. I decided to use UpperCamelCase for classes/types, and lowerCamelCase for functions. Since our compiler is can be whiny, I think it's safe to stay with the _ prefix for static/private variables.
The actual integration should probably done in steps (and focus on the Window system, in order to not disrupt @duncanspumpkin's work). This is more of an introduction to the idea.

I'm not fussed if you want to change the style but i really don't want us to have an inconsistent code base like in OpenRCT2.

I agree with the proposed naming conventions. Like @duncanspumpkin, I would prefer to change the entire code base at once, though.
I'm not sure how far off #136 is, but depending on how close that'll be, perhaps we should wait for it and tackle all at once…?

#136 has a number of bugs in it but its hard to work out where they are occurring.

How come you have moved the windows namespace outside of ui? It makes sense if the ui namespace is to be separated to a separate library.

Because I want the namespaces to match the directory structure. I just let the directory structure be leading for the windows, but I'd be just as happy to put them in src/openloco/ui/windows

Since the project is picking up steam again, I think we should definitely revisit our coding standards.
Personally, as mentioned earlier, I'm in favour of most of the changes outlined in this PR.


🐛 Issue in latest DownloadPackage task to grab the latest package version automatically (version 1.213.0)

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: DownloadPackage
Environment
Azure Pipelines
Issue Description
There seems to be a bug in the latest version of the DownloadPackage task (version 1.213.0). The bug I found is that it can't grab the latest version anymore automatically by specifying latest for the version property of the task. Please note that we're also using the property view: Release in our setup, I don't know if this bug is also there if you don't use that.
Two workarounds:

Specify the task version 1.210.0, this was yesterdays version and in that task version it still works. Change - task: DownloadPackage@1t to: - task<EMAIL_ADDRESS>Don't use latest for the package version, but provide the actual package version you need.

Task logs
##[debug]Got URL https://feeds.dev.azure.com/<account removed by me>/38caf554-5343-4b53-962f-da54d05e434a/_apis/Packaging/Feeds/e1781db3-1264-4241-9c4c-bbe2f95761b4%40Release/Packages/6e0bfc90-970a-4e51-b967-cfdd32476b8b?protocolType=pypi from versioning data.
##[debug]Found 1 packages matching search pattern 6e0bfc90-970a-4e51-b967-cfdd32476b8b
##[debug]task result: Failed
##[error]Latest version not found.
##[debug]Processed: ##vso[task.issue type=error;]Latest version not found.
##[debug]Processed: ##vso[task.complete result=Failed;]Latest version not found.

I can also vouch that something similar is happening in our pipelines as well. Before December 8th, the task was able to pull latest on a per-view basis.
Now unless the latest package in the feed also happens to be the latest in the view we receive this error as well.
Thanks @DaveRuijter for the workarounds.

This essentially also breaks classic pipelines as it's not possible to set the version directly there.

AFAIK this is still a bug

@DaveRuijter  I believe this issue has been fixed with the above merge. Can you confirm the newest version of the download task?


Can't install on heroku

git push logs below

-----> Installing dependencies with npm 1.0.94

       ><EMAIL_ADDRESS>install /tmp/build_2tla4epbiliie/node_modules/libxmljs
       > node-waf configure build

       Checking for program g++ or c++          : /usr/bin/g++
       Checking for program cpp                 : /usr/bin/cpp
       Checking for program ar                  : /usr/bin/ar
       Checking for program ranlib              : /usr/bin/ranlib
       Checking for g++                         : ok
       Checking for node path                   : not found
       Checking for node prefix                 : ok /tmp/node-node-MGI8
       Checking for program xml2-config         : /usr/bin/xml2-config
       'configure' finished successfully (0.080s)
       Waf: Entering directory `/tmp/build_2tla4epbiliie/node_modules/libxmljs/build'
       [ 1/10] cxx: src/libxmljs.cc -> build/default/src/libxmljs_1.o
       [ 2/10] cxx: src/xml_attribute.cc -> build/default/src/xml_attribute_1.o
       [ 3/10] cxx: src/xml_document.cc -> build/default/src/xml_document_1.o
       [ 4/10] cxx: src/xml_element.cc -> build/default/src/xml_element_1.o
       [ 5/10] cxx: src/xml_namespace.cc -> build/default/src/xml_namespace_1.o
       [ 6/10] cxx: src/xml_node.cc -> build/default/src/xml_node_1.o
       [ 7/10] cxx: src/xml_sax_parser.cc -> build/default/src/xml_sax_parser_1.o
       [ 8/10] cxx: src/xml_syntax_error.cc -> build/default/src/xml_syntax_error_1.o
       ../src/xml_sax_parser.cc:18: error: 'Persistent' was not declared in this scope
       ../src/xml_sax_parser.cc:18: error: 'String' was not declared in this scope
       ../src/xml_sax_parser.cc:18: error: '::New' has not been declared
       ../src/xml_sax_parser.cc:18: error: 'String' has not been declared
       Waf: Leaving directory `/tmp/build_2tla4epbiliie/node_modules/libxmljs/build'
       Build failed:  -> task failed (err #1):
       	{task: cxx xml_sax_parser.cc -> xml_sax_parser_1.o}
       npm ERR! error installing<EMAIL_ADDRESS>Error<EMAIL_ADDRESS>install: `node-waf configure build`
       npm ERR! error installing<EMAIL_ADDRESS>`sh "-c" "node-waf configure build"` failed with 1
       npm ERR! error installing<EMAIL_ADDRESS>   at ChildProcess.<anonymous> (/tmp/node-npm-RFUR/lib/utils/exec.js:49:20)
       npm ERR! error installing<EMAIL_ADDRESS>   at ChildProcess.emit (events.js:67:17)
       npm ERR! error installing<EMAIL_ADDRESS>   at ChildProcess.onexit (child_process.js:192:12)

       ><EMAIL_ADDRESS>preuninstall /tmp/build_2tla4epbiliie/node_modules/libxmljs
       > node-waf clean

       'clean' finished successfully (0.005s)
       npm ERR<EMAIL_ADDRESS>install: `node-waf configure build`
       npm ERR! `sh "-c" "node-waf configure build"` failed with 1
       npm ERR!
       npm ERR! Failed at the<EMAIL_ADDRESS>install script.
       npm ERR! This is most likely a problem with the libxmljs package,
       npm ERR! not with npm itself.
       npm ERR! Tell the author that this fails on your system:
       npm ERR!     node-waf configure build
       npm ERR! You can get their info via:
       npm ERR!     npm owner ls libxmljs
       npm ERR! There is likely additional logging output above.
       npm ERR!
       npm ERR! System Linux 2.6.32-341-ec2
       npm ERR! command "/tmp/node-node-MGI8/bin/node" "/tmp/node-npm-RFUR/cli.js" "install"
       npm ERR! cwd /tmp/build_2tla4epbiliie
       npm ERR! node -v v0.4.7
       npm ERR! npm -v 1.0.94
       npm ERR! code ELIFECYCLE
       npm ERR!
       npm ERR! Additional logging details can be found in:
       npm ERR!     /tmp/build_2tla4epbiliie/npm-debug.log
       npm not ok
 !     Failed to install dependencies with npm
 !     Heroku push rejected, failed to compile Node.js app

Heroku supports only node 0.4.7 oficially. There are some hacks to install 0.6 using a buildpack, but that is not officially supported by the platform.

I don't really like this. We shouldn't have to put in unrecommended constructs to support bugs that were fixed. I don't know the best way to put pressure on PaaS providers, but they should really upgrade to the lastest stable versions of node. 0.4.7 has bugs. That's why there are 5 point releases after it.

It isn't really unrecommended. The using statement there is perfectly valid and acceptable syntax. That being said, I agree 100% but that fix was the reality I had to face. I would rather have had a function versus a define in any case.
Unfortunately, as an end user I guess there is not much a person can do about it in this case. And sometimes there might be other factors preventing the upgrade. I did update the "engine" version in the package.json to reflect a floor for things we will compile on and we can shift that higher if we want to stop supporting old engine version altogether.


Replaced particles.js with the lighter tsParticles

tsParticles is lighter than particles.js, it was born from it but with bugs fixed and new features added. At least it won't use 100% CPU for every visitor

Matteo,
Thanks for submitting this PR. I saw your review on the previous PR, it was just getting unwieldy and the emphasis was on getting it out the door. This looks like a manageable diff but I'd like to test it out locally tomorrow before approving it.


Stride value not consistent with paper

Hello,
Should the stride value at here: https://github.com/bonlime/keras-deeplab-v3-plus/blob/b90de745612df2f367649f64b8ea47b9108618fa/model.py#L371 https://github.com/bonlime/keras-deeplab-v3-plus/blob/b90de745612df2f367649f64b8ea47b9108618fa/model.py#L372  be 2 instead of 1 based on the paper?
Thanks.

You probably refer to this image in paper:

but it shows original Xception
in Deeplab the second exit block uses dilation rate=2 to compencate unexisting stride=2 in block 1


Clarification request for GHES usage

We are using this app for our GHES servers and are seeing some discrepancies in some of the dashboard we'd like to get clarification on. Currently we're on GHES 3.8.2.

In the github_app_for_splunk/2_process_monitor view the bottom 4 dashboard panels remain empty. It seems these are referencing metrics that are not available in our collectd data?

processes.ps_disk_ops.read/write
processes.ps_storage_octets.read/write

We do have other metrics which might be usable for this (going by their names):

processes.io_ops.read/write OR processes.disk_octets.read/write
processes.disk_octets.read/write

Are these the correct ones to use, or should there be others in the GHES collectd data?

In the 3_authentication_monitor view it seems there is an issue with the metric names containing forward slashes '/'?
Looking for statsd.gauge.github/auth/result/*/*.value --> We have statsd.gauge.github_auth_result_*_* . To make these panels work we need to change the slashes to underscores.
Is this supposed to work like that, or should the queries be updated in this app? If so, I'm happy to create a PR for that.

In the different audit view(s) we notice that the action=* filter is not working as expected. Field extractions are not working correctly with GHES audit log data and we need to include "github_source action | spath input=message" to all the queries to make it work. Is that intended?

In the workflow overview view, field names are different in GHES data as well? workflow_job.name, workflow_job.id are not available, but we do have workflow_run.name, worflow_run.id. As a job and a run are not technically the same, should this be changed?

Next to this, really loving the insights we get from this app. ❤

Any feedback on this?

Probably better to tag someone, maybe @derkkila ?


⚠ Samsung has degraded performance

In 2f1c566, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2698 ms

Resolved: Samsung performance has improved in 4a73434.


Change Azure embedding+chat options 'model' property to 'deployment-name'

Azure uses 'deployment-name' when provisioning models and is what needs to be passed in to the client, not the model name. This is a difference with the OpenAI API that doesn't have a deployment-name This change aligns the terminology used with Azure so that there is less confusion when setting configuration property values

Fixes #10
Thank you for taking time to contribute this pull request!
You might have already read the [contributor guide][1], but as a reminder, please make sure to:

Sign the contributor license agreement
Rebase your changes on the latest main branch and squash your commits
Add/Update unit tests as needed
Run a build and make sure all tests pass prior to submission

merged in 1e98f82e03529506c9afaa650717b3819633d573


[audio-button-response] Fix undefined startTime

In the plugin audio-button-response when the audio is started and context is already defined a startAudio variable is used, but never defined, this causes e JS error: Uncaught ReferenceError: startTime is not defined.
This fixes the issue by inlining the variable since this was not reused anywhere else.

@esolitos thanks very much for catching this!
@jodeleeuw is this due to a start_time/startTime typo?
In the audio-slider-response plugin, startTime is a performance.now timestamp and is overwritten with a WebAudio timestamp if WebAudio is used:
https://github.com/jspsych/jsPsych/blob/005772d78b8cb6e573f668e67df54c8c8d525cb5/plugins/jspsych-audio-slider-response.js#L234-L238
And then startTime is compared to either performance.now or context.currentTime to get the RT:
https://github.com/jspsych/jsPsych/blob/005772d78b8cb6e573f668e67df54c8c8d525cb5/plugins/jspsych-audio-slider-response.js#L178-L183
Whereas in this audio-button-response plugin, the performance.now timestamp is given a different variable name (start_time), so it's not overwritten in the WebAudio case:
https://github.com/jspsych/jsPsych/blob/005772d78b8cb6e573f668e67df54c8c8d525cb5/plugins/jspsych-audio-button-response.js#L223-L228
and the response time is always logged with a performance.now timestamp:
https://github.com/jspsych/jsPsych/blob/005772d78b8cb6e573f668e67df54c8c8d525cb5/plugins/jspsych-audio-button-response.js#L165-L166
Should the audio-button-response plugin also collect an RT based on the WebAudio clock (when WebAudio is used)?

Great catch @esolitos. @becky-gilbert I think you've identified the root cause. I'm not sure how the plugins ended up being different, but your solution seems absolutely correct here.

@jodeleeuw thanks!
@esolitos did you want to update your pull request with the above changes, i.e. so that the audio-button-response RT method is the same as that used in audio-slider-response? No problem if not - I can close this PR and make the changes.

Sure @becky-gilbert I can take care of that. :)

@esolitos fantastic, thank you!!

hemm  :D  Sorry, has been a bit of a busy period. :)
I can send in those changes tonight (UTC+1 Tz).
On Mon, 30 Nov 2020 at 22:29, Becky Gilbert<EMAIL_ADDRESS>wrote:

Hi @esolitos https://github.com/esolitos, just checking on the status
of this PR. We're releasing v6.2 soon and want to include this change to
the audio-button-response plugin. But I can make the changes if you don't
have time to do it. Thanks again!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jspsych/jsPsych/pull/1194#issuecomment-736067885, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AADCDG5AQMRZZRQQRVQWOJ3SSQFD7ANCNFSM4TWDHYAA
.

Fixed this issue in commit 074aca7 so I'll close this pull request now. Thanks again for flagging this @esolitos!


expat: showing 0.0% code coverage even if the static inline function is reached

Cf https://introspector.oss-fuzz.com/project-profile?project=expat
This seems to come from
Cf https://storage.googleapis.com/oss-fuzz-coverage/expat/reports/20240113/linux/src/expat/expat/fuzz/xml_parse_fuzzer.c.html#L51
We see that the function's body of ParseOneInput, (likely inlined by the compiler) is shown as covered, but the lines calling it like https://storage.googleapis.com/oss-fuzz-coverage/expat/reports/20240113/linux/src/expat/expat/fuzz/xml_parse_fuzzer.c.html#L71 show a O% coverage, even if they were obviously run as the lines just above and below them...
Would you know about this already ? (bug in clang somehow ? )

I think this may be similar to https://github.com/ossf/fuzz-introspector/issues/482

I think this may be similar to #482

Indeed, any plans to fix it ?


desktop.Clr.x64$C94B8CFE-E3FD-4BAF-A941...

System Information (please complete the following information):

Model Builder or CLI Version: <IP_ADDRESS>6001
Visual Studio Version (if applicable): VS 2019 16.8 RTM

Describe the bug

On which page of the tutorial did you run into an issue (URL): https://dotnet.microsoft.com/learn/ml-dotnet/get-started-tutorial/create
Clear description of the problem: Get an error dialog.

To Reproduce
Steps to reproduce the behavior:

Add .NET Core console app in new solution.
Right-click project > Add > Machine Learning > error dialog.

Expected behavior
Should be able to add ML functions to project similar to instructions.

@shaggygi are you using a 64bit machine? Model Builder only supports 64 bit machines at this time

@shaggygi are you using a 64bit machine? Model Builder only supports 64 bit machines at this time

@JakeRadMSFT yes, this is a 64bit machine.  I believe this was working in an earlier preview, but getting the error now for some reason.  Tried repairing the VS instance, but still fails.

@JakeRadMSFT yes, this is a 64bit machine.  I believe this was working in an earlier preview, but getting the error now for some reason.  Tried repairing the VS instance, but still fails.

@shaggygi Sorry about the delay - I've been having difficulties with github notifications. We're you able to resolve this?
I believe following these steps would resolve it:
https://github.com/dotnet/machinelearning-modelbuilder/blob/main/troubleshooting/ModelBuilderTroubleshooting.md#dev-team-cannot-reproduce-no-constant-repro-on-other-machines

@shaggygi I know this issue is older, have you been able to resolve it?

@beccamc yes, but not sure what resolved.  I believe it was a fluke install of VS or ML extension.  sorry on delay for not closing.  thx for checking in 😄


chore: bump importGraph

use a fix for lake exe graph --exclude-meta.

[x] depends on: leanprover-community/import-graph#1

Thanks! :tada:
bors merge


Return Result instead of panic when looking up?

Currently, the lookup_xxx functions, when encoutering bad FTL message (wrong syntax, for example), it just panic.
Could you please make the function return Result, instead of panic?

Thank you for your issue! This has been resolved by #47 which adds try_ variants which return Options instead of panicking


Can I run it in video/real-time?

Can I run it in video/real-time? Or just in images for now?

Like OVIS: http://songbai.site/ovis/index.html#visualization

@rkz98 you can run  it on realtime /video also, first you need to detect the object, use object detector & pass that detected object frame by frame .

Take a look at https://github.com/z-x-yang/Segment-and-Track-Anything

No, this cannot be run in real time (at least not more than about 5-10 FPS).  Every video frame needs to have a heavyweight image feature detector run first, before the segmenter runs.  Even on an A100, the feature detector takes some 150ms per image.

Yes, checkout https://github.com/UX-Decoder/Segment-Everything-Everywhere-All-At-Once. they combine models together to solve problem


Feat: change olivere/elastic to the official go client for es

Proposed Changes:

olivere/elastic is deprecated, so we use the official Elasticsearch client for Go at https://github.com/elastic/go-elasticsearch

use https://github.com/loggie-io/loggie/pull/581


Remove keychain if failed to log in #28

Resolves #28
This catches any log in error with apple and removes the keychain password so that we don't try to use the keychain next time around.

This looks like it'll do part of #28, but the other part I was hoping would happen was that after the incorrect password was removed from the keychain the user would then be prompted for their password as if they had originally logged in without a password in the keychain. Would you be able to add that as well?

@interstateone not sure I fully undestand what you are looking for. Are you looking to basically call readSecureLine again to get a new password?

Yep, that's right. It would also be nice to have both "login without a saved password successfully" and "login with a saved password, fail, prompt for password and login successfully" reuse the same code where appropriate. I haven't put any thought into the details of that though.

@interstateone i added in a retry for password. Currently there is not limit and it will continue to prompt for password. User can obviously cmd+c to quit to stop the loop. I thought that would be better then prompting to retry?

Merged with suggested changes in c12b7c4939202fe8b5e1fa38ee578ed7beeb1d65


fix(core): CW-22295 length of s in canonical signature must be 32 bytes

PR Summary by Typo
Summary
This pull request updates package versions to 1.1.30-beta.0 and pads signature strings in getCanonicalSignature function.
Key Points

Updates package versions to 1.1.30-beta.0 in package-lock.json and package.json.
Pads canonicalS and canonicalR strings in getCanonicalSignature to 64 characters long.

To turn off PR summary, please visit Notification settings.

Task linked: CW-22295 CS - 送 DOT 時，因 bad signature 失敗


FindComponents() The renderer does not have a component with ID ...

I'm pretty sure I'm doing something completely wrong here.
I'm trying to test a component where some information on the component is changed through opening a modal and submitting a form.
In other tests, I'm able to use IRenderedFragment.Find("... css selectors") and everything works out pretty well.
In this test however, I'm wanting to find and act on a component with specific information on it that is most easily accessible through the instance of the component itself, so I wanted to use FindComponent(s).
I saw that I could filter out the component I'm looking for though the Instance property of the IRenderedFragment and tried to use that.
Unfortunately, I'm getting an error ("The renderer does not have a component with ID 22") and I can't seem to find anything about this error in other issues or by Googling.
As far as I can see, somehow I'm losing a reference to the component I'm trying to test, but I don't know how or why (or how to re-get a good reference to it again).
//find specific element in a container to change info on
 var comp = container.FindComponents<OrderProductModelGroup>().Where(o => o.Instance.Info.Po == oldPo).FirstOrDefault();

//open the modal
 comp.FindAll(".OrderProductModelGroupInputs .showModal").FirstOrDefault().Click();

//get the PO element (information we want to change)
var PoElement = comp.FindAll(".modal .Po").FirstOrDefault();

//change Po
PoElement.Change(newPo);

//submit - error here "The renderer does not have a component with ID 22"
comp.FindAll(".modal .confirm").FirstOrDefault().Click();

The component I'm trying to test is very big and has a lot of moving parts, so I won't try to post it here without anyone saying that I need to.
Any help would be appreciated greatly.

Hi @kwhv23
I'm without computer this weekend, and cannot say for sure without seeing your code, but I think that the comp component gets disposed during the Change call. It can happen if you add and remove it from the render tree. If that's the case, you have to call FindComponet again.

@egil
Thanks for your reply!
I tried to find the component with FindComponent again, but I'm getting the same error.
Does this mean my "container" component is getting disposed as well?
If so, would I have to call RenderComponent for the container again or is there some other way to get an updated reference from the renderer?
Is this evidence of something wrong with how I've set the component up in general? I am very new to Blazor in general. I came from MVC so I'm having to learn a lot of new stuff.

Can you describe your test goal. Usually the component you render (container in your case) is the primary target of the test.

Sure.
So, the component is kind of a big one but I'll describe what it does in as few words as I can.
I can't really show too much of the actual code because it is proprietary stuff that my company is working on, but I can provide pictures of the components and describe them if you would like.

Context: (The main purpose and function of the component under test)
In the application I'm building, users can create orders for customers for pieces of equipment (OrderProductModels).
One requirement of the software is that an order can have a "main category / set of information" and each OrderProductModel on the order can belong to a group of "sub categories / set of sub information" which can be separated to the point where changing a PO number on an OrderProductModel creates a different group (an OrderProductModelGroup).
All of these OrderProductModelGroups are collected into an OrderProductModelGroupContainer. (This is the container component that I'm testing).

Additional Context: (More specific, but still potentially relevant information about how the component works)
If any of the information on an OrderProductModel changes, code is run to re-group all of the OrderProductModels on the order.
The sub categories / information for each OrderProductModel can also be adjusted on the group itself, which adjusts all of the OrderProductModels contained within it.
Many of the inputs for controlling the information we're grouping by are abstracted out of the main view the user sees into a modal because there is too much information we're grouping by to show in one small component. The information on an OrderProductModel does not change until the user presses a submit button on the modal itself.

The test:
In this test, I am testing, once the information on an OrderProductModel is changed and is correctly separated into a different group, if the groups can be "re-combined" by resetting the information on the newly separated OrderProductModelGroup.
To do this, I'm performing the following steps:

Render the container for the OrderProductModelGroups
Create a new OrderProductModelGroup with 2 OrderProductModels within it
Change the PO on one of the OrderProductModels to separate it into a new group
Try to re-combine the groups by resetting the PO number on the new group to its original value (this is where I'm stuck)
Verify that there is now one OrderProductModelGroup with the correct information on it

(The behavior of correctly separating into a different groups is verified in a separate test)

I'm very sorry if this is too much information. I'm not very good at cutting down explanations to just the important bits but I tried my best.
I believe I should be able to share much of the testing code if that's something that you would like to see as well.

@kwhv23 hehe thanks for the explanation. It's still a bit hard to follow.
I think I need to see a minimal example of your components and the test you are trying to write. It does not have to be the real code from your system, just something very basic that showcases this test challenge. Maybe you found a bug, or maybe something is unnecessarily hard to test with bUnit, either way I would love to see code and a running example I can play with to better understand it.
Alternatively, let me suggest something else. Try writing the test without using FindComponents, and instead Find() and FindAll(). I am pretty sure that you should be able to make that work (e.g. use the nth css pseudo selector).
Ps. instead of FindAll(..).FirstOrDefault() just use Find(..).

Understood. Sorry about that.
I'll throw an example case together when I get a chance (or I might just ask if it's okay to share this code specifically since it's all just presentation logic).
I actually had the test running using Find/FindAll at one point, but I didn't like how I was having to find the component with specific information using only information present in the DOM. That's when I ran into the error I'm having.
And thanks for the tip on Find()! I wasn't sure how it would work if it found multiple elements, so I'll definitely use that instead.

Actually I already got approval to share the relevant code with you.
What's your preferred file sharing method? Posting all of the code on a comment would make it too long to read feasibly.

Actually I already got approval to share the relevant code with you.
What's your preferred file sharing method? Posting all of the code on a comment would make it too long to read feasibly.

I prefer a minimal example to make it easy for me to comprehend. Remove all the parts that is unnecessary to understand the scenario, e.g. properties, render logic, and markup, that is not relevant for the test at hand. Put it in a repository that I can git clone and run locally.

Understood. I'll try my best at a minimal example. I'll make a private repo and add you as a collaborator.
I'll comment here again when it's done too. It could take a little while. (I'll probably have it by at least tomorrow)

That's fine. I have quite a bit on my plate, so take your time, I might 😉

Alright. I have a minimal example and I added you as a colaborator.
It's still pretty big, unfortunately, so I included a .readme for it. I hope that helps.
I also forgot to add the .vs folder on the .gitignore so I'm also sorry about that.

After playing with your code I am pretty sure you have stumbled upon a bug here. I still do not completely understand what is going on in your components to trigger the bug, but I think I have a fix which I can push in a day or two to the dailys channel here on GitHub Packages.

Oh. That's very surprising for me.
I'm happy to have pointed out a bug at the very least!

Oh. That's very surprising for me.
I'm happy to have pointed out a bug at the very least!

Hehe well yeah, I wish I got everything right in the first try too, but alas 🤣
Seriously though, this is some of the very hard parts of bUnit to test, so I am very happy when users bring forward new cases where the inner parts go boom.

Same.
Very glad I was able to help. I was convinced at the start that I was doing something incorrectly.
I'll wait for a package update and then I'll let you know if that definitely fixed everything.

ok I have pushed a fix to the dev branch.
I do not know yet when beta-9 will ship, but if you are blocked, you can add https://github.com/egil/bUnit/packages to your package sources and get the latest daily from here.
If there are any more issues please let me know, and if you (or your boss( can, consider supporting me and bUnit by clicking on the Sponsor button on the repo or navigating to https://github.com/sponsors/egil.
Best, Egil

Hey! Thanks. I'm having a little trouble installing the package though.
I added the link to my package sources like you said, but I get the following error when I ran the following command:
I changed the names of some local directories but this shouldn't matter
$ dotnet add Project.Tests package bunit --version 1.0.0-beta-9-gd37601398d
  Determining projects to restore...
  Writing C:\Users\Me\AppData\Local\Temp\tmp57CF.tmp
info : Adding PackageReference for package 'bunit' into project 'C:\Users\Me\Documents\Work\Company\Solution\Project.Tests\Project.Tests.csproj'.
info : Restoring packages for C:\Users\Me\Documents\Work\Company\Solution\Project.Tests\Project.Tests.csproj...
info :   CACHE https://api.nuget.org/v3-flatcontainer/bunit.core/index.json
info :   GET https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.core'&semVerLevel=2.0.0
info :   CACHE https://api.nuget.org/v3-flatcontainer/bunit.web/index.json
info :   GET https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.web'&semVerLevel=2.0.0
info :   CACHE https://api.nuget.org/v3-flatcontainer/bunit.xunit/index.json
info :   GET https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.xunit'&semVerLevel=2.0.0
info :   NotFound https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.xunit'&semVerLevel=2.0.0 362ms
info :   NotFound https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.core'&semVerLevel=2.0.0 450ms
info :   NotFound https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.web'&semVerLevel=2.0.0 365ms
log  : Retrying 'FindPackagesByIdAsyncCore' for source 'https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.xunit'&semVerLevel=2.0.0'.
log  : Response status code does not indicate success: 404 (Not Found).
log  : Retrying 'FindPackagesByIdAsyncCore' for source 'https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.web'&semVerLevel=2.0.0'.
log  : Response status code does not indicate success: 404 (Not Found).
log  : Retrying 'FindPackagesByIdAsyncCore' for source 'https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.core'&semVerLevel=2.0.0'.
log  : Response status code does not indicate success: 404 (Not Found).
info :   GET https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.xunit'&semVerLevel=2.0.0
info :   GET https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.web'&semVerLevel=2.0.0
info :   GET https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.core'&semVerLevel=2.0.0
info :   NotFound https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.web'&semVerLevel=2.0.0 62ms
info :   NotFound https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.xunit'&semVerLevel=2.0.0 65ms
info :   NotFound https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.core'&semVerLevel=2.0.0 63ms
log  : Retrying 'FindPackagesByIdAsyncCore' for source 'https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.web'&semVerLevel=2.0.0'.
log  : Response status code does not indicate success: 404 (Not Found).
log  : Retrying 'FindPackagesByIdAsyncCore' for source 'https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.core'&semVerLevel=2.0.0'.
log  : Response status code does not indicate success: 404 (Not Found).
log  : Retrying 'FindPackagesByIdAsyncCore' for source 'https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.xunit'&semVerLevel=2.0.0'.
log  : Response status code does not indicate success: 404 (Not Found).
info :   GET https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.core'&semVerLevel=2.0.0
info :   GET https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.xunit'&semVerLevel=2.0.0
info :   GET https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.web'&semVerLevel=2.0.0
info :   NotFound https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.web'&semVerLevel=2.0.0 56ms
info :   NotFound https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.core'&semVerLevel=2.0.0 57ms
info :   NotFound https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.xunit'&semVerLevel=2.0.0 56ms
error: Failed to retrieve information about 'bunit.web' from remote source 'https://github.com/egil/bUnit/packages/FindPackagesById()?id='bunit.web'&semVerLevel=2.0.0'.
error:   Response status code does not indicate success: 404 (Not Found).

@kwhv23 did you follow the setup guide here: https://docs.github.com/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages#installing-a-package

Nope. I sure didn't. Lol.
I haven't ever tried to install a github package before. I'll follow that and get back to you.

Nope. I sure didn't. Lol.
I haven't ever tried to install a github package before. I'll follow that and get back to you.

I remember it tripping me up a bit when I tried first. The trick is getting the personal token set up correctly to have read access to GPR.

So, I setup the personal token and gave it the read rights for "Download packages from github package registry".
I made the nuget.config, put it in my Project.Tests directory and wrote my token and username in there.
Is this what I'm supposed to put on the package sources? (Before I just added the package source through a menu on visual studio)
<packageSources>
        <clear />
		<add key="github" value="https://github.com/egil/bUnit/packages" />
    </packageSources>

If it is, I'm stuck again. I'm getting pretty much the same error.

Okay, so I had to change what I just posted to:
    <packageSources>
        <clear />
		<add key="github" value="https://nuget.pkg.github.com/egil/index.json" />
    </packageSources>

and it worked perfectly!
Just ran my test and it's passing now! Thank you so much for all of your help.

Awesome, and thanks for the sponsorship @kwhv23, much appreciated.

No problem.
Like, within a week I got a Microsoft MVP to talk with me one-on-one about a very niche problem, fix that problem, and help on the package install process. That's some serious dedication and it's much appreciated.


spl: Added token-2022 extensions' wrappers

While this does look good there are spaces in the directory names which is not ideal

You mean this space?

Space, like an empty character. It's usually bad to have them in a path. Better to use - or something else to append extension

Okay got it, so i make a new pr with the updated directory then it'd be good to go right?

It can be the same PR just a new commit to change the path of the files /
directories
On Sat, Nov 19, 2022, 11:44 PM harsh4786 @.***> wrote:

Okay got it, so i make a new pr with the updated directory then it'd be
good to go right?
—
Reply to this email directly, view it on GitHub
https://github.com/coral-xyz/anchor/pull/2142#issuecomment-1320993508,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADAHMGG6KAVZLOU7XG22YMDWJFQ7PANCNFSM57DTXKTA
.
You are receiving this because you commented.Message ID:
@.***>

how about now?

Looks good thanks. Will merge soon

Just noticed this PR doesn't

add any imports to the cargo.toml to allow the use of the token 2022 crate
doesn't add a feature flag for using these features, similar to how serum dex requires a special feature flag
doesn't have a mod file that exports the functions from the sub directory (at least I think that's what you'd need?)

This just the basic stuff that I've noticed might be missing and would prevent compiling / even accessing the new function, there might be more I didn't spot.
At the very least @harsh4786 you'd need to add a simple test to misc which imports the new token extension features and uses a least one of them. Then you should run into all of the above issues plus maybe more?


[#86]: Adds aws-file as connection method

resolves #86
Description
Adds aws-file as a connection method option for getting credentials from AWS.
Checklist

[x] I have signed the CLA
[ ] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change to the "dbt-bigquery next" section.

@siephen if you could sign the cla that should kick off some tests, we will have a lot of failures for now till we can incorporate This connection type into CI/CD

@siephen if you could sign the cla that should kick off some tests, we will have a lot of failures for now till we can incorporate This connection type into CI/CD

I've signed the CLA and getting details on how to get this working locally to ensure we can replicate it within the CI/CD pipeline.

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Kyle Wigley. This is most likely caused by a git client misconfiguration; please make sure to:

check if your git client is configured with an email to sign commits git config --list | grep email
If not, set it up using git config --global user.email<EMAIL_ADDRESS>Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@McKnight-42 , any ideas why this is hitting after I merged the main branch into it?

@McKnight-42/@VersusFacit, if I add a screenshot of a dbt debug with this and provide the details vis gist, is that enough to get this under review?

@nathaniel-may , looks like the CLI bot removed the tag after I updated the branch with master, Can you add it back in, and this PR is ready for some feedback.

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Kyle Wigley. This is most likely caused by a git client misconfiguration; please make sure to:

check if your git client is configured with an email to sign commits git config --list | grep email
If not, set it up using git config --global user.email<EMAIL_ADDRESS>Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@McKnight-42 or @nathaniel-may , I do not understand why this comment is coming up, and also it seems the branch keeps going stale and then cla-bot removes the cla:yes label.

Hey @McKnight-42 would you say this one is ready-for-review?

@McKnight-42 or @Fleid, I'm having issues running this locally with this set up, so I'm unsure what the issue is, I'm going to keep working on this this week, but I was curious if y'all have seen anything related to service account impersonation that could be used with the aws auth process in Google Cloud

Hi @siephen,
Are you have trouble resolving the CLA warning? Have you followed the step the bot is suggesting? We won't be able to merge the PR as-is if not.
To your question, let me start by restating that I'm not an expert at Google authentication ;)
To me that impersonation option leverages the local OAuth authentication context to be resolved.

Unattended, the identity your runner (CI agent) is using needs to be able to impersonate the service account you define there
Locally you should be able to use the gcloud option to set you up properly

That's my current understanding anyway - please correct me if I'm wrong ;)

@Fleid, Every time I update the branch with the new contents from main. CLA warning shows for Kyle Wigley: I'm not sure how to resolve that, without destroying this branch and starting over.
Do you have any ideas on how to resolve that?

What shows if you git config --list | grep email in your local terminal?

If that was me, I would start over with a new PR, based of the latest main.
I'm sure there is a combination of git magic to get us out of the current situation, but I'm nowhere near that power level 🧙

This sort of thing has happened in the past and has been remedied with a new PR as annoying as that can be. Just link the new PR to this one so there's some semblance of history. That way they're at least connected and not lost in the ether from one another.

@siephen, I'm going to close this PR.
Please open a new one from a fresh branch off main, and we'll move other there.
Sorry about the clunky process :/


New Repository Name
auto-generated-3
Template Repository
sample-template-repository-universe
Team Permission
team A
Enable Issues

[X] Yes, I want to enable Issues

Enable Project

[X] Yes, I want to enable Projects

Allow Squash Merge

[X] Yes, I want to allow squash merge

Private Repository

[X] Yes, I want a private repo

Updated to use warnings only for configuration failures since repo Admins can change this as needed & GitHub Plan features are ever-changing


Table Tool not closing

When I exit the tool by menu it still runs. Only force closing works in this situation. Happens every time.

This issue could be caused by an exception that happens while closing open documents. We need more information to debug.
Can you see if any messages related to Table Tool appear in Console.app when you try to quit the application?
Could it be that this only happens with certain documents? If that is the case, could you share a copy of a problematic documents with us? Of course, only if the document doesn't contain private data.

Closing because the issue is not reproducible. @pascalheidman-bedarf if you are still around please send details and we can reopen the issue.


No pump notes since 2 months

I'm refreshing the TL, but I can't update it including pump.io messages (using 5 accounts: pump, twitter and 3 of GNU social)

If you noticed that you stopped getting updates from some account:
1.Go to AndStatus Settings - Manage existing accounts - select that account from a list.
Account settings window will be opened.
2. Press "Reverify credentials" button to check and fix authentication-rrelated problems.

Re-verified, but still the same problem

I've tried to remove it and add it again, but I only could delete it, if I try to add it, Andstatus crashes (Andstatus has stopped) when verifying

@moshpirit Let's separate different issues.  Crash on adding account and timeline not updated.
I don't have problems getting updates from identi.ca...
Did you succeed in adding account, so we could move further in this ticket? If no, please raise another issue on that, trying to provide me a stack trace,  log...

But I think it crashes because it can add the account.

@moshpirit Anyway, in order to fix the problem, I need to reproduce it or to get logs from who can reproduce it...

I deleted my identi.ca account from AndStatus and created it again - no problems.

Could you please try to add mine to see if it crashes on your phone? (I had no time to add the password, so there's no need to know it)

I'm getting "Internal error" error message after entering username without a passwort at 1realtime.net site. Please set password and email it to me.

sent

I created this account, synced all timelines - this works.
Then deleted it and created again - also no problems. I even posted a test message, sorry :-)

Ok, I have no idea about what I'm doing wrong, I've recompiled it and it is still crashing.

As you can easily reproduce the crash, you should be able to capture a crash report / log from Android Logcat using Eclipse.
See https://www.google.com/search?q=android+logcat+in+eclipse

OK, I've just reinstalled it using a newer version of AIDE. Everything works fine again :+1:

Ok, the TL doesn't get updated and looks like I'm not the only one with this problem:

Trying AndStatus again hopefully my automatic syncing of the timeline is back.

source

@moshpirit Is the problem still actual? If yes please check if you can Reload a Timeline manually.

Update: I still can't see any new note from 4 months ago. I think it's a very big bug. Can you see your pump.io TL? How could I delete just the Pump TL without deleting both accounts? Maybe it's because it can't load the next message from the last it downloaded 4 months ago.

I can see everything perfectly using another clients like Dianara, Puma or Pumpa.

I see pump.io timeline normally.
The fact that you don't see new posts doesn't mean that there is any "bug" ☺

Please check if you can Reload a Timeline manually.
If you don't see anything loaded,  look in a "Commands in a queue". Is anything there about this?

Re-Verify credentials for your Pump.io accounts.

I tried reloading manually all the time (in every message I wrote here) but I found this error in the "commands in a queue":
R; Avatar para<EMAIL_ADDRESS>para pump.io R; Avatar , foreground , manual para<EMAIL_ADDRESS>para pump.io
Creado hace 22 días
executed:1005, last:hace 16 minutos, retriesLeft:10, error:None,
"Creado hace 22 días" means "made 22 days ago"

I did it a few times too and got nothing :\

Could you please switch AndStatus interface to English and repeat this.

Sure! (sorry)
R; Avatar for<EMAIL_ADDRESS>at pump.io
Created 22 days ago
executed:1006, last:4 minutes ago, retriesLeft:10, error:None,

This error is nothing to do a Timeline loading. This means that there was no error downloading a timeline.
The question is, why no new messages are downloaded and/or shown. In order to have an answer to this question, I need a log, created during the Pump.io timeline reload + all "Network level messages",
saved to files:
"Log everything to file" and "Log Network Level Messages" should be turned on, Minimum logging level: VERBOSE.
Can you find these logs?

No, sorry, there's no "logs" folder in /storage/sdcard/Android/data/org.andstatus.app/files/logs :( just "database" and "avatars"

ok, this means that you are using internal storage now?!
Is your device rooted?
If yes, you will see these folders on your internal SD. If no, please switch to External storage first and then repeat  the test and logs search.

...or maybe that path is internal SD? Try to search the same on ExtSdCard...

In the internal storage I don't have any org.andstatus.app in Android/data :\
Yes, I have enabled the external storage and my phone is not rooted.

I  don't see anything about pump in the logs, do you?

Sorry for bothering you, but is there any news?

I didn't have a chance to look into all logs. But my first thought is that in order to easily find a problem we need much less files.
Could you please:
1 . Sync everything
2. Delete all logs.
3. Make a test of reloading one Timeline of the account only  (not in a Combined mode )
4. Immediately copy all logs.

I've deleted the account and I can't fix it (see #268 )

Fixed resintalling it without restoring.Thank you for the support!


Syncing Issues with Feedly

I am facing syncing issues with Feedly and the NNW clients. I use NNW on macOS and iPadOS with my Feedly account linked to both. In the past, when I marked feeds read on one client, the change would propagate to Feedly and to the other NNW client. Now however, each seems to maintain a separate state that only it is aware of. The NNW macOS and iPadOS clients keep track of which feeds have been read on their ends but do not sync with each other or the Feedly web client. I am not sure how to produce logs for this.

Did you restore anything from a Time Machine backup or migrate to a new device lately?

I have not. The only possible issue in the setup is that the iPad is on the 16 beta. Everything else has stayed the same. However, up until a month or so ago, everything was syncing (including on the iPad with the beta OS)

If you do a manual refresh on either your Mac or iPad, do you get an error?
When you check against the Feedly web interface, which matches it? Your iPad or your Mac?

I don't get any errors on either the iPad or the Mac. None of them are in sync either. To test, I read a bunch of feeds on one device, then synced. Checked Feedly online and the other device. All of them show different unread counts. Each device seems to be keeping track of everything that has been read on that device, but is not syncing them over to Feedly itself.

I don't know what is happening to be honest. To resolve it, I recommend deleting your Feedly accounts on both your Mac and iPad and recreating them.

I reset everything and that finally made it work. I'm annoyed that I don't know why it stopped working, because nuking and restarting isn't really a solution, but it's worked for now. Thank you for your help and apologies for the bother.

Most likely your local sync databases got corrupted. We aren't sure how this happens and it isn't a common occurrence, but it seems to happen for all Account types. We're sorry this happened, but are glad that you are back up and working again.


Anti-aliasing question

I've recently upgraded to the latest version of the Azure Maps Control package, but I have some issues with the new anti-aliasing (AA) setting on the PolygonLayer. When enabling the setting, my polygons get a dark border around them, as if there is an additional LineLayer drawn with this data source. I don't know if this is by design, so I'll first give my setting and explain it a bit more.
My PolygonLayer consists of several shapes, all rectangles, that are placed next to each other. The shapes share corners, meaning that adjacent shapes share two identical coordinates. This means that there is no space between them. The expected visualization of these shapes is a big rectangle of a singular color, consisting of several smaller rectangles (Because each rectangle has the same fillColor value (and no fillPattern)). However, when enabling the anti-aliasing setting on the layer, I see borders around each shape:

When disabling the setting, the borders dissapear:

Is it possible that the AA does not take the adjacent shapes into account (which I would expect not to be the case as to how AA usually works)? Or is this effect due to the shapes overlapping?

First off, just set the fillAntialias option to false, as that is the only solution here.
History of this issue:
I came across this a while back, before this option was added to Azure Maps. There is a long story behind it, but basically, the root cause of the issue is not antialiasing specifically, but some other oddity in WebGL (Azure Maps uses MapLibre which is originally a fork of Mapbox gl js, and this issue goes back to at least 2016, and exists in all of them still). This issue doesn't appear too often. You are only the third person that I have had encounter this and mention it in the Azure Maps community in the last 7 years. The first time I didn't think much of it, the second time it came up (last winter) I spent a few days diving into this and eventually figured out the disabling antialiasing helped resolve this issue (or make it less visible). Once I figured that out I reached out to the Azure Maps team and recommended that they expose an option to disable antialiasing so that there is a workaround for this issue for the few data sets that encounter it. This feature is set to true by default as that's what it has been under the hood since the beginning of Azure Maps, and we didn't want to modify the behavior of existing apps, especially since this issue only appears in rare situations. So that new feature was added to provide an option to address this issue, and not the cause of it.

Thanks for the info @rbrundritt! Guess I'll close this issue as your answer is clear!


AssertionError : AWQ Kernels not found

I am facing below error while running one of the examples shared in the examples directory - here
It is unable to find AWQ kernels. I am facing this for all version starting from 0.2.0 to the latest.
I am running this on Google colab with Nvidia T4 GPU.
/usr/local/lib/python3.10/dist-packages/huggingface_hub/utils/_token.py:88: UserWarning:
The secret `HF_TOKEN` does not exist in your Colab secrets.
To authenticate with the Hugging Face Hub, create a token in your settings tab (https://huggingface.co/settings/tokens), set it as secret in your Google Colab and restart your session.
You will be able to reuse this secret in all of your notebooks.
Please note that authentication is recommended but still optional to access public models or datasets.
  warnings.warn(
config.json: 100%
 904/904 [00:00<00:00, 47.7kB/s]
Fetching 10 files: 100%
 10/10 [00:40<00:00,  8.57s/it]
README.md: 100%
 17.9k/17.9k [00:00<00:00, 250kB/s]
special_tokens_map.json: 100%
 72.0/72.0 [00:00<00:00, 561B/s]
generation_config.json: 100%
 111/111 [00:00<00:00, 1.07kB/s]
.gitattributes: 100%
 1.52k/1.52k [00:00<00:00, 20.5kB/s]
tokenizer.json: 100%
 1.80M/1.80M [00:00<00:00, 11.9MB/s]
quant_config.json: 100%
 124/124 [00:00<00:00, 1.81kB/s]
tokenizer_config.json: 100%
 1.46k/1.46k [00:00<00:00, 72.2kB/s]
tokenizer.model: 100%
 493k/493k [00:00<00:00, 6.45MB/s]
model.safetensors: 100%
 4.15G/4.15G [00:39<00:00, 29.6MB/s]
Replacing layers...: 100%|██████████| 32/32 [00:08<00:00,  3.58it/s]
Fusing layers...: 100%|██████████| 32/32 [00:00<00:00, 60.56it/s]
---------------------------------------------------------------------------
AssertionError                            Traceback (most recent call last)
[<ipython-input-1-4c44ae784519>](https://localhost:8080/#) in <cell line: 25>()
     23
     24 # Generate output
---> 25 generation_output = model.generate(
     26     tokens,
     27     streamer=streamer,

16 frames
[/usr/local/lib/python3.10/dist-packages/awq/models/base.py](https://localhost:8080/#) in generate(self, *args, **kwargs)
    102         """A generate function that mimics the HF generate function."""
    103         with torch.inference_mode():
--> 104             return self.model.generate(*args, **kwargs)
    105
    106     @torch.no_grad()

[/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py](https://localhost:8080/#) in decorate_context(*args, **kwargs)
    113     def decorate_context(*args, **kwargs):
    114         with ctx_factory():
--> 115             return func(*args, **kwargs)
    116
    117     return decorate_context

[/usr/local/lib/python3.10/dist-packages/transformers/generation/utils.py](https://localhost:8080/#) in generate(self, inputs, generation_config, logits_processor, stopping_criteria, prefix_allowed_tokens_fn, synced_gpus, assistant_model, streamer, negative_prompt_ids, negative_prompt_attention_mask, **kwargs)
   1477         if generation_mode == GenerationMode.GREEDY_SEARCH:
   1478             # 11. run greedy search
-> 1479             return self.greedy_search(
   1480                 input_ids,
   1481                 logits_processor=prepared_logits_processor,

[/usr/local/lib/python3.10/dist-packages/transformers/generation/utils.py](https://localhost:8080/#) in greedy_search(self, input_ids, logits_processor, stopping_criteria, max_length, pad_token_id, eos_token_id, output_attentions, output_hidden_states, output_scores, return_dict_in_generate, synced_gpus, streamer, **model_kwargs)
   2338
   2339             # forward pass to get next token
-> 2340             outputs = self(
   2341                 **model_inputs,
   2342                 return_dict=True,

[/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py](https://localhost:8080/#) in _wrapped_call_impl(self, *args, **kwargs)
   1516             return self._compiled_call_impl(*args, **kwargs)  # type: ignore[misc]
   1517         else:
-> 1518             return self._call_impl(*args, **kwargs)
   1519
   1520     def _call_impl(self, *args, **kwargs):

[/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py](https://localhost:8080/#) in _call_impl(self, *args, **kwargs)
   1525                 or _global_backward_pre_hooks or _global_backward_hooks
   1526                 or _global_forward_hooks or _global_forward_pre_hooks):
-> 1527             return forward_call(*args, **kwargs)
   1528
   1529         try:

[/usr/local/lib/python3.10/dist-packages/transformers/models/mistral/modeling_mistral.py](https://localhost:8080/#) in forward(self, input_ids, attention_mask, position_ids, past_key_values, inputs_embeds, labels, use_cache, output_attentions, output_hidden_states, return_dict)
   1152
   1153         # decoder outputs consists of (dec_features, layer_state, dec_hidden, dec_attn)
-> 1154         outputs = self.model(
   1155             input_ids=input_ids,
   1156             attention_mask=attention_mask,

[/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py](https://localhost:8080/#) in _wrapped_call_impl(self, *args, **kwargs)
   1516             return self._compiled_call_impl(*args, **kwargs)  # type: ignore[misc]
   1517         else:
-> 1518             return self._call_impl(*args, **kwargs)
   1519
   1520     def _call_impl(self, *args, **kwargs):

[/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py](https://localhost:8080/#) in _call_impl(self, *args, **kwargs)
   1525                 or _global_backward_pre_hooks or _global_backward_hooks
   1526                 or _global_forward_hooks or _global_forward_pre_hooks):
-> 1527             return forward_call(*args, **kwargs)
   1528
   1529         try:

[/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py](https://localhost:8080/#) in decorate_context(*args, **kwargs)
    113     def decorate_context(*args, **kwargs):
    114         with ctx_factory():
--> 115             return func(*args, **kwargs)
    116
    117     return decorate_context

[/usr/local/lib/python3.10/dist-packages/awq/modules/fused/model.py](https://localhost:8080/#) in forward(self, input_ids, attn_bias, attention_mask, is_causal, *args, **kwargs)
    117                 mask,
    118             )
--> 119             h, _, past_key_value = layer(
    120                 h, None, attention_mask=mask, is_causal=is_causal
    121             )

[/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py](https://localhost:8080/#) in _wrapped_call_impl(self, *args, **kwargs)
   1516             return self._compiled_call_impl(*args, **kwargs)  # type: ignore[misc]
   1517         else:
-> 1518             return self._call_impl(*args, **kwargs)
   1519
   1520     def _call_impl(self, *args, **kwargs):

[/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py](https://localhost:8080/#) in _call_impl(self, *args, **kwargs)
   1525                 or _global_backward_pre_hooks or _global_backward_hooks
   1526                 or _global_forward_hooks or _global_forward_pre_hooks):
-> 1527             return forward_call(*args, **kwargs)
   1528
   1529         try:

[/usr/local/lib/python3.10/dist-packages/awq/modules/fused/block.py](https://localhost:8080/#) in forward(self, hidden_states, past_key_value, attn_bias, attention_mask, is_causal)
    110         is_causal=None,
    111     ):
--> 112         norm_out = self.norm_1(hidden_states)
    113         attn_output, _, past_key_value = self.attn.forward(
    114             hidden_states=norm_out,

[/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py](https://localhost:8080/#) in _wrapped_call_impl(self, *args, **kwargs)
   1516             return self._compiled_call_impl(*args, **kwargs)  # type: ignore[misc]
   1517         else:
-> 1518             return self._call_impl(*args, **kwargs)
   1519
   1520     def _call_impl(self, *args, **kwargs):

[/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py](https://localhost:8080/#) in _call_impl(self, *args, **kwargs)
   1525                 or _global_backward_pre_hooks or _global_backward_hooks
   1526                 or _global_forward_hooks or _global_forward_pre_hooks):
-> 1527             return forward_call(*args, **kwargs)
   1528
   1529         try:

[/usr/local/lib/python3.10/dist-packages/awq/modules/fused/norm.py](https://localhost:8080/#) in forward(self, x)
     17
     18     def forward(self, x):
---> 19         assert AWQ_INSTALLED, (
     20             "AWQ kernels could not be loaded. "
     21             "Please install them from https://github.com/casper-hansen/AutoAWQ_kernels"

AssertionError: AWQ kernels could not be loaded. Please install them from https://github.com/casper-hansen/AutoAWQ_kernels

@casper-hansen Kindly help.

you can try
pip install autoawq_kernels

@DonliFly Based on the Readme page, pip installing autoawq automatically installs compatible autoawq_kernels version.
And I can also see the autoawq_kernels already installed as a dependency for autoawq.
Still I get the error.

Did you try to install the kernels as suggested by the error message? Most likely, an error happened during installation due to your environment not meeting the requirements. Please retry and paste the logs

@hitsense Oh, I have faced the same problem as you. Did you solve this problem?

@hitsense I just solved this issue. You just need to create a new virtual env and install autoawq and autoawq-kernels.

@casper-hansen I faced another issue. I ran generate code, However, I set the prompt, data, and model to my own fine-tuned model. But I encountered the following error. How can I resolve it?
~/autoawq$ python3 test.py
Replacing layers...: 100%|██████████████████████| 40/40 [00:04<00:00,  9.71it/s]
Fusing layers...: 100%|█████████████████████████| 40/40 [00:02<00:00, 17.21it/s]
The attention mask and the pad token id were not set. As a consequence, you may observe unexpected behavior. Please pass your input's `attention_mask` to obtain reliable results.
Setting `pad_token_id` to `eos_token_id`:2 for open-end generation.
Traceback (most recent call last):
  File "/home/jeffrey/autoawq/test.py", line 93, in <module>
    generated_output = model.generate(
  File "/home/jeffrey/.cache/pypoetry/virtualenvs/autoawq-MwlF3Uxe-py3.10/lib/python3.10/site-packages/awq/models/base.py", line 104, in generate
    return self.model.generate(*args, **kwargs)
  File "/home/jeffrey/.cache/pypoetry/virtualenvs/autoawq-MwlF3Uxe-py3.10/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/jeffrey/.cache/pypoetry/virtualenvs/autoawq-MwlF3Uxe-py3.10/lib/python3.10/site-packages/transformers/generation/utils.py", line 1544, in generate
    return self.greedy_search(
  File "/home/jeffrey/.cache/pypoetry/virtualenvs/autoawq-MwlF3Uxe-py3.10/lib/python3.10/site-packages/transformers/generation/utils.py", line 2401, in greedy_search
    model_inputs = self.prepare_inputs_for_generation(input_ids, **model_kwargs)
  File "/home/jeffrey/.cache/pypoetry/virtualenvs/autoawq-MwlF3Uxe-py3.10/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 1256, in prepare_inputs_for_generation
    if past_key_value := getattr(self.model.layers[0].self_attn, "past_key_value", None):
  File "/home/jeffrey/.cache/pypoetry/virtualenvs/autoawq-MwlF3Uxe-py3.10/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1688, in __getattr__
    raise AttributeError(f"'{type(self).__name__}' object has no attribute '{name}'")
AttributeError: 'LlamaLikeModel' object has no attribute 'layers'

Same as @Sangh0 on generation I am getting the error  - AttributeError: 'LlamaLikeModel' object has no attribute 'layers'

@imohitmayank Did you solve this problem?

@Sangh0 Nope

I am facing a similar problem: I am using a T4 on google colab
!pip install torch
!pip install transformers
!pip install autoawq

but
import awq_ext

will error:
ImportError: /usr/local/lib/python3.10/dist-packages/awq_ext.cpython-310-x86_64-linux-gnu.so: undefined symbol: _ZN2at4_ops19empty_memory_format4callEN3c108ArrayRefINS2_6SymIntEEESt8optionalINS2_10ScalarTypeEES6_INS2_6LayoutEES6_INS2_6DeviceEES6_IbES6_INS2_12MemoryFormatEE

I have unsuccessfully tested a few configurations and versions. Do we have a setup on google colab that works?
it looks like the current version of cuda on google colab is 12.2 (according to nvcc --version and nvidia-smi)

Ooh I'm importing torch beforehand

The command python -c "import torch; import awq_ext" works on my setup on RunPod. It looks like there must be a mismatch in your environment versus how AutoAWQ was compiled. To resolve this, you either have to match the requirements for the distributed wheels or retry building from source.

got it! i instlaled everything from source (especially autoawq_kernels) and it works! it does take a while though...

Closing this as it is an environment issue. If issues persist with mismatches in torch and cuda versions, you need to compile from https://github.com/casper-hansen/AutoAWQ_kernels/.

got it! i instlaled everything from source (especially autoawq_kernels) and it works! it does take a while though...

thanks , your answer solved my problem


USHIFT-315: Add swap space to the development environment setup

Add swap space to the development environment setup
Closes: USHIFT-315

/assign @dhellmann

/lgtm


[ADD] allow to pass parameters to ./run

with this we can use the run script for arbitrary actions

@hbrunn Thanks!


Cannot select input field inside iframe on E2E test

Describe the bug
When testing a payments application using Cypress, it has proven difficult to type inside an encrypted input field which is inside an iframe. The securedfields component is created using the AdyenCheckout function.
To Reproduce
Steps to reproduce the behavior:

Create a securedfields component using AdyenCheckout
Target the iframe and then its associated input field, e.g.const getIframeBody = (field: string) => cy.get(`iframe[title="Iframe for ${field}"]`).its('0.contentDocument.body').should('exist')

getIframeBody('card number').find('input')

Input field cannot be found
May see an error message:

ERROR: One or more securedFields has just loaded new content. This should never happen. securedFields have been removed. iframe load count=4. Expected count: 3

Expected behavior
Should be able to target and type into the input field using Cypress
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

Browser [Chrome]

Additional context
Have added the property chromeWebSecurity and set it to false in the Cypress config file
Would really appreciate working examples

May be irrelevant as an issue, but I'd appreciate it immensely if anyone else has overcome this issue on their end

Hey @ashrafnazar ,
Sorry, but we can't really support you with that, as it is not an issue with the library but it is mainly with your code and how you implement your own test cases using your specific tech stack.
Regardless of that, I am not sure if this can shed some light, but we have E2E tests in place that interact with secured fields, although they are written using Playwright. You can check them here if you are interested. Good luck with that!

Hey @ribeiroguilherme - no worries.
FYI, I was able to still carry out E2E tests using Cypress, but only on Electron. Had issues with Chrome - may be helpful to other users out there


How can I add a company backend ?

Hello, Mr.Purcell:
I'm sorry to have trouble you twice  today........
I want to add a company backend, but I added the configuration (follow the instructions for these plugins) without any effect.
Please see my file:
~/.emacs.d/init-cc.el

(when (maybe-require-package 'irony)
  (add-hook 'c-mode-hook 'irony-mode)
  (add-hook 'c++-mode-hook 'irony-mode)
  (add-hook 'objc-mode-hook 'irony-mode))
(after-load 'irony-mode
  (diminish 'irony-mode))

(eval-after-load 'company
  '(add-to-list 'company-backends 'company-irony))

(when (maybe-require-package 'company-irony-c-headers)
(eval-after-load 'company
  '(add-to-list
    'company-backends '(company-irony-c-headers company-irony))))

(provide 'init-cc)

I have done all the other work. (For example, add (reqiure 'init-cc) to init.el)
What mistakes did I make ?
Also, I've seen some guidance on elpa packages in many emacs tutorials and other people's configurations
Their init-elpa file is generally like this:
setq package-archives '(("gnu"   . "xxx")
                         ("melpa" . "xxx")))

.....................................

(require-package 'xxx)
(require-package 'xxx)

........................................

But I did not see the above code in your configuration. What is your implementation ?
Then I see that you use a lot of your own created functions to create this emacs configuration.（like sanityinc/xxx).
Is my error related to not using these functions ?
Thank you very much.

No, you're generally doing the right thing.
I can't really spend much time helping here, but my guess is that your eval-after-load block is getting executed before a similar block in init-company.el, so your settings are getting lost. Try making sure that init-cc.el is loaded after init-company.el.


XCM Asset Metadata

This is a refined version of the XCM Asset Metadata RFC.
This PR supersedes the PR opened in the xcm-format repository following the migration of XCM RFCs to the Fellowship RFCs.
Summary
This RFC proposes a metadata format for XCM-identifiable assets (i.e., for fungible/non-fungible collections and non-fungible tokens) and a set of instructions to communicate it across chains.

Let me know if you want me to put this for onchain voting


cherry-pick Pick "Enhancement Add fix tablet data size api for meta service (#41782)"

Pick #41782

run buildall

run buildall

run cloud_p0

run external

run external