Heatmap Test Protocol

I think we all have small misunderstandings about the manual test protocol, I hope I can clear this up on tuesday.
@markus2330 @kitzbergerg
Manual tests should also be executable without the need of such a big json string. If every test requires that, we will have a hundred page long test protocol.
This
However, main is broken right now because of a missing README.md file, will try to fix it.

I see it is an actual issue, that we need to manually add companions, neutral and antagonist to the db in order to perform this tests. The steps should be written in a way were they are already in the db.

I think we all have small misunderstandings about the manual test protocol, I hope I can clear this up on tuesday.

Yes, let us talk about this on Tuesday. To start the discussion: imho there are two different kinds of test protocols: one to show that a use case was done and another one for releases. In the long term most of it hopefully gets automatically tested. So imho the test protocols are mainly for:

that devs show me what I can expect from PRs/implemented UCs
steps to be automated later

To actually do all these tests manually will hopefully be only needed in the very first releases (for the user studies/beta tests).

I see it is an actual issue, that we need to manually add companions, neutral and antagonist to the db in order to perform this tests. The steps should be written in a way were they are already in the db.

Yes, I also think that tests should simply import everything via scraper.
In the heatmap this was probably only done this way because the scraper for relations was not merged yet.


Merge helm-update-modernization-api-1.0.1-DEMO.f205cc0 into main

Created by Github action in refs/heads/rc_20230803

Adds https://cdc-nbs.atlassian.net/browse/BBJ12-51 fix to rc20230803


Spring Boot 2.1.4+HikariCP 3.3.1+MySQL Duplicate entry exception on batch insert

Environment
HikariCP version: 3.3.1
JDK version     : 1.8.0_201
Database        : Aurora MySQL
Driver version  : 8.0.15

I've check the closed issues and what looked like possible matches in S/O.

I'm getting an error executing batch inserts with a constraint violation exception, which to me makes no sense.
I'm getting a list of users from a table and then looking for entries of those users in an auditing table. If not there, insert them. Because I'm dealing with a lot of users, I batch up the data to be inserted, creating a list of objects and then using saveAll(list) to batch them up.
I'm using Spring Boot 2.1.4 and HikariCP 3.3.1. The primary key of the table getting the inserts is the ID field that is auto-generated. So how I could be getting duplicate entry errors is unclear, unless perhaps this is a timing issue.
I'm batching 1000 objects/statements at a time. It works for at least 1 set of 1000 before it barfs. I'm assuming that the "managed flush" error is a side effect of the duplicate entry error.
My entity is:
@Data
@Entity
@Table(name = "event_state", schema = "subscription")
public class EventState {

	@Id
	@GeneratedValue(generator = "generator")
	@GenericGenerator(name = "generator", strategy = "increment")
	private Long id;

	@Column(name = "customer_dimension_id")
	private Long customerDimensionId;

	@Column(name = "event_id")
	private Long eventId;

	@Column(name = "last_modified")
	@Temporal(TemporalType.TIMESTAMP)
	private Date lastModified;
}

Here is the application.properties file:
spring.output.ansi.enabled=ALWAYS

# logging
logging.file=/tmp/activeusers.log

#HikariCP  config
subscription.datasource.url=jdbc:mysql://mysqlhost:3306/subscription
subscription.datasource.username=USER
subscription.datasource.password=PASS
subscription.datasource.driverClassName=com.mysql.cj.jdbc.Driver
subscription.datasource.hikari.connection-timeout=60000
subscription.datasource.hikari.maximum-pool-size=6
subscription.datasource.hikari.idle-timeout=300000
subscription.datasource.hikari.max-lifetime=1800000
subscription.datasource.hikari.minimum-idle=6
subscription.datasource.hikari.auto-commit=false
subscription.datasource.hikari.validation-timeout=15000
subscription.datasource.cachePrepStmts=true
subscription.datasource.prepStmtCacheSize=250
subscription.datasource.prepStmtCacheSqlLimit=2048
subscription.datasource.useServerPrepStmts=false
subscription.datasource.useLocalSessionState=true
subscription.datasource.rewriteBatchedStatements=true
subscription.datasource.cacheResultSetMetadata=true
subscription.datasource.cacheServerConfiguration=true
subscription.datasource.elideSetAutoCommits=false
subscription.datasource.maintainTimeStats=false
subscription.datasource.hikari.pool-name=SubscriptionPool

#HikariCP  config
activity.datasource.url=jdbc:mysql://mysqlhost:3306/activity
activity.datasource.username=USER
activity.datasource.password=PASS
activity.datasource.driverClassName=com.mysql.cj.jdbc.Driver
activity.datasource.hikari.connection-timeout=60000
activity.datasource.hikari.maximum-pool-size=6
activity.datasource.hikari.idle-timeout=300000
activity.datasource.hikari.max-lifetime=1800000
activity.datasource.hikari.minimum-idle=6
activity.datasource.hikari.auto-commit=true
activity.datasource.hikari.validation-timeout=15000
activity.datasource.cachePrepStmts=true
activity.datasource.prepStmtCacheSize=250
activity.datasource.prepStmtCacheSqlLimit=2048
activity.datasource.useServerPrepStmts=true
activity.datasource.useLocalSessionState=true
activity.datasource.rewriteBatchedStatements=true
activity.datasource.cacheResultSetMetadata=true
activity.datasource.cacheServerConfiguration=true
activity.datasource.elideSetAutoCommits=true
activity.datasource.maintainTimeStats=false
activity.datasource.hikari.pool-name=ActivityPool

spring.jpa.properties.hibernate.jdbc.batch_size=500
spring.jpa.properties.hibernate.order_inserts=true
spring.jpa.properties.hibernate.order_updates=true

I had batch_size set at 1000 originally, then changed it to 100.
UPD 1:  tried changing from using saveAll to save in a loop. Same problem.
UPD 2:  tried switching to the MariaDB driver, but had the same problem.
I don't know if there is a config issue with HikariCP or a Hibernate issue or both. The problem is on the subscription DB, and only one thread does the saveAll.

Hi, I am also having the same issue. For now, i have just removed REV column from primary key in audit table and it worked for me. however, there are now more than one entry in audit table for the same revision number.


Including data into token

How can I insert some more information into JWT response? For example, include the name and email of logged user, just to show it in a fixed bar, avoiding to make a new request on the frontend just to take it. And on JWT decode, to obtain something like:
{
  "userId": 2,
 "name": "john",
 "loginUser":"johndoe42",
  "iat":<PHONE_NUMBER>,
  "exp":<PHONE_NUMBER>,
  "aud": "<IP_ADDRESS>",
  "iss": "feathers",
  "sub": "anonymous"
}

Sorry, my mistake, it is actually a issue using Feathers Authentication


Names of the apps and groups are not visible on mobile

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-1856. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.


build: use the just build compiler if available

It is possible to partially build the necessary tools.  Attempt to use
the just-built compiler if available.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test

CC: @hyp

What does this fix exactly? SWIFT_NATIVE_SWIFT_TOOLS_PATH is already set to the just-built compiler by default, this patch will simply override that even when it isn't.
That will break cross-compiling the Swift compiler and stdlib at one go, ie when the Swift compiler is cross-compiled for a target other than the host and since that cannot be used to cross-compile the stdlib too, a host compiler for Swift is passed in with SWIFT_NATIVE_SWIFT_TOOLS_PATH. I have been experimenting with using precisely such a build config for cross-compiling the Swift compiler and stdlib to Android.

I'm seeing a build failure with SWIFT_NATIVE_TOOLS_PATH for the translation tools and not the compiler break.  I'm trying to repair that scenario.

I'm not familiar with that scenario: SWIFT_NATIVE_SWIFT_TOOLS_PATH is set to the wrong Swift compiler then? This fix is going to break the --cross-compile-hosts scenario, when cross-compiling the stdlib with the just-built host compiler.

It’s less that it’s set to the wrong computer, it’s more that there is no compiler (other than the just built one).  The native tools are being used for the internationalization tools only.

Well, if the just-built one is there, why isn't it set by the main CMakeLists.txt, as shown in my first link above, in your scenario?

Because SWIFT_NATIVE_TOOLS_PATH is set, and that just checks if the value is equal to "", which it is not, so that branch is never taken.

That sounds like the real problem then, fix where "SWIFT_NATIVE_TOOLS_PATH is set" to a non-existent Swift compiler in your scenario instead. This doesn't seem the right way to correct a bad SWIFT_NATIVE_TOOLS_PATH being passed in, if you're breaking other scenarios doing it.

Perhaps you have a better solution in mind, but the scenario is that the internationalization tools are split out, and the SWIFT_NATIVE_TOOLS_PATH is being used to pass those in.  This does need a solution in the short term.  I'm okay with you driving this to a solution if you are interested.

Can you point me at the build-script command or CMake invocation for this main Swift repo that you're trying to fix? I'll take a look.

Its the 5.3 branch btw, and the failure occurs at testing time - not build time.  The build completes, the tests fail due to the "missing" compiler.
Full logs for a recentish run are at https://dev.azure.com/compnerd/swift-build/_build/results?buildId=37997
The CMake invocation for build:
"C:\Program Files\CMake\bin\cmake.exe"
  -B D:\a\1\b/toolchain
  -C D:\a\1\s/swift-build/cmake/caches/toolchain-5.3.cmake
  -C D:\a\1\s/swift-build/cmake/caches/windows-x86_64.cmake
  -C D:\a\1\s/swift-build/cmake/caches/org.compnerd.dt.cmake
  -D CMAKE_BUILD_TYPE=Release
  -D CMAKE_INSTALL_PREFIX=D:\a\1\a/toolchain-windows-x64/Library/Developer/Toolchains/unknown-Asserts-development.xctoolchain/usr
  -D LLDB_FRAMEWORK_INSTALL_DIR=D:\a\1\a/toolchain-windows-x64/Library/Developer/Toolchains/unknown-Asserts-development.xctoolchain/Library/PrivateFrameworks
  -D LLVM_DEFAULT_TARGET_TRIPLE=x86_64-unknown-windows-msvc
  -D LLVM_USE_HOST_TOOLS=NO
  -D LLVM_TABLEGEN=D:\a\1\b\llvm-tools\bin\llvm-tblgen.exe
  -D CLANG_TABLEGEN=D:\a\1\b\llvm-tools\bin\clang-tblgen.exe
  -D LLDB_TABLEGEN=D:\a\1\b\llvm-tools\bin\lldb-tblgen.exe
  -D SWIFT_PATH_TO_LIBDISPATCH_SOURCE=D:\a\1\s/swift-corelibs-libdispatch
  -D SWIFT_NATIVE_SWIFT_TOOLS_PATH=D:\a\1\b/llvm-tools/bin
  -D LLVM_EXTERNAL_SWIFT_SOURCE_DIR=D:\a\1\s/swift
  -D LLVM_EXTERNAL_CMARK_SOURCE_DIR=D:\a\1\s/swift-cmark
  -DLLVM_ENABLE_LIBEDIT=NO
  -DLLVM_PARALLEL_LINK_JOBS=2
  -DPYTHON_EXECUTABLE=C:\hostedtoolcache\windows\Python\2.7.18\x64/python.exe
  -DLLVM_DEFAULT_TARGET_TRIPLE=x86_64-unknown-windows-msvc
  -DSWIFT_WINDOWS_x86_64_ICU_UC_INCLUDE=D:\a\1/icu/icu-windows-x64/Library/icu-67/usr/include/unicode
  -DSWIFT_WINDOWS_x86_64_ICU_UC=D:\a\1/icu/icu-windows-x64/Library/icu-67/usr/lib/icuuc67.lib
  -DSWIFT_WINDOWS_x86_64_ICU_I18N_INCLUDE=D:\a\1/icu/icu-windows-x64/Library/icu-67/usr/include
  -DSWIFT_WINDOWS_x86_64_ICU_I18N=D:\a\1/icu/icu-windows-x64/Library/icu-67/usr/lib/icuin67.lib
  -DSWIFT_PARALLEL_LINK_JOBS=2
  -DSWIFT_BUILD_DYNAMIC_STDLIB=YES
  -DSWIFT_BUILD_DYNAMIC_SDK_OVERLAY=YES
  -G Ninja
  -S D:\a\1\s/llvm-project/llvm

