Update README

The README is horribly out of date. Rewrite it with all current sub packages, descriptions and plots.

I was thinking we should revamp this while we're working on it, especially since as the number of sub packages grows, this README will get unwieldy.
First of all, we need install instructions.
Then perhaps a short summary of each sub package with no images but a link to the sub package README, which has more detail, references, maybe an example, and nice plots.
What do you think @ExoCTK/development

@hover2pi This plan sounds reasonable.

Ok, @catherine-martlin and I are going to meet about it tomorrow to plan our assault.

AT DAWN WE RIDE, @hover2pi . (JK, more like 3pm.)

Feel free to pull me in if you want my help!

This README will be our master version of documentation which we will use to wrangle the website and the Read the Docs. First steps will be to remove the initialisms; provide more details in projects that are done/further along; also update the general info (see website for example).
@julesfowler and @hover2pi - I will want to meet with you both to go over the modules and update our documentation on these.

This is dealt with by #83 . Closing this now since it's under there.


Cygwin hooks for stdenvNative and cygwin fixes for various packages

Could you please rebase this branch relative to the current master and force-push the new version?

@peti i'll do it during next week

So much to review. Maybe this can be splitted in multiple commits? Don't know.

Some of the .patch files in there are huge. Unless you made all the changes yourself (in which case we should probably look at them very carefully), It seems like it would be cleaner to just refer to wherever the new versions of the source files come from.

@copumpkin: The patches are mostly taken from cygwin tarballs, i.e. there are no direct urls to them.

@chaoflow @copumpkin what if we create derivation for those patches and extract patches ? it should be possible to refer to patches easier to keep them up to date.

Apart from the "sed-i" issue, non-cygwin impact seems relatively safe, but it's still a mass rebuild, and it will be better to screen this for larger build regressions before merging to staging.
As for the Travis error, it sounds like an escaping issue unrelated to this. We have python27Packages."plone.synchronize-1.0.1", so there are dots inside the attribute name (which is really ugly). The message seems like the quotation is missed (searching for plone attribute).

Patches: as suggested, on your place I'd consider creating a derivation that extracts all the cygwin patches, so it's easier to update (once upon a time); then they could be used like optional stdenv.isCygwin "${cygwinPatches}/pkgconfig-foo.patch".

Is this still alive? It seems exciting!

@copumpkin still alive. i hope to find time to finish this soon.

"if" was used instead of "stdenv.lib.optional/stdenv.lib.optionals/stdenv.lib.optionalString" to not trigger stdenv rebuild.

I see, but for the sake of readability... on staging we do a stdenv rebuild almost every week.

@vcunat this PR is being here for almost half a year. it is really hard to keep it up to date because of patches changing for every version. i would really like to merged it as is, otherwise we would lose what we have currently working.

OK, I thought the PR is waiting for you to finish something

i hope to find time to finish this soon.

it is an old comment @chaoflow and I rebased it 2 days ago.

manually merged here

I see; github doesn't notify participants when you add or change PR commits.

Meanwhile, we got around to publish the report: http://ternaris.com/lab/nix-on-windows.html


Version  Duplicate.

Environment

Dubbo version: 2.7.2
Operating System version: win10
Java version: 1.8

this issue
[DUBBO] Duplicate class org/apache/dubbo/common/Version.class in 2 jar [file:/E:/maven/repository/default/org/apache/dubbo/dubbo/2.7.2/
dubbo-2.7.2.jar
!/org/apache/dubbo/common/Version.class, file:/E:/maven/repository/default/org/apache/dubbo/dubbo-common/2.7.2/
dubbo-common-2.7.2.jar
!/org/apache/dubbo/common/Version.class], dubbo version: 2.7.2

In dubbo-2.7.2.jar, it contain all of dubbo jar.  It is repackaged as inner class in a jar.

In dubbo-2.7.2.jar, it contain all of dubbo jar. It is repackaged as inner class in a jar.

I added a new serialization module 'dubbo-serialization-protostuff ', and this problem arises.  Y^.^Y

It's okay like this :

org.apache.dubbo
dubbo-serialization-protostuff
${dubbo.version}

org.apache.dubbo
dubbo-common

It's okay like this  :
<dependency>             <groupId>org.apache.dubbo</groupId>             <artifactId>dubbo-serialization-protostuff</artifactId>             <version>${dubbo.version}</version>             <exclusions>                 <exclusion>                     <groupId>org.apache.dubbo</groupId>                     <artifactId>dubbo-common</artifactId>                 </exclusion>             </exclusions>         </dependency>


Are the training loss and validation loss recorded?

Hi, Dear:
Thank you very much for your code. I am reproducing your training process. I wonder what your training loss and validation loss are during the training process, and I want to align them with your training process on dataset Magicoder-OSS-Instruct-75K and datasets--ise-uiuc--Magicoder-Evol-Instruct-110K
Thx

Thank you for your open source, I am replicating your fine-tuning process according to the code on github. Do the results of train loss=0.16 and eval_loss=0.21 I trained on the 75k dataset match yours? I will continue training on the 110k dataset.
I trained for 4 epochs and indeed started overfitting after the second epoch.

Magicoder-S-CL.json
Magicoder-CL.json
Magicoder-S-DS.json
Magicoder-DS.json
Hi, here are the trainer states. Hope they can help!

Magicoder-S-CL.json Magicoder-CL.json Magicoder-S-DS.json Magicoder-DS.json
Hi, here are the trainer states. Hope they can help!

Thank you very much, my training process is basically the same as your loss metric and the test results on humaneval dataset are basically consistent

Good to hear you can reproduce it. Yeah we did observe that the infilling capability was at least not decreasing. We believe this is because the model learned some general alignment during the instruction tuning, and infilling is a kind of alignment based on the surrounding context. Further study of this phenomenon would be interesting.


EAGLE-789: Add a new publisher to write alerts into a local file

https://issues.apache.org/jira/browse/EAGLE-789

LGTM


ClusterLayer

Hi,
You have a great example. My team is using webpack / Arcgis 3.18 and Angular2. We used your example to help us load the esri / dojo modules. However, we really need to get ClusterLayer working. Could you please show us how or offer advice on how we can integrate one of the following two projects:
https://github.com/Esri/cluster-layer-js
https://github.com/nickcam/FlareClusterLayer
Thanks,
Kai

This repo shows how to use cluster-layer-js:
https://github.com/tomwayson/esri-webpack-babel#dojo-lbraries
You could probably adopt those patterns to work w/ v3 of FlareClusterLayer b/c it looks like that library is distributed as something you can load as a Dojo package
As for his (TypeScript) v4, you could probably adopt his instructions 4.1 to work w/ webpack instead of esri-system-js. I won't be able to help you with that. A while back I naively assumed that would be an matter of npm install and import, but my experience trying to publish angular2-esri-loader in a way that it could be easily consumed in an Angular 2 application built w/ webpack (or presumably SystemJS) was so painful that I don't want anything to do with any problems related to publishing or consuming TypeScript libraries for Angular 2.

Issue solved. Thanks!

That's great. How did you solve it?


Feature request > format tests times for easier readability

Hello,
I would like to propose adding an option to make easier to read the test times.
So instead of having something like this:

You should really fix these slow tests (>2000ms)...

18859ms to run x
16441ms to run y
12352ms to run z
2352ms to run z

We could have something like:

You should really fix these slow tests (>2000ms)...

18.8s to run x
16.4s to run y
12.3s to run z
2352ms to run z

Something similar to Carbon::diffForHumans().
Great job btw!

Hi @marcelopm! That's a great idea. Based on your example, should the report print time in seconds once exceeding 10000ms?

Not sure @johnkary, maybe it could be configurable by an optional param with a default value?
Thanks.

I think something as simple as adding a period for some number formatting could take it most of the way. So instead of 18859ms it would say 18.859ms (or with a comma instead)


KAFKA-17593 [1/N]: Async regex resolution for subscriptionPattern in HB

This PR includes:

add RE2J dependency (license added and validated)
add new records to persist regular expression resolution
regex validation and async eval triggered from heartbeat
persist regex eval result and replay them to make them available

Closing this, is being split in several PRs


[Primitive] Tag component

Tag / label UI component

Review:

[ ] Large tag has 30px height, should be 26px

Reviewed; ready to close.


feat(cli): add Markdown support for CLI

Summary

Enhance Lacework’s Timeline/commenting functionality to better support investigation workflows, specifically by including the ability to leverage Markdown.
How did you test this change?

Demo video:
https://github.com/lacework/go-sdk/assets/132718757/239261c3-6b0c-4af1-bd48-cf27a0efea38
Before:

After:

Issue

https://lacework.atlassian.net/browse/ANEP-2048

@jasminesun-lw , can we add some screenshots to the description with before+after side-by-side rendering of plaintext comments?

@jasminesun-lw , we will want and need some updated automated testing for this using the -f flag...

Check windows 🪟

Also, this is exciting!!

@jasminesun-lw , this looks good to me.  I'll let the GROW team weigh in on this as well.  Can we also create a GROW Jira ticket to look into windows markdown rendering support?

Ping!


⚠ Bofrost.at has degraded performance

In 1a07452, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1640 ms

Resolved: Bofrost.at performance has improved in fdffe6f after 6 minutes.


#366 - 2 new lint checks: disallow pull-left/right on .row and .col-- classes

A fix for #366 which I created an issue for this morning.  Seemed easy enough to fix, so I made new rules for this.
New rule E050 will disallow .pull-right and .pull-left on the same element as a .col-*-* class

New rule E051 will disallow .pull-right and .pull-left on the same element as a .row class

@XhmikosR I also fixed this one

Here are the docs to add for these rules:

E051
.pull-right and .pull-left classes, and manual style attributes with float: left or float: right are not allowed on .col-*-* elements
The grid already uses css floats to work, so manually applying floats like this will break the way the grid works.
Wrong:

E052
.pull-right and .pull-left classes, and manual style attributes with float: left or float: right are not allowed on .row elements
The grid already uses css floats to work, so manually applying floats like this will break the way the grid works.
Wrong:

Thanks!


MonitoringV2 sometimes includes an alert name in the subject of the email and sometimes it does not

