ES2015 for node

Is it possible to use ES2015 modules in node?

Not directly. They'll need to be compiled to commonjs. Universal-react-scripts should take care of this for any modules in your src directory, but will not do so for anything in node_modules - just as with create-react-app.

But what i don't understand is in the client mode the Unexpected token export does not come up. So it should be compiled somewhere in the dev server right?

I’m honestly not sure why this is, but if this is with loadable components
then it’s out of my experience so I can’t support it, sorry.
On Wed, Jul 24, 2019 at 23:45 Alex van der Vegt<EMAIL_ADDRESS>wrote:

But what i don't understand is in the client mode the Unexpected token
export does not come up. So it should be compiled somewhere in the dev
server right?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jamesknelson/create-react-app/issues/1?email_source=notifications&email_token=AABHPK6KNVR6BRKKHVX2JLDQBBTJPA5CNFSM4IGQZCX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2WSFBQ#issuecomment-514663046,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABHPK4S7WF6O4QOFCFWPY3QBBTJPANCNFSM4IGQZCXQ
.

No this has nothing to with loadable components for now, i am just using the preloadAll function before i start rendering the index.node.js response.
This also includes some modules from the node_modules folder and then the error turns up.

I see. It may be to do with the modules exporting both a “main” and a “web”
field from package.json. In this case, the “web” file will be used in the
browser, while the “main” file will be used on node.js.
Can you take a look at the relevant package.json and see if this could be
it?
On Wed, Jul 24, 2019 at 23:50 Alex van der Vegt<EMAIL_ADDRESS>wrote:

No this has nothing to with loadable components for now, i am just using
the preloadAll function before i start rendering the index.node.js response.
This also includes some modules from the node_modules folder and then the
error turns up.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jamesknelson/create-react-app/issues/1?email_source=notifications&email_token=AABHPK5ZGHSLFGZIKL2FHIDQBBT2HA5CNFSM4IGQZCX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2WST7Q#issuecomment-514664958,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABHPK2ERIGGASLEY4QWKDLQBBT2HANCNFSM4IGQZCXQ
.

I dont see a web file, i think?
{   "name": "@material-ui/core",   "private": false,   "author": "Material-UI Team",   "version": "3.9.3",   "description": "React components that implement Google's Material Design.",   "keywords": [     "react",     "react-component",     "material design",     "material-ui"   ],   "repository": {     "type": "git",     "url": "https://github.com/mui-org/material-ui.git"   },   "license": "MIT",   "bugs": {     "url": "https://github.com/mui-org/material-ui/issues"   },   "homepage": "https://material-ui.com/",   "peerDependencies": {     "react": "^16.3.0",     "react-dom": "^16.3.0"   },   "dependencies": {     "@babel/runtime": "^7.2.0",     "@material-ui/system": "^3.0.0-alpha.0",     "@material-ui/utils": "^3.0.0-alpha.2",     "@types/jss": "^9.5.6",     "@types/react-transition-group": "^2.0.8",     "brcast": "^3.0.1",     "classnames": "^2.2.5",     "csstype": "^2.5.2",     "debounce": "^1.1.0",     "deepmerge": "^3.0.0",     "dom-helpers": "^3.2.1",     "hoist-non-react-statics": "^3.2.1",     "is-plain-object": "^2.0.4",     "jss": "^9.8.7",     "jss-camel-case": "^6.0.0",     "jss-default-unit": "^8.0.2",     "jss-global": "^3.0.0",     "jss-nested": "^6.0.1",     "jss-props-sort": "^6.0.0",     "jss-vendor-prefixer": "^7.0.0",     "normalize-scroll-left": "^0.1.2",     "popper.js": "^1.14.1",     "prop-types": "^15.6.0",     "react-event-listener": "^0.6.2",     "react-transition-group": "^2.2.1",     "recompose": "0.28.0 - 0.30.0",     "warning": "^4.0.1"   },   "sideEffects": false,   "publishConfig": {     "access": "public"   },   "engines": {     "node": ">=6.0.0"   },   "main": "./index.js",   "module": "./index.es.js" }

I also got some feedback on the material-ui github:
Somewhere in your build setup you're aliasing to the ES 8 build without transpiling it for the server.
referencing this page: https://material-ui.com/guides/minimizing-bundle-size/#ecmascript

Okay, I have one idea for the issue. For whatever reason, the node version must be resolving the "module" string instead of the "main" one.
I'm not sure if this is actually the case though. I haven't run into this in my project, which uses a number of 3rd party modules.
If you'd like to have a go at fixing this I'd definitely accept a PR, but unfortunately I can't dedicate any time to it right now.

If you can point me a bit in the direction i am willing to try

Unfortunately I don't think I really understand this issue any better than you do yourself, so you'd be on your own for this one.

If i do a little test like this:
"main": "./index.es.js",   "module": "./index.es.js"
I get another error:
`/node_modules/@material-ui/core/index.es.js:6
import * as colors from './colors';
^^^^^^
SyntaxError: Unexpected token import
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:617:28)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
`

It is indeed using the main entry and not the module entry. But when i do the test as described above it still does not compile correct.

If you add the  "@material-ui/core": "^3.9.3" package to your installation you will see the bug right away. Would be great if we can fix this.

I am really pulling my hair out, maybe this is saying something to you:
https://github.com/babel/babel/issues/8638

Hi,
I hope you will have a few more minutes for me.  I think it has to do with the index.js that is booting the server some other way then you do. But I don't see it.
Here is my index.js:
require('@babel/polyfill');
require('@babel/register')({
    ignore: [/\/(build|node_modules)\//],
    presets: ['@babel/preset-env', '@babel/preset-react'],
    plugins: [
        '@babel/plugin-syntax-dynamic-import',
        '@babel/plugin-proposal-class-properties',
        'dynamic-import-node'
    ]
});

require('./server');

The server.js is an exact copy of the index.node.js I use in universal-react-scripts.
package.json:
"devDependencies": {
        "@babel/cli": "^7.5.5",
        "@babel/core": "^7.5.5",
        "@babel/node": "^7.5.5",
        "@babel/plugin-proposal-class-properties": "^7.5.5",
        "@babel/plugin-transform-runtime": "^7.5.5",
        "@babel/polyfill": "^7.4.4",
        "@babel/preset-env": "^7.5.5",
        "@babel/preset-react": "^7.0.0",
        "babel-plugin-import-static-files": "^1.0.4",
        "babel-plugin-module-resolver": "^3.2.0"
    },

I am on node v8.15.0.
I am really looking forward to a reply.

Running @babel/register on the server will definitely fix the problem, as it will cause every file that your server loads to be transpiled by babel -- whether there are modules are not. The problem is that it's slow and probably unstable, and you definitely don't want to be doing it in production.
The funny thing to me is that there's any code with ES6 modules being loaded in the first place. I've taken a look at the file you pointed out, and it's possible that it may be the source of the problem. However, that file actually tells babel to do extra module->commonjs transpilation for node.js, while leaving modules as-is on the browser.
It's a bit of a mystery to me. Unfortunately actually fixing these kinds of issues often involves spending a few hours on them even for me, and it'll be a while before I can put the time in.

Thanks for your reply! Where can I include teh babel/register in the config so I can debug the issue and check if its working then.

babel/register is something that needs to run at runtime, so you'd just put it directly in index.node.js

When I put this at top of the index.node.js
require('@babel/polyfill');
require('@babel/register')({
    ignore: [/\/(build|node_modules)\//],
    presets: ['@babel/preset-env', '@babel/preset-react'],
    plugins: [
        '@babel/plugin-syntax-dynamic-import',
        '@babel/plugin-proposal-class-properties',
        'dynamic-import-node',
        [
            'transform-assets',
            {
                'extensions': [
                    'png',
                    'jpg',
                    'gif',
                    'svg',
                ],
                'name': 'static/media/[name].[hash:8].[ext]',
            },
        ],
    ],
});

import fs from 'fs';
import React from 'react';

I still have the same error:
SyntaxError: Unexpected token export
That's weird right?

I really don't get it anymore, I am going to wait for you to have a look.

After days of debugging I found the issue, and its a really stupid one :D
Turns out my editor was referencing Typography somehow from another package as the rest. So everything is solved now!
Thanks a lot for all your help in this, I will start testing it thoroughly now :)
import Typography from '@material-ui/core/es/Typography';
import {Button, Hidden, IconButton} from '@material-ui/core';

Hey, that's great to hear! Glad you got it working :D

@alexvandervegt The lack of reply on the thread on the create-react-app repository makes me wonder if we might need to start a separate project for maintenance of this, at least in the short term.
Would you be interested in putting together a FAQ with this issue and anything else you run into while setting things up, mainly as a resource to help anyone else trying to get started with universal-react-scripts? Hopefully, making it easier to dive in will get more people using this, and thus result in more people sharing the maintenance work.

Sure, tell me what you need.

To start with, it'd be great if you could put together a small PR with a FAQ.md, with any questions you run into while setting it up (like the above), and a short answer detailing the answer.


@AutoConfigureWireMock doesn't stop Jetty server properly.

Using @AutoConfigureWireMock in more than one test class with same wiremock.server.port causes the following exception:
java.lang.IllegalStateException: Failed to load ApplicationContext
.....
Caused by: org.springframework.context.ApplicationContextException: Failed to start bean 'org.springframework.cloud.contract.wiremock.WireMockConfiguration'; nested exception is com.github.tomakehurst.wiremock.common.FatalStartupException: java.lang.RuntimeException: java.net.BindException: Address already in use
.....
Caused by: com.github.tomakehurst.wiremock.common.FatalStartupException: java.lang.RuntimeException: java.net.BindException: Address already in use
    at com.github.tomakehurst.wiremock.WireMockServer.start(WireMockServer.java:146)
    at org.springframework.cloud.contract.wiremock.WireMockConfiguration.start(WireMockConfiguration.java:142)
    at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:175)
    ... 46 more
Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use
    at com.github.tomakehurst.wiremock.jetty9.JettyHttpServer.start(JettyHttpServer.java:137)
    at com.github.tomakehurst.wiremock.WireMockServer.start(WireMockServer.java:144)
