NTR: [serotonin-gated anion-selective channel activity]

NTR: [serotonin-gated anion-selective channel activity]
Please provide as much information as you can:

Suggested term label:
serotonin-gated anion-selective channel activity

Definition (free text)
Enables the transmembrane transfer of an inorganic anion by a channel that opens when the biogenic amine serotonin has been bound by the channel complex or one of its constituent parts.
Serotonin (5-hydroxytryptamine) is a neurotransmitter and hormone found in vertebrates and invertebrates.

Reference, in format PMID:#######
PMID:11100728

Gene product name and ID to be annotated to this term
Q9GQ00	mod-1	Serotonin-gated chloride channel mod-1

Parent term(s)
GO:0099589	serotonin receptor activity
GO:0099095	ligand-gated anion channel activity

Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?
Not sure but would also like to request:

**NEW CHILD TERM REQUEST (child to "serotonin-gated anion-selective channel activity", above).
serotonin-gated chloride ion channel activity

Definition of new child term (free text)
Enables the transmembrane transfer of a chloride ion by a channel that opens when the biogenic amine serotonin has been bound by the channel complex or one of its constituent parts.

Cross-references

For enzymes, please provide RHEA and/or EC numbers.

Can also provide MetaCyc, KEGG, Wikipedia, and other links.
https://en.wikipedia.org/wiki/Ligand-gated_ion_channel
https://tcdb.org/search/result.php?tc=1.A.9

Any other information
This new term(s) would avoid having to co-annotate to 'serotonin receptor activity' and 'ligand-gated anion channel activity'.

@vanaukenk

Sorry - forgotten how to tag people here!

@Pauldenny Is it useful to create serotonin-gated anion-selective channel activity in addition to serotonin-gated chloride ion channel activity? In other words, are there other serotonin-gated anion (but chloride) channels that we know of?
In comparison, GO:0022851 GABA-gated chloride ion channel activity does not have a grouping parent GABA-gated anion-selective channel activity.
Thanks.

Please reopen if there are more comments. Thanks.

I was also wondering if we really needed the anion grouping term?
Le mar. 12 juil. 2022 à 7:40 PM, Raymond Lee @.***> a
écrit :

@Pauldenny https://github.com/Pauldenny Is it useful to create
serotonin-gated anion-selective channel activity in addition to
serotonin-gated chloride ion channel activity? In other words, are there
other serotonin-gated anion (but chloride) channels that we know of?
In comparison, GO:0022851 GABA-gated chloride ion channel activity does
not have a grouping parent GABA-gated anion-selective channel activity.
Thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/geneontology/go-ontology/issues/23509#issuecomment-1182091592,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEPWUHHFAEQDD5CVLH7WH3VTWUYHANCNFSM5Y7NS44Q
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Having looked in PubMed (I'm not an expert in this field), perhaps the grouping term
serotonin-gated anion-selective channel activity
is not necessary - I couldn't find any examples, other than the already known chloride-selective worm channel

Thanks for checking on this @Pauldenny


CIS tokens patch

This PR enables the CIS addon to switch away from the tokens based auth.
The work on the enable/disable hooks will not run on 1.28 snap as that snap will ship without token auth by default. The work on the hooks is only relevant to snaps that got refreshed to the 1.28 version.
This PR also includes updates on the README on how to configure a pre 1.28 node not to use auth tokens.

As the corresponding PR on the MicroK8s repo has landed I am merging this too to get the GH tests passing again. Please review when you get the time.


Error thrown from NodeRSA.js:178 "Empty key given" when attempting to start the server

I followed your steps on https://github.com/eduardoboucas/staticman:

Clone the repository and install the dependencies via npm
Create a development config file from the sample file.
Edit the newly-created config file with your GitHub access token, SSH private key and the port to run the server.
I additionally run export NODE_ENV=development
Start the server.

When I start the server I get the following error:
martm106-3AH03Y:staticman martm106$ npm start

><EMAIL_ADDRESS>prestart /Users/martm106/Dev/staticman
> if [ ! -d node_modules ]; then npm install; fi

><EMAIL_ADDRESS>start /Users/martm106/Dev/staticman
> node index.js

/Users/martm106/Dev/staticman/node_modules/node-rsa/src/NodeRSA.js:178
            throw Error("Empty key given");
            ^

Error: Empty key given
    at NodeRSA.module.exports.NodeRSA.importKey (/Users/martm106/Dev/staticman/node_modules/node-rsa/src/NodeRSA.js:178:19)
    at Object.<anonymous> (/Users/martm106/Dev/staticman/controllers/encrypt.js:8:5)
    at Module._compile (module.js:569:30)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:503:32)
    at tryModuleLoad (module.js:466:12)
    at Function.Module._load (module.js:458:3)
    at Module.require (module.js:513:17)
    at require (internal/module.js:11:18)
    at new StaticmanAPI (/Users/martm106/Dev/staticman/server.js:13:14)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/martm106/.npm/_logs/2017-07-26T13_49_18_210Z-debug.log

Any hint how to resolve?
Node v8.2.1
MacOS Sierra v10.12.5

@micmart this one threw me for a while. For development, put your environment variables into .env, and try adding
const env = require('dotenv').config()

to the top of index.js, and adding "dotenv":"^4.0.0" to package.json`
You probably won't want that in production though. Better to just export the environment variables directly there.

I have the same problem. RSA private key is in config.development.js but starting in development mode gives:
> node index.js

/home/jo/dev/staticman/node_modules/node-rsa/src/NodeRSA.js:178
            throw Error("Empty key given");
            ^

Error: Empty key given
    at NodeRSA.module.exports.NodeRSA.importKey (/home/jo/dev/staticman/node_modules/node-rsa/src/NodeRSA.js:178:19)

I have the same problem. RSA private key is in config.development.js but starting in development mode gives:
> node index.js

/home/jo/dev/staticman/node_modules/node-rsa/src/NodeRSA.js:178
            throw Error("Empty key given");
            ^

Error: Empty key given
    at NodeRSA.module.exports.NodeRSA.importKey (/home/jo/dev/staticman/node_modules/node-rsa/src/NodeRSA.js:178:19)

Wondering how you fixed?  I get the same error and don't see an issue with the json syntax.

I'm unable to start staticman after following steps noted above.  Here's my debug log.
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
7 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/share/npm/bin/node-gyp-bin:/opt/staticman/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
8 verbose lifecycle<EMAIL_ADDRESS>CWD: /opt/staticman
9 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'if [ ! -d node_modules ]; then npm install; fi' ]
10 silly lifecycle<EMAIL_ADDRESS>Returned: code: 0  signal: null
11 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>12 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
13 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/share/npm/bin/node-gyp-bin:/opt/staticman/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
14 verbose lifecycle<EMAIL_ADDRESS>CWD: /opt/staticman
15 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node index.js' ]
16 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
17 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
18 verbose stack Error<EMAIL_ADDRESS>start: node index.js
18 verbose stack Exit status 1
18 verbose stack     at EventEmitter. (/usr/share/npm/lib/utils/lifecycle.js:232:16)
18 verbose stack     at emitTwo (events.js:126:13)
18 verbose stack     at EventEmitter.emit (events.js:214:7)
18 verbose stack     at ChildProcess. (/usr/share/npm/lib/utils/spawn.js:24:14)
18 verbose stack     at emitTwo (events.js:126:13)
18 verbose stack     at ChildProcess.emit (events.js:214:7)
18 verbose stack     at maybeClose (internal/child_process.js:925:16)
18 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
19 verbose pkgid<EMAIL_ADDRESS>20 verbose cwd /opt/staticman
21 error Linux 4.15.0-36-generic
22 error argv "/usr/bin/node" "/usr/bin/npm" "start"
23 error node v8.10.0
24 error npm  v3.5.2
25 error code ELIFECYCLE
26 error<EMAIL_ADDRESS>start: node index.js
26 error Exit status 1
27 error Failed at the<EMAIL_ADDRESS>start script 'node index.js'.
27 error Make sure you have the latest version of node.js and npm installed.
27 error If you do, this is most likely a problem with the staticman package,
27 error not with npm itself.
27 error Tell the author that this fails on your system:
27 error     node index.js
27 error You can get information on how to open an issue for this project with:
"npm-debug.log" 49L, 2967C                                                                                1,1           Top

@micmart this one threw me for a while. For development, put your environment variables into .env, and try adding
const env = require('dotenv').config()

to the top of index.js, and adding "dotenv":"^4.0.0" to package.json`
You probably won't want that in production though. Better to just export the environment variables directly there.

How did you push staticman to a dokku server?  I'm getting the error "Empty key given" when I try to push using dokku.  Any thoughts on what I need to do to fix?  Thanks!

Is there any updates on this, I'm stuck at the same spot.

If recall right, its an issue with rsaPrivateKey in the config file.  I
used a command line tool to check my syntax.
On Mon, Feb 11, 2019, 1:52 PM Justin Rummel<EMAIL_ADDRESS>wrote:

Is there any updates on this, I'm stuck at the same spot.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/eduardoboucas/staticman/issues/128#issuecomment-462509302,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AivBM-fQAFt7iodM3OH5YqK9T_CKhXUnks5vMeYEgaJpZM4Oj92g
.

