Promise.resolve() is not a function error angular 4

I am using this library as
import Relational from 'relational-pouch';
PouchDB.plugin(Relational);
Its showing Promise.resolve() is not a function console error.
Please help.

To get around this problem I commented out line 3 in lib/pouch-utils.js
'use strict';

//var Promise = require('pouchdb-promise'); <-- commented out
/* istanbul ignore next */
exports.once = function (fun) {

Not sure what the actual problem is, though.

Same problem with angular 4 and ionic 2. @MrPutuLips comment helps, but it's not a good idea to comment out script :)

Think found where exactly issue is.
Here is used CommonJs require https://github.com/pouchdb-community/relational-pouch/blob/master/lib/pouch-utils.js#L3
And  'pouchdb-promise'  which is required written with ES6 and exported as default.
So proper syntax will be
not

but

I saw there is https://github.com/59naga/babel-plugin-add-module-exports but can't setup it so it could help here.
Any ideas?

This might be a silly question but can't we just rely on native promises now ?
https://github.com/pouchdb-community/relational-pouch/blob/master/lib/pouch-utils.js#L3 ( just removing this line fixes everything up for me )
If you don't have promise support in your target build in 2018 then chances are that you are already polyfilling them earlier in your build step ?

The only solution is changing relational-pouch/lib/pouch-utils.js line 3: var Promise = require('pouchdb-promise');
to this: var Promise = require('pouchdb-promise').default;
????
Thanks!

Yes.... Still now not found other solution....
On 30 April 2018 at 08:34, luca147<EMAIL_ADDRESS>wrote:

The only solution is changing relational-pouch/lib/pouch-utils.js line 3:
var Promise = require('pouchdb-promise');
to this: var Promise = require('pouchdb-promise').default;
????
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pouchdb-community/relational-pouch/issues/86#issuecomment-385305488,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOLoZ2Jm43keyF4WVezvhq2fPUcdYjwAks5ttn9WgaJpZM4PQGGP
.

--
Thanks,
Prabuganesan

: ( very bad....
how can we work with this solution, so that all the members of the team can have that change without needing to modify it each one of them???

Well i decided i will not use this plugin, it have lot of bugs, i think use only pouch is more efficient.
Thanks

@luca147 You will need to create a fork of this repo and modify it yourself to have the change like what @rwein did in his fork: https://github.com/rwein/relational-pouch/commit/6b525a3ca3eea891a4a12c3b195e7c730be67e80
Then install the package using the github repo.
Or simply use the fork I pointed out in the link above.
This way you and all your team members should have the change.

@509dave16 thx man, I decided not to use the plugin, as I told you in the other thread.. thx a lot

I made a webpack alias to the browser version file. Like this:
alias: {
      'pouchdb-promise': path.join(__dirname, '../node_modules/pouchdb-promise/lib/index.js')
    },

@liquid36 good solution!! What it's great, no need to fork or make changes to the source code! Thx!

@liquid36 where do you put that alias?

Here!
It's depends on your webpack configurations.

@liquid36 where do you put that alias?

Hi guy I know it's a bit late but I have just faced the issue and base on https://github.com/pouchdb-community/relational-pouch/issues/86#issuecomment-400101873. This is how I have managed:
I am using create-react-app
I have installed react-app-rewired react-app-rewire-aliases in order to be able to modify it. check the docs for more info:
yarn add react-app-rewired react-app-rewire-aliases -D
but basicaly this is the code to put in config-overrides.js in your root folder
const rewireAliases = require("react-app-rewire-aliases");
const path = require("path");

module.exports = function override(config, env) {
  config = rewireAliases.aliasesOptions({
    "pouchdb-promise": path.join(
      __dirname,
      "/node_modules/pouchdb-promise/lib/index.js"
    )
  })(config, env);

  return config;
};

@liquid36 where do you put that alias?

Hi guy I know it's a bit late but I have just faced the issue and base on #86 (comment). This is how I have managed:
I am using create-react-app
I have installed react-app-rewired react-app-rewire-aliases in order to be able to modify it. check the docs for more info:
yarn add react-app-rewired react-app-rewire-aliases -D
but basicaly this is the code to put in config-overrides.js in your root folder
const rewireAliases = require("react-app-rewire-aliases");
const path = require("path");

module.exports = function override(config, env) {
  config = rewireAliases.aliasesOptions({
    "pouchdb-promise": path.join(
      __dirname,
      "/node_modules/pouchdb-promise/lib/index.js"
    )
  })(config, env);

  return config;
};

this works for me . if you use customize-cra , config-overrides.js might like this :

const {
    override,
   ...,
    addWebpackAlias
  } = require("customize-cra");

const path = require("path");

  module.exports = {
    webpack: override(
        addWebpackAlias({"pouchdb-promise": path.join(
          __dirname,
          "/node_modules/pouchdb-promise/lib/index.js"
        )})
    )
  };

Here's a workround:
    const utils = require('relational-pouch/lib/pouch-utils.js');
    utils.Promise = window.Promise;
    PouchDB.plugin(require('relational-pouch'));

You can manully change the default Promise object before PouchDB plugin it.
This is because angular uses ZoneAwarePromise as the default Promise.
Normally, it will work fine. But in some unknown (just I don't know) reasons, ZoneAwarePromise become a module with a default property who wraps the real ZoneAwarePromise Object.


Added save_image_macos to specify path on MacOS

Added save_image_macos() to specify path on MacOS

Worked on it together on a different branch.


Geometric StateSpace does not support native OMPL space functions

OMPL checks if the statespace is one of the native spaces and sets them up accordingly. Calls such as copyToReals() do not work with GeometricStateSpace when passed to OMPL planners which might internally use these functions on the statespace.

Are there any specific functions for ompl calls that doesnt support the geometricstatespace values as input ?? that are supposed to be implemented as I see there is a seperate cpp file specifically on geometricstatespaces for function calls from ompl.


Software NGFW Hub Phase 2

[x] Autoscaling example for centralized design
[x] Autoscaling example for isolated design
[x] Panorama standalone example
[x] #297
[x] Remove tgw_inbound_with_alb_nlb, transit_gateway_peering, vmseries_combined_with_gwlb_natgw, vpc_endpoint examples

All examples were delivered in #327 and #333


Maybe I  can help

Can we work together? maybe I can write some easy python code for you to finish the repo as soon as possible………………

Most of codes has been completed

Looking forward to enjoy your repo~


Lockdown version of nan

Fixes the error I was experiencing in #7 . The 2.0 release of nan contains different methods which breaks pdf-fill-form.

+1
Experiencing the same issue and this PR fixed it for me. Please merge.

Can you updated the npm release?

done (1.0.3)


Basis set contraction coefficients

Before performing benchmark calculations I wanted to be sure the basis was consistent.
The exponents and contraction coefficients in the data file cc-pvdz.dat are exactly what I expect.
For a given molecule, the exponents
mol.bas_exp()

return exactly the values I expect.
However,
mol.bas_ctr_coeff()

returns many values that are close, but not those in the data file, and others that are not at all close.
Silly question: is this correct or should it be? I just want to be sure before performing benchmark calculations.

My assumption is that PySCF normalizes the contraction coefficients, and converts them to match the unnormalized primitives: basis sets are conventionally reported in terms of normalized primitive functions, while integrals are typically computed in terms of unnormalized primitives. The difference between these is just the normalization factor; however, due to finite precision and truncation of the contraction coefficients in usual basis sets, there can be another effect from renormalizing the contracted functions.


tests: TestDockerVolumeSemantics: more tests with symlinks

I tried to reproduce the issue mentioned in:
https://github.com/coreos/rkt/pull/2290#issuecomment-206003364
However, the tests pass fine for me. Nevertheless, this test is worth
adding.

TestDockerVolumeSemantics was added in https://github.com/coreos/rkt/pull/2315
/cc @iaguis @sjpotter

LGTM


Switching MetaMorpheus and mzLib from AppVeyor/Jenkins to GitHub Actions?

I've recently switched Spritz and TopDownSDK over from using AppVeyor to using GitHub Actions for continuous builds and periodic testing, and I'm finding it to be pretty great in comparison.
Here are Spritz's build and release scripts (more like MM with uploading to a GitHub release), and here are topdownsdk build and release scripts (more like mzLib with a nuget push).
Is there any interest in switching MM and mzLib over to GitHub Actions? One advantage of switching mzLib and MetaMorpheus over to GitHub Actions would be that the scripts for these builds would be contained in the repositories themselves, rather than on AppVeyor and Jenkins on separate services or machines. They can then also be updated with pull requests if needed based on the changes (e.g. https://github.com/smith-chem-wisc/MetaMorpheus/pull/2060). The builds seem to be a bit quicker than AppVeyor, too.
The checks/builds can then be viewed on the main page by pressing the green check or red X on the latest-commit line of GitHub, and they can be used as gates for PRs in the same way as AppVeyor. Here's that view within Spritz, for example:

Here's a draft of the actions that AppVeyor is doing: https://github.com/smith-chem-wisc/MetaMorpheus/pull/2128/files.

that's pretty cool. it kinda does a jenkins sort of thing.

Yep! And it'll be version controlled and all in one place.

just fyi i tried to use github actions, and abandoned it because it did not share secrets across forks. so if you've forked MM, and you have an API token saved as a secret on the upstream repo, your fork will not be able to access that API token secret. this is deliberate, for security reasons (you could fork someone's repo and print out their secrets, for example). I went back to appveyor because it's self-contained and no one is able to access secrets stored on appveyor via forking.

These are great notes. What issues did you run into with token usage on other forks? Personally, I find these to be more features than bugs:

The release workflows require tokens to place the installer and commandline zip file into a Github release, and this is only useful for the main fork where the release is located.
AppVeyor used codecov tokens, but these are not required for open source projects
Tokens for deploying docker images and nuget packages should be located only on the main fork, where the packages and images are released from and tagged
Pull requests to the main branch can activate token usage on the main branch if needed

I forget the specifics but I think it was about deploying a docker image. IIRC I tried to deploy a docker image to dockerhub on PR merge or something like that, with my docker username and password as secrets. but github actions wouldn't deploy it because it didn't have access to my secrets

I’ve had success automatically deploying Docker images to Docker Hub from Github Actions for Spritz using tokens created under Settings -> Access Tokens in Docker Hub. I wonder why you had issues with accessing the secrets.

I sort of remember it better now...

make PR to upstream from my fork
something went wrong in the GH actions script that I wanted to fix
Fix the script
could not get my PR to run the updated script instead of the original script
create a .sh script that basically just does what appveyor does, use GH actions to just download and run the .sh script
could not access secrets in the .sh script to deploy to github
get annoyed with GH actions and quit


[QUESTION] Raise exception in python-fastApi middleware

I am trying to validate token in fastapi middleware but this seems impossible. As i am thinking middleware needs to make next call although its not required. I am not able to find any good solution to handle token in one go in this python-fastapi backend. Any help is appreciated.
@app.middleware("http")
async def add_middleware_here(request: Request, call_next):
    token = request.headers["Authorization"]
    try:
        verification_of_token = verify_token(token)
        if verification_of_token:
            response = await call_next(request)
            return response
    except InvalidSignatureError as er:
        raise HTTPException(status_code=401)

My expectation is that it should throw 401 error once wrong token is provided.
Instead it throws 500 with below Exception traceback:
Traceback (most recent call last):
  File "c:\users\covered\appdata\local\programs\python\python38\lib\site-packages\uvicorn\protocols\http\h11_impl.py", line 385, in run_asgi
    result = await app(self.scope, self.receive, self.send)
  File "c:\users\covered\appdata\local\programs\python\python38\lib\site-packages\uvicorn\middleware\proxy_headers.py", line 45, in __call__
    return await self.app(scope, receive, send)
  File "c:\users\covered\appdata\local\programs\python\python38\lib\site-packages\fastapi\applications.py", line 140, in __call__
    await super().__call__(scope, receive, send)
  File "c:\users\covered\appdata\local\programs\python\python38\lib\site-packages\starlette\applications.py", line 134, in __call__
    await self.error_middleware(scope, receive, send)
  File "c:\users\covered\appdata\local\programs\python\python38\lib\site-packages\starlette\middleware\errors.py", line 178, in __call__
    raise exc from None
  File "c:\users\covered\appdata\local\programs\python\python38\lib\site-packages\starlette\middleware\errors.py", line 156, in __call__
    await self.app(scope, receive, _send)
  File "c:\users\covered\appdata\local\programs\python\python38\lib\site-packages\starlette\middleware\base.py", line 26, in __call__
    await response(scope, receive, send)
TypeError: 'NoneType' object is not callable

What kind of behavior do you expect when if verification_of_token: is elsed? Seems like you must raise HTTPException(status_code=401) then.
Also there is also option to use https://fastapi.tiangolo.com/tutorial/dependencies/

What kind of behavior do you expect when if verification_of_token: is elsed? Seems like you must raise HTTPException(status_code=401) then.
Also there is also option to use https://fastapi.tiangolo.com/tutorial/dependencies/

Actually verification_of_token can be true or false depending on token's validity. I am trying to check token here itself before it goes any further. Also InvalidSignatureError error comes up when token is invalid. Now problem is: this always fails the backend here by going in 500 interval server error other than going in 401 unauthorized error. I want to throw 201 error.

I have updated the above problem with exception traceback

I have updated the above problem with exception traceback

According to middleware docs you must either return response or call_next func. Seems like your middleware is not properly throwing a InvalidSignatureError and if block being ignored. So you return None from your middleware which causes exception

So how should i then check validity of token now?

I'd go for something likes. Not sure how's your verify_token func looks like. But it's how to you how you make it) It doesn't seems like FastAPI issue)

def verify_token(token):
       if check_token(token):
           return True
       else:
           return False

@app.middleware("http")
async def add_middleware_here(request: Request, call_next):
    token = request.headers["Authorization"]
    if verify_token(token):
        response = await call_next(request)
        return response
    else:
        raise HTTPException(status_code=401)

I'd go for something likes. Not sure how's your verify_token func looks like. But it's how to you how you make it) It doesn't seems like FastAPI issue)

def verify_token(token):
       if check_token(token):
           return True
       else:
           return False

@app.middleware("http")
async def add_middleware_here(request: Request, call_next):
    token = request.headers["Authorization"]
    if verify_token(token):
        response = await call_next(request)
        return response
    else:
        raise HTTPException(status_code=401)

This totally sounds reasonable but i have already performed this thing and it throws same error as above.

Well, just to be clear I didn’t tested code above. It was just a graft. Also may be that’s because you are raising exception instead of returning Response object. Give it a few tries. Also take a look at Dependency based authorization it looks sexy

hey @priyankagupta34 I just came across the same issue, seems weirdly HTTPException doesn't work in middle ware. See https://github.com/tiangolo/fastapi/issues/1125

the comment in there has the solution tho
return Response(content="", status_code=401)
but I agree this is unclear  would be good to know if this should be in the documentation or if it's a bug @tiangolo and others think should be addressed.   Something like bubbling up if the caught below exception is already of type HTTPException.

This is an intended. So the thing you should do is to return a Response with right status code and message.
See #458

It might not be a bug but you might be able to classify it as an anti-feature 😆. I'd still be super interested in having the option to use the exception middleware for this... It would allow for much more consistency in the processes.
Having a request not being able to authenticate is an exception in my eyes, therefore these requests should trigger the flows that we have built for errors (via middleware). It'd be a shame if we cannot use that in combination with authentication middleware. Just silently returning a 401 code would break our monitoring systems.


[feature request] support suffix other than .js or .jsx

Hi
Thanks for creating this brilliant tool.
Our project is trying to use this tool, however we want to apply it to a script language defined by our own. It's syntax is a subset of JavaScript so the tool works well on the texts. The only problem is that we are using a suffix defined by ourself.
Is it possible to let JsInspect accept an argument to include certain type of files?
Thanks

.mjs is the file extension for native ESM, which is supported in Node.js v13.2+. Even adding it to the hardcoded list of extensions prior to making the list configurable would be great.

you can do jsinspect some_path/**/*.random_file_extension


Release for scala 2.13

Now that scala 2.13 is out, would it be possible to make a new release for 2.13?

Yes, sure, I'll try to make one this week.

I had a quick look and it seems like we need to wait until the play dependencies are available for 2.13.

Hi @edgarmueller, can you take a look again? As far as I can tell, they are available now.

Yes, they are, thanks for letting me know! I'll try to update this week.

I've released a new version with support for Scala 2.13 as 0.9.5.


Proposal for logging infrastructure in Entitas

Motivation:
There are two main reasons why one would consider introducing logging in a game.

Finding and fixing bugs
Gathering data for analytic purposes

Logging for Bug finding and fixing
It is fairly easy to unit test a system and therefore write robust code which transforms state in a expected manner. This however doesn't mean that one will not run into bugs. There are always a possibility for a behaviour which we do not expect. The unknown unknowns. For this type of situations it is crucial to have a logging infrastructure which can provide us with context and historical development of the state which lead to the bug. It helps us to understand and reproduce unexpected behaviours.
Gathering User Data
There are multiple reasons for gathering user data:

Understanding how many people play your game and how often
Understanding which parts of the game logic are executed
Analyse User input

This data than can be used for refining game design decisions, UI decisions and even for a creation of interactive agents and NPCs.
Hoover this kind of logic is very game specific and can already be achieved with smart use of reactive systems.
Therefore this proposal will concentrate on the Logging for Bug finding and fixing starting from here.
General Context
In order to analyse the logging data every logging statement has to be provided with context.
Time and order related context

Time (time stamp), it is the local time of device running the game. It reflects the time when the logging statement was created.
Current tick. As Entitas systems are executed on every tick. This can be considered as an additional information to time. Giving us an FPS agnostic view on execution.
Log Statement Index. This provides an additional information if we chose to select a time stamp format which is not fine granular enough. (e.g. multiple log statement have the same time stamp)

Time seems to be the important data point for this context. Two other data points can be seen as optional.
Identification context

GameId. This can be a static id for the game but it could also contain the game version and device information, because a game compiled for a different platform is technically not the same game.
UserId. Can be left blank or set to placeholder value if you want to protect the privacy of your users. However it can be helpful for contacting a user who happened to get all this bugs and crashes.
SessionId. If you have a logical concept of a game session.

Entitas specific events
I see two types of events which can help developers in finding and fixing Bugs

State Events:

Entity Created
Entity Destroyed
Component Added
Component Removed
Component Replaced
Pool Cleared

Logical events

Initialise System Executed
System Executed
Reactive SubSystem Executed
Event Listener executed (On Entity or on Group)
System crashed

This events also need context which is Entitas specific:
Entitas state context

Pool Type. Reflects pool the pool which manages the entities which were involved in state events and event listener / reactive sub system execution
Pool instance ID. We could potentially have multiple instances of the same pool type. In this case logging the instance id would be very helpful.
Entity Creation Index. Gives us a possibility to aggregate all changes happening to an entity during it's life cycle.
Entity instance ID. As an entity is pooled and reincarnated after destruction. This gives us a possibility for spotting bugs happening because of bad memory management. (Usage of Retain Release methods)

For component related events it would be nice to see the data the component was storing.
Something like:

PositionComponent x:45, y:13 was added
PositionComponent x:45, y:13 was replaced with x:45, y:12
Position component x:45, y:12 was removed

This would be hard to achieve automatically because a component can store any kind of data. Therefore I suggest to introduce a ILoggableInterface:
interface ILoggable {
   public string LogString {get;}
}

Which when implemented by a component class will lead to a more verbose log statement.
Examples of Log Statements:
2015-12-26T09:56:21Z game1 user1 session1 CorePool 34526 45673 1 e_created
2015-12-26T09:56:21Z game1 user1 session1 CorePool 34526 45673 1 c_added PositionComponent(5,4)
2015-12-26T09:56:21Z game1 user1 session1 CorePool 34526 45673 1 c_replaced PositionComponent(5,4) PositionComponent(5,5)
2015-12-26T09:56:21Z game1 user1 session1 CorePool 34526 45673 1 e_destroyed

Which can be decode as following
Time | GameId | UserId | SessionID | PoolType | PoolInstanceID | EntityInstanceID | EntityCreationIndex | EventName | ComponentRelatedData

Now by searching for game1 user1 session1 CorePool 34526 45673 1 we can find out the whole history of entity with creation index 1.
By excluding the creation index game1 user1 session1 CorePool 34526 45673 we can see how and when this entity instance was reused during the whole session1.
Logging BackEnd infrastructure
Logging all the events that I have described in Entitas specific events means that every instance of the game will generate a massive amount of data. This is why I would suggest using such high level logging only during development and maybe internal beta releases. However even for this controlled scenarios we would need to have a Log receiving part which can handle so much data.
Without trying it out my self, I would suggest to use Papertrail and see how much load it can handle. Papertrail provides a nice infrastructure for storing and querying Log statements.

This would be awesome! What's the procedure on getting it in? I think I could help with it :)

I am not sure yet :)
First just wanted to see how much interest there is for such a feature.
Let's meditate on it for a couple more days and than flesh out a plan.