The failing invocation for tests:
"C:\Program Files\CMake\bin\cmake.exe" --build D:\a\1\b/toolchain --target check-swift

With the message:
ninja: error: 'D:/a/1/b/llvm-tools/bin/swift.exe', needed by 'tools/swift/test/CMakeFiles/check-swift-windows-x86_64', missing and no known rule to make it

I'm not convinced that this change is even correct but it was an initial stab at what I thought it might've been.

Ah, just a typo? I think SWIFT_NATIVE_SWIFT_TOOLS_PATH=D:\a\1\b/llvm-tools/bin should be SWIFT_NATIVE_LLVM_TOOLS_PATH=D:\a\1\b/llvm-tools/bin.

No, but you're right that is confusing.  The llvm-tools has clang, llvm, lldb, and swift tools in it (llvm-config, llvm-tblgen, clang-tblgen, lldb-tblgen, and swift-serialize-diagnostics).  BTW, the caches aren't interesting, you can swap them with the content in swift/cmake/caches/Windows-x86_64.cmake

OK, but which of those prebuilt tools are you trying to pass in and actually use? If you don't want to use the prebuilt Swift tools in D:\a\1\b/llvm-tools/bin, then you can just have it use those prebuilt LLVM tools by setting SWIFT_NATIVE_LLVM_TOOLS_PATH instead.

Ah, the prebuilt tools Id like to use in this case are swift-serialize-diagnostics (and swift-def-to-yaml-converter).

Oh, I see, you want to mix some prebuilt Swift tools in with a fresh build? Such mixing is not supported by the current CMake config though, and this pull isn't the way to fix it.
If you just want to run some tests locally and don't need this to work upstream, my suggestion would be to pass the path in with SWIFT_NATIVE_LLVM_TOOLS_PATH and then amend localization/CMakeLists.txt to look there for these two tools instead. Another possibility is to not build the stdlib, if you don't need it for your tests.
If you need this working upstream, that's a whole different can of worms.

I think that we might be able to get away with a less than perfect solution though.  Sadly, I do need this working in upstream (since this is meant to be fore the releases).  The test suite currently requires the standard library for the compiler side of the tests even sadly.  I think that the longer term fix is to split up the test suite into two suites so that they can be run independently, but for the immediate term, we need another solution.
One thing that we could do is to ensure that the build and host are the same when using the just built compiler.  But again, Im not 100% certain that this fixes the test suite execution.

Alright, if this is to get Swift 5.3 for Windows released soon, feel free to do whatever you need, including merging this pull. We can always figure out a better solution for the long-term later on, as that will take more work.

I think I know how to fix both the issue that you are worried about and the actual testing at the same time.  I'll upload a new revision in a little bit.

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

How to change the base branch: (Link)
More detail about the branch update: (Link)


Adding PO.DAAC data source

This PR adds PO.DAAC data source, at present the data source is incomplete and most of the load_dataset function is replicated from the dap.py.
The development of the data source will be continued on this branch.
The tests fail for now, since the data source is still under development.
The retrieve_granule_name and _convert_times_to_datetime works perfectly at present.

@lewismc

Merged build triggered. Test Failed.

Merged build triggered. Test Failed.

I am closing this PR and sending a new one which works with all test cases running OK. Thanks.

@Omkar20895 Could you fix the critical bug at your earliest convenience? Currently, I cannot load ocw.data_source.podaac_datasource.

@huikyole can you link the issue you created in Jira here so we can address it?

@lewismc https://issues.apache.org/jira/browse/CLIMATE-864
As a temporary solution, I disabled podaac modules in dataset_loader in the latest PR, #402


BUG-7616 Wait for response before sending follow-up polling with setp…

…oint gets
Users have reported issues controlling the setpoints of CT100 thermostats. Inspecting logs revealed that the device was not responding to setpoint gets. This was presumably due to issues with the device being overloaded by the number of z-wave messages in a short timeframe. Timers were implemented to attempt to mitigate this, but on busy networks, message queueing means that delays between commands may not be preserved when they're sent by the radio. This approach waits until we have received a response and then sends any subsequent follow-up polls.

This has renewed my desire to implement mailboxing for z-wave devices. Or to enable some sort of transactional relationships.

Can you comment the code a little bit so its easy to understand why this approach was taken?

more than this: https://github.com/SmartThingsCommunity/SmartThingsEdgeDrivers/pull/759/files#diff-1098053ec5c064f9ee13c5285d1e89c8ee7557ebf75ba2db73350edb835d6bf5R127-R129 ?

On second reading that seems fine. LGTM


Feature Request: Allow draw.collide option to be a funcion

While the colide field must be a static boolean field, another fields like the color allows functions.
It would be nice to accept functions in the collide field so for example the value would change depending on the zoom level.
Does it seems like a good idea to you?
Regards.

Hi @IagoLast -- for most cases where we allow a JS function, the output value can be a continuous range that is likely to vary significantly according to feature properties (e.g. feature property mapped to a color range). For fields like collide that can only accept a boolean, where each value gives very different behavior, the currently preferred way would be to use separate sub-layers with a filter to differentiate your features. This is more efficient for the engine to evaluate, as there is some overhead to the JS functions (checking a simple boolean vs. having to call an additional function for every feature, and in addition this has a higher bar for our native ES codebase than in a browser environment). If you have a use case where you think this doesn't make sense, please feel free to elaborate.

Hi @bcamper thx for the quick reply.
We are generating the scene.yaml using a turbocarto file (think in a css for maps).
So for example, this map will have green points in small cities and red points in big ones.
#cities_layer {
  marker-with: 20px;
  [population <= 1000000] {
    marker-color: green;
  }
  [population > 1000000] {
    marker-color: red;
  }
}

Generates the following scene.yaml
layers:
...
    cities_layer:
        data:
            ...
        draw:
            points_0d78ba88223feb7bb63e1ead1bc7d169:
                size: 20
                color: "function() { if (feature['population'] <= 1000000) {return 'green"} else { return 'red'}}"

This runs perfectly, but when we do something similar but varying the collide field it doesn't work.
Im not acquainted with sub-layers. Do you think that using them can solve this kind of issues?
Regards.

You can nest layers (to any depth), and each sub-layer narrows the filter of the layer above it (like a more specific CSS selector). The draw properties from the ancestor layers inherit. See the layer docs for more info.
So in your example something like this, with a new sub-layer to change the collide value based on a feature property called capital for capital cities (this is a hypothetical example):
layers:
...
    cities_layer:
        data:
            ...
        draw:
            points_0d78ba88223feb7bb63e1ead1bc7d169:
                size: 20
                color: "function() { if (feature['population'] <= 1000000) {return 'green"} else { return 'red'}}"
                collide: true # turn collision on by default

        # turn collision off for capital cities only
        capital-cities:
            filter: function() { return feature.capital; }
            draw:
                points_0d78ba88223feb7bb63e1ead1bc7d169:
                    collide: false

Ok, I will check, thank you very much for the help!

Np. To clarify, this is the preferred method for reasons described above, and also because with only two boolean values, it's straightforward to create two separate sub-layers if needed (one for collide: true, one for collide: false). On the other hand, for some continuous values like color, this would be impractical (could potentially lead to hundreds of sub-layers which wouldn't be efficient).


feat: allow skip scaled object creation with config

When integrate Keda-Http with other KEDA scalers, we want to manage ScaledObject by ourselves, and add http-scaler as one of the triggers. In this PR, we allow users to do such ScaledObject management. When flag SKIP_SCALED_OBJECT_CREATION is set to true, keda-http-operator will skip the ScaledObject creation.
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO)
[x] Changelog has been updated and is aligned with our changelog requirements
[x] Any necessary documentation is added, such as:

README.md
The docs/ directory
The docs repo

I think that this is a nice feature and simplifies the compatibility between KEDA and the HTTP add-on because avoid the requirement of implementing the whole ScaledObject spec in the add-on. WDYT @tomkerkhove  @t0rr3sp3dr0 ?
@frankliu20 , Could you add an e2e test for testing this feature? IMO this requires an update in docs to explain that this can be done for other users

I like the idea but would rather have this as a field in the HTTPSO definition instead of an Operator argument. That way, you could have some services using the managed SO while others use a custom one.

@frankliu20 , any update?

Hi, any updates on that feature?
I would like to use zero scaling feature, but for that I need a combination of a keda built-in trigger and the http trigger, at the moment its not possible.

