Theory behind this project?

Hello, is it possible for us to have the theory that makes this project work and possibly a way to detect vulnerable servers?
Trying to implement a similar project in Python.

The Big Bang Theory is the leading explanation for how the universe began. Simply put, it says the universe as we know it started with an infinitely hot and dense single point that inflated and stretched — first at unimaginable speeds, and then at a more measurable rate — over the next 13.8 billion years to the still-expanding cosmos that we know today.
Existing technology doesn't yet allow astronomers to literally peer back at the universe's birth, much of what we understand about the Big Bang comes from mathematical formulas and models. Astronomers can, however, see the "echo" of the expansion through a phenomenon known as the cosmic microwave background.
While the majority of the astronomical community accepts the theory, there are some theorists who have alternative explanations besides the Big Bang — such as eternal inflation or an oscillating universe.
Around 13.7 billion years ago, everything in the entire universe was condensed in an infinitesimally small singularity, a point of infinite denseness and heat.
Suddenly, an explosive expansion began, ballooning our universe outwards faster than the speed of light. This was a period of cosmic inflation that lasted mere fractions of a second — about 10^-32 of a second, according to physicist Alan Guth’s 1980 theory that changed the way we think about the Big Bang forever.
When cosmic inflation came to a sudden and still-mysterious end, the more classic descriptions of the Big Bang took hold. A flood of matter and radiation, known as “reheating,” began populating our universe with the stuff we know today: particles, atoms, the stuff that would become stars and galaxies and so on.
This all happened within just the first second after the universe began, when the temperature of everything was still insanely hot, at about 10 billion degrees Fahrenheit (5.5 billion Celsius), according to NASA(opens in new tab). The cosmos now contained a vast array of fundamental particles such as neutrons, electrons and protons — the raw materials that would become the building blocks for everything that exists today.
This early "soup" would have been impossible to actually see because it couldn't hold visible light. "The free electrons would have caused light (photons) to scatter the way sunlight scatters from the water droplets in clouds," NASA stated. Over time, however, these free electrons met up with nuclei and created neutral atoms, or atoms with equal positive and negative electric charges.
This allowed light to finally shine through, about 380,000 years after the Big Bang.
Sometimes called the "afterglow" of the Big Bang, this light is more properly known as the cosmic microwave background (CMB). It was first predicted by Ralph Alpher and other scientists in 1948 but was found only by accident almost 20 years later.
This accidental discovery happened when Arno Penzias and Robert Wilson, both of Bell Telephone Laboratories in New Jersey, were building a radio receiver in 1965 and picked up higher-than-expected temperatures, according to NASA(opens in new tab). At first, they thought the anomaly was due to pigeons trying to roost inside the antenna and their waste, but they cleaned up the mess and killed the pigeons(opens in new tab) and the anomaly persisted.
Simultaneously, a Princeton University team led by Robert Dicke was trying to find evidence of the CMB and realized that Penzias and Wilson had stumbled upon it with their strange observations. The two groups each published papers in the Astrophysical Journal in 1965.
Because we can't see it directly, scientists have been trying to figure out how to "see" the Big Bang through other measures. In one case, cosmologists are pressing rewind(opens in new tab) to reach the first instant after the Big Bang by simulating 4,000 versions of the current universe on a massive supercomputer.
"We are trying to do something like guessing a baby photo of our universe from the latest picture," study leader Masato Shirasaki, a cosmologist at the National Astronomical Observatory of Japan (NAOJ), wrote in an email to Live Science.
With what is known about the universe today, the researchers on this 2021 study compared their understanding of how gravitational forces interacted in the primordial universe with their thousands of computer-modeled universes. If they could predict the starting conditions of their virtual universes, they hoped to be able to accurately predict what our own universe may have looked like back at the beginning.
Other researchers have chosen different paths to interrogate our universe's beginnings.
In a 2020 study, researchers did so by investigating the split between matter and antimatter. In the study, not yet peer-reviewed, they proposed that the imbalance in the amount of matter and antimatter in the universe is related to the universe's vast quantities of dark matter, an unknown substance that exerts influence over gravity and yet doesn't interact with light. They suggested that in the crucial moments immediately after the Big Bang, the universe may have been pushed to make more matter than its inverse, antimatter, which then could have led to the formation of dark matter(opens in new tab).
The CMB has been observed by many researchers now and with many spacecraft missions. One of the most famous space-faring missions to do so was NASA's Cosmic Background Explorer (COBE) satellite, which mapped the sky in the 1990s.
Several other missions have followed in COBE's footsteps, such as the BOOMERanG experiment (Balloon Observations of Millimetric Extragalactic Radiation and Geophysics), NASA's Wilkinson Microwave Anisotropy Probe (WMAP) and the European Space Agency's Planck satellite.
Planck's observations, first released in 2013, mapped the CMB in unprecedented detail and revealed that the universe was older than previously thought: 13.82 billion years old, rather than 13.7 billion years old. The research observatory's mission is ongoing and new maps of the CMB are released periodically.


Modal Dialog

Images load at 1000px wide however the css for .modal-dialog is set to a max-width of 500px at the min-width:576px. Updating this to 50% would make the images ideal for non-mobile devices.

This issue appears like it belong on the frontend repo: https://github.com/bitclout/frontend

Thank you. Submitted.


Exception Details: 3070000 wasm_exception: WASM Exception

2018-10-09T03:27:36.492 thread-0   http_plugin.cpp:473           handle_exception     ] FC Exception encountered while processing chain.push_transaction
2018-10-09T03:27:36.492 thread-0   http_plugin.cpp:474           handle_exception     ] Exception Details: 3070000 wasm_exception: WASM Exception
env._ZNKSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEE7compareEjjPKcj unresolveable
    {"module":"env","export":"_ZNKSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEE7compareEjjPKcj"}
    thread-0  wasm_interface.hpp:42 resolve

    {"mod_name":"env","export_name":"_ZNKSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEE7compareEjjPKcj"}
    thread-0  wasm_interface.hpp:44 resolve
pending console output:
    {"console":""}
    thread-0  apply_context.cpp:61 exec_one

Looks like it is related to the smart contract compiler. Can you provide the minimum of your smart contract code that can result in this error?

We haven't received any follow up from this.

If you still have the problem and wish to discuss further, please post it in https://eosio.stackexchange.com. To keep things organized, Github issues are intended for bugs reporting and features tracking, and Stack Exchange is the right place for any technical support discussions. Thanks!


b582afd3 Fixing implementation_coverage script

95a82671
Updating implementation coverage

Coverage increased (+0.01%) to 93.575% when pulling 95a82671a8ede780321376d52cbb347b24ab9d04 on JackDanger:jackdanger/update-implementation-coverage-2019-10-22 into 4d0099499faf54b940f807781c7e821ea69b8f70 on spulec:master.


Wait should emit some output

Add a spinner so that during long runs its easy for users to know that
process is still running. It should also update the intermediate state
of execution for sonobouy run and delete command.
Fixes #607
Signed-off-by: ekj1711<EMAIL_ADDRESS>Which issue(s) this PR fixes

Fixes #607

Thanks @ekj1711 ! I'll take a look as soon as I can. FYI tests are failing because the build can't find the vendored code; we save the vendored code in the repo as well so you'll need to run dep ensure and commit the new vendor code too.

Thanks @johnSchnake
I have committed the vendor package also along with the changes.

Thanks @johnSchnake for the review comments.

ping; are you still planning to fix this up and get it merged?

ping; are you still planning to fix this up and get it merged?

Yes, sorry for delay. I will update new patch in next 2 days.

Codecov Report

Merging #622 into master will decrease coverage by 0.1%.
The diff coverage is 26.66%.

@@            Coverage Diff             @@
##           master     #622      +/-   ##
==========================================
- Coverage   42.79%   42.69%   -0.11%
==========================================
  Files          71       72       +1
  Lines        4229     4258      +29
==========================================
+ Hits         1810     1818       +8
- Misses       2311     2332      +21
  Partials      108      108

Impacted Files
Coverage Δ

cmd/sonobuoy/app/common.go
0% <0%> (ø)
:arrow_up:

cmd/sonobuoy/app/run.go
27.77% <10%> (-3.34%)
:arrow_down:

cmd/sonobuoy/app/args.go
89.37% <100%> (+0.34%)
:arrow_up:

cmd/sonobuoy/app/wait.go
11.11% <11.11%> (ø)

cmd/sonobuoy/app/delete.go
37.14% <50%> (+0.77%)
: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 700ac79...3ef16ca. Read the comment docs.

Based on my quick look it seems good; some nits but nothing I'll block it on.
I'll try and build/run it manually tomorrow just to double check things but otherwise I think this is a great start to try this feature out. Once we get some sort of status capability, this may be really useful to have, and, as the original problem scope stated, it already solves the problem of leaving a terminal hanging in CI (which can cause fatal errors)

Builds and runs great! Thanks @ekj1711 !


feat(ci): fix ruff-generated errata

PR Checklist

[x] Have you followed the guidelines in CONTRIBUTING.rst?
[x] Have you got 100% test coverage on new code?
[ ] Have you updated the prose documentation?
[ ] Have you updated the reference documentation?

There is one lingering issue
https://github.com/JacobCoffee/starlite/blob/13de06e968b1f388d3139e6311a942018d63f73c/starlite/_openapi/responses.py#L186-L189
starlite/_openapi/responses.py:186:9: SIM108 Use ternary operator `schema = Schema(oneOf=exceptions_schemas) if len(exceptions_schemas) > 1 else exceptions_schemas[0]` instead of `if`-`else`-block
Found 1 error.

I tried schema = Schema(oneOf=exceptions_schemas) if len(exceptions_schemas) > 1 else exceptions_schemas[0]  but then mypy/pyright gets mad and i am not sure how to proceed.
I am more than certain that some things maybe should be undone and added to an ignore (❓) but I am not familiar enough to know what.

This is failing in quite a few places... we may need to revert some things I put into TYPE_CHECKING blocks and add it to ruff ignore