Caused by: java.net.BindException: Address already in use
    at sun.nio.ch.Net.bind0(Native Method)
    at sun.nio.ch.Net.bind(Net.java:433)
    at sun.nio.ch.Net.bind(Net.java:425)
    at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
    at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
    at wiremock.org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
    at wiremock.org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
    at wiremock.org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
    at wiremock.org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
    at wiremock.org.eclipse.jetty.server.Server.doStart(Server.java:366)
    at wiremock.org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
    at com.github.tomakehurst.wiremock.jetty9.JettyHttpServer.start(JettyHttpServer.java:135)

Obviously when a second test is started it tries to run a server in the same port, but for some reason the first one hasn't stopped the previous properly.
All tests in https://github.com/spring-cloud-samples/spring-cloud-contract-samples/ which use @AutoConfigureWireMock, have Spring's @DirtiestContext declared. Unfortunately I couldn't find explicit requirement for this annotation at https://cloud.spring.io/spring-cloud-static/spring-cloud-contract/1.2.4.RELEASE/single/spring-cloud-contract.html#_spring_cloud_contract_wiremock

That's a known issue (that's why @DirtiesContext is there). If you search for @DirtiesContext in the docs you'll get https://cloud.spring.io/spring-cloud-static/spring-cloud-contract/1.2.4.RELEASE/single/spring-cloud-contract.html#_limitations
AFAIR @dsyer was looking into it once and there was no easy way to fix it. I guess we should document it better / investigate it again.

@marcingrzejszczak any chance to have it in 1.2.6?

As a workaround you can copy the classes and register them manually

@marcingrzejszczak Let me try it on Monday. Thanks!

I'm insane... It has already been backported - https://github.com/spring-cloud/spring-cloud-contract/commit/c9228969de898b0c4373877dcd56b73134b1f77b

Oh sorry, I somehow missed it in branch history. So now we are waiting for 1.2.6 😃

Hi Could you please help me here .
I am running wiremock junit test case and getting below exception every time
2020-04-10 20:51:34.541  INFO 84435 --- [    Test worker] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 2 endpoint(s) beneath base path ''
2020-04-10 20:51:34.822  INFO 84435 --- [    Test worker] org.eclipse.jetty.server.Server          : jetty-9.4.26.v20200117; built: 2020-01-17T12:35:33.676Z; git: 7b38981d25d14afb4a12ff1f2596756144edf695; jvm 1.8.0_221-b11
2020-04-10 20:51:34.853  INFO 84435 --- [    Test worker] o.e.jetty.server.handler.ContextHandler  : Started o.e.j.s.ServletContextHandler@a51c931{/__admin,null,AVAILABLE}
2020-04-10 20:51:34.856  INFO 84435 --- [    Test worker] o.e.jetty.server.handler.ContextHandler  : Started o.e.j.s.ServletContextHandler@3d622400{/,null,AVAILABLE}
2020-04-10 20:51:34.869  INFO 84435 --- [    Test worker] o.e.jetty.server.AbstractConnector       : Started NetworkTrafficServerConnector@709ceff2{HTTP/1.1,[http/1.1]}{<IP_ADDRESS>:5000}
2020-04-10 20:51:34.869  INFO 84435 --- [    Test worker] org.eclipse.jetty.server.Server          : Started @80828ms
2020-04-10 20:53:40.153  INFO 84435 --- [tp780160597-117] o.e.j.s.handler.ContextHandler.ROOT      : RequestHandlerClass from context returned com.github.tomakehurst.wiremock.http.StubRequestHandler. Normalized mapped under returned 'null'
2020-04-10 20:53:40.301 ERROR 84435 --- [qtp780160597-92] WireMock                                 : Request was not matched as there were no stubs registered:
{
"url" : "/o/.well-known/openid-configuration",
"absoluteUrl" : "http://<IP_ADDRESS>:5000/o/.well-known/openid-configuration",
"method" : "GET",
"clientIp" : "<IP_ADDRESS>",
"headers" : {
"Cache-Control" : "max-age=0",
"Accept" : "text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3",
"Upgrade-Insecure-Requests" : "1",
"Connection" : "keep-alive",
"User-Agent" : "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36",
"Host" : "<IP_ADDRESS>:5000",
"Accept-Encoding" : "gzip, deflate",
"Accept-Language" : "en-GB,en-US;q=0.9,en;q=0.8"
},
"cookies" : { },
"browserProxyRequest" : false,
"loggedDate" :<PHONE_NUMBER>194,
"bodyAsBase64" : "",
"body" : "",
"scheme" : "http",
"host" : "<IP_ADDRESS>",
"port" : 5000,
"loggedDateString" : "2020-04-10T19:53:40Z",
"queryParams" : { }
}
Caused by: java.io.IOException: Failed to bind to /<IP_ADDRESS>:5000
at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:346)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:307)
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:231)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:72)
at org.eclipse.jetty.server.Server.doStart(Server.java:385)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:72)
at com.github.tomakehurst.wiremock.jetty9.JettyHttpServer.start(JettyHttpServer.java:174)
... 67 common frames omitted
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:342)
... 74 common frames omitted
Code sample:
@RunWith(SpringRunner.class)
@SpringBootTest(classes = Application.class, webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
@DirtiesContext
public abstract class SpringBootIntegrationTest {
@LocalServerPort
protected int port;

}
@configuration
@AutoConfigureWireMock(port = 5000)
public abstract class AuthorizationEnabledIntegrationTest extends SpringBootIntegrationTest {
@ClassRule
public static WireMockRule someService = new WireMockRule(options().port(5000).withRootDirectory("src/integrationTest/resources/mappings"));
}
inside mappings folder :
{
"priority": 1,
"mappings": [
{
"request": {
"method": "GET",
"url": "/o/.well-known/openid-configuration"
},
"response": {
"status": 200,
"headers": {
"Content-Type": "application/json"
},
"jsonBody": {
"issuer": "http://<IP_ADDRESS>:5000/o",
"jwks_uri": "http://<IP_ADDRESS>:5000/jwks"
}
}
}
]
}

Please learn how to properly format the code
Also are you sure you're using the latest version?

Currently experiencing this issue in spring-cloud-contract-wiremock 2.2.5-REALEASE. I have a  project containing couple spring boot at work (unfortunately unable to shared the source code) and when the tests in the modules are run in parallel, this issue appears.
Is this still an issue that we have to use @DirtiesContext as a work around?

Currently experiencing this issue in spring-cloud-contract-wiremock 2.2.5-REALEASE. I have a  project containing couple spring boot at work (unfortunately unable to shared the source code) and when the tests in the modules are run in parallel, this issue appears.
Is this still an issue that we have to use @DirtiesContext as a work around?

If you're using random ports then it shouldn't be an issue. If there's one then it's a bug.


ModuleResolution Node16/NodeNext fails without extension starting on 5.5.0-dev.20240413

🔎 Search Terms
moduleResolution node16 nodeNext import extension
🕗 Version & Regression Information

This changed between versions 5.5.0-dev.20240413 and 5.5.0-dev.20240415 (last one checked)

⏯ Playground Link
No response
💻 Code
type Something1 = typeof import('@some/package/path/to/file');
type Something2 = typeof import('@some/package/path/to/file.js');

🙁 Actual behavior
Something1 resolves to any
Something2 resolves to Something
🙂 Expected behavior
Something1 resolves to Something
Something2 resolves to Something
Additional information about the issue
This happens on the latest nightly versions and on moduleResolution Node16/NodeNext.
From what I could get, it started on 5.5.0-dev.20240413.

We need a complete repro here; the package.json of @some/package, the importing package, and the tsconfig for the importing file all matter

https://stackblitz.com/~/github.com/Noriller/ts-issue-58214
I hope this one helps.
In the test.d.ts with the current typescript@next and same jsconfig (its a legacy project, using mostly jsdocs, but with the problem in a d.ts file)
If changing ts version with:
 npm i -D<EMAIL_ADDRESS>then both work

This bisects to #57896. @andrewbranch
(I'm not an expert, but it seems strange that you'd need an extension when the d.ts file is effectively CJS, importing another CJS file, but importing via a JS file is already funky.)

Guessing I accidentally made ImportTypes look like an ESM-mode source location, when they were previously kept CJS-mode for backward compatibility reasons. Will take a look. Thanks!

Your jsconfig.json is invalid:

Option 'module' must be set to 'Node16' when option 'moduleResolution' is set to 'Node16'

module is defaulting to es2020 because of target, which is causing everything to resolve under ESM rules (since everything will emit as ESM). I’d argue this is probably more logically consistent than what we used to do, where the module resolution implementation made a lot more assumptions about module format and emit.
I guess we could consider making --moduleResolution node16 imply --module node16 instead of issuing an error, but I think we did the error on purpose so that people would notice we were making a breaking change when we started requiring these options be used together in https://github.com/microsoft/TypeScript/pull/54567.

You can set "moduleDetection": "legacy"


Update to v2.2.4 - all shutters and blinds disappeared

After updating to 2.2.4, all my shutters and blinds are gone. All my backup files are shown as invalid. Even after a backflash to 2.2.3.

Remove the .txt extension from the file.

Upload one of those backup files here.  I thought for a moment that I may have had a mime check on it but that message is a service return.

The story behind this is in this ticket #215.   Changes being made to support other boards required posting interim releases in pre-release but unfortunately they showed up on the OTA.  This all has been rectified but in the meantime it looks like some of the interim releases got installed.
Keep going back in time with the backup files until you find a good one.  The rolling code persistence keeps the data in non-volatile storage on the chip as well and backups are backward compatible.

Thanks for the help. I rolled back to 2.2.3, removed the extension .txt from the backup file and successfully imported the backup.
However, I then updated to 2.3.0 and now my ESP is no longer reachable at all. I'm just going to reflash him completely over the next few days. But this is another problem. The issue can be closed.
And please excuse my rudeness, I wish you a good, healthy and prosperous 2024!
Thank you very much, also for this great project.
Greetings
Mirko

Just to complete it, after a complete reflash with 2.3.0 everything is running great again! THX


docker compose build fail

hi there, was trying to install the docker-compose "as is" without any change but it's giving the following error
@calcom/prisma:build: error: Environment variable not found: DATABASE_URL.
@calcom/prisma:build:   -->  schema.prisma:6
@calcom/prisma:build:    |
@calcom/prisma:build:  5 |   provider = "postgresql"
@calcom/prisma:build:  6 |   url      = env("DATABASE_URL")
@calcom/prisma:build:    |
@calcom/prisma:build:
@calcom/prisma:build: Validation Error Count: 1
@calcom/prisma:build:
not sure if the solution will be to add the DATABASE_URL into the ARG of the Dockerfile
anyone can help?

I am having the same issue

Anyone found a solution ?

@kaddour-youcef here is a repo that builds from the non docker files and creates a docker container: https://github.com/speckm/calendso-docker

Facing the same issue

If possible, please try the changes in #112.
Prior to building, you can run docker compose up -d database, to make a database available, then use host.docker.internal as the hostname for the DATABASE_URL arg, and that will successfully validate the prisma schemas. Afterwards you can change your database host back to the desired runtime database.

@kaddour-youcef here is a repo that builds from the non docker files and creates a docker container: https://github.com/speckm/calendso-docker

This doesn't work unfortunately.

@Th0masDB #112 worked for me

@Th0masDB #112 worked for me

Unfortuanly for me it doesn't.... It makes the container.... But the container won't run with this error (but I think this is another topic):
/calcom/scripts/start.sh:4

scripts/wait-for-it.sh ${DATABASE_HOST} -- echo "database is up"

             ^^^

SyntaxError: Unexpected token 'for'

    at wrapSafe (internal/modules/cjs/loader.js:1001:16)

    at Module._compile (internal/modules/cjs/loader.js:1049:27)

    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)

    at Module.load (internal/modules/cjs/loader.js:950:32)

    at Function.Module._load (internal/modules/cjs/loader.js:790:12)

    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12)

    at internal/main/run_main_module.js:17:47