It looks that the PR has been abandoned by the OP :(
Are you willing to continue it @muecahit94 ?

@JorTurFer tbh no, just wanted to ask if there are any updates

I've opened up new PR to allow annotation to be set on the HTTPSO instead as this allows more flexibility.
https://github.com/kedacore/http-add-on/pull/929

This feature is already done by https://github.com/kedacore/http-add-on/pull/929


Adsense stops loading ads after couple of clientside page navigations

When switching pages in my nextjs blog using client side routing, it seems after a few navigations the ads are not showing anymore.
A full page reload resolves this.
I think this is caused by having a maximum number of ads loaded. Probably each navigation needs to do some cleanup on the window object so it behaves like a full page reload.
Anyone else experienced this?
Maybe we need to include some examples for nextjs _app.js or something on how to resolve this.
e.g. This is code I already have in my _app.js, but not sure how to fix google adsense.
export default function App({ Component, pageProps }) {
  const router = useRouter();

  useEffect(() => {
    const handleRouteChange = (url) => {
      console.log(`navigated: ${url}`);
      gtag.pageview(url); // this does the google-analytics pageview tracking.
      // do something with the googleadsense stuff to make it behave like a full page reload.
    };
    router.events.on("routeChangeComplete", handleRouteChange);
    return () => {
      router.events.off("routeChangeComplete", handleRouteChange);
    };
  }, [router.events]);

.........
left for brevity
....

We might also offer a React hook like useAdsense() with instructions on where to add the hook in a nextjs app and where to add it in a plain react app etc.

In react-router i used forceRefresh=true to try and solve for this. I did not notice any real differences. My issue is drop off in revenue and missing clicks. I see them reported in Analytics fine but in Adsense I am only getting 30-40% of clicks. This is down from 80% of clicks when using the old server based site in an A/B test.
Anyone else having this issue?


Use CaseInsensitiveInputStream for Apex parsing

This is a fix for an issue @aly76 mentioned at https://github.com/nawforce/apex-parser/issues/3.
The problem you are having is that Apex being a case insensitive language needs to use a special input stream for ANTLR. In the PR I have swapped the input stream and removed the workarounds. I have tested the this against a few thousand Apex files without error.
While I was testing I had a problem with the fs.existsSync call in list.ts, fs was undefined. I tweaked the code to workaround this but not really sure what my problem was so you may not want that change.

Thanks @nawforce @aly76   that indeed fixes it!


what is the range of the BEV map？

Dear author， thanks for your work！
I am curious about the topdown files. I notice the vehicle in the map is 30m around，but what is the range of drivable area and line？ and how can change the map range？

The topdown files are 500x500 pixels at a resolution of 5 pixels per meter (so totally 100m x 100m with the ego vehicle at the center).
You can find the relevant code here: https://github.com/autonomousvision/transfuser/blob/22b3ccdb7e806b42c9be2aa476b71546e8ec3620/team_code_autopilot/utils/lts_rendering.py#L16

The topdown files are 500x500 pixels at a resolution of 5 pixels per meter (so totally 100m x 100m with the ego vehicle at the center).
You can find the relevant code here:
https://github.com/autonomousvision/transfuser/blob/22b3ccdb7e806b42c9be2aa476b71546e8ec3620/team_code_autopilot/utils/lts_rendering.py#L16
Thanks for your reply!! I understrand


face mesh execution error 3

Plugin Version or Commit ID
v0.11.0
Unity Version
2022.3.1f1
Your Host OS
Ubuntu20.04
Target Platform
Linux Standalone
Target Device
No response
[Windows Only] Visual Studio C++ and Windows SDK Version
No response
[Linux Only] GCC/G++ and GLIBC Version
No response
[Android Only] Android Build Tools and NDK Version
No response
[iOS Only] XCode Version
No response
Build Command
MediaPipeUnity.0.11.0.unitypackage
Bug Description
web camera image wasn't shown.
Steps to Reproduce the Bug

start unity
import MediaPipeUnity.0.11.0.unitypackage
select Face Mesh.unity
set UNITY_MEDIAPIPE_CPU_INFERENCE
run

Log
MediaPipeException: MediaPipe Aborted, refer glog files for more details
Mediapipe.MpReturnCodeExtension.Assert (Mediapipe.MpReturnCode code) (at ./Packages/com.github.homuler.mediapipe/Runtime/Scripts/PInvoke/MpReturnCode.cs:48)
Mediapipe.Glog.Initialize (System.String name) (at ./Packages/com.github.homuler.mediapipe/Runtime/Scripts/External/Glog.cs:78)
Mediapipe.Unity.Bootstrap+d__16.MoveNext () (at Assets/MediaPipeUnity/Samples/Common/Scripts/Bootstrap.cs:59)
UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) (at /home/bokken/build/output/unity/unity/Runtime/Export/Scripting/Coroutines.cs:17)
UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
Mediapipe.Unity.Bootstrap:OnEnable() (at Assets/MediaPipeUnity/Samples/Common/Scripts/Bootstrap.cs:36)
NullReferenceException: Object reference not set to an instance of an object
Mediapipe.Unity.TextureFramePool.OnDestroy () (at Assets/MediaPipeUnity/Samples/Common/Scripts/ImageSource/TextureFramePool.cs:53)
Screenshot/Video

Additional Context
No response

duplicates #915
See https://github.com/homuler/MediaPipeUnityPlugin/issues/915#issuecomment-1593902902.
First, please check if there're already similar issues before creating a new issue (in most cases, there is).
Second, please don't create the same issue repeatedly.

But, the status is not completely the same.


Fix Lint Errors

Summary
I am noticing lint errors on the master branch. Looks like Travis isn't failing when lint fails.

Verifying Travis fails when there are lint errors, then will clean up the lint errors.

Danger, lint, jest build correctly failed with proposed changes.


did the exercises

Thanks for taking a look! Give me more harder exercises if you have them.

Hey Reuben,
This looks great. Clean code, well written, and working. I left a couple comments in-line.

I think you might lije
On Tue, Feb 7, 2017 at 8:51 AM Reuben Ayres<EMAIL_ADDRESS>wrote:

@reubenayres commented on this pull request.
In js/app.js https://github.com/ga-chicago/javascript-reps/pull/1:

}

if(accent=="elongated vowels") {

return sentence.replace(/[A,o,e,i,u]/gi, '$&$&');

}

else return "no accent specified";
+}

