Readme tutorial outdated

I'm currently working on a university project. But im struggling with adding my one device to the Chip.
For the project I need to get a pwm working, which is a nice coincidence.
Anyway with the current state of the Rocket-Chip, the tutorial is not working.
I understand that the rocket-chip is transitioning from TileLinkIO to TileLinkIO2 atm, so it's probably not the best idea to updated the Tutorial right now.
But like I said we are struggling to make it work, so any help or information would be very much appreciated.

I'm not sure about this tutorial, but have you looked at other example projects using the current rocket-chip? You could see
https://github.com/sifive/sifive-blocks/blob/master/src/main/scala/devices/pwm/PWMPeriphery.scala
That example uses rocket-chip's TLRegisterRouter to make a simple register-controlled device (TLPWM), then uses Periphery traits to hook it up into the overall SoC. This is basically what this tutorial describes, but with updated syntax that is known to work with current rocket-chip.

I have problem to understand the process of how to add an accelerator!Can anyone help me and tell me the steps i have to do, the files i have to change?

In the current state of the rocketchip, it does not work out of the box. You can read about it in the issue here.
The repo itself tells you how to work around the problems though. It will show you how to get the build in accelerators to work. https://github.com/seldridge/rocket-rocc-examples/
Note that the repository tells you to use an older commit of the rocket-chip repository, but you can actually use the version pointed to by this project-template repository.
Once you get the build in once to run you can try implementing your own instead, the RoCC interface is actually documented pretty well here.
You'll find the build in accelerators here rocket-chip/src/main/scala/rocket/rocc.scala, other then that you only have to change the mapping of the custom0-3 opcodes to your Accelerator here: rocket-chip/src/main/scala/coreplex/Configs.scala
I myself have some problems getting my own one to run, so so far i edited the build in ones to fit my purpose, so you might one to fall back to that, too. Other then that i wish you the best of luck, you'll need it ;).

I've updated this repo to track (close to) the latest master of rocketchip and added better documentation. Hopefully things should be more understandable now.


WIP: Clean up thread creation parameters

This is WIP, or I can split this into multiple PRs. Also, I've only tested this building core, not the examples and tests yet. I'll update those if people are happy with this.
What I've done so far:

Add initial_state and run_now to thread_init_data
Remove initial_state and run_now from all the create_thread/work functions (thread pool, schedulers, thread queues, wrappers in create_thread/work.hpp)
Disable all register_* overloads except for register_thread/work which take a pool and thread_init_data (I'll hide these behind a real compatibility option, I've just disabled them now to keep things simple)
Use the reduced set of register_thread/work in the core library
Add make_thread_function{,_nullary} for creating appropriate thread functions (the caller of register_* is responsible for conversion

To do for this PR:

[x] Add a real CMake compatibility option
[x] I won't do this in this PR: Reduce set of overloads even further? For this I would be tempted to go with only one overload: thread_id_type register_thread(thread_init_data, thread_pool_base = /* default */, error_code = /* default */). The reason for this is that I'm not sure the register_thread/work distinction has been followed very well. There were cases of register_thread with run_now = false and vice versa. I think it may be clearer to just have one version, with the returned thread id being the invalid thread id if run_now = false. What do other people think about this? I'm happy to go either way as long as people find the behaviour clear.

Edit: I'll clean this PR up and leave the following for a follow-up PR:

Extend the use of thread_init_data to future_data, async/post_launch_policy_dispatch, and whatever else is passing priorities etc. as separate function arguments.

There is actually a use for not quite going all in with thread_init_data above the register_* functionality: the function itself might be known quite late. E.g. futures_factory wraps the actual function to call. So we may want the function or the launch parameters separate from thread_init_data. That way we can pass launch parameters without a function attached to it.

I think I'm done with this PR for this round, modulo build and inspect errors that may still come up. I'll leave cleaning up the launch parameters higher up than register_thread to a second PR. I now left register_thread and register_work as non-deprecated functions (but they only have two overloads each). register_thread and register_work set run_now to the correct value. If one wants different behaviour one can still directly call create_thread/work.

Just an observation: currently almost all thread functions are explicitly wrapped by a make_thread_function_nullary(). Wouldn't it be possible to make that the default to reduce the amount of code users have to write?

Yes, that's a fair point. thread_init_data could easily get a constructor for functions with the signature void(). I quite like that the conversion is explicit on the calling side though, and in this case users = us mostly. That said, I can definitely add an overload if you'd like.


Question regarding subscription without Mandate Up Front

So our main idea is to give some certain users a subscription plan for customizable period of time for free (not to oblige them to specify the credit card details).
The first idea was to create a subscription record in subscriptions table to with custom trial_ends_at and chosen plan. The question is won't it break something (e.g. cashier:run command)?
Thanks in advance!

Cashier Mollie support this using generic trials.


Cannot find type definition file for 'popper.js'.

On a fresh ng2 install and doing all the steps in the readme, I get this error when running ng build or ng serve:
ERROR in S:/01.Git/java/microservice_skeleton/ui/jmss-ui/node_modules/ng2-semantic-ui/components/util/positioning.service.d.ts (1,1): Cannot find type definition file for 'popper.js'.

Same problem:
ERROR in F:/Kolibri/frontend/node_modules/ng2-semantic-ui/components/util/positioning.service.d.ts (1,1): Cannot find type definition file for 'popper.js'.

Have just released 0.6.4 onto npm, that includes a hotfix for this issue. Sorry for the inconvenience!
$ npm update ng2-semantic-ui


Feature/159 update search button

Related Issues:

EQ-159

Main Changes:

Added a confirmation modal  dialog to the clear search button.
Added a clear search button to the top of the filters
Add a cypress test for this new functionality
Updated clear search button to component

Updated code as per the suggestion and added a Button component, then used it for Clear search and in ConfirmationModalFooter.
In ConfirmationModal I have added ConfirmationModalFooter and, I used it in ClearSearchModal. For the next PR I will update it in DownloadModal.
The reason why the test case failing, there might be API response getting slow, otherwise it might be due to the options available given the data I have in my local database.


Move rich card from Adaptive Cards to native HTML

Background
We use Adaptive Cards to simplify composition of rich card. There are number of reasons we would like to move away from Adaptive Cards:

Cosmetics

Adaptive Cards cannot be styled to remove pictures padding

Users on minimal build will be able to use rich card

Minimal build does not contains Adaptive Cards, so they cannot use rich card too

We have limited number of rich cards

Note to fixer

[ ] Animation card
[ ] Audio card
[ ] Hero card
[ ] OAuth card (variation of sign-in card)
[ ] Receipt card
[ ] Sign-in card
[ ] Thumbnail card
[ ] Video card

Moved from P1 to P2 because without this feature, everything still works fine.

@corinagum should we reconsider this into 4.6 or 4.7 when Marc is redesigning our UI?

@compulim Yeah, let's bring this up at our 4.6 planning meeting this week.


Search for plugins in config_base

instead of the hardcoded ~/.flexget/plugins. This effectively allows to
put plugins in $XDG_CONFIG_HOME/flexget/plugins.

Cool, thanks! Perhaps we should put a little note about this in upgrade actions since it might affect a few people.


Add binarize as a plotting transform

Reference Issues/PRs
Fixes #230
What does this implement/fix? Explain your changes.
Add binarize as a plotting transform
Any other comments?

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@324764b). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master     #233   +/-   ##
=========================================
  Coverage          ?   85.99%
=========================================
  Files             ?       31
  Lines             ?     1899
  Branches          ?        0
=========================================
  Hits              ?     1633
  Misses            ?      266
  Partials          ?        0

Impacted Files
Coverage Δ

graspy/plot/plot.py
52.29% <100%> (ø)

Continue to review full report at Codecov.

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

Thanks for the PR @Kikiwink !


hive/metrics: Adds hive degraded status labeled by modules

