HIP 94: Response Time Windows for Witness Rewarding

HIP 94: Response Time Windows for Witness Rewarding

Author(s): @disk91, @jmarcelino
Start Date: 2023-07-20
Category: Economic, Technical
Original HIP PR: #749
Tracking issue: #764
Voting Requirements: veIOT Holders

Summary
Currently the Proof-of-Coverage Oracles reward the 14 first hotspots (defined in default_max_witnesses_per_poc ) reporting a witness. This rewards the fastest hotspots, incentivizing fiber backhauls and specific hardware models that happen to be able to produce fast signatures. The result is that the same hotspots are selected, making others unviable even if they provide unique and useful coverage for the network. In other words, it punishes hotspots for falling short of millisecond optimizations when the LoRaWAN protocol functions to the order of seconds - see also.
A hotspot’s utility in providing LoRaWAN coverage is based on measuring “good enough” response times, not absolute fastest as absolute speeds provides no marginal utility, the Uplink does not have a particular time-window, the downlink time windows is up to 2 seconds, and the Join process up to 6 seconds.
Since HIP-83, changing the way hotspot are selected, we see an acceleration of hotspots not participating to PoC anymore conducting to network size reduction.
This HIP proposes to evolve the hotspot selection by adding a response time window to eliminate only
slow hotspots that fail to meet LoRaWAN-grade timing constraints and push helium hotspots to improve their reponse time, over time, reasonably.
Rendered View
https://github.com/helium/HIP/blob/main/0094-response-time-windows-for-witness-rewarding.md

assuming hip83 is the only reason rewarded hotspots are reducing faster is not correct. the halving also plays a role.
drawing the authors eyes to the big drop in earnings, no reason for a reduction in rewarded hotspots right?

We've also seen with optimisations that earnings have improved, and much needed changes to data transfer to move to a session key base system which are all positive outcomes of Hip83. here I see very little benefit whilst also giving packet stuffers more chance at being rewarded.
Which one are we also voting on, the one listed or the alternative? how does someone vote for the alternative listed? better to focus it on one of the two.

assuming hip83 is the only reason rewarded hotspots are reducing faster is not correct. the halving also plays a role.
drawing the authors eyes to the big drop in earnings, no reason for a reduction in rewarded hotspots right?

We've also seen with optimisations that earnings have improved, and much needed changes to data transfer to move to a session key base system which are all positive outcomes of Hip83. here I see very little benefit whilst also giving packet stuffers more chance at being rewarded.
Which one are we also voting on, the one listed or the alternative? how does someone vote for the alternative listed? better to focus it on one of the two.

The HIP dos not says it's the only reason, it show that there is an acceleration, even if the HIP83 is not related to the decrease, it did not make a change in the current decrease.
The graph with the number of rewarded hotspot within a day does not show the disconnected devices, this metric is important and linked in the HIP but it does not prove that we are in a good situation, it just show a continuous decrease.
I think it's important to look at hotspot disconnection (the one you never see again) to understand when things impacts.
Halving played a role the same way and the combination of the two is having a big impact on the network.
@BFGNeil  you don't need to defend HIP-83, this HIP is not against HIP-83, like any HIP it's  a proposal to make what exists working better to develop the network.
Session key is a good thing, HIP83 helped to accelerated the discovery of it for sure, this will not be impacted by this HIP proposal. Basically with the session key deployment, all the purpose of the HIP-83 is becoming not applicable as the response time for witnessing will become totally uncorrelated with the data response time.
In particular, this improvement conduct to the need for this HIP to consider with the witness time the ability for a hotspot to transfer the data in a correct timing in regard of the LoRaWan network timing constraints.

Feedback from the community to add in the HIP (as a reminder)

the time windows extension for low density area is fixed at 14 hotspots in the 1st proposal and 5 in the second (coherence)

Feedback from the community to add in the HIP (as a reminder)

The witness from the beaconner itself must be ignored as it can be a way of gaming the timing windows

Feedback from the community to add in the HIP (as a reminder)

The witness from the beaconner itself must be ignored as it can be a way of gaming the timing windows

What does this mean? A Hotspot can't witness itself.

What does this mean? A Hotspot can't witness itself.

Well they do, but its ignored for rewards, so I guess that this is for clarity of how many are counted in the timing windows.

Feedback from the community to add in the HIP (as a reminder)

option to scenario with an incentive for some of the fastest hotspot

What does this mean? A Hotspot can't witness itself.

Well they do, but its ignored for rewards, so I guess that this is for clarity of how many are counted in the timing windows.

exactly

Feedback from the community to add in the HIP (as a reminder)

Freedom Fi ECC is 400ms

Feedback from the community to add in the HIP (as a reminder)

Get and add detail on the exact HPR data integration windows

Personal point of view, that may be a really good reason to not give reward to slow hotspot that could impact the uplink data quality & communication costs

Feedback from the community to add in the HIP (as a reminder)

Freedom Fi ECC is 400ms

upside of the hip83 exercise is that we did end up finding that the standard OEM driver was very slow and some optimizations are available to get it within the same ballpark as the ecc signing speed.

assuming hip83 is the only reason rewarded hotspots are reducing faster is not correct. the halving also plays a role.
drawing the authors eyes to the big drop in earnings, no reason for a reduction in rewarded hotspots right?

We've also seen with optimisations that earnings have improved, and much needed changes to data transfer to move to a session key base system which are all positive outcomes of Hip83. here I see very little benefit whilst also giving packet stuffers more chance at being rewarded.
Which one are we also voting on, the one listed or the alternative? how does someone vote for the alternative listed? better to focus it on one of the two.

oh there you are, you installed a trojan horse into Helium network with your scammy Hip 83, and you did so just before the halving, but hey you made sure to mask it so to blame ''halving'' is what reduced earnings, yeah second time you aren't fooling anyone here buddy, we see exacly what your HIP 83 has done, -35k hotspots as i have projected when i said if this scammy hip 83 passes, this will be the result, and all we got is few lazy hotspots with no unique coverage earning everything.

Feedback from the community to add in the HIP (as a reminder)

Freedom Fi ECC is 400ms

upside of the hip83 exercise is that we did end up finding that the standard OEM driver was very slow and some optimizations are available to get it within the same ballpark as the ecc signing speed.

do we have some measurement update we could add in the HIP for the different brands ? and a refresh of the reward distribution per brand ? It would be great to use the last / updated data in the HIP

HIP 94 will be closed in 2 weeks unless the HIP is updated without multiple options and includes the supporting data.

I would opt for an combination of the 2

reward the first 7 witnesses
random select the other 7 from the pool of witnesses within set time limit

Personally I'm in agreement that we should not penalize hardware that is slightly slower so much, as long as it leaves plenty of time for the lorawan timing requirements.
I think the only comment I might make is to make it a weighted selection from the qualifying witnesses. We should strive for the fastest response times both from a QoS perspective but also from a anti-gaming perspective.

Any thoughts on adding weighting @disk91 ?

example 3 needs updating:
Example 3
25 witnesses received:
10 within MAX_WITNESS_WAIT_WINDOWS_MS 200ms
8 within EXTENDED_WITNESS_WAIT_WINDOWS_MS 200-500ms
7 outside EXTENDED_WITNESS_WAIT_WINDOWS_MS 500ms
The first 10 are marked as SELECTED, the next 8 are marked as VALID, the 7 others are marked as INVALID.
Oracle will reward all the SELECTED, then will randomly choose 6 (14-8) of the 8 witnesses marked as VALID and reward them. Assuming default_max_witnesses_per_poc is 14
should be 4 more chosen from valid for a max of 14, 10 were in the max wait.

I am opposed to implementing a weighted selection process that favors the quickest response times. HIP 83 aimed to decrease the concentration of hotspots in dense areas. I believe that all participants providing coverage within a specific time window (like 200 ms), should be rewarded equally, regardless of their equipment (hotspot, internet,...).
I run a hotspot located 10 km away from the next one. I guess that's a low-density area where you want more hotspots? Yet this is the consistent feedback my hotspot receives:
Valid, Not Selected, Arrival Rank: 56 of 73, Late: 84 ms (Fastest hotspot: -10 ms)

I earn 0 for witnessing.
The issue is that my hotspot can only connect with other hotspots in a city (dense area) about 20 km away.
Using a weighted selection that rewards those with quicker response times will only perpetuate the advantage for hotspots in such dense areas, since there'll always be many that respond faster than mine. Consequently, my hotspot, which provides important coverage in a low-density area, will continue to go unrewarded, like it did since HIP 83.


.Net Potential concurrency bugs in FunctionsView Fix

Motivation and Context
FunctionsView appears to be trying to be thread-safe, as its SemanticFunctions and NativeFunctions are both ConcurrentDictionary. However, in that case there are a couple of concurrency bugs lurking.
If multiple threads concurrently try to add a FunctionView for the same skill, they could end up both mutating a List concurrently, which is not safe.
Resolves #604
Description
Applied suggestions.

Using GetOrAdd instead of Contains
Added lock when Adding new Function details to the list (prevent concurrency)
Removed the FunctionView setters
Improved IsSemantic and IsNative logic
Added Concurrency UnitTest

Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

Closing this PR as the FunctionsView class is being removed #2878


use gem env user_gemhome instead of system-wide location

This solves https://github.com/ruby/ruby.wasm/issues/343 by running bundle install in the context of gem env user_gemhome.

Hmm, I don't think specifying GEM_HOME in bin/setup is a standard way: https://github.com/search?type=code&q=path%3Abin%2Fsetup+org%3Aruby
Since there are some ways to make bundle install installable, I think setting tweaking GEM_HOME is out of bin/setup responsibility.

Would it then at least be possible to add a note about it to the CONTRIBUTING page? As said in https://github.com/ruby/ruby.wasm/issues/343, currently this step fails and using sudo doesn't seem to be a solution either.
With this PR, I can follow the CONTRIBUTING;s Install dependencies step successfully, without it the script fails.

As I said, there are several ways to fix and root reasons for bundle install failures. And your change is one of them. You said, sudo solution is not right way, but it could be a right solution for some users. So adding such specific solution in bin/setup is too much, I feel.
Having said that, adding a sentence like "If you face permission error, please consider using user-local Ruby instead of system wide one" is reasonable for me.
Or you will be able to solve the issue by just using the latest Ruby including https://github.com/rubygems/rubygems/pull/5327.

Or you will be able to solve the issue by just using the latest Ruby including rubygems/rubygems#5327.

Fair enough, I'll close this PR, and just wait for my distribution to update to ruby 3.3 once it's out.

