Can't Establish a new Athena connection from dBeaver CE

Description
I am trying to set-up a new Athena connection from dBeaver CE on my Mac.  I am behind a proxy.
How can I setup the connection so I can use dBeaver to connect to Athena ?
I have added these properties under Driver Properties Tab.
Ref:https://github.com/dbeaver/dbeaver/issues/3918#issuecomment-511484596

AwsCredentialsProviderClass to com.simba.athena.amazonaws.auth.profile.ProfileCredentialsProvider
AwsCredentialsProviderArguments

When I do Test Connection I get the following error
[Simba]AthenaJDBC An error has been thrown from the AWS SDK client. Unable to execute HTTP request: Connection reset [Execution ID not available]
Unable to execute HTTP request: Connection reset
Unable to execute HTTP request: Connection reset
Connection reset
Connection reset
Thanks
DBeaver Version
dBeaver Community Edition Version <IP_ADDRESS>309260508
Operating System
macOS Ventura 13.6 (22G120)
Database and driver
DB - AWS Athena
Driver- com.simba.athena.jdbc42.Driver

Steps to reproduce
No response
Additional context
Behind a proxy

Sorry, the driver is - com.simba.athena.jdbc42.Driver

Hello @adbdkb
Did you try to configure something in the Proxy tab?

Yes, I had.  But my tab loos a little different.  it doesn't have the checkboxes you have in the above image.
This is what I get

Also, just realised where I can get more details for the error below.
[Simba][AthenaJDBC](100131) An error has been thrown from the AWS SDK client. Unable to execute HTTP request: Connection reset [Execution ID not available]   Unable to execute HTTP request: Connection reset   Unable to execute HTTP request: Connection reset     Connection reset     Connection reset
This is what I saw in the log tab for the error - if this gives any clue
java.net.SocketException: Connection reset 	at java.base/sun.nio.ch.NioSocketImpl.implRead(Unknown Source) 	at java.base/sun.nio.ch.NioSocketImpl.read(Unknown Source) 	at java.base/sun.nio.ch.NioSocketImpl$1.read(Unknown Source) 	at java.base/java.net.Socket$SocketInputStream.read(Unknown Source) 	at java.base/sun.security.ssl.SSLSocketInputRecord.read(Unknown Source) 	at java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(Unknown Source) 	at java.base/sun.security.ssl.SSLSocketInputRecord.decode(Unknown Source) 	at java.base/sun.security.ssl.SSLTransport.decode(Unknown Source) 	at java.base/sun.security.ssl.SSLSocketImpl.decode(Unknown Source) 	at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source) 	at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) 	at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) 	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:436) 	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:384) 	at com.simba.athena.amazonaws.http.conn.ssl.SdkTLSSocketFactory.connectSocket(SdkTLSSocketFactory.java:142) 	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142) 	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376) 	at jdk.internal.reflect.GeneratedMethodAccessor68.invoke(Unknown Source) 	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 	at java.base/java.lang.reflect.Method.invoke(Unknown Source) 	at com.simba.athena.amazonaws.http.conn.ClientConnectionManagerFactory$Handler.invoke(ClientConnectionManagerFactory.java:76) 	at com.simba.athena.amazonaws.http.conn.$Proxy32.connect(Unknown Source) 	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393) 	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) 	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186) 	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) 	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) 	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) 	at com.simba.athena.amazonaws.http.apache.client.impl.SdkHttpClient.execute(SdkHttpClient.java:72) 	at com.simba.athena.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1346) 	at com.simba.athena.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1157) 	at com.simba.athena.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:814) 	at com.simba.athena.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:781) 	at com.simba.athena.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:755) 	at com.simba.athena.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:715) 	at com.simba.athena.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:697) 	at com.simba.athena.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:561) 	at com.simba.athena.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:541) 	at com.simba.athena.amazonaws.services.athena.AmazonAthenaClient.doInvoke(AmazonAthenaClient.java:2570) 	at com.simba.athena.amazonaws.services.athena.AmazonAthenaClient.invoke(AmazonAthenaClient.java:2537) 	at com.simba.athena.amazonaws.services.athena.AmazonAthenaClient.invoke(AmazonAthenaClient.java:2526) 	at com.simba.athena.amazonaws.services.athena.AmazonAthenaClient.executeStartQueryExecution(AmazonAthenaClient.java:2050) 	at com.simba.athena.amazonaws.services.athena.AmazonAthenaClient.startQueryExecution(AmazonAthenaClient.java:2019) 	at com.simba.athena.athena.api.AJClient.executeQuery(Unknown Source) 	at com.simba.athena.athena.api.AJClient.checkAthenaConnection(Unknown Source) 	at com.simba.athena.athena.api.AJClient.<init>(Unknown Source) 	at com.simba.athena.athena.core.AJConnection.connect(Unknown Source) 	at com.simba.athena.jdbc.common.BaseConnectionFactory.doConnect(Unknown Source) 	at com.simba.athena.jdbc.common.AbstractDriver.connect(Unknown Source) 	at org.jkiss.dbeaver.model.impl.jdbc.JDBCDataSource.lambda$1(JDBCDataSource.java:237) 	at org.jkiss.dbeaver.model.impl.jdbc.JDBCDataSource.lambda$0(JDBCDataSource.java:250) 	at org.jkiss.dbeaver.model.impl.jdbc.JDBCDataSource.openConnection(JDBCDataSource.java:269) 	at org.jkiss.dbeaver.ext.generic.model.GenericDataSource.openConnection(GenericDataSource.java:155) 	at org.jkiss.dbeaver.model.impl.jdbc.JDBCExecutionContext.connect(JDBCExecutionContext.java:103) 	at org.jkiss.dbeaver.model.impl.jdbc.JDBCRemoteInstance.initializeMainContext(JDBCRemoteInstance.java:102) 	at org.jkiss.dbeaver.model.impl.jdbc.JDBCRemoteInstance.<init>(JDBCRemoteInstance.java:61) 	at org.jkiss.dbeaver.model.impl.jdbc.JDBCDataSource.initializeRemoteInstance(JDBCDataSource.java:123) 	at org.jkiss.dbeaver.ext.generic.model.GenericDataSource.<init>(GenericDataSource.java:120) 	at org.jkiss.dbeaver.ext.athena.model.AthenaDataSource.<init>(AthenaDataSource.java:40) 	at org.jkiss.dbeaver.ext.athena.AthenaDataSourceProvider.openDataSource(AthenaDataSourceProvider.java:57) 	at org.jkiss.dbeaver.registry.DataSourceDescriptor.openDataSource(DataSourceDescriptor.java:1278) 	at org.jkiss.dbeaver.registry.DataSourceDescriptor.connect0(DataSourceDescriptor.java:1117) 	at org.jkiss.dbeaver.registry.DataSourceDescriptor.connect(DataSourceDescriptor.java:950) 	at org.jkiss.dbeaver.runtime.jobs.ConnectJob.run(ConnectJob.java:77) 	at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105) 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

@LonwoLonwo LonwoLonwo - Any update on this?  Is there anything else I can try?
Thanks

Hi, could you try to use another port apart from 8080. Make sure is it open while you're at it.
Here is the wiki page on this matter.

Hi, I tried to read the doc, but have a question.  I am presuming the port needs to be open on the proxy server, correct?  How can I check what port is open on that server ?
Thanks

@adbdkb It depends on the OS you use on your proxy server. What OS do you use?

Operating System
macOS Ventura 13.6 (22G120)

Is your proxy configuration system-wide, or do you need to explicitly specify its settings in applications you would like to use that proxy? Can you please provide more information about your environment?

@adbdkb This seems to be a problem with the proxy itself. I've tried replicating it on our athena instance with additional proxy and wasn't able to reproduce it. Have you tried connecting to your server using other tools with the same proxy?

It's been a while since no update here. If the issue is still actual please let me know and provide additional information.


Add iam:CreateServiceLinkedRole to all IAM policies

We recently had cluster provisioning fail on the installer role generated by the rosa cli missing the iam:CreateServiceLinkedRole permission.
This can happen in brand new accounts where the AWS service linked roles have not been created by other AWS activity.
I believe we should include this on all of our IAM roles, since it is something that can be needed, if a service linked role has not already been created before in that account. At a minimum we should include it in our installer role.

We're going to address this in documentation as a pre-req rather than adding another permission to the role


Improve test failure logging and stacktrace

Is your feature request related to a problem? Please describe.
Detox stack trace logging needs to be improved. It actually got worse recently (I can’t track specific time when) - in test failure summary, you cannot see exact failure reason (e.g. matcher not found) and valuable stacktrace is one line only. There are many "runtime" trace which provides me nothing. This summary is provided in CI for failed tests, but it's not informative and you still need to go dig the build log.
example:
FAILED
Error:
    at tapDismissButton$ (/Users/builduser/buildAgent/work/5da578ee2a15ccd4/e2e/screens/stores/HappyMoment.screen.js:27:44)
    at tryCatch (/Users/builduser/buildAgent/work/5da578ee2a15ccd4/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:45:40)
    at Generator.invoke [as _invoke] (/Users/builduser/buildAgent/work/5da578ee2a15ccd4/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:274:22)
    at Generator.prototype.(anonymous function) [as next] (/Users/builduser/buildAgent/work/5da578ee2a15ccd4/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:97:21)
    at tryCatch (/Users/builduser/buildAgent/work/5da578ee2a15ccd4/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:45:40)
    at invoke (/Users/builduser/buildAgent/work/5da578ee2a15ccd4/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:135:20)
    at /Users/builduser/buildAgent/work/5da578ee2a15ccd4/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:170:11
    at new Promise (<anonymous>)
    at callInvokeWithMethodAndArg (/Users/builduser/buildAgent/work/5da578ee2a15ccd4/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:169:16)
    at AsyncIterator.enqueue (/Users/builduser/buildAgent/work/5da578ee2a15ccd4/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:192:13)
    at AsyncIterator.prototype.(anonymous function) [as next] (/Users/builduser/buildAgent/work/5da578ee2a15ccd4/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:97:21)
    at Object.exports.async (/Users/builduser/buildAgent/work/5da578ee2a15ccd4/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:219:14)

Describe the solution you'd like
In failure summary, provide clear definition of the failure and trace to where exactly issue happened - test > driver > helper functions (if any)
Describe alternatives you've considered
With Mocha we had better logging, but we switched to Jest
Additional context
Add any other context or screenshots about the feature request here.

I experienced this after switching to the jest-circus runner, but after I switched back to the jasmine runner (for Jest) I got informative test errors again.

This has been proven to be caused by jest preprocessors. By default Jest transforms whatever test code you have using babel if present.
By adding to config.json/js the following line, I have disabled the babel transformation on the test code, and got nice stack traces again.
...
    "transform": {},
...