Rancher Cluster:
Rancher version: 2.5.5
Number of nodes:
Node OS version:
Downstream Cluster:
Number of Downstream clusters:
Node OS:
RKE/RKE2/K3S version:
Kubernetes version:
CNI:
Longhorn:
Longhorn version:
CPU per node:
Memory per node:
Disk type: HDD/SSD/NVMe
Network bandwidth between the nodes:
Other:
Underlying Infrastructure: AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal
ssue description:
MonitoringV2 sometimes includes an alert name in the subject of the email and when multiple alerts are triggered, it does not show the alert name.
Business impact:
The customer is unable to find what alert is triggered when multiple alerts are fired at the same time.
Troubleshooting steps:
No
Repro steps:
Fire multiple alerts at the same time.

Workaround:
Is workararound available and implemented? No
What is the workaround:
Actual behavior:
Multiple alerts fired at the same time don’t have an alert name in the alert
Expected behavior:
Multiple alerts fired at the same time should have an alert name in the alert, like it is there in a single alert.
Files, logs, traces:
Single alert containing alert name at the starting
[FIRING:1] (Cluster-CPU-usage-more-than-95% cattle-monitoring-system/rancher-monitoring-prometheus critical [realtime])
Multiple alerts missing the alert name at the starting
[FIRING:2] ([Warning] [merchantscreening] cattle-monitoring-system/rancher-monitoring-prometheus [online])
[FIRING:2]kube-state-metrics (Deployments-have-lower-number-of-pods-in-card-merchant-screening-* http <IP_ADDRESS>:8080 [Warning] rancher-monitoring-kube-state-metrics-5c549477ff-wgccj [merchantscreening] cattle-monitoring-system/rancher-monitoring-
Additional notes:
SURE-5088

This needs to be reproduced in 2023-Q1-2.6x and 2023-Q1-2.7x

Since this behaviour was reproducible on our chart, I decided to give it a try with the upstream version of the Kube Prometheus Stack (kube-prometheus-stack) chart. I installed chart version 45.4.0 from the prometheus-community Helm repository in a downstream RKE cluster with Kubernetes v1.25.6 on Rancher 2.7-head.

Setup instructions & replication steps

Add the prometheus-community Helm repository to your local Helm install:
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo update

Change the Helm driver so that installation does not fail on the downstream cluster with an HTTP 413:
export HELM_DRIVER=configmap

Targeting the downstream cluster, install the required CRD chart:
helm upgrade --install prometheus-operator-crds \
  prometheus-community/prometheus-operator-crds \
  --namespace monitoring-system --create-namespace

Create a values.yaml with the following content:
prometheus:
  prometheusSpec:
    ruleSelector:
      test.example.org/selected-rule: "true"

This ensures that alerts generated by PrometheusRules that match the selector are going to be picked up by Alertmanager.

Install kube-prometheus-stack:
helm upgrade --install kube-prometheus-stack \
  prometheus-community/kube-prometheus-stack \
  --namespace monitoring-system \
  --values values.yaml

Create an echo SMTP server using Python smtpd:
---
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: smtp-server
  name: smtp-server
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      app: smtp-server
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      labels:
        app: smtp-server
    spec:
      containers:
      - command:
        - python3
        - -u
        - -m
        - smtpd
        - -c
        - DebuggingServer
        - -n
        - <IP_ADDRESS>:5678
        image: python
        imagePullPolicy: IfNotPresent
        name: python
        ports:
        - containerPort: 5678
          name: smtp-port
          protocol: TCP
      restartPolicy: Always
---
apiVersion: v1
kind: Service
metadata:
  labels:
    app: smtp-server
  name: smtp-server
  namespace: default
spec:
  ports:
  - port: 5678
    protocol: TCP
    targetPort: 5678
  selector:
    app: smtp-server
  type: ClusterIP

Create an AlertmanagerConfig to target alerts towards the newly deployed e-mail server in your cluster:
apiVersion: monitoring.coreos.com/v1alpha1
kind: AlertmanagerConfig
metadata:
  name: test-alert
  namespace: default
spec:
  receivers:
  - emailConfigs:
    - from: test@example
      requireTLS: false
      sendResolved: true
      smarthost: smtp-server.default.svc:5678
      tlsConfig: {}
      to: recipient@example
    name: test-receiver
  route:
    groupBy: []
    groupInterval: 30s
    groupWait: 15s
    matchers:
    - matchType: =
      name: team
      value: test
    receiver: test-receiver
    repeatInterval: 45s

Create a PrometheusRule to fire those alerts at a regular interval:
apiVersion: monitoring.coreos.com/v1
kind: PrometheusRule
metadata:
  name: prom-rule-test
  namespace: default
  labels:
    test.example.org/selected-rule: "true"
spec:
  groups:
  - name: test-group
    rules:
    - alert: test-alert
      expr: vector(1)
      for: 0s
      labels:
        namespace: default
        severity: none
        team: test

Watch the smtp-server logs for e-mails coming in:
kubectl logs -f deploy/smtp-server

Notice that the e-mails contain the alert name test-alert in the subject line:
Subject: [FIRING:1] default (test-alert monitoring-system/kube-prometheus-stack-prometheus none test)

Create a new PrometheusRule:
apiVersion: monitoring.coreos.com/v1
kind: PrometheusRule
metadata:
  name: prom-rule-second-test
  namespace: default
  labels:
    test.example.org/selected-rule: "true"
spec:
  groups:
  - name: test-group
    rules:
    - alert: test-second-alert
      expr: vector(1)
      for: 0s
      labels:
        namespace: default
        severity: none
        team: test

Notice that in the output for smtp-server the e-mails now show FIRING:2 without an alert name:
Subject: [FIRING:2] default (monitoring-system/kube-prometheus-stack-prometheus none test)

Using the above setup instructions, I was able to confirm the same behaviour happens with the upstream chart. Whenever a single alert is firing, the e-mail is sent with the alert name in the subject line. If more than one alert is fired, then the subject line omits the alert name.

Relevant template: https://github.com/prometheus/alertmanager/blob/eea788a968c870e3bd78a228e394f745701f18a0/template/default.tmpl#L4


Fix bug passing parameters within userauth.py

Are we good to go here? Looks like a trivial change to me.

LGTM

@gsfr Megan's waiting on me to submit a test for this issue, specifically the abao test to validate the response of the list users endpoint against the raml output schema which is how we discovered the bug.  I plan to submit that shortly, before I leave today

LGTM


Use DateTimePicker with only time picker in 24 hours format

Hello
I am using date time picker with only time picker option in Blazor. My code is given below:
   $('#' + id).datetimepicker({             pickDate: false,             pickSeconds: false,             pick12HourFormat: false,              minuteStep: 1,             pickerPosition: 'bottom-right',             container: '#' + modal,             format: 'hh:ii',             autoclose: true,             showMeridian: true,             startView: 1,             maxView: 1,         })
On UI it is looking like this:

Questions
-How can I force the picker to show time in 24 hours format instead of AM and PM?
-Also what to do If I don't want to show date?

I think you could just change the formatTime setting in your settings to formatTime: 'g:i A',


[spi_device] Lint error

This commit fixes unused cmdfifo_depth errors in the lint tool. The
signal is being used in the assertion not in the actual logic.

Let me merge this as FPGA test is not needed.


Cross-site Scripting (XSS)

Vulnerability Type Cross-site scripting, in the login of administrator, and to retrieve the password and register a user from the part of the customer!

Is 3.0.2 affected? And is there a plan to fix it by 3.0.3?

Can't reproduce in 3.0.2. Closed for now


added UDAF Histogram that counts the number of times each value occurs

Why would we need this given that you can do SELECT k, count(*) FROM ... GROUP BY 1?

@martint the differences are 1) different aggregations can be
computed in a single query / pass over the data and 2) the results are
collected into a map rather than exploded over several rows.

Superseded by #3062


IDLE states on ducted unit

