Refactoring

support Bower versioning
support Node versioning

Cnown bugs:
Transliteration.slugify - do not work properly
src/transliteration.js - source main file
build/transliteration.js - minified for Node.js
build/transliteration.min.js - minified and browserified for <script>

Thanks very much for your contribution! I'll merge it for now and possibly refactor it a bit more before updating npm version

Please, don`t forget add Git tag for release as I did in my fork!

For your info, I have managed to refactor the code in 1.0 version. I believe that it's more stable and convenient than previous versions. I also try to follow best practices. Please take a look :), If you find any issues please let me know. Thanks!


How can I write a streaming compression(deflate, gzip) Middleware

What Response.body looks like
/// The response representation given to `Middleware`
pub struct Response {
    // ... other fields
    /// The body of the response.
    pub body: Option<Box<WriteBody>>
}

What WriteBody looks like
/// A trait which writes the body of an HTTP response.
pub trait WriteBody: Send {
    /// Writes the body to the provided `Write`.
    fn write_body(&mut self, res: &mut Write) -> io::Result<()>;
}

As you can see, WriteBody has only one method write_body to write itself to a given Write (which is hyper::server::Response). Once write_body is called, it write its entire data to the Write, which is not flexible.
So, in a AfterMiddleware how can I consume Request.body and Encode it with deflate/gzip then set it back to the same Response, streaming like? Means that we do not need to read all data from origin body then compress it.
I can not see how to do this.
I think if Request.body is a io::Read would be great!

Wow, thanks! Seems a great solution. I'll test it soon!

Solved, thanks again!


Fix incorect price send to avatax

I want to merge this change because it sends to Avatax price with discounts instead of undiscounted_price

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-6683 Incorect amount send to Avatax


sctp: allow partial reads

This PR modifies read behaviour to permit partial reads and no longer return ErrShortBuffer if the buffer is too small to fit a whole message. The buffer will be filled up to its size and the rest of the msg will be returned upon the next call to read.
Closes #273

✅ tested with webrtc libp2p transport (all tests are passing)

@melekes did you review the callsites where data channels use SCTP?

@melekes did you review the callsites where data channels use SCTP?

Yes

Maybe I am missing something, but this seems like a silently breaking change?
read_data_channel() calls read_sctp() and this change seems to imply that we may now get a partial read.  There's no indication that each each read_sctp() call is a partial or full message.
From what I can tell, WebRTC data channels are meant to be message based, not stream based, and so it seems like this like a single logical message will now trigger multiple DataChannelMessage events to propagate with the data split between them.
Am I missing something?

Maybe I am missing something, but this seems like a silently breaking change?

It is a breaking change (if the given buffer is not long enough to fit the message).
However, the size of the buffer is capped at u16::MAX and it's max for Chrome.
/// message size limit for Chromium
const DATA_CHANNEL_BUFFER_SIZE: u16 = u16::MAX;

So if you're using the default (i.e. read_loop), then you should be fine.
If you're calling data_channel.read with a smaller buffer, then the behavior is indeed different now.

and so it seems like this like a single logical message will now trigger multiple DataChannelMessage events to propagate with the data split between them.

It won't (because of u16::max).

From what I can tell, WebRTC data channels are meant to be message based, not stream based,

Does this mean we can't make this change?

After giving it a little bit of thought (and reading https://lgrahl.de/articles/demystifying-webrtc-dc-size-limit.html), I think from the Rust perspective it would still be correct to fill the buffer in case of read (because other Reader's do it and that's what every developer expects) BUT we should also indicate that message is not fully read somehow (maybe adding Result<usize, bool> boolean flag to indicate that). What do you think @k0nserv @KallDrexx ?

It feels a bit dubious to mess with the message based nature of Data Channels. As it would be a departure from the specification. Is there a different way to work around the problem you have @melekes?
If you control both sides‚ message size can be known and buffers always appropriately sized

message size can be known

not always!

As it would be a departure from the specification.

can you point me to the exact place?

Is there a different way to work around the problem you have @melekes?

yes. create a very big buffer, which is not ideal to say the least.

I see two problems here:

if you don't know the size of the biggest message, you will try to read it and fail (ErrShortBuffer). The message will be lost. Unless resubmitted by the remote.
if you have two messages (1MB and 200MB in size), you are forced to always create a buffer of size 200MB, right?

With this PR, you'll never face both problems.

With this PR, you'll never face both problems.

I could be mistaken, but while this PR as written fixes those two problems it creates new problems.
Specifically, we send protobuf messages across data channels from the browser.  We had an issue where the message we were trying to send ended up being significantly large in some circumstances which caused the ErrShortBuffer error to propogate, which ended up in our code tearing down the connection and raising an error. This was good for us because we decided that the large data messages was a design flaw in our protocol and worked around it so we didn't need such large data messages (yes I understand this is not always feasible without manual splitting).
If your PR was in at the time, unless I'm missing something this would have been significantly harder to figure out what was going wrong, because partial reads would have triggered multiple data channel messages, which mean all code that expects a single data channel message to be a single deserializable self contained message would have been false.  We would have gotten no errors or warnings and just random circumstances of deserialization failures.
Maybe I'm wrong and I'm just missing the code which would assemble partial reads into a single DataChannelMessage buffer though.
For what it's worth, the data channels spec itself in section 6.6 recommends a message size limit of 16K.  Specifically:

As long as message interleaving is not supported, the sender SHOULD limit the maximum message size to 16 KB to avoid monopolization.

if you have two messages (1MB and 200MB in size), you are forced to always create a buffer of size 200MB, right?

Maybe this is better solved by utilizing the bytes crate better.  Specifically,

Make the buffer a BytesMut
set the size to whatever size we want to do each individual read at
Read into the BytesMut.  If we read to the full capacity and there's more, extend the buffer and do another read
If we've red less than the full capacity of the individual read buffer, consider the message complete, split and freeze the buffer and return that as the message, and retain the BytesMut for the next read attempt.

Read into the BytesMut. If we read to the full capacity and there's more, extend the buffer and do another read

huh? in the current implementation you'll just get ErrShortBuffer if you "read to the full capacity and there's more".


Issues with current application system

[ ] Finalise: users do not get deleted
[ ] Reapplying collegists' educational data gets modified (https://github.com/EotvosCollegium/mars/issues/312)
[ ] Correct the anternet access date for admitted collegists
[ ] #327
[ ] come up some solution for this: https://github.com/EotvosCollegium/mars/issues/325
[ ] #321

Could you explain the internet access date problem a bit more? Maybe even in a separate issue, if you have the time.
Also, for the first point: this means that after clicking the finalise button, they stay in the database, right?

We might need to store data of accepted applications for more than 80 years. We should probably be able to archive this data easily. (NFTV 3. melléklet I/B. 3. "Az adatkezelés időtartama: a hallgatói jogviszony megszűnésére vonatkozó bejelentéstől számított nyolcvan évig.")
@kosblskvcs

@horcsinbalint @viktorcsimma If we can merge #560 #572 and #574 we should be ready for final tests and opening the admission period. Make sure that you delete the applications from the last year beforehand (that was a bug).
I will implement #327 and the finalise method again in the meantime, those are less of a priority.

I did not see any data now from last year, but yes.

There are some records in the DB.

I have lost the track of these PR's, and will not be able to test them as I am busy with unrelated stuff - mostly TermTudTábor - (I am not planning on commenting on this repo for the next 10 days), but I am a bit concerned whether there is enough time to test all these as the application will be opened on Wednesday and the Student Council is also quite busy.


[HOLD for payment 2023-08-10] Match Report Header and LHN Avatars

Part of https://github.com/Expensify/App/issues/20486. We want to match the header avatars to the LHN avatar patterns.
Used for both https://github.com/Expensify/App/issues/22333 and https://github.com/Expensify/App/issues/22332 so I am separating out into its own issue.
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0197cbf143b0f44102
Upwork Job ID:<PHONE_NUMBER>206991872
Last Price Increase: 2023-07-08

Payment summary:
$1000 to @parasharrajat via NewDot
Please go ahead and request the payment @parasharrajat 👍

Based on this SO we can close this out in the meantime seeing as no BZ steps are needed here 🚀

Reviewed the details for @parasharrajat. This $1,000 payment is approved via NewDot based on the BZ summary above.


Fix potential dead lock in reaper

origin issue is #2709, detail dead lock information is in #2743.
This is long time issue, I wonder if the patch this can fix instead
of workaround it
Signed-off-by: Ace-Tang<EMAIL_ADDRESS>I wrote a unit test for v2 reaper (also can be use for v1 reaper)
package shim

import (
	"fmt"
	"os"
	"os/exec"
	"os/signal"
	"testing"

	"golang.org/x/sys/unix"
)

func doSignals() error {
	signals := make(chan os.Signal, 32)
	signal.Notify(signals, unix.SIGTERM, unix.SIGINT, unix.SIGCHLD, unix.SIGPIPE)

	for {
		select {
		case s := <-signals:
			switch s {
			case unix.SIGCHLD:
				if err := Reap(); err != nil {
					fmt.Printf("reap get error %s\n", err)
				}
			default:
			}
		}
	}
}

func TestReap(t *testing.T) {
	end := make(chan bool, 10)
	go doSignals()
	num := 10
	for j := 0; j < num; j++ {
		go func() {
			for i := 0; i < 5; i++ {
				if err := makeCmd(); err != nil {
					fmt.Printf("makeCmd errr %s\n", err)
				}
			}
			end <- true
		}()
	}

	fin := 1
	for {
		select {
		case <-end:
			fin++
			fmt.Printf("finish %d test\n", fin-1)
		}

		if fin > num {
			fmt.Printf("test end\n")
			break
		}
	}
}

func makeCmd() error {
	cmd := exec.Command("echo", "1")
	c, err := Default.Start(cmd)
	if err != nil {
		return fmt.Errorf("error monitor start, %s\n", err)
	}
	_, err = Default.Wait(cmd, c)
	if err != nil {
		return fmt.Errorf("error monitor wait, %s\n", err)
	}
	return nil
}

Codecov Report

Merging #3267 into master will decrease coverage by 0.03%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #3267      +/-   ##
==========================================
- Coverage   44.56%   44.53%   -0.04%
==========================================
  Files         113      113
  Lines       12194    12203       +9
==========================================
  Hits         5434     5434
- Misses       5928     5937       +9
  Partials      832      832

Flag
Coverage Δ

#linux
48.49% <0%> (-0.05%)
:arrow_down:

#windows
39.8% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

runtime/v2/shim/reaper_unix.go
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #3267 into master will decrease coverage by 0.03%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #3267      +/-   ##
==========================================
- Coverage   44.56%   44.53%   -0.04%
==========================================
  Files         113      113
  Lines       12194    12203       +9
==========================================
  Hits         5434     5434
- Misses       5928     5937       +9
  Partials      832      832

Flag
Coverage Δ

#linux
48.49% <0%> (-0.05%)
:arrow_down:

#windows
39.8% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

runtime/v2/shim/reaper_unix.go
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Is the c.Wait() that part of the code that causes the deadlock?

Is the c.Wait() that part of the code that causes the deadlock?

I still not understand why c.Wait() cause deadlock, if this caused deadlock, can move it to goroutine
go func() {
        for e := range ec {
            if e.Pid == c.Process.Pid {
                exit = e
                c.Wait()
                hasExit <- true
            }
        }
    }()

No, I was asking you if you knew if the wait call was causing the deadlock or if it was something different.

No, it not the part of deadlock from code and from test code I post. I am sorry I just find two code in runtime/v1 and v2 not same, one put the c.wait in the goroutine, and one is not. But I donot think it will cause deadlock.
I will do more test to verify the patch do work.


BIGINT constants support

Parser fails with when SQL expression contains long BIGINT constant.
Example:
select * from student where student_no =<PHONE_NUMBER>0000035001;

Error:
java.lang.NumberFormatException: Passed value does not contain a parsable long value

I see that net.sf.jsqlparser.expression.LongValue keeps value as long. Maybe it should be BigInteger. Or maybe BigIntegerValue expression should be introduced.
Source problem: https://github.com/serge-rider/dbeaver/issues/1116

Hope that helps. I did not yet published the compiled version.
The LongValue now accepts all numbers regarding the grammar definition.
< S_LONG: ( <DIGIT> )+ >
So veeerrry large numbers are allowed.
Only if one wants the long value using getValue, the Long.valueOf call will fail. I introduced another getBigInteger method to handle larger values.

Great, thanks!

I am a fan of dbeaver. Thx  for using JSqlParser. Tobias
Am 1. Februar 2017, um 17:55, schrieb Serge Rider<EMAIL_ADDRESS>Great, thanks!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.￼
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/JSQLParser/JSqlParser","title":"JSQLParser/JSqlParser","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/JSQLParser/JSqlParser"}},"updates":{"snippets":[{"icon":"PERSON","message":"@serge-rider in #390: Great, thanks!"}],"action":{"name":"View Issue","url":"https://github.com/JSQLParser/JSqlParser/issues/390#issuecomment-276713418"}}}


Avoid exclusive language "blacklist"

Checklist

[x] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated
[x] PR title is ready for changelog and subsystem label(s) applied

A tiny change in an effort to be more inclusive. Thanks https://twitter.com/topclaudy/status/1267450297816879107

Closing issues
n/a

This will require co-ordination to migrate the existing ENV VARs over to the new format.

This will require co-ordination to migrate the existing ENV VARs over to the new format.

correct, but I thinks it's totally worth it doing this.


Support Java-style escape sequences

Support Java-style escape sequences (e.g. \uDDDD for Unicode character) by referring to the lexer of Language.Java package v0.2.7. Add an example examples/StringEscape.sf for using escape characters. This pull request is intended to solve Issue #72.

Since it already uses language-java, isn't this possible without copy-pasting language-java parser code?

@tomtau It seems the unescape function convChar is a private function in the Lexer. I don't know if we can reuse that function if it is not exported.

I see; I guess that's fine then. Maybe later we may need to fork language-java, I remember that in the later version's AST, some things were missing.


Add different varieties of shapes

#7

Need to add more shapes

closing this as of now because we should now focus on completing the website first. Then we will come back to build more shapes.

closing this as of now because we should now focus on completing the website first. Then we will come back to build more shapes.

Yes! roger that.


Incompatibility with lcobucci/jwt:^5.0

Summary
Laravel Passport 11 requires "lcobucci/jwt": "^4.3|^5.0", but if we haven't specified a version lower than 5.0, the CheckForClaim middleware fails.
Details
The \Lcobucci\JWT\Configuration::forUnsecuredSigner() method is deprecated since version 4.3 of the lcobucci/jwt package. This method is used in the CheckForClaim middleware of this package.
Potential fix options

Migrate to symmetric signer with dummy configuration like:

Configuration::forSymmetricSigner(
    new \Lcobucci\JWT\Signer\Rsa\Sha256(),
    \Lcobucci\JWT\Signer\Key\InMemory::plainText('empty', 'empty')
)

Lock to "lcobucci/jwt": "^4.3 in composer.json,

Yes, it seems like it is a minor release done just yesterday. Since the parser is only used from the configuration, it could also be rewritten like it's done in passport.

Hi, I released a new version 5.1.0 which I think should fix the issue. I installed a fresh laravel, fresh passport, and latest claims package and I correctly got claims on the JWT.  Let me know.

Yes, it works like a charm. Thanks!


[AutoPR compute/resource-manager] Add new API convertToSinglePlacementGroup for VM Scale Set.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5614

(message created by the CI based on PR content)


Removing 'horizontal-form' class from the form tag. See issue #16.

To fix issue #16. Any concerns with this, @bassplayer7 ?

I think that is good. Thanks for fixing that!


Running the Prometheus Operator scoped to a namespace

This request is to propose a new documentation page explaining how to use Prometheus Operator with namespaced scope in for example restricted environment.
#787

That doesn't look quite right. Please open the PR against the master branch, and it looks like you're not proposing to merge from your fork/branch.

Please open a new PR against the master branch.


added host genome generation wdl

I created a basic wdl file for generating host genomes. This will be deployed automatically alongside the short-read-mngs wdl files. Developers can use the single wdl infrastructure to manually fill in a JSON template with the values it needs. This may not be the cleanest solution but it gets us off of running idseq-dag in one of the last few places and it's simple. I also think it makes sense to keep here because host genome generation is part of the short-read-mngs pipeline.
I am testing this now by running it to generate the new host genomes. I will update the wiki if it works.

Went with a different approach

Went with a different approach


chore: [FX-4058] update jira deployment

FX-4058
Description
We should adjust jira-deployment GH Action to trigger Jenkins job to create JIRA deployment properly.
How to test

Use alpha package or branch name to test

Development checks

[x] Add changeset according to guidelines (if needed)

PR commands

List of available commands:

@toptal-anvil ping reviewers - Ping FX team for review

@toptal-anvil ping reviewers


New-template-annotations

Is this a new chart

No

What this PR does / why we need it:
This PR adds the ability to insert annotations inside spec.templates into this chart using the reffered value.yaml file in this repo.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x ] DCO signed
[x ] Chart Version bumped
[x ] Variables are documented in the README.md
[x ] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @dwardu89

/assign @fabioviana

/s

/ok-to-test

/lgtm


AttributeError: module 'scvi.data' has no attribute 'setup_anndata' when following atlas-level integration tutorial

I am following the documentation for atlas level label transfer as found here. When following precisely the same code structure, I get the error.
scvi.data.setup_anndata(
    adata,
    layer="counts",
    batch_key="batch",
    labels_key="celltype_scanvi",
)
 >>> AttributeError: module 'scvi.data' has no attribute 'setup_anndata'

Versions:

'0.16.2'

Where did you get that link? The correct one is:
https://docs.scvi-tools.org/en/stable/tutorials/notebooks/harmonization.html
As you can see in the URL of the one you sent there is 0.10.0, indicating this is the documentation for v0.10.0

Thank you! I simply googled "scvi label transfer", and clicked the very first result which brought me to the page I linked initially.


Want different color for map keys and values

As the following screenshot shows, Sass map's key-value pairs are displayed in the same color, unlike property name-
value pairs in CSS declarations. I am not sure how you guys feel, but personally I prefer to have a clearer distinction between them.

Thank, I will update in the next major version (2.0).


High-Resistivity Poly Resistors LVS Issue

I find LVS issues with the attached source files which consist of two sky130_fd_pr__res_xhigh_po resistor networks. Manually inspecting the netlist I see no difference.
Netgen agrees the topology is the same but differs on the property values:

Netlists match uniquely.
Circuits match correctly.
There were property errors.
sky130_fd_pr__res_xhigh_po_1p00_12p4_0[1]/sky130_fd_pr__res_xhigh_po0 vs. sky130_fd_pr__res_xhigh_poRptat3:
w circuit1: 1   circuit2: 7   (delta=150%, cutoff=1%)
sky130_fd_pr__res_xhigh_po_1p00_12p4_0[1]/sky130_fd_pr__res_xhigh_po0 vs. sky130_fd_pr__res_xhigh_poRptat3:
w circuit1: 7   circuit2: 1   (delta=150%, cutoff=1%)
sky130_fd_pr__res_xhigh_po_1p00_12p4_0[9]/sky130_fd_pr__res_xhigh_po0 vs. sky130_fd_pr__res_xhigh_poRctat6:
w circuit1: 1   circuit2: 7   (delta=150%, cutoff=1%)
sky130_fd_pr__res_xhigh_po_1p00_12p4_0[9]/sky130_fd_pr__res_xhigh_po0 vs. sky130_fd_pr__res_xhigh_poRctat6:
w circuit1: 7   circuit2: 3   (delta=80%, cutoff=1%)
sky130_fd_pr__res_xhigh_po_1p00_12p4_0[9]/sky130_fd_pr__res_xhigh_po0 vs. sky130_fd_pr__res_xhigh_poRctat6:
w circuit1: 3   circuit2: 1   (delta=100%, cutoff=1%)

issue_source_files.zip

@yrrapt :  This appears to be a netgen issue and I will need to investigate it.  Apparently the combination of parallel and series resistors is not being combined correctly, although the algorithm should have been pretty straightforward, identifying and combining parallel devices first, then series.
If you ensure, as you have done, that your schematic side netlist represents the resistors exactly as they are in the layout, then you can work around the problem by editing the sky130A_setup.tcl setup file for netgen.  Comment out ("#") the three lines that indicate how to combine resistors in series (lines 47-49 and lines 60-62).  This will force netgen not to combine the resistors in series.  With that change, it doesn't have any problem matching the two netlists exactly.
Meanwhile I will track down what is wrong with the series/parallel combining algorithm.


⚠ Bofrost.lu has degraded performance

In 48d3b84, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2236 ms

Resolved: Bofrost.lu performance has improved in 60350ff after 32 minutes.


Add a test to demonstrate aggregate cluster circuit breaker behavior

Based on code spelunking, I believe aggregate clusters have a single set of circuit breakers, not per-component cluster. It would be helpful to add some tests to test/extensions/clusters/aggregate to demonstrate this.
CC @yxue

Looking at this.

If no one else is interested, can you assign the task to me

@Belyenochi thanks, assigned.

@Belyenochi if it is alright with you, may I take this issue off your hands?


fix(scripts/artifacts): fix check-tiup.sh

Compatibility to run for version lower then v8.4.0
Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

tested manually.

fix the issue we found in releasing for v8.4.0

/hold
I want add more changes for other script, i do not want to write more chore pull requests.

/unhold


fix: assets with special characters

Closes #121.

I recommend adding a small unit test to cover this case... and the following potential cases...
Even if it takes a bit more time to fix.

I really agree for the tests. We seriously need unit tests inside package:media_kit.
There's a lot to cover at the moment. The rendering size is still well tested.

I added a unit test, I don't know the Dart / Flutter conventions, I did what I thought was right.

Converting to draft for now based on the last comment on issue thread.


scrolling not too smooth

I see scroll behavior in items that is not as “smooth” as native. There is a little bit of jerkiness when scrolling. You can see it in the View > Sections area of Jasonpedia with the Jason app.
Please disregard the first time that it loads, as it clearly has to load images, maps, etc. After it has loaded, it still has a distinct "jerkiness" to it that you typically not see in native apps (mail, duck duck go ios app, etc.), even when scrolling somewhat slowly.
My app has a header, footer and one section with a bunch of items, typically a dozen or so, 6 showing at a time. Every app will improve if the framework is smooth at scrolling.

The example on Jasonpedia (more specifically the "section" view where it showcases multiple components) is choppy because it has tons of distinct components all being rendered simultaneously. This is an edge case, because most apps won't have so many different types of components in one screen. Basically this shouldn't be a problem for 90% of the cases, which includes your case.
What I do want to make sure is if this is actually a problem you are facing with your app right now. If your app actually scrolls noticeably choppy, that should not happen. For most apps with just a couple of distinct component types (image/label) it should scroll smoothly.
If it's actually slow, could you share your code so it can be tested?

I'm confused. When I mentioned this in slack, you immediately said you had noticed it as well.
In any case, here is an example with a long list that shows the effect. It's not slow .. but rather it shows also even when scrolling slowly. Because of that, I would think it might not be a performance issue (i.e. it does not happen only when scrolling fast, or with lots of interactive things like maps, input boxes, etc., ... just a list of items seems to do it).
This was mostly filed to track the issue, though it's not a high priority one, just a nitpick where the framework feels just a little bit less than an ideal native counterpart.

Maybe we are talking about different things. I just tried the link you shared on my phone and recorded it as video. Here's what it looks like: https://youtu.be/jogQP_RBYGU
If yours doesn't feel this way, then there's something wrong.

You are scrolling way too fast. If you scroll like you would read through post headlines or something, you will feel it's laggy at certain intervals. I will see if i can post a video (though you said you noticed it too right at the start!). Anyway, it's a minor jumpiness to it, not major.

I think it must have been a miscommunication. If it was actually bad I would have been working on it.
I do tell people that the particular jasonpedia view page with many components can feel choppy exactly for the reasons I mentioned above. But that's the only page I notice any issues. Maybe this is what you heard from me?
Please do share the video, and also share the device spec you're using. I just went back and tried scrolling slow, and it works fine. maybe it feels different on different devices but I have no idea because I only can test on a couple of different devices. If that's the case I will be sure to take a look at this with high priority

As I said above, it's not high priority by any stretch. I just added it in case someone at some point wants to look into it.
Scrolling does not feel native-smooth in virtually any of the Jasonette apps I have tested (typically in Jason), where there is more than a pageful of scrolling (i.e. not in simple lists of labels). There is always a jumpy feel to it.
See if you notice in this video. In Jasonedia I notice it as well in View > Component > Image.
My device is an iphone 6 with the latest ios as of this writing (10.1.1) and not much running on it.
Again -- a small thing that, if fixed, would make things smoother and even more indistinguishable from native.

I was looking at the videos and I couldn't really see the difference. Could it be something related to iOS' momentum or something? What I mean is, if there's any lag or performance impact, it is not that evident.
What do you think about this: repurpose this issue or close it and open another with an example that really shows off and highlights what the problem might be… Call it something like Screen stutters with lots of heavy components and label it help wanted. We'll also need some benchmark data to support us. This example could be an oversized version of what we have in jasonpedia. 💭?
One thing I think is important to highlight is that Jasonette is native. We need to be careful to not plant a doubt seed into newcomers mind… 😄

Just wanted to add my feedback. I gave an app written with Jasonette-ios to a friend which had ~ 15 items, each item has a small 64x64 image, and a title - typical "media" object layout.
The first feedback I got was how choppy/ragged the scrolling was - iPhone 7 plus, so not a hardware issue.
@gtramontina I know Jasonette is native, but unless it looks/behaves like it too that point is moot with the users. This isn't a problem with lots of heavy components, the iPhone 7's processor is more than capable of handling scrolling a dozen or so media objects (using bootstrap terminology)

@darenr can you share the JSON? Like I mentioned, that's not supposed to happen for most apps.
I have iPhone 5, iPhone 6 and an iPad mini. I can try it out.

@gliechtenstein absolutely, appreciate you taking a look: https://www.jasonbase.com/things/Lrz.json
what it appears to be, from looking at the screen carefully is that as some element goes out of view some event fires which injects a minor delay which suspends the disbelief of the screen view being a physical object that's being manipulated.

I made progress on understanding this a little. The choppiness occurs when a new section scrolls into view. I can easily see this now when I write the json to position the section change at a different point - basically adding to each section a big space eliminates the choppy scrolling until we get to the section transition. I hope this helps understand it better so you can see what's going on at that point.

Here's the fix
First things first, please try this branch I just pushed: https://github.com/Jasonette/JASONETTE-iOS/tree/scroll_improvement It's improved a lot.
The nature of the problem
That said, I want to clarify what this problem is, and what it is not:
This is NOT a matter of feeling "native" vs. "non-native". This is a "native" problem. In fact, this is one of the most common problems iOS developers deal with. Just take a look at all the google search results for "UITableView jerky"
Actually if you really want to see this problem in action, please try opening your iOS mail app (yes, the default mail app that ships with the iPhone). When you have multiple accounts added to the mail app, you will feel the jerkiness as you bring the app from background to foreground and start scrolling after a bit of inactivity.
I don't know if you guys have tried HTML5-built apps, but the scrolling problem there is on a completely different level than this. It's more about how responsive the scroll is to your touch than if there's a frame skip. Once you try those apps you will get why people talk about building apps natively.
So why does this problem happen on a native app?
The problem happens because of the way iOS handles scrolls.
Basically, when you have 1000 rows on your screen, there will be only like 10 rows that are visible at a time. The OS doesn't render the rest 990 until you start scrolling. And as you start scrolling, it creates a new row by recycling the row that just disappeared. This way it doesn't have to keep all 1000 cells in memory, it just needs about 12. Still it gives the illusion that there are all 1000 rows in the out-of-screen area.
This recycling scheme works well when you're dealing with static content with static width and static height, because when you recycle one cell with another, they all have the same dimension, therefore no drastic change of each cell size as you scroll.
But it becomes hard as we start dealing with dynamic content that needs to adjust itself in realtime as you scroll. Because, in this case when you take the row that just disappeared and try to reuse it, you need to make sure the cell has the right dimension to fit the new content, etc.
There are many techniques used to deal with this, but they're all a matter of optimization. For example, instead of having to calculate the width and height in realtime you could send already adjusted images from the server so the client knows exactly what their sizes are, etc. Most app developers use several of these techniques to make their apps perform well.
Jasonette and optimization
Jasonette is a general purpose app that needs to take care of all these special cases, but in a more generic way. That's what makes it non-trivial. Like I mentioned above, if you're building a single app, you can hardcode all the optimizations, but Jasonette shouldn't try to do that. It instead needs to find the most severe bottlenecks and start optimizing from there.
That's why until now Jasonette really had no optimization logic, and that's where some of the jerkiness came from.
With the new branch I've added some optimization logic. I think there are more ways we can optimize this further going forward, but I think it's a good start, and for now I think it's good enough.
Please try it out: https://github.com/Jasonette/JASONETTE-iOS/tree/scroll_improvement

My feeling is that it's substantially improved. Great job!
In longer lists (like in the RackerLogger app, under the longer list of rackets with 60 to 80 items) one can still notice the issue a little bit, but it's barely noticeable. I worked in CPU/GPU optimizations way back when DVD play was the rage on laptops and I guess I'm still more sensitive that the average user for these things.
I did not realize it needed so much optimization work. I created this as something to track in the future and not critical, as I mentioned. I thought maybe it was some small setting somewhere.
As you said, I think it's good enough. Any more optimization in the future will be welcome, but this is great. Awesome job!

Appreciate the optimizations.
I don't really agree with "This is NOT a matter of feeling "native" vs. "non-native". This is a "native" problem" - the expectation from users is that an app will scroll smoothly, it's a very common issue because it's also a very basic part of rendering, the scroll port code will (typically) call back into your components to ask for their dimensions so it can know how to layout the upcoming screen elements. That's just how scroll port rendering works. If it doesn't keep up with 60fps then users will feel that they aren't using a native app, that was my point.
I've worked with layout managers that use a scrollport like iOS the usual/best practice issue for knowing cell height is to keep a dictionary. it's usually possible to know the cell height before you've started rendering. Although the data is loaded dynamically I'm not sure that cell height really is dynamic in Jasonette, aside from images which is usually solved using a placeholder. It's not possible inside of a cell's rendering to change the height dynamically as far as I know, I can't for example set height using a function - variable substitution is all known before rendering starts. So I think that if you create a dictionary of cell heights then use the async image loaded handler to update as/when images have a dimension it will make scrolling smooth. I suspect it was being calculated every frame by summing which is of course inefficient. That said, for a dozen items I'm really surprised that the quad core processor can't keep up with 60fps with even the most inefficient code. I would totally understand if it was 1000 elements with lots and lots of images, but I need(ed) only a dozen.
Anyway, thanks for the fix.

My two apps went live with these new performance improvements. It may not be perfect (maybe because my apps do not have fixed height in every row?), but it's noticeably smooth.


PRO-1861 - Error handling and apollo/client package fixes

Description

Added possibleSolution parameter for the errors that are commonly returned from the bundler which are taken from the eip4337 error codes
Updated package dependencies for the apollo/client
Updated config.yml to point to this branch for running e2e tests temporarily.

How Has This Been Tested?

Tested Locally and build also was successful

Screenshots (if appropriate):

Types of changes

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

@vignesha22 pls can you address the issue related to failing e2e tests?

Please ignore the package version update as 1.3.9 is not yet published as that merge with master failed to build because of dependencies outdated @0xSulpiride @lbw33 @kaushalrajbacancy


Upgrade Ansible to 2.0

This needs to be tested as it looks like the upgrade will break things.

Closed by #142


Move crd to crds dir

PR for #31

Hey @Transmitt0r, to do this you'd have to edit the makefile to swap them around. This pull completely automagically so manually editing the files doesn't persist the changes

@tomhobson hey, this PR is now 9 months old and I now understand a lot better why the CRD's are not part of the CRD directory (resources in the crd dir do only get applied once and then not updated, this would be confusing for people that use this chart). I'm still slightly annoyed that this means that this chart can't be used as a direct Helm-dependency, but applying CRD's should probably be done in a separate step from your application anyways since they are cluster-scoped resources.


Use import/group-exports for nodejs only

This commit https://github.com/strvcom/eslint-config-javascript/commit/e8452078753d043396559a10afa7227906526a54 breaks usage of styled-components on almost every frontend project
example:
import styled from 'styled-components'

export const StyledButton = styled.button`...`

export const ButtonWrapper = styled.div`...`

We can keep the rule in optional ruleset.

What's wrong with defining the components before exporting them...? 🤔
import styled from 'styled-components'

const StyledButton = styled.button`/* ... */`
const ButtonWrapper = styled.div`/* ... */`

export {
  StyledButton,
  ButtonWrapper
}

There is nothing wrong with it, just that nobody is using it like right now. 😀 Well, current projects can disable it and at least new ones will have it. Silly idea, we can close.

Yeah, it's unfortunate that I did not have time to implement autofixer for that rule... 😢 I guess existing projects will be better off disabling the rule and only new ones will use it until someone adds auto fixer for it.


AND-91 Fixed ordering of recent exposures.

Fixed ordering of recent exposures.
Changed demo data to adjust to the new way of creating Exposures


renderdoc is shutdown/unloaded on exit

When the renderers are shutting down they call unloadRenderDoc which (when renderdoc is present) will call Shutdown on renderdoc's API and then unload its DLL.
This is dangerous to do since Shutdown is only intended to be called right at startup immediately after the DLL is loaded, if you detect a case like too old a version of renderdoc being present. It should work in that scenario (although it's not guaranteed) but once you've started running the program it's impossible to reliably remove the hooks and you shouldn't call Shutdown or try to unload the DLL. Someone reported that it can cause app verifier issues (baldurk/renderdoc#685) but it could also just lead to crashes after that point.
Instead just leave the DLL alone and only call Shutdown if absolutely necessary after loading it in the first place.

But what happens after switching renderer for example, from D3D11 to GL to D3D12, etc.? bgfx internally manually loads/unloads these DLLs, there is no stub linkining. Just load once and leave it forever?

Yes, it should be loaded once and left forever, never shut down.


Can not override styles on MKIconToggle

Upgraded to version v0.3.2 and it seems that MKIconToggle is ignoring the styles that I'm passing to it. It was working in the previous version.
I was using it to make the toggle a bit bigger than the default size so if there is better way to do it now would be interested to know.

Hi,
Thanks for reporting this issue. How do you currently override the default style? Like that I'll be able to reproduce the same issue and try to fix it.

Was using like this:
<MKIconToggle
  style={{ width: 100 }}
/>

I found the issue(It was introduced "long" time ago : https://github.com/xinthink/react-native-material-kit/commit/116760340ca7d734a9768c6d1d464cdddf9e2221#diff-d3366018012b3dfe74baecaf89a0c7d1L86). I'll check with @xinthink to see if there is a good reason for this modification. In the meantime you can patch it yourself to see if it breaks something else ;)


Update vue package

Fixes a few syntax errors with later versions of vue, and bumps the vue package as necessary to work across more than just my dev environment. :)

@nschonni - if you could review, this fixes the build error that occurred.
My apologies for not testing in a prod like env. :)


What sdk is this for?

I am wondering if some of this documentation relates to the old WindowsAzure.ServiceBus.
As the new sdk Microsoft.Azure.EventHubs does not depend on servicebus, yet this doc mentions various servicebus exceptions.
It would also be good to have some documentation on the eventhubsclient retrypolicy / what type of exceptions it retries. I had to look into the source code here to find out.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d5b68363-44de-93fe-d564-336e32768e7c
Version Independent ID: 40f681e7-df94-2620-87c1-201d402203e5
Content: Troubleshooting guide - Azure Event Hubs
Content Source: articles/event-hubs/event-hubs-messaging-exceptions.md
Service: event-hubs
GitHub Login: @ShubhaVijayasarathy
Microsoft Alias: shvija

@adewaleo Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

This article is marked legacy now. It has a link to the newer article: https://docs.microsoft.com/en-us/azure/event-hubs/exceptions-dotnet.
#please-close

This article is marked legacy now. It has a link to the newer article: https://docs.microsoft.com/en-us/azure/event-hubs/exceptions-dotnet.
#please-close


Selection model

In the git infinite scroll story, click on commits to add them to a selection prop, hold down ctrl to select multiple.

Thanks for your contribution. I have some concerns about this selection feature you proposed, as it seems to not go well with the hover effect. Could you explain the specific use case for this addition? This will help me better assess its integration with the current design.

Sure - the purpose is to select two commits to do a diff comparison with, and to give the user visual feedback about the sequence position of the selected commits.  In our application these diffs will be displayed in realtime so knowing where the selection is presently positioned is helpful.
Another use case is when analyzing the repo state, it is helpful to show the user which commit they are presently analyzing, visually, in context with all other commits.
The selection function becomes important to us when we are displaying the commits alongside another react component that is reacting to the changing in commit selections.

Thanks for sharing this, sounds like a great feature! I’ll look into how best to expose the necessary functions or variables  to support your use case.


CI, MAINT: pin pytest for Azure win

pytest 6.0.0 was released yesterday and we've been
observing pytest related traceback in the Windows ilp64
Azure CI job consistently since yesterday, both in the main
repo and in backport CI:

gh-12600
gh-12626
gh-12611

here, the version of pytest is temporarily pinned to
the latest stable release before the new 6.x.x series;
perhaps the complex ecosystem of pytest + plugins +
Windows + 64-bit integers is enough to expose an issue
that needs a bit more testing upstream

not sure if this will actually fix the problem, but worth
a try...

I should also refactor the yml list of deps to a nice alphabetical
list instead of a 100+ char line, but try to keep the diff as simple
as possible here

@nicoddemus has something like this been reported upstream in pytest after the recent release?

I'm going to merge this; it's super low risk and we'll roll back if it doesn't help.
Thank @tylerjereddy for investigating CI issues.

Hi @tylerjereddy, thanks for the ping.
Can I see a traceback?

@nicoddemus I've opened a more detailed issue in your repo upstream, cross-linked above.


Integration "failed to set up" after update to 3.19.3

HA 2023.6.3 running in Docker container on an RPi4B.
I updated the custom integration via HACS, to the suggested level, namely 3.19.3
On restart, HA reports the integration "needs attention", and "failed to set up".
Related entities are all "unavailable".
The only mention of the integration in the log is this:
ERROR (MainThread) [homeassistant.config_entries] Error setting up entry <tesla_login_id> for tesla_custom
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/tesla_custom/__init__.py", line 144, in async_setup_entry
    async_setup_services(hass)
  File "/config/custom_components/tesla_custom/services.py", line 61, in async_setup_services
    hass.services.async_register(
TypeError: ServiceRegistry.async_register() got an unexpected keyword argument 'supports_response'

I tried to supply a refresh token via the Integration options interface but it fails saying the id is already registered.

@purcell-lab We probably needed to bump the hacs.json requirements when we added supports_response for 3.19.x.
Supports_response was introduced in HA 2023.07.
@MrMEScott Your options are to update HA or downgrade the component.


Multicast packet APIs for dispatch core sending program pages

As long as our dispatch multicasts own a particular VC, we don't need to do path reservation. Additionally, all of our writes are less than MAX_BURST_SIZE, so we can use the packet APIs

Closing with 3bfc414


Allow compiling orchestrator to riscv

Description
Allow compiling orchestrator to riscv
Implementation ideas
I did a partial implementation here but got stuck with 4.3-beta2 working.
https://github.com/V-Sekai-fire/godot-orchestrator/tree/riscv-4.3-beta2

It's part of my proposal here I will submit to the godot engine organization. https://github.com/V-Sekai/manuals/blob/main/decisions/20240627-gdextension-as-libriscv.md


WeakMap polyfill does not work on IE11

@byao This implementation seems to work in IE11 according to Polyfill.io: https://github.com/Financial-Times/polyfill-service/blob/master/polyfills/WeakMap/polyfill.js
We will be doing further testing on our end to verify

@byao Any repro step? I tried loading WeakMap both in the console and in jsfiddle using a script tag and they both work fine.


finish upgrading webpack & babel dependencies, fix monaco example

[x] reintroduce the monaco-graphql-webpack workspace for local resolution, to honor DEVELOPMENT.md
[x] tweak webpack configs for upgrade, to work on clean build
[x] upgrade babel versions and webpack loaders/plugins and implementations
[x] consolidate versions across the monorepo so that, despite adding a workspace, our yarn.lock file only grows by ~200 lines

I have tested this exhaustively across browsers, I hope it's ok, I had to tweak the postcss configuration, but after reviewing the changelogs I don't think we should expect changes that would impact our users (theming css variables, etc). There are a couple tweaks and improvements that are still dev related - for example, react fast refresh vs HMR plugin, etc, but those can wait or just be replaced by another bundler soon if we still go that route


Move reconnect code into KazooTestHarness#force_reconnect

I think this will be useful for other tests so move it to one of the base classes (i.e.: I am already using it for some branches I am preparing for read-only support and SetWatches support).
Signed-off-by: Raul Gutierrez S<EMAIL_ADDRESS>

Looks fine, but needs a rebase.

Please re-open to rebase and update as needed.


adapt runner and session for concurrency

The current implementation of the session and the runner do not play to well when we try to introduce concurrency. This is not because of concurrency per say, but rather we are adding another dimension of functionality requiring an excessive number of changes.
We have 2 types of sessions, primary and resume. The runner drives the session. Either of these session types used to have only a single way of driving the navigator, ie in a synchronous fashion. Then along came concurrency and that was shoe horned in, but not so well. To support concurrency, the following was added:

accelerator: added as a property of the runner
runner operators: sets concurrency options the accelerator
AsyncInfo: contains properties relating to concurrency, unfortunately also containing the context which as I recently discovered should not be stored in a struct because that would lead to the lifetime of the context potentially outliving the go routine it relates to and could be interacted with when it is no longer valid. Actually, it was this issue that led to the need for this refactor requirement.

AsyncInfo has to be passed in as variadic parameter via the following routes:

PrimarySession.Run to navigator.ensync
ResumeSession.Run to navigator.ensync and then ResumeController.Continue

⚠ Actually, just writing this out has me thinking, for the resume scenario, why do we have 2 opportunities to pass in AsyncInfo? We should try and remove the one from Continue. In fact, it looks like this was a left over parameter, it is set on strategy.ResumeInfo, which is passed into strategy.resume, but it is not retrieved from here. So let's delete it from Continue.
To fix this, the accelerator needs to be accessed via some other abstraction that has non currency equivalent.
Todo items:

Define an extractor specially for the async parameters that receives the params from a slice of any and returns the typed parameters. Let’s call this extractSyncParams
By default the sync object will be inline
Define a new async operator that by default sets no of workers to NumCPU. This sets the sync object to accelerated. This operator takes no of workers as an optional parameter
We now don’t need WithPool operators
Introduce no of workers type def

See the bridge pattern.
We also have to re-consider context. It is not just useful for async scenario. It can and should be used for the inline use case, because we need to support cancellation from ctrl-c interrupt. For this reason, we need to build the context into the inline situation, however we should never need a cancel function that is required by the accelerated scenario. The interrupt can be handled by the client using os.Interrupt

The problem with the Run method (on the runner/driver) is that we want a different signature depending on the sync is inline or accelerated.

One way to resolve this is to have th Run method be defined in a way that is compatible with both sync schemes, ie only have path and optionsFn parameters. We then pass the accelerated parameters into Accelerate. The issue with this approach is that we need to be able to define the context on a struct, which we are trying to avoid. But we can appease this demand by implementing a release mechanism invoked as part of the walk (just before it), that passes the temporarily stored context into walk, then discards it immediately. This will ensure that it is not accidentally referenced outside of it valid lifetime.
Another way to solve this issue is to pass in a func to Run... The client can pass a function that sets all the appropriate properties, but this still has the downfall of requiring storing the context.
But a better way to implement this that does not require storing context on a struct and that is to define Run that take variadic args list of any. There then needs to be an extractor function that can turn these any args into the required args. The downfall of this approach is we lose type safety. The only we can do to compensate for this is to make sure that we panic if we detect incorrect specification of args. The only 3 valid types of args are: context, cancel and *ai.

Some assistance from draw.io is required to get a cohesive design that works across primary/resume, inline/accelerated.

oops, I discovered a very bad faux par in the naming of the resumeNavigator. It is the front end of the navigator that is used by a primary session and a resume session. There appears to be nothing in it that is related to resume so it should not be called the resumeNavigator; that is very misleading.


WebSocket connection to 'wss://mydomain:8443/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED

Getting error :
WebSocket connection to 'wss://mydomain:8443/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
configure letsenctypt ssl :
Open port : 8888 , 8443
I'm using apache2 and i get configuration for ngix not for apache2 if any have this answer please provide.

Make sure you've got something dealing with proxying set up.  The wiki here has a couple of examples of ways to set up for secure connections.

Really helpful buddy ...
i was using stunnel but when you have apache2 there is no need of use stunnel and using proxy i can achieve that one.
https://github.com/GeniusesOfSymfony/WebSocketBundle/wiki/Ssl-proxy-on-apache-2.4-to-ratchet-symfony-2.8-on-Ubuntu-16.4
Thanks @mbabker


Release v12.2.0 is only a tag

The latest v12.2.0 release is only showing up on GitHub as a tag and not as an actual release. This means that automation (or anything else) listening for releases will not work correctly.

Oops! My mistake. It's now a release on github.
Thank you.


add getters/setters to all Resultset classes and dependencies - issue…

… #89
Added getters and setters / Switch some methods from private to public

@pierrelambert
Does this solve the serialization issue?
Can you add a test?


eda: enable URL to access a study on a map (or eda workspace too?) with filters applied

The use case is mapping the old mapveu link:
https://vectorbase.org/popbio-map/web/?projectID=VBP0000806
to something like
https://vectorbase.org/vectorbase/app/workspace/maps/DS_480c976ef9/EUPATH_0000605?POPBIO_8000215=VBP0000806
Or f=POPBIO_8000215:VBP0000806 potentially multi-valued (allowing multiple variables)
We should probably limit this functionality to single value filters (e.g. one VBP ID) and use a different approach for multiple values (e.g. sequence IDs) --> https://github.com/VEuPathDB/web-monorepo/issues/912
Site search results should also use this mechanism.
DF's comment from Slack:

A question is, should these result in a saved analysis in the users history, or should it remain unsaved until the user does something with it (adds a new filter, configures a market, etc). Also, will we want to specify other things, like active marker type and variable?

unclear is this needed anymore since we came up with a new route to the map for legacy links

I don't think this is needed. Another similar case we have is for popset studies, but we will also be using something custom for that, since we could end up with filters that have a large number of values, exceeding limitations in GET requests


Draggable feature in modal popup

can we have this draggable property for a modal popup ?
I am using ngx-modal to create a modal popup

@lafiza
I use the ModalModule in ngx-bootstrap to open the modal popup, so I can just add ngDraggable in modal-content such as:
<button type="button" class="btn btn-primary" (click)="staticModal.show()">Static modal</button>

Static modal

        <button type="button" class="close pull-right" aria-label="Close" (click)="staticModal.hide()">
          ×
        </button>

        This is static modal, backdrop click will not close it.
        Click × to close modal.

I can test it in ngx-modal later.

I use something similar to that, but found an issue with being able to use the mouse to select any text in the modal-content area, so I tried to use a handle for the modal-header like this:

				<button type="button" class="close" aria-label="Close" (click)="dismiss()">×</button>

				<ng-content></ng-content>

				<button type="button" class="btn btn-primary" (click)="dismiss()" *ngIf="showFooter">Close</button>

but with this, the user must click on an area outside the h4 to be able to drag.  I've put the handle on the h4 as a workaround, but I could see this being an issue in some scenarios.  Can you make the handle work on child elements, or allow for multiple handles?

@clabough I use your h4 approach, thank. In order to make the whole header as a drag handle I modified bootstrap styles a bit:
.modal-header {padding: 0}
.modal-header h4 {padding: 15px}
.modal-header button.close {margin: 15px}


Weird SSL Problem.

Here are details
http://stackoverflow.com/questions/35255037/i-cant-run-rake-dbmigrate-on-heroku/35255942#35255942
When I try to run heroku logs, I get this error. It is very unstable. With proxy I can "sometimes" make commands work. Also I can not connect to heroku.com It says unsecured connection.
Firefox, Ubuntu 14.04
!    Heroku client internal error.
!    Search for help at: https://help.heroku.com
!    Or report a bug at: https://github.com/heroku/heroku/issues/new
Error:       hostname "api.heroku.com" does not match the server certificate (OpenSSL::SSL::SSLError)
Command:     heroku logs
Version:     heroku-toolbelt/3.42.33 (x86_64-linux) ruby/2.2.2
Error ID:    e7d2409f80f746cbb8308e2539a544bd

More information in /home/xelamony/.heroku/error.log

Those are some of the errors I get when I try to "heroku run rake db:migrate", "heroku run rails c"
▸    Hostname/IP doesn't match certificate's altnames: "Host: api.heroku.com. is not in the cert's altnames: DNS:*.demdex.net, DNS:demdex.net"

 ▸    Hostname/IP doesn't match certificate's altnames: "Host: api.heroku.com. is not in the cert's altnames: DNS:*.securefirmportal.com, DNS:securefirmportal.com"

@MrWilhelm your proxy software appears to be using its own certificate rather than propagating the heroku certificate, therefore the heroku toolbelt rejects your proxy's certificate because the hostname does not match.  This suggests that your proxy is not configured correctly, rather than a problem in the heroku toolbelt.

Just wanted to chime in that I received this error today, just once. Haven't been able to replicate. On Comcast residential internet in San Francisco, no proxy. Unfortunately I closed the terminal buffer so I can't paste the altnames given.

I'm also getting very similar SSL errors today:
 !    Heroku client internal error.
 !    Search for help at: https://help.heroku.com
 !    Or report a bug at: https://github.com/heroku/heroku/issues/new

    Error:       hostname "manager-api.heroku.com" does not match the server certificate (OpenSSL::SSL::SSLError) (Excon::Errors::SocketError)
    Backtrace:   /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/openssl/ssl.rb:139:in `post_connection_check'
                 /Library/Ruby/Gems/2.0.0/gems/excon-0.31.0/lib/excon/ssl_socket.rb:86:in `initialize'
                 /Library/Ruby/Gems/2.0.0/gems/excon-0.31.0/lib/excon/connection.rb:410:in `new'
                 /Library/Ruby/Gems/2.0.0/gems/excon-0.31.0/lib/excon/connection.rb:410:in `socket'
                 /Library/Ruby/Gems/2.0.0/gems/excon-0.31.0/lib/excon/connection.rb:122:in `request_call'
                 /Library/Ruby/Gems/2.0.0/gems/excon-0.31.0/lib/excon/middlewares/mock.rb:42:in `request_call'
                 /Library/Ruby/Gems/2.0.0/gems/excon-0.31.0/lib/excon/middlewares/instrumentor.rb:22:in `request_call'
                 /Library/Ruby/Gems/2.0.0/gems/excon-0.31.0/lib/excon/middlewares/base.rb:15:in `request_call'
                 /Library/Ruby/Gems/2.0.0/gems/excon-0.31.0/lib/excon/middlewares/base.rb:15:in `request_call'
                 /Library/Ruby/Gems/2.0.0/gems/excon-0.31.0/lib/excon/middlewares/base.rb:15:in `request_call'
                 /Library/Ruby/Gems/2.0.0/gems/excon-0.31.0/lib/excon/connection.rb:265:in `request'
                 /Library/Ruby/Gems/2.0.0/gems/heroku-3.3.0/lib/heroku/client/organizations.rb:31:in `request'
                 /Library/Ruby/Gems/2.0.0/gems/heroku-3.3.0/lib/heroku/client/organizations.rb:76:in `get_orgs'
                 /Library/Ruby/Gems/2.0.0/gems/heroku-3.3.0/lib/heroku/command/base.rb:53:in `org'
                 /Library/Ruby/Gems/2.0.0/gems/heroku-3.3.0/lib/heroku/command/apps.rb:237:in `create'
                 /Library/Ruby/Gems/2.0.0/gems/heroku-3.3.0/lib/heroku/command.rb:218:in `run'
                 /Library/Ruby/Gems/2.0.0/gems/heroku-3.3.0/lib/heroku/cli.rb:28:in `start'
                 /Library/Ruby/Gems/2.0.0/gems/heroku-3.3.0/bin/heroku:17:in `<top (required)>'
                 /usr/bin/heroku:23:in `load'
                 /usr/bin/heroku:23:in `<main>'

    Command:     heroku create
    Version:     heroku-gem/3.3.0 (universal.x86_64-darwin13) ruby/2.0.0

I'm not running a proxy either. Based in the UK, using EE broadband (unlike OP, no problems accessing heroku.com though).

you are running an ancient version


How to set the overlay option of webpack-hot-middleware

The code below don't work.
app.use(require("webpack-hot-middleware")(compiler, {
    overlay: false
}));

The code below don't work.
app.use(require("webpack-hot-middleware")(compiler, {
    overlay: false
}));

If you want to set the overlay, you must do this by setting the value to true
app.use(require("webpack-hot-middleware")(compiler, {
    overlay: true
}));


fix: export package.json and dist/svgo.browser.js again

Fixes #1998

Hmm, we could do something like this:
  "exports": {
    ".": {
      "import": "./lib/svgo-node.js",
      "require": "./dist/svgo-node.cjs",
      "types": "./lib/svgo-node.d.ts"
    },
    "./browser": {
      "import": "./dist/svgo.browser.js",
      "types": "./lib/svgo.d.ts"
    },
    "./dist/svgo.browser": {
      "import": "./dist/svgo.browser.js",
      "types": "./lib/svgo.d.ts"
    },
    "./bin/*": "./bin/*",
    "./dist/*": "./dist/*",
    "./lib/*": "./lib/*",
    "./plugins/*": "./plugins/*",
    "./package.json": "./package.json"
  },

We could also do:
  "exports": {
    ".": {
      "import": "./lib/svgo-node.js",
      "require": "./dist/svgo-node.cjs",
      "types": "./lib/svgo-node.d.ts"
    },
    "./browser": {
      "import": "./dist/svgo.browser.js",
      "types": "./lib/svgo.d.ts"
    },
    "./dist/svgo.browser": {
      "import": "./dist/svgo.browser.js",
      "types": "./lib/svgo.d.ts"
    },
    "./*": "./*"
  },

However, this will only make the imports available with the .js/.json suffix, excluding ./dist/svgo.browser which has an explicit alias defined. I think it's the best we could do for now without explicitly adding aliases for each and every file in the repo.
Alternatively, it could be worth deprecated v3.3.0 and v3.3.1, and making a new release v3.3.2 which reverts the changes. Then we just make a v4.0.0 release, with less concern over breaking changes.

Agreed, @SethFalco the latter is the best choice.
But while at it, we should look into any other major changes slated for v4 like dropping any Node.js version support

Now that we're committed to do a v4 release instead, I'm thinking we could close this, and make the change in imports one of the documented breaking changes.
That way, there's no need to define the aliases and duplicate type versions.
If there are no qualms with that, feel free to close the issue. Otherwise, hit me with any feedback!

Sounds good!
Let's document the changes for the release notes

Actually, I still think we need package.json there, don't we @SethFalco ?

Actually, I still think we need package.json there, don't we @SethFalco ?

As far as I'm concerned, package.json isn't considered part of our public interface, so normally I'd say it doesn't belong there.
I noticed in the other issue that it looked like you were importing it, though. Mind sharing your use case and we'll see if it makes sense, or maybe SVGO could do something better to export what is it you need?
For example, if you want the SVGO version at runtime, then this is something we could export ourselves.

We use it in svgomg for the version only during build time:
https://github.com/jakearchibald/svgomg/blob/d70f2619fbf6f662d04b6bccd9485558c06b52ba/gulpfile.js#L5

Understood, instead of export package.json then, how about we export a version like how some other libraries do:
import { version } from "react";
import _ from "lodash";
import axios from "axios";

console.log(version, _.VERSION, axios.VERSION);
// 18.3.1 4.17.21 1.6.8

I'll write up an issue later, should be simple to do.

Thanks for being so active with pull requests and issues, by the way. I'll be reviewing them over the next few days as I find time between other tasks.


Migrate to other ZMQ library for C++

We are currently using zmqpp to interact with ZMQ from C++, but this project is no longer actively maintained and hasn't had a new release since 2017. Because of this, Ubuntu no longer ships zmqpp since Ubuntu 22.04.
We could consider migrating to cppzmq, which is a header-only library and doesn't need to be installed separately.

Done in #195


[FEATURE] Rename package to AzureCommunicationUICalling

Purpose

Rename the project to AzureCommunicationUICalling

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

What to Check
Verify that the following are valid

AzureCommunicationUICalling and AzureCommunicationUICallingDemoApp can be build and tests can be run

@vhuseinova-msft, could you create a ticket to cleanup documents(including picture updates, renaming, etc) in Readme, Quick-start Documentation, Manual Installation, making a contribution guide and https://github.com/Azure/communication-ui-library-ios/blob/feature/project-renaming/AzureCommunicationUICalling/AzureCommunicationUICallingDemoApp

I couldn't run the local UI Test anymore.

I couldn't run the local UI Test anymore. Anyone else has this issue?

@AmyL219 fixed!

Please make sure we update the change log with this change

@JoshuaLai Updated!


remove cgmath support

cgmath is deprecated: https://github.com/bjz/cgmath-rs/issues/144
Removing support in favor of nalgebra will lead to a less confusing API.

I don't think the API is confusing. The only place where cgmath is used is here: https://github.com/tomaka/glium/blob/9ecf57c01096e3b18cd1cc568534f353781329a6/src/uniforms/value.rs#L500-552


Add servo-tomcat subproject: generate metrics related to tomcat

NetflixOSS » servo » servo-pull-requests #11 SUCCESS
This pull request looks good

NetflixOSS » servo » servo-pull-requests #12 SUCCESS
This pull request looks good

That's good to know. I'll do a couple of deployments with custom executors and make sure we're generating the same names. Thanks for the feedback.

NetflixOSS » servo » servo-pull-requests #13 SUCCESS
This pull request looks good

NetflixOSS » servo » servo-pull-requests #14 SUCCESS
This pull request looks good


Randomize the ArchiveTree the proper Python way

Signed-off-by: Jody Bruchon<EMAIL_ADDRESS>My C roots are showing. This removes the loop and uses Python's native random.shuffle() instead. Tested, works, checks out with flake8.

By the way, you may appreciate the video at the top of this article I dropped...it could be handy to show people why they ought to switch to this fork ;-)

Turns out Python sets are simpler to write and may be faster, so let's switch to those. At the least, they're much easier to read in the code.

https://github.com/ytdl-org/youtube-dl/pull/26643
@rebane2001
Someone else was looking for the same change.


Add --append-dat flag for TPC-DS benchmark

Signed-off-by: Andy Grove<EMAIL_ADDRESS>Within the TPC-DS code, the appendDat parameter had a default value in a number of places but the parameter wasn't always propagated, so it was not possible to override in some cases. This PR is essentially just a refactor so that the only place default values are used are when calling the top-level TpcdsLikeSpark.csvTo* and TpcdsLikeSpark.setupAll* methods and the default value here is still true so that this isn't a breaking change to that API when called from spark-shell. Also, appendDat is hard-coded to true when reading CSV during these conversions because the generated CSV files do have that extension.
The benchmark CLI is also updated to add an --append-dat flag so that the user can specify whether the input parquet or orc files have the .dat extension, meaning that the benchmark tool can now be used with the parquet files generated by spark-sql-perf.
I tested these changes by performing the csv to parquet conversion with and without the .dat extension and then used the benchmark runner against both datasets.
This closes https://github.com/NVIDIA/spark-rapids/issues/996

@revans2 One question I have with this PR is do we ever really want to append .dat onto the path when converting csv to parquet or orc? I wasn't really sure if we were doing this by design or not.

@revans2 One question I have with this PR is do we ever really want to append .dat onto the path when converting csv to parquet or orc? I wasn't really sure if we were doing this by design or not.

I did it in my code just for consistency when I did the conversion, but I am fine either way.

I did it in my code just for consistency when I did the conversion, but I am fine either way.

Ok. I think I'll leave the default this way since we're used to it working this way, and we can override it if we need to.

build

The build is failing with errors that are unrelated to this change:
16:58:30  StringFallbackSuite:
16:58:30  Exception in thread "spark-listener-group-shared" java.lang.VerifyError: Bad type on operand stack
16:58:30  Exception Details:
16:58:30    Location:
16:58:30      com/nvidia/spark/rapids/GpuOverrides$$anon$125.<init>(Lorg/apache/spark/sql/catalyst/expressions/RegExpReplace;Lcom/nvidia/spark/rapids/RapidsConf;Lscala/Option;Lcom/nvidia/spark/rapids/ConfKeysAndIncompat;)V @22: invokespecial
16:58:30    Reason:
16:58:30      Type 'org/apache/spark/sql/catalyst/expressions/RegExpReplace' (current frame, stack[1]) is not assignable to 'org/apache/spark/sql/catalyst/expressions/TernaryExpression'

@andygrove have you updated to the latest on branch-0.3?  The RegExpReplace issue in Spark 3.1 should have been fixed by #1013

build


Can I load same chart twice?

Because when I try to do that, it just loads one instance. I need that to display and create pdf out of it using jsPdf. Or if there is a better way, please guide me. I am fairly new to all this.

You need to use IDs on each graph
and in the c3 config, bindto: "#" + id,

Yes, I know that. Suppose my graph ID is #graph1, can I load like this?

and can it generate two graphs?

No, duplicate IDs are invalid HTML. But, you could turn your config into a constructor function - then you can get two copies.
For example:
function MyGraph (id) {
    this.bindto = id;
    this.data = {
        columns: [
            ['data1', 30, 200, 100, 400, 150, 250],
            ['data2', 50, 20, 10, 40, 15, 25]
        ]
    };
}

var chart = c3.generate(new MyGraph(1));
var chart2 = c3.generate(new MyGraph(2));

The alternative is use a "deep copy" such as:
// Assuming graph1 already exists
var graph2 = {};
jQuery.extend(true, graph2, graph1);
graph2.bindto = "#graph2";

Now you have a clone of the first graph object, rather than a reference, so you can do whatever you like to it.
You can share data between graphs though, it's only the config that should be distinct for each graph.

Does this need to be open still?

Yes, close it. I tried to help but it certainly has been open for way too long, and it's not a bug or issue, just help request!
Stack overflow next time perhaps?

@SamMorrowDrums maybeGoogle Groups might help you aswell

True, but I meant for @simkeyur we should probably close issues like that quickly and as you rightly point out direct them to google group is good shout!

@SamMorrowDrums yes, sorry, I confused you as the issue author :smile:


TxFilter shouldn't be visually shown in app code

My understanding is that TxFilter is in the LDK not the app code. We should have @jkczyz or someone confirm and update the visual.
https://ldk-docs-preview.netlify.app/architecture/

TxFilter is an interface that the user has to provide if they want to provide filtered/non-full blocks, and then they use that to receive information about which transactions they need to watch the chain for.

Yeah, it corresponds to a user-defined implementation of chain::Filter. Hopefully, the following docs make the purpose clear but happy to update if not:
https://docs.rs/lightning/0.0.100/lightning/chain/trait.Filter.html


rejoining_of_upstream_concepts test doesn't ignore exposures and metrics correctly

Describe the bug

It appears fct_rejoining_of_upstream_concepts is trying to filter out exposures and metrics here  but it's filtering using ('exposures', 'metrics') when it looks like parent_resource_type and child_resource_type are actually exposure and metric (non-plural). Because of this, the filter isn't working properly.
Steps to reproduce

We have an exposure in our dbt project and it's failing the rejoining_of_upstream_concepts check and I can see the resource_type is listed as 'exposure' not 'exposures'

Expected results

Exposures and Metrics successfully ignored by the rejoining_of_upstream_concepts test.
Actual results

Exposures and Metrics are not successfully ignored by the rejoining_of_upstream_concepts test.
Screenshots and log output

System information
The contents of your packages.yml file:
packages:

package: dbt-labs/dbt_utils
version: 1.0.0

package: calogica/dbt_expectations
version: [">=0.8.0", "<0.9.0"]

package: dbt-labs/dbt_project_evaluator
version: 0.5.0

package: mjirv/dbt_datamocktool
version: 0.3.5

Which database are you using dbt with?

[ ] postgres
[ ] redshift
[ ] bigquery
[ ] snowflake
[ ] trino/starburst
[x] other (specify: databricks)

The output of dbt --version:
1.6

Additional context

Are you interested in contributing the fix?

Sure

hey @AlexPuletti! would welcome a PR if you're still interested!

happy to!


get an erro when changing the disk size

The message
Cannot save "RemoteException: no parameter matching parameter name 'f' could be found." Disk Settings. Error: "{1}"

What troubleshooting steps did you try?


Another attack to graph-based ML method

Attacking graph-based classification via manipulating the graph structure, CCS'19.

Hi Binghui,
Thanks for mentioning this paper. Currently we are focusing on node-level attack and defense methods. For graph-level, we will develop them later.
However, it seems that your are the author of this paper, so I am wondering if you could help develop the algorithm in this repository. You can create a pull request of your algorithm and we will process it.
Thank you.

Hi Wei,
Thanks for your reply.  I need to clarify that our method is also focusing
on novel-level attack. Currently, our attack is implemented in C++, as it
is designed for very large-scale graph datasets. I will consider rewriting
it in python in the future.
thanks,
Binghui
On Wed, Jun 24, 2020 at 10:41 AM Wei Jin<EMAIL_ADDRESS>wrote:

Closed #24 https://github.com/DSE-MSU/DeepRobust/issues/24.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/DSE-MSU/DeepRobust/issues/24#event-3477849946, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6CTJT27OEOLXECY5J5NWLRYIGDFANCNFSM4OD7WVQQ
.


hyprland/window: Add .hidden CSS class, account for hidden & fullscreen windows

The .solo and .<app_id> classes now account for hidden (aka swallowed) windows, and also fullscreen windows in "fullscreenMode": 1 (where a window is fullscreen but the bar is visible).
Add .hidden CSS class for when a hidden/swallowed window is present on the workspace.

Thanks!
Can you update the man and the Github wiki? 🙏

Thanks! Can you update the man and the Github wiki?

Done


Adds podman-socket helpers to config.go

Adds a helper to the config to get the default podman socket and adds some extra MacOS instructions to the readme.

All looks good to me


Unknown25 is changed

it is now ->   unknown25: '7363665268261373700' (still static)

Maybe a lame question but could you please indicate how to find this out ?
(which tools are best for catching and then decoding the official app requests) ?
I think that besides unknown25 it is also good to know the hash used in DownloadSettings request message (?)

@kermel  https://github.com/rastapasta/pokemon-go-mitm for fields which exist in the current protobuf spec (it's not good at identifying new fields)

Thanks, I will try to run it (seems not just a piece of cake :-) )

@trisk @rastapasta we found unk25. It's the encrypted sha1 hash of the version code

https://github.com/AeonLucid/POGOProtos/pull/208

Closing this issue, it's fixed.


Installation issue, no HDMI output

Need some help to install PIGFX on a RPi Zero 1.3 because I did not succeed and there is not any video output. These are my steps so far:
– using a 16GB fast Sandisk SD card I made only 1 partion (of 1 gb)
– FAT32 formatted
– copied bootcode.bin, kernel.img and start.elf in root of the SD card
– created a config.txt file containing one line: init_uart_clock=3000000
– copied config.txt to the root of the SD card
The Zero is powered with 5.1 volt / 2500 mA and after (re-)booting the Zero LED goes on for only a short time and that is it. Not any video output, with or without USB keyboard connected.
The bootcode.bin and start.elf files were extracted from another (working) Pi-Zero SD card installation. The kernel.img file was downloaded from https://github.com/fbergama/pigfx
Someone knows if I am missing something?

Hello,
Looks like it should work fine. Maybe I'd use a 5V power supply rather than a 5.1V. Ttry with a basic USB->micro USB cable (like the ones for samsung phones pre usb-c) on an USB port from any computer.
Can you check if your PiZEro works ok with a Raspbian (on another SD card)?

Thanks for replying Francis. The Pi Zero 1.3 is okay (I've tested two), the power is okay and powered via PC or powerplugs did not solve.
Below some text about the issue as posted by me on a retro forum.
Regards, Hans.
_I have allocated a 0.9 GB partition on a Kingston SD card and on several fast Sandisk cards,  FAT and FAT32 format as well. The files bootcode.bin, start.elf, kernel.img and config.txt were copied to the root (/) of the prepared SD card. After rebooting the Zero the LED turns on for a short time, sometimes it keeps blinking but there was never any HDMI output. No matter how I setup the HDMI monitor.
To me it seems there are circulating several versions of the four needed files, I have tried many without succes including files from https://github.com/fbergama/pigfx._

If possible, please try this again with the latest version 1.2.0 of PiGFX.

V1.6.2 is working on Pi Zero 1.3.


TypeError: MarkItDown.init() got an unexpected keyword argument 'llm_client'

md = MarkItDown(llm_client=client, llm_model="gpt-4o")

make sure that you are using latest version use git install if possible

Sorry for not adding depreciation warning. See #101

#101 will at least correct this issue. I'll cut a new release ASAP to address this.

Version 0.0.1a3 is out now, with this corrected.


Heavy line under selected tab doesn't update when tab label is changing

🐛 Bug Report
If you change the label of tab, the heavy line underneath the selected tab doesn't update in position or width to accommodate the new label.

🤔 Expected Behavior
The heavy line under the selected tab would always be the same width of selected tab and always the correct position.

😯 Current Behavior
The width and position of the heavy line doesn't change.

💁 Possible Solution

🔦 Context
We have tabs whose labels can dynamically change.

💻 Code Sample
https://codesandbox.io/s/tabs-with-changing-label-w41cc?file=/src/App.js
Change the value in the text field. Notice the width of the heavy line doesn't change. Select the Empire tab. Change the value in the text field some more. Notice the position of the heavy line doesn't change.

🌍 Your Environment

Software
Version(s)

react-spectrum
3.0.0-rc.0 of Tabs

Browser
Chrome

Operating System
Mac

🧢 Your Company/Team
Adobe Experience Platform Data Collection

🕷 Tracking Issue (optional)

Yep, looks like a bug

For now it's enough to add the missing dependency to the the right useEffect by passing through the children to https://github.com/adobe/react-spectrum/blob/main/packages/%40react-spectrum/tabs/src/Tabs.tsx#L290

This is probably related. If there is a font loading issue it seems that the tabs don't update where there should be a resize. See this story where the component loads, font loading is delayed, and once the font loads and is applied to the page, the selected tab indicator doesn't line up. https://git.corp.adobe.com/pages/taborski/rsp-storybook/?path=/story/v3-components-tabs--font-change

I would like to take a look at this.


⚠ Mobitopup has degraded performance

In 448868f, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 5390 ms

Resolved: Mobitopup performance has improved in 2994a0f.


test: add profile tests

Add a basic test for changing to a new password and checking if the
password length is between 16 and 64 characters long.

thx 3521f6b200b37d52f43a16346d5dcd88c0c30148


Material-Ui grid will not disappear when xs={0} it just defaults to 1. How can I get certain grids to "disappear" on smaller screen sizes?

--------------^ Click "Preview" for a nicer view!
We primarily use GitHub as an issue tracker; for usage and support questions, please check out these resources below. Thanks!

Read the documentation: https://material-ui.com/.
Ask questions on StackOverflow using the tag material-ui: https://stackoverflow.com/questions/tagged/material-ui.
Chat with the community on Gitter: https://gitter.im/mui-org/material-ui.
Ping us on Twitter: https://twitter.com/MaterialUI.

@DevoKit You have a demo in the documentation. You can use the Hidden helper component for that.


admin should be able to disconnect credit card

The disconnect button uses the authenticated user in the URL, not the user being viewed.
https://github.com/gratipay/gratipay.com/blob/1931/js/gratipay/routes.js#L39

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29206306-admin-should-be-able-to-disconnect-credit-card?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

ref.: https://gratipay.freshdesk.com/helpdesk/tickets/3641

Workaround:
$ heroku run python
>>> from gratipay import wireup
>>> env = wireup.env()
>>> wireup.db(env)
>>> wireup.billing(env)
>>> from gratipay.models.participant import Participant
>>> from gratipay.models.exchange_route import ExchangeRoute
>>> p = Participant.from_username('foo')
>>> route = ExchangeRoute.from_address(p, 'braintree-cc', 'deadbeef')
>>> route.invalidate()

deadbeef?

deadbeef is a metasyntactic variable like "foo," used for hex code-ish strings.

Duplicate of https://github.com/gratipay/gratipay.com/issues/3548.


[Doc][NFC] Fix typo in readme content

Fix "Composable Kernel" name typo

@ypapadop-amd thanks for pointing this issue out. For some reason I cannot find your user ID when trying to add you as reviewer.

The change is too simple and should be included in one of the other PRs :)


Adding HTML-CSS Automations

@xTrilton this has the same issue as the TODO PR. Please make sure it only includes the relevant changes.


App Logo

I think the logo the app is using right now is pretty simple and ugly to be honest. Can someone with good skills in graphic design, design a logo for animity. Use your imagination and I will make a poll so we can choose the best logo for the app!

Anime play app

Bro there are templates in canva @kl3jvi They are pretty good.

I really dont know anything abt how to design a logo
So googling everything I found canva which had this abstract template check it...looks something like this

It just represents A

A plain "A" would look boring. If anyone can draw something simple by paper and pencil I could try to illustrate it. I'm not good at drawing things myself. As an idea, maybe a cat or something cute using the letter α? Or maybe something less related? Like a slime?

I like the second one. Can we chat in private so we can do a nice logo?

@LvClFER can you recreate this logo as an svg?

I like the second one. Can we chat in private so we can do a nice logo?

sure

@LvClFER can you recreate this logo as an svg?

i can try

email me<EMAIL_ADDRESS>

https://github.com/saikou-app/saikou/releases/download/1.0.10/Saikou.<IP_ADDRESS>_fixed.apk


Need to extend the messaging interface

Want to support a more diverse collection of messages that can be shared

Want to standardize on a "language" for the messages.  Will likely use JSON with a formalized schema which can be used to validate the integrity of the messages that each participant receives.

@atheurer I believe there was a particular feature (ie. "message") that you wanted, can you document that here?  I can't recall the specifics.

At the moment I can only remember one use case:  When a participant sends an abort signal, it may be useful to send an additional, more detailed message about the reason for the abort.

Another possibility:  when we start running client/server benchmarks in environments where the IP used by the client is not known before the test, we will need some way to communicate this info between servers and clients.  Actually I am not even sure if the servers will know this information.  It may come from the endpoint(s).  Regardless of where it comes from, we will probably need a method for a participant to provide a message or messages to specific other participants.

When you do a client/server benchmark (ie. uperf) run with rickshaw and it uses roadblock, does the client server pairs know each other's IDs that are being used for roadblock?
I'm wondering if a roadblock member broadcasts a message to all roadblock participants and says something like this is my information (in this case IP addresses) and this is my ID, would a client/server be able to know which message came from their matching client/server?

When you do a client/server benchmark (ie. uperf) run with rickshaw and it uses roadblock, does the client server pair know each other's IDs that are being used for roadblock?

Yes.  There is a env var, CS_LABEL which is [client|server]-

I'm wondering if a roadblock member broadcasts a message to all roadblock participants and says something like this is my information (in this case IP addresses) and this is my ID, would a client/server be able to know which message came from their matching client/server?

As long as all members can send a unique message and it reaches all other members, that should work.

Ok, before I start working on this part we need to merge this: https://github.com/perftool-incubator/roadblock/pull/13
Be sure to read the last comment because you will likely need to make some small changes to rickshaw.

OK, I am testing https://github.com/perftool-incubator/roadblock/pull/13 and making necessary changes to rickshaw.  I have to update a few things as I was parsing stdout to catch some of the exit status, but I think you have fixed the exit codes, should I should not need to do that anymore.

Hmm, that is interesting as I don't really recall specifically doing anything with the exit codes other than making sure I kept the same behavior for abort.  What exactly do you think I fixed?

At one point I think the roadblock leader would not exit with the right code if it was a time out or abort, I forget which.  I think it had to do with the parent not looking at the exit code of the forked child and exiting with that code.

When you do a client/server benchmark (ie. uperf) run with rickshaw and it uses roadblock, does the client server pair know each other's IDs that are being used for roadblock?

Yes.  There is a env var, CS_LABEL which is [client|server]-

I'm wondering if a roadblock member broadcasts a message to all roadblock participants and says something like this is my information (in this case IP addresses) and this is my ID, would a client/server be able to know which message came from their matching client/server?

As long as all members can send a unique message and it reaches all other members, that should work.


Cleanup deprecated usage and warnings

This PR cleans up deprecated component access in tests and fixes other warnings thrown during testing.

:ghost:

🤖


Update openapi.parser.ts

Support inline enum types. Checks property and if enum sets type = 'string'

:tada: This PR is included in version 3.0.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


User Testing

@AhrasAli and I took the mock trade show on March 3rd to gather user feedback. Everything is documented on this wiki page.


how to bind uploadFailed event from server response

I'm getting troubles to bind the uploadFailed event if errors occurs during file processing in the server.
This JSON response binds the fileuploadfail blueimp-jquery-fileupload event:
statusCode: 400
responseText: 'error' => 'Ooh no, an error occurs'

But doesn't bind the uploadFailed event of this plugin.
What's the expected JSON server response to bind uploadFailed code?

Looking at code, I don't think we're showing upload errors right now. Feel free to add it here: https://github.com/orthes/medium-editor-insert-plugin/blob/master/src/js/images.js#L200


provide predefined list of data formats using internet media types

Describe the improvement
Currently, when entering a data format manually, any free text is accepted. I would like to choose from a predefined list of formats. In addition, I want to be able to add a data format that is not available in the predefined list.
predefined list of formats: media types https://www.iana.org/assignments/media-types/media-types.xhtml

@sdebodt media types have a very strict syntax (e.g. image/jpeg and not jpg or jpeg). Sounds a bit too error prone, not?

The internet media type list would mainly be there to select from based on autocomplete in the file type field. The syntax is indeed a bit complicated, but users would not have to type it themselves. This list is far from complete so I expect that only in case of csv, txt, jpg and other common file types it will be used. In other cases, free text needs to be accepted to allow for file types which are e.g. specific to a certain research discipline.
Nevertheless, if you are aware of alternative, controlled lists of file types, there is no reason to stick to the internet media types.

The dropdown menu to select a file format appears when typing something in the text box for the first data format. However, when adding a second data format, the dropdown menu does not appear.

For this issue, the bug mentioned in the previous comment needs to be fixed.
In addition to choosing from the dropdown menu, users need to be able to add a data format as free text.
Can this free text input be checked for being lowercase and having no punctuation marks?

To dos for v2 release:

As for licenses for datasets, have 1 text box to enter value through select from autocomplete or free text. In the background, save each option as a different field.
Treat old license info as free text.

Future work:

Old license info could be curated later on, either automatically if 1-on-1 mapping is possible or manually, in case of datasets.
Other predefined lists of data formats might be used. Investigate which ones are valuable.
Ideally, a label of the data format is shown instead of the actual ID. To check how this can be implemented.


[QUERY] EventHubConsumerClient thread safety

Library name and version
Azure.Messaging.EventHubs.Consumer
Query/Question
Is EventHubConsumerClient thread-safe?
Does each thread need its own client?
Currently we use a single consumer which is being called by multiple threads. The documentation here https://learn.microsoft.com/en-us/dotnet/api/azure.messaging.eventhubs.consumer.eventhubconsumerclient?view=azure-dotnet does not really mention anything about this so I’d like to confirm.
Environment
No response

Hi @dddat1017.  Thank you for reaching out.  Thread safety for the Event Hubs client library is discussed in the Overview and applies to each of the Event Hubs client types, including the consumer.   It states:

Thread safety
We guarantee that all client instance methods are thread-safe and independent of each other (guideline). This ensures that the recommendation of reusing client instances is always safe, even across threads.
The data model types, such as EventData and EventDataBatch are not thread-safe.  They should not be shared across threads nor used concurrently with client methods.

The same guidance applies to types across the current generation of Azure SDK packages, as discussed in Thread safety and client lifetime management for Azure SDK objects.   Further discussion and examples can be found in Lifetime management for Azure SDK .NET clients
.
I'm going to mark this as addressed, but please feel free to unresolve if you'd like to continue the discussion.

/unresolve
Thank you for the prompt response! I did have one more question if you don't mind.
I can see here https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-quotas#basic-vs-standard-vs-premium-vs-dedicated-tiers that the limit on "number of brokered connections per namespace" for standard tier is 5000. Does this roughly translate to "the amount of calls to read or send events at any point in time is capped at 5000"? I'm asking because I'd like to understand what is a good number of threads I should allocate to call the consumer client to read from the event hub. Thanks again!


MaxMessageBytes config works only if set in both Kafka and Sarama

Versions
Sarama Version: f21e149e5948e9c9b9034f1a19f430d62e00c4d3
Kafka Version: 2.0.0
Go Version: 1.10
Configuration
Producer.MaxMessageBytes = 20000000
Problem Description
I'm playing with http server from examples directory, trying to send file contents(about 20MB) to kafka producer. It seems, that I need to set both message.max.bytes param in config for Kafka server and Producer.MaxMessageBytes in config for SyncProducer. If i'm setting only one, i'm getting error: kafka server: Message was too large, server rejected it to avoid allocation error.. Is that expected behavior?

Yeah, we also faced same issue recently and that's what it was about. Reading suggest that it is an expected behavior.