For reference, this is how my e2e/config.json looks now:
{
    "setupFilesAfterEnv": ["./init.js"],
    "transform": {},
    "testEnvironment": "./CustomDetoxEnvironment",
    "testRunner": "jest-circus/runner",
    "testTimeout": 180000,
    "reporters": [
        "detox/runners/jest/streamlineReporter",
        ["jest-summary-reporter", {"failuresOnly": false}]
    ],
    "testResultsProcessor": "jest-teamcity-reporter",
    "verbose": true,
    "globalSetup": "./jestSetup.js",
    "globalTeardown": "./jestTeardown.js"

I am closing this issue.

@rotemmiz, @viktorijasujetaite, resolved by #2151 in 16.9.2. The transform comment also is relevant since transformations such as regenerator (for async/await) look redundant for the current versions of Node.js.


How to build recast libraries?

Hello,
how to build and install Recast as library. I dont want demo or examples. Only valid libs + devel files for other project.
Preferably without alfa build systems like premake ( pretty bad idea use ALPHA build system)

We recommend that you simply copy the directories that you need to your project. Take a look at the Integrating with your own project part of the readme.

@jakobbotsch  so recommended is a bundle in every project?
What about distribution as a system library?

Yes, that is the recommended way. However it might be possible to install it as a system library with the CMake build, see #310.
R&D has no external dependencies and is very portable so just copying the directories is easy and works out of the box on any platforms, without mucking around with build files.

GCC 8.2.1
cmake line:
/usr/bin/cmake /home/abuild/rpmbuild/BUILD/recastnavigation-1.0.0+20181016.56dbf4c/. '-GUnix Makefiles' -DCMAKE_INSTALL_PREFIX:PATH=/usr -DINCLUDE_INSTALL_DIR:PATH=/usr/include -DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc -DSHARE_INSTALL_PREFIX:PATH=/usr/share -DCMAKE_INSTALL_LIBDIR:PATH=/usr/lib64 -DCMAKE_BUILD_TYPE=RelWithDebInfo '-DCMAKE_C_FLAGS=-O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -DNDEBUG' '-DCMAKE_CXX_FLAGS=-O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -DNDEBUG' '-DCMAKE_Fortran_FLAGS=-O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -DNDEBUG' '-DCMAKE_EXE_LINKER_FLAGS=-Wl,--as-needed -Wl,--no-undefined -Wl,-z,now' -DCMAKE_MODULE_LINKER_FLAGS=-Wl,--as-needed '-DCMAKE_SHARED_LINKER_FLAGS=-Wl,--as-needed -Wl,--no-undefined -Wl,-z,now' -DLIB_SUFFIX=64 -DCMAKE_SKIP_RPATH:BOOL=ON -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DBUILD_SHARED_LIBS:BOOL=ON -DBUILD_STATIC_LIBS:BOOL=OFF -DCMAKE_COLOR_MAKEFILE:BOOL=OFF -DCMAKE_INSTALL_DO_STRIP:BOOL=OFF -DCMAKE_MODULES_INSTALL_DIR=/usr/share/cmake/Modules -DRECASTNAVIGATION_DEMO=OFF -RECASTNAVIGATION_TESTS=OFF -DRECASTNAVIGATION_EXAMPLES=OFF -DRECASTNAVIGATION_STATIC=OFF ..
always fails in Detour
9s] /home/abuild/rpmbuild/BUILD/recastnavigation-1.0.0+20181016.56dbf4c/DetourCrowd/Source/DetourProximityGrid.cpp:63: undefined reference to `dtFree(void*)'
[    9s] /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: CMakeFiles/DetourCrowd.dir/Source/DetourProximityGrid.cpp.o: in function `dtFreeProximityGrid(dtProximityGrid*)':
[    9s] /home/abuild/rpmbuild/BUILD/recastnavigation-1.0.0+20181016.56dbf4c/DetourCrowd/Source/DetourProximityGrid.cpp:39: undefined reference to `dtFree(void*)'
[    9s] collect2: error: ld returned 1 exit status
[    9s] make[2]: *** [DetourCrowd/CMakeFiles/DetourCrowd.dir/build.make:162: DetourCrowd/libDetourCrowd.so.1.0.0] Error 1
[    9s] make[2]: Leaving directory '/home/abuild/rpmbuild/BUILD/recastnavigation-1.0.0+20181016.56dbf4c/build'
[    9s] make[1]: *** [CMakeFiles/Makefile2:204: DetourCrowd/CMakeFiles/DetourCrowd.dir/all] Error 2
[   10s] [ 58%] Linking CXX shared library libDetour.so
[   10s] cd /home/abuild/rpmbuild/BUILD/recastnavigation-1.0.0+20181016.56dbf4c/build/Detour && /usr/bin/cmake -E cmake_link_script CMakeFiles/Detour.dir/link.txt --verbose=1
[   10s] /var/lib/build/ccache/bin/c++ -fPIC -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -DNDEBUG -O2 -g -DNDEBUG -Wl,--as-needed -Wl,--no-undefined -Wl,-z,now -shared -Wl,-soname,libDetour.so.1 -o libDetour.so.1.0.0 CMakeFiles/Detour.dir/Source/DetourAlloc.cpp.o CMakeFiles/Detour.dir/Source/DetourAssert.cpp.o CMakeFiles/Detour.dir/Source/DetourCommon.cpp.o CMakeFiles/Detour.dir/Source/DetourNavMesh.cpp.o CMakeFiles/Detour.dir/Source/DetourNavMeshBuilder.cpp.o CMakeFiles/Detour.dir/Source/DetourNavMeshQuery.cpp.o CMakeFiles/Detour.dir/Source/DetourNode.cpp.o
[   10s] cd /home/abuild/rpmbuild/BUILD/recastnavigation-1.0.0+20181016.56dbf4c/build/Detour && /usr/bin/cmake -E cmake_symlink_library libDetour.so.1.0.0 libDetour.so.1 libDetour.so
[   10s] make[2]: Leaving directory '/home/abuild/rpmbuild/BUILD/recastnavigation-1.0.0+20181016.56dbf4c/build'
[   10s] [ 58%] Built target Detour
[   10s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/recastnavigation-1.0.0+20181016.56dbf4c/build'
[   10s] make: *** [Makefile:144: all] Error 2
[   10s] error: Bad exit status from /var/tmp/rpm-tmp.4ypIep (%build)

cc @elsid, any thoughts?

The reason is absence of dependecies between libraries. Linker with -Wl,--no-undefined flags checks for existence of all symbols in shared library. Without dependecies it couldn't find them. Made a pr to fix it.


Passwords?

Just to confirm, it doesn't show the credentials (passwords), just the owner, right?
Thanks for the work and the chat.

Hi! This project hasn't been updated for a while now :). We've focused efforts on https://github.com/mbrg/power-pwn that can find the actual creds.
Zapier connections won't give the actual creds. But you can use the connection object to perform API calls using those credentials.


SVG elements with children

Issue
hyperx is not allowing many SVG elements to have animation-related tags embedded in them.
Both of these examples reproduce the issue:
const rectNode = html`<svg><rect>
        <animate attributeType="CSS" attributeName="opacity"
                from="1" to="0" dur="5s" repeatCount="indefinite" />
        </rect></svg>`

//Markup by Aurer on Codepen: http://codepen.io/aurer/pen/jEGbA
const spinnerNode = html`
        <div class="loader loader--style1" title="0">
        <svg version="1.1" id="loader-1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
        width="40px" height="40px" viewBox="0 0 40 40" enable-background="new 0 0 40 40" xml:space="preserve">
            <path opacity="0.2" fill="#000" d="M20.201,5.169c-8.254,0-14.946,6.692-14.946,14.946c0,8.255,6.692,14.946,14.946,14.946
                s14.946-6.691,14.946-14.946C35.146,11.861,28.455,5.169,20.201,5.169z M20.201,31.749c-6.425,0-11.634-5.208-11.634-11.634
                c0-6.425,5.209-11.634,11.634-11.634c6.425,0,11.633,5.209,11.633,11.634C31.834,26.541,26.626,31.749,20.201,31.749z"/>
            <path fill="#000" d="M26.013,10.047l1.654-2.866c-2.198-1.272-4.743-2.012-7.466-2.012h0v3.312h0
                C22.32,8.481,24.301,9.057,26.013,10.047z">
                <animateTransform attributeType="xml"
                attributeName="transform"
                    type="rotate"
                    from="0 20 20"
                    to="360 20 20"
                    dur="0.5s"
                    repeatCount="indefinite"/>
            </path>
        </svg>
        </div>`

In the 1st example, Hyperx is treating the  and  tags as sibling elements.
In the 2nd example, Hyperx is treating the 2nd  and  tags as siblings.
It seems to be a fairly common technique for animating SVGs, based on Codepen examples and articles like this: https://css-tricks.com/guide-svg-animations-smil/
Is this something that could be allowed?

I've started running this through the debugger and there is definitely a problem in the parse() function.
I've been able to reduce the minimum markup to make this fail:
const input = `<svg>
      <use></use>
    </svg>`

I'm still investigating but it seems to have something to do with using a tag that can be self closing but has a closing tag provided.

further reduced the minimum case; this fails too:
const input = `<svg><use></use>  </svg>`

I think this is not a problem with parse(), it seems to be in the handling of the generated tokens, because the generated tokens seems right (I was mistaken in my last comment because I misunderstood the token types.)

@SkaterDad I've found the exact bug!
When we iterate over tokens and an encounter a tag that is in a list of ones we know can be self closing (rect, use, path, etc.) we immediately assume that it is closed, and that an explicit close tag will never appear in the token list.
Then later, if we encounter that unexpected closing tag (</use>, </rect>, etc.) we close again. So basically these elements get put one level too high in the stack. here it is illustrated.
input string:
<svg>
   <use></use>
</svg>

expected tree structure:
  svg
      use

actual tree structure:
  svg
  use

That's why these html strings are throwing the multiple root elements must be wrapped in an enclosing tag error;  due to this bug we end up with a tree that has more than one root node, and hyperx is designed to allow only one root node.
I think I can develop a fix for this, where we explicitly check to see if a self-closing tag does indeed close itself, rather than assume that based on the name of the tag.  Whatever strategy we pursue to fix this would require a major version bump because it would definitely change the behavior of the parser. @goto-bus-stop what are your thoughts on this? Is this something you'd be keen to accept a PR for?

@goto-bus-stop got a fix for this! I'd love some feedback.

I'd really like to get this fix merged, if this is something we're open to.
hyperx underpins some really high value frameworks, so I'm keen to see some of these foundational problems get resolved.
I'm also happy to help with a bit of maintainership if that would be useful.


V2 - React Router v7

V2 Release for React Router 7
Description
This is a "soft" breaking change: @remix-run dependency becomes react-router.
No API changes.

waiting for https://github.com/sergiodxa/remix-hono/pull/297

Hi @rphlmr thank-you for react-router-hono-server! It answered some questions I had. I have worked with react-router a ton of times on SPA's but not much with remix. Earlier today I upgraded an SPA to React Router v7 today with all future flags enabled and it was painless so I figured it was a good time to learn a little more about the feasibility to use v7 in a new full stack project.
Suggestion to unblock and improve maintainability
I thought I'd share a first thought I had when I reviewed the code in this package and remix-hono, before I even looked at the issues and saw this one:

"if react-router-hono-server is only using remix-hono/handler, and that's only a handful of lines of code, why wouldn't the author directly incorporate those crucial lines directly in react-router-hono-server?

Reference: https://github.com/sergiodxa/remix-hono/blob/main/src/handler.ts
I think adding yet another set of third-party dependencies, maintainers, etc. adds unnecessary risks for what amount to a few lines of code, especially where those lines are so critical for this package to succeed in its purpose. I think that this early PR being blocked is an early warning about future challenges to come.
The collection of exports in remix-hono while insightful are all very succinct and ripe to copy as needed.
By all means I agree to give credit where credit is due for remix-hono and sergiodxa in the README, along with mention of some of the other exports that might potentially be useful to some :) Thanks again for creating this repo :)

Thank @firxworx!
You are right, it could be simpler to fork this part since it is really a basic binding and the core part of this library.
I'm also a maintainer of remix-hono and I started to re-export it. Then I realized that it would be better to compound them instead of mixing them, so I rolled back.
Let's do this, of course, with credits.


Removing an extra line break in line 66.

Checklist:

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the main branch of freeCodeCamp.
[ ] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #XXXXX

Thank You
Thank you for submitting this pull request. However, we are unable to accept your contribution at this time.
Reason: The additional line break in this file is required, as noted in the comment on line 63.
We welcome future contributions from you. If you have not done so, we encourage you to read our contributing guidelines.


chore: specify highlight.js version

Describe your changes
This PR updates sets the version to ^11.5.1.
We were locked at 11.0.1 because it was specified in package-lock.json and we using * as the version in package.json.
Additional context
This should address some of this issues in https://github.com/StackExchange/Stacks-Editor/issues/21.
Fixed with this PR

Triple asterisks don't terminate

Not fixed with this PR

Non-terminating italics
Escaped asterisks
Multi-line asterisks

ref: https://github.com/highlightjs/highlight.js/issues/3519


[UI] Fix wrong dialogs for process definition's version info

We should use process_definition.update_time instead of create time
to make more sense.
close: #7660

@songjianet @labbomb PTAL, I notice that we have ui-next module, should I also change ui-next module code?

@songjianet @labbomb PTAL, I notice that we have ui-next module, should I also change ui-next module code?

Yes, the refactored project will be developed with reference to the existing project completely, and if there are minor problems, it will be repaired in the refactored project.

But I could not find any content like create time or .createTime in UI-NEXT module. So I do not know which line should I change. Could you give some hints for me? @songjianet

But I could not find any content like create time or .createTime in UI-NEXT module. So I do not know which line should I change. Could you give some hints for me? @songjianet

There is no formal development of business functions yet.

Codecov Report

Merging #7662 (311ecd6) into dev (b2e2de7) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #7662      +/-   ##
============================================
- Coverage     41.17%   41.14%   -0.04%
+ Complexity     3668     3664       -4
============================================
  Files           641      641
  Lines         26553    26553
  Branches       2971     2971
============================================
- Hits          10934    10924      -10
- Misses        14588    14599      +11
+ Partials       1031     1030       -1

Impacted Files
Coverage Δ

...he/dolphinscheduler/common/enums/SqoopJobType.java
0.00% <0.00%> (-88.89%)
:arrow_down:

...inscheduler/common/task/sqoop/SqoopParameters.java
74.00% <0.00%> (-2.00%)
:arrow_down:

...dolphinscheduler/remote/future/ResponseFuture.java
81.96% <0.00%> (-1.64%)
:arrow_down:

Continue to review full report at Codecov.

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

@songjianet Ok, I got the point, so do you have time review this patch？

@songjianet Ok, I got the point, so do you have time review this patch？

yes.


Images do not appear using this theme

Images do not appear using this theme
I genuinely love this theme! It's perfect for documentation and has a dark option so I 'm really happy with how it presents everything except...images don't work. This is especially a problem for a theme intended for guides and/or documentation
The images work fine on github, but do not show up in the github page
for example in the example websites:
your website has this issue

my website which is a guide
In github:

In github pages:

I would really appreciate if this was fixed because this is my only problem with what would be an amazing theme otherwise.
here's a link to the source code of the website in case I've done something wrong

Fixed this by dragging images onto the .md and having them as those instead


Error: Class incorrectly implements interface with no reason specified

I'm getting the following compiler error using TypeScript 1.4.1:
error TS2420: Class 'WorkerFS' incorrectly implements interface 'FileSystem'.

Unfortunately, TypeScript does not tell me what property or method is incorrectly implemented/specified, if any. Is this a bug in the compiler?
The relevant code can be checked out of the webworker branch of my BrowserFS repository.
Compiler command:
tsc --module amd src/backend/workerfs.ts

If that's too much code to work through, I can see if I can work it into a smaller test case...
Thanks in advance!

It should certainly be telling you the offending member.

Offhandedly, it seems like you're missing diskSpace, you may have misspelled supportsSync as supportsSynch in file_system (or vice versa).
A couple of the *Sync methods are missing, for which you'll need to implement in WorkerFS and throw an exception in them, or make them optional in the FileSystem interface.
There might be more but that's it at a glance. If this fixes your problem, don't close the issue.

Related to #933 perhaps?

Here's an example of a way to reproduce the issue (might not be the same as the linked repo, but illustrates the point):
interface FileSystem {
  read: number;
}

function fn(s: WorkerFS): void;
function fn(s: FileSystem): void;
function fn(s: FileSystem|WorkerFS) { }

class WorkerFS implements FileSystem {
  read: string;
}

This emits only the following error:
a.ts(10,7): error TS2420: Class 'WorkerFS' incorrectly implements interface 'FileSystem'.

Wow, didn't take long for all of you to look into this! Awesome.

...you may have misspelled supportsSync as supportsSynch in file_system (or vice versa).

Yup, that was the only thing I was missing. The diskSpace and *Sync methods have default implementations in the BaseFileSystem class that I am extending. (It's supportsSynch to disambiguate between synchronous file system operations and the sync method.)
Hopefully I won't encounter this bug again until it's fixed, since it's rather frustrating to have an unactionable error when you have a lot of methods in an interface. Best of luck with the fix!

I'm still having this problem, even though it's marked as fixed.
Please see Gist: https://gist.github.com/hessryanm/177b0cada8c51516371e
Error is: models/Card.ts(13,14): error TS2420: Class 'Card' incorrectly implements interface 'ICard'.

@hessryanm filed #5757 to track this issue.


fix(lightningcss): search for assets with correct base path

Description
Closes https://github.com/vitejs/vite/issues/16457

still needs a test case

I tried with ok.png, however this file is too large and will not be inlined. If you not using inlined file looks good to you, I can make the changes.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Hiroshi Ogawa @.>
Sent: Friday, August 9, 2024 7:42:15 PM
To: vitejs/vite @.>
Cc: Meng, Shaoyu @.>; Author @.>
Subject: Re: [vitejs/vite] fix(lightningcss): search for assets with correct base path (PR #17856)
@hi-ogawa commented on this pull request.

In playground/css-lightningcss/nested/nested.csshttps://urldefense.com/v3/__https://github.com/vitejs/vite/pull/17856*discussion_r1712498445__;Iw!!DZ3fjg!86HE1qG0hFYwh7kLcgKwhvsQkYPnNCbV4Aq6fOY3CUS_VtLLx3HmqZQKDOyndg1G3LwbRgD4T38E4nW8_eORzhKBI7w$:

@@ -0,0 +1,3 @@
+.nested-css-relative-asset {

background-image: url('../test.avif');

Fix looks good to me, but this test doesn't have any visual feedback, so I was a little confused.
I think doing it similar to .external would be nicer?
⬇ Suggested change

background-image: url('../test.avif');

background-image: url('../ok.png');
width: 50px;
height: 50px;

—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/vitejs/vite/pull/17856*pullrequestreview-2231300420__;Iw!!DZ3fjg!86HE1qG0hFYwh7kLcgKwhvsQkYPnNCbV4Aq6fOY3CUS_VtLLx3HmqZQKDOyndg1G3LwbRgD4T38E4nW8_eOREB9b7Qc$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AJHAEC3WTIRMYD5PJU2HVB3ZQV4YPAVCNFSM6AAAAABMJJMA4CVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDEMZRGMYDANBSGA__;!!DZ3fjg!86HE1qG0hFYwh7kLcgKwhvsQkYPnNCbV4Aq6fOY3CUS_VtLLx3HmqZQKDOyndg1G3LwbRgD4T38E4nW8_eORDQN0Bbc$.
You are receiving this because you authored the thread.Message ID: @.***>

I tried with ok.png, however this file is too large and will not be inlined. If you not using inlined file looks good to you, I can make the changes.

Is there any reason inlined asset (base64 data url) is required to demonstrate the fix? I thought non-inlined asset is also broken due to the same bug.

Not really, I previously just reused the failed case from the original issue. I have made the changes according to your suggestions.


Bifrost database is growing with every sync

We have written an internal tool to automatically sync cookbooks from a git repository to Chef Infra Server.
It performs delta syncs every minute (based on what changes in the git repo) and then perform a full sync nightly (as a backstop in case the delta syncs missed something).
What we're seeing is that the bifrost database grows by about 60MB every full sync.
Normally I wouldn't trip about this, but we just recently migrated to a new Chef Infra Server using knife-ec-backup and the bifrost database went from 140GB to 600MB. Now after just a few weeks the bifrost database is 1.39GB.
We originally did the migration because calls to bifrost was the bottleneck in Chef Infra Server being able to serve requests because the authz calls were taking up-to 6 seconds at times.
We're running chef-server-core v14.5.29 on RHEL 7.
Support Notes
This issue is down to multiple cookbook updates, however, this causes a lot of Bifrost data.
We initially had chef-server-ctl cleanup-bifrost created for ticket https://getchef.zendesk.com/agent/tickets/6991
This however does extend to all of the tables in the bifrost DB,
This bug is to resolve that.
To Reproduce
with a large bifrost DB, mainly with lots of data in the auth_object, object_acl_actor and object_acl_group tables, run chef-server-ctl cleanup-bifrost
Expected behavior
This should help in the cleardown of these older and orphaned items
Actual behavior
It does not extend to tidy up these tables in the DB
Additional context
https://github.com/chef/chef-server/blob/main/src/chef-server-ctl/plugins/cleanup_bifrost.rb

I think this may have been resolved by https://github.com/chef/chef-server/pull/3275, but I would ask @vinay-satish to be sure.

Closing, release https://docs.chef.io/release_notes_server/#14.16.19 includes the fix for the issue.


What to change in secondary_code argument for mode --sentiment if I want to generate negative sentiment text?

@akhileshgotmare I was trying to generate negative sentiment text instead of default one..How can I do that?
Thanks!

One more thing I wanna ask what is the difference between gen_type --gpt-2 CCLM and gen_type --gedi? Both looks similar as both are conditioned on secondary_code and mode like sentiment,detoxify or topic..
Thanks!

Thanks!

Hi! To answer your questions:

Sentiment doesn't use a secondary code, it only uses --code_desired and --code_undesired, but these are set automatically if you run the shell script.

To get negative sentiment, run_generation.sh and set --mode sentiment. You'll be prompted with the opportunity to change to negative sentiment. When this happens, type n and press enter, and then you can give the model your prompt.

--gpt2 and cclm were baselines for --gedi. --gpt2 just generates from OpenAI's gpt-2 language model using greedy decoding and a repetition penalty (it will be the same regardless of attribute codes). --cclm generates directly from a language model directly conditioned on an attribute variable. --gedi is the method described in our paper where we guide generation from gpt-2 using a language model that conditions on an attribute variable. Both --gedi and --cclm can control generation to an extent, but --gedi tends to give much more interesting and diverse responses for different prompts.

If you want to train your own GeDi, it's advisable to train the whole network. Last layer only training would not work as well, and would require some modification to the codebase.

@benkrause Thanks for your valuable responses. I wanna ask one more thing from my last question.. How should I make my labelled dataset because as per your default dataset of AG News, there is four topics and for each sentence one topic is assigned, I also have to make dataset of four topics or I can have more or less than four topics? If I can change number of topics, then which python file or script I should update to change number of topics of a dataset?
Another thing I wanna ask, what is the need of second column in train and test files of AG News as second column sentences are of length 4 to 5 words which I couldn't understand why is it necessary to have?

One last question I wanna ask how can I label each sentence to specific topic as I have just preprocessed text file of sentences? Till now , I have applied LDA to classify sentences but for each sentence I didn't get broad topics like politics,crime or sports instead I am getting set to topics for each sentence..
Thanks!

The second column of AG news is just the article titles, we don't actually use these. Our scripts only process the first and third columns. It assumes the topic labels are in the first column (and start at 1), and the text is in the third column.
If you want to train on your own topic dataset with minimal changes, first set up new csv files in the same format as the AG news train and test csv files. So topic label IDs in the first column, second column can be blank since we ignore it anyway, third column has text.

If you want to avoid having to specify paths in the processing and training scripts, you could save your csv files with the same names in the same directory that we download to (data/AG-news/train.csv and data/AG-news/test.csv for the train and test splits). This would be the simplest, but would overwrite AG-news.

Alternatively, you could save it in a new directory if you replace the paths in proc_data.py and specify the directory in the --data_dir argument in scripts/run_training.sh.

Once you have replaced the AG-news train and test csv files with your own, you can process them into a dataset suitable for GeDi with python proc_data.py. To change the topics, you will have to change the list on line 16 in proc_data.py, which currently specifies the topic names used for AG-news. Make sure the list corresponds to the topic labels you saved in the csv files, so the first topic in the list should correspond to the label "1", second topic should correspond to the label "2", etc. You can potentially have as many topics as you want, as long as you have data and numbered labels for these topics in your csv file.
As for your last question on how to use unlabeled data, that is something we haven't explored yet, all our experiments so far have used labeled datasets. I will mention that GeDi can often generate to topics it hasn't seen during training. For instance, if you run our topic GeDi trained on AG-news (which was trained on "world", "sports", "business" and "science"), and give it a secondary code of "crime", depending on the prompt, it should sometimes be able to generate text relating to crime.
Hope this helps!

@benkrause Thanks for your valuable response, it really helped me a lot.


Always giving z.any() in output

Passing the converted JSON Schema from the sister package to this gives out z.any() always. attaching a screenshot which tries to convert the example from https://www.npmjs.com/package/zod-to-json-schema directly on demo app, it produces the same result.

Fixed in 1.0.0


regression: unicode encoding broke?

冒险村传说 for some reason appears as å†’é™©æ‘ä¼ è¯´

ASF / Windows console host issue, not ASFui.

Fixed in ASF https://github.com/JustArchiNET/ArchiSteamFarm/commit/029c62590a47a53d63f77fd62ee7b568059cffb4


Fix typo

There is _url in the property name as Application Insights resource properties.
However, when I check the schema at the following site, it looks to me that url is correct.
https://dev.applicationinsights.io/apiexplorer/querySchema?appId=DEMO_APP&apiKey=DEMO_KEY

@changeworld : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Correct unmutated/unused variable warnings when building SDK

Describe the bug
When building the SDK, the following warnings are received:
/Users/jbelkins/Code/Xcode/aws-sdk-swift/Sources/Services/AWSWAFV2/Sources/AWSWAFV2/Models.swift:12427:13: warning: variable 'value' was never mutated; consider changing to 'let' constant
12425 |     static func read(from reader: SmithyJSON.Reader) throws -> WAFV2ClientTypes.NotStatement {
12426 |         guard reader.hasContent else { throw SmithyReadWrite.ReaderError.requiredValueNotPresent }
12427 |         var value = WAFV2ClientTypes.NotStatement()
      |             `- warning: variable 'value' was never mutated; consider changing to 'let' constant