can we fix this for the current version of ruby even if its just temporary until 3.3 comes out? I'm also having this issue.

@ralyodio Use of bin/setup is not mandatory. You can just type bundle install and npm ci by yourself.


Cant launch game properly

Whenever I try to install the game, it installs correctly and then I try to launch it. At this point, the loading bar opens and after zipping through some parts, It finally gets blocked on 100% when it comes to the jna-4.5.1.jar.
https://gyazo.com/248846623d1e97c49ca11e23ec616619

Open issue in https://github.com/runelite/launcher, this is wrong repo


Allow user to control fallback reasons on the CLI

See: https://runtimeverification.slack.com/archives/CC360GUTG/p1702579255239909
I would like to be able to tell the Booster to not fallback to the old backend on branches (to confirm the branch), so that pyk can first apply some semantics specific logic which may mean that the branch just doesn't even need to be considered. In particular, when there is a semantic terminal state (not a stuck state), which pyk can identify using semantics-specific information, in KEVM we always get a 5-way branch as the next states. This branch does not need to be analyzed for correctness by the old backend, because we simply don't need to explore past that point.
So instead, if we can have the booster just return branchces immediately, then pyk can decide first (i) is this a branch even worth inspecting, and if so (ii) invoke the simplify endpoint directly on the post-branch states anyway. Then we can log in pyk the various simplifications that are actually being applied.
In particular, a CLI option for telling the booster to not fallback on branches would be good. We could also add the other fallback reasons as switches, so that we can experiment directly in pyk with turning those off (to understand them better).

Yep, a server CLI option will be fine, and easy to integrate into testing. I think that should be enough, actually doing it per RPC request looked like it would be harder to setup pyk to handle anyway.


Update Blog “meditation-pop-up-forage”

Automatically generated by Netlify CMS

👷 Deploy Preview for vakumposeti processing.
🔨 Explore the source changes: 8578ac6d2edb99bf518284366a90a43ab4c7fd90
🔍 Inspect the deploy log: https://app.netlify.com/sites/vakumposeti/deploys/61d374fc61fea400072669bc


Implemented globally replace word.

added solution to http://rosettacode.org/wiki/Globally_replace_text_in_several_files

In order to conform with #410 this will need to change:
-// Implements http://rosettacode.org/wiki/Globally_replace_text_in_several_files
+// http://rosettacode.org/wiki/Globally_replace_text_in_several_files

Do you think you could do this? Otherwise I can do it instead.

Made changes.

Yup that's it! Thanks! :)


[useInput] Externally provided ref is ignored

https://github.com/mui/material-ui/blob/62cd1590b4f4dbe29651236dffbb556d096bb1cf/packages/mui-base/src/InputUnstyled/useInput.types.ts#L22

It doesn't look like this bug report has enough info for one of us to reproduce it.
Please provide a CodeSandbox (https://mui.com/r/issue-template), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

there is a declaration of inputRef in useInput.types.ts but this variable doesn't use in hook, if you try pass the data it won't be initialized

@michaldudak created PR for the fix. https://github.com/mui/material-ui/pull/35807

@michaldudak could you please check this PR. I added some tests to be sure that we can continue support inputRef from useInput and handle all passed refs through props from InputUnstyled (forwardedRef and slotProps.input.ref as well)


[5.5] Ensure getJobIds always return an array.

Ensure getJobIds always return an array.

with Collections doesn't work

with Collections doesn't work
example:
Artisan::call("queue:retry", ['id' => collect(1, 2, 3)])

That is not a valid way to call the command.

This problem, when upgrade from 5.4 to 5.5, prompted me to think that the Collection should have the __toArray() method implemented.
Because something as simple as a type cast (array) breaks behavior.
Despite the fact that collections work quietly with "foreach" and "count"
but they do not know how to work with (array)
It turns out that the Collections want to appear as an array, but are not converted to an array.

The code you had before was never supported, and worked by chance.


Add item about dbt to "etl" section

About
Last week, @hlcianfagna and @hammerhead published the article Using dbt with CrateDB. Thanks. This patch also adds a corresponding item to the "etl" section, and also links to that article.
Preview
https://crate-clients-tools--41.org.readthedocs.build/en/41/etl.html#dbt

I wonder if we should maintain this page considering we already have https://crate.io/integrations and https://community.crate.io/t/overview-of-cratedb-integration-tutorials/1015

We definitively should. Both other pages are just indexes, without being able to add any significant and individual content easily, due to different reasons.
Here, we are in control without much bureaucracy, and have plenty of authoring capabilities to leverage, in order to balance between both pleasant appearance and guidance vs. information density, all at the blink of an eye, versioned, collaborative, and with corresponding preview capabilities, what both other resources and corresponding authoring environments just don't provide.
Future iterations will probably support, converge, and assimilate all of those resources to be derived from a single data source, to reduce maintenance.


Deploying to GitHub pages

When I deploy to GitHub pages, it renders README.md instead of the website. Any one else encountering this problem and how to fix it?
Running locally works fine.

Consider moving your web content into the root of your repository and renaming your default page to index.html, depending what type of file it is. (By convention the default page of most websites is called index.html, and this is what GitHub Pages will show by default if it exists.)
so try to do this if it doesn't solve your error do share some screenshot that will help me to know the actual reason behind it.


New version: CloudFoundry.CLI.v7 version 7.7.10

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Closes #163401
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335141
2024-07-17 07:32:16.625 [CLI ] Unable to locate nested installer at: C:\Users\VALIDA~1\AppData\Local\Temp\WinGet\CloudFoundry.CLI.v<IP_ADDRESS>\extracted\cf.exe
2024-07-17 07:32:34.809 [CLI ] Unable to locate nested installer at: C:\Users\VALIDA~1\AppData\Local\Temp\WinGet\CloudFoundry.CLI.v<IP_ADDRESS>\extracted\cf.exe

Automated error analysis suggests -1978335141 may mean Unable to locate nested installer. Does the RelativeFilePath have the previous version number in it?
(Automated response - build 886.)

I added the wrong URL. Should have added the binary URL instead of the installer URL. I have fixed this in this PR and the other related PRs of this package

https://github.com/microsoft/winget-pkgs/issues/142854


Keep the ghcr.io/kmesh-net/kmesh:latest image in sync with the master branch

What would you like to be added:
Use the CI/CD mechanism of Github to update ghcr.io/kmesh-net/kmesh:latest once the master branch is updated.
Why is this needed:
When developing and testing, we are used to using the latest image of Kmesh. However, we are updating latest image manually from time to time, and we often don't know what the latest commit is in the latest image.
Therefore it's often the case that the function works fine when testing with the latest iamge, but there are problems when merging into the master branch.
If the latest image is synchronized with the latest commit of master branch, this problem can be alleviated to a great extent.

It has already do that within github action.  https://github.com/kmesh-net/kmesh/actions/workflows/release-master.yaml

Excellent!


blacklist in separate file

Make the blacklist a separate file so it can be pulled from the following url
http://raw.githubusercontent.com/yeoman/yo/master/blackList.json
Related to https://github.com/yeoman/yo/issues/261

I'd prefer to have the list in the https://github.com/yeoman/yeoman.io as a lot more people have access there ;)


LoadConfig FileNotFoundException Error

bot.LoadConfig() System.IO.FileNotFoundException not found in the bot path.

@zezo010 Hi please copy the sample config from the path Aiml.NET.Tests/defaults

I have pushed new changes that include the sample files


ci: fix release

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


Node 6 execution handler warning in Azure Devops Task

We are experiencing the below warning message in our Azure Devops pipeline:
"This task uses Node 6 execution handler, which will be deprecated soon. If you are the developer of the task - please consider the migration guideline to Node 10 handler - https://aka.ms/migrateTaskNode10. If you are the user - feel free to reach out to the owners of this task to proceed on migration."
I am the user of the task who use DevOps pipeline for code deployment purpose and not sure whom to reach out to for this migration. Need your assistance to resolve this warning.

Hello @ananta5sweta,
Could you please provide name of affected task(s) in pipeline?

Hello, I have the same problem. For me it is with the following tasks: nuget, install nuget, dotnet, copy files, and publish artifacts.
For all tasks (except install nuget) I used the newest available version.
The Devops Server 2020 version is: Dev18.M170.8

Also: The instruction to upgrade to Node 10 tells something about updating TypeScript and changing some json files. I'm totally lost there: Where are the json files, on which computer should I upgrade typescript, on the agent or on the TFS server.
Of cource, the only thing, I know what to do with, is the DISABLE_NODE6_DEPRECATION_WARNING thing ;) But that seems not the right way to do it. Or, is this a viable option? What are the downsides to this?

Hello Denis,
While using below plugins in our Azure pipeline, we are getting the mentioned warning:

Artifactory Generic Upload
Artifactory Generic Download

Kindly let us know what could be done to resolve the issue.

Hi Denis,
We are getting below error intermittently during our deployment, we would like to understand
Error - Javascript heap out of memory, screenshots attached

If these issues are related?
Is this an intermittent issue? Is there anything we can do to avoid this issue?


Migrate to sound null safety

Description

Migrate to sound null safety
Bump up package version

Awesome @AyushBherwani1998 looks good to me

Awesome @AyushBherwani1998 looks good to me

just to confirm inorder to use the null safe version of this package,the Flutter project should also support null safety (with the required dart sdk constraints  sdk: ">=2.12.0-0 <3.0.0")?

just to confirm inorder to use the null safe version of this package,the Flutter project should also support null safety (with the required dart sdk constraints  sdk: ">=2.12.0-0 <3.0.0")?

Or its the other way around if a project wants to use the null safety feature it should you all the null safe versions of its dependencies.

Or its the other way around if a project wants to use the null safety feature it should you all the null safe versions of its dependencies.

To use the null safe version of the package, the Flutter project must satisfy the SDK constraint of >=2.12.0-0 <3.0.0.  Apart from that it should also satisfy transitive dependencies.  For instance if package a-nullsafe depends on package b-nullsafe and the project is using package b, it will raise issue of dependency.

To use the null safe version of the package, the Flutter project must satisfy the SDK constraint of >=2.12.0-0 <3.0.0.  Apart from that it should also satisfy transitive dependencies.  For instance if package a-nullsafe depends on package b-nullsafe and the project is using package b, it will raise issue of dependency.

okay got it thank you so much.

okay got it thank you so much.


Mutation arguments does not accept customType

Environment information
latest packages

Description
In gen1 I could do this
input UserInput {
  securityId: ID!
  docId: someEnum
}