Hello.
First of all, my English is bad (sorry, I'm French).
I got a document from panasonic that could probably interest you.
Then, I have been using your dev for a few months. The problem that I encounter is the following: on my ductable, I will need to recover the "idle" state because I have a regulation by zone.
Do you think it's possible?
Questions frÃ©quentes.ppt  -  Mode de compatibilitÃ©.pdf

Can you define what you mean with "idle state"?
Can you give an example of what you're trying to accomplish?

By "idle state" I mean when the duct is on but not heating. When it has reached the set temperature for example.
I am trying to optimize my regulation by zone but the duct starts far too often.
Ideally, I am looking to shunt the value of the return temperature sensor


etcdserver: fix potential lease race between leader and old leader

Bad sequence:

SA (Leader), SB (Follower), SC (Follower)
SA is partitioned
SB becomes the new leader
Client CA revokes lease LA from SB
Client CA renews lease from SB (renew wont go through consensus)

Waiting here makes sure when 4 happens SB cannot be at leader state. So 5 will not succeed.
/cc @heyitsanthony @fanminshi
It would be great if @fanminshi can write a test for it.

@xiang90 i'll try to create a test case for this one. can be a bit tricky to get it right.

I did some testing and figured out this is not the correct way to do it. This does not prevent from follower to propose revoke to leader and get the request committed.
I will redo this.


Add flash to ctx.state?

Usually you want to show the flash message in a template. With ctx.state being the primary way to share messages with templates, would it be a good idea to ctx.state.flash = ctx.flash()?
I currently do this with a middleware:
exports.addFlashToState = () => {
  return async (ctx, next) => {
    ctx.state.flash = ctx.flash();
    await next();
  };
};

But that only works when you have multiple middlewares to pass through, and not in the case of e.g.:
router.post("profile", authenticated(), async ctx => {
  ctx.flash("success", "Profile successfully updated");
  await ctx.render("profile", {});
});

see https://github.com/ladjs/state-helper/blob/master/index.js#L16-L24


why maps for amcl and nav are different?

can i use the same one generated by mapping?

Hi @leehaijun
Well, You can use one map.
The reason we used two maps in here is that map_amcl is for localization purpose (amcl pkg), and the other one, called map_nav is for navigation and obstacle avoidance (move_base)


Delete the node_modules folder: rm -rf node_modules && npm install.
Reset Metro Bundler cache: rm -rf /tmp/metro-bundler-cache-* or npm start -- --reset-cache.
Remove haste cache: rm -rf /tmp/haste-map-react-native-packager-*.

The files mentioned in step 3 and 4 may not exactly have the same name (e.g. metro-cache or haste-map-metro). To make sure you delete the temp files, navigate to /tmp directory and delete anything with metro or haste in it files yourself.

In my case, the emulator was on airplane mode.
Make sure your emulator or mobile phone can communicate with the Metro server.

me too

I m facing again this issue when I upgraded to react native 0.62.0
Any idea how to resolve it ?

Pessoal, essa solução funcionou para mim:
Não foi possível carregar o script dos ativos 'index.android.bundle'. Certifique-se de que ...
Esse erro geralmente ocorre porque o sistema não conseguiu criar o pacote inicial que contém todo o código Javascript da aplicação.
1- Para resolver, comece a criar uma pasta de ativos dentro da pasta android / app / src / main.
2- Logo após, execute o comando:
npx react-native bundle --plataforma android --dev false --entry-file index.js - android-app de saída de pacotes / app / src / main / assets / index.android.bundle --assets-dest android / app / src / main / res /
3- Agora, feche o terminal e execute novamente o comando:
npx react-nativo run-android
ou fio executar react -nativo run-android
ou fio android
Fonte: https://react-native.rocketseat.dev/erros/android/

I had same error, with a wipe data for emulator on AVD problem solved

In my case, the emulator was on airplane mode.
Make sure your emulator or mobile phone can communicate with the Metro server.

Man, so simple! Mine had the network disconnected...

And even this won't work if you manually do not create the assets subfolder in the android/app/src/main folder. Thanks for the command!


Setup fails: Unsupported URL Type "workspace:"

Started encountering this error today:
> npx hyperbook setup
Removing old template
Downloading files from repo https://github.com/openpatch/hyperbook/tree/main/templates/simple. This might take a moment.

Installing packages. This might take a couple of minutes.

npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:*

npm ERR!  I move most of the features into separate packages, but encountered a few issues along the way. But now everything should work as before.
And tomorrow I can finally release a VS Code extension for rendering hyperbook pages directly in VS Code without the need of running the development server.


Preprocessing for Fine-tuning

Thank you all for this excellent work and for open-sourcing it as well!
I am interested in fine-tuning the Biomedparse model for a CT dataset. In the inference code, there are some preprocessing steps for CT scans (e.g., windowing, normalization, etc.). When preparing the dataset for finetuning, should the input images in the train and test directories already be preprocessed, or will the training and evaluation code automatically preprocess the data?

They should be preprocessed before putting in the train and test folders. If there are image types that are out of the current preprocessing categories, feel free to preprocess in the way that makes most sense for your application. The model should be able to adapt to that after finetuning.


BOP evaluation's results don't match paper's results on LM-O

Hello,
I followed the evaluation instruction
./core/gdrn_modeling/test_gdrn.sh configs/gdrn/lmo/a6_cPnP_AugAAETrunc_BG0.5_lmo_real_pbr0.1_40e.py 0 output/gdrn/lmo/a6_cPnP_AugAAETrunc_BG0.5_lmo_real_pbr0.1_40e/gdrn_lmo_real_pbr.pth
using the checkpoint that is provided in this repository. The results that I get evaluating with the BOP toolkit are the following:
{
"bop19_average_recall": 0.6371949250288351,
"bop19_average_recall_mspd": 0.80719723183391,
"bop19_average_recall_mssd": 0.6251903114186852,
"bop19_average_recall_vsd": 0.47919723183391005,
"bop19_average_time_per_image": 0.060607782814723316
}
while in the paper the results that are reported are the following

could it be that the checkpoint provided in this repository is different from the one used in the paper?

Yes. And lm bop uses a different test subset. its training images are also different. You can refer to bop challenge website for further info.

thank you. It is possible to make available the checkpoint trained on the BOP training set?

It is not trivial to share that model. As mentioned in readme, for training on bop, we did a refactor on the code, which is incompatible with code provided here. But I think it should be easy to train on bop by yourself. Similar training configs can be referred to https://github.com/THU-DA-6D-Pose-Group/self6dpp/tree/main/configs%2Fgdrn%2FlmoPbrSO. (this is another refactored version)

Thank you very much for the help.


Update transform and babel-jest docs

Summary
Clarify that when "transform" is overwritten, the babel-jest is not loaded automatically anymore and should be explicitly defined in the config.
Related to: #2096

I have a more detailed explanation in the wiki of my TypeScript starter project. I wonder if I can add another example with two code transformers (babel-jest and tsc)  in the Jest repository or add a link to that explanation somewhere in the docs?

Current coverage is 87.93% (diff: 100%)

No coverage report found for master at 51b0ad6.

Powered by Codecov. Last update 51b0ad6...273baad

@jsynowiec an example would be great! I didn't know how transform should look like until I searched Jest's tests.

@silvenon updated the Configuration.md docs with a link to the typescript example.

thank you! Sorry for making you wait.


Kotlin Algorithms

💥 Proposal
I noticed almost zero algorithms are present in the folder of Kolin. Can I add the basic Areas problem as my WoC contribution?
Kindly assign me the Areas Problems in Kotlin.
Thank You
Have you read the Contributing Guidelines on Pull Requests?
Yes

Can I take up this task? Kindly assign it to me, please. @shraddhavp

assigned @itsIapetus

I do mostly Java, but learning Kotlin for a while. Would love to add some sorting/ searching algorithms in Kotlin. Kindly assign me the issue to add some sorting/ searching algorithms in Kotlin.

assigned @iamvs-2002

Thankyou! I am on it.

I am trying to add heapsort.kt file but it is adding it in the same pull request. Is there any way I can make a new pull request for the different issue?

I have started adding the implementations.
These contributions are for DWOC - DevScript Winter of Code.
Thank you!

@shraddhavp There were some issues in the files and also it was those I had learned from youtube. So I closed the pull requests. I'd rather implement them entirely by myself and then submit them.

@iamvs-2002
It would be recommended to make separate Issues for all of them and raise PRs for them subsequently. We are here to help you out :)

@iamvs-2002
It would be recommended to make separate Issues for all of them and raise PRs for them subsequently. We are here to help you out :)


err :: Script @auto-scripts was called via post-install-cmd

In Symfony 4.1.x when deploying the app, int "---> Installing Composer dependencies" section the scripts crash with this message:
| err :: Script @auto-scripts was called via post-install-cmd
Composer version is 1.7.2

Add this to your deploy configuration:
->composerInstallFlags('--prefer-dist --no-interaction --no-dev')

This will disable the  --quiet flag from composer. Most likely something went wrong there with composer install

If you remove the --quiet flag and there are package updates wouldn't this still cause it to fail?

In my case it was due to .env file:
| err :: Executing script cache:clear [KO]
| err ::  [KO]
| err :: Script cache:clear returned with error code 255
| err :: !!  PHP Fatal error:  Uncaught Symfony\Component\Dotenv\Exception\PathException: Unable to read the "/var/www/project/releases/20200619075019/.env" environment file. in /var/www/project/releases/20200619075019/vendor/symfony/dotenv/Dotenv.php:510
| err :: !!  Stack trace:
| err :: !!  #0 /var/www/project/releases/20200619075019/vendor/symfony/dotenv/Dotenv.php(65): Symfony\Component\Dotenv\Dotenv->doLoad(false, Array)
| err :: !!  #1 /var/www/project/releases/20200619075019/vendor/symfony/dotenv/Dotenv.php(85): Symfony\Component\Dotenv\Dotenv->load('/var/www/bm-dok...')
| err :: !!  #2 /var/www/project/releases/20200619075019/config/bootstrap.php(17): Symfony\Component\Dotenv\Dotenv->loadEnv('/var/www/bm-dok...')
| err :: !!  #3 /var/www/project/releases/20200619075019/bin/console(30): require('/var/www/bm-dok...')
| err :: !!  #4 {main}
| err :: !!    thrown in /var/www/project/releases/20200619075019/vendor/symfony/dotenv/Dotenv.php on line 510
| err :: !!
| err :: Script @auto-scripts was called via post-install-cmd
[ERROR] Cancelling the deployment and reverting the changes


What is the status of flexbox support?

I see a bunch of code in there, but I'm not sure what it does. Is it usable? Should it be documented?