Adds cilium_hive_degraded_status metric to count degraded health status levels of Hive components labeled by modules. It improves the monitoring effectiveness by exposing the affected modules instead of the general count.
Fixes: https://github.com/cilium/cilium/issues/34823
Adds `cilium_hive_degraded_status` metric to count degraded health status levels of Hive components labeled by modules. ```

Grafana
If there are no cells degraded, the metric will have no data to reduce the metrics cardinality.

/test

Please review but do not merge it yet as we need to wait for the hive version bump to ensure the job modules IDs are complaint.

@tommyp1ckles is the expert, so please take the following with a grain of salt. I'm just giving a drive-by review :).
If all modules within the hive are defined when cilium boots up, meaning, no modules can be added during runtime, then I think we will be fine. The biggest concern would be a metric with unbounded labels, like "pod name", but since the number of labels here is determined when the agent boots we won't have to worry about unbounded growth.
That being said, one concern I do have is that the optimization "We are only publishing module names for the degraded cells" isn't entirely true. When a module experiences degraded health, the metric with the module's label will be exposed until the agent is restarted even if the module becomes healthy again. As soon as WithLabelValues is called, a metric tracking the given label is exposed. Even if the PR was modified to decrement the module's metric value when it becomes healthy again, the metric's value will be 0 and therefore continue to be exposed.
The impact of the metric's cardinality will change as new cells are added and cell behavior changes, which is also a concern because that kind of impact is not easy to review or detect.

I see some benefits a metric like this one, that reports the cell modules that are in a degraded state, do you see any value in having something like this?
To reduce the risk of cardinality. do you think it would make sense to limit the number of reported modules, for example if we exceed to have more than 10 unhealthy modules, we publish the metrics only for the first 10?

I see some benefits in a metric like this one, that reports the cell modules that are in a degraded state, do you see any value in having something like this?

I agree there's definitely a benefit to having it, we just have to figure out a "safe" way to add it into the agent to prevent potential issues.

To reduce the risk of cardinality. do you think it would make sense to limit the number of reported modules, for example if we exceed to have more than 10 unhealthy modules, we publish the metrics only for the first 10?

This could be interesting, but the main concern I'd have with an approach like this is with agents that run for a very long time. If an agent faces an issue that causes some modules to fail, say in the first day or two that it is running, then the metric is only useful if those same modules are the only ones to fail for the rest of the lifetime of the agent. We won't have visibility into other failing modules.
One idea that @marseel, @joamaki and I were discussing is having a second Prometheus endpoint for high-cardinality metrics that are useful for troubleshooting, like this one. This shifts them to be more "opt-in" for continual scraping and opens the option for them to only be used when needed to debug issues. Would you have any interest in implementing something like this for Cilium?

I see some benefits in a metric like this one, that reports the cell modules that are in a degraded state, do you see any value in having something like this?

I agree there's definitely a benefit to having it, we just have to figure out a "safe" way to add it into the agent to prevent potential issues.

To reduce the risk of cardinality. do you think it would make sense to limit the number of reported modules, for example if we exceed to have more than 10 unhealthy modules, we publish the metrics only for the first 10?

This could be interesting, but the main concern I'd have with an approach like this is with agents that run for a very long time. If an agent faces an issue that causes some modules to fail, say in the first day or two that it is running, then the metric is only useful if those same modules are the only ones to fail for the rest of the lifetime of the agent. We won't have visibility into other failing modules.
One idea that @marseel, @joamaki and I were discussing is having a second Prometheus endpoint for high-cardinality metrics that are useful for troubleshooting, like this one. This shifts them to be more "opt-in" for continual scraping and opens the option for them to only be used when needed to debug issues. Would you have any interest in implementing something like this for Cilium?

So thinking more about it, how many cells could we expect to be degraded and the cluster to be happy...?
And how many cell.modules do we have, 50? So even if we have all cells degraded this is still a low cardinality...
We are exposing the cell.moduleID and not all the sub-modules.
I think the new API would make sense and I'm happy to contribute to it, but for this one I think it would make sense to have it enabled by default on the default API.

I think the new API would make sense and I'm happy to contribute to it, but for this one I think it would make sense to have it enabled by default on the default API.

Thank you, that's kind of you. I think that your logic makes sense here. IMO we can move forward with this PR then. CC @tommyp1ckles can you take a look?

@learnitall @ovidiutirla Sorry for the late review, I'm a bit on the fence on this one. Theoretically it's unbounded cardinality but in practice there is only so many modules in a particular release/configuration that could be emitted.
One suggestion I had was to use the DeletableGaugeVec type to manage the metric lifecycles, such that we cleanup modules that are zero instead of keeping them around forever.
Otherwise, just making this metric Opt-in via the IsDisabled option in the metrics-opts would remove any concern 😄

@tommyp1ckles, kindly ask for a review. I applied your suggestions, marked as Deletable and also disabled by default 🙏

/test

/test

/test

/test

/test

cc @pchaigno :)


RadSideDrawer : ActionBar invisible when using ShowOverNavigation

Hi,
The action bar is invisible when I add showOverNavigation="true" to the RadSideDrawer. But, ActionItem are clickable!
<template>
    <page class="page">
        <action-bar :title="pageTitle" class="bg-primary">
            <ActionItem text="Menu" @tap="$refs.drawer.nativeView.showDrawer()" />
        </action-bar>
        <RadSideDrawer ref="drawer" class="sidedrawer-left" showOverNavigation="true">
            <StackLayout ~drawerContent class="sidedrawer-left">
                <StackLayout class="sidedrawer-header">

                </StackLayout>
                <StackLayout class="sidedrawer-content">

                </StackLayout>
            </StackLayout>
            <StackLayout ~mainContent >

            </StackLayout>
        </RadSideDrawer>
    </page>
</template>

With showOverNavigation :

Without :

I can't reproduce with latest version, not sure what's going on: https://play.nativescript.org/?template=play-vue&id=6o7FUvfPHw04BqIOY5sz&v=2

It's probably different with the webpack build? I'm using version nativescript-vue 0.3.1, with ns-vue-loader 0.1.0.
Here is my complete dependencies:
  "dependencies": {
    "nativescript-pro-ui": "^3.2.0",
    "nativescript-theme-core": "~1.0.4",
    "nativescript-vue": "^0.3.1",
    "tns-core-modules": "^3.0.0",
    "vue-i18n": "^7.3.0",
    "vue-router": "^2.4.0"
  },
  "devDependencies": {
    "babel-core": "^6.26.0",
    "babel-loader": "^7.1.2",
    "babel-preset-es2015": "^6.24.1",
    "babel-preset-stage-2": "^6.24.1",
    "babel-traverse": "6.24.1",
    "babel-types": "6.24.1",
    "babylon": "6.16.1",
    "copy-webpack-plugin": "~4.0.1",
    "css-loader": "^0.28.4",
    "extract-text-webpack-plugin": "~2.1.0",
    "json-loader": "^0.5.7",
    "lazy": "1.0.11",
    "merge-files-webpack-plugin": "^1.1.2",
    "nativescript-css-loader": "~0.26.0",
    "nativescript-dev-android-snapshot": "^0.*.*",
    "nativescript-dev-sass": "^1.3.5",
    "nativescript-dev-webpack": "^0.6.3",
    "node-sass": "^4.7.2",
    "ns-vue-loader": "^0.1.0",
    "raw-loader": "~0.5.1",
    "resolve-url-loader": "~2.0.2",
    "sass-loader": "^6.0.6",
    "style-loader": "^0.18.2",
    "vue-loader": "^12.2.1",
    "vue-style-loader": "^3.0.1",
    "vue-template-compiler": "^2.5.9",
    "webpack": "~2.6.1",
    "webpack-sources": "^1.1.0",
    "yaml-include-loader": "^1.0.0"
  }

Removing class="sidedrawer-left" from the RadSideDrawer  fixes the issue, probably a css issue?

 But I'm using the core.light theme from Nativescript (didn't change the implemention from the webpack template) and this class came from the documentation...

I think that class is supposed to go on the drawerContent view, and not the RadSideDrawer itself

Again, you're right... I did a lot of tests yesterday... I put it on both the sidedrawer and it's content. My bad. Sorry!


Payment.J is undefined

In your dist/payment.js, you forgot the line Payment.J = QJ
I managed to fix it by referring to your online demo scripts ...
Online Demo

Which line did you put Payment.J = QJ?

Line 704...
Just before u export it...

Yea I found it while looking through the script for the online demo, but thanks for the reply!


Implement labels/catalog support for recipes

Modify the MongoDB structure to incorporate labels for each recipe, allowing more than one label for a recipe. (e.g., Indian, Favorite)
Update the recipe creation form to allow users to add labels.

can i get this assigned?

!assign @namrataaravinda 60

@Samyukta-b would this be the right approach?: https://github.com/Delta18-Git/recipe-manager/commit/21c9da93f11c1032e3751bc98e15d2d39f65ed71

See #9 @Samyukta-b


RDKTV-10986: DeviceName not listed for casting

Reason for change:
DeviceName not listed for casting
Test Procedure: None
Risks: Low
Change-Id: I9f35e8e8f32d501f3e627c83a8ca876c6263fc22
Signed-off-by: Anooj Cheriyan<EMAIL_ADDRESS>

Closed due to inactivity, please restore if still needed.


Add reset_encoding to Dataset and DataArray objects

Is your feature request related to a problem?
Xarray maintains the encoding of datasets read from most of its supported backend formats (e.g. NetCDF, Zarr, etc.).  This is very useful when you want to perfectly roundtrip but it often gets in the way, causing conflicts when writing a modified dataset or when appending to another dataset. Most of the time, the solution is to just remove the encoding from the dataset and continue on. The following code sample is found in a number of issues that reference this problem.
    for v in list(ds.coords.keys()):
        if ds.coords[v].dtype == object:
            ds[v].encoding.clear()

    for v in list(ds.variables.keys()):
        if ds[v].dtype == object:
            ds[v].encoding.clear()

A sample of issues that show variants of this problem.

https://github.com/pydata/xarray/issues/3476
https://github.com/pydata/xarray/issues/3739
https://github.com/pydata/xarray/issues/4380
https://github.com/pydata/xarray/issues/5219
https://github.com/pydata/xarray/issues/5969
https://github.com/pydata/xarray/issues/6329
https://github.com/pydata/xarray/issues/6352

Describe the solution you'd like
In many cases, the solution to these problems is to leave the original dataset encoding behind and either use Xarray's default encoding (or the backends default) or to specify one's own encoding options. Both cases would benefit from a convenience method to reset the original encoding. Something like would serve this process:
ds = xr.open_dataset(...).reset_encoding()

Describe alternatives you've considered
Variations on the API above could also be considered:
xr.open_dataset(..., keep_encoding=False)

or even:
with xr.set_options(keep_encoding=False):
    ds = xr.open_dataset(...)

We can/should also do a better job of surfacing inconsistent encoding in our backends (e.g. to_netcdf).
Additional context
No response

see also #6323

As I said in #4817, I think we should pursue the keep_encoding option (in addition to the proposal in this PR).


Development Guide

Clone repository and install dependencies
git clone https://github.com/Nault/Nault
cd Nault
npm install

Run the wallet in dev mode
npm run wallet:dev

If you want to debug in VS code, first install debugger for chrome
Then you can just go to the debug screen and choose "Launch Chrome http"
Run the wallet in dev mode as https (for example if using the Ledger device)
npm run wallet:dev-ssl

To debug in VS code: Go to debug screen and choose "Launch Chrome https"
Build Wallet (For Production)
Build a production version of the wallet for web:
npm run wallet:build

Build a production version of the wallet for desktop: (Required for all desktop builds)
npm run wallet:build-desktop

Available at https://github.com/Nault/Nault/blob/master/DEVELOPMENT.md


Added an example for an older version to the docs

Hi,
thanks again for the implementation. I was looking for a solution like this. I ran into the same error as #5 and stumbled upon these docs after some googling. Changing the name to gpt-3.5-turbo worked for me.
This PR updated the Readme and makechain.ts to include the reference to the working model (and the docs).

Did your tests find that 'text-davinci-003' doesn't work as a modelName?

Yes. You (by proxy) are using the /v1/chat/completions endpoint. These are the supported models:

gpt-4, gpt-4-0314, gpt-4-32k, gpt-4-32k-0314, gpt-3.5-turbo, gpt-3.5-turbo-0301
text-davinci-003 is only allowed for the /v1/completions endpoint:

And if you follow OpenAIChat
import { OpenAIChat } from 'langchain/llms';

you reach:

-> https://platform.openai.com/docs/api-reference/chat/create
And there it says that it's hitting the POST https://api.openai.com/v1/chat/completions endpoint :)


Cannot load a maf file

Hi, I am trying to load a maf file, and it seems to have correct format, according to the NCI page, but when I try to load it, I get an error message:

mymaffile <- system.file('HCT.maf.subst', package = 'maftools')
HCTmaf <- read.maf(maf = mymaffile, removeSilent = F, useAll = T, verbose = T)
reading maf..
Error in data.table::fread(input = maf, sep = "\t", stringsAsFactors = FALSE,  :
Input is either empty or fully whitespace after the skip or autostart. Run again with verbose=TRUE.

Not sure what's causing this issue, and how I can resolve it.
Thank you!

Hi,
You don't have to run first system.file command. You can directly pass your maf file to read.maf.
HCTmaf <- read.maf(maf ="/path/to/HCT.maf.subst", removeSilent = F, useAll = T, verbose = T)


Rename to ihsan

Remaining work

pulumi account project name
awk secrets manager setup
ecr

Need to delete the following:

AWS secrets manager, anything with khatm/staging and khatm/production
The *.khatmapp.com cert in ACM
mmislam101 pulumi account


datapath/test: Do not SNAT for WORLD_ID and enable BPF masquerading by default in CI

See commit msgs.
Partially_fix #11442

test-me-please

test-focus K8sDatapath*

test-me-please

test-me-please

test-me-please

I might need to fix https://github.com/cilium/cilium/issues/11464 before this PR can be merged (otherwise, I might introduce flakes)

Coverage increased (+0.002%) to 37.887% when pulling 961b375843569b39ae8123d32bced835420c8afe on pr/brb/ci-bpf-masq-by-default into fb8481a2e9e0f006dde144f64b196addc5fe8529 on master.

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-focus K8sDatapathConfig*

test-me-please

test-me-please

retest-net-next

test-focus K8sKubeProxyFree*

test-me-please

retest-net-next

test-focus K8sKubeProxy*

test-focus K8sKubeProxy*

retest-net-next

retest-4.19

retest-4.9

retest-runtime

retest-runtime

CI runtime failed:
[2020-05-18T15:26:35.027Z] [Fail] RuntimePrivilegedUnitTests [It] Run Tests
[2020-05-18T15:26:35.027Z] /home/jenkins/workspace/Cilium-PR-Runtime-4.9/runtime-gopath/src/github.com/cilium/cilium/test/runtime/privileged_tests.go:47
[2020-05-18T15:26:35.027Z]
[2020-05-18T15:26:35.027Z] Ran 72 of 393 Specs in 4779.419 seconds
[2020-05-18T15:26:35.028Z] FAIL! -- 71 Passed | 1 Failed | 9 Pending | 312 Skipped

retest-runtime


ansible-lint complains about curl and get_url module

ansible-lint site.yml
[ANSIBLE0006] curl used in place of get_url module
/var/lib/jenkins/jobs/infrastructure/workspace/ansible/roles/geerlingguy.jenkins/tasks/main.yml:0
Task/Handler: Wait for Jenkins to start up before proceeding.
[ANSIBLE0006] curl used in place of get_url module
/var/lib/jenkins/jobs/infrastructure/workspace/ansible/roles/geerlingguy.jenkins/tasks/plugins.yml:0
Task/Handler: Update Jenkins plugin data.

ansible-lint is a bit heavy-handed, imo. Sometimes it's a lot simpler (and even cleaner) to use curl, especially when you need to run a command with pipes, etc. Doing this using get_url would make for a lot more configuration, and the role would be overly complicated (IMO).

Reopening; I may be able to use the uri module instead... https://github.com/willthames/ansible-lint/issues/70

Closing again—once we go full 2.0, I might add the new 'ignore warnings' modifier to those tasks, as the way they're written, it would be difficult to switch to using a different technique... not impossible, but not something I want to spend a couple hours debugging.


⚠ Digital Ocean - https://status.digitalocean.com/ has degraded performance

In 05414c5, Digital Ocean - https://status.digitalocean.com/ (https://status.digitalocean.com/api/v2/status.json) experienced degraded performance:

HTTP code: 200
Response time: 183 ms

Resolved: Digital Ocean - https://status.digitalocean.com/ performance has improved in 92ee507.


c++_linux_opt.bins/opt/hybrid_end2end_test --gtest_filter=HybridEnd2endTest.AsyncRequestStreamResponseStream_AsyncDupService GRPC_POLL_STRATEGY=poll (from grpc.c++_linux_opt)

Standard Output
D1215 16:29:11.170558720   28875 test_config.c:290]          test slowdown: machine=1.000000 build=1.000000 poll=1.000000 total=1.000000
Note: Google Test filter = HybridEnd2endTest.AsyncRequestStreamResponseStream_AsyncDupService
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from HybridEnd2endTest
[ RUN      ] HybridEnd2endTest.AsyncRequestStreamResponseStream_AsyncDupService
D1215 16:29:11.170822380   28875 ev_posix.c:105]             Using polling engine: poll
D1215 16:29:11.171998810   28875 ev_posix.c:105]             Using polling engine: poll
I1215 16:29:11.172032957   28875 server_builder.cc:247]      Synchronous server. Num CQs: 16, Min pollers: 1, Max Pollers:<PHONE_NUMBER>, CQ timeout (msec): 1000
I1215 16:29:11.234500675   30624 test_service_impl.cc:305]   recv msg hello0
I1215 16:29:11.234682417   30624 test_service_impl.cc:305]   recv msg hello1
I1215 16:29:11.234818595   30624 test_service_impl.cc:305]   recv msg hello2
test/cpp/end2end/hybrid_end2end_test.cc:70: Failure
Value of: VerifyReturnSuccess(cq, i)
Actual: false
Expected: expect_ok
Which is: true
[  FAILED  ] HybridEnd2endTest.AsyncRequestStreamResponseStream_AsyncDupService (1118 ms)
[----------] 1 test from HybridEnd2endTest (1118 ms total)
[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (1118 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] HybridEnd2endTest.AsyncRequestStreamResponseStream_AsyncDupService
1 FAILED TEST
D1215 16:29:12.288335972   28875 ev_posix.c:105]             Using polling engine: poll

Seen again https://grpc-testing.appspot.com/job/gRPC_pull_requests_linux/1589/

Seen twice in the last two days for gRPC_master_asanitizer_cpp:

553
556

Seen in gRPC_master_linux:

1005
1012
1017

... and in gRPC_master_tsan_cpp build 536.

also for epoll
#8816

seen again in https://github.com/grpc/grpc/pull/9322

seen again in #9373
https://grpc-testing.appspot.com/job/gRPC_pull_requests_asan_cpp/1337/

Ping. Any ideas?

Seen again in #9428

@vjpai this test is preventing most builds from being green. Are you actively looking or should this be reassigned?

Consider reassigning if this is needed urgently as I realistically won't be looking at this for at least a few days.

This test has been marked as flaky as of #9530. Keeping this issue open in hopes it can be unmarked.


Jittery and jumpy movement

Whenever I mousein on a div (whose background has to be parallaxed) it jumps a little bit, usually in the direction in which I was mousing in. However, this keeps pushing the background images around, in a very jumpy way and after some time you notice the background-repeat.
Hardly suitable.

closed.
no code samples provided /
On Mon, Jan 4, 2016 at 16:46 Tom V<EMAIL_ADDRESS>wrote:

Whenever I mousein on a div (whose background has to be parallaxed) it
jumps a little bit, usually in the direction in which I was mousing in.
However, this keeps pushing the background images around, in a very jumpy
way and after some time you notice the background-repeat.
Hardly suitable.
—
Reply to this email directly or view it on GitHub
https://github.com/hwthorn/parallaxify/issues/8.


Privacy notice empty state

Closes https://github.com/ethyca/fidesplus/issues/738
Code Changes

[x] Add chrome around the page (breadcrumbs, header) which I missed in the initial page scaffolding ticket
[x] Add empty state
[x] Cypress test

Steps to Confirm

[x] Start up fidesplus
[x] Navigate to Privacy requests > Privacy notices
[x] You should see the empty state

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation:

[x] documentation complete, PR opened in fidesdocs
[x] documentation issue created in fidesdocs

[x] Issue Requirements are Met
[x] Relevant Follow-Up Issues Created
[x] Update CHANGELOG.md
[x] For API changes, the Postman collection has been updated

Description Of Changes

Note: the "See data uses" button goes to the /systems route at the moment, though this still appears to be in discussion. There is also no link to the "Consent guide" mentioned in the copy right now.

It just occurred to me that this copy might not be right for someone with the Viewer role who can't actually set up data uses. Should we render something else for Viewers/Viewers+Approvers? @mfbrown
So overall, 3 questions for you:

Where should the "set up data uses" button go?
What should "Consent Guide" link to?
Should we render different copy for Viewers/Viewers+Approvers?

In order for a notice to appear, there must be systems with data uses that match the notices, so the natural place for a user to go right now is the /system route. I don't think this is an ideal solution, because it still requires an additional step from the user of selecting a system and knowing what data use to apply, but in the absence of additional guidance capabilities, let's go to this screen for now.
Let's axe that last sentence for now until we publish documentation that targets this area. I'll create a follow up issue for that.
Do we have any other examples yet in the app where we've changed copy for viewers and not just visibility or active/disabled state?

Thanks @mfbrown , those sound good to me!

Do we have any other examples yet in the app where we've changed copy for viewers and not just visibility or active/disabled state?

We render some copy when a contributor shows up on an owner's permission page saying they can't change that user's permissions. But yeah for the most part we just control visibility / disabled state


storage: Update block proposer index to include height

We always order by height, so make the index more efficient by including the height.
Already applied.

Merging since this has already been applied.


chore(readme): badge style alignment

Codecov Report

Merging #239 (a07ae68) into main (4cf99be) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #239   +/-   ##
=======================================
  Coverage   93.88%   93.88%
=======================================
  Files          27       27
  Lines         278      278
  Branches        4        4
=======================================
  Hits          261      261
  Misses         15       15
  Partials        2        2

Flag
Coverage Δ

unittests
93.88% <ø> (ø)

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

Continue to review full report at Codecov.

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


TTS support

Could you please add support for TTS?
Example:

           Alexa, tell Sonos to say hello world.

           Alexa, tell Sonos to say I love you.

           Alexa, tell Sonos to say dinner is ready in living room.

           Alexa, tell Sonos to say good night in bedroom.

It can be used as a remote speaker. And if every room has an echo and sonos, they can be used as two-way radios. That will be cool.

This would be awesome, great way for me to tell the kids upstairs to wind down their game without yelling.


🚀 Feature: URL Shortener for Python

🔖 Feature description
Appwrite Functions allow you to extend and customize your Appwrite server functionality by executing your custom code. 🤩 You can learn more at our official Appwrite Functions docs.
Your task is to implement the URL Shortener function in Python. You can look at the existing Appwrite Functions Templates in another coding language.
Your function should behave and be implemented similarly to existing URL Shortener Node.js template.
Tasks summary:

[ ] Fork & clone Appwrite's templates repository
[ ] Create a branch feat-implement-url-shortener-python
[ ] Write code for the function in folder python/url_shortener/.
[ ] Test the function using Appwrite, provide a video.
[ ] Write a README.md explaining what the function does, how to use it, and customize it. Here is an example.
[ ] Submit a pull request to our templates repository

If you need any help, contact us on our Discord server.
Are you ready to work on this issue? 🤔 Let us know, and we will assign it to you 😊
Happy Appwriting!
🎤 Pitch
Upon reviewing the project's README, it has come to my attention that the Python implementation for a specific feature is pending. A corresponding issue related to this matter was not evident in the available documentation. Drawing from my experience, I successfully engineered a bespoke URL shortener leveraging Django during the Tally Hackathon, where my team became finalists. Given this proficiency and accomplishment, I am confident in my ability to construct a URL shortener template for appwrite.
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

can you assign this issue to me, if its a valid issue I can start working on it please @Haimantika

Is this issue not appropriate @Haimantika

Hi @codewithkushagra This is not one of our Hacktoberfest issues, you're free to contribute but will not be a part of Hacktoberfest, and the PR review will likely happen after Hacktoberfest.
Thanks!

oh, okay @gewenyu99

I will work on it

I will work on it

Assigning it to you. If you have any questions, feel free to ask us on Discord


Exclude co-authored commits in dim-bots

Test URL: https://github.com/OpenLightingProject/open-fixture-library/commits/c18c0b9caf5127637c56ff518623a0fd3effb738/.github/workflows/test.yaml
The commit from Jun 26, 2020 is dimmed correctly, as the squash-merged PR was opened by a bot.
The commit from Dec 27, 2019 is dimmed incorrectly IMHO, as the squash-merged PR was opened by a bot, but enhanced by me. So also squash merge commit was co-authored by me. This PR fixes that.

I'll add this testing URL too, since it's committed and authored by 2 users, but they're both bots: https://github.com/mozilla/web-ext/commits/master

I'll add this testing URL too, since it's committed and authored by 2 users, but they're both bots: https://github.com/mozilla/web-ext/commits/master


handle commiting when no file change

In cz-cli, if we run git cz without any file change, we'll get the message "No files added to staging! Did you forget to run git add?".
However, in cz c, we can still run the whole process.
The git commit is not actually created.

Maybe we can detect file change like cz-cli? Or, at least we could let the user know that this commit is not actually created.

I like the idea. I'm not sure whether we should do it before or after the
prompted questions. What would you suggest?
On Fri, Nov 8, 2019, 10:57 Wei Lee<EMAIL_ADDRESS>wrote:

In cz-cli https://github.com/commitizen/cz-cli, if we run git cz
without any file change, we'll get the message "No files added to staging!
Did you forget to run git add?".
However, in cz c, we can still run the whole process.
The git commit is not actually created.
[image: Screen Shot 2019-11-08 at 5 53 05 PM]
https://user-images.githubusercontent.com/5144808/68467190-ba08ce80-0250-11ea-9d0e-f617d9e25eed.png
Maybe we can detect file change like cz-cli? Or, at least we could let the
user know that this commit is not actually created.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Woile/commitizen/issues/45?email_source=notifications&email_token=AATXJWDXL4JOLI7MZXDGLRLQSUZY5A5CNFSM4JKVBOKKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HX5LC6Q,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AATXJWAY4FQ6HIUWWZ7RJDTQSUZY5ANCNFSM4JKVBOKA
.

I would suggest do it before because in such situation all the actions after that are meaningless.

Agreed, I had that very same issues a few minutes ago haha. Feel free to create a PR to fix this.


Enhancements to Docs for getting started

[x] explicitly show what "good to go, everything is green!" looks like, after flutter doctor
[x] explicitly tell the developer what to do when flutter doctor fails for some reason (e.g. email our mailing list or open a bug with the output)
[x] include a link to "how to install Atom" at bottom of Setup
[x] add Next Steps at end of Setup, pointing to Getting Started
[x] link to Setup from Homepage, under Getting Started
[ ] iOS screenshot on Getting Started needs to show Slow Mode banner

thanks!


Correctly respond with plain text BAD_REQUEST on crypto errors

Motivation:
We need to respond with plain text if we fail to remove encapsulation
Modifications:
Correctly detect if we failed to remove encapsulation and if this is the case don't try to encapsulate before responding with BAD_REQUEST
Result:
Correctly follow the RFC

LGTM. Good catch. I think the wording of some of the comments could be improved.

Fixed


feat: Add links to PR articles

As mentioned in artsy.github.io#650, this PR adds a couple links to our recent blog articles on pull requests.

Amaaazing, thank you!


fix: do not trigger CursorHold when exiting

Steps that cause the problem:

Open a file with more than one line with Nvim and go to non-first line
:autocmd CursorHold * echomsg localtime()
:call nvim_input('ggZ')
Wait for several seconds and press Q

Without this PR time is printed to stderr. With this PR it is not.

Some plugins may run something on that doesn't work when Nvim is exiting on CursorHold, and this can cause an error, and the error message is printed to stderr.

@zeertzjq thanks a lot for you contribution !


Fix notifications.

If the opened file URIs list is empty then check again after grace period. If list is empty cancel work. otherwise, most notification gets canceled as soon as opened
This is to ensure there is no sync issues between threads, the list is reported empty when it is clearly not empty! But when we check again after few seconds, the list correctly reports the opened files. If it was indeed empty, then cancel work by deferredUntilCompleted.complete(Unit).
I opted to use Handler(Looper.getMainLooper()).postDelayed() instead of Timer. The Handler uses the main applications thread, while the Timer creates a background thread to call the deferred work. I didn't notice much difference between both, but Handler is safer if we are checking the value of StateFlow cifsRepository.openUriList.value since if we did that in a background thread, that might cause race conditions and sync issues between threads.
And since WorkManager automatically runs it on a background thread, that might have caused a race condition when checking the state flow. This is just a guess.
Anyways. This fixes the notifications, and has no bad side effects after extensive testing.

This video shows the issue from 0:00 to 2:45 .. and after the fix from 2:46+
https://streamable.com/2o5i8j
I had to use something other than youtube, I got a strike for dangerous content! 🤣 lol.

@RebelliousX
Thank you!

No.. Thank you @wa2c 😊


Inline not found branched requires

Fixes https://github.com/zeit/ncc/issues/358.
The approach taken here is effectively to work around the Webpack error thrown by inlining any not found branched requires. Instead of statically analyze the known branch conditional, instead we analyze both branches and remove branches that are not found.

Thanks, I forgot to push the latest commit. I also added a further refactoring to some previous code based on this approach, which removes some constraints too.

Codecov Report

Merging #24 into master will decrease coverage by 1.62%.
The diff coverage is 67.85%.

@@            Coverage Diff             @@
##           master      #24      +/-   ##
==========================================
- Coverage   72.05%   70.42%   -1.63%
==========================================
  Files          10       10
  Lines         848      869      +21
==========================================
+ Hits          611      612       +1
- Misses        237      257      +20

Impacted Files
Coverage Δ

src/asset-relocator.js
80.97% <67.85%> (-1.63%)
:arrow_down:

src/utils/static-eval.js
58.29% <0%> (-4.53%)
:arrow_down:

Continue to review full report at Codecov.

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

The latest commit comment was meant in reference to the other PR.


COMMONSRDF-33 Add Jena integration

This adds the jena module, Commons RDF implementations backed by Apache Jena.
See also COMMONSRDF-33

Here is what the combined Javadoc looks like, including org.apache.commons.rdf.jena
Worthy of review is perhaps all the method variations in JenaRDFTermFactory.

It seems like the generalized quad is supported, but not the triple. Am I missing something?

Thanks for the review, @ajs6f! I'll try to fix.

Glad to, @stain ! This is good stuff, and again, let me know if/how I can help.

OK, pushed fixes. I didn't fix the <T extends Node> because of the weird Node sub-types, and I didn't add a JenaGeneralizedQuadLike.

I also exposed createdAnyVariable() and createVariable(String) in the JenaRDFTermFactory as those were hidden inside impl.JenaFactory - not sure if those would be useful with a generalized triple/quad or only would appear in a SPARQL query?

The "weird" Node sub-types question is a good one. My sense is that they are indeed internal. @afs , can you comment here? I like to type as strongly as possible, but I don't want to lead anyone astray! :)

The comment on Jena's Node_Variable:
    "variable" nodes; these are outside the RDF2003 specification, but are
    used internally for "placeholder" nodes where blank nodes would be
    wrong, most specifically in Query.

leads me to believe that we are talking about SPARQL here. There's not really any other place in Jena I know about that would use such machinery-- the find methods on various structures just use null or Node_ANY as a wildcard.

Also, the phrase "used internally" in that comment makes me wonder if it is right to expose those methods?

So I guess they would be mainly to represent the "triple patterns" in SPARQL, e.g. ?s in:
?s a <http://example.com/>;

although there would not be any way to use those jena variables with the Commons RDF-exposed graph/datasets - and they should not be returned in there. (unless someone had deliberately added such to a Jena Graph manually - which is allowed today as it excepts any Node)
Do I get it right that these would not be appearing in query results?

I don't think there is any situation in which a variable can appear as part of query results (except, I suppose, if you want to think about the label of a variable appearing as the name of a column).

OK, then I'll remove JenaVariable and merge the rest. Thanks for the review, @ajs6f !

Hmm.. Removing JenaVariable means in fromJenaGeneralized(Node) I have to fail on node.isVariable() (which is in the Jena API):
e.g. current suggestion
if (node.isVariable()) {
  return new JenaVariableImpl(node);
}

will instead become:
throw new IllegalArgumentException("Unrecognized node type: " + node);

@afs  - how generalized should I make the generalized quad? :)

I'd keep to concrete RDFTerms, i.e. no named variables.  Interop is not served by having them.

Instead of
throw new IllegalArgumentException("Unrecognized node type: " + node);

what about
throw new ConversionException(new UnsupportedOperationException("Conversion does not currently support SPARQL variables : " + node));

Thanks for the great review, @ajs6f  and @afs! Now merged in master.

Great stuff, @stain -- thanks for moving this forward!


[FEATURE] Get-PnPMicrosoft365Group ExpirationDate

Is your feature request related to a problem? Please describe.
Nope
Describe the solution you'd like
It would be great to make Get-PnPMicrosoft365Group return ExpirationDate the same way Get-UnifiedGroup does:

Get-PnPMicrosoft365Group does not seem to return these details. It has just RenewedDateTime instead.

Describe alternatives you've considered
As of November 3rd, 2022 we have to use Get-UnifiedGroup to get ExpirationDate
Additional context
Name    : PnP.PowerShell
Version : 1.11.123

In 1.12, we have added Get-PnPMicrosoft365ExpiringGroup, maybe that can help you ? It fetches you expiring groups.
https://pnp.github.io/powershell/cmdlets/Get-PnPMicrosoft365ExpiringGroup.html

Closing as no response.


IPTT: Inconsistent indenting in NO. column

Issue
Looks like Goal and Activity indicators are indented while others are not. Not sure what happens with a 5- or 6-tier RF.
Acceptance criteria
All indicators are flush left, no indentation.

PASSED. All left aligned now.


Implement Versioning

Right now pony-stable still has no concept of versions.
I'd like pony-stable to follow the model of Rust's Cargo but we can avoid version ranges for now.
A basic package manager needs to do implement these rough functions.

Define the dependencies inside a manifest.

Optional: If version ranges will be supported the package manager has to use constraint solving to generate the current dependency graph and save it in a lockfile. The lockfile has to be commited to the repository to ensure reproducible builds.

Fetch the dependencies and store them in this flat path structure:

<package-name>/<version>/<package-contents>

(Let's avoid the recursive mess that NPM used to create before version 3.)

The last step is to give the compiler information about the location of the packages.

pony-stable already does 1., 3., 4. partially but it's still missing features such as version information.
What I'd like to see is the ability to specify the version in the manifest.
Without version ranges there are two primary version types in this scenario:
static/pinned versions like 2.5.3 which could be denoted '=2.5.3' (in line with NPM and Cargo)
moving versions like latest or master that follow a branch which could be denoted as ':latest' (afaik no package manager uses colons as a prefix)
Side Note: These symbols were chosen to leave room for version ranges if the need arises.
Step 1., 2., 3. can be implemented without modifying ponyc.
Step 4. is problematic when there is more than one version of a single package.
Here is an example dependency graph:
A version 1.0.1
    B version 1.3.5
       C version 2.3.0
    D version 1.0.9
       C version 1.4.0

Right now there can only be one version of C.
When B uses "C" the compiler looks for .deps/C rather than .deps/C/2.3.0
and D uses "C" it also chooses .deps/C rather than .deps/C/1.4.0.
Ponyc has to be changed to support some sort of "package redirection" for specific packages.
Alternatively we could also use pony_packages and redirect from pony_packages/C to .deps/C/2.3.0 on the filesystem layer via symlinks.
I'm still not sure how to pass on the redirection information to the compiler.
Here are the two approaches I've figured out so far.
Package specific PONYPATHs via command line parameters. The path of the package is specified and the paths of the dependency packages. The command may become very large and hit limits of the CLI.
ponyc --package-path /path/to/package/D/1.0.9=/path/to/package/C/1.4.0 --package-path /path/to/package/B/1.3.5=/path/to/package/C/2.3.0

The alternative is that pony-stable generates a json file that contains this information and the compiler reads the redirect information from it.
{
    path: "/path/to/project"
    dependencies: {
        "B": {
            path: "/path/to/project/.deps/B/1.3.5",
            dependencies: {
                "C": {
                    path: "/path/to/project/.deps/C/2.3.0",
                    dependencies: {}
                }
            }
        },
        "D": {
            path: "/path/to/project/.deps/D/1.0.9",
            dependencies: {
                "C": {
                    path: "/path/to/project/.deps/C/1.4.0",
                    dependencies: {}
                }
            }
        }
    }
}

@Vorlent can you clarify "has no concept of versions"?
do you mean, that dependencies always use HEAD? if yes, then that isn't the case. However, there are certainly improvements that can be made. It doesn't for example, do ranges. You can use a specific git tag/commit. For example...
https://github.com/WallarooLabs/wallaroo/blob/master/machida/bundle.json#L8

Okay I didn't know about the ability to specify versions inside tags.
Handling the minor and patch versions with tags this way is perfectly okay as long as the library does not have any breaking changes. But when backwards compatiblity is broken you need to be able to use two major versions of the same library in one program. Does pony-stable handle this in any way?
Let's take the pony-inspect library. Suddenly one day version 2.0.0 of pony-inspect is released. How do I use it via pony-stable?
Does pony-stable offer a solution beyond just putting the major version into the package name like this?
use "inspect"
use "inspect2"

you would change the version in your bundle.json to match the API you are using in your code:
{
  "deps": [
      { "type": "github",
        "repo": "jemc/pony-inspect",
        "tag": "2.0.0"
      }
  ]
}

you would version your bundle.json along with your changes to upgrade to whatever the API changes were for the new version of pony-inspect.

Ok. Thank you.


Switch back to using antlr4 from original repository.

Issue #1718 - Switch back to using antlr4 from original repository.
Introducing custom implementation of dynamic_cast to speed
up things.

Codecov Report

Merging #1886 (ba1c275) into master (a51956f) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1886      +/-   ##
==========================================
- Coverage   24.19%   24.16%   -0.03%
==========================================
  Files         187      187
  Lines       31299    31335      +36
==========================================
  Hits         7573     7573
- Misses      23726    23762      +36

Impacted Files
Coverage Δ

src/DesignCompile/UhdmWriter.cpp
28.66% <0.00%> (-0.49%)
:arrow_down:

src/DesignCompile/CompileModule.cpp
18.35% <0.00%> (-0.22%)
:arrow_down:

src/DesignCompile/CompileStmt.cpp
0.06% <0.00%> (ø)

Continue to review full report at Codecov.

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


Postgres node failures and recovery

Is this a request for help?: Yes

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Version of Helm and Kubernetes: helm v2.12.2 / k8s 1.11.5
Which chart: stable/postgresql
What happened: What is the best practice to promote standby node to master?
Detailed description: I have a kubernetes cluster with two nodes across different fault/update domains and I would like to perform several tests with different failure scenarios.
The postgres master node is running on, say, node-0, and slave node is running on node-1.
A stateless service S is scheduled on one of nodes and has single connection string - one which points to the service of master node.
When node-0 dies, S becomes unstable since it can not connect to database. I would like to promote the running standby node to master node and avoid changing connection string in S. When node-0 recovers, I would like to promote back postgres node running on node-0 to master. The best approach I could think off so far is

Promote the standby node to master using pg_ctl
Update service of dead master node to point to new master node
Once when node-0 is live again, promote it to slave node and do backup

Is this a correct approach? Is there a better one (in terms of sum of downtime)? Should I rather work on recovering the dead node ?
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:

Hi,
Your approach makes sense to me. Unfortunately, we do not currently have an automated approach to do so, so you would need to perform these steps manually. It would be extremely helpful for us to know more details about your use case. Have you faced this issue in the past? Is it part of your testing pipeline?


swagger make sure generic collection is supported for complex types

public List<Employee> addEmployees(List<Employee> employees) {
...

Both the generic return and parameter should generate the right swagger stuff.

    /* This does not really handle generic returns or generic params which are collections but....
            We know how to do this see io.advantageous.boon.core.reflection.fields.BaseField constructor
            protected BaseField ( String name, Method getter, Method setter ) for an example.

     */


[RFC] docs: add FAQ section

Related issue

#986
#322
In relation with deprecated warnings we need to inform users how to turn off this warnings in development mode. Furthermore we need this section to write all frequently asked questions.
Scope of work

add FAQ section

Screenshots of visual changes

Checklist

[x] No commented blocks of code left
[x] Run tests and docs
[x] Self code-reviewed

#867

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: martaradziszewska:x: Marta RadziszewskaMarta Radziszewska seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


feature request: API to set file_index

I will be more than happy to contribute.

@quininer This sounds reasonable, doesn't it? Can you give the go ahead to offer a PR?

Please feel free to open a PR.

I think this one is in fact a duplicate of https://github.com/tokio-rs/io-uring/issues/178, see the list of relevant opcodes there. All relevant ones should be fixed now.


[BUG] NodeJs, out of memory exception

🐛 Bug Report
Pauses at addCellEx from cell matrix.js on readfile, out of memory  exception
Links to similar issues
https://github.com/exceljs/exceljs/issues/967
https://github.com/exceljs/exceljs/issues/1898
Lib version: v4.2.1
Steps To Reproduce
Use Code
file : 1,209kb
Ext: xlxs
const workBook = new ExcelJS.Workbook()
await workBook.xlsx.readFile(file)

Error Code
<--- Last few GCs --->
[5872:0000028127127A10]  2177807 ms: Scavenge 8184.3 (8211.8) -> 8182.8 (8218.8) MB, 22.3 / 0.0 ms  (average mu = 0.705, current mu = 0.584) allocation failure
[5872:0000028127127A10]  2180354 ms: Mark-sweep 8191.1 (8218.8) -> 8189.2 (8232.8) MB, 1994.8 / 0.1 ms  (+ 1617.0 ms in 29656 steps since start of marking, biggest step 28.8 ms, walltime since start of marking 13466 ms) (average mu = 0.723, current mu = 0

<--- JS stacktrace --->
FATAL ERROR: MarkCompactCollector: young object promotion failed Allocation failed - JavaScript heap out of memory
 1: 00007FF7316D4C9F napi_wrap+111007
 2: 00007FF731678226 v8::base::CPU::has_sse+59910
 3: 00007FF731679126 node::OnFatalError+294
 4: 00007FF731F52ABE v8::Isolate::ReportExternalAllocationLimitReached+94
 5: 00007FF731F3788D v8::SharedArrayBuffer::Externalize+781
 6: 00007FF731DE09DC v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1516
 7: 00007FF731DCB45B v8::internal::NativeContextInferrer::Infer+59739
 8: 00007FF731DB072F v8::internal::MarkingWorklists::SwitchToContextSlow+56975
 9: 00007FF731DC441B v8::internal::NativeContextInferrer::Infer+31003
10: 00007FF731DBB4FD v8::internal::MarkCompactCollector::EnsureSweepingCompleted+6285
11: 00007FF731DC366E v8::internal::NativeContextInferrer::Infer+27502
12: 00007FF731DC76BB v8::internal::NativeContextInferrer::Infer+43963
13: 00007FF731DD10B2 v8::internal::ItemParallelJob::Task::RunInternal+18
14: 00007FF731DD1041 v8::internal::ItemParallelJob::Run+641
15: 00007FF731DA46A3 v8::internal::MarkingWorklists::SwitchToContextSlow+7683
16: 00007FF731DBB9AC v8::internal::MarkCompactCollector::EnsureSweepingCompleted+7484
17: 00007FF731DBA1E4 v8::internal::MarkCompactCollector::EnsureSweepingCompleted+1396

The expected behaviour:
Please throw it before the memory overflows.

try this  https://stackoverflow.com/a/71215812/7840345

I had the same problem after maximizing the memory.
So, instead of using this package, I replaced it with xlsx(SheetJS) and used it without any problems.

I have heard xlsx(SheetJS is no better than exceljs for writing huge data. Are you sure?

SheetJS has no styling/images in the community version :/


Put icons back on the left (or make it an option)

I don't know if it's big-sur or a recent Vienna Update but icons are now located on the right. This is very inefficient moving around because I pick entries on the left, move down to some entries, move up and right to some icon, again left and so forth. Before it was mostly a little bit up and down and only a little left and right.
As a work around I have put tons of spaces in the bar to get them back to the old location.

This is indeed a change in Big Sur; it is how the default toolbar style works.
I happen to know that you can force the old toolbar style with this command:
defaults write uk.co.opencommunity.vienna2 NSWindowSupportsAutomaticInlineTitle -bool false

This is indeed a change in Big Sur; it is how the default toolbar style works.
I happen to know that you can force the old toolbar style with this command:
defaults write uk.co.opencommunity.vienna2 NSWindowSupportsAutomaticInlineTitle -bool false


Feat: Setting default configuration

This PR adds a default configuration object based on the CLI generator templates. @zacharygolba — I'm sure you might want to make some adjustments, but... here's a starting point!
--
Closes #257

This is a great start! As per the changes suggested in our meeting I'm adding the needs-update label for the time being. 😃

@zacharygolba hopefully this is closer to what you were thinking!

👏  Awesome job! I have one small request.
Can we dry up the Application$opts type in ./src/packages/application/interfaces.js?
// @flow
import type { Config } from '../config';
import type { Database$config } from '../database';

export type Application$opts = Config & {
  path: string;
  port: number;
  database: Database$config;
};

Ah yes forgot about that! Updating now.

Just found a small bug. As usual it's 100% my fault! 😆
If you only export an empty object from the test app config you run into the following error.
TypeError: Cannot read property 'level' of undefined
    at new Logger (/Users/zacharygolba/workspace/postlight/lux/src/packages/logger/index.js:164:66)
    at /Users/zacharygolba/workspace/postlight/lux/src/packages/cli/commands/serve.js:26:18
    at next (native)
    at step (/Users/zacharygolba/workspace/postlight/lux/src/utils/set-type.js:22:3)
    at /Users/zacharygolba/workspace/postlight/lux/src/utils/set-type.js:22:3
    at /Users/zacharygolba/workspace/postlight/lux/src/utils/set-type.js:22:3
    at serve (/Users/zacharygolba/workspace/postlight/lux/src/packages/cli/commands/serve.js:16:1)
    at exec (/Users/zacharygolba/workspace/postlight/lux/bin/lux:63:18)
    at exec.then (/Users/zacharygolba/workspace/postlight/lux/bin/lux:151:19)

You were right all along! We should merge the config file in the loader as well as the Application's constructor. This will prevent instances of Logger running outside of Application instances from throwing errors.

Just finished testing this. It works great! Awesome job 😃


⚠ Secret Website 3 has degraded performance

In 63b9197, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 8992 ms

Resolved: Secret Website 3 performance has improved in 48fbf9e.


[DON'T MERGE]: testing if ARROW-14514 is fixed in CI

This should not be merged, it is a combination of #11573 and #11577 to test if the new CI and the fix works. Used for ease and visibility of crossbow triggering

@github-actions crossbow submit test-fedora-r-clang-sanitizer

@github-actions crossbow submit test-fedora-r-clang-sanitizer
Fix a typo in the CI script


Unused file Pan_Docs.md

What should we do with https://github.com/gbdev/pandocs/blob/master/src/Pan_Docs.md? It appears to be a copy of https://gbdev.gg8.se/wiki/articles/Pan_Docs, but I don't think it should be here?

What should we do with https://github.com/gbdev/pandocs/blob/master/src/Pan_Docs.md? It appears to be a copy of https://gbdev.gg8.se/wiki/articles/Pan_Docs, but I don't think it should be here?

I think we can safely remove it, probably a remain of the wiki dump


Use PrismicImage on Events/ExhibitionsPromo

Waiting on #7371
Starts using the PrismicImage, which uses the next/image.
The main inspiration to do this is to allow me to continue with my Prismic refactoring (#7363). By not using the severly coupled, and impossible to refactor UiImage component, this will allow me to move closer to using generic Prismic types over our custom ParsedFromPrismic types as it takes a generic Prismic type as an argument.
As mention, we have also hit a stale mate with our Image types and components, where they've proliferated out somewhat (UIImage, Image, TASL, Picture etc). This will hope to move in the direction of having a simpler model on the frontend.
I have also tried to use a more structured API when using sizes. i.e.
{
  sizes: {
    breakpointName: ratio
  }
}

// e.g. we have 3 images in a row on xlarge breakpoint
{
  sizes: {
    xlarge: 1/3
  }
}

// Currently we just use the string
// (min-width: 1420px) 386px

For those not faniliar with the sizes/srcset APIs - this is what is produced from CardGrid that breaks from 3 to 2 to 1 as we size down. (min-width: x) Ypx means at x breakpoint, use closest to Y from the srcset, which is a combined list from these values.
<UiImage sizes="(min-width: 1420px) 386px, (min-width: 960px) calc(28.64vw - 15px), (min-width: 600px) calc(50vw - 54px), calc(100vw - 36px)" />

<PrismicImage sizes="(min-width: 1338px) 446px, (min-width: 960px) 33.33333333333333vw, (min-width: 600px) 50vw, (min-width: 0px) 100vw" />

I have compiled some results on the On Happiness
with pages with articles, events and exhibitions in the CardGrid.
UiImage
1338+
initial: 268.38 kB / 278.53 kB transferred
fullscroll: 334.08 kB / 346.27 kB transferred

960
initial: 97.44 kB / 108.16 kB transferred
fullscroll: 133.48 kB / 146.80 kB transferred

600
initial: 55.16 kB / 64.85 kB transferred
fullscroll: 112.02 kB / 125.34 kB transferred

----

PrismicImage
1338+
initial: 78.92 kB / 80.27 kB transferred
fullscroll: 349.65 kB / 356.66 kB transferred

960
initial: 69.61 kB / 73.10 kB transferred
fullscroll: 148.15 kB / 155.19 kB transferred

600
initial: 44.22 kB / 47.20 kB transferred
fullscroll: 126.72 kB / 133.75 kB transferred

There are small bumps in full scrolled, but a significant saving on initial load. I think this might be because we account for the minutia of padding as the strings generated using a tool to get the exact amount. I feel the understandability of using a more structured API will allow us to be able to move away from current layouts more easily, but also optimise more easily too, so worth it.

I'm going to wait until #7371 is merged before I review this.

@alexwlchan - merged, sorry just had the description writ up, so put it in.

Converting to draft as I've thought of a better way to introduce this.

@wellcomecollection/js-ts-reviewers I've refactored the refactor to:

Create the new exhibition PrismicDocument
Attach the prismic document to the exhibition model. This would convcern me with data transfer sizes, but we never do this async.
Pass that document to the ExhibitionPromo
Use the new PrismicImage in that promo
☝ the refactoring to the image component explained in the description

This allows me to keep creating and using the new prismic stuff, which will then allow me to remove the old types and parsers.


fix dotenv package link

the current package link is incorrect

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

The current link works but the import name changed from config to load in std/dotenv recently. x/dotenv is not updated anymore as far as I know, so it still uses the previous name.


Error while CreateThis : Invalid URI: The URI is empty.

I keep getting this error, then it tells me to restart and It happens again
osu!: b20180413.2
Sync: 2.17.0
Windows 64 bit

Please give some error log or screenshot :smile:

Same Issue here

Very sorry, i restart the server but not re-cache latest version in to memory.
I was already put the cache and now may work fine.


Milestone 5: UI

So far, you have implemented all the frontend functionality of the bookstore management app using React and Redux. However, the application still looks very ugly. In this milestone, you will follow the provided design specs to build a UI for your app.
Live here: https://muffinbookstore.herokuapp.com

i need the "add book" form below, the drop-down category-filter and the submit


PLS update I want boobs

Hello. My name is Jumanji. I am very good programmer for google. I live in India and hate Pakistan. I met this hot tub twitch streamer ladyboy and sent her 50bits which is like arm and leg of holy cow (a lot).  But I love her and I need to send her more money.
Can you please update overlay so I can learn Tekken and kill Arslan Ash (in Tekken) from Pakistan and win Harada money for place Nr 1 in prestigious Jefrey Epstein pedophile EVO tournament.?  I play Jack 7

No.

Done.


all: fix sync.Once copy

We're doing object copy on String call, but it makes race detector
angry: copy of sync.Once and changing its state at the same time. Also,
it fixes three vet warnings about passing lock by value.
ping @aaronlehmann @stevvooe

Nice catch. Hopefully this finally fixes the race detector issues.

LGTM


AJAX don't working with this debugbar

Subj..
When this panel is turned on - AJAX does not work (AJAX-alert don't show ((( )

Update libraries/Profiler.php // _get_assets()
Add 1 Line
echo 'jQuery.noConflict(true);'; // jQuery Not Found Bug Fix
ex)
protected function _get_assets()
{
ob_start();
echo ''."\n";
echo ''."\n";
return ob_get_clean();
}
Please refer to url for this problem.
http://phpdebugbar.com/docs/rendering.html#managing-jquery-conflicts // Managing jQuery conflicts


new python lib pafy init version 0.3.74

Add new python lib: https://github.com/mps-youtube/pafy

@odi: could you squash all commits into one, rebasing against current master?

Thanks!


refactor the form section for desktop and mobile view

Improved the styling of the form section of the website both in desktop and mobile view.
Desktop View

Before:
After:

Mobile View

Before:
After:

Can someone please help me in understanding why these checks are not passing and how I can resolve this?


bdf_lexer not available

(UndefinedFunctionError) function :bdf_lexer.string/1 is undefined (module :bdf_lexer is not available)

I think you need to add the src folder to the hex package.

:O Right! Anyway, I'm going out from the yecc and leex, Hopefully I can release a new version today with a new parser. Thanks @ConnorRigby !!


Application crashes when you switch from Mozc to other IMEs such as MS-IME

Description
mozc_ja_tip{32.64}.dll causes access violation when switching to another IME, which results in application restart.
Steps to reproduce
Steps to reproduce the behavior:

Check out b861ff249766d5750ac72e308204aac69e7c41dd, build Debug version, and install it.
Open notepad.exe
Enable Mozc on notepad
Switch to MS-IME

Expected behavior
You can switch to MS-IME.
Actual behavior
notepad.exe will be relaunched due to unhandled exception at the following location.
https://github.com/google/mozc/blob/b861ff249766d5750ac72e308204aac69e7c41dd/src/win32/tip/tip_text_service.cc#L1229
Exception thrown: read access violation.
this->**ptr_** was 0xFFFFFFFFFFFFFFFF.

Version or commit-id
b861ff249766d5750ac72e308204aac69e7c41dd.
Environment

OS: Windows 11

Investigations
While the deterministic app crash started happening from b861ff249766d5750ac72e308204aac69e7c41dd, the root cause is a bit more complicated.

There had been a kind of use-after-free issue in TipTextServiceImpl::RemovePrivateContextIfExists().
Our migration to ComPtr<T> at b861ff249766d5750ac72e308204aac69e7c41dd made it possible to detect such a problem as a runtime error in a reliable manner.

Here is the entire logic of TipTextServiceImpl::RemovePrivateContextIfExists().
https://github.com/google/mozc/blob/b861ff249766d5750ac72e308204aac69e7c41dd/src/win32/tip/tip_text_service.cc#L1216-L1237
The issue is that private_context_map_.erase(it) triggers ComPtr<T>::InternalRelease() at the line 1224. context.As(&source) at the line 1229 should have been done before ComPtr<T> gets released.

Thanks for catching the issue. I think we can switch to absl::flat_hash_map and then use extract() so the object won't get destroyed.


UTXO Support Fixes and Tweaks

[x] Spend UTXO when detaching assets
[x] Attach: use destination field to specify the vout to use instead an arbitrary UTXO
[x] Attach: remove source field; use the transaction source instead
[x] Detach: remove source field; detach all UTXO with balances in the inputs
[x] Detach: make destination optional; detach to utxo_address.
[x] Don't use other utxo with balance when composing utxo move

[x] Double-check the spelling and grammar of all strings, code comments, etc.
[x] Double-check that all code is deterministic that needs to be
[x] Add tests to cover any new or revised logic
[x] Ensure that the test suite passes
[x] Update the project release notes
[x] Update the project documentation, as appropriate, with a corresponding Pull Request in the Documentation repository

@adamkrellenstein @wilfreddenton @DerpHerpenstein with all the good ideas described here https://github.com/CounterpartyXCP/counterparty-core/issues/2624#issuecomment-2446892916 there are too many changes to do this properly in utxo.py.. so I took the opportunity to split the contract into two attach.py and detach.py, it's much cleaner and readable. From the activation it will be these two contracts that will be used instead of utxo.py. Sorry for this first review before a refactor!

We primarily reviewed attach.py and detach.py. Our feedback mainly focuses on the following two points for your reference:

To ensure detach transactions without non-OP_RETURN outputs can be processed correctly, "sources" should be returned when there's no "non-opreturn" in the get_utxos_info method. Consequently, the logic in attach.py related to checking for bindable UTXOs will need adjustment.
Avoid attaching assets to already spent UTXOs whenever possible—either burn the assets or return them to the relevant address.

Thank you for this review!

see my comment above
it's not possible anymore! the assets are always attached to the first non-OP_RETURN output or to the destination_vout  output

It all seems good. @ouziel-slama Appreciate your work.

Thank you so much  for your great feedbacks!!

@adamkrellenstein @DerpHerpenstein @wilfreddenton ok for you to merge ?

@ouziel-slama do the release notes need tweaking?

@ouziel-slama do the release notes need tweaking?

I don't think. Just added this line at the end of the last paragraph:
"A UTXO move with a transaction that contains only a single OP_RETURN output behaves like a detach"


Add charm for minio console (web portal for minio)

Logging this here as it relates to minio, although it does not really affect this charm specifically.
We could add an additional charm to provide the minio console (similar to the Argo server charm)

Minio console is currently running on a random port of the minio container.
We can specify this port using --console-address ":9001". Additionally, this port can be handled in the same manner that port 9000 is.

This PR should fix it: https://github.com/canonical/minio-operator/pull/36


chore(main): release 1.2.0

:robot: I have created a release beep boop
1.2.0 (2023-09-18)
Features

parallelise recursive create (#26) (9e2dcd9)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/aidanaden/canvas-sync/releases/tag/v1.2.0 :sunflower:


Minimum universal react API

Hi, I've been working on https://github.com/guidsen/react-simple-universal that solved the boilerplate involved with universal React Apps.
I'm really curious about your thoughts about this and would love to have some help evolving this repo.

Hi,
Closing this since it's not a issue related to this repo. Thanks for the tip though, I will check out your project.


Try again using Dask to load Satellite data, but use chunks={}; and don't process entire array

Don't normalise the entire array.  That's what causes dask to take multiple seconds to think about what it's going to do.  Instead, normalise after selecting.

nope, don't, dask is too slow.


ImportError when  import taso

I build TASO on ubuntu18.04(on cuda) and meet error when 'import taso' in python3.
here is error info:
Python 3.8.6 (default, Oct  6 2020, 03:22:36)
[GCC 7.5.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

import taso
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.8/dist-packages/taso-0.1.0-py3.8-linux-x86_64.egg/taso/init.py", line 1, in
from .core import *
ImportError: libtaso_runtime.so: cannot open shared object file: No such file or directory

And a Cmake Warning occured when cmake it and it seems it doesn't matter.
CMake Warning (dev) in CMakeLists.txt:
Policy CMP0104 is not set: CMAKE_CUDA_ARCHITECTURES now detected for NVCC,
empty CUDA_ARCHITECTURES not allowed.  Run "cmake --help-policy CMP0104"
for policy details.  Use the cmake_policy command to set the policy and
suppress this warning.
CUDA_ARCHITECTURES is empty for target "taso_runtime".
This warning is for project developers.  Use -Wno-dev to suppress it.
Thanks

I had the same problem, did you find any solution ? I had the same cmake warning

you can try cp /usr/local/lib/libtaso_runtime.so /home/yourname/anaconda3/lib/


Add Promise return type doc in Async client

Looks better?

Would remove "MUST" as the message is more for the user, and people implementing the library must conform with the view of the user

A part from that :+1:


BUG: _time_mask does not work properly for non-uniformly spaced inputs

See:
>>> from mne import _time_mask
>>> import numpy as np
>>> _time_mask(np.array([0.4]), tmin=1., sfreq=1000.)
array([ True], dtype=bool)
>>> _time_mask(np.array([0.4, 1]), tmin=1., sfreq=1000.)
array([False,  True], dtype=bool)
>>> _time_mask(np.array([0.4, 1]), tmin=0.5, sfreq=1000.)
array([ True,  True], dtype=bool)

@jaeilepp I think you wrote the deltas.min() stuff that causes this, can you fix it?

(in case it's not clear, the first and third cases are bugs, but the middle one is fine)

I'm not sure why the third case is a bug. I thought we wanted the _time_mask to be inclusive i.e. 0.5 is closer to 0.4 than 1. Unless you mean that the 'closeness' should be defined with sfreq taken into account.


Unnecessary use of SafeMath in StandardToken

The issue is for the following line:
https://github.com/OpenZeppelin/zeppelin-solidity/blob/5cf503673faea92c1b5c615c3f8358febf06e160/contracts/token/StandardToken.sol#L81
The use of SafeMath adds the following check:
https://github.com/OpenZeppelin/zeppelin-solidity/blob/f3867f847722b298c360a9a0158c7aa89c7d557c/contracts/math/SafeMath.sol#L23
However, exactly that is checked right before:
https://github.com/OpenZeppelin/zeppelin-solidity/blob/5cf503673faea92c1b5c615c3f8358febf06e160/contracts/token/StandardToken.sol#L78

https://github.com/OpenZeppelin/zeppelin-solidity/pull/591 @maraoz @ritzdorf

Exactly as Brandon explained.


Migrate to new animation for button

Background
Now we have new animations for the emulation buttons
Changes

Create new ComposableEmulateButton and ComposableEmulateButtonWithText
Refactor all old buttons to new ComposableEmulateButtonWithText

Test plan
Try emulate and send nfc/subghz keys

End some design by placeholder


Updated unit tests in src/transport/raw/tests/ to use PW instead of NL.

These changes are replacing NL unit tests with pigweed unit tests, continuing the efforts of #29342 and others.
I updated the tests in src/transport/raw/tests/
The order which the tests appear in TestTCP.cpp and TestUDP.cpp was changed so that they will be run in the same order that they were run in the old NL version.
The tests in TestTCP.cpp and TestUDP.cpp had fixtures that included an instance of chip::Test::IOContext which needed to go into the test class so that it is available to all the tests that use it.

The order which the tests appear in TestTCP.cpp and TestUDP.cpp was changed so that they will be run in the same order that they were run in the old NL version.

Order-dependent tests should be fixed. If that's the case with this unit-test, then fix the test, or at least submit an issue for that.

@jlatusek any chance you can do another review pass and see resolution of comments?
@feasel0 this seems to require conflict resolution on openiot files

@andy31415 I reviewed the changes. I'm starting a holiday, so I might not be able to review them the last time. I think this is the last list of changes.


Using of discard probabilities

As I can see the 'ws' variable representing discard probabilities of each word is unused. Should it be applied for calculating weights?

Yep. Calculated from https://github.com/theeluwin/pytorch-sgns/blob/master/train.py#L57 and used in https://github.com/theeluwin/pytorch-sgns/blob/master/train.py#L36
It's a subsampling method from https://arxiv.org/pdf/1310.4546.pdf section 2.3.


Regression from 4.0: You can no longer send a streamed response

In 4.0 I could write to the output stream in chunks, and then close the stream and the response. But I guess now, Grapevine checks and tries to close the response without checking if it's already closed resulting in an exception at the end of the response (after all the data has already been sent)
In theory just checking if the response has closed first would be sufficient, but a more sensible system would be to have a "MarkComplete"-like method so we can manually handle the outputstream and then let Grapevine know that the response is finished.

Can you provide a code sample of what you are referring to? Both from 4.0 and what you are seeing in 5.0 would be helpful.

Essentially if I wrote to the Output stream directly I could then do this in 4.0:
            context.Response.Advanced.OutputStream.Close();
            context.Response.Advanced.Close();

And all would be well.
But now it seems that an attempt is made (and exception thrown) to close it as though I haven't sent any data as ResponseSent is not set to true. I've sorted it on my end by adding this to HttpResponse.cs and calling it after closing the output stream:
        public void MarkSent() {
            ResponseSent = true;
            Advanced.Close();
        }

I see. So you are using the HttpResponse.Advanced field to write directly to the output stream, and then closing the output stream and the HttpListenerResponse yourself, but you aren't setting the ResponseSent property of the HttpResponse at the same time, which is what would happen if you called SendResponseAsync.
If you are going to circumvent the SendResponseAsync method, then you will need to set the ResponseSend property yourself, too. But you can't set that field directly because of it's accessors.
So, you need a way to mark it as sent when you bypass the SendResponseAsync method, right?

Correct. Which I've done with a MarkComplete method in my fork which closes the stream and marks it as sent for now


Fix datarace on git.GlobalCommandArgs on tests

Should be part of #1441

If the reason to constantly change the global options is that some commands require LFS settings and some commands don't, isn't it better to simply have two sets of global options?

@guillep2k so in the git_test we create some LFS files as a client. We want the LFS filters to run to install them into the client repository that we are going to push to Gitea. That is the only reason for changing the filters.

@guillep2k Only a little git commands need that changes, so I think that's unnecessary.

Codecov Report

Merging #9162 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #9162      +/-   ##
==========================================
+ Coverage   41.01%   41.03%   +0.01%
==========================================
  Files         553      553
  Lines       72026    72041      +15
==========================================
+ Hits        29545    29562      +17
+ Misses      38750    38747       -3
- Partials     3731     3732       +1

Impacted Files
Coverage Δ

modules/git/command.go
92% <100%> (+0.42%)
:arrow_up:

modules/git/repo.go
45.11% <100%> (+1.04%)
:arrow_up:

modules/git/commit.go
52.09% <100%> (+0.94%)
:arrow_up:

models/unit.go
62.16% <0%> (-5.41%)
:arrow_down:

modules/indexer/indexer.go
55.26% <0%> (+10.52%)
:arrow_up:

Continue to review full report at Codecov.

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

make l-gtm work


When grouping, the values in the cells disappear

Steps to reproduce the bug

changed the date type column format to MM/dd/yyyy
I click grouping in the menu and the values in the cells disappear

Expected results
When grouping, the value must remain in the cell
Actual results
When grouping, the values in the cells disappear
Code sample
  PlutoColumn(
    filterPadding: EdgeInsets.zero,
    titleSpan: TextSpan(
        text: 'Date',
        style: TextStyle(
          color: Colors.black,
          fontSize: 16,
          fontWeight: FontWeight.w400,
        )),
    width: 150,
    title: 'Date',
    field: 'data',
    type: PlutoColumnType.date(format: 'MM/dd/yyyy'),
  ),

Execution Environment
Flutter version
Flutter version is 3.16.4
PlutoGrid version
PlutoGrid version is 7.0.2
OS
Ubuntu 22.04.3 LTS

I took the example of the date type column type and added grouping. Values in cells with non-standard formatting disappear

I also ran into the same issue.


Question: ng-click in custom template doesnt fire

thats my template:

the ng-click inside the a doesnt fire, so no alert! what might be wrong here?

@digitalkaoz have you solved that?

yeah by using another tree component ;)

:D can you tell me which?

in the end it was some jquery treeview component, not as sexy as a angular one, but that one worked ;)

Just FYI there's no reason you can't use ng-click inside a template. Your example doesn't work simply because alert is not defined within the context of your angular expression. E.g.:

  <button ng-click="alert('foo')">clicky</button>

Clicking the button here will not generate an alert.

I don't know what I'm doing wrong, but I've tried several places where to put ng-click.

In the controller I have treeNodeClick(ivhNode) which is set in ivh-treeview-on-toggle. It works fine. But in the same controller I have also clickHandler():
$scope.clickHandler = function() {
    console.log('clicked!');
};

and it doesn't work.
I need that functionality because I want to be able to handle ivh-treeview-on-toggle on a node which has empty or none children property.
@jtrussell do you have any workaround for this?

Each node has an isolate scope - even when passing the template as transcluded content you won't have access to the transcluded scope. The means individual nodes can't see methods exposed by your controller.
You can use events (e.g. ng-click="$emit('trvw_click', node)"), create a directive which attaches click handlers to your nodes, etc.
BTW - Are you hoping to fetch new nodes when a "leaf" is expanded? You may want to consider creating a directive which does that and using it as the leaf twistie.

I have a following component:

On the left is the tree which code I mentioned in the comment above.
On the right is simple ng-repeat list of the content of folder selected in the tree on the left.
You can see blue expanded folder Marketing on the left and it's content fetched from the Google Drive API.
What I want is, when I click on the folder HR (which has no children in the tree model because only folders are loaded in the tree) then content of this folder will fetch to the right side.
I can't do that because when the node is a leaf, none of the listeners can handle it.

Yes, I'd suggest using a leaf node template that supports "async" expanding and also communicates fetched nodes as necessary (e.g. by broadcasting an event or interacting with a service). Here's a rough hacked together demo:
http://jsbin.com/vatexa/edit?js,console,output

Thx, finally I solved it by ng-click="$emit('trvw_click', node)".
Maybe you can do something like ivh-treeview-on-click handler similar to ivh-treeview-on-toggle to cover these cases.


CC license icons don't need underlining

If you go to a photo page and hover over the CC icons you'll see a small line appear behind them. The a element for the CC license icons shouldn’t have text-decoration: underline on :hover.

Fixed


WIP: use packages from prometheus/common instead of prometheus/prometheus/pkg

This commit depends on the change https://github.com/prometheus/common/pull/101 which allows developing and using tsdb without needing prometheus dev branch

May I ask why you want to change this?
@fabxc

The dependency should only be used for some tests and the benchmark. The main library does not depend on it AFAIK and thus it should work okay with vendoring.
It's a bit annoying right now because you have to checkout the dev-2.0 branch, agreed. But that problem will solve itself soon enough.
I think the prometheus/pkg/textparse should not be in common. It's a very specialized way of parsing, purely done to serve some optimizations in Prometheus. The API is awkward and of little use in the more general case.

All good... I'll close the PR in a bit... Sorry about that
On Tue, Sep 5, 2017 at 6:03 PM Fabian Reinartz<EMAIL_ADDRESS>wrote:

The dependency should only be used for some tests and the benchmark. The
main library does not depend on it AFAIK and thus it should work okay with
vendoring.
It's a bit annoying right now because you have to checkout the dev-2.0
branch, agreed. But that problem will solve itself soon enough.
I think the prometheus/pkg/textparse should not be in common. It's a very
specialized way of parsing, purely done to serve some optimizations in
Prometheus. The API is awkward and of little use in the more general case.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/tsdb/pull/136#issuecomment-327223154, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAHMTdeCCk3cwgfKQ9yKDBm6LxuZ9VNvks5sfXDdgaJpZM4PNJZq
.

FWIW since prometheus depends on tsdb, would it maybe make sense to move text parse and labels over to tsdb?


Color changes

Gradients, glowing effects added to events section and added navigation responsiveness in events-workshops section

Everything is good


Fix formatting HAProxy doc

What are your changes?

Moved the agent IP note inline with example.
Fixed formatting of bullets.

What type of changes does your doc introduce?

[x] Bug fix
[ ] New feature

What is the urgency level of this change?

[ ] Blocker
[ ] High
[x] Medium

I have completed these items:

[x] I have tested all commands and code snippets.
[x] I have built locally and tested for broken links and formatting.
[x] I have made this change for all affected versions (e.g. 1.7, 1.8, and 1.9).
[ ] My doc follows the style guide: https://github.com/dcos/dcos-docs#contributing.

Ping @emanic, @sascala, or @joel-hamill for reviewing pull request changes.
If you included a comment with your commit, it appears here:

@nlsun let me know what you think.

Other than that it looks good

@sascala ready for merge


Update Sentry SDK

Hi, I’d like to help with this. Would you mind if I open a PR, assuming no one else is already working on it?


Automated Package Upgrade

:tada: This PR is included in version 2.0.28 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


:sparkles: add repository functions

Add repository functions
close #120

There is no unit tests for repositories functions


[refactor] #4126: test to prevent cross chain replay attacks

Description

Linked issue

Closes #{issue_number}

Benefits

Checklist

[ ] I've read CONTRIBUTING.md
[ ] I've used the standard signed-off commit format (or will squash just before merging)
[ ] All applicable CI checks pass (or I promised to make them pass later)
[ ] (optional) I've written unit tests for the code changes
[ ] I replied to all comments after code review, marking all implemented changes with thumbs up

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
3647 unchanged lines in 60 files lost coverage.
Overall coverage decreased (-0.3%) to 56.533%

Files with Coverage Reduction
New Missed Lines
%

core/src/sumeragi/network_topology.rs
1
98.78%

tools/kagami/src/crypto.rs
1
12.12%

data_model/src/metadata.rs
2
78.87%

primitives/src/unique_vec.rs
2
91.24%

config/src/kura.rs
3
80.0%

config/src/logger.rs
5
72.73%

logger/src/lib.rs
5
94.12%

tools/kagami/src/main.rs
5
0.0%

crypto/src/signature/secp256k1.rs
7
96.09%

data_model/src/smart_contract.rs
7
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
22517

Relevant Lines:
39830

💛  - Coveralls


Can this tool calculate the THD vs Time of a "chirp" waveform

Can this tool get the THD vs Time of a "chirp" waveform?

Not really, no.  If the chirp is slow enough, you could run it through the THD function in small chunks, though.

@abrahamcn
Is there anything you need from me on this it can I close it?
I think you would need a different algorithm to process actual sweep signals. Stepped sweep signals should work fine as long as you process chunks less than one step.


Add built-in redis templates

Add redis templates backed by kubernetes/aws/alicloud.

Environment

Walrus version: f94d57de903a925f2bd72d34b5aa1eaf8213f6ad
UI version: dev-ab43587

Test Result:

terraform-kubernetes-redis
terraform-alicloud-kvstore-redis
terraform-aws-elasticache-redis
terraform-static-redis

Issues:

Deployment fails if you don't fill in the password. https://github.com/seal-io/walrus/issues/1475
Failed to deploy alicloud/aws redis if you don't delete the Domain Suffix in UI schema. Same reasons as above.
Failed to deploy the aws redis using the default value cache.t2.micro of class field.

[kubernetes-redis]
The requirements for password is 16-32 chars but if you don't input one the generated password is 10 chars.

[alicloud-redis]
Enabled Publicly Accessible, but cannot connect to the address.

[x] kubernetes redis
[x] static redis
[x] alicloud redis
[x] aws redis

Verified in main.