Proposing New Component - OTP INPUT - Areteans

Title: OTP INPUT
Overview:
An OTP Input Component is a user interface element designed for capturing One-Time Passwords (OTPs) or verification codes typically sent via SMS, email, or an authentication app. The component allows users to enter OTP codes in a segmented input field, enhancing user experience with intuitive interaction, validation, and error feedback.
For banking and insurance domain applications, OTP component is critical as it ensures secure and seamless user authentication. Account login, transaction authorization, password recovery and device verification are most common use cases.
Usage:
This component is commonly used in authentication flows, such as login, sign-up, or password recovery processes. It supports customization options to align with the branding and behavior of your application. Provision given to make the length of the OTP dynamic through configuration. Validations with respect to length are already in place.
Props:
Label – will be used as an input label for the control.
Length – integer value to determine the length of the OTP
Dependencies:
 UUID (Universally Unique Identifier)

 npm install uuid

Styled Components ---> npm install styled-components
Component benefits:

Enhanced User Experience ---> OTP controls automatically move the focus to the next input field as users type, making the process smoother and faster.

Customization and Styling –--> can be customized for appearance and behavior, allowing developers to match the UI with the application's branding.

Popular Use Cases -->
Two-Factor Authentication (2FA): OTPs sent via SMS, email, or authenticator apps.
Account Verification: Verifying user identity during sign-up or login.
Transaction Confirmation: Confirming sensitive actions like financial transactions.

Attached the component code and detailed description with images below.
OTP_Input_Component.docx
OTPInput.zip

adding this component makes sense - I will take the source code and refactor the code and add it to the gallery - Thanks for your contribution!

Thinking more about this - What is the use case in a Pega application for showing this component? All authentication is done by an external IDP provider and they will implement the page showing the OTB input - I have never seen a use case where a user enters the OTP input inside an assignment - this is all done before loading the portal.
In all your popular use cases:
Two-Factor Authentication (2FA): OTPs sent via SMS, email, or authenticator apps.
Account Verification: Verifying user identity during sign-up or login.
Transaction Confirmation: Confirming sensitive actions like financial transactions.
the Pega Platform is not mark of the authentication flow and does not render the screen.
At this point I don't think there is real value adding this component to the repo - if the use case is to enter a 5 digit input fields - the OTP input might be useful but it become a more generic PinCodeinput component

OTPInput.docx
Attached details why this component was built and its usage.

Rejected-  SDK only – for Constellation UI – an external OAUTH IDP is expected to be used and handled MFA and OTP input


Issue #2320: fixing circular dependencies

There is an index file in the root src file that imports and exports all the components. These two components import various Tab-related components from that index file, but that index file also imports these components themselves. Instead of pulling from that index file I just import them directly.

Hi!
Can someone review & merge this ?
Changes to files
src/basic/Tabs/DefaultTabBar.js and  src/basic/Tabs/ScrollableTabBar.js
make sense for me.
I have this issue of warnings with circular dependencies to.
@see: https://github.com/GeekyAnts/NativeBase/issues/2320
Thanks

Hello guys, i think i've implemented the same fix here #2394 more than a month ago but nobody merged it.

@SupriyaKalghatgi can you review?

@sanketsahusoft @sankhadeeproy007 @akhil-geekyants @shivrajkumar

duplicate of #2394


Full wikipedia sentence match code keeps crashing

Cross posting from fb group (https://www.facebook.com/groups/532005453808326/permalink/614668408875363/)
When I try to train the full wikipedia model for sentence matching using "./examples/wikipedia_sentence_matching_full.sh", my code keeps getting killed. I am running it on a fairly beefy VM with 4 CPU cores and 36G memory. Any suggestions for fixing this?
Output I see:
./starspace train -trainFile data/wikipedia_shuf_train5M.txt -model wikipedia_sentence_matching_full -trainMode 3 -initRandSd 0.01 -adagrad true -ngrams 1 -lr 0.05 -margin 0.05 -epoch 30 -thread 40 -dim 100 -negSearchLimit 100 -fileFormat labelDoc -similarity "cosine" -minCount 5 -normalizeText true -verbose true
Arguments:
lr: 0.05
dim: 100
epoch: 30
maxTrainTime: 8640000
saveEveryEpoch: 0
loss: hinge
margin: 0.05
similarity: cosine
maxNegSamples: 10
negSearchLimit: 100
thread: 40
minCount: 5
minCountLabel: 1
label: __label__
ngrams: 1
bucket: 2000000
adagrad: 1
trainMode: 3
fileFormat: labelDoc
normalizeText: 1
dropoutLHS: 0
dropoutRHS: 0
Start to initialize starspace model.
Build dict from input file : data/wikipedia_shuf_train5M.txt
Read 2099M words
Number of words in dictionary:  1892639
Number of labels in dictionary: 0
Loading data from file : data/wikipedia_shuf_train5M.txt
		Killed

@rajhans : in your output dim is 300, can you try something smaller? In addition, can you check how much memory the program takes? It should not be bigger than 36 GB.

Same result: tried with -dim=100 and still got killed.
./starspace train -trainFile data/wikipedia_shuf_train5M.txt -model wikipedia_sentence_matching_full -trainMode 3 -initRandSd 0.01 -adagrad true -ngrams 1 -lr 0.05 -margin 0.05 -epoch 30 -thread 40 -dim 100 -negSearchLimit 100 -fileFormat labelDoc -similarity "cosine" -minCount 100 -normalizeText true -verbose true
Arguments:
lr: 0.05
dim: 100
epoch: 30
maxTrainTime: 8640000
saveEveryEpoch: 0
loss: hinge
margin: 0.05
similarity: cosine
maxNegSamples: 10
negSearchLimit: 100
thread: 40
minCount: 100
minCountLabel: 1
label: __label__
ngrams: 1
bucket: 2000000
adagrad: 1
trainMode: 3
fileFormat: labelDoc
normalizeText: 1
dropoutLHS: 0
dropoutRHS: 0
Start to initialize starspace model.
Build dict from input file : data/wikipedia_shuf_train5M.txt
Read 2099M words
Number of words in dictionary:  226815
Number of labels in dictionary: 0
Loading data from file : data/wikipedia_shuf_train5M.txt
Killed

@rajhans Thanks! What is the memory taking by starspace? Can you try a smaller training dataset? We can also use streaming data but that requires some functionality change in the code.


[Steps] Evenly Divided Steps

In version 1.8.1 the steps don't evenly divide amongst their parent anymore when using numbered steps. They used to fill the entire width.
example:

This appears to be a bug caused by switch to table-cell for equal height.  One secs

Fixed in next


Can't use --depth command anymore?

The --depth arg was used to restrict the depth of the repositories checked out, but it appears that it can no longer be passed, unless the syntax has changed to something weird. I tried several combinations and none worked:
python -m astrocats --depth 1 supernovae import

python -m astrocats supernovae import --depth 1

The --depth arg is needed to get the Travis build working, otherwise we run into Travis' disk quota.

I think this is just not being parsed and passed by the argparse.  Should be an easy fix I can take care of this afternoon.

No, actually, it's just that the argument was --git-depth instead of --depth.
BUT I just changed it to --clone-depth (and variable clone_depth) for clarity.


API for exporting mesh and color data

I am working on an API to export the raw data from ARHeadsetKit. It takes all geometry and color data present at one point in time, then reorders it into a simple serialization format. This is entirely lossless and should happen very quickly.

To work with this format, you need a programming language with low-level access to memory layout. Python is not ideal; rather, use Swift or C/C++ compiled in release mode.

The next step is converting the YCbCr data to RGB (if you wish) or rearranging the geometry data into a different layout.

Initially, you should convert the luma and chroma into PNG images, before converting to RGB. They are valid color spaces that can be viewed as images.

This can be done for a single triangle (a very tiny image).

Next, read this: https://developer.apple.com/documentation/accelerate/conversion/understanding_ypcbcr_image_formats
Apple has utilities in vImage for converting YCbCr -> RGB on the CPU: https://developer.apple.com/documentation/accelerate/1533189-vimageconvert_ypcbcrtoargb_gener

Concatenate all the chroma tiles into a massive array, do the same with luma, and send that through vImage.

cc @knightfork

Serialization format:
64 bytes {
  UInt32 - number of small triangles
  UInt32 - number of large triangles
  56 bytes of padding
}
repeat for number of small triangles {
  320 bytes {
    [SIMD4<Float>](count: 3) - vertices; SIMD3<Float>(x, y, z, 0)
    [SIMD2<Float>](count: 3) - texture coordinates; SIMD2<Float>(u, v)
    32 bytes of padding
    [SIMD2<UInt8>](count: 36) - row-major 6x6 matrix of chroma
    [SIMD<UInt8>](count: 144) - row-major 14x14 matrix of luma
  }
}
repeat for number of large triangles {
  1280 bytes {
    [SIMD4<Float>](count: 3) - vertices; SIMD3<Float>(x, y, z, 0)
    [SIMD2<Float>](count: 3) - texture coordinates; SIMD2<Float>(u, v)
    32 bytes of padding
    [SIMD2<UInt8>](count: 196) - row-major 12x12 matrix of chroma
    [SIMD<UInt8>](count: 784) - row-major 28x28 matrix of luma
  }
}

Texture coordinates are local coordinates within the 12x12 or 28x28 tile. They start at (0, 0) at the bottom left corner of the first pixel. The coordinates increase by 1 for each pixel traveled right or up.
This should ZIP compress quite nicely, as over 50% of the pixels are zeroed out.

Example of usage:
import ARHeadsetKit
import Metal
import QuartzCore

class MyRenderer: CustomRenderer {
  unowned let renderer: MainRenderer
  var startTime: Double?
  var endTime: Double?

  required init(renderer: MainRenderer, library: MTLLibrary!) {
    self.renderer = renderer
  }

  func updateResources() {
    guard let startTime = self.startTime else {
      self.startTime = CACurrentMediaTime()
      return
    }
    if self.endTime != nil {
      // Already exported once; don't do it again.
      return
    }

    // Automatically export after 30 seconds (you can adjust the duration).
    let timerDuration: Double = 30.0
    let currentTime = CACurrentMediaTime()
    guard currentTime - startTime > timerDuration else { return }
    self.endTime = currentTime

    let exporter = ARDataExporter(renderer: self.renderer)
    let data = exporter.exportMesh(includeColor: true)

    // Do something with the `Data` object, like inspecting it in some Swift
    // code you write. You don't have to export it via 'ActivityViewController'
    // (ref: https://github.com/philipturner/lidar-scanning-app/blob/main/LiDARScanningApp/ActivityViewController.swift)
    // just to debug the exporter.
    print("Number of bytes: \(data.count)")

    let rawMemory = malloc(data.count)!
    defer { free(rawMemory) }
    data.copyBytes(
      to: rawMemory.assumingMemoryBound(to: UInt8.self), count: data.count)

    let header = rawMemory.assumingMemoryBound(to: UInt32.self)
    let numSmallTriangles = Int(header[0])
    let numLargeTriangles = Int(header[1])
    print("Number of small triangles: \(numSmallTriangles)")
    print("Number of large triangles: \(numLargeTriangles)")

    if numSmallTriangles > 0 {
      let smallTriangles = rawMemory + 64
      for i in 0..<min(numSmallTriangles, 10) {
        // Address of the i-th triangle
        _ = smallTriangles + i * 320
      }
    }
  }

  func drawGeometry(renderEncoder: ARMetalRenderCommandEncoder) { }
}

This is ready for testing inside an ARHK tutorial. I won’t proactively test it, but I’ll fix any bugs you report.

I corrected a previous error in the serialization format specification. It previously had 14x14 luma for the 320-byte tiles and 12x12 chroma for the 1280-byte. That should be reversed; 12x12 for 320-byte and 14x14 for 1280-byte.


meltTokens signs P2PK proofs

Fixes: #164
Description
added option to sign P2PK proofs if a private key is provided
PR Tasks

[x] Open PR
[x] run npm run test --> no failing unit tests
[x] run npm run format

@gudnuf Let me know if this helps...

@Egge21M can you bring this in?

@lollerfirst Thank you so much for taking this on. This does look good to me, but this branch diverges from the current development branch and a merge would add some duplicate commits under old hashes. Could you please reset this branch to 4ae5562496f221271e3f68025c325807d709121d and rebase it?

@Egge21M Is this good?


Object Rest/Spread / Babel Issue

Hello,
Another babel issue, been banging my head against the wall for a while and turning to the community is my last resort.
I've looked for and found most of the current and older babel issues, nothing seems to bulge my issue. Im looking to use the new Object Rest/Spread Properties in a vue single file component together with vuex.
Here goes.
Versions:
Node - 7.9.0
npm - 4.2.0
yarn - 0.27.5
laravel-mix - 1.4.2
OS - OS X El Capitan 10.11.6
note - It's an electron app, so not using laravel project build etc.
Package.json:
Probably includes a ton of redundant libs by now after all the different tests and attempts
{
    ...
    "scripts": {
        "dev": "yarn run nvm && cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
   },
    "dependencies": {
        "axios": "^0.16.2",
        "babel-core": "^6.26.0",
        "babel-loader": "^7.1.2",
        "babel-plugin-transform-object-rest-spread": "^6.26.0",
        "babel-polyfill": "^6.26.0",
        "babel-preset-env": "^1.6.0",
        "babel-preset-es2015": "^6.24.1",
        "babel-preset-stage-3": "^6.24.1",
        "cross-env": "^5.0.5",
        "electron": "^1.7.5",
        "electron-reload": "^1.2.1",
        "es6-promise": "^4.1.1",
        "imagemin-webpack-plugin": "^1.5.0-beta.0",
        "jshint": "^2.9.5",
        "jshint-esnext": "^2.7.0-3",
        "laravel-mix": "^1.4.2",
        "postcss-flexbugs-fixes": "^3.2.0",
        "sass-resources-loader": "^1.3.0",
        "vue": "^2.4.2",
        "vue-devtools": "^3.1.6",
        "vue-select": "sagalbot/vue-select",
        "vuex": "^2.3.1"
    }
}

webpack.mix.js:
const { mix } = require('laravel-mix');

const ImageminWebpackPlugin = require('imagemin-webpack-plugin').default;

mix
  .js('renderer/js/renderer.js', 'renderer/dist');

mix
   .sass('renderer/assets/styles/main.scss', 'renderer/dist/style.css');

mix.options({
  processCssUrls: false,
  postCss: [
    require('postcss-flexbugs-fixes'),
  ],
});

mix.sourceMaps();

mix.webpackConfig({
    plugins: [
            // Minify images matching the test regex
            new ImageminWebpackPlugin({
            disable: process.env.NODE_ENV !== 'production',
            test: /\.(jpe?g|png|gif|svg)$/i,
        }),
    ],
    resolve: {
        alias: {
            'vars': path.resolve(__dirname, './renderer/assets/styles/vue-wrap.scss'),
            'components': path.resolve(__dirname, './renderer/js/vue/components/'),
            'api': path.resolve(__dirname, './renderer/js/api/api.js'),
        },
    }
});

.babelrc:
{
    "presets": ["es2015", "stage-3"],
    "plugins": ["transform-object-rest-spread"]
}

Steps To Reproduce:
I use yarn devto start the defined dev script from package.js
During compilation I get following error:
Syntax Error: Unexpected token (58:2)

  56 | 			return "Yay?"
  57 | 		},