Thanks for the quick reply @shoreviewanalytics, however, it just leaves more questions.  What was wrong w/ the config file?  What command line tool did you use to check the syntax?  I have something like the below (fake data):
{
  "githubToken": "5091869e2c124aa7ad7a592bf8114a8b",
  "rsaPrivateKey": "-----BEGIN RSA PRIVATE KEY-----
b3BlbnNzaC1rZXktdjEAAAAABG5vbmUAAAAEbm9uZQAAAAAAAAABAAABFwAAAAdzc2gtcn
NhAAAAAwEAAQAAAQEArJ+ZlUKOPHILf3hfzTo/fqlnu9koIQBK05Z3Q2NqwlKRBqYT3sH9
IZXpMxkzHt5W0Nkvk/cNwqK7dEXAweXfPN11XvzZKaXEYrBbUIUBiw5v8NfEGJRnxY0UQy
9iLehUAungExEWQphlVArDzPXQiYXetX9yMZ6ITnDs3VhcMZE901l9wfKFj6l2yv67qGjp
yeHWNcV88MDkdKZqGU3wSNnPhOA9obo8vOJqio+CReNHQPCMyBkw+0s1FeSyzUKYWqognI
SPluQYqMpnXkrqd7ipukMxSe0ag5kEgGxYwk+E8ZLMgUpE+5CcKVFwbMM0TPkSGbfuvUdI
STg2jk2ZIwAAA8BQIjjNUCI4zQAAAAdzc2gtcnNhAAABAQCsn5mVQo48cgt/eF/NOj9+qW
e72SghAErTlndDY2rCUpEGphPewf0hlekzGTMe3lbQ2S+T9w3Cort0RcDB5d883XVe/Nkp
pcRisFtQhQGLDm/w18QYlGfFjRRDL2It6FQC6eATERZCmGVUCsPM9dCJhd61f3IxnohOcO
zdWFwxkT3TWX3B8oWPqXbK/ruoaOnJ4dY1xXzwwOR0pmoZTfBI2c+E4D2hujy84mqKj4JF
40dA8IzIGTD7SzUV5LLNQphaqiCchI+W5BioymdeSup3uKm6QzFJ7RqDmQSAbFjCT4Txks
yBSkT7kJwpUXBswzRM+RIZt+69R0hJODaOTZkjAAAAAwEAAQAAAQBNqQ/DYsnyz6v0kQco
oUfnh/cvP6caEbOYNV06aAOjoNm2EAlocgWbkoHzhybEgGq2Ur9g5gi+w89po+fwU6Z3D3
q6XS6l2fncHFM4il4DXV9nDusd08ZLzgiLoUmeNaN2HBm++jT1iPItORqVnxFOjXeAV/Hb
+OKBx7QIcLQpZ90qbVbmPxNvoalHECEibQEzZ/Tv/wt2uSrGHddRtySgqtsY2F8MxJe6a7
SMvGsJLwgrgvTFIPNXDHf6d/8Kpm7IiREdZ/i36RtXTuq6KJQeWmB6XZFYDD6MCTXy3QXh
dpDIIUuH/GkuHboZ4PTbw5XM1woY1nzdf9ljQtMtW6gBAAAAgFUBoX+vywpXVxCuni/9zS
hUXrejjxV+duYd1iQ96zm3nKdLv5WBL2JIsy9mkDd00c8Ab5C/Wuw7D60zDAQK/LoJLUJ2
A+luuuTGNU29vwNxLADzRvG5HoqrRvLh7NeOD3hjQH+/2YpD38EfiJzJ5V5ro3mqPcHd46
a6V9nWsIcZAAAAgQDU5VIjNAwD9pZE4CeN4tDRH5EE0/DNzPyivq5YMCw501Cr1BMK5lXe
GPVpdP37wYpVEsd08VQmiLge1maC8NkH7YKjZsVhiGwWaufylqfWpiNRf7crip6L+0wKqp
Ol8KzdtpQggEh59NdW5hoLyxvJJu2emuK1IdZN9aBtHtMsIwAAAIEAz5LoiTxnsJmNOxR4
boW9kvLSxvaeBc/r1jDXRY8fgR1KGvDrRp9v3HptcoLJwaZC6j1Ybbor39U/AyfFpk3vKS
VvyLpN8Hrh1vazp/+POfZXbhFfkdZABE1Cto+zC0GjVA/Od/daNRJnGIhoeoFrh3w0Tb6G
IOEJEr/8T6IgLwEAAAAJZGVsZXRlLW1lAQI=
-----END RSA PRIVATE KEY-----",
  "port": 443
}

OK, couple of notes for future people.  YES, the rsaPrivateKey is just one line (not over serval lines like you would expect). Also, for whatever reason I could not bind against port 443, but 8443 allowed me to start.
sadmin@staticman:~/staticman$ npm start

><EMAIL_ADDRESS>prestart /home/sadmin/staticman
> if [ ! -d node_modules ]; then npm install; fi

><EMAIL_ADDRESS>start /home/sadmin/staticman
> node index.js

Staticman API running on port 8443

Cool, I have a post on my blog on how to setup your own instance.  Please
have a look, leave a comment.  It took me days to figure it out!  😁
https://shoreviewanalytics.github.io/Staticman-API-Dokku-Deployment/
On Tue, Feb 12, 2019, 12:01 PM Justin Rummel<EMAIL_ADDRESS>wrote:

OK, couple of notes for future people. YES, the rsaPrivateKey is just one
line (not over serval lines like you would expect). Also, for whatever
reason I could not bind against port 443, but 8443 allowed me to start.
sadmin@staticman:~/staticman$ npm start

<EMAIL_ADDRESS>prestart /home/sadmin/staticman
if [ ! -d node_modules ]; then npm install; fi

<EMAIL_ADDRESS>start /home/sadmin/staticman
node index.js

Staticman API running on port 8443
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eduardoboucas/staticman/issues/128#issuecomment-462912288,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AivBM7EZOohugHRiXG22q5M467rB5pbkks5vMx21gaJpZM4Oj92g
.

Thanks @shoreviewanalytics !  I'll go through your documentation over the weekend

hello @shoreviewanalytics unfortunately still not getting anything to work.  Used Digital Ocean and created my own Dokku on Ubuntu 18 LTD and I'm always getting stuck somewhere on /app/node_modules/node-rsa/src/NodeRSA.js.  I feel like your directions are more notes for yourself vs. directions, especially for someone who has ZERO experience with Dokku.

Hi Justin,
Unfortunately, I don't really remember more than the notes I took on how I
did it.  My explanation is far from a step by step, so I agree with you
that it is really just my notes on the process.  You can try the following
for config.production.json.  Please be sure that the .json is valid by
using a validator and make sure that you don't wrap the rsaPrivatKey
either.  Where I say "insert public key here all on one line, no wrapping"
is where you put your key.
{
"githubToken": "",
"rsaPrivateKey": "-----BEGIN RSA PUBLIC KEY-----insert public key here
all on one line, no wrapping==-----END RSA PUBLIC KEY-----",
"port": 80
}
On Sat, Mar 2, 2019 at 12:53 PM Justin Rummel<EMAIL_ADDRESS>wrote:

hello @shoreviewanalytics https://github.com/shoreviewanalytics
unfortunately still not getting anything to work. Used Digital Ocean and
created my own Dokku on Ubuntu 18 LTD and I'm always getting stuck
somewhere on /app/node_modules/node-rsa/src/NodeRSA.js. I feel like your
directions are more notes for yourself vs. directions, especially for
someone who has ZERO experience with Dokku.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eduardoboucas/staticman/issues/128#issuecomment-468943518,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AivBMxLTA1sR54dy0VxUH9n69USOVIqqks5vSrqTgaJpZM4Oj92g
.

Unfortunately, that does not fix the problem for me.


[rlgl] rlPushMatrix() is incorrect

Look at this line here:
https://github.com/raysan5/raylib/blob/master/src/rlgl.c#L413
glPushMatrix() is supposed to push on a new matrix onto the stack, with cloning the previous one.  Though rlPushMatrix(), it's also loading the identity matrix (because of a call to rlLoadIdentity()).  This is incorrect if you want to emulate the original OpenGL fixed function API.

Actually rlgl module pretends to be a kind-of-emulation layer but not a direct implementation (like Mesa project).
Do you know any specific case where reseting the current matrix after pushing it to stack could suppose an issue?

Resetting the current matrix to the identity matrix kind of destroys the purpose of the stack.  It's purpose was that you could chain on other transforms (scale, rotate, translate, etc...) upon an existing base transform.  And then (with ease) call the pop function to undo those transforms in a single command, instead of having to reverse them.
Take for example a the skeleton rig for a stick figure.  You could push on the first (base) matrix transforms for the torso, then push/pop on the matrix transforms for the legs, arms, & head; though have these transforms be relative to the body.  So if someone moved the body, it would the move the arms, legs, and head along with it.
With how rlPushMatrix() right now functions, you can't do that.  It kind of makes push/pop functionality useless.  Take a look at the official docs for glPushMatrix():
https://www.khronos.org/registry/OpenGL-Refpages/gl2.1/xhtml/glPushMatrix.xml

Thanks for the detailed explanation. You are right, I'll review it!

Corrected in commit https://github.com/raysan5/raylib/commit/ff9b486ebe61d84d14add801d67c3bbdaca111e2

Just reverted this change because it breaks 3D shapes drawing examples, transformations are accumulated into currentMatrix and drawn doesn't work as expected.
Need to think about this change more carefully...

short notice, without this change and the models using rlPushMatrix it's not possible to draw a rotated cube, isn't it? I've tried the following setup:
rlPushMatrix();
rlRotate(45,0,0,1);
DrawCube(...);
rlPopMatrix();
but because DrawCube internally also does a rlPushMatrix my rotation isn't used to draw the cube.
In my test without the LoadIdentity in rlPushMatrix the camera is in the beginning off, but I'm not sure why.

Hey, I'm bumping this because this is kind of a semi-critical issue.  It at least deserves a special tag.

Hi @define-private-public! Thanks for the reminder, I couldn't find the moment to work on that...
Previously proposed change breaks shapes/textures drawing while using internal buffers...

I think it does not break the shapes/textures, it just has the wrong initialization for the camera for your examples. I'm quite sure when you move the camera around (in the opposite direction) you will see the expected content.

This is going to be one of the more nasty/frustrating things to fixup.  Do you have a list of all the things that are going to need to be adjusted?

This is going to be one of the more nasty/frustrating things to fixup.

Yes, I can't find the right time to jump into this...

Do you have a list of all the things that are going to need to be adjusted?

Mainly focused on rlgl module (OpenGL abstraction layer), I'd start reviewing rlPushMatrix() and rlPopMatrix() implementations. Behaviour is not exactly the same as their OpenGL 1.1 counterparts.

Hey, has there been any movement on this issue lately?  It's kind of a very important one for proper OpenGL compatibility.

Well, actually, issue is in stand-by, I didn't close it because if I have enough time in a future I could try to look for an easy solution to align implementation with OpenGL 1.1 but as stated in my last post I have my doubts if it really worths it.

Issue corrected in commit https://github.com/raysan5/raylib/commit/97e40ced57489f4d66d4b9bc9fe213c388e1a827.


Allow admins to create and manage recommended tags

Includes an API to view the active ones
https://zube.io/smartlogic/bchd/c/227
https://zube.io/smartlogic/bchd/c/228
https://zube.io/smartlogic/bchd/c/229
Migrations to Run: Yes / No
Yes

Spec failure looks like your psql instance made the sql file something CI can't handle. Looks like CI is 10 and prod is 11, you are probably on 12 or 13

Got postgres 10 running locally in docker and re-did the migrations. Here we go CI :crossed_fingers:


Matching Neural Net input-outputs to SCAM input-outputs

We will need to suitably re-interface the Neural Net model, but something we will need to solve is that the co-ordinate schemes between (previously used) SAM and SCAM differ. Therefore some translation with interpolation will be needed.  This will likely need a lot of steer from Judith and Paul.

Identify input-output interface for the model within SCAM
Identify the translation and interpolation needed in the co-ordinate schemes
Design translation scheme
Write tests to ensure that the translation in-and-out is an isomorphism (no junk no noise).
Identify CESM/SCAM metrics we can use to test end-to-end after parameterization inserted (continuous integration test)

From @paogorman's M2LInES talk the following 'impedance matching' activities are needed (with some rephrasing from me):

Match certical coordinate: Interpolate from pressure in CAM to/from reference pressure
profile in anelastic SAM

Variable conversions: convert tendency of liquid/ice static energy to temperature

Energy conservation: conserve enthalpy in CAM versus static energy in anelastic SAM
(use anelastic-primitive equation analogy). @paogorman does this come for free from some variable conversion, or are we going to need to do something extra?

Timesteps: subcycling due to mismatch in timesteps

I think it might be best for us to break these into 4 separate issues actually.

The first three may well need to be combined as I suspect they will be interlinked.
The subcycling I agree should be tackled elsewhere, as it is likely non-trivial.

I expect energy conservation will come for free with correct choice of variables

Made a separate issue for subcycling then https://github.com/m2lines/convection-parameterization-in-CAM/issues/37