+function wordReverse(str) {

// var wordArray = str.split(' ');
// console.log(wordArray);
var revArray = (str.split(' ')).reverse();
var returnString = "";
for(var i = 0; i<revArray.length; i++) {

returnString += revArray[i];

if(i==revArray.length-1){

ah yea of coursed-- like add the space if it's not = 1 and get rid of the
else statement
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ga-chicago/javascript-reps/pull/1, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEsiXXk3CM2YRJgqmush5dkzFX526a2lks5raITpgaJpZM4L40Zl
.

I don't know why that sent.
You might like trying to answer these questions using javascript:
https://projecteuler.net/archives
They will really challenge you to think through what you are trying to do
before writing the code. They're also probably similar to problems you
worked on in school.
Let me know if you are looking for something different.
-Jeff
On Tue, Feb 7, 2017 at 8:52 AM, Jeff Krantz<EMAIL_ADDRESS>wrote:

I think you might lije
On Tue, Feb 7, 2017 at 8:51 AM Reuben Ayres<EMAIL_ADDRESS>wrote:

@reubenayres commented on this pull request.
In js/app.js https://github.com/ga-chicago/javascript-reps/pull/1:

}

if(accent=="elongated vowels") {

return sentence.replace(/[A,o,e,i,u]/gi, '$&$&');

}

else return "no accent specified";
+}

+function wordReverse(str) {

// var wordArray = str.split(' ');
// console.log(wordArray);
var revArray = (str.split(' ')).reverse();
var returnString = "";
for(var i = 0; i<revArray.length; i++) {

returnString += revArray[i];

if(i==revArray.length-1){

ah yea of coursed-- like add the space if it's not = 1 and get rid of the
else statement
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ga-chicago/javascript-reps/pull/1, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AEsiXXk3CM2YRJgqmush5dkzFX526a2lks5raITpgaJpZM4L40Zl
.


add option to install cosign binary for linux with piv/pkcs11 enable

Summary

add option to install cosign binary for linux with piv/pkcs11 enable

also notice that we are not building the same for linux arm64, will fix that in the release job in the cosign repo

as soon we merge i will try that in a linux amd64 machine


CHAOS-4153 Mention how to add enterprise chaoshub to smp

Mention how to add enterprise chaoshub to smp

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65dd7da2e814428565a4acb2--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65e6b16beaea395427680c04--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65f7e1400df21d1cf2ec2f1a--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65f7e99dc265721eb7aa23e1--harness-developer.netlify.app


ROX-13540: Make Sensor Component NodeScanHandler restartable

Description
This is a follow-up PR to address review comments from #3533.
The original PR was merged by accident without addressing optional but
good suggestions.
It includes:

🗑 Removing stoppedC leftover
🐛 Handling a panic when two or more consecutive Start() calls happen without a Stop() call in-between
🧪 Adding a regression test for the two or more consecutive Start() calls
🐛 Fixing previously undiscovered race condition
💄 Removing one level of indentation in sendScan
💄 Using s.Assert() instead assert.
✨ (Extra) Making the component restartable

Re-added Stopped() so that the tests can wait for the handler to finish work.

Extra
After the first comment about not closing the toCentral channel, I decided that the only clean solution to that challenge it to make the component restartable. I added the restartability in https://github.com/stackrox/stackrox/pull/3800/commits/be4bb7cde40d2548bc71fa84d6fd1a3b158d3752.
Checklist

[x] Investigated and inspected CI test results
[x] Unit test and regression tests added

Not applies

[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

Testing Performed

[x] CI
[x] go test -race -count=1 -v -run ^TestNodeScanHandler$ ./sensor/common/compliance
[x] go test -race -count=12 -v -run ^TestNodeScanHandler$ ./sensor/common/compliance (more executions at once)
[x] Manual deployment of cluster locally, enabling the FF, and
confirming that the messages are sent to Sensor and Central. Also
killing sensor pod and making sure that it gets restarted and
self-heals.

Current dependencies on/for this PR:

master

PR #3800   👈

This comment was auto-generated by Graphite.

Inviting additional Sensor experts to review if they find a time :) @fredrb and @lvalerom

havent read it all yet, but wanted to leave some comments in case i forget to come back to this in a timely manner

Thanks @msugakov , I will address the review on Monday!

I removed the restartabilty and simplified some parts in d7353aed4c076ee0b9e3a9ad492ab84d28a93433

Rebased to get rid of the expired cert failure

/test all

One test still has issues: go test -race -count=30 -timeout=10s -v -run ^TestNodeScanHandler/TestStopHandler$ ./sensor/common/compliance. Will continue the next working day.

@RTann @fredrb @lvalerom we are done with changes (provided that CI is happy), if you want to review again, then it may be a good time for it.


[api-docs] Separate two hyperlinks for better readability

A new commit was made into the api-docs repo. This issue was created automatically. Need to review if we made any change to the library for this commit.
https://github.com/discord/discord-api-docs/commit/6cd58500f2ea370cd2ae86ce11a52918b474526b

ncn


pdffiller - google cloud function - question

I'm trying to implement a pdf filler within a google firebase (function) environment without much luck.
Has anyone tried this with any success?
const bucket = storage.bucket('somebucket');
const sourcefilename =  '/test.pdf';
const sourcePDF = bucket.file(sourcefilename);
const filename =  "test-result.pdf";
const file = bucket.file(filename);
const destinationPDF = file.createWriteStream();
var data = {
"last_name": "last",
"first_name": "first",
"date": "Jan 1, 2013",
"football": "Off",
"baseball": "Yes",
"basketball": "Off",
"hockey": "Yes",
"nascar": "Off"
};
const GeneratePDF = (req, res) => {
console.log("here....");
pdfFiller.fillForm(sourcePDF, destinationPDF, data, function (err) {
if (err) throw err;
console.log("In callback (we're done).");
});
};
I think the main issue is around the need to createWriteStream to save to firebase.
Any ideas?

I have been struggling with this too. Uploading is not the problem, I just upload it using
firebase.storage().bucket().upload(destinationPDF, {
    destination: 'forms/' + id + "/form.pdf",
})

But then again, the real problem is
{
  "errno": "ENOENT",
  "code": "ENOENT",
  "syscall": "spawn pdftk",
  "path": "pdftk",
  "spawnargs": [
    "assets/u130.pdf",
    "fill_form",
    "/tmp/temp_data15593199237626mwrm.fdf",
    "output",
    "/tmp/GVdxWekDP8W3Gb1AIJptFgUigvJ3"
  ],
  "cmd": "pdftk assets/u130.pdf fill_form /tmp/temp_data15593199237626mwrm.fdf output /tmp/GVdxWekDP8W3Gb1AIJptFgUigvJ3"
}

pdftk is not available on Firebase Cloud Functions, I'm thinking about setting up a VM but I think is too much trouble. Have you resolved spawn pdftk by any chance?


updated user Details and Added screener chat API

Updated the document with the below details as per the latest ‘xtravision-node’ package we have  https://github.com/xtravision-ai/xtravision-node

Added API details for query getScreenerChatHistory details.
Updated API details for mutation registerUser details, updated with 2 new attribute profileData and timezone missing in the doc.
Added type details for ScreenerChat
. Added type details for ScreenerChatFilter
Added type details for ScreenerChatHistory
Added type details for SortDirection
Updated type details for UserAssessment - updated with 2 new attribute stats and sessionId which were missing in the doc.
Updated type details for userAssessmentFilter - updated with 1 new attribute isRequiredStats.

@mManishTrivedi


"Error: unable to get local issuer certificate" with @sentry/vite-plugin on Node.js v20.9.0 and macOS 14.0

Environment

Sentry Vite Plugin Version: 2.10.1
Vite Version: 4.5.0
Node.js Version: v20.9.0
Operating System: macOS 14.0 (23A344)

Steps to Reproduce

Installed @sentry/vite-plugin version 2.10.1 in my Vite project (version 4.5.0).
Set up the plugin in the Vite configuration file.
Ran the project using yarn run dev.

Expected Result
The project should have started without any SSL certificate issues, and Sentry should be integrated smoothly.
Actual Result
Received an error related to SSL certificates when starting the dev server. The specific error message was:
Error: unable to get local issuer certificate
at TLSSocket.onConnectSecure (node:_tls_wrap:1659:34)
at TLSSocket.emit (node:events:514:28)
at TLSSocket.emit (node:domain:488:12)
at TLSSocket._finishInit (node:_tls_wrap:1070:8)
at ssl.onhandshakedone (node:_tls_wrap:856:12)

Hi, we're not doing any custom network things/tls in the plugins so this is likely an issue with your setup.

Closing for clean-up. Please open a new issue if this still applies. Thanks!


Fixed and improved tests for non-npm usage

Following changes:

File path used in fake commits for tests were from the wrong directory, fixed that.

currentWorkspace definition wasn't generic and would fail for other project file structure, see the substring(11) in
https://github.com/restfulhead/npm-auto-plugins/blob/b509925edaf0f4a8ffa18f9903213794bebf30d9/packages/filter-by-workspace-path/src/index.ts#L56

Also removed:

  // auto adds the current path to the file paths reported from git, so we need to undo this
  const fixedFiles = commit.files.map((file) => path.relative(currentDir, file))

as I couldn't see this behaviour when testing, instead I think the reason for this codepath was the mistake in 1.

Duplicated the test batteries for non-npm usage.

@restfulhead After some testing I realised the latest release of this plugin is broken as filtering doesn't seem to work for non-npm usage.
This PR should hopefully fixes the issue but it's hard to know for sure as I need the new version of the code to be released before importing it in my projects (because local auto plugins are broken see https://github.com/intuit/auto/issues/2019).

@Maxim-Durand Thanks for testing and providing a fix. I will try to test this for the NPM use case later.

// auto adds the current path to the file paths reported from git, so we need to undo this
as I couldn't see this behaviour when testing, instead I think the reason for this codepath was the mistake in 1.

I believe I saw this happen out in the wild before adding the test. I'll double check. Maybe it is something that has been fixed in a more recent auto version.

Released to NPM as v0.4.0

Thanks for the quick release ! :pray:
After some testing I realised my change 3. was incorrect and there is indeed a bug in auto making it append the execution dir as a prefix to the commit files.
I found the reason why and fixed the bug in https://github.com/intuit/auto/pull/2456
Will report back when it's merged to see if this plugin does work as expected on non-npm usage.

I found the reason why and fixed the bug in intuit/auto#2456

@Maxim-Durand Given that this is probably a breaking change and that it'll take time to merge, I think we should revert the path changes and cut another release until it's fixed. Would you agree?

I found the reason why and fixed the bug in intuit/auto#2456

@Maxim-Durand Given that this is probably a breaking change and that it'll take time to merge, I think we should revert the path changes and cut another release until it's fixed. Would you agree?

Sorry I didn't see your message sooner.
Yes I also agree the change 3. should be reverted for now.
Honestly, I'm not even sure auto is still managed anymore since it's been more than 2 months without any new reviews (not a single PR got merged).


user list 1190

Closes #1190

Coverage increased (+0.08%) to 76.724% when pulling 5f59633247d528c5f47d9befb9048ad03196fa35 on na3d:user-list into 29b058d5355f1e11b00cf02cba19dc7ffb966ded on linode:master.

Coverage increased (+0.08%) to 76.724% when pulling 416e55abe02edda58b2b21ded0ba1fc7bd42862b on na3d:user-list into 29b058d5355f1e11b00cf02cba19dc7ffb966ded on linode:master.

Coverage increased (+0.08%) to 76.724% when pulling 1ae394f76ba3fd56c440d24971388ee7e85001c2 on na3d:user-list into 29b058d5355f1e11b00cf02cba19dc7ffb966ded on linode:master.

Coverage increased (+0.08%) to 76.724% when pulling 7aaad3b7de56e79320b3bb44844ddd630f265efe on na3d:user-list into 29b058d5355f1e11b00cf02cba19dc7ffb966ded on linode:master.


Update README.md

Please explain in more detail, how the automatic decoding works - maybe here:
https://github.com/zbateson/MailMimeParser/wiki/ZBateson-MailMimeParser-MimePart#getcontentresourcehandle
Some questions:

It's based on the Content-Transfer-Encoding: header of the mime part?
Which encodings are supported?

Cool, thanks again @ThomasLandauer
I'll create a ticket for your request as well so I don't forget about it :)


Error when I try to run example code

I tried running the example code, and got an error that appears to be linked to the SummarizeReruns function. Perhaps this is user error but I'm hoping someone can help me resolve the issue. Thanks!
Below is the code that I initially ran.

rm(list=ls())

library(tidyverse)
library(gridExtra)
library(zaminfluence)
library(AER)
library(dplyr)
library(tidyr)
library(zaminfluence)

compare <- function(x, y) { return(max(abs(x - y))) }
check_equivalent  <- function(x, y) { stopifnot(compare(x, y) < 1e-8) }

num_obs <- 10000

set.seed(42)

SummarizeReruns <- function(reruns, preds) {
  reruns_df <- GetSignalsAndRerunsDataframe(signals, reruns, model_grads)
  preds_df <- GetSignalsAndRerunsDataframe(signals, preds, model_grads)

  summary_df <-
    rbind(reruns_df %>% mutate(method="rerun"),
          preds_df %>% mutate(method="prediction")) %>%
    pivot_wider(-method, names_from=method, values_from=value) #added df
  return(summary_df)
}

# Generate data.
set.seed(42)
x_dim <- 3
param_true <- 0.1 * runif(x_dim)
num_groups <- 50
df <- GenerateRegressionData(num_obs, param_true, num_groups=num_groups)

# se_group is zero-indexed group indicator with no missing entries.
table(df$se_group)

# Fit a regression model.
x_names <- sprintf("x%d", 1:x_dim)
reg_form <- formula(sprintf("y ~ %s - 1", paste(x_names, collapse=" + ")))
fit_object <- lm(data=df, formula=reg_form, x=TRUE, y=TRUE)

# Get influence and reruns.  Pass the grouping indicator to the `se_group`` argument
# of `ComputeModelInfluence`.
model_grads <-
  ComputeModelInfluence(fit_object, se_group=df$se_group) %>%
  AppendTargetRegressorInfluence("x1")

# The grouped standard error which zaminfluence computes...
cat("Zaminfluence SE:\t", model_grads$param_infls[["x1"]]$se$base_value, "\n")

# ...is equivalent to the that computed by the following standard command:
cat("vcovCL se:\t\t",
    vcovCL(fit_object, cluster=df$se_group, type="HC0", cadjust=FALSE)["x1", "x1"] %>% sqrt(),
    "\n")

signals <- GetInferenceSignals(model_grads)
reruns <- RerunForSignals(signals, model_grads)
preds <- PredictForSignals(signals, model_grads)
summary_df <- SummarizeReruns(reruns, preds)

Here's the error I got:
Error in `stop_subscript()`:
! Can't subset columns that don't exist.
x Column `method` doesn't exist.
Run `rlang::last_error()` to see where the error occurred.

When I run rlang::last_error(), it gives me:
<error/vctrs_error_subscript_oob>
Error in `stop_subscript()`:
! Can't subset columns that don't exist.
x Column `method` doesn't exist.
---
Backtrace:
  1. global SummarizeReruns(reruns, preds)
  4. tidyr:::pivot_wider.data.frame(...)
  5. tidyr:::build_wider_id_cols_expr(...)
  6. tidyr:::select_wider_id_cols(...)
  7. tidyselect::eval_select(enquo(id_cols), data)
  8. tidyselect:::eval_select_impl(...)
 17. tidyselect:::vars_select_eval(...)
 18. tidyselect:::walk_data_tree(expr, data_mask, context_mask, error_call)
 19. tidyselect:::eval_minus(expr, data_mask, context_mask)
 20. tidyselect:::eval_bang(expr, data_mask, context_mask)
 21. tidyselect:::walk_data_tree(expr[[2]], data_mask, context_mask)
 22. tidyselect:::as_indices_sel_impl(...)
 23. tidyselect:::as_indices_impl(x, vars, call = call, strict = strict)
 24. tidyselect:::chr_as_locations(x, vars, call = call)
 25. vctrs::vec_as_location(x, n = length(vars), names = vars)
 26. vctrs `<fn>`()
 27. vctrs:::stop_subscript_oob(...)
 28. vctrs:::stop_subscript(...)
Run `rlang::last_trace()` to see the full context.

I also got a similarly strange error this week, but it went away when I updated my packages (update_packages() in R).
I never tracked down the root cause, but before spending much time digging further, could you please update your packages and try again?

Just checking whether update_packages() worked for you here?

I'm going to close this for inactivity, but feel free to re-open it if you still have problems!


xworkspaces is empty with pinned workspaces

With herbstluftwm, the xworkspaces area of the bar doesn't display anything and cannot be interacted with (scroll/click warns of no matching input area) when pin-workspaces is true. Log messages indicate that the ewmh module is active (start/rebuild cache). When it's false, everything works as expected.
Using polybar 3.1.0 and herbstluftwm 0.7.0.
Apologies if this just hasn't been added in yet - I know xworkspaces is still wip.

It should be working because hlwm implements _NET_DESKTOP_VIEWPORT...
What is the output of xprop -root _NET_DESKTOP_VIEWPORT?

>>> xprop -root | grep "NET_DESKTOP_VIEWPORT"
_NET_DESKTOP_VIEWPORT(CARDINAL) = 0,<PHONE_NUMBER>

>>> polybar -m
eDP-1: 1600x900+0+0

The second value (coordinate?) of _NET_DESKTOP_VIEWPORT changes across restarts, but it's always some ridiculously large number.

That's interesting, the second coordinate is supposed to be the y coordinate of the desktop. This might be a bug with hlwm.

Might be some weird overflow issue. hlwm sets that property in https://github.com/herbstluftwm/herbstluftwm/blob/master/src/ewmh.cpp#L124:
int buf[] = { 0, 0 };
XChangeProperty(g_display, g_root, g_netatom[NetDesktopViewport], XA_CARDINAL, 32, PropModeReplace, (unsigned char *) buf, LENGTH(buf));

However, I don't see anything immediately wrong with this.

I have the same problem.
$ xprop -root _NET_DESKTOP_VIEWPORT
_NET_DESKTOP_VIEWPORT(CARDINAL) = 0,<PHONE_NUMBER>

Maybe you could add a config option to display a list of workspaces?

Yes, it's an overflow issue. Even though 32 is passed to XChangeProperty, the buf array needs to be of type 'long int'.

Thanks for the quick fix @t-wissmann!
I can confirm that xprop -root _NET_DESKTOP_VIEWPORT now returns 0, 0. As for polybar's behaviour, it will now display all workspaces if the bar is on the monitor with (0, 0) as its top-left coordinates, the others will still be empty. The pin-workspaces option in the xworkspaces module isn't really that useful as it just just distributes the defined desktops onto all viewports defined in _NET_DESKTOP_VIEWPORT. A workspace-monitor mapping isn't something that is defined in the EWMH spec as far as I can tell. This notion of a workspace being assigned to a monitor is something that doesn't exist inside hlwm.
I will open a PR to deprecate pin-workspaces in the xworkspaces module, it really only adds confusion, as the behaviour can be quite weird.


SSR not working when react integration is added

Hello!
I have this static page: (/)

and this SSR page: (/eventos-gratuitos)

they work fine but as soon as I use react js on the project

the SSR page stops working

Im not sure why, it works on local though.
Any ideas on how to solve this? it's driving me crazy
thanks in advance!

Hi do you get any errors in console or your Amplify SSR logs? Does that SSR page have prerender = false?

@alexnguyennz Srry I didn't put logs in the original post, I didn't know where to find them but I finally found them.

seems like it doesn't know what react is which is weird since I have it on dependencies

and yes! the SSR page has:

the not SSR page:

I created the app with pnpm create astro, created that SSR page and added the adapter , also react integration... nothing more than that just to see if it works properly.

Thanks for that - can you share the repo or create one that I can quickly deploy to Amplify? I'm away at the moment.

Thanks for that - can you share the repo or create one that I can quickly deploy to Amplify? I'm away at the moment.

@alexnguyennz sure. This is exactly the repo of the screenshots and this is the deploy.
Thank you again for helping!

@alexnguyennz I just tried adding svelte instead of react and it works. Something is wrong with only react but Im not sure what...
(forget about the deploy link, I'm doing more tests and had to remove it since I can only have one live)

I'm using pnpm and I have to use this amplify.yml. Maybe I have to change the outdir? or something like that?
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - npm i -g pnpm
        - pnpm config set store-dir .pnpm-store
        - pnpm i
    build:
      commands:
        - env >> .env
        - pnpm run build
        - mv .env ./.amplify-hosting/compute/default/.env
  artifacts:
    baseDirectory: .amplify-hosting
    files:
      - "**/*"
  cache:
    paths:
      - .pnpm-store/**/*

More info:
With a working svelte integration, I installed the library swiper and it gives the same error given with react...
21:44:41 [ERROR] Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'swiper' imported from /var/task/chunks/index_Dwwy3-g_.mjs

It is weird that in the root page which is static, swiper works properly. But when I go to the SSR page (I didn't put swiper component there), it shows the same as the first post (Just a empty page - doesn't render anything)

There seems to be an issue now with pnpm deployments with the default build spec example. If I test your project with an npm  config (from the repo readme), the SSR page works.
For now, if you want to keep using pnpm in dev but use npm in production, you can use a config like:
version: 1
frontend:
  phases:
    preBuild:
      commands:
	- npm install
        - npm ci
    build:
      commands:
        - env >> .env
        - npm run build
        - mv node_modules ./.amplify-hosting/compute/default
        - mv .env ./.amplify-hosting/compute/default/.env
  artifacts:
    baseDirectory: .amplify-hosting
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Copying the node_modules in the pnpm config (similar to npm/Yarn) results in a build output too large issue on my end - will need to do some more testing and try to find a better solution.

@alexnguyennz we run into same issue now with react and tried your solution with npm but it did not work.
See Build error below:
2024-08-22T16:30:14.418Z [ERROR]: !!! CustomerError: The size of the build output (292846482) exceeds the max allowed size of 230686720 bytes. Please reduce the size of your build output (/codebuild/output/src3799594688/src/astro-aws-amplify/demos/hybrid/.amplify-hosting/compute/default) and try again.
Do you have any other ideas on how to fix this or?
It seems like astro team already had some temp folder for build
https://github.com/withastro/astro/pull/4736

Not at the moment - the adapter relies on Astro's Node.js adapter to build for SSR which requires the node modules folder, and Amplify's build size limit is very small compared to other hosting providers. I still need to find out why pnpm has issues now but unfortunately getting support for this from AWS is a bit difficult.
There are some things you can do to try and reduce the overall size.

Much appreciated. I'm currently stuck with the same issue using pnpm.

@johnajacob Can you try a modified build of:
build:
      commands:
        - env >> .env
        - pnpm run build
        - mv node_modules ./.amplify-hosting/compute/default
        - mv .env ./.amplify-hosting/compute/default/.env

Moving the node_modules works (previously not required with using pnpm stores but now it seems it is).
Note this may result in the build size issue.
@tapnicom Have found another issue related to the build problem https://github.com/aws-amplify/amplify-hosting/issues/3863 Let me know if your project is public, I can have a look at seeing if there's anything that can be removed after the build to drop the size down. Otherwise with Amplify's size limit, I really don't know there's much I can do unfortunately.

Thanks Alex.
I will create a fresh Astro project with React and a library like Shadcn and, maybe there's something you can spot that I don't. If I remember correctly, last time I tried, I ran into the size issue very quickly. I know there's not much to do on this end, and the size limit should be increased, but it's frustrating.

@alexnguyennz pnpm build works
but we are getting such errors with pnpm
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'clsx' imported from<EMAIL_ADDRESS>
when we try to build with npm, we get size limit issue..
We are also not using next but just fork of your blog repo where we tried to add other libraries like react etc.
It seems like Vercel is default path for astro projects?

I wonder if the issue is ouput: hybrid instead of output: server

I encounter a similar issue with an Astro website that integrates a Svelte component. I had to reduce the size because of Amplify limitations by changing from npm to pnpm. I encounter the issue in a specific page that loads a Svelte componente using client:load. This is not working on Amplify. If I change it to client:only="svelte" it work's properly, though i loose all the benefits prerendering my svelte app.
This doesn't work:
<FormContacto client:load />
This works:
<FormContacto client:only="svelte" />
Any suggestions or workarounds to keep prerendering while making client:load work would be greatly appreciated.


Czech translation improvement

Translation improvement. Not sure about broker, however. In czech we do have "burza" and "smenarna". In burza you are paing usually some fees for order, where smenarna using spread for financing their business. Did I get it right?
Also would be good to use some local shops and exchange/broker, where you can spare bitcoins, based on OSM, or some list, like Alza.cz, what is one of very known shop here also for non-bitcoiners.

Moc vám děkuji! :)))

Also would be good to use some local shops and exchange/broker, where you can spare bitcoins, based on OSM, or some list, like Alza.cz, what is one of very known shop here also for non-bitcoiners.

I know about Alza.cz. The Lightning to be accepted by Pilulka.cz, Qerko app (restaurants) and https://cryptopay.cz/cs-CZ/
I want to remake code for language-related links. But I will do it near end of August.


Use parent_root for finalized chain check

Summary
Use block.parent_root instead of hash_tree_root(block) to determine if the block descends from the finalized root.
This has two outcomes:

Removes a single iteration from the check (probably trivial).
Allows for storing the block in store.blocks only if it is valid.

Reasoning
I will make an argument that the following two checks are equal:
Check 1 (existing)
assert get_ancestor(store, hash_tree_root(block), finalized_slot) == store.finalized_checkpoint.root

Check 2 (proposed)
assert get_ancestor(store, block.parent_root, finalized_slot) == store.finalized_checkpoint.root

Argument
In get_ancestor, there are effectively two paths:

if block.slot > slot, recurse using block.parent_root.
Return root.

Considering we've established that prior to both checks we have assert block.slot > finalized_slot, the only possible path in get_ancestor is (1). This recursion in path 1 is equivalent to check 2.
Why am I raising this?
Optimization
Firstly, this removes a redundant block lookup. However, it's not significant and shouldn't be a driving factor, IMO.
Ergonomics
My motivation is that it allows for calling store.blocks[hash_tree_root(block)] = block only once the block is valid. This is important for implementations (like Lighthouse) because it means we don't need to roll back on an invalid block.
I'd like to implement this for Lighthouse and similar to #1880 it would nice to get feedback from spec authors and link to this PR in our code.
Spec bug
Seeing as the spec doesn't implement a rollback, I also believe that this PR fixes a bug that we can call: "Fork choice store is corrupted if an invalid block is suppplied to on_block".
Consider we have some signed_block with an invalid signature and it is the first block to be added to Store after genesis. In on_block that block will be added to store.blocks. Then, the invalid signature will cause on_block to terminate prior to adding the respective state to store.block_states.
Consider that there are now two objects in store.blocks:

The genesis block (genesis_block)
The invalid block (invalid_block)

But only one object in store.block_states:

The genesis block state

Now consider the call stack the next time get_head is called:

get_head(store)
get_filtered_block_store(store)
filter_block_tree(store, tree_hash_root(genesis_block_root), {})
filter_block_tree(store, tree_hash_root(invalid_block), {})

During (4) we will run:
head_state = store.block_states[tree_hash_root(invalid_block)]

This will raise an exception.

As discussed out of band, agreed on the modification here, but also want to add a note to spec that signals that any failed assertion in a handler should result in a no-op to the store.
Doing a quick review to make sure there aren't any other issues like this


ciao-cli: identity: return wrapped errors

The ciao-cli's identity code that handles tokens is never returning an
error.  These leads to strange runtime behaviors in the face of a bad
identity service:  A token related command would fail, but the function
would return a nil error.  The caller would then carry on with
uninitialized "" string variables, which of course led to more failures.
This obfuscates the root issue.
There is an errorf (in some cases of questionable quality) present into
the code adjacent to the nil return.  For simplicity, I've just moved
these existing messages into the errors.Wrap() in addition to the err
itself.  At that point we get the benefit of annotated errors in the
call stack and a non-nil error return so that callers don't carry on
thinking there was no error.
Fixes: #1068
Signed-off-by: Tim Pepper<EMAIL_ADDRESS>

Coverage decreased (-0.02%) to 66.761% when pulling 266ae4bb3737a912748a7a538eb885b38a9209be on tpepper:cli_identity_oddity into 6eb98ce70d8b923bcdcedf628d68dd36645f9b87 on 01org:master.


VersionNumber (A number value)

Interface\AddOns\GSE\API\Serialisation.lua:160: attempt to call field 'VersionNumber' (a number value)
Started getting this around August 22nd.
Version dated 8/21/19.  2.4.14-30-ge3f0660

Hey Merlin
This is known / its with the alpha version that’s in progress.  I should have a fix for it when I get back home Sunday
TimothyLuke

On 24 Aug 2019, at 5:54 am, Fireymerlin<EMAIL_ADDRESS>wrote:
Interface\AddOns\GSE\API\Serialisation.lua:160: attempt to call field 'VersionNumber' (a number value)
Started getting this around August 22nd.
Version dated 8/21/19. 2.4.14-30-ge3f0660
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


fix(*) drop luasocket in CLI

WIP, need to add ssl cafile support in kong migrations CLI; maybe that will benefit to kong vaults as well.
Summary

Full changelog

[Implement ...]
[Add related tests]
...

Issue reference

Fix #[issue number]

@fffonion I don't think this can be done, for the reasons you found out. I discussed it with @bungle as well for Vaults and other pieces that need it as a fallback. Even if it can be done, I think it would take more hackery than would be wise...
The only proper way out I see would be for OR to support sockets in those phases, but that's a whole new challenge 🤷

@Tieske How do you feel about https://github.com/Kong/kong/pull/8993/commits/a6a1c72aaf33f461b7e5f509737e637f17584f52 🤔 ? I haven't really tested it, but it shows proof of concept.

I feel it could be done. Not sure how hackery is respawning (but I think we were already doing it, perhaps we need to do it twice, once to gather trusted certs and then to do what it was already doing). On my mind I though about similar resolution to the issue. The vaults currently do resolving of process secrets on CLI in timer phase with cosockets (no fallback to cosockets and pass the secrets to init with env var or on reload with a file), but they are missing support for trusted_certs currently. I think lua-resty-secrets (which integrated vault solution does not use) may work differently as it uses resty.socket or similar lib embedded. I am excited if we can get this working.

lua-resty-aws and lua-resty-gcp both use LuaSocket fallbacks as well. Not sure how that works/fails with the current Vaults solution.

@Tieske it seems the only two parts that does network connection is:

cluster_events update its initial time (https://github.com/Kong/kong/pull/8993/files#diff-bf75cd7b30a4bf3453f56734db348cbed164bf32a6be22107e950c6f64fcd079L129) updated to the fallback method to use ngx.time() (let me know if it's a sane change)
cache_warmup: move to a timer, i think this is fine, as it's running at the last part of init_worker and no other components seems to rely on it.

Closing because of lack of activity. We would like to accept this contribution if anyone wishes to pick this back up.


wrong type printed for tuple containing null

It seems that, at least on JS, the following is printing [ceylon.language::Null], whereas it should be printing [ceylon.language::null]:
import ceylon.language.meta {type}
print(type([null]));

I don't think this is actually correct. The specification says that the type of the expression [null] is [Null] (anonymous types are eliminated by type inference).
Now, there is a difference between the string representation of tuple types between JS and JVM, but that's not precisely a "bug" as such. string is already defined to have very weak semantics.

Then it seems there are two bugs:

A conflation of the two null types at runtime on JS, e.g. `\Inull`.supertypeOf(`Null`), type(Singleton<\Inull>(null)).typeArguments)
A compile time type inference bug

A conflation of the two null types at runtime on JS, e.g. `\Inull`.supertypeOf(`Null`), type(Singleton<\Inull>(null)).typeArguments)