It sounds pretty interesting. Would it be possible to also see which system did the action?

This is what I meant by Logical events.
Combined with state events you would see something like
2015-12-26T09:56:21Z game1 user1 session1 InitSystem1 startExecution
2015-12-26T09:56:21Z game1 user1 session1 CorePool 34526 45673 1 e_created
2015-12-26T09:56:21Z game1 user1 session1 CorePool 34526 45673 1 c_added PositionComponent(5,4)
2015-12-26T09:56:21Z game1 user1 session1 InitSystem1 finishExecution
2015-12-26T09:56:21Z game1 user1 session1 SystemA startExecution
2015-12-26T09:56:21Z game1 user1 session1 CorePool 34526 45673 1 c_replaced PositionComponent(5,4) PositionComponent(5,5)
2015-12-26T09:56:21Z game1 user1 session1 SystemA finishExecution

This might get chatty, but I think it worth a try.
We can also adjust the log levels.

Ah, ok, was looking at the examples. Then I'm all for it as I've been wishing for a way to see what systems use what components (in an easier way than searching around in the code).

Hello,
I was just wondering what the benefits of having a logging system integrated with Entitas are. If you just provide the events and contexts then we are free to choose our own logging framework.  I have previously used nlog and log4net

That was actually what I planned to do.
Figuring out all the hooks and maybe providing a few classes, which will make it easy to use those.