Ethan: Blacklist<PHONE_NUMBER>(?#IS NorAm)

Ethan requests the blacklist of the number<PHONE_NUMBER>(?#IS NorAm). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Makyen in Charcoal HQ


OPCT-242: support mirrored images for features introduced in v0.5.x

Supporting disconnected for new collectors.

must-gather-monitoring added in https://github.com/redhat-openshift-ecosystem/provider-certification-plugins/pull/45
etcdfio added in https://github.com/redhat-openshift-ecosystem/provider-certification-plugins/pull/46
Don't break for any collectors
CLI change is added in the PR https://github.com/redhat-openshift-ecosystem/provider-certification-tool/pull/83

@rvanderp3 would you mind to take a look?
/assign @rvanderp3

Hey @rvanderp3 @faermanj , please take a look?
/assign @rvanderp3 @faermanj

/lgtm
/approve


ISPN-7503 Resolve expressions in the endpoint subsystem

https://issues.jboss.org/browse/ISPN-7503

@ryanemerson I have removed the unused imports.

look good. pushing...

integrated! thanks @tristantarrant


Stacked line chart does not auto-adjust y-axis minimum value

Hi thanks for this amazing tool, I tried to induce it into my line chart though i found out i cant have my y-axis auto-adjusted. it will set the y axis to start from zero as i import the plugging
i don't know if it's because the following setting( stacked: true) somehow disables the auto-adjusting function. how could i have my y-axis back to auto-adjusted mode?
// Core options
scales: {
y: {
stacked: true
}
}

Repro: https://codepen.io/kurkle/pen/XWMWQer

Probably due to || stacked in https://github.com/chartjs/Chart.js/blob/master/src/scales/scale.linearbase.js#L165 but unsure if removing that breaks anything

The expectation for stacked min value was changed here: https://github.com/chartjs/Chart.js/pull/1963
It looks like the expectation is to start a bar chart from zero. This is handled today by having beginAtZero default to true for bar charts, so I think we can quite safely enable this use case too. I'll create a PR and leave the decision to @etimberg :)


Running tasks after response

Describe the feature
I have an endpoint I don't want the user to wait while I talk to third party apis that isn't critical to the response So such logic could be run after the response has been sent.
For example:
// ~/server/api/form.post.ts
import { object, string } from 'yup';
import runAfterResponse from "~/server/utils/runAfterResponse";

export default defineEventHandler(async event => {
    const body = await readValidatedBody(event, body => {
        const bodySchema = object({
            email: string().required().email()
        });

        return bodySchema.validateSync(body);
    });

    const sendEmail = async () => {
        await ...logic;
    };

    // user doesn't really needs to wait for these...
    runAfterResponse(event, async () => ...talkToS3);
    runAfterResponse(event, sendEmail);

    return {
        success: true
    };
});

Then the runAfterResponse looks like this:
// ~/server/utils/runAfterResponse.ts
import type { H3Event } from 'h3';
import getRequestFingerprint from '~/server/utils/getRequestFingerprint';

type Callback = () => void | Promise<void>;
export type CallbackDictionary = Record<string, Callback[]>;

// I'm certain this is less then optimal in large applications but good for mvp
export const currentDict: CallbackDictionary = {};

export default function runAfterResponse(event: H3Event, fn: Callback): void {
    const fingerprint = getRequestFingerprint(event)!;

    if (!(fingerprint in currentDict)) {
        currentDict[fingerprint] = [] as Callback[];
    }

    currentDict[fingerprint].push(fn);
}

getRequestFingerprint in turn looks like:
// ~/server/utils/getRequestFingerprint.ts
import type { H3Event } from 'h3';
import crypto from 'crypto';

export default function getRequestFingerprint(event: H3Event): string {
    return crypto.createHash('sha1')
        .update(`${getRequestIP(event)}-${event.method}-${getRequestURL(event).toString()}`)
        .digest('hex');
}

(the getRequestFingerprint could be a Pull Request on its own...
And lastly I have a nitro plugin that will process these callbacks
// ~/server/plugins/runAfterResponse.ts
import getRequestFingerprint from '~/server/utils/getRequestFingerprint';
import { currentDict } from '~/server/utils/runAfterResponse';

export default defineNitroPlugin((nitroApp) => {
    nitroApp.hooks.hook('afterResponse', async (event) => {
        const fingerprint = getRequestFingerprint(event)!;

        for (const fn of currentDict[fingerprint]) {
            await fn();
        }

        // eslint-disable-next-line @typescript-eslint/no-dynamic-delete
        delete currentDict[fingerprint];

        return;
    });
});

Let me know your thoughts, concerns, etc.
I have tested this and it works as expected with with the order of execution console.log(new Date().getSeconds(), {count})
Additional information

[X] Would you be willing to help implement this feature?

Hi. I think what you are looking for is event.waitUntil(() => {} it works universally (and makes cloudflare worker to be alive until tasks are being done and response sent)

If I'm not mistaken it looks like you are implementing a very basic queue pattern ? I would love if we could support queues as a first class citizen (similar to laravel); in the meantime there's this cloudflare hook based approach we've been tinkering with https://github.com/unjs/nitro/pull/1579/files

waitUntil does in fact do what I want.
I get that it's called waitUntil because the server will wait until all these functions are finished, but this makes most sense from the library developer's perspective. For me, it would read better if it was called something like afterResponse. My heart isn't set on it I just think that the naming should make most sense from the perspective of a request<->response cycle.
I'm not seeing where these waitUntil promises are resolved? Where do I find that? I'm interested in seeing if they are resolved after each other or with Promise.all. Also, is this called when the request is done for the user or when the server closes? (I don't know enough, but maybe the server won't close if there's another ongoing request?)
I'm not too familiar with Cloudflare, but I'm definitely not thinking of queues in the sense that there is a worker process that handles jobs. I'm thinking staying within the request lifecycle.

Can the waitUntil be updated so it can take regular functions too? Maybe some people want to do some more heavy computation that is in sync but user doesn't have to wait for.

Thanks for the feedbacks. The initial API was designed following up cloudflare workers. They expect you to give the util a promise that is already running in parallel to the request.
I think we can as well allow passing functions to waitUntil and internally call them in after response hook (in app.ts). This seems an ergonomic feature 👍🏼

what are your thoughts on the getRequestFingerprint and the renaming of waitUntil? Will other providers be supported that aren't Cloudflare workers?

You might want to choose using onAfterResponse hook with h3 object syntax (https://unjs.io/blog/2023-08-15-h3-towards-the-edge-of-the-web#object-syntax-event-handlers) as well or make a similar util leveraging global onafterresponse hook.
Since we already introduced (platform agnostic) waitUntil, deprecating or introducing a second similar util might be confusing. Sometimes it is actually more useful to run tasks in parallel. But also makes sense to support differed jobs.
Re getRequestFingerprint, i think it could be a nice potential for h3 utils more. We can build it with uncrypto util to make sure remains platform agnostic (feel free to open an issue there).


Updated: 4k-video-downloader <IP_ADDRESS>42

Newer version of 4k-video-downloader (<IP_ADDRESS>12) is now available in master.


New branches have been added to VMR pipeline

There are two new branches under 'release' folder that have been added to VMR pipelilne:
New branch release/9.0.1xx: release/9.0.1xx (internal Microsoft link)
New branch release/9.0.1xx-rc1: release/9.0.1xx-rc1 (internal Microsoft link)
Do we need to add 'release/9.0.1xx' and 'release/9.0.1xx-rc1' to License Scan Test Pipeline and SDK Diff Test Pipeline?

Based on https://github.com/dotnet/sdk/pull/42784#discussion_r1721790415, is this a necessary issue to solve? We say in the yml that we only want to run the tests on internal branches when possible because that's where dependencies flow.

Since there will be an internal/release/9.0.1xx-rc1 build,  no changes are necessary.


Can't input Chinese

Can't input Chinese in every inputfield

This isn't something I can easily fix right now, but it can be done in the future.


add options to specify library

This PR actually does two things:

Add options for user to specify the library and library path when some op is translated into call to external library.
Add an option to control the ConvOptPass. Some user may want to keep the ConvOp with the similar reason that ConvOp is kept for accelerator. By default, the ConvOptPass will be invoked for CPU (unchanged).

Jenkins Linux s390x Build #12266 [push] add options to specify l... started at 21:00

Jenkins Linux ppc64le Build #11259 [push] add options to specify l... started at 21:07

Jenkins Linux amd64 Build #12253 [push] add options to specify l... passed after 1 hr 5 min

Jenkins Linux s390x Build #12266 [push] add options to specify l... passed after 1 hr 28 min

Jenkins Linux ppc64le Build #11259 [push] add options to specify l... passed after 1 hr 50 min


Refactored classes name manipulation using classnames library.

(will merge after Travis build passes)

Coverage remained the same at 45.07% when pulling ebc9aa0f22fb8bd54425df2ede830af371b7ea01 on gcedo:master into 67fe87973c00d21f2bf119a29788e26ef8aadc09 on buildo:master.

Oh, there was a subtle bug in the implementation. See e279085a1b0d2a223ecfbe735e5d345b724918fd
Tests were passing because they were running against the (unchanged) built library.
This will be fixed as soon as I put the new karma-based test suite in place (which tests against the source as opposed to the build)


Add support for Scenes and renamed inputs

This pull request contains 2 changes:  API to set scenes (self explanatory), and API to get an array of input objects with their friendly names.
When you call getAvailableInputs, the Yamaha receiver (or at least mine) will return a list of renamed inputs.  For example my HDMI1 was renamed AppleTV.  When calling setInputTo it seemed to expect the original name of the input, HDMI1 in this case, and rejected the renamed input of AppleTV.
This exposes the link between original input names and the renamed names

Thanks! published with 0.9.5

No problems.  My Yamaha-nodejs pull request has not yet been merged so anyone wishing to use this currently would need to manually install that branch

Whoops, I commented on the wrong pull request


上传图书时报错无法导入lxml.etree.ParserError: Document is empty

Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/flask/app.py", line 2073, in wsgi_app
response = self.full_dispatch_request()
File "/usr/lib/python3.9/site-packages/flask/app.py", line 1518, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/usr/lib/python3.9/site-packages/flask/app.py", line 1516, in full_dispatch_request
rv = self.dispatch_request()
File "/usr/lib/python3.9/site-packages/flask/app.py", line 1502, in dispatch_request
return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
File "/usr/local/calibre-web/app/cps/usermanagement.py", line 35, in decorated_view
return login_required(func)(*args, **kwargs)
File "/usr/lib/python3.9/site-packages/flask_login/utils.py", line 272, in decorated_view
return func(*args, **kwargs)
File "/usr/local/calibre-web/app/cps/editbooks.py", line 59, in inner
return f(*args, **kwargs)
File "/usr/local/calibre-web/app/cps/editbooks.py", line 1087, in upload
modify_date |= edit_book_comments(Markup(meta.description).unescape(), db_book)
File "/usr/local/calibre-web/app/cps/editbooks.py", line 469, in edit_book_comments
comments = clean_html(comments)
File "src/lxml/html/clean.py", line 562, in lxml.html.clean.Cleaner.clean_html
File "/usr/lib/python3.9/site-packages/lxml/html/init.py", line 875, in fromstring
doc = document_fromstring(html, parser=parser, base_url=base_url, **kw)
File "/usr/lib/python3.9/site-packages/lxml/html/init.py", line 763, in document_fromstring
raise etree.ParserError(
lxml.etree.ParserError: Document is empty
上传的图书：链接:https://pan.baidu.com/s/1kzpbWUCtbvscfOlTl3Kn1w?pwd=nyyz 提取码:nyyz

用window版的calibre可以识别，，重新转换成epub格式后再导入就正常

你可以试下自动添加书籍：
-v /自动添加文件夹:/autoaddbooks


Angular Bindings not being updated on successful upload.

I'm pretty sure this is not a bug on ng-file-upload, but I wanted to share this here in case anyone run into the same issue or knows what might be going on.
http://stackoverflow.com/questions/32075605/why-is-my-angularjs-binding-not-always-updating-properly
Thanks in advance!
PS: Should I post the actual question or the SO link is fine?

Closing this since it is already on SO.


Fix JSExpr compat for Knockout.jl

JSExpr v1 was yanked (because reasons) but yanking doesn't exist for Julia 1.0.
This should fix the compat so that only versions [0.0, 1.0) can be installed (please make sure that's what the bound is actually doing - I'm not 💯 percent certain).

Editing the compressed registry files like this can often break things.
Why not just register a new release of Knockout.jl with the appropriate company entry?

My understanding is that this is essentially what RetroCap would have done, just limited to Knockout in particular.
I can definitely just release a patch of Knockout.jl with the appropriate compat, but I'm not certain that would truly solve all of the issues. I'm not sure how the compat solver resolves between candidates where upgrading one package will downgrade another and vice versa; e.g., if Knockout v0.2.0 depends on JSExpr unbounded and Knockout v0.2.1 depends on JSExpr v0.5, what will Pkg do (especially in Julia 1.0 since that's where the issue lies)?
As always, advice is appreciated. :^) I wish we weren't in this situation but a lot of this code was written before the Julia community had really started to take compatibility seriously (and also before I knew what kinds of hell can emerge).

Alright let’s give it a try. If it breaks things, we can revert.

Installing Knockout on Julia 1.0 installs the correct version of JSExpr, so that's a good sign! Thank you so much for being so patient throughout all of this. If you ever end up in Ann Arbor, I owe you a coffee/tea (or six).


Ref is always called twice on the DropTargetConnector element (null, then the element)

Example code:
@DropTarget(dragTypes, target, connect => ({
  connectDropTarget: connect.dropTarget(),
}))
export default class TestComponent extends PureComponent {
  constructor(props) {
    super(props)

    this.setContainerRef = (ref) => {
      console.log("setting container ref", ref)
      this.container = ref
    }
  }

  render() {
    const { connectDropTarget } = this.props

    return connectDropTarget(
      <div ref={this.setContainerRef} />
    )
  }
}

Whenever the component is re-rendered, setContainerRef is called twice:
setting container ref, null
setting container ref, <div ... >

I just realized that this is explained in the DropTargetConnector docs:

Internally it works by attaching a callback ref to the React element you give it.

I'm assuming that it wraps the existing ref I passed, and returns a new function each time.
I know refs are ugly, but in this case I really need to calculate the scrollTop of that div
in a different component. My code is breaking because ref gets set to null during the state change, so I can't calculate the scroll.
It would be awesome if connectDropTarget could do some memoization for the ref callback (like what I'm doing in the constructor.) That would solve my issue.
(As a workaround, I know that the element is never going to be null, so I'll just ignore null for now.)

You can do it yourself, as connectDropTarget is really just a ref callback.
this.setContainerRef = (ref) => {
  console.log("setting container ref", ref)
  this.container = ref
  this.props.connectDropTarget(ref);
}

Oh that's a great point, thanks!
On 21 Oct 2017, 12:27 AM +0700, Alex Guerra<EMAIL_ADDRESS>wrote:

You can do it yourself, as connectDropTarget is really just a ref callback.
this.setContainerRef = (ref) => {
console.log("setting container ref", ref)
this.container = ref
this.props.connectDropTarget(ref);
}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


More updates for new DbKi=R8Ki behavior

A few more changes for DbKi = R8Ki behavior, especially on Windows:

change DBLE to REAL(*,R8Ki) to avoid possible issues when default double is specified as other than 8 bytes
remove QuKi from rest of the Sys*.f90 routines
make default double 64 instead of 128 bits in VS project files' DP configurations
consistent variable types in DCM_expR and DCM_SetLogMapForInterpRand other routines in NWTC_Num.f90

Thanks for submitting this, I should have done more checking for the other compilers and environments.


refactor(iroh-net): Keep connection name, remove connection count

Description
These are two cleanups in the relay client:

The relay::Client hands out a connection object when asked to
connect.  This Conn was imported with rename to RelayClient
which was a bit confusing as this was already the relay client.  It
is now renamed to RelayConn which makes a lot more sense.  The
related builder struct etc are renamed to match.

The relay::Client had a counter for the number of connections made
to the relay.  That seems fun, but was entirely unused.  If this is
a useful thing to have it should probably be a counter metric
instead but let's not add anything that no one is using.  Removing
this makes a lot of APIs a bit simpler and removes some state
tracking.

Breaking Changes
None hopefully, please let this all  be internal APIs.
Notes & open questions

Change checklist

[x] Self-review.
[x] Documentation updates following the style guide, if relevant.
[x] Tests if relevant.
[ ] All breaking changes documented.

LGTM!
Don't want to get nitpicky so do as you wish: There are still many variables named client when doing relay_conn.method() like take, as_ref etc. I find it understandable enough to leave it like that, just slightly cleaner to change it

Your nitpicking is totally right, might as well try and do this more consistent because it does make it more readable.  But yeah, I was moving on as I wanted to get to the actual bugfix I was aiming for at the end of this chain of PRs.
PTAL


[RFR] Use arrow keys to play

Add the lib curses to the project so we can play the game using the arrow keys.
Had to remove all the inputs. Add the option to quit and restart the game.
Trello task 1
Trello task 2

Cruelly lacking unit tests. Try to unit test each of the methods / functions you create.


[Accessibility] A11y_.Net Editor: A user is unable to fold the code in the editor using keyboard

Environment Details
https://docs.microsoft.com/en-us/dotnet/csharp/quick-starts/hello-world?tutorial-step=4User
Browser: Edge (41.16299.402.0)
Chrome (67.0.3396.87)
Additional Details:
MAS Violated: MAS2.1.1
Repro steps:
Hit the URL https://docs.microsoft.com/en-us/dotnet/csharp/quick-starts/hello-world?tutorial-step=4User
Tab till “Enter focus mode” and press enter
Write a Sample program
Now press F1 and tab till Fold and press enter
Verify Fold action is getting performed or not.
Actual Result:
A user is unable to fold the code in the editor using keyboard
Expected Result:
A user should be able to fold the code using either shortcut or navigating to Fold in command Palette
User Impact:
A disabled user wouldn't be able to avail the functionality.
MAS Reference:
https://microsoft.sharepoint.com/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={8492c4eb-c179-40ae-8777-cd044ed725a2}
A User is unable to fold the code in the editor.pptx

Opened an issue an issue with monaco-editor

Update
Issue has been flagged and assigned in the Monaco repo
https://github.com/Microsoft/monaco-editor/issues/1168

Importance of experience
A user should be able to fold the code using either shortcut or navigating to Fold in command Palette

Quality of Experience (High or Low Impact). Describe user impact and workarounds.

Link to AAT entry where issue has been documented in conformance documentation

Any alternate solutions or technologies evaluated

Ensure all evidence for hand-off to external team is provided in the bug


bug(iOS): crash on document create when out of space on free tier

Repro on v0.8.3:

on free tier, added some screenshots and hit limit
out of space with unsynced changes (wasn't clear to me that I hit the limit, although I would have noticied eventually if I tried to hit the sync button)
crashed on creating a new document in a nested folder (no local/unsynced edits were lost during crash 👍 )
crash dump: Lockbook-2023-11-11-181341.ips.zip

I crashed again even though I am on the paid tier now, so might not be related to space
paid tier crash dump Lockbook-2023-11-11-205834.ips.zip

Fixed on iOS and app update! ❤


[chip-tool] Move WebSocketServer code to src/app/tests/suites/server …

…so it can be reused
Problem
This PR just moves chip-tool web socket server code to a place where other apps can used it.

src/app is taken as part of Matter core SDK in coverage statistic, if WebSocketServer is only reused by example apps, why not move to some place under examples, such as examples/common?

src/app/tests/suites/ has since a long time be a place where code related to the test harness lives. If that is really an issue I believe I can moved it to examples/common...

src/app is taken as part of Matter core SDK in coverage statistic, if WebSocketServer is only reused by example apps, why not move to some place under examples, such as examples/common?

src/app/tests/suites/ has since a long time be a place where code related to the test harness lives. If that is really an issue I believe I can moved it to examples/common...

Currently, WebSocketServer is under 'examples/chip-tool/commands/interactive', so I think this is not used only for the testing.
The idea is we want to set a clear boundary between the example code and core SDK code, we conducts daily coverage statistic for Matter Core SDK for our internal reference, we don't count the code coverage in the examples now, so it is better to keep all example code outside of core SDK directories.

src/app is taken as part of Matter core SDK in coverage statistic, if WebSocketServer is only reused by example apps, why not move to some place under examples, such as examples/common?

src/app/tests/suites/ has since a long time be a place where code related to the test harness lives. If that is really an issue I believe I can moved it to examples/common...

Currently, WebSocketServer is under 'examples/chip-tool/commands/interactive', so I think this is not used only for the testing.
The idea is we want to set a clear boundary between the example code and core SDK code, we conducts daily coverage statistic for Matter Core SDK for our internal reference, we don't count the code coverage in the examples now, so it is better to keep all example code outside of core SDK directories.

I have moved the component in examples/common...


[beast] Move out of this repo

move beast out of this repo and into website repo: https://github.com/datacommonsorg/website/tree/master/static/js/import_wizard

What is the new link to the wizard tool?
The Infosys team (datcom-india-extended@) is using this one, and it might be worth letting them know the new URL.

The new link is https://autopush.datacommons.org/import/


xor_keystream(): Use unsafe, and process one byte at a time.

Oh boy, I feel silly.  This is portable and faster (for larger writes), because it skips all the bounds checking in the loop (the asserts ensure that nothing bad happens).
After playing with a bunch of different variants:

I messed up taking performance numbers in my initial pull request,
so the numbers I quoted are off (I was getting chacha/salsa 20
confused I think).
At least on my desktop, minimizing the codesize/branches in
xor_keystream appears to give the best results, leading to this,
which also happens to be the most portable.

The 64k chacha performance goes from 326 MiB/s to 363 MiB/s.  The 10
byte case got slightly slower (232 -> 208 MiB/s), but I think the
tradeoff is worth it.
It's worth noting that all of the ARM targets currently supported by
rustc are ARMv6+, so unaligned access will work if that's an approach
people want to try but this is getting to the point where there's
better ways to optimize the code (generate more keystream at once, do
the xor as the keystream is generated, etc).

I played around with trying to use usizes or u32s to do the XORs if the buffers are properly aligned, but that seemed to only hurt performance, at least for the small-ish buffers that all of the current algorithms use.
Thanks!


make/docker-compose.tpl: fix wrong mount configuration(#5208)

details can refer to #5208

Pull Request Test Coverage Report for Build 7554

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 64.603%

Files with Coverage Reduction
New Missed Lines
%

src/common/scheduler/policy/alternate_policy.go
3
80.29%

Totals

Change from base Build 7546:
-0.01%

Covered Lines:
11082

Relevant Lines:
17154

💛  - Coveralls

@kulong0105
Thanks a lot for your contributions. Hope you can continuously participate in harbor community and do more contributions.
You can subscribe our dev mail list to get more info<EMAIL_ADDRESS><EMAIL_ADDRESS>To unsubscribe from this group and stop receiving emails from it, send an email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit https://groups.google.com/d/msgid/harbor-dev/DC20AAAF-C647-47D3-AC5C-F59D0948B0F6%40vmware.com.
For more options, visit https://groups.google.com/d/optout.


Update README and LICENSE

Nice, this is new Readme looks really good!
Do you think we should add some screenshots of our web app and mobile app?


Very difficult to click on mobile

It's very difficult to click on mobile/touch devices; it seems like you have to not move your finger at all while it's in contact with the screen.
Sigma.js version: 2.40 - 3.0.0alpha3 (since https://github.com/jacomyal/sigma.js/commit/2135a8eb3b1b26cb6129fa24aa53fa561e5b6c5e)
Graphology version: 0.25.4
Operating system: Android 13, One UI 5.1 (Galaxy S21 5G)
Web browser: Chrome 117.0.5938.60
Steps to reproduce

Visit https://codesandbox.io/s/sigma-click-demo-244fhq?file=/index.ts on mobile
Try to tap on any node, which should start an animation to center the camera on it

Expected behaviour

If the touch time is short enough (or if the movement is minimal?) it should still count as a click

Actual behaviour

Clicks don't register if you make the slightest movement before lifting your finger

still relevant :P


1M Limit clarification for direct query

Following document says the 1M limit is configurable for direct query,
https://docs.microsoft.com/en-us/power-bi/admin/service-admin-premium-workloads#max-intermediate-row-set-count
while this document says it's not possible, what's the difference?

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

ID: 1ed1625f-12a2-5962-2959-696188711efe
Version Independent ID: d8796367-6bd1-c63c-db86-59eb5a66c213
Content: Using DirectQuery in Power BI - Power BI
Content Source: powerbi-docs/connect-data/desktop-directquery-about.md
Service: powerbi
Sub-service: powerbi-desktop
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment, @mganeshphani.
I've assigned this issue to the doc author for review.
In the meantime, you might find an answer in the Power BI Community.

Good point - the difference is that it can exceed 1m only in Premium capacities. I've added a clarification and a link - thanks!


Compare helm chart with SMM repository

Compare helm chart with SMM repository and if they are not identical, make it identical to the smm repository.

addressed


writing about 31M of data to a file crashes the app

Keep writing data to a file (in an isolated but tried it with async with the same result). It is reproducible: it crashes every time. Please find a simple test app that demonstrates the problem. Just run it and click the Start button.
Below is the output of "flutter doctor":
./flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, v1.1.8, on Linux, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Android Studio (version 3.3)
[✓] Connected device (1 available)
• No issues found!
There is nothing special in the log: it only says "application finished":
...
I/flutter ( 5028): 31689728 (<=== these are the byte counts output by my test app)
I/flutter ( 5028): 31690752
I/flutter ( 5028): 31691776
I/flutter ( 5028): 31692800
I/flutter ( 5028): 31693824
Application finished.
There is no exception.

file_writing_crash.zip

@freemant2000
Can you run flutter run -v and paste the crash related log here?

I guess only the last portion of the log is useful:
...
[        ] I/flutter ( 6017): 31798272 (<== my byte counts)
[        ] I/flutter ( 6017): 31799296
[        ] I/flutter ( 6017): 31800320
[  +78 ms] Service protocol connection closed.
[        ] Lost connection to device.
[   +1 ms] DevFS: Deleting filesystem on the device
(file:///data/user/0/com.example.filewritingcrash/cache/file_writing_crashDFCSKQ
/file_writing_crash/)
[        ] Sending to VM service: _deleteDevFS({fsName: file_writing_crash})
[ +252 ms] TimeoutException after 0:00:00.250000: Future not completed
[   +9 ms] "flutter run" took 57,608ms.

it seems to be issue of future

Have you tried with a different device or emulator?

Does it behave differently with a smaller file?

In the attached app, the IOSink is buffering all the data until flush is called.  Eventually the Android out-of-memory killer shuts down the process.
The app could call flush more frequently during the loop.  But this will work more efficiently with the RandomAccessFile API:
    RandomAccessFile f = await File("$app_data_directory/test_file").open(mode: FileMode.write);
    var n = 0;
    Uint8List bs = Uint8List(1024);
    for (int i = 0; i < 100000; i++) {
      await f.writeFrom(bs);
      n += bs.length;
      print(n);
    }
    await f.close();


How to handle new page from "target=_blank" event?

I don't know the keyword to use. In pure Python I could use with context.expect_page(), but it seems no keyword like this already existed..
How could I make it happen in robot-browser?

Here is a brief explanation on how to handle the new page in a "target=_blank" event:
Understanding "target=_blank"
When an HTML link has the attribute "target=_blank", clicking on it will open the linked page in a new browser tab or window. This is commonly used to direct users to external resources or other relevant pages while keeping the original page accessible.
Handling in JavaScript (Common Approach)
1. Using the window.open Event and Managing the New Window/Tab
<!DOCTYPE html>

    <meta charset="UTF-8">
    <title>Target Blank Handling</title>

    Click me

Explanation:

The window.open function is called when the link is clicked (through the onclick event handler). It creates the new window or tab.
We can then customize the new window's properties like its size (resizeTo) and position (moveTo).
Also, we can attach event listeners to the new window. In the example, we listen for the load event to know when the new page has fully loaded. Note that returning false in the onclick event handler prevents the default behavior of the link from immediately opening the page, allowing us to manage it first.

2. Security and Cross-Origin Considerations
When working with the new window created by window.open, if the new page is from a different origin (domain, protocol, or port), there are security restrictions due to the browser's same-origin policy. For example, you won't be able to directly access the DOM elements of the new page from the original page's JavaScript code if they are from different origins.
To communicate between pages from different origins in a limited way, you can use techniques like the postMessage API. The originating page can send a message like this:
newWindow.postMessage('Some data', 'https://example.com');

And the receiving page (in the new window) can listen for the message:
window.addEventListener('postMessage', function (event) {
    if (event.origin === 'https://your-origin.com') {
        console.log('Received message:', event.data);
    }
});

Handling in Other Programming Languages (Server-Side)
If you want to handle the new page from a server-side perspective (for example, in a web application using Python with a framework like Flask or Django), you can track the clicks on links with "target=_blank" and perform actions such as logging, analytics, or even modifying the page content that is about to be served in the new window based on certain conditions. However, the specific implementation would depend on the server-side framework and its capabilities.
In summary, handling the new page in a "target=_blank" event mainly involves using JavaScript to manage the new window/tab properties and dealing with cross-origin communication if necessary, while on the server side, it can be about tracking and potentially influencing the page content in the new window based on application requirements.

I don’t quite understand your question but ‘Switch Page    NEW` should work. If it doesn’t, then could you explain what else you have tried and what errors you get and what actually happened?


Need to change the API Structure

As this app was made in the march, that time this api was in different structure. Now it's in some different structure.
Use API of covid19india

@jayskhatri Hello ! I wish to work on this issue. Would you please assign it to me?

@VarunT11 Sure!


More DRCs in Caravel

This issue notes two DRC errors flagged in the Caravel design:
(1) NDMY spacing error (in the caravel logo)
(2) Metal slotting stress rule error (in the simple_por MiM cap).
Resolution for (1):  Removing the layer 111:5 (COMP fill block) from being generated where "fillblock" is used in magic.  Normally, "fillblock" should only indicate that metal fill shapes should not be generated.  All text blocks were regenerated with only the metal fill block, not the COMP fill block.
Resolution for (2): This is a very obscure error, but the current belief is that there is a requirement that the top metal layer must completely cover the cap plate.  This is not an explicit DRC rule in the MiM cap rule section, but appears to be implicitly enforced by an obscure implementation of a slot rule.  Metal 5 was expanded to include the entire area of the MiM cap plate.
Both issues have been fixed by PR #114

Additional file---update to the simple_por GDS---added by PR #118


try out nextjs 13 app dir again

this time more luck, still investigating

and blockly upgrade to 10

stay with blockly 9, because 10 has a regression in the flyout (huch?)
Got the app directory up and running


link to something from camelus notifications on GitHub tests

Pull requests to opam-repository show up with info like the screen shot below. It would be helpful to get more info somehow. For example, travis tests provide a link pointing to a log of what was run. If nothing else, at least point to this repo and update the README of this repo to provide more information about what is checked.

Indeed, thanks for pointing this out!


Build multi-platform images

This PR updates the build workflows to make sure the images will be built in the linux/amd64 version, used on x86 machines, and the linux/arm64 one, used by ARM processors (e.g. Apple Silicon).

This PR was opened and closed to leave a "paper trail" of the change.
The actions to build the images will only fire on pushes to the main and major.minor.patch branches.


feat: add PCI Blueprint

Description

Adds PCI Blueprint

Testing required outside of automated testing?

[ ] Not Applicable

Screenshots (if appropriate):

[ ] Not Applicable

Rollback / Rollforward Procedure

[ ] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

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


Fix typo

What?
Minor typo fix.

CC @hamchapman

          1 Warning

:warning:
Any changes to library code should be reflected in the Changelog. Please consider adding a note there. \nYou can find it at CHANGELOG.md.

SwiftLint found issues
Warnings

File
Line
Reason

ChatManager.swift
103
TODOs should be avoided (This could be nicer).

ChatManager.swift
104
TODOs should be avoided (We don't need to wait for init...).

ChatManager.swift
105
TODOs should be avoided (Do we need to nil out subscrip...).

ChatManager.swift
118
TODOs should be avoided (This is madness).

ChatManager.swift
203
TODOs should be avoided (This being here at the end see...).

ChatManager.swift
207
TODOs should be avoided (Maybe we need some sort of Cha...).

ChatManager.swift
247
TODOs should be avoided (When can percent encoding fail...).

ChatManager.swift
86
Function body should span 40 lines or less excluding comments and whitespace: currently spans 72 lines

ChatManager.swift
107
Variable name should be between 3 and 40 characters long: 'cu'

ChatManager.swift
166
Line should be 120 characters or less: currently 130 characters

ChatManager.swift
185
Line should be 120 characters or less: currently 138 characters

ChatManager.swift
189
Line should be 120 characters or less: currently 129 characters

ChatManager.swift
193
Line should be 120 characters or less: currently 138 characters

PCCurrentUser.swift
23
TODOs should be avoided (This should probably be [PCUse...).

PCCurrentUser.swift
391
TODOs should be avoided (Use the soon-to-be-created new...).

PCCurrentUser.swift
481
TODOs should be avoided (Do we need to fetch users in t...).

PCCurrentUser.swift
684
TODOs should be avoided (Do we need a Last-Event-ID opt...).

PCCurrentUser.swift
791
TODOs should be avoided (What happens if you provide bo...).

PCCurrentUser.swift
813
TODOs should be avoided (This should probably be a room...).

PCCurrentUser.swift
1103
TODOs should be avoided (What to do with an error? Just...).

PCCurrentUser.swift
1053
Unused parameter "data" in a closure should be replaced with _.

PCCurrentUser.swift
711
Function body should span 40 lines or less excluding comments and whitespace: currently spans 42 lines

PCCurrentUser.swift
914
Function body should span 40 lines or less excluding comments and whitespace: currently spans 55 lines

PCCurrentUser.swift
207
MARK comment should be in valid format. e.g. '// MARK: ...' or '// MARK: - ...'

PCCurrentUser.swift
266
MARK comment should be in valid format. e.g. '// MARK: ...' or '// MARK: - ...'

PCCurrentUser.swift
631
Arguments can be omitted when matching enums with associated types if they are not used.

PCCurrentUser.swift
631
Arguments can be omitted when matching enums with associated types if they are not used.

PCCurrentUser.swift
5
Variable name should be between 3 and 40 characters long: 'id'

PCCurrentUser.swift
66
Variable name should be between 3 and 40 characters long: 'id'

PCCurrentUser.swift
177
Variable name should be between 3 and 40 characters long: 'id'

PCCurrentUser.swift
194
Variable name should be between 3 and 40 characters long: 'id'

PCCurrentUser.swift
228
Variable name should be between 3 and 40 characters long: 'id'

PCCurrentUser.swift
283
Variable name should be between 3 and 40 characters long: 'id'

PCCurrentUser.swift
343
Variable name should be between 3 and 40 characters long: 'id'

PCCurrentUser.swift
1130
Enum element name should be between 3 and 40 characters long: 'messageIDKeyMissingInMessageCreationResponse'

PCCurrentUser.swift
121
Collection literals should not have trailing commas.

PCCurrentUser.swift
655
Opening braces should be preceded by a single space and on the same line as the declaration.

PCCurrentUser.swift
198
Line should be 120 characters or less: currently 122 characters

PCCurrentUser.swift
216
Line should be 120 characters or less: currently 144 characters

PCCurrentUser.swift
228
Line should be 120 characters or less: currently 140 characters

PCCurrentUser.swift
232
Line should be 120 characters or less: currently 137 characters

PCCurrentUser.swift
512
Line should be 120 characters or less: currently 123 characters

PCCurrentUser.swift
540
Line should be 120 characters or less: currently 121 characters

PCCurrentUser.swift
565
Line should be 120 characters or less: currently 139 characters

PCCurrentUser.swift
569
Line should be 120 characters or less: currently 139 characters

PCCurrentUser.swift
591
Line should be 120 characters or less: currently 133 characters

PCCurrentUser.swift
602
Line should be 120 characters or less: currently 132 characters

PCCurrentUser.swift
696
Line should be 120 characters or less: currently 123 characters

PCCurrentUser.swift
952
Line should be 120 characters or less: currently 123 characters

PCCurrentUser.swift
1058
Line should be 120 characters or less: currently 136 characters

Errors

File
Line
Reason

PCCurrentUser.swift
4
Type body should span 200 lines or less excluding comments and whitespace: currently spans 685 lines

PCCurrentUser.swift
693
Variable name should be between 3 and 40 characters long: 'r'

PCCurrentUser.swift
1149
File should contain 400 lines or less: currently contains 1149

  Generated by :no_entry_sign: Danger

Nice 👍


changing shopping cart icons for library icons

For the time being I've just updated the visual names and icons, perhaps we should also consider changing the methods and file names

I agree with you. I will create an issue for that.
Thanks for the suggestion!

Besides the comment above, could you please change the text "No items in the cart" to "No items in the stash" in file src/app/modules/shopping-cart/components/shopping-cart/shopping-cart.component.html?

Stash

No items in the cart

I forgot to include this name in the issue description.


change field and table name

do you plan to add annotation to change field name and table name ?
it's good for ProGuard

Sure. I will consider this function in the future release. And for the proguard part, I just updated the document. You can check it for more details.


Several errors on Thermos Server 1.7.10

Hey,
I get several errors with Gringotts. We're using Thermos (a current Cauldron fork) for 1.7.10, Vault 1.6.6 and Gringotts 2.9.
Please take a look at the loading error:
http://pastebin.com/085DjcVV
Strange: Vault detects Gringotts as active.
And the error for the /money command:
http://pastebin.com/Ayt5C1iC

It looks like Thermos might not contain the Ebean library, which Gringotts uses as default database backend. If that is the case, Gringotts might unfortunately be incompatible.

As far as I can see, ebean should be included:
https://github.com/CyberdyneCC/Thermos/blob/master/build.gradle
Any chance to correct this or load this library externally?
Gringotts is a must-have plugin for us!

Do you think you can fix that?

I'm afraid I don't really have the time these days. I'm happy to help out if you want to work on a fix.

Hey @TomberWolf,
The Thermos has really different API than Bukkit and I really don't have the time to make Gringotts works with it.


Profile pop-up issues after recent update

Since discord has added a new "about me" section it dramatically increased the width of the usercard page, and also created this strange effect that goes into the user's roles.

the same thing is happening to me, not sure how to fix it ;;


Failed Test

This is from TestQuality

Created by TestQuality - Linked to TestQuality.com defect D2. Do not remove or edit. D2


sha1

In the example you say that sha1 is included in the digest node
But when i install it i cannot find the sha1 only the sha3
is this correct?
thanks
Rogier

Ask the original developer in
https://github.com/baumblatt/node-red-contrib-crypto-js
This repo is only a copy of that for personal testing purposes with no maintenance.
Sorry.


Debug install_openstack_ca molecule failure

As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

recheck

/approve
@cescgina I updated the PR title and description to match the actual commit information.

/approve
@cescgina I updated the PR title and description to match the actual commit information.

thanks!

/lgtm


Page navigation shows me the end of the next page

Steps to reproduce:

Go to the homepage
Click "OLDER ARTICLES" to navigate to the second page
Note that you're now looking at the end of Page 2 (unless you didn't have images cached, in which case you're looking at somewhere near the end but not quite at the end of Page 2.

Debated whether or not to report this, since it could be useful on occasion for quickly paging as the page navigation links remain visible (unless there are uncached images that load after the page scrolls). But this seems like an odd use-case.

Yeah I had noticed this too and had a similar debate. I think there's going to be other ways of navigating quickly to other posts if you're looking quickly though, so I'm implementing a $(window).scrollTop(0) with page changes with https://github.com/StackExchange/blog/commit/6e25fc24314b900326a0ee3ce79fe98c0728129a


Get Nancy compiling on dotnet54/dnxcore50

Proposal
As part of the latest microsoft movement, it would be nice to get nancy working on the new dotnet environment.
This was started with pull requests #2211 and #2212 to get things compiling using the project.json project system. Now we need to get some good work done to get this working on dotnet54.
Approach
So far, there has been analysis completed on the nancy package to see what is/isn't available in the latest runtimes, and there are some areas that need replacing.
Due to the amount of work that needs doing, It's been suggested by @thecodejunkie that we try to get the project compiling first, then approach tests later on once we are happy and settled with the replacement code.
Most areas of the code should remain the same for the full CLR, and ifdefs should be used to swap out logic with comparable parts in the new environment.
Why choose dotnet54 and not dnxcore50?
Dotnet54 is intended for use by microsoft by libraries and not the consuming applications, more information can be found here : aspnet/announcements#98
Things that need tackling to get things compiling

[ ] Removal of SerializableAttribute (should be simple, but not sure on repercussions)
[x] RNGCryptoServiceProvider -> RandomNumberGenerator.Create(), (this is currently what the Microsoft Identity packages use.) [in PR #2215]
[ ] BootstrapperException Ctor (SerializationInfo info, StreamingContext context), SerializationInfo isn't available, suitable replacement needed
[ ] DefaultObjectSerializer uses BinaryFormatter, it's not available, suitable replacement needed
[ ] Classes inheriting Stream need to use the suitable overrides, signatures have changed
[ ] Url class implements ICloneable, it's not available, is this an issue?
[ ] Most reflection needs tweaking/replacing. May even be worth a seperate PR?
[ ] CultureInfo caching (ie BuiltInCultureConventions class) needs replacing, suitable replacement needed
[ ] RijndaelEncryptionProvider makes use of RijndaelManaged class, not available. Replace or remove?
[ ] MemoryStream.GetBuffer is not available, suitable replacement needed
[ ] Uri.IsHexDigit/Uri.FromHex() is not available, suitable replacement needed.

Things to note:
@khellang has asked for a list of packages and why we use them so we can try and trim the list of dependencies down, do we need some place to put this? maybe a wiki page in the long run?

@khellang has asked for a list of packages and why we use them so we can try and trim the list of dependencies down, do we need some place to put this? maybe a wiki page in the long run?

This is a good thing to bring up in the description of each of the pull-requests

RNGCryptoServiceProvider -> RandomNumberGenerator.Create()

I don't think there's a need to #ifdef anything here. The RandomNumberGenerator.Create() API is available on both net451 and dotnet5.4

RijndaelEncryptionProvider makes use of RijndaelManaged class, not available.

This can be replaced using the Aes class in the https://www.nuget.org/packages/System.Security.Cryptography.Algorithms package :+1:

CultureInfo caching (ie BuiltInCultureConventions class) needs replacing

What does this mean? Are there any specific APIs that we use, that's not available?

Uri.IsHexDigit/Uri.FromHex() is not available, suitable replacement needed.

Let's just rip the original implementations :smiling_imp: They're trivial. https://github.com/dotnet/corefx/blob/ac67ffac987d0c27236c4a6cf1255c2bcbc7fe7d/src/System.Private.Uri/src/System/Uri.cs#L1364-L1392

MemoryStream.GetBuffer is not available, suitable replacement needed

If we can live with copying the data, let's just use ToArray here. Not sure where it's used.

Most reflection needs tweaking/replacing.

This is mostly just a matter of adding in a .GetTypeInfo() call everywhere :dancers:

Url class implements ICloneable, it's not available, is this an issue?

No, just :fire: it. If it's heavily used, we can keep the method, but :fire: the interface.

Removal of SerializableAttribute
BootstrapperException Ctor (SerializationInfo info, StreamingContext context)

These can easily be #ifdef'ed away, if we really need them, but in general, I think we should try to :fire: them :grin:
Just a couple of ¢ from me :wink:

Agree with most of what @khellang said, few notes:
As I said on the call, CultureInfo caching is the biggest concern I have - we put that in because the performance of doing it non-cached is stupid slow (like drop to 30 requests per second slow).
I cloneable I think we might use, but doing it without the interface is easy enough.
Bootstrapper exception - AFAIK this is the "best practice" way of making exception ctors, pretty sure we don't ever use that ctor so happy to nuke it :)
BinaryFormatter - can replace this with JSON once we have simple json in, although it's going to be a lot slower - surprised there isn't a replacement for this to be honest.
GetBuffer is (IIRC) a lot more efficient than ToArray so this is really going to nail perf when we have a stream switch I think.
The rest of the stream stuff is a reasonable chunk of work to switch over to using all the async methods, but it definitely something we need to do (along with update the response class)

Everything on the checklist is done, are the additional items we should be adding to it or shall we close this issue?

Woo that's awesome.

I guess add whatever the remaining errors are?
On 23 February 2016 at 07:13, Phillip Haydon<EMAIL_ADDRESS>wrote:

Woo that's awesome.
—
Reply to this email directly or view it on GitHub
https://github.com/NancyFx/Nancy/issues/2220#issuecomment-187577716.

pinging @Yantrio

I think if @thecodejunkie is happy that we are compiling we can close this and open more issues if we need to futher down the line.

:+1:

WE DID IT GUYS!
Closed


Enhancement - DOC - Missing added feature

Need to add new feature in the feature list description

Closed by commit #1e079b1


Accordion data option allowAllClosed not working

What should happen?
All the panes in the accordion should be closed by default when using the data-allow-all-closed="true" option according to the doc here : https://foundation.zurb.com/sites/docs/accordion.html#all-closed
What happens instead?
There is still one pane opened.
As you can see, even on the doc : https://foundation.zurb.com/sites/docs/accordion.html#all-closed
Test Case and/or Steps to Reproduce
Test Case: https://foundation.zurb.com/sites/docs/accordion.html#all-closed
Your Environment

Foundation version(s) used: 6.4.3
Browser(s) name and version(s): Firefox Dev Edition 61.0b14 (64 bits) - Chrome Version 67.0.3396.87 (Build officiel) (64 bits)
Operating System and version (desktop or mobile): MacOSX High Sierra

It just means that you can close all. Try removing the is-active class.

See https://codepen.io/DanielRuf/pen/WyXLwZ?editors=1000

I am facepalming right now... Really tired today didn't even noticed that 😔
Thanks ! 🎉

No problem. I'm happy that I could help and that the initial question is solved.
Have a great week!

Have a great week too!


Add support for dependencies to "maybe-existing" targets

Currently the IsDependentOn extension requires that the depentend on task exists. While writing Cake scripts which are shared among different projects it can be usefule to make a task in the shared script dependent on some other task, which serves as extension point for the concrete Cake script using the shared script.

Closing this as a duplicate of #1818


logo for 0.1

New logo for 0.1 (provided by Jerry Koh!)

The ... menu to the right of the binary file has a "view file" option that can be used to view the logo.  It is 256x256.

@EHO-makai , is this still needed since we're past the 0.1?


Document skiplang background story in docs introduction

There is a TODO to fill in the skiplang background story here.

TODO moved from source to here:
brief Skiplang story/history/context: probably best for someone with more first-hand experience than me to write this.

developed at facebook to speed up updates and deliver real-time experience through the back-end
couldn't be achieved in Hack/PHP, so an in-house language was designed and developed specifically for reactive computation.
spun out from open-source into SkipLabs


Cancelling a transcoded Publish doesn't work

Select an mkv file with the "Transcode" checked.
Publish
Cancel the operation (upper-right "x")

I can still see the transcoded file being generated.  Minutes later, I see the Publish (Uploading) modal appear and thing got published.

I don't think there's any way to cancel a publish on the SDK side once it's been submitted. We are working on a big revamp there, so it may be possible later with web sockets. For now, on the UI side we should just disable that option to cancel.

Ah, from the GUI, I was under the impression that we haven't submitted to the servers yet and is still transcoding locally, hence was expecting the Cancel button to kill ffmpeg and skip the submission.


Serenity/JS 3.0 - Standardise shadow DOM-piercing selectors across Web integration tools

The problem
To enable selectors to pierce shadow DOM, Protractor requires a plugin - query-selector-shadow-dom. The plugin provides the below selector, which Serenity/JS uses under the hood:
by.shadowDomCss('#item-in-shadow-dom')

WebdriverIO ships with support for deep selectors, which under the hood also use query-selector-shadow-dom. They provide the following syntax with >>>  prefix:
browser.$('>>> #item-in-shadow-dom')

Note that >>>  is not a standard CSS selector and Playwright is not compatible with it
Playwright, on the other hand, uses shadow DOM-piercing selectors by default and requires developer to explicitly opt-out from this behaviour:
page.locator('#item-in-shadow-dom')             // pierces shadow DOM
page.locator(':light(.article > .header)')      // does not pierce shadow DOM

It seems useful for Serenity/JS to have the behaviour of selectors consistent across the various Web integration tools to enable greater portability.
Our support for shadow DOM currently looks as follows:

Selector
Protractor
WebdriverIO
Playwright

By.css(selector)
✅, but needs a prefix >>> ${selector} and inject query-selector-shadow-dom
✅, but needs a prefix >>> ${selector}
✅ but any >>> breaks the selector

By.cssContainingText(selector, text)
🚫
🚫
✅

By.id(id)
🚫
🚫
🚫

By.tagName(tagName)
🚫
🚫
✅

By.xpath(xpathSelector)
🚫
🚫
🚫

Proposed approach
Since query-selector-shadow-dom has certain important limitations (particularly when it comes to Firefox and Safari support), caused by the limitations of the browsers themselves, making all CSS-based Serenity/JS selector rely on query-selector-shadow-dom to provide shadow DOM piercing capabilities feels like a bad idea.
To make the behaviour of Serenity/JS selectors consistent across Web integration tools, we could instead:

introduce a new selector, e.g. By.deepCss(selector) that:

for Protractor, injects query-selector-shadow-dom and delegates by.shadowDomCss('#item-in-shadow-dom')
for WebdriverIO, prepends selector with >>>
for Playwright, delegates to page.$ without any modifications

make sure that any CSS-based selectors used with Playwright use the "light" engine

This way we'd have:

Selector
Protractor
WebdriverIO
Playwright

By.css(selector)
🚫
🚫
🚫 :light(selector)

By.deepCss(selector)
✅, prefix and inject query-selector-shadow-dom under the hood
✅ prefix under the hood
✅ pass-through

By.cssContainingText(selector, text)
🚫
🚫
🚫 :light(selector)

By.id(id)
🚫
🚫
🚫

By.tagName(tagName)
🚫
🚫
:light(selector)

By.xpath(xpathSelector)
🚫
🚫
🚫

@viper3400 - thoughts?

Released in 3.0.0-rc.20


Jameica crashes when trying to print / render a page

Describe the bug
I use Jameica with the Hibiscus homebanking plugin. When I try to print/render a printable page, jameica crashes with
[Thu Aug 04 16:04:45 CEST 2022][INFO][main][de.willuhn.jameica.hbci.io.VelocityExporter.getIOFormats]   found template: /home/aj/projekte/linuxconfigs/shared/.jameica/plugins/hibiscus/lib/velocity/de.willuhn.jameica.hbci.rmi.Umsatz.html.vm
(Jameica 2.10.2:471465): GLib-GIO-ERROR **: 16:04:58.211: No GSettings schemas are installed on the system
Trace/breakpoint trap (core dumped)
Steps To Reproduce

Start jameica with installed hibiscus plugin
Go to e.g. Menuitem Umsaetze , click export

Expected behavior
It shows a rendered page
Additional context
Workaround:
export GSETTINGS_SCHEMA_DIR=/nix/store/34gizkg2d1p27ym1rfcihxncpdi5vham-gtk+3-3.24.34/share/gsettings-schemas/gtk+3-3.24.34/glib-2.0/schemas
Notify maintainers
@flokli
@r3dl3g
Metadata

system: "x86_64-linux"
host os: Linux 5.18.13, NixOS, 22.05 (Quokka), 22.05.2019.d9536b9b1e3
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.8.1
channels(aj): "nixos-unstable"
channels(root): "home-manager-22.05.tar.gz, nixos-22.05, nixos-hardware, nixos-unstable"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos
Java 15

Hint: "I would guess it needs to use wrapGAppsHook as nativeBuildInputs but I have no idea how/where to add that." ( Taken from https://bytemeta.vip/repo/NixOS/nixpkgs/issues/181500 )

Could you check if it's fixed by #183969 ?

Could you check if it's fixed by #183969 ?

Yup, I checked with jameica in nixos unstable and I am able to print without workaround. Thx.
#closing


"All SQL" no longer available

Selecting All SQL > Hide nothing is no longer available in the version filter.

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

ID: 707f60c5-6dee-8cf3-4f1f-49ad87b9337b
Version Independent ID: 9f4ce234-fe5b-03d0-3dd1-4a2790c09674
Content: SQL Server docs navigation tips - SQL Server
Content Source: docs/sql-server/sql-docs-navigation-guide.md
Product: sql
Technology: release-landing
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

@Yanis77240 -- thank you for catching this.  I am updating the article.

Thank you for your feedback.  I have updated the documentation and it should be live by tomorrow.


Stop and Start the ops-agent separately in the enable script for MSSQL

Description
Nightly builds have had inconsistent MSSQL errors. Noticed in research that AD & IIS integration enable scripts do not call Restart-Service, but instead call Stop & Start service independently. Seeing if this

Current failing windows test appears to be a fluke
err=googleapi: Error 503: We encountered an internal error. Please try again


Package broken due to jQuery deprecation from Atom

It appears that this package is no longer functioning due to changes in Atom 1.16 regarding the removal of jQuery from bundled packages, which the atom-space-pen-views (dependency of this package) relied upon.
It looks like the Atom team have nominated atom-select-list as a replacement for sourcing SelectListView, which previously came from atom-space-pen-views. This new dependency is based on etch.
I'll need to find some time to upgrade components so this package is compatible again.

This should now be resolved with the v0.4.0 release.


LOW: [$500] Android-Thread-In Android, with uneven spacing as text entered, displayed in reply thread title

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
Action Performed:

Go to https://staging.new.expensify.com/
Tap on a chat
Send a message with uneven spacing
Long press the message sent and select Reply in thread
Note the header in mweb
Launch app
Perform step 2-step4
Note the header in Android

Expected Result:
In reply thread page, in both mweb and Android, the title must be shown in a consistent way.
Actual Result:
In reply thread page, in mweb, text title is shown with normal spacing but in Android, with uneven spacing as text entered, it is displayed.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/e465a3ec-f634-4345-bf2e-9bc5cc4db0d5

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01208eb9280d67b191
Upwork Job ID:<PHONE_NUMBER>892351488
Last Price Increase: 2023-12-27

Proposal
Please re-state the problem that we are trying to solve in this issue.
The thread title in header have a different white space behavior between native and mWeb.
What is the root cause of that problem?
On mWeb, we use styles.noWrap and this make several space to one space.
https://github.com/Expensify/App/blob/bbe73efdfab056d5ab6d864941fc3da44ec1c084/src/components/DisplayNames/DisplayNamesWithTooltip.tsx#L50
On native, we don't have that and that doesn't work on native.
https://github.com/Expensify/App/blob/bbe73efdfab056d5ab6d864941fc3da44ec1c084/src/components/DisplayNames/index.native.tsx#L12
What changes do you think we should make in order to solve the problem?
We need add new function for native
const title = String(fullTitle).trim().replace(/\s\s+/g, ' ').trim();

And use title instead of fullTitle
https://github.com/Expensify/App/blob/bbe73efdfab056d5ab6d864941fc3da44ec1c084/src/components/DisplayNames/index.native.tsx#L15
What alternative solutions did you explore? (Optional)

Let's keep this, cross-platform consistency ftw.  Adding to VIP.

@quinthar - Is Daily still the right priority for this one or can we move it to at least weekly since it's low?

Moving this to weekly since it's Low priority. Please feel free to update labels as needed when priority changes.

Reviewing

@strepanier03 Can you clarify what is the expected outcome here.
If text with multiple consequent spaces are enter(hello    world), how we should show it?
a) Collapse spaces - hello world
b) Keep them and display them as it is

Can you clarify what is the expected outcome here.

@alitoshmatov - I'm unsure which of the two behaviors will be the final one we decide to go with when this becomes a priority to work on.
Since right now this is set to LOW, I'd recommend focusing on other higher-priority bugs. @quinthar will update the priority on this bug as the #vip-vsb project progresses and when we're ready to focus on this we can confirm the expected behavior.
If anyone feels differently, feel free to chime in and share the context I'm missing. But it makes sense to me to focus elsewhere until this becomes higher priority or more relevant.

@tienifr - Thank you!

We can proceed with @tienifr proposal and make all platforms consistent by showing all spaces and not collapsing them.
C+ reviewed 🎀 👀 🎀

@bernhardoj Thank you for your proposal. Your proposal is very similar to @tienifr 's and have the same approach

@yh-0218 Thank you for your proposal, we decided to preserve spaces on all platforms.

Waiting for @techievivek's take on @tienifr's proposal

Flopping back to External since automation switched it over and we're waiting for a review of @tienifr's proposal from @techievivek.

Ooops sorry, I missed the ping.

Thanks @techievivek - @tienifr will you submit the draft PR soon?

All good Melvin.

The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/21664
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/21664/files#r1464963197
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/a
Determine if we should create a regression test for this bug. No need

Dang, another one where the automation didn't work to move this over to Daily. I'll work on this now.

All paid up and contracts closed. Thanks everyone!


Apache?


Add keepParentField support

closes #17

Pull Request Test Coverage Report for Build 43

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 99.574%

Totals

Change from base Build 38:
0.01%

Covered Lines:
123

Relevant Lines:
123

💛  - Coveralls

@Mikhus

@Mikhus

sorry for delay, and thank you for contribution. Now this included in v2.2.0


Fix nested render without rendering block

I ran into the same issue as reported in https://github.com/bullet-train-co/nice_partials/issues/98. local_assigns aren't being set on nested renderings when the call to render doesn't supply a block.
I narrowed it down to this line: https://github.com/bullet-train-co/nice_partials/blob/fc66c50c8828bcb374f5f3abd0acb0a43c014085/lib/nice_partials/monkey_patch.rb#L113
capture_with_outer_partial_access isn't being called when there isn't a supplied block.
This change in this PR moves the block guard from within the render_partial_template method to the capture_with_outer_partial_access method.

@chrisgibson thank you very much for the PR! And to @adampal for reporting it originally.
I haven't had as much time for Nice Partials for a while. I'm hoping to do a double check of this PR this week.
Then I'll merge and ship a release. Thanks again!

@chrisgibson thanks again! I played around with the implementation some more and felt like capture_with_outer_partial_access shouldn't be called without a block.
I ended up coming up with an alternative that finally called removed our whole Stack implementation, which I always felt icky about. I tried explaining more thoroughly in the commit, I hope it makes sense!

I was planning on shipping a release for this, but it looks like our CI isn't quite fresh anymore. https://github.com/bullet-train-co/nice_partials/commit/06eae3f84f9ce0d3d7a6623314eb66f26a005916
I'm not sure why or how we're getting Ruby 2.7.8 there.

Just released this, thanks again @chrisgibson and @adampal for reporting! Let me know how it goes https://github.com/bullet-train-co/nice_partials/releases/tag/v0.10.1


Fixes exception when raising error 😜

This fixes exception when raising errors with ruby version > 3 . < 3 untested

This sort of fix for Ruby 3 is necessary also at https://github.com/allmarkedup/lookbook/blob/main/app/helpers/lookbook/component_helper.rb#L13 (splat the hash to keyword args)

Thanks guys - I need to get some better testing set up to catch things like this with different Ruby versions! Much appreciated (and will fix the component helper in a separate commit).


⚠ Bofrost.at has degraded performance

In 4521c71, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1741 ms

Resolved: Bofrost.at performance has improved in 519f286 after 308 days, 8 hours, 52 minutes.


Add support for push notifications

There should be built in libraries for doing push notifications so that everyone won't need to wing their own.

https://github.com/invertase/dart_firebase_apis

https://github.com/google/googleapis.dart/blob/master/generated/googleapis/lib/fcm/v1.dart

As with almost every open source BaaS, PN is the missing peice - Putting in a vote for PN here.

I really need push notifications, and just now realized Serverpod doesn't support them yet...
There's a discussion of tradeoffs of different approaches here:
https://pub.dev/packages/push
But I wonder if Serverpod could skip using Firebase Cloud Messaging entirely, and have its own service in the Flutter client listening to notifications from the Serverpod server...

FCM push notifications can be sent from the server using the Firebase Admin SDK for FCM:
https://firebase.google.com/docs/cloud-messaging/server#firebase-admin-sdk-for-fcm
But to do this without depending upon the Firebase libraries, the FCM REST API can be called directly:
https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages
--
This is only orthogonally related, but may get at deeper push notification issues, so I throw this out here too:
I have been looking at adding push notifications to the chat server, but I have come across two issues:

The Redis pub/sub model only tracks subscriptions for a single server, and there may be different users subscribed to different servers;
The current chat server API requires the user's server code to decide whether a user can join a given chat channel or not. The chat channels that any given userId should be able to join are not stored anywhere that the Serverpod chat module knows anything about. That means that there is no way to know what users are part of a chat channel, but are not currently subscribed to the stream of updates from that channel (which is the situation where a push notification should be sent out). Furthermore, the mapping from channel to users that are part of the channel should persist across server restarts, and REDIS doesn't do that.

So basically, more infrastructure needs to be built in Serverpod to track notification subscriptions, and user liveness.

@lukehutch You can configure the chat module to use Redis by setting postMessagesGlobally to true.
https://github.com/serverpod/serverpod/blob/main/modules/serverpod_chat/serverpod_chat_server/lib/src/business/config.dart
You currently need to keep track of the channels yourself, that is not automatically covered by the chat API.

Right, I have that option set already. However something missing from the current system is a presence-tracking system (who is currently connected via a socket?). If that were in place, I could find the difference between who is supposed to be able to access a channel (in my own code) and who is currently connected (via the presence system), in order to figure out whether to push a message just to the channel, or out via the push notification API.
I may extend the chat server to store the currently-connected users in Redis, so that no matter where they are connected, whether a user is active can be queried from any Redis node. Is that a change you'd want to see incorporated into Serverpod?

@lukehutch, that would be a very cool feature to incorporate! :) Perhaps it should be part of the authentication module over the chat module as it can be very useful outside the chat too. It should definitely be a configurable and opt in though as it may incur costs on Redis and Redis isn't turned on by default.

I have been looking extensively at how to make a single Serverpod server scale to millions of daily active users.
One of the biggest scalability bottlenecks I have run into is that every client that opens a streaming connection uses up a port on the server, and a single IP address can utilize a max of 65536 ports concurrently.
I know that web sockets are very useful, but they don't give you a highly scalable client/server architecture.
I plan to instead use Firebase messaging to push messages from the server to the client, and the regular HTTPS request-based system to send requests from the client to the server. This should scale much better in the long run.
Figured I should mention this here, just to make the point that scalability is a very big reason for Serverpod to support server-origin cloud messaging out of the box.

One of the biggest scalability bottlenecks I have run into is that every client that opens a streaming connection uses up a port on the server, and a single IP address can utilize a max of 65536 ports concurrently.

@lukehutch   Where do you see 1 stream connection = 1 server port used ?

It is my understanding that websockets always use one port per connection.
Actually on a related note, does serverpod-chat multiplex all subscribed chat channels through one websocket connection per connected user?

I currently have no idea how serverpod handles websocket. But in general, websockets are handled through 80 and 443.
I am not an expert on real-time web communication but from my little experience on sysadmin, I've never opened, on a firewall, a range of outgoing ports from websocket servers.

I currently have no idea how serverpod handles websocket. But in general, websockets are handled through 80 and 443.

Soery, you're right, the limit is 64k ports *per client per server port", not per server.
https://stackoverflow.com/a/2332756/3950982
However the real limit appears to be the number of available file descriptors.
The conclusion is still about the same -- from the link: "The realistic limits being boasted about for normal boxes are around 80K for example single threaded Jabber messaging servers."
Presumably this is a CPU limit, but even for multithreaded servers, you wouldn't be able to support more than an order of magnitude more concurrent connections than that.


Fix CMake integration of NMODL generation.

The code for the code-generator NMODL is itself generated from Jinja templates. This requires CMake integration to ensure it happens automatically.
The following has been changed about the integration:

The CMake code needs a list of the generated files. This list is stored in a CMake file and included. This file must exist before running code_generator.py to generate the NMODL code, because the command to generate the files needs to know which file it will be generating. Therefore, we split the script into two phases: one to generate the list of generated files, and another to generate the files.

The list of generated files depends on the build flags. Therefore, this file (code_generator.cmake) can't be checked into the Git repo. The code_generator.cmake is created during the configure phase, and now lives in the build directory.

CMake code was lifted from src/language/CMakeLists.txt to the top-level CMakeLists.txt to avoid any scoping issues for the lists of generated files.

Removed pattern of yielding tasks while creating a list tasks in favour of returning the list of tasks directly.

Second attempt at fixing the issue. The previous was a rather short-lived "solution".


Automatic response for community contributors

Description
This is a Github action that will respond automatically to comments made by community contributors, inviting them to consult our Wiki page.

(praise) Overall good job


Re-exported packages cleanup.

Make sure we're using re-exported packages from near-sdk as opposed to adding those directly to Cargo.toml.
Some good examples of that include serde package in near-contract-standards.

I asked @iho to work in this one

@PolyProgrammist I don't see any other places to be honest. Thanks for checking and fixing the remaining ones


[Throughput] Create CSV to JSON ServiceBus Throughput Test Apps

Add apps to test suite with these instructions.

Closing as complete


Track 'ipinfo'

Vendor site - https://ipinfo.io/
Example site - https://rothys.com/products/the-lightweight-tote-coffee-brown
Category - Geolocation
Detection - track for XHR request to https://ipinfo.io/

Hey @rockeynebhwani , added thanks!!


fixes and enhancements for modal spaces

What changes are proposed in this pull request?
fixes and enhancements for modal spaces
How is this patch tested? If it is not, please explain why.
Using spaces in sample modal
Release Notes
Is this a user-facing change that should be mentioned in the release notes?

[x] No. You can skip the rest of this section.
[ ] Yes. Give a description of this change to be included in the release
notes for FiftyOne users.

(Details in 1-2 sentences. You can just refer to another PR with a description
if this PR is part of a larger change.)
What areas of FiftyOne does this PR affect?

[ ] App: FiftyOne application changes
[ ] Build: Build and test infrastructure changes
[ ] Core: Core fiftyone Python library changes
[ ] Documentation: FiftyOne documentation changes
[ ] Other

Summary by CodeRabbit

New Features

Enhanced modal responsiveness with dynamic height adjustments for improved layout.
Improved sidebar behavior in modal contexts to prevent overflow.
Streamlined handling of modal states for better performance and clarity in the AddPanelButton component.
Added a new icon to the modal sample plugin for improved visual representation.
Enhanced functionality of the Panel component with state management for panel IDs and scopes.
Introduced new hooks for better panel state management, allowing for contextualized control.

Style

Simplified CSS styling for the ActionsRow component, promoting a cleaner design.
Adjusted height specifications for the Arrow component in modal navigation for better adaptability.
Removed conditional styling for StyledElements to ensure consistent layout.

E2E failure is unrelated and will be addressed as follow-up. Merging.


Remove instructions extension for simple-schema

Now that the {{schema}} helper in Element templates allows all schema fields to be accessible, a package-provided extension to simple-schema fields is unnecessary.
Such an idea could be presented in the docs as part of a section on working with simple-schema.
Already, I can see how instructions is insufficient for some uses--for example, where you want to have placeholder text in an input and an example below the input. It's out of this package's scope to solve for all use cases involving these types of additional fields.

Totally agree.

#23

You could do what autoform does and introduce something like a 'forms' field to SimpleSchema. Users could then add whatever fields they need to that. You could provide a pass-through mechanism for parameters, so you don't have to prefix everything with 'forms.'
new SimpleSchema({
name: {
type: String,
label: 'Name',
max: 40
forms: {
placeholder: 'Your name...',
helpText: 'Name is a required field with a maximum length of 40 characters.'
}
}
}

:+1:

@jcheroske, could you please elaborate? Why is it necessary to add a specific field named 'forms'? Why not just add whatever field I want in the schema and use it from templates:forms?
Wouldn't a specific field represent an extra and unnecessary link with SimpleSchema?
What if I use several form packages: would I need to duplicate my properties in several custom fields like 'forms', 'super-forms' and 'extra-forms'?
Suppose I need a new property in my schema, which I want to use both in my forms and my database. Why would I want to store this in a 'forms' field?

Good questions! It's all just about pros and cons I guess. Your criticisms are pretty much spot on, and I think in general you are correct. The issue really boils down to, "Do I want to just add whatever to my core schema, or do I want that info in a sub object?" And also, "Is the info tied to a specific library?" I don't really have much problem with putting placeholder text in the schema, but if there was a bunch of view-related stuff, I think putting it in a 'view' sub-object would make things cleaner. But, like you alluded to, that can be left up to the developer. In autoForm, there were a handful of config options that could be tied to a specific field via an 'autoForm' object in the schema. Maybe Forms doesn't need it now, but going forward it might be something to keep in mind as a possibility. Like, maybe you want to be able to specify the validationEvent on a per-field basis. Being able to say:
new SimpleSchema({
   name: {
      type: String,
      label: 'Name',
      max: 40
      forms: {
         validationEvent: 'keyup'
      }
   }
}

might come in handy. Idk.

The problem with specifying validationEvent this way is that it's something you should specify on an element, since for example one element might respond on keyup and another might respond when you click an add button and then use validationValue to get a combination of a text input and a select box and form the data a certain way.

I know my response is probably taking your example too seriously, but I figured I should mention it anyway :)

See the conversation in #30.

Just had a surprise realising that it is not a blackbox. :+1: for removal.


Not working when using Nvidia Freestyle.

Hello. I use this app with Nvidia Freestyle over my game which is essentially Nvidia's Reshade. The filters I use alter the game's appearance using shaders to change color, contrast and adds bloom etc. When these filters are applied, the app's detection of Paimon's name starts to fail which is understandable in extreme cases, however the detection fails from very slight color changes due to bloom or saturation which would display over the UI. I've had to unfortunately change my Freestyle preset around this in order to keep the app working. Even as I still have it, the app still mutes and unmutes rather frequently and inconsistently when her name appears in dialogue. Is there a way we could adjust the color to detect or change the way Paimon's name is spotted so the app continues to mute in these circumstances? No setting in the current config works unfortunately.

Currently, these values are hardcoded:
https://github.com/tmarenko/GenshinImpact_PaimonShutUp/blob/70ae5df91f507c8f0a13e5c8fe521c064cbba8b1/source/main.cpp#L42-L43
You could fork the repository and compile the app with your own values (I have an automatic workflow for this!).
Moving them to a configuration file is possible, but explaining how to set these values properly is a big concern. For the average user, it would be challenging to explain how to select the low and high color values, especially in BGR format.


STL-2204 create anchor btn and use for share buttons

Short Description

new anchor button component created

Changes

adds a new generic anchor button component to use for  all different cases to get rid of the "wild growth"
use them for share buttons
next step is to exchange all the other anchor buttons

Feedback

something missing?
Hints:
You have to start storybook to see it in action
the one with the icon and text (play, youtube): hover state for icon has to be set in the parent component where it is used, because colors could be different

How to review this Pull Request
Link to Confluence (internal)

Good idea with the generic anchor button! I didn't go through the all css definition but I checked it live and the share buttons do not look like as specified:
* Not the same font. Figma says BundesSansWeb with 700 Bold, but this is the topic with do we use the actual BundesSansWeb Bold oder the regular on with 700 weight?

* Font color should be also white for facebook and whatsapp

* Hovering effect :
  -- Only working with "Link kopieren"
  -- "E-Mail schreiben" does not have any hovering effect at all
  -- Both facebook and whatsapp only change the font color to white when hovering

And also the display of the button on mobile versions do not put every button in one line as specified in figma?

Thx.

we should use BundesSansWebBold
I will check the hovering effects and responsive behaviour

I have talked to UX - the style should be okay this way. Possibly there will come breaking points adjustments later. @VictorDelCampo


⚠ API - Lens has degraded performance

In 0f69100, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 503
Response time: 938 ms

Resolved: API - Lens performance has improved in 1dd18a0 after 9 minutes.


Code clean up

Replace function names m_....
Add comments to the code
Tests: improve test names
Document how to get sample block headers from doge blockchain (libdohj java code written by oscar)

Moving the remaining task to a new issue


release_subdir option

I was deploying two different applications to one machine and I was using releases_to_keep which was deleting old releases. I had been deploying the two apps at the same time regularly so I wasn't having any issues until I deployed only one of the apps a number of times in one day. This resulted in releases_to_keep deleting the current release folder for the other app - oops.
So I figured that the best way to solve this was to add a release_subdir so that app release folders are completely independent. By adding release_subdir: 'myapp' to your options the release folder changes from releases/20150101120000 to  releases/myapp/20150101120000.
Now when I deploy an app, to the same machine as another app that used grunt-ssh-deploy,  the clean up won't affect the other app(s).
I also changed the code to use path.join rather than having to worry about slashes.

+1
Great solution - I was just about to run into the same issue on an upcoming project.


Runtime panic due to Garbage collection

I have used C2go to transpile PCRE C library into Go.
It's available on https://github.com/Jemmic/libpcre
The transpiled tests are also available as Go tests.
Everything works with GC turned off (GOGC=off).
With GC however, there are panics:
runtime: pointer 0xc420171fff to unused region of span idx=0xb8 span.base()=0xc420170000 span.limit=0xc420171fe0 span.state=1
runtime: found in object at *(0xc420047c70+0x30)
object=0xc420047c70 k=0x6210023 s.base()=0xc420044000 s.limit=0x0 s.sizeclass=0 s.elemsize=0 s.state=_MSpanStack
 *(object+0) = 0x6d74c0
 *(object+8) = 0x0
 *(object+16) = 0x0
 *(object+24) = 0x0
 *(object+32) = 0xc420172000
 *(object+40) = 0x0
 *(object+48) = 0xc420171fff <==
fatal error: found bad pointer in Go heap (incorrect use of unsafe or cgo?)

runtime stack:
...

runtime: nelems=512 nfree=510 nalloc=2 previous allocCount=1 nfreed=65535
fatal error: sweep increased allocation count

runtime stack:
...

These panics happen randomly due to the non-deterministic behavior of GC.

As a workaround, it's possible to build & run libpcre with a Golang that's patched with c2go.patch
However, it would be preferable for c2go to directly produce correct code.