> 58 | 		...mapState({
     | 		^
  59 | 			availableBrookers: state => state.appSettings.availableBrookers
  60 | 		})
  61 | 	},

 @ ./renderer/js/vue/Login.vue 8:2-229
 @ ./node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":[["env",{"modules":false,"targets":{"browsers":["> 2%"],"uglify":true}}]]}!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./renderer/js/App.vue
 @ ./renderer/js/App.vue
 @ ./renderer/js/renderer.js
 @ multi ./renderer/js/renderer.js ./renderer/assets/styles/main.scss

Im also currently forced to use babel-polyfill in my entry file. It seems like my .babelrc config is completely ignored.

Update. Workaround found.
Finally found a workaround. Easy to forget but looking through the docs for babelrc I was reminded that you can define babel settings in the package.json instead of in a separate babelrc file.
My laravel-mix is still ignoring the .babelrc file in my project root, but not the settings in package.json.
Run:
yarn add babel-plugin-transform-object-rest-spread
Then add the following to package.json:
    "babel": {
        "plugins": ["transform-object-rest-spread"]
    },

Should do the trick.


Cannot instantiate abstract class Zend\Diactoros\ServerRequestFactory

How do you use Sentry?
Sentry Saas (sentry.io)
Version
3.17.0
Steps to Reproduce
ZF 2.5.3
I'm trying to throw an error
\Sentry\captureLastError();
Also tried to send messages
\Sentry\captureMessage('Something went wrong');
Expected Result
There is always an attempt to instantiate an abstract class
Actual Result
Cannot instantiate abstract class Zend\Diactoros\ServerRequestFactory, <path to project>/vendor/php-http/discovery/src/ClassDiscovery.php, 219
#0 <path to project>/vendor/php-http/discovery/src/Psr17FactoryDiscovery.php(74): Http\Discovery\ClassDiscovery::instantiateClass('Zend\\Diactoros\\...')
#1 <path to project>/vendor/php-http/discovery/src/Psr17Factory.php(96): Http\Discovery\Psr17FactoryDiscovery::findServerRequestFactory()
#2 <path to project>/vendor/php-http/discovery/src/Psr17Factory.php(104): Http\Discovery\Psr17Factory->createServerRequest('GET', Object(GuzzleHttp\Psr7\Uri), Array)
#3 <path to project>/vendor/sentry/sentry/src/Integration/RequestFetcher.php(25): Http\Discovery\Psr17Factory->createServerRequestFromGlobals()
#4 <path to project>/vendor/sentry/sentry/src/Integration/RequestIntegration.php(125): Sentry\Integration\RequestFetcher->fetchRequest()
#5 <path to project>/vendor/sentry/sentry/src/Integration/RequestIntegration.php(117): Sentry\Integration\RequestIntegration->processEvent(Object(Sentry\Event), Object(Sentry\Options))
#6 <path to project>/vendor/sentry/sentry/src/State/Scope.php(378): Sentry\Integration\RequestIntegration->Sentry\Integration\{closure}(Object(Sentry\Event), Object(Sentry\EventHint))
#7 <path to project>/vendor/sentry/sentry/src/Client.php(292): Sentry\State\Scope->applyToEvent(Object(Sentry\Event), Object(Sentry\EventHint))
#8 <path to project>/vendor/sentry/sentry/src/Client.php(169): Sentry\Client->prepareEvent(Object(Sentry\Event), Object(Sentry\EventHint), Object(Sentry\State\Scope))
#9 <path to project>/vendor/sentry/sentry/src/Client.php(161): Sentry\Client->captureEvent(Object(Sentry\Event), Object(Sentry\EventHint), Object(Sentry\State\Scope))
#10 <path to project>/vendor/sentry/sentry/src/Client.php(202): Sentry\Client->captureException(Object(ErrorException), Object(Sentry\State\Scope), Object(Sentry\EventHint))
#11 <path to project>/vendor/sentry/sentry/src/State/Hub.php(166): Sentry\Client->captureLastError(Object(Sentry\State\Scope), NULL)
#12 <path to project>/vendor/sentry/sentry/src/functions.php(65): Sentry\State\Hub->captureLastError(NULL)
#13 <path to project>/module/Application/src/Application/Controller/IndexController.php(76): Sentry\captureLastError()
#14 <path to project>/vendor/zendframework/zend-mvc/src/Controller/AbstractActionController.php(84): Application\Controller\IndexController->indexAction()
#15 [internal function]: Zend\Mvc\Controller\AbstractActionController->onDispatch(Object(Zend\Mvc\MvcEvent))
#16 <path to project>/vendor/zendframework/zend-eventmanager/src/EventManager.php(490): call_user_func(Array, Object(Zend\Mvc\MvcEvent))
#17 <path to project>/vendor/zendframework/zend-eventmanager/src/EventManager.php(260): Zend\EventManager\EventManager->triggerListeners('dispatch', Object(Zend\Mvc\MvcEvent), Object(Closure))
#18 <path to project>/vendor/zendframework/zend-mvc/src/Controller/AbstractController.php(118): Zend\EventManager\EventManager->triggerEventUntil(Object(Closure), Object(Zend\Mvc\MvcEvent))
#19 <path to project>/vendor/zendframework/zend-mvc/src/DispatchListener.php(118): Zend\Mvc\Controller\AbstractController->dispatch(Object(Zend\Http\PhpEnvironment\Request), Object(Zend\Http\PhpEnvironment\Response))
#20 [internal function]: Zend\Mvc\DispatchListener->onDispatch(Object(Zend\Mvc\MvcEvent))
#21 <path to project>/vendor/zendframework/zend-eventmanager/src/EventManager.php(490): call_user_func(Array, Object(Zend\Mvc\MvcEvent))
#22 <path to project>/vendor/zendframework/zend-eventmanager/src/EventManager.php(260): Zend\EventManager\EventManager->triggerListeners('dispatch', Object(Zend\Mvc\MvcEvent), Object(Closure))
#23 <path to project>/vendor/zendframework/zend-mvc/src/Application.php(340): Zend\EventManager\EventManager->triggerEventUntil(Object(Closure), Object(Zend\Mvc\MvcEvent))
#24 <path to project>/public/index.php(79): Zend\Mvc\Application->run()