type Mutation {
  requestOperation(input: UserInput!): Document // input is a custom type and output is a model

Gen2 shows an error if I use custom type in the arguments
requestOperation a
.mutation()
.arguments({
  input: a.ref("UserInput")
})

It was convenient since front-end would get strongly typed, separate interfaces for the input

Hi @OperationalFallacy this is currently expected behavior. Using a.ref does not dereference model fields when passed to custom query/mutation arguments.you have to explicitly list the fields. Same with referencing an enum, online inline enums are supported.

Hi @chrisbonifacio,
I think we might have raised a duplicate here:
https://github.com/aws-amplify/amplify-category-api/issues/2936
What would be the work around if we nested arrays what we want to pass to an AppSync resolver or lambda?
Item: a.customType({
  modifiers: a.string().array(),
}),

updateItems: a
  .mutation()
  .arguments({
    items: a.ref('Items').array(),
  })

We could flatten it, but then we would need to track the relations relationships manually.
updateItems: a
.mutation()
.arguments({
  items: a.string().array(),
  modifiers: a.string().array(),
})

All suggestions would be helpful. Thank you!


Issue #2703. Bitstamp Funding request bug fix

library creates request with double slash in the end: https://dev-publicapi.cryptonit.net/api/v2/user_transactions//
So Bitstamp understands this request like try to get trading pair related transactions but not funding history and throws error: {"status":"error","reason":{"MARKET_UNKNOWN":[]}}"; line: 1, column: 1]
Solution is to use implementation of web service call without currencyPair parameter,

It looks like the currency pair is part of the API.
https://www.bitstamp.net/api/
Maybe there's some other issue?

I working with this API. So if I need to have history of deposit and withdrawal transactions I should not send currecyPair to the API call. And it works ok and I get funding history in response. In other case? if I send currencyPair I get only trading transactions history for specified currencyPair and NO funding history at all. And we have related error which I described above.
Also, I see that in BItstampAuthenticatedV2 class line 52 already exists call for this url without currencyPair and without second slash. Only BItstampAccountService.getFundingHistory uses incorrect api call. So I fixed it and tested.

https://www.bitstamp.net/api/
In API documentation also specified two variants of this API function call with and without currencyPair. Search by https://www.bitstamp.net/api/v2/user_transactions/


Tasks not being queued in order

It appears usage of the NodeJS API for asynchronous tasks are not being added to the browser task queue in the correct order when the NodeJS API is used within the browser frame. Here's a code sample that demonstrates the problem:
test.html (loaded within an ElectronJS BrowserWindow):
<!DOCTYPE html>
<html>
<head>
</head>
<body>
<script>

function wait(seconds) {
	var until = new Date().getTime() + (seconds * 1000);
	while(new Date().getTime() < until) {};
}

var fs = require('fs');

// ----

console.log('1');

wait(1);

setTimeout(function() {
	console.log('3');
}, 0);

wait(1);

setTimeout(function() {
	console.log('4');
}, 0);

wait(1);

fs.readFile('./test.html', {encoding: 'utf-8'}, function(error, data) {
	console.log('5');
});

wait(1);

console.log('2');

</script>
</body>
</html>

When executed, I expect the output to be 1, 2, 3, 4, 5. Instead, it is 1, 2, 5, 3, 4. This appears to be related to the computation being performed from the calls to wait. When the calls to wait are taken out, it prints 1, 2, 3, 4, 5 as expected.

hi @jameslk, I just ran your code against 0.29.2 on Windows and I got the expected results 1,2,3,4,5
Here is a screenshot:

@frankhale That's odd. The issue does seem to sometimes go away when the browser frame is refreshed.
I've tried it on 0.28.3, 0.29.0, 0.29.1, and 0.29.2 on OS X Yosemite.
Here's a screenshot of the issue:

And the output from console:
$ node_modules/.bin/electron app.js
[43698:0715/234410:INFO:renderer_main.cc(200)] Renderer process started
[43699:0715/234410:INFO:renderer_main.cc(200)] Renderer process started
[43696:0715/234410:INFO:CONSOLE(17)] "1", source: file:///Users/james/Desktop/test-electron-async/test.html (17)
[43696:0715/234414:INFO:CONSOLE(39)] "2", source: file:///Users/james/Desktop/test-electron-async/test.html (39)
[43696:0715/234414:INFO:CONSOLE(34)] "5", source: file:///Users/james/Desktop/test-electron-async/test.html (34)
[43696:0715/234414:INFO:CONSOLE(22)] "3", source: file:///Users/james/Desktop/test-electron-async/test.html (22)
[43696:0715/234414:INFO:CONSOLE(28)] "4", source: file:///Users/james/Desktop/test-electron-async/test.html (28)

This is the source running the browser window:
var app = require('app');
var BrowserWindow = require('browser-window');

var mainWindow = null;

app.on('window-all-closed', function() {
	app.quit();
});

app.on('ready', function() {
  mainWindow = new BrowserWindow({width: 800, height: 600});

  mainWindow.loadUrl('file://' + __dirname + '/test.html');

  mainWindow.openDevTools();

  mainWindow.on('closed', function() {
    mainWindow = null;
  });
});

I'm not trying to shoot you down, there may in fact be a problem, just trying to provide some more context here. I reloaded it 10 times (reload via F5 in dev tools) and all the times it printed the correct results on Windows using Electron 0.29.2. I only tested 0.29.2 on Windows, I can test Mac tomorrow.

Actually, I just tested on a Windows VM and can confirm that it shows 1, 2, 3, 4, 5. So perhaps its a Mac-only issue. I'll try testing on a different Mac when I get a chance.

Okay cool, I'll definitely test in the morning on my Mac to confirm your results.

In Electron the task queue of Node.js and the task queue of browser are independent, so there is no guarantee that tasks of setTimeout and Node.js APIs would run in sequence. Also the web standard never guarantees the sequence of setTimeout callbacks, so I think current behavior is fine.

Unfortunately, this functionality caused a particularly nasty race condition for me that was pretty difficult to debug. I don't think how it currently works is what a developer would be expecting.
As a workaround, I will have to put NodeJS asynchronous API calls in setTimeouts to force the correct order of operation.


Toggle full name display of users

Would've closed #5222 if it was still open

@LavissaWoW thanks, looks good to me :)

Wouldn't it make sense to also add this new setting to PUI so that they don't get out of sync?

@wolflu05 yep, that's a good point. @LavissaWoW would you be able to implement a similar change into the new react frontend?

In this case, adding the key of the setting somewhere here should be enough BTW
https://github.com/inventree/InvenTree/blob/d30ff8a291d945c13984d6998dce67b4091839c4/src/frontend/src/pages/Index/Settings/SystemSettings.tsx#L47-L62


links2: fix darwin build

Description of changes

Modernize package by using finalAttrs instead of rec and hash instead of sha256
Disable implicit-int warning to fix failing configurePhase thinking compiler is unable to produce binaries due to implicit int being disallowed in C99 and above.
Add libavif to buildInputs to fix failing configurePhase due to avif.h header not being found
Disable graphics on Darwin to fix failing configurePhase due to graphics drivers not being found

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3439

Thanks for merging @7c6f434c, much appreciated! 🙂


【TCC】The vector obtained by T-SNE visualization cannot obtain the vector overlay of the paper in Figure 8.

After 70,000 epoch of training, by obtaining the aligned frame numbers, and extracting the mapping vector of each frame according to the index， and then visualizing with T-SNE, it is found that the T-sne visualization in Figure 8 of your paper is not available. The alignment vectors I get based on the reference video cannot overlap.  Do you have any visual skills for setting up?  Another question, I would like to ask for the annotation of Penn-action, get the json file of your thesis, what kind of annotation tool can be used for you, and how to get the json file, I hope to get your help.@debidatta

After 70,000 epoch of training, by obtaining the aligned frame numbers, and extracting the mapping vector of each frame according to the index， and then visualizing with T-SNE, it is found that the T-sne visualization in Figure 8 of your paper is not available. The alignment vectors I get based on the reference video cannot overlap. Do you have any visual skills for setting up? Another question, I would like to ask for the annotation of Penn-action, get the json file of your thesis, what kind of annotation tool can be used for you, and how to get the json file, I hope to get your help.@debidatta


CDS-80843 select temp version in studio

https://harness.atlassian.net/browse/CDS-80843
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ x] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

https://harness.atlassian.net/browse/CDS-80843

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


BUG: make build in Mac arm64

===========> Building binary sealctl for linux_arm64
CGO_ENABLED=0 GOOS=linux GOARCH=arm64 go build -tags "containers_image_openpgp" -ldflags "-X github.com/labring/sealos/pkg/version.gitVersion=untagged -X github.com/labring/sealos/pkg/version.gitCommit=4333c493 -X github.com/labring/sealos/pkg/version.buildDate=2022-06-24T23:27:38+0800" -o /Users/cuisongliu/Workspaces/go/src/github.com/labring/sealos/bin/linux_arm64/sealctl github.com/labring/sealos/cmd/sealctl
===========> Building binary sealos for linux_arm64
CGO_ENABLED=1 GOOS=linux GOARCH=arm64 go build -tags "containers_image_openpgp" -ldflags "-X github.com/labring/sealos/pkg/version.gitVersion=untagged -X github.com/labring/sealos/pkg/version.gitCommit=4333c493 -X github.com/labring/sealos/pkg/version.buildDate=2022-06-24T23:27:40+0800" -o /Users/cuisongliu/Workspaces/go/src/github.com/labring/sealos/bin/linux_arm64/sealos github.com/labring/sealos/cmd/sealos
# runtime/cgo
linux_syscall.c:67:13: error: implicit declaration of function 'setresgid' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
linux_syscall.c:67:13: note: did you mean 'setregid'?
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/unistd.h:593:6: note: 'setregid' declared here
linux_syscall.c:73:13: error: implicit declaration of function 'setresuid' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
linux_syscall.c:73:13: note: did you mean 'setreuid'?
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/unistd.h:595:6: note: 'setreuid' declared here
make[1]: *** [go.build.linux_arm64.sealos] Error 2
make: *** [build] Error 2

It's impossible to build Linux binaries on macOS when CGO_ENABLED=1, which is required by sealos.


[HOLD 22719] Create a truly cross platform map library in collaboration with Mapbox and rnmapbox/maps

Problem
For distance requests in App we created the ExpensiMaps library as a way of encapsulating platform specific logic for rending Mapbox maps using react native on native and web platforms. Although the platforms specific code is isolated from our App, we ultimately still have to maintain two different platforms by stitching together the rnmapbox/maps and react-map-gl libraries. It would be a lot more simple if Expensimaps used a single Mapbox library that was truly cross platform.
Why it's important
We want to be leaders in the react native space and push for more libraries to support cross platform, so let's lead the way by creating our own.
Solution
Work with Mapbox and maintainers of rnmapbox/maps to create a truly cross platform map library, then update ExpensiMaps to use it.