An integrated logging system could also make sense to use it as a foundation for visualization tools. A consistent logging output across projects could enable visualizing behaviour over time (e.g creating, changing and removing entities) which might help find some bugs.

It might help finding some bugs but as @mzaks said it would be useful only in dev state. The log output  would be insane. If done I would like to see it as kind of plugin that is not built in to framework.
I agree with @SvDvorak  checking for system-component dependencies is troublesome. Similar thing to Artemis-odb Component-Dependency-Matrix could resolve that issue quite nicely.

@kicholen I agree. It should be very easy to deactivate the logging. In the future I can imagine that we can build all kinds of visualization tools etc based on this data

One of the major problems with Unity development is there is no standard easy to extend logging interface. There have been attempts to replace the built in logger with something better but nothing that the entire community is using.
I think whatever solution you guys come up with needs to be easily extendable / modifiable to use 3rd party loggers.

Yes, I don't plan to add a logging framework (I already did one, it's open source NLog)
I plan to provide sth to plug into with any logging tool you like

@mzaks what's the state with this?

@sschmid Can add it to the new Plugins structure. Schools I clone develop or wait until the release and make PR on master?

Might be safer to wait for the next release. PR on develop please (default branch)
Does it require changes in entitas? or is it a Plugin?

It is a Plugin. Sending the system will/did execute event schools be figured out though. But it will still be a Plugin

It's been a while :) I saw a working prototype ages ago. Shall finalize this? Whats the state with the web UI?