I added allow-plugins, But the error remains
Installed with composer require sentry/sdk command
composer version 2.5.5

What ideas? What else can you try?

There is no version 2.5.5 of the Zend framework. Looking at your stack trace, are you referring to https://github.com/zendframework/zend-mvc instead?
A few options you can take:

Disable the RequestIntegration https://docs.sentry.io/platforms/php/integrations/#custom-integrations
Use a version of the SDK before 3.17.0.

The last version of Zend\Diactoros\ServerRequestFactory is not an abstract class anymore, this change happened five years ago.


Typo - missing space before the link

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

Looks good; thanks @zikato.


Change parameter of try_pack from T to &T

Any::try_pack takes message: T as parameter, consuming it.
However, taking message: &T instead of message: T would work too, allowing the callers to reuse message.

Good point. Let me check if this can simply be added as well.

Same for unpack. A common pattern would be to try to unpack as a series of different types, but taking self by ownership prevents this and forces you to explicitly check the type url first.
AFAICT it's a trivial change, since self never actually needs to get consumed in the unpacking functions.


server: introduce basic Server

simplified using the new core.SplitAddrPort()

Refactored, a few times 😅

pulling this out, no value


Adds HCI command HCI_LE_Set_Connection_CTE_Transmit_Parameters

This PR adds new HCI command introduced by Bluetooth v5.1 for Direction Finding: HCI_LE_Set_Connection_CTE_Transmit_Parameters.
Besides command itself there is a Host wrapper implementation and Unit Tests of the wrapper.

I find the unit under test to simple and the mock too complicated to be considered a good unit test.

In addition to very little confidence added by this unit test I would consider the maintenance cost to be too big to be worth it in this case, especially without proper unit test mock support.

I will strongly recommend that we remove this unit test.

@joerchan
Referring to unit test I've provided and your comment.
Solution is based on idea that is already in the Zephyr repository: hci_prop_evt. The complexity of mocking in hci_prop_evt is on the same level as the one I've provided. What more the solution I've provided will be used to tests all HCI DF related commands, so there will be a number of unit tests implemented with it.
The solution (mocking part) may be generalized and used as common solution for implementation of any HCI command and especially wrappers or higher level functions. That was secondary goal for that implementation besides check of HCI DF commands.
If there is no plan to provide any unit tests for HCI command in future then that may be dropped from the PR.
Pay also attention that we already support on such solution.
I'm not sure what did you mean with:

"it would be better to test this through the bt_hci_cmd_send(_sync) functions instead."

Can you put more details about it?

@ppryga My main issue here is maintainability of the tests. I'm not objecting to testing, simply how easy they are to write and add, and how easy it is to change the implementation, I don't want to loose productivity because of unit test maintenance.
I have to main issues with the unit test now.

The test is testing static functions and not API functions. This ties the implementation instead of the API to the test, and making internal changes means having to update the unit test.
The mocking of the HCI layer is spread across multiple files, so if there is a new command that must be handled in init suddenly we have to update X amount of unit test mocks in addition.

The hci_prop_evt unit test is already problematic in it's own right. The feature that it tests is quite simple and unit test is at risk of needing updates for unrelated changes when new commands must be mocked (has happened a few times already).
It does however only use public API functions, so that part is not that bad.
Adding new unit tests currently does not scale well, and I would prefer not to add more unit tests until this scalability issue has been resolved.
I think the best way to handle unit tests for the host is to only use the public API functions, and only mocking the HCI layer with a single HCI mock.

I'm not sure what did you mean with:

"it would be better to test this through the bt_hci_cmd_send(_sync) functions instead."

Can you put more details about it?

Just scratch this part, my point was supposed to be about only using public APIs, but bt_hci_cmd_send would not be the public API for this. In fact we don't even have a public API yet.

@joerchan I see your point and I agree. The way I have implemented the test will require maintenance in the near or distant future. I'm sure about it because the provided test depends e.g. on steps required to initialize the stack.
Also I agree that opening static function just for unit test was a bad idea.

I think the best way to handle unit tests for the host is to only use the public API functions, and only mocking the HCI layer with a single HCI mock.
Agree with you about above suggestions.

What more after re-consideration provided tests are more integration tests than unit tests and as such (in my humble opinion) should be implemented and maintained by person/people dedicated to that.
I will drop test part of the PR. If there is a decision to provide public API for DF in host, I will implement unit tests for the public API only with use of BOARD=unit_testsing and mocking all HCI related functions instead of simulating controller. In such case no bt_init should be required for start of the test unit (it will be true isolated environment).
I'm afraid it will also require to write a good portion of code to handle HCI and other host functions. On the other hand it should be easier to understand and require less or no maintenance effort.

Commits that introduced testing were dropped.

@joerchan @jhedberg @rugeGerritsen @cvinayak Can you do a review of updated sources?

I'm happy with the Kconfig-changes now. I assume that HAS_HW_NRF_RADIO_BLE_DF will be added to nrf5340, nrf52820, and nrf52811 when you're ready to do so
Yes, I'll add HAS_HW_NRF_RADIO_BLE_DF to other SOC configs when I test running code on that HW.

@jhedberg @joerchan please take another look

@jhedberg All style related issues are corrected. Can you do a review?

@joerchan @jhedberg @cvinayak could you see at the PR?

Most of requested changes were done. A few were left with my explanation and questions.

Code update according to all requests.


Add transient option to node configurations

The Snowflake adapter allows for +transient: [boolean] as a configuration option:
See docs here: https://docs.getdbt.com/reference/resource-configs/snowflake-configs
Docs example:
name: my_project

...

models:
  +transient: false
  my_project:
    ...

This pull request adds +transient as a supported attribute in the JSONSchema for node configurations.
I also confirmed that it is a boolean and not a #/$defs/boolean_or_jinja_string, i.e. "{{ True }}" renders as a string literal in the manifest.json, not as true.

@joellabes Ah! Learned something new about dbt.
Made the requested change, although it means the description has to go, unless you want to do something like {"allOf": [{"$ref": "#/$defs/string_or_array_of_strings"}], "description": "..."}.

@dwreeves sorry for the delay getting back to you! I don't think that's right - wouldn't it behave the same as https://github.com/dbt-labs/dbt-jsonschema/blob/main/schemas/dbt_project.json#L343-L347 where you can have a ref and then extend it with extra context?

Ah, can you do that? I am not well versed enough at JSONSchema to know if that works. I was basing my assumption off googling for various things and sort of half-following what others were saying.
It seems in the earliest draft of JSONSchema this would not have been supported, and frankly I'm not entirely following the discussions I'm reading on how this has changed over time.

An object schema with a "$ref" property MUST be interpreted as a
"$ref" reference.  The value of the "$ref" property MUST be a URI
Reference.  Resolved against the current URI base, it identifies the
URI of a schema to use.  All other properties in a "$ref" object MUST
be ignored.

Still, regardless of whether it works or not to just add the description, I don't know if I want to be the first person to add a description attribute to an object with a $ref property in this JSON.
So, is it OK if we leave the description out? 😬 Or do you want it in still?

Hmmmm that stack overflow post is pretty definitive! I also don't know a ton about JSON schema - I've picked up the basics from developing this repo but not an expert.
I think that for now let's leave the description out, and I'll do some experimenting some other time


rn-carousel-buffered shows first 3 slides then repeats third slide

I have a large set of slides (currently ~200 slides) and I am using rn-carousel-buffered to mitigate the effect of loading all these slides.
If I try to slide to the fourth slide, the fourth slide will flash for a brief second then the third slide will reappear.  If I continue trying to go to the next slide, the same thing will happen: the fourth slide will flash briefly then the third slide will take its place.  Interestingly, if I now try to go back I have to go back 5 slides to get to the beginning.
I know the description is a little confusing so I have a video of the problem and will share it with you using via Youtube using the<EMAIL_ADDRESS>email (since it contains other people's emails, I'd rather not post it here).
You can look at the code on my Github here:
html: https://github.com/c1moore/frank2015_app/blob/dev/public/view/frankbook.html
js: https://github.com/c1moore/frank2015_app/blob/dev/public/js/frankbook.js

I am working on fixing this bug myself.  Is there any assumptions you made that would limit the number of slides in a buffered carousel?

@c1moore did you make a fix for the flashing when it loads and updates the slides?

The problem was being caused by bindonce in combination with the rn-carousel-buffered attribute.  I couldn't find a way to make them work together so I decided to remove bindonce and preload (cache) the slides far enough ahead that the user would not notice a lag from too many pictures being loaded at once.

thanks @marksy, removing the bindonce fixed this for me too. from:

to (notice there is no :: before images)

thanks a lot! solved it for me also

Hey im having this same problem and im not using bindonce. Any help on how to fix this ???

I am also seeing a flash of another slide. I use rn-carousel-buffered and am not using bindonce.
I my case sliding from 1 to 2 works fine and 2 to 3 as well. But when sliding from 3 to 4 the 5th slide is flashing briefly before slide 4 is shown. This pattern continues. I.e. when sliding from 11 to 12, slide 13 is briefly visible.
I don't have this problem when I don't use  rn-carousel-buffered, but the page is lagging if I load all slides.

Fixed by removing the track by $index
FROM

TO

Fixed by using ng-style instead style
FROM

TO


Add geographic limit rectangle

Needed for https://github.com/AnalyticalGraphicsInc/cesium/pull/6986, because some projections really really don't work well unless you clip out everything but the local area (EPSG 2039, for example).
This is distinct from clipping planes on the globe in that this respects curvy projections, which become possible in #6986. Keeping this separate also avoids adding extra complication to the clipping planes implementation.
Pretty pictures:

Coffee belt in 3D

Coffee belt in Columbus View

Thanks for the pull request @likangning93!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Nice!  Please update CHANGES.  People have been asking for this feature for a while (even without projections).
Does it work with both infinite scrolling and 2D map rotate modes?
We should probably wait until after the release to merge this, even if we think it's ready.

How hard would it be to get rid of the white seam at the IDL when east == west?
Did you check to make sure this works if east < west (ie the rectangle crosses the idl)

I assumed the outline was for the screenshots, is there a need to have it at all in production?

It's strange that the performance drops in 2D only when showing the rectangles. I only get ~20 FPS.

How hard would it be to change the center of projection? Columbus view might be useless if there is a limiting rectangle crossing the anti-meridian:

It's strange that the performance drops in 2D only when showing the rectangles. I only get ~20 FPS.