OK, so indeed it does look like the JS metamodel doesn't properly distinguish between the types \Inull and Null.

A compile time type inference bug

I don't see any such bug. The correct type is inferred at compile time.

The specification says that the type of the expression [null] is [Null]

[\Ismaller] a = [smaller]; // no error
Singleton<\Ismaller> b = Singleton(smaller); // error

@gavinking
I think there is something clearly wrong here:

Tuple literals don't seem to be getting their type inferred by normal means; they are not eliminating anonymous class types. I.e. [\Inull] nt = [null]; works.
Tuples should have their type narrowed to the most specific type at run-time, hence the run-time type of [null] should be [\Inull] at run-time, however, the type accused by the type function is [Null].
assert(is [\Inull] nt = [null] of Anything); works, which indicates that the type accused by the type function is wrong.

@gavinking, I think that this issue should be reopened to represent [a] conflation of the two null types at runtime on JS, and a new issue should be opened to represent [a] compile time type inference bug.

OK, I see. That looks wrong.

Alright, I have now reviewed precisely what the spec says on this topic, and I've verified that the typechecker tests indeed test exactly the specified behavior. In fact, the typechecker is doing exactly what is defined in the spec, and @Zambonifofex's original bug report is correct and that really is a minor bug in the JS metamodel stuff.
Note that the bug is very specific to Null vs null, and doesn't affect smaller, for example.