12428 |         value.statement = try reader["Statement"].readIfPresent(with: WAFV2ClientTypes.Statement.read(from:))
12429 |         return value
/Users/jbelkins/Code/Xcode/aws-sdk-swift/Sources/Services/AWSQBusiness/Sources/AWSQBusiness/Models.swift:9946:39: warning: immutable value 'value' was never used; consider replacing with '_' or removing it
 9944 |                 try writer["payloadFieldNameSeparator"].write(value.payloadFieldNameSeparator, with: SmithyReadWrite.WritingClosures.writeString(value:to:))
 9945 |                 payload = try writer.data()
 9946 |             case .endofinputevent(let value):
      |                                       `- warning: immutable value 'value' was never used; consider replacing with '_' or removing it
 9947 |                 headers.append(.init(name: ":event-type", value: .string("endOfInputEvent")))
 9948 |             case .authchallengeresponseevent(let value):

Correct codegen so that these warnings are not received.
Expected Behavior
SDK should build without warnings.
Current Behavior
SDK builds with the warnings listed above.
Reproduction Steps
Build the AWSWAFV2 and AWSQBusiness services
Observe the compiler warnings
Possible Solution
No response
Additional Information/Context
No response
AWS SWIFT SDK version used
1.0.3 / latest
Compiler and Version used
Xcode 16.0
Operating System and version
macOS 14

In the case of AWSWAFV2 above, the cause is that the property being modified is @Indirect:
    public struct NotStatement: Swift.Sendable {
        /// The statement to negate. You can use any statement that can be nested.
        /// This member is required.
        @Indirect public var statement: WAFV2ClientTypes.Statement?

        public init(
            statement: WAFV2ClientTypes.Statement? = nil
        )
        {
            self.statement = statement
        }
    }

In the case of AWSQBusiness, the value is a struct with no members that is being written to an event stream.
    public struct EndOfInputEvent: Swift.Sendable {

        public init() { }
    }

The generated code only sends an :event-type in this event message:
 headers.append(.init(name: ":event-type", value: .string("endOfInputEvent")))

It is worth investigation to see if this creates a valid message on the event stream.

The second of these is fixed here:
https://github.com/smithy-lang/smithy-swift/pull/839


[GlobalFunctions] Codeunit 31020 "Purchase-Post Advances"

Please remove local for functions
local procedure PreparePmtJnlLine(var GenJnlLine: Record "Gen. Journal Line"; PurchInvHeader: Record "Purch. Inv. Header")

local procedure PrepareGenJnlLine(var GenJnlLine: Record "Gen. Journal Line"; PurchInvHeader: Record "Purch. Inv. Header")

local procedure SetCurrencyPrecision(CurrencyCode: Code[10])

local procedure CalcLinkedPmtAmountToApplyTmp(PurchAdvanceLetterLine: Record "Purch. Advance Letter Line"; TotalAmountToApply: Decimal; var VendLedgEntry: Record "Vendor Ledger Entry"; var VendLedgEntryLink: Record "Vendor Ledger Entry"; var AdvanceLink: Record "Advance Link")

local procedure CalcVATToDeduct(PurchAdvanceLetterLine: Record "Purch. Advance Letter Line"; var TotalBase: Decimal; var TotalAmount: Decimal; var TotalBaseLCY: Decimal; var TotalAmountLCY: Decimal; VendEntryNo: Integer)

@AlexanderYakunin - we need any reaction.
It is blocking our business and we need to resolve it as soon as possible.
Thanks
Jiří Bureš
CEO

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.


GH-3528 remove deprecated FederationSail and switch Console to FedX

GitHub issue resolved: #3528
Briefly describe the changes proposed in this PR:

remove deprecated federation sail and related unit/compliance tests
fix various poms
replace its use in the console by FedX

PR Author Checklist (see the contributor guidelines for more details):

[ ] my pull request is self-contained
[ ] I've added tests for the changes I made
[ ] I've applied code formatting (you can use mvn process-resources to format from the command line)
[ ] I've squashed my commits where necessary
[ ] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

@aschwarte10 you should be able to run the console directly from Eclipse, just by running Console.java as a java app.


Feature/exam tests combined

merged exam changes tested

new release of chaincode break current development status anyways - at least this PR fixes some of the issues


Offset canvas helper doesn't have the open/ close methods

After initializing the helper, and getting the off-canvas component, the methods described in the docs (open/ close) seems to not be available.

Fixed for v2.5.0


Error:Execution failed for task ':mobile:compileDebugJavaWithJavac'. > java.lang.NoSuchMethodError: butterknife.internal.ListenerClass.remover()Ljava/lang/String;

Error:Execution failed for task ':mobile:compileDebugJavaWithJavac'.

java.lang.NoSuchMethodError: butterknife.internal.ListenerClass.remover()Ljava/lang/String;  what this i got i not possible to fix

You are using different versions for the 'butterknife' and 'butterknife-compiler' artifacts. These are only guaranteed to work with the same version.


Documentation for Interface

One of the arguments for the __init__() function of the Interface class is the dripline_config object.  While the available parameters can be determined with some work (e.g. looking at the final config output when running dl-agent, or looking in dl-cpp::dripline_config), we should instead add some documentation somewhere about what values can be used.
I'm not sure this is the right place for it, but I'm leaving this issue here because the Interface class is an obvious place where this would be useful to a dl-python client.  However, this object configures dl-cpp::core, so maybe the documentation belongs in dl-cpp with links from other places.

Yeah I think that's right. The pattern is to accept a config object without parsing/constructing that object so that if dl-cpp::core ever changes what's in the config, that is transparent here. We should at least link out to the dl-cpp build results. For bonus points the sphinx autodoc could probably extract that unit from the doxygen XML and populate the object right in the dripline python docs. ... that sounds super slick, but I dunno who/when there'll be time to do it.

This is taken care of in the auth branch.


Menu Item to load custom blocks

Can a menu item be added for loading/unloading the custom blocks, such as the grove blocks?
Maybe as a sub item within the preferences or under a view menu?
Thanks.

The Grove blocks and the functionality to add additional blocks (specifically extending things like types, additional rules, warnings, and things like that) are not yet ready, which is the reason a menu item hasn't been added yet.
If open the development tools and execute in the javascript console Ardublockly.openExtraCategoriesSelect() it should open a modal window allowing you load the current blocks.

I understand.  I have been adding the Ardublockly.openExtraCategoriesSelect() line to the ardublockly.js file around line 34 so it opens at first run.
Quick question, are the json files for the additional blocks auto generated?  If not, where would I find information on how to format them?

Thats the thing, it hasn't really been defined. In the future the file /blocks/blocks_data.json will be autogenerated (not really to be kept in the repository, but the json itself would be autogenerated by the server on a specific URL) to combine the data from all the individual blocks_config.json files from each block subfolder.

I understood about the future autogeneration of the  /blocks/blocks_data.json and that this is an experimental and not yet developed area of the program.
I was looking at the format  and function of the individual blocks_config.json files with a lo of novice confusion.  The format seems different than what the factory produces, and I was not sure where to find the details of what I actually needed to put in there and the format.

Yeah, the factory in Ardublockly hasn't been modified yet, so it produces "vanilla" blockly blocks.
The details of how to create new blocks is meant to go into the wiki (which is also packed as static documentation with the Ardublockly downloads). At least one page with a general description of what is required to add new blocks still needs to be created, and then the "API" to extend Ardublockly should be defined here: https://github.com/carlosperate/ardublockly/wiki/Create-Blocks-~-Extending-Ardublockly But it does not really contain useful information yet, as this is likely to change very soon as I keep exploring the idea.


SWAMP_DRAGON_HEARTBEAT_ENABLED breaks onlineCount

Enable SWAMP_DRAGON_HEARTBEAT_ENABLED and set SWAMP_DRAGON_HEARTBEAT_FREQUENCY
Open two connections (two users connecting to websockets)
Close one connection (close that user's tab)
Run

notifications.onlineCount(function (count) {
    console.log(count);
});

We expect this to be 1. But it is 2. Run the same test with HEARTBEAT disabled and we do get 1.
I was trying to debug by inspecting the user_manager. I did some print statements on add_user and saw the result increments on each HEARTBEAT. Perhaps related? Sorry I don't really know how the user_manager is supposed to be working.

That's interesting, the heartbeat needs to be enabled for the online count to correct it self in case of a skew.
Have you tried this using different browsers rather than tabs?
You can't really be signed in as two different users in the same browser (it will overwrite the bookie the next time you sign in)

I think I have it figured out. Let me know if you have questions about my fix. In the process I got to learn about using redis for more than just cache and message queues :)

Redis is amazing!
So much more than just a KV store.
I'm currently traveling but once I'm back I will review the code and merge it


nchat: 3.67 -> 5.2.11, move to by-name, add luftmensch-luftmensch to maintainers

Description of changes
Update to the latest version.

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This should be merged only after confirmation that all build checks pass.

This seems to fail because the tests on darwin are not working as expected. For now, I'll disable the tests to see if everything working as expected. If someone has a darwin machine to test if this PR is working it would be appreciated.

I can confirm that the OPENSSL_ROOT_DIR was the problem for the darwin build. I've also tested this about an hour ago and the build worked as expected.

Result of nixpkgs-review pr 345606 run on x86_64-darwin 1

1 package built:

nchat

Doesn't work for me on darwin:
[nix-shell:~/.cache/nixpkgs-review/pr-345606]$ results/nchat/bin/nchat
Failed to load /nix/store/f80r6rnllkdkfrw9sar1vhr13ml5lv08-nchat-5.2.11/bin/..//nix/store/f80r6rnllkdkfrw9sar1vhr13ml5lv08-nchat-5.2.11/lib/libtgchat.dylib, skipping profile.
Protocol Telegram not supported
No profiles setup, exiting.

The error also occurs on Linux so is not darwin specific.

Fixed the import error and squashed everything into a single commit.


Add feature for Exporter Interface(GCS, S3, Kafka and etc)

What problem does your feature solve?
Reading the code for exporting the cmds, it only supports GCS for now. Since there are no export option interface, changing the export option for instance to S3 or to Kafka, or wanting to add a new feature has to change a lot of files and code.
What would you like to see?
I will hope the exporting func are all abstracted into export and by default it will send the data to GCS, and we can start building S3, Kafka, Postgres exporters one by one.
What alternatives are there?
Not for now

@jensenity I agree this is a good feature. Once we are finished with the Protocol 20 testnet release, we will look into updating the code to an export interface versus the tight coupling with GCS today.

Added flags and interface for choosing where to upload data
https://github.com/stellar/stellar-etl/blob/master/internal/utils/main.go#L253-L259


Version updates in module poms are not covered by git add

I have a multi module project where some of the modules define versions themselves. The versions are updated but the POM files seem not to become part of the final git commit.
I will try to create a test scenario/test case for this as soon as my time permits.

Thanks for reporting.

During Cyberland Hacktoberfest event, we could reproduce it with JGit provider (only manually)

Root cause: JGit Provider only add root pom.xml because of line https://github.com/georgberky/dependency-update-maven-plugin/blob/122ce217d3f552516378f1f2c2f32272b401d8c5/src/main/kotlin/io/github/georgberky/maven/plugins/depsupdate/UpdateMojo.kt#L58
Native git provider uses it as pattern, but JGit Provider as file name.


1.2 release not deployed on pypi

The version number in the last release has not been updated to 1.2, so the deployment of the release has been made with the wrong version (namely 1.1.2.dev0. I think this could be fixed with a correctly versioned 1.2.1 release.

Done.


📘 doc: typo in plugin example

Sorry for the slow response, I have just recovered from COVID.
Btw, LGTM too :)


mmcv version

Hello FAST Team
many thanks for your great job
my question is, what is the proper version of mmcv pakage for torch 1.1.0  and where can I download it?
Thanks in advance.

Hi, you can try pip install mmcv.
We only use mmcv to load configs, so most versions of mmcv are compatible.


hmac panic on mac os x in 4.34.0_1

What version of V2Ray are you using?
4.34.0_1 (brew version)
What's your scenario of using V2Ray?
Vmess websocket
What problems have you encountered?
it's not working and initiating at all
Please attach error logs here
V2Ray 4.34.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.16 darwin/amd64)
A unified platform for anti-censorship.
2021/03/06 20:46:38 [Info] v2ray.com/core/main/jsonem: Reading config: /usr/local/etc/v2ray/config.json
panic: crypto/hmac: hash generation function does not produce unique values

goroutine 134 [running]:
crypto/hmac.New(0xc002ee6c60, 0xc000408000, 0x18, 0x18, 0x18, 0x18)
	crypto/hmac/hmac.go:143 +0x370
v2ray.com/core/proxy/vmess/aead.KDF(0xc000400030, 0x10, 0x10, 0xc002ee6e20, 0x1, 0x1, 0xc002e66280, 0x1a286b8, 0xc00008fd60)
	v2ray.com/core/proxy/vmess/aead/kdf.go:13 +0x12f
v2ray.com/core/proxy/vmess/aead.KDF16(...)
	v2ray.com/core/proxy/vmess/aead/kdf.go:22
v2ray.com/core/proxy/vmess/encoding.(*ClientSession).DecodeResponseHeader(0xc000400000, 0x1b00b20, 0xc001ffa360, 0x0, 0x0, 0x0)
	v2ray.com/core/proxy/vmess/encoding/client.go:195 +0xd6
v2ray.com/core/proxy/vmess/outbound.(*Handler).Process.func3(0x0, 0x0)
	v2ray.com/core/proxy/vmess/outbound/outbound.go:161 +0x16b
v2ray.com/core/common/task.OnSuccess.func1(0x0, 0x0)
	v2ray.com/core/common/task/task.go:12 +0x2f
v2ray.com/core/common/task.Run.func1(0xc001ff60a8, 0xc000012600, 0xc001ff8330)
	v2ray.com/core/common/task/task.go:28 +0x2b
created by v2ray.com/core/common/task.Run
	v2ray.com/core/common/task/task.go:27 +0x152
panic: crypto/hmac: hash generation function does not produce unique values

goroutine 119 [running]:
crypto/hmac.New(0xc002eeac60, 0xc000196e28, 0x18, 0x18, 0x18, 0x18)
	crypto/hmac/hmac.go:143 +0x370
v2ray.com/core/proxy/vmess/aead.KDF(0xc0008d4030, 0x10, 0x10, 0xc002eeae20, 0x1, 0x1, 0xc0008aa048, 0x0, 0x0)
	v2ray.com/core/proxy/vmess/aead/kdf.go:13 +0x12f
v2ray.com/core/proxy/vmess/aead.KDF16(...)
	v2ray.com/core/proxy/vmess/aead/kdf.go:22
v2ray.com/core/proxy/vmess/encoding.(*ClientSession).DecodeResponseHeader(0xc0008d4000, 0x1b00b20, 0xc0008ac3c0, 0x0, 0x0, 0x0)
	v2ray.com/core/proxy/vmess/encoding/client.go:195 +0xd6
v2ray.com/core/proxy/vmess/outbound.(*Handler).Process.func3(0x0, 0x0)
	v2ray.com/core/proxy/vmess/outbound/outbound.go:161 +0x16b
v2ray.com/core/common/task.OnSuccess.func1(0x0, 0x0)
	v2ray.com/core/common/task/task.go:12 +0x2f
v2ray.com/core/common/task.Run.func1(0xc0008a8088, 0xc0008b25a0, 0xc0008aa240)
	v2ray.com/core/common/task/task.go:28 +0x2b
created by v2ray.com/core/common/task.Run
	v2ray.com/core/common/task/task.go:27 +0x152

This is a known issue when building V2Ray with Go v1.16, that has been fixed in V2Ray v4.35.0+. Please wait for it to be released and updated on Homebrew. Or you can download pre-built binary from https://github.com/v2fly/v2ray-core/releases for now.

V2Ray in Homebrew has been updated to the latest v4.35.1


Update to the latest build conventions and workflows

& update Gradle.
& run build & tests in parallel
Reviewer checklist

[ ] Read the contributing guide
[ ] PR should be motivated, i.e. what does it fix, why, and if relevant, how
[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Downgrading to Gradle 7.6.1 due to https://github.com/gradle/gradle/issues/24458

Downgrade to Gradle 7.6.1
due to https://github.com/gradle/gradle/issues/24458


Update authentication-custom.md

The JSON definition for using a custom OpenID Connect provider is incorrect and will not work properly.

Changed secretSettingName to clientSecretSettingName property

Ref : https://www.aaron-powell.com/posts/2021-05-13-using-auth0-with-static-web-apps/
It seems to have been fixed in the following commit, but a merge error prevented it from being imported correctly.
https://github.com/MicrosoftDocs/azure-docs/commit/52dadd8b779ba9032db1f4995dd80655558839ca#diff-066681c2084efbf0ba9a21a6779356149584081048f0e01cb19d493b1e3d31d5
cc @anthonychu @mkarmark

@shibayan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Note that publishing in this repository is suspended until Tuesday, May 25. Merging will resume Tuesday. Authors can still review and sign off on PRs in the interim. Thanks.

@shibayan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks @shibayan, not sure what happened with the previous merge.

#sign-off

@aaronpowell PRs that are approved by using the Review changes function in the diff view don't turn up consistently. Your surest option is to add #sign-off. (But we'll keep looking for the Approved PRs.)

@ktoliver: I'm sorry - only the author of this article, @aaronpowell, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@ktoliver: I'm sorry - only the author of this article, @aaronpowell, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Thanks @ktoliver, I didn't realise they didn't get picked up that way


Fix #286 by adding a registry option

I think this should be sufficient to use a registry in the docker image. The image can be tagged using the full name (with the registry) and used also in local mode as is, so the registry can be provided as command line option or configured in the pom.xml without issues.
@rhuss, can you give a quick look?

This should fix #286.

If I remember right, the issue is not so much about that the image has the proper prefix when its generated, but when it is referenced in the resource descriptors (e.g. when added by an enricher). There the registry prefix is still missing there.

Yeah, there's a unused registry property in the ImageConfiguration and it's true that it is not read. But sadly it's also not settable through the builder.
This works, as shown by the IT test. To properly fix it I'll add that property to the d-m-p builder.

thanks ! btw, I can do a d-m-p release rather quickly.

Ok, so. Thanks!

@nicolaferraro fyi, d-m-p 0.22.1 has been released.

Upgraded to latest d-m-p and changed impl

[merge]


[consensus] add one missing checks on 2-chain timeout

Motivation
Add the missing round > qc_round check for struct timeout.
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
Added a negative test case.
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/diem/diem/tree/main/developers.diem.com, and link to your PR here.)
If targeting a release branch, please fill the below out as well

Justification and breaking nature (who does it affect? validators, full nodes, tooling, operators, AOS, etc.)
Comprehensive test results that demonstrate the fix working and not breaking existing workflows.
Why we must have it for V1 launch.
What workarounds and alternative we have if we do not push the PR.

/land


fix kontinuous spelling

Thanks! Our first PR for the project 👍
A reminder that I shouldn't write docs late at night ;)


OTR:extracellular matrix relationship with extracellular region part

Would it be possible to make extracellular matrix a child (is a) of  extracellular region part?

"Note that this term is intended to annotate gene products that are not attached to the cell surface. "
This has often caused confusion. It would be better if this comment could be included in the definition

It is included in the comment for extracellular region GO:0005576, but not 'extracellular region part' GO:0044421

proteinaceous extracellular matrix GO:0005578 is a child of extracellular region part GO:0044421- so is this incorrect?

Well one is ;)

Old issue around the use of ECM to refer to plant ECM which includes cell walls + definition of cell in GO to include material outside the PM (cell walls etc).  Pretty sure we agreed to stop use OF ECM for plants some time ago.  Will look into it.
But - for Drosophila, you should be using proteinaceous ECM anyway.

I was just poking around a slim, trying to work out how to get all the extracellular stuff under one heading when I came across the ECM issue!
yes - plant ECM GO:0048196 was made obsolete.

Given that we no longer have to account for plants, I've moved the part relationship to extracellular region up to the general ECM class.  For Drosophila, you should still use the more specific term 'proteinaceous ECM'.

Yay! This will solve my slimming issues! I shall endeavour to use proteinaceous ECM in curation!
Thanks.


Add markdown example

Describe the PR
Add markdown description examples
Relation issue
#412
Additional context
None

Codecov Report

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

@@           Coverage Diff           @@
##           master     #486   +/-   ##
=======================================
  Coverage   86.58%   86.58%
=======================================
  Files           7        7
  Lines        1558     1558
=======================================
  Hits         1349     1349
  Misses        120      120
  Partials       89       89

Continue to review full report at Codecov.

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


Data add algorithm to add a dict entry

This algorithm has to check the whole set of rules to add a word to the dictionary.

Please refer to issue #3 for the rules of the L/D moroccan words to add.


[NVC-Net] About 16 kHz training and model convergence

Hi,
Thank you for sharing your great work!
I'm using nvcnet to train a Japanese voice conversion model, I have two questions.
First, I try to adapt your code to 16 kHz wavs, I did the following two manipulations:

changed sr in hparams.py  from 22050 into 16000
changed segment_length in hparams.py from 32768 into 16384
The training goes well but the performance is bad even after 400 epochs.

I wonder if you have any idea on training nvcnet on 16 kHz wavs? Do I need any other modifications to ensure the training will go well ?
Second, could you share the value of g_loss_rec when the model converges?.
In my training the g_loss_rec converged to around 0.9 to 1.2, I'm not sure if this is what I should expect in model convergence.

Hi,
we haven't tried to train NVC-Net on 16 kHz. Under the current hyper-parameters, g_loss_rec should be around 1.2 to1.3
In your case, it could be that other weighing terms are not appropriate for 16 kHz.

Hi,
Thank you for your answering!
Do you mean that the converged g_loss_rec value is normal in my case?


BUG: Testing the SNS requires us to use the system subnet type with the attached network config which breaks ic-repl

Hi @chenyan-dfinity
When testing the SNS workflow locally, we need to set the following in our network config,
{
  "local": {
    "bind": "<IP_ADDRESS>:8080",
    "type": "ephemeral",
    "replica": {
      "subnet_type": "system"
    }
  }
}

This seems to be breaking ic-repl from running and gives the following output:

Thoughts on how we can fix this? Thank you for your inputs :)

You can specify on the replica url as command-line flag: ic-repl -r http://<IP_ADDRESS>:8080


Return supported locales

Descrease number of exceptions in case of empty filename
Make it returning supported locales both for jars and source
Also there is support for custom locales added via custom providers
e.g.
faker.locality().allSupportedLocales(Set.of("datafaker", "custom jar"));

in args need to pass jar names to look at
should fix #566

Codecov Report

Merging #589 (0bbd333) into main (24e3c99) will decrease coverage by 0.30%.
The diff coverage is 50.00%.

@@             Coverage Diff              @@
##               main     #589      +/-   ##
============================================
- Coverage     93.54%   93.23%   -0.31%
- Complexity     2441     2443       +2
============================================
  Files           252      252
  Lines          5051     5073      +22
  Branches        550      558       +8
============================================
+ Hits           4725     4730       +5
- Misses          192      207      +15
- Partials        134      136       +2

Impacted Files
Coverage Δ

...n/java/net/datafaker/providers/base/BaseFaker.java
94.04% <ø> (ø)

...in/java/net/datafaker/providers/base/Locality.java
65.38% <45.45%> (-31.50%)
:arrow_down:

...rc/main/java/net/datafaker/service/FakeValues.java
83.03% <80.00%> (-0.61%)
:arrow_down:

.../datafaker/transformations/sql/SqlTransformer.java
87.45% <0.00%> (-0.74%)
:arrow_down:

.../java/net/datafaker/service/FakeValuesService.java
86.27% <0.00%> (+0.20%)
:arrow_up:

...ker/idnumbers/pt/br/IdNumberGeneratorPtBrUtil.java
96.29% <0.00%> (+3.70%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


node-env: fix for utillinux deprecation

Things done
There was an old workaround from 2020 for the change from utillinux to util-linux. It's broken now that utillinux is hard deprecated, since the first viable option gets picked, and now that throws. I just removed the workaround. As it stands, master seems to be broken for me. (My cinnamon session pulls in xreader -> mathjax -> node -> utillinux.)

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

This will also need to go into unstable asap, I think. It's breaking cinnamon there, too.


Add branch protection rule on Main branch

Add branch protection rule which will require CI / build status to pass before branches can be merged into Main.

Added branch protection rule on main branch.


MongoDB Setup

Create Dev MongoDB on Atlas Cloud.
Create Prod MongoDB on Atlas Cloud.
MongoDB Setup on Atlas Cloud
Sign in/Register on MongoDB Atlas: Go to MongoDB Atlas and sign in or register for an account.
Create Organization and Project: Once you're in, create a new organization (if you haven't already), and within that organization, create a new project for your application.
Build a New Cluster:
Click on the Build a Cluster button.
Choose the cloud provider and region. AWS is usually a good match since you are using AWS for other parts of your project.
Select the cluster tier; you can start with a free tier.
Set additional settings like backup, etc., according to your needs.
Click Create Cluster.
Repeat for Production: Repeat step 3 to create another cluster, but this time, it will be for your production environment. Make sure to name them differently to avoid confusion, e.g., DevCluster and ProdCluster.
Whitelist IP Addresses: For each cluster, go to the Network Access tab and add the IP address(es) that should have access to the database. You can add <IP_ADDRESS>/0 for wide-open access, but it's not recommended for the production environment.
Create MongoDB Users: In the Database Access tab, create a MongoDB user for each cluster with read and write access.
Get Connection Strings: After setting up, click Connect on your cluster and get the connection string. This string is what your application will use to connect to MongoDB. Make sure to replace the  placeholder with the actual password for the user you created.
Store Connection Strings as Secrets: You can store these connection strings in GitHub as secrets for use in GitHub Actions. Name them something like MONGODB_DEV_URI and MONGODB_PROD_URI.

Environment Variables: Store your connection strings in environment variables on your local machine. Most IDEs like Visual Studio Code allow you to create a .env file where you can place your environment variables.
always make sure that your connection strings and other secrets are never committed to version control. Typically, .env file needs to be added to the .gitignore file


Build reproducibility inconsistent CSS file names in vite manifest

Describe the bug
Validating the reproducibility of build results is innacurate because the CSS resources listed in vite-manifest.json are not consistent.
i.e. if routes are using components, their common CSS are collected to avoid duplication. The generated entries inherit a name that changes on each npm run build. Entries which are added to vite-manifest.json and have for results to produces a different vite-manifest.json on each build. Per extension, validating the build results - e.g. comparing hashes of results - is not possible.
Reproduction
git clone https://github.com/peterpeterparker/my-app-reproducibility
cd my-app-reproducibility
npm ci
npm run build
-- copy build/vite-manifest.json somewhere
npm run build
-- compare build/vite-manifest.json with previous output
-- repeat

Logs
No response
System Info
System:
    OS: macOS 13.1
    CPU: (8) arm64 Apple M2
    Memory: 81.19 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.12.1 - /usr/local/bin/node
    npm: 8.19.2 - /opt/homebrew/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 108.0.5359.124
    Firefox: 108.0.1
    Safari: 16.2
  npmPackages:
    @sveltejs/adapter-static: ^1.0.0 => 1.0.0
    @sveltejs/kit: ^1.0.1 => 1.0.1
    svelte: ^3.55.0 => 3.55.0
    vite: ^4.0.3 => 4.0.3

Severity
annoyance
Additional Information
Follow-up of my other issue regarding reproducibility #8290

likewise, don't know if the issue is a SvelteKit, static adapter, ViteJs or even Sass related issue
to make the build reproducible a consistent version should be set what is done in the sample repo
the entries of the vite-manifest.json should be sorted what is solved in the sample repo with a post script

Workaround
Find and remove the duplicated Css scoped in components and extract these to global CSS styles.

i.e. if routes are using components, their common CSS are collected to avoid duplication. The generated entries inherit a name that changes on each npm run build. Entries which are added to vite-manifest.json and have for results to produces a different vite-manifest.json on each build. Per extension, validating the build results - e.g. comparing hashes of results - is not possible

I don't understand this to tell whether it's a Vite issue or not. I don't see any manifest difference when running the repro build multiple times. The CSS file names are the same to me.

In our CI or when I build the sample repo I provided locally (OSX), I get different vite-manifest.json. The differences are related to the CSS tree resolution - i.e. the CSS files src list varies among builds.
Here a screenshot, hopes it help. Let me know if still unclear.

I can reproduce this, though I had to update the repro as we now delete the vite-manifest.json file:
// scripts/make-reproducible.js
import glob from 'tiny-glob/sync.js';
console.log(glob('**', { cwd: '.svelte-kit/output/client/_app/immutable' }).join('\n'));

First run:
assets
assets/ComponentA-24a268d9.css
chunks
chunks/0-6f33aa2b.js
chunks/1-0517ce83.js
chunks/2-20f1e404.js
chunks/3-3f7236d3.js
chunks/4-2ac1ebaf.js
chunks/5-fd48400c.js
chunks/ComponentA-c2bc9bb4.js
chunks/_layout-7e4796dc.js
chunks/index-1664d19c.js
chunks/singletons-90043bb3.js
components
components/error.svelte-52f74891.js
components/layout.svelte-e0888d8b.js
components/pages
components/pages/_page.svelte-443891f6.js
components/pages/a
components/pages/a/_page.svelte-85de7681.js
components/pages/b
components/pages/b/_page.svelte-85de7681.js
components/pages/c
components/pages/c/_page.svelte-9857a16a.js
modules
modules/pages
modules/pages/_layout.ts-bf954bd4.js
start-22da26f5.js

Second run:
assets
assets/_page-24a268d9.css
chunks
chunks/0-6f33aa2b.js
chunks/1-0517ce83.js
chunks/2-20f1e404.js
chunks/3-cec61401.js
chunks/4-0411d579.js
chunks/5-ea0c3f7e.js
chunks/ComponentA-d36a269d.js
chunks/_layout-7e4796dc.js
chunks/index-1664d19c.js
chunks/singletons-90043bb3.js
components
components/error.svelte-52f74891.js
components/layout.svelte-e0888d8b.js
components/pages
components/pages/_page.svelte-443891f6.js
components/pages/a
components/pages/a/_page.svelte-27f46159.js
components/pages/b
components/pages/b/_page.svelte-27f46159.js
components/pages/c
components/pages/c/_page.svelte-86b10778.js
modules
modules/pages
modules/pages/_layout.ts-bf954bd4.js
start-efaf7fc0.js

This seems like a fairly serious bug — as well as making builds non-reproducible, it affects cache stability meaning it directly affects users. Will see if I can create a repro without SvelteKit.

Struggling a bit to create a repro, so I'll leave this for others...

Thanks for digging into this!


Fix z-index issues caused by sticky-discussion-sidebar

Closes #2339
Test
This feature depends on the viewport size, the sidebar has to be sticky for these issues to appear (or not appear)

The Labels dropdown should not overlap the file's header in the review below. Example
The "Notifications settings" lightbox should appear and work correctly, without the Repo’s social buttons being overlapped. Example
The "Repo Notifications" dropdown should not overlap the sidebar. Example

@fregante looks like this breaks on Enterprise GitHub. The entire Labels panel when popped up is now behind the description box, titles, etc.
Actually now that I've taken a look, the sticky "follow the scrollbar" feature of the sidebar hasn't been working in Enterprise for quite some time...


chore(CPlusPlus): add sliding windows

PR Checklist:

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is on refer on the language README.md file
[x] My addition does not have a spelling problem
[x] My submission has a proper and user-friendly description of the algorithm
[x] My submission has the time complexity of the algorithm
[ ] My submission has sample input-output of the program (NOT FOR PYTHON)

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] New algorithm
[ ] Optimization in previous algorithms
[ ] Code style update
[ ] Refactor
[ ] Documentation
[ ] Other, please describe:

Briefly describe the changes in this PR

Other information:

Please go through my pull request and let me know if any changes required thanks and regards

Hello @ming-tsai  my pull request still in queue, any changes required?

Hello @ming-tsai  my pull request still in queue, any changes required?

Hi @Amit-exe,
Please wait for 72 hours, due to this is open source project we need to wait until the reviewer is not busy

@ming-tsai  okay sir no issues, thank you for the update

Hello @Arsenic-ATG  and @ming-tsai ,
codespell check is failing but it has nothing to do with my code or any changes done by me.
since it's in  java/math/roman-numerals.java:13.

Hello @ming-tsai please check and merge my pull request it's already approved  but failing spell check due to someone else's java code in math section


yarn install gives 404 for @mattrglobal/node-bbs-signatures

I downloaded the repo, run yarn install, and got 404 status code downloading tarball https://github.com/mattrglobal/node-bbs-signatures/releases/download/0.5.0/node-v72-linux-x64.tar.gz.
It seems my system is trying to download v72 when the available is v64, but I don't know why.
Here is the full output:
yarn install v1.16.0
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
[1/4] ⡀ @mattrglobal/node-bbs-signatures
[2/4] ⡀ sodium-native
[-/4] ⢀ waiting...
error /home/geovane/dev/swarm/tmp/jsonld-signatures-bbs/node_modules/@mattrglobal/node-bbs-signatures: Command failed.
Exit code: 1
Command: node-pre-gyp install --fallback-to-build=false
Arguments:
Directory: /home/geovane/dev/swarm/tmp/jsonld-signatures-bbs/node_modules/@mattrglobal/node-bbs-signatures
Output:
node-pre-gyp info it worked if it ends with ok
node-pre-gyp info using<EMAIL_ADDRESS>node-pre-gyp info using<EMAIL_ADDRESS>| linux | x64
node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp info check checked for<EMAIL_ADDRESS>(not found)
node-pre-gyp http GET https://github.com/mattrglobal/node-bbs-signatures/releases/download/0.5.0/node-v72-linux-x64.tar.gz
node-pre-gyp http 404 https://github.com/mattrglobal/node-bbs-signatures/releases/download/0.5.0/node-v72-linux-x64.tar.gz
node-pre-gyp ERR! install error
node-pre-gyp ERR! stack Error: 404 status code downloading tarball https://github.com/mattrglobal/node-bbs-signatures/releases/download/0.5.0/node-v72-linux-x64.tar.gz
node-pre-gyp ERR! stack     at Request.<anonymous> (/home/geovane/dev/swarm/tmp/jsonld-signatures-bbs/node_modules/node-pre-gyp/lib/install.js:142:27)
node-pre-gyp ERR! stack     at Request.emit (events.js:208:15)
node-pre-gyp ERR! stack     at Request.onRequestResponse (/home/geovane/dev/swarm/tmp/jsonld-signatures-bbs/node_modules/request/request.js:1059:10)
node-pre-gyp ERR! stack     at ClientRequest.emit (events.js:203:13)
node-pre-gyp ERR! stack     at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:565:23)
node-pre-gyp ERR! stack     at HTTPParser.parserOnHeadersComplete (_http_common.js:116:17)
node-pre-gyp ERR! stack     at TLSSocket.socketOnData (_http_client.js:452:22)
node-pre-gyp ERR! stack     at TLSSocket.emit (events.js:203:13)
node-pre-gyp ERR! stack     at addChunk (_stream_readable.js:294:12)
node-pre-gyp ERR! stack     at readableAddChunk (_stream_readable.js:275:11)
node-pre-gyp ERR! System Linux 4.19.0-8-amd64
node-pre-gyp ERR! command "/home/geovane/.nvm/versions/node/v12.6.0/bin/node"<EMAIL_ADDRESS>"install" "--fallback-to-build=false"
node-pre-gyp ERR! cwd /home/geovane/dev/swarm/tmp/jsonld-signatures-bbs/node_modules/@mattrglobal/node-bbs-signatures
node-pre-gyp ERR! node -v v12.6.0
node-pre-gyp ERR! node-pre-gyp -v v0.14.0

I think this maybe because we built to use node v10 latest and the node version you use locally affects the uri that's constructed when downloading the script. Try using v10 latest for now and we'll work on getting support for newer versions of node.
@tplooker as far as I remember there weren't any constrains that kept us to having to use v10 for this package, so I think we should be able to add publishing the tarballs for different node versions. Do you see any concerns with this?

Thanks, that worked.
In particular, I had to use 10.13.0, as per this message: error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "^8.10.0 || ^10.13.0 || >=11.10.1". Got "10.0.0".

We'll leave this issue open until we decide how to handle support for node 12 as well. Thanks for filing the issue.

@geonnave correct our CI pipeline on each stable build creates a release for different OS's for node-bbs-signatures. We just need to add your node abi to one that is built in this release process. As an interim solution if you have rust installed on your machine try installing one of our unstable builds of node-bbs-signatures as this will compile the rust on your machine.

@geonnave and @OR13 this should now be working for Node 12.

@geonnave release 0.4.0 and beyond should have this fix.


Build Error: payload/error could not resolve package in Resend email package

Describe the Bug
The payload resend email package is broken -
`
⨯ ./node_modules/.pnpm/@payloadcms+email-resend@3.0.0-beta.29_payload@3.0.0-beta.121_graphql@16.9.0_monaco-editor@0._srgwrjl2b7cefuyhbajcvxefse/node_modules/@payloadcms/email-resend/dist/index.js:1:1
Module not found: Can't resolve 'payload/errors'