I'm seeing this in master as well, although not in the 1.49 release. Interesting thing, it doesn't happen if the scene starts in 2D. I'll write up an issue.
var viewer = new Cesium.Viewer('cesiumContainer', {
    terrainProvider: Cesium.createWorldTerrain()
});

viewer.scene.debugShowFramesPerSecond = true;

// Tropics of Cancer and Capricorn
var coffeeBeltRectangle = Cesium.Rectangle.fromDegrees(-180, -23.43687, 180, 23.43687);

viewer.scene.globe.geographicLimitRectangle = coffeeBeltRectangle;
viewer.scene.skyAtmosphere.show = false;

// Add rectangles to show bounds
var rectangles = [];

for (var i = 0; i < 10; i++) {
    rectangles.push(viewer.entities.add({
        rectangle : {
            coordinates : coffeeBeltRectangle,
            material : Cesium.Color.WHITE.withAlpha(0.0),
            height : i * 5000.0,
            outline : true,
            outlineWidth : 4.0,
            outlineColor : Cesium.Color.WHITE
        }
    }));
}

Sandcastle.addToolbarButton('Show/Hide Bounds', function() {
    var rectanglesLength = rectangles.length;
    for (var i = 0; i < rectanglesLength; i++) {
        var rectangleEntity = rectangles[i];
        rectangleEntity.show = !rectangleEntity.show;
    }
});

Open here: https://github.com/AnalyticalGraphicsInc/cesium/issues/7018

Hi all, you forgot to update the documentation for the Globe class.  The new member in the public API isn't mentioned there.  It looks like it's a Rectangle that defaults to undefined?  Also, should it be possible to specify this at construction time, maybe by passing it to the constructor of the owning Scene?

Can i use other shape ?
Only 'rectangle'?

@kenghuo only rectangle is supported at this time


Update jackson.version to 2.9.10 to address CVE-2019-14540 & CVE-2019-16335

Update jackson.version in dropwizard-bom from <IP_ADDRESS>90807 to 2.9.10
This addresses two CVE, both with CVSS v3.1 score of 9.8

CVE-2019-14540
CVE-2019-16335

The update should be done for both release/1.3.x branch and for master (2.0.x)

Thanks!

Any idea how long it'll be before a release would go out with this?
Our CI builds break (debatable whether they should) because of the CVE severity score of this one.

@jplock. any idea of a release date for 1.3.15?

@richmidwinter @msymons We're currently blocked by some flakey behavior of Sonatype OSS when trying to deploy artifacts. Once these issues have been resolved, we'll publish Dropwizard 1.3.15.

@richmidwinter @msymons Dropwizard 1.3.15 should hit Maven Central within the hour.


Could not set FunctionTemplate to Global Object.

Hi @rogchap
I am writing some polyfills for v8go, but it seems can't set function template to an existing global object:
obj := ctx.Global()

fetchFn, _ := v8go.NewFunctionTemplate(iso, f.goFetchSync)
if err := obj.Set("_goFetchSync", fetchFn); err != nil {
    return err
}

v8go: unsupported object property type `*v8go.FunctionTemplate`

https://github.com/rogchap/v8go#update-a-javascript-object-from-go

We would need to implement GetFunction() for this to work: https://v8.github.io/api/head/classv8_1_1FunctionTemplate.html#a2e019c10474a4b2352bd1e1cb094f84a
That said, is there a reason why you are not using a TemplateObject as your Global Object and setting a function on creation of the Context? There are performance benefits as the template can be cached and re-used to create new contexts.
See here for an example fetch API (a very simplified one) that uses a Promise: https://github.com/rogchap/v8go/blob/master/function_template_test.go#L52

I'm writing a package, which add some polyfills to v8go: #77
Here is my code:
https://github.com/kuoruan/v8go-polyfills
My API is like:
ctx, _ := v8go.NewContext()

fetch.Inject(ctx)
console.Inject(ctx)
url.Inject(ctx)

The problem is some polyfills will need to both set global Object and RunScript, I can't run script when Context is not inited.

I would love to see an example of bare bone setup for you GO with React SSR with pollyfills.

Hi @Terfender It's almost done, and I will publish a repo when it is ready.

I'd love to see an example as well!

I'm curious how ES Module imports would work and things like dynamic imports.
The easiest answer probably is: don't bother, just run esbuild/webpack ahead of time and format the output as an IIFE.
A better answer is something like this: https://stackoverflow.com/questions/52023157/how-would-one-enable-and-use-es6-modules-in-the-v8-javascript-engine/52031275
Looking at the v8go code, I don't currently see any uses of InstantiateModule or CompileModule

Hi @rogchap
I rewrite the fetch API with pure Go code now, https://github.com/kuoruan/v8go-polyfills/tree/master/fetch
It's works fine.
But my problem is, can we get this object in the FunctionTemplate ?

Are you not able to pass this as your first argument?

So, if I have a cat, the object is like:
const cat = {
    name: "Tom",
    getName: function () {
      return this.name;
    }
}

Create a object template for it:
iso, _ := v8go.NewIsolate()
ctx, _ := v8go.NewContext(iso)

cat, err := v8go.NewObjectTemplate(iso)
if err != nil {
	panic(err)
}

getName, err := v8go.NewFunctionTemplate(iso, func(info *v8go.FunctionCallbackInfo) *v8go.Value {
	return nil // get the cat name
})
if err != nil {
	panic(err)
}

if err := cat.Set("getName", getName); err != nil {
	panic(err)
}

myTomCat, err := cat.NewInstance(ctx)
if err != nil {
	panic(err)
}

if err := myTomCat.Set("name", "Tom"); err != nil {
	panic(err)
}

because we can't get this in the functionTemplate, so I must create new object template for Tony Cat, Jack Cat...
but it's not a big problem.


Coordinator: per node mediators instead of tablets

Testing queue-like workload showed a huge disadvantage to the way current mediator time is propagated. Tablets that belong to a mediator are split into buckets, and each bucket advances its mediator time when all transactions in that bucket are acknowledged. Unfortunately this acknowledgement may take an unexpectedly long time, for example, given round-trip time between nodes is rtt:

@ 0.0rtt KQP node receives a read request, which needs a snapshot. The request will take 0.5 rtt to arrive to coordinator.
@ 0.5rtt Coordinator plans a new step S with some transactions and sends it to mediators, which will travel for 0.5 rtt.
@ 0.5rtt Coordinator receives a new snapshot request and replies with S. This step will travel back to KQP node for 0.5 rtt.
@ 1.0rtt KQP node receives snapshot and sends a read request to shard 1. This request will travel for 0.5 rtt.
@ 1.0rtt Plan step S arrives to mediator. Since it has transactions, mediator time is not updated, plans are forwarded to participating shards. They will travel for 0.5 rtt.
@ 1.5rtt Shard 1 receives a read request at step S, this is not the current time so it starts waiting (background request for this step is not important).
@ 1.5rtt Shard 2 receives transactions at step S, it starts to persist the plan, which will take 1.0 rtt.
@ 2.5rtt Shard 2 finishes committing the plan, and sends acknowledgement to mediator, it will travel for 0.5 rtt.
@ 3.0rtt Mediator receives acknowledgements and advances mediator time, it is broadcast to nodes and will reach shard 1 node in 0.5 rtt.
@ 3.5rtt Shard 1 can finally see that step S arrived and it has no preceding transactions. Let's say read request is served from memory and response is sent immediately. It will travel for 0.5 rtt.
@ 4.0rtt KQP node receives a read response and replies to client.

It seemed like mediators only add 0.5 rtt which is not much, but as it turns out it may block mediator time updates for a very long time. What we need is a way to stop using these "buckets" and use personal per-participant mediator time.
To do that we need to make mediators per-node, which will subscribe to coordinators on behalf of running tablets and then distribute merged transactions to these nodes. Since this merging will be effectively per-tablet, mediator time will also be per-tablet, although we need a way to optimize the majority of idle tablets to observe updated time with a single atomic (when possible).
The first step would be a way for actors (nodes) to subscribe to a subset of the transaction stream (filtering it by tablet), and for coordinators to then stream relevant steps to these subscribers. When a new tablet is needed nodes will add/remove tablets to the stream and we need a way for additional events to be injected at the front of the queue, so nodes can determine when historic events end and the complete stream begins.
Challenges:

