Add background image

Add background image. Maybe implies sending only drawing instead of full image data on mouse up

Hello I'm trying to load a bg image but doesn't work for me, can you pls help me. Thanks in advance.
repo
deployed app


this.$router in component

I have a problem to navigate route my web via event handler such as @click

Can i use a this.$router in a component ?

Yes, you can use the router in a component, but I think that you are not doing it right.
Don't put that into the console.log ...


Manage vulnerability sources in database

Add a model for available data sources where we can keep metadata such as the license under which the vulnerability data is published. This would make it easier to maintain this kind of information than having it in the code. When we have importers for standardized formats like OVAL it would also allow to add additional data sources that follow this standard by adding a new entry to this DB table.
An implementation of this would benefit from a bit of refactoring to some kind of base class for vulnerability sources.

closed by #152


wait-for-expect dependency throws Unknown plugin "@babel/proposal-class-properties"

dom-testing-library version: 2.2.0
react-testing-library version: 3.0.2
react version: 16.3.1
node version: v8.9.4
npm (or yarn) version: 6.0.0

What you did:
Upon updating to the latest version of react-testing-library I now receive the following error when running npm test
What happened:
    ReferenceError: Unknown plugin "@babel/proposal-class-properties" specified in "/Users/ec/Payload/payload/node_modules/dom-testing-library/node_modules/wait-for-expect/.babelrc" at 0, attempted to resolve relative to "/Users/ec/Payload/payload/node_modules/dom-testing-library/node_modules/wait-for-expect"

      at node_modules/babel-core/lib/transformation/file/options/option-manager.js:180:17
          at Array.map (<anonymous>)
      at Function.normalisePlugins (node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
      at OptionManager.mergeOptions (node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
      at OptionManager.init (node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
      at File.initOptions (node_modules/babel-core/lib/transformation/file/index.js:212:65)
      at new File (node_modules/babel-core/lib/transformation/file/index.js:135:24)
      at Pipeline.transform (node_modules/babel-core/lib/transformation/pipeline.js:46:16)

Problem description:
I'm not entirely sure if this a config issue on my end or with the wait-for-expect package within dom-testing-library, but I decided to ask here first.

Very weird, could you remove your node_modules and package-lock.json and run npm install again?

Removed both node_modules and package-lock.json and it still seems to happen.

I don't understand why jest is trying to read .babelrc from there - you shouldn't be "babeling" your node_modules.
But, at the same time, we shouldn't have the .babelrc there in the first place in the npm package anyway, only in the sources, so I will tweak that.

No problem. Please let us know what you find :-)
You might need to put. "wait-for-expect": "0.6.2" in your devDependencies to force using that particular version

After fixing what I believe was a jest configuration problem and doing a fresh npm install I no longer receive this error. Thanks for all your help.


Add support for string interpolation

This requires support in the parser and a new InterpolatedStringExpression class or similar.

Completed in https://github.com/ethanblake4/dart_eval/commit/eaa0a049a7f6a8c17686fdf8fe330592fc0ccf3f


Added support for SimplePay payment gateway.

This is the plugin for SimplePay payment gateway (developers.simplepay.ng).

Sorry did it to wrong branch


Update tag to 1.0.10.

Updates the buildkit tag. (and that's it.)

done in https://github.com/Islandora-Devops/isle-dc/pull/316


Merge Main into Compatability

Do this so I can delete the ones which are necessary to delete.

No, this was bad and unnecessary and bad and not the right way to do this, closing time.


Fix links to various alloc citizens

This fixes all of the warnings that pop up from cargo doc

Thanks, forgot that when converting to no_std.


Change reissue_transaction_until_included() to await_block_inclusion()?

Change reissue_transaction_until_included() to something like await_block_inclusion()? Reissuing doesn't work the same way anymore as before (if one block was already successfully sent) and requires more mana which needs to be alloted first, therefore it's probably better to just wait for inclusion of the block and if the tx doesn't get confirmed create a new one.

This seems related to #1867


WIP: some steps to implement alphaGen portal

I don't claim it is working, but we need this to make it work.
We can notice the current code computes the distance to portal in fragment shader, but ioq3 does it in vertex shader, and it's probably faster to do it once per vertex than once per pixel, but this is a good start.
I'm not sure the existing GLSL code is correct, but the GLSL code will not run without those patches anyway.
The ioq3 code also does the range compute in the generic shader and at some point we may want to do the same as there may be other needs for doing blend operations according to distance, but yet again, we can look small and do small steps after small steps.

When I apply #1019 I see the portal map being blended with distance, though it is upside down and it is not blended over the portal but over itself, but this is promising.

I think I've identified the issue, hopefully should be fixed soon.

I believe this is because of how we render portals now. The portal surfaces themselves are not rendered with the other surfaces, but alphagen portal uses Render_portal() which seems to be a really old function. I assume that's a relic of the fixed function pipeline where it had to be drawn in multiple passes. We can just pass the alphagen parameters and texture to the shader now and blend it there.

Yeah, ioq3 apply alphaGen portal directly in generic_fp.glsl.

We should too, we can use gl_FragDepth with a uniform passing in the alphagen value. Might need to get the linear depth since I assume that's what alphagen portal is supposed to use.

You might need to add Tess_Begin() and rb_surfaceTable() or equivalent. I think the reason we're getting incorrect rendering here might be because the portals are rendered as follows:

PreparePortalCommand
DrawViewCommand
FinalisePortalCommand
That last one does a Tess_Begin(), rb_surfaceTable and a Tess_End(), while Render_portal() just does Tess_DrawElements(), which would then have indirect data (presumably Render_portal() would be called after FinalisePortalCommand).

Current state is:

image is displayed properly,
fading works, but fading to black instead of fading to portal render,
fading it inversed: image is seen when close and disappear when moving back, while the image should not be rendered when close and appear when moving back.

fading works, but fading to black instead of fading to portal render,

Not sure what that means.

fading is done in reverse: image is seen when close and disappears when moving back, while the image should not be rendered when close and start appearing when moving back.

Isn't that the crrect behaviour? I'm pretty sure trem works like that too (it also just makes sense, what's the point of a portal that you can't really see?).

You should see the portal surface (the scene from the camera) when close, but the fallback image when far, with the fallbck image fading from transparent to opaque while increasing the distance. The idea is that the portal is only rendered when close with an image rendered instead when far.

Oh, so it's just backwards, right? I think just changing color.rgb *= 1.0 - clamp(len, 0.0, 1.0); to color.rgb *= clamp(len, 0.0, 1.0); should fix it.

OK, now two things are missing:

Once out of range, the surface turns full black instead of just rendering the image.
there is no blending to a portal surface, but to black.

I also noticed that while it fades in the right direction, it doesn't really fade to black.
Example of test scene: nova, 9459 3037 -21 59 3.

I also noticed that while it fades in the right direction, it doesn't really fade to black.

It should be fading to an image though, rather than black?

Incorrect might be because alpha channel is not set and/or because of the blend functions.

It should be fading to an image though, rather than black?

It should be fading to the image from the distant camera.
I assume fading to black is expected when blending is not working yet.

Blending is fixed now.

I also noticed that while it fades in the right direction, it doesn't really fade to black.
Example of test scene: map nova, viewpos 9459 3037 -21 59 3.

What you're seeing on nova is because the game doesn't render the portal at all from this position.

This also happens on 0.54.1, so at least it's not a regression (or not a recent one).

Blending is fixed now.

Excellent!

What you're seeing on nova is because the game doesn't render the portal at all from this position.

Yes. The expected behavior of such surface is that when the view position is out of range, the surface always renders the textures, so what should be disabled is not the whole material, but only the portal rendering, with the texture being displayed.

Doing this “fixes” it:
diff --git a/src/engine/renderer/tr_main.cpp b/src/engine/renderer/tr_main.cpp
index 061baee51..f19166508 100644
--- a/src/engine/renderer/tr_main.cpp
+++ b/src/engine/renderer/tr_main.cpp
@@ -1587,7 +1587,7 @@ static bool SurfBoxIsOffscreen(const drawSurf_t *drawSurf, screenRect_t& surfRec

 	if (shortest > (shader->portalRange * shader->portalRange))
 	{
-		return true;
+//		return true;
 	}

 	return false;
@@ -1741,7 +1741,7 @@ static bool SurfIsOffscreen( const drawSurf_t *drawSurf, screenRect_t& surfRect

 	if ( shortest > ( tess.surfaceShader->portalRange * tess.surfaceShader->portalRange ) )
 	{
-		return true;
+//		return true;
 	}

 	return false;

But this is wrong, it defeats the portalRange, meaning the portals are always rendered. What we need is to never disable the surface when out of range, but to disable the portal rendering when out of range.

I tried doing this:
--- a/src/engine/renderer/tr_main.cpp
+++ b/src/engine/renderer/tr_main.cpp
@@ -1585,10 +1585,7 @@ static bool SurfBoxIsOffscreen(const drawSurf_t *drawSurf, screenRect_t& surfRec
 		return false;
 	}

-	if (shortest > (shader->portalRange * shader->portalRange))
-	{
-		return true;
-	}
+	shader->isPortalOutOfRange |= shortest > (shader->portalRange * shader->portalRange);

 	return false;
 }
@@ -1739,10 +1736,7 @@ static bool SurfIsOffscreen( const drawSurf_t *drawSurf, screenRect_t& surfRect
 		return false;
 	}

-	if ( shortest > ( tess.surfaceShader->portalRange * tess.surfaceShader->portalRange ) )
-	{
-		return true;
-	}
+	shader->isPortalOutOfRange |= shortest > ( tess.surfaceShader->portalRange * tess.surfaceShader->portalRange );

 	return false;
 }

Now I'm looking for a place to do:
if ( shader->isPortalOutOfRange  )
{
 	return;
}

To  avoid rendering the related portal surface when out of range, but without disabling the surface itself.

Now I'm looking for a place to do:
if ( shader->isPortalOutOfRange  )
{
 	return;
}

To avoid rendering the related portal surface when out of range, but without disabling the surface itself.

Perhaps in an else block here?
https://github.com/DaemonEngine/Daemon/blob/e522be8b10f3c31a5218337a420d01c42795bf31/src/engine/renderer/tr_main.cpp#L2094-L2101

This works now:

LGTM


Cannot read property 'defaultView' of undefined

peError: Cannot read property 'defaultView' of undefined
at Object.getStyle (http://<IP_ADDRESS>:41998/appservice/f2-canvas/lib/f2.js:1532:61)
at Object.getWidth (http://<IP_ADDRESS>:41998/appservice/f2-canvas/lib/f2.js:1534:22)
at t.e._initCanvas (http://<IP_ADDRESS>:41998/appservice/f2-canvas/lib/f2.js:2152:47)
at new t (http://<IP_ADDRESS>:41998/appservice/f2-canvas/lib/f2.js:2136:96)
at e.n._initCanvas (http://<IP_ADDRESS>:41998/appservice/f2-canvas/lib/f2.js:763:19)
at e.n._init (http://<IP_ADDRESS>:41998/appservice/f2-canvas/lib/f2.js:770:24)
at new e (http://<IP_ADDRESS>:41998/appservice/f2-canvas/lib/f2.js:652:15)
at

https://github.com/antvis/f2-canvas#问题-1


Cleanup DTLog, implement log levels

Add version suffix in DTLibInfo
Remove duplicate mode logging
Use tryFlush() instead of flush()
Add constant LOG_PATH_SEPARATOR
Use RobotController.getTeamNumber() instead of custom implementation
Change unknown team number to 0
General cleanup, suppress useless warnings

Implement log levels for variables. They filter variables based on their immediate parent's log level, allowing components to be selectively logged based on the current level. Levels for variables are not denoted in the log output.
Also, properly implement log levels for messages. These are denoted in the log, under identifiers 0x0008 through 0x000B.

Properly log exceptions where applicable (not during startup, DEBUG level when explicitly caught, etc.)

This PR is ready for review


Could not set style to columns and also could not make columns autofit

Styles requires the Pro Version https://sheetjs.com/pro


[Question] Is it safe to add an OnRootViewsChangedListener to Curtains.onRootViewsChangedListeners from an Activity?

Is it safe call Curtains.onRootViewsChangedListeners += OnRootViewsChangedListener { ... from an Activity?
I'm assuming yes, but didn't know if there are any particular issues or any special cleanup needed with doing so.
The reason I'm asking is because I would like to avoid writing any business logic within my custom Application class and because I have a single Activity in my project, it makes sense to keep view/window-related listeners there.
Thanks!

It should be safe to do this from anywhere, however you need to be careful to remove it when the activity is destroyed. Also remember that there can be several activities in create state at the same time so you might register several listeners.


scratchhost servers

they're down, dont know if its me?
https://panel.justablock.online/

Don't think so
T_cat9000_2 @.***> schrieb am Di., 5. Nov. 2024, 01:33:

they're down, dont know if its me?
https://panel.justablock.online/
—
Reply to this email directly, view it on GitHub
https://github.com/TimMcCool/scratchattach/issues/271, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCKMZUF545L5KTGBSGXXTLZ6776FAVCNFSM6AAAAABRFMSY76VHI2DSMVQWIX3LMV43ASLTON2WKOZSGYZTIMJVG4ZTGMY
.
 It won't ever install any servers

oh that's what you mean
SpyC0der77 @.***> schrieb am Di., 5. Nov. 2024, 14:44:

Yeah they are. It won't ever install any servers
—
Reply to this email directly, view it on GitHub
https://github.com/TimMcCool/scratchattach/issues/271#issuecomment-2457219560,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCKMZSPESH3QALRXC3LHFDZ7DDSFAVCNFSM6AAAAABRFMSY76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJXGIYTSNJWGA
.
You are receiving this because you commented.Message ID:
@.***>

@TheCommCraft The servers on there never finish installing, and it gives me an error when I press reinstall or delete server. Also, I can create unlimited servers free of charge

should i use something else if so what?

*it needs to be free

I will look into it

I will look into it

I use SillyDev but currently they dont have any open nodes

this hurts nothing is up. but ill try sillydev...

it does not have what i am looking for, if so not free.

do i just put the scratchattach source code in the home area?
from flask import Flask, request
import random
import time
import requests

app = Flask(__name__)

@app.route('/')
def home():
  return "hello world!"

if __name__ == '__main__':
    app.run(debug=True)

@webbrowser11 you have to put the vode above the if __name__ == '__main__'

it does not have what i am looking for, if so not free.

wdym, it is just scratchhost but you get more credits per minute

no i have to pay pounds. im also not in the UK :skull:

ight i just needa figure out how to run it now...

i am also not in uk

lol

i got the link i just neeeeddaaa ping it i thinnnkkk

nope thats not working....

i found different hosting made by this scratcher: https://scratch.mit.edu/users/uukelele/
my code just wont work on scratchattach 2.0 now:
import scratchattach as attach
import time

print("Creating session")
session = attach.login("sped_AI", "nap bud")
print("Connecting studio")
studio = session.connect_studio("35292763")
off = 14640
index = 0
while True:
    print(f"Fetching projects with offset of {off}")
    projects = studio.projects(limit=20, offset=off)
    for project_info in projects:
        index += 1
        project = session.connect_project(project['id'])
        project.get_author().follow()
        print(f"{index}: Followed author {project.get_author().username} from project {project.title}")
    off += 20
    time.sleep(60)

Just look at the errors and you'll find where your mistakes are. The login
method is incorrect.
T_cat9000_2 @.***> schrieb am Mo., 11. Nov. 2024, 22:30:

i found different hosting made by this scratcher:
https://scratch.mit.edu/users/uukelele/
my code just wont work on scratchattach 2.0 now:
import scratchattach as attach
import time
print("Creating session")
session = attach.login("sped_AI", "nap bud")
print("Connecting studio")
studio = session.connect_studio("35292763")
off = 14640
index = 0
while True:
print(f"Fetching projects with offset of {off}")
projects = studio.projects(limit=20, offset=off)
for project_info in projects:
index += 1
project = session.connect_project(project['id'])
project.get_author().follow()
print(f"{index}: Followed author {project.get_author().username} from project {project.title}")
off += 20
time.sleep(60)
—
Reply to this email directly, view it on GitHub
https://github.com/TimMcCool/scratchattach/issues/271#issuecomment-2469052630,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCKMZVGGW7SAH7X2BH773L2AEOYVAVCNFSM6AAAAABRFMSY76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRZGA2TENRTGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Actually the login method looks correct to me, but there are a few other things you need to change:
Change
    projects = studio.projects(limit=20, offset=off)
    for project_info in projects:
        index += 1
        project = session.connect_project(project['id'])

to
    projects = studio.projects(limit=20, offset=off)
    for project in projects:
        index += 1

and project.get_author() to project.author()

i already did that, and it was rate limiting me so i added some waits its good now

Actually the login method looks correct to me, but there are a few other things you need to change:
Change
    projects = studio.projects(limit=20, offset=off)
    for project_info in projects:
        index += 1
        project = session.connect_project(project['id'])

to
    projects = studio.projects(limit=20, offset=off)
    for project in projects:
        index += 1

and project.get_author() to project.author()

wasn't the login by password changed

yeah


install and setup

Hi,
I have installed the plugin and the theme and followed your instructions, however, I am not able to configure it correctly.
I run npm install, and configure the theme and plugin settings.
everything works however the front-end theme layout is missing css?
the console returns 4 errors
GET http://localhost/@vite/client net::ERR_ABORTED 404 (Not Found)
localhost/:87 GET http://localhost/resources/js/app.js net::ERR_ABORTED 404 (Not Found)
localhost/:88 GET http://localhost/resources/js/home.js net::ERR_ABORTED 404 (Not Found)
localhost/:86 GET http://localhost/@vite/client net::ERR_ABORTED 404 (Not Found)

If I try to run npm run watch  the script is missing.
$ npm run watch
npm ERR! missing script: watch

npm ERR!      C:\Users\hesse\AppData\Roaming\npm-cache\_logs\2022-01-27T23_02_46_021Z-debug.log

If I switch dev port from 80  (lxamp localhost port) to 3000 the console return other errors:
Failed to load resource: net::ERR_CONNECTION_REFUSED                        client:1
app.js:1 Failed to load resource: net::ERR_CONNECTION_REFUSED           app.js:1
home.js:1 Failed to load resource: net::ERR_CONNECTION_REFUSED        home.js:1

how to proceed from this point?

Hello @Hessel91
Are you using it with OctoberCMS or WinterCMS, and which version to check please.
Thanks.

Hi, OctoberCms on localhost >version 2.1.27


Fixup RPC responses to always be json

May introduce some double-jsoning, but seems to be fine on my end.
Opening as draft to see if the CI is happy.
Also improved the server stop command to show something nice, and shutdown gracefully on the Flask side.

Ci is happy!


SpringBoot Webflux reactive non blocking application. Performance drop using Logstash when sending logs to logstash server

Hello team,
This is my first post in this repo.
If not anything else, wanted to say thanks for the project.
It is easy to use, clear and simple.
Wanted to reach out to report an issue:
Setup: I have a basic Spring Webflux reactive non blocking web application.
Upon invoking the rest endpoint, I have application logs.
We forward those logs to a Logstash endpoint (which later will forward to our ElasticSearch)
Therefore, this is the push model (it is not like logstash or filebeat will come and "poll" the logs)
While the logs are indeed being sent, we are unfortunately observing performance drop.
Periodically, we can see our app "freeze". After investigation with actuator, it seems the app "freezes" when trying to send the logs.
The freezes are disappearing if we do not enable logstash forwarding (when we just print the logs in console without forwarding, the app is fine).
We are running our reactive application using 1CPU only. Therefore, would it be possible Logstash performs a blocking operation when sending the logs, thus blocking the reactor core?
If yes, can we have a non blocking version when sending the logs please?
Thank you
       <dependency>
            <groupId>net.logstash.logback</groupId>
            <artifactId>logstash-logback-encoder</artifactId>
            <version>7.2</version>
        </dependency>

<?xml version="1.0" encoding="UTF-8"?>
<configuration>

    <property scope="context" name="log.fileExtension" value="log"/>
    <property scope="context" name="log.directory" value="/logs"/>
    <property scope="context" name="log.fileName" value="reactiveapp"/>

    <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
        <layout class="ch.qos.logback.classic.PatternLayout">
            <pattern>[%d{yyyy-MM-dd HH:mm:ss.SSS}] [${HOSTNAME}] [%thread] %level %logger{36}@%method:%line - %msg%n</pattern>
        </layout>
    </appender>

    <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
            <fileNamePattern>${log.directory}/${log.fileName}.%d{yyyy-MM-dd}.${log.fileExtension}</fileNamePattern>
        </rollingPolicy>
        <encoder>
            <pattern>[%d{yyyy-MM-dd HH:mm:ss.SSS}] [${HOSTNAME}] [%thread] %level %logger{36}@%method:%line - %msg%n</pattern>
        </encoder>
    </appender>

    <appender name="STASH" class="net.logstash.logback.appender.LogstashTcpSocketAppender">
        <destination>mylogstash:5000</destination>
        <!-- encoder is required -->
        <encoder class="net.logstash.logback.encoder.LogstashEncoder"/>
        <keepAliveDuration>5 minutes</keepAliveDuration>
    </appender>

    <logger name="org.hibernate" level="TRACE">
        <appender-ref ref="STASH"/>
    </logger>

    <root level="INFO">
        <appender-ref ref="STDOUT"/>
        <appender-ref ref="STASH"/>
        <appender-ref ref="FILE"/>
    </root>
</configuration>

Hi @patpatpat123,
The LogstashTcpSocketAppender is an asynchronous appender, in that it does not block the thread that calls the logger.  The log event is put onto a ring buffer.  Another thread retrieves the event from the ring buffer, encodes it in JSON, and sends the JSON over the TCP connection.  If the TCP connection is slow, and the ringbuffer backs up, then when new events are attempted to be added to the ring buffer, those events will be dropped by default (so as to not prevent blocking the calling thread).
The sending thread uses blocking I/O.   However, this should not block the thread calling the logger, since it is a different thread.  A 1CPU machine should be able to schedule these threads appropriately and not freeze the app, however there will be some context switching overhead.
Perhaps you could use a profiler to dig in a little more?  I use yourkit quite a bit when profiling, and it can capture a CPU profiling snapshot that might help.

Hello @philsttr,
Very clear answer. Indeed, from your writing, the root cause should not be the appender.
Running some tests with yourkit asap and will update or close this.
Again, many thanks

Hello team, it seems indeed the LogstashTcpSocketAppender  is not the root cause of the issue.
Apologies for the inconveniences caused. Closing


python310Packages.mlflow: 1.25.1 -> 1.26.0

Description of changes
https://github.com/mlflow/mlflow/releases/tag/v1.26.0
Fix build (https://hydra.nixos.org/build/177827835)
ZHF: #172160

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg eval


Making links on side navbar hover with transition

On the links of the Side Navbar, there is no hover & transition effect. Can I work on this?

Sure.
Also before creating PR make sure to send screenshot or short video of your changes

Please assign it to me. If the issue is still open.

Sure

@AyushSarode I've already started working on it and just need to make an PR

@AyushSarode I've already started working on it and just need to make an PR

Can you make PR tmrw?

@AyushSarode I've already started working on it and just need to make an PR

Can you make PR tmrw?

Yeah sure
Within an hour

@AyushSarode I've already started working on it and just need to make an PR

Can you make PR tmrw?

Yeah sure Within an hour

Thanks!

@AyushSarode I've raised my PR kindly review and merge it.


How to handle client clock being skewed, not synced with actual time?

Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[X]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Description
Is there any guidance on how to deal with client clock being skewed. Eg imagine a scenario where the client's clock thinks it is currently 18:00 UTC and has a cached token that is valid until 19:00 UTC. The client app then makes an api call using the cached token since it thinks it is still valid. However, the actual time is 20:00 UTC, and the server rejects the request with a 401 because the token is expired (the token expires around 19:00 UTC, and the current time is 20:00 UTC)
We see evidence of this happening in our current application, where the client side log's show the request being made at an incorrect time like 18:36 UTC (the timestamp is from client side clock) but when we search up the request in backend logs, the time is 19:32 UTC and the client had passed a token that is valid until 19:00 UTC.
I was wondering if this scenario has been encountered before, if so, is there any guidance on how to handle such situations? In my opinion, it looks like the solution boils down to the client app being aware that the time is incorrect and should react to that (display some error message or force fetch a new token)
Thanks!
Source

[X] Internal (Microsoft)
[ ] Customer request

@thoo1 Are we talking about access tokens or refresh tokens? If it's access tokens, the token expiration date returned in the response should be calculated based on the client's time. Tokens are valid by default for 1 hour from when they are issued. When you call acquireTokenSilent, it will check the current expiration time based on the client side calculation and renew the token if it is past this time.

We see evidence of this happening in our current application, where the client side log's show the request being made at an incorrect time like 18:36 UTC (the timestamp is from client side clock) but when we search up the request in backend logs, the time is 19:32 UTC and the client had passed a token that is valid until 19:00 UTC

This shouldn't be the case. So lets say the client's clock is skewed 1 hr before the server's clock (using your example). If the client acquired a token at 18:00, the token should have a exp claim, assuming 1hr token lifetime, based on the server's clock of 20:00 in its claims (19:00 + 1hr)  (double checking this, but pretty sure that this is how it works), but MSAL will set the expiration date to 19:00. When the token is validated, it should be based on the time of the server's clock.
Are you seeing different behavior? Check the exp claim of the token.

In the above image you can see there is a slight difference in the expiration times - this is because the expiration used by MSAL is calculated separately than the one from the auth server.
There is a tokenRenewalOffsetSeconds configuration option but this is usually to offset seconds or minutes, not an entire hour.

The client app then makes an api call using the cached token since it thinks it is still valid

How does this happen? The client should be using acquireTokenSilent to retrieve a new token to make sure that the token is still valid. If it isn't valid, acquireTokenSilent should be renewing the token. acquireTokenSilent does this based on the client clock, not the exp claim in the token.

the server rejects the request with a 401

By "the server" do you mean the resource server? How does the token validation happen?

Hi @pkanher617 thanks for taking your time to look into this. I can answer some of your questions

The client app then makes an api call using the cached token since it thinks it is still valid
How does this happen? The client should be using acquireTokenSilent to retrieve a new token to make sure that the token is still valid. If it isn't valid, acquireTokenSilent should be renewing the token. acquireTokenSilent does this based on the client clock, not the exp claim in the token.

Sorry for the confusion in my wording, when I said client app I meant the msal-library, we do just use acquireTokenSilent and don't do anything special on top. I meant to express that msal-browser library thought the token was still valid (as it looks at the client clock, not the exp claim) and our code sent the request with the token. Since the client clock was about an hour behind, the token in reality was expired and the server had rejected it.

This shouldn't be the case. So lets say the client's clock is skewed 1 hr before the server's clock (using your example). If the client acquired a token at 18:00, the token should have a exp claim, assuming 1hr token lifetime, based on the server's clock of 20:00 in its claims (19:00 + 1hr) (double checking this, but pretty sure that this is how it works), but MSAL will set the expiration date to 19:00. When the token is validated, it should be based on the time of the server's clock.

I understand what you're saying, and I agree. If the client clock is consistently 1 hour behind the server, that is fine as long as long as the server validates the token using the exp claim (which will be based on server time). Let me validate this with the backend team, that they are using the exp claim (I don't see any other claim that could be used).
There is one small nuance. What happens if the client clock is not consistently 1 hour behind? I'll see if I can validate this in the logs first before I raise this topic further
Thanks for your answer! I'll do a bit more digging

I think we need to be really clear here about which actors are performing specific actions. There is a client, which calls ATS to get tokens. This client should never be sending expired tokens. ATS always calculates lifetimes based on the client's clock, so it should never return a token that has passed the lifetime.
There is a resource server, which validates the access token. If this service is out of sync, there are going to be issues no matter what.
Finally, there is the auth server which is the one that accepts the login credentials and issues tokens.

Since the client clock was about an hour behind, the token in reality was expired and the server had rejected it.

If the token was used within an hour of when it was issued, the only way it would be expired on the service but not the client would be if the client clock is somehow moving slower than the server's clock, or the resource service is also skewed. Expiration for ATS is calculated based on lifetime, not exact timestamps.

There is one small nuance. What happens if the client clock is not consistently 1 hour behind? I'll see if I can validate this in the logs first before I raise this topic further

Again, the expiration timestamp claim of the token is always based on the auth server's clock, not the client. It depends on the resource service validating the token. If that resource service is out of sync, there isn't much we can do. As I said above, the only way the client would be sending expired tokens is if the clock is somehow moving at a different rate than the auth server's clock. Meaning, 1hr on the service is >1hr on the client.

Closing as this doesn't appear to be a problem with the library. Please open a new issue if you determine there is any action we need to take, thanks!


Update Licences at Notice.txt to reflect dependency changes.

We will recreate PR by reexecuting the pipeline after fixes.


The num_edges member of the Graph object is incorrect when graph is weighted

Given a weighted graph object, the graph.num_edges gives half of the total volume of the graph, rather than the actual number of weighted edges.
This should be replaced with two methods on the object, a num_edges method which gives the number of non-zero elements of the adjacency matrix (corrected for the symmetry) and a graph_volume method which returns the total weight of all the edges in the graph.

Fixed by pull request #11 .


Add validation rule to make sure Relationship columns in join condition are all defined in model columns

considering the following scenario
model("Book",
        "select * from (values (1, 'book1', 1), (2, 'book2', 2), (3, 'book3', 3)) book(id, name, authorId)",
        List.of(
                column("id", GraphMLTypes.INTEGER, null, true),
                column("name", GraphMLTypes.VARCHAR, null, true),
                column("author", "People", "BookPeople", true))),
model("People",
         "select * from (values (1, 'people1'), (2, 'people2'), (3, 'people3g')) People(id, name))",
         List.of(
                 column("id", GraphMLTypes.INTEGER, null, true),
                 column("name", GraphMLTypes.VARCHAR, null, true),
                 column("book", "Book", "BookPeople", true)))),
relationship("BookPeople", List.of("Book", "People"), JoinType.ONE_TO_ONE, "book.authorId  = people.id")

We will rewrite Book to
SELECT id, name, author FROM
    (select * from (values (1, 'book1', 1), (2, 'book2', 2), (3, 'book3', 3)) book(id, name, authorId))

As you can see, column authorId is eliminated from the physical table Book. While authorId still needed in relationship rewrite. Therefore we need to make sure that relationship join condition columns should all defined in model fields.

this is a non-goal, so close it


Opt-out for knobs URL update

Is your feature request related to a problem? Please describe.
If you have a lot of complexes props on some component, you might end up with a too long URL in the browser bar.
Then when you refresh the page or try to add iframe.html to the URL you will get an "Request-URI Too Long" error.
Describe the solution you'd like
Add an opt-out to not update the URL with knobs values.
Ideally you want to opt-out only for some knobs (huge object knobs for instance).
A general opt-out can also be a solution.
Describe alternatives you've considered
Not using knobs ?
Are you able to assist bring the feature to reality?
Maybe. Need to ask my boss.
Additional context
This is a duplicate of closed issue #1680

knobs now no longer appear in the url, unless you generate a share-url


Small k in url

/assign @kbhawkey

Page preview:
https://deploy-preview-23876--kubernetes-io-master-staging.netlify.app/docs/reference/glossary/?all=true#term-platform-developer

Thanks @inductor .
/lgtm

/approve


fix typo

Type of change:

[ ] Bugfix
[ ] New feature provided
[ ] Improve performance
[ ] Backport patches
[x] Documentation
[ ] Refactor
[ ] Chore
[ ] CI/CD or Tests

What this PR does / why we need it:

Pre-submission checklist:

[ ] Did you explain what problem does this PR solve? Or what new features have been added?
[ ] Have you added corresponding test cases?
[ ] Have you modified the corresponding document?
[ ] Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

Codecov Report

Merging #1790 (9b78f4d) into master (3a8fdf6) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 9b78f4d differs from pull request most recent head 792d9c0. Consider uploading reports for the commit 792d9c0 to get more accurate results

@@           Coverage Diff           @@
##           master    #1790   +/-   ##
=======================================
  Coverage   39.30%   39.30%
=======================================
  Files          91       91
  Lines        8073     8073
=======================================
  Hits         3173     3173
  Misses       4494     4494
  Partials      406      406

Impacted Files
Coverage Δ

pkg/apisix/cluster.go
28.14% <ø> (ø)

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


New version: Google.AndroidStudio version 2<IP_ADDRESS>

Checklist for Pull Requests

[X] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.6 schema?

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

Will pass validation after index publish of:

#183429

Microsoft Reviewers: Open in CodeFlow

Once #183429 has published, then this PR should be run again.


Feature request: support update pipeline only

There can be a shift of schema during analysis, which only requires a new pipeline setting (i.e., a new _targets.R file.

This can be done by checking whether "config.yml" file exists. If so, skip updating "config.yml".


Suggesting Delete -feature

I'd like to suggest adding a delete button to delete the uploaded project.
It would be helpful if the user added a wrong project link/repo.

We are done transitioning the project to react . We will be working on the implementation of the delete and editing  feature see issue #65 .


cards seem to have a lot of extra space in the header?

Is this amount of space expected in the design, or is there a way to tighten this up?

perhaps there are extra fields, eg subtitle that will always take up space?
markup is as below:
      <Card
        initiallyExpanded={true}
        >
        <CardHeader
          title={this.data.topicName}
          actAsExpander={true}
          showExpandableButton={true}
        />
        <CardText
          expandable={true}
          initiallyExpanded={true}
        >
        <form>
          <TextField
            defaultValue={this.data.topicData.inherits}
            floatingLabelText="inherits" />

            <RaisedButton secondary={true} label='save' />

          </form>
        </CardText>
      </Card>

I also tried adding a subtitle and using CardTitle instead of CardHeader
there's a big dead area created under the subtitle. HR added for clarity in next block

      <Card
        initiallyExpanded={true}
        >
        <CardTitle
          title={this.data.topicName}
          subtitle={this.data.topic.lesson}
          actAsExpander={true}
          showExpandableButton={true}
        />
        <CardText
          expandable={true}
          initiallyExpanded={true}
        >

...

Hmmm I'm not experiencing this issue. We have to investigate. a PR would also be welcome :grin:

I have the same problem and hope someone can get it fixed. Thanks.

I am also wondering if there is a way to increase the fond size of title in CardHeader.

@stevehu Thanks!

Not able to reproduce this in the docs.
closing this for now. If its still an issue for the OP, kindly comment below int he  post.


list_orders: history of past orders [feature request]

Thank you for the great collection of methods. To complement it, it would be useful to add api.list_orders() - get the history of past orders.

Great idea! I will make sure to add it!

So you are now able to call
cira.list_orders()

This will return a list of all open orders.
This will be with all default arguments.

@smjure I'm glad you like the lib and thank you for the feature request!
You should be aware that I am planning to redesign the library but I have forked cira with this older style. I won't start the redesign until cira-classic is up and working. So if you are using it a lot it all that needs to be done is to change
import cira_classic as cira # or something like that


Request for option to hide chart header and toolbar

Pretty much what the title says, we want to be able to turn off the header, either by css or typescript

Hi @brian-patrick-3, my use case is to show the chart without the header for a widget in Enterprise Marketplace, like the mock attached, since its it widget and we are using our own header, there isn't enough space and need for the header

Hi, if you're referring to the actual Console Widget itself, right now this is not a Shidoka component. It is being planned in the future releases for Shidoka to supply components like the Widget for the dashboard. Is this widget showing up on Console? If yes, please bring this up with the Console team<EMAIL_ADDRESS>or<EMAIL_ADDRESS>I can tell you if you are bringing this widget over to Console though, you will not be able to do what you're asking for as I wrote those guidelines myself.

This is what they want to hide, for clarification:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Strange "reject" error

I'm getting a error "TypeError: Cannot read property 'reject' of undefined":
  File "/app/releases/20150624035113/node_modules/rethinkdbdash/lib/connection.js", line 170, in Connection._processResponse
    if (typeof self.metadata[token].reject === 'function') {
  File "/app/releases/20150624035113/node_modules/rethinkdbdash/lib/connection.js", line 129, in Socket.<anonymous>
    self._processResponse(response, token);
  File "events.js", line 77, in emitOne
  File "events.js", line 166, in Socket.emit
  File "_stream_readable.js", line 145, in readableAddChunk
  File "_stream_readable.js", line 109, in Socket.Readable.push
  File "net.js", line 509, in TCP.onread

What the query that trigger this error?
A readable stream? Is it on a table? Or on a changefeed?

It is on a table, I'm gonna find out what query triggered the error

@thelinuxlich -- did you close a cursor while fetching data from it maybe?

Ok, I found a case when this could happen.
If you have a cursor on a query, and call cursor.stop since the protocol v0_4 we will send a STOP query. At that time we have to outgoing request.
In your stacktrace, we are getting a CLIENT_ERROR. My guess is that the cursor returned a CLIENT_ERROR for the CONTINUE query, we then deleted the metadata, and we get a second time a CLIENT_ERROR for the STOP query - and at that time we get your error.
It should be fixed in 2.0.15.
Feel free to reopen if it happens again :)

I will update, but I wasn't using cursors either


Increase table editor window size in the Web app

Could the table editor window (Options > Manage Custom Generators) in the Web app be bigger? Perhaps the window could be dynamically scaled to use maybe 90 % of the available screen estate - in my vertically positioned monitor the current layout is not quite optimal. :)
Currently the window only shows about 2 lines of the table at a time. Sometimes it would be good to test minor changes directly in the browser, but the small window makes this quite inconvenient.

Will be resolved with the new UI on which we are working currently .

Good to know! And the window sizing is already now better than it originally was.


kyma-system namespace not found in API Rule Creation

Description

Go to API Rules
Create new API Rule
In Gateway section, namespace "kyma-system" is markdown as red
When clicked to namespace dropdown, kyma-system is not found
If not clicked on dropdown, API Rule creation is still allowed, endpoint works with no issues.

Hello,
I couldn't reproduce the issue.


Add consumer parameter types

Reference: deltaDAO/ocean.js#1
While working on bringing ConsumerParameters to Ocean Market, we learned that the required types are currently missing from ocean.js.
Proposed Changes
Add required types as documented in Ocean Protocol DDO Docs

Add new ConsumerParameter interface
Add consumerParameters to the MetadataAlgorithm interface
Add consumerParameters to the Service interface

Additional Information
While publishing we noticed that current validation schemas in aquarius only support string types for all properties other than required.
The proposed types of the PR are therefore considering this behaviour.
It could make sense to either

update aqua shapes (if behaviour from docs is preferred)
or note how to handle other types (e.g., we currently JSON.stringify the default value and optional options object in our implementation that's coming for market during publish / edit and parse for display in UI)

lgtm, waiting for github to recover


Connector distance

Hello,
Out of curiosity, why are the 100 pin connectors in the footprint 33.92mm apart instead of 34mm? I don't think it's a "real" issue, but why did you do it?
All the best,
Lasse

Hi Lasse
Your are right. The connector distance is 33.92mm. This is a mistake it the PCB library. Thanks for pointing out this issue.


View blinks when popping view controller on UINavigationController

First of all, sorry for my bad English.
I'm using Motion on my project in UINavigationController, view blinks with black color when pushing/pop view controller repeatedly after 10 times.
First 10 times of translation is OK and no glitches, but it blinks weirdly by repeating popping vieewcontroller a few times after.
Additional: And some subview blinks when pushing view controller after pushing 10 times.
I just enabled isMotionEnabled property on my UINavController and UIViewController.
Here is my view controller code for setup Motion:
self.isMotionEnabled = true
self.navigationController?.motionNavigationTransitionType = .autoReverse(presenting: .fade)
current.motionIdentifier = "ppj-header-progress"
I tried to remove motionNavigationTransitionType but same result.
Update: This issuse is caused on iPhone X, iOS 11.1.1
Update 2: My code works perfectly and not happening any issue on iPhone 4s, iOS 9
Update 3: Not happening black blink issue on iPhone 5s, iOS 11 but some subviews translates weirdly (e.g. blinking layer shadows) when pushing/popping view.

Nice find. Can you send over the sample project you are using so I can easily reproduce this? As well, is this only happening in the simulator?

I attached sample project archive. You can see screen is blink weirdly after pushing viewcontrollers a few times after, also you can see blinking navigation bar on the top when pushing vc every time.
I added some views (like UIImageView) in my sample and it also blinking weirdly.
I tested on my real device of iPhone X, iPhone 4s and iPhone 5s, not simulator.
Simulator works fine and no glitches on my iPhone X simulator.
sample.zip

Thank you! I am going to test this today.

Looking at this now. Thank you!

Please give Motion 1.3.0 a try. If the issue persists, please reopen it. Thank you!


Add send_event and friends to WorldCell

Objective
Copy send_event and friends from World to WorldCell.
Clean up bevy_winit using WorldCell::send_event.
Changelog
Added send_event, send_event_default, and send_event_batch to WorldCell.

Slowly untangling that code is very nice, thank you.

bors r+


Launch Meltano in the DigitalOcean Marketplace

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/926
Originally created by @dmor on 2019-08-27 18:25:43

DigitalOcean is a cloud hosting provider with a one-click app marketplace where users can install software to a pre-configured virtual machine (called a "Droplet") and get started using that software in less than 60 seconds. We would love to offer Meltano users this smooth adoption experience, and this issue details the steps required to do so.
Opportunity Assessment:
https://docs.google.com/document/d/1IzRmOgkREXVcZ1R7TpkUcscg9dd96OThFeR_UfjO2eQ/edit#
Product Management

[x]  @dmor complete Vendor application https://marketplace.digitalocean.com/vendors
[x]  @dmor review marketplace terms and conditions https://www.digitalocean.com/legal/marketplace-vendor-terms/
[ ]  @dmor find out if we need to have GitLab legal review of the vendor terms
[x]  @dmor read Getting started as a Marketplace Vendor
[x]  @dmor upon approval, complete form for first listing
[x]  @dmor come up with a list of keywords we want to be sure to including in the listing for marketplace SEO purposes
[x]  @dmor upon approval, join the DigitalOcean Developer Forum (they will send a link with the approval email)

Technical Implementation

[x]  review guidelines and scripts provided by DigitalOcean
[x]  review DigitalOcean's Getting Started with Marketplace Images documentation to familiarize with image requirements, configuration recommendations, how to run commands on first boot and first login, and details on exactly what DigitalOcean's helper scripts do.

Create First Marketplace Image

[x]  @dmor [#927] Document how to create a Droplet and install Meltano as a tutorial on our website (why wait?! let's iterate and get DigitalOcean in user's hands)
[x]  @dmor Create and configure a build Droplet manually first to make sure the configuration works
[x]  @dmor handoff technical implementation to @mbergeron to speed things up
[x]  @mbergeron Review the image configuration documentation to determine what can be pre-built, what scripts we will need to run once, and what scripts we will want to run every time the user launches their one-click app
[x]  @mbergeron [#938] Clean up and validate the build Droplet with the provided scripts, cleanup.sh and img_check.sh. The scripts will check for and fix potential security concerns and verify that the image will be compatible with Marketplace.
[x]  @mbergeron [#939] Take a snapshot of the build Droplet after you power it down, then test the resulting image. While there are several ways to create an image, we recommend snapshots as the most simple and consistent option.
[x]  @mbergeron [#940] Automate your build for replicable and configurable processes with minimal additional effort. We provide some Fabric and Packer templates to get you started.
[x]  @mbergeron Submit your final image to the Marketplace team for review.

Marketing Launch

[x]  @dmor update Meltano docs with instructions for using the one-click installer
[x]  @dmor create speedrun video using the Digital Ocean one-click image
[x]  @dmor create walkthrough video using Digital Ocean one-click image (for the docs page)
[x]  @dmor add promotion bar with CTA for DigitalOcean Marketplace on Meltano.com homepage
[x]  @dmor update the Meltano.com website with a branded create button that is a call-to-action to install Meltano (see more details in the guide for how to form the links)
[x]  @dmor draft blog post announcing our 1-click app is now available in the DigitalOcean marketplace
[X]  @dmor include in the v1 Meltano announcement email

View 62 previous comments from the original issue on GitLab


adding more existing dependencies

Thanks for providing this PR.  I've decided to move all python3 package dependencies into another file, 'requirements.txt'.  So this PR is no longer needed.


Pull variables from type.script

How to directly pull variables from type.script
now i use  this.apiReques call_service to pull three variables:
type: 'call_service',
service: 'turn_on',
domain: 'script',
service_data: { entity_id: "script.common_timer", variables:{"duration":"00:10","entity_id":"switch.mp1_mp11","operation":"switch.toggle"} }

I'm adding support for that in https://github.com/resoai/TileBoard/pull/417
Feel free to try early as I haven't.


Incorrect result is reported for Siamese architectures

It looks like every parameter is counted twice. Is there a way to report correct results for Siamese and Triplet models?

https://github.com/sksq96/pytorch-summary/pull/71

I am also facing the same issue in a siamese network!


Install fails

I followed the doc to install the operator:
    kubectl create namespace netchecks
    kubectl apply -f https://github.com/hardbyte/netchecks/raw/main/operator/manifests/deploy.yaml
    kubectl wait Deployment -n netchecks -l app.kubernetes.io/instance=netchecks-operator --for condition=Available --timeout=90s

While netchecks-operator-ui starts fine, the netchecks-operator-policy-reporter pod fails starting:
2023/11/21 08:42:28 [INFO] UI configured
2023/11/21 08:42:28 [INFO] REST api enabled
2023/11/21 08:42:28 [INFO] metrics enabled
W1121 08:42:28.125071       1 reflector.go:424] pkg/mod/k8s.io/client-go@v0.25.4/tools/cache/reflector.go:169: failed to list *v1alpha2.ClusterPolicyReport: the server could not find the requested resource (get clusterpolicyreports.wgpolicyk8s.io)
W1121 08:42:28.125071       1 reflector.go:424] pkg/mod/k8s.io/client-go@v0.25.4/tools/cache/reflector.go:169: failed to list *v1alpha2.PolicyReport: the server could not find the requested resource (get policyreports.wgpolicyk8s.io)
W1121 08:42:29.412807       1 reflector.go:424] pkg/mod/k8s.io/client-

Is there an additionnal requirement no mentioned in the doc ?

it sounds like the policy-repoerter is not optional.
I had an issue getting it installed but that resolved the issue for the netchecks-operator-policy-reporter.


Sync keyword list

This commit syncs keywords from
github.com/facebook/reason/blob/master/src/reason-parser/reason_lexer.mll.
Additionally,
github.com/reasonml-editor/vscode-reasonml/blob/master/src/syntaxes/basis.ts
is consulted whether a keyword should be removed or not.

Thanks!


Add a script to populate the db

Currently after starting the container and running rd-admin init, the db is empty.
There should be a script to easily populate the db, able to quickly:

create a few users with different permissions (a Coordinator, a Developer, and a regular user)
create a few issues with a few messages each
create a specific number of users/issues/messages/etc with specific parameters
perhaps import an issue from bpo

This script might also be exploited by the tests.

#7 addresses the first point.
I think this might be enough, since creating new users from rd-admin is easy.  Issues and messages are also easy to create from rd-admin and/or from the tracker (once it's initialized and has a few issues), so implementing the points 2-3 might be unnecessary.
I now think that implementing 4 is a good idea that can also replace 2-3, but should be developed as a separate script.


Don't format things on top of each other

Not looking for any smart formatting based on relationships, but defaulting to everything just being centred and on top of each other makes me sad 🥲
Love the app though, great work ❤

Glad to hear you enjoy it!
I have been wanting a "smart spread" of sorts that spreads out the nodes based on relations, need to see if I can find any examples of it out in the wild though since I have no idea how that'd work out atm. I suppose I could add a simple fully-random spread in the interim just so it doesn't have everything stuffed on top of each other for now, better that nothing I guess 😛

@Ovyerus first of all great work on the tool, I love it!
I've been working with Prisma for some time also on a larger project - it's great to have an option to visualise it but it's hard to do without spread of the models. I went ahead and added the spread using elkjs (by clicking the new control icon in the bottom). I've also added a few additional features for managing larger schema:

having large enums expandable
option to navigate to the relation on field name click
farther zoom out

It's still not a final feature (not covering all the cases and without tests etc) - I wanted first to catch up with you if that's something you'd like to include in prismaliser.
You can find the repo at https://github.com/MariannaKrzewinska/prismaliser
Let me know what you think!

@MariannaKrzewinska yeah that all sounds great! Definitely would love to make managing large schemas easier to work with. 👍

+1 for this.
Great tool but this would make it awesome!
As an example dbdiagram has an 'auto arrange' feature which does this very well.
https://dbdiagram.io/

Finally got the spread button pushed to production, sorry for the huge delay. Will try get position saving done as soon as I can.


flexget history - Could not start manager due to unicode.

Expected behaviour:
To be able to pipe "flexget history -s" into the TAIL command or into file. Such as..
flexget history -s | tail -n 10
or
flexget history -s > /tmp/flex-history.txt
Actual behaviour:
flexget history -s | tail -n 10
Could not start manager: 'ascii' codec can't encode character u'\xed' in position 3601: ordinal not in range(128)
Steps to reproduce:
A unicode character must be present in a history log to cause breakage. Example: í (u'\xed'), http://www.codetable.net/hex/ed.
Additional information:

FlexGet version: 2.10.48-1
Python version: 3.6.3
Installation method: AUR
Using daemon (yes/no): no
OS and version: Manjaro, 17.1pre3

Same thing happens for flexget series list all.  This is a frequent regression- it repeatedly breaks on various subcommands ,then gets fixed, then breaks again. I got sick of waiting for a proper fix, and just alias flexget to "LC_ALL='en_US.utf8' flexget" which works around the bug.

@rollor thanks for the workaround.

This is a bit annoying issue with python, depending on where stdout is going default encoding changes ...


classes for a few tooltips

hello and congratulations on a wonderful plugin, i really love it.
I was curious, is it possible to set a class just for one tooltip?
when i use your example it changes it for all the tooltips. Am i doing something wrong?

Thank you for your kind words, it makes it worth investing time in making these pieces of code.
And yes, you can customize all of the tooltips.
After installing the base javascript and included css, if you want custom classes, you can add it up super easily.
I made an example for you: https://codepen.io/hekigan/pen/oebpPm

Dear sir, you are a prince, thank you very much!!

Laurent, do you freelance or mentor at all? I would love some one on one time to answer many questions no one can answer for me. I'm willing to pay of course.

Glad I could be of help.
For this kind of inquiry please use the mail displayed on my profile.
It was not there before, I just added it for convenience.


KRActivityIndicatorView

Throwing 2 errors after update.
animation.fillmode = .forwards & animation.timingFunction = CAMediaTimingFunction(name: .linear)

@cmhu9985
What is the Swift version?
The latest version of KRProgressHUD (and KRActivityIndicatorView) can only be used in Swift 4.2.

no response


Update CHANGELOG.md

Fix release notes for version 1.4.0:

Correct link to PR
Fix minor typo

Thanks for the patch!
Could you recommit with your sign for DCO?

This change looks being already merged into master in https://github.com/fluent/fluentd/commit/56a8a824f6575ed51fb5a52fa691610ca885a848.
Thank you for your contribution 👍


[RFC][DNM] Settings stream codec

This patch reworks routines used to store and read the settings data.
Provide stream-style encoding and decoding to/from flash, so the the
API only requires a pointer to binary data, and the settings
implementation takes care of encoding/decoding to/from base64 and
writing/reading to/from flash on the fly. This would eliminate the
need of a separate base64 value buffer on the application-side, thereby
further contributing to the stack footprint reduction.
Above changes allows to remove:
256-byte value length limitation.
removing enum settings_type usage so all settings data are treated
now as a byte array (i.e. what's previously SETTINGS_BYTES)
Introduced routine settings_val_read_cb for read and decode the
settings data from storage inside h_set handler implementations.
h_set settings handler now provide persistent value's context
used along with read routine instead of immediately value.

Above changes so far applied only to fcb-back-end. They will be escalated to nffs-back-end once
its shape will be accepted.
Any new back-end need to implement two I/O handlers:
``int (*read_cb)(void *ctx, off_t off, char *buf, size_t *len),
int (*write_cb)(void *ctx, off_t off, char const *buf, size_t len)```
and register it using f. settings_line_io_init.
Above handler need only to provide RAW access to the back-end storage.
The Introduced codec take ceare about I/O access alignment.

remove Remove the tgt parameter to the export callback
The tgt parameter is unneeded and only complicates the API.
Signed-off-by: Andrzej Puzdrowski<EMAIL_ADDRESS>

For sure the code still need some clean-up - so pleas comment on general conception and so one (no coding standard session for now).

Codecov Report

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

@@           Coverage Diff           @@
##           master    #9521   +/-   ##
=======================================
  Coverage   52.19%   52.19%
=======================================
  Files         215      215
  Lines       26010    26010
  Branches     5594     5594
=======================================
  Hits        13576    13576
  Misses      10175    10175
  Partials     2259     2259

Continue to review full report at Codecov.

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

@jhedberg @Laczen @carlescufi @lemrey Pleas review in yours convenience.

Hi @nvlsianpu, sorry I did not respond any faster. I am tied up in other work. This is a great improvement to the settings module.
Maybe there is still an opening for a big simplification of the settings module. As I mentioned before the encoding could be removed. The encoding was imo needed for:

Storing binary information as string, when also other information (string, int, ...) was stored as string. If you now only have byte char storage this requirement has been removed.
Sending information over serial line (export to serial monitor). As this target has been removed encoding is also not required anymore.
Storing binary information in a ascii file with line ends. This is only required for nffs (I am not sure it is really required in this case). This requirement remains.

In fcb you could just store the items as "variable_name=" concatenated with the binary data. As you know the total length of an item in fcb getting the length of the binary data is the difference between the length and the location of the first "=". No need for encoding or streamed encoding. The advantage is of course the reduction in data size and the simplicity.
For nffs it might also be possible to do something like this (I have never used nffs). In the worst case nffs would still require encoding but the settings module would be a lot simpler for fcb.

@Laczen Thanks for comments - I received similar comments off-channel from my colleges. I  will differentiate algorithm between FCB and FS.
Idea of this patch is to satisfy points 1,2,4,6 of #7413 .

Sending information over serial line (export to serial monitor). As this target has been removed encoding is also not required anymore.

Hi @nvlsianpu, what I meant by serial monitor was newt_mgr. The implementation in mynewt has the possibility to export to newt_mgr, this would require encoding to be able to do this.

@Laczen Sure - the idea is not to keep things like in the MyNewt it used to be. So zephyr-mcumgr-go-app will suport this (remote provisioning) in the appropriate shape.

/recheck

recheck

cc @vikrant8051 this PR contains mesh example settings code rework
cc @Qbicz settings implamentation and API was changed, please consider it for your future works, any review welcome.
@jhedberg @Vudentz (at last on of you  both) Please review.
@Laczen @lemrey @sjanc @carlescufi  Please review in your convenience.

@nvlsianpu Thanks for making changes in onoff_level_lighting_vnd_app. It looks now more intuitive.

Generally I very much like the way the code looks after this. Do you have any figures how much we save in call stack usage? Also, how much testing (if any) have you done for the Bluetooth settings with this PR?

@jhedberg
I didn't check how much stack this saves (probably will try when have a chance).
I tested this PR roughly with the bluetooth/peripheral sample, I check  especially bounding and CCC functionality.
If you can perform or recommend me some testing suite pleas do.

@jhedberg  updated

@jhedberg I hope I solved all problems you had found.

@rakons could you please re-review?


 Learn more about stacking.

Join @Maddiaa0 and the rest of your teammates on  Graphite

Benchmark results
Metrics with a significant change:

protocol_circuit_witness_generation_time_in_ms (private-kernel-tail): 3,393 (+20%)
protocol_circuit_witness_generation_time_in_ms (base-parity): 872 (-51%)
protocol_circuit_witness_generation_time_in_ms (root-parity): 65.2 (+32%)
protocol_circuit_proving_time_in_ms (private-kernel-tail-to-public): 102,152 (+17%)
protocol_circuit_proving_time_in_ms (base-rollup): 79,035 (+21%)
protocol_circuit_proving_time_in_ms (root-parity): 39,902 (+16%)
protocol_circuit_proving_time_in_ms (public-kernel-setup): 43,844 (+16%)
protocol_circuit_proving_time_in_ms (public-kernel-app-logic): 46,389 (+19%)
protocol_circuit_proving_time_in_ms (public-kernel-teardown): 45,221 (+16%)
protocol_circuit_proving_time_in_ms (root-rollup): 23,208 (+18%)
pxe_database_size_in_bytes (3): 9,242 (+19%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,730 (-1%)
1,551 (-1%)
707 (-1%)
755 (-3%)
769 (-1%)

proof_construction_time_sha256_30_ms
11,885 (-1%)
3,137 (-1%)
1,403
1,444
1,471

proof_construction_time_sha256_100_ms
43,886 (-1%)
12,063 (-1%)
5,654
5,579 (+1%)
5,506

proof_construction_time_poseidon_hash_ms
78.0 (-1%)
34.0
34.0
57.0
88.0 (+1%)

proof_construction_time_poseidon_hash_30_ms
1,516 (-1%)
415 (-1%)
200
226 (-1%)
270

proof_construction_time_poseidon_hash_100_ms
5,739 (-1%)
1,579 (-2%)
721 (-1%)
815 (+3%)
798

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs

l1_rollup_calldata_size_in_bytes
1,412
1,412

l1_rollup_calldata_gas
9,452
9,454

l1_rollup_execution_gas
607,988
607,990

l2_block_processing_time_in_ms
691 (-1%)
1,292

l2_block_building_time_in_ms
22,544 (+1%)
46,011 (+1%)

l2_block_rollup_simulation_time_in_ms
22,418 (+1%)
45,658 (+1%)

l2_block_public_tx_process_time_in_ms
19,259 (+1%)
42,259 (+1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
5,927
8,531

node_database_size_in_bytes
9,474,128
12,783,696

pxe_database_size_in_bytes
:warning: 9,242 (+19%)
15,127

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.4
16.9 (-1%)
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.7
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.604
0.517 (-1%)
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.7
76.2
133
247
474
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
288
543
1,055
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.497
0.469
0.456
0.448
0.442
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
58.5
113 (+1%)
184
351
628
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
107
208
355
686
1,263
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.504 (-1%)
0.505
0.488
0.480
0.471
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
58.8

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
101

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.549

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
79,470
665,267

Transaction size based on fee payment method
| Metric |  |
| - |  |


[FR]: ord, chr, hex

What is the current behavior?
The canonical starlark implementation does not have these methods.
Describe the feature
Implementing the Python functions ord, chr, hex. At the moment, I don't see a way to do this code-points (ord) without a lookup table; but it's certainly possible. url_encode and url_decode could also be neat; e.g.   becomes %20.

Related, I think: https://github.com/bazelbuild/starlark/issues/112

% bazel run src/main/java/net/starlark/java/cmd:starlark
>> ord
<stdin>:1:1: name 'ord' is not defined
>> hash('a')
97
>> hash('/')
47
% python3 -c "print(ord('a'), ord('/'))"
97 47

fixed by #425


Update output-viewer.md

Fix link to Python Based Visualizations page.

@googlebot I signed it!

/assign @joeliedtke

/ok-to-test

/approve
Thanks for fixing this link, @hirokinko!

Thanks!


Fix Model & Start Pose Mode Error Blender 2.82a

Using Blender 2.82a Tested with both CATS 0.17.0 and 0.14.1-dev with same result.
I have a MMD model that I had saved from when I used Blender 2.79.
When using Fix Model or Start Pose mode, I get a error.
I only get these errors when using CATS in Blender 2.82a, when opening the same file in Blender 2.79 both options work fine.
Fix Model Error:
Traceback (most recent call last):
  File "C:\Users\Eldar\AppData\Roaming\Blender Foundation\Blender\2.82\scripts\addons\cats-blender-plugin-master\tools\armature.py", line 446, in execute
    bpy.ops.pose.rot_clear()
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\modules\bpy\ops.py", line 201, in __call__
    ret = op_call(self.idname_py(), None, kw)
RuntimeError: Operator bpy.ops.pose.rot_clear.poll() failed, context is incorrect

location: <unknown location>:-1

Start Pose Error:
Traceback (most recent call last):
  File "C:\Users\Eldar\AppData\Roaming\Blender Foundation\Blender\2.82\scripts\addons\cats-blender-plugin-master\tools\armature_manual.py", line 82, in execute
    bpy.ops.pose.rot_clear()
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\modules\bpy\ops.py", line 201, in __call__
    ret = op_call(self.idname_py(), None, kw)
RuntimeError: Operator bpy.ops.pose.rot_clear.poll() failed, context is incorrect

location: <unknown location>:-1

Could you send me that blend file in which this error occurs? It would allow me to replicate that error which makes it easier to fix.

Blake_Bomber_Jacket6.zip

Works fine for me on the dev version of cats now, give it another try.


execution lag in python console of Spyder environment using windows 7 x64 Anaconda

This issue seems very similar to the one discussed in issues #1611 and #1714.
i am running a dell with windows 7 AMD64
Anaconda   2.2.0
Python        3.4.3
matplotlib    1.4.3
pandas        0.15.2
statsmodels 0.6.1
numpy         1.9.2
I am mostly running code from cells in the console.  some cells seem to case some amount of lag in execution and I end up having to hit return a few times to see results. as the session progresses I gets progressively worse.  It seems like the lag adds up as a problem cell is run more times.  after a while it can get to having to hit return well over 20 times to see a graph or get a result summary printed to the console.  This looks a lot like the issue(s) mentioned above. I have tried updating anaconda using their method from the FAQ section on the Continuum Analytics website.
I seem to mostly have problems in cells that have plotting commands mostly matplotlib.pyplot
other major modules i have imported when this occurs are pandas statsmodels  and numpy
I'm sorry if this is a repeat of a previous issue ... the ones above are the only ones i could find.
thanks,
Robbie

This seems more related to issue #1831.

Thanks for the update, good luck in finding any solutions. I will follow along in the #1831 thread for future news.

Ok, closing this one then.

that is fine
Cheers
Robert (Robbie) McMurry
Assistant Development Engineer, Western Cooling Efficiency Center
Minister, Davis Bike Collective (Bike Forth)
<EMAIL_ADDRESS>mobile:<PHONE_NUMBER>
On Wed, Apr 8, 2015 at 1:49 PM, Carlos Cordoba<EMAIL_ADDRESS>wrote:

Ok, closing this one then.
—
Reply to this email directly or view it on GitHub
https://github.com/spyder-ide/spyder/issues/2304#issuecomment-91032972.


fix: l2-to-l1 messaging

Pull Request type

Bugfix

What is the current behavior?
Receipt is produced wrong
What is the new behavior?
We need to do the same thing for both events and l2-to-l1 messages: iterate recursively into the callinfos.
We already had a function to do that for events, but it looked kind of ugly - so I replaced it with the recursive iterator that blockifier provides. I moved events to use that too.

this should effectively solve l2>l1 messaging @shamsasari

As I mentioned offline, this PR unfortunately doesn't make the Kakarot TestL2ToL1Messages test pass. This could be an issue with the test itself though, since it waits for a custom MessageHashesAddedFromL2 event to be emitted. I had a look at Katana, which is what Kakarot is using for their tests, and it seems to have code which emits this custom event.
I'm not sure what to make of this. Is this behaviour somehow expected of a Starknet node?

this should effectively solve l2>l1 messaging @shamsasari

As I mentioned offline, this PR unfortunately doesn't make the Kakarot TestL2ToL1Messages test pass. This could be an issue with the test itself though, since it waits for a custom MessageHashesAddedFromL2 event to be emitted. I had a look at Katana, which is what Kakarot is using for their tests, and it seems to have code which emits this custom event.
I'm not sure what to make of this. Is this behaviour somehow expected of a Starknet node?

The TestL2ToL1Messages event, do you mean it's a l1 core contract event or an event in L2?

TestL2ToL1Messages is the name of the kkt test class. In it it waits for MessageHashesAddedFromL2 events to be emitted from L2. Obviously Madara isn't emitting these, but Katana does!! Nor is this an event from the Starknet Core contract from what I can tell. I may be wrong and missing something here, but to me this looks like a poorly designed kkt test.

TestL2ToL1Messages is the name of the kkt test class. In it it waits for MessageHashesAddedFromL2 events to be emitted from L2. Obviously Madara isn't emitting these, but Katana does!! Nor is this an event from the Starknet Core contract from what I can tell. I may be wrong and missing something here, but to me this looks like a poorly designed kkt test.

oh right that's an event produced by the core contract in L1.
Madara doesnt deploy L1 test core contract yet, it's expected to be deployed by the madara bootstrapper. I think we should do something similar to katana and actually deploy it in devnet mode.
i believe that we should change kakarot to have it listen to https://github.com/starkware-libs/cairo-lang/blob/a86e92bfde9c171c0856d7b46580c66e004922f3/src/starkware/starknet/solidity/StarknetMessaging.sol#L142 that event instead, and ou solidity test core contract (that would be deployed on l1 at startup when running madara in devnet mode) would produce this event instead.
I'm not sure I understand their motivation for their MessageHashesAddedFromL2 event, they talk about it above the function you linked but i don't see the difference with the official ConsumedMessageToL1 that i just linked?

Yeah that makes more sense.

Sorry, I forgot to ask, where is this L1 test core contract defined? If you say to listen to ConsumedMessageToL1 events instead then why need anything from this test contract?

i'll explain it again
the l1 core contract is a solidity contract, which is not in madara
I am talking about this core contract https://etherscan.io/address/0xc662c410c0ecf747543f5ba90660f6abebd9c8c4 here is the one for the starknet mainnet chain, this is an ethereum contract on eth mainnet.
the core contract address is specified in the chain_config, and differs for each starknet chain
as of now, the only interaction we have with the l1 core contract is that we watch it in mc-eth for state updates (in full node mode) and l1 to l2 messages and message cancellations for sequencing mode.
we do not publish anything to the core contract, as this is the responsability of the madara-orchestrator - but in a real chain we should publish the SNOS proof (to another contract called gps statement verifier actually, but it's linked to the state update that is later published on the core contract), the state update as blob, and this is where the l2-to-l1 messages are consumed
for devnet mode, we probably want to deploy a fake core contract to L1, and have this publish to core contract thing in the sequencer instead of the bootstrapper
I kind of don't want the madara node to have this logic for production, as it would mean we need to have private keys to an ethereum wallet inside the madara node - and I really dont want that, i think it's way safer if it's the orchestrator who has it
also, if we were to manage the core contract in the madara node, this would mean that everything that orchestrator is doing (running SHARP, making the pie, publishing DA etc) would be in the madara node and that goes against the model we were thinking of with karnot
this means that right now, there is nothing that consumed the produced blocks in l2 by the madara node and updates the core contract
i'd like to have that logic in for devnet only in madara node, and even deploy that core contract
this would work very similarly to what katana is doing, which is deploying a core contract that does not require any stark proof, it's just a dumb contract for devnet that actually doesnt secure anything
the MessageHashesAddedFromL2 is an event that is produced on L1, the file you linked is a solidity file, not cairo. it's an L1 core contract event.


Datepicker show out of the page

Bug, feature request, or proposal:
Datepicker open out of page when page don't have space at bottom
What is the expected behavior?
Datepicker open at top of container if bottom don't have space
What is the current behavior?
Datepicker open out of the page
What are the steps to reproduce?
You can use Angular material 2 docs. datepicker docs
Resize page and open datapicker
img

Duplicate of #4406


Tests broken (maybe openrpc changed?)

A test regarding openrpc fails (see https://github.com/pymeasure/pyleco/actions/runs/10473269206):
__________________ Test_discover_method.test_fail[RPCServer1] __________________

self = <test_rpc_server.Test_discover_method object at 0x7f83c6102040>
methods = [{'examples': [{'params': [{'name': 'arg', 'value': None}], 'result': {'value': {}}}], 'name': 'sem', 'params': [{'nam...ue, 'schema': {'title': 'Arg1', 'type': 'number'}}], 'result': {'name': 'result', 'schema': {'title': 'Result'}}, ...}]

    def test_fail(self, methods: list):
        m = methods[2]
        assert m["name"] == "fail"
>       assert m["description"] == fail.__doc__
E       KeyError: 'description'

tests/json_utils/test_rpc_server.py:167: KeyError

It only happens on Python >=3.9, suggesting, that it has to do with openrpc package (see #90 ).

In fact, openrpc changed treating a docstring as description to making summary be the first line of the docstring and the multi line description enters description.


MacOS compatibility

Is it compatible with MacOS? I use BIgSur (11.4) and I always get the error
browsermobproxy.exceptions.ProxyServerError: Can't connect to Browsermob-Proxy.

Yes, it is. I have a Mac OS myself :)


Gopass git setup

Summary
Tl;dr git behavior in the initial setup
Steps To Reproduce

gopass uses the 3rd Mail of my GPG-key for commits
Expected behavior

It uses the primary mail or just applys my global git config
Environment

OS: Arch Linux
OS version: Linux pioneer 4.18.16-arch1-1-ARCH #1 SMP PREEMPT Sat Oct 20 22:06:45 UTC 2018 x86_64 GNU/Linux
gopass Version: gopass 1.8.2 (2018-08-03 20:31:47) go1.10.3 linux amd64
Installation method: https://aur.archlinux.org/packages/gopass-git/

Additional context

chris@pioneer ~ » gopass recipients
gopass
├── MyStore (/home/chris/.password-store-MyStore)
│   └── 0xA3AA55C37A759E7C - Christian Heusel<EMAIL_ADDRESS>└── 0xA3AA55C37A759E7C - Christian Heusel<EMAIL_ADDRESS>
chris@pioneer ~ » gpg --list-keys Christian
uid           [ultimate] Christian Heusel<EMAIL_ADDRESS>uid           [ultimate] Christian Heusel<EMAIL_ADDRESS>uid           [ultimate] Christian Heusel<EMAIL_ADDRESS>

I agree that we should default to the global git config if there is one. Should be easy to detect.
However if there is none, I'm not sure if we can select the "first" sub id. Afaik they are unordered, or aren't they?

Well in all the searches they appear sorted by the date of creation, but I think you are right that there is no "real" order ... :smiley:

The golang.org/x/crypto/openpgp package provides a map[string]*Identity which is unordered.
The on-disk keyring is probably stored in order of creation, but this isn't available through this interface.

But wouldnt it make sense to ask the user which one he wants to use if multiple identities are provided? :)
Thanks for all the input tho :+1:

Using the global git config if it exists is definitely we should do.
Also we may ask the user to select an identity. If someone wants to do it, go ahead.

Hey @dominikschulz, I just want to say thank you! ❤  I really really appreciate that you took the time to make this work and the countless hours of work you put into gopass in general! 😃

Thanks a lot. Our users feedback is very important to me. So any kind of feedback absolutely helps to drive this project forward.
Please give the feature a try once you get a chance to and report back if anything doesn't work as expected.


A single step to bridge BOBA tokens between different L2s

Ideally, we can connect all smart contracts so that users only need to click one button on Boba Eth L2 and their BOBA will appear on Bobabeam.
This process simplifies the user experience and makes it easier for users to move assets between different chains.

Problems:

Users need to provide liquidities for the fast exit pools and we need a way to rebalance them
It's hard to estimate the cost, but it's doable.
We only support BOBA tokens. All other tokens have to be swapped to BOBA.

amazing! what do you think about these alternatives?

direct LPs between Boba Eth L2 <> Boba Alt L2
i) enforced by Lz Messaging with multiple LP providers
LP providers take the risk of providing funds for the swap, if the LP is automated, this is higher risk though - and has the same assumptions as the Fast exit pool - assumes L2 validity because of a single sequencer, probably not an option
ii) enforced by centralized control (non-automated) by a single LP provider (custodian)
centralized actor has his own validator or is connected to a validator off-chain, and decides whether to relay the message (probably longer waiting period)- direct LPs could be cheaper than going the usual way through L1

We connect contracts through the route touching ethereum
If we use fast-bridge or Liquidity pools - the validity assumptions present in the first option would still hold, with the standard bridge its better (I think we can still do the automation), but bridging between L2s would take 7 days. Not sure if its complicated the other way (from Boba alt L2 to Boba Eth L2) and if we have fast bridges for this route


New: Add svls for verilog and systemverilog support

Here is another try to include svls. I simply added the Lua file.

I didn't find many resources for the macOS issue, only this link:
https://support.circleci.com/hc/en-us/articles/360043542933--Error-The-brew-link-step-did-not-complete-successfully-When-Installing-Python
Maybe the recommendations he provides may solve the issue:
brew unlink python@2

I pushed force my master branch fix an issue with svls server. Now it's working like a charm:

Thanks to accept this PR :)

Can you add the cargo installation instructions? I would copy the format from something like rust-analyzer in this repo

Can you add the cargo installation instructions? I would copy the format from something like rust-analyzer in this repo

Hello,
do you think this pull request could be merged ?

Yes, if you address my comment about adding installation instructions :)


Add randomization mode suitable for js numbers

See #1030
Add another randomization mode to create additional test cases which are more friendly to js consumption.

Imho defining a lower maximum is not the correct way to test support for edge-cases. If it's 64 bits, you should test for 64 1s. Wrapping the number in quotes is doable, but technically it's perfect valid yaml. Oh javascript...
Anyone else problems with yaml parses? Should we quote them?

This PR is mostly for the lols.
I know its valid yaml, its just practically not favorable with our current tooling
(defacto standard yaml parsing library not compliant w the yaml spec == sad javascript :clown_face: )
We can/do parse arbitrary length strings into numbers, no problem.
We could also do our own pre-processing on the yaml files and wrap numbers in quotes ourselves, but ofc it would be preferable to have something nice out of the box.


Issue 1304 - Use default EMR properties in functional tests

Make sure you have checked all steps below.
Issue

[x] My PR addresses the following issues and references them in the PR title. For example, "Issue 1234 - My Sleeper
PR"

Resolves https://github.com/gchq/sleeper/issues/1304

Tests

[x] My PR adds the following tests OR does not need testing for this extremely good reason:

Reran EmrPersistentBulkImportIT

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it, or I have linked to a
separate issue for that below.
[x] If I have added, removed, or updated any external dependencies used in the project, I have updated the
NOTICES file to reflect this.

Closing, issue being fixed in #1311


pynmrstar installation issues

in a fresh install, (pip install pynmrstar==3.3.2) I get the error message below when importing pynmrstar
Any idea what could be the cause?
Thanks - Eiso
Python 3.11.10 | packaged by conda-forge | (main, Oct 16 2024, 01:27:36) [GCC 13.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pynmrstar
Traceback (most recent call last):
  File "/software/miniforge3/envs/shine/lib/python3.11/site-packages/pynmrstar/__init__.py", line 15, in <module>
    import cnmrstar
ModuleNotFoundError: No module named 'cnmrstar'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/software/miniforge3/envs/shine/lib/python3.11/site-packages/pynmrstar/__init__.py", line 18, in <module>
    import pynmrstar.cnmrstar as cnmrstar
ModuleNotFoundError: No module named 'pynmrstar.cnmrstar'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/software/miniforge3/envs/shine/lib/python3.11/site-packages/pynmrstar/__init__.py", line 23, in <module>
    raise ImportError('Could not import cnmrstar sub-module! Your installation appears to be broken.')
ImportError: Could not import cnmrstar sub-module! Your installation appears to be broken.

Hello - I can reproduce the issue, but I can also confirm that it is resolved in version 3.3.3 and above. As I can't change the existing published 3.3.2 package, please update to version 3.3.3 or 3.3.4. The change log is available here:
https://pynmrstar.readthedocs.io/en/latest/release-notes.html#id1
Best,
Jon


fix: typo in Data Factory CI/CD docs

Replace on with in

Docs Build status updates of commit f74406c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/data-factory/continuous-integration-delivery.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@nabhishek
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks for your submission to help us improve the ADF docs!  I merged this change now.  #please-close


Type-Ahead and "remember last X" searches

#109
This is a feature for saving the last X searches in memory. The previous unique values typed in(up to the max specified in prefs) will be available via type-ahead suggestion or pulldown from the specific input box. Right now selecting a previous value just fills out the individual field, however it is possible to perform a more robust action on select. This is what I have done specifically in just the name field, when selecting a previously searched for name from the name drop-down, the name AND any other parameters present when that search was performed are auto-filled. This was only implemented in the name field because it would open up a lot of complexity checking which values should be filled over other ones etc but I think it is worth further discussion about the right way to handle this.
The arch pattern being used is abstract collection (Folio) of abstract items(FolioItem). Doing this feature this sprint allowed me to sketch out how to approach the more feature rich implementation expected for ad-hoc saving of searches/results/graphs/entities commonly referred to as the "Folio" feature.
new models/classes:

SzFolioItem
SzFolio
SzSearchParamsFolioItem extends SzFolioItem
SzSearchParamsFolio extends SzFolio
SzSearchHistoryFolioItem extends SzSearchParamsFolioItem
SzSearchHistoryFolio extends SzSearchParamsFolio

new services:

SzFoliosService

new events:

SzSearchService.parametersChanged
SzSearchService.resultsChanged
SzSearchService.searchPerformed

Issue number: #109


Add Matched Environment Variable Option

This solution not only breaks linting, it also does not feel right. Putting this PR up as a draft until I can think of a better way to make options work more fashionably.
The only way this solution works is by doing:
bundle exec ec diff foobazz-production foobazz-staging --matches --all

I think this brings up a good point re: default behavior.

What should we show by default (all/matches/differences)
What should the CLI commands look like for swapping the other

I think the most intuitive CLI behavior might be to show all by default, and then have booleans for --matches-only and --diff-only.
My first pass of showing differences only, then refactoring to add an --all flag didn't involve much thought but upon reflection I think the above might make more sense. Even though I want to use diff by default most of the time, there are other ways we can configure that (via an actual .config file for example)
Thoughts?

I think this brings up a good point re: default behavior.

What should we show by default (all/matches/differences)
What should the CLI commands look like for swapping the other

I think the most intuitive CLI behavior might be to show all by default, and then have booleans for --matches-only and --diff-only.
My first pass of showing differences only, then refactoring to add an --all flag didn't involve much thought but upon reflection I think the above might make more sense. Even though I want to use diff by default most of the time, there are other ways we can configure that (via an actual .config file for example)
Thoughts?

Ya, it's a bit tough to think about what would make the most sense as a default. Given we add --diff-only & --matches-only then --all as the default seems to make the most sense.


readpixel less than -1

Describe the bug

readpixel is less than -1
Operating system: (please complete the following information)

OS: win-64
Version: Windows 10

Can you reproduce this issue?

I saw the solution #419 , and found the reason, thank you


dev: Update naive timestamps with UTC timezones

Current Behavior
Currently, we store timestamps without any timezone information. This is a bad practice as it could lead to wrong interpretations at later stages.
Expected Behavior

The timestamps in our databases should have TZ info
The rust code should fetch timestamps as DateTime instead of NaiveDateTime

Changes reverted in

pragma-monitoring: https://github.com/astraly-labs/pragma-monitoring/commit/fab52331b4f13bdab47fa16c0e6c9a2be5a5fd99
pragma-node: https://github.com/astraly-labs/pragma-node/commit/f1171bd13d375faabae116f532a5ed58ae5f97e0

Those caused new entries to not be published & we had TimeSinceLastUpdateTooHigh alerts (causing WrongPrice alerts later).
Labels:
 - alertname = TimeSinceLastUpdateTooHigh
 - group = API
  - job = prometheus_monitoring
 - network = Testnet
 - pair = BTC/USD
 - severity = warning
Annotations:
 - description = The time since the last update for BTC/USD has exceeded 1800 seconds.
 - summary = Time since the last update is too high
Labels:
 - alertname = TimeSinceLastUpdateTooHigh
 - group = API
 - job = prometheus_monitoring
 - network = Testnet
 - pair = DAI/USD
 - severity = warning
Annotations:
 - description = The time since the last update for DAI/USD has exceeded 1800 seconds.
 - summary = Time since the last update is too high
Labels:
 - alertname = TimeSinceLastUpdateTooHigh
 - group = API
 - job = prometheus_monitoring
 - network = Testnet
 - pair = ETH/USD
 - severity = warning
Annotations:
 - description = The time since the last update for ETH/USD has exceeded 1800 seconds.
 - summary = Time since the last update is too high
Labels:
 - alertname = TimeSinceLastUpdateTooHigh
 - group = API
 - job = prometheus_monitoring
 - network = Testnet
 - pair = USDC/USD
 - severity = warning
Annotations:
 - description = The time since the last update for USDC/USD has exceeded 1800 seconds.
 - summary = Time since the last update is too high
Labels:
 - alertname = TimeSinceLastUpdateTooHigh
 - group = API
 - job = prometheus_monitoring
 - network = Testnet
 - pair = USDT/USD
 - severity = warning
Annotations:
 - description = The time since the last update for USDT/USD has exceeded 1800 seconds.
 - summary = Time since the last update is too high
Labels:
 - alertname = SourceDeviation
 - job = prometheus_monitoring
 - network = Testnet
 - pair = BTC/USD
 - severity = warning
 - source = BINANCE
 - type = future
Annotations:
 - description = The source deviation of BTC/USD from BINANCE has exceeded 2%.
 - summary = Source deviation is too high
Labels:
 - alertname = WrongPrice
 - job = prometheus_monitoring
 - network = Testnet
 - pair = BTC/USD
 - severity = warning
 - source = BINANCE
 - type = future
Annotations:
 - description = The price deviation of BTC/USD from BINANCE has exceeded 2.5%.
 - summary = Price deviation is too high

We reverted those changes and now everything works correctly.


Update request: gitea 1.22.2 → 1.22.3

Package name: gitea
Latest released version: 1.22.3 (GitHub release, compare to v1.22.2)

Current version on the unstable channel: 1.22.2
Current version on the stable/release channel: 1.21.11

[x] Checked the nixpkgs pull requests

Notify maintainers
@ma27 @techknowlogick @SuperSandro2000

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

It would be appreciated if you could open a PR right away :)

@SuperSandro2000 Apologies, that was my intent as soon as I arrived to my personal laptop, just wanted to ensure it got tracked (as it contains a security fix).

(just saw you've added the security + backport labels, appreciated :) )