We have great flexbox support (#188, #192, #115), but no docs to explain it - only test cases

For future visitors, this is not exactly accurate. Flexbox prefixing fails horribly when used with block mixins (https://github.com/tj/nib/issues/291), and the only workaround in the issues is to disable prefixing altogether for the mixin (https://github.com/tj/nib/issues/312#issuecomment-132997055)
tl;dr avoid nib if you're trying to do all of these things at once:

support many old browsers
incorporate a responsive design
use block mixins for your media queries


[Port] undo remove project change in data workspace (#22283)

This PR fixes #22278. Porting fix from main https://github.com/microsoft/azuredatastudio/commit/394d88445a11a73756ff7997dc0fdccd40ac3640

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
8 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.02%) to 41.938%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/dialog/configurePython/configurePathPage.ts
1
57.02%

extensions/sql-database-projects/src/common/httpClient.ts
1
66.18%

extensions/sql-database-projects/src/dialogs/publishDatabaseDialog.ts
2
52.88%

extensions/notebook/src/jupyter/serverInstance.ts
4
75.5%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
28804

Relevant Lines:
63772

💛  - Coveralls


could not find source plugin ansible.eda.range

Please confirm the following

[X] I agree to follow this project's code of conduct.
[X] I have checked the current issues for duplicates.
[X] I understand that ansible-rulebook is open source software provided for free and that I might not receive a timely response.

Bug Summary
Documentation for an ansible-rulebook content developer does not mention ansible-galaxy collection install ansible.eda, which is required to get the first example in the Rulebook working.
Environment
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS"

Steps to reproduce

Read and complete the Installation docs
Read and complete the Usage docs
Move onto the Rulebook docs and try the first example

Actual results
ansible-rulebook --rulebook chaos.yml --inventory inventory.yml
2024-06-07 13:08:39,153 - ansible_rulebook.engine - ERROR - Source error Could not find source plugin for ansible.eda.range
2024-06-07 13:08:39,153 - ansible_rulebook.engine - ERROR - Shutting down source: ansible.eda.range error : Could not find source plugin for ansible.eda.range
2024-06-07 13:08:39,169 - ansible_rulebook.app - ERROR - Could not find source plugin for ansible.eda.range
2024-06-07 13:08:39,170 - ansible_rulebook.cli - ERROR - Terminating One of the source plugins failed

Expected results
After completing the Installation -> Usage and moving on to the Rulebook section of the docs. I expect to be able to run the first example.
Additional information
I had to install the ansible.eda collection via ansible-galaxy collection install ansible.eda. I didn't find this step in the Developer section, I just got lucky. Now I see it's in the Developer section but I'd argue it should be more front and center. Probably in the Installation section but I could see it in the Rulebook section too.
I wouldn't think to go to the Developer doc section because I figure that is for contributing to the ansible-rulebook project. I'm just looking to author content.

Hello @chrismeyersfsu
Thanks for your report. Technically, ansible.eda is not required to use ansible-rulebook, and I think we took that reasoning when writing the documentation. I agree that it might be a mistake if later we are referencing that collection in our examples. I think we should mention it.

Sorry, @chrismeyersfsu reviewing the current documentation I have found that we already have a step to install the collection, in both places, the developer section and the general installation guide:
https://github.com/ansible/ansible-rulebook/blob/main/docs/installation.rst?plain=1#L40
https://github.com/ansible/ansible-rulebook/blob/main/docs/development_environment.rst?plain=1#L31
Where and how did you consult the documentation?

:facepalm: You are 100% correct. The installation docs say to install the ansible.eda collection. https://ansible.readthedocs.io/projects/rulebook/en/stable/installation.html#installation-via-pip
Closing this issue.


[HUDI-2126] The coordinator send events to write function when there …

…are no data for the checkpoint
Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Codecov Report

Merging #3219 (85305d0) into master (62a1ad8) will decrease coverage by 44.62%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #3219       +/-   ##
============================================
- Coverage     47.51%   2.88%   -44.63%
+ Complexity     5431      82     -5349
============================================
  Files           922     280      -642
  Lines         41001   11570    -29431
  Branches       4104     947     -3157
============================================
- Hits          19480     334    -19146
+ Misses        19799   11210     -8589
+ Partials       1722      26     -1696

Flag
Coverage Δ

hudicli
?

hudiclient
0.00% <ø> (-34.58%)
:arrow_down:

hudicommon
?

hudiflink
?

hudihadoopmr
?

hudisparkdatasource
?

hudisync
5.35% <ø> (-48.90%)
:arrow_down:

huditimelineservice
?

hudiutilities
9.31% <ø> (-48.72%)
:arrow_down:

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

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


AFNetworkReachabilityManager.h generates warning "Conflicting nullability specifier on return types"

AFNetworkReachabilityManager.h generates a warning stemming from conflicting definitions of init. Specifically the following definitions conflict.
AFNetworkReachabilityManager.h's - (nullable instancetype)init NS_UNAVAILABLE; conflicts with NSObject.h's - (instancetype)init.
Warning:  AFNetworkReachabilityManager.h:115:1: Conflicting nullability specifier on return types, 'nullable' conflicts with existing specifier 'nonnull'.
Environment

Xcode Version 8.3.3 (8E3004b)
iOS 10.3
AFNetworking Version: 3.1.0
macOS Version 10.12.6 (16G29)
Installed via Cocoapods.

I am also experiencing this issue in one of my projects.
Environment

Xcode Version: 9.1 (9B55)
iOS Version: 11.1
Deployment Target: 10.0
AFNetworking Version: 3.1.0
macOS Version: 10.13.1
Installed: Manually

I'm seeing this too AFNetworking Version: 3.2.0, this silences the warning:
- (nullable instancetype)init NS_UNAVAILABLE;

to:
- (instancetype)init NS_UNAVAILABLE;

This is still happening :)
But I guess AFNetworking is not maintained anymore?


Regexp functions support

Closes #12
BREAKING :(

As other solution, string mode may be replaced directly with callable
F.text.regexp(r"(\w+-\d+)", mode=re.findall).as_("issues"),

It can be completed without making it breaking.
For example you can set mode by default to None, when you set search as True just set mode to SEARCH and show deprecation warning, when search is False set mode to MATCH but when both parameters are set just raise an error that indicates you can't set both parameters.

@JrooTJunior, okay, I'll take it.
What do you prefer enum params or callable?
If enum, in which file should I place it?


Smarter policy for /packit build

It may seem obvious to not run /packit copr-build command twice.
However, it may happen that my colleague will decide to be proactive and post comment for a build at the same moment as I'm. This will cause 2 builds and wasting for COPR resources + ref status is updated twice. So if one build was lucky enough in all aspects you will get passed everywhere and 30 second later this status is replaced with a new one. In worst case with failures.
End goal:

Only one build can provide result
Rebuild is still possible - meaning wait till I have results and then rebuild if COPR screwed it (hello mirror fedora issue)
Less confusion
??? Definitely profit

Possible solutions:

Ditch previous builds and start a new one
Do not accept new builds until current is running

This is applicable not only to comments. It would also be nice to solve this in general (e.g. for multiple pushes in a short while).
We need to see if we can easily kill the already running build.

Related: #5

This is applicable not only to comments. It would also be nice to solve this in general (e.g. for multiple pushes in a short while).
We need to see if we can easily kill the already running build.

Copr provides a way to cancel builds:
copr_client.build_proxy.cancel()

This should be easy to implement: just check if the build is running, if it is, cancel it and submit a new one.

Related: #5

@jpopelka, thanks for linking that issue.
Let's mark this one as a duplicate and focus on the other issue..
Duplicate of #5

I think @jpopelka marked #5 as "related" for a good reason. There are 2 cases here, when "duplicate" builds have to be dealt with:

a duplicate /packit build command is issued, but a build for the git ref is already running - this is the case this issue was filed for.
a new commit is pushed into the PR, rendering a build still running for the previous commit unnecessary - this is the case #5 was filed for.

On a high level implementing something that would cover both of the scenarios above would look like (pseudo code):
build_trigger():
    if build for current git_ref is running:
        ignore trigger
        return

    if build for current pr is running:
        cancel current build

    start new build

Optionally a /packit rebuild command could be provided for cases, when one would like to cancel a currently running build and restart a new one from the same commit. Could be used in cases, when one sees a build will fail due to infra issues, but doesn't want to wait until the failure reaches Packit.

@csomh I've closed this one to move the discussion to one place...
Can you please copy your (valid) comment to the #5 and close this one after that? Thanks!

@lachmanfrantisek convinced me that cancelling running jobs is the way to go: will provide one solution for all similar issues and the behaviour is consistent with other tooling (like zuul).
Updated #5 to make sure we don't forget about jobs started as a result of commands. @StykMartin please subscribe to that one if you are interested.
Closing this, this time for real :bomb: :boom: :boom: :boom:


Improve  Contact Form and Send Data on Email

Read Form in angular page
Read also Here
before  starting implementation

DONE


Test and fix the end-to-end Kubeflow on GCP Tutorial

https://www.kubeflow.org/docs/gke/gcp-e2e/
The End-to-end Kubeflow on GCP tutorial is having issues and is probably using outdated python tutorial code no longer compatible with the default version of TensorFlow in the Jupyter notebook environment setup by default. The issue related to section (Optional) Test the code in a Jupyter notebook
Here are the steps I took to before having the issue:

I created a new GCP based kubeflow cluster by running through the Kubeflow on GCP documentation and was able to get a cluster with IAP running.
I created a new Jupyter notebook to attempt running the section example, I used
gcr.io/kubeflow-images-public/tensorflow-1.13.1-notebook-cpu:v0.5.0 as the notebook docker image.
Created a Python2 notebook in the Jupyter notebook environment.
I cloned the code from https://github.com/kubeflow/examples.git
As the section suggested I cut and pasted the code from mnist/model.py into a cell and ran it and had my first exception:

I fixed this temporarily by adding another allowed command line argument:

But then ran into the model type conflict seen by the second exception:

The tutorial code expects only tf_model_type == "LINEAR": but is being passed a type of "CNN".
Unfortunately I am really new to Data Science and don't have much experience with TensorFlow as I come from a Web Application Developer / DevOps Engineer background so I really can't debug any further.

I did also add a print(args) statement, which is what you see first in the second run detail.

Text based output of the run if that is helpful:
`Namespace(f='/home/jovyan/.local/share/jupyter/runtime/kernel-3cf0407c-c1c2-4149-a60e-291f1335e518.json', tf_batch_size=100, tf_data_dir='/tmp/data/', tf_export_dir='mnist/', tf_learning_rate=0.01, tf_model_dir=None, tf_model_type='CNN', tf_train_steps=200)
INFO:tensorflow:TF_CONFIG {}
INFO:tensorflow:cluster=None job_name=None task_index=None
INFO:tensorflow:Will export model
Extracting /tmp/data/train-images-idx3-ubyte.gz
Extracting /tmp/data/train-labels-idx1-ubyte.gz
Extracting /tmp/data/t10k-images-idx3-ubyte.gz
Extracting /tmp/data/t10k-labels-idx1-ubyte.gz
No such model type: CNN
An exception has occurred, use %tb to see the full traceback.
SystemExit: 1`

And contents of %tb:
SystemExitTraceback (most recent call last)
<ipython-input-16-840d9f7d1603> in <module>()
    224
    225 if __name__ == '__main__':
--> 226   tf.app.run()

/opt/conda/envs/py2/lib/python2.7/site-packages/tensorflow/python/platform/app.pyc in run(main, argv)
    123   # Call the main function, passing through any arguments
    124   # to the final program.
--> 125   _sys.exit(main(argv))
    126

<ipython-input-16-840d9f7d1603> in main(_)
    205   else:
    206     print("No such model type: %s" % args.tf_model_type)
--> 207     sys.exit(1)
    208
    209   train_spec = tf.estimator.TrainSpec(

SystemExit: 1

I'm closing this as a duplicate of issue https://github.com/kubeflow/website/issues/844
/close

/assign

Thanks @DanSanche for fixing the problem that cause the model.py code to error out when copied and pasted into a notebook! See PR https://github.com/kubeflow/examples/pull/625


Navlink | Bug | Prevent JS errors in Navlink When Clicking on "Non Scroll-to" Links

Jira
http://vjira2:8080/browse/BDS-1728
Summary
Updates the Navlink JS to fix JS errors getting thrown if a link that gets clicked on isn't a link that would get scrolled to.

Note: This error can be viewed on the live boltdesignsystem.com by opening the browser console on the homepage and clicking on the Github link that opens in a new tab.

Details

Adds missing super calls to the Navlink's older JS
Add missing config to disable Shadow DOM in the Navlink component (just a precaution given that this component isn't currently rendering / re-rendering any HTML)
Update the Navlink JS logic to account for links that don't have an href, aren't a hashed link to scroll to an element on the page, or don't have a matching element to scroll to

How to test

[x] Pull down the changes from this branch, run npm run setup, and start up the local dev environment via npm start
[x] Confirm that the Nav indicator continues to work on this Pattern Lab page as expected: http://localhost:3000/pattern-lab/patterns/04-pages-40-d8-content-hub-00-sticky-navbar/04-pages-40-d8-content-hub-00-sticky-navbar.html#transformation
[x] Edit the docs site header at docs-site/src/templates/_page-header.twig and add a few new fake links to do a smoke test on a few different Navlink use cases:

      {
        text: "No Link",
        url: ""
      },
      {
        text: "Non-existent Element",
        url: "#foo"
      },

[x] Locally, on the main docs site homepage, click on a few different Navlinks in the Navbar to test out the following use cases:

Clicking on a navbar nav link that doesn’t contain an href doesn’t throw a JS error
Clicking on a navbar nav link with a hashed URL but without a matching HTML element with the expected ID doesn’t throw a JS error
Clicking on a navbar nav link with a regular page URL (non-hash URL) doesn’t throw a JS error like it does currently. NOTE: this is easier to replicate when clicking on a URL that opens in a new tab!

[x] Navigate to the sticky navbar demo page and confirm that when clicking on a navbar nav link that DOES have a matching HTML element with the expected ID, the matching element is smooth scrolled into view as expected.

Looks good, tested and works as expected.
For my own benefit, is there a back story/reference with more details about calling super() in the connector/disconnector methods?

@remydenton add that to the list of stuff to chat about during our next Dev huddle!
TLDR: super is super important to call when we're dealing with multiple layers of Classes that open times have have inherited behavior and defaults!


test: fix headerMapEqualIgnoreOrder utility missing a check

Signed-off-by: Saidi Tang<EMAIL_ADDRESS>Commit Message: Added a flag variable to check whether the iterate function returned after a value mismatch for a key
Risk Level: Low, it's part of the test utility
Testing: Does not apply

/retest

The PR should be ready for a first pass review


RDKDEV-649: Run correctly as an out-of-process service

Run the DVB correctly as an out-of-process plugin so the DVB stack isn't running in the WPEFramework process. This protects the wpeframework process if the DVB crashes.
Split the functionality so the DVB libraries are only included in the plugin that runs out-of-process so the size of the WPEFramework process is reduced.

@steveford-obs , can you please create a PR against sprint/23Q1?

Internal ticket for tracking https://ccp.sys.comcast.net/browse/RDKCOM-3545


verifying one config or all

Currently only verifying one config because normally you edit the main configuration file and it will include other configurations with %include.
But if user is editing an included file, and he set the same option that was made on another included file, that will overwrite previous options, setting to the last one. The warn won't be given and it will run of course but vitor would be catching this problem.
But I can't also run blindly just tor --verify-config because if built from source it will read /usr/local/etc/tor/torrc and I don't use that.
Or what I think would be better but would require more work and testings is:

use the same method from tor-ctrl to read from system the tor files https://github.com/nyxnor/tor-ctrl/blob/ea1ddcd507f480113626563b129d47800065481c/usr/bin/tor-ctrl#L125
if file was not read/included on that verification, run file by itself because it could be just a test file on /tmp/torrc.

Anyway, maybe nothing is done in this case because it vitor will explictly say the configuration is valid but warnings were received. Maybe add you can ignore warnings if other tor configuration files will fix this problem.

another problem is that it will never verify this temporary file because it has another name and probably won't match the include pattern of *.conf, which is correct.

solution: add option to suppress warnings if configuration is valid

only verifying one config makes sense and tor user option should be set.


forms: Update create organization part of registration form.

Adds a legend to the "org-registration" fieldset where the user inputs info about the new organization. Previously, there was only a legend for the "user-registration" fieldset. Also, increases the opacity of CSS rule for the legend color so that they are more visible.
Removes the hint text about what the organization URL value is used for since it is pretty clear from the field's name.
Relevant CZO conversation

Screenshots and screen captures:

Current versions of form in dev environment

Updated versions of form in dev environment

--
Self-review checklist

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

Communicate decisions, questions, and potential concerns.

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

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

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

Completed manual review and testing of the following:

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

CI failed due to unrelated puppeteer test.

This looks great, but I wonder if we can do a better heading than "Organization information" at the top that feels a bit more friendly. @alya thoughts?

Hmm, maybe just "Your organization"?

Updated for Your organization being the heading.
Screenshots:

No organization URL checkbox (like Zulip Cloud)

Organization URL checkbox toggled

Organization URL checkbox not toggled

Looks good to me! @timabbott please take a look. :)

Merged, thanks @laurynmm!
One other thing that would be nice to fix from looking at the screenshots is if we can convince lastpass to not try to do something with the organization name and subdomain fields. I'm not sure whether autocomplete="off" is the right fix for that, but it might be worth a try.


Clique createemptyblock set to false, should allow to sync even if there are empty blocks

Found that the createemptyblocks option, introduced in https://github.com/hyperledger/besu/pull/6082, prevents syncing a network that had some empty blocks at the beginning, that scenario could happen if a network was created without this option (or with it set to true) and then changed to false.
The validation should only apply when the node is creating a block, but not when the node is syncing/importing existing blocks.

That is the expected behaviour, the value for createemptyblocks must be the same and was documented with that warning https://besu.hyperledger.org/development/private-networks/how-to/configure/consensus/clique#skip-empty-blocks.
If we don't validate existing blocks then it would be possible for nodes to have a different value for createemptyblocks and we could have a network split. I guess could just validate newly imported blocks though including those that are created and imported that might be ok.
Is it necessary to change from having no empty blocks to having empty blocks? A nicer approach rather than removing the header validation would be add a transition for this.


fix: hub dropdown empty label

fixes https://github.com/ResearchHub/issues/issues/1

@stackedq still getting empty hubs when editing a post

After testing a couple of times, I ended up pushing a fix. Your code was close but a bit off.
Merged your z-index issue PR though.


bring back article titles

Twitter has decided to remove the titles of links to articles and display only an image.
Only the domain name is displayed, but too discreetly.

It's hard to tell the difference between an article and a simple image.
the image doesn't always tell you what the article is about.
there's a risk of scamming.

Already done in v3.20.0: https://github.com/insin/control-panel-for-twitter/releases/tag/v3.20.0

Will that new release be on firefox soon?

Firefox Add-ons has recently been taking up to 4 days to review and approve new versions.

Firefox Add-ons has recently been taking up to 4 days to review and approve new versions.

Gotcha, thanks for all your work making the site usable


[SPARK-8705][WebUI]Don't display rects when totalExecutionTime is 0

Because System.currentTimeMillis() is not accurate for tasks that only need several milliseconds, sometimes totalExecutionTime in makeTimeline will be 0. If totalExecutionTime is 0, there will the following error in the console.

This PR fixes it by using an empty svg tag when totalExecutionTime is 0. This is a screenshot for a task that its totalExecutionTime is 0 after fixing it.

/cc @sarutak

Merged build triggered.

Merged build started.

Test build #36000 has started for   PR 7088 at commit ef2ecfa.

LGTM, but just in case, could you show a screen shot in the case of totalExecutionTime == 0 ?

could you show a screen shot in the case of totalExecutionTime == 0 ?

I have already put a screenshot in the PR description.

Ah, that is after patch applied. O.K, I'll merge once the test finish successfully.

Test build #36000 has finished for   PR 7088 at commit ef2ecfa.

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

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Addressed comments.

Test build #36093 has started for   PR 7088 at commit 9ee4ef5.

Test build #36093 has finished for   PR 7088 at commit 9ee4ef5.

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

Merged build finished. Test PASSed.

I think, we can merge this. @andrewor14 do you think this is ready to merge?

Looks great. I'm merging this into master and 1.4.

@zsxwing looks like this doesn't merge cleanly into branch-1.4. Can you open a new patch against that branch?

@andrewor14 this is because #7082 is not merged into branch-1.4. Do you think if it's worth to merge into branch-1.4?

Oh, then it's OK


Update 2-how-we-style-our-sql.md

Group by column names
What are you changing in this pull request and why?

Checklist

[x] I have reviewed the Content style guide so my content adheres to these guidelines.
[ ] The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the version a whole page and/or version a block of content guidelines.
[ ] I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
[ ] The content in this PR requires a dbt release note, so I added one to the release notes page.

hey @Vhonani-Nelwamondo , thanks for opening this pr up and great initiative!
grouping by is definitely a matter of preference and our best practice stance is to group by number, not column name. we explain our reasons in our article here.
since this change doesn’t align with our best practices, i’ll go ahead and close this PR. however, we really appreciate your effort, and we’d love to see more contributions from you in the future. if you have other ideas or edits in mind, feel free to submit them — we’re always excited to collaborate!
thanks again for your contribution! 🙌


Fix typo in comment

It was found and fixed by codespell.
Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

LGTM


Is this repo still maintain ?

@oblador  Is this repository still alive ?
I can see there is 12 Pull Request waiting for review and the repo hasn't been updated since the 22 Sept 2017.
You have 1 500+ stars also, which means people like this project.
I think it would be a pity to let such a cool project dying.

Unfortunately, it's not really active no. I didn't plan on abandoning it, but I've made the realization that this kind of functionality best resides or is tied to some kind of navigation library. I have actually made some work earlier in this direction, but there was a pressy crazy turnover of what was the "default" navigation library – like three changes within a year so I've been waiting for it to stabilize and mature. Currently my bet is on react-navigation which has some plans on adding shared element transitions, but that work has been stalled for half a year at least, so my expectations are low.
It would however be possible to reduce the scope to what it was originally and just write a custom navigator/transitioner. I have a pretty good idea how I'd approach it and how to make it more performant, but don't have the time to be sole maintainer and at the same time triage issues, write features, documentation etc. Would you be up for helping me out with things like triaging I could revive the repo.

I understand the difficulty of maintaining this kind of library which heavily depends on the navigation library. In my case, I am using both RNN and react-navigation at the same time. When I was trying to customize the lightbox, I did rewrite the lightbox depending on the RNN due to the deep dependency and different props structure.
However, I am happy to hear more about the future thought about this library as lightbox is now kind of a must for every app which contains any image or video. Previously, I was thinking whether this library could implement something like mentioned in this video: https://youtu.be/7emqc7yf-Zg?t=7m1s to improve the performance.

@oblador I do love to help if I can, but I am an ex native iOS developer with only three months experience with React Native and Javascript.
I am not sure what's the deal with Navigator, I am myself using React Navigation in my project, but I think it would be sad if this project was a depending on one or another solution.
I might say something stupid, but wouldn't Modal do the job ? It's compatible with both Android/iOS and you can overwrite the transition by just setting animationType to none.
But as I said above, I really do love to help. If can do anything I will.

Hey @StevenMasini, I've decided to try to take up development again, but start afresh given a lot has changed in the RN world since I started this three years ago (pre android, native animation driver etc).
I'll try to keep compatibility where it's easy and possible, but will not limit myself to old and imperfect APIs. Next up will be to track the work in a PR and list my requirements and maybe have some discussion around it.
Is there a way for us to talk directly, like on twitter/email @StevenMasini (and potentially @peteroid)?

@oblador Great! I am willing to help, let's do it! My Github and Twitter username are the same. Let's talk there.
PS: I didn't find you, using oblador on Twitter.

@oblador my twitter id is _peteroid

@oblador @peteroid I will close this issue then. Let's use the Road to 1.0 (request for comments) for now on.


area/iteration behavior is inconsistent in ui

related to #1686
other Issues:
Iteration is set to None (should be "/" or /):

root iteration is only listed in other choices and there is a None choice - should be consistent i.e. "/" instead of None and don't show root area name in other choices:

in iteration view it says "wonka/tonka" and below is the full path but here it uses "/here/wonka/tonka" (could be "/wonka/tonka" to be consistent):

The left hand panel should only be showing the child as the main name.  So in this case "Tonka" should be shown only, with the full path below it.


Large Text File Compression to .zip Format  (IDFGH-10694)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
We are using the ESP32 WROOM 32D with a 16 MB flash size and want to implement a feature that compresses a large text file from the SD card and sends it to the cloud through HTTPS.
Is there any library for Esp idf to compress a text file to zip format?

I'm not aware of an IDF library specifically for handling zip format, but there is a port of standard zlib library to ESP-IDF which you can use to implement Deflate: https://components.espressif.com/components/espressif/zlib.

Came across a similar requirement: decompressing (aka unzipping) a .zip file located on a connected SD card. The SD card is connected to the ESP32 via SDMMC.

Came across a similar requirement: decompressing (aka unzipping) a .zip file located on a connected SD card. The SD card is connected to the ESP32 via SDMMC.

@hayschan what did you end up using?

Came across a similar requirement: decompressing (aka unzipping) a .zip file located on a connected SD card. The SD card is connected to the ESP32 via SDMMC.

@hayschan what did you end up using?

Came across a similar requirement: decompressing (aka unzipping) a .zip file located on a connected SD card. The SD card is connected to the ESP32 via SDMMC.

@hayschan what did you end up using?

I took another technical route by not using zip compression.


Fix Metal backend on OSX

Metal backend has been found to fail with the following stacktrace:
-[MTLVertexDescriptorInternal newSerializedDescriptor]:832: failed assertion `None of the attributes set bufferIndex to 2, but MTLVertexDescriptor set buffer layout[2].stride(4).'
Process 87068 stopped

    thread #8, stop reason = signal SIGABRT
    frame #0: 0x00007fff5cf7be3e libsystem_kernel.dylib__pthread_kill + 10 libsystem_kernel.dylib__pthread_kill:
    -> 0x7fff5cf7be3e <+10>: jae 0x7fff5cf7be48 ; <+20>
    0x7fff5cf7be40 <+12>: movq %rax, %rdi
    0x7fff5cf7be43 <+15>: jmp 0x7fff5cf730b8 ; cerror_nocancel
    0x7fff5cf7be48 <+20>: retq
    Target 0: (00_cube_d) stopped.
    (lldb) bt
    thread #8, stop reason = signal SIGABRT
        frame #0: 0x00007fff5cf7be3e libsystem_kernel.dylib__pthread_kill + 10 frame #1: 0x00007fff5d0ba150 libsystem_pthread.dylibpthread_kill + 333
        frame #2: 0x00007fff5ced8312 libsystem_c.dylibabort + 127 frame #3: 0x00007fff5cea0368 libsystem_c.dylib__assert_rtn + 320
        frame #4: 0x00007fff39ad3f8d MetalMTLReportFailure + 778 frame #5: 0x00007fff39adc805 Metal-[MTLVertexDescriptorInternal newSerializedDescriptor] + 454
        frame #6: 0x00007fff39ad362f Metal-[MTLRenderPipelineDescriptorInternal newSerializedVertexDataWithFlags:error:] + 490 frame #7: 0x00007fff39ac1382 Metal-[MTLCompiler newRenderPipelineStateWithDescriptor:options:reflection:error:completionHandler:] + 153
        frame #8: 0x00007fff39aa43a4 Metal-[_MTLDevice newRenderPipelineStateWithDescriptor:options:reflection:error:] + 76 frame #9: 0x00000001018c619c 00_cube_dbgfx::mtl::Device::newRenderPipelineStateWithDescriptor(this=0x0000000106f16008, _descriptor=0x00000001034759e0, _options=2, _reflection=0x000070000b8aa0c8) at renderer_mtl.h:315
        frame #10: 0x00000001018be593 00_cube_dbgfx::mtl::RendererContextMtl::getPipelineState(this=0x0000000106f16000, _state=106319887, _rgba=0, _fbh=(idx = 65535), _numStreams='\x03', _vertexDecls=0x000070000b8aac50, _programIdx=11, _numInstanceData='\0') at renderer_mtl.mm:2010 frame #11: 0x00000001018b90cc 00_cube_dbgfx::mtl::RendererContextMtl::submit(this=0x0000000106f16000, _render=0x000000010c800440, _clearQuad=0x000000010f343e90, _textVideoMemBlitter=0x000000010f343e20) at renderer_mtl.mm:3849
        frame #12: 0x0000000101858d80 00_cube_dbgfx::Context::renderFrame(this=0x000000010c800040, _msecs=5000) at bgfx.cpp:1911 frame #13: 0x0000000101858c46 00_cube_dbgfx::renderFrame(_msecs=-1) at bgfx.cpp:1096
        frame #14: 0x0000000101859ee3 00_cube_dbgfx::Context::renderThread((null)=0x000000010c800240, (null)=0x000000010c800040) at bgfx_p.h:2714 frame #15: 0x00000001018fd783 00_cube_dbx::Thread::entry(this=0x000000010c800240) at thread.cpp:294
        frame #16: 0x00000001018fd72d 00_cube_dbx::ThreadInternal::threadFunc(_arg=0x000000010c800240) at thread.cpp:89 frame #17: 0x00007fff5d0b76c1 libsystem_pthread.dylib_pthread_body + 340
        frame #18: 0x00007fff5d0b756d libsystem_pthread.dylib_pthread_start + 377 frame #19: 0x00007fff5d0b6c5d libsystem_pthread.dylibthread_start + 13

For now this can be worked around by forcing the renderer to OpenGL, but in the future we want to support the Metal backend.

I accidentally ended up here after github suggested to take a look at mud :)
I solved a similar issue with Metal a couple of weeks ago. In my case the problem seemed to be that I was setting a vertex stream which wasn't used by the shader. More specifically, I was using 3 vertex streams (pos, color and uv) and all of them were used by the most common shader. But once I used a shader which didn't use the uv stream, I got that error from Metal. Solved by moving the uv stream binding inside the specific case.
See: https://github.com/jdryg/vg-renderer/commit/23e2221c7e72058547557f17ed138beb4423c5ed
Hope it helps :)

Well sounds like it might actually come from vg-renderer then :) Sadly I don't have an OSX device myself to check. Thanks for the heads up!


E2E test improvements

E2E tests should log the sha1 of the deployment under test.
E2E test should mirror prod to staging before running.

Hey team! Please add your planning poker estimate with Zenhub @tihuan @ebezzi

@tihuan do you think this falls into the the datavis realm of work?

Adding a data-viz label as per @Bento007 's comment, but please update if this is incorrect! 🙏

data-viz sounds good!

@Bento007 @atolopko-czi how do we find the SHA for BE now? Thanks!

@Bento007 @atolopko-czi I think this ticket should be E2E tests should log the sha1 of the deployment under test . Not sure why it was changed back in August if anyone remembers 😄 ?
Thank you!

Oh, what have I done!? 😄 We still need to do what the current title says, so let's keep this as is and create a new issue for "E2E tests should log the sha1 of the deployment under test". I'll do that, and make it a P1.

Ahh got it! Okay thank you!
In that case, should we find a BE eng to take on this ticket? Thank you!

This could also be used for s3 mirroring: https://docs.aws.amazon.com/AmazonS3/latest/userguide/batch-ops.html


Disable "allow pasting" warning in Chrome's dev tools (OSOE-873)

This noob-proofing security feature is incredibly annoying during test troubleshooting. We should see if it can be disabled, since it's not helpful to wed developers in the middle of a UI test.

Jira issue

It doesn't seem to be possible to disable this in any other way than indeed opening the console and typing allow pasting. How exactly is this causing an issue for you?

When I want to check a path from the code I'd start typing $() or $x() into the dev console, then try to paste like I'd do in my regular browser. The warning appears so I have to clear the input, type in "allow pasting" and then try again. And the setting is not remembered across UI tests. It's not a blocker, but it's very irritating and destroys the working experience.
It hard to believe that there is no automation flag to disable this in Chrome for Testing. I will research the question and open a Chrome issue if indeed it's not been raised (or more likely, link any already existing issue to keep an eye on).

OK, thank you.

Looks like there is already something: https://issues.chromium.org/issues/41491762
I will try to implement it.

Cool!


DateTimeOffset type is not supported

When attempting to generate a merge-statement on a table containing a column of the datetimeoffset datatype, the datetimeoffset-type is not recognized, resulting in datetimeoffset-values not being wrapped in single-quotes and generating a faulty script.
Steps to reproduce
CREATE TABLE tbl_datetimeoffset (id int IDENTITY PRIMARY KEY, dto datetimeoffset);
INSERT INTO tbl_datetimeoffset (dto) VALUES (SYSDATETIMEOFFSET());
EXEC sp_generate_merge 'tbl_datetimeoffset';

Result script
--MERGE generated by 'sp_generate_merge' stored procedure, Version 0.93
--Originally by Vyas (http://vyaskn.tripod.com): sp_generate_inserts (build 22)
--Adapted for SQL Server 2008/2012 by Daniel Nolan (http://danere.com)

SET NOCOUNT ON

SET IDENTITY_INSERT [tbl_datetimeoffset] ON

MERGE INTO [tbl_datetimeoffset] AS Target
USING (VALUES
  (1,2018-10-23 13:14:53.7638046 +0)
) AS Source ([id],[dto])
ON (Target.[id] = Source.[id])
WHEN MATCHED AND (
	NULLIF(Source.[dto], Target.[dto]) IS NOT NULL OR NULLIF(Target.[dto], Source.[dto]) IS NOT NULL) THEN
 UPDATE SET
  [dto] = Source.[dto]
WHEN NOT MATCHED BY TARGET THEN
 INSERT([id],[dto])
 VALUES(Source.[id],Source.[dto])
WHEN NOT MATCHED BY SOURCE THEN
 DELETE
;
GO
DECLARE @mergeError int
 , @mergeCount int
SELECT @mergeError = @@ERROR, @mergeCount = @@ROWCOUNT
IF @mergeError != 0
 BEGIN
 PRINT 'ERROR OCCURRED IN MERGE FOR [tbl_datetimeoffset]. Rows affected: ' + CAST(@mergeCount AS VARCHAR(100)); -- SQL should always return zero rows affected
 END
ELSE
 BEGIN
 PRINT '[tbl_datetimeoffset] rows affected by MERGE: ' + CAST(@mergeCount AS VARCHAR(100));
 END
GO

SET IDENTITY_INSERT [tbl_datetimeoffset] OFF
GO
SET NOCOUNT OFF
GO

Should probably be handled here:
https://github.com/readyroll/generate-sql-merge/blob/81dacbe11a5f63086052bb2493ba80d23b67975a/master.dbo.sp_generate_merge.sql#L352

Thank you for providing all those details, made it very easy for me to reproduce the issue. I've run the steps against #35 (now merged) and it appears to now be resolved. If you continue to encounter the problem, please let me know.


Fixed typo on L42

Minor typo raised in issued #29065

@ssennettau : Thanks for your contribution! The author, @mgoedtel, has been notified to review your proposed change.


Updated RSS publication with PDF url

Check my comment on the file. Please fix.

bump

I will fix it and create a PR tomorrow
On Sun, Nov 28, 2021 at 6:03 PM John Jackson @.***>
wrote:

bump
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aria-systems-group/website/pull/7#issuecomment-981203842,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHAY4BCIUVSHYZJBSYTSJCLUOLGMJANCNFSM5IP63J7Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

bump 😊

Thanks for the reminder. Check the new URL. Let me know if you see any problem.

See fix, still need the comma

Thanks. Added comma and created a new commit. FYI, I can not see your original comment on my pdf for some reason.


Intermittent Exception(s) occur launching ReactGrid, ReactReduxSpa

On Windows 7 SP1, I'm experiencing intermittent exception(s) launching ReactGrid, ReactReduxSpa. Exception details can be found below. I have not been able to repro on my Win10 machine using Chrome, IE, or Edge.
First, I suspected it was a MAXPATH issue because my content dir was several levels deep, but I cloned the repo into a short path C:\Git\JavaScriptServices\ and am still experiencing this behavior. I've also noticed that ReactGrid and ReactReduxSpa (AFAIK) are the 2 React projects that employ SSR. I haven't been able to repro this on Windows 7 SP1 with the simple (CSR-only) ReactSpa using Chrome 50 or IE 11.
Internal Server Error.html.txt
Raw Details:
System.Net.Http.WinHttpException: A connection with the server could not be established
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at System.Net.Http.WinHttpHandler.<StartRequest>d__102.MoveNext()

More info:
When I wrote the issue above, both ReactGrid and ReactReduxSpa were giving the same exceptions (IIS Express was listening on 49552). I just now changed the Startup Project in VS 2015 to ReactGrid, attempted to run it (unsuccessfully) without stopping ReactReduxSpa (49552), then switched the Startup Project back to ReactReduxSpa and it's launching without error... for now.

I'm not sure if this has anything to do with anything but I'm just throwing it out there.

Update 2:
I just used the yeoman generator instead of running the template(s) directly and I'm no longer getting the dev exception page with the stack trace. However, I am still seeing the exception crop up in bursts of 4 or 5 every time I refresh the browser in the Debug output in VS:
Exception thrown: 'System.Net.Http.WinHttpException' in System.Net.Http.dll
Exception thrown: 'System.Net.Http.WinHttpException' in System.Net.Http.dll
Exception thrown: 'System.Net.Http.WinHttpException' in System.Net.Http.dll
Exception thrown: 'System.Net.Http.WinHttpException' in System.Net.Http.dll

Update 3
After a cold boot of Windows 7 SP1, the page of death included in my original post came back in Chrome 51. I tried waiting and refreshing the browser several times to no avail. A few minutes later I launched IE 11 and the site rendered properly there. Immediately after that, the site was also rendering fine in Chrome. No other user interactions were taken.

I changed my exception settings to break on all .NET Exceptions, which reveals:
System.Net.Http.WinHttpException occurred
Message: Exception thrown: 'System.Net.Http.WinHttpException' in System.Net.Http.dll
Additional information: The option is invalid
at this location:

..I see someone else is having a similar issue:
http://stackoverflow.com/questions/37469122/asp-net-5-tag-returning-500-internal-server-error/37499200#37499200?newreg=d4bc81f2c9f74f9db13b51a7f7819236
As the SO poster suggests, if I comment out the prerender tag helpers in Index.cshtml, the problem goes away. Any thoughts?
Thanks!

I'm not certain what specific problem occurs with WinHttpHandler on Windows 7. Using such an old OS is quite an unusual case, and a low-level bug in an OS service might be beyond what this repo can do anything about.
Rather than get too deep into that, can you try the following possible workaround? Instead of using the HTTP-based .NET/Node interop, you can switch over to a new hosting model which is soon going to become the new default, because it's faster than the HTTP interop mechanism.

Make sure you have the latest version of the Microsoft.AspNetCore.NodeServices package - version 1.0.0-beta-000003

Add the following to the ConfigureServices method in your Startup.cs file:
services.AddNodeServices(new NodeServicesOptions { HostingModel = NodeHostingModel.Socket });

(you'll probably also need to add using Microsoft.AspNetCore.NodeServices; at the top of the file)

This at least avoids the HTTP aspect of things. Does this work?

Hi Steve, unfortunately that didn't seem to work. I'm still getting the WinHttpException for one. I'll provide more details shortly.

I verified v.1.0.0-beta-000003
I added the code you provided above to Startup.cs.

The symptoms remain intermittent. At times, I get 502.3 Bad Gateway (details below) when launching the app for the first time. (This never happened before I modified the code per your instructions.)
Sometimes, a browser refresh will allow the page to display properly, but I still see 4 "WinHttpException"s in the VS output window.

HTTP Error 502.3 - Bad Gateway
The specified CGI application encountered an error and the server terminated the process.
Most likely causes:
The CGI application did not return a valid set of HTTP errors.
A server acting as a proxy or gateway was unable to process the request due to an error in a parent gateway.
Things you can try:
Use DebugDiag to troubleshoot the CGI application.
Determine if a proxy or gateway is responsible for this error.
Detailed Error Information:
Module	   AspNetCoreModule
Notification	   ExecuteRequestHandler
Handler	   aspNetCore
Error Code	   0x80072ee2
Requested URL	   http://localhost:60389/
Physical Path	   C:\Git\rryo
Logon Method	   Anonymous
Logon User	   Anonymous
Request Tracing Directory	   C:\Users________\Documents\IISExpress\TraceLogFiles\RRYO
More Information:
This error occurs when a CGI application does not return a valid set of HTTP headers, or when a proxy or gateway was unable to send the request to a parent gateway. You may need to get a network trace or contact the proxy server administrator, if it is not a CGI problem.
View more information »

Thanks for the updated information. Sorry this is being troublesome for you. Is it still definitely only happening on your Windows 7 machine and not on Windows 10?
It's not likely that I'm going to have capacity to investigate this if it's Windows 7-specific. The error looks pretty low-level and most likely is independent of anything that NodeServices controls directly. If you are able to diagnose this fault I'd be very interested to know the details. Otherwise, at least in the short term, we might have to amend the requirements list for NodeServices to specify Windows 8 or above. I know that won't be ideal from your perspective, and if this gets reported by more people then the plan might change. Does that make sense?

Is it still definitely only happening on your Windows 7 machine and not on Windows 10?

I'll try on Windows 10 today and post back.

Does that make sense?

Yup. In the meantime, I'll try to dust off my WinDbg+SOS when I have some time and see if I can get to the root of it. I'd love to be able to get SSR; it's a great selling point and a shame to have to disable it.

The following exception occurs on both Windows 7 SP1 and Windows 10:
Object reference not set to an instance of an object.
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at Microsoft.AspNetCore.NodeServices.HostingModels.VirtualConnections.VirtualConnectionClient.OpenVirtualConnection()
   at Microsoft.AspNetCore.NodeServices.SocketNodeInstance.<Invoke>d__7`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.AspNetCore.SpaServices.Prerendering.PrerenderTagHelper.<ProcessAsync>d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Razor.Runtime.TagHelpers.TagHelperRunner.<RunAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Asp._Views_Home_Index_cshtml.<ExecuteAsync>d__23.MoveNext()

If you can provide any information on how to repro that (even if the repro is intermittent like you mention) that would be great. It's difficult to begin any investigation without that info.
Based on the stack trace you posted, I identified one line of code in VirtualConnectionClient's OpenVirtualConnection method that's not thread-safe like it should be. This might be the cause of the error, but I can't be sure.
I've fixed this (https://github.com/aspnet/JavaScriptServices/commit/3fc19ea77bdbf09d764c2116eab20a32fe1f34eb) and pushed an updated build of all the packages. The new package version for all of them, which includes this fix, is 1.0.0-beta-000004 (e.g., https://www.nuget.org/packages/Microsoft.AspNetCore.NodeServices/1.0.0-beta-000004). Can you please update to beta-000004 and check if the problem still occurs?
If it does, I'll need more detailed steps that reproducing the issue (even if intermittently). Thanks!

Thanks, Steve. It's been a while since I pulled down the latest. I will try this today and post back.

Ok. I installed the latest yeoman generator and generated a fresh React-Redux app. No signs of WinHttpException so far (fingers crossed)!
The following may no longer be relevant, but if I add:
services.AddNodeServices(new NodeServicesOptions { HostingModel = NodeHostingModel.Socket });
then I still either get "HTTP Error 502.3 - Bad Gateway" or:

An unhandled exception occurred while processing the request.
IOException: Pipe is broken.
System.IO.Pipes.PipeStream.WriteAsyncCore(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken)
AggregateException: One or more errors occurred. (Pipe is broken.)
System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
AggregateException: The connection failed - see InnerException for details. (One or more errors occurred. (Pipe is broken.))
Microsoft.AspNetCore.NodeServices.HostingModels.VirtualConnections.VirtualConnectionClient.ThrowIfReadLoopFailed()
AggregateException: One or more errors occurred. (The connection failed - see InnerException for details. (One or more errors occurred. (Pipe is broken.)))
System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)

Speaking of, is Socket the new DefaultNodeHostingModel? It looks like it may still be Http, which contradicts the docs:
Code:
https://github.com/aspnet/JavaScriptServices/blob/f2e89fd3bcfee38de3950d908888f8d4e53747cb/src/Microsoft.AspNetCore.NodeServices/Configuration.cs#L9
Docs:
https://github.com/aspnet/JavaScriptServices/blob/44c8b9985b63eb1a33dd3048c0b3b67732b12d08/src/Microsoft.AspNetCore.NodeServices/README.md#built-in-hosting-models

(cont.) My latest error looks like a duplicate of #110. I'm using beta 00004.

Speaking of, is Socket the new DefaultNodeHostingModel? It looks like it may still be Http, which contradicts the docs:

You're right that these are currently inconsistent, but that won't be fore long. Socket will be the new default hosting model, but isn't in the current packages. I wrote in the docs that it is because it will be very soon.

My latest error looks like a duplicate of #110. I'm using beta 00004.

OK then, closing this as a duplicate of #110.


'dbtPowerUser.showCompiledSQL' not found

This extension used to work well, but a couple of months ago, it started giving me command xxx not found error whenever I try to use the extension from Ctrl+Shift+P menu.
I checked this following issue that mentions the same error message but it doesn't seem to apply to me as I'm not using devcontainer or anything like that.
https://github.com/innoverio/vscode-dbt-power-user/issues/78
I noticed the "Runtime Status" tab says "Not yet activated" when I open the extension detail in VS code.
Is there I can try to troubleshoot the issue?

DBT_PROFILES_DIR = r:\1.dbt
Dbt version 1.0.1
Plugin: -sqlserver 1.0.0
Manifest location
/dbt_projects/target/manifest.json
VS Code version 1.63.2
dbt Power User v0.5.9

the issue is that the extension can't be activated, could you check the console log through Help >> Toggle Developer tools and post the log. It might be that the extension can't read your dbt_project.yml file (invalid yaml).

Absolutely nothing shows up in the developer console before and/or after the error message. Is there anything else I can try?

Where does the extension look for the dbt_project.yml?

Everywhere in the opened folders within the vscode workspace.
**/dbt_project.yml


Fix for missing additional features fields when creating new popup windows

The non-standard features (like this-is-not-a-standard-feature) given to window.open() are lost in the popup window creation workflow. This leads to the 'new-window' event handler not receiving these 'additional' features. These features may be used by applications to give some specific data to the popup.
NOTE : This is a prerequisite of pull request #7291 in electron repo.

Requested changes done.

@zcbenz PR updated with requested changes

:+1:


[NTT] Explore faster NTT implementations.

A more thorough background is provided by @sampsyo in #277.

The next step along those lines would be to try implementing one of the better (non-naive) NTT implementations, such as Cooley–Tukey, using Dahlia. That opens a few interesting possibilities:

I expect this will run into serious parallelizability problems, so we will need to think through what can be done to work around those limitations—likely by generating FuTIL code directly.
These realistic algorithms, including Cooley–Tukey, have lots of parameters. So just getting to a place where we can DSE those parameters would be good. The parameters we DSE may be surprisingly subtle, which may make for an interesting FuTIL generator.
We'll want to compare our performance with Shunning's PyMTL implementation. How much worse are we? This will be the first time we'd have an "expert-crafted" RTL baseline to compare FuTIL-generated against, which would be pretty exciting.

https://github.com/cornell-brg/pymtl3-fft/blob/sj634-poly-dft-xcel/nttlib/arith/ntt_play.py
This link doesn't work for me. Am I missing something?

Nope—just missing access to @jsn1993's repository. :smiley: If you're interested, we can ask him to give you access! (@yoonachang and I currently do.)

Great. And yes, TBH most of the math is unintelligible to me and I'm reproducing the algorithms "phonetically."
For the radix-2 algorithm's dynamic loop bounds: probably the right thing to do in Dahlia is use a while loop. The reason for loops need static loop bounds is that we want to reason about parallelism in these loops, and more relevantly here to guarantee that a loop has "simple" control hardware, even when unrolled. That's impossible, of course, if we can't prove that the unrolling factor divides the loop bound (i.e., if the bound is dynamic).
So by way of answer also to your question about finding a high-performance algorithm to implement: I think the hard part (after getting a basic/non-parallelized Cooley–Tukey working) is to look into what a good hardware implementation of Cooley–Tukey usually entails. There are these things called "butterfly units," for example. I don't know if they will be easy/possible to express in Dahlia. Hence the possible need for either extensions to Dahlia or bypassing Dahlia altogether in favor of generating Calyx directly.

Ok that makes more sense. I wasn't aware of the butterfly units. I did some wikipedia reading just now.
For a prime number P and array of twiddle factors omegas, we have:
y0 = (x0 + x1 * omegas[g]) % P
y1 = (x0 - x1 * omegas[g]) % P

Which, at the FuTIL level might look something like:
x0 = prim std_reg(32);
x1 = prim std_reg(32);
y0 = prim std_reg(32);
y1 = prim std_reg(32);
add = prim std_add(32);
sub = prim std_subtract(32);
...
add.left = x0.in;
add.right = x1.in; // Still need to multiply by omegas[g].
y0.in = add.out;   // Still need to apply modulus P.

sub.left = x0.in;
sub.right = x1.in;  // Still need to multiply by omegas[g].
y1.in = sub.out;    // Still need to apply modulus P.

Perhaps we should blackbox a butterfly unit so it takes in as input wires to x0, x1, y0, y1, some P, and the necessary twiddle factor omegas[g]? Just kind of throwing out some initial thoughts here, but perhaps you've already got something in mind.
This also has some useful diagrams: DFT and FFT Overview

Got it, that's cool! No, I have nothing currently in mind. But I do think it would be fun to first try writing the (slow, serial) Dahlia for the Cooley–Tukey algorithm, and then we can use an empirical approach to iteratively making it better with such optimizations.

Cooley-Tukey implemented in Dahlia in #308.

So the next step is to write benchmarks for NTT. I've never written benchmarks for FuTIL, so perhaps someone can point me in the right direction.

Not quite sure what you mean by “benchmark for NTT”. What do you want to measure.
If you want to measure  the number of cycles used in the two implementations, you can use a jq query on the output of “fud e —to vcd_json”.
See the “.jq” file for th systolic array correctness test.

Good question. @sampsyo mentioned comparing performance with Shunning's PyMTL implementation, so I think he has something specific in mind.

Good point! Cycle count is a good place to start, but the other important metrics are area and maximum frequency (both of which require going through a real synthesis tool, i.e., either Vivado or some ASIC toolchain). But a first "baby step" would be just comparing the cycle counts for the naive and sequential Cooley-Tukey implementations.
As far as comparing with Shunning's implementation, I think the next step would be to email Shunning! We can see if he has his PyMTL implementation available somewhere, and then maybe we can put both his code and your code through the same synthesis toolchains (perhaps Vivado, for starters, since fud already supports it built in).
A semi-parallel thread to explore would be attempting to parallelize the CT implementation, somehow, to reduce its cycle count.

The cycle count of my implementation is quite easy to calculate. For N -
size FFT, it takes log2(N) runs and k + N/P cycles for each run to compute
the results assuming the SRAMs are already loaded with data. K is the
number of pipeline stages in the butterfly unit. P is the number of PEs.
On Wed, Dec 30, 2020 at 3:25 PM Adrian Sampson<EMAIL_ADDRESS>wrote:

Good point! Cycle count is a good place to start, but the other important
metrics are area and maximum frequency (both of which require going through
a real synthesis tool, i.e., either Vivado or some ASIC toolchain). But a
first "baby step" would be just comparing the cycle counts for the naive
and sequential Cooley-Tukey implementations.
As far as comparing with Shunning's implementation, I think the next step
would be to email Shunning! We can see if he has his PyMTL implementation
available somewhere, and then maybe we can put both his code and your code
through the same synthesis toolchains (perhaps Vivado, for starters, since
fud already supports it built in).
A semi-parallel thread to explore would be attempting to parallelize the
CT implementation, somehow, to reduce its cycle count.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cucapra/futil/issues/302#issuecomment-752747566, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPYGAMAVZQKTDNZJQRXP7LSXOEENANCNFSM4USZJIAA
.

--
Shunning Jiang
Ph.D. Candidate
Computer Systems Laboratory
School of Electrical and Computer Engineering
Cornell University
http://www.csl.cornell.edu/~shunning

Awesome; thanks @jsn1993!

@cgyurgyik has this been resolved? I remember that we've gotten some benchmarking for NTT stuff already working with the new frontend.

I believe so. The pipeline set up that we are currently using is as fast as we can get in terms of parallelism.


exit on producer|subscriber err

Apply code changes from v32 to main

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.009%) to 28.66%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/datasync/directory.go
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/datasync/directory.go
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>7:
-0.009%

Covered Lines:
920

Relevant Lines:
3210

💛  - Coveralls


[Feature]: Add an About Us Page

@rishicds Atleast assign me this issue to add an about Us.

Assigned.