I dont know about the docker it did not work, but you can build it from the repo it worked for me!

This issue even exists today.
Prisma schema loaded from schema.prisma
36.82 @calcom/prisma:post-install: Formatted /app/packages/prisma/schema.prisma in 178ms 🚀
37.18 @calcom/prisma:build: cache bypass, force executing 48912e58258dab66
39.92 @calcom/prisma:build: No DATABASE_URL found, skipping migrations
40.00 @calcom/api:build: cache miss, executing 7fa1bf89949b74e8
43.97 @calcom/api:build: destination does not start with /, http://, or https:// for route {"source":"/api/v2","destination":"undefined/health"}
43.97 @calcom/api:build:
43.97 @calcom/api:build: destination does not start with /, http://, or https:// for route {"source":"/api/v2/health","destination":"undefined/health"}
43.97 @calcom/api:build:
43.97 @calcom/api:build: destination does not start with /, http://, or https:// for route {"source":"/api/v2/docs/:path*","destination":"undefined/docs/:path*"}
43.97 @calcom/api:build:
43.97 @calcom/api:build: destination does not start with /, http://, or https:// for route {"source":"/api/v2/:path*","destination":"undefined/api/v2/:path*"}
43.97 @calcom/api:build:
43.97 @calcom/api:build:
43.97 @calcom/api:build: Error: Invalid rewrites found
44.03 @calcom/api:build: ERROR: command finished with error: command (/app/apps/api/v1) yarn run build exited (1)
44.03 command (/app/apps/api/v1) yarn run build exited (1)
44.03
44.03  Tasks:    2 successful, 3 total
44.03 Cached:    0 cached, 3 total
44.03   Time:    39.812s
44.03 Failed:    @calcom/api#build
44.03
44.03  ERROR  run failed: command  exited (1)


Upgrade Java SDK to 6.13.0

6.12.1 of the Java SDK had memory issues. 6.13.0 fixes them.

Again, sorry, Not meant to be here


add argument to store retrieved historical data on a database

add an optional parameter for equity, fund and etf retrieval functions in order to allow the user to store the retrieved content directly on a database instead of storing it into a pandas.DataFrame.
as the most used databases are mongodb and mysql, the tests are going to be developed on pymongo and pymysql, respectively.

In order to reduce extra-dependencies and complexity, the database storage is discarded because of the simplicity of doing it with the retrieved data via investpy, which will be done as following:
import investpy

import json
from pymongo import MongoClient

res = investpy.get_fund_recent_data(fund='Sabadell Rendimiento Cartera Fi',
                                    as_json=True,
                                    order='ascending')

obj = json.loads(res)

client = MongoClient('mongodb://' + username
                     + ':' + password
                     + '@' + username
                     + ':' + port)

database = client['db_name']
collection = database['collection_name']

collection.insert_one(obj)

Take into consideration that as noSQL storage allows documents, JSON objects do not need to be formatted as the investpy output is a JSON as specified with the as_json param.


update api endpoint

should fix https://github.com/FZJ-INM1-BDA/siibralab/issues/44

the failed test is likely due to the the resource that was given to v1 endpoint is signficantly reduced. (1G memory limit).
As a ressult, low resource intensive tasks such as atlas querying would work, getting region specifics (which requires getting the region map etc) would be killed due to OOM.
this is also one of the reason why https://github.com/FZJ-INM1-BDA/siibralab/issues/43 should be persued. the corresponding v3 API call would be:
curl 'https://siibra-api-stable.apps.hbp.eu/v3_0/regions/Component%2057%3A%20Superior%20parietal%20lobule?parcellation_id=minds%2Fcore%2Fparcellationatlas%2Fv1.0.0%2Fd80fbab2-ce7f-4901-a3a2-3c8ef8a3b721&space_id=minds%2Fcore%2Freferencespace%2Fv1.0.0%2Fdafcffc5-4826-4bf1-8ff6-46b8a31ff8e2
'