The answer is [#4558] Add grpc transport an's Page and answer session an'spage

@anspage 😒- Add grpc modules are you looking
@tru64ufs #4726
@denzels #4724
@pinetree408 #4003 @denzels

get back [__](url)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Scrapland Remastered - Crash on New Game

Describe the bug

On attempting to start a new game, the game attempts to load the first level (Orbital Station), then crashes with an error.
Remix ver.: DXVK 65dab8b Debug-Optimized, Bridge 5aa73bc Debug-Optimized
GPU: Nvidia Geforce RTX 3080
Driver: Nvidia Studio 536.67
Version: GOG

Attach files!

ScraplandRTXSaves.zip

Extract the contents to User<user>\Documents\MercurySteam\Scrapland\

gameconf.zip

Includes conf files to place inside the Scrapland Remastered folder. (just the base folder, not Bin)

crashlogs.zip

A zip including the game logs and Remix log up until the point of crashing.

Installation instructions (to be replaced with link to repo):

Install game from GOG

Steam will work as well but that version has anti-debug protection in place.

Place the contents of gameconf.zip inside Scrapland Remastered
Place the contents of ScraplandRTXSaves.zip inside Documents/MercurySteam/Scrapland (Create if it doesn't exist)

If using the Steam version, run the game at least once then replace the contents of the subfolder with an ID string for a name
Verify that Scrap.cfg is read-only

Rename the "Video" folder
Install DXVK and Bridge Remix to Scrapland Remastered/bin
Open game (Bin/Scrap.exe) using a new shortcut with the launch arguments  -console -debug:10 -enginedebuglevel:10

When using the debug console shortcut all game info will be dumped to log.html and logAI.html.

To Reproduce
Steps to reproduce the behavior:

Open Scrap.exe with the debug arguments mentioned above
Click on "Single Player," then "New Game" and pick any difficulty
Allow the game to load briefly
Observe crash message

Expected behavior

The game should complete loading and with Video renamed, the game should immediately cut to gameplay with the player on Orbital Station.

Error
Actual Level at :  Levels/Orbit
No PythonExecute
Python script subsystem initialized.
ProgressBarCount: 922 (1070)
Level loaded in 5.52 seconds

FATAL ERROR: Check failed!

Expression: vp8.Width

Compiled file info:
File: 'F:\GOG Games\Scrapland Remastered\Bin\Scrap.exe'
Date: Nov 24 2021  15:24:13

Source code info:
File: 'Engine\render.cpp'
Date: Wed Nov 24 14:55:12 2021
Line: 783

@anchorlightforge Hello. Could you please see if these issues will repro with the Release build?

Confirming that this bug still occurs with Release.  The following is a set of logs from the New Game crash tested on the release binaries for 0.3.0.
Release030NewGameCrash.zip

REMIX-2287 for tracking.

Hi @anchorlightforge , I noticed a fix I made might impact this issue. Can you please try to reproduce this issue using https://github.com/NVIDIAGameWorks/bridge-remix/actions/runs/8903349558 or more recent?

@nv-ajaus I tested Bridge Remix build 68 with the GOG version and was able to change resolutions and start a new game successfully.  In other words, you got it.  Thank you!


docs: Update asciidocs to reflect latest changes

Description
Updates the .adoc files to reflect the recent changes in the markdown files
Types of Changes

[x] Documentation

Thanks for the review @nrichers! Sorry for breaking the build 🙈 😅


[FEATURE] Add option to override default apiUrl and authHeader

🚀 Feature request
Is your feature request related to a problem?
Hi all, thanks for maintaining this lib!
We use today self-hosted Glitchtip, and we are considering migrating from @sentry/browser to micro-sentry on the frontend. However, we noticed that you follow a very specific apiUrl structure and have a pre-defined authHeader, so that custom DSNs won't match this pattern and will fail.
Describe the solution you'd like
Add option to override the default apiUrl and authHeader.
This would also be beneficial for people using tunnel.
Thanks!
Additional context
Here is the snippet I refer to:
  constructor(options: SentryClientOptions) {
    if (options && options.dsn) {
      const searched = DSN_REGEXP.exec(options.dsn);
      const dsn = searched ? searched.slice(1) : [];
      const pathWithProjectId = dsn[5].split('/');
      const path = pathWithProjectId.slice(0, -1).join('/');

      this.apiUrl =
        dsn[0] +
        '://' +
        dsn[3] +
        (dsn[4] ? ':' + dsn[4] : '') +
        (path ? '/' + path : '') +
        '/api/' +
        pathWithProjectId.pop() +
        '/store/';

      this.authHeader =
        'Sentry sentry_version=7,sentry_key=' +
        dsn[1] +
        (dsn[2] ? ',sentry_secret=' + dsn[2] : '');
    }

Source: https://github.com/taiga-family/micro-sentry/blob/main/libs/core/src/lib/service/micro-sentry-client.ts

Hi!
Would extending and overriding the MicroSentryClient class be a feasible solution for you? Additionally, could you provide details on the specific DSN format used by Glitchtip and any custom headers you need? Understanding the format and headers will help us identify any compatibility issues and see how micro-sentry might better accommodate your setup.

As far as I understand, using this DSN<EMAIL_ADDRESS>should result in https://app.glitchtip.com/api/12345/store/ and include sentry_key=v7mp44vih7hbapmexkz3fdvpxle3m3ii in the header. This setup seems compatible with the Sentry API and likely with Glitchtip as well.
Aside from the tunnel option, could you clarify what specific issues you’re encountering with the default DSN parsing? Understanding where it diverges from this expected behavior could help pinpoint any necessary adjustments.

1.	Store API:  Yeah, store api seams to be deprecated but is indeed still functional. Here is an example of how it works in practice: [microsentry + glitchtip](https://stackblitz.com/edit/vitejs-vite-qempbm?file=src%2Fcounter.ts).
2.	Envelope API: As for the Envelope API, you’re absolutely right—this is something we currently do not support, and we will need to develop a feature to enable it. I’ll make sure we add this feature to our backlog.

Thanks again for your feedback


Drop Admin Password From API

This functionality was recently dropped from the installer in favor of using a static user with an auto-generated password.
We need to revendor the installer, adjust our API to match the change in https://github.com/openshift/installer/pull/771, and I suspect we will need to pull out the admin password generated similar to how we upload the admin kubeconfig after an install.
CC @jhernand the installer dropped functionality to let you specify the OpenShift admin password and email, is this workable on your side?

CC @ericavonb as well who has a cool idea that may help if we have issues around not being able to set admin password.

@dgoodwin It is workable for us, we are setting a hard-coded password now. If you change Hive so that it informs us of the password generated by the installer we can take it.
CC: @zgalor @elad661 @tzvatot


Switch to usize / isize indices

This will be needed. Iterator perf is abysmal with u32.

In 0.3.0-alpha.1


CF updates to address 1.0 issues

CF updates to address 1.0 issues

https://github.com/fabric-testbed/ControlFramework/pull/123


Release/0.22.1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
10 unchanged lines in 7 files lost coverage.
Overall coverage decreased (-0.2%) to 80.568%

Files with Coverage Reduction
New Missed Lines
%

modules/core/src/main/scala/com.snowplowanalytics/iglu.schemaddl/bigquery/Row.scala
1
74.36%

modules/core/src/main/scala/com.snowplowanalytics/iglu.schemaddl/jsonschema/JsonPath.scala
1
85.71%

modules/core/src/main/scala/com.snowplowanalytics/iglu.schemaddl/jsonschema/mutate/Mutate.scala
1
76.36%

modules/core/src/main/scala/com.snowplowanalytics/iglu.schemaddl/parquet/Field.scala
1
93.1%

modules/core/src/main/scala/com.snowplowanalytics/iglu.schemaddl/redshift/ShredModelEntry.scala
1
86.54%

modules/core/src/main/scala/com.snowplowanalytics/iglu.schemaddl/parquet/Caster.scala
2
83.58%

modules/core/src/main/scala/com.snowplowanalytics/iglu.schemaddl/jsonschema/circe/StringCodecs.scala
3
64.29%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
1248

Relevant Lines:
1549

💛  - Coveralls


[nowness] fix video extraction and add support for serie and playlist extraction (fixes #6720)

i make the requested changes.

Thanks.


List the PackageIdentifier of the package to be added to automation
veeam.veeam-agent
Details about the application
To get to the list/main page for the downloads you need to login here.
But luckily not for the release PDF and program itself!
The changelog for the latest version currently (5.0.2) is here.
The program itself (sadly zip) is here.

@Macleykun you can also use the New-PackageJson.ps1 script to add packages hosted on GitHub. For some packages, the existing version & installer regex may need some tweaks to equalize the number of installers' URLs with the ones from the latest existing version of that package. Would love to see you open a PR! No pressure here :)

sadly the both packages aren't hosted on github.
I personally don't use either of the apps anymore, so i'm ok to close the issue if that's ok

i will add this package, like the other two, once the first version is added to winget-pkgs, because it will be used as a base for future updates. i was saying for other packages, which you might request in the future. i rarely find time to search through winget-pkgs repo and add pkgs myself, which is why requests by people opened in the form of GitHub issues are an immense help to me.

i will add this package, like the other two, once the first version is added to winget-pkgs, because it will be used as a base for future updates. i was saying for other packages, which you might request in the future. i rarely find time to search through winget-pkgs repo and add pkgs myself, which is why requests by people opened in the form of GitHub issues are an immense help to me.

mhm!
also, here is the description if needed:
Simple and free Windows backup for cloud and physical servers, desktops, endpoints and more. Secure Windows workloads with Veeam Agent for Windows.
And the install args:
/silent /accepteula /acceptthirdpartylicenses
source: https://helpcenter.veeam.com/docs/agentforwindows/userguide/installation_unattended.html?ver=60

Heya, I added veaam-agent! There’s also a newer version out :) !

@SpecterShell I could not find any API from where the website fetches. Can you find one with your method?

$Response = Invoke-RestMethod -Uri 'https://autolk.veeam.com/json-rpc.php' -Method Post -Body '{"id":1,"method":"CheckForUpdates","params":{"ProductName":"AgentWindows","Version":"<IP_ADDRESS>80"}}'
[System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($Response.result.data))

https://autolk.veeam.com/json-rpc.php

wow, i'm impressed that you guys found an api!

Heyo! Wanted to ask if ya have been able to look into this! Hope your doing well


Hyperiond won't initialize framegrabber if you enable v4l with no hardware

Pi1 with framegrabber and v4lgrabber enabled
No grabbing hardware, no /dev/video
Start hyperiond
An error is logged, but the dispmanx grabber never gets initialized
I'll look into it later if no one beats me to it

I could confirm this :)

solved ...


Make singularization complete

The current inflector is bare bones and only supports a couple types of singularization. This should either be made complete, or use some existing library.

Obsolete.


Bug/Breaking change introduced in v20.8.3

Description
Have a series of CICD pipelines that started failing when patch version 20.8.3 was released. Seems to be a breaking change from the previous one originating from PR-2963

[x] ✋ I have searched the open/closed issues and my issue is not listed.

Versions

Module version: 20.8.3

Terraform version: 1.6.6

Provider version(s):

registry.terraform.io/hashicorp/aws: 5.40.0
registry.terraform.io/hashicorp/kubernetes: 2.27.0

Reproduction Code
Can't provide a minimal reproducible example at the moment. Will try to do it soon.
Expected behavior
Successful plan step.
Actual behavior
Plan step fails with the following error:
│ Error: Resource precondition failed
│
│   on .terraform/modules/cluster.eks_managed_node_group/modules/_user_data/main.tf line 10, in resource "null_resource" "validate_cluster_service_cidr":
│   10:       condition     = var.create ? length(local.cluster_service_cidr) > 6 : true
│     ├────────────────
│     │ local.cluster_service_cidr is ""
│     │ var.create is true
│
│ `cluster_service_cidr` is required when `create = true`.
╵

Additional context
None for now.

that is not a breaking change - thats simply expanding the scope of functionality of the module and ensuring failure to do so is not silent
I am going to assume you are using a node group that is defined on its own (separate module instantiation) as opposed to creating nodegroups through the root module, is that correct?

Hi @bryantbiggs yes, that is correct. Shouldn't the validation then be on the root module to allow this use-case?

again, to be fair - nothing is breaking. we have fixed a bug, and in order to fix said bug, a value is required. when users create nodegroups through the root module (i.e. - like this), there is no change required on their end. The module itself ensures the required values are passed down to the sub-modules correctly.
Its only in the scenario where  users have "disconnected" nodegroups, those that are defined outside of the root module like this, where we need to ensure that users provide this key piece of information in order to avoid the prior bug. In addition, on AL2 AMIs, the service CIDR has always been option, but with the change to AL2023, the service team is requiring this input. So we are aligning with that expectation here

Ok, didn't understood that was a required input for AL2023. We can easily fix this on our side, however I'm still not very convinced this should be a patch version upgrade 😄
Either way, thanks for the fast response! I'll close this issue

Thanks for your help @bryantbiggs


isoArcade.setBounds does not update octree

As found here I set the 3D world bounds of my world like this in the preload callback:
game.physics.isoArcade.setBounds(-30, -30, 0, 100, 100, 150);
And in the render callback I use octree to display the world bounds:
game.debug.octree(game.physics.isoArcade.octree, '#FFFFFF');
game is an instance of Phaser.Game
This results in the following being displayed:

Which is wrong because the white wireframe does not actually reflect the world bounds. In fact, whatever I pass to setBounds, the white wireframe stays the same size.
So after spending a while on navigating through the code I found out that the setBounds function (which is part of the Phaser.Plugin.Isometric.Arcade class, see source code) calls the setTo function on this.bounds which is a Phaser.Plugin.Isometric.Cube, simply passing on its parameters.
However, octree uses a completely different property in its own class to hold the current world bounds (see source code), which is never updated.
Since octree updates its data in the reset function, which is called in the constructor, I tried game.physics.isoArcade.octree = new Phaser.Plugin.Isometric.Octree( game.physics.isoArcade.bounds.x, ......); directly after the call to setBounds from above and the bounds are correctly displayed:

But I don't think this is the correct way of doing it. the setBounds function should handle changes to the bounds on its own. Maybe octree is not the only part which should be updated whenever the world bounds change.
So: Is this a bug?
It seems reasonable to me to assume that I can change the world bounds with a single call and not have to worry about other stuff getting updated correctly. If that's not the case though: Where am I expected to find that information? Googling for "phaser isometric world bounds" and the like, I found multiple websites mentioning game.world.setBounds(x, y, width, height); (e.g. this and this), which does not really make sense when using isometric world space. There are also a few abandoned questions about this (e.g. this).
I was lucky to find this post mentioning the 3D version of the setBounds function.

This is likely an oversight/bug based on essentially porting the Arcade physics from Phaser without fully understanding its workings. I'll possibly take a look at this if I get time, though someone with active use of the plug-in (such as yourself) may be better suited to submitting a PR to fix this.

I could submit a pull request to fix this particular case, but I don't know the details either because I am only using it for a very small project, so my guess is as good as yours.


why it always occur like this   " No such module PiedPiper ?"

i follow below tips step by step,but the repo doesn't work...
To use our Playground, please follow these steps:
Open the Xcode project Carlos.xcodeproj
Select the Carlos framework target, and a 64-bit platform (e.g. iPhone 6)
Build the target with ⌘+B
Click the Playground file Carlos.playground
Write your code

Hi @apiapia, thanks for pointing out this mistake! I believe I missed this paragraph when I updated Carlos to include PiedPiper as an external dependency. I'll have to update the documentation to use the Playground, will do it in the following days

Carlos will be migrated from PiedPiper to Combine in the nearest future.


Remove type ignore from undeprecated path

Codecov Report

Merging #113 (e28c108) into master (775e4ac) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #113   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines          493       494    +1
  Branches        93        93
=========================================
+ Hits           493       494    +1

Impacted Files
Coverage Δ

tomli/_parser.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


rustup

Looks like we haven't had one of these in a bit.

@bors r+

:pushpin: Commit aa3bc06f0f1f0c45ca5d84d030400bb052f51e73 has been approved by RalfJung

:hourglass: Testing commit aa3bc06f0f1f0c45ca5d84d030400bb052f51e73 with merge d0a4b5d5cc4308dd7ef08a46af56eaa52d991531...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing d0a4b5d5cc4308dd7ef08a46af56eaa52d991531 to master...


bitwarden: 1.31.3 -> 1.32.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/bitwarden/desktop/releases.
meta.description for bitwarden is: "A secure and free password manager for all of your devices"
meta.homepage for bitwarden is: "https://bitwarden.com"
meta.changelog for bitwarden is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/dgi3725vb0bm0v2dqwqf28r263dclxqj-bitwarden-1.32.1/bin/bitwarden had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 1.32.1 with grep in /nix/store/dgi3725vb0bm0v2dqwqf28r263dclxqj-bitwarden-1.32.1
found 1.32.1 in filename of file in /nix/store/dgi3725vb0bm0v2dqwqf28r263dclxqj-bitwarden-1.32.1

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

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
bitwarden

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

bitwarden

Maintainer pings
cc @Kiwi for testing.

Result of nixpkgs-review pr 168212 run on x86_64-linux 1

1 package built:

bitwarden


Frrist/update golang1.23.0

Why
In https://github.com/bacalhau-project/bacalhau/pull/4330/files#diff-77364c74880b2d28d60bdc250c7832430bb2c7d87d2e2359b05146c9f3cb5d6bR111 we are adding migration logic which requires directories to be copied. go 1.23 includes the os.CopyFS method which is helpful for this task, and preferred to writing our own CopyFS implementation.
How
Developers will need to perform the following actions:

download and install go 1.23.0
update golangci-lint: curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s -- -b $(go env GOPATH)/bin v1.60.1

Updating to this version of golang requires we update the linter to match, it appears the buildkite instance lacks sufficient memory to run the liner now:
2024-08-16 10:39:44 PDT	golangci-lint............................................................Failed
2024-08-16 10:39:44 PDT	- hook id: golangci-lint
2024-08-16 10:39:44 PDT	- exit code: 137
2024-08-16 10:39:44 PDT
2024-08-16 10:39:44 PDT	/buildkite/builds/4s62es3plflsi-1/expanso/bacalhau-golang/.gitprecommit/golangci-lint.sh: line 3:   450 Killed                  golangci-lint run --allow-parallel-runners --timeout 10m
2024-08-16 10:39:44 PDT	/buildkite/builds/4s62es3plflsi-1/expanso/bacalhau-golang/.gitprecommit/golangci-lint.sh: line 3:   452 Killed                  golangci-lint run --allow-parallel-runners --timeout 10m
2024-08-16 10:39:44 PDT	/buildkite/builds/4s62es3plflsi-1/expanso/bacalhau-golang/.gitprecommit/golangci-lint.sh: line 3:   453 Killed                  golangci-lint run --allow-parallel-runners --timeout 10m
2024-08-16 10:39:44 PDT	/buildkite/builds/4s62es3plflsi-1/expanso/bacalhau-golang/.gitprecommit/golangci-lint.sh: line 3:   454 Killed                  golangci-lint run --allow-parallel-runners --timeout 10m

This PR is currently block on updating the docker container buildkit uses to build and test bacalhau. I have updated the Dockerfile for the image here: https://github.com/bacalhau-project/bacalhau/pull/4332/commits/3c9de726a4a73c009591534719a5fd9ba18f3427 but need direction from @udsamani on how to make this change take affect.


member_joined_channel and member_left_channel events miss to trigger sometimes

Description
I can't figure out why sometimes these events are not executed... And also, when i am joining channel, i have to send dummy message in order to be actually join.

const app = new App({
    token: process.env.SLACK_BOT_TOKEN,
    signingSecret: process.env.SLACK_SIGNING_SECRET,
    socketMode: true,
    appToken: process.env.SLACK_APP_TOKEN,
  });

  const port = process.env.PORT as unknown as number || 5000;
  await app.start(port);
  app.event('member_joined_channel', async ({event, client}) => { ... });
  app.event('member_left_channel', async ({event, client}) => { ... });

What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[x] discussion

Requirements (place an x in each of the [ ])

[ ] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[ ] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version: "@slack/bolt": "^3.7.0",
node version: v12.16.3
OS version(s): windows
Steps to reproduce:
/
Expected result:
I would expect my code to be called on every member_left_channel and member_joined_channel event.
Actual result:
Sometimes member_left_channel and member_joined_channel event are not called.
Attachments:

Hi @StefanZivkovic, thanks for asking the question!

i have to send dummy message in order to be actually join.

I'm still unsure about what's going on in your Slack workspace yet but as far as I know, this is not a common situation.
As for the missing Socket Mode event delivery, checking the following thread may help:
https://github.com/slackapi/java-slack-sdk/issues/803#issuecomment-895768180

Hi @seratch thanks for reply. I saw actually your post days ago but was busy and forgot to answer. Ok that might be the same situation with me. Must say that i tried it a bit next morning and i didn't face any issues for that short amount of time.
I will have my eyes on this reference, and investigate as proposed in such a case. I can close this.


Add packaging scripts for embedded Mono and MSBuild bits

This change adds two scripts, copy-mono.sh and copy-msbuild.sh, that can be used to create embedded Mono and MSBuild packages for the operating system that they're run on (macOS, linux-x64 and linux-x86).
Note that I've gone ahead and included the binary that was causing trouble with the McMaster.Extensions.CommandLineUtils package.

Thanks all! This should fix the problem that https://github.com/OmniSharp/omnisharp-roslyn/pull/1259 was addressing.


Automated cherry pick of #4319: fix: bucket list objects with marker and limit

Cherry pick of #4319 on release/2.12.
#4319: fix: bucket list objects with marker and limit

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.12@2835fed). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.12   #4321   +/-   ##
==============================================
  Coverage                ?   6.85%
==============================================
  Files                   ?     501
  Lines                   ?   85140
  Branches                ?       0
==============================================
  Hits                    ?    5839
  Misses                  ?   78808
  Partials                ?     493

Flag
Coverage Δ

#aFlag
6.85% <0%> (?)

Impacted Files
Coverage Δ

pkg/multicloud/aws/bucket.go
0% <ø> (ø)

pkg/multicloud/ucloud/ufile.go
0% <ø> (ø)

pkg/compute/models/buckets.go
1.25% <0%> (ø)

pkg/cloudprovider/objectstore.go
2.55% <0%> (ø)

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 2835fed...ace9f6e. Read the comment docs.


Create CODE_OF_CONDUCT.md

Codecov Report

Merging #499 into master will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #499      +/-   ##
==========================================
- Coverage   90.36%   90.29%   -0.07%
==========================================
  Files          39       39
  Lines        2967     2967
==========================================
- Hits         2681     2679       -2
- Misses        286      288       +2

Impacted Files
Coverage Δ

vent/menus/tools/tools.py
95% <0%> (-2.5%)
:arrow_down:

Continue to review full report at Codecov.

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


Fix type graphql nullable types

:warning: This pull request includes the changes in #4833. Unfortunately there was no other way to do it, as #4833 includes a refactored way of setting TypeGraphQL decorator options
This merge requests is an improvement over #4181 and fixes #4663. In GraphQL arrays, there are several nullable types:

Items in the array may be null, ([String]!)
The array itself may be null, ([String!])
Both the array and items in the array may be null ([String])
Neither the array nor the items in it may be null ([String!]!])

So far, @graphql-codegen/typescript-type-graphql did not support either of the cases where the items in the array can be null. This led to uncompilable code, which #4181 attempted to fix. However, there were two problems with this merge request:

It only fixed fields definitions, but not input value definitions, leaving the bug in #4663
It removes the compilation error, but actually outputs the incorrect, non-nullable item type

TypeGraphQL supports nullable list types through the options { nullable: 'items' }, and  { nullable: 'itemsAndList' }, which this pull request will properly set on the field and input field decorators.

Branch has become unmergable. Will create a new branch


MudChipSet: Added toggle with spacebar (#4236)

Description

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[X] I've added relevant tests.

It looks like you added a .razor file for the test but didn't add a test here: https://github.com/MudBlazor/MudBlazor/blob/dev/src/MudBlazor.UnitTests/Components/ChipSetTests.cs

Oops. I will add

Did you test it manually? I have some comments about it.

By default space key also scrolls the page, you need to prevent default.
You wrote "toggle" in header, but in code it only select the chip, not has ability of deselect.
You invoke ChipSet.OnChipClicked(this); when user presses space key. But what if the OnChipClicked code change in future?As the naming it has a special code with click event. We should seperate the key events.
In Mud standards, if a component accepts keys, it should have focus visual. Example the chip should have a focus style when user presses tab and focus on a chip.

I there any news on this topic?
I would love to have this feature!
Since this feature already seems to have been created: will it also go to production?
I haven't been able to find these changes in v6.3.1..

Hi!

I haven't been able to find these changes in v6.3.1

Since this pull request has not been merged, the changes are not included in any version of the MudBlazor.

Since this feature already seems to have been created: will it also go to production?

Upon reviewing this pull request, it appears to be unfinished. There are several aspects that still need attention:

The author has not addressed all of the recommendations provided by @mckaragoz.
The problem that this pull request aims to solve is not clearly described or explained.
It seems that there is no opt-out mechanism available for this new feature, which could be a concern for some users.
Documentation about this feature has not been added, which is important for understanding its functionality and usage.

Based on these observations, it is evident that this pull request is not yet ready to be merged into the production codebase. Further work is needed to address the mentioned points and ensure that the changes are well-documented before proceeding with merging.

hi @snehabihani, are you able to return to this PR and make the suggested changes?

I can ,
but not immediately.
On Tue, Jun 6, 2023 at 2:36 AM Riley Nielsen @.***>
wrote:

hi @snehabihani https://github.com/snehabihani, are you able to return
to this PR and make the suggested changes?
—
Reply to this email directly, view it on GitHub
https://github.com/MudBlazor/MudBlazor/pull/4439#issuecomment-1577475261,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM4MS63LRSBPUXQZ5TA35P3XJZC4LANCNFSM5TVTMN7A
.
You are receiving this because you were mentioned.Message ID:
@.***>

Closing in favor of #9455


Explain that postdated posts can't be previewed

Clarify in the readme that setting a post's date for the future will cause it to not be displayed and prevent previewing your work.

Is there a special way to "preview" the site that isn't what everyone else would see? I agree with the clarification (this got me in the past), just want to make sure the language is clear - right now this implies to me that if I were to date my post in the past, there'd be some sneaky way for me to view it without it also being visible to all other blog viewers / RSS users - which I believe isn't the case (as soon as it launches it's out there)? I think removing the lines about "previewing" would avoid this confusion for me (while keeping the lines about how the dates control publication).

@momack2 The thing I'm referring to as "previewing" is loading the site on localhost to proof your work, as described in the readme instructions. So the "sneaky way to view it without it being visible to all other blog viewers" is just to load it up locally before merging the PR, but this doesn't work in the standard flow of events where you'd be trying to write before the publication date. Is there a word other than "preview" that would make more sense to me there?
I don't think we should state that you can load it on localhost without also mentioning in the same spot that you'll fail to see it if you're prepping your article in advance and setting the publication date to the date you actually want.

I think specifying how you’re  “previewing” would help (like what Oli
wrote). Otherwise it’s unclear what your note refers to.
On Mon, Sep 16, 2019 at 6:31 AM Oli Evans<EMAIL_ADDRESS>wrote:

@olizilla approved this pull request.
The specific notes here are correct. hugo will not build out the html for
the blog post page nor add an item for it in the blog index if the post has
a data that is in the future at the time, according to the computer it is
run on.
So looking at it locally in dev mode, or looking at the published preview
on ipfs via our CI build would both be affected.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ipfs/blog/pull/301?email_source=notifications&email_token=AAEXAFZBWDLKXVNITWXOOHDQJ6DBHA5CNFSM4IWR6F32YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCE2CAMA#pullrequestreview-288628784,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEXAF7XC7SMSSG72F6Y2J3QJ6DBHANCNFSM4IWR6F3Q
.

Just to clarify, @olizilla, how would one go about finding the link to the Cl preview on IPFS? I assume it's related to this check but I don't see a preview button (not sure if that's a permissions thing). If it is possible for someone to view a preview without using the command line, it would be lovely, because it would allow for non-coders to submit a markdown file right inside GitHub and still have a chance to proof their work, but if that's an option I don't think we've made it obvious.

@momack2 I've added a couple of words to help clarify what I mean by previewing (note that the first mention is inside of a section about using localhost). Please let me know if this addresses your concerns.
I spoke with @olizilla and the Circle CI process that creates preview website on IPFS (better for those who don't want to use the command line) is only available to specific users. It's related to https://github.com/ipfs-shipyard/ipfs-dns-deploy#what-it-does and would produce a "website added to IPFS" line in the checks where some folks would be able to click for a preview.

I'm only addressing the localhost case in this PR since the other option isn't yet explained and will need more explanation around for whom it's an option.
This is ready to merge if you're okay with the rewording @momack2.

this seems like an easy fix, am I missing something? PR here: https://github.com/ipfs/blog/pull/304


Timeout (control socket) while running engine

Please: I get a timeout error (control socket) with the --verbose option enabled. How do I find out what precisely timed out?
Input:
ng deploy --host 'my-host.url' --port 23 --tls --username 'myusername' --password 'mypassword' --remote-dir '/path/to/my/folder' --clean-remote --verbose --no-build --dry-run
Output:
Your global Angular CLI version (13.1.2) is greater than your local version (11.2.8). The local Angular CLI version is used.

To disable this warning use "ng config -g cli.warnings.versionMismatch false".
📦 Skipping build
🔍 Verifying passed options...
✔ Verified passed options
As --dry-Run was used nothing will get changed on the remote.
🌐 Connecting to remote...
Connected to <IP_ADDRESS>:23 (No encryption)
< SSH-2.0-mod_sftp

7ϛ�#�|WT�S��ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group18-sha512,diffie-hellman-group16-sha512,diffie-hellman-group14-sha256,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,rsa1024-sha1,ext-info-s=ecdsa-sha2-nistp256,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-dss_aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,cast128-cbc,3des-ctr,3des-cbc_aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,cast128-cbc,3des-ctr,3des-cbc[hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-sha1-96,umac-64@openssh.com,umac-128@openssh.com[hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-sha1-96,umac-64<EMAIL_ADDRESS>❌ An error occurred!
❌ An error occurred when trying to deploy:
Timeout (control socket)

Thank You :)

Hey @cocomo thanks for reporting. I'll have a look into this during the next few days. From what I think having a quick look and comparing your log outputs with the code the timeout happens between connecting to the host and switching the hosts working dir as you've provided the remote dir parameter and the log output that the dir will be changed never reached your terminal.
In the meantime: Have you checked that the host you're trying to connect to actually supports the actions you wanna do?

Thank You @bohoffi for the quick reply :-) I think the server should support my options, i copied most of the settings from Filezillas Site Manager, like: host, port, protocol (sftp), username.. I also played with some of the parameters, i.e. change the port to 22, got rid of tls along with changing port to 20 and 21.. I just wish i could get more information about what's actually causing the timeout error. The remote directory is accessible by Filezilla from my ftp user ..

I have a request @cocomo
As I can't reproduce the exact same error myself because I won't ask for your configuration parameters:
What IDE are you using? If it's VS Code could you try to debug the execution of the deploy process? The location for the breakpoint of interest would be inside node_modules\ngx-deploy-ftp - I'd like to be more precise about the further sub path but I don't have my computer around right now - you'd have to look for the log statement
context.logger.error('❌ An error occured when trying to deploy:');

Set a breakpoint on the subsequent statement which logs the errors message (e.message) and you'd be able to obtain more details from the error object itself.
I'm really sorry for the inconvenience of handing the errors message only to the user. I'll update the error logging to print out more - or even better all - information on Wednesday.

Hey @cocomo I just released v1.1.0 to npm which includes increased log output in case of an error. I do hope that this can help you with your issue.

Thank You very much @bohoffi for the quick reply and the new release :-) Unfortunately I am at the moment quite busy with other duties, but I will hopefully get back to testing within the next 2 weeks.