Question: How to use Factory Proxy Providers?

Thanks for this awesome library!
While trying to get rid of request-scope, that we are currently using to have RLS-scoped database connections, those Factory Proxy Providers looked very nice. Unfortunately, I cannot get them to work.
In the docs there is this example, but I just cannot get it to work 😓

ClsModule.forFeature({
    provide: TENANT_CONNECTION,
    import: [DatabaseConnectionModule],
    inject: [CLS_REQ, DatabaseConnectionService],
    useFactory: async (req: Request, dbService: DatabaseConnectionService) => {
        const tenantId = req.params['tenantId'];
        const connection = await dbService.getTenantConnection(tenantId);
        return connection;
    },
});

forFeature does not seem to accept the config, probably forFeatureAsync is meant?
with forFeatureAsync I run into dependency errors

The old request scope approach
This works, but we want to get rid of:
@Global()
@Module({})
export class RLSModule {
  static forRoot(
    importModules: (
      | DynamicModule
      | Type<any>
      | Promise<DynamicModule>
      | ForwardReference<any>
    )[],
    // eslint-disable-next-line @typescript-eslint/ban-types
    injectServices: (string | symbol | Function | Type<any> | Abstract<any>)[],
  ): DynamicModule {
    const rlsProvider: Provider = {
      provide: TENANT_CONNECTION,
      inject: [REQUEST, DataSource, ...injectServices],
      scope: Scope.REQUEST,
      durable: true,
      useFactory: async (request: Request, connection: DataSource, ...args) => {
        const authInfo = request.auth.payload as Auth0JWTPayload;
        return createScopedDataSource(
          connection,
          authInfo.sub,
          authInfo.tenantId,
        );
      },
    };

    return {
      module: RLSModule,
      imports: importModules,
      providers: [rlsProvider],
      exports: [TENANT_CONNECTION],
    };
  }
}

Then, this global RLSModule is simply imported in app.module.ts.
embed ClsModule in RlsModule
This didnt work with errors like connection is undefined
@Global()
@Module({})
export class RLSModule {
  static forRoot(
    importModules: (
      | DynamicModule
      | Type<any>
      | Promise<DynamicModule>
      | ForwardReference<any>
    )[],
    // eslint-disable-next-line @typescript-eslint/ban-types
    injectServices: (string | symbol | Function | Type<any> | Abstract<any>)[],
  ) {
// where should we put ClsModule.forFeatureAsync?
    const dynamicModule = ClsModule.forFeatureAsync({
      provide: TENANT_CONNECTION,
      imports: [TypeOrmModule],
      inject: [CLS_REQ, DataSource],
      useFactory: async (request: Request, connection: DataSource) => {
        const authInfo = request.auth.payload as Auth0JWTPayload;
        return createScopedDataSource(
          connection,
          authInfo.sub,
          authInfo.tenantId,
        );
      },
    });
    return {
      module: RLSModule,
      imports: importModules,
      providers: [...dynamicModule.providers, RLSEnforcerService],
      exports: [TENANT_CONNECTION],
    };
  }
}

standalone ClsModule
here I run into dependency errors, where it cannot resolve the tenant connection:
@Module({
  imports: [
    ClsModule.forRoot({
      global: true,
      middleware: { mount: true },
    }),
    ClsModule.forFeatureAsync({
      provide: TENANT_CONNECTION,
      imports: [TypeOrmModule],
      inject: [CLS_REQ, DataSource],
      useFactory: async (request: Request, connection: DataSource) => {
        const authInfo = request.auth.payload as Auth0JWTPayload;
        return createScopedDataSource(
          connection,
          authInfo.sub,
          authInfo.tenantId,
        );
      },
    }),
    ConfigModule.forRoot({ isGlobal: true }),
//...
});

Nest can't resolve dependencies of the Auth0Guard (ConfigService, ?, ContextService, TenantsService, PinoLogger). Please make sure that the argument TENANT_CONNECTION at index [1] is available in the AuthModule context.

Hi, thank you for providing such elaborate issue description!
First and foremost - yes, you're correct, there's a mistake in the docs and it should be forFeatureAsync.
Second - the forFeatureAsync registers the provider (in your case TENANT_CONNECTION) only in the module where you define it. You can the use module re-exporting to make the providers also available in the parent module. With that in mind, I think your RLSModule as a wrapper is almost correct.
Without a guarantee whether it would work, I'd suggest this form:
@Global()
@Module({})
export class RLSModule {
  static forRoot(
    importModules: (
      | DynamicModule
      | Type<any>
      | Promise<DynamicModule>
      | ForwardReference<any>
    )[],
    // eslint-disable-next-line @typescript-eslint/ban-types
    injectServices: (string | symbol | Function | Type<any> | Abstract<any>)[],
  ) {
    return {
      module: RLSModule,
      // use define the ClsModule in imports
      imports: [
        ...importModules,
        ClsModule.forFeatureAsync({
          provide: TENANT_CONNECTION,
          imports: [TypeOrmModule],
          inject: [CLS_REQ, DataSource],
          useFactory: async (request: Request, connection: DataSource) => {
            const authInfo = request.auth.payload as Auth0JWTPayload;
            return createScopedDataSource(
              connection,
              authInfo.sub,
              authInfo.tenantId,
            );
          },
        });
      ]
      // do not put other module's providers to providers (that might be the reason the connection was undefined)
      providers: [RLSEnforcerService],
      // re-export the dynamic ClsModule definition - this makes `TENANT_CONNECTION`
      exports: [ClsModule]
    };
  }
}

The other variant, where you register the ClsModule.forFeatureAsync directly in root doesn't work, because the provider is available only in AppModule (that's why you must use a wrapper module in the current situation).
It might be a good idea to add the global flag to the forFeatureAsync option as well to make the provider accessible globally.
Please let me know if this helped, or create a minimal reproducible example that I can debug on my machine.

Wow, thanks for the quick reply and the new release 🙇🏼
Re-exporting the module did work as you suggested, but now I am running in a more DX problem. Maybe you have a suggestion as well:
When using your approach as a drop-in solution the code will not work due to error at boot time:
TypeError: connection.getRepository is not a function