I'll take this on, but I'm going to put it on hold until we finish the project. It's really icing on the cake so it shouldn't slow the project down.


Fabric server 1.18.2 - No portal or Dragon

My 1.18.2 server for fabric doesnt spawn a dragon or the portal frame under the dragon, ive tried reseting the end multiple times, as stated in issue  #473 . Ive also editied the level.dat file as you previous stated so the fight never happend then reset the end again, still didn't work, i took a screenshot so you can see that not even the portal frame is there as it normally would be, even i vanilla if the dragon was glitched.

Hope you can help.
-XelaDK

If dragon don't spawn - this is issue with incorrectly removed data. This bug will happen in vanilla too, it is not related to BetterNether. Please don't duplicate issues if they were already opened


Expand BondFunctions::yield to accept dirty price as input too

This PR ports the changes made on the other side and enhances the yield() methods to accept both clean and dirty prices.

@igitur some issue on Appveyor build not related to code I'm going to fix it.


Edit: Self-hosted documentation

Description
This PR is really important because it was born after collecting a lot of feedback about Self-hosted documentation. The purpose of this refactors aims to improve the clarity of the documentation and the user experience for a self-made Mia-Platform Installation.
The PR introduces a refactor of the Self-Hosted section, reorganizes files and content and add new simplified ways to address some phases of the installation.
Pull Request Type

[x] Documentation content changes
[ ] Bugfix / Missing Redirects
[ ] Docusaurus site code changes

PR Checklist

[x] The commit message follows our guidelines included in the CONTRIBUTING.md
[x] All tests of Lint, cspell and check-content pass. (How to launch them?)
[x] No sensitive content has been committed

Other information

@stefano-arre I'd remove changes from this PR impacting the ones made in the private repo so that you won't have merge issues once it gets migrated here

@fredmaggiowski probably it would be easier if I create a new branch and adding all the other changes.  Unfortunately in this branch i made huge commits and i could lose the control of the edits.

@fredmaggiowski probably it would be easier if I create a new branch and adding all the other changes. Unfortunately in this branch i made huge commits and i could lose the control of the edits.

OK then I think we can close this PR and open a new one once you are ready. Let's put this on hold until the new one is open so we don't forget to delete the branch as well
I'm setting it to draft :)


chore(blog): post about finding governance model for the initiative

Description
The goal of this post is to make it easier to read asyncapi charter proposal

@fmvilas thanks a lot for the detailed review mate, all changes applied.
@smoya thanks mate, there is one open questions only, and a bit different solution to your proposal


Unable to type into monaco editor

Current Behavior
When typing into the monaco editor in a function node nothing happens. I cant cut or paste from context menu either. The editor on https://microsoft.github.io/monaco-editor/ works as expected.
EDIT:
I get this error in the console:
Uncaught Error: e[Symbol.iterator] is not a function

4780/</e.first@http://<IP_ADDRESS>:1880/vendor/monaco/dist/editor.js:1:395595
getCommand@http://<IP_ADDRESS>:1880/vendor/monaco/dist/editor.js:5:2530044
executeCommand@http://<IP_ADDRESS>:1880/vendor/monaco/dist/editor.js:5:967349
type@http://<IP_ADDRESS>:1880/vendor/monaco/dist/editor.js:5:410055
type@http://<IP_ADDRESS>:1880/vendor/monaco/dist/editor.js:5:162065
Ge/<@http://<IP_ADDRESS>:1880/vendor/monaco/dist/editor.js:5:155324
fire@http://<IP_ADDRESS>:1880/vendor/monaco/dist/editor.js:1:375996
f/<@http://<IP_ADDRESS>:1880/vendor/monaco/dist/editor.js:5:78560
    unexpectedErrorHandler http://<IP_ADDRESS>:1880/vendor/monaco/dist/editor.js:1
editor.js:1:370468
    unexpectedErrorHandler http://<IP_ADDRESS>:1880/vendor/monaco/dist/editor.js:1

Expected Behavior
I can type into the editor
Steps To Reproduce
Here's my codeEditor value:
{
            /** Select the text editor component used by the editor.
             * Defaults to "ace", but can be set to "ace" or "monaco"
             */
            lib: "monaco",
            options: {
                /** The follow options only apply if the editor is set to "monaco"
                 *
                 * theme - must match the file name of a theme in
                 * packages/node_modules/@node-red/editor-client/src/vendor/monaco/dist/theme
                 * e.g. "tomorrow-night", "upstream-sunburst", "github", "my-theme"
                 */
                theme: "vs",
                /** other overrides can be set e.g. fontSize, fontFamily, fontLigatures etc.
                 * for the full list, see https://microsoft.github.io/monaco-editor/api/interfaces/monaco.editor.istandaloneeditorconstructionoptions.html
                 */
                //fontSize: 14,
                //fontFamily: "Fira Code, Consolas, 'Courier New', monospace",
                //fontLigatures: true,
            }
        }

If I change lib from "monaco" to "ace" I get the old editor and it works as expected.
Example flow
No response
Environment

Node-RED version: 2.0.1 (official docker image)
Node.js version: Whatever is in the docker image
npm version: Whatever is in the docker image
Platform/OS:

Server: Official docker image
Client: Wayland on Arch Linux

Browser: Latest Chrome and Firefox

We have identified an issue with some nodes that include an old version of the jQuery multiple-select plugin - this causes conflicts with monaco.
The following nodes have been identified as including the offending version. Issues have been raised and some have since been resolved.

node-red-contrib-deconz-test-zehir - issue raised
node-red-contrib-defaro - issue raised
node-red-contrib-zigbee2mqtt - issue raised
node-red-contrib-wirenboard - issue raised
node-red-contrib-deconz - Issue raised - author is working on it :)
node-red-contrib-zway - Issue raised
node-red-contrib-spruthub - Issue raised

If you don't have any of these nodes installed, it would be helpful to identify what other contrib nodes you do have - particular any that have 'custom' edit dialog behaviours.

Updating node-red-contrib-zigbee2mqtt solved the issue! Thanks a lot!

Hi all,
just wanted to say how awesome internet is... I had this problem, had no idea what to do, installed another browser... Then looked at error messages and search internet for "e[Symbol.iterator] is not a function monaco" second result was this issue, noticed deconz, went to node-red, clicked update button, and now it works.
With all bad in the world, it's good to be reminded how far we have come as civilization.
Best regards,
David