1 | import { APIError } from 'payload/errors';
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2 | /**
3 |  * Email adapter for Resend REST API
4 |  */ export const resendAdapter = (args)=>{

https://nextjs.org/docs/messages/module-not-found
`
Link to the code that reproduces this issue
https://github.com/theHoracle/donner-payload3b.git
Reproduction Steps
pnpm add @payloadcms/email-resend
then in payload.config
`
import { resendAdapter } from '@payloadcms/email-resend'
export default buildConfig({
email: resendAdapter({
defaultFromAddress<EMAIL_ADDRESS>defaultFromName: 'Foundation',
apiKey: process.env.RESEND_API_KEY || '',
}),
})
`
Which area(s) are affected? (Select all that apply)
plugin: other
Environment Info
cross-env NODE_OPTIONS=--no-deprecation payload "info"

Binaries:
  Node: 22.9.0
  npm: 10.8.3
  Yarn: 1.22.22
  pnpm: 9.12.2
Relevant Packages:
  payload: 3.0.0-beta.121
  next: 15.0.2
  @payloadcms/db-mongodb: 3.0.0-beta.121
  @payloadcms/email-nodemailer: 3.0.0-beta.121
  @payloadcms/email-resend: 3.0.0-beta.29
  @payloadcms/graphql: 3.0.0-beta.121
  @payloadcms/next/utilities: 3.0.0-beta.121
  @payloadcms/payload-cloud: 3.0.0-beta.121
  @payloadcms/richtext-lexical: 3.0.0-beta.121
  @payloadcms/translations: 3.0.0-beta.121
  @payloadcms/ui/shared: 3.0.0-beta.121
  react: 19.0.0-rc-b7e21579-20241031
  react-dom: 19.0.0-rc-b7e21579-20241031
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:02:27 PDT 2024; root:xnu-11215.41.3~2/RELEASE_X86_64
  Available memory (MB): 8192
  Available CPU cores: 4

Hey @theHoracle! Looks like your installed version of @payloadcms/email-resend is 3.0.0-beta.29, while other packages are on 3.0.0-beta.121. They should be all on the same version, try to run pnpm add<EMAIL_ADDRESS>


Add ca/uregina.ca domain (University of Regina)

Adding the University of Regina domain.
Official domain: https://uregina.ca
Links to a few Software / CS / IT programs:

https://www.uregina.ca/engineering/students/programs/software-systems.html
https://www.uregina.ca/science/cs/undergraduate/index.html

Support page indicating that students have @uregina.ca domain email addresses: https://www.uregina.ca/is/index.html

@ericyanush lib/domains/ca/uregina.ca: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@ericyanush I am sorry, the domain uregina.ca is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Unable to test : network connection pb

I ran
docker run -it -d -p 8181:8181 kdelfour/cloud9-docker

So I have a running container :
9084bc7af42d        kdelfour/cloud9-docker:latest   "supervisord -c /etc   52 seconds ago      Up 51 seconds       <IP_ADDRESS>:8181->8181/tcp   naughty_nobel

With some process inside :
$ docker exec -it 9084bc7af42d ps -aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.1  0.1  60532 13864 ?        Ss+  20:09   0:00 /usr/bin/python /usr/bin/supervisord -c /etc/supervisor/s
root         7  0.3  0.2<PHONE_NUMBER>8 ?        Sl   20:09   0:01 node /cloud9/server.js --listen <IP_ADDRESS> -w /workspace
root        13  0.0  0.0  15564  1152 ?        R+   20:14   0:00 ps -aux
$

But when I try to access the IDE from my browser : http://<IP_ADDRESS>:8181/ the connection can't be establish (like a TCP/IP level connection error). I tried on 2 different machines,  I also tried to build from source : same result ...
(I do not have firewall rules or something that could explain that).
is it working for you ?

I have the same issue. It claims to be running but can't access it.

Figured it out....it needs authentication on the config file:
docker exec -it <CONTAINER_ID> vi /etc/supervisor/conf.d/cloud9.conf (look at line 2)
[program:cloud9]
command = node /cloud9/server.js --listen <IP_ADDRESS> -a user:password -w /workspace
directory = /cloud9
user = root
autostart = true
autorestart = true
stdout_logfile = /var/log/supervisor/cloud9.log
stderr_logfile = /var/log/supervisor/cloud9_errors.log
environment = NODE_ENV="production"
restart container! awesomeness awaits!
Thanks for dockerizing cloud9

Now it's not necessary to add --auth in cloud9.conf to test it.


[PDI-15973]   Salesforce Input step no longer allows for relationship…

… queries
Sorry, previous PR got broken

Proper selection of child elements value
Unit - test

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f plugins/salesforce/build.xml clean-all resolve jacoco && ant -f plugins/salesforce/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  plugins/salesforce/src/org/pentaho/di/trans/steps/salesforce/SalesforceConnection.java
  plugins/salesforce/test-src/org/pentaho/di/trans/steps/salesforce/SalesforceConnectionTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.trans.steps.salesforce.SalesforceConnection

Branch Change:  + 3.96%
Complexity Change:  + 2.26%
Instruction Change:  + 3.43%
Line Change:  + 4.16%
Method Change:  + 3.57%

org.pentaho.di.trans.steps.salesforceupdate.SalesforceUpdateMeta

Instruction Change: -.17%:small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceupsert.SalesforceUpsertMeta

Instruction Change: -.14%:small_red_triangle_down:


Deal with PROJ4 / PROJ6 issues

When reading in forecast climate data, there is some funny business about projection data. Might be an issue that requires dealing with, might not. Specifically, something like
gfdl_data <- raster::getData(name = "CMIP5",
                             var = "bio",
                             res = 2.5,
                             rcp = 45,
                             model = "GD",
                             year = 70,
                             path = "data/")

Returns a series of warnings (usually 20 per raster::getData() call)
In showSRID(SRS_string, format = "PROJ", multiline = "NO",  ... :
  Discarded datum unknown in Proj4 definition

Closing for now, since we no longer use raster::getData() to retrieve forecast data.


Examples are mixed/stacking up

📚 The doc issue
Under examples/notebooks there are many example notebooks varying from LLMs, text, images, DBs. Should we store them in separate directories?
Suggest a potential fix
├── examples
├── ├── notebooks
├── ├── ├── benchmark
├── ├── ├── image_experiments
├── ├── ├── ├── StableDiffusionExperiment.ipynb
├── ├── ├── llm_experiments
├── ├── ├── ├── LlamaCppExperiment.ipynb
├── ├── ├── db_experiments
├── ├── ├── ├── LanceDBExperiment.ipynb
├── ├── ├── audio_experiments
├── ├── ├── ├── MusicGenExperiment.ipynb
├── ├── ├── video_experiments

This is definitely better in the long term. The downside of updating the path is that previous posts (on social media, etc) might have broken links.
We will also have to make sure all links within the repo (e.g. doc, README) have the updated links.

One idea: we can move the notebooks and use symlinks to keep the previous links working.

I have moved the non-LLM examples to subfolders. Let's close this for now. Feel free to re-open if anyone has concerns about this.


Store atomtyping results in a dict instead of the topology

PR Summary:
Implements @ctk3b's idea in #233
Not all tests are passing (some residue map and override stuff needs to be updated) but the basic cases are handled.
PR Checklist

[x] Includes appropriate unit test(s)
[x] Appropriate docstring(s) are added/updated
[x] Code is (approximately) PEP8 compliant
[x] Issue(s) raised/addressed?

This PR accomplishes what I wanted to do, but the organization of the various functions could be improved upon. As you can see, the unit test now looks quite clunky, and it's not clear how easily a user could pick apart steps of this process, i.e. grabbing the dictionary of types from the atom-typing process without going all the way to a fully-parametrized system.

@mosdef-hub/mosdef-contributors this is a fairy sizeable start to reworking some of the guts of foyer. Could you grab these changes and run some test or production systems?
You can do something like this to grab these changes in a new branch
git remote add https://github.com/mattwthompson/foyer
git fetch matt
git checkout -b matt/separate-apply
git checkout -b separate-apply

Did a workflow with this version of foyer, parameters looked good and simulation ran fine

I used this version of foyer and Python 3.7.3 to build a solvent-ionic liquid system.  The system was atomtyped correctly and the simulations are running fine.

where are workflows currently shared? are they on the MoSDeF site?
On Jun 11, 2019, at 1:19 PM, Ray Matsumoto <notifications<EMAIL_ADDRESS>wrote:
I used this version of foyer and Python 3.7.3 to build a solvent-ionic liquid system. The system was atomtyped correctly and the simulations are running fine.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmosdef-hub%2Ffoyer%2Fpull%2F249%3Femail_source%3Dnotifications%26email_token%3DAFAGPYOJYBRFCJFTHUO6OTLPZ7UDDA5CNFSM4HQXDC72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXOBRUA%23issuecomment-500963536&data=02|01|peter.cummings%40vanderbilt.edu|1f7e8d2209684506cfb108d6ee9958c8|ba5a7f39e3be4ab3b45067fa80faecad|0|0|636958739717964087&sdata=tDhibNNkC%2FrwH3Hcf3syErxv455%2Fq4tXw%2Bfr3tGf2GI%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFAGPYNP7WRFLV5L2V7ZTQDPZ7UDDANCNFSM4HQXDC7Q&data=02|01|peter.cummings%40vanderbilt.edu|1f7e8d2209684506cfb108d6ee9958c8|ba5a7f39e3be4ab3b45067fa80faecad|0|0|636958739717974096&sdata=dtxalaukTIg3D7pFaNDGGzN%2BuZY8ZRz2LrDUV01Uzx8%3D&reserved=0.

@ptc2ug we currently dont have a place where these are shared.
@mattwthompson I also pulled these changes and have been able to atomtype my alkylsilane tethered monolayers successfully with this update.


Moving json fixtures files

Removing rest-api fixtures files as they are part of brooklyn-ui now
Adding a test dependency to brooklyn-jsgui for fixtures files inclusion

Merge together with apache/brooklyn-ui#9

I've tried this together with https://github.com/apache/brooklyn-ui/pull/9 -- I get 4 failures in the rest-resources bundle, including ApplicationTest.testDeserializeFromJSON: IllegalState Cannot find resource...

I'm now getting
SoftwareProcessPersisterInMemorySizeIntegrationTest>BrooklynMementoPersisterInMemorySizeIntegrationTest.testPersistenceVolumeFast:55->BrooklynMementoPersisterInMemorySizeIntegrationTest.doTestPersistenceVolume:83

Investigating...

My problem above is unrelated, I've fixed it in master.  The Jenkins failure is expected of course as it depends on #9 but I confirm it builds fine for me.
Now looking at the code in more detail.

Code is nice and simple.  Nice job @ygy. Merging.


admin: add host priority to cluster response

Signed-off-by: Yan Xue<EMAIL_ADDRESS>Description: add host priority to cluster response
Risk Level: low
Testing: unit test
Docs Changes: N/A
Release Notes: https://github.com/envoyproxy/envoy/compare/master...crazyxy:admin?expand=1#diff-d8d3e33358b55e6c0466dd1bb5f40c79

@zuercher Could you please take a look? Thanks!

This looks good. Can you merge master and fix the conflicts? (Sorry for the slow response, I was out of town last week.)

@zuercher I merged the upstream code. PTAL, thanks!