(n.b. the name change. see https://github.com/FZJ-INM1-BDA/siibra-configurations/commit/3aa5818b794f5579d64c97b84ec83cf2252d2f72)
works without a hitch.


Remove running rubocop on rake task

As pointed out here this is something worth a discussion at least. Sorry for merging without a review!

@tvdeyen ^


autojump: rework

Motivation for this change
Modernize the package, fix fish completion, and update URLs.

fetchurl -> fetchFromGitHub
Update URLs: joelthelion -> wting
mkdir + cp -> install
Use -z flag to set zshshare_dir
Add me to meta.maintainers
Use rec-ursive version instead of let
meta: with stdenv.lib; ...

N.B. I've only tested fish completions.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

/ping @domenkozar

@GrahamcOfBorg build autojump

Success on aarch64-linux (full log)
Attempted: autojump
Partial log (click to expand)

post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/6dj1hs4cv8ws51s5vbzshylp0mdrzkp5-autojump-22.5.1
gzipping man pages under /nix/store/6dj1hs4cv8ws51s5vbzshylp0mdrzkp5-autojump-22.5.1/share/man/
strip is /nix/store/jk6j4lh9v5mvjdbdc35sj0zffhhf6s56-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/6dj1hs4cv8ws51s5vbzshylp0mdrzkp5-autojump-22.5.1/bin
patching script interpreter paths in /nix/store/6dj1hs4cv8ws51s5vbzshylp0mdrzkp5-autojump-22.5.1
/nix/store/6dj1hs4cv8ws51s5vbzshylp0mdrzkp5-autojump-22.5.1/bin/autojump: interpreter directive changed from "/usr/bin/env python" to "/nix/store/vhz9s1dzzbndz032dysnixj8mxyfl30s-python-2.7.14/bin/python"
checking for references to /build in /nix/store/6dj1hs4cv8ws51s5vbzshylp0mdrzkp5-autojump-22.5.1...
/nix/store/6dj1hs4cv8ws51s5vbzshylp0mdrzkp5-autojump-22.5.1

Success on x86_64-linux (full log)
Attempted: autojump
Partial log (click to expand)

post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/rs3rkd9x7avan09yq40a9jym7gna7w3c-autojump-22.5.1
gzipping man pages under /nix/store/rs3rkd9x7avan09yq40a9jym7gna7w3c-autojump-22.5.1/share/man/
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/rs3rkd9x7avan09yq40a9jym7gna7w3c-autojump-22.5.1/bin
patching script interpreter paths in /nix/store/rs3rkd9x7avan09yq40a9jym7gna7w3c-autojump-22.5.1
/nix/store/rs3rkd9x7avan09yq40a9jym7gna7w3c-autojump-22.5.1/bin/autojump: interpreter directive changed from "/usr/bin/env python" to "/nix/store/l9j2jsc9flrbmpf799nw9wdq59gpwms8-python-2.7.14/bin/python"
checking for references to /build in /nix/store/rs3rkd9x7avan09yq40a9jym7gna7w3c-autojump-22.5.1...
/nix/store/rs3rkd9x7avan09yq40a9jym7gna7w3c-autojump-22.5.1

Success on x86_64-darwin (full log)
Attempted: autojump
Partial log (click to expand)

Please restart terminal(s) before running autojump.

post-installation fixup
gzipping man pages under /nix/store/9i6maxr6zqb6m5xi7s8ly00jkfwpwac2-autojump-22.5.1/share/man/
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/9i6maxr6zqb6m5xi7s8ly00jkfwpwac2-autojump-22.5.1/bin
patching script interpreter paths in /nix/store/9i6maxr6zqb6m5xi7s8ly00jkfwpwac2-autojump-22.5.1
/nix/store/9i6maxr6zqb6m5xi7s8ly00jkfwpwac2-autojump-22.5.1/bin/autojump: interpreter directive changed from "/usr/bin/env python" to "/nix/store/10f4qxb00wk9j6cicd9h1qzwqgnc36ji-python-2.7.14/bin/python"
/nix/store/9i6maxr6zqb6m5xi7s8ly00jkfwpwac2-autojump-22.5.1

Until now the recommended way of activating autojump on NixOS was the following:
if type "autojump-share" > /dev/null; then
  source "$(autojump-share)"/autojump.zsh > /dev/null
fi

This PR removes the autojump-share script (which was there to dynamically get location of $out/share). Is there a replacement?

I'm not a Z shell user, and as I (poorly) stated above, I only tested on fish, but now the site functions are installed to $out/share/zsh/site-functions/, so that should Just Work™, right?

Actually you're right. I totally missed that. Thanks!
Eric Bailey<EMAIL_ADDRESS>writes:

I'm not a Z shell user, and as I (poorly) stated above, I only tested on fish, but now the site functions are installed to $out/share/zsh/site-functions/, so that should Just Work™, right?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/40725#issuecomment-393906930

Awesome!

How can I make this work with bash? Currently I'm not sure what to put into my ~/.bashrc instead of the autojump-share script. Do I need to have bash-completions installed?

@Janiczek, I believe so. If you use the programs.bash module, its option enableCompletion defaults to true, so It Should Just Work™. I'm a fish user, so YMMV.

 Do I use programs.bash module if I just nix-env -iA nixpkgs.bash? (If the answer to both is no, can I make this somehow work on Nix itself?)

I'm a bash user.  Now that the autojump-share function has been removed, I'll need to make sure to source $out/etc/profile.d/autojump.sh on startup so that my PROMPT_COMMAND will be updated automatically.
How does Nix handle that?  If there are any profile.d/* files, do these automatically get sourced by /etc/profile?
I currently don't have a /etc/profile.d/ directory, so I'm wondering how this works?  I tried to look in nixpkgs to figure out how /etc/profile.d/ is handled, but I couldn't really find anything.
Will this just be handled automatically?
(Note, this is something completely different than autocompletion.)

For users of oh-my-zsh in nixos systems, the autojump plugin is searched for in /run/current-system/sw/shared/autojump/. In 18.03, I disabled the plugin and used autojump-share in my .zshrc. With #47334 the right links are created when programs.autojump.enabled is set to true and the oh-my-zsh autojump plugin works like a charm.

Nixos beginner here.
It seems that bash completions are lazily loaded (since this commit) and thus that autojump.bash is no longer sourced by default. I added programs.bash.interactiveShellInit = "source /run/current-system/sw/share/autojump/autojump.bash"; and it seems to work, although I am not sure that it is the best way to do things.

The best option imo would be to have autojump.bash loaded automatically when programs.autojump.enable is set (and the same should apply to zsh - this would even remove the need for the oh-my-zsh autojump plugin). I will investigate this when I find time.


Encountered error while trying to install fasttext

anyone has idea how to fix this?
i am using a new profile on company's laptop, the old profile had no issue when installing

use linux and still you need build-essential-12.9, install it as .deb package

In case anyone still looking for a solution. The problem is in the fastText package which doesn't have pre-built binaries for Python 3.10 and later. So it requires a rebuild from source, which requires the correct version of gcc compiler, which in this case is 12.
You can check which version of gcc you have by running this command:
gcc --version
If it's 13, 14 or whatever, then you need to the following:

You need to install previous gcc and g++ version using this command:
apt install gcc-12 g++-12

Then you need to set this version as default one:
update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-12 1

Then install the fasttext package:
pip install fasttext

Then you can finally install the EasyNMT

To revert back, use these commands:

Revert the default version back using this command:
update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-13 1

Remove unneeded compiler:
apt remove gcc-12 g++-12


Resizing browser seems to break renderer

Hi there, apologies if this is a THREE.js issue, I haven't been able to find any instances of it in their forums either.
I am using the <Canvas> component here in my source code, and this is where I load a gLTF model into it.
Whenever a user resizes the browser, at the point when the canvas starts to be resized my scene seems to break, disappear, or possibly be reduced to 0px in one or both dimensions:
https://github.com/threlte/threlte/assets/23481541/f2861e5c-3e27-4556-bfea-5a1f78fe9e30
I thought that invalidating the render manually whenever $threlteSize changed might help, but it doesn't seem to have.
Am I missing something obvious in the docs on useThrelte() that I can use in this scenario, or am I perhaps abusing the way that <T.OrthographicCamera> is meant to be used?

Hi @franknoirot,
You likely missed to add the prop manual to your camera, see this paragraph of the docs: https://threlte.xyz/docs/reference/core/t#camera-props.
I'll close it for now, feel free to reopen if that doesn't solve your problem 🙂


compile

Hello, do I need to compile after adding my own network

If you installed MMDetection with editing mode (use pip install -e . or python setup.py develop), you don't have to reinstall it after modifying the code.


1.0.0: splash screen is not sized properly

Config:
"plugins": {
"meteor-desktop-splash-screen": {
"version": "0.3.0",
"windowSettings": {
"width": 800,
"height": 600
}
}
},
Expected: splash screen is 800 x 600.
Result: splash screen is very small (50 x 50?).
Other than that I haven't noticed any issues when upgrading to 1.0.0.
Maybe the autoUpdate functionality? It seems that, after installing, the app immediately pulled in a new client version (Meteor) but only applied it after restarting (not sure if this is to be expected?).

Please check firstly with<EMAIL_ADDRESS>

Ohh weird that I did not spot this while testing. Electron 2.0 have a lot of issues reported on the window appearance when frame: false transparent: true is used.
I am not sure if I will be able to come up with a workaround until the issues are resolved in Electron.
Will let you know.

Try 0.4.2 now

The screen is now the proper size, however previously the image auto-scaled to 100% of whatever size you set, now it leaves the images as-is and centers it.
This is quite easily fixed by resizing the image, so I will just do that now.

Do you have anything else than
{
"version": "0.3.0",
"windowSettings": {
"width": 800,
"height": 600
}

in plugin settings?
Can you attach the image or do some screenshots?
And I forgot to ask in the first place, on what platform that happens?

Try now with meteor-desktop 1.1.0 and splash screen 0.4.3 - there is a fix for the window problem in electron 2.0.2, not sure if this will help for your case, but it solves the issues with the default style


SichboInteractive.SichboPVR4 version <IP_ADDRESS>

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.1 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Installer doesn't support quiet installation. I submit pull request later, after contacting the program author.


Cordova website plugin improvements

Converts the plugin help pages to markdown so that their formatting remains consistent with the rest of the website and tweaked their content slightly. Also:

Adds credit to npmsearch below the search results
Adds title text to platform icons in search results for accessibility reasons
Removes plugin issue tracker link
CSS fixes for plugins

Merged. Feel free to delete.


fix InitVar problem

Description

Fixes type detection requested in #1940.
This PR adds to changes from #1966 support for InitVar and Optional.
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

@tlambert03 please check. I add conservative support for Optional Which depends on the current implementation of its, but its change should not cause the crash of napari application. But it is not pretty.

cc @kevinyamauchi this has now merge and should unblock #1940


Datasheet scripting does not appear to be working

Describe the bug
I'm a new user but this looks like a great tool, thanks. When I create my army, pressing 1 on the model does not bring up the datasheet.
I have "Enable model scripting" selected on the upload. The descriptions are showing correctly, just not the datasgeet
Expected behavior
That the datasheet should show when I press 1.
Upload the Roster
CA19 - ambitious surge.zip
Thanks for any help!

Happy to look into this further, but as an initial check can you try changing the key for Scripting Button 1 in the key bindings in TTS to something else (like "K" or some other letter with no binding), and try it again using that? Want to make sure it's not some key binding issue.

I've confirmed that this seems to be working on my side for this roster - please try again on your side with some new scripting button set and let me know what happens

Hi Porter,
Just tried this and it works perfectly when switching to an unused key -
very happy!
Thanks
James
On Tue, Apr 14, 2020 at 5:14 AM Porter Westling<EMAIL_ADDRESS>wrote:

I've confirmed that this seems to be working on my side for this roster -
please try again on your side with some new scripting button set and let me
know what happens
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pwestling/battlescribe-roster-parser/issues/20#issuecomment-613216255,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APAL7KREFWIPYCQOOMMA2MLRMPPKRANCNFSM4LX62YEQ
.

Awesome!


⚠ ClamAV has degraded performance

In 639b213, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 77 ms

Resolved: ClamAV performance has improved in dbec79d after 5 minutes.


faas-cli: 0.16.30 -> 0.16.31

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/openfaas/faas-cli/releases.
meta.description for faas-cli is: Official CLI for OpenFaaS
meta.homepage for faas-cli is: https://github.com/openfaas/faas-cli
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.16.31 with grep in /nix/store/iljf9dgdcdqihw5lin52w8y24ni3skc0-faas-cli-0.16.31
found 0.16.31 in filename of file in /nix/store/iljf9dgdcdqihw5lin52w8y24ni3skc0-faas-cli-0.16.31

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

faas-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/iljf9dgdcdqihw5lin52w8y24ni3skc0-faas-cli-0.16.31 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A faas-cli https://github.com/r-ryantm/nixpkgs/archive/5197abc1a2a1e1b366c55dc39d7dd94878f1641b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5197abc1a2a1e1b366c55dc39d7dd94878f1641b#faas-cli

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/iljf9dgdcdqihw5lin52w8y24ni3skc0-faas-cli-0.16.31
ls -la /nix/store/iljf9dgdcdqihw5lin52w8y24ni3skc0-faas-cli-0.16.31/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

faas-cli

Maintainer pings
cc @welteki @techknowlogick for testing.

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

1 package built:

faas-cli


Add LUID Support for HIP devices

HIP API didn't support LUID query before ROCm 6. It is available on Linux and Window HIP SDK 6.1 got released recently. The missing piece-- to have LUID query functional on OIDN for HIP device-- is to also enable the support in OIDN

Thanks, I'll take a look at the new HIP SDK!

LUID is now supported in the devel branch, and it will be released soon!


What is this project used for?

I have no idea the purpose of this project

I also have the same question as #4

but I guess I am fine for now

good!


COLLECTIONS-843: Implement Layered Bloom filter

Implementation to fix COLLECTIONS-843
This is a simple Layered Bloom filter implementation with complex configuration options.
A static method to create a fixed level implementation that does not merge is provided.
An example of a complex time based Bloom filter is provided in the testing code where filters are added to until they are saturated or one second has elapsed and are removed after they are 4 seconds old.
this change is in support of Kafka KIP-936
https://cwiki.apache.org/confluence/display/KAFKA/KIP-936%3A+Throttle+number+of+active+PIDs

Codecov Report

Merging #402 (b8fe880) into master (5e24a6f) will decrease coverage by 0.17%.
The diff coverage is 72.25%.

@@             Coverage Diff              @@
##             master     #402      +/-   ##
============================================
- Coverage     81.19%   81.03%   -0.17%
- Complexity     4605     4662      +57
============================================
  Files           288      291       +3
  Lines         13424    13597     +173
  Branches       1983     1998      +15
============================================
+ Hits          10900    11018     +118
- Misses         1932     1979      +47
- Partials        592      600       +8

Impacted Files
Coverage Δ

...s/collections4/bloomfilter/WrappedBloomFilter.java
26.92% <26.92%> (ø)

...commons/collections4/bloomfilter/LayerManager.java
72.54% <72.54%> (ø)

...s/collections4/bloomfilter/LayeredBloomFilter.java
84.21% <84.21%> (ø)

...apache/commons/collections4/bloomfilter/Shape.java
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

mvn doesn't catch all the issues :(  I just spend a number of hours working out new tests for coverage changes.

I have made a mess of the formatting.  I am working at cleaning it up now.

Recent changes:
Main code
BloomFilterProducer

Cleaned up documentation to specify that implementations should specify if filters used in forEachBloomFilterPair() and asBloomFilterArray are copies or references.
Layer and depth order discussion moved to LayerManager.
asBloomFilterArray coding change accepted, now uses List internally and returns array.
forEachBloomFilterPair documentation corrected.
added flatten()

CountingPredicate

documentation updated

LayerManager

documentation updated.
ExtendCheck and Cleanup classes changed to have only static methods, no public static variables.
added parameter checks for ExtendCheck.advanceOnCount#breakAt, ExtendCheck.advanceOnSaturation#maxN, and Cleanup.onMaxSize#maxSize
removed the ``ExtendCheck.advanceOnSaturation(int)` method
LinkedList is required as the Bloom filter storage implementation (and cleanup argument) as we need rapid access to the intermediate layers in order to return the specific layers.
added method addFilter() to verify that the filterSupplier did not return null.
optimised copy() so that no filters are created during the construction
moved the check for empty filter in next() to be part of the cleanup consumer.
the get() method needs to be public so that access to the specific layer is permitted as required by the LayeredBloomFilter.
target() renamed to getTarget()
clear() now calls addFilter() to ensure a non-null filter is added.
Builder.withX pattern change to Builder.setX
Builder method documentation added.
changed Builder exceptions from IllegalArgument to NPE
The quesiton of whether to use a Builder here is still open.

BloomFilter

added isEmpty()

LayeredBloomFilter

Changed the hyphens in the cite for the article but left the "V1"s in the page numbers as that is how the publisher asks for it to be cited.
updated documentation
Access to layers is provided because there can be additional info associated with the Bloom filter. In the paper and in many implementations the find returns the deepest node that matches. Our finds returns the indexes that match so that the application may select the deepest, the shallowest, the one from the middle, or perhaps all of them and do some subsequent processing.
removed clear(int) and target()
added contains(BloomFilterProducer) to handle the special case.
Continued to return 0 (zero) for the characteristics() as the layered Bloom filter makes some assumptions that work best when it is considered non-sparse. As we don't know what other characteristics may be added in the future, it seems that defining the characteristics here is correct. In addition there is no requirement that all the layers be of the same characteristic.
notes on forEachIndex() in the general case notes for the method indicate that index ordering and uniqueness are not guaranteed.
forEachBitMap() may only return the nbumber of BitMaps specified by the Shape so it must use flatten().
simplified forEachBitMap(), estimateN(), and estimateUnion() to explicitly use flatten()
removed redundant estimateUnion()
the use case for next() is using ExtendCheck.neverAdvance() and then triggering the advance on some outside state change/trigger.

Shape

clarified estimageMaxN() documentation
fixed formatting

WrappedBloomFilter

argument for not moving code to test directory:  Let's consider this for a moment. The example in the test code is precisely what the Kafka KIP-936 is looking for. Now, I don't want to implement a "strange" bloom filter in this class, but I do want an easy way to extend the classes we have. Since they are all final decorating them with a wrapper is the only reasonable solution. So let's provide the solution. If we move it out, then I will have to ask to move it back when the KIP-936 begins development using this library. I believe they are starting that process now.
Updated documentation

Testing code
DefaultBloomFilterTest

Provided access to the two (2) BloomFilter test classes that implement the Defaults (Sparse and non-Sparse).

LayerManagerTest

Significantly modified testOnMaxSize() and testAdvanceOnCount to test wider range of values, including breaking out parameterized tests.
Adjusted to match the methods now provided in LayerManager

LayeredBloomFilterTest

Removed checks of zero depth as it can not be returned.
Reduced time in testExpiration() to approx 600ms

TestingHashers

converted to ThreadLocalRandom.current()
left randomHasher() as public so that it can be utilized in 3rd party Bloom filter testing.

@garydgregory @aherbert  I have merged the latest main branch into this pull request and the last major changes are summarized above.

@garydgregory @aherbert
Gentlemen,
Can I get eyes on the new code please.  I think it is correct and fixes all the previously identified issues.

@garydgregory @aherbert nudge

@aherbert thank you for your review.  Changes have been made to the base code.  One of these days I will figure out how you see all those things that I seem to miss.

Let's make sure we let GitHub squash the commits once this is approved.

@aherbert Have you had a chance to look at the test code?  I have a series of blog posts about Bloom filters coming out "soon" (depending on when my company gets around to finalizing it).  The second one in the series talks about commons-collections Bloom filters.  I am hoping we have this in the 4.5-SNAPSHOT before then.
Thanks to you and @garydgregory  for all your assistance in making the entire package a better submission.

Hi All. Is this PR ready to be merged?

There are some changes to make to the test code. I only reviewed this yesterday.

There are some changes to make to the test code. I only reviewed this yesterday.

👍  TY for the update

@aherbert just a friendly ping.  I'd like to get this closed.

@aherbert @Claudenw
Is this PR ready to merge? If not, what remains? TY!

I previously requested Claude to remove some commented out code in a test class. Otherwise this is fine.


Support for subproject folders (multiple classpaths)

Probably needs some work if someone needs this feature.

Implemented. Will be released in the next release.


Spec generation is non-deterministic

The swagger.json generated by SpringFox varies between builds, even if the underlying code did not change.
The methods for a particular API are not guaranteed to be generated in any particular order, instead being ordered at random every time the spec is generated. While this doesn't affect the functionality of the swagger.json file, it is annoying for our workflow where we commit both swagger.json and a generated client to git. Given that the swagger.json is constantly changing due to the random method order, this results in spurious diffs, and makes actual changes harder to see.

It seems everything is ordered by path, but when the path is the same for two methods, this causes problems.
@PostMapping
public void doSomething(@RequestBody Foo foo) {
// ...
}

@PostMapping(consumes = MediaType.MULTIPART_FORM_DATA_VALUE)
public void doAnotherThing(@RequestParam MultipartFile file) throws IOException {
// ...
}

In this example, the order of the two methods will change from run to run.

Thanks for reporting! Will take a look

Moving it to oas3 support since this situation is not supported in swagger 2.0


Bump dependencies to solidus v1.2

brand-new solidus minor :gem: :tada:

@dfranciosi thats nice, thanks, but the current version check allows 1.1 and 1.2, so there is no need to set it to 1.2 only. Or did you had any problems with using it with 1.1 and 1.2?


Database

Postgres by Flask-SQL-Alchemy

Tables:
Character
import from react class
user id
campaign array - campaign ids
Users
id
username
password
Campaign
id
password
DM: user ID
Characters array - character ids
Notes:
id
Title
text
user id
campaign id
many to many tables:
campaign_character
campaign id
character id
campaign_user
campaign id
user id
many to many : campaign to character
many to many: campaign to user
one to many: user to character
one to many: user to notes
one to many: campaign to notes


Encrypt ldap bind password when queuing to MiqQueue

https://bugzilla.redhat.com/show_bug.cgi?id=1297576
This PR encrypts the Ldap bind password when placing it on the MiqQueue in Args
and decrypts it when popping the message off the MiqQueue. This ensures unencrypted
passwords are not in the DB and also prevents them from being logged.

@abellotti Please review and share any suggestions for where the encrypt and decrypt methods should live if not where I have them. I could imagine their might be other possibilities for where they should be but there was other if ldap logic in the current location.
Also the v2 encrypted test data might be better generated instead of hard coded but I an not sure the best way to generate them. As long as the encrypted and decrypted test data will always match the solution I have should work fine.
Thank you!
JoeV

@chrisarcand and @jrafanie Thank you for the spec simplification suggestions. I like this approach much better. :+1:
Merge if appropriate.
Thank you! JoeV

@chrisarcand Thank you again for the help!
@jrafanie I believe this is ready to merge.

:+1: :tada:

:cake:

:trophy:


Improve the wording of the message that prints when conjure exits unexpectedly

This error message confused me initially. Now that I have context, I figured there was an opportunity to improve the error message a bit. Feedback welcome!

Nice! I like it :D thank you very much, it's definitely an improvement!


[SPARK-20304][SQL] AssertNotNull should not include path in string representation

What changes were proposed in this pull request?
AssertNotNull's toString/simpleString dumps the entire walkedTypePath. walkedTypePath is used for error message reporting and shouldn't be part of the output.
How was this patch tested?
Manually tested.

cc @cloud-fan

Test build #75728 has started for PR 17616 at commit bc30530.

LGTM

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75728/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

Test build #75736 has started for PR 17616 at commit bc30530.

Test build #75736 has finished for PR 17616 at commit bc30530.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75736/
Test PASSed.

Thanks! Merging to master.


Add Hs809

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

@Poonam1607 how can I merge this branch to the master branch of hacktober fest?

Hey @Hs809 , your work is done here. Now one of the maintainers will review your PR and they will merge it to the master branch of hacktober fest.


@conda-forge-admin,please add bot automerge

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/dvc-s3-feedstock#5.


Add functionality to set custom headers to RulesLoader.loadFromUrl()

Expected Behaviour
Actual Behaviour
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Platform and Version
Sample Code that illustrates the problem
Logs taken while reproducing problem

Reopen if we have a requirement for this API


Cydia is not installing after successful jailbreak.

Cydia is not installing after successful jailbreak.
I have Siri, find my iphone, and password disabled, also running in airplane mode when running the jailbreak. I've also tried reinstalling cydia and refresh icon cache. I am also unable to SSH because the connection is always refused. I have attached an image of my iphones info as well as a video of everything that happens. I am also unable to look or pull my logs.

Youtube video link if video doesn't post on here.
https://www.youtube.com/watch?v=SnahZ1yYgVo
Device (please complete the following information):

iOS Version: 12.0
iOS Device: Verizon iPhone XS Max 256GB Gold
unc0ver Version: 3.0.0b46

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[x ] this issue is present on the latest version of unc0ver

Logs
Unable to access the logs.

Cydia is not out for the iPhone XS Max yet. It's only a PARTIAL jailbreak. Wait for Pwn to update the jailbreak for Cydia support.

@andrewlove1 makes sense now, thank you.

I'd suggest closing this issue since this wont help them.


rocon_tutorials: 0.6.6-0 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository rocon_tutorials to 0.6.6-0:

upstream repository: https://github.com/robotics-in-concert/rocon_tutorials.git
release repository: https://github.com/yujinrobot-release/rocon_tutorials-release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.18
previous version for package: 0.6.5-0

chatter_concert
* disable zeroconf option
* Contributors: Jihoon Lee

gazebo_concert

No changes

rocon_app_manager_tutorials

No changes

rocon_gateway_tutorials

No changes

rocon_tutorials

No changes

turtle_concert
* default values for request turtle closes #58 <https://github.com/robotics-in-concert/rocon_tutorials/issues/58>
* Contributors: Jihoon Lee

This downgrades concert services. Please regenerate the pull request or rebase.


"Add explicit cast" code fix inserts the wrong cast

The following code contains an error because there is no implicit conversion from int to short.
short s = 0;
int i = 0;
s += i;

OmniSharp offers a fix for this error: "Add explicit cast". However, applying the fix results in this code:
short s = 0;
int i = 0;
(void)(s += i);

This not only doesn't fix the error, but also introduces another error because it's illegal to cast to void. OmniSharp then offers the same fix again, which just leads to more void casts.
The correct fix should be this:
short s = 0;
int i = 0;
s += (short)i;

OmniSharp version: 1.39.0

Thanks for the report - this is a bug in Roslyn not in OmniSharp (same happens in Visual Studio) - I opened an issue there https://github.com/dotnet/roslyn/issues/66369


bind-9.19.24  run issue as segfault error.

I'm on:

bind-9.19.24
Linux centos7-9 3.10.0-1160.71.1.el7.x86_64
cpu: 12core
memory: 64G

I have a error message below in /var/log/messages.log :
message.log:
Aug18 04:38:10 dns01 kernel:isc-1oop-0034[14137]:segfault at 9f ip 00007fccd60365d8 sp 00007fcc6aff3d90 error 6 in libns-9.19.24.so [7Ecc6028000+17E000)*
Aug 18 04:38:10 dns01 abrt-hookccpp: Process 14102 (named)of user 53 killed by $rGseGv - dumping core
Aug18 04:38:14 dns01 systemd:named.service:main process exited, code-killed, status=11/$EGV
Aug18 04:38:14 dns01systemd:Unit named.service entered failed state.18Aug04:38:14 dns01systemd:named.service failed.18Aug04:38:14 dns01abrt-server: Executable '/opt/named/sbin/named' doesn't belong to any package and processUnpackaged is set to "no
Aug18 04:38:14 dns01 abrt-server;'post-create"on"/var/spool/abrt/ccpp-2024-08-18-04:38:10-14102'exited with 1
Aug1804:38:14 dns01 abrt-server: Deleting problem directory"/var/spool/abrt/ccpp-2024-08-18-04:38:10-14102'

it's segfault at 9f ip 00007fccd60365d8 sp 00007fcc6aff3d90 error 6 in libns-9.19.24.s0
I don't konw it's like memory leak or bind9 bugs.
but I don't find any CVE message.
please help me.

Hello,
Unfortunately I'm not sure how is connected with the project, but just in case will try to replicate it and report here.

Hello,
Unfortunately I cound not replicate and it is not related to the tool, so I'm closing it. If you find new issues, please report again.


Error when running command

I've tried to get the editor to run but I keep running into an error in the terminal.
 ERROR in libsass bindings not found. Try reinstalling node-sass?
@ ./app/styles/index.scss 4:14-276 11:1-15:3 12:19-281

Can someone please help out. Its my wish to get a code in the dark setup in southern California.
cheers

I have the same error, on linux and windows.

Have you guys tried manually installing Atom's node-sass package?

Yes, didn't work

This is a common problem affecting a number of packages. I don't remember which was which, but an update to either Node or to node-sass broke support for previous versions of the other.
It's caused by the version of Node on your system vs the version of node-sass that's running.
It looks like the version of sass-loader in package.json is using a very outdated version of node-sass. Updating this dependency fixes the problem for me. See my PR #9


Adding functions to handle custom agent pools.

Overview/Summary
Adding new functions to allow functionality to manage custom agent pools.
This allows you to pin an agent pool to a Azure Virtual Machine Scale Set.
I've added some examples of how to run the New-AZDOPSElasticPool, however I'll need to dig into PlayPS to create this using the same tooling used across the project.
No tests have been created as of yet.
This PR fixes/adds/changes/removes
Adding new functions to:

Create a new ElasticPool
Get/List ElasticPool
Get/List Node
Get/List Pool

Closes #53
Closes #57
Closes #55
As part of this Pull Request I have

[X] Checked for duplicate Pull Requests
[X] Associated it with relevant issues, for tracking and closure.
[X] Ensured my code/branch is up-to-date with the latest changes in the main branch
[] Performed testing and provided evidence.
[Half X!] Updated relevant and associated documentation.

Resolving the conflig in azdops.psd1.
Added the functions that has been commited to main and not included when these functions were written.

Please add basic tests to the functions as well as documentation,
Or just documentation so its easier for me to add tests afterwards.

@SebastianClaesson ping me and I can help you get started with PlatyPS. There are guidelines in the contribution guide that might help you get started.

Closing pull request as a new one with correct documentation and tests will be opened from my fork instead.


chore: require acking v0.4 upgrade instructions via env var

This will require all end users to acknowledge that they are aware of upgrading in the lockstep requirement.

@douglaz Do you think this is OK w.r.t. to infra automation etc.? I think it shouldn't be a problem, but would love a second opinion.

Looks ok to me. But for people running on third party services like Clovyr it will be pretty much impossible to safely upgrade, I guess.

Ping @Kodylow for opinion.

But for people running on third party services like Clovyr it will be pretty much impossible to safely upgrade, I guess.

@douglaz You mean due to the lockstep upgrade requirement, right? Or is setting env var an extra problem?

ACK. yes this doesn't work with clovyr, no one is running mainnet clovyrs besides me though so that's fine.

Successfully created backport PR for releases/v0.4:

#5616


f_c float/tuple option is really ugly

I think having to juggle between float and tuple is confusing, as oppose to always requiring a tuple and put in 0s for low/high-pass.

agreed. but can you do it? :)

ffs.

I think it's reasonable to always accept tuples AND also accept an int/float if the filter type is highpass or lowpass

@rdgao What do you think needs to be changed for the filtering to be ready for v1.0?

bandpass/bandstop requires tuple, and tuple and float are acceptable for low/high-pass?
so lowpass would only look at fc[1], and highpass fc[0]?

sounds good

so am I doing it?

looks like you're assigned to this issue

should we deprecate the option to use f_lo/f_hi?

alright I'm taking it out. I'm the captain now.

solved in PR#72


Unable to access archetype sorting page

https://pennydreadfulmagic.com/admin/archetypes/
results in

Tom gave me access about a month ago. I have tried to access this via a different browser (discord login and all) with the same result.
Tried on Firefox and Edge

Works on fresh installation of Chrome. Strange.


PlaybackRatePlugin is not defined

Tried Both way to call the plugin. But getting the same error every time.
plugins: {
             'core' : [PlaybackRatePlugin]
	},
plugins: {
             core : [PlaybackRatePlugin]
	},

Uncaught ReferenceError: PlaybackRatePlugin is not defined
at window.onload ((index):32).
After that i take code and compile it on my local machine. Files are generated, but getting the same error.

It looks like the instructions for using this outside of an ES6 module are incomplete.  I'm assuming you're not using webpack or any other ES6 bundler, correct?
The workaround would be to do the following:
<script src="https://cdnjs.cloudflare.com/ajax/libs/clappr/0.2.87/clappr.min.js"></script>
<script>window.clappr = Clappr</script>
<script src="lib/lib/clappr-playback-rate-plugin.min.js"></script>
<script>window.PlaybackRatePlugin = window['clappr-playback-rate-plugin'].default</script>
<script>
    // initialize player as before...
</script>

Also see #8

Its because i didn't add this in code.

Now its working fine. Thanks @bikegriffith for your instant help.


sometimes the data recorders silently die

I've noticed that sometimes a data recorder, usually one of the visibility recorders, stops receiving packets/reporting its status.  There aren't any clues about why this happens since the logs just stop but the process doesn't completely die either.

https://github.com/lwa-project/ovro_data_recorder/commit/6f15499f291a50eb73a71084183394586842f3d7 adds a WatchdogLogger that looks at the age of the "summary" monitor point.  Maybe this will help find when this problem pops up.


[Docs]: Audit log streaming for google cloud

Type
Improvement idea
What do you want to report?
Is seems the Organization > Audit Log export explanation is incomplete for Google Cloud Streaming. The access credentials needed are not clear here (usually GCP uses json for auth)
Amir could help us here
Code of Conduct

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

Amir advised we use hmackeys for exporting to GCP: https://cloud.google.com/storage/docs/authentication/hmackeys#overview


Add webchat to VAT enquiries page and remove opening times

This enables the new webchat for the VAT enquiries page.
It also removes the opening times for webchat. This is because the current opening times of HMRC webchat are more flexible than suggested. Sometimes webchat is open earlier or later in the day, and at times may be closed while advisors handle other channels. This means the published opening times are misleading and causing confusion.
Should be merged alongside https://github.com/alphagov/static/pull/828

👍  this should work, you need to update both webchat.js and contact_presenter.rb which is a faff to keep in sync but you already did.


Clarify CVE / security fix

Not sure if you want to be this explicit, but took the example from below.
Also, there is an CVE for Swiftmailer, instead those two from phpmailer, see https://legalhackers.com/advisories/SwiftMailer-Exploit-Remote-Code-Exec-CVE-2016-10074-Vuln.html

Perfect!

Thank you @barryvdh.


[ROS2] Check the re-taring delay

Currently, the pre_moveto_config idiom waits for the re-taring service to succeed and then immediately re-enables the watchdog listener. However, the core question is: do the FT sensor readings pause for ~0.75s before the service returns success, or after?

If before: pre_moveto_config is fine, just modify dummy_ft_sensor to mimic this behavior.
If after: add a sleep to pre_moveto_config, no need to modify dummy_ft_sensor.

This commit in forque_sensor_hardware addresses the issue. Now the F/T sensor keeps publishing data during retaring, it just drops from 100 Hz to 10 Hz. As a result, there is no longer a need to toggle the watchdog listener off during re-taring.


Jest test are slow

I'm trying to write some basic tests using jest and I figured out that Jest is super slow.
I have three simple tests and running them takes 5 seconds.
When I clone este and run gulp jest, it takes ~1.4 sec, which is so much for running only one test for getrandomstring.js
I tried to google how to improve tests speed but I haven't found anything interesting. Lot of users recommends to use mocha instead of jest. They showed some benchmarks and mocha was running over 100 test in ~3 secs.
What do you think about mocha? Wouldn't it be better?

I just tried to setup mocha and run tests for my project and they passed in 222ms. I think it's big difference to 5sec

Possibly related, https://github.com/facebook/jest/issues/116

I have to say I didn't liked jest, because I expected issues with auto mocking. I was using Mocha for years in my previous Este stack also with JSDOM, and it was super fast.
I have to rethink unit tests strategy for new Este, probably going back to Mocha. I will also add test strategies into wiki.

Jest will be removed.

Can confirm improving babel parser to skip node_modules as well as setting correct testPathDirs (so it does not loops through node_modules) improves it to run within 2/3 seconds for ~20 tests. To me, not a problem given the nice React-Native support and the fact, it still runs fast on the CI.

I can confirm that fixing babel parser to skip node_modules as well as setting correct testPathDir so it does not loop through node_modules makes start-up time to be less than 1 second. Also, optimising imports makes my tests run in less than 0.1 so very acceptable.

Still, jsdom is deal breaker for Node 0.12 and what is worse, auto mocking is brittle and magic.

I am testing react native, so auto mocking is actually my friend (React-Native provides lots of modules you can require during its runtime that are not available in test environments, so at least with Jest I can easily mock them, see https://github.com/este/native/blob/master/src/app/menu.style.js#L1

I think as per tests, what matters are the solid and reasonable use cases, not the framework being used :}


Can't publish bot

400 - {"error":{"code":"BadArgument","message":"Failed to parse azure account information object object."}}
Message:

My publish configuration
{
"accessToken": "eyJ0eXAixx",
"name": "QnAMaxx",
"environment": "composer",
"settings": {
"applicationInsights": {
"InstrumentationKey": ""
},
"cosmosDb": {
"cosmosDBEndpoint": "",
"authKey": "",
"databaseId": "",
"collectionId": "",
"containerId": ""
},
"blobStorage": {
"connectionString": "",
"container": ""
},
"luis": {
"authoringKey": "767xxx",
"authoringEndpoint": "https://westus.api.cognitive.microsoft.com",
"endpointKey": "",
"endpoint": "",
"region": "westus"
},
"MicrosoftAppId": "f29f8xxx",
"MicrosoftAppPassword": "4xxxx"
},
"subscription": "452xxx",
"hostname": "qna-rxxx",
"luisResource": "luis-xxt"
}

@samaroj you need to provide the endpointkey as well for luis publish.

Hi @samaroj any updates?

Hi @samaroj I am closing this issue for now. Feel free to reopen it when you think it necessary. Thanks!

Where do you find the luis endpoint key ?

I'm having the same issue. When I add LUIS to my BOT I can't publish it on Azure. But in local with Emulator it's running good.

Was this ever resolved? I am getting the same error now

Hi @tekram
Composer has released its 1.1.1 version, which you can try here.
Apologies for the inconvenience of the publishing issues. We will address as many as we can for the next release in November.
Thanks again for your feedback.

I am currently running 1.1.1. Until the next release, what do you recommend?
@zxyanliu

Was this ever resolved? I am getting the same error now

I couldn't get any fixes for it still

Alternatives for deploying?


Support for provisioning new cluster with spot pool

As far as I understand there is no way to create a new AKS cluster with an additional spot node pool, am I right? Is there a plan to implement this feature for GA?

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

ID: 5fc40e8e-558d-171c-2fd9-82b67f89d221
Version Independent ID: 9a757f12-cf86-2095-0f6a-37397024e3a5
Content: Preview - Add a spot node pool to an Azure Kubernetes Service (AKS) cluster - Azure Kubernetes Service
Content Source: articles/aks/spot-node-pool.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

Is your question about creating a new AKS cluster with a spot node pool instead of adding to the existing AKS cluster?
That is not supported yet. You must add a spot node pool to an existing cluster that has multiple node pools enabled.

I'd like to create a cluster with three node pools, two standard pools and one spot node pool.  And then we can assign kubernetes pods to different pools using node labels. We use amazon EKS the same way to save cost in test/dev environments. That would be very beneficial on azure platform too.

@ohorvath You can create a cluster with additional node pools, including spot pools, using an ARM template
cc @palma21

I tried to deploy a new cluster using ARM with scaleSetPriority: Spot against api 2020-02-01 without any luck. The pool created as regular.

Never mind, I've used incorrect parameter names but as I didn't get any error message I thought this was ok. Now the deployment works fine, but the documentation is not so clear about the support of creating new clusters with spot pools. Thanks for the help anyway.

@zr-msft I think it is not clear from the documentation. Can we add this information to the doc?

I will share this feedback with the author.
Thanks for bringing this to our attention. We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


DEV: Pin development and minimum required version of numpy

closes #24

Codecov Report

Merging #26 (c17d9f8) into main (eaf5094) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #26   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         4    +1
  Lines          175       184    +9
  Branches        22        24    +2
=========================================
+ Hits           175       184    +9

Impacted Files
Coverage Δ

pyloras/_common.py
100.00% <100.00%> (ø)

pyloras/_loras.py
100.00% <100.00%> (ø)

pyloras/_prowras.py
100.00% <100.00%> (ø)

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 eaf5094...c17d9f8. Read the comment docs.


Fix Agenda sort collapse all/expand all

while the agenda is being sorted it can happen, that the collapsed items expand all at once
How to recreate:

navigate to agenda > sort agenda
collapse all
let an autoupdate happen (e.g. change your own presence)
everything expands again

wanted behaviour:
the collapsed items should not expand because of an autoupdate, they should only expand when they are expanded again

Also happens in other filtered lists. @emanuelschuetze can give more information.


[Question] Tutorial 11, Variational dequantization

Tutorial 11
Hello, I hope you are well. I am studying for a Ph.D. in normalizing flow, and this tutorial is a fantastic help. However, I have five questions I would appreciate if you could answer.
I have doubts about cell number 10:
img = (z / 255.0) * 2 - 1 # We condition the flows on x, i.e. the original image
# Prior of u is a uniform distribution as before
# As most flow transformations are defined on [-infinity,+infinity], we apply an inverse sigmoid first.
deq_noise = torch.rand_like(z).detach()
deq_noise, ldj = self.sigmoid(deq_noise, ldj, reverse=True)

I wonder:

why do you want img in the range [-1, 1]
why do you want the deq_noise in the range [-inf, +inf]
Is that because you apply the inverse of the sigmoid to the images throughout the other flows after de-quantizing?
Isn't it enough to use the deq_noise without conditioning the flow to the image? I don't get the idea of conditioning the noise to the transformed image in the range [-1, 1].

Extra:
In my case, I am familiar with the FrEIA framework, and they implement the conditional INN in this way. They first split the input tensor x. Then, they add the condition c to the half and pass it through the subnet.
x1, x2 = torch.split(x[0], self.splits, dim=1)
if self.conditional:
          x1c = torch.cat([x1, *c], 1)
          a1 = self.subnet(x1c)

You first concatenate the condition, ingest the subnet, and split the vector.
if orig_img is None:
          nn_out = self.network(z_in)
else:
          nn_out = self.network(torch.cat([z_in, orig_img], dim=1))
          s, t = nn_out.chunk(2, dim=1)

Is there something I'm missing?
Thanks for your time!

@mjack3 in your second question, the mask gets applied to z_in, effectively splitting it. The masked z_in and condtion gets passed through the network to predict s,t which then gets applied to the z_in multiplied by the inverse of the mask, i.e. the "other" half. While the two implementations are not exactly the same, I think they achieve the same thing.
Also hope @phlippe can shed some light on this and your first questions

Hi @mjack3, thanks for your questions, and thanks @cviviers for already answering the second question! Let me try to give you some more intuition below.

why do you want img in the range [-1, 1]

This image will be the input to a neural network. As with any neural network, you want the input to be ideally zero-centered and have a standard deviation of 1 (rest of the network is designed for that, e.g. see initialization - Tutorial 4). A cheap, approximate way of getting this with images is to normalize them in the range [-1, 1].

why do you want the deq_noise in the range [-inf, +inf]

We will apply normalizing flows on this deq_noise, which are defined for an input range of [-inf, +inf] and output range of [-inf, +inf]. If we would put in a range of [0, 1], we are not guaranteed to get actually outputs in the range [0, 1], which means the flow may not be invertible in your expected range. Going to the [-inf, +inf] makes your life easier, since you can freely choose from your flow operations.

Is that because you apply the inverse of the sigmoid to the images throughout the other flows after de-quantizing?

Before we dequantize, we will map this noise back to [0, 1] (see the sigmoid 2 lines later). We want the flows to operate on [-inf, +inf], and an easy way to invertibly transition between [-inf, +inf] and [0, 1] is a sigmoid (or its inverse for reverse).

Isn't it enough to use the deq_noise without conditioning the flow to the image? I don't get the idea of conditioning the noise to the transformed image in the range [-1, 1].

Conditioning on the image allows your model to flexible adjust the noise distribution for each individual image, which represents a sub-distribution in your global marginal distribution (basically $p(z|x)$ vs $p(x)$ with $z$ being the latent variables and $x$ the image). If you have a completely black image, you may want to use different noise distributions on these black pixel versus a very bright image with rare black pixels. Overall, you can make the life of the model much easier by that.

Extra

As @cviviers already correctly mentioned, they are basically doing the same thing. The masking strategy, commonly used in flows, simply supports any form of mask, while the splitting approach requires a certain structure in x such that you can split.
Hope this helps, let me know if you have any follow-up questions!

Great! Thanks!


:four_leaf_clover: Proposal:  github-action plugin

What Would You Like to Add? Why Is This Needed?
we should add a plugin for github-action with a more generic function. we have golang, python, nodejs for now, But their design is too simple. We can create a new github-action plugin for more generic usage.
Design

support sonarqube
support multi language
support image repo
support notify (dingding)

Anything else

lgtm, but could you give some more detailed design here?


Save Button Appears Without Re-testing After Credential Changes in Plugin Form

In the plugin form, after a user successfully tests the credentials, the "Save" button becomes available. However, if the user makes any changes afterward, the "Test Connection" button does not reappear, allowing the user to save without re-testing.
Steps to Reproduce:

Navigate to Plugins.

Click on "Add Plugin."

Fill in all required details and proper credentials.

Click on "Test Connection."

Make any changes to the form, Test connection won't reappear, and save button is enabled

Specific File Affected:

raggenie/ui/src/pages/Configuration/ProviderForm/ProviderForm.jsx

Proposed Solution:

Disable the "Save" button when any changes are made and re-enable the "Test Connection" button

@agberoz  Please assign me this issue

Hello, I would like to work on this issue. Could someone please assign it to me?


ThermoRawFileParser not recognizing some instruments?

Hi, we have discovered that many of our ThermoRawFileParser converted files do not have the correct instrument model encoded in them. Example:
    <referenceableParamGroupList count="1">
      <referenceableParamGroup id="commonInstrumentParams">
        <cvParam cvRef="MS" accession="MS:1000483" value="" name="Thermo Fisher Scientific instrument model" />
        <cvParam cvRef="MS" accession="MS:1000529" value="SN03468B" name="instrument serial number" />
      </referenceableParamGroup>
    </referenceableParamGroupList>
    <softwareList count="1">
      <software id="ThermoRawFileParser" version="1.3.0-pre">
        <cvParam cvRef="MS" accession="MS:1000799" value="ThermoRawFileParser" name="custom unreleased software tool" />
      </software>
    </softwareList>

The instrument model is not provided, just the ambiguous parent term.
For the same file, msconvert provides this:
    <referenceableParamGroupList count="1">
      <referenceableParamGroup id="CommonInstrumentParams">
        <cvParam cvRef="MS" accession="MS:1001742" name="LTQ Orbitrap Velos" value=""/>
        <cvParam cvRef="MS" accession="MS:1000529" name="instrument serial number" value="SN03468B"/>
      </referenceableParamGroup>
    </referenceableParamGroupList>
    </sampleList>
    <softwareList count="2">
      <software id="Xcalibur" version="2.7.0">
        <cvParam cvRef="MS" accession="MS:1000532" name="Xcalibur" value=""/>
      </software>
      <software id="pwiz" version="3.0.20155">
        <cvParam cvRef="MS" accession="MS:1000615" name="ProteoWizard software" value=""/>
      </software>
    </softwareList>

This seems to happen for both instruments:
"name": "LTQ Orbitrap Velos"
"name": "LTQ Orbitrap Elite"
Would you add those instruments to ThermoRawFileParsers list of recognized instruments?
The above example comes from the raw files in:
ftp://ftp.pride.ebi.ac.uk/pride/data/archive/2015/02/PXD000660

Hi Erik,
thank you for reporting the problem. The instrument in the files you refrence is provided as "Orbitrap Velos Pro", that does not have a specific CV term, the closest one is "LTQ Orbitrap Velos".
As a fix I added "Orbitrap Velos Pro" resolving to "LTQ Orbitrap Velos", but none of the the referenced files was from Orbitrap Elite, thus I will need an example to add Oribtrap Elite in the same way.

Thanks for this. I have requested a new term for LTQ Orbitrap Velos Pro:
https://github.com/HUPO-PSI/psi-ms-CV/pull/31/files
Please review that PR.
As for the Orbitrap Elite, please see the first few files here:
ftp://ftp.pride.ebi.ac.uk/pride/data/archive/2019/08/PXD013646
Apparently the "LTQ Orbitrap Elite" and the "Orbitrap Elite" are the same instrument, just different names.

I have updated the mapping in ThermoRawParser with new terms. I will talk with @nielshulstaert to get the new release.

Any news on a new release?

I've added these in msconvert as well. The Exploris 120 and 240 and the Orbitrap ID-X too. (NB for @caetera: that is the instrument model string to check for)

Thanks, @chambm !
@caetera , new term is here:
https://github.com/HUPO-PSI/psi-ms-CV/pull/37/files

Added Orbitrap ID-X in ded9953
Sorry, no updates on the new release. I talked with @nielshulstaert to review my changes (two pair of eyes are better, than one) and do a release some time ago, but I haven't heard from him since then.

okay, thank you! We're still using 1.3.0-pre (or some version of that if there's more than one) but it would be super nice to have an official 1.3.0 or whatever version with these changes in there and whatever else has happened. Thanks!

Release is published.


Package Requested

[X] I would like someone else to build the manifest.
[x] I would like help so I can submit the manifest.
[X] I have performed a search and couldn't find this package.
[X] I have checked that the installer for this package is not a standalone or portable executable or a .zip file
[x] I think there is a new version available and I have provided the URL.

Please provide the following information
Publisher: vladimiry
Publisher Url: https://github.com/vladimiry/ElectronMail
Package Name: ElectronMail
Description:  Unofficial ProtonMail Desktop App
Package Version: 4.15.0
Installer URL: https://github.com/vladimiry/ElectronMail/releases/download/v4.15.0/electron-mail-4.15.0-windows-x64-nsis-installer.exe
Current Package Identifier (for new versions):

The last 3 times this have been submitted it have been blocked by VC++2015-2019 https://github.com/microsoft/winget-pkgs/pull/20471#issuecomment-880163897 install prompt, so it probably has to wait for Dependency support to roll out (leave the issue open =))

I think this should be enabled now after this commit: https://github.com/vladimiry/ElectronMail/issues/528


Please consider to compile static libraries with -fPIC on Linux

Static libraries (2.4.2) cannot be used for linking of a shared library on x86-64 Linux, the linker returns the following error:

relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC SFML/lib/libsfml-system-s.a: error adding symbols: Bad value

Do you mean we should add this to CMake? Or do you just mean for the builds on the website? Or the builds that come with your package manager?

I encountered this problems with static libraries downloaded from the homepage as I tried to use them for linking of a shared library. But I think if you are going change that, it only makes sense if you change it everywhere.
Here is a small reproducer, I hope it explains what I mean:
//error.cpp
#include <SFML/System.hpp>
void log_error(){
   sf::err()<<"Error!";
}

and now:
g++ -c error.cpp -o error.o -fPIC -ISFML-2.4.2/include
g++ error.o -shared -LSFML-2.4.2/lib -lsfml-system-s -o my_err.so

leads to:

/usr/bin/ld: SFML-2.4.2/lib/libsfml-system-s.a(Err.cpp.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
SFML-2.4.2/lib/libsfml-system-s.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status

I'm not sure this is a feature request and consider it to be a bug of the build-configuration: I think the option -fPIC should be used, so the built SFML-libraries can be used for building shared libraries out of the box. But it is also possible, that I'm wrong - I don't have much experience with this kind of things.

Never noticed this not set. Can't test it right now, but does it compile if you omit -fPIC for our own code? Besides that I'd say it should be added by default. Can't think of any reason not to use it right now.

Traditionally, static libraries are compiled without -fPIC on Linux because it usually doesn't have much use and on some architectures there is a small performance penalty for using it. You only need it if you're compiling a shared library using it, whereas I expect most people want to compile their entire executable statically (which does not need the flag).

@MarioLiebisch To my knowledge, -fPIC is obligatory for shared libraries on Linux x86-64. So if I omit  -fPIC for the cpp, the linker will complain already about the first object-file.

As pointed out by @jcowgill, static libraries on Linux are commonly compiled without -fPIC, as such SFML will follow this semi-standard.
Additionally the Linux binaries provided as download on the website are not really the recommended way to use SFML under Linux. Either use the SFML package provided by your package manager or if you need some special version or changes (like having the SFML libraries built with -fPIC), build SFML from source yourself.
I'm going to close this issue. If you think this is too important to not be followed up further, please make a case for it on the SFML forum.


chore: Update default pixi gitignore and gitattributes

With .pixi/config.toml being a valid configuration place, what do you think about excluding it from .gitignore?
Also, with pixi.lock file diffs getting very large, especially with multi-envs, I think it makes sense to add linguist-generated=true (in some cases, github refused to render the markdown anyway). https://github.com/pavelzw/pixi-diff-to-markdown can generate a bit prettier diffs anyway.
Maybe it makes sense to have a diff mode pixi diff pixi.lock.old pixi.lock.new as well that generates the same json output as pixi update --json and allow people to configure their git diff to use pixi similar to how bun does it.

The diff thing is awesome!


Installation instructions

Hi folks,
Can the installation instructions have more content added? It presumes a lot of prior knowledge.

Specifically, which permissions do we need to enable for the new GitHub app we need to create?
Can we get examples of the webhook URL, etc needed for setting up the GitHub app, for when we're hosting on Glitch?
Can we get some instructions on how we "upload" the project to Glitch? I presume we add Glitch's repo as a 'remote' to our cloned copy of this project, and push to that remote?

https://github.com/waffleio/cardcannon/pull/3 feedback appreciated


Proper Alias System

Cleaned up the way aliases used to be made, they no longer require creating another command entirely. Just add a table as the last argument in the xAdmin.Core.RegisterCommand function.
Example:

(also makes it work with the new permission table added in the last PR i made)

This PR will also fix MySQL not working because of my last PR's new autoloader. It now forces the DB config to load first.


Trev8939/stretch renderer

Adds a sample demonstrating use of the StretchRenderer.

https://devtopia.esri.com/runtime/java-android-sdk/issues/1303

@TADraeseke Need to add module to settings.gradle

@doneill All proposed changes made. Back to you!

@TADraeseke Updates look good to merge.


Refactoring Log Targets

Removes old targets and replaces them with spdlog infrastructure.
Summary of Changes

Test Instructions

/format