I just had the same issue (using kinda outdated stuff as I didn't have the need to upgrade anything, "don't fix what's not broken")
Anyways in my case it was the same issue, node-red-contrib-zigbee2mqtt, but I also had to update everything else (mostly addition dashboard widget plugins) because there were conflicting dependencies between them. So I had to figure out a proper order of updating them and clicking on the update buttons one-by-one.
So my question is (and I tried to Google): is there a quick way to upgrade all the plugins at once to the latest versions possible (without them depending on conflicting libraries)?
Thanks in advance!


cURL command to download TRAM docker-compose.yml broken (doesn't follow redirect, zero byte file downloaded)

WHERE: Step 2 of "Installation/Web Application/" hosted at "https://github.com/center-for-threat-informed-defense/tram/wiki/Installation"
EXPECTED RESULT: non-zero byte "docker-compose.yml" downloaded to current directory after executing listed cURL command
OBSERVED RESULT: zero-byte "docker-compose.yml" created from executing "curl -O https://github.com/center-for-threat-informed-defense/tram/raw/main/docker/docker-compose.yml"
WHY: The target url redirects to final url "https://raw.githubusercontent.com/center-for-threat-informed-defense/tram/main/docker/docker-compose.yml" and the cURL "-O" option alone does not follow redirects
SUGGESTED FIX: use the -L option to force cURL to follow redirect(s) e.g., "curl -L -O https://github.com/center-for-threat-informed-defense/tram/raw/main/docker/docker-compose.yml"
SUPPORTING DATA (terminal transcript):
localhost:~/tram$ ls -la
total 8
drwxr-sr-x 2 nathan nathan 4096 Sep 13 10:42 .
drwxr-sr-x 3 nathan nathan 4096 Sep 13 10:42 ..

localhost:~/tram$ curl -O https://github.com/center-for-threat-informed-defense/
tram/raw/main/docker/docker-compose.yml
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

localhost:~/tram$ ls -la
total 8
drwxr-sr-x 2 nathan nathan 4096 Sep 13 10:44 .
drwxr-sr-x 3 nathan nathan 4096 Sep 13 10:42 ..
-rw-r--r-- 1 nathan nathan    0 Sep 13 10:44 docker-compose.yml

localhost:~/tram$ rm docker-compose.yml

localhost:~/tram$ curl -s -L -D - https://github.com/center-for-threat-informed-defense/tram/raw/main/docker/docker-compose.yml -o /dev/null -w '%{url_effective}\n\n'
HTTP/2 302
server: GitHub.com
date: Wed, 13 Sep 2023 10:46:53 GMT
content-type: text/html; charset=utf-8
vary: X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, Accept-Encoding, Accept, X-Requested-With
access-control-allow-origin: https://render.githubusercontent.com
location: https://raw.githubusercontent.com/center-for-threat-informed-defense/tram/main/docker/docker-compose.yml
cache-control: no-cache
strict-transport-security: max-age=31536000; includeSubdomains; preload
x-frame-options: deny
x-content-type-options: nosniff
x-xss-protection: 0
referrer-policy: no-referrer-when-downgrade
content-security-policy: default-src 'none'; base-uri 'self'; child-src github.com/assets-cdn/worker/ gist.github.com/assets-cdn/worker/; connect-src 'self' uploads.github.com objects-origin.githubusercontent.com www.githubstatus.com collector.github.com raw.githubusercontent.com api.github.com github-cloud.s3.amazonaws.com github-production-repository-file-5c1aeb.s3.amazonaws.com github-production-upload-manifest-file-7fdce7.s3.amazonaws.com github-production-user-asset-6210df.s3.amazonaws.com cdn.optimizely.com logx.optimizely.com/v1/events *.actions.githubusercontent.com productionresultssa0.blob.core.windows.net/ productionresultssa1.blob.core.windows.net/ productionresultssa2.blob.core.windows.net/ productionresultssa3.blob.core.windows.net/ productionresultssa4.blob.core.windows.net/ productionresultssa5.blob.core.windows.net/ productionresultssa6.blob.core.windows.net/ productionresultssa7.blob.core.windows.net/ productionresultssa8.blob.core.windows.net/ productionresultssa9.blob.core.windows.net/ wss://*.actions.githubusercontent.com github-production-repository-image-32fea6.s3.amazonaws.com github-production-release-asset-2e65be.s3.amazonaws.com insights.github.com wss://alive.github.com; font-src github.githubassets.com; form-action 'self' github.com gist.github.com objects-origin.githubusercontent.com; frame-ancestors 'none'; frame-src viewscreen.githubusercontent.com notebooks.githubusercontent.com support.github.com; img-src 'self' data: github.githubassets.com media.githubusercontent.com camo.githubusercontent.com identicons.github.com avatars.githubusercontent.com github-cloud.s3.amazonaws.com objects.githubusercontent.com objects-origin.githubusercontent.com secured-user-images.githubusercontent.com/ user-images.githubusercontent.com/ private-user-images.githubusercontent.com opengraph.githubassets.com github-production-user-asset-6210df.s3.amazonaws.com customer-stories-feed.github.com spotlights-feed.github.com *.githubusercontent.com; manifest-src 'self'; media-src github.com user-images.githubusercontent.com/ secured-user-images.githubusercontent.com/ private-user-images.githubusercontent.com; script-src github.githubassets.com; style-src 'unsafe-inline' github.githubassets.com; upgrade-insecure-requests; worker-src github.com/assets-cdn/worker/ gist.github.com/assets-cdn/worker/
content-length: 0
x-github-request-id: C9C6:6255:47E3B4C:4B04BB0:6501931D

HTTP/2 200
cache-control: max-age=300
content-security-policy: default-src 'none'; style-src 'unsafe-inline'; sandbox
content-type: text/plain; charset=utf-8
etag: "b4981856678d55fda3ac924d94d74d51edd1af438cfc24de8a64bd1d8d078bda"
strict-transport-security: max-age=31536000
x-content-type-options: nosniff
x-frame-options: deny
x-xss-protection: 1; mode=block
x-github-request-id: C3A2:6442:6559CC:78ACCE:650189FB
accept-ranges: bytes
date: Wed, 13 Sep 2023 10:46:53 GMT
via: 1.1 varnish
x-served-by: cache-bur-kbur8200144-BUR
x-cache: HIT
x-cache-hits: 1
x-timer: S1694602014.628118,VS0,VE1
vary: Authorization,Accept-Encoding,Origin
access-control-allow-origin: *
cross-origin-resource-policy: cross-origin
x-fastly-request-id: 9651738f71971f0b444ec2950c3420a7e6fa8f54
expires: Wed, 13 Sep 2023 10:51:53 GMT
source-age: 91
content-length: 1271

https://raw.githubusercontent.com/center-for-threat-informed-defense/tram/main/docker/docker-compose.yml

localhost:~/tram$ curl -L -O https://github.com/center-for-threat-informed-defense/tram/raw/main/docker/docker-compose.yml
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  1271  100  1271    0     0   2771      0 --:--:-- --:--:-- --:--:--  2771
localhost:~/tram$ ls -la
total 12
drwxr-sr-x 2 nathan nathan 4096 Sep 13 10:48 .
drwxr-sr-x 3 nathan nathan 4096 Sep 13 10:42 ..
-rw-r--r-- 1 nathan nathan 1271 Sep 13 10:48 docker-compose.yml

localhost:~/tram$ cat docker-compose.yml
# TRAM compose file.
#  - TRAM is currently setup to use Django with SQLite DB
#  - TRAM currently only works from localhost on port 8000 (or whatever port you select here)
#  - Any ML data and DB data is stored at the path stored in the environment variable
#    `DATA_DIRECTORY`. This is internal to Django.
#  - ALLOWED_HOSTS is a list of hosts allowed to connect to the Django server (in settings.py)
#  - SECRET_KEY is generated at startup to a random value. Set SECRET_KEY env variable for tram service below
#               to use a static value.
version: '3.5'
services:
  tram:
    image: ghcr.io/center-for-threat-informed-defense/tram:latest
    environment:
      - DATA_DIRECTORY=/tram/data
      - ALLOWED_HOSTS=["example_host1", "localhost"]
      - DJANGO_SUPERUSER_USERNAME=djangoSuperuser
      - DJANGO_SUPERUSER_PASSWORD=LEGITPassword1234 # your password here
      -<EMAIL_ADDRESS># your email address here
    volumes:
      - tram:/tram/data
      - tram_static:/tram/src/tram/staticfiles
  nginx:
    image: ghcr.io/center-for-threat-informed-defense/tram-nginx:latest
    ports:
      - "8000:80"
    volumes:
      - tram:/tram/data:ro
      - tram_static:/tram/src/tram/staticfiles:ro

volumes:
  tram:
  tram_static:

localhost:~/tram$

Thank you @nathanching for catching this and taking the time to report it. I just added your suggested fix to the install instructions.


how to create (edit) optipon so I can generate a canvas fom exsist data

I used Signature-pad to make a sketch field and I save the hidden input value in the database.
now I need to let the user edit the sketch again if he needs, so any way to sync the sketch and the hidden field,  so I generate the old sketch and also its the option to clear the sketch  and draw it again
any way to add undo option?

See Regenerating Signatures

Thanks for following up @ten9inc. @tryagain-3 did you get your issue sorted out? You can also use the clearCanvas() option to clear out the signature via JavaScript and the user will be able to clear it themselves if you add a .clearButton for SignaturePad to attach to.


Prevent  from generating srcset which doesn't support image size

Which package or tool is having this issue?
hydrogen-react
What version of that package or tool are you using?
2024.7.1
Steps to Reproduce

Upload a image to Shopify. E.g. 1500x1000
Use <Image /> component, and set aspectRatio to 1/2
Large srcset values will now load "correctly" with width and height attributes in correct aspect, but Shopify server can't transform images with width or height higher than original image size, and then return original image.

Expected Behavior
I would expect the <Image /> image component to omit any srcset value when it knows that it wont be generated for the specific aspect ratio

@wizardlyhel I am willing to work on this, if the issue should be resolved?

@andershagbard We happy if you can submit a PR for it.


Technical Debt: Add a Currency Model for points

Adding a Currency Model
This change addresses technical debt as noted in the code here:
https://github.com/SSWConsulting/SSW.Rewards/blob/983c49e2d69ff5a2adbce7cfbe0de8e6e2a5fce9/API/SSW.Rewards.Application/Reward/Commands/ClaimReward/ClaimRewardCommand.cs#L76
       // TECH DEBT: the following logic is intended to 'debounce' reward
       // claiming, to prevent users claiming the same reward twice
       // within a 5 minute window. This workaround is only required on
       // the current 'milestone' model for points. Once we move to the
       // 'currency' model, this will not be required anymore.

Add the ability to have QR codes that hold negative point values
Currently, points are calculated before the user information is sent to the application. During this calculation also include the negative QR codes.
Create unique QR codes for each prize that can be awarded and assign them the respective negative value of their point value.
Provide each office with these QR codes so that when a user claims and picks up a prize the user can scan the negative code.

Include a URL that explains to a new developer both models that the app users

Add an additional page to the Introductory popup in the Rewards app.
On the new page say something similar to, “The SSW Rewards app gives you the opportunity to accumulate points and win prizes. There are 2 ways that you can earn prizes with these points. First, by reaching specified milestones at which you will be rewarded the prize specific to that milestone. Second, by accumulating points, selecting a prize you would like, and then trading in the number of points that that prize is valued at.”

AB#59098

[ ] test
[ ] test2

@adamcogan  @MattGoldmanSSW @SSWnathanmills @jerwinparker Related database changes to separate achievements and rewards
https://ssw.visualstudio.com/SSW.Rewards/_workitems/edit/44263

Done! This has now been implemented in v2.


Typing a comma in argument list shows parameter hints in an object/array

When I type a comma inside a function argument list inside an object/array, the parameter hints are shown even before I have finished the argument.
E.g. in the following example, I am still on the 0th argument but the parameter hints are shown as if I'm moving on to the next one. Instead those hints are not relevant to me because I am still typing the same argument.

This gets really inconvenient because I can't see the surrounding context of my code when I just type a comma, but the hints are actually useful when I finish an argument, so I wouldn't want to disable them.

Thanks! Opened https://github.com/Microsoft/TypeScript/issues/22106 to track this upstream


Create page that displays users whole collection

In order to accomplish https://github.com/JDGiardino/BGG-Companion/issues/30, we first need a new page that can grab a users collection and display it as a table.

Ahhhhh yeah this makes sense!


Support for ns

added support for ns and enabled downcasting similar to the similar to the  pa.types.is_timestamp(primitive):   ,  didn't enable upcasting as it wasn't mentioned in the issue

@kevinjqliu  can you please review my PR and let me know if i made a mistake (please check with extra caution as it is my first contribution to any open source project)


Vim plug and lua plugins: calling setup & config functions

Hi, I am just posting here the solution of a problem on which I spent all my day...
The problem: many lua plugins require for their configuration, or even to run, to call a lua function. For example:
use({
    'emileferreira/nvim-strict',
    config = function()
        require('strict').setup()
    end
})

How to call such a function from vim plug like in packer (above)?
Of course all these plugins I found did'nt give any instructions about installing them with vim plug (always Lazy, packer... lua things...). On the web I found many tutorial about setting the vim config in lua, even to use vim plug from lua, but not the inverse.
Like often, it was so simple and evident than no one on the web thought it was usefull to explain that for the newbies a bit slow on the uptake like me... The solution is to use an include of lua code in init.vim, BUT not in the vim plug block delimited by call plug#begin() and call plug#end() but after (if I understood well!). Like that:
lua <<EOF
require("catppuccin").setup({
    flavour = "latte", -- latte, frappe, macchiato, mocha
    background = { -- :h background
        light = "latte",
        dark = "mocha",
    },
    transparent_background = true, -- disables setting the background color.
})
EOF

One day of roaming on the web to understand that... I hope this small post will avoid such a exhausting experience to some people after me!

Oh my god thank you so much for posting this! Finally solved my problem.


Remove dead code

https://github.com/xnd-project/rbc/blob/d8e409560b38a0173e6489f2675e680eaa596a15/rbc/thrift/client.py#L142-L177

Reason: theres a return statemente right before if not spec.thrift_spec which makes this code dead.


Update otomi-tools' jq

Is your feature request related to a problem? Please describe.
CI of otomi-core fails when having yq and jq as shadow functions that execute through docker otomi-tools.
Turns out that otomi-tools' jq version is 1.5 and has apparently issues with json piped to it.
jq in otomi-tools needs to be updated to 1.6
Describe the solution you'd like
Update otomi-tools to use jq-1.6 instead of 1.5
In preliminary tests, it seems to resolve the CI issue, where piping the yq's shadow output to jq's shadow would fail.

Can you not create issues for PRs that are not delivered to master yet? Just incorporate your findings there. Closing this.

Can you not create issues for PRs that are not delivered to master yet? Just incorporate your findings there. Closing this.


Failures when SchemaRegistry has high number of schemas defined

Describe the bug
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 03:38:50.833 [reactor-http-epoll-8] ERROR org.springframework.boot.autoconfigure.web.reactive.error.AbstractErrorWebExceptionHandler - [2af5bd65]  500 Server Error for HTTP GET "/api/clusters/cluster/schemas"
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | org.springframework.core.io.buffer.DataBufferLimitException: Exceeded limit on max bytes to buffer : 262144
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	at org.springframework.core.io.buffer.LimitedDataBufferList.raiseLimitException(LimitedDataBufferList.java:101) ~[spring-core-5.2.3.RELEASE.jar!/:5.2.3.RELEASE]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | Error has been observed at the following site(s):
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	|_ checkpoint ⇢ Body from GET http://host1.name:8081/subjects [DefaultClientResponse]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	|_ checkpoint ⇢ Handler com.provectus.kafka.ui.controller.SchemasController#getSchemas(String, ServerWebExchange) [DispatcherHandler]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	|_ checkpoint ⇢ com.provectus.kafka.ui.config.ReadOnlyModeFilter [DefaultWebFilterChain]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	|_ checkpoint ⇢ com.provectus.kafka.ui.config.CustomWebFilter [DefaultWebFilterChain]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	|_ checkpoint ⇢ org.springframework.security.web.server.authorization.AuthorizationWebFilter [DefaultWebFilterChain]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	|_ checkpoint ⇢ org.springframework.security.web.server.authorization.ExceptionTranslationWebFilter [DefaultWebFilterChain]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	|_ checkpoint ⇢ org.springframework.security.web.server.authentication.logout.LogoutWebFilter [DefaultWebFilterChain]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	|_ checkpoint ⇢ org.springframework.security.web.server.savedrequest.ServerRequestCacheWebFilter [DefaultWebFilterChain]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	|_ checkpoint ⇢ org.springframework.security.web.server.context.SecurityContextServerWebExchangeWebFilter [DefaultWebFilterChain]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	|_ checkpoint ⇢ org.springframework.security.web.server.context.ReactorContextWebFilter [DefaultWebFilterChain]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	|_ checkpoint ⇢ org.springframework.security.web.server.header.HttpHeaderWriterWebFilter [DefaultWebFilterChain]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	|_ checkpoint ⇢ org.springframework.security.config.web.server.ServerHttpSecurity$ServerWebExchangeReactorContextWebFilter [DefaultWebFilterChain]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	|_ checkpoint ⇢ org.springframework.security.web.server.WebFilterChainProxy [DefaultWebFilterChain]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 	|_ checkpoint ⇢ HTTP GET "/api/clusters/cluster/schemas" [ExceptionHandlingWebHandler]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | Stack trace:
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 		at org.springframework.core.io.buffer.LimitedDataBufferList.raiseLimitException(LimitedDataBufferList.java:101) ~[spring-core-5.2.3.RELEASE.jar!/:5.2.3.RELEASE]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 		at org.springframework.core.io.buffer.LimitedDataBufferList.updateCount(LimitedDataBufferList.java:94) ~[spring-core-5.2.3.RELEASE.jar!/:5.2.3.RELEASE]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 		at org.springframework.core.io.buffer.LimitedDataBufferList.add(LimitedDataBufferList.java:59) ~[spring-core-5.2.3.RELEASE.jar!/:5.2.3.RELEASE]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 		at reactor.core.publisher.MonoCollect$CollectSubscriber.onNext(MonoCollect.java:132) [reactor-core-3.3.2.RELEASE.jar!/:3.3.2.RELEASE]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 		at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:114) [reactor-core-3.3.2.RELEASE.jar!/:3.3.2.RELEASE]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 		at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:192) [reactor-core-3.3.2.RELEASE.jar!/:3.3.2.RELEASE]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 		at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:192) [reactor-core-3.3.2.RELEASE.jar!/:3.3.2.RELEASE]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 		at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:114) [reactor-core-3.3.2.RELEASE.jar!/:3.3.2.RELEASE]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 		at reactor.netty.channel.FluxReceive.drainReceiver(FluxReceive.java:218) [reactor-netty-0.9.4.RELEASE.jar!/:0.9.4.RELEASE]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 		at reactor.netty.channel.FluxReceive.onInboundNext(FluxReceive.java:351) [reactor-netty-0.9.4.RELEASE.jar!/:0.9.4.RELEASE]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 		at reactor.netty.channel.ChannelOperations.onInboundNext(ChannelOperations.java:348) [reactor-netty-0.9.4.RELEASE.jar!/:0.9.4.RELEASE]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 		at reactor.netty.http.client.HttpClientOperations.onInboundNext(HttpClientOperations.java:588) [reactor-netty-0.9.4.RELEASE.jar!/:0.9.4.RELEASE]
kafka_kafka-ui.1.wra5xvqg3tbz@redacted    | 		at reactor.netty.channel.ChannelOperationsHandler.channelRead(ChannelOperationsHandler.java:90) [reactor-netty-0.9.4.RELEASE.jar!/:0.9.4.RELEASE]