@Injectable()
export class ResourcesService {
  constructor(
    @Inject(TENANT_CONNECTION)
    private connection: RLSConnection,
    private resourceStorageService: ResourceStorageService,
    private eventEmitter: EventEmitter2,
  ) {
    // here we will get
    this.resourceRepository = connection.getRepository(Resource);
  }
  resourceRepository: Repository<Resource>;

which makes sense, as the connection is only populated during a request right?
We used the connection.getRepository() approach in order to have a repository as member variable for the entire service, so that all other methods can simply run this.resouceRepository.findAll() for example.
Shall we refactor to use it like this? e.g.
  async findAll() {
// Replace
//  const resources = await this.resourceRepository.find({
    const resources = await this.connection.getRepository(Resource).find({
      relations: {
        assets: true,
        requests: true,
        createdBy: true,
        lastEditedBy: true,
      },
    });

or is there a smoother approach to have the repository available in a more nest-idomatic way?
Thanks a lot for your support! 🤜🏼 🤛🏼

Ah nice, this is the DX I was hoping for and it makes this a really viable solution - case closed!👌🏼
Thx for the support and this library 🙌🏼


persyst annotations error

Describe the bug
The persyst raw file function is able to open the persyst files and annotations with no issues. The issue I am having. For my particular use case we need to get all annotations regardless if they are repeated. When some of the EEG systems generate annoations they use xlevents or xlspikes and sometimes they can be multiple of these in the files. however the parser is only taking unique annotations. So if a human annotator or machine annotator uses same annotations then the parser is not picking up all of the annotations but rather unique names or the first one with that name.
Steps to reproduce
Open any lay/dat files that have annotations with different times and same name/description
Expected results
The expected behavior is that the parser should be able to pick up all annotations even if they have the same name.
Actual results
only picks up the first annotation with that name.
Additional information
If I have time I can try to submit a suggestion on how to fix it.
I think the issue is that you are using the comment texts as keys for your dictionary of annotations. So when your script finds a new comment with the same text is overwriting the previous one. Perhaps one suggestions to append the values to your keys as a list if the keys are already in the dictionary.

ping @adam2392

Yes that totally sounds like a bug to me :P.

Additional information
If I have time I can try to submit a suggestion on how to fix it.
I think the issue is that you are using the comment texts as keys for your dictionary of annotations. So when your script finds a new comment with the same text is overwriting the previous one. Perhaps one suggestions to append the values to your keys as a list if the keys are already in the dictionary.

Ah I see this sounds like a good fix to me! Would you be willing to submit a PR and I can help review and get it merged? It seems like a few line fix to adapt the dictionary to dictionary of lists.

I was able to get that fixed , but it is breaking the part of the code that
adds annotation to the annotation object because It is expecting single
value Instead of a list. I need to give this some thought.
Andres Rodriguez
On Wed, Sep 23, 2020, 2:04 PM Adam Li<EMAIL_ADDRESS>wrote:

Yes that totally sounds like a bug to me :P.
Additional information
If I have time I can try to submit a suggestion on how to fix it.
I think the issue is that you are using the comment texts as keys for your
dictionary of annotations. So when your script finds a new comment with the
same text is overwriting the previous one. Perhaps one suggestions to
append the values to your keys as a list if the keys are already in the
dictionary.
Ah I see this sounds like a good fix to me! Would you be willing to submit
a PR and I can help review and get it merged? It seems like a few line fix
to adapt the dictionary to dictionary of lists.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/issues/8292#issuecomment-697805179,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA22CDGUPAWTGSKGQ5JYHO3SHI2BHANCNFSM4RWRTAQA
.

Yes that totally sounds like a bug to me :P.

Additional information
If I have time I can try to submit a suggestion on how to fix it.
I think the issue is that you are using the comment texts as keys for your dictionary of annotations. So when your script finds a new comment with the same text is overwriting the previous one. Perhaps one suggestions to append the values to your keys as a list if the keys are already in the dictionary.

Ah I see this sounds like a good fix to me! Would you be willing to submit a PR and I can help review and get it merged? It seems like a few line fix to adapt the dictionary to dictionary of lists.

I think i got issue resolved . Now there will be objects with same description. I needed to change some of the way you unpacked you annotations to account for the lists of annotation. This way now wach annotation has an object. An alternative way to do it is to pass the whole list to a repeated annotation element but was not sure if that will be more desirable. One thing I dont know if need fixing is that the now when you transform annotations to events it has trouble to recognize the repeated annotation instances. Let see how I can show you the code and you can test.

@infinitejest  awesome! can you make the PR into actual mne-python? I think the current one you have is to your local copy.

Check if it went through. I am not very good with git.


ENI: security-group-tags not working

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Specifying spec.eni.security-group-tags in custom cni-config has no effect.
Debugging information:

Similar fields like spec.eni.security-groups and spec.eni.subnet-tags work.
SNI Debug reveals that security-group-tags get properly parsed (see logs below).
ciliumnode resource after startup does contain all fields except for security-group-tags:

apiVersion: cilium.io/v2
kind: CiliumNode
spec:
  alibaba-cloud: {}
  azure: {}
  encryption: {}
  eni:
    availability-zone: eu-central-1a
    disable-prefix-delegation: false
    first-interface-index: 1
    instance-type: r5a.large
    subnet-tags:
      testing-subnet: "true"
    use-primary-address: false
    vpc-id: vpc-03bdc4a64bd4a96d8

Status field in ciliumnode reveals it uses security groups from first eni.

CNI Custom config:
apiVersion: v1
kind: ConfigMap
metadata:
  name: cilium-cni-config
data:
  cni-config: |-
    {
      "cniVersion":"0.3.1",
      "name":"cilium",
      "plugins": [
        {
          "cniVersion":"0.3.1",
          "type":"cilium-cni",
          "eni": {
            "vpc-id": "vpc-03bdc4a64bd4a96d8",
            "first-interface-index": 1,
            "security-group-tags": {
              "testing-sg": "true"
            },
            "subnet-tags": {
              "testing-subnet": "true"
            }
          },
          "enable-debug": true,
          "log-file": "/var/run/cilium/cilium-cni.log"
        }
      ]
    }

Setup considerations:

Node role has permissions ec2:DescribeSecurityGroups.
Agent reports all security groups in log: level=info msg="Synchronized ENI information" numInstances=10 numSecurityGroups=9 numSubnets=33 numVPCs=2 subsys=eni

Cilium Version
cilium-cli: v0.12.12 compiled with go1.19.4 on linux/amd64
cilium image (default): v1.12.5
cilium image (stable): v1.12.6
cilium image (running): v1.12.5

Kernel Version
AWS Bottlerocket, 5.10.157
Kubernetes Version
v1.23.14-eks-ffeb93d
Sysdump
Will provide upon request
Relevant log output
Cilium CNI Debug log:
level=debug msg="CNI NetConf: &types.NetConf{NetConf:types.NetConf{CNIVersion:\"0.3.1\", Name:\"cilium\", Type:\"cilium-cni\", Capabilities:map[string]bool(nil), IPAM:types.IPAM{Type:\"\"}, DNS:types.DNS{Nameservers:[]string(nil), Domain:\"\", Search:[]string(nil), Options:[]string(nil)}, RawPrevResult:map[string]interface {}(nil), PrevResult:types.Result(nil)}, MTU:0, Args:types.Args{}, ENI:types.ENISpec{InstanceID:\"\", InstanceType:\"\", MinAllocate:0, PreAllocate:0, MaxAboveWatermark:0, FirstInterfaceIndex:(*int)(0xc00030d980), SecurityGroups:[]string(nil), SecurityGroupTags:map[string]string{\"testing-sg\":\"true\"}, SubnetIDs:[]string(nil), SubnetTags:map[string]string{\"testing-subnet\":\"true\"}, VpcID:\"vpc-03bdc4a64bd4a96d8\", AvailabilityZone:\"\", ExcludeInterfaceTags:map[string]string(nil), DeleteOnTermination:(*bool)(nil), UsePrimaryAddress:(*bool)(nil), DisablePrefixDelegation:(*bool)(nil)}, Azure:types.AzureSpec{InterfaceName:\"\"}, IPAM:types.IPAM{IPAM:types.IPAM{Type:\"\"}, IPAMSpec:types.IPAMSpec{Pool:types.AllocationMap(nil), PodCIDRs:[]string(nil), MinAllocate:0, MaxAllocate:0, PreAllocate:0, MaxAboveWatermark:0, PodCIDRAllocationThreshold:0, PodCIDRReleaseThreshold:0}}, AlibabaCloud:types.Spec{InstanceType:\"\", AvailabilityZone:\"\", VPCID:\"\", CIDRBlock:\"\", VSwitches:[]string(nil), VSwitchTags:map[string]string(nil), SecurityGroups:[]string(nil), SecurityGroupTags:map[string]string(nil)}, EnableDebug:true, LogFormat:\"\", LogFile:\"/var/run/cilium/cilium-cni.log\"}" eventUUID=c7b55ec1-a809-401e-8091-8e5ab0e1b84c subsys=cilium-cni

Anything else?
No response
Code of Conduct

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

@blang -- mind sharing how you installed Cilium and what your cloud layout looks like. I might have some time next week to repro this and see where the problem is.

@ungureanuvladvictor Sure, thanks for the quick reply and hope you can reproduce it.
Setup is pretty basic, default helm setup of chart version 1.12.5 with values and custom cni config, see here: https://gist.github.com/blang/74f2287cc064c3c0801ae0141e494dd2
The outcome should be: Node and Pod ENIs separated into specific subnets and pods only use the second ENI upwards with prefix delegation and with own security group different from nodes.
This setup works with security-groups hardcoded in cni-config but i need to select the pod security groups by tags instead of hardcoding them.
Happy to provide more feedback, but i think that is all the setup there is.
For debugging: Honestly i don't quite get who creates and patches the ciliumnode resources. The agent is the only one mounting the cni-config which contains the security-group-tags field, but the operator is the only one with the cache of security groups to filter by tag.
Since the end result is that the ciliumnode resource does not contain the security-group-tags field at all, but if i use hardcoded security-groups in the cni-config it gets written into ciliumnode, i can only suspect that this field is not written in the first place (by which entity, probably agent) or there is some exchange between operator and agent missing.
I tried to dig through the code, but i'm don't understand the system enough to follow the trail

This issue is still open and still affects v1.13.1.
@ungureanuvladvictor Can you give me any hint why that happens, maybe i find time to open a PR


mv and rename not working as expected

I create a folder in a bucket  "/my-bucket/folder/" which contains some text files. I then run
fs.rename("/my-bucket/folder/", "/my-bucket/new_folder", recursive=True)
Instead of seeing "/my-bucket/new_folder", I see "/my-bucket/new_foldermy-bucket/folder"
That doesn't seem correct. mv does the same thing.
Testing with fsspec and the localfilesystem give the expected result of there being just a "/folder/new_folder" that you would expect

This has been fixed by the recent improvements to recursive path expansions in fsspec. I have added an explicit test for this in #575.


Saddle points

what are saddle points?

For a multivariate function, a saddle point occurs when the first partial derivatives are zero, indicating a critical point. However, the second partial derivatives at this point show a mix of positive and negative values, suggesting that the function neither strictly increases nor decreases along all directions. This property distinguishes a saddle point from local extrema.

https://en.m.wikipedia.org/wiki/Saddle_point


How to get log of an UDP handler

Hi,
I'm not able to trace any logs of an UDP handler. Here is my Sensu config.

InfluxDB UDP handler:

{
  "handlers": {
    "influxdb_udp": {
      "type": "udp",
      "mutator": "influxdb_line_protocol",
      "socket": {
        "host": "<IP_ADDRESS>",
        "port": 8189
      }
    }
  }
}

The mutator influxdb_line_protocol is from mutator-influxdb-line-protocol.rb
. The mutator does yield 0 when run so I guess Sensu log should show some info about this handler but it doesn't.
I'm able to query those inserted metrics in InfluxDB. However, in the sensu-server.log (INFO level) I cannot see any log message like other TCP handler("message":"handler output").
Is it because of nature of UDP (shoot and forget) or can we  improve this. Because if InfluxDB not working, I cannot trace anything from Sensu.

I'm using Sensu version 0.21.0-2.

@chrisduong you can toggle debug logging with a SIGTRAP. You will see your mutator output in the Sensu log file: https://github.com/sensu/sensu/blob/master/lib/sensu/server/handle.rb#L159

Hi,
Could I ask one more silly question.
How to toggle debug logging with a SIGTRAP in Sensu, could you tell a little more specifically. Thanks

kill -TRAP $sensu-server-pid where $sensu-server-pid is the Sensu server process ID.


[BUG] AddToCart and Clearance sale activated

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
If I have a product with that stock configuration:

I can still click the AddToCart Button in Frontend and get a success message.
However, the product is not added to the cart ... everything looks correct as a customer.
Expected Behavior
As a customer, I would expect a message that the product is not in stock and the AddToCart Button should be disabled.
I would also expect another error message when I am allowed (not deactivated) to click the AddToCart Button.
Suggestion: Compare the template with the default storefront and how the flow is there.
Steps To Reproduce
Test-Product:
http://localhost:3000/LAVENDA-Product-Variants/SW20004.1
Environment
No response
Anything else?
No response

it duplicates those issues:
https://github.com/shopware/frontends/issues/464
https://github.com/shopware/frontends/issues/782


Received IPN once, no longer receiving IPN in testing mode

Hello,
I am developing a website and implementing the django-paypal API. I was able to get a POST to my notify_url once however when I tried to reproduce the result I could not do so on two different machines.
I have followed your directions in your documentation page by making sure I am using ngrok to make my local machine visible as well as making the confirm_url csrf exempt as that was one hurdle I had to cross to initially get it to work.
Here is the current process I am using.

I run the the server locally using python run manage.py runserver in which I have the server running at http://<IP_ADDRESS>:8000/.
I then run ngrok using the command ngrock http <IP_ADDRESS>:8000 to target the port I am running on.
I change the notify_url to the https url I get from ngrok , ex. (https://1420ef2e.ngrok.io/Notify) with the added reverse('paypal-ipn') on the end.
I update the url in which IPNs can be sent on the paypal website.
I get to the point where I should see a post to the notify page but I don't see one.

I'm not sure what is causing the breakdown. I changed a couple of things around after getting the signal the first time as I felt they would not accept it however I believe the way I have implemented it is correct. I used the IPN simulator to make sure my notify page can recieve a post to the https://1420ef2e.ngrok.io/Notify for example, and I was successful.  I am quite perplexed on what might be occurring and feel that two others on stackoverflow might be having the same issue.
http://stackoverflow.com/questions/42869542/django-paypal-unable-to-handle-notification-signal
http://stackoverflow.com/questions/42356166/signals-on-django-paypal-not-firing
I'm not sure if this is a bug or a breakdown in my implementation. Any constructive insight on this would be great.
I have also attached files of views.py,  main urls.py, template urls.py, and the html page that has the button and the notify_url page.
Thanks
possible_bug.zip

Closed for reasons described in the README - https://github.com/spookylukey/django-paypal/#issue-tracker-and-support-requests

You have commented out the include line in urls.py
You have a file name urls_main.py.py
Your notify_url is not as described in the docs - why are you adding /Notify?

Check the docs again, follow them carefully. Also, there is no way to know what is going on without a reproducible test project - you have just included a small set of files from your project which doesn't show me how it all fits together. However, please do not send a complete project again - I do not have resources for more support requests, I do this for free.


Blog Post: 4th Wave of Bitcoin Grants

To be reviewed by @OpenSats/volunteers
Build preview:

/blog/bitcoin-grants-feb-2024

Social preview:

@Arvin21M yeah it seems like the SSL certificate of bitcoinacks.com expired. Not much we can do 🤷♂

Just looked over it again, I think it's good. Let's push it live. Thanks everyone! 🙏🧡


Define trait functions

Define:

[x] trait
[x] for
[ ] impl (standard library)
[x] Traits for builtins (Name, Text, Number, etc.)

Traits for builtins are added in 58b77c4

impl removed because you can just partially apply for, eg. foo : Foo for.


Add new methods required for Testerina to PackageInfo and ProgramFile

This PR will add a couple of new methods to PackageInfo and ProgramFile which are utilized in Testerina. This PR also changes the isNonBlockingAction() in AbstractHTTPAction class to false in order to get HTTP Client Connector to work properly.

This will be added by PR: #2563


Bigint and numeric separators support

@michaelficarra please check this.

@michaelficarra please check this

@michaelficarra Ping.

@michaelficarra ping

@michaelficarra ping

@michaelficarra ping

@michaelficarra please check this

@michaelficarra ping

@michaelficarra ping

@michaelficarra Ping

@michaelficarra last ping in hope that it will be merged and I wont create a fork with all my PRs

I created the fork with this feature:
https://www.npmjs.com/package/@javascript-obfuscator/escodegen


Allow to represent opt input parameters as Option

This is a small ergonomic change which allow to define any Redscript opt input parameter which itself already implement Default and FromRepr optionally as Option<T>.
It alleviate boilerplate if e.g. a CName is n"None" in Redscript and it can be as well considered as None in Rust.
private native func MyNativeFunc(opt param: CName) -> Void;

// updated code from red4ext-rs 0.6 up
impl Plugin for MyPlugin {
    // ...
    fn exports() -> impl Exportable {
        exports![
            GlobalExport(global!(c"MyNativeFunc", my_native_func)),
        ]
    }
}

pub fn my_native_func(param: Option<CName>) { /* ... */ }

There was compilation issues that I addresses in #47, which should probably be merged before this one.

I did reset everything to latest red4ext-rs before reapplying same change.

I'm skeptical of this change because optional arguments in the game aren't really optional and it can lead to confusing behavior: someone can define an Option<i32> parameter and passing 0 will translate to None,
Also every CName can already be CName::undefined, so by wrapping CNames in Option you have 2 layers that both can be undefined

The idea behind is that developer must explicitly opt-in to turn e.g. a i32 into a Option<i32>: no type T gets automatically turned into a Option<T>.
Putting it in unwanted places then is no different than messing up regular FFI function signatures.
It's more of a way to explicitly translate opt into its natural representation in Rust.

Let's take the example of AudioSystem.Play. Developer can still choose to write it like so if (s)he wants to.:
unsafe extern "C" fn play(event_name: CName, entity_id: EntityId, emitter_name: CName) -> ()

Now having read its definition in NativeDB, (s)he can also opts to turn it into:
unsafe extern "C" fn play(event_name: CName, entity_id: Option<EntityId>, emitter_name: Option<CName>) -> ()

Following our short discussion I refactored Option<T> into a more explicit OptArg<T> as requested.


JavaFX WebView

Hi, i'm trying to use JavaFX Webview component, but don't know how can i get request and response headers. In my desktop app i want to login via webview and after that get some headers, thats needed for making api requests, is it possible or i wasting my time?)
Maybe is there analogues for android webview component, that i can use in desktop compose application? Thanks!
code ex:
private fun initialiseJavaFXScene() {
    val webView = WebView()

    val cookieManager = CookieManager()
    CookieHandler.setDefault(cookieManager)
    //URL.setURLStreamHandlerFactory(CustomURLStreamHandlerFactory()) //not working

    with(webView.engine) {
        loadWorker.stateProperty().addListener { _, oldValue, newValue ->
            with(cookieManager.cookieStore.cookies) {
                       //...
                }
            }
        }
        load(BASE_URL)
    }

    val scene = Scene(webView)
    setScene(scene)
}

use JavaFX Webview component, but don't know how can i get request and response headers ... is it possible or i wasting my time?

This question is not related to Compose Multiplatform. You can ask it on StackOverflow.

is there analogues for android webview component, that i can use in desktop compose application

There is no official WebView for Compose for Desktop at the moment. You can follow this issue

I would recommend this library https://github.com/KevinnZou/compose-webview-multiplatform. It supports WebView on the desktop side using JCEF.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


run tests on failing builds of PR 226

bors try

@jamesmunns could you cancel the other travis job ? it already failed


Emulate bitcoin mining on shadow simulator

WIP
Before emulating the bitcoin mining, find an easy way to leverage bitcoind's solo mining process with minimal mining difficulty.

Bitcoind's solo mining is not possible since the Bitcoin Core removed CPU mining option in version 0.13.0. (https://bitcoin.org/en/release/v0.13.0)

Removal of internal miner
As CPU mining has been useless for a long time, the internal miner has been removed in this release, and replaced with a simpler implementation for the test framework.
The overall result of this is that setgenerate RPC call has been removed, as well as the -gen and -genproclimit command-line options.
For testing, the generate call can still be used to mine a block, and a new RPC call generatetoaddress has been added to mine to a specific address. This works with wallet disabled.

Currently, this issue is more like implementing the shadow-injector plugin for bitcoin (#1 ), so i merge this issue into #1 .

Duplicated of #1

Duplicate of #1

duplicate of #1
aa


Docs getting started diverged floc 1232

This is a provisional WIP PR for integration of the new getting started guide in to the Sphinx-generated docs.
Fixes FLOC-1167

Closed in favour of  #1083.


Fixed typo

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

Looks good; thanks @lunaticitizen


Error on startup

After updating the bot, I get this error on startup and the programme closes: https://imgur.com/a/8ukcSNj
It has actually been a while that it has broken, and it happened after an update a while ago. Meanwhile I updated it again it still doesnt work. Reddis is running according to the updater screen.
What can I do to revive my bot from the dead?

Tried backing up db and config files, removing bot completley, re-install it. And then put the backed-up files back and restart again?

Hmm, I think I have already attempted to reinstall the bot before, but why not give it a try again. It is my local computer where I am also on Discord on just fine.
I havent taken a look at the tokens, I kept them the way it is since installing. So that is also something to look into then. ;)

Yea it's simply something wrong with your connection, antivirus, firewall, or anything of the sort.


Components re-render when device rotates even if breakpoint does not change

Description
NativeBase components rerender unnecessarily
CodeSandbox/Snack link
https://snack.expo.dev/@n_harada/nativebasebreakpointsexample
Steps to reproduce
Open the snack on a device.

See a number having been incremented at regular intervals at the center of screen.
Rotate device.
You can see the count incrementation stops for several seconds.
(4. If you can put logger into your NativeBase code, you can see this occurs due to unnecessary re-rendering)

NativeBase Version
3.2.1
Platform

[ ] Android
[ ] CRA
[X] Expo
[ ] iOS
[ ] Next

Other Platform
No response
Additional Information
NativeBase components re-render when screen size changes and break points value does not matter with this re-rendering.
Even if breakpoint does not change, re-rendering occurs.
It is because usePropsResolutionWithComponentTheme fires when useWindowDimensions's state changes and return value of usePropsResolutionWithComponentTheme is different object every time.
Also, ReactNative's useWindowDimensions has a bug((https://github.com/facebook/react-native/issues/29290) of which useWindowDimensions returns wrong value and the value are swapped for a very short amount of time(https://github.com/facebook/react-native/issues/29290#issuecomment-696537458).
I faced that swapping when iPad app comes to foreground.
This useWindowDimensions'bug combined with NativeBase re-rendering, my app on iPad freezes several seconds  every time when it comes to foreground.
I came up with two solutions about this problem with useWindowDimensions'bug.The first one is making NB components render only when value of props changes(if break point value does not change, component does not re-render even if screen size changes).The second one is to wrap   useWindowDimensions for debounce to prevent re-rendering by size swapping for a very short amount of time by useWindowDimensions's bug.
Here is an example of my second solution.

import { useEffect, useRef, useState } from "react"
import { Dimensions, useWindowDimensions } from "react-native"

const debounceTime = 1000
export const useDebouncedWindowDimensions = () => {
	const timerRef = useRef<ReturnType<typeof setTimeout> | null>(null)
	const [debouncedScreen, setDebouncedScreen] = useState(
		Dimensions.get("screen")
	)
	const screen = useWindowDimensions()

	useEffect(() => {
		if (timerRef.current) {
			clearTimeout(timerRef.current)
		}
		timerRef.current = setTimeout(() => {
			setDebouncedScreen(screen)
		}, debounceTime)
	}, [screen])
	return debouncedScreen
}

I love NativeBase, this library is giving me great development experience but this problem is so serious that I'm thinking about stopping using NativeBase.
Hope this problem gets resolved as soon as possible.

Hi @n-harada, Thanks for reporting this issue. We will look into it.

I confirm, I have a similar problem of native-base components freezing on screen rotation, mainly on iOS.

I have been working on a project and we are experiencing the same problem, it happens when we load an embedded youtube video from a react native webview go into landscape mode, this triggers the unnecessary re-render thus ruining the end user experience, could someone at NativeBase please look at a fix for this!


Maybe you can also add the !? Right now we have to manually edit the file to add that in after transforming

thx. Maybe you can also add the !? Right now we have to manually edit the file to add that in after transforming
Originally posted by @unional in https://github.com/antongolub/tsc-esm-fix/issues/89#issuecomment-1214433826

:tada: This issue has been resolved in version 2.20.2 :tada:
The release is available on:

v2.20.2
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

@unional, 2.20.2, your turn.

(/file:\/{2,3}(.+)\/[^/]/.exec(import.meta.url) || [])[1] that gives me butterflies... :)
It it true that ([])[1] gives undefined, but it's not a good practice.
Yes, while this is more defensive than using !, but IMO that mask the actual problem (that in certain case the regex fails).
IMO, I would prefer using ! to make sure it fail fast (getting an accessing 1 from undefined error) instead of discovering the error later on.