Please @bohoffi : What would I look out for in the run and debug window of VS Code? The error object listed there does not provide new insights to me, the only thing that makes me wonder is that the socket is called .. Does that state the ftp process cannot connect to the server? Should i send any particular output from the vscode debugging panels?
The upgraded ngx-deploy-ftp module provides also no new insights to me, here is my current output:
ng deploy --host 'ngcobalt###.manitu.net' --port 23 --username '###########' --password '###########' --remote-dir '/web/path/live' --clean-remote --verbose --no-build --dry-run
Debugger listening on ws://<IP_ADDRESS>:51878/c88ad17c-2a46-423b-bdae-bc0f23f8d1ac
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Your global Angular CLI version (13.1.2) is greater than your local version (11.2.8). The local Angular CLI version is used.

To disable this warning use "ng config -g cli.warnings.versionMismatch false".
📦 Skipping build
🔍 Verifying passed options...
✔ Verified passed options
As --dry-Run was used nothing will get changed on the remote.
🌐 Connecting to remote...
Connected to <IP_ADDRESS>:23 (No encryption)
< SSH-2.0-mod_sftp

�)͕���0�Kfn�K�ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group18-sha512,diffie-hellman-group16-sha512,diffie-hellman-group14-sha256,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,rsa1024-sha1,ext-info-s=ecdsa-sha2-nistp256,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-dss_aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,cast128-cbc,3des-ctr,3des-cbc_aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,cast128-cbc,3des-ctr,3des-cbc[hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-sha1-96,umac-64@openssh.com,umac-128@openssh.com[hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-sha1-96,umac-64<EMAIL_ADDRESS>❌ An error occurred when trying to deploy:

I finally got it deploying 🚀  Probably i did not provide my ssh-key in the desired process to the web hosting service? After successfully connecting to the server via sftp and ssh i changed the port in ng-deploy-ftp to 21 and things started running. I wish i could have done it via SFTP, but as far as i understand it FTPS seems to be a viable solution to easily deploy code for a non-profit charity project. Thank You @bohoffi for sharing and maintaining this awesome piece of software :-)

Hey @cocomo I'm glad to hear that you got it running in the end :)
Sadly this lib supports FTP only which is statet in the README but maybe I should point that out more clearly. I'll have a look on the error logging one more time as it seems that there was no output at all in your last terminal snippet.

I'll be glad to try, just let me know when the new version comes up (still might take some time due to other duties :) @bohoffi


Multiple Groups Not Working

I built a config based off the standalone example. Below is the code section I altered. Pretty simple. Nothing's showing up in its box on the web page. The "public_dns" group still works fine.  I can ping the custom hosts I added from the device I'm testing with.

The only thing I can think of: These hosts are either a PaloAlto firewall or some device behind the PA firewall. They're controlled by a friend who has locations around the world we can test to.
Is there something besides ping / ICMP (8 - at least I think it's 8?), that needs to be allowed?

That's showing it's not getting any data back, so yes, it looks like the firewall.
fping by default should just use ICMP, depending on what system you're running on, so you should be able to check the logs on the PAN device to see what's getting blocked.

I asked my friend to check when he gets a chance. Will find out soon, hopefully. Thanks.

Appears fping uses more than just "ICMP ECHO_REQUEST", as laid out in its man page. My friend is showing traceroute being denied / blocked.


Custom-sidebar is not working anymore

Hello, i need some help.
After some updates of Home Assistant, my custom-sidebar is not working anymore.
reinstall via Hacs doesn't help.
Downgrade to 4.6.0 (This Version was definitive working for me before) with no success.
Where can I find a Log/Trace for a hint?
Thanks and best regards
remoter3406

Hi @remoter3406,
Did you read the release note before updating to the major version?
If you didn't read it just go to the last release and you can read it there.
Regards

Thank you, that was very helpful. (dev tools)
So, I could find my config error very easy.
Regards

Perfect @remoter3406,
Glad that you solved it 👍


fix: missing status update in KMP controller

Description
What this PR does / why we need it:
In this PR the writeKMProviderStatus and helper functions were moved from the refresher back to the controller to ensure status messages get written to the KMP resource.
Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #
#1733
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[x] Does the affected code have corresponding tests?
[x] Do all new files have appropriate license header?

Post Merge Requirements

[ ] MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

@duffney PR lgtm, could you update commits to be verified so that we can merge it?


feat: Add functions_log_stackdriver

Adds functions_log_stackdriver snippet.

devrel/samples/1156
b/132734861

Note: I'm not sure how to effectively test this method as there is no response.
Other languages do not seem to test this method.

Java 11 is still seeing the error:
[ERROR] Failures:
[ERROR]   SnippetsTests.logEntry:190
Expected: a string containing "Hello, data"
     but: was ""

@grant is this still WIP or can we close?

I tested this function on GCF Java 8. Works fine.
I made the Kokoro test pass.
This PR was approved by kvg on Sep 23 (thanks for the patience).
Merging! 🎈


Tracer timestep choice

GFDL runs their OM4 cases with DT_THERM = 7200, and suggest that there is no need to decrease this as resolution is increased. We were previously running all panan cases with DT_THERM = 1800. I found a 20% speedup by increasing this to 3600 in panan-01-zstar.
Today we discussed (badly) what a reasonable value for this might be, e.g. I suggest we should choose between 3600 and 7200. How would we tell if we have increased it too far? Perhaps a comparison test with a short and long tracer timestep would be useful and an investigation of what impact it has on regions like the overflows.
@angus-g volunteered to do a bit more reading on tracer advection and timesteps from the mom6 docs and update us.

The statement I was thinking about regarding this is[^1]:

Advective mass fluxes in MOM6 are often accumulated over multiple dynamic steps. The goal is that as we go to higher resolution, this tracer advection will remain stable at relatively long time-steps, allowing for the inclusion of many biogeochemical tracers without adding an undue burden in computational cost.

Also from the Tracer Timestep page, the mixing and diffusion are handled with the thermodynamic processes. I guess that suggests that things could get unstable with a sufficiently long thermodynamic time step? I don't know how long it takes for enough energy to cascade into small scales for that to be an issue though.
[^1]: From https://mom6.readthedocs.io/en/main/api/generated/pages/Tracer_Transport_Equations.html

Posting this figure here also showing the impact of changing the tracer timestep in panan-01. This shows the transport in each layer at 37S for the first 6 months of the run. The black is the original panan-01. The others are my recreations of that with different tracer timesteps and forcing.

Questions:

Why did increasing the tracer timestep have this impact?
How do we tell in the future if we have the right tracer timestep? As far I could tell there weren't a lot more instabilities or obvious errors with the larger timestep.

If anyone has the time and will to investigate this further that would be awesome. The two comparison runs (blue dashed and solid blue above) are:

/scratch/x77/akm157/mom6/archive/panan-01-zstar-v13-exact/ (blue dashed, DT_THERM = 1800)
/scratch/x77/akm157/mom6/archive/panan-01-zstar-v13-exact_dt3600/ (blue solid, DT_THERM = 3600)

Any ideas @angus-g? I think it's to do with the interaction with the open boundary. It was much harder to tell that anything (abyssal transports etc) were going wacky away from the boundary until many years later. Some interaction with the nudging timescales or something?

Just confirming that the large tracer time step continues to be an issue (gets worse in fact) if you run for longer. This shows the same black and blue simulations from the above plot but now averaged over the 2nd year:

I can also confirm that I see a similar behaviour in the 1/20th run (this is the first 3 month average). Here the solid blue has a longer tracer timestep and looks wacky, and the dashed blue has a shorter tracer timestep and looks good. [Note that the original 1/20th looks a little odd, which could either be due to the bugs it had or perhaps a different density spacing in this diagnostic.]

Perhaps it's worth exploring a bit more and reducing DT_THERM in the panan-01 even more to 900?

Interesting indeed. So, it seems like the model is indeed stable with large DT_THERM, but the solution goes to crap.  Question is, how long can we push it without degrading the solution? And is this issue solely because of the open boundaries in PanAnt, or will we see the same issue in the global? Worth testing that too??

Hm, interesting. Definitely worth testing in the global to see if this is just a BC issue. I would expect increasing any of the timesteps will degrade the solution, even if the model is numerically stable (numerical stability doesn't mean the solution has converged to the continuous solution, ie become independent of further refinement in timestep). So maybe the question is, what features of a "reference" solution with a short timestep are "must haves" which we need to retain with a longer timestep? ie choose the longest timestep that retains the "must have" features. It could become disconcertingly subjective though...

Some interaction with the nudging timescales or something?

I haven't looked at the velocity side of things, but this is my understanding of the tracer nudging part of the OBC code. Each tracer has the segment forcing value segment%tr_Reg%Tr(m)%t (directly from the file), and a corresponding "reservoir" segment%tr_Reg%Tr(m)%tres. As far as I can tell, initially, the reservoirs are filled with the initial tracer values from the domain (i.e. the initial condition, not the first timestep of OBC forcing).
There's also an array which is used for modifying the reservoir (and restarts), OBC%tres_x (and tres_y). This array is initially filled with the segment data, not the domain initial condition. When radiation conditions are enabled, the tracer reservoir is reset to the forcing reservoir on the dynamics timestep in radiation_open_bdry_conds(). I actually don't understand the purpose of this...
On the tracer timestep, during tracer advection, the boundary values are overwritten by the tracer reservoirs, which are then used for calculating the advective fluxes, etc. Once advection is done, the tracer reservoirs are updated. This is where the reservoir lengthscales come into play: they determine how the interior and forcing values modify the reservoir, depending on whether there is inflow or outflow through the boundary. Once the tracer reservoir is updated, the forcing reservoir is set to this new value.
Both advection and the reservoir update use uhtr (respectively vhtr), which is the accumulated zonal (meridional) flux over the tracer period. I suppose we could look at tres_x/tres_y in the restarts to see if these have gone weird with the increased tracer timestep, and somehow the reservoir modification is odd? That's the only real difference from the non-OBC case, which would otherwise just use the accumulated fluxes for advection without replacing any values from a reservoir.

I did the test with an even shorter tracer timestep and good news is it seems to be converged - DT_THERM = 1800 and DT_THERM = 900 look the same for the boundary transport in the panan-01:

Maybe the solution for new regional configs is to do a short run with different values of DT_THERM and check when the boundary transport converges? In these runs the difference shows up very quickly (3 months is sufficient to distinguish them).

Looks like someone else has had a similar issue with too large DT_THERM interacting with the boundary. From https://github.com/jsimkins2/nwa25/tree/main/run:
"Per Andrew Ross:
To summarize, NWA12 behaves normally with DT_THERM = 1200 or 1800. If I try to increase DT_THERM to 3600, however, the Gulf Stream rapidly dissipates with a bizarre wave traveling to the south, and then reestablishes as a very weak current that doesn't separate at all. At the same time there appears to be extensive mixing in the Gulf Stream region, evident as cooling above 1000 m and warming below 1000 m all the way down to 5000 m. The initial dissipation starts immediately after switching to DT_THERM = 3600, and the total collapse and reestablishment happens within the first few months. Afterwards the weak boundary current remains roughly stable for years. I've attached some figures showing sea level as this is happening.
Previously I've run different experiments to try to identify the issue. I completely turned off tides and the open boundaries but still encountered the problem. The only control that I've found is the biharmonic viscosity (either Smagorinsky or using the velocity scale); with a low viscosity, the Gulf Stream dissipates much more rapidly, while with a high viscosity, the dissipation still happens but it occurs a lot slower."

I did another check, and we could also run the 1/20th panan with a slightly larger DT_THERM = 1200. However, this would require us reducing DT to 400 from 450, so that DT is a factor of DT_THERM, and from my test this doesn't give us any speed up.


Feat: updated the helper.js and style.css files

Steps

Made site completely responsive

Screenshot
Mobile Version

Tablet Version

Thanks


Support ESLint 8.x

ESLint v8.0.0 is released 🎉
It would be awesome to have official ESLint 8 support. 👊
I'm happy to help where I can of course 🙂

Support will wait until an actual release (betas don’t count).

Actual release has happened.

Until this is resolved, it would be helpful to update the installation instructions on https://www.npmjs.com/package/eslint-plugin-react. (Right now, they do not mention that eslint version 8 is not supported, so if you follow the installation instructions as given, you get an error.)

@skedwards88 sure, done in bf089982, but it won't likely be published until we support eslint 8 anyways.

@ljharb Will you push a release soon?

@silkfire i would say the will: https://github.com/yannickcr/eslint-plugin-react/commit/21e01b61af7a38fc86d94f27eb66cda8054582ed

on npm already released: https://www.npmjs.com/package/eslint-plugin-react/v/7.27.0

Thank you everyone 🤗


Expose payload version

Either a constant or a function that can evaluate the package to determine the current value.
The intent is to allow client code to determine what version of a function to use to decode a payload.
Still not sure what the best form for this to take would be.
While pre-1.0 this is less important, but once v1.0 is reached we need a way to allow changes to the payload while still allowing client code to reliably decode a mix of current and older payload versions.

Note to self:
I have some paper notes that I need to transfer to this GH issue.
Some of those notes warrant spinning off various other enhancement issues for further work.


persian/arabic hashtag

hashtag plugin does not support persian/arabic hashtags like: #سلام
please add this feature.

Hi @alirezamaleky, thanks for reporting this. Internationalized hashtag support is officially in development and is now available for preliminary testing the the latest v3.0.0-beta.1. Production release coming soon.

If you can, please try out that release and see if you can find any bugs.

Fixed in v3


missing

im missing daemon.json need help where should i get it?

Closing as irrelevant to this repo.


[GURPS 1.5.4]

Changes / Comments

Changed Speed Add To Tracker to use rolltemplates.
Added Thrown Object based on weight on combat tab below Ranged Attacks.
Added Bio tab. For Misc. Information, Physical Description, Background information.
Updated General tab. Replaced Miscellaneous box with a notes text box
Inventory tab. Cosmetic update to text box to remove scroll bar.
Options tab. Reduced font-size for Wound Modifier Notes text boxes.
Roll templates. Reduced font-size for results.
Delete old update notices
Updates tab. Highlight "mark updates as read" checkbox
Grimoire Tab. Tweak Spells based on: heading area. Added spacing
Tweaks to sheet.json file.

Roll20 Requests
gurps.html
gurps.css
sheet.json

Greetings @MadCoder253
You overwrote the sheet.json with your css. I have fixed this. Please update your fork before doing further edits.
Thanks,
Cassie

Dang! Good catch.


update error handing of the functions && add record operation trail function - [closed]

In GitLab by @sokril on Jun 27, 2018, 03:19
Merges weioperation -> operation

In GitLab by @wknet123 on Nov 13, 2019, 11:08
The test coverage for backend is FAIL  ,The test coverage for frontend is 38.11   , check  consolse log

In GitLab by @wknet123 on Nov 13, 2019, 11:08
closed


fix(lane_change): remove unnecessary if condition

Description
https://github.com/autowarefoundation/autoware.universe/pull/3635
I guess that the if condition should be removed.
  virtual void setPreviousDrivableAreaInfo(const DrivableAreaInfo & prev_drivable_area_info)
  {
    if (prev_drivable_area_info_) {
      *prev_drivable_area_info_ = prev_drivable_area_info;
    }
  }

Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Close


insertRow doesn't work if bootstrap and jquery installed via npm

Instead of directly importing jquery and bootstrap library in html tag, I tried to install them via npm, in this case, the New button after turn on insertRow={true} won't pop up dialog somehow.

@dp-huang, could you please confirm your version of bootstrap via npm? Because I use this react-bootstrap-table on my other web project and also install bootstrap(integrated by bootstrap-loader) and jquery via npm, that's all fine.
So I thinks it's not a real issue, feel free to discuss with me. Thanks


The Case for Bluetooth (Suggestion)

Relying on locations published by authorities is problematic for two reasons. First it's vulnerable to human errors and malicious behavior (publishing wrong info) and second, it takes time. Besides, tracking people's locations indoors can be inaccurate.
To tackle these issues I suggest generating a public/private key pair {pub, pvt} at installation time. Now, assuming Bob went close enough to Carol for a Bluetooth connection to be established, then they both send their corresponding {id=H(pubme), proof=signme(H(pubother))} where H is a cryptographic hash function and they both add a new entry to their (truncated) list of "touched" users as {id, proof, time, location}. If a user appears twice we can override the last entry, keeping only the last appearance.
If Bob has been tested positive, he gives his public key and proves to Arthur (the authority) that he has the corresponded private key. Arthur then publishes {H(pubb), signa(H(pubb))} using his public key. When Carol receives it she can verify the message is from Arthur and if H(pubb) appears in her truncated list she gets a notification with the corresponding time and location. She can then use proofb as an evidence for being near Bob. (It is not a proof, although it otherwise requires cooperation.)
This way Arthur cannot push false information, no one can pretend to be someone else, it is much faster and it does not require Arthur to know anything about other users except for their public key. If a user agree to share his/her "touched" list with Arthur, it can be used to warn second generation. Users can upload their keys after installation so if they are tested positive, we know their public key is not fresh and therefore useless
Actually I had a much simpler idea, using only hash functions and random numbers, it is  inspired by what they did in Singapore: https://www.tracetogether.gov.sg
In any case, location tracking would still be beneficial since some devices do not support it. We need both.

Sounds like a good idea. Hopefully the source code of TraceTogether will be published soon.
https://www.theregister.co.uk/2020/03/26/singapore_tracetogether_coronavirus_encounter_tracing_app_lessons/

Check out this (admittedly Android only) API for the broadcast and sharing of the keys in a peer to peer fashion https://developers.google.com/nearby/connections/overview

There is an open source implementation for similar feature:
https://github.com/tripleblindmarket/covid-safe-paths/pull/279

see https://github.com/DP-3T/documents/issues/66 and for context: https://github.com/DP-3T/documents/blob/master/DP3T White Paper.pdf as well as https://github.com/DP-3T/documents/issues/222 and https://covid19-static.cdn-apple.com/applications/covid19/current/static/contact-tracing/pdf/ContactTracing-CryptographySpecification.pdf

Also see #213


Error 0x80070003 when running bash

Your Windows build number:  10.0.16299.492

What you're doing and what's happening:  Running bash or C:\Windows\System32\bash.exe results in "Error 0x80070003 Press any key to continue...". The Ubuntu 18.04 shortcut works.

What's wrong / what should be happening instead: The Bash shell should open or at least give a more descriptive error.

First of all, @IamCarbonMan you're out of date, get Redstone 4 build 17143!

Same issue: error 0x80070003  when starting bash.

OS build: 17134.137

lxcore.zip

I took a look at the trace and the service is failing to find a registered distribution.  Can one of you please share the output of wslconfig.exe /list

Closing as stale given wslconfig.exe is deprecated and no follow-ups were forthcoming. If the "failing to find a registered distribution" problem persists please open a new ticket and the error can be revisited.


ref(pkg/envoy): rm old config file

ref(pkg/envoy): rm old config file
part of #2397
Please mark with X for applicable areas.
-->
Affected area:

New Functionality      [ ]
Documentation          [ ]
Install                [ ]
Control Plane          [ ]
CLI Tool               [ ]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests                  [ ]
CI System              [ ]
Performance            [ ]
Other                  [ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution? No

Codecov Report

Merging #2628 (3148052) into main (2d1db5c) will decrease coverage by 0.35%.
The diff coverage is 95.55%.

@@            Coverage Diff             @@
##             main    #2628      +/-   ##
==========================================
- Coverage   64.36%   64.00%   -0.36%
==========================================
  Files         152      151       -1
  Lines        7002     6910      -92
==========================================
- Hits         4507     4423      -84
+ Misses       2479     2471       -8
  Partials       16       16

Flag
Coverage Δ

unittests
64.00% <95.55%> (-0.36%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/envoy/route/route_config.go
98.31% <95.55%> (-1.69%)
:arrow_down:

pkg/endpoint/providers/kube/client.go
78.00% <0.00%> (-1.00%)
:arrow_down:

pkg/envoy/ads/stream.go
0.00% <0.00%> (ø)

pkg/envoy/proxy.go
69.23% <0.00%> (+0.71%)
:arrow_up:

pkg/service/types.go
66.66% <0.00%> (+66.66%)
:arrow_up:

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 2d1db5c...3148052. Read the comment docs.


CAMEL-10447 Added Transformer adoc

Thanks for the PR it has been merged. Do you mind closing this?

Thanks! closing


Feature Request: Add typos Github Actions

Is your feature request related to a problem?
@halkeye recently shared with me https://github.com/marketplace/actions/typos-action which is a tool to detect typos in the codebase
I executed it against this repository and it detects a few.
Solution you'd like
I would like to fix all the typos and then enable the Github Action  as explained on https://github.com/marketplace/actions/typos-action
Alternatives you've considered
No response
Anything else?
No response

This https://github.com/updatecli/updatecli/pull/1268 introduce the typos
Once again thanks @halkeye for this great suggestion