Set up
Docker
Steps to Reproduce
Steps to reproduce the behavior:

High number of schemas (~100k)
Try to load

Expected behavior
Should work

Max buffer size in Spring defaults to hardcoded value of 256 KB: https://github.com/spring-projects/spring-framework/blob/main/spring-core/src/main/java/org/springframework/core/codec/AbstractDataBufferDecoder.java#L51
But what puzzles me more is why this code is using some custom HTTP queries instead of official SR client library: https://github.com/confluentinc/schema-registry/tree/master/client/src/main/java/io/confluent/kafka/schemaregistry

Hi, @akamensky. We are using the Reactive Web client in our schema registry service to make interaction non-blocking.
It's default not we expected that you have so many subjects in your schema registry, and we definitely have to add pagination here. We'll do it in the next major versions. According to your problem, I think the simplest solution, for now, would be to add env variable
SPRING_CODEC_MAX_IN_MEMORY_SIZE: 20MB

Tried this variable, does not change anything. Still same exact error and same limit shown in error.

@germanosin any feedback on this issue? As I mentioned I tried env.var, but it does nothing. Still same error with the same buffer size limit.

@akamensky. Thanks for your partience. Trying to reproduce it.

@akamensky, we merged https://github.com/provectus/kafka-ui/pull/903 that adds support for WebClient's buffer size tuning (now it is set to 20mb by default). Please try to use it. We will add pagination support in next releases.

This works now, I can browse schemas, but it is pretty bad experience -- every request is very very slow. But guess that is separate issue.

@akamensky it is expected that it will work slow without pagination :-) if you suspect that it is caused by debug logging please try to add -e LOGGING_LEVEL_ROOT=INFO


Serde support

This is more of a request for comments than an issue: I consume an XML-based API where neither quick-xml's Serde support the strong-xml or hard-xml wrapper around xmlparser can currently handle the format (OGC CSW records). serde-xml-rs does correctly deserialize the format though.
While I understand that one would normally base Serde support directly on xmlparser instead of roxmltree, in my case, my data model is already Serde-oriented and going via the intermediate roxmltree is still ten times (90%) faster than using serde-xml-rs and it seems significantly simpler to implement than an integration with xmlparser. (So basically, I just use Serde to avoid manually unpacking the document structure.)
Hence, I created a small crate available at https://github.com/adamreichold/serde-roxmltree and wanted to ask you a few questions before publishing anything, namely:

Whether you are alright with name directly referencing roxmltree or whether I should try to be more creative?
Whether you consider this useful and small enough to include here as an optional feature? (It works equally well as a separate library, so I think this would mainly help discoverability.)
Whether you have any hints on things that should be implemented differently?

While I understand that one would normally base Serde support directly on xmlparser instead of roxmltree

Not really. xmlparser is just a tokenizer/lexer. You cannot use it directly to handle real-world XML. roxmltree adds proper escaping/attribute value normalization, entity references, whitespaces and namespaces.
As for serde, I have essentially zero knowledge about it, at least from the implementation and not a user perspective.
Adding serde feature directly to roxmltree seems like an unnecessary maintenance burden for me. So I would prefer a separate repo/crate for now. And when it would become stable and battle-tested we might merge it here.
At a quick glance, serde-roxmltree looks way too minimalistic. Imho, XML is too complex/versatile for serde. You do not handle namespaces, complex text (text can be before and after an element) and so on.
Like for example, how would you handle:
<text>some<q/>text</text>

So yes, directly referencing roxmltree if fine. Separate crate for now. No comments about the implementation.

Imho, XML is too complex/versatile for serde. You do not handle namespaces, complex text (text can be before and after an element) and so on.

Indeed, I think this is a general issue with all integrations between Serde and XML. One can try to work around this by giving special meaning to names given via #[serde(rename = "..")], but I suspect this would quickly spiral into a separate mini-language. I think this is also why crates like strong-xml/hard-xml go for a separate XmlRead trait and derive macros which include fine-control over the mapping to the XML structure.
In any case, the trivial mapping to children and attributes which ignores namespaces is often good enough for the applications I have and one can always fall back to using Document/Node directly when that does not work.

So yes, directly referencing roxmltree if fine. Separate crate for now. No comments about the implementation.

Thanks for looking it and giving clear advice!


propose changing define_state to simply state, and required_param to simply param

From @catmando on November 25, 2015 15:29
state :foo, :bar  # syntax stays the same just drop the "define_"
param :baz, :type => String # by default params are required
param :baz, :required, :type => String # can explicitly say :required
param :user, :optional, :type => User # must say :optional or
param :user, default: nil, :type => User # if a default is given its also optional

(assuming params is kept as the react.rb access to props... if we change to props the above would be prop :user, etc)
Copied from original issue: zetachang/react.rb#85

From @ajjahn on November 25, 2015 15:49
Yep, I'm on board with this. Also, keep it param instead of prop. I agree with the point in made #83:

params allows "props" to be for low level access to the actual react props hash

A param is a prop + observers, etc. If you need access to low level props, they're there as well.
Also, I may be in the minority, but I use and prefer the grape style params declarations in my own components. I vote to continue to support that, especially since both methods work exactly the same in the validator anyway.