! — agree, nice option for ts files, but ecma standard, IINM, did not introduce smth similar.

I suggest to introduce alternative subs syntax:
--dirnameVar = true / 'expression' — current legacy impl
--dirnameVar = 'const' — append constants to the begining of files

The ! is TypeScript only syntax. Tt is removed after transpilation. It is just an assertion to tell TS to be quiet.

I'm a little confused. tsc-esm-fix can be used for both sources and bundles. And the latter are no longer subject to change.

I see. Then adding ! is a no-go. Unless you can detect whether the source is TS or JS.

Ah, now it's clear! I'll land this improvement tomorrow.

Done. 2.20.3 is waiting for feedback

Working as expected! 🎉


Issue with rest api return content formatting

Issue reported by Saturn
possible we have something like this in the responces:
\r\n\t\t\t\t\t\t\t\t

need to investigate this
https://discordapp.com/channels/423097982498635778/514359683490775042/737032863572164668

not an issue. should be cleaned on demand by plugin.


chore(deps): update renovate/renovate docker tag to v36.96.0

This PR contains the following updates:

Package
Update
Change

renovate/renovate
minor
36.93.7 -> 36.96.0

Release Notes

renovatebot/renovate (renovate/renovate)
v36.96.0
Compare Source
Features

presets: add promster monorepo (#24142) (7779ebd)

Bug Fixes

bundler: remove —strict flag if —conservative is used (#24457) (3d588b8)

v36.94.5
Compare Source
Build System

deps: update dependency @renovatebot/ruby-semver to v3.0.14 (#24454) (6cd27d8)

v36.94.4
Compare Source
Bug Fixes

deps: update ghcr.io/containerbase/sidecar docker tag to v9.20.2 (#24446) (f78b103)

v36.94.3
Compare Source
Build System

deps: update dependency node-html-parser to v6.1.8 (#24435) (c368463)

v36.94.1
Compare Source
Build System

deps: update dependency node-html-parser to v6.1.7 (#24434) (f27ba96)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 5.2.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Progess bars not updating properly in Python Interactive Window on macOS

Steps to cause the bug to occur

Create a model that fits using a progress bar to monitor progress, such as Tensorflow.
Run model in interactive window with progress bar enabled.

Actual behavior
The progress bar does not update properly, printing a new line with every update, rather than using the existing line. Here is a screen shot:

Expected behavior
A progress bar that updates in the same line.
Your Jupyter and/or Python environment

Jupyter server running: Local
Extension version: 2020.8.108011
VS Code version: 1.49.0
Setting python.jediEnabled: false
Setting python.languageServer: Pylance
Python and/or Anaconda version: Python 3.8.5, Anaconda 3
OS: macOS Catalina
Virtual environment: conda

Python Output
See screen shot above.
Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer, @joyceerhl

@fonnesbeck Thanks for reporting and sorry about the issue here. We did have a problem like this in the past, but as far as I know this was resolved.  Or with everything with an updating progress bar? For example do you have the same issue with the super basic sample here?
#%%
import tensorflow as tf
mnist = tf.keras.datasets.mnist

#%%
(x_train, y_train),(x_test, y_test) = mnist.load_data()
x_train, x_test = x_train / 255.0, x_test / 255.0

model = tf.keras.models.Sequential([
  tf.keras.layers.Flatten(input_shape=(28, 28)),
  tf.keras.layers.Dense(128, activation='relu'),
  tf.keras.layers.Dropout(0.2),
  tf.keras.layers.Dense(10, activation='softmax')
])

model.compile(optimizer='adam',
              loss='sparse_categorical_crossentropy',
              metrics=['accuracy'])

#%%
model.fit(x_train, y_train, epochs=5)

#%%
model.evaluate(x_test, y_test)

Yeah, it happens with this test case as well. Again, only on Mac. Works fine on Linux/Windows. I thought it might be readline, but I installed it from conda and it still happens.

I'll try poking around a bit more with the repro, but I'm still not seeing the same issue locally and I'm on Mac as well. I did look online and I found this which looks similar:
https://stackoverflow.com/questions/41442276/keras-verbose-training-progress-bar-writing-a-new-line-on-each-batch-issue
The terminal width issue shouldn't apply here. Buy you could give the TQDM or import ipykernel possible fixes a try.


Added new entry for 'Rachit Garg'

@rstar900  contribute here https://github.com/Ishaan28malik/Get-Dev-Resources


[SPARK-29674][CORE] Update dropwizard metrics to 4.1.x for JDK 9+

What changes were proposed in this pull request?
Update the version of dropwizard metrics that Spark uses for metrics to 4.1.x, from 3.2.x.
Why are the changes needed?
This helps JDK 9+ support, per for example https://github.com/dropwizard/metrics/pull/1236
Does this PR introduce any user-facing change?
No, although downstream users with custom metrics may be affected.
How was this patch tested?
Existing tests.

Test build #112974 has started for PR 26332 at commit aefde48.

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-K8s/17897/
Test PASSed.

Wow. Nice!

BTW, what happens to ganglia? Do we still have Ganglia support after this PR?

Test build #112974 has finished for PR 26332 at commit aefde48.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

I don't know of a reason it would change Ganglia support. metrics-ganglia is still included, updated, and built here.

Oh, wait no I see the issue. Ganglia support is in a different module that I didn't enable. Indeed it isn't present in 4.x: https://search.maven.org/search?q=g:io.dropwizard.metrics AND a:metrics-ganglia&core=gav
Hm, OK, that's a problem, as we have historically maintained some Ganglia support.
But there are actually no tests for this integration, so we wouldn't have noticed any issues with it anyway.
Maybe I need to take this to dev@ ... if the support doesn't necessarily work on JDK 11 (unproven) then do we need to consider removing it?

Since we dropped kafka-0.8 at 2.4.x (Scala-2.12), can can disable Ganglia support in JDK11 first? It's because the main distribution of Apache Spark 3.0.0 is still JDK8.

Oh.. It's difficult to keep separately for JDK8/11.

Adding a link to a similar discussion in #26212
Probably getting rid of the Ganglia reporter is a good solution. Just a thought is that if some people still need it in Spark 3.x, maybe the Ganglia reporter can be supported by Apache Spark? It does not seem like a lot of code. There is the annoying issue of LGPL licensing of course though, that's why Dropwizard metrics library dropped it, I understand.

Yep, I am next going to try that, just inlining the simple single file metrics-ganglia contained. Dropwizard itself is ALv2. Ganglia is not, but, Spark doesn't publish this module directly, so that doesn't change.
Honestly most of the work is updating the license files!

Yep, I am next going to try that, just inlining the simple single file metrics-ganglia contained. Dropwizard itself is ALv2. Ganglia is not, but, Spark doesn't publish this module directly, so that doesn't change.
Honestly most of the work is updating the license files!
If this file gets hard to maintain, we can consider removal. If it's pretty easy to keep it for now, we can just keep it.
Honestly the only problem here is lack of tests.

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-K8s/17957/
Test PASSed.

Test build #113036 has started for PR 26332 at commit b842ad4.

Test build #113036 has finished for PR 26332 at commit b842ad4.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class GangliaReporter extends ScheduledReporter
   public static class Builder

Merged build finished. Test FAILed.

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

Test build #113037 has started for PR 26332 at commit 79bd378.

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-K8s/17958/
Test PASSed.

Test build #113037 has finished for PR 26332 at commit 79bd378.

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/113037/
Test PASSed.

IIUC, we are publishing our Ganglia module to Maven directly from Apache Spark 1.2.0 to 2.4.4 technically.

Spark doesn't publish this module directly, so that doesn't change.

https://repo1.maven.org/maven2/org/apache/spark/spark-ganglia-lgpl_2.11/

Ah sorry, you are correct. What I really mean is that it isn't bundled in the binary release, because that would entail distributing the ganglia dependency. At least this was true last time I checked!

Retest this please.

Test build #113178 has started for PR 26332 at commit 79bd378.

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-K8s/18092/
Test PASSed.

Test build #113178 has finished for PR 26332 at commit 79bd378.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Retest this please.

Test build #113182 has started for PR 26332 at commit 79bd378.

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-K8s/18096/
Test PASSed.

Test build #113182 has finished for PR 26332 at commit 79bd378.

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/113182/
Test PASSed.

Thank you so much, @srowen . Merged to master.
Also, thank you, @LucaCanali .

@LucaCanali @jerryshao maybe I can get your advice on something related here.
I was investigating back-porting this to 2.4.x. I find that the tests run out of memory with this change. A heap dump suggests that a lot of memory in consumed by MetricRegistry objects, with transitive references to all sorts of big objects. (Let's put aside why those references exist for now.)
As part of my hacking, I found that manually clearing all the Metrics in the registry when Spark's MetricSystem stops seems to resolve it. As in, in MetricSystem:
def stop(): Unit = {
    ...
      sinks.foreach(_.stop)
      registry.removeMatching(new MetricFilter {
        override def matches(name: String, metric: Metric): Boolean = true
      })
    ...
  }

Is this crazy? like, is clearing out all of the metrics going to break something? or is this a sensible cleanup step?
I'm still investigating, but wanted to reach out to anyone who may be familiar with this code.

What you write sounds reasonable to me. As an additional comment I'd say that while stopping the metrics system makes sense for a testing suite, it is not something that happens often in real usage: for most cases I can think of, metrics are started/registered at the component instance startup and they stay up for all its life.

Thanks @LucaCanali . Yeah, that's my worry. This means that after the Spark cluster is stopped, the metrics all disappear. Is that expected, or a problem? I am not sure how metrics are used. Of course at that point the components' lifecycle has ended anyway. Would external services rely on 'pulling' metrics after it's done but before the JVM stops, or do metrics implementations typically 'push' as they go? sorry for the dumb question.

Metrics are written to sinks at regular time intervals (configurable, let’s say 10 seconds). I mostly use the Graphite sink to write to an InfluxDB instance. Metrics are persisted there and consumed from InfluxDB by a Grafana dashboard.
The metrics system also has the MetricsServlet and more recently PrometheusServlet sink, which publish metrics to the Spark UI, + also I believe the JmxSink is quite popular. In these cases the idea is for the metrics to be consumed by the final user by pulling. It would be the end user/consumer's job to keep a history of the gathered metrics in these cases.

OK it's sounding reasonable to explicitly remove the registry then, as it's going away pretty immediately anyway, and the sinks are shutdown. I will propose it.
That helps the tests, which do start/stop contexts, and I think we otherwise somehow 'leak' all the previous metrics registries in this case. However it's kind of specific to the tests.
The other question remains: why is this an issue only in 2.4 (as far as I can tell), and only with metrics 4.x? Since you've looked at a lot of metrics related changes @LucaCanali , do you recall anything we fixed in 3.0 that might help avoid using a lot of memory in the metrics system? I don't, and didn't see anything in skimming JIRAs.
I am still not clear whether the big closures captured by gauges that Spark registers are necessary or an accident that will otherwise cause long-running apps to 'leak' somehow. I don't think so; what it retains a reference to are all the current Spark machinery like BlockManager. Not a problem as long as there is only one live BlockManager anyway. Still, need to keep an eye on it in 3.0.

Most of the PRs for the metrics system targeting 3.0 so far have been about adding new metrics.
It's good to know that the memory usage issue does not seem to affect 3.0 though.
BTW we could work on adding a few configuration parameters to allow turning on/off some of the more "chatty metrics"? For example: #26320


azure v0.34.0 - gopanic: send on closed channel

Hello,
with the latest version of thanos v0.34.0 running a compactor on an Azure Container storage. We are seeing from time to time some go panics while uploading the blocks. I think this is new to v0.34.0 and was working ok with v0.33.x
We are running in the official docker image with the following config:

args

      --log.level=debug
      --data-dir=/data
      --objstore.config=
        type: AZURE
        config:
          container: "argos-argos-amadeus-com"
          endpoint: "privatelink.blob.core.windows.net"
          storage_account: "$(OBJSTORE_ACCESS_KEY)"
          storage_account_key: "$(OBJSTORE_SECRET_KEY)"
          max_retries: 0
          http_config:
            insecure_skip_verify: true
      --wait
      --wait-interval=30m
      --compact.cleanup-interval=30m
      --compact.concurrency=8
      --downsample.concurrency=2
      --compact.blocks-fetch-concurrency=1
      --block-files-concurrency=1
      --block-meta-fetch-concurrency=5
      --web.disable
      --compact.progress-interval=10m
      --http-address=<IP_ADDRESS>:8080
      --consistency-delay=30m
      --retention.resolution-raw=35d
      --retention.resolution-5m=100d
      --retention.resolution-1h=100d
      --compact.skip-block-with-out-of-order-chunks

Go Panic stack trace

ts=2024-02-26T12:19:24.936631613Z caller=downsample.go:391 level=info msg="downsampled block" from=01HQ3G1QHTRFY7KSAJ2RJRXXT4 to=01HQJNH9DAP3BQCEKK8HT619MG duration=2m36.3914078s duration_ms=156391
ts=2024-02-26T12:19:37.839394217Z caller=azure.go:311 level=debug msg="uploading blob" blob=01HQJNH9DAP3BQCEKK8HT619MG/chunks/000001
panic: send on closed channel
goroutine 1233414 [running]:
github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/internal/shared.staticBuffer.Put(...)
/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v0.5.1/internal/shared/transfer_manager.go:83
github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/blockblob.(*copier).write(0xc0013c9400, {{0xc01d0a2000, 0x300000, 0x300000}, {0xc004e3c5a0, 0x58}, 0x300000})
/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v0.5.1/blockblob/chunkwriting.go:179 +0x39a
github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/blockblob.(*copier).sendChunk.func1()
/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v0.5.1/blockblob/chunkwriting.go:153 +0xb6
github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/internal/shared.NewStaticBuffer.func1()
/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v0.5.1/internal/shared/transfer_manager.go:62 +0x35
created by github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/internal/shared.NewStaticBuffer in goroutine 1233411
/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v0.5.1/internal/shared/transfer_manager.go:60 +0xc6
panic: send on closed channel
goroutine 1233413 [running]:
github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/internal/shared.staticBuffer.Put(...)
/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v0.5.1/internal/shared/transfer_manager.go:83
github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/blockblob.(*copier).write(0xc0013c9400, {{0xc01c5a8000, 0x300000, 0x300000}, {0xc00529a240, 0x58}, 0x300000})
/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v0.5.1/blockblob/chunkwriting.go:191 +0x37c
github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/blockblob.(*copier).sendChunk.func1()
/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v0.5.1/blockblob/chunkwriting.go:153 +0xb6
github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/internal/shared.NewStaticBuffer.func1()
/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v0.5.1/internal/shared/transfer_manager.go:62 +0x35
created by github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/internal/shared.NewStaticBuffer in goroutine 1233411
/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob@v0.5.1/internal/shared/transfer_manager.go:60 +0xc6

Oh, it looks like the azblob library is very old. It could be this issue; in fact the stack traces look pretty similar.

@MichaHoffmann Hello Michael, can we please make sure Thanos updates the go modules to get this fix in the next thanos versions?
I think the dependency is not updated.
I dont have right now the project setup on my localdev, so i guess its faster for anyone of you to upgrade and create a Pull request there. If it's not that easy for you, tell me and I'll try to find some time to do it.
Thank you :)
https://github.com/thanos-io/thanos/blob/main/go.mod#L67

@ahurtaud I just openend a pr to bump up the version. https://github.com/thanos-io/thanos/pull/7228
Sometimes maintainers might miss updating the dependency on the main repo. When anyone notices it, feel free to upgrade the go mod on Thanos and open a pr. Leaving a comment in the issue helps as well.


[WIP] Static typing with typescript

This PR is alternative way to solve #6 using typescript instead of flow.

the flow alternative can be found #8

Pros:

typescript seems to be a more robust typings solution. Things that flow allowed, typescript has flagged. (Although my flow setup is probably not 100%)
typescript auto generates type definitions for source methods. This makes exporting types trivial. (Again, this could be possible in flow but from what I saw, you have to manually define export types in flow)
singular build + typechecking
more robust editor integration

Cons:

GraphQL type definitions are not stock from graphql-js which uses flow
parsing isn't as flexible as flow in some cases (although with a type system I guess this is probably a good thing?)
Can't change type of var on the fly (This can't be right? Surely I'm missing something?) https://github.com/apollostack/apollo-client/blob/typescript/src/parser.ts#L10-L16
no support for ES7/8 spread operators let foo = { ...bar }

Note:
I'm really new to typescript and would love someone with some experience to take a look. From what I can tell though, we are going to run into some issues with graphql's existing typing. Take the following:
export function cacheFieldNameFromSelection(selection: Field): string {
  if (selection.arguments.length) {
    const argObj: Object = {};
    selection.arguments.forEach((argument: Argument) => {
      argObj[argument.name.value] = argument.value.value; // ERROR
    });
    const stringifiedArgs: string = JSON.stringify(argObj);
    return `${selection.name.value}(${stringifiedArgs})`;
  }

  return selection.name.value;
}

Not all types of Value in graphql-js have a value field:
interface IntValue {
    kind: string;
    loc?: Location;
    value: string;
}

interface FloatValue {
    kind: string;
    loc?: Location;
    value: string;
}

interface StringValue {
    kind: string;
    loc?: Location;
    value: string;
}

interface BooleanValue {
    kind: string;
    loc?: Location;
    value: boolean;
}

interface EnumValue {
    kind: string;
    loc?: Location;
    value: string;
}

// No value key
interface ListValue {
    kind: string;
    loc?: Location;
    values: Array<Value>;
}

// No value key
interface ObjectValue {
    kind: string;
    loc?: Location;
    fields: Array<ObjectField>;
}

interface ObjectField {
    kind: string;
    loc?: Location;
    name: Name;
    value: Value;
}

I'm not sure the best way around this.

Actually I feel like both things listed as drawbacks for typescript here are actually issues with my code!

My argument serialization for the cache key is not complete, and just doesn't handle list values properly, among other things
I think it isn't a good idea to change the type of a value mid-function so I think it would be best to change that code!

@stubailo I've made a branch to verify the CI will handle typescript correctly and highlight the current issues. If we want to slowly adopt typescript, we can use any in places where we still aren't strict enough with types?
here is the branch https://github.com/apollostack/apollo-client/tree/typescript-weak

On object spread, I agree that it’s a bit unfortunate that Typescript doesn’t support it given how popular they are in the Redux/functionalJS communities. Hopefully it will come sooner than latter, https://github.com/Microsoft/TypeScript/issues/2103, and so using Object.assign for now and replacing them by object spread when it arrives is reasonable.

Hmm, that's kind of a bummer - it's a reminder that TypeScript isn't compatible with all future JavaScript features that Babel might be. Perhaps it is worth it to just avoid those features to get the enhanced tooling...

So far the spread operator is the only big miss I've seen. I love ...foo but I do think the tooling out weighs it. Plus the timeline for it being added is within the next month or so :tada:

@jbaxleyiii I'm going to try to merge like all of these PRs today, if that's fine with you?

@stubailo that would be great! I'd recommend merging #11 instead of this one though since it will let us adopt fully typed more slowly

@jbaxleyiii after some in-depth conversation with @helfer I feel like it might be better to adopt Flow instead of TypeScript after all for the following reasons (assuming they both support basic typing requirements):

It will be nicer for potential users of this library that it's a codebase built using Babel that they can understand, with .js file extensions. I think Flow looks a lot more like "annotations on top of JavaScript" vs. TypeScript which is more like "a new programming language that looks like JavaScript".
People looking to use Apollo will have to accept using tools developed by Facebook, specifically GraphQL. It might be easier to convince those people that Flow is a reasonable choice than also having to trust Microsoft.
After looking into TypeScript a bit, it looks like it doesn't do well in cases where not all of your stuff is typed - it's a bit harder to incrementally adopt (as you've seen in these two PRs)

The next step for me is, I'm going to take your Flow PR and try to set up the right tooling in Atom to get autocompletion, etc. If it works well I think I'm going to call it in favor of Flow. If it's too hard to set up I'm going to do the same with TypeScript to see if it's significantly better.
Does this sound like a reasonable choice?

@stubailo that sounds good to me. I like typescript but flow is way easier to get into!

I'm starting to go back on this, after trying to get Flow to work... have you actually been able to get it to report a useful type error? Like it doesn't actually seem to check if the fields we are using are on the GraphQL AST...?

On @stubailo point 3., maybe I’m underestimating the amount of development that went into the Apollo client, but is the difficulty to incremental adopt typing is such a big deal? Mmaybe it’s worth spending a few days to have 100% type coverage (whichever type system end up being chosen)?

is the difficulty to incremental adopt typing is such a big deal?

I agree! I'm just wondering about stuff like NPM packages and the like. In TypeScript it seems like we basically need to have 100% coverage on these? I could be misinterpreting though.

Haven’t tried it yet but Typescript 1.8 introduced the ability to mix JavaScript and Typescript in the same application (see the release notes). (and there are already many libraries on DefinitelyTyped)

Can't change type of var on the fly

The way you do it is by defining a new var:
const myVar: string | number;
const myNumberVar =

@stubailo you fixed all the typing errors :tada: :tada:

Yeah arguably a lot of them were actual flaws in the code!

I'm really loving VS Code btw. This is super dope.

@stubailo the auto type generation is really great as a consumable:
import { Document } from 'graphql';
export declare function readQueryFromStore({store, query}: {
    store: Object;
    query: Document | string;
}): Object;
export declare function readFragmentFromStore({store, fragment, rootId}: {
    store: Object;
    fragment: Document | string;
    rootId: string;
}): Object;

@jbaxleyiii so should I merge this branch now, or what? Also, are you working on this full-time? If so, we should get on some kind of chat channel or something.

@stubailo I'm all for the merge! I can go through tonight and update my network interface to be typed :100: I'm working about 30% on this right now as I clean up and add a few quick features to our app that just launched. But I pretty much always have slack open so a chat would be awesome!

@jbaxleyiii can you join me on the MeteorChef slack? http://slack.themeteorchef.com/

I don't know if this is still helpful, but I believe you can use any JavaScript if you require it (not import as that does needs types).
const importEverything = require('myJavaScriptLibrary');
const { importThisOneThing } = require('myJavaScriptLibrary');

Ooh, good to know! So far, I've been able to find type definitions online for every library we are using, but it will be helpful to know we don't absolutely need them!

I noticed you have typings reference comments shown in the code in the pull request. I believe that is also not required anymore with recent versions of TypeScript. Good luck.

Yep, you'll see that the master branch doesn't have those anymore!


gpt-4-vision-preview这个模式下，请增加上传图片的功能

GPT-4 with Vision, sometimes referred to as GPT-4V or gpt-4-vision-preview in the API, allows the model to take in images and answer questions about them. Historically, language model systems have been limited by taking in a single input modality, text. For many use cases, this constrained the areas where models like GPT-4 could be used。
选择了这个模型，无法上传图片

附议

顶一顶

顶一手

顶一顶，该更新了，大佬！

+1

顶顶

This project is so neat, I believe the developer will add this function very soon.
Looking forward!!!

hhh, 这是要把开发者累坏的节奏呀😂

#3110

我这边实现了gpt4-vision-preview识图功能，可以了解下。
https://github.com/vual/ChatGPT-Next-Web-Pro


Add support for jest

I added support for jest through the jasmine matchers I wrote for #34.
Sadly I wasn't able to get the .not syntax to work; a solution for now is to use our negative variants (for instance expect(..).toNotDispatchActions)
This closes #33

Thanks a lot! Both jasmine and jest will lend in the new version!


Feature request: Selection TreeView style for Source Control

VSCode Version: 1.18.1
OS Version: Ubuntu Linux 17.10 x86_64

I would be very nice to have an optional way to stage changes on Source Control. The current way (add a file by selecting them and clicking in a + sign) can be very tricky when working with multiple files and folders. A Selection TreeView could be a little more intuitive, I think.
Image exemplifying the functionality:

https://github.com/Microsoft/vscode/issues/14582


@xtina-starr => Bump artsy-passport for redirect bug, and also maintain current filters

Last bit of functional work needed for the CTA!
Up next:

address some largely visual QA in https://github.com/artsy/force/issues/688
add analytics/AB test with @anipetrov

This PR:

bumps artsy-passport for a fix that didn't let you skip onboarding after social auth
maintains the current filter state (like ?medium=works-on-paper) through the /payoff and /follow screens

@mzikherman update the specs?

Just did!

That last failure looks unrelated. I see you kicked it again, fingers crossed. Everything looks good to me so feel free to merge when green.

🍏 mergey

👍


Committees: Old Committee members showing

Yesterday, I updated the Planning and Programming Committee members in Legistar. On boardagendas.metro.net, the new members are showing, but so are the old members. https://boardagendas.metro.net/committee/planning-and-programming-committee-a48178fe48d3/

https://boardagendas.metro.net/committees/ also shows two chairs and 11 members:

Hi, @shrayshray! Great to be back at it with you. 😊 I've gone in and cleaned up the errant memberships on the site: https://boardagendas.metro.net/committee/planning-and-programming-committee-a48178fe48d3/
Can you say a bit more about how you updated the memberships? It seems we got all of the incorrect ones in mid-July, and I no longer see them in the API. Were they deleted from Legistar?
Leaving myself a log, for posterity:
>>> Person.objects.get(family_name='Barger').memberships.filter(organization__councilmatic_organization__slug='planning-and-programming-committee-a48178fe48d3').values_list('start_date', 'end_date', 'role', 'updated_at')
<QuerySet [('2021-07-01', '2022-06-30', 'Member', datetime.datetime(2021, 9, 2, 4, 7, 25, 579922, tzinfo=<UTC>)), ('2021-07-01', '2022-06-30', 'Chair', datetime.datetime(2021, 7, 15, 4, 10, 33, 873320, tzinfo=<UTC>)), ('2017-07-01', '2018-06-30', 'Member', datetime.datetime(2020, 3, 24, 15, 10, 48, 897245, tzinfo=<UTC>)), ('2017-01-01', '2017-06-30', 'Member', datetime.datetime(2020, 3, 24, 15, 10, 48, 856112, tzinfo=<UTC>))]>
>>> Person.objects.get(family_name='Barger').memberships.filter(organization__councilmatic_organization__slug='planning-and-programming-committee-a48178fe48d3', end_date='2022-06-30', role='Chair').delete()

>>> Person.objects.get(family_name='Dutra').memberships.filter(organization__councilmatic_organization__slug='planning-and-programming-committee-a48178fe48d3').values_list('start_date', 'end_date', 'role', 'updated_at')
<QuerySet [('2021-07-01', '2022-06-30', 'Member', datetime.datetime(2021, 7, 15, 4, 10, 34, 902676, tzinfo=<UTC>))]>
>>> Person.objects.get(family_name='Dutra').memberships.filter(organization__councilmatic_organization__slug='planning-and-programming-committee-a48178fe48d3', end_date='2022-06-30').delete()

>>> Person.objects.get(family_name='Mitchell').memberships.filter(organization__councilmatic_organization__slug='planning-and-programming-committee-a48178fe48d3').values_list('start_date', 'end_date', 'role', 'updated_at')
<QuerySet [('2021-07-01', '2022-06-30', 'Member', datetime.datetime(2021, 7, 15, 4, 10, 34, 438341, tzinfo=<UTC>))]>
>>> Person.objects.get(family_name='Mitchell').memberships.filter(organization__councilmatic_organization__slug='planning-and-programming-committee-a48178fe48d3', end_date='2022-06-30').delete()

>>> Person.objects.get(family_name='Bonin').memberships.filter(organization__councilmatic_organization__slug='planning-and-programming-committee-a48178fe48d3').values_list('start_date', 'end_date', 'role', 'updated_at')
<QuerySet [('2021-07-01', '2022-06-30', 'Member', datetime.datetime(2021, 7, 15, 4, 10, 33, 237468, tzinfo=<UTC>)), ('2020-07-01', '2021-06-30', 'Member', datetime.datetime(2020, 8, 2, 0, 40, 12, 103255, tzinfo=<UTC>)), ('2014-07-01', '2015-06-30', 'Chair', datetime.datetime(2020, 3, 24, 15, 10, 48, 690803, tzinfo=<UTC>)), ('2017-07-01', '2018-06-30', 'Member', datetime.datetime(2020, 3, 24, 15, 10, 48, 648163, tzinfo=<UTC>)), ('2018-07-01', '2019-06-30', 'Member', datetime.datetime(2020, 3, 24, 15, 10, 48, 565012, tzinfo=<UTC>)), ('2019-07-01', '2020-06-30', 'Member', datetime.datetime(2020, 3, 24, 15, 10, 48, 430846, tzinfo=<UTC>)), ('2015-07-01', '2016-06-30', 'Chair', datetime.datetime(2020, 3, 24, 15, 10, 48, 102101, tzinfo=<UTC>))]>
>>> Person.objects.get(family_name='Bonin').memberships.filter(organization__councilmatic_organization__slug='planning-and-programming-committee-a48178fe48d3', end_date='2022-06-30').delete()

>>> Person.objects.get(family_name='Krekorian').memberships.filter(organization__councilmatic_organization__slug='planning-and-programming-committee-a48178fe48d3').values_list('start_date', 'end_date', 'role', 'updated_at')
<QuerySet [('2021-07-01', '2022-06-30', 'Vice Chair', datetime.datetime(2021, 7, 15, 4, 10, 34, 836038, tzinfo=<UTC>)), ('2017-01-01', '2017-06-30', 'Vice Chair', datetime.datetime(2020, 3, 24, 15, 10, 48, 355968, tzinfo=<UTC>)), ('2016-07-01', '2016-12-31', 'Vice Chair', datetime.datetime(2020, 3, 24, 15, 10, 48, 209322, tzinfo=<UTC>))]>
>>> Person.objects.get(family_name='Krekorian').memberships.filter(organization__councilmatic_organization__slug='planning-and-programming-committee-a48178fe48d3', end_date='2022-06-30').delete()

What happened?

Replicated 2020-1 memberships for 2021-2
Created new memberships once updated info came in
Replicated memberships that were not correct deleted

I'll open an issue to keep track of membership deletions so we get a better idea in a central place of how often this is happening, and open an issue on the scrapers about a revised mechanism for importing memebrships, where we delete and reimport everything on each scrape.


Motion Sensor entities cannot be changed

Prerequisites

[X] I have checked that this issue has not already been reported
[X] I am running the latest version of the integration
[ ] I have checked the Home Assistant logs for relevant errors

Description

I cannot change Motion Sensor entities. I can change all other entities in other categories. I have deleted the areas that need the sensors changed created before the 2024.12 update and the issue still exists in areas created after the 2024.12 update.
Steps to Reproduce

Expected behavior:

Change, add or delete motion sensors
Actual behavior:

The changes are submitted but then the have not stored and I go back into edit the area and nothing has changed.
Debug Information
Home Assistant version:

Integration version:

Integration configuration:

[X] Motion sensors
[ ] Media devices
[ ] Appliances
[ ] Illuminance sensors
[ ] Humidity sensors
[ ] Temperature sensors

Relevant logs:
# Copy relevant logs from Home Assistant

Additional Context

area_error_log.txt

Thanks for reporting, I can see the issue should have a fix tomorrow


Mismatches beetween lm_embeddings order and structure chains order

Trying to reproduce the training process, I found that at some point in the dataset preparation algorithm the order of  lm_embeddings and corresponding chains mismatch (for some proteins with multiple chains in the structure).
The example I found is the protein from 3doz complex, where lm_embeddings are concatenated in the order of chains [D, B, A] and all other protein graph features in the order [A, B, D].
I believe it happens because of this part https://github.com/gcorso/DiffDock/blob/8e853d6b14fb57baf90fa8529349117439f06819/datasets/pdbbind.py#L133-L141 which does not guarantee the same order as the order of chains in a .pdb file.

Thank you a lot for finding this and letting us know!
We will push a fix together with some other improvements soon instead of immediately to not disrupt compatibility with the currently provided weights.

It seems that the error occurs when one tries to retrain the model with own complexes containing and '' (underscore) in the name of the structure. In such a case the key_name = key.split('')[0] assigns the wrong value to the key_name.


Optimize bcast op

Describe the bug
bcast op is not optimized
The bcast variant sharded bcast_h was optimized to reuse in0
New timings:
block sharded (8x8) cores, H=256 W=9182
0.0225 ms
block sharded (8x8) cores, H=2048 W=9182
0.0359 ms
width sharded (8x8) cores, H=32 W=9182
0.005 ms
width sharded (8x8) cores, H=2048 W=9182
0.025 ms
Other variants (sharded h / hw and interleaved variants) need to be revisited for similar optimizations.
bcast_h interleaved timings:
interleaved (8x8) cores, H=256 W=9182
0.255 ms
--> very slow for a bcast, interleaved bcast_h also not re-using in1.
Other possible optimizations to consider (e.g. for sharded bcast_h, but might also applicable for other variantes):

mcasting for block sharded inputs
wrapping around 32 for in1 (as done in layernorm) to reduce the number of tiles to be read

FYI: @TT-BrianLiu @shwetankTT @tt-aho @davorchap @uaydonat

We are in the process of removing bcast entirely.   @johanna-rock-tt can we swap out for the ttnn add/multiply/subtract and check these performance issues?


RetryAfter Error

Error:
ERROR teloxide::error_handlers   > An error from the update listener: RetryAfter(5s)

Made throttle bot to avoid it: link
Anything changed.

Fixing attempt - d87a07f
https://github.com/teloxide/teloxide/issues/1120

[2d68e2d]:
Testing possible fixes by Teloxide contributors.
(Comment about possible fix)

I contacted the teloxide team, they explained that the error may depend on the poor quality of the Internet. They will not fix it somehow, as a solution I see only changing the logging level for them to "Debug".


Remove PATH assumption from fhs-userenv.

Previously is was assumed that bash was in the path when calling the
environment setup script. This changes all of the references of bash to
be absolute paths so that the user doesn't have to worry about the
environment they call it with.

I have no problem regarding the change but how have you encountered a problem?  bash should be called inside FHS sandbox and we have bashInteractive there as a base package (see https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/build-fhs-chrootenv/env.nix#L50).

I don't know what caused it but this issue came up a couple of days ago on master. This commit looks suspicious for triggering the issue but a good idea to do. Also you have linked fhs-chrootenv where as I was using fhs-userenv.

The use case was calling this from a systemd service. (I'm running a fuzzer in an environment because the shell script doesn't play nicely with Nix). I suppose it rears it's head in this scenario because the path only has the bare minimum in this case, where as most other times you have bash in your path.

This part of build-fhs-chrootenv is common -- it builds an actual FHS environment. Anyway, let's merge this, assumptions like that are invalid anyway (what if we'd change the default shell in FHS in future?).