Fixed now, I believe.


Prepending toolchain flags or setting tool parameter order

Is your feature request related to a problem? Please describe.
A specialized archiver I am working with uses the format ar [mode] -o [outFile] [inputFiles...]
This mode flag has to be the first parameter, and from what I have found you are only able to append flags at the end
Describe the solution you'd like
add_arflags("mode", { prepend = true })
this would yield the following command
artool mode -o "outfile.a" "one.o" "two.o" "three.o" ...etc
Describe alternatives you've considered
alternatively some way to directly set the order
set_ar_order({ "userflags", "defaultflags", "files", ...etc })
Additional context
No response

for now I've solved this with an intermediate executable that takes the xmake inputs and reformats them for the archiver
having it natively in xmake would be nice though

Reordering flags is not supported yet, and it's complicated to implement.
if you use specialized archiver, you can call set_toolset("ar@artool mode") to set mode.
or write a shell script to wrap it to ar

I tried doing "ar@artool mode" but that failed due to the exec trying to run a file named artool mode.
if I remember correctly the command it called looked something like
exec( "\"artool mode\" -o file... ..etc" )
I'll wait for the feature, my workaround does its job for now :)


DAPR QuickStarts are getting enhanced with Multi App Run as a default option, so does the change to DAPR docs too.

The DAPR Quickstart samples are narrated with DAPR run command. Since we are supporting Multi App Run with both Standalone and AKS modes on Linux and Windows operating systems, we are enhancing all Quickstarts to demonstrate multi app run scenario as the first point. We need to modify documentation as per the quickstart changes.
@hhunter-ms FYA

Completed


Added get_cycle_count and get_core_id

Added functions to get the cycle count and core id.
Also ran cargo fmt, so slight difference in spacing

LGTM! Thanks!


[r114] Retrieve sample reg. features from funcgen DB

Description
Use funcgen PERL API to retrieve the sample reg. feature instead of the INI file.
Views affected
Species INFO pages:

http://wp-np2-25.ebi.ac.uk:6020/Homo_sapiens/Info/Index
http://wp-np2-25.ebi.ac.uk:6020/Sus_scrofa/Info/Index
...

Related JIRA Issues (EBI developers only)
ENSREGULATION-2281

Hi @pblins We see this message when we access Example regulatory feature from species home page.
Activity is not available for regulatory features of type EMAR. Is this expected?

Hi @jyothishnt, this is expected.
Activity is not available for EMAR and CTCF reg. feature types.
Thanks for checking.


Boot Loader agent update.

Boot loader agent has changed in the recent images created for WVD. But this website still has the link for previous version. Previous version reports VM Status differently than the new version. So, kindly update the link for Version <IP_ADDRESS>. Currently it has got <IP_ADDRESS>.
Thank you

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

ID: 7bfcfbec-b7ca-57e2-67cc-e5891fdbefd7
Version Independent ID: 16b54c4d-07de-9d14-2a74-38e321361069
Content: Create Windows Virtual Desktop host pool PowerShell - Azure
Content Source: articles/virtual-desktop/create-host-pools-powershell.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@jsk999 - Thanks for posting your valuable feedback. We are looking into it and will get back to you soon.

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.


Django Girls update

This branch makes two changes:

I've added some clarity to the registration form.
I've included links to the assessment criteria Django Girls uses.

Much better, cheers. What're your thoughts on moving whole sentence inside tag? (Not an objection, happy to merge as is, just curious)

More a questions of aesthetics in terms of both the language and how the link looks within the sentence (I dislike looooooooong links). ;-)

Please merge... (then I can announce Django Girls via Twitter etc....)


Question - Why using inserts within transaction

Hello @kshvakov ,
Since clickhouse doesn't support db transaction at all, I was wondering why you use
var (
		tx, _   = connect.Begin()
		stmt, _ = tx.Prepare("INSERT INTO example (country_code, os_id, browser_id, categories, action_day, action_time) VALUES (?, ?, ?, ?, ?, ?)")
	)
	defer stmt.Close()

in example, but not just use
var (
		stmt, _ = connect.Prepare("INSERT INTO example (country_code, os_id, browser_id, categories, action_day, action_time) VALUES (?, ?, ?, ?, ?, ?)")
	)
	defer stmt.Close()

is it necessary to run inserting by transaction? if yes, why? thanks in advance for your help:)

Hi, it's not a real transaction. It's necessary for data block formation.

It's no good point for ClickHouse.
begin
 prepare -- prepare block
  for {
    exec -- write data to the block
 }
commit -- send the batch request


Allow for returning 'false' to pathfinder to prevent room pathing.

There are 3 return options for multi-room pathfinding functions:

Return a new cost-matrix. This value is used instead of the passed in one.
Return false which prevents the path finder from using this room.
Returning any other value results in the default cost-matrix being used. (This only contains room terrain I believe.)

This requires splitting all pathfinding related functions in to ones that either operate on a single room or deal with multiple room pathing. There is still a common set of options that are represented by FindOptions. To support both multi and single room, FindOptions is now generic with respect to the type returned by the cost callback. To limit this to sane values a tag of RoomCostResult is required.

Thanks for taking a look at the feedback.
Here's the code in the pathfinder that responds to 'false': https://github.com/screeps/driver/blob/e6849f9e2db9495e4344f3ac5d6dd3264e8fb3c6/lib/path-finder.js#L123
Room.findPath does call through the pathfinder but has an early out it the current room is not the same as the target room. It also has a different callback wrapper that doesn't handle a return value of 'false' which arguably is busted. This accounts for the difference between the pathfinder and the room APIs. See: https://github.com/screeps/engine/blob/92a3fffee65d547f12f5a99940c6155d9482a254/src/game/rooms.js#L248
In practicality the Room.findPath is odd in usage due to it early bailing if the rooms are different but however still allows the path being returned to traverse multiple rooms, see: https://github.com/screeps/engine/blob/5eec8a935db9715845ec5bdad1249fd9b8fe8e3d/src/game/rooms.js#L841 This needs an engine change and then we could unify the return results to multi-room everywhere.
The RoomPosition findPathTo delegates to the Room so in any case this API has to be identical to the room one.

I'm working through some more changes on this still to get it in to better shape.

It could be nice to unify the APIs, but I think at this point that would be a pretty big breaking change for the engine, and I don't know if it would be worth it?
I think that Room.findPath and friends are useful in the beginning, but are almost always bypassed later on. Not being able to ignore a room is one problem, but even if we fixed that, they still trim all returned paths to one room, and always run the engine's cost calculation code once per room per tick. There's a lot of room for improvement there: path caching for multiple rooms is a big CPU improvement, as is caching calculated cost matrices over multiple ticks. In practice, at least when I was more active, I found most  players either used Traveller or built their own movement wrapper. And building a movement wrapper is a lot easier around PathFinder.findPath, just because of how it actually exposes all the information.
Room.findPath has a number of nice things going for it, including per-tick-cached calculated cost matrices, and automatic movement with moveTo, but almost every part of it is sub-optimal overall :/
Sorry to ramble! I think my main point is that there would probably be diminishing returns trying to get Room.findPath to be a good multi-room usable API. But if you want to take that on, feel free - this is just my experience.