From @Thermatix on November 25, 2015 16:42
I like this, always felt that define_state, required_state, optional_state was a little redundant to be honest.
By the way, can we have props like a state but without an observer? so we have three tools,
params = values passed into component
state = value with observer to re-render on value change
prop = value without observer that doesn't cause re-render on value change
or does that already exist?

From @catmando on November 25, 2015 19:2
your third case would be an instance variable...

mechanism
.js
.rb

component state
accessed via a hash, use setState or replaceState to update the hash
accessible as methods on the state object (lets call them state variables), the state name followed by "!"** updates the state variable, and calls replaceState

component parameters
accessed via a hash
accessible as methods on the params object

global state
various flux libraries add this
uses same syntax and mechanisms as component state

two way binding
LinkedStateMixin
The React::Observable class provides this as a stand alone feature, but for simplicity, all states can create observables, and params typed React::Observable provide a "!" method that has the same semantics as the state "!' methods.  Both these features are just syntactic sugar, and don't change any underlying semantics of state or params.

call back params
pass a function as a param
pass any proc as a param.  If the param is typed, then accessing the param will directly call the proc.  To retrieve the actual proc without calling use the #method.  Like two way binding this is just syntactic sugar

** why not just use assignment?
Consider a state variable that contains an array.  As you add or remove or just change values in the array, the state variable itself never changes values.  Instead if you write state.foo! << "new item" then you both access the value of foo, and also notify the system when the state changes.
Of course we could allow state.foo = "xxx" to work as well, but it seems like having two mechanisms that have only some overlap, does not add clarity.
The way state.foo! works is also nicely consistent with other mechanisms.  It creates an observable, that notifies any observers (in the case of state variables, the observer is simply a method that will deal with updating the state.)  But the same mechanism also allows us to pass the observable as a param, and without any extra work create a two way linkage.  Finally this mechanism has everything we need for the flux architectures observers and notifiers.


Add handling for datasets data is null to use last line coordinates

thanks, this is now available in 5.6.1


Bug fix: Enable fast to override quantize json

Follow up fix for: https://github.com/pytorch/torchchat/commit/46977645de6e9e29e58fada7d600c1930ed6f67b
We want to allow "fast" to work as a manual overwrite of a --quantize accelerator config, which the previous PR disabled while fixing a different bug

No overwrite
python3 torchchat.py generate llama3.1 --quantize '{"precision": {"dtype":"float16"}, "executor":{"accelerator":"mps"}}'

NumExpr defaulting to 10 threads.
PyTorch version 2.6.0.dev20241002 available.
lm_eval is not installed, GPTQ may not be usable
Using device=mps

Overwrite with device arg
python3 torchchat.py generate llama3.1 --quantize '{"precision": {"dtype":"float16"}, "executor":{"accelerator":"mps"}}' --device cpu

overriding json-specified device mps with cli device cpu
NumExpr defaulting to 10 threads.
PyTorch version 2.6.0.dev20241002 available.
lm_eval is not installed, GPTQ may not be usable
Using device=cpu Apple M1 Max

Overwrite with fast arg
python3 torchchat.py generate llama3.1 --quantize '{"precision": {"dtype":"float16"}, "executor":{"accelerator":"cpu"}}' --device fast

overriding json-specified device cpu with cli device mps
NumExpr defaulting to 10 threads.
PyTorch version 2.6.0.dev20241002 available.
lm_eval is not installed, GPTQ may not be usable
Using device=mps

Run with fast arg (same as running without device arg)
python3 torchchat.py generate llama3.1 --device fast

NumExpr defaulting to 10 threads.
PyTorch version 2.6.0.dev20241002 available.
lm_eval is not installed, GPTQ may not be usable
Using device=mps

cc: @mikekgfb


cmd/go: reject packages whose import paths collide with std packages

What version of Go are you using (go version)?

$ go1.19rc1 version
go version go1.19rc1 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What did you do?
--- go.mod ---
module sync

go1.18

--- sync.go ---
// this is my sync!
package main

What did you expect to see?
build error
(no main function!)
What did you see instead?
no error
$ go1.19rc1 build .
$ echo $?
0

$ go1.19rc1 doc .
this is my sync!

$ go1.19rc1 list -f '{{.ImportPath}} {{.Dir}}' .
sync /Users/hakim/sdk/go1.19rc1/src/sync

And go list is confused, as a result, tools that depend on x/tools/go/packages (e.g. gopls) are very confused.

It's worth clarifying that the go build . command in the example builds the stdlib sync package, not our package, driven by go list's confusion.

I think this is either #35270 or #26227


Script tag execution and openapi rendering

closes #61
Supports script  tag execution in MD file
Supports Swagger UI for openapi specs loading using html and script tag in MD file as below

  <meta charset="utf-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <meta
    name="description"
    content="SwaggerIU"
  />
  <title>SwaggerUI</title>
  <link rel="stylesheet"<EMAIL_ADDRESS>/>

@adrianvlupu Please help review the changes and let me know if we need any adjustments as this is my time engaging in this project.
If all good please help merge these changes when you get a chance. Hope it will help incorporate API specs along with awesome plantuml C4design artifacts.

@vellala2000 Have some questions around this one (I haven't tested it so)

Does it work with local openapi.json files? (having a documentation failing because the web api isn't running seems wrong)
The Swagger UI present a readonly presentation or are you able to make API calls from it? (Normally I have Swagger activated on my Web API:s in dev/test stage)
What happens if you generate a PDF? If it breaks or looks totally weird should it be special case handling for that.

And also a small comment: The option naming should be something like includeSwagger instead of executeScript because it only includes the JS link or not.

@MickeJohannesson

Yes its working with local and remote JSON file
Try it out feature available and working in swagger UI
PDF is generating okay with just one liner showing folder name and path with the example code.  it depends on what user puts in  and

@vellala2000 I think this is a good addon, even though I would like an automatic generated md file with all content instead of the SwaggerUI generation (Need to have the PDF in some cases). Like you add the json-file in the /src directory and in the /docs there would be a generated MD file.
Regarding the naming, sorry but I missed the option in the docsify option. Naming makes more sense then :)
Still will test it out to see how it works, but I haven't got the time at the moment

Yeah I understand where you are coming from.
I looked into widdershins which converts specs into MD file and  generated md file is not reader friendly without using another tool like slate. slate is kind of docsify for API specs.

I am looking forward to use this functionality soon. no pressure :)
this actually completes all types of design documents I am trying to showcase.

I am able to do openapi rendering by using existing custom docsify template option.


fix: support cast negative numbet to decimal

negative numbers
Which issue does this PR close?

Closes #5127
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

I think @viirya already has a PR related to this #5128

Closing in favor of #5128


Bower.json - main options incorrect

Please, modify bower.json, in the option "main" the value from "dist/angular-input-match.min.js" to "angular-validation-match.min.js".

Does bower assume the files will be in a folder called "dist"?  Because that is the only place a file named "angular-validation-match.min.js" exists.  Looking at bower docs for main, I am not seeing how it would know.

I made a verification in the files and realized that wiredep not replace the value according to your modification. The bower.json is correct!!! Sorry my rush in the diagnostic!!


How to correctly run a driver so that it always kills the process it spawns (binary)?

The handling of the custom binary is quite inconsistent because the driver does not always kill everything. It seems highly dependent on the signal it receives. Is there a way to ensure that the driver spawns its processes in a group that will be killed when it shuts down?

https://github.com/MicrosoftEdge/EdgeWebDriver/issues/152


Add new webhooks for Labels and Milestones

Announcement: https://developer.github.com/changes/2016-10-27-new-label-and-milestone-webhooks/
This should be very straightforward... just defining the types for these new events.

working with.


GH-37907: [R] Setting rosetta variable is missing

Rationale for this change
The latest version of r/R/install-arrow.R  was not working properly, since it was relying on the on_rosetta() function, which is not defined elsewhere. I just fixed the identification of rosetta in the script.
With the current code, the following gives an error
> source("https://raw.githubusercontent.com/apache/arrow/master/r/R/install-arrow.R")
> install_arrow()
Error in on_rosetta() : could not find function "on_rosetta"

What changes are included in this PR?
It only removed the on_rosetta() function, which was not defined elsewhere, and reverted back to the rosetta object to identify if rosetta is present or not on a user's system.

Are these changes tested?
Yes. It was tested with the current code and the proposed PR. The proposed PR works as expected.

Are there any user-facing changes?
No.

Closes: #37907

Thanks for making this PR! One small change, otherwise looks good to go :)

@thisisnic should we merge this before the release?

@jonkeane You most recently worked on the code that this PR touches and I'm not sure where is best for this function - I don't suppose you'd mind giving this a quick look over?

@thisisnic should we merge this before the release?

Yes, but it'll need a final change before merging

It looks like this would also fix a nightly fail/cran warning: https://github.com/ursacomputing/crossbow/actions/runs/6463099167/job/17545762151#step:6:3794

I hope you don't mind that I pushed those changes requested to this branch so that we can get this in before the upcoming release.

@github-actions crossbow submit test-r-install-local

Once the crossbow build is done I'm going to merge this, unless there are objections

I've also created https://github.com/apache/arrow/issues/38251 to track adding a test for this self-containedness

Thanks @jonkeane and @thisisnic
I can confirm that now the command
source("https://raw.githubusercontent.com/apache/arrow/main/r/R/install-arrow.R")
install_arrow()

works as expected again, as stated in the documentation https://arrow.apache.org/docs/r/articles/install.html?q=install_arrow#using-install_arrow

Thanks again @fernandomayer for the issue + PR


Remove VERSION.txt

Forgotten in 997677a.

Codecov Report

Merging #325 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #325   +/-   ##
=======================================
  Coverage   93.68%   93.68%
=======================================
  Files         133      133
  Lines        4151     4151
  Branches      413      413
=======================================
  Hits         3889     3889
  Misses        167      167
  Partials       95       95

Coverage remained the same at 95.856% when pulling 43872bfb9f4459be486121df70a0b7a355a0e2a8 on blueyed:rm-version into e913bc6cf8f906c9ba42150294d2057e886f5d0c on Kuniwak:master.


Cache deps between github CI action runs

Caching support was announced recently: https://github.blog/changelog/2019-11-04-github-actions-adds-dependency-caching/

Fetching deps and building is pretty quick, so I'm not really worried about this right now.


 Delete the others, including these Instructions.
{{cask_file}} represents the cask file you’re submitting/editing (if applicable).
If there’s a checkbox you can’t complete for any reason, that’s OK. Just explain in detail why you weren’t able to do so.