The number of tablets may be huge (millions), a simple hash table for routing might consume a lot of memory. Subscribing to these millions of tablets may also be expensive. Probably need a way to batch these, and maybe optimize it somehow, so nodes begin receiving streams based on some hashes instead of individual tablets? Likely not really a problem, even for millions the hash table memory is in the order of dozens of megabytes.
The number of nodes coordinators will need to broadcast steps may become very large (thousands). However realistically it shouldn't be a problem, since mediators already have to broadcast timecast updates.
There will be two streams of transactions running in parallel, which may duplicate traffic (but it's very small). Shards should handle duplicates gracefully however.
We need a way for idle shards to use some common atomic variable, but also a way to reliably switch them between personal and common time. This is needed to avoid doing too many atomic updates for thousands of running idle shards, but may be ignored in the first version (so that all atomics are "personal").

I think I have a way to make atomic counters that don't need any complicated trees and have update and read operations as O(1). The key aspect is that mediator time advances for all tablets, except those that are currently frozen at Step-1 because they have unacknowledged transactions at Step. And we need a way to freeze and unfreeze mediator time for a particular tablet, while updating all non-frozen tablets.
This can be achieved using two atomic counters:

Common is shared by all tablets and updated every time we need to advance mediator time for all non-frozen tablets
Local is set to Step-1 when tablet has unacknowledged transactions at Step, and Max<ui64>() otherwise

Operations:

Advance mediator time to Step: Common.store(Step, std::memory_order_release)
Freeze tablets at Step: Local.store(Step-1, std::memory_order_relaxed) for each tablet with the first unacknowledged transaction at Step, then advance time to Step
Unfreeze tablets: Local.store(Max<ui64>(), std::memory_order_relaxed) for each unfrozen tablet
Read current mediator time: ui64 common = Common.load(std::memory_order_acquire); ui64 local = Local.load(std::memory_order_relaxed); return Min(common, local);

Why this works:

Operation order between different atomic variables is not fixed (and may be reordered, just like any memory accesses), we can only rely on release/acquire order of a particular atomic variable and how it affects other reads.
The logical update order between Common and Local is synchronized to a single actor thread at any given time
When we perform a release-store to Common we release all previous memory stores, which will be acquired by an load-acquire from Common
Let's suppose a load-acquire from Common observes some value Step, the next load from Local is guaranteed to have at least the last value stored to Local before Step was stored to Common, but it may (or may not) also be some future value.
If the tablet was frozen at Step and not yet unfrozen, that value is guaranteed to be Step-1 and the minimum will stay at Step-1 even when Common is further updated to Step+∂. Thus a tablet that was frozen before the time is updated to Step is guaranteed to stay at Step-1 and stay unaffected by further updates to Common until it is unfrozen.
If a tablet was unfrozen at Step (or later) and then optionally frozen at Step+∂ we may observe Local to be either Max<ui64>() or Step+∂-1, but since we read Common to be Step the result will not exceed Step
Let's supposed we unfreeze a tablet and then update Common to Step+∂, is it guaranteed for this tablet's time to update to Step+∂ as well? Since we set Local to Max<ui64>() before updating Common we may read some intermediate value from Common between Step and Step+∂ and also observe Local to be either Step-1 or Max<ui64>(). Depending on the observed Local value we may also observe some intermediate time. Eventually tablet will read Commonto beStep+∂and afterwards it is guaranteed to observeLocalto beMax()and notStep-1`

All synchronization is done via Common, and we get a reliable way to freeze/unfreeze time for any particular tablet, while continuing to update time for idle tablets. Relaxed load/store to Local is enough (and proving correctness must be done using the weakest order possible), in practice it's better to also use acquire/release, because those are better at pulling the latest value from caches in weak architectures (especially under simulators like relacy). This is mostly important when unfreezing tablets, when one core is reading current time in a loop it may take a long time to finally observe the change from Step-1 to Step. Note however that this is true for any atomic read, observing the latest value is never guaranteed unless it's a failed cas.

After making an actual sketch of the streaming protocol I think I found some problems with the idea:

Tablets don't initially know their list of coordinators/mediators. This is not a major issue, but it may require making a lot more changes than anticipated. For example, currently datashards register in the timecast service after the initial distributed transaction is complete, but in the future, with per-node mediators, they wouldn't even receive plan steps until they register. Currently datashards, columnshards, persqueue and schemeshard tablets participate in distributed transactions, and we would have to carefully review code and ensure tablets register very early, as soon as they learn their processing params. I'm not sure whether it's easy, especially with schemeshard, which may simultaneously participate in multiple coordinator sets due to legacy subdomains (which still exist in production).

Possibly stuck transactions that don't have a destination. Imagine a tablet that receives a plan for a drop and self-deletes because coordinator could process an ack. Now this tablet has no subscribers, nobody is waiting for its transactions, but they are still in the queue. Currently mediators will eventually notice that pipe cannot connect and check whether the tablet is deleted, automatically acknowledging transactions that don't have a recipient. Coordinators will not use pipes and hence will not be able to auto ack transactions in the same way (or they would have to after some timeout?). This complicates things a lot.

I think we need a simpler solution to the timecast problem for now, i.e. support for timecast exclusion lists.


mkisofs returns "Bad Option '-e' (error -1 BADFLAG)"

As stated in the title, when executing your script, i am getting an BADFLAG error of mkisofs.
I am using mkisofs  version 3.02a09 (x86_64-unknown-linux-gnu) on Arch Linux.
Do i need to fix something or has that flag been replaced?
Thanks!

Hi!
I seem to have it fixed - all i had to do was to replace the -e with a -d.


Context menu missing in object-list on dashboard

Issue Type: Bug
When using database dashboard to query or edit data no context-menu is available
Reproduce:

Select manage database in context menu

Right-click on item in object list

Result:
No context menu is available
Expected result:
Same context menu as in connections

Azure Data Studio version: azuredatastudio-insiders 1.13.0-insider (75388cc3afd30f5d69d4e5752b62fda6351b78ca, 2019-10-15T07:48:57.461Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 x 3600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.94GB (11.38GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (2)

Extension
Author (truncated)
Version

import
Mic
0.11.0

schema-compare
Mic
0.7.0

Thanks for your feedback! I don't believe this is functionality we've enabled yet.

Here is the same functionality in a stable build

Version info for this screenshot:
Version: 1.9.0
Commit: 78a42e1d112ae3231777722b51eaf44f83ddbe55
Date: 2019-07-10T04:10:29.206Z
VS Code 1.34.0
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Linux x64 5.0.0-29-generic

Thanks for the update, I'll re-classify this as a bug.

@anthonydresser There were a number of changes made to explorerWidget.component.ts and explorerTree.ts prior to this issue existing. The context menu worked fine in the latest release, but seemingly after these changes were made, the context menu no longer worked. Something is causing the context menu functions to not work properly on the items anymore. I suggest you look into what is preventing the context menu from popping up as this was a feature in previous builds.


pip install facepy doesn t work

Collecting facepy
  Could not fetch URL https://pypi.python.org/simple/facepy/: There was a problem confirming the ssl certificate: [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:590) - skipping
  Could not find a version that satisfies the requirement facepy (from versions: )
No matching distribution found for facepy

Cannot install using pip, can you fix this? :)
Thanks

Well, I used pip install facepy,
but I tried today, and it worked. Really weird, it must have been something with my machine apparently. Thanks for your answer.


[NMA-1338] CoinJoin P2P messages

Issue being fixed or feature implemented

What was done?

Added classes for the new CoinJoin messages
Amended SendDsq to fit our purposes
Modified BitcoinSerialize to receive the new messages
Cleaned up some unused/obsolete messages

How Has This Been Tested?

Breaking Changes

Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

[ ] I have assigned this pull request to a milestone

Codecov Report

Merging #172 (2e4eaea) into master (7183a64) will increase coverage by 1.87%.
The diff coverage is 44.95%.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Use GITHUB_WORKSPACE for repo root

Signed-off-by: Aditya Sharma<EMAIL_ADDRESS>
Description of your changes

Should fix

I have:

[x] Read and followed Upbound's contribution process.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR, as appropriate.

How has this code been tested

Finally worked:

https://github.com/upbound/homebrew-tap/actions/runs/2937267774
https://github.com/upbound/homebrew-tap/pull/27


integrations: Improve Sentry Integration.

This PR makes the following changes to the Sentry Integration:

Updates the documentation to be more accurate.
Adds support for the "Rails" backend for Sentry Integration.
Limits the check for Raven SDKs only to Python.
Adds an exception fixture for "Vue".
Adds support for sample events (previously, the integration used to send 400).

Regarding the support for "Vue", I created a sample Vue App, and the value of the platform field in the captured payload was javascript, which is already included in the integration. Hence, no change was required for this.
The sample event for python had a version equal to 5. Hence, I had to use pass for that.
Fixes: #25778

Documentation Changes

Before
After

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@zulipbot add "mentor review"

@alexmv Thanks for reviewing my work. :heart_decoration:
I have updated the PR to incorporate the suggested changes. Let me know if there is anything more required in this one!

Merged, thanks @sbansal1999 and @alexmv!

Backported to 7.x as c7839ff084201848af65433be3c5a3d82938882b through 421ce4ffe0d4692e3b637ba85401186b67abf324.


Clearer documentation of CosmosClient Dispose API contract

This issue is to request that the conditions under which one should call CosmosClient.cs > Dispose() be documented in the API comments.
Context is that I am instantiating a new CosmosClient per rotated CosmosDB key/token but am not sure if it's fine to rely on GC to clean up the old CosmosClients or I need to call Dispose() explicitly.
I am not using the Singleton pattern which lets .NET handle CosmosClient.cs > Dispose() natively because from the documentation, it appears I need 1 CosmosClient per key/token.

Relatedly, I'm confused about why the performance best practices doc recommends using CosmoClient as a singleton b/c CosmosDB key/token rotation seems like a security best practice and that necessitates a CosmosClient per key/token.

As a general guidance, any class implementing IDisposable needs to be disposed when no longer user, if your application, for whatever reason, no longer needs the CosmosClient instance, then you can dispose it.
Why you would no longer need the CosmosClient? That's up to your business logic.
Ideally yes, you would have a Singleton instance for the lifetime of the application, if you use MSI authentication, there are no keys, so there is no rotation scenario. If you do use keys and you need to rotate, then sure, you can dispose the current client (because you no longer need it, following IDisposable usage) and create a new one in its place. It's still 1 active client, not 2.


Bad Checksum solc 0.8.15

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (2457e5f 2022-06-16T00:04:27.032663Z)
What command(s) is the bug in?
forge build
Operating System
macOS (Intel)
Describe the bug
Same issue as #1648, I believe svm-rs is missing a checksum.
cc @roynalnaruto
 forge build
[⠊] Compiling...
[⠃] installing solc version "0.8.15"The application panicked (crashed).
Message:  checksum not available: "0.8.15"
Location: /Users/runner/.cargo/git/checkouts/svm-rs-cd2fa967df1e48a1/70fe9d9/src/lib.rs:197

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
[1]    41261 abort      forge build

Workaround is to add solc_version = "0.8.14" to foundry.toml

will be fixed by https://github.com/gakonst/ethers-rs/pull/1387 and an ethers bump here

Duplicate of https://github.com/foundry-rs/foundry/issues/1991


cleaning

Draft PR in preparation for meeting.

[x] Added setup structure with setup.py (no sys.path.append required)
[x] Added environment.yaml file
[x] Added .gitignore to avoid accidentially commiting uneccessary files, e.g., __pychache__
[x] Added .pre-commit-config.yaml for use with pre-commit: Format code nicely and automatically.

Let's also check out how fair is


[SPARK-12025] [SparkR] Rename some window rank function names for SparkR

Rename some window rank function names for SparkR.

Test build #46815 has started for PR 10016 at commit c56a7bc.

Test build #46815 has finished for PR 10016 at commit c56a7bc.

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

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

Merged build finished. Test PASSed.

code change looks good. New names have no conflict with R base package.
But I don't see they are deprecated now? Could you point to me the discussion or JIRA that they will be removed in Spark 2.0?
If they are deprecated, I am fine with the name change.
If they are not deprecated, could we add new names as aliases, while keeping the old names at the same time?

@sun-rui Thanks for your comments. You can get the issue from the source code and this PR(#9930).

@yanboliang, thanks for your info. I didn't look at the latest code:)
LGTM

LGTM. Thanks @yanboliang -- BTW were these APIs were present in SparkR 1.5 ? If so we'll need to update the release docs about this change.

@shivaram they were added only for Spark 1.6, so no need to update release doc on breaking changes
https://github.com/apache/spark/commit/dc3220ce11c7513b1452c82ee82cb86e908bcc2d
https://github.com/apache/spark/commit/40c77fb23a1ee0a4e69d735ee6247f83b7e13b92
But the new names seem to mask methods from dplyr.


Fix global artifact overwriting in nested workflow

This PR is to solve my issue https://github.com/argoproj/argo/issues/1085.
You could run this workflow to see the difference in consume-artifact logs:
https://gist.github.com/WeiTang114/ed3813ea801180c3cf860a3caa42eac9
Previously, in the workflow processing, the global artifacts in the scope (stepsCtx.scope["workflow.outputs.artifacts.XXX]) are updated only by the call of woc.addOutputsToScope("workflow", woc.wf.Status.Outputs, stepsCtx.scope) in executeSteps(). Inside the "steps", the scope will not be updated unless there is another nested "steps" and executeSteps() is called.
If a stepGroup inside the deepest "steps" has a generator step which tries to overwrite the global artifact, it would only write to woc.wf.Status.Outputs.Artifacts[i] = art (in addArtifactToGlobalScope() called by addOutputsToScope called by processNodeOutputs in the loop in executeSteps()). There will be an info log: overwriting workflow.outputs.artifacts.global-art: {global-art  <nil>  {<nil> http://storage.googleapis.com/XXXX/artifact-passing-njfhl/artifact-passing-njfhl-4212700704/my-art.tgz <nil> <nil> <nil> <nil>}  <nil>}"  which is somehow misleading, as it does not overwrite the global artifact in stepsCtx.scope.
Because the global artifacts are resolved from stespCtx.scope, (stepGroup, err := woc.resolveReferences(stepGroup, stepsCtx.scope) in executeStepGroup()), but not woc.wf.Status.Outputs.Artifacts,  a reader step right after the generator step may resolve wrong global artifact from the scope.
This PR makes addArtifactToGlobalScope() also overwrite the global artifact into scope to fix the problem described above.
I'd like to mention that the new behavior solve the problem in my use case (sequential workflow loops). If there are many parallel steps writing to the same global artifact, and if the desired behavior is "get the latest generated global artifact", we would need to further improve the implementation, e.g. by checking overwriting by generated timestamp. The problem is also discussed in https://github.com/argoproj/argo/issues/1085.

@WeiTang114 thanks for the fix and sorry for the delay in the review. We are turning our attention back to workflows (from CD).


How to configure Local Oracle DB to auto update?

Hi @jeremylong ,
I am running the dependency analyzer by configuring a local Oracle. Initial set up of changing the Connection_string and the credentials are done. I have also modified the code to run initial_oracle.sql script. But if I just want to autoupdate like how it happens with the h2 db rather than re creating the db structure every time, it seems not to work.
I see the following error in the logs -  "Unable to update Cached Web DataSource, using local data instead. Results may not include recent vulnerabilities."
Can you please point out if i am missing anything?
Also, Is there a Doc where I can refer to configure a local Oracle DB instead of h2 DB?
Thanks

The only limited documentation can be found here: https://jeremylong.github.io/DependencyCheck/data/database.html
If after looking at that you are still having issues we would need to see the full log rather then just the console output to assist further. (i.e. $ dependency-check.sh --updateOnly --log odc.log ...(


Azure Mesos template cluster spams console with complaints about nodes not being marked as preemptable

The Mesos batch system seems to expect its nodes to be tagged in Mesos with "preemptable" as either true or false. If not, it spams my logs with a lot of this:
WARNING:toil.batchSystems.mesos.batchSystem:Slave not marked as either preemptable or not. Assuming non-preemptable.
WARNING:toil.batchSystems.mesos.batchSystem:Slave not marked as either preemptable or not. Assuming non-preemptable.
WARNING:toil.batchSystems.mesos.batchSystem:Slave not marked as either preemptable or not. Assuming non-preemptable.
WARNING:toil.batchSystems.mesos.batchSystem:Slave not marked as either preemptable or not. Assuming non-preemptable.

Can it be made to be a little more quiet? I only have 4 slaves, and these messages are flooding my console output, and I don't care about them because I'm running in a cluster where nothing is ever going to be preempted by anything anyway.

I'm running in a cluster made with the default Azure Mesos template from the Toil repo. If Toil expects all Mesos nodes to have this info attached, Toil ought to be attaching it to all the nodes that it itself makes through its official template. It looks like maybe nobody tested the Mesos template after adding preemptability as a consideration?

If you implement 2, do you still need 1?

IMO, you'd want 1 anyways for people who are running Mesos not through the toil/cgcloud scripts (i.e., most of the installed Mesos userbase).

I added that warning because at some time in the past I broke the code that sets up that attribute in cgcloud and didn't have any indication in Toil that I did. OTOH, I also see that the flooding is an issue.

I think https://github.com/adamnovak/toil/commit/6cbc4aac032eb577b091b7562d1842545230ecfb ought to solve point 2; it did when I ran it manually on all my worker nodes.


README

The README.rst claims that some features are broken outside the notebook. Is this still valid? If so, could we document the features?

I also want to ask this question.

I think in general it would be good to update the README.rst. I don't know if anyone feels like volunteering for that, @QCoDeS/core?

related to #839 too


Update default 404 page

refs. https://github.com/TryGhost/Ghost/issues/10899

removed broken ghost "illustration" from default frontend 404 page
refined style of 404 page to be more theme agnostic

Screenshot of updated 404 page:


redis_cache backend

@czue will use this branch on ansible to update staging local vars so i can actually deploy. no need to merge until redis has actually passed QA

:+1:

g2g


fixing kim dev atlases

Description
What is this PR

[x] Bug fix
[ ] Addition of a new feature
[ ] Other

Why is this PR needed?
The kim_dev atlases fail one of our validation functions as the mesh and the annotations layers don't overlap.
What does this PR do?
References
Fixes #303
How has this PR been tested?
Atlases were regenerated and checked visually
Is this a breaking change?
No
Does this PR require an update to the documentation?
No
Checklist:

[x] The code has been tested locally
[ ] Tests have been added to cover all new functionality (unit & integration)
[ ] The documentation has been updated to reflect any changes
[ ] The code has been formatted with pre-commit

Orientation looks OK (root mesh only)


Fix links in registry folder view

Fixes issue introduced in #60

Thanks for the quick fix!
This is the sort of thing I hope we can protect against with tests

@lucacasonato I think there's another link issue with the breadcrumbs too. Try clicking on "std" from https://deno.land/std/bundle/

Just found that too. I'll submit a fix in a few minutes.
On Fri, 25 Oct 2019 at 20:12, Ry Dahl<EMAIL_ADDRESS>wrote:

@lucacasonato https://github.com/lucacasonato I think there's another
link issue with the breadcrumbs too. Try clicking on "std" from
https://deno.land/std/bundle/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/denoland/deno_website2/pull/62?email_source=notifications&email_token=AB3XNVL7KE3GFHRLZRU6Y7TQQMZI5A5CNFSM4JFGUSYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECJEKFY#issuecomment-546456855,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3XNVOYUU5PCEZDZQVBZKLQQMZI5ANCNFSM4JFGUSYA
.


numba 0.55.0 on defaults doesn't constrain numpy as expected

When using Conda to create an environment with both Numba and NumPy, I notice that the linux-64 numba 0.55.0 package hosted on defaults doesn't respect the max version constraint for NumPy like the conda-forge package does; this means it is possible to create an environment with numba 0.55 and numpy 1.22, which results in an ImportError when trying to import numba:
$ mamba create -n test numba=0.55 numpy=1.22
...
  + numba                0.55.0  py310h00e6091_0      pkgs/main/linux-64       Cached
  + numpy                1.22.1  py310h454958d_0      conda-forge/linux-64     Cached

If we limit the environment creation to only use conda-forge, this constraint is properly respected:
$ mamba create --override-channels -c conda-forge -n test numba=0.55 numpy=1.22
...
Encountered problems while solving:
  - package numba-0.55.0-py37h2d894fd_0 has constraint numpy >=1.18,<1.22 conflicting with numpy-1.22.0-py310h454958d_0

Is this different behavior between the two packages expected? I notice that before, the defaults hosted packages seemed to respect this constraint:
$ mamba create --override-channels -c defaults -n test numba=0.54 numpy=1.21
...
Encountered problems while solving:
  - package numba-0.54.1-py37h51133e4_0 has constraint numpy >=1.17,<1.21 conflicting with numpy-1.21.2-py310h20f2e39_0

For context, I observed this issue in https://github.com/dask-contrib/dask-sql/pull/383 - here is an example of potential downstream failures that can occur as a result of this.

@charlesbluca thank you, I can confirm this, but I do need to add -c conda-forge for it to resolve as 1.22 isn't available from defaults at the time of writing:
conda create -c conda-forge -n testxyz numba=0.55 numpy=1.22

Interestingly enough the build from the numba channel may be correct. Here is what I get when I try to force it:
 💣 zsh» conda create -c conda-forge -n testxyz numba::numba=0.55 numpy=1.22                         :(
Collecting package metadata (current_repodata.json): done
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: |
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.
failed

UnsatisfiableError: The following specifications were found to be incompatible with each other:

Output in format: Requested package -> Available versions

Package pypy3.7 conflicts for:
numba::numba=0.55 -> llvmlite[version='>=0.38.0rc1,<0.39'] -> pypy3.7[version='7.3.3.*|7.3.4.*|7.3.5.*|7.3.7.*|>=7.3.3|>=7.3.4|>=7.3.5|>=7.3.7']
pip -> python[version='>=3.6'] -> pypy3.7[version='7.3.3.*|7.3.4.*|7.3.5.*|7.3.7.*|>=7.3.7|>=7.3.5|>=7.3.3']

Package numpy conflicts for:
numpy=1.22
numba::numba=0.55 -> numpy[version='>=1.18,<1.22']

Package pip conflicts for:
numba::numba=0.55 -> python[version='>=3.7,<3.8.0a0'] -> pip
pip

  70.96s user 2.29s system 89% cpu 1:21.71 total

The error message is somewhat confusing however...

@charlesbluca I have forwarded this to the team that does defaults.

@esc should this be closed?

@stuartarchibald only when the package has been fixed, I would say?

I just tried this and the package from defaults will happily install alongside a Numpy 1.22 which we don't support:
  numba              pkgs/main/osx-64::numba-0.55.0-py310hc081a56_0
  numpy              conda-forge/osx-64::numpy-1.22.2-py310hfbbbacf_0

During an OOB conversation with a colleague, I was pointed towards:

During an OOB conversation with a colleague, I was pointed towards:
https://github.com/AnacondaRecipes/repodata-hotfixes
This may be a good way to constrain the package data.

xref https://github.com/conda-forge/numba-feedstock/issues/90


Audio stop play when you switch to Functions

Describe the bug
When I play an audio in live mode (button), then I switch to Functions and click on any function (scene, script...), or when i want to create new, the music stops.
To Reproduce

Add button with audio in Console
Go to Live mode
Click on button to play a Audio
Switch to Functions tab and do something

Expected behavior
Audio should continue
Desktop (please complete the following information):

OS: Ubuntu 22.04 (tested also on Windows 11)
QLC+ Version 4.12.4

I made some tests on Ubuntu 22.04 with QLC+ 4.12.5-GIT. Audio stops after a few clicks in the function manager. Sometimes crash at first click selecting any function manager element, sometimes crash after 3, 4, 5 or 6 clicks.

Switch to Functions tab and do something

Please define "do something"
If you click on the same audio function then yes, audio is stopped.
If you click on any other DMX function then it works for me. I just tested and no crash

do something
click on any function (scene, script, efx...) you don't need to do any change. Just click to see a detail.
Its not crashing. Its just stop an audio playing in Virtual console (live mode).
If this not help. I will share you project file with audio file on monday. Also I can record video what exactly I am doing.


CMake: support ninja as a build backend

Close #621.
Benchmark between make and ninja build for kvrocks can be found in #625.
TL;DR: The benchmark shows that ninja is slightly slower than make build in clean build, but has huge advantages in incremental build, which is very friendly to kvrocks developers who need to do frequent incremental builds.
So in this PR, kvrocks still use make by default, but the problem that blocks ninja backend to successfully build in cmake is fixed and now build.sh has a --ninja option to enable ninja.

Shall we add a matrix to test build with ninja in CI workflow?

I think we could add a ninja job to the daily ci now, but since the workflows haven't been refactored, it might not be easy to use a matrix, which is described in #572, and I will make a PR to refactor workflows later.

Thanks for your contribution!

Hi @PragmaTwice Currently daily CI is failed, please have a look,
one tips for debugging daily CI on github, you can remove the rule of daily https://github.com/apache/incubator-kvrocks/blob/unstable/.github/workflows/daily-ci.yaml#L21 in you branch, you can submit a PR after there is no error report.

Actually I think whether we should running a daily CI or just run it every PR - with Apache INFRA we may have enough resource to run CI now. At least we may try to trigger daily CI when related files touched (however, "related files" can be any source files and thus it becomes a CI runs for every PR).

Hi @tisonkun it will cost much time if we run also daily CI for every PR, i think it is not friendly for contributors.

At least we may try to trigger daily CI when related files touched (however, "related files" can be any source files and thus it becomes a CI runs for every PR).

This idea sounds good, could we support this feature?

At least we can add:
name: Daily CI
on:
  pull_request:
    paths:
      - ".github/workflows/daily-ci.yaml"
  schedule:
    - cron: '0 1 * * *'
  workflow_dispatch:

If I find can find some spare time I'll make some investigation. But feel free to do it yourself.

Actually I think whether we should running a daily CI or just run it every PR - with Apache INFRA we may have enough resource to run CI now. At least we may try to trigger daily CI when related files touched (however, "related files" can be any source files and thus it becomes a CI runs for every PR).

I think we could use ccache and actions/cache to accelerate the build procedure in CI.

Hi @PragmaTwice Currently daily CI is failed, please have a look, one tips for debugging daily CI on github, you can remove the rule of daily https://github.com/apache/incubator-kvrocks/blob/unstable/.github/workflows/daily-ci.yaml#L21 in you branch, you can submit a PR after there is no error report.

Sorry for that, seems there is no pre-installed ninja in the virtual environment, some apt install is needed.

name: Daily CI
on:
  pull_request:
    paths:
      - ".github/workflows/daily-ci.yaml"
  schedule:
    - cron: '0 1 * * *'
  workflow_dispatch:

thanks @tisonkun cool, i am not familiar CI, but it seems it is a light and useful way to resolve our problem.
@PragmaTwice please don't say sorry, you already have done much for Kvrocks. Just let's fix it, we can adopt @tisonkun advise as above to check.
PS: In redis repo, maintainers can trigger manually daily CI, maybe it also is a way for us.

In redis repo, maintainers can trigger manually daily CI, maybe it also is a way for us.

We can also trigger the daily CI manually since workflow_dispatch is added to https://github.com/apache/incubator-kvrocks/blob/unstable/.github/workflows/daily-ci.yaml#L24.
Just like this, click the Run workflow button:

found, cool, thanks @PragmaTwice


Server stops responding when player logs out.

What is your Quests version / build number (do not say "latest")?
Quests v5.1.4-b507, but it was happening on a previous version as well. Tried updating to fix the issue but didn't work.
Describe the problem and how to replicate it.
Randomly when a player logs out and I'm running Quests the server will stop responding and start spitting errors in console until it stops randomly but the server does not respond again until killed and restarted. I have tried regenerating Quests/config.yml and Quests/data (folder) but this didn't help either.
latest (5).log
Scroll down to 10:13.
Any console errors to share?
See log @ 10:13.

[10:13:31] [Server thread/INFO]: bicudoti lost connection: Timed out
[10:13:41] [Paper Watchdog Thread/ERROR]: --- DO NOT REPORT THIS TO PAPER - THIS IS NOT A BUG OR A CRASH  - 1.21.1-119-7cd4f2c (MC: 1.21.1) ---
[10:13:41] [Paper Watchdog Thread/ERROR]: The server has not responded for 10 seconds! Creating thread dump
[10:13:41] [Paper Watchdog Thread/ERROR]: ------------------------------
[10:13:41] [Paper Watchdog Thread/ERROR]: Server thread dump (Look for plugins here before reporting to Paper!):
[10:13:41] [Paper Watchdog Thread/ERROR]: ------------------------------
[10:13:41] [Paper Watchdog Thread/ERROR]: Current Thread: Server thread
[10:13:41] [Paper Watchdog Thread/ERROR]: 	PID: 50 | Suspended: false | Native: false | State: WAITING
[10:13:41] [Paper Watchdog Thread/ERROR]: 	Stack:
[10:13:41] [Paper Watchdog Thread/ERROR]: 		java.base@21/jdk.internal.misc.Unsafe.park(Native Method)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		java.base@21/java.util.concurrent.locks.LockSupport.park(LockSupport.java:221)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		java.base@21/java.util.concurrent.CompletableFuture$Signaller.block(CompletableFuture.java:1864)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		java.base@21/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3780)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		java.base@21/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3725)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		java.base@21/java.util.concurrent.CompletableFuture.waitingGet(CompletableFuture.java:1898)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		java.base@21/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2072)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		Quests-5.1.4.jar//me.pikamug.quests.player.BukkitQuester.saveData(BukkitQuester.java:3630)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		Quests-5.1.4.jar//me.pikamug.quests.listeners.BukkitPlayerListener.onPlayerQuit(BukkitPlayerListener.java:948)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		com.destroystokyo.paper.event.executor.asm.generated.GeneratedEventExecutor924.execute(Unknown Source)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		org.bukkit.plugin.EventExecutor$2.execute(EventExecutor.java:77)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:80)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:70)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		io.papermc.paper.plugin.manager.PaperEventManager.callEvent(PaperEventManager.java:54)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		io.papermc.paper.plugin.manager.PaperPluginManagerImpl.callEvent(PaperPluginManagerImpl.java:131)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:628)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.players.PlayerList.remove(PlayerList.java:605)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.network.ServerGamePacketListenerImpl.removePlayerFromWorld(ServerGamePacketListenerImpl.java:2107)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.network.ServerGamePacketListenerImpl.onDisconnect(ServerGamePacketListenerImpl.java:2087)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.network.ServerCommonPacketListenerImpl.disconnect0(ServerCommonPacketListenerImpl.java:397)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.network.ServerCommonPacketListenerImpl.disconnect(ServerCommonPacketListenerImpl.java:388)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.network.ServerCommonPacketListenerImpl.disconnect(ServerCommonPacketListenerImpl.java:345)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.network.ServerCommonPacketListenerImpl.lambda$handleKeepAlive$0(ServerCommonPacketListenerImpl.java:141)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.network.ServerCommonPacketListenerImpl$$Lambda/0x00007f5c9f721200.run(Unknown Source)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.util.thread.BlockableEventLoop.lambda$submitAsync$0(BlockableEventLoop.java:60)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.util.thread.BlockableEventLoop$$Lambda/0x00007f5c9f721420.get(Unknown Source)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		java.base@21/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.TickTask.run(TickTask.java:18)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.util.thread.BlockableEventLoop.doRunTask(BlockableEventLoop.java:151)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.util.thread.ReentrantBlockableEventLoop.doRunTask(ReentrantBlockableEventLoop.java:24)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.MinecraftServer.doRunTask(MinecraftServer.java:1535)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.MinecraftServer.doRunTask(MinecraftServer.java:201)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.util.thread.BlockableEventLoop.pollTask(BlockableEventLoop.java:125)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.MinecraftServer.pollTaskInternal(MinecraftServer.java:1512)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.MinecraftServer.pollTask(MinecraftServer.java:1505)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.util.thread.BlockableEventLoop.managedBlock(BlockableEventLoop.java:135)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.MinecraftServer.managedBlock(MinecraftServer.java:1464)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.MinecraftServer.waitUntilNextTick(MinecraftServer.java:1471)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1316)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:329)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		net.minecraft.server.MinecraftServer$$Lambda/0x00007f5c9ccba2b0.run(Unknown Source)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		java.base@21/java.lang.Thread.runWith(Thread.java:1596)
[10:13:41] [Paper Watchdog Thread/ERROR]: 		java.base@21/java.lang.Thread.run(Thread.java:1583)

If applicable, can you provide an example quest from quests.yml?
No response

Now I'm seeing this on startup. [17:40:00 WARN]: Couldn't look up profile properties for 71f17181-c618-4e7e-aa31-9d0d0d1fba1c
com.mojang.authlib.exceptions.MinecraftClientException: Failed to read from https://sessionserver.mojang.com/session/minecraft/profile/71f17181c6184e7eaa319d0d0d1fba1c?unsigned=false due to Read timed out
at com.mojang.authlib.minecraft.client.MinecraftClient.readInputStream(MinecraftClient.java:108) ~[authlib-6.0.54.jar:?]
at com.mojang.authlib.minecraft.client.MinecraftClient.get(MinecraftClient.java:57) ~[authlib-6.0.54.jar:?]
at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fetchProfileUncached(YggdrasilMinecraftSessionService.java:201) ~[authlib-6.0.54.jar:?]
at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fetchProfile(YggdrasilMinecraftSessionService.java:171) ~[authlib-6.0.54.jar:?]
at com.destroystokyo.paper.profile.PaperMinecraftSessionService.fetchProfile(PaperMinecraftSessionService.java:35) ~[paper-1.21.1.jar:1.21.1-119-7cd4f2c]
at org.bukkit.craftbukkit.profile.CraftPlayerProfile.getUpdatedProfile(CraftPlayerProfile.java:180) ~[paper-1.21.1.jar:1.21.1-119-7cd4f2c]
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.base/java.lang.Thread.run(Thread.java:1583) ~[?:?]
Caused by: java.net.SocketTimeoutException: Read timed out
at java.base/sun.nio.ch.NioSocketImpl.timedRead(NioSocketImpl.java:278) ~[?:?]
at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:304) ~[?:?]
at java.base/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:346) ~[?:?]
at java.base/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:796) ~[?:?]
at java.base/java.net.Socket$SocketInputStream.read(Socket.java:1099) ~[?:?]
at java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:489) ~[?:?]
at java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:483) ~[?:?]
at java.base/sun.security.ssl.SSLSocketInputRecord.bytesInCompletePacket(SSLSocketInputRecord.java:70) ~[?:?]
at java.base/sun.security.ssl.SSLSocketImpl.readApplicationRecord(SSLSocketImpl.java:1461) ~[?:?]
at java.base/sun.security.ssl.SSLSocketImpl$AppInputStream.read(SSLSocketImpl.java:1066) ~[?:?]
at java.base/java.io.BufferedInputStream.fill(BufferedInputStream.java:291) ~[?:?]
at java.base/java.io.BufferedInputStream.read1(BufferedInputStream.java:347) ~[?:?]
at java.base/java.io.BufferedInputStream.implRead(BufferedInputStream.java:420) ~[?:?]
at java.base/java.io.BufferedInputStream.read(BufferedInputStream.java:399) ~[?:?]
at java.base/sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:827) ~[?:?]
at java.base/sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:759) ~[?:?]
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1690) ~[?:?]
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1599) ~[?:?]
at java.base/java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:531) ~[?:?]
at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:307) ~[?:?]
at com.mojang.authlib.minecraft.client.MinecraftClient.readInputStream(MinecraftClient.java:84) ~[authlib-6.0.54.jar:?]
... 9 more

I know it says "look for plugins here" but that merely describes what was happening at the time of crash; it does not indicate that Quests is the cause. It's more likely that you have other plugin(s) slowing down your server and disk I/O. Use a performance profiler like spark (not affiliated) to see what needs to be addressed.
The startup error is likely from using third-party launchers. Try this guide https://minecrafthopper.net/help/hosts-file/

Each time this happens it shows the same thread dumps with Quests in them, which at the very least tells me that if it's not Quests then whatever it is is happening at the same time Quests is doing something. I don't think I use a third party launcher and I don't know what third party launchers are or why people would use them - looks like, to allow cracked clients? I run paper and currently am on a host provider that uses pterodactyl. I honestly don't think Quests is the culprit, but was hoping for some direction or advice on to why this could be happening. I've since removed Quests and the issue has stopped. I was using quests for over around 2 months before this started happening.


Remove the @DatabasePublished property wrapper

The @DatabasePublished property wrapper was ill-designed, and has been removed.
The view model of the demo application has been rewritten with a plain ValueObservation publisher.
Our goal is to eventually bring something similar to @FetchRequest, when it becomes possible.

Thanks for rewriting the demo! I find it the best way to figure out how things work :)

Thank you @bellebethcooper!


fix: run treefmt from shell env

Problem
treefmt fails in CI
Solution
It's failing because it can't find ocamlformat, etc. So we run it with nix develop to ensure all required deps are there.

I'm not sure why it formats the nix files, aren't we  using nixfmt already?

Yes, but the files should have been formatted already :thinking:

@d4hines I fixed this by creating a custom formatter that just wraps all the formatters we need with treefmt :sweat_smile: we can revert that  particular change, but using git to do the diff seems more robust for CI in either case.


057-pip-bi: Increase number of tries to find a suitable PIP INT tile

This PR is aimed at solving the stability issue of the 057-pip-bi fuzzer reported in issue #661.
Currently the number of tries was set to 3. In this case to find the right tile needed to successfully route through the specified BI PIPs the number of attempts needs to be higher (sometimes 4-5).
Added 10 to be on the safe side. This doesn't affect run time much anyway.

The CI failed on 053-pip-ctrlin which is addressed in #849

I know that CI is red, but this is because of the instability of 053 which is subject to #849.
I tested this fuzzer locally for more than 50 iterations and it worked fine after the fix.
Before it failed after 2-3 iterations.
If we merged this it would leave us with only 41 being disabled.


I think the deployed package includes the test models

I was linting  a project which uses this package, and got a curious error:
RuntimeError: File C:\Users\...\data_warehouse\dbt_packages\dbt_artifacts\integration_test_project\models\incremental.sql was not found in dbt project

Now this is evidently a sqlfluff problem, but it's failing to find a file, which is a test file within dbt artifacts. I don't think this file should even be present or rendering within the host project.
Sure enough when I check the dbt_packages folder I see the test project included in the installed package, which I suspect is why dbt is trying to compile it along with the rest of the project.
Is there something in the dbt package config which we should update so that the test project isn't included in the eventual parse DAG of a host project?

Ignore me - this isn't an issue with dbt_artifacts this is an issue with me...


Fix nightly version modification

Adding .dev to a version number actually makes the version LESS than the published version.
e.g. 0.1.0b4 > 0.1.0b4.dev20160920
In this fix, we would modify 0.1.0b4 to 0.1.0b4+1.dev20160920
and 0.1.0b4+1.dev20160920 > 0.1.0b4.dev20160920

@BurtBiel Updated the PR to remove the pattern check for the last number.
Now, I add +1.dev to the end of the version string.


sys/linux: wireguard support

WireGuard is new tunnel for linux:
https://www.wireguard.com/
Hopefully soon lands in kernel:
https://patchwork.kernel.org/patch/10647355/
Official docs:
https://www.wireguard.com/papers/wireguard.pdf
Need descriptions when lands (or earlier).

We will need to setup 2 net devices of type wireguard, connect them with each other and setup public/private keys for peers.
@zx2c4 are there any docs on netlink interface?
And then there is also some new L5 packet format inside of UDP, need to add that to vnet.txt.

Yes!

FTR lots of relevant discussions here:
<EMAIL_ADDRESS>

I think we may consider this as fixed now. No known actionable items remain.

Indeed lots of good coverage now.


Added hint about characters in kfctl path

Thanks to @deepdad for suggesting this change in PR https://github.com/kubeflow/website/pull/1074

This change is

/assign @abhi-g

Friendly ping @abhi-g


Oni crashes on Linux Mint 18.3

After building Oni on linux mint 18.3 I am unable to type more than 20 or so characters without oni hanging. There is no debug output, so I don't have much to go on. Basically, it becomes less and less responsive as I type until about 20 characters in it just hangs. This happens every time on the latest master built from source, but not when using the 3.2 deb package.
To reproduce on Linux Mint 18.3 "Sylvia" using VMware workstation player 14.1.1:

build oni using the instructions here: https://github.com/onivim/oni/issues/1460
launch oni from the terminal
start typing

Sorry for the low information issue, but since there is no debug output to indicate anything is going wrong I'm not sure what else to include.

The latest .deb build for 0.3.2 also exhibits this behavior.

It turns out this was a problem with OpenGL and VMWare, and the issue was resolved by setting an environment variable in my .bashrc:
export SVGA_VGPU10=0

Stack Overflow issue: https://stackoverflow.com/questions/47150110/error-context-mismatch-in-svga-sampler-view-destroy-running-gui-programs-on-ub


Resolves #336 chore/CI: only test packaged app

Also, looking at commit hygiene: @hunterlester @bochaco I think, we dont want resolves as the first part of the commit title.
I think we should have the chore/ci as the first part. And if we want resolves it should be part of the commit message body (on another line), after the title.
Thoughts?

Yes I think so, since that's the format we'll need for the automatic changelog generator


[Feature] Strapi App as service ?

Upvote it here
https://feedback.coolify.io/posts/29/service-strapi
Github issues are for bugs and problems in coolify. For new features, we maintain it at https://feedback.coolify.io

@vasani-arpit the link is not working, where we can upvote for this now?


Build process should also create minified version of gh-emoji

What do you think @zzarcon?

Totally agree on that

Cool! Will work on that after autocomplete in demo is done :)

Great! Let me know if you are not sure about how to do it

Closed with #9


TypeScript support

Hey,
Thanks for your hard work on this great animation library!
I wondered if there are any plans to make type definitions available in order to use it properly in TypeScript based projects?

@itpropro I've made a tsconfig.json which generates a typescript/index.d.ts file, please test latest master and provide feedback.
Thanks

2.1.3 now has Typescript TYPES.

Hi, thanks for the hard work on this awesome library.
However, I have some problems for compiling it on an Angular project.
It could not resolve de dependencies from svg-path-commander :

If I replace the full js path by svg-path-commander it's working
There is another error on the Version.d.ts :

For reproducing I have just made a ng new test-kutejs, installed kute.js package and imported it in the app.component.ts like this :
import KUTE from 'kute.js';

I'm currently working on SVGPathCommander and KUTE.js, so feel free to provide any suggestion in regards to TypeScript, I'm still new to this.

If I replace the full js path by svg-path-commander it's working

@j-vallet-onesys can you please explain what do you mean?

I have replaced this import statements like this in svgMorph.d.ts in the node_module directory of my app and there is no more errors :

I'm not really used to compile javascript application descriptions for typescript too, but I will make some tests on my side too.

@j-vallet-onesys
Please update to the latest and report any issue.

I attempted to add the library to my Angular project, but the problem above persisted.

KUTE.js codebase need to be reworked with Typescript. I'm planning a major rework and major version release in the next couple of weeks, I already have SVGPathCommander done.


Upgrade to deploy-pages and v4 broken

Describe the bug
They fail with "Error: HttpError: No artifact_url provided"
See https://github.com/actions/deploy-pages/issues/284

resolved in cee78bc61753606e461c85611461f6eecc7a3b85


Gameobject Flicker Issue (Material)

So I have been trying out this shader for a while and came across some issue. When I changed the material to the corresponding shader, it has this kind of flickering, where the trees pop in and out, although the trees are present because I can collide with their colliders except they're not being rendered, they just flicker everywhere, it also happens with objects that I just changed the material to PSX/Lit,. Here's the video and pictures for additional information.
https://github.com/pastasfuture/com.hauntedpsx.render-pipelines.psx/assets/104110725/b1dc7043-47e6-4109-84c7-db081494f7e1
https://github.com/pastasfuture/com.hauntedpsx.render-pipelines.psx/assets/104110725/1944ef2a-04a0-4c12-9772-c6addcae3d74

any fix to this? thank you!

Interesting! I’ve never seen this specific bug before - but I just noticed in your material screenshot you have gpu instancing on - can you try turning that off to see if the bug goes away? I think gpu instancing may be bugged. If we can confirm the issue is gpu instancing I can then look at fixing that

it did go away! the objects stop flickering now, thank you very much and will be looking forward for the fix! have a good one!

Fixed on master as of e779c1c2af4a4a1fc2b98807063cc547ea49877d