So I think that's a totally reasonable perspective - this is a significant breaking change with questionable benefit for people that have existing code.
I'm working on essentially an equivalent to traveler but built in rust and I'm using some of these changes as building blocks. Let's put this PR on hold until there's something paired with it that brings some value to the community versus just API cleanup.

Closing this until there's more pressing need for it.


zvm upgrade failure on ArchLinux

❯ zvm upgrade
There's a new version of ZVM (v0.4.0).
 Run 'zvm upgrade' to install it!
Upgrading ZVM... 100% |██████████████████████████████████████████████████████████████████████████████████████████| (7.5/7.5 MB, 34 MB/s)
2023/11/02 18:52:55 ERRO this is a new command, and may have some issues. Consider reporting your problem on Github :) github=https://github.com/
tristanisham/zvm/issues
2023/11/02 18:52:55 FATA failed to self-upgrade zvm
rename /tmp/zvm-upgrade-2633282309/zvm /home/dogue/.zvm/self/zvm: invalid cross-device link

Was on 0.3.0, tried to upgrade and now my zvm installation appears to be broken. The .zvm folder is still in place but the shell can't find the actual zvm binary.
Doing a fresh install seems to have worked to repair my install.

❯ which zvm
/home/dogue/.zvm/self//zvm

Binary path, as requested on xitter

This is similar to the issue on windows after fixing the unzipping issue. Thanks for posting this!

I don't know whether I understand that correctly but for me it doesn't seem like the Windows issue.
On Arch Linux and maybe on other distros /tmp is an tmpfs mount which resides in memory (quote).
os.Rename won't work in this case and you need to find another solution for this.
When you already knew that it was failing because of this: just ignore this comment.

That appears to be correct. My machine has 32GB and df reports /tmp as being a 32GB tmpfs.
tmpfs            32G  6.5M   32G   1% /tmp

I just saw the help wanted label.
What kind of help do you need?
Isn't the solution to simply replace the usage of the os.Rename by a function that works over partition boundries?

I think so? I haven't had time to diagnose this issue fully, thus the help wanted badge.
What're your applicable solutions?

also on openSUSE Tumbleweed

i have this problem too. in my case i have / (including /tmp) mounted on a separate partition to /home

@xtexChooser @darccyy @dogue Could one of you guys build clone from the most recent master, change the version in cli/meta/version.go to something less than the current version and run ZVM_DEBUG=1 zvm upgrade and let me know if it works?
I updated the upgrade to now just use ~/.zvm as the temp dir and updated clean to take care of the upgrade files (It'll call it right after upgrading). It works on my machine, but, ya know.

I can as soon as I fix a no-boot condition.

~/Projects/External/zvm master* 50s
❯ go install .

~/Projects/External/zvm master*
❯ zvm version
v0.4.9

~/Projects/External/zvm master*
❯ ZVM_DEBUG=1 zvm upgrade
You are on ZVM v0.4.9... upgrading to (v0.5.0)2024/01/30 19:06:27 DEBU exe dir path=/home/dogue/.zvm/self
2024/01/30 19:06:27 DEBU tempDir name=/home/dogue/.zvm/4259791209.tar
Upgrading ZVM... 100% |██████████████████████████████████████████████████████████████████████████████████████████| (8.0/8.0 MB, 37 MB/s)
2024/01/30 19:06:28 DEBU zvmPath path=/home/dogue/.zvm/self/zvm
2024/01/30 19:06:28 DEBU untar tarball=/home/dogue/.zvm/4259791209.tar target=/home/dogue/.zvm/zvm-upgrade-1973702191

~/Projects/External/zvm master*
❯

@dogue what version of ZVM do you have installed now (if you just run zvm version off the zvm installed on your path?

0.5.0 :grin:

i was previously using the AUR version (listed as 0.5.0-1 on the AUR, but zvm version returns v0.4.2).
i installed v0.4.1 from manually from releases, and it had the same issue.

Isn't the solution to simply replace the usage of the os.Rename by a function that works over partition boundries?

This sounds right to me 😄

Okay, so it worked correctly. @darccyy could you please try the same thing? You don't have to install zvm like @dogue did. You can just run go build and it'll build in the directory. It'll only update the binary it's called from if the install directory envs are changed. Really an option for people who have weird circumstances on their machine.

it seems to have worked😄

yeah it worked!

Okay, so it worked correctly. @darccyy could you please try the same thing? You don't have to install zvm like @dogue did. You can just run go build and it'll build in the directory. It'll only update the binary it's called from if the install directory envs are changed. Really an option for people who have weird circumstances on their machine.

Yeah I'm still a Go noob but I removed that version and verified that everything is good in ~/.zvm

Thanks @dogue! You really helped me out tonight,

@xtexChooser Thank you so much for helping out. You helped a ton. All three of you are awesome.


GSI does not send to HUD when not spectating player

When using the hud for free cam, the hid "freezes" when you're not on a player and "catches up" once you go back onto a player. Makes it hard to run 2 observers as observer lerps don't exist anymore

Ran demo locally to test and cannot reproduce while running hud via yarn, however bug exists when running the compiled version.

I can't really reproduce this; everything seems to work fine for me when flying around the map in a demo, both via yarn (on master) and the pre-built binary (both master and 2.1.1).
The only thing I'm seeing is that the focused player thing in the bottom center remains on the player you spectated before; logged as #102.

Is this still an issue on v2.3.0?

Gonna close this one for now, feel free to reopen if you're still seeing this.


Support --database-uri option and MELTANO_DATABASE_URI env var on meltano init

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2062
Originally created by @DouweM on 2020-05-26 17:39:40

These are currently only supported on meltano commands run inside an existing project, meaning that the initial system database is always created at .meltano/meltano.db even if a different location is preferred.

View 2 previous comments from the original issue on GitLab


Custom types cause typing errors

Trying out the example at https://pydantic-docs.helpmanual.io/usage/types/#classes-with-get_validators
If you enable all the extra options in the mypy plugin, you get this error:
error: Argument "post_code" to "Model" has incompatible type "str"; expected "PostCode" [arg-type]
Additionally, if you try to set a default like:
    post_code: PostCode = "BN1 1AA"
Then you get this error:
error: Incompatible types in assignment (expression has type "str", variable has type "FormatStr") [assignment]
These errors make sense, as we actually only want to validate a str, not change the type (there is a comment about that in the example, where it probably makes more sense to return a str)
Wouldn't this be better if validators can be included using Annotated? Which would accurately match the exact meaning that we are trying to give this custom type.
For example, my actual use case is just wanting to format a str with previously defined values, so the validator could be something along these lines:
class _FormatStr:
    validate_always = True

    @classmethod
    def __get_validators__(cls):
        yield cls.validate

    @classmethod
    def validate(cls, v: str, values: Dict[str, str]) -> str:
        try:
            return v.format(**values)
        except KeyError as e:
            raise ValueError("Missing settings needed for '{}'.".format(v)) from e

FormatStr = Annotated[str, _FormatStr]

class WelcomeMessage(BaseModel):
    name: str
    message: FormatStr = "Hello, {name}"

The main differences from the docs example is not inheriting from str, not returning an instance of cls, and using Annotated to specify the validator (this could really just be a standalone function, rather than a class, as long as there's a way to specify the validate_always option).
This should type check cleanly if implemented. The plugin could also check that the type accepted by _FormatStr.validate() is compatible with the primary type specified in Annotated (so Annotated[int, _FormatStr] would cause a type error).
If we can allow multiple validators as well, then it would allow chaining validators together which would also be great. For example:
# Formats the string, then passes it to another validator which checks the result is a valid format for a name.
name: Annotated[str, FormatStr, ValidFullName] = "{first_name} {last_name}"
# Could also be used to convert type of previous field or something
name_dict: Annotated[Dict[str, str], ConvertNameToDict]

Would also be nice to specify input/output types explicitly and still be strict typing capable. Something like:
class ConvertToDict:
    ...
    def validate(self, v: str):
        return {...}

class Name(BaseModel):
    name: Annotated[Dict[str, str], ConvertToDict]

n = Name(name="Foo Bar")  # Type of name in __init__ is str, based on validate().
n.name["first"]  # Output type is Dict[str, str]

We’re no longer actively developing Pydantic V1 (although it will continue to receive security fixes for the next year or so), so we’re closing issues solely related to V1. If you really think this shouldn’t be closed, please comment or create a new issue 🚀.


Fix minimum jump height of underwater physics

A check in Air.gd, that cuts off the player's jump height when the jump button is released, only tested for the default jump release value without accounting for underwater physics, which caused every jump while underwater to reach maximum height. This update checks for the current jump release value to fix the problem.
This is my first PR, so I apologize if I have made any mistakes.

looked it over, didn't see any issues with it, seems like it was an oversight on my end. good catch


Backport two fixes

This backports:
ISPN-15184 SIFS can leave many data files left around
ISPN-15147 DefaultExecutorFactory can create multiple ThreadGroups

Thanks

Changes seem fine. I am surprised about the thread group commit though. @FireBurn Are you using wildfly?
Also to give you a heads up there are a lot of fixes in 14 for SoftIndexFileStore. I would highly highly suggest upgrading to the latest version there instead of going down this path.

Yeah I'm using Wildly 26.1.3, it didn't seem a simple change moving to 14

I pushed another commit to fix the thread group stuff that also fixes test failures that are present without it.

It appears the remainder of the test failures are unrelated, hard to tell with this version. Going to integrate.

Thanks @FireBurn !

Thanks, any idea when 13.0.21 might be cut?

https://github.com/infinispan/infinispan/releases/tag/13.0.21.Final


Microsoft.UI.Xaml.Data.ICustomProperty not being excluded from projection

so it's showing up in winrt.runtime.dll and microsoft.winui.dll.  an entry should be made to cswinrt\helpers.h, and breaking change relnote posted

Need to coordinate with WinUI, potentially breaking change.
This type should be provided by WinRT.Runtime.dll, but WinUI is projecting when it shouldn't be.

@stevenbrix as fyi

Thanks @AdamBraden, how will users be affected by this?

The reason this is a breaking change is that assembly-qualified references to ICustomProperty must now be updated to find the type in winrt.runtime.dll, and not Microsoft.WinUI.dll

Reviewing the code, I don't think this change is warranted.  There's no conflict between the public projected ICustomProperty* interfaces in Microsoft.WinUI.dll, and the internal managed implementations provided for all CCWs in winrt.runtime.dll.  We could go to some trouble to consolidate these, and create a breaking change, or just leave things as is.


Fixed: The submenus are not aligned with the title menu #247

Fixed the issue #247
The original code was getting the bounding box of the Title, so the menu was being aligned with the text and not the actual Menu button, this PR fixes it.

:tada: This PR is included in version 4.2.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


The readme file is missing

Add a file to familiarize users with the project and its implementation

Added in feature/issue2 branch


Bump Django versions for Travis to the latest for each release

These got a bit out of date

Thanks!


Proximity chat dose not work, only radio.

Running latest recommended artifact, (4394)
PMA-Voice, 4.0.0
RP-Radio Adapted for pma, 2.2.3
Players can hear eachother thru the radio just fine, but cannot hear eachother  thru proximity chat.
Player can see their own name when talking thru normal game chat (not radio), but  dont see others.

Closing due to inactivity


[BEAM-7370] Upgrade sphinx to 3.0.3

R: @udim.
I tried doing this on the latest docs (from master, 93f605db3034cb0c814ec6baa474b718fbbcf47a) and the diff from sphinx 1.8.5 -> 3.0.3 looks like this: https://github.com/epicfaace/beam-site/commit/bb961b925983cd15e7945e48c8fec9a1cf3a733b

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Thanks! LGTM


The custom endpoint does not execute when the form is rendered

If your dataTableContext uses a custom endpoint, when you render the form it does not get called

Navigate to the configuration form: https://function-adminportal-test.shesha.dev/shesha/forms-designer?id=c3b1d5f5-dcc6-4957-b45f-34bdc9f59d95
Click on the membership payement dataTableContext
Verify the custom endpoint ended on the property
Render the form: https://function-adminportal-test.shesha.dev/dynamic/Shesha/member-details-view?id=b7f0594e-9a6b-478d-bf35-e71962070507 and check if the endpoint is being called
Actual Results: The endpoint is not executed

Expected Results
The endpoint should be executed when the form is rendered

Hi @hlayisanimazuze. It's fixed, please check


[Event Request] codeunit 6500 "Item Tracking Management" - OnCopyItemTracking3OnBeforeReservEntry1Insert

Please add new event in codeunit 6500 "Item Tracking Management" in the function CopyItemTracking3
[IntegrationEvent(false, false)]
local procedure OnCopyItemTracking3OnBeforeReservEntry1Insert(var ReservEntry1: Record "Reservation Entry")
begin
end;

ModifyTempReservEntrySetIfTransfer(TempReservEntry);

if TempReservEntry.FindSet then begin
    ReservEntry1.Reset();
    repeat
        ReservEntry1 := TempReservEntry;
        ReservEntry1."Entry No." := 0;
        OnCopyItemTracking3OnBeforeReservEntry1Insert(ReservEntry1);
        ReservEntry1.Insert();
    until TempReservEntry.Next() = 0;
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 48444.


onSlideChangeEnd making illegal behavior

This is a (multiple allowed):

[x] bug

[x] enhancement

[ ] feature-discussion (RFC)

Swiper Version: 3.4.2

Platform/Target and Browser Versions: Google Chrome Version 58.0.3029.81 (64-bit)  and Windows 10 CU.

What you did
settings.onSlideChangeEnd = function(swiper) {
    console.log('Slide Changed');
}

Expected Behavior
The log will come if the slide changed.
Actual Behavior
The log comes every time if slide changed or not while I'm trying to move the slide.
Additional Information
You can check this video what happening actually.
But, it's working fine as I expected with 3.2.7 version of Swiper.

Issue is closed because of outdated/irrelevant/not actual/needed more information/inactivity.
If this issue is still actual and reproducible for latest version of Swiper, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with issue


Make displayed week for punch card configurable (go back one week, forth one week)

Use date picker directive used in other parts of the ui


x/pkgsite/cmd/pkgsite: Unable to fetch std@Latest Pkgsite documentation for Local Main go Repo : https://go.googlesource.com/go

What version of Go are you using (go version)?

$ go version
go1.21.3

Does this issue reproduce with the latest release?
Yes. But the ultimate intention is to run pkgsite for main go repository - std@latest against master(1.22) branch.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
Windows, amd64, gcc

What did you do?
1. git clone https://go.googlesource.com/go/
2. git checkout go1.21.3
3. git switch -c go1.21.3
4.

-------------------------------------
5. go install golang.org/x/pkgsite/cmd/pkgsite@latest
6. C:\Users\R\golang\go\src>pkgsite .

C:\Users\R\golang\go\src>pkgsite .
2023/10/25 16:29:15 Info: go/packages.Load(["all"]) loaded 277 packages from . in 655.6654ms
2023/10/25 16:29:15 Info: go/packages.Load(std) loaded 0 packages from C:\Program Files\Go in 9.2327ms
2023/10/25 16:29:15 Error: loading packages from stdlib: err: fork/exec C:\Users\R\golang\go\bin\go.exe: The parameter is incorrect.: stderr:
2023/10/25 16:29:15 Info: Listening on addr http://localhost:8080
2023/10/25 16:29:51 Info: FetchDataSource: fetching std@latest
2023/10/25 16:34:10 Error: serveUnitPage(ctx, w, r, ds, &{std std latest}): FetchDataSource.GetUnitMeta("std", "std", "latest"): FetchDataSource.findModule("std", "std", "latest"): FetchDataSource.getModule("std", "latest"): FetchModule("std", "latest"): stdlib.ContentDir("latest"): remoteGoRepo.clone("v1.21.3"): running git fetch: exit status 128: fatal: refusing to fetch into branch 'refs/heads/main' checked out at 'C:/Users/R/AppData/Local/Temp/1087088232'

What did you expect to see?
I was hoping to see the documentation website like pkg.go.dev and std libs listed and to look at their documentation.
What did you see instead?

When I try pkgsite with proxy I get below error

pkgsite -proxy   (GOPROXY - https://proxy.golang.org,direct)

 BYPASSING LICENSE CHECKING: MAY DISPLAY NON-REDISTRIBUTABLE INFORMATION 2023/10/28 17:24:30 Info: go/packages.Load(std) loaded 0 packages from C:\Program Files\Go in 22.9285ms 2023/10/28 17:24:30 Error: loading packages from stdlib: err: fork/exec C:\Program Files\Go\bin\go.exe: The parameter is incorrect.: stderr: 2023/10/28 17:24:30 Info: Listening on addr http://localhost:8080 2023/10/28 17:25:09 Info: FetchDataSource: fetching std@latest 2023/10/28 17:25:09 Info: FetchDataSource: fetched std@latest using *fetch.proxyModuleGetter in 5.7355ms with error FetchModule("std", "latest"): proxy.Client.Info("std", "latest"): Client.readBody("std", "latest", "info"): Client.escapedURL("std", "latest", "info"): path: malformed module path "std": missing dot in first path element: invalid argument 2023/10/28 17:25:09 Error: serveUnitPage(ctx, w, r, ds, &{std std latest}): FetchDataSource.GetUnitMeta("std", "std", "latest"): FetchDataSource.findModule("std", "std", "latest"): FetchDataSource.getModule("std", "latest"): FetchModule("std", "latest"): proxy.Client.Info("std", "latest"): Client.readBody("std", "latest", "info"): Client.escapedURL("std", "latest", "info"): path: malformed module path "std": missing dot in first path element: invalid argument
Note: However, when I tried local packages(Cloned from repo to local), they are working , screenshots attached.

@bcmills - I have my local devel golang - set GOVERSION=devel go1.22-b5f87b5407 Tue Oct 24 20:28:25 2023 +0000 and GOROOT and tools are all local development directory. It is not able to show pkgsite and has shown above errors.
However when I point my GOROOT to my base golang installation "C:\Program Files\go" and respective set GOTOOLDIR, I am able to see the local stdlib code changes reflecting in the documentation. Looks like I am using different toolchain here to render local development stdlib documentation on pkgsite? Is this an issue to be reported?

CC @matloob @jba
Michael, could this be related to recent cmd/pkgsite changes?

@findleyr yes, I think it is related to the recent cmd/pkgsite changes.

@matloob thanks, tentatively assigned to you to investigate further.

I was able to reproduce the Error: loading packages from stdlib: err: fork/exec  $GOROOT\bin\go.exe: The parameter is incorrect.: stderr:  error on Windows. Seems like it's only happening there.
The refusing to fetch into branch 'refs/heads/main' may be the same as issue #63254


Add quantized krmsnorm

This adds more options for kRMSNorm:

optional gain parameters (can simplify hardware)
different quantizations with zero points and scaling factors (currently int8, int16, and none)
more selection strategies - first k, last k, or random k

And a configuration sweep json to search through the settings space for krmsnorm including krmsnorm_num.

Uploading image of current training, hoping complete a grid_search sweep before tomorrow.

Updates

Above shows that no qat has better validation loss, higher precision (int16) does better, and appears larger 'k' values also have a larger impact when quantized.


load native modules

This PR add native modules like fs, net, http, etc.
I use this quite a lot in my plugin for Sublime that does almost the same thing that this package for Atom:
https://github.com/jfromaniello/sublime-node-require
Thanks!

coffutt/atom


Added the ability to send ArtSync message in the Art-Net protocol implementation.

Changes:

Implemented the send_artsync method, which sends an ArtSync message to Art-Net receiving devices.
Added the artsync_header header to the StupidArtnet class for creating ArtSync messages.

Purpose:
Introducing the capability to send ArtSync messages enables synchronization of Art-Net receiving devices, which is essential for ensuring synchronized lighting effects on stage or in other environments.

Summary by CodeRabbit

New Features

Updated the StupidArtnet class to support creating and sending an ArtSync header, enhancing synchronization capabilities.

In case we want to utilize ArtSync, we send it after each buffer transmission (sometimes we want to send a lot of buffers before artsync, what i tell about below).
For the ArtNet data transmission, we could consider adding an option to send ArtSync directly in the constructor. This way, we determine whether we will send synchronization data or not.
When setting up multiple ArtNet servers, for example, a list consisting of 20 ArtNet servers, each sending data to different universes but sequentially, I would like to synchronize the data only after iterating through all 20 elements. At that point, it constitutes one frame of animation for me. Then, we send the synchronization signal. For this purpose, I utilize a separate instance responsible for sending the buffer to a specific address.
Based on this, I'm introducing a commit that enables sending the synchronization signal after each packet transmission (by default, this option is set to false in the constructor). Additionally, I'm allowing direct invocation of the function via the class instance, as this might be useful in certain scenarios (at least in my case).

This all sounds sensible to me, thank you for your work.
I will prepare a release, meanwhile, do you think I could ask you for some feedback on this unresolved PR?
https://github.com/cpvalente/stupidArtnet/pull/25


Respect "editor.parameterHints.enabled" and don't show parameter hint on "*.suggest.completeFunctionCalls"

VSCode Version: 1.47.3
OS Version: macOS

Steps to Reproduce:

Add "editor.parameterHints.enabled": false and "javascript.suggest.completeFunctionCalls": true to your settings.
Open JavaScript file and write console.log, press Tab to autocomplete. Actual behavior, parameter hints are visible even though config is false. Expected behavior, parameter hints are invisible.

/cc @mjbvz

Same happens for TypeScript.

Should the box not display at all or should "...data: any[]" just not show in case of testing it with console.log?

Hi @mjbvz I am currently attempting  to work on this issue and I have a quick question. With "editor.parameterHints.enabled" set to false and "*.suggest.completeFunctionCalls" set to true is the expected behavior to have the parentheses still be inserted but just not have the popup appear or should the parentheses not be inserted?

@andrew-maust You just need to disable parameter hints. The problem is they appear even if they are disabled.
Imagine this pseudo code:
if (config.parameterHints) { // bool
  showPopup();
} else {
  // do nothing
}

I know I fixed it. Im gonna submit a PR now.