Changes to a cask
Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.

Adding a new cask

[x] Checked there aren’t open pull requests for the same cask.
[x] Checked there aren’t closed issues where that cask was already refused.
[x] When naming the cask, followed the token reference.
[x] Commit message includes cask’s name.
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.

Changes to the core

[x] Followed hacking.md.

One PR per cask, please, so it doesn’t happen that one stops the other from being included, like here. Will update qq separately. Thank you for the report.


[hold] [feature] @mentions and notifications [OSF-5975][OSF-5658]

Carried over from #5840

Purpose
Add functionality for @/+ mention of contributors in comments. Only confirmed contributors, both bibliographic and non-bibliographic, can be mentioned.
Related tickets: https://openscience.atlassian.net/browse/OSF-5658 & https://openscience.atlassian.net/browse/OSF-5975
Changes

@ symbol or + triggers dropdown where user can select the full name of a contributor to mention them in a comment
@ mention names appear as a link to the mentioned contributor
Email notifications are sent to contributors who are mentioned but are grouped if user would receive multiple for one event i.e. new comment and mention
An error message is shown and the submit button is disabled if a comment is over 500 characters
change comments template from textareas to ContentEditable divs

support keeping track of users who have been mentioned
does not allow partial deletion of the mention

add dependency At.js

provide @/+ functionality

add ever_mentioned to the comment model

support determining who is a new mention after editing so contributors are not notified multiple times for the same comment

add new notification types and email templates

mention notifications can occur on creation or on edit while comments only notify subscribers on creation
comments and mentions have different notification settings
currently the mentions are all of the 'email_transactional' notification_type

Mentioning a contributor:

Entering a comment longer than 500 characters:

Possible additions

Emojis PR #5418 (this is being updated to reflect changes on this PR)

Side Effects

ContentEditable divs

can cause some unexpected behavior with pasting/arrow keys/enter

a user can write in a different name for the mention if they really understand the code

Initial round of bugs/questions found by @AllisonLBowers:

[ ] *In email notifications, the usernames that are @ mentioned have links that go nowhere (they are just the user GUIDs)
[ ] *Usernames with certain characters do not work (!, @, ?, -, #, $, ~, +, `, “, (), *, ., etc). The username shows up correctly in the list of contributors when you type “@,” but if you select the name, it just shows up as regular text and does not perform the @mention.
[ ] *I’m not getting notifications for users who have comments set to “Never”
[ ] *Is there supposed to be a separate email template for @mentions? Currently, they only show up in regular OSF Notifications format and seem to be treated like regular comments.
[ ] *On global notification settings, it is only possible to set Mentions to “Instantly.” However, it is possible to receive mentions daily if you have comments for a particular project set to “Daily.” Should there be multiple options listed for Mentions? And if Instantly is the only option, should it be presented in a drop-down menu? This makes it look like the user can change their settings, only to click on it and discover this isn’t the case.
[ ] *If I’m understanding the PR correctly, if a user edits a comment and adds an @mention, the mentioned user should receive a notification. However, this behavior is not occurring.


Create feature list

I need to compile a feature list and game description.

FEATURES:

Top down fast paced racing game.
Support for keyboard, controller, and mobile for gameplay and interface.
13 Campaign Maps, 54 medals to unlock.
Ability to race against your best time, or ghost medals.
Online leaderboards to watch or race against other players runs.
Map maker to create your own maps.
Community map list to share your maps, and community leaderboards.
Ability to choose an avatar, and a car model.
Ability to create, and edit your own profile.
Invite other players to race against your time.
Settings
Custom keybinds
A progression graph to view your performance on previous runs.

PAGES:

/ (title)
/welcome
/signup
/signin
/signup/gmail
/signin/gmail
/main
/profile
/profile/guest
/profile/edit
/profile/guest/edit
/profile/guest/upgrade/gmail
/profile/guest/upgrade/email
/campaign
/campaign/:mapIndex
/campaign/progression/:id
/community-maps
/community-maps/create
/community-maps/edit/id
/community-maps/clone/id
/community-maps/upload
/community-maps/all
/community-maps/leaderboard/id
/map-import
/leaderboards
/leaderboards/community
/leaderboards/campaign
/leaderboards/campaign/id
/settings
/settings/keybinds
/countdown
/hidden
/pause
/finish
/invited
/invited/info
/test
/dialogue/id
/credits
/test-nested
/rotate-device


[libs/movex] Remove unused types

Where
libs/movex/src/lib/core-types.ts
What
Remove the commented code and the unused type MovexState as well as the import MovexReducer!

Why
Readablity
Definition of done

The unused code is gone
The comments are gone
All tests keep passing

i want to contribute kindly assign this to me

i want to contribute kindly assign this to me

Hey @khushi-rastogi, this is already taken care by @igorwessel, but here's a list of other issues we can use your help with https://github.com/movesthatmatter/movex/labels/hacktoberfest!
Thank you so much 🙏


TypeError: browser.on is not a function

08 11 2015 14:18:56.615:ERROR [launcher]: [TypeError: browser.on is not a function]
TypeError: browser.on is not a function
    at /home/rgibson/Projects/sizzle/node_modules/karma/lib/launcher.js:94:17
    at next (/home/rgibson/Projects/sizzle/node_modules/karma/node_modules/batch/index.js:118:7)
    at Batch.end (/home/rgibson/Projects/sizzle/node_modules/karma/node_modules/batch/index.js:154:5)
    at launch (/home/rgibson/Projects/sizzle/node_modules/karma/lib/launcher.js:110:11)
    at invoke (/home/rgibson/Projects/sizzle/node_modules/karma/node_modules/di/lib/injector.js:75:15)
    at Server.<anonymous> (/home/rgibson/Projects/sizzle/node_modules/karma/lib/server.js:170:24)
    at Server.g (events.js:260:16)
    at emitNone (events.js:67:13)
    at Server.emit (events.js:166:7)
    at emitListeningNT (net.js:1260:10)
    at doNTCallback1 (node.js:428:9)
    at process._tickCallback (node.js:350:17)

I think this should be getting on from BaseLauncher like karma-sauce-launcher (rather than a self.on = emitter.on kludge), but baseLauncherDecorator is not a drop-in change because this plugin provides a kill that is signature-incompatible with BaseLauncher kill & forceKill.

also getting this issue.


Improvements

Ask for workflow URL (not ID)

could it not clear the form every time?
the WF seems to need to be 'published' and not 'by link', is that correct? maybe add to the help text for that field?
I'd suggest making the links all target="_blank" because I clicked one and lost my download


Galaxy manga AR Version

Source information
Galaxy manga AR
Source language
arabic
Source new URL
https://galaxymanga.net
Other details
The link of the AR version has changed
Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I will fill out all of the requested information in this form.

The link ok the extension has changed updste it pls

The extension has been replaced with an updated version, read what the bot says. You should search the existing issues (both open & closed) before opening a new issue, and acknowledging that you did when you didn't. Also consider joining the Keiyoushi Discord server, and check the status-update, where this fix has been in place since July.


Set the host in the configuration file

It's practical to be able to define the host in the configuration file, like the port.

This pull request is now managed with CodeReviewHub. Refresh.


Remove DropCap setting from the Core Paragraph Block by default

This will only work for WordPress 5.6 & 5.7 and is likely going to need an update for 5.8 again.

Description of the Change

With this PR I am removing the DropCap option from the sidebar of the core/paragraph block.
The DropCap setting can get disabled via the theme.json file. Since this mechanism currently is only available in the Gutenberg Plugin there is a way to filter these setting in core. Since the theme.json format is still experimental however the format for disabling the dropCap option changed between WordPress 5.6 & 5.7. In 5.8 the theme.json will most likely be supported and this won't be necessary any longer.
Alternate Designs

Benefits

Possible Drawbacks

Verification Process

Checklist:

[X] I have read the CONTRIBUTING document.
[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[ ] I have added tests to cover my change.
[X] All new and existing tests passed.

Applicable Issues

Changelog Entry

Removed DropCap option of Core Paragraph block by default.

@fabiankaegy since some projects will still need or want the DropCap support, I would be hesitant to include this in the Scaffold. Also, I think we'll get in the rabbit hole of bloating the Scaffold with code disabling a bunch of settings that aren't really useful.
I think this code snippet is valuable and should be available somewhere but not baked into the Scaffold. Again main concern being that we can potentially bloat the Scaffold mainly because Gutenberg has lot of settings that aren't really useful.

@smy315 the reason I added this PR is because of a request that @joesnellpdx had made in a list of improvements to the scaffold. So we may want to check on what we actually want there :)

@fabiankaegy the code looks fine to me. However, I am also a little hesitant to include this as the default state for the scaffold for the same reasons as @smy315.
@joesnellpdx if there is a common list of features that we disable and it needs to be in the theme scaffold, I wonder if we can handle this with a custom filter like tenup_disable_block_features that will target those items specifically? It will bloat the scaffold a bit but if it's being done on the majority of projects, we'll save some engineering cycles so IMO it's worth it.

@ryanwelcher maybe this is something worthy of us hoping on a call.
There are several things we are considering moving forward on the scaffold that will add in our overall project initial build efficiencies... things we do 80% or more of the time (see https://docs.google.com/spreadsheets/d/1-aatYPaTtzG5kk0ik3FcxUaYL5xjIuGfchopDINU-Qo/edit#gid=0)
One of those items on the list is removing drop caps - hardly ever in designs and hardly ever used.
Any of these updates should be easily removed when they are not applicable to a particlar project.
So, maybe a function setting makes more sense tenup_disable_dropcaps( 'true' ); ... or something similar.
CC: @fabiankaegy

@fabiankaegy
Will you revisit this and the validity since the 5.8 release and any thoughts on moving this forward.
I think the proper solution now would be a default theme.json with dropcaps removed from paragraphs.
{
  "version": 1,
  "settings": {
      "typography": {
        "dropCap": false
      }
  }
}

If recommending this, we need to also make sure that adding a theme.json file by default will not cause any other issues
Thanks!

@joesnellpdx This is a great point. I think this PR can get closed because it doesn't apply to WordPress 5.8.
I would suggest that we do add theme.json support to the Theme scaffold because it makes a whole bunch of things easier. But there are a few things that will need to get considered. I am creating a ticket for this specifically.


Merge API-endpoints of task-creation

Feature-request
Description
At the moment creating a image-request-task, table-learn-task and so on, have all different API-endpoint. This doesn't scale very well and reduce usability, so the have to be combined to one.